puzzigully

Hi Guys,

i'm still having issues with my 1987 B2K corvette throwing Code 36 errors.

I know this is not the correct way to do this, but is is possible to get inside and alter the "code" or programming that it doesn't actually "look" for the burn off to have taken place?

It is happening, just something funny with the signal on its way to the ECM.

i'm aware guys get into the programming to bring on thermo fans at a lower temperature, so I'm guess this is a similar thing?

If so, what would be the best way to do this?
Moates Ostrich?

thanks

tequilaboy

Diagnostic trouble codes can be easily disabled in the bin. The software is structured so that each code can be turned on or off by a flag/switch setting. This can be done by any of the common editors.

Beyond that, the logic for setting each code can be edited in order to adjust the sensitivity or mature time of a given failure in the event that the factory failsafe no longer fits the actual behavior of the hardware in use.

For this application, the Ostrich is overkill, but it is very handy for real time tuning and works great if you're retuning constantly. A G1 adaptor, an eeprom and a Burn2 programmer will get the job done at lower cost.

You can also read, erase and reprogram any factory memcal with an appropriate programmer and a header like the HDR1 and a U/V eraser (old school). Just buy a spare memcal and keep your original, if desired. I have a couple socketed memcals that I prefer to use over the plug-in G1 style adaptors, but both methods work fine.

Cliff Harris

It's pretty easy to disable the reporting of any particular error. The error will still occur but the ECM will never report it.

puzzigully

Thanks guys,

I'm aware the memcal? (chip) is specific to the B2K, so want to be cautious not to change anything else.

I'll just need to find the line of code and either erase it, or tell it to check for it, but not report a code.

Cheers!

tequilaboy

Here are examples of the malfunction/error flag mask settings from $32B code:

Note: Bit = 0 Disables MALF Recognition

LC1DD FCB $F7 ; 1111 0111, MASK FOR MAL FUNCT FLG 1
;
; Bit 0 = ERR Code 23 MAT Sensor low
; Bit 1 = ERR Code 22 TPS low
; Bit 2 = ERR Code 21 TPS High
; Bit 3 = NOT USED 16 NOT USED
;
; Bit 4 = ERR Code 15 Cool Sensor Low Temp
; Bit 5 = ERR Code 14 Cool Sensor Hi Temp
; Bit 6 = ERR Code 13 Oxy Sensor
; Bit 7 = ERR Code 12 No Ref pulse (Dist)
;---------------------------------------------
LC1DE FCB $CE ; 1100 1110, MASK FOR ERR FLAG 2
;
; Bit 0 = ERR Code 35 NOT USED
; Bit 1 = ERR Code 34 MAF Sensor low
; Bit 2 = ERR Code 33 MAF Sensor high
; Bit 3 = ERR Code 32 EGR Diag
;
; Bit 4 = NOT USED 31 NOT USED
; Bit 5 = NOT USED 26 NOT USED
; Bit 6 = ERR Code 25 MAT Sensor High
; Bit 7 = ERR Code 24 VSS
;---------------------------------------------
LC1DF FCB $FF ; 1111 1111, MASK FOR ERR FLAG 3
;
; Bit 0 = ERR Code 51 Prom Error
; Bit 1 = ERR Code 46 VATS Fail
; Bit 2 = ERR Code 45 o2 Sensor Rich
; Bit 3 = ERR Code 44 o2 Sensor Lean
;
; Bit 4 = ERR Code 43 ESC Fail
; Bit 5 = ERR Code 42 EST Monitor error
; Bit 6 = ERR Code 41 CYL Select error
; Bit 7 = ERR Code 36 Burn off Diag.
;---------------------------------------------
LC1E0: FCB $E0 ; 1110 0000, MASK FOR ERR FLAG 4
;
; Bit 0 = ERR Code 63 NOT USED
; Bit 1 = ERR Code 62 NOT USED
; Bit 2 = ERR Code 61 NOT USED
; Bit 3 = ERR Code 56 NOT USED
;
; Bit 4 = ERR Code 55 NOT USED
; Bit 5 = ERR Code 54 Fuel pump Voltage
; Bit 6 = ERR Code 53 Over voltage
; Bit 7 = ERR Code 52 Missing Cal Pack
;---------------------------------------------
LC1E1: FCB 00 ; 0000 0000 MASK FOR ERR FLAG 5
;
; Bit 0 = NOT USED
; Bit 1 = NOT USED
; Bit 2 = NOT USED
; Bit 3 = NOT USED
;
; Bit 4 = NOT USED
; Bit 5 = ERR Code 66 NOT USED
; Bit 6 = ERR Code 65 NOT USED
; Bit 7 = ERR Code 64 NOT USED
;---------------------------------------------

By setting the bit associated with any error code to zero, the logging and display functions for that error code will be disabled.

To disable code 36, you would edit the byte at C1DF (by changing from $FF to $7F...to set Bit 7 to 0) as shown below:

