checksum bypassing

[Charlescrown]

Just need a little info. Some time ago I did my V8 and the cell light came on. Thanks to you guys advising to set the checksum to 170 fixed the problem. I am about to venture into a VN V6. Question is do i need to change checksum number to stop the same problem occuring? If so is it the same? 170 or must I enter another number? Thanks for reading Dave

[antus]

Most the xdf files should calculate the checksum correctly. If they do not, then you can set the program ID to AA (hex) which is 170. It is better to leave the checksum enabled and do it properly so if there is a problem with the chip the CEL (check engine light) can come on and warn something is wrong before corrupted data is used which could potentially cause engine damage.

[Charlescrown]

That's interesting. I was of the impression it had to be changed. With the V8 all I did was change the ignition map a little and the CEL came on so I was advised to change the checksup to 170. Got me wondering why I had to. The car goes a lot better than before by just smooting out the original map which I thought looked pretty sloppy. Thanks will give it a go without changing.

[antus]

It depends if the XDF you use to do the edits has the checksum properly set up in them. It can be calculated, but thats not to say the XDF you were using was set up right. What XDF are you using, and on what program (bin)?

[Charlescrown]

I used the $11A VR Auto Version E XDF and PFPL2416 Bin file. Do you know if that's the correct one?

[VL400]

For $11 you either need to have the program id to AA(170) or use this .. https://pcmhacking.net/forums/viewtopi ... 51&p=31085

[Charlescrown]

Do you know if I have to change anything in the $5? Or will the std checksum work OK?

[VL400]

$5D? It should be ok, but depends on the XDF. Which one are you using and what bin?

[Charlescrown]

The Bin file is ARBP4435 and $5D XDF. I don't have a version of the $5P.

[Charlescrown]

correction a version of the $5D not P