I did a search, but didn't really find too much info regarding my situation. Let me start at the beginning of my code 33 troubles. Last September, I had a code 33 problem. You can read about it here if you like https://www.thirdgen.org/forums/tech...t=#post3472914. I solved it by replacing the MAF and the MAF power and burnoff relays. Then it ran trouble-free for about a month until I got another code 33 in October. Similar problem as to what happened in September (it would barely run), but this time it was solved by soldering on a new MAF pigtail. No more code 33, until yesterday. It ran fine all day and then out of nowhere, it felt like it lost power. This happened maybe five times, but only once did the check engine light come on. I took it home, scanned it, and got a code 33. I made sure the relays and MAF connector were snug, reset the ECM, and took it for a drive. Everything seemed alright then and an the way to school this morning. On the way back from school, it did it again, This time with an SES light. This has me really confused. Any ideas as to what would be causing this? Could my soldering job at the MAF connector have failed? I can't imagine that any of the parts that I replaced last year are bad already.

 

Anyone?

 

I had that problem for such a long time..I was ready to shoot the ECM....lol

Did everything you mentioned but would still come back. Burned my own chip and increased the MAF threshold and finally!!!!! code 33 is history...car has been running great for a year now with no code....My incoming air was also increased due to my supercharger that was basically turning on code 33...increased air flow was going past the stock threshold of 45 gm/sec which is the stock setting on the ECM.

Burn your own and you can kiss 33 bye-bye

I have the Moates burning ..here is the site

http://www.moates.net/index.php?cPath=51

I have the APU1

 

That's what I was afraid of hearing . I read on here that the only way some other people were able to get rid of the code was to burn a new chip.

I don't understand why it would be fine for four months (and over a year before the initial problem happened) and then start acting weird like that out of no where.

 

I hear ya, same crap would happen to me..I was replacing MAF sensors like no tommorrow over the years...would solve the problem for so long then pow 33 back again!!.All these times the MAF`s were probably all good!!.. All this time MAF threshold was overlimit do to the increase air flow from the performance parts I have installed( learned alot from this site, great wealth of info on thirdgen )....Also make sure all your intake connections are all tight but you probably done all that....Do you have any mods done to your car or is it stock?? Either way burn a new chip trust me you wont regret it..too bad you didnt live closer..I could burn you one ..You would just need to by the adapter from Moates so you could plug your stock chip and the new chip together on the adapter then the adapter plugs into your ECM.

 

All I have is an SLP cold air intake and catback. Maybe the CAI is causing the excessive airflow, hmmm... I've been wanting to get into chip burning for a while, I guess this is my opportunity, lol.

 

Put the original air canister back on last night and it still happened this afternoon leaving school . You know what's wierd? It's thrown the code in the exact same spot every day for the past three days. Coincidence? I've also noticed it only happens on the second startup after resetting the ECM.

I think I'm going to order a PROMinator this weekend.

 

My 85TA used to do that a lot, so did my 86 actually. So far the 89 has been ok. I think GM's MAF check threshold was a little too close for comfort.

We should have a separate sticky that says if you have a code 33 dont replace your MAF. Most of the time its not the issue.

 

Madmax is right, the error code 33 not a MAF or relay problem most of the time.

It was said that you did a search. I posted on this matter twice in the last month. Do another search.

 

Burn a new chip and you will be happy motoring again

 

And I have to agree with CRUSHER, the only way that I could permenently fix the 33 error code was to "burn" my EPROM chip.

 

I did see your other posts, I guess I just didn't want to believe that I would have to burn a new chip to get rid of the code. Mainly because most people's cars who threw the code were modified, such as your's and CRUSHERS'. Mine isn't.

It turned out my TPS was bad. For the hell of it, I checked the voltage on it, and it was way off. Tried to set it to spec and it just wouldn't stay on .54VDC at idle. It kept jumping to other values. So, I went out and bought a new one, set it to spec, and that seems to have taken care of it. It's been running trouble-free for four days now.

I'm still going to buy a prominator and bump up the MAF threshold to be on the safe side. I think I'll do a few other things while I'm at it too.

 

Years ago, I did what must of us do, jump in there and replace parts. I replaced the MAF and both relays on the firewall. The 33 code kept coming back. Played with the TPS setting, etc, etc. Finally, I stumbled across a guy from near Detroit who was burning EPROMs, I told him what my problem was, he knew right away how to fix it. I bought a chip from him, no more 33 codes. And since then, I learned how to burn EPROMs from this board, and I discovered how he fixed the 33 error code for me by comparing my stock EPROM to his EPROM. I guess that its all in the learning process.

 

Glad to here it Mike.....That damn 33 is a pain!!......

 

other than activating the light will the 33 effect anything? I had 22, 34 and 44. I have replaced the MAF (filament was broken.) Now I got rid of the 22 and 44 but I still have a 33. I have not driven the car much seeing as it is currently off the road. I will know more tuesday once she is registered. also is there anyone here that programs chips for people? I assume that is cheaper than buying a programmer.