Hi there,

I have just purchased a multi protocol OBDII scan lead ( to plug into PC ). I have plugged this into the OBD II port on my baleno (2001 1.6 AUS model), however the software cannot negotiate a compatible protocol with the ECU.

Does anyone know how to get this working ? I have read elsewhere that the Baleno uses OBD 1 behind OBD II, I have bought a spare OBD II plug that I can solder up on the lead if required.

I believe AutoTap sell a conversion lead that will make this work. I have emailled them and am now waiting for a reply.

If someone can give me info on how to make my own lead, or a supplier in Aus that would be greatly appreciated


Thanks,

Cam

Hi, I don't know why you need this as you can check error codes by shorting a link in under bonnet fuse box and counting the flashes of the check engine light.

Hi Damo,

Im always tinkering with cars. I'm an ex-mechanic, so that kinda makes me the fixit man for everyone I know. I bought this OBD II for the ease of diagnosing problems quicker, however it seems to work on everyones car except mine

Im in the process of playing around with different OBD software and toying with the idea of putting together a carputer with an interface that captures data from OBD..

Its not totally necessary at the moment, hence the reason why Im try to get away with it as cheap as possible

Thanks,

Cam

The wiring diagram shows the datalink going to pin 9 on the OBD2 connector. The OBD2 spec reserves pin 9 for the manufacturers use. Your vehicle is therefore probably not OBD2 but a Suzuki/DSM proprietary protocol.
I borrowed this pic from the TechEdge site, ignore the 8192 reference. I have logged the data transfer between the ECU and immobiliser at approx 16KHz, 8n1.

Sounds like Peugeot and many other manufacturers... This is to ensure that no one else can service your car / reset your ECU etc...etc... Has much more relevance and impact on newer multiplexed cars with body computers... Nobody but the OEM manufacturer / dealer who has the software and protocols can work on them... Yet another subtle way to ensure you have to take the care to them forever more.

I think Suzuki are much better in this respect. They at least have an OBD port that allows some fault finding without the expensive stuff. Some time back I found a reference to Mitsubishis MUT-II protocol being 16250kHz, so maybe its that. I can't find that info now. I'm trying to determine the protocol, when I do I'll publish details.

Does the port have only 3 wires running out of it? I am asking this because the pic shows only 3 pins being connected. Also, my Baleno has only 3 wires coming out of the OBD port. I was wondering if any of the connections are missing or its just the way it should be.

I think the protocol is OBD 1.5 or GM OBD. Look up wikipedia for "OBD 1.5"

The handheld diag tool called ETAS Tech 2 used by the Suzuki dealers here supports 3 protocols - GM OBDI, OBDII and GMLAN (Info from Tech 2 flyer pdf @ http://www.etas.com/en/products/1275.php ).


Pic credit: Mclaren1885 @ http://www.teambhp.com

Also, the Baleno service manual states that the Tech 1, a predecessor to Tech 2, can be used for fault code diagnosis. I cant find any documentation for this device though.

What you probably need is some thing like this -> http://www.aldlcable.com/sc/details.asp?item=aldlobd2u.

This is all "educated" guess work of course. So check out with your Suzuki dealer before you buy anything !!

What the Baleno needs is someone who can and will go to the trouble to do similar to what is now available for the many versions of Nissan factory ECU's.
Known as Nistune.

http://home.aanet.com.au/nistune/

I would love to have the time and inclination to look into this for the Baleno but unfortunately I don't.

If someone was to look into it there may well be many similarities in what needs to be done in order to do this for a Suzuki.

My Wolf ECU is in... I have made my bed and I must lie in it so to speak.

Ah only if it was that easy, I would have saved all that time upside down under the dash wiring in my Haltech.

Okk.. So you taken out the OEM ECU and put in an aftermarket one? Can you tell us whats the make of the OEM ECU? Is it a Bosh or Delphi? A pic would be nice.

The factory ECU is made by Denso.

Yeah.. supposed to be Denso 33920 - 60GB1. Not sure if its the same with the Indian Baleno though.

GM OBD1 means practically every other ECM/ECU had its own protocol. So even if we get the cable and stream the data to a PC, we will have to sit and decode it . There is free software out there which allow the data stream to be interpreted using a ECM specific data stream definition file. But couldn't find one for Suzuki so far.. Some people have decoded it for non GM cars like Lotus etc, but I guess its lot of hard work to start from scratch with no guaranteed result.

I got into the Suzuki SDL this afternoon , not on a Baleno but it should work just the same. Some details here: http://www.btinternet.com/~j_holland/pages/diag.html

I tried sending the byte sequence using share ware programs like Tuner Pro RT (http://www.tunerpro.net/) and Car Bytes. Tuner Pro does not have the option to change the baud rate beyond 8192 baud. I got some "packet error" every time I tried to send data. Car Bytes and its successor EFILive (http://www.efilive.com/download.aspx#downloads3) seems more promising.

My laptop battery died when I was about to try sending data using Car Bytes . Will try it out tonight.

What hardware are you using? You must have an interface that can communicate on pin 9, most of the commercially available scanners (ie Elmscan) can only communicate on the standard OBD2 interfaces (pin 9 is reserved for the manufacturers use). Pin 9 is also 5V and not 12V like OBD2. I used a modified microcontroller demo board for the interface. The demo board just sits between the PC and the OBD2 connector and translates the OBD 15126 baud to a standard PC baud rate (115K2).

I am not much of a DIY person . So I bought this -> http://www.aldlcable.com/sc/details.asp?item=aldlobd2u

That may work. I suspect that under the heatshrink on the USB end is a USB/TTL chip and a couple of resistors. I had problems with the voltage levels until I used a comparator on the input to shift the levels a bit.

Can you send me the program you are using? Does it communicate via one of the virtual com port.

At the moment I'm using RS232 Hex Comm Tool (http://www.rs232pro.com/).
I'm going to lash up some wiring and try to communicate with my Baleno ECU. I have the wiring from the engine bay so it looks like I have 2 of the 3 plugs. I suspect that the other plug must have the immobiliser wiring.