Thread: Td5 with altitude sickness

also try running with the maf disconnected, they can be overcleaned especially if something other than dedicated maf cleaner was used, what year is the deefer?

Originally Posted by discorevy

also try running with the maf disconnected, they can be overcleaned especially if something other than dedicated maf cleaner was used, what year is the deefer?

It’s a 2005 model. The MAF sensor is about a year old and got only cleaned with MAF cleaner.

ok , if the maf is vdo it should be ok unless you've increased boost too much, try disconnecting it and go for a run , you'll have a delayed throttle at first but will be ok after that so don't pull out in front of traffic till after the first delay, this is just to diagnose .

Originally Posted by discorevy

ok , if the maf is vdo it should be ok unless you've increased boost too much, try disconnecting it and go for a run , you'll have a delayed throttle at first but will be ok after that so don't pull out in front of traffic till after the first delay, this is just to diagnose .

The MAF is DPL to suit the engine modifications and tune. I forgot to connect it last time I cleaned it and was wondering why the engine was running rough and had a delayed turbo response .

Originally Posted by harro

Input for altitude come from the AAP sensor on the airbox lid.
Disconnect it and it defaults to 100 kpa (sea level).

See how that goes, it will tell you if the sensor is faulty or not.
Hopefully just a clean as they are quite expensive.

Paul.

+1 for that^^^

Thanks everyone for all the input.
I cleaned the connectors with contact cleaner and the engine runs just fine here in Sydney.
Today, I plugged the Nanocom in and I got he following engine fault which I haven't seen before:
(3,7) Air Flow Circuit Logged High

I couldn't find any clear definition of this fault on the web. Can anyone explain this fault reading?

Cheers
Joachim

The MAF reading is higher than expected for the driver demand and the delivered boost, could be due to faulty MAF or some boost leak

Sounds to me like a MAF fault...