bad seal on the intake pipes bad seal on the intake manifold. even a really bad air filter might cause this prior to it just stopping the engine from running. or even bad wiring to the map sensor. i would have been looking at causes the map is seeing bad readings after the first one.
MAP
2000 Durango 4x4 5.9,,,,MAP code,changed it with Mopar part lasted a couple days and threw another MAP code,,,,,changed it again with Mopar part and after 3 days threw code again......any ideas i'm stumped here ,and the world is going to run out of MAP sensors at this rate ..
1 - 7 of 7 Posts
it's strange runs fine till it hits operating temp
I'd begin with wiring integrity, presumably you have three wires between the sensor and the computer. It's not impossible that a wiring issue could damage a sensor (shorts to ground, 12V, etc. ). Is the code specific (circuit high, low, etc.)? Last resort would be to run the truck while monitoring MAP data, presumably this would be very revealing. Good luck and keep us posted.
yea i checked the map i had 5.2v on supply wire and 5.0v going back to ecu,,,,,that 5.0v going back is way to high isn't it,,,,,these were checked engine running at idle.....had good ground..
On the 3.9L the MAP has an operating range of 4.6V at sea level, to as low as 0.3V at high altitudes. As manifold vacuum increases, the MAP decreases proportionally. A persistent high voltage should indicate low manifold vacuum. Have you checked for vacuum issues? Keep us posted.
No it is not strange, when you get up to operating temp then the computer goes into closed loop, before that it is just running on a preset programit's strange runs fine till it hits operating temp
1 - 7 of 7 Posts
Dakota Durango Forum
A forum community dedicated to all Dodge Dakota and Durango owners and enthusiasts. Come join the discussion about modifications, troubleshooting, towing capacity, maintenance, and more!
Full Forum Listing
