Omega Owners Forum

Omega Help Area => Omega General Help => Topic started by: Steve B on 24 January 2015, 20:14:09

Title: P0100
Post by: Steve B on 24 January 2015, 20:14:09
So this is a MAF related code i read on here and live data Can help to diagnose
Is it the MAF only live data i need to put up or the whole sheet cos there is a lot of it  :y

IE; Voltage and Kg/h
Title: Re: P0100
Post by: Steve B on 25 January 2015, 00:13:21
(https://dl.dropboxusercontent.com/u/70807181/3.2%20read.jpg)

MAF Not working proper   9 secs on tickover and when i increase rev MAF data stays same .

And the code is tripped up instantly after clearing code on start up
high MPG
Uneven tickover

Title: Re: P0100
Post by: 05omegav6 on 25 January 2015, 08:30:59
To be sure, does it run better with the MAF unplugged :-\

If yes, then you need a new one, if no, then there's potentially an air leak somewhere  :y
Title: Re: P0100
Post by: TheBoy on 25 January 2015, 18:41:12
Ah, another shitty code reader ;D

The fact its whacked at one end of the scale suggests the ECU isn't seeing the MAF reading at all. If should be able to detect that, and substitute a limp value.

Is the bugger plugged in?
Title: Re: P0100
Post by: Steve B on 25 January 2015, 18:43:51
Ah, another shitty code reader ;D

The fact its whacked at one end of the scale suggests the ECU isn't seeing the MAF reading at all. If should be able to detect that, and substitute a limp value.

Is the bugger plugged in?
Yep  ;D ;D ;D

Is that what your thinking tb not plugged in  :-\
Title: Re: P0100
Post by: TheBoy on 25 January 2015, 18:52:22
Ah, another shitty code reader ;D

The fact its whacked at one end of the scale suggests the ECU isn't seeing the MAF reading at all. If should be able to detect that, and substitute a limp value.

Is the bugger plugged in?
Yep  ;D ;D ;D

Is that what your thinking tb not plugged in  :-\
Either not plugged in, completely 'dangle berries'ed, severely damaged loom or shagged ecu.
Title: Re: P0100
Post by: Steve B on 25 January 2015, 18:53:59
Ah, another shitty code reader ;D

The fact its whacked at one end of the scale suggests the ECU isn't seeing the MAF reading at all. If should be able to detect that, and substitute a limp value.

Is the bugger plugged in?
Yep  ;D ;D ;D

Is that what your thinking tb not plugged in  :-\
Either not plugged in, completely 'dangle berries'ed, severely damaged loom or shagged ecu.
Dont say that.. gonna nip out in bit have a look
Title: Re: P0100
Post by: Steve B on 25 January 2015, 19:23:02
Yes its plugged in alright..Too dark to see how to unplug...What do you do press that little tab in on the side  :-\
Title: Re: P0100
Post by: 05omegav6 on 25 January 2015, 20:27:06
Yes its plugged in alright..Too dark to see how to unplug...What do you do press that little tab in on the side  :-\
That's about it :y
Title: Re: P0100
Post by: Steve B on 26 January 2015, 16:01:57
(https://dl.dropboxusercontent.com/u/70807181/3.2%20read.jpg)

MAF Not working proper   9 secs on tickover and when i increase rev MAF data stays same .

And the code is tripped up instantly after clearing code on start up
high MPG
Uneven tickover
Does that look any better   Coldish engine

(https://dl.dropboxusercontent.com/u/70807181/3.2%20maf%20in.jpg)



Title: Re: P0100
Post by: Steve B on 26 January 2015, 19:55:51
Drives a lot better now its not using the default settings in the ECU.. Put in a Known working MAF cleared codes been on a few trips and no more code and dash is clear for the first time...Great  :y :y
Title: Re: P0100
Post by: TheBoy on 27 January 2015, 18:42:59
That looks more viable for kg/hr. Shade high, but if the engine was cold...
Title: Re: P0100
Post by: Steve B on 27 January 2015, 20:23:02
That looks more viable for kg/hr. Shade high, but if the engine was cold...
Yes its  sorted.. But to be on the double safe side. I bought Two MAF,s  ;D ;D ;D

Put the other one on today to give that a test too on a warm engine..

(https://dl.dropboxusercontent.com/u/70807181/second%20maf.jpg)
Title: Re: P0100
Post by: TheBoy on 28 January 2015, 18:01:13
That's about right.