eatmydust

I read on the main page what it says causes the code, but surely my MAF sensor isn't bad, I just got a new one and it's less than a year old. So, what do I do to fix this problem? Any help is greatly appreciated.

eatmydust

Anybody?

FlamedROC

check your connecter for corrotion. For the hell of it take a wire brush and brush it clean. I did this and it cured my problem...if code 33 is still there clear ur codes by removin the neg. ba. terminal and letting it sit for about 20 mn. then hoo it back up and see what happens...

MIDNITERIDER

If that fails; replace the MAF relay. Its cheap and it worked for me. Was in the same situation as yourself.
1988 Formula 350
13.93 sec. @ 99.32 mph

Jim85IROC

iTrader: (2)

You have an 86. I think the early 86s had a lot of code 33 problems, so they came out with an updated PROM mid-way through the model run that was less sensitive to throwing a 33. There's a field right in the programming for code 33 sensitivity. But anyway... if the new relay doesn't fix it (I'd try the relay first), and you're sure that all of your wiring is intact and you don't have any bad grounds, then you may want to buy a new PROM or get into burning your own.

eatmydust

Ok, i'll try replacing both the MAP sensor and MAF relay, see if that does it. Thanks.

Morley

That was code 34, they did a no no with the factory proms, they didn't put the stickers over the UV window on the chips right after programming them and they were exposed to light.

Jim85IROC

iTrader: (2)

Whoops. I thought it was 33. Did the 85s have a 33 problem or am I just getting more confused?

8Mike9

Save some looking...you don't have a MAP sensor on your car.

Not that the relay's are not the cuase...but never assume a "year old" part, is still good.

Morley

85 & 86 had the same problem with their proms

doc

Do a search on this topic. Over the last 5 years, there has beem ALOT of stuff on this.

I had this problem, and did everything that was recommeneded. In the end , it took a custom burned Eprom chip to solve this problem.

There was a thirdgenner from Kent, Ohio who had this problem just this last June. He finally gave up on all of the fixes and drove up to see me and I fixed him up with a custom chip. He is a happy camper now.

The Eprom chips from Hypertech and SLP do not fix this problem, at least mine did not.

8Mike9

Doc,

How ya been?

You still have the 4th gen>? been awhile since we crossed threads, thougt I'd say "Hi".

hi

eatmydust

So, I don't have a MAP sensor on my car? Strange, wonder why my chilton's manual says I do? I guess it must not be too big a problem, cause the SES light hasn't come back on since that day and i've started it and let it run for at least 10 minutes every day since then. I haven't driven it, but i've still gave it gas, let it sit and run, put through all the gears and nothing happend. Also, I know it maybe has came up alot in the last 5 years, but i've gone through every page in this forum and done a search and nothing came up about code 33 problems, so maybe in the last few months nothing has came up about it. So, i'm guessing if nothing fixes the problem, then I should check out the custom prom forum huh?

eatmydust

I called my local Chevy dealer, I do have a MAP sensor on my car, but they said they cannot find a MAF sensor relay. So, now i'm confused. Anybody point me in the direction of where this sensor and maybe the MAP sensor are located.

doc

eatmydust: You have an '86 TPI car, so you should have a MAF sensor (not a MAP sensor). The relays are on the firewall near the brake booster (drivers side).

But like I said, you are wasting your time and money. The only for sure way to get rid of the 33 error code is with a custom chip. With only a few mods, the ECM will read a MAF sensor fault due to high air flow (thats the 33 error code), but there is nothing wrong, GM simply set a too close of a tolerance standard for the MAF cars.

This is a very fustrating and annoying prolem.

8Mike9: I sent you email.

DannyT

Will the code 33 cause driveability problems?
My SES will come on every once in a while and this is the only code stored. My car appears to be cutting out every once in a while at various throttle positions and I thought it was fuel related. Today was the first time the SES light on at the same time that my car was acting up.

Morley

Check the pins on the harness connector for the MAF sensor, they are a female pin and get stretched out of round easily and will cause lots of hard to trace problems.

DannyT

That could be it. The plastic clip that holds the connectors together broke so the connection isn't as solid as it should be. In fact the plug has slipped off a few times. I'm not sure how else to secure it though.

Morley

Pep Boys sells those connectors, I just replaced mine a few months ago. If the connector is loose enough to fall off then you need to fix that first off, then if the problem remains start troubleshooting it again.

doc

DannyT, yes, the 33 code causes an annoying drivibility problem.
It seems like the throotle position and fueling are not a linear thing any more.

DannyT

That is EXACTLY the trouble that I am having. I thought my fuel pump was going out but usually they just quit. I also suspected a bad TPS and was going to replace it.

Morley: Thanks, I'll check tomorrow for those connectors