Defender Source Forum banner

Troubleshooting a P1179 on 97 NAS / GEMS

144 views 6 replies 4 participants last post by  carlosz  
#1 ·
Truck running rough and trying to understand the code and live data that I see... via OBD2.

LONGFT1 & LONGFT2 are showing -82.8%. I believe this is long term fuel trims and so sounds like it thinks the engine is running to rich and throttling back fuel.

More concerningly the MAF reading is 0.0 lbs/s, which would suggest a failed MAF. I swapped it out for an older MAF that I had kicking around for the last 10+ years and that also registered 0.0 lbs/s.

Of the 3 wires going into the MAF - I have 12v across brown-orange and red-black and looks like the blue wire goes to the ECU.

Possibilities:

1. MAF value is not actually reported via ODB2 and so it's a red herring to chase it.
2. Both MAF sensors are bad
3. Blue 'sensor' wire between MAF plug and ECU is damaged.

Can anyone help rule out 1. before I go down the 3. rabbit hole. Would you expect the MAF value to show up in live data, or is the fact that the scanner detected a MAF field at all and showing zero mean that is is actually being sent vs. not supported.

A P1179 search here, yielded "replaced fuel filter and fixed it" - but that wouldn't make sense to me as the huge negative LONGFT1 values suggest it's way too rich vs. way too lean.

Any other theories?
 
#2 ·
theres a small vacuum hose going to the fuel pressure regulator on the fuel rail. Make sure it isn't split

look at engine load, not maf values.

I think maf values are only available with rover specific software. The torque app or whatever isn't going to be able to get to that using the standard 01XX PID.

if you ever swap MAFs or TPS you should reset the adaptive values. it takes a while for the ECU to catch up.
 
#5 ·
Hey @robertf - are you same guy that made the GEM reset android tool on DiscoWeb? Looks like it's not in Playstore anymore. I'm a Software Engineer with a lot of experience in mobile apps, but clueless about low-level ECU programming. If you need someone to help resurrect it and try and bundle an IOS and Android version on-top of the same codebase, LMK - might have some time to help with it. Tried to DM you but can't - feel free to DM me if interested...
 
#4 ·
Yeah - think MAF doesn’t report via obd2. I get voltage on the blue-green wire:


0.26v on ac2
1.9 idle
2.26 with Revs

still shows 0 on scanner

and confirmed connectivity to ecu plug.

removed and cleaned pvc. PVC hose a bit firm bit good shape.

Small hose from plenum to fuel regulator is really loose and sloppy on plenum side. Maybe that’s the smoking gun? Doesn’t look that special - maybe 1/8” vacuum hose - assume I can use bulk hose from Napa to see if it improve ?

also - there are no clamps on that little hose - seems like if it’s that important there should be be?
 
#6 ·
yeah thats me. Im a java serial port kind of guy, havent made time to learn the goofy apple language yet or BLE beacon interfaces for the new gen bluetooth scanners.

Google sent me a bunch of legal docs to fill out to keep it on the playstore, and I lost interest at that point
 
#7 ·
yes OBD2 does report ALL engine functions to ecu to include MAF, these engines are very prone to vacuum leaks requiring replacement of intake valley pan gasket and valve cover gaskets as well as vacuum lines. the last defender to have reached US shores is now 25 yrs old, regardless of mileage components do deteriorate with age.