Well, I replaced the MAF sensor relay for the second time in three years and it looks like that solved my code 36..... for now.

FYI: If anyone is getting a code 36, replace the relay on the driver's side firewall with P/N 14089936. It's the one with the two orange, one black, and one blue wires going to it. More often than not, this will solve the code 36, provided your connectors are in good shape.

Interestingly, I started getting the code 36 shortly after swapping in a WELLS SU-145 sensor in place of the BOSCHE unit. To get rid of the code, I would clear the computer's memory and everything would be fine. After approximately 4 -5 start-ups, the code 36 would rear it's ugly head again. Does this indicate a failed MAF burn-off relay, or should I be looking at something else? Wouldn't a bad relay generate a code 36 all the time?

Since the WELLS unit does not require the MAF burn-off function, does anyone know of a way to totally disable the MAF burn-off?

I am burning my own eeprom chips, so if there is a flag within the 6E bin using WinBIN, I would really appreciate it if someone could enlighten me.

Thanks.

88 GTA 5.7

 

Jay,

Just disable the DTC 26 in the error code tables. Your relay has probably solved it, though. I've been using the SU-145 for three years with no problems "faking out" the burnoff function.

 

How do I go about disabling the DTC 36 in the error code tables using ECM Editor? (ie switch location/mask)

(I have replaced the MAF burn-off relay and I still get a 36 after about 4 -5 restarts)

I would like to spend less time chasing this problem and devote more of it to tuning the "perfect" BIN instead!

Thanks again