Here I am

Engine/Transmission (1998.5 - 2002) Inside the ECU

Attention: TDR Forum Junkies
To the point: Click this link and check out the Front Page News story(ies) where we are tracking the introduction of the 2025 Ram HD trucks.

Thanks, TDR Staff

Engine/Transmission (1994 - 1998) BD Cool Down Timer Problem

Engine/Transmission (1998.5 - 2002) 3rd vp44 in 4 weeks

Status
Not open for further replies.
Jdonoghue,



What ever happened to the web page you mentioned at the beginning of this thread where you were documenting your work? I tried it today and got a page not found error.



Thanks,



John L.



I recently had to change my ISP. That site was hosted on a PC here at home, and my old ISP was nice enough to let me have a static IP to run a site from. My router doesn't work right with the new DSL service so I may have to find someplace to host those web pages. Until then, I have no way to bring the site back up.
 
I've done a bit of research and I have found that there is a commercially available USB-to-serial cable that can be set up for the 'weird' baud rates that the SCI requires. And it's readily available from most electronics distributors for about $20. The only other component needed is a cable to adapt the serial pin connector to the OBD connector. This means no special circuit board to make to get a laptop to talk to the truck, it will all be in software.



Once the cable arrives here the real fun can begin!



AH! That sounds REAL promising! :DOo.
 
Major success update

Got the USB-Serial cable Friday. Spent a good part of the weekend digging through my old notes, and the code itself. This morning, I was able to upload the original flash file to the test ECU and return it back to its original condition Oo.

So, with a $20 cable, and the program I developed over the weekend, I can now erase and reflash. This is going to get real fun...



I have got my web site back online, and I added a section to track updates as this project moves along. It is at vs18k - Electronics, computers, and Diesel stuff
 
Last edited by a moderator:
JEEZE - you're my HERO! :-laf:-laf



The pointer - AND info works great, but you HAVE to get rid of that dark background - makes the text VERY hard to read comfortably - but a GREAT effort! Oo.
 
This morning, I was able to upload the original flash file to the test ECU and return it back to its original condition
Fantastic! That's great work you're doing.

So, with a $20 cable, and the program I developed over the weekend, I can now erase and reflash.
Boy do I wish I had the ability to upload DC flash files (available on TechAuthority.com) to an ECM. This would eliminate the need for the DRB$$$ Scan Tool.

I have got my web site back online, and I added a section to track updates as this project moves along.
On your web site notes you said:



Other information



It appears that the ECU itself was designed (and possibly manufactured) by Motorola. The ECU software, is unknown. There is no copyright message or any other identifying information in the dump of the flash memory, except the VIN number and the string '091197'. I do not know what language the program was originally written in, probably C, I really don't think something that large would be written in assembly language.



Could that "091197" be the vehicle milage... or maybe the PIN code for a factory security system (if installed).



Best regards,



John L.
 
Fantastic! That's great work you're doing.

Boy do I wish I had the ability to upload DC flash files (available on TechAuthority.com) to an ECM. This would eliminate the need for the DRB$$$ Scan Tool.

On your web site notes you said:



Other information



It appears that the ECU itself was designed (and possibly manufactured) by Motorola. The ECU software, is unknown. There is no copyright message or any other identifying information in the dump of the flash memory, except the VIN number and the string '091197'. I do not know what language the program was originally written in, probably C, I really don't think something that large would be written in assembly language.



Could that "091197" be the vehicle milage... or maybe the PIN code for a factory security system (if installed).



Best regards,



John L.



John,



How does one obtain the flash files from that site? Some time in the future I am going to need to have a complete set of original flash files.



The '091197'. . well, I while working on the 'boot loader' code I found some indication that it is the software release date. There is no way to read/write this area unless you actually overwrite the boot loader itself, which is not normally done.
 
How does one obtain the flash files from that site? Some time in the future I am going to need to have a complete set of original flash files.
There's a section of the site that requires paid access... $20 for 24 hours, $200 for a month, etc. That section of the site has excerpts from the service manuals, TSB's, diagnostic troubleshooting info, etc. You can search for ECM and PCM flash files by year, model, and engine, or by flash file number, or by the VIN if you have it.



Regards,



John L.
 
It appears that the ECU itself was designed (and possibly manufactured) by Motorola.
Now that you mention it. . When i worked for Motorola in Seguin Tx. we actually did make modules for different vehicle mfgs. I remember they did have an extended life cycle test in progress for Cummins modules. . I assumed they were for OTR rigs, but they could have been making ecm's for the 5. 9 as well. I do remember the failure rate was approx 5. 5 per MILLION! They were using the 6 sigma quality process at that time and were trying to improve upon that. (I got to work on LoJack ;)). They were also making modules for Allison Transmissions, cadillac lighting modules, and Jeep Cherokee Chief factory wireless alarm transmitters, Amungst other stuff...

On edit, I can't guarantee i'm remembering the number correctly. I remember it as being 5. 5 failures per million, but gosh that seems almost impossible. . Might have been per thousand, but still thinking "million".
 
Last edited:
Update

More fun with SCI cable. I reflashed the eBay ECU with a hacked version of my truck's original flash file that lets me 'peek' at anywhere in memory. The reflashed unit is in my truck and is operational. I was able to peek at some VP44 CAN messages.



A more detailed explanation is in the project log on my site.
 
Is there a good product to spray in the wire connection of the truck side ecu wires? I think I might have spilled some fuel in there and want to clean it out.
 
Maps and parameters

I've found most of the 2D and 3D maps in the ECU flash file from my truck. I spent some time this afternoon working on the definition file for RomRaider - now I can see cool 3D views of the map tables (and edit them too!).



I've got quite a bit more of digging through the code to nail down what all the maps do. There are also constants that need to be changed (limits, etc. ). I've also got to get back to my hack that will let me download temporary changes to the ECU. I've already hacked a memory read function into the code. memory write will let me temporarily alter stuff with the engine off, instantly, without having to reflash the unit.
 
I've always used this stuff with good results:



#ad



Well, RadioShack didn't have the exact stuff you have here but, what they did have was a very small can of $10 stuff. So, I went with the WD-40 route and rinsed it with alcohol. I'll probably need to buy a new connection now for sure, right? I'm hoping it will all be ok but I suppose I can always use it for a good example in my auto class that i will be teaching this next year. I just graduated and took a job teaching for a heck of alot more money than I have seen in the last 4 years. Now my CTD money pit can be fun again!!
 
That can I pictured IS sorta small - about 4 ounces - but lasts a LONNNNG time, that one is about 5 years old, and still half full - a little goes a long way!



I just used a bit more to clean the trailer plugs on the 5er getting set for our RV trip tomorrow morning...
 
P0602

I've figured out where the P0602 DTC comes from. Interesting because I have seen reports of programmers generating P0602's. It would be an easy patch to get rid of the P0602.
 
Status
Not open for further replies.
Back
Top