RhinoPower Ltd

Rhinoman wrote:

---

That should be OBD2 however there are a number of compatibility problems with Suzukis and OBD2 scanners so if one scanner doesn't work then try another.
The Elm based scanners are usually quite reliable if you avoid the Chinese clones.

---

 Please guide me.  I am planning to buy ELM 327 Bluetooth with Torque software.  I have a Maruti Suzuki Wagon R DUO (2010).

The port has 4, 5, 7, 9 and 16 pins respectively.  Will ELM work in my car?    Thanks

 

I will get you the request and response with engine on and off.

I am located in Pune, India.

I also had success to conenct with ECU with ELM327.

 

aashishkul wrote:

---

Yes, it is the same ECU. Actually, it looks like to me that Maruti Suzuki might have blocked the standard OBD and kept only their own implementation.

---

I think that they have only implemented the protocol that is used in other markets for accessing Suzuki Proprietary Data on KWP2000 ECUs. I believe that I have the information required to implement this so I will work on producing a new interface and software to support this.

 

aashishkul wrote:

---

At kw
At kw
1:E9 2:8F
>

---

I'm puzzled by this, in your last post have:

Res. 80 F1 11 03 C1 EF 8F C4

is this the same ECU? 

To give you an idea:

1. Initialization- Fast KWP init

2. Init message:

Start of comm
Req. 81 11 F1 81 04
Res. 80 F1 11 03 C1 EF 8F C4

Wake up

Req. 81 11 F1 3E C1
Res. 80 F1 11 01 7E 01

 

I will sniff some more and let you know. However, given this inforamtion, how would you proceed in this case?

It is possible to make a Y-cable to sniff the protocol. You would need to connect the SDL line to the receive line of another interface and then monitor the data on the SDL line using a trerminal emulator such as RS232 Hexcom tool. What tool do you have access to? I have an SDT but I haven't been able to try it on an Indian ECU.

Switch off header checking and try changing the header byte to force the ELM tool to insert a length byte. If you don't get a positive response then try changing the ECU address to 12.

For some reason my cheap eBay clone doesn't show headers even when I send ATH1 so I need to get a serial analyser hooked up.

I haven't given up on this, I'm still working on it with a guy in Australia who has a similar issue. I have a lot of new information about the way that Suzuki use the KWP2000 protocol, I just need to run a bunch of tests. It looks as if the ELM tool doesn't support the correct version of the KWP2000 spec.

The Denso ECUs that we have use Motorola/Freescale microcontrollers and are programmed via the diagnostic port. What numbers are on the processor?

Not much help unfortunately.

When you open the case on the ECU look on the circuit board for the pin designations, these are usually printed on the circuit board. There are two pins that are of interest ST is the 12V/OBD2 connection and SDL is the OBD1 connection. ST should be wired to pin 7 on the diagnostic connector, SDL may not be present and if it is may not be wired and the components may not be fitted but any information that we can get helps us.

Can you post a picture of the circuit board? it looks like its in a metal case so it should be similar to the Swift Euro 3 ECU that I have here.

aashishkul wrote:

---

>
0100
83 F1 11 7F 01 11 16
>
020000
83 F1 11 7F 02 11 17
>
0902
83 F1 11 7F 09 11 1E
>
03
83 F1 11 7F 03 11 18
>
07
83 F1 11 7F 07 11 1C
>
0a
83 F1 11 7F 0A 11 1F
>
020200
83 F1 11 7F 02 11 17
>

---

 

Not so good as I first thought

 

83  = odd parity, three byte message

F1 = address of tester

11 = address of ECU

7F = negative response

xx = requested mode

11 = ??

xx = checksum

 

 

So it seems that the ECU knows what KWP2000 is but it doesn't support any of the standard modes.

 

Hi,

I don't have airbags or ABS in the car. However, there is some other controller for electronic power steering. I don't know if it can work on OBD protocol too.

Rhinoman wrote:

---

Have you got airbags or ABS? do you know if they are also connected to the same diagnostic line? 

The last response says that its KWP2000 so you should be able to read data, the response before that effectively states that KWP2000 is not supported. I have heard of this before with a 2006 GV sold in Qatar. I need to check what the other data means.

-- Edited by Rhinoman on Tuesday 12th of July 2011 06:52:48 PM

---

 

aashishkul wrote:

---

Atz
ELM327 v1.4
>
At sp 5
At sp 5
OK
>
At kw 0
At kw 0
OK
>
01 00
01 00
BUS INIT: OK
7F 01 11
>
At kw
At kw
1:E9 2:8F
>

---

Maybe this is a different ECU, the response to the 0100 message is completely different. If you can get it to respond like it did in the post above then send it the AT KW message and see what response you get.

 

Have you got airbags or ABS? do you know if they are also connected to the same diagnostic line? 

The last response says that its KWP2000 so you should be able to read data, the response before that effectively states that KWP2000 is not supported. I have heard of this before with a 2006 GV sold in Qatar. I need to check what the other data means.

-- Edited by Rhinoman on Tuesday 12th of July 2011 06:52:48 PM

Yes, I do have access to the tool. Actually, I bought it from a chinese site. If you want me to do any tests that will be helpful- I am eager to follow your directions.

Hi Rhinoman,

I was able to get hold on ELM327 based scaner and the tool was able to detect the protocol to be KWP Fast Init. It was able to show only one gauge i.e. ODB Port Voltage. No other gauges were detected. I used symbian based OBDDiag tool for this. Can you give me pointers on how other sensors could be read?

I intentionally removed inlet air temperature sensor and engine fault light came on. I tried to find the problem usng diag functionality in the software but nothing came on.

-- Edited by aashishkul on Tuesday 12th of July 2011 10:37:18 AM

My code reader returns 'link error' I think that this is good because I can now try to work out what the problem is. So far I have traced out some of the circuitry, I have a logic analyser on the processor pins and I can see that the ECU does not respond to the initialisation sequence. I am now looking at the ECUs software and trying to decipher the OBD2 code.
I have found out that the initial 5 baud data is handled by an /IRQ interrupt, this is because the processor does not support 5 baud. Next I will work through the message handler code, that will tell me what the protocol is.

Did you make any progress with this? I am currently investigating a EURO3 ECU from a 2001 Swift, The software appears to support the OBD1 protocol and it responds correctly to an OBD1 ID request but not to any data requests.

Edit: It seems to have an OBD2 port also, I'm going to connect a code reader.

-- Edited by Rhinoman on Thursday 26th of August 2010 07:38:53 PM

Hi,
Which reader works? Many people in India are complains that their reader does not work with Suzuki ECUs (however, I dont know anyone who has tried it on Wagon R).

Sorry for phrasing my question confusingly. I have not bought any reader at the moment. I intend to buy one. When I saw the schematic on the your site, I feel it's for reading suzuki protocol which is to be connected to data line on pin 9. As my car does not have any pin on no. 9 position and it appears to be ISO protocol ECU. As Suzuki has incompatibilities, I was curious to know which reader would work.

Thanks. Do you know what incompatibilities are known? Were you able to read any Suzuki ECU with OBD II protocol. I assume, the circuit you gave in one of previous message is used for communication on using Suzuki protocol and not OBD protocol.

Hi,
Thanks for your quick answer.
It's a March 2005 model of Maruti Wagon R. That was the time when cars with Euro 3 emission standard were introduced in the market and this is one of the initial one. Later on, these were called 'Bharat Stage 3' standard which is similar to Euro-3.

Following pins are populated on OBD-II style connector. Pins 4, 5, 7, 16.

Attaching pictures of the ECU label and OBD-II connector.

Can you tell which protocol it might use from this description?