Consult Checksum Invalid?

[jaqattack02]

Bought an ECU already installed with the board from another someone who had been running it in his car. I sent him an email and he said he never had any problems connecting to the ECU. Installed it in my car and I can't get it to connect to my laptop. When I hit the consult button it says Consult Checksum Invalid and then something about the address file. I selected the 84-85 address file. It seems to be getting something from the ecu because if I pick a different year of Z31 it will pop up and tell me its the wrong address file and that I need the 84-85 one. I read through the Nistune Diagnostics document and tried a couple things that were suggested there and they didn't help. I also tried uninstalling and reinstalling Nistune from my laptop (laptop is a Core2Duo Lenovo T60P running Win7x64 if it makes a difference). The ECU seems to be working fine as I can crank the car over and it will start and idle, but won't do much more. Wideband also said it was running crazy rich. Anyone have any ideas?

[Matt]

Does the checksum error only occur if engine is running?

What is the part number on the Nistune board?

[jaqattack02]

We didn't try connecting to consult while the engine was running, only while the key was in the 'on' position. I can try it while running. I'll see about pulling the ECU next time I have a chance and get the number.

[Matt]

Number is written on the board normally. Debug log file if you could email that through would help also. Dont bother getting engine running if its doing it with the ignition off

[jaqattack02]

Ok, I cracked it open tonight. It said "Type 1 NIStune Interface R8". Picture of the board is below.


Also, here is a screenshot of Nistune giving me the error, in case that helps any.


Where do I find the debug log? I looked through the directories and didn't see anything.

Feel free to email me if that would be easier.

[Matt]

02P03 is for 1984 model Z31 so that is the correct address file loaded

I'm not sure why you have a checksum error. File > Configuration > Debug logging to enabled debug log and email to info[at]nistune.com so I can have a look through it. Most likely board could require reprogramming

[jaqattack02]

Ok, thanks. I'll see about getting the debug logs for you when I get home tonight.

[jaqattack02]

I emailed the debug log to you.

[Matt]

responded. board needs reprogramming. Got some weird response back from it

[jaqattack02]

Appreciate all the help. I'll get in touch with AVP about getting it fixed.

[jaqattack02]

Fixed in 0.12.5

[Matt]

Thanks for the update. The other customer with the earlier firmware said his was working also