This would be a an example of fully OBD2 device.
You see the difference I hope between this handheld device and a USB-OBD2 lead?
I agreed with the second half of the quote (after the comma), it is quite correct.
OBD if you mean OBD1 is entirely propriety to the vehicle manufacturer. In the case of BMW, the language is DS2, the interface is 2 wire 9600 baud moving to 1wire 9600/10400 baud moving to 1 wire 100k baud.
9141 is a messaging structure standard that all OBD2 vehicles can support, 1 wire 9600 baud, standardised message structures (start/stop/parity/checksum) and error packet handling (retransmission/acknowledges).
Chipset for E36? pre facelift - ADS. Post facelift - mixed ADS/K line. Messaging standard DS2.
Thanks for putting together a comprehensive post on this.
However, my analogue brain is still trying to process all the info and requested whether I could just ask to simplify matters.
I have an E36 1998 323i Coupe Automatic.
I have a VAGCOM USB interface and recently bought a Chinese C@rsoft 5.6 serial interface module.
I tried the VAGCOM USB interface with my engine side 20 pin socket and didn't get very far - it seemed to connect but didn't seem to read anything. I found some info about shorting pins on this interface to get it to work but then also there are posts stating doing this it still doesn't work on the 323.
I tried the serial interface with supplied software and it connected ok, gave me live readings rpm, o2, maf etc.. But when I tried to read all the modules it read some but not all.
The 2 immediate things I want to achieve are;
1. Read my ASC module - it is currently disabled and I want to get it working again.
2. Clear my brake pad wear indicator - when I bought the car I was told the brake pads/disks had been replaced but the light was on. I checked them and indeed they were new but the front NS sensor had been 'activated' and not replaced. I replaced the sensor but the warning light is still on even after trying various suggestions of pressing the brake pedal with the drivers door open and turning on the ignition. None have made it go off.
Then I would like to get another ignition key and program it in to the car (EWS II?).
I note the reference to ADS interface for 'older' cars - BUT is my car a compatible 'older' car and ideally since I already have 2 interfaces I would like to avoid buying another and achieve my goals with cleverer software or mods to my interfaces.
Shorting pins 7&8 is for cars without the 20 pin connector.
The ABS module is old and needs £85 ADS interface over factory fitted RS232.
Brake wear indicator is done by a sensor that is GNDed when pads are worn. No ECU involvement.
EWS coding can't help with, I don't know if it is possible with INPA, you may need NCS, which I can't help with.
I'm back - I have been doing further research and need further advice....
I read somewhere about about different models not having all the pins present in their 20 pin socket in the engine bay. So I decided to have a look at mine and I have the following 9 pins;
I also got out out my 'BMW Interface' and it has status leds for;
K-Line Pin 20,
K-Line Pin 17 &
L-Line Pin 15
So is this already an ADS & OBD interface?
I suppose I'm not getting access to all the modules as I do not have a Pin 17?
So what are my options?
17 is TxD2, and only for DME and EGS. There are also on 15 and 20. You must use a factory fitted serial port and STD:ADS to access your old gen modules.
|« Previous Thread | Next Thread »|