Torque

Forums

Forums

Guest  

Show or hide header
Welcome Guest, posting in this forum require registration.




Torque » Torque OBD ECU Scanner » Torque Discussion / Ideas » It's not working on my Suzuki Swift

Pages: [1]
Author Topic: It's not working on my Suzuki Swift
lfperez1982
Member
Posts: 4
Post It's not working on my Suzuki Swift
on: December 6, 2018 (GMT)

I havent been able to work with my Swift.

I currently own a Swift 2018 GL, I haven’t been able to read anything with this app, it won’t connect to the ECU.

I was checking why so I can give a bit of useful info and I found I was able to connect using this other app made for Suzukis, however is a bit simple though:

https://play.google.com/store/apps/details?id=com.malykh.szviewer.android

Since I paid for Torque and it shows a lot more info than this app I’ve figured the torque app is not supporting the ECU protocol used by Suzuki cars, i think the protocol is: SDL-KWP [or SDL-CAN (most likely its the SDL-KWP since the model of my engine is a K12)

This is the screenshot I made while using that other app: https://imgur.com/a/HDSIayM

lfperez1982
Member
Posts: 4
Post Re: It
on: December 6, 2018 (GMT)

I can’t see my previous post, I tried to make this app work with my 2018 Swift but it will not recognize the ECU, I’ve tried another app made for suzukis at the app store and it did worked with that one.

The app shows that is using a protocol SDL-KWP, SDL-CAN that doesnt seem to be supported by the Torque app. I believe the solution would be to support this protocols.

I see many others tried to used torque with suzukis and failed, I have the pro version of the app and wasnt able to make it work as well.

I’ll be happy to provide screenshots of the other app showing the readings on my auto if that provides any assistance.

The app name is “SZ Viewer A1”

Regards.

lfperez1982
Member
Posts: 4
Post Re: It
on: December 6, 2018 (GMT)

In this page they explain it fairly well:

http://www.rhinopower.org/diag/diag_main.html

I hope this is useful

lfperez1982
Member
Posts: 4
Post Re: It
on: December 6, 2018 (GMT)

I must be a terrible annoyance by now, i think I found out the issue:

SDL/KWP
From some time around 2001 Suzuki started to use a different proprietary protocol for their factory scan tools, they call this protocol SDL/KWP. SDL/KWP was implemented worldwide and for markets where OBD2 was not mandated this was the only protocol available. OBD2/EOBD models have SDL/KWP as the primary interface and OBD2/EOBD as the ‘public’ interface’. As the name suggests this protocol uses the KWP2000 protocol and uses pin 7 as specified by the J1962 specification, however there is no support for the OBD2 modes specified by J1979. Although the ECU will correctly respond to an ‘OBD2’ request with a not supported message many OBD2 scan tools incorrectly report ‘cannot connect’ or ‘no data’ rather than ‘not supported’. If an ELM tool is available then a terminal emulator programme such as Hyperterminal can be used to check the response to a Mode 1, PID0 (0100) request, a 0x7F response means that it is an OBD1 ECU. RhinoPower Ltd is working on a scan tool and software that will be compatible with KWP/SDL and OBD2 protocols using pin 7.
The Factory Service Manual for some models states the protocol to be ISO9141-2, this is because KWP2000 is a software protocol, it uses the ISO9141-2 hardware interface.

I got that from this website:

http://www.rhinopower.org/diag/diag_main.html

Again, It cant be the obd2 adapter since it works with this app:

https://play.google.com/store/apps/details?id=com.malykh.szviewer.android

Pages: [1]
WP-Forum by: Fredrik Fahlstad, Version: 2.4
Page loaded in: 0.05 seconds.

  Follow me on twitter