uffeg
Guest
Yes there is. It is placed below the ash tray. There is a small protection cover in front of the connector.
From memory - On Board Diagnostics socket.Originally posted by ozzy
I also want to know..............
Serial port into the ECU of sorts...
Bill
Oh right! (didn't know wtf an OBD was either )
In that case ~ it's in the centre console storage area beneath the ashtray. Behind a plastic cover..
)In that case ~ it's in the centre console storage area beneath the ashtray. Behind a plastic cover..
Thanks!!
yeap, OBD = On Board Diagnostics
The dealer uses this connector for pluging the diagnostic computer (VAG1551) and get all errors from the ECU among other things like resetting the check engine light, programming your alarm, etc ...
There are some programs that allow a laptop (or a palm) with a cheap hardware interface to emulate the VAG1551. Besides getting the diagnotic codes, there's additional data can also be obtained like: speed, rpms, requested boost, actual boost, coolant temperature, o2 sensors voltage, misfires, air flow, etc ...
I have built the interface and found a free program for my palm, I'll try it and report here if i was succesful getting the Palm to talk to the ECU.
For this information to be really useful I need the service manual , there are generic diagnostic codes but without the manual this is more of a curiosity than anything else.
yeap, OBD = On Board Diagnostics
The dealer uses this connector for pluging the diagnostic computer (VAG1551) and get all errors from the ECU among other things like resetting the check engine light, programming your alarm, etc ...
There are some programs that allow a laptop (or a palm) with a cheap hardware interface to emulate the VAG1551. Besides getting the diagnotic codes, there's additional data can also be obtained like: speed, rpms, requested boost, actual boost, coolant temperature, o2 sensors voltage, misfires, air flow, etc ...
I have built the interface and found a free program for my palm, I'll try it and report here if i was succesful getting the Palm to talk to the ECU.
For this information to be really useful I need the service manual , there are generic diagnostic codes but without the manual this is more of a curiosity than anything else.
VAG emulation software
You can download a shareware programme which can be fully activated when ordering it.
Available from http://www.ross-tech.com
Its a good piece of kit.
Bill
You can download a shareware programme which can be fully activated when ordering it.
Available from http://www.ross-tech.com
Its a good piece of kit.
Bill
Amgtorre,
Where did you get the software for the palm ?, i havent found anything but pc software to do it!
Where did you get the software for the palm ?, i havent found anything but pc software to do it!
OBD scanner Palm software :
http://www.auterraweb.com/lib/auterra/ScanTool20.prc
Due to size constrains I can't post the view of the diagram in jpg format.
The interface diagram is in postscript format.
there are 2 ways to see this:
1. send the file to a postscript printer
2. get postscript viewer installed in your pc, I installed GSview 4.1 - PostScript previewer. Needs Ghostscript 7. from http://www.ghostgum.com.au/ . With this software you can print postscript files on non-postscript printers.
The OBD connector pinout can be seen at: http://www.obdii.com/connector.html
The interface I built does not use the L-line portion, only the K-line. L-line was used in OBD I cars (ie: my old 1994 Golf) to manually get the diagnostic codes thru the check engine light.
The interface diagram is courtesy of Steffen Koehler a nice guy I met through newsgroup rec.autos.makers.vw.watercooled a few years back.
This interface has been tested with Steffen owns software which supports OBDI cars, (pre 1996 ) the hardware interface is the same at the electrical signal levels, the actual protocol, transmition speeds have changed to OBD II (post 1996 cars).
This harware interface is assumed to work with the ISO9141 OBD (used by VAG cars), this means it only uses voltage levels to transmit digital 1s or 0s. Other manufacturers use pulse wide modulation, and another kind I can't recall right now (more info on http://www.obdii.com )
W a r n i n g:
There is +12V battery voltage and ground present at the OBD connector, these plus the signals come from/through the ECU, you run the risk of at least blowing a fuse, So.... unless you know what you're doing leave it alone. Otherwise.. enjoy!
http://www.auterraweb.com/lib/auterra/ScanTool20.prc
Due to size constrains I can't post the view of the diagram in jpg format.
The interface diagram is in postscript format.
there are 2 ways to see this:
1. send the file to a postscript printer
2. get postscript viewer installed in your pc, I installed GSview 4.1 - PostScript previewer. Needs Ghostscript 7. from http://www.ghostgum.com.au/ . With this software you can print postscript files on non-postscript printers.
The OBD connector pinout can be seen at: http://www.obdii.com/connector.html
The interface I built does not use the L-line portion, only the K-line. L-line was used in OBD I cars (ie: my old 1994 Golf) to manually get the diagnostic codes thru the check engine light.
The interface diagram is courtesy of Steffen Koehler a nice guy I met through newsgroup rec.autos.makers.vw.watercooled a few years back.
This interface has been tested with Steffen owns software which supports OBDI cars, (pre 1996 ) the hardware interface is the same at the electrical signal levels, the actual protocol, transmition speeds have changed to OBD II (post 1996 cars).
This harware interface is assumed to work with the ISO9141 OBD (used by VAG cars), this means it only uses voltage levels to transmit digital 1s or 0s. Other manufacturers use pulse wide modulation, and another kind I can't recall right now (more info on http://www.obdii.com )
W a r n i n g:
There is +12V battery voltage and ground present at the OBD connector, these plus the signals come from/through the ECU, you run the risk of at least blowing a fuse, So.... unless you know what you're doing leave it alone. Otherwise.. enjoy!
Have a look at: www.planetfall.com/~jeff/obdii/
Plenty of information on the interface including PCB and Circuits (in PDF format)
Plenty of information on the interface including PCB and Circuits (in PDF format)
>>Have a look at: www.planetfall.com/~jeff/obdii/
>>Plenty of information on the interface including PCB and circuits (in PDF format)
Excellent !!!
If the interface I have doesn't work we another one to try ...
If I were going to build one from scratch I'll build the one from Jeff Noxon, the optocoupler requires less components than the Max232 and for sure provides better isolation between the car and the pc.
another PC OBD freeware: http://www.obd-2.com/ve101u.zip
>>Plenty of information on the interface including PCB and circuits (in PDF format)
Excellent !!!
If the interface I have doesn't work we another one to try ...
If I were going to build one from scratch I'll build the one from Jeff Noxon, the optocoupler requires less components than the Max232 and for sure provides better isolation between the car and the pc.
another PC OBD freeware: http://www.obd-2.com/ve101u.zip
I've just built the one from www.andywhittaker.com/ecu/obdii_hardware.htm
Just bought the bare board and connector and built it from parts I have to hand. It's uses the opto-coupler design and works very well.
Just bought the bare board and connector and built it from parts I have to hand. It's uses the opto-coupler design and works very well.
There seems to be loads of different ways of getting these cables to connect to the OBD.
Just keeping things simple ... where is the cheapest place I can buy one from ready made. I take it then all I need is to plug it into my COM port on my laptop and get some software ???
Also is the Golf connector the same ?
Just keeping things simple ... where is the cheapest place I can buy one from ready made. I take it then all I need is to plug it into my COM port on my laptop and get some software ???
Also is the Golf connector the same ?
I tried the above software with the interface I posted in the postcript file and it did not connect to the ECU. I'm going to build the one with the optocoupler. I'll post what happens.
Similar threads
