EEHack continuous checksum failure ???

[kris72079]

I am attempting to download my stock .bin file from my pcm with no success. I am on EEHack v4.70 and at the end of each attempt I get a checksum fail on download. I grabbed up a different pcm and get the same fault! Ideas? Suggestions?

I also have noticed now that the original PCM doesn't take any of the changes from tunerpro. The load through EEHack shows successful, but even simple adjustments like cmd idle rpm remain the same after flash.

[kur4o]

Check your cable first. If cable is ok, check your PC power supply. Than try to read PCM off the car. I hope you don`t use programm stability test.

[kris72079]

Check your cable first. If cable is ok, check your PC power supply. Than try to read PCM off the car. I hope you don`t use programm stability test.The cable is fine, I can datalog and and write via the cable, however, I can't download. The file transfer occurs all the way to the end and then reports a checksum failure. What's the deal with not using the program stability test? Curious as to why you don't suggest that?

[kur4o]

Open debug window on eehack, check verbose box and post the log after failed read attempt.

[steveo]

thats weird. theres an option in settings to allow a bad checksum for bin downloading. its in advanced, called "save invalid bin". try that, at least you will be able to save the result and compare it to see what's going on.

[steveo]

just out of curiosity what xdf are you editing with? if you use the wrong xdf you could break your bin and checksum but it may still run.... that would explain why nothing is working

[kris72079]

just out of curiosity what xdf are you editing with? if you use the wrong xdf you could break your bin and checksum but it may still run.... that would explain why nothing is working
What do you mean steveo? I downloaded the stock tune from your (pretty sure its yours) fbodytech site. I downloaded and flashed my original pcm with 16209481--1995--F--AUTO 3.23 as that is the year/trans/body/rear combo currently assembled. The engine/trans/pcm was donated from a b-body (16209331). The newly acquired pcm is a 1995--F--AUTO 2.73 (16209471).

[kris72079]

Open debug window on eehack, check verbose box and post the log after failed read attempt.Ypu want the log in the debug window after attempting to read the stock file?

[kur4o]

yes, but make sure Verbose box is checked.
It will be a long log, you`d better save it as txt file with Notepad.

[kris72079]

After checking save invalid bin the the advanced tab, I do not get automatically prompted to save the file after download but I do get prompted to save a log when I attempt to close the program. The log shows the time when I attempted to download the stock bin from the pcm. When I do open that file it certainly does not look right at all. Like this for example...12067

[kris72079]

yes, but make sure Verbose box is checked.
It will be a long log, you`d better save it as txt file with Notepad.where would you like the notepad file?

[JustinSEO]

Looks like a bad or invalid XDF was used to write the bin maybe? I had this happen one time before, I had to get the latest XDF and I updated all my tunerpro stuff with latest info. Then started from a stock calibration and tried again; worked great. The numbers were all messed up in Tunerpro before I had the proper XDF, kind of like your picture.

There are many versions floating around. Find the right one or latest one (believe there is a thread here).

[kris72079]

Looks like a bad or invalid XDF was used to write the bin maybe? I had this happen one time before, I had to get the latest XDF and I updated all my tunerpro stuff with latest info. Then started from a stock calibration and tried again; worked great. The numbers were all messed up in Tunerpro before I had the proper XDF, kind of like your picture.

There are many versions floating around. Find the right one or latest one (believe there is a thread here).
The image shown is pulled from a PCM that I have yet to flash anything to...Although the pcm is "supposed to be" virgin, but as with buying anything used, how do you really know? I'm going to try to flash it with a "factory file" from here and see what happens.

Anyone have any further suggestions as to why the mated PCM wont react to any changes/take a new load???? There are a few things that are pissing me off with this thing right now, and without being able to verify if the PCM is at fault/failing makes troubleshooting difficult.

[kris72079]

Open debug window on eehack, check verbose box and post the log after failed read attempt.

12073

[kur4o]

Everything looks ok with reading.
Can you open eehack at advance setting there is a checkbox save invalid bin. Check the box and do a read, then post the bin here.

[steveo]

i bet the bin is EEB

[JustinSEO]

If it's EEB you will need a different xdf for tunerpro. Download EEB and check if it loads properly. If it does, find an EE file stock and flash it as is then go modify it and make changes you want... I didn't like editing the EEB as support in TunerPro definition wasn't as filled.. especially when learning.

I bricked one PCM to date going from EEB to RE. Make sure you start stock file with EE.. to avoid issues.

[kur4o]

I checked the vin and it is from 95. I will guess some tuner disabled checksums. I would like to see what else is changed.