Omega Owners Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

Welcome to OOF

Pages: [1] 2  All   Go Down

Author Topic: Engine cutting out & fault codes  (Read 3155 times)

0 Members and 1 Guest are viewing this topic.

MikeDundee

  • Omega Lord
  • *****
  • Offline Offline
  • Gender: Male
  • Costa Del Peckham
  • Posts: 9370
    • View Profile
Engine cutting out & fault codes
« 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?
Logged

chrisgixer

  • Omega Baron
  • *****
  • Offline Offline
  • Woking ham
  • Posts: 2616
  • Banned
    • Irmscher 3.2 Elite lpg
    • View Profile
Re: Engine cutting out & fault codes
« Reply #1 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....?
Logged

MikeDundee

  • Omega Lord
  • *****
  • Offline Offline
  • Gender: Male
  • Costa Del Peckham
  • Posts: 9370
    • View Profile
Re: Engine cutting out & fault codes
« Reply #2 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.
Logged

chrisgixer

  • Omega Baron
  • *****
  • Offline Offline
  • Woking ham
  • Posts: 2616
  • Banned
    • Irmscher 3.2 Elite lpg
    • View Profile
Re: Engine cutting out & fault codes
« Reply #3 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
Logged

chrisgixer

  • Omega Baron
  • *****
  • Offline Offline
  • Woking ham
  • Posts: 2616
  • Banned
    • Irmscher 3.2 Elite lpg
    • View Profile
Re: Engine cutting out & fault codes
« Reply #4 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?
Logged

MikeDundee

  • Omega Lord
  • *****
  • Offline Offline
  • Gender: Male
  • Costa Del Peckham
  • Posts: 9370
    • View Profile
Re: Engine cutting out & fault codes
« Reply #5 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
Logged

chrisgixer

  • Omega Baron
  • *****
  • Offline Offline
  • Woking ham
  • Posts: 2616
  • Banned
    • Irmscher 3.2 Elite lpg
    • View Profile
Re: Engine cutting out & fault codes
« Reply #6 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.
Logged

MikeDundee

  • Omega Lord
  • *****
  • Offline Offline
  • Gender: Male
  • Costa Del Peckham
  • Posts: 9370
    • View Profile
Re: Engine cutting out & fault codes
« Reply #7 on: 13 June 2015, 10:44:02 »

Logged

chrisgixer

  • Omega Baron
  • *****
  • Offline Offline
  • Woking ham
  • Posts: 2616
  • Banned
    • Irmscher 3.2 Elite lpg
    • View Profile
Re: Engine cutting out & fault codes
« Reply #8 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.
Logged

TheBoy

  • Administrator
  • *****
  • Offline Offline
  • Gender: Male
  • Brackley, Northants
  • Posts: 105930
  • I Like Lockdown
    • Whatever Starts
    • View Profile
Re: Engine cutting out & fault codes
« Reply #9 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.
Logged
Grumpy old man

MikeDundee

  • Omega Lord
  • *****
  • Offline Offline
  • Gender: Male
  • Costa Del Peckham
  • Posts: 9370
    • View Profile
Re: Engine cutting out & fault codes
« Reply #10 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?
Logged

TheBoy

  • Administrator
  • *****
  • Offline Offline
  • Gender: Male
  • Brackley, Northants
  • Posts: 105930
  • I Like Lockdown
    • Whatever Starts
    • View Profile
Re: Engine cutting out & fault codes
« Reply #11 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
Logged
Grumpy old man

MikeDundee

  • Omega Lord
  • *****
  • Offline Offline
  • Gender: Male
  • Costa Del Peckham
  • Posts: 9370
    • View Profile
Re: Engine cutting out & fault codes
« Reply #12 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 ::)
Logged

MikeDundee

  • Omega Lord
  • *****
  • Offline Offline
  • Gender: Male
  • Costa Del Peckham
  • Posts: 9370
    • View Profile
Re: Engine cutting out & fault codes
« Reply #13 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
Logged

TheBoy

  • Administrator
  • *****
  • Offline Offline
  • Gender: Male
  • Brackley, Northants
  • Posts: 105930
  • I Like Lockdown
    • Whatever Starts
    • View Profile
Re: Engine cutting out & fault codes
« Reply #14 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
Logged
Grumpy old man
Pages: [1] 2  All   Go Up
 

Page created in 0.031 seconds with 18 queries.