Omega Owners Forum

Omega Help Area => Omega General Help => Topic started by: MikeDundee on 13 June 2015, 09:54:23

Title: Engine cutting out & fault codes
Post by: MikeDundee on 13 June 2015, 09:54:23
Earlier this week the engine just cut out when coming up to a junction, today coming back from my trip to VX in Welling car cut out after pulling away at the lights, and then cut out again a little further upon the road. Started fine again, done the pedal trick, and codes 0170 & 0173 came up Fuel trim malfunction Banks 1 & 2. Now the lambda sensors have been moved on the car (Thanks to Marks DTM), reading through some other threads could this be the MAF sensor?, breathers needing a good clean out, not been done for a while or possibly something else?
Title: Re: Engine cutting out & fault codes
Post by: chrisgixer on 13 June 2015, 10:11:33
Moved sensors only affects 0420/30. So a fuel trim malfunction, if sensor related, would point to sensor wiring or sensor performance. Could also be maf, although no code. (Or an air leak. Is tick over solid? ) no dash lights permanently lit?

Main culptret for cutting out with no code would be crank sensor though....?
Title: Re: Engine cutting out & fault codes
Post by: MikeDundee on 13 June 2015, 10:16:23
Moved sensors only affects 0420/30. So a fuel trim malfunction, if sensor related, would point to sensor wiring or sensor performance. Could also be maf, although no code. (Or an air leak. Is tick over solid? ) no dash lights permanently lit?

Main culptret for cutting out with no code would be crank sensor though....?

Only lights that came on when cut out was battery and oil light, RPM sensor was replaced in 07, but when that started originally the car would not start at all, had to get towed to VX garage until they could replace the sensor, tick over is fine.
Title: Re: Engine cutting out & fault codes
Post by: chrisgixer on 13 June 2015, 10:22:21
Yes the more normal failure mode for cs is starting issues. But they have been know to cut the engine while driving. A fuel trim error, if bad enough, will bring the engine light on.

Further investigation needed, but I'd "guess" at either a cs issue or a drive by wire issue.

But see what others say there's far more qualified than me on here. As you know. :y
Title: Re: Engine cutting out & fault codes
Post by: chrisgixer on 13 June 2015, 10:23:29
Ps. It's got fuel in? Right? ;D

And how old is fuel filter?

Does it cut under load or on tick over?
Title: Re: Engine cutting out & fault codes
Post by: MikeDundee on 13 June 2015, 10:25:38
Ps. It's got fuel in? Right? ;D

And how old is fuel filter?

Does it cut under load or on tick over?

There is fuel in :y, and yes just picked up a new fuel filter from Vx today, as cams and plugs etc., all getting done next weekend, set me back £277 today :-X
Title: Re: Engine cutting out & fault codes
Post by: chrisgixer on 13 June 2015, 10:30:17
Blocked breathers won't cause a stall btw. Mine where blocked for over a year on the old 3.2 until Dtm noticed there was no oil residue in the inlet on a pic I posted up.
Title: Re: Engine cutting out & fault codes
Post by: MikeDundee on 13 June 2015, 10:44:02
Marks DTM post  on this thread suggests that 90% of this fault is the MAF,

http://www.omegaowners.com/forum/index.php?topic=76450.msg1027673#msg1027673

http://www.omegaowners.com/forum/index.php?topic=76450.0
Title: Re: Engine cutting out & fault codes
Post by: chrisgixer on 13 June 2015, 17:45:45
2.6 is indeed sensitive to maf. Which would explain the codes.

But the stalling? Surely the maf would cause limp mode first?

Anyway, see what tothers say. :) I have a spare maf if you need one.
Title: Re: Engine cutting out & fault codes
Post by: TheBoy on 13 June 2015, 20:08:04
Without live data, we are guessing. But on a 2.6/3.2 running on petrol, if both trims are throwing trim codes, the MAF is suspicious.

This tends to lead to poor performance first, though, rather than cutting out.
Title: Re: Engine cutting out & fault codes
Post by: MikeDundee on 13 June 2015, 20:14:44
Without live data, we are guessing. But on a 2.6/3.2 running on petrol, if both trims are throwing trim codes, the MAF is suspicious.

This tends to lead to poor performance first, though, rather than cutting out.

I assume Tech 2 is needed then, to confirm?
Title: Re: Engine cutting out & fault codes
Post by: TheBoy on 13 June 2015, 20:26:33
Without live data, we are guessing. But on a 2.6/3.2 running on petrol, if both trims are throwing trim codes, the MAF is suspicious.

This tends to lead to poor performance first, though, rather than cutting out.

I assume Tech 2 is needed then, to confirm?
Generally anything capable of reading live data :y
Title: Re: Engine cutting out & fault codes
Post by: MikeDundee on 13 June 2015, 21:21:09
Without live data, we are guessing. But on a 2.6/3.2 running on petrol, if both trims are throwing trim codes, the MAF is suspicious.

This tends to lead to poor performance first, though, rather than cutting out.

I assume Tech 2 is needed then, to confirm?
Generally anything capable of reading live data :y

Thanks, that clear that up then :y, so what time will you be in Costa del Peckham tomorrow then ::)
Title: Re: Engine cutting out & fault codes
Post by: MikeDundee on 14 June 2015, 08:27:17
DLK will be down next week end so hopefully will get it all sorted, will let you know the outcome :y
Title: Re: Engine cutting out & fault codes
Post by: TheBoy on 14 June 2015, 09:07:44
(Probably for DLK's benefit)

The MAF should show up at idle if its at fault. At idle, a 2.6 should be around 13kg/hr.  Generally reads low when they start to fail.


Put on a fault code on (unplug something), then clear the fault codes, which will reset trims. Then monitor Long Term Fuel Trims (LTFT) for each bank, and see if they drift from 0%. If they both drift together, and MAF is misreading, be suspicious of the MAF...  ...but rule out airleaks in intake first.

HTH :y
Title: Re: Engine cutting out & fault codes
Post by: MikeDundee on 14 June 2015, 09:20:32
(Probably for DLK's benefit)

The MAF should show up at idle if its at fault. At idle, a 2.6 should be around 13kg/hr.  Generally reads low when they start to fail.


Put on a fault code on (unplug something), then clear the fault codes, which will reset trims. Then monitor Long Term Fuel Trims (LTFT) for each bank, and see if they drift from 0%. If they both drift together, and MAF is misreading, be suspicious of the MAF...  ...but rule out airleaks in intake first.

HTH :y

Cheers :y
Title: Re: Engine cutting out & fault codes
Post by: MikeDundee on 16 June 2015, 06:33:57
Well kept an eye on the RPM's yesterday slightly lower than normal on tick over, cut out 3 times yesterday whilst driving around, and 2 times whilst in car park, revs are just dropping out when cuts out.
Title: Re: Engine cutting out & fault codes
Post by: MikeDundee on 22 June 2015, 06:11:31
Confirmed MAF at fault, unfortunately, DLK brought a MAF but wrong one 4 pin and not 5, so have ordered one :y, for now have left the MAF unplugged, new one should be here by tomorrow, so no major hardship. Thanks to DLK for his help yesterday in sorting the problem out and confirming :y
Title: Re: Engine cutting out & fault codes
Post by: MikeDundee on 23 June 2015, 20:01:48
New MAF arrived, today, just changed over and all appears fine now, just need the EML reset, Big thanks to Jamie as he has said on a pm he will pop down to sunny Costa Peckham tomorrow to reset :yi
Title: Re: Engine cutting out & fault codes
Post by: TheBoy on 24 June 2015, 14:15:08
New MAF arrived, today, just changed over and all appears fine now, just need the EML reset, Big thanks to Jamie as he has said on a pm he will pop down to sunny Costa Peckham tomorrow to reset :yi
Have a bloody job, seeing as I'm the other side of the Channel ;D

EML should go out when fault is fixed...
Title: Re: Engine cutting out & fault codes
Post by: Marks DTM Calib on 24 June 2015, 15:26:55
Might take a while for the fuel trims to recover though  :y
Title: Re: Engine cutting out & fault codes
Post by: MikeDundee on 01 July 2015, 05:56:47
EML went out the day after, all good now :y