MAF Sensor Needs Replaced (did ORM mod cause it)???

2mopar_diesels · **Posted:** Wed Jan 27, 2010 8:43 pm

Been running the ORM mod ever since I bought the CRD back in Sept. '08 every few months I would plug it in, take it to parts store to clear and read any other codes not associated with the ORM and then unplug it again. Anyways, a couple weeks ago I was accelerating from a red light and the CRD had absolutely no power like it was in limp mode. Stopped, pulled over, and found nothing wrong. Left out from there fine, thought it was just a fluke. And so it goes like this a few times, and I now know something is wrong. Plug the MAF back in, take it to the nearest Autozone to clear codes and he says it clears but comes right back. All kinds of codes dealing with air flow and intake sensors. CEL never goes out and CRD about every 5-6 stops will leave with no power, only to get power back at next stop. Does this with or without ORM.

Finally took it to the dealr today (of course I didn't tell him I run with MAF unplugged) and says the MAF sensor is not responding to the Starscan or voltage inputs and therefore is bad and need replaced. So I'm wondering now if always leaving the MAF unplugged somehow caused this??? If so, maybe running a few days to a week every now and then would prevent it from happening again. I just dont understand how it can go bad if it never gets used.

CATCRD · **Posted:** Wed Jan 27, 2010 9:12 pm

Mine's been unplugged for over 20,000mi. I just plugged it back in recently for an emissions test, cleared the codes, and it worked fine. Unplugged it again too.

Sir Sam · **Posted:** Wed Jan 27, 2010 9:28 pm

Mines been unplugged for over 50,000 miles. No problems at all, plugged it back in during the summer for emissions test and all was fine.

I suspect you are having some other failure that is causing a MAF code.

ATXKJ · **Posted:** Wed Jan 27, 2010 9:34 pm

FYI - running ORM leaves codes in the computer saying the sensor's not working
if you plug it in and take it to the dealer - they read the codes and say the sensor's dead.......

and then when that doesn't fix the problem - they then troubleshoot the next code that comes up.

2mopar_diesels · **Posted:** Wed Jan 27, 2010 9:59 pm

And thats the thing. I watched and they did more than simply stick a scan tool on it. They had a volt/ohm meter hooked up to all sensors/systems associated with airflow control. The MAF, intake air temp, MAP sensors and EGR system. Pulled and checked connectiions, plugs and sensors and still, the only one not showing correct values was the MAF. Everything plugged in with cleared codes, would crank up and come back with CEL and code out 5 seconds later. All values were within spec at all the plugs. But I'm just wondering how it can go bad while not being plugged in, and if it's something else causing the limp mode problem??? But the only codes being thrown had to do with airflow.

LibertyCRD · **Posted:** Wed Jan 27, 2010 10:13 pm

No damage to your connections? Wires? No corrosion in your plugs? Obviously your Jeep is running bad for other reasons since it does it with or without the MAF plugged in. The MAF not responding is a separate issue it sounds like.

2mopar_diesels · **Posted:** Thu Jan 28, 2010 12:52 am

Ok, I've exhausted hours on this, and to the best of what I can come up with (both through research and my own theory) is this:

Something else caused/is causing the intermittent limp mode from dead stop problem. When that "something else" through the code and check engine light, it was a permanent entry into the ECM and it needed communication via bus with the MAF to correct the parameters. Until the ECM and whatever circuit that needs the MAF sensor communication gets said signal, it will not run right. Some way, some how, while running the ORM the MAF sensor went dead. Something else went wrong, and now needs communiction with the MAF to correct itself and clear the permanent fault. In other words, it's continually running in an open loop constantly looking for communication with a sensor that is either no longer there, or is not working. And, until the bad MAF is replaced, the Jeep will not be happy. LOL!!!!!

racertracer · **Posted:** Thu Jan 28, 2010 5:33 am

I too have had a problem with my MAF sensor after ORM.

Here is what I experienced:
I decided to reconnect the MAF sensor after an ORM to see if the turbo boost increased. It worked fine for 15 minutes, then the engine light came on and I got a P0100 code (Mass or Volume Air Flow Circuit Malfunction).

I believe that the open sensor connection may have come in contact with rain water and maybe corroded. I would like to know how to test to see if the problem is with the connector or the sensor, how do I test them and how do I clean them?

My Limp Mode happens when I punch the peddle to the metal and get no turbo boost and limp.

I am thinking that the problem may be that the MAF sensor connector is plugged in even now that the engine light is on.

I will unplug it and report back.

liberty2.8 · **Posted:** Thu Jan 28, 2010 8:49 am

Quote:

Been running the ORM mod ever since I bought the CRD back in Sept. '08 every few months I would plug it in, take it to parts store to clear and read any other codes not associated with the ORM and then unplug it again. Anyways, a couple weeks ago I was accelerating from a red light and the CRD had absolutely no power like it was in limp mode. Stopped, pulled over, and found nothing wrong. Left out from there fine, thought it was just a fluke. And so it goes like this a few times, and I now know something is wrong. Plug the MAF back in, take it to the nearest Autozone to clear codes and he says it clears but comes right back. All kinds of codes dealing with air flow and intake sensors. CEL never goes out and CRD about every 5-6 stops will leave with no power, only to get power back at next stop. Does this with or without ORM.

Finally took it to the dealr today (of course I didn't tell him I run with MAF unplugged) and says the MAF sensor is not responding to the Starscan or voltage inputs and therefore is bad and need replaced. So I'm wondering now if always leaving the MAF unplugged somehow caused this??? If so, maybe running a few days to a week every now and then would prevent it from happening again. I just dont understand how it can go bad if it never gets used.

Wow, its sounds like we all have something in common possible related to ORM/MAF. I am experiencing the exact same symptoms and have tried troubleshooting several things to eliminate the problem to no avail YET. I hope somebodt can shed some light on our problem.

2mopar_diesels · **Posted:** Sun Feb 28, 2010 6:10 pm

Time for an update. Finally got around to getting a new MAF sensor, installed it, and went to Autozone to clear the codes. All is well with the CRD now. Kinda scared to unplug and run the ORM again, as I don't know exactly what or how this all happened in the 1st place. As the best that I can come up with is that I may have at some point in time plugged up the MAF while the engine was running and fried it. Then, had an overboost code thrown that caused the resulting&erratic limp mode/power loss from a stop. The fault codes and the CEL would not reset until communication with the MAF was reestablished. (by the way........I've had the Striker pullled off for several months before this started)

So much for the notion that there is no need for a MAF sensor on the CRD and the only thing it is used for is the operation of the EGR, as it seems to be alot more involved than that!!!

MrMopar64 · **Posted:** Sun Feb 28, 2010 7:28 pm

The MAF on the KJ is used only for the control of the EGR system and no other purpose. No other protection algorithm is based around it. My hypothesis is that in the process of moving the wiring for the MAF you also disturbed the wiring for the intake air pressure sensor on the side of the air box since the two wirings come out of the bundle at the same spot. If that sensor becomes unplugged and/or has an intermittent connection, it will give you minimal performance.

2mopar_diesels · **Posted:** Sat Mar 06, 2010 10:26 pm

Well, after I swapped out the bad MAF sensor, it went 2days b4 it went into limp mode again, and since then, maybe once or twice every couple days or so. This time only showing MAP sensor malfunction. Took out and cleaned both the manifold and air intake sensors. Sprayed the sensors and plug fittings liberally with contact cleaner then coated them with dielectric grease and plugged back in. Zero problems for last three days. If this happens again, I'll know it's most likely the airbox sensor thats bad.

StanCRD · **Posted:** Mon Mar 08, 2010 5:45 pm

Did the ORM on mine, but I put a peice of tape right in the plug and then plugged it back in but not enough to make any contact, then wrapped it with electric tape to hold it together. this way it will stay clean. A little dirt and moisture in those connectors is a recipe for disaster.

MAF Sensor Needs Replaced (did ORM mod cause it)???

Who is online