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

[vansit1]

does it show any text info for codes? 0.47 bar demanded is kinda weird if atm is 1?

[Burn2]

No error code here.

[Burn2]

Firmware updated, and new egr ( because the electric part die )

Nothing change for the "Dmd value bug" on mine.

Don t understand why i got that... But well now all is already updated to latest version.

[therightangle]

Firmware updated, and new egr ( because the electric part die )

Nothing change for the "Dmd value bug" on mine.

Don t understand why i got that... But well now all is already updated to latest version.

Just to ask, did you find any answer since on those funny DMD values?
I have the same issue, with no obvious running issues that I can see.

[MagsH72]

Burn2, I'm not so sure the DMD values are a "bug" tbh, fair enough if you disagree...

[metalworker0]

before you reply you should press on their profile and see the last time they were here

burn was last here December 2025

so maybe not around and will never see your questions.

all the best.mark

[glenandemm]

if you read my recent posts to do with an overboost issue that I think was originally just sticking turbo vanes that possibly messed the actuator up, i had to replace the turbo as I broke the cartridge trying to separate the turbo to clean and then I had all sorts of issues but praying ive sorted it after a replacement actuator and fitting my original vane system all cleaned up on the new turbo but going back to the map/map values I had and still have exactly the same myself I even replaced the map hoping that was part of my issue but I think they genuinely don't match that close reading up from various posts and its not really an issue to focus on as long as you see the actual live sensors working and trying to move to the dmd value.
the only thing I havent replaced is my Maf sensor but the engines running well now so im just going to drive it but I may replace it at some point for the sake of the price of a sensor and see if it does get any closer to dmd values, I mean ive replaced everything else so why stop with one more sensor lol