The later method is mainly used on earlier models. Insertion of a jumper in the monitor coupler or the insertion of a fuse in the 'Diag' slot in the fuse box. The most basic form of diagnostic interface fitted to a Suzuki flashes fault codes on the Check Engine Light when the interface is activated. With an annual licence fee being charged. The Suzuki specifications have not been made public but are available to aftermarket scan tool manufacturers Tech2 and SDT use this propritary/OBD1 interface. The official, and hugely expensive, factory scan tools, the Tech1, The primary interface on Suzuki ECUs is a proprietary format (generally still referred to as OBD1) and where an OBD2 or EOBD interface is alsoįitted, to meet legislative requirement, it is limited to the legal minimum.
#Conector aldl free#
Of course manufacturers were free to adopt OBD2 or EOBDīefore the mandated dates so legislation dates only mean that vehicles introduced after those dates will meet the relevant specification,īefore those dates they may be OBD2, EOBD or proprietary. Japan adopted EOBD in 2004, AustraliaĪdopted EOBD in 2006 and India is currently scheduled to adopt it in 2013. In the US OBD2 was mandated from 1996 onwards, in Europe legislation required the adoption of EOBD (mostly compatible with OBD2)įrom 2001 for new petrol engined passenger vehicles through to 2004 for existing models of diesel engined passenger vehicles. The terms 'OBD1' and 'OBD2' are actually very specific to the US but have achieved common usage worldwide. The majority of Suzuki ECUs from 1991 onwards were fitted withĪ diagnostic link, a notable exception being the Swift GTi models. Most manufacturers did fit diagnostic interfaces and these were usually proprietary. Prior to the adoption of OBD2 some countries had a mandatory requirement for On Board Diagnostics, others didn't. Make everything neat with heat-shrink tubing.Suzuki (and Geo badged Suzuki) ECU diagnostics can be categorised into two very broad types, usually refered to as 'OBD1' and 'OBD2'. Cut off the other side of it, and connect to your $7.66 USB to ALDL adapter. But this proves that an ALDL-interface cable can be built for $7.66 including shipping.Įxtra credit: For an additional $5, order. Step #10: Start engine to get some more meaningful data, but you should be getting data flow just from being in "RUN" and trying the "Force Data" function.ĭisclaimer: This worked on my 1992 LH0-engined car. Press "Force Data" button in Freescan screen if data does not transmit automatically. You should get at least a partial data flow when the key is in the RUN position.
#Conector aldl serial#
If not, then you've done something wrong earlier.Īlternatively, use a terminal emulator such as PuTTY, set into serial mode, with the appropriate (virtual) com port (mine was COM4), and the baud rate set to 8192. Look at the LEDs on the USB connector, to make sure there's some data flow. Set e-brake (to inhibit DRL's draining your battery and just as basic protection since you'll probably wanna sit in the passenger seat to mess with a laptop), turn key to run position. Also, make sure you select "Interact" mode. Select the appropriate COM port (showed up as COM4 for my laptop), and select "GM 410B" as the ECU in the software.
#Conector aldl install#
Wire the Black connector (GND) to the "A" connector on the ALDL block.Ĭonnect USB to laptop, let Windows install the FTDI drivers. Wire the combined TXD and RXD pins to the "M" connector on the ALDL block Wire the TXD and RXD pins together, Green and Yellow. Many Arduino-targeted cables use 3.3V, which may not be adequate for the TX pin to the 5V logic used in the ECU!) (must be this one, with the FTDI chip to support 8192 baud, and must use 5V TTL levels. Okay everyone, as a public service, I thought I'd do a bit of a write-up on how hooked up to my 1992 LH0-engined car with a <$8 USB cable and no messing around with MAX232's, transistors, resistors, or even soldering.
0 kommentar(er)
