So is it a config issue then? What is the best software for this interface?
I've got an old laptop with proper hardware serial port and I've just found a larger hd to replace its massive original 6gb disk
I'll have a go at installing other interface software this week.
Or can anyone advise me. I have a UK 320i six cylinder M52 E36 August 1995 build. What interface do I need to enable me to read all modules and what langage is the car using to comunicate with the software and what software should I use?
Thanks for any help.
Your E36 is at a real awkward age to get a straight answer for, if it was 1996 I'd tell you to get a vagcom lead for £10 and the BMW 20-16 pin OBD2 adapter and to use Inpa. There's a bit more information here BMW and INPA success E39/E46 onwards.
The ADS interface which should give full connectivity is this one BMW INPA OBD & ADS Compatible Interface but it requires a laptop with a serial port (it may be available cheaper it was my first google result!).
To be honest, I'd probably take the gamble and try the vagcom lead and BMW 20 pin adapter, but remember it is a bit of a risk if it'll work or not. This post suggests it might INPA/DIS problem 1995 e36 328i. If it works it'll give you access to the ecu but not all modules. From memory you'll get ECU, airbag, abs but not the instrument cluster.
95 build is gonna be full ADS a vagcom and pacman adaptor may connect to some of it but not all of it a serial 16 pin and pacman adaptor with inpa set to ADS will deffo connect to some of the more important bits, but also then if itsa pre none EWS car you may have problems with INPA which likes to talk to an EWS before it will proceed....
Hi, I already have a bmw 20 pin to obd cable : - http://www.ebay.co.uk/itm/2909548225...84.m1497.l2649
Does anybody knows where to find a reliable ads-obd2 interface?
Ive read about inpa and ediabas, for a 11/96 328i 2d with asc can you give some advice about best soft?
I find it a little ironic that i found this not technical enough.
I was hoping for a little more detail to design a cheap and easy ADS physical interface with - i gather it will need inverting to speak to the serial port on my latitude e6400 docking station.
I saw you say about routing the k line to the l line - the k line is half duplex bidirectional is it not, and the l line is full duplex, so does this mean the dtr routed the tx and rx to the l line tx and rx when dtr is high (or is it low?) and then routes the k line to both terminals when the dtr is in the other logic level, such that anything leaving the rs232 tx is seen at the rx and the k line, and anything seen by the k line is seen at both tx and rx??
What are the signal levels - what sort of current is required by the 2 busses - can rs232 drive it or does it need amplifying, and can the car drive rs232 from both lines or does that need current amplifying?
Ideally i would like to knock up a logic diagram and build from 40xx cmos rather than the rather delicate BJT circuit i have seen.
IF i can do if you can expect ~$20 ADS converters, the circuit sounds like it should only be a couple of chips, $5 or so to knock up.
OK, i think i got it - feedback always good - im a bit tired so may have the wrong lead off DTR notted, but i think i got it right, the logic is based off the freeADS
Uses a single chip - a 4502 which is a tri-state output hex inverter along with four pull up resistors. ridiculously simple. As always optoisolators would be wise - you would want four -= one for each of the lines on the computer side (none of them are bi-directional so much simpler) but as it stands you should be able to make it for under a fiver a tenner with the optos, in manufacturing quantities they should be about $2 to make, maybe 4 with the optos.
|« Previous Thread | Next Thread »|