Ok, so I'm not sure if I mentioned it or not but I am the ultimate NOOB when it comes to CMD. I am doing my best to learn by reading all I can here and watching some youtube vids. I decided to just try and read the eprom over the OBD port in the car (not trying to get into bootmode) just to get a feel for the program. I've attached a screenshot showing my result. If someone would be so kind and maybe help walk me through this I would be truly greatful. I am doing my best not to just ask for the IMMO off. I would like to learn how to edit it myself but haven't a clue where to start. If I am not mistaken, it is trying to access the ecu in bootmode? The way I understand things is that you don't have to be in bootmode to read the ecu over the OBD. Am I incorrect?

The pictures are both sockets. Imagine that as the OBD socket on your car not your cable.

I don't think I mentioned why I needed to do this and hopefully it helps someone similar to myself in the future. I have 2001 VR6 Jetta that was misfiring on cylinder #1. After much troubleshooting it turned out to be the injector driver in the ecu. I purchased a used ecu from the same model car thinking much like Hondas that the ecus are interchangeable. Obviously that isn't the case which after many local quotes of $150+ for an IMMO off led me here. Having no CMD experience the task seemd daunting but this site was a huge help. I documented in posts above about not being able to read the ecu over the in car OBD port. After making a jumper harness and getting boot mode on the bench here are my results.

I was able to read and save the 95040.bin off of the bad ecu which matches the cluster and key



Initially I couldn't get it to write but after switching the baud rate I was able to write the 95040.bin from the bad ecu to the new to me used one



At this point I was elated but cautiously optimistic about it working in the car. I am happy to report that it did. It fired right up with no misfire. These are prob baby steps for most but I am pretty proud of myself lol. Just thought I would share and thank everyone on this topic and forum who takes the time to post and create a library of information that can be used by NOOBS like me.

Thanks again.

-Ryan

Exactly. Only prob now is the ecu was out of an automatic and is searching for the auto trans leaving me with a CEL lol. Next stop, coding.........

What car? Which ECU?

Are you using proper ECU for your car?
Does it have proper communication with other modules on CAN?

You can pretty easily open the cluster up and desolder the light, or slip a piece of plastic over it, on many of the clusters I have done.


A word of advice. I spent 17 hours or so trying to get this program to work using a variety of cables, including a true hex can vcds cable, a real vag tacho cable, a fake vag tacho cable, chinese vag k can, chinese vag commander, and probably a couple others. NONE of them worked for boot mode, best I could do was the real licensed VCDS Hex Can cable was able to read in OBD mode.

I also tried on Windows 7 and Xp. In the end, the blue KKL cable with the horseshoe looking emblem and the CE sticker under it is what worked for me, easily using Vista Driver CDM 2.04.15 WHQL drivers I got off this site. So if you're having issues, I suggest just buy the 9 dollar with shipping cable, or find somebody to borrow from. Because nothing else worked for me.