Wondering if anyone can help me with a bin file?

**stingr** · 12-30-2020

I'm new to the forum and haven't found everything on here yet. I'm wondering if someone can help me out here. I need a oem bin file for a 1993 lt1 trans am with a 6 speed. I found the auto but not the 6 speed. I'm using tunerpro rt and I need this bin to get up and running. Thanks

**dave w** · 12-30-2020

Link to gearhead-efi 1992 - 93 LT1 information, including .bin files (post #3): http://www.gearhead-efi.com/Fuel-Inj...mation-DA2-DA3

dave w

**steveo** · 12-30-2020

i don't know that we actually have one. do you have a working ECM from a 6 speed? i'm pretty sure i can assist you in dumping the bin via your aldl port, then we'll have one

**stingr** · 12-31-2020

Originally Posted by dave w

Link to gearhead-efi 1992 - 93 LT1 information, including .bin files (post #3): http://www.gearhead-efi.com/Fuel-Inj...mation-DA2-DA3

dave w

Are the stock tunes for a f-body and a corvette the same?

**dave w** · 12-31-2020

Originally Posted by stingr

Are the stock tunes for a f-body and a corvette the same?

The quick answer is likely no. Maybe there is something about the Corvette using a CCM / BCM?

The quick answer is likely yes. Maybe the fuel / air / spark parameters are the same?

TunerPro has a "COMPARE" in the tool bar to identify the differences between two different binary files with the same definition, like $DA2.

dave w

**stingr** · 12-31-2020

Originally Posted by steveo

i don't know that we actually have one. do you have a working ECM from a 6 speed? i'm pretty sure i can assist you in dumping the bin via your aldl port, then we'll have one

I do but I'm having a tough time getting my aldl to connect. Intalled drivers and when I test it says its working but the damn thing won't connect up to read on the car.

**2xls1** · 12-31-2020

93 is a Memcal computer. Are you reading those through the ALDL now? I haven't messed much with OBD1 in years but here are a couple of 93 bins.

**steveo** · 01-01-2021

Originally Posted by 2xls1

93 is a Memcal computer. Are you reading those through the ALDL now?

yeah, for any obd1.5 (8192 baud style) device that GM left the mode 2 'dump memory' command enabled and unlocked for (which seems to be all of them). i built a sequential read tool into my flashhack tool for those devices. you could probably dump the rom of an ABS controller using it

**2xls1** · 01-01-2021

Originally Posted by steveo

yeah, for any obd1.5 (8192 baud style) device that GM left the mode 2 'dump memory' command enabled and unlocked for (which seems to be all of them). i built a sequential read tool into my flashhack tool for those devices. you could probably dump the rom of an ABS controller using it

So just reading them or flashing them too?

**NomakeWan** · 01-08-2021

Originally Posted by 2xls1

So just reading them or flashing them too?

Reading only. The EPROM inside the MEMCAL is not an EEPROM; there's no way to command it to erase and reprogram.

**2xls1** · 01-08-2021

Originally Posted by NomakeWan

Reading only. The EPROM inside the MEMCAL is not an EEPROM; there's no way to command it to erase and reprogram.

I've erased and programmed many of them years ago. I guess my confusion or maybe better surprise is what good is the ability to read them from the ALDL when you can't program them from the ALDL unless i guess just the novelty of being able to. Or maybe they were being replaced by EEPROMs.

**NomakeWan** · 01-08-2021

Originally Posted by 2xls1

I've erased and programmed many of them years ago. I guess my confusion or maybe better surprise is what good is the ability to read them from the ALDL when you can't program them from the ALDL unless i guess just the novelty of being able to. Or maybe they were being replaced by EEPROMs.

There are two issues here, and I'll try to clarify them in a way that will make sense.

Firstly, to my knowledge, all of the ROM chips used in pre-1994 ECMs were EPROMs. They are either write-once, or have a sticker covering a window that houses a UV-reactive element. By exposing this element to UV light (UV-C, to be precise), it resets the values of the cells on the chip. This is a tedious process, and you have to read back the chip afterward to make sure it's actually been erased, but it can be done. At which point you can then insert the chip into a programmer and burn it again.

Second, even if you were to expose the UV element with the chip in its socket (or replace the EPROM with an EEPROM), these chips still require a very specific sequence of signals in order to enter programming mode. One of those signals is a high voltage, usually between 12V~20V. If the circuitry in the ECM is not designed to provide this sequence of signals, then you cannot enter programming mode, and as such, there is no way to burn a chip in situ. You would need to remove the chip from the ECM and place it into a chip burner as designed.

The 1994~1997 LT1/LT4/L99 PCM changed that, by both providing EEPROM chips as storage and also providing the appropriate circuitry and microcode to command an erase and enter programming mode for the chips. Earlier ECMs do not have this circuitry, and as such, are wholly unable to be reprogrammed in-place.

Reading the contents of a chip, however, is just a question of having the command present. It requires no special mode or high voltage on the part of the chip itself. At that point it's only a protocol issue.

**2xls1** · 01-09-2021

Originally Posted by NomakeWan

There are two issues here, and I'll try to clarify them in a way that will make sense.

Firstly, to my knowledge, all of the ROM chips used in pre-1994 ECMs were EPROMs. They are either write-once, or have a sticker covering a window that houses a UV-reactive element. By exposing this element to UV light (UV-C, to be precise), it resets the values of the cells on the chip. This is a tedious process, and you have to read back the chip afterward to make sure it's actually been erased, but it can be done. At which point you can then insert the chip into a programmer and burn it again.

Second, even if you were to expose the UV element with the chip in its socket (or replace the EPROM with an EEPROM), these chips still require a very specific sequence of signals in order to enter programming mode. One of those signals is a high voltage, usually between 12V~20V. If the circuitry in the ECM is not designed to provide this sequence of signals, then you cannot enter programming mode, and as such, there is no way to burn a chip in situ. You would need to remove the chip from the ECM and place it into a chip burner as designed.

The 1994~1997 LT1/LT4/L99 PCM changed that, by both providing EEPROM chips as storage and also providing the appropriate circuitry and microcode to command an erase and enter programming mode for the chips. Earlier ECMs do not have this circuitry, and as such, are wholly unable to be reprogrammed in-place.

Reading the contents of a chip, however, is just a question of having the command present. It requires no special mode or high voltage on the part of the chip itself. At that point it's only a protocol issue.

You're not telling me anything I don't already know. Now tell me what good is the ability to read the program from the ALDL.

**In-Tech** · 01-09-2021

Originally Posted by 2xls1

You're not telling me anything I don't already know. Now tell me what good is the ability to read the program from the ALDL.

Cuz it's cool

I wish I could have read every single thing I came across without having to find the ecu, pull the chip, read it, put it back, reinstall the ecu, hope I didn't fook up old wiring by moving it just to add to my archives.

**2xls1** · 01-09-2021

Originally Posted by 2xls1

I've erased and programmed many of them years ago. I guess my confusion or maybe better surprise is what good is the ability to read them from the ALDL when you can't program them from the ALDL unless i guess just the novelty of being able to. Or maybe they were being replaced by EEPROMs.

So like I said.