Omega Owners Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

Welcome to OOF

Pages: [1]   Go Down

Author Topic: MV6 engine light trouble  (Read 1106 times)

0 Members and 1 Guest are viewing this topic.

Ratboy

  • Newbie
  • *
  • Offline Offline
  • Gender: Male
  • netherlands
  • Posts: 33
    • 99 opel omega caravan
    • View Profile
MV6 engine light trouble
« on: 28 March 2017, 23:05:10 »

hi,
After selling my 99 caravan last week i ran into an 96 MV6 for 400€. i was looking for a 3.0 to use as donor for a 1964 opel rekord but thats besides the issue. because the MV6 still has MOT till september and only issue was a leaking coolin hose i decided to see how good it still runs and what parts need attention. even as it has had 10+ owners the car seemed to be pretty good looked after. only minor issues like the rear sunshade, electric passenger seat, alarm and faded headlights, everything works like a charm. The only other issue is that when driving arround relaxed at city speeds the engine light goes on and of almost all the time. when i decelerate it usually goes on and as soon i hit the gas it goes out again. on the highways theres no issue. at first i tought it was maybe a case of bad fuel as i noticed it first when i filled her up but have refueled it from other places and its still the same.
and what puzzles me the most is that the car doesn't act strange at all, no lumpy idle, backfires, heavy fuel consumption(i just done 150km with an average of 8.3l/100km at 140km/h, less then my 2.5) or loss of power it just keeps buzzing like she should.
So far i did not find time to read the ECU but will come tomorrow.
anyone here had the same issue. i did google for it but nothing came up like this.
Logged

zirk

  • Omega Queen
  • *****
  • Offline Offline
  • Gender: Male
  • Epping Forest
  • Posts: 11431
  • 3.2 Manual Special Saloon ReMapped and LPG'd and
    • 3.2 Manual Special Estate
    • View Profile
Re: MV6 engine light trouble
« Reply #1 on: 29 March 2017, 07:13:24 »

No real point in trying to guess, EML light means read the Code(s).
Logged

TheBoy

  • Administrator
  • *****
  • Offline Offline
  • Gender: Male
  • Brackley, Northants
  • Posts: 105932
  • I Like Lockdown
    • Whatever Starts
    • View Profile
Re: MV6 engine light trouble
« Reply #2 on: 29 March 2017, 14:29:50 »

Should be able to read codes on that with a paperclip, like Opels of old :y
Logged
Grumpy old man

Ratboy

  • Newbie
  • *
  • Offline Offline
  • Gender: Male
  • netherlands
  • Posts: 33
    • 99 opel omega caravan
    • View Profile
Re: MV6 engine light trouble
« Reply #3 on: 01 April 2017, 01:44:23 »

Update,
today i finally had the time to plug in the scanner.
I did't had any real codes stored. it only gave a
"message" saying that it didn't recieve any revmeter signal
when the car is started. normally with the vertrix scanner at work
if you then highlight the message and press the ok button you then
get a code and more details. But highlighting wasn't available in this case.
so i called the troops in and they suggested replacing camshaft and
crankshaft sensors and see what it does. if not i can just return them to the
partsstore.(benefit of working at a garage  :y )
So i pretty much gone thru the entire menu of the car,
Then one of the guys suddely said to go a page back, and he pointed to the
ignition advance degree numbers when the car was idling and it gave  a abnormal
reading of 38 to 40 degrees advance  :o :o :o
He guessed that as the ecu regulates this, it could be that 40 is the maximum
possible and therefor it might be the EML lighting up.
what also might cause a high advance is a bad timingbelt change or it has jumped
a tooth on the part responsible for timing.
We shall see next week how the car behaves with the new sensors.
Logged

powerslinky

  • Guest
Re: MV6 engine light trouble
« Reply #4 on: 02 April 2017, 13:51:34 »

V6 cam sensors  virtually bullet proof IMO

Crank sensor fault causes "cutting out"  and "not starting" issues

So probably replacing these will not help  . . . .only my opinion though ::)
Logged

Ratboy

  • Newbie
  • *
  • Offline Offline
  • Gender: Male
  • netherlands
  • Posts: 33
    • 99 opel omega caravan
    • View Profile
Re: MV6 engine light trouble
« Reply #5 on: 02 April 2017, 22:17:22 »

Still, no one any ideas about the 40°advance on the ignition timing?
What i did notice was that as long as the engine has not been at the
Normal operating temperature the light does not come on. So could it be
That the EGR valve doesn't work as should? Well meaning that its doesnt shut
Down once temp of the engine is nornal.
Logged

Ratboy

  • Newbie
  • *
  • Offline Offline
  • Gender: Male
  • netherlands
  • Posts: 33
    • 99 opel omega caravan
    • View Profile
Re: MV6 engine light trouble
« Reply #6 on: 17 April 2017, 22:13:34 »

SORTED! It was a faulty knock sensor cable on the 135 bank. I was going thru all the connectors and accidently rubbed against the wire right behind the connector and suddenly the engine like choked and started to run different with more vibrations. So i replaced both sensors and checked the vacuum lines where one line wasnt connected to the vacbox above the interior filter. Also when i took a quick drive to germanys autobhan (german border is only 30km away) the 3way bypass split open with a puff of white smoke ::) . as this one is my second ommi i had my lil toolbox with me where i keep a splitter for a (don't laugh....it works) gardenhose with on each end an inch of hose glued to the splitter. Its the same diameter as the coolant hoses. And on my first ommi it got me thru the week untill the new one arrived from ebay. So after a good 30mins i still got to put the old mv6 to its limits. I got 236km/h. :D.
Next week my usual daily driver (64 opel rekord A) will have its new drumbrakes and the ommi will be retired and stripped completely to have its parts used for my lil rekord project. Somewhere next year. I got my GMC vandura 4x4 conversion to finish first.
Logged
Pages: [1]   Go Up
 

Page created in 0.018 seconds with 18 queries.