Dead MAF?
This morning I decided to disconnect the MAF sensor and see if that might be the problem. I checked for codes first and had none.
With the engine running, I popped the connector off the MAF sensor. SES light, code 100.
Thought maybe the idle was better. Noticed a knock when reving the engine.
Turned the engine off and reconnected the MAF sensor. Restarted. Code 100 still there, won't erase.
Did I kill my MAF sensor? Was it already dead? Do I drive the car with a dead MAF sensor?
And what about that knock suddenly appearing? It sounds like a lifter.
Had a surging, bucking problem a couple of weeks ago and it was the MAF. There was no code either.
I checked all the other stuff first, IAC, TPS, ignition timing, but car still jumped, bucked, surged, etc.
I finally disconnected the MAF WITH THE ENGINE RUNNING and problems went away. I then borrowed a friend's MAF off his 85 and problem was cured.
I was able to track down a replacement and I'm back in business.
If it turns out to be the MAF auto parts stors sell them for $50 with 30 warranty (sometimes less), auto parts stores sell remanufactured ones for $150 exchange or you can check the For Sale board on this site. =Jeff= has one for sale.
With the new MAF, I left the heat sinks in just in case my MAF troubles have been heat related. I did remove the screens though, but I epoxyed a small screen directly in front of the MAF's interior wires to protect them from debris. Best of both works, good airflow and wire protection.
Hope this helps.
Jake
[Modified by JAKE, 6:16 PM 6/11/2002]
Did I kill my MAF sensor? Was it already dead? Do I drive the car with a dead MAF sensor? ...
the irony is that when you run the car, it will probably won't run too well since usually during a code the MAF reading will default to a fixed or a "guesstimate" value. if my hunch is right, the code will clear during driving, and the engine should run normally afterwards.
hope this works.
The odd thing is that I didn't really notice much difference, but before I drove it I plugged the MAF back in so maybe it was working in spite of the code.
If the problem goes away w/ the MAF disconnected, there diag say's the MAF is bad. If it doen't go away, plug it back in, clear teh code, and keep looking.









