I am having a code 33 problem and i have a Superchip...why does this seem to matter? does the chip cause the code 33?

I Also Have The Wells MAF Sensor

here is a reference to the aftermarket chip:

"Keep both relays unless you want to generate an error code. Even though the thick film sensor does not require burn off, the ECM on some cars needs to detect burn off circuit current to complete teh cycle and prevent a '36'. Wells installed a ballast resistor in the burn off circuit to emulate the function, even though the sensing element never sees any burn off current. If you want to test the theory, remove the burn off relay and wait a few days, then scan for DTCs.

As for your original problem, the DTC 33 is for a high indicated MAF flow, which is normally a problem with the TPS voltage being too low, incorrect orientation of the MAF (is it backward?), or missing distributor reference pulses. Are you using the stock EPROM for the engine?"

 

i dont think the chip has anything to do with it, if u put in a new MAF it must have caused some problem cuz code 33 is the MAF, it is not the burn off circuit which is a diff code...i dont really know what the exact problem would be, do u have any thing to help u troubleshoot it, dunno

 

No, your 'superchip' has nothing to do with the code 33.

What he probably was trying to ask was if you had a custom chip. You can adjust the thresholds for MAF errors inside the chip, which comes in handy depending on the engine combination. Radical combos don';t have anywhwere near the same MAF response at idle and cruise that a stock engine does.

So whoever asked if you had a chip, was really tring to ask if you had stock MAF error values. And considering how useless a superchip is, and that a near stock engine doesn't need error threshold changes anyway, i am reasonably sure your chip is stock in that regard.

 

It is.

Take that Superchip, and throw it as far as you can. Well... do that after you get (or find) a stock GM one to put in its place.

 

Why should i throw the superchip away? is it causing the code 33?

 

Well I have only known of 2 people with those (one of them being myself) and both went bad. Mine was fine till one day it started running like crap and setting a code 51. I just pitched it and put the GM chip back in. Didnt have anymore funny problems either.