Page 1 of 2 12 LastLast
Results 1 to 15 of 18

Thread: EEHack continuous checksum failure ???

  1. #1
    Carb and Points!
    Join Date
    Aug 2017
    Age
    44
    Posts
    9

    EEHack continuous checksum failure ???

    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.

  2. #2
    Fuel Injected!
    Join Date
    Mar 2013
    Posts
    1,470
    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.

  3. #3
    Carb and Points!
    Join Date
    Aug 2017
    Age
    44
    Posts
    9
    Quote Originally Posted by kur4o View Post
    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?

  4. #4
    Fuel Injected!
    Join Date
    Mar 2013
    Posts
    1,470
    Open debug window on eehack, check verbose box and post the log after failed read attempt.

  5. #5
    LT1 specialist steveo's Avatar
    Join Date
    Aug 2013
    Posts
    4,007
    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.

  6. #6
    LT1 specialist steveo's Avatar
    Join Date
    Aug 2013
    Posts
    4,007
    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

  7. #7
    Carb and Points!
    Join Date
    Aug 2017
    Age
    44
    Posts
    9
    Quote Originally Posted by steveo View Post
    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).

  8. #8
    Carb and Points!
    Join Date
    Aug 2017
    Age
    44
    Posts
    9
    Quote Originally Posted by kur4o View Post
    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?

  9. #9
    Fuel Injected!
    Join Date
    Mar 2013
    Posts
    1,470
    yes, but make sure Verbose box is checked.
    It will be a long log, you`d better save it as txt file with Notepad.

  10. #10
    Carb and Points!
    Join Date
    Aug 2017
    Age
    44
    Posts
    9
    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...Capture.PNG

  11. #11
    Carb and Points!
    Join Date
    Aug 2017
    Age
    44
    Posts
    9
    Quote Originally Posted by kur4o View Post
    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?

  12. #12
    Fuel Injected!
    Join Date
    Aug 2014
    Age
    32
    Posts
    32
    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).

  13. #13
    Carb and Points!
    Join Date
    Aug 2017
    Age
    44
    Posts
    9
    Quote Originally Posted by JustinSEO View Post
    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.

  14. #14
    Carb and Points!
    Join Date
    Aug 2017
    Age
    44
    Posts
    9
    Quote Originally Posted by kur4o View Post
    Open debug window on eehack, check verbose box and post the log after failed read attempt.
    1.txt
    Last edited by kris72079; 08-31-2017 at 04:09 AM.

  15. #15
    Fuel Injected!
    Join Date
    Mar 2013
    Posts
    1,470
    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.

Similar Threads

  1. Disabling Checksum
    By wanderingturtle in forum TunerPro Tuning Talk
    Replies: 3
    Last Post: 08-01-2017, 05:36 AM
  2. Would Checksum failure cause these issues?
    By trippyjoey in forum GM EFI Systems
    Replies: 8
    Last Post: 10-01-2014, 09:22 PM
  3. ERROR: PROM I/O returned failure?
    By brian617 in forum TunerPro Tuning Talk
    Replies: 4
    Last Post: 10-14-2013, 01:51 AM
  4. Disabling Checksum
    By POZE in forum GM EFI Systems
    Replies: 7
    Last Post: 01-14-2013, 06:21 PM
  5. Checksum disable ('165), TP5
    By dyeager535 in forum GM EFI Systems
    Replies: 4
    Last Post: 07-24-2012, 06:32 AM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •