I have checked my database and the Maruti Swift diesel prior to 2010 is listed as using the Suzuki proprietary SDL/KWP protocol, my new tool will support this vehicle.
__________________
1984 Suzuki SJ413K pick up, 1.6 16V Baleno engine 2000 Suzuki Vitara 1.6 8V, many mods 2004 Suzuki Ignis 1.5VVT 4Grip 2006 Suzuki Jimny 1.3VVT JLX+ and many more.
That describes the OBD2 version of KWP2000, Suzuki use their own proprietary implementation of KWP2000. The early diesel may use that protocol or a FIAT version of it, I may be able to determine which one it is as I have since done quite a lot of work on this, I will run some tests. Yesterday I was able to establish two way communications with an ECU using the Suzuki protocol with my prototype KWP interface, although I still have a lot of work to do before I have some production ready software.
KWP2000 uses the ISO9141-1 physical interface (hardware) which is why it says ISO9141 in the service manual although it is KWP2000.
-- Edited by Rhinoman on Wednesday 3rd of April 2013 01:03:04 PM
__________________
1984 Suzuki SJ413K pick up, 1.6 16V Baleno engine 2000 Suzuki Vitara 1.6 8V, many mods 2004 Suzuki Ignis 1.5VVT 4Grip 2006 Suzuki Jimny 1.3VVT JLX+ and many more.
Thats not a real Tech2 and it only has prograqmming for GM vehicles. A real Tech2 can be used on GM or Suzuki but you have to use different software.You can't communicate with a Suzuki using GM software except for a few models that were sold badged as GM vehicles in the US.
__________________
1984 Suzuki SJ413K pick up, 1.6 16V Baleno engine 2000 Suzuki Vitara 1.6 8V, many mods 2004 Suzuki Ignis 1.5VVT 4Grip 2006 Suzuki Jimny 1.3VVT JLX+ and many more.
Neither of those will work. The Tech2 is a handheld scantool, not a USB interface and costs several thousand dollars. I'm not sure if you would need the Tech2 tool or the later SDT diagnostic tool.
__________________
1984 Suzuki SJ413K pick up, 1.6 16V Baleno engine 2000 Suzuki Vitara 1.6 8V, many mods 2004 Suzuki Ignis 1.5VVT 4Grip 2006 Suzuki Jimny 1.3VVT JLX+ and many more.
The ELM device has a command that allows the header information to be changed, maybe that will work. I wish that I had an ECU here that I could run some tests on. I have access to a GM scantool that should be capable of KW81 communication but I also need the specification.
Your ELM device may just have a bad solder joint, its not uncommon with Chinese electronics. If you can get it working again then it would be a good idea to disable any airbag or ABS controllers to ensure that it is the Engine ECU that is responding.
__________________
1984 Suzuki SJ413K pick up, 1.6 16V Baleno engine 2000 Suzuki Vitara 1.6 8V, many mods 2004 Suzuki Ignis 1.5VVT 4Grip 2006 Suzuki Jimny 1.3VVT JLX+ and many more.
I'm a member of GH and I've already read the post by Ripper :) .
The ELM 327 will not work OOB. The protocol is KWP2000 fast init. You need to turn off the keyword checking and you will be able to get the bus initialised. But there is some specific command to get it working (by changing the headers etc) which I don't know. I was trying and reading the ISO protocols etc and also expecting some help from Rhinoman but my ELM327 broke inbetween (lived just 2 days :( )
There are some major doubts if Maruti is using the Magnetti Marelli MM-6JF ECUs in the Swift or if they approached Bosch for the ECUs. Are you sure the ECU is a MM and not Bosch?
I too have a Diesel Swift. But haven't gotten around to fooling with it yet.
__________________
India's fastest Naturally Aspirated Baleno on a drag strip. Quarter Mile in 16.287 seconds. Time to go turbo...
The ISO14230 standard expects keywords of 8F E9, but there are a family of these that all begin with 8F, so you might be able to get the ELM327 to work as long as the KW1 is 8F. Since you have an 81, I believe you have a different protocol (KW81) that is unfortunately not supported by the ELM327.
Jim
So the problem is that the ELM327 doesn't support the particular protocol that the Suzuki uses. From what I can determine KW81 was commonly used on Vauxhall/Opel vehicles as well as FIAT vehicles, including Alfa Romeo and vehicles made by other subsidaries.
Is KW81 part of the ISO14230 standard? I will continue researching this.
__________________
1984 Suzuki SJ413K pick up, 1.6 16V Baleno engine 2000 Suzuki Vitara 1.6 8V, many mods 2004 Suzuki Ignis 1.5VVT 4Grip 2006 Suzuki Jimny 1.3VVT JLX+ and many more.
OK so it has an OBD2 port and the protocol is KWP2000 fast init. What we need to know is what the 81h, 01h response means. I will try and find my KWP2000 specification, meanwhile I have also asked ELM to comment.
__________________
1984 Suzuki SJ413K pick up, 1.6 16V Baleno engine 2000 Suzuki Vitara 1.6 8V, many mods 2004 Suzuki Ignis 1.5VVT 4Grip 2006 Suzuki Jimny 1.3VVT JLX+ and many more.
Yes connected it to the vehicle. Tried using softwares like Scantool.net, Scanmaster ELM, both shows "interface not found". Used Torque for Android, it tries to connect using various protocols but ultimately fails to connect. Tried Putty to connect to the COM port, it connected, issued ATZ command to test, various LEDs on the scanner shows some activity suggesting that the reset has been done.
For OBD2 that should be close to battery voltage, is that 4V with the interface connected or without? Its rather odd, someone else has reported having 9V on that pin which is also too low.
What voltage have you got on pin 9?
__________________
1984 Suzuki SJ413K pick up, 1.6 16V Baleno engine 2000 Suzuki Vitara 1.6 8V, many mods 2004 Suzuki Ignis 1.5VVT 4Grip 2006 Suzuki Jimny 1.3VVT JLX+ and many more.
I have a Maruti Suzuki Swift diesel 2007 which has a OBDII connector. But everybody failed to get the Scangauge working with it. The service manual says that the pin no. 7 (K line - ISO 9141) is used to communiacte with Suzuki scantool.
Also, the ECU uses 2 sockets to connect with the vehicle.
Here are are photos from the service manual.
If it uses standard ISO 9141 - I failed to understand why most of the diagnostic tools fails to connect with it.
But Maruti also uses CAN protocol for communicating with the ECM and BCM (body electrical control module). The pin no. 14 (CAN low) and pin 6 (CAN high) present in the OBDII connector is present to diagnose any problem with the BCM.
Can it be the case that when we connect the scanners and tools like ScangaugeII, the presence of output for both ISO 9141 and CAN confuses the scanner tool which then fails to connect.