I’m attempting to install the INPA 18.104.22.168 program along with EDAIBAS program EBAS32. EXE (6.4.3) dated 12/4/2002
My vehicle is a later 1999 E39 528i with two diagnostic ports (ODB2 and ADS)
Red = my changes/comments apply below:
I believe I fit this scenario:
20pin OBD1 socket Scenario 2:
You have an E38 or above that does not use the L-Line anymore and does not have pin15 of the 20pin socket is installed / wired. Those cars and all modules (ECUs) inside them behave pretty much the same as the later 16pin OBD2 socket equipped ones, and you will have full access to all modules (ECUs) using Interfaces that were intended and designed for the 16pin OBD2 socket, all you will need is an Adapter from OBD2 female to the 20pin plug.
(We recommend that you only use adapters made by us because adapters made by other manufacturers might not have all the wiring needed to work correctly for the products sold by us)
Since Interfaces that were intended and designed for the 16pin OBD2 socket can be used for those cars and they get setup as "STD:OBD" you can choose any comport number for them (which must be assigned in the obd.ini of course) and also make use of converters such as USB to serial, Express to serial, PCI to serial and PCMCIA to serial cards without any problems. I have a USB to serial (Comm.) converter (with the FTDI chip) built into the ODB2 cable connector)
Common Issues and Frequently Asked Questions:
Q: What will happen if I use an Interface that was intended and designed for the 16pin OBD2 socket with an Adapter from OBD2 female to the 20pin plug on a BMW such as the E39?
A: Everything will be fine, since all modules in this car will behave exactly the same as in a 16pin OBD2 socket equipped BMW you will be able to access all of them.
FYI = MY Red high-lighting of the text ends here or is by other means or contributing information as provided by other sources such as pasted images, etc
The item I bought from eBAY(UK) Oct 14, 2012
BMW Diagnostic USB Cable Code Reader Interface + Full Adapter Set INPA SSS DIS
Cheapest, With Free software + Installation Guide
Item Number 120987489499
ebay item_odb2 cable set.jpg
BMW Diagnostic USB Cable Code Reader Interface + Full Adapter Set INPA SSS DIS | eBay
tidbit cable description.jpg
Now to my dilemma (as I see it):
1. My efforts on my vehicle and or laptop haven’t been able to get a response to my inputs when plugged in to either ports on my car. I do see my input selections being accepted on the laptop…such as the selecting of your vehicle (for me this is the <F5> E39). Also the selecting of systems such as chassis, body, transmission, radio, CD player,etc; are accepted as inputs. However, when I push the “Enter” Key on my Panasonic Toughbook CF-19 MK3 laptop running Win xp Pro, SP2 I receive an error message “cannot compile scripts”.
I should also mention that the TWO BLACK DOTS are not BLACK. The explicit instructions state that this is essential.
I followed the very explicit installation instructions provided with my items from eBAY. And IMHO the instructions are complete and compare favorably with those provided elsewhere as well as here on this forum’s offerings.
I’d also offer this tidbit of information: The C:\INPA\BIN directory (folder) has an error file with the name “inpa.err”. This file offers the following information based on my efforts to select a subject as offered on the 1st screen. For example when selecting “E39 \communication systems \ radio.” I’ll get an error message POPUP box and an error file is also created stating:
C:\INPA\sgdat\radio.ips(455) : error I227: Can’t open file
C \INPA\sgdat\radio.ips(455) : error I014 : Undefined global symbol [inpainit]
C:\INPA\sgdat\radio.ips(455) : error I014 : Undefined global symbol [inpaexit]
My Panasonic Toughbook Laptop has both USB and a Serial Comm. Port. I have attempted to connect at both the ADS (bonnet) and the ODB2 (dash).
I have two ODB.ini files posted in the following directories/folders
One here in C:\ Windows and also C:\EDIABAS\BIN\ODI.BIN File (see comment below)
The ODB.ini file reads as follows
1. I feel there may be an error in this file…perhaps the need to see the “ODB or ADS” as hardware?
2. The folder ODI.BIN File was generated during the installation. The format is a bit unusual. Should this be corrected to C:\ODB BIN or perhaps some other variation such as C:\ODBBIN or whatever?
Looking for a little help …I’ve been to the idiots guide for INPA dummies. I obviously fall far short of the needed qualifications.
Hopefully this Nov 2012 effort might serve for some other BMW owners suffering similar pains with the newer cables being offered with built in Serial to USB converter chips by FTDI.
As part of my efforts…I had to go here FTDI Drivers
to get a driver that would see the ODB2 cable when I made my very first attempt to connect to the ODB2 port under my dash. Hopefully this isn’t part of the problem I’m having as well. Anybody knowing about this in invited to jump in.
From across the pond,
Thanks in advance,