RhinoPower Ltd

JimJ · Member

Check Engine Light

TechSupport · Guru

JimJ wrote:
Should a generic OBD II connect?

No, sometimes they will connect but they don't communicate, OBD2 uses a different implementation of KWP2000.

JimJ · Member

Has the fuel filter been changed?

That is next on my list.

Plugs have been changed and ignition coils disconnected one by one.

Back to the old days of elimination.

I will have to figure out how to read the codes using the jumper.

if it doesn't connect through EOBD/OBD2

Should a generic OBD II connect?

TechSupport · Guru

FSM = factory Service manual, I see that you already have it. You have ISO9141 comms and not SDL, if it doesn't connect through EOBD/OBD2 then you need the Suzuki Scan Tool. You can access fault codes using a jumper in the monitor coupler. Has the fuel filter been changed?

JimJ · Member

OK.Thanks for the reply

So I have two "ports" on my GV. One "ÖBD style" 16 pin connector under the dash with pins 4 5 7 9 16 populated and a white female six pin connector (monitor coupler?) near the ABS unit in the engine bay.

The Service Manual refers to the port under the dash as "Data Link Connector"

What is the purpose of this connector under the dash and what scan tool will work with that connector or will it only work the Suzuki scan tool?.

According to the Service Manual for the GV,

Data Link Connector (DLC)
DLC (1) in compliance with SAE J1962 in its installation position, the shape of connector and pin assignment.
K line of ISO 9141 (4) is used for SUZUKI scan tool to communication with ECM (PCM), Airbag SDM and ABS control module.
SUZUKI serial data line (3) is used for SUZUKI scan tool to communicate with an electronic control units (Immobilizer control module).

Not sure what you mean by;

You can download the FSM here

TechSupport · Guru

The SDL interface will not work with vehicles that have pin 7 populated, those vehicles use an implementation of KWP2000, its not an OBD/EOBD compatible format.

You should have a 'monitor coupler' that allows you to read codes through the check engine light, the codes on that are probably not the same as the earlier models. You can download the FSM here: Rhinoman's Portal

JimJ · Member

My Suzy GV is an Australian 2001 V6 2.5 VIN JSAFTD62V00154280

I have an "Check Engine Light" that comes on after about 20 minutes of driving.

The symptoms are;

A monetary shudder.

Check engine light

Engine loses power

Runs rough intermittently

An increase in throttle gives symptoms similar to flooding

Idles smoothly.

I have replaced all the spark plugs.

I have tried to scan with a OM126 OBDII+EOBD. This would not connect.

Our local mechanic cannot connect to the ECU with his reader.

After a bit of searching and reading the maintenance manual I concluded that the vehicle had a SDL interface. Am I correct?

I have just received the SDL Interface and I am having trouble connecting to the ECU.

Running windows 10 pro 64bit on a Intel i5 on Thinkpad laptop.

I have installed RhinoView Dashboard v1.3 with the FD2XX files in the same folder.

When I select Comms - Connect I get a message "trying to Connect" and a continuous "Rx Errors" count.

The OBD style port has connections to 4, 5, 7, 9 and 16.

Questions;

Should this SDL Interface work with the port?

If not, with what can I read codes, etc from the ECU.

TIA

-- Edited by JimJ on Thursday 4th of April 2024 05:42:25 AM