Been using a romulator to make loads of small amendments to an otherwise stock LO3.

Now that the VE tables are all nice and 128ish and the timing has been set, i wanted to burn a chip and remove the romulator.

I have tried a few different 2732a's and all result in a fast flashing SES light, i have done a few searches and the checksum looks like a likely candidate.

I am using tunercat (cos it seems easier for a noob than Tunerpro)

I can confirm that the blank checks are all ok FF's after a 5 min UV bath.
The device programs ok and verifies ok.
I can reread the bin and when compared in tunercat they are identical.
When i use the PP2 verify function it says all is ok.

I am guessing the checksum might be the prob.
I dont change start addresses or anything like that.
I dont try to stack bins.

My romulator is permanently connected to a second 1228746 ecu that i ebayed, i just umplug that at the loom and plug the original ecu (with the freshly burnt chip back in).

Any ideas where to go next ?

 

Try burning $AA into the PROM ID location. That will tell the ECM to ignore a checksum error and continue reading the code...at least that's my understanding of it.

 

Jeepguy

thanks for that, i put a decimal value of 170 in the mask ID revurned and all went OK.

Many thanks !

 

No problem...

 

Anything that allows for on the fly tuning, bypasses the check sum. So as mentioned you have to run any .bin from such devise thru an editor to refigure the check sum.

When your done it's a good idea to refigure the checksum, so the ecm has a lil protection in case the prom gets corrupted for some reason.