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

Thread: 1994 Corvette EEHack Errors

  1. #1
    Electronic Ignition!
    Join Date
    Mar 2019
    Posts
    13

    1994 Corvette EEHack Errors

    Hello,

    I have a few questions regarding utilizing EEHack with my 1994 Corvette (LT1 OBD1).

    I have recently rebuilt the engine and am at the point of tuning (engine runs, have driven the car 100 miles +). I increased the compression and changed out the factory LT1 cam with a LT4 Hot Cam kit with 1.6rr. With the increased duration and compression I believe I should retune the vehicle.

    I have purchased a ALDL (OBD1 w/16 pin connector) from ALDL cables. Installed the software (EEHack) and am now attempting download by factory tune to save if ever needed in the future before proceeding with writing a new tune.

    Upon connection of the software to the vehicle I notice that my "Service ABS" and "Service ASR" light illuminate after I am connected via EEHack... (no other issues with these lights just wanted to highlight that they are illuminated).

    Once I proceed with downloading the factory tune I am greeted with an error at the end "Checksum FAIL in downloaded bin! Bin might be corrupt". Also I have ran the stability test and also received an error that reads "TSIDE_VPP_REMOVE routine upload error".

    I have checked the "save invalid bin" box under settings - advanced but am still encountering the same failure notice.

    I do not have a new tune yet nor have I tried to upload a new tune yet, just verifying everything before uploading.

    I am utilizing EEHack version V4.70, vehicle battery connected to a trickle charger, laptop connected to charger.

    Any suggestions? Any help would be greatly appreciated. '

    Thank in advance.

  2. #2
    LT1 specialist steveo's Avatar
    Join Date
    Aug 2013
    Posts
    4,007
    corvettes are bitchy for sure due to how many devices are on that same aldl bus line. make sure the 'silence extra modules' thingie is checked, that might help. the connection code in 4.7 has been fairly stable for most people but some cars still experience problems. i never tested it on a 'vette, someone else wrote that part of the code.

    first, don't ever write a bin until you can read successfully, as the procedure is similar, but a failure during WRITE will likely cause your ECM to never wake up again.

    if all else fails, i think if you pull some fuses so only the ECM has ign power, you can get around it. this might involve switching to f-body connection mode (as the CCM wouldn't respond as expected)

    you could also just snip the aldl data wire near the ECM and put a connector there or something, and when you want to flash, unhook it, jumper it to your ALDL cable and a good engine ground. that way it's just you and the ECM and no other 'vette accessories in the way.

  3. #3
    Electronic Ignition!
    Join Date
    Mar 2019
    Posts
    13

    ABX File

    I read somewhere that possibly I need a different ABX file due to constant communication with the CCM? Sorry this is completely new to me just trying to understand the ALDL data stream.

  4. #4
    LT1 specialist steveo's Avatar
    Join Date
    Aug 2013
    Posts
    4,007
    you mean adx file. those are for tunerpro logging, eehack doesn't use them. the equivalent in eehack is just selecting the correct vehicle type in settings

  5. #5
    Electronic Ignition!
    Join Date
    Mar 2019
    Posts
    13
    Quote Originally Posted by steveo View Post
    make sure the 'silence extra modules' thingie is checked, that might help.
    steveo, the "silence extra modules" you mention, is this located in the settings tab of EEHack? I am thinking now that is why my ABS and ASR lights activate when I am connected as there is now a new piece of hardware introduced onto ALDL data stream...

  6. #6
    Electronic Ignition!
    Join Date
    Mar 2019
    Posts
    13
    No luck with the "Silence extra modules" if anything the box not checked prevented the ABS light from illuminating.

    Below is my debug log and a few pictures of the errors and settings

    Loading Definition DEVICE=0xF4 MSG=0x0
    Loading Definition DEVICE=0xF4 MSG=0x1
    Loading Definition DEVICE=0xF4 MSG=0x2
    Loading Definition DEVICE=0xF4 MSG=0x3
    Loading Definition DEVICE=0xF4 MSG=0x4
    Loading Definition DEVICE=0xF4 MSG=0x5
    Loading Definition DEVICE=0xF4 MSG=0x6
    Loading Definition DEVICE=0xE4 MSG=0x0
    Loaded 1014 elements into 8 definitions.
    VERSION re-checking, network went online!
    VERSION offline status, skipping versioning
    Using monotonic reference clock.
    EEHack Version 4.70
    Current OS : Windows 10
    Built with THROTTLE_MS=2
    Opened serial port COM4 Description USB Serial Port MFR FTDI
    START SILENCE ROUTINE
    Opened serial port COM4 Description USB Serial Port MFR FTDI
    START SILENCE ROUTINE
    SERIAL: DEVICE/MODE MISMATCH: *F4922100000000000000007C3E00000040000200FFFF00FF0 24439452822F41E0078F464616565008080808000000000000 0008F2000000000000000000000B6
    Opened serial port COM4 Description USB Serial Port MFR FTDI
    START SILENCE ROUTINE
    SERIAL: WAITED_TOO_LONG in serial_read_packet
    SERIAL: WAITED_TOO_LONG in serial_read_packet
    SERIAL: WAITED_TOO_LONG in serial_read_packet
    SERIAL: WAITED_TOO_LONG in serial_read_packet
    Opened serial port COM4 Description USB Serial Port MFR FTDI
    START SILENCE ROUTINE
    Opened serial port COM4 Description USB Serial Port MFR FTDI
    START SILENCE ROUTINE
    Opened serial port COM4 Description USB Serial Port MFR FTDI
    START SILENCE ROUTINE
    SERIAL: WAITED_TOO_LONG in serial_read_packet
    Opened serial port COM4 Description USB Serial Port MFR FTDI
    START SILENCE ROUTINE
    SERIAL: WAITED_TOO_LONG in serial_read_packet

    Read PCM Error_3-25-19.jpg
    Stability Test Error.jpg
    Read PCM Error_3-25-19.jpg
    Settings Main 3-26-2019.png
    Settings 3-26-2019.png
    Last edited by RISK81; 03-27-2019 at 03:31 AM. Reason: Added Error Picture

  7. #7

  8. #8
    Fuel Injected! spfautsch's Avatar
    Join Date
    Apr 2015
    Location
    Montgomery City, MO
    Age
    52
    Posts
    883
    RISK81-

    You want the ABS and ASR MILs (service lights) on when using any ALDL programming tool on these cars. These modules as well as the CCM all talk on the ALDL and the code I added sends packets on the bus to tell these modules to stop talking until a "resume comms" packet is sent to them.

    If you're having problems with the stability test I'd try a different cable if possible. Definitely don't attempt to flash until the stability test succeeds.

    With all that in mind, I don't think I've ever read the bin from mine using eehack either. I did try to once last year but there was some problem (which I unfortunately don't recall). I would suggest trying winflash to read your bin initially. If it won't work that's another sign your cable isn't playing nice.

  9. #9
    Electronic Ignition!
    Join Date
    Mar 2019
    Posts
    13
    Quote Originally Posted by steveo View Post
    after the failed read did you actually go and reset the ecm by pulling power for a bit?

    does datalogging work at all?
    steveo-

    Power is cycled after every failure by removing negative battery lead for a few minutes.

    I can datalog but I can not recall the playback due to an error stating that I am missing a .CSV files (I can see the file but can not open it via EEHack).

  10. #10
    Electronic Ignition!
    Join Date
    Mar 2019
    Posts
    13
    Quote Originally Posted by spfautsch View Post
    RISK81-

    You want the ABS and ASR MILs (service lights) on when using any ALDL programming tool on these cars. These modules as well as the CCM all talk on the ALDL and the code I added sends packets on the bus to tell these modules to stop talking until a "resume comms" packet is sent to them.

    If you're having problems with the stability test I'd try a different cable if possible. Definitely don't attempt to flash until the stability test succeeds.

    With all that in mind, I don't think I've ever read the bin from mine using eehack either. I did try to once last year but there was some problem (which I unfortunately don't recall). I would suggest trying winflash to read your bin initially. If it won't work that's another sign your cable isn't playing nice.
    Spfautsch-

    Thanks for the explanation regarding the MIL's, I have a better understanding now.

    I'll attempt to use winflash tonight to read the bin, I'll update with results.

    Out of curiosity, is there checksum failure a Corvette related issue? Are F&B body's able to read the bin?

    Thanks

  11. #11
    Fuel Injected! spfautsch's Avatar
    Join Date
    Apr 2015
    Location
    Montgomery City, MO
    Age
    52
    Posts
    883
    Quote Originally Posted by RISK81 View Post
    Thanks for the explanation regarding the MIL's,
    No problem - I also meant to mention that when logging the ASR will be disabled and none of the functions of the DIC except the speedometer and odometer will work i.e. MPG gauge, temp volts, etc. I've yet to determine whether ABS functions.

    Quote Originally Posted by RISK81 View Post
    I'll attempt to use winflash tonight to read the bin, I'll update with results.

    Out of curiosity, is there checksum failure a Corvette related issue? Are F&B body's able to read the bin?
    The checksum failure probably isn't a Y body issue. I suspect you will have a similar problem with winflash as well. My guess would be a problem with your cable and / or a USB power problem. It seems like there was another complaint from someone using this particular cable sometime last year but unfortunately I can't find the thread. There was discussion about the merits of using a ready-made cable with "support" versus making one from a $5 USB adapter board that needed only two wires attached and the rx + tx lines connected.

    I will try to read my bin as soon as possible just to verify it can do it, but I'm a few days away from having my ride running again so I might not be able to get there until late this weekend or early next week. I've flashed hundreds of bins with eehack without pulling any fuses or cutting any wires, but I can't recall reading one. But my memory is crap so that doesn't mean it never worked.

    Edit: Added "pulling fuses / cutting wires" qualifier to next to last sentence. Shame on you Steveo for suggesting the wire cutter approach. ;-)

  12. #12

  13. #13
    Fuel Injected!
    Join Date
    Nov 2017
    Location
    Californiacation
    Age
    57
    Posts
    811
    Quote Originally Posted by steveo View Post
    if you aren't cutting a few wires, it isn't really a project.
    -Carl

  14. #14
    Fuel Injected!
    Join Date
    Jan 2015
    Posts
    111
    I’d bet money it’s your cable. Other people have had issues whether diy cables or cheaper ones.

    I personally have a moates cable and while pricey ($80), I’ve never had a single issue. I’ve flashed dozens of LT1 vehicles with EEhack including my own corvette multiple times and never had a single connection issue.

  15. #15
    LT1 specialist steveo's Avatar
    Join Date
    Aug 2013
    Posts
    4,007
    when i developed eehack i used a cheap ftdi board from ebay, one of the ones that are intended for arduinos for a few bucks. it worked great both on the bench and in the car.

    i think this helps too http://fbodytech.com/ftdi-serial-lat...readed-eehack/

Similar Threads

  1. 1994 Corvette Cam Change
    By Coltomi in forum GM EFI Systems
    Replies: 3
    Last Post: 05-30-2017, 06:51 PM
  2. Data Errors 1227747 $42 ?
    By EagleMark in forum GM EFI Systems
    Replies: 14
    Last Post: 09-04-2013, 04:24 AM
  3. DA Data Errors?
    By xtreamvette69 in forum TunerPro Tuning Talk
    Replies: 55
    Last Post: 08-31-2013, 05:54 PM
  4. DA Data errors
    By brian617 in forum TunerPro Tuning Talk
    Replies: 15
    Last Post: 05-16-2013, 05:51 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
  •