MAF and MAP value live different from the DMD Value

[Burn2]

Hello,

I have got something that warn me on my transit 2.4 TDCI 140 RW 2009.

First of all, i have got some P0299/P0234 code that appear. P0299 was confirm and turn on the check engine light.
I take a look on the value on fordscan and see that MAP and MAP_D are note the same, and the same for MAF and MAF_D.

I change the MAF sensor and the MAP sensor to be sure ==> Same light continue to appear.
The car seems to react better, but check engine ligth continue to turn on sometime.
I change the EGR valve, and now do not have check engine light on any more (after 7400km more) but i continue to see P0299/P0234 on the history, but that does not turn on the check engine light.
But the maf_D and map_D are not respected.
I did not reset any thing after the remplacement, only clear the code. (so no fuel relearn or maf relearn but that does not exist in service for maf)

For exemple on charge:
MAF (live): 82.22g/s
MAF_D: 290.21g/s
MAP (live): 197.2 kPa
MAP_D: 47.2 kPa

Air filter, Gazoil filter are new, oil and oil filter are new too.
VCV Valve haz been remplaced to solve idle problem (and it has solve it).

On new error that i got one time on this 7400km after all that change is: P2563:73-68 that seems to be related to the actuator.


1) Is it normal to have a maf lower then the DMD value BUT an MAP upper then DMD value all the time even if the egr is not recycling?
I would think that a low maf value would say low air pression after turbo (because low before), so if no EGR recycling you should have low MAP value too?? Am i wrong?

2) Has i got P0299/P0234 with new sensor, new EGR valve, and that i get (but only one time) a P2563, could it be related to a turbo problem?
As it's a an electric actuartor with a VG, could it explain the MAF/MAP Wrong value if the actuator goes wrong?

Thank's a lot.

VCV Valve has been changed too

[Burn2]

Hello,

nobody now if it's normal to have such big difference between map and map_DMD and MAF and MAF_DMD?

Does anybody could take a look and see if you have such difference?

Thank' you.

[p0l0us]

Hi, did you resolve the issue ?

I have same behavior. 2.4tdci, 140ps. I have new ( refubrished ) engine, new maf & map sensors, new EGR, refurbished turbo, all pipes cleaned, and still such weird values.

[knobby1]

Hi, did you resolve the issue ?

I have same behavior. 2.4tdci, 140ps. I have new ( refubrished ) engine, new maf & map sensors, new EGR, refurbished turbo, all pipes cleaned, and still such weird values.

He hasn't been back since December last year, so we'll probably never know.

Lord Knobrot

[Burn2]

Hello.

Even i do not connect, i read stuf and if i could help i did it.

In fact i never found any "solution". Then engine run normally, there is nothing particular, just that the values are totally wrong when i read it with odb reader. Even with for scan.
I don know if it's an upgrade of the firmware that is needed or not.

Readed value seems to bee good, it's dmd values that seems to be wrong.

P0299 comes back one times, but not often so don t know what to deduce.

[andz327]

Hi, did you resolve the issue ?

I have same behavior. 2.4tdci, 140ps. I have new ( refubrished ) engine, new maf & map sensors, new EGR, refurbished turbo, all pipes cleaned, and still such weird values.

He hasn't been back since December last year, so we'll probably never know.

Lord Knobrot

Cop that ma lord there is one oot there after all hahaha

Sent from my SM-G990B using Tapatalk

[knobby1]

Hi, did you resolve the issue ?

I have same behavior. 2.4tdci, 140ps. I have new ( refubrished ) engine, new maf & map sensors, new EGR, refurbished turbo, all pipes cleaned, and still such weird values.

He hasn't been back since December last year, so we'll probably never know.

Lord Knobrot

Cop that ma lord there is one oot there after all hahaha

Sent from my SM-G990B using Tapatalk

Well I'll eat my hat..!

Lord Knobrot