nurbs
New Member
Posts: 25
|
Post by nurbs on Jan 9, 2023 4:09:04 GMT
Hi Forum. Received my adapter a couple days ago ( 3+ weeks to the US for others that may be waiting ). I've only played with for about an hour, but I like the GUI interface and appreciate the layout and quality of the board! Update of firmware using menu option didn't work for me, but the manual method did ( from 0.2.1 to 0.2.8 ). Although "Connect" and connected testing so far work any use of "disconnect" results in GUI hanging. I was able after some manipulation of window size within C# source code to get the GUI to load correctly with WINE on Linux. My development happens in Linux so being able to use the program with WINE would be easier. Remaining problem is that diagnostic pane layout with some characters not rendering ( row and column separators ) which is making difficult to read values.
So in creating a graphical interface and exploring data I believe I need to get the data, starting at least with my module, into data structures that I can manipulate. Towards that end it seems that DRBIII is currently in some proprietary binary file. Does anybody know of some other format that I can migrate/manipulate in conventional database tools or language interfaces ?
Sven
|
|
|
|
Post by admin on Jan 9, 2023 9:25:29 GMT
I hear similar issues from Linux users. At the moment I don't know how to resolve them.
We tried Mono to run the GUI but USB communication doesn't work.
WINE is a step forward.
Please post some pictures.
The only known/public DRB3 database reader is written by Kyle Repinski (included in GUI folder).
The DRB3 Emulator software by Controller Technologies Corp uses the same database but to get to its handler one needs to disassemble the application.
I tried but only got so far that the app checks if database exists.
So as of now there's no database conversion tool available.
All I could extract from the database regarding Cummins ECM is now in the SCIPCM.cs source file.
Within the "Engine tools" menu try Detecting hardware type, or select "CUMMINS".
Explore low-speed mode features, then switch to high-speed mode (click on 62500 baud button) and select F8/FB/FC/FD RAM tables.
Listbox updates with relevant PIDs.
Select one or more and click Read. Optionally check "repeat" and set repeat interval to update values in real-time.
|
|
nurbs
New Member
Posts: 25
|
Post by nurbs on Jan 12, 2023 4:19:20 GMT
Thanks for DRB3 info and the updates to SCIPCM.cs, looking forward to trying tomorrow.
|
|
nurbs
New Member
Posts: 25
|
Post by nurbs on Jan 14, 2023 7:12:40 GMT
Unsuccessful so far in trying to see any SCI activity. PCI is working. "Engine tools" menu option is only available after I connect and then selecting "Engine Tools" changes the button that now says disconnect to connect. Detect doesn't report any visible change or allow for reading of data. I tried CUMMINS along with a few others that seemed to make sense like CM845. When I generate an SCI message the TX and message is shown in USB communication, but I wonder if data is going out on the bus. I'll try to confirm that tomorrow with a scope measuring the "receive" side ( reference to ground ) ? Tried briefly today but so hard to maintain terminal contact backprobing unsealed DLC connector. My DLC has SCI RECEIVE (PCM) on 12 & SCI TRANSMIT (PCM) on 7 and truck schematic shows direct connection to CM845 ECM. No SCI wires for TCM in DLC which makes sense given manual transmission.
|
|
nurbs
New Member
Posts: 25
|
Post by nurbs on Jan 14, 2023 7:24:34 GMT
In reviewing User's Guide I now realize that I should have configuration "B" with dedicated SCI TPM wires. I think I was on "A" by default today.
|
|
|
|
Post by admin on Jan 14, 2023 8:07:45 GMT
Yes, I forgot to mention that there are two SCI-bus channels. A-configuration is installed most of the time. B-config came later in years. 12/7 is definitely B-config:  |
|
nurbs
New Member
Posts: 25
|
Post by nurbs on Jan 16, 2023 2:30:37 GMT
So far everything works! Correctly identifies CM848 ( thought it was CM845 so I've already learned something from it ). I've tried several low-speed SCI commands without issues. I'll try high-speed stuff tomorrow including RAM table experiments. Kudos on the great documentation too, so unusual in my experience.
|
|
|
|
Post by admin on Jan 16, 2023 9:42:16 GMT
Great!
For future reference, EEPROM read/write should work as well:
> txsearch CM848
READ_ECM_MODIFIER_CM848: SCI; xmit: 28-00-00; sc: ECM; 0x800079f2
WRITE_ECM_MODIFIABLE_CM848: SCI; xmit: 27-00-00; sc: ECM; 0x800079f3
These are well-known SBEC3/JTEC commands.
I suppose the write permission unlock mechanism is the same, given that so far everything matched.
ECM is unlocked automatically when you try to write EEPROM bytes.
GUI prioritizes the legacy unlock method (SCI 2B). Your ECM may reject this command.
In this case go to Engine tools, and get level 1 access without legacy mode checked (SCI 35 01).
In "Tools / Read/Write memory" you should be able to manipulate EEPROM content.
Buttons:
- BAK = backup,
- RES = restore.
Both read/write 512 bytes in one go.
You can also read/write individual byte(s) or known fields (VIN).
RAM read/write may not work in this menu. Only SBEC3A seems to have this command.
You are quite welcome! I shall rework the documentation (and move it online, like GitHub wiki) to reflect the huge development made last year.
This right here is making a difference in real-time. Brilliant!
|
|
nurbs
New Member
Posts: 25
|
Post by nurbs on Jan 16, 2023 16:13:43 GMT
|
|
|
|
Post by admin on Jan 17, 2023 15:15:48 GMT
Agreed, this is more informative than just lines of texts.
I will incorporate similar diagrams into the docs!
|
|
