OK, I Made a Mistake - Maybe

[Guest]

OK, I made a mistake, maybe, and bought a iCarsoft i930 code scanner a few weeks back and whilst it works quite happily with most of the Control Modules on my S Type it cannot get data from the ECU. My grumbles to the supplier have produced requests for confirmation of model and year and whether I have updated the on-board software to latest version - provided and done. Still no joy getting data from the ECU and now the supplier is suggesting the car is not ODB2 compliant.

My understanding is that all cars sold in the UK after 2001 had to be ODB2 compliant to conform with EU directives. Can anyone confirm this or indeed whether any S Types managed to escape this net?

I'm planning to take the car along to a Jag specialist to ensure there is not a problem with the ECU itself to avoid any possible further embarrassment but I would have expected all kinds of warning lights to go on if there were - or am I kidding myself?

All suggestions or comments welcome before I aim a firm kick at the suppliers tender bits.

Many thanks in anticipation.

[JOE-DOT-COM]

Hi

Its a common problem with the Icarsoft I930, most people cant get them to work, with the engine ecu

some people can by updating the I930 through the Icarsoft site,

but most people I've seen end up returning it and swapping for the Icarsoft LRII

just google it, a lot of people have had the same problem

cheers

Joe

[Raistlin]

Exactly my experience Joe / Steve.

I930 would not see the ECU. LR2 sees everything.

[Guest]

Thanks Joe/Paul,

Now to aim a boot at some tender bits.

Cheers,

Steve

[thathawk400]

I have one as well I use on my 2002 STR did have a similar problem as well not seeing the ecu may be I am lucky as all I did was disconnect and connect it again and switch on the ignition and it worked great bit of kit if you get it working has saved me quite a bit of money in diagnostics.