1994 Corvette EEHack Errors

[RISK81]

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.

[steveo]

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.

[RISK81]

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.

[steveo]

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

[RISK81]

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...

[RISK81]

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

[steveo]

after the failed read did you actually go and reset the ecm by pulling power for a bit?

does datalogging work at all?

[spfautsch]

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.

[RISK81]

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).