Omega Owners Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

Please play nicely.  No one wants to listen/read a keyboard warriors rants....

Pages: 1 [2]  All   Go Down

Author Topic: 2.2 not OBD11 compliant  (Read 1840 times)

0 Members and 1 Guest are viewing this topic.

whippit

  • Junior Member
  • **
  • Offline Offline
  • Gender: Male
  • Kirkcaldy, Fife
  • Posts: 79
    • View Profile
Re: 2.2 not OBD11 compliant
« Reply #15 on: 15 September 2010, 12:35:10 »

had a bit of fun with this myself.
Took the car (2.2 pettrol auto) to my local mech on saturday and he could not get any of his code readers to talk to it (including the snap-on verso which is the dogs danglies).
He was convinced he must have had a fault with his lead or something.
Anyhow took it back in today and his lad was working who seemed much more clued up, apparently its something to do with the switched and permanent live to the socket and you have to connect first then turn the ignition on, the other guy had just been connecting with the ignition already on.
Upshot..all connected fine, codes read and reset and no naggy light on the dash ;)
Logged

omegod

  • Omega Baron
  • *****
  • Offline Offline
  • Gender: Male
  • liverpool
  • Posts: 4348
    • 2017 Seat Ateca
    • View Profile
Re: 2.2 not OBD11 compliant
« Reply #16 on: 15 September 2010, 13:06:19 »

What wellung suggested worked but no codes, new thread started to find out WTF
Logged
Happy to do Omega servicing etc around Merseyside,cruise activation, airbag lights sorted too...

Marks DTM Calib

  • Administrator
  • *****
  • Offline Offline
  • Gender: Male
  • West Bridgford
  • Posts: 34016
  • Git!
    • View Profile
Re: 2.2 not OBD11 compliant
« Reply #17 on: 15 September 2010, 13:14:37 »

Quote
had a bit of fun with this myself.
Took the car (2.2 pettrol auto) to my local mech on saturday and he could not get any of his code readers to talk to it (including the snap-on verso which is the dogs danglies).
He was convinced he must have had a fault with his lead or something.
Anyhow took it back in today and his lad was working who seemed much more clued up, apparently its something to do with the switched and permanent live to the socket and you have to connect first then turn the ignition on, the other guy had just been connecting with the ignition already on.Upshot..all connected fine, codes read and reset and no naggy light on the dash ;)

Crappy code reader then
Logged
Pages: 1 [2]  All   Go Up
 

Page created in 0.031 seconds with 17 queries.