Uh oh...these codes are no good.. dead MAF? :-/
Thread Starter
Supreme Member
iTrader: (1)
Joined: Jun 2003
Posts: 3,085
Likes: 2
From: Elgin, IL
Car: 1997 Corvette
Engine: LS1
Transmission: 4L60E
Axle/Gears: 2.73 IRS
Uh oh...these codes are no good.. dead MAF? :-/
Alright, two nights ago I ripped all of my AC stuff out and disconnected all of the sensors and connectors related to AC. I started my car up and there was an SES, but I figured it was probably just something to do with the air conditioning being gone (which I didn't think SHOULD cause a code, but nothing else made sense to me really). Then yesterday upon starting my car a few times it wanted to die, and I started getting a bit worried again. Then, this morning when I was laying there in bed when I woke up, I was thinking for a second and then all of a sudden I was like "I didn't plug the MAF sensor back in!" So I finish waking up, run outside, and plug hte MAF sensor in. Now I'm still getting an SES light and my car is running VERY rough at idle. The car actually tries to die it seems like.
When I checked the codes I got 12, 33, and 36. Then I realized 12 is normal for the "blink-test". Anyways, 33 is "High voltage (low vacuum) at mass air flow sensor (or MAP sensor)". And 36 is "Burn off at mass air flow sensor OR
Problem in transmission shift OR
Fault in direct ignition system OR
Missing pulses in electronic spark timing signal".
Could running the car for a few days without the MAF sensor somehow ruin the MAF sensor? It doesn't make much sense to me because I would think it would just act as if the car were turned off (i.e. not affect the MAF sensor). I have both MAF screens intact as well as the air filter so I don't see how anything really could have damaged it anyways.
What does "Burn off at mass air flow sensor" mean? Does that mean somehow I cooked my MAF? That'd not be very good at all..
When I checked the codes I got 12, 33, and 36. Then I realized 12 is normal for the "blink-test". Anyways, 33 is "High voltage (low vacuum) at mass air flow sensor (or MAP sensor)". And 36 is "Burn off at mass air flow sensor OR
Problem in transmission shift OR
Fault in direct ignition system OR
Missing pulses in electronic spark timing signal".
Could running the car for a few days without the MAF sensor somehow ruin the MAF sensor? It doesn't make much sense to me because I would think it would just act as if the car were turned off (i.e. not affect the MAF sensor). I have both MAF screens intact as well as the air filter so I don't see how anything really could have damaged it anyways.
What does "Burn off at mass air flow sensor" mean? Does that mean somehow I cooked my MAF? That'd not be very good at all..
TGO Supporter
Joined: Oct 2003
Posts: 2,069
Likes: 0
From: ready room
Car: NCC-1701-D (docked in AZ)
Engine: impulse drive
Transmission: fusion reactors
Axle/Gears: Rescued from the Borg by my crew
Re: Uh oh...these codes are no good.. dead MAF? :-/
Originally posted by DuronClocker
Alright, two nights ago I ripped all of my AC stuff out and disconnected all of the sensors and connectors related to AC. I started my car up and there was an SES, but I figured it was probably just something to do with the air conditioning being gone (which I didn't think SHOULD cause a code, but nothing else made sense to me really). Then yesterday upon starting my car a few times it wanted to die, and I started getting a bit worried again. Then, this morning when I was laying there in bed when I woke up, I was thinking for a second and then all of a sudden I was like "I didn't plug the MAF sensor back in!" So I finish waking up, run outside, and plug hte MAF sensor in. Now I'm still getting an SES light and my car is running VERY rough at idle. The car actually tries to die it seems like.
When I checked the codes I got 12, 33, and 36. Then I realized 12 is normal for the "blink-test". Anyways, 33 is "High voltage (low vacuum) at mass air flow sensor (or MAP sensor)". And 36 is "Burn off at mass air flow sensor OR
Problem in transmission shift OR
Fault in direct ignition system OR
Missing pulses in electronic spark timing signal".
Could running the car for a few days without the MAF sensor somehow ruin the MAF sensor? It doesn't make much sense to me because I would think it would just act as if the car were turned off (i.e. not affect the MAF sensor). I have both MAF screens intact as well as the air filter so I don't see how anything really could have damaged it anyways.
What does "Burn off at mass air flow sensor" mean? Does that mean somehow I cooked my MAF? That'd not be very good at all..
Alright, two nights ago I ripped all of my AC stuff out and disconnected all of the sensors and connectors related to AC. I started my car up and there was an SES, but I figured it was probably just something to do with the air conditioning being gone (which I didn't think SHOULD cause a code, but nothing else made sense to me really). Then yesterday upon starting my car a few times it wanted to die, and I started getting a bit worried again. Then, this morning when I was laying there in bed when I woke up, I was thinking for a second and then all of a sudden I was like "I didn't plug the MAF sensor back in!" So I finish waking up, run outside, and plug hte MAF sensor in. Now I'm still getting an SES light and my car is running VERY rough at idle. The car actually tries to die it seems like.
When I checked the codes I got 12, 33, and 36. Then I realized 12 is normal for the "blink-test". Anyways, 33 is "High voltage (low vacuum) at mass air flow sensor (or MAP sensor)". And 36 is "Burn off at mass air flow sensor OR
Problem in transmission shift OR
Fault in direct ignition system OR
Missing pulses in electronic spark timing signal".
Could running the car for a few days without the MAF sensor somehow ruin the MAF sensor? It doesn't make much sense to me because I would think it would just act as if the car were turned off (i.e. not affect the MAF sensor). I have both MAF screens intact as well as the air filter so I don't see how anything really could have damaged it anyways.
What does "Burn off at mass air flow sensor" mean? Does that mean somehow I cooked my MAF? That'd not be very good at all..
Thread Starter
Supreme Member
iTrader: (1)
Joined: Jun 2003
Posts: 3,085
Likes: 2
From: Elgin, IL
Car: 1997 Corvette
Engine: LS1
Transmission: 4L60E
Axle/Gears: 2.73 IRS
I probably should have done a search first, but I was kind of in a panic to get answers quick, lol. Anyways, I got some ideas from searching, so I'm going to check all my connections and relays.
Thread Starter
Supreme Member
iTrader: (1)
Joined: Jun 2003
Posts: 3,085
Likes: 2
From: Elgin, IL
Car: 1997 Corvette
Engine: LS1
Transmission: 4L60E
Axle/Gears: 2.73 IRS
As if this makes much sense... I just cleared the codes on my car by disconnecting the battery for a few seconds. Now, no codes, and engine is running fine. Obviously I see why the codes would now be cleared. What I don't understand is why my car would run better now that I cleared the codes. Does the computer run the car differently if it has codes stored? I would think the codes would just be there to remind you there was an error with it, but it seems as when there is a code on there at all, the computer acts like the problem for that code is always there...even when its not. I say this because my car idles fine now and doesn't want to die anymore.
TGO Supporter
Joined: Oct 2003
Posts: 2,069
Likes: 0
From: ready room
Car: NCC-1701-D (docked in AZ)
Engine: impulse drive
Transmission: fusion reactors
Axle/Gears: Rescued from the Borg by my crew
Originally posted by DuronClocker
As if this makes much sense... I just cleared the codes on my car by disconnecting the battery for a few seconds. Now, no codes, and engine is running fine. Obviously I see why the codes would now be cleared. What I don't understand is why my car would run better now that I cleared the codes. Does the computer run the car differently if it has codes stored? I would think the codes would just be there to remind you there was an error with it, but it seems as when there is a code on there at all, the computer acts like the problem for that code is always there...even when its not. I say this because my car idles fine now and doesn't want to die anymore.
As if this makes much sense... I just cleared the codes on my car by disconnecting the battery for a few seconds. Now, no codes, and engine is running fine. Obviously I see why the codes would now be cleared. What I don't understand is why my car would run better now that I cleared the codes. Does the computer run the car differently if it has codes stored? I would think the codes would just be there to remind you there was an error with it, but it seems as when there is a code on there at all, the computer acts like the problem for that code is always there...even when its not. I say this because my car idles fine now and doesn't want to die anymore.
Thread
Thread Starter
Forum
Replies
Last Post
BumpaD82
Tech / General Engine
37
Feb 26, 2016 02:57 PM
MikkoV
TPI
2
Sep 9, 2015 04:25 PM