LC1DF FCB $7F ; 0111 1111, MASK FOR ERR FLAG 3
;
; Bit 0 = ERR Code 51 Prom Error
; Bit 1 = ERR Code 46 VATS Fail
; Bit 2 = ERR Code 45 o2 Sensor Rich
; Bit 3 = ERR Code 44 o2 Sensor Lean
;
; Bit 4 = ERR Code 43 ESC Fail
; Bit 5 = ERR Code 42 EST Monitor error
; Bit 6 = ERR Code 41 CYL Select error
; Bit 7 = ERR Code 36 Burn off Diag.

Note: Most common editors will have the Malfunction masks already set up as simple on/off switches to make each bit easier to edit.

puzzigully

Tequilaboy,

Awesome info...thanks so much!

Just need to work out how to get into the code...

puzzigully

I have MOATES XtremeALDL and CABL1 and downloaded Datamaster - I can see all the engine parameters running, but pretty sure it wont allow me to alter any of the parameters you mentioned.

Given, I have the above hardware, what are the choices I have to get the job done:
1. Cheapest
2. Easiest for a novice

I understand 1 & 2 aren't necessarily the same

MikeT 90 C4sixer

You need a software program to edit the bin, to make your changes.
Tunercat is prolly the easiest, but costs a little. TunerPro could be used for free, but not that easy! And there others of course.

puzzigully

So I'm looking at (from Moates) G1, BURN2 and Ostrich2.0

As I understand it.

• If I used Ostrich2.0 only, I could make changes, but once I disconnect it, it goes back to the original tune.
• Can someone confirm?
• I need the G1, so I can connect the Ostrich2.0 whilst having the eprom also conencted - but still cannot make permanent changes
• Can someone confirm?
• I need the BURN2, so that I CAN make permanent changes?
• Can someone confirm?

Cliff Harris

The Ostrich uses EEPROM (Electrically-Erasable Programmable Read Only Memory). It is NON-VOLATILE, which means is retains the information when the power is removed. I don't know if it defaults back to the original EPROM when power is removed. There might be a jumper/switch for choosing that.

The changes are made to the EEPROM, which is permanent if you don't erase it.

You make permanent changes in the EPROM after debugging/tuning with the EEPROM.

puzzigully

Hi,

maybe I'm a bit thick, or asking the wrong questions...

Can the original EPROM in the ECM be modified? (I'm assuming you'd use BURN2 and appropriate software to do this?)

If not, I further assume you need to copy all the data across to an EPROM that can be modified and then installed? (I assume you'd need software and BURN2 as well)

Thanks for your patience

tequilaboy

So in summary, first you need a programmer (like a Burn2) that can read your existing eprom while it is still soldered into the memcal if you use an HDR1 header or equivalent device.

Once you have a copy of your original bin, you can then edit it as desired. Then reprogram a new EPROM, EEPROM, Ostrich, or even an OTP if you've got one, and install with a G1 adaptor and memcal into the ecm.

You can also erase an existing memcal's eprom with a U/V eraser and then reprogram it using a programmer (like a pocket programmer) and an HDR1 header. Just need the right equipment.

Since your original B2K memcal is somewhat of a rarity, you probably want to leave it alone after reading and saving the bin file.

I erased and reprogrammed my factory EPROM while still installed on the memcal about 100 times before I went with a sockted memcal to make it easier to swap in new Eproms without pulling the memcal out all the time, and then eventually moved on to an Ostrich.

puzzigully

Thanks..still learning

Whats the difference between the G1 and the HDR1?
Do they do the same job?

Yes, I think i'd like to copy the data from the B2K EPROM onto a spare EPROM and put the original in a safe place.
Then edit the "copy"

puzzigully

Been pouring over MOATES web site and some of it is becoming clearer.

The HDR1 allows me to plug in the MEMCAL to BURN2 so the reader can read the info off the EPROM?

• Then I can download the data offline (using software and a laptop) so I can upload it to a programmable EPROM.

I cant reprogram the original using BURN2 as I need a UV-eraser etc.

BUT I can program a suitable EPROM (or EEPROM - not sure of correct terminology) if I insert it into BURN2?

• This would be the original program with changes made off line
• (Remember i just want to change the reporting of Code36)

THEN:

I can insert the newly BURN-ed EPROM into G1, so I dont have to remove the original EPROM from the MEMCAL, then plug the original MEMCAL onto the G1

• Then Install the G1 into the ECM as per instructions

AND I'm done - the car will run off the info contained in the newly burnt EPROM.

If I ever want to go back to Factory, I just remove the MEMCAL from the G1 and install the MEMCAL into its original position

Have I got it now?

ANTI VENOM

I believe that you've got it. I'm not familiar to all of Moates "new" stuff, but that looks right. EEPROM's (electrically erasable programmable read only memory) can be "erased" by electronic means. I believe you are just writing 0's into every register. EPROM's must be erased by ultraviolet light. You are well on your way to programming freedom.
Good luck.