P139C Code

[RangerBill]

I get the code off and on. While I was doing that previous test, the code light was off. I drove around for 15 minutes and the code came back on. I have to use my laptop with FORScan to monitor the data. I did notice while moving but without my foot on the gas, it was almost always around -0.80 psi.

DPFE_UR showed "no fault" even when the code light was on.

Also, it is running rough and "studdering".

Mark

Replace the DPFE sensor and see if that fixes it.

Sponsored

 

[airline tech]

yes - replace the sensor and then follow up with Live Data again to ensure readings come back to normal range if they do not - then the issue is within the EGR Tube Assembly or electrically (wiring) we can isolate that if the sensor does not bring it back to normal readings but since at KOEO the voltage is very near (new) normal - electrically it appears fine and the issue is withing the (pressure reading) capabilities

 

[emesel]

I hope to receive and replace the sensor tomorrow. But, is there a way to check if the orifice is clear? What about blowing compressed air in high or low pressure port and checking other port for flow?

 

[airline tech]

I hope to receive and replace the sensor tomorrow. But, is there a way to check if the orifice is clear? What about blowing compressed air in high or low pressure port and checking other port for flow?

The high pressure side - only as to check the orifice the tube must be removed, the only thing that you can do is disconnect both hoses and then koeo and note did the readings change

 

[emesel]

The high pressure side - only as to check the orifice the tube must be removed, the only thing that you can do is disconnect both hoses and then koeo and note did the readings change

I imagine it would have to be totally blocked for the readings to change when houses removed.

 

[airline tech]

My hunch is - it’s the sensor itself - the problem is that 99% of the members that have changed the sensor for Buck Surge did not have any PID data before they changed it - all of my data for T-Shoot is derived from expected readings from the very few (real failure) readings and my own Live Data (normal) drives , once you understand what is actually happening, you gain the understanding on how to monitor for the no code failures, and it’s all in the (Learned Zero) band and how much positive flow (accuracy) is left.
I will need to run Forscan and see if I can find the same PIDs as in the past it was not available, so this is actually some good news for others to post their PIDs as well - I imagine they are near the same readings as you have - the problem is the Buck / Surge appears before it codes P139C and the reason for that is it’s still in the Learned Zero Band , but when driving the positive flow is now not hitting it’s normal range voltage/ pressure- the PCM reacts by adding more EGR then the Buck Surge is felt although the sensor is still in a (PCM) believes the reading is normal until it pushes outside the band and becomes (untrustworthy) and sets the code - like you have

Sponsored