Inpa BMW Software is used to BMW car diagnostic, we provide free software to you install, and tell you how about install the software. During install inpa BMW software, maybe you would be encounter some problems. The following are the problems that would be happen when you install, and the solutions for the problems.
1. How can I find out if the serial interface COM1 has been taken?
There is a way to find out if the serial interface, for example COM1, has been taken, but it is
not possible to find out what programme has taken the interface.
As described in the respective sections of Chapter 3, the programmes that most often take
COM1 are HotSync for the Palm and ActiveSync for the lpack or a Nokia software. In order
to establish whether these programmes are automatically started when you start the
computer, please check your ‘Autostart’ settings. Do this by making sure that these
programmes don’t appear in the following directories:
– C:\Documents and Settings\All Users\Startmenu\Programs\Autostart\
– C:\Documents and Settings\Your QX Number\Startmenu\Programs\Autostart\
Another way to check the utilisation of COM1 is to look in the system information. The
system information can be run with the DOS command winmsd in an input prompt (Start
Run… enter winmsd OK). Here, it is important that you only run winmsd if the Ediabas
server is closed. Under the path System Summary Components Ports Serial, the
information about the active serial ports COM1, COM2, and so on will be shown if they exist.
The current value can be seen in the element “Busy”. If this value is “No”, then the interface
is free, and if it is “Yes”, then the interface has been taken by a programme. You can’t find
out what programme it is here.
2. How do I start INPA BMW Software?
Start Inpa using Inpaload.exe in C:\Inpa\Bin or alternatively C:\EC-Apps\Inpa\Bin or use
Start All Programs EDIABAS INPA ELDI NCS NFS INPA(_.IPO) to start the general
reworking programme. This corresponds to calling Inpaload.exe under
smuc0900\sg\Inpa\Bin or alternatively C:\Inpa\Bin.
3. How can I switch between OBD and ADS interfaces?
The appropriate driver must be installed for the interface that you want to use. In the
installation guide for INPA BMW software (http://smuc0900/TI-430 or http://smuc0900/TI-430 under Subjects
EDIABAS /INPA EDIABAS or INPA), you can look up how a driver is installed.
Now, you can change the interface directly in the file Ediabas.ini (C:\EDIABAS\BIN). You
only have to make the appropriate change to the line where the interface is entered.
Interface = STD:OBD, i.e the OBD interface will be used.
Interface = ADS, i.e the ADS interface will be used.
Frequently Asked Qu
For the case that OBD is being used via USB, an additional entry is necessary in OBD.ini.
See C:\EDIABAS\BIN\INI.PDF for this.
4. In which directory structure is OBD.ini saved?
If the OBD.ini file exists, then in order to not run the interface via COM1 by default (compare
to 1 i), then the OBD.ini file must be saved in the directory C:\WINDOWS\ for Windows XP
or in directory C:\WINNT\ for Windows NT up to the Ediabas Package 1.3 and as of Ediabas
Package 1.4 in directory C:\EDIABAS\BIN\. The current version of the Ediabas Package can
be seen in the files C:\EDIABAS\version.txt or C:\EDIABAS\package.pdf
5. How can I find out what interface I installed with INPA BMW Software?
To do this, you have 2 possibilities:
(1) Call Start All Programs EDIABAS INPA ELDI NCS NFS EDIABAS Tool32. In
the configuration menu, select Ediabas. There, you will find the desired information in the
(2) However, you can also check in the Ediabas.ini (C:\EDIABAS\BIN) to see what
interface you have installed. For the OBD interface, you will find the line ‘Interface =
STD:OBD’ and for the ADS Interface the line ’Interface = ADS
6. How do I find out what EDIABAS package is installed?
The version of the currently installed Ediabas package can be seen in the files
C:\EDIABAS\version.txt or C:\EDIABAS\package.pdf
7. How can I uninstall EDIABAS or INPA?
You uninstall INPA BMW Software by deleting the Ediabas and Inpa folders under C:\.
Reason: No registry entries are made during the installation.
8. How can tell if the EDIABAS server is running as a 16-bit or a 32-bit
Under Windows 95 and 98, the EDIABAS server runs as a 16-bit version. The can be
recognised by the yellow E in the task bar
Under Windows NT4 and XP, the EDIABAS server runs as a 32-bit version. This can be
recognised by the green E in the task bar.
As of 2003, there is the EDIABAS Version 6.4. This can also run as a 32-bit application
under Windows 95/98 and XP
9. What is the difference between \EDIABAS\bin\ToolSet.exe and \EDIABA\bin\Tool32.exe?
Tool32.exe is current and when it is started, the Ediabas server will start as a 32-bit
application. ToolSet.exe is an old version and is required under Windows 3.11
10. What is an SGBD and what is its connection to EDIABAS?
The controller description files (SGBD) contain the controller-specific know-how. Each SGBD
contains the order telegram of the respective controller and decodes its reply telegrams. In
the process, the raw data (bytes) is converted into directly useable variables (Data types: int,
long, real, string), i.e the error code is converted into error text.
For each controller variation, there is exactly one variation-specific SGBD.
The SGBDs are loaded and interpreted by the EDIABAS runtime system by an application
programme when the order is issued. The file name of the SGBD (without extension) is the
name with which the application programme addresses a controller variation or controller
11. Where are the individual SGBD names and their meanings given in plain English?
Click the “Show” Version List SGBD button on the ”Dienste Tool” interface. There will be a
list of all SGBDs by name with the current version number, the person responsible at BMW,
and the name of the associated controller. It is only possible to access the version list when
the network is in operation or it can be viewed at \\smuc0900\Referenz\Referenz.sgbd.
12. What is a Job?
Jobs are services that EDIABAS provides. They aren’t hard coded in EDIABAS, but are a
main component of each SGBD.
Each job has a fixed name and any number of results. Jobs are independent of each other.
There is no data exchange between jobs.
A job corresponds to a function with one complete order. It usually reads data from a
controller, analyses it and returns results that can be used directly by different applications.
A job normally works with one diagnostics telegram (multiple in exceptional cases)
13. What do SGBDs with the name _xxx mean?
SGBDs that begin with “_” (e.g. _LWS5), contain jobs that are only intended for development
(e.g.: writing the ident data). These SGBDs are not used in production or in customer service.
14. What is the group file used for?
Among other things, INPA BMW software uses group files to select the respective SGBD. The group
identifies the controller and starts the corresponding SGBD. The choice is made using the
diagnostics, and as of E65 using the variation index in addition.
The group files are located in C:\EDIABAS\ECU and have the following naming convention:
D_00xx.grp were assigned up to the E65; xx = the controller address; For example:
D_0032.grp = transmission. The name D_??????.grp is assigned after the E65 and is
legible; for example D_KLIMA.grp or D_MOTOR.grp, etc.
Updating the group files as of the E65 has changed since February 2004. The table with the
information about which controller must load which SGBD, depending on the diagnostics and
variation index, was moved from the group file to an external table. At runtime, the swappedout table C:\ECU\T_GRTB.prg is used. Therefore, it is now only necessary to update this
table and not D_??????.prg.
Additional Information for SGBD Developers:
In the file STD_GRTB.b2s, the diagnostics and variation indexes of the individual SGBDs
can be seen as well as the group file to which the respective SGBD is assigned. You can
find the file STD_GRTB.b2s on drive \smuc0900\sg\ in directory \Referenz\Ediabas\Include\.
15. How is the simulation file connected to the trace file?
There is one simulation file for each ECU. In this file are the ECU’s request and reply
telegrams. This file has the same name as the ECU description file, however it has the
ending “*.SIM” (e.g. DME31.SIM).
There is also a separate simulation file for each interface that is to be simulated. The
filename is made up of the name of the interface with the ending “*.SIM” (e.g. EDIC.SIM).
The setting of the EDIABAS configuration element called Interface will be used as the
interface name. The interface-specific return values are in the interface simulation files.
The trace file records the telegrams that have been sent (INPUT) and received (OUTPUT).
The recording of such traces can be enabled in the Tool Set in the menu bar under
“Configuration” as well as in the Ediabas.ini configuration file.
A simulation file can be automatically created from the ifh.trc trace file by using
trace2sim.exe. This tool is found in \\smuc0900\sg\Ediabas\Sim\ trace2sim.exe.
16. Why have an XBD Generator?
Before the introduction of the SGBD generator, the source code was edited with a text editor
(up to 40,000 lines). For this purpose, it was necessary to learn the special, C-based
programming language BEST/2 (description language for ECU). Manual programming is
known to be very prone to errors (copy & paste), and it is very difficult to implement the
guidelines specified in the diagnostics specification sheet part 5 as the SGBD becomes
Now, the SGBD Generator is to be used to create an SGBD by means of menu-driven input
of the data, in which the BMW guidelines are kept. This should result in less effort for the
developer, but it definitely requires a certain amount of practice in working with the SGBD
Generator. A major advantage is the automatic integration of standard ‘include’ files,
whereby new standard ‘includes’ can be added without further ado (new sample XML)
17. What are the prerequisites for remote access via TCP/IP?
EDIABAS for WIN32 makes it possible to access the diagnostics interfaces and the attached
ECUs that are connected to another PC. The prerequisite for this is a network connection of
locally and remotely controlled PCs via TCP/IP as well as a WIN32 operating system that is
supported by EDIABAS.
Applications and EDIABAS run on the local PC and the interface handler (IFH) as well as the
IFH-Server run on the PC to be remotely controlled. Before accessing the remotely
controlled PC, the IFH server IFHSRV32.EXE must be started. The remote control is
activated, or alternatively controlled using the EDIABAS configuration file EDIABAS.INI. The
EDIABAS configuration must be performed manually on both PCs.
The EDIABAS configurations TracePath and SimulationPath are not transferred from the
local PC to the remotely controlled PC, rather the respective configurations of the
EDIABAS.INI file that is on the remotely controlled PC is used.
The network protocol TCP (NetworkProtocol entry) as well as a freely selectable port
number must be given on both PCs. The port number must be identical on both PC and
must not collide with other TCP applications (1000 < port number < 30000)
18. What is the VC Tool and when is it used?
VC Tool (version check) can be used to check the versions of the files that are created
during the installation of EDIABAS. When it runs, the tool compares the files specified in the
files BMW_bin.pid, BMW_hw.pid and BMW_rest.pid with regard to their creation data and
creation time. That way, changes made incorrectly in the EDIABAS files can be detected and
After running, the VC Tool creates a text file called VC.log in which the comparison is given
with the specific results. This file is stored in the directory where the VC Tool is found
19. What is the KVP Editor?
KVP stands for continuous improvement process. The KVP Editor can be called when usingthe INPA BMW software Tool. This is mainly used in reworking and in the plant. Here, the user has thepossibility to enter his name and telephone number and then enter an error description andimprovement request and then to send the form directly to the person responsible at B