 | Home > Puma (Tdci) > MAF Sensor Wiring |
 
|
|
|
| B4Lamb Member Since: 21 Mar 2015 Location: Abergavenny, Wales Posts: 233   
|
The only thing I can possibly add is that during the diagnosis of mine the ScanGaugeII gives you the option of seeing the FRDZ...this is described as the Parameter Identification Descriptors (PIDs) if any data was captured during the fault code being 'logged' this is stored....so I was hoping to see 'how out of range' the MAF had gone...all I got was PID00= which I currently interpret as 'nothing measured'
It's a pity your scangauge cannot bring back the parameter values when the recent P1103 was logged. These are stored in the ECU. I am not familiar with that device but maybe you should enquire why it was unable to recover those parameters. I think once you clear the fault code the stored values are all cleared as well. Pity you are not nearby as I could test your MAF sensor, it doesn't take long. If you happen to need to come to South Wales you could pop in? If you do go and buy a New MAF sensor you could send me the old one in the post and I can test it for you and then send it back in the post. My guess is that there is nothing wrong with it. There are so many posts on this subject I'm beginning to think that there is an inherent sensitivity in the Puma ECU that throws up this Error code on a single misreading. It appears that the EGR valve also comes into question and this is renowned for failing and sticking. My EGR started making horrible chirping noises and really made a racket during its cleaning cycle at engine off so i fitted a new one a few months ago. So in my case i dont think the fault was that but you never know. It's frustrating to say the least.  "You are never to old to learn something new" |
||
13th Dec 2015 9:30am |
|
| B4Lamb Member Since: 21 Mar 2015 Location: Abergavenny, Wales Posts: 233
|
I meant to say that someone must know what are the MAF expected values and the threshold values that cause the error code to be logged. These must be built into the ECU as a calculation it performs. I could do with knowing that algorithm. "You are never to old to learn something new"
|
||
|
13th Dec 2015 9:53am |
|
| X4SKP Member Since: 29 Nov 2013 Location: Berkshire Posts: 2295  
|
Hello B4Lamb
I tend to agree...looks to be several posts on here and else where with this one and general 'confusion' with the error code when it appears...to paraphrase 'oh that's common... it will go away' I may have missed an opportunity when diagnosing mine and then clearing it as the stored PID data as you say may have been there, within the ECU, and if not via the ScanGaugeII a 'higher level' piece of kit could have added to what there is to be known. If I had waited until the MIL engine light 'self corrected', the logged code would have still been there and possibly this PID information...maybe at the stage below the 'left and right arrow options' would have revealed more...possibly the lowest and highest values of the MAF measured values...  maybe not...
 Click image to enlarge ScanGaugeII users may know the answer to this...
I have the Ford Motor Company OBD-II Diagnostic Troble Code Definitions document (revision Date Oct 17 2007) kindly sent to me by another D2N member and on page 41 / 97 the code is described as shown... Click image to enlarge Thanks for the 'diagnosis offer' when I get to replacing mine...I also agree I'm not convinced that there is much wrong with my current MAF Sensor, but I think I will do a swap and view the old one as a usable backup maybe. The only other possibly irrelevant aspect to my Engine Light / P1103 fault code was that both situations were under very similar driving condition...early morning, (6.00 - 7.00 am) high moisture content in air (misty rain) similar seasonal temperatures (February / December) and motorway driving (50-60 mph)...maybe just coincidence... Good luck with yours...is it a watch and see (and measure) approach... SKIP
https://www.defender2.net/forum/topic83242.html |
||
|
13th Dec 2015 10:41am |
|
| B4Lamb Member Since: 21 Mar 2015 Location: Abergavenny, Wales Posts: 233
|
Hi There X4SKP, thanks for your contribution to this discussion point. As you say its now a case of watch and see and measure again if it occurs. If you do swap your MAF sensor I would be more than happy to test the old one for you (no charge). The conditions that led up to your fault code was similar to mine and to others that I have read about. Mine was 9 mins into a journey on a damp cold day driving at 60 mph on a dual carriageway. Your Ford diagnostic Code book does not give much more detail really but interesting that there is a fault code for an intermittent flow sensor. Good luck with your fix as well. "You are never to old to learn something new"
|
||
|
13th Dec 2015 12:30pm |
|
| X4SKP Member Since: 29 Nov 2013 Location: Berkshire Posts: 2295
|
Hello B4Lamb
Oh now that is interesting, as what I didn't include in my 'similarities between P1103 faults' is that both mine were towards the end of that initial 'warming up period', 10-15 min I would estimate from setting off... 
Good luck anyway... SKIP https://www.defender2.net/forum/topic83242.html |
||
|
13th Dec 2015 2:18pm |
|
|
|
| All times are GMT |
< Previous Topic | Next Topic > |
Posting Rules
|
Site Copyright © 2006-2025 Futuranet Ltd & Martin Lewis
