Omega Owners Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

Search the maintenance guides for answers to 99.999% of Omega questions

Pages: [1]   Go Down

Author Topic: Got EML Fault codes Help needed  (Read 945 times)

0 Members and 1 Guest are viewing this topic.

andycuk71

  • Junior Member
  • **
  • Offline Offline
  • Gender: Male
  • Reading
  • Posts: 113
    • View Profile
Got EML Fault codes Help needed
« on: 23 May 2007, 18:06:11 »

Ok flashed the Diagnistic thingy and found the following fault codes.

19 = RPM Crankshaft sensor

59 = Inlet manifold valve

132 = Exhaust gas recirculation valve


Any thoughts anyone???
Logged

JamesV6CDX

  • Omega Queen
  • *****
  • Offline Offline
  • Gloucestershire/Buckinghamshire
  • Posts: 16640
    • Omega 3.2 Retail MV6 LPG
    • View Profile
Re: Got EML Fault codes Help needed
« Reply #1 on: 23 May 2007, 18:13:19 »

19 is usually fatal - crankshaft sensor. Would be worth clearing the codes if you can and seeing if it re-appears.

as far as the EGR ones goes - make sure you have good connections on ALL plugs, and there is no loom damage from work done...
Logged

andycuk71

  • Junior Member
  • **
  • Offline Offline
  • Gender: Male
  • Reading
  • Posts: 113
    • View Profile
Re: Got EML Fault codes Help needed
« Reply #2 on: 23 May 2007, 18:15:42 »

Ok how do you clear codes??

Why has crankshaft come up when it was not before

Why is it fatal??

 RPM signal (crankshaft sensor) Incorrect signal  was the exact error stated on topbuzz is this fatal and why???
« Last Edit: 23 May 2007, 18:21:38 by andycuk71 »
Logged

JamesV6CDX

  • Omega Queen
  • *****
  • Offline Offline
  • Gloucestershire/Buckinghamshire
  • Posts: 16640
    • Omega 3.2 Retail MV6 LPG
    • View Profile
Re: Got EML Fault codes Help needed
« Reply #3 on: 23 May 2007, 18:24:53 »

Quote
Ok how do you clear codes??

Why has crankshaft come up when it was not before

Why is it fatal??

 RPM signal (crankshaft sensor) Incorrect signal  was the exact error stated on topbuzz is this fatal and why???

Crank sensor stores 2 codes, 19 is no signal, and 31 is low voltage (FROM MEMORY!)

code 19 USUALLY means the crank sensor is on the way out, but may not be the case all the time

Does is start ok, and rev over 5000 rpm?

As before, check all connections religiously before you suspect anything is up. Make sure they are all home, all wires are in good order, and you haven't got 2 transposed..
Logged

TheBoy

  • Administrator
  • *****
  • Offline Offline
  • Gender: Male
  • Brackley, Northants
  • Posts: 107026
  • I Like Lockdown
    • Whatever Starts
    • View Profile
Re: Got EML Fault codes Help needed
« Reply #4 on: 23 May 2007, 18:34:44 »

On the v6, 2 crank sensor codes:

19 (incorrect signal) - crank sensor IS fubar. It WILL let you down. Replace ASAP. Ignore at your peril.
31 (no signal) - If the car not running, this is normal. If the car won't start, this code is indeterminate.  If the car starts, and you still get this code with engine running (v6 can be paperclipped with engine running), sensor is bust.
Logged
Grumpy old man

amba

  • Omega Baron
  • *****
  • Offline Offline
  • Gender: Male
  • Medway towns
  • Posts: 4827
    • German V6
    • View Profile
Re: Got EML Fault codes Help needed
« Reply #5 on: 24 May 2007, 05:45:03 »

Identical case with my 1998 2.5 elite..took TB,s advise and replaced the crank sensor..beware though..there are 2 plug type connecters which are different in price and have different plug connecter..can be seen with windscreen scuttle panel removed..just trace the connecter and follow the wire down to around oil filter area..if you  check out site there is a perfect "how to " on replacing it.Not too bad a job with car in air..but with a code 19 you should replace that first then see if anything else flashes up...incidentley mine also required a TPS but unsure if they were related problems or just bad luck..anyway mine now runs sweet..good luck with yours
Logged
Pages: [1]   Go Up
 

Page created in 0.01 seconds with 17 queries.