I had it working once, just fine.
I think I might have shorted something out tho, because I went to use it again and it wouldnt work, and some of the wires looked melted (on the cable I made, not on the factory harness)
Now, on a new cable (continuity checks out great), it wont read the ROM id
Ive checked and doublechecked the pinouts, and everythings fine.
Is it possible that I wrecked the Scantool port? It seems unlikely that I could do that without damaging the ECU.
Scantool doesnt read ROM id
Moderators: Helpinators, Moderators
Scantool doesnt read ROM id
98 Steel Widebody RSTi-RA Superbeast
-
- Vikash
- Posts: 12517
- Joined: Sun Nov 03, 2002 2:13 am
- Location: USA, OH, Cleveland (sometimes visiting DC though)
- Contact:
Not reading the ROM ID just means it's not communicating successfully.
Woah. What looked melted? How exactly would you have shorted something out?
It's possible that the ECU's diagnosis port has been damaged. It has some basic protection circuitry but it's always possible. It certainly is possible to kill the port without damaging other things in the ECU.
You could pop the ECU's case open and look for scorch marks or something.
Woah. What looked melted? How exactly would you have shorted something out?
It's possible that the ECU's diagnosis port has been damaged. It has some basic protection circuitry but it's always possible. It certainly is possible to kill the port without damaging other things in the ECU.
You could pop the ECU's case open and look for scorch marks or something.
"Just reading vrg3's convoluted, information-packed posts made me feel better all over again." -- subyluvr2212