Omega Owners Forum

Omega Help Area => Omega General Help => Topic started by: omegod on 14 September 2010, 16:01:56

Title: 2.2 not OBD11 compliant
Post by: omegod on 14 September 2010, 16:01:56
It seems there is some confusion over wether a 2001 2.2 petrol would be OBD11 compliant, anyone got any clue as to this being correct?
Title: Re: 2.2 not OBD11 compliant
Post by: Rob-Mitton on 14 September 2010, 16:29:05
My 2001 2.2 petrol estate on a "Y" plate is OBD11 compliant.

Hope this helps

Rob
Title: Re: 2.2 not OBD11 compliant
Post by: omegod on 14 September 2010, 16:33:13
Cheers mate mine is a y reg too! Spoke to a reader supplier who thinks the Autel maxiscan ms309 I am looking at may not cover my car...strange one
Title: Re: 2.2 not OBD11 compliant
Post by: PhilRich on 14 September 2010, 18:49:56
Omegas from MY2000 are OBD11 Compliant afaik ;)
Title: Re: 2.2 not OBD11 compliant
Post by: omegod on 14 September 2010, 19:13:25
Quote
Omegas from MY2000 are OBD11 Compliant afaik ;)

Managed to try the  one mentioned above on the car and it wouldn't  connect!!! Any recomendations of one that has worked?

Any 
Title: Re: 2.2 not OBD11 compliant
Post by: Entwood on 14 September 2010, 19:15:57
The Maxscan GS500 works on my 2001 3.2 .. :)
Title: Re: 2.2 not OBD11 compliant
Post by: SJKOO01 on 14 September 2010, 19:32:11
My Sealey VS8700 reader works fine on my 2.2 as well.

What are you trying to read / problems are you having ?.
Title: Re: 2.2 not OBD11 compliant
Post by: omegod on 14 September 2010, 19:35:52
Quote
My Sealey VS8700 reader works fine on my 2.2 as well.

What are you trying to read / problems are you having ?.

Intermittent MIL and SVS light which clears when restarted, driving fine and dandy though ! Reader seems to be identifying the right protocol ( KWP 2000 ? ) but reports a "linking error"
Title: Re: 2.2 not OBD11 compliant
Post by: SJKOO01 on 14 September 2010, 19:45:21
Quote
Quote
My Sealey VS8700 reader works fine on my 2.2 as well.

What are you trying to read / problems are you having ?.

Intermittent MIL and SVS light which clears when restarted, driving fine and dandy though ! Reader seems to be identifying the right protocol ( KWP 2000 ? ) but reports a "linking error"

Not sure what could be causing the x2 problems myself.
As for the 'linking error', sounds like your reader is not capable of reading your error codes.  Hope you don't mind me asking, bit did you get the reader from ebay at all ?.  As I know some people have had problems buying readers on the site  :-? .

Just a thought, but maybe an idea to put up another thread, with the subect / heading as "highlighted", you may have some luck with someone who's had the same kind of problem advising you better.  :y
Title: Re: 2.2 not OBD11 compliant
Post by: RobG on 14 September 2010, 20:06:01
Quote
The Maxscan GS500 works on my 2001 3.2 .. :)
And my 2003 2.2
Title: Re: 2.2 not OBD11 compliant
Post by: Welung666 on 14 September 2010, 20:08:13
Linking error on some of the cheaper readers is common. Plug the reader in, start the car and try to connect. It'll work everytime :y
Title: Re: 2.2 not OBD11 compliant
Post by: omegod on 14 September 2010, 20:12:00
Quote
Linking error on some of the cheaper readers is common. Plug the reader in, start the car and try to connect. It'll work everytime :y

Cheers, will give that a try in the morning 
Title: Re: 2.2 not OBD11 compliant
Post by: TheBoy on 14 September 2010, 21:57:51
Quote
Omegas from MY2000 are OBD11 Compliant afaik ;)
Nope. Not true.


2.2 petrol is OBDII compliant though.
Title: Re: 2.2 not OBD11 compliant
Post by: PhilRich on 14 September 2010, 22:12:54
Quote
Quote
Omegas from MY2000 are OBD11 Compliant afaik ;)
Nope. Not true.


2.2 petrol is OBDII compliant though.






 :-[ That will teach me to either get my facts right or keep my nose out! ::) ;D ;D :y
Title: Re: 2.2 not OBD11 compliant
Post by: davethediver on 14 September 2010, 23:02:18
Quote
Quote
Quote
Omegas from MY2000 are OBD11 Compliant afaik ;)
Nope. Not true.


2.2 petrol is OBDII compliant though.






 :-[ That will teach me to either get my facts right or keep my nose out! ::) ;D ;D :y

But it would be no fun otherwise ;D ;D
Title: Re: 2.2 not OBD11 compliant
Post by: whippit 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 ;)
Title: Re: 2.2 not OBD11 compliant
Post by: omegod on 15 September 2010, 13:06:19
What wellung suggested worked but no codes, new thread started to find out WTF
Title: Re: 2.2 not OBD11 compliant
Post by: Marks DTM Calib 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