GV 2006 made in Japan distributed in Qatar Middle East not OBD2 compliant

[joeyd11ph]

Please confirm if above subject is true.

Please read my email inquiry to generic ScanTool manufacturer and their reply:

Hi Avary,

My car is Suzuki Grand Vitara 2006 made in Japan distributed in Qatar, Middle East.

There is wire on pin 7 ISO9141 and 6/14 for CAN on J1962 DLC female connector under the dashboard.

I managed to established the link between laptop and vehicle through ElmScan5Bluetooth. All LEDs are working and even able to verified protocol (KWP2000 fast ini) used.
Problem is using your ScanTool.net v1.14 I got N/A on all sensors or even one sensor only (RPM).

I tried to use your STNterm to see if I can talk to Elm and ECU.
For AT command all are ok but for OBD like 01 00 and other comands I got only 7F 01 11 response.

I also tried the diferent CAN settings from 6 to C but I got CAN ERROR message.

Please let me know what this 7F 01 11 means. Take note that Ive tried several OBD commands and I got same response.

thanks

joey

Hi joeyd11ph,

If you receive a 7F 01 11 response to a 0100 command, it means that your vehicle knows what OBDII compliance is, but the manufacturer has decided not to support service 01 pid 00. A 7F 01 11 response is a not supported response for an ISO-14320-4 protocol vehicle. Effectively that makes your vehicle non OBDII compliant and you cannot expect to connect with an ElmScan5 Bluetooth or any other OBDII compliant scan tool. The possible reason for this is that your country doesn't regulate for OBDII compliance, and therefore the manufacturer decides to deliberately omit OBDII compliance from the vehicle.

Regards
Graham McKechnie
GLM Software
OBD 2007

[Msolano]

Just my two cents on this:

A couple of months ago, a friend of mine brought a MaxiScan MS509 OBDII EOBD Scanner, which is OBDII compliant and accept several other protocols. He's used his scanner on his Isuzu Trooper flawlessly and I tried to use it on my 2006 2.0 Grand Vitara.

No protocol (from a list about 15 different ones) was able to communicate with the GV ECU, although the connector is an OBDII compliant. I gave up and never tried again.

Looking at your post, it might confirm why my GV didn't communicate with the scanner. Probably because my GV was sold on Panama, where the ODBII compliance is not enforced, Suzuki decided to not make it available to us.

Comments?

-MJ

[joeyd11ph]

Hi Msolano

Thanks for your info.

Currently Im doing hardware/firmare investigation. I will let you know any pogress on this.

Please find a way to contact Suzuki Japan and ask them on how to activate our OBD2 feature.

Thanks

Joey

[Rhinoman]

I'm a bit late to this but earlier Suzuki models have a datalink on pin 9 of the OBD2 connector. I hacked this a couple of years ago and have been working on a project to allow the data link to be read using an ALDL style interface. There is already one guy who has this working with a 1999 GV. I don't believe that anyone has tried this with a vehicle as new as 2006 but it seems likely that it will work.

RhinoPower