bad mass air flow sensor again?
#1
bad mass air flow sensor again?
I just replaced my MAF in May. It would crank over, but not fire. Replaced the MAF and instant success. Now, I am having the same symptoms. The engine cranks, will sputter like it wants to start, but will not. The MAF is not dirty, I checked that. The distributor and rotor are clean, not new, but look fine and it seems like it is getting fuel, I can hear the fuel pump spin up and come to a stop. How could I test the MAF? Can these MAFs go bad quickly? Any other thoughts, suggestions?
Thanks,
Tim.
Thanks,
Tim.
#2
#3
RE: bad mass air flow sensor again?
the current MAF is OEM. Got it from the local dealer, five months ago.
I did get it to run with the MAF unplugged. So would you think that it is bad again?
I'll try a purchase from a different source this time tho.
Is there anything else that could make these go bad this quickly?
I did get it to run with the MAF unplugged. So would you think that it is bad again?
I'll try a purchase from a different source this time tho.
Is there anything else that could make these go bad this quickly?
#5
#6
#7
RE: bad mass air flow sensor again?
Well, I'm running a dry media filter that is not the fav of lots of buffs, but they are so cheap. Cheap is loosely framed in this case tho, because if particles are getting by and smacking the MAF, then I'm done with cheap filters.
I still need to run the codes, I'll get them tomorrow, I don't have a scanner handy til then.
I still need to run the codes, I'll get them tomorrow, I don't have a scanner handy til then.
#9
RE: bad mass air flow sensor again?
I replaced the MAF and the car ran great...for 200 miles, then the same thing happened.
The car starts up fine when the MAF is disconnected, then as soon as I reconnect the MAF, the engine stops instantly. I'm wondering if the leads develop a short somewhere?
I checked the codes, 102 comes up because the MAF is disconnected and other than 302 and 303, I also have 444, which I found to be the evap signal too high.
What is the standard procedure to debug this code?
Thanks
Tim.
The car starts up fine when the MAF is disconnected, then as soon as I reconnect the MAF, the engine stops instantly. I'm wondering if the leads develop a short somewhere?
I checked the codes, 102 comes up because the MAF is disconnected and other than 302 and 303, I also have 444, which I found to be the evap signal too high.
What is the standard procedure to debug this code?
Thanks
Tim.
Thread
Thread Starter
Forum
Replies
Last Post