Inpa error 165

INPA BMW Tool Set Error Messages Trouble Shooting

INPA BMW cable is the strong diagnostic cable for BMW.Many client got problem with tool set error when using .Here vxdas.com share INPA BMW tool set error messages trouble shooting.Hope it can help every INPA BMW owner.

INPA BMW Tool Set Error Messages Trouble Shooting

1.EDIABAS error 100: SYS-0010: INITIALIZATION ERROR

Reason: This message comes when an SGBD has an automatic concept switch between
multiple diagnostics logs and is not connected to the controller.
Solution: Connect the controller

2.EDIABAS Error 126 (only up to Ediabas V6.4.x)

Reason: This error message appears if you start the Tool Set while an INPA BMW script is
running. This is also true the other way round. The reason for this is that only one
programme can access EDIABAS at a time.
Solution: Therefore, before you start the ToolSet, you must exit INPA!!!

3.IFH-0006: Command not accepted and IFH-0018: Initialization Error and
IFH-0038: Interface Command not implemented

Errors IFH-0006 and IFH-0018 occur if any SGBD is loaded in the Tool Set. Error IFH-0038
is generated when loading the utility file into the Tool Set.
Reason 1: The error was caused by another programme that accessed the COM1
interface. This programme could be “HotSync” for Palm or “ActiveSync”
for lpack.
Solution 1: Check the programmes that are started automatically when Windows is
started (see Chapter 4.1).
Reason 2: The COM1 interface is taken by a serial printer.
Solution 2: Uninstall the printer.
Reason 3: The infrared interface is active.
Solution 3: Deactivate the infrared interface.
Reason 4: There is no COM1 interface (COM3 instead, for example)
Solution 4a): Install the COM1 interface.
Solution 4b): Create a file with the name OBD.ini and make the following entry to set
the existing serial interface (COM3, for example)

[OBD]
Port = Com3
The file OBD.ini 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:EDIABASBIN. The current version of the Ediabas Package can be
seen in the files C:EDIABASversion.txt or C:EDIABASpackage.pdf.
Reason 5: Only for IBM notebooks: The COM1 interface is reserved for the docking
station; the COM3 interface is installed instead.
Solution 5a): see solution 4b:
Solution 5b): Set the COM3 port to COM1: In the device manager (Windows XP:
Select “Start” “Control Panel” “System” “Hardware” and then
select COM3 from the ports under the menu item “Device Manager”.
Then use the right mouse button “Properties” “Port Settings”
“Advanced” to reach the “Advanced Settings for COM3”. Set COM1 in the
COM Port Number. The message that COM1 is already taken can be
ignored in this case.
Reason 6: The old OMITEC driver wasn’t uninstalled correctly.
Solution 6: Please uninstall the old OMITEC driver with the instructions
InstructionforOMITECInstallation.pdf via the GIS server

4 IFH-0006: Command not accepted

This error occurs if a SGBD is loaded in the Tool Set when the OBD connector is being used.
Reason 1: ODB has actually been set as the interface in Ediabas.ini, but the Tool Set uses
the multi-instance with another interface, e.g. K-Line. The setting for the multiinstance and the interfaces used here is made in the file Tool32.ini in the
directory C:Windows (for Windows XP) or alternatively C:Winnt (for Windows
NT). Then, the entries in Tool32.ini, or alternatively the interface apply and not
the ones in Ediabas.ini. The use of multi-instance in the Tool Set is identified in
the title bar, for example with “Tool32:1”, for single multi-instance.
Solution 2: Enter the interface that is being used in Tool32.ini or disable multi-instance with
the entry “No”.
Reason 2: A SGBD is loaded in the Tool Set when the diagnosis protocol UDS is being
used. For UDS-SGBDs You have to use the interface OMITEC but in the
EDIABAS.ini the setting fort he interface ist „STD:OBD“.
Solution 2: Change the setting for thr interface to „interface = STD:OMITEC“ in the
EDIABAS.ini file. The OMITEC connector has to be stressed by the voltage (blue
blinking). If the connector can’t be stressed by the voltage and You want to load
the SGBD yet, You will use the simulation mode. You can activate the simulation
mode e.g. with the menue „configuration -> EDIABAS“. Notice, if you want to use
the simulation mode, a simulation file for the interface will have to exist in the
simulation path.

5 IFH-0009: ECU isn’t connected or doesn’t respond

Reason 1: In the Ediabas.ini file, the interface is set to STD:ADS. However, you have
connected an OBD connector.
Solution 1: Modify the interface setting.
Reason 2: The ignition is switched off.
Solution 2: Switch the ignition on.
Reason 3: The device manager has been used to disable the FIFO buffer for COM1.
Solution 3: In the device manager (Windows XP: Enter “Start” “Control Panel”
“System” “Hardware” “Device Manager” Ports (COM & LPT)), and select
COM1 from the ports and under the “Port Settings” tab, select “Advanced”. There
must be a check-mark by “Use FIFO buffers” and the highest possible setting
must be selected for the receive buffer.

6 SYS-0002: ECU OBJECT FILE NOT FOUND

Reason 1: If the external table T_GRTB.prg doesn’t exist in the directory C:EDIABASECU
the error message will be displayed when You execute the job
IDENT_FUNKTIONAL of a functional SGBD.
Solution 1: You have to download the external table using the ECCO Web Export and copy it
in the directory C:EDIABASECU.
Reason 2: The SGBD, which You want to start doesn’t exist in the directory
C:EDIABASECU or is an old one.
Solution 2: You have to download the SGBD using the ECCO Web Client and copy it in the
directory C:EDIABASECU

7 SYS-0005: Controller description file not found. The programme will be
aborted!

Reason 1: The SGBD is not located in the path C:EdiabasEcu.
Solution 1: Copy the SGBD into the Ecu directory.
Reason 2: This error occurs if the EcuPath in Ediabas.ini (C:EdiabasBin) isn’t set to
C:EDIABASECU.
Solution 2: Set the correct path

8 ToolSet Error: Runtime error ’372’

The following error message appears.

Reason: The old version msflxgrd.ocx exists under c:winntsystem32.
Solution: msflxgrd.ocx under c:Ediabasbin must be registered. To do this, select “Start”
“Run…” and execute regsvr32 :ediabasbinmsflxgrd.ocx in the window and
confirm with “OK“.
The following must be entered for Windows XP: “regsvr32 c:ediabasbin
msflxgrd.ocx

9 INPA BMW Tool Set Error: Run-time error ’5’ – Invalid Procedure Call

Reason: The Tool Set was started twice in a very short period of time.
Solution: Close all Tool Set processes that are running and start the Tool Set again with
only one double-click

10 INPA BMW Tool Set Problem: If an SGBD is opened, then only the hourglass
appears and the SGBD is not loaded.

Reason: An old version Richtx32.ocx exists under c:winntsystem32.
Solution: Richtx32.ocx under c:Ediabasbin must be registered. To do this, select “Start”
“Run…” and execute “regsvr32 :ediabasbinrichtx32.ocx“ in the window and
confirm with „OK“.
The following must be entered for Windows XP: „regsvr32 c:ediabasbin
richtx32.ocx

11 INPA BMW EDIABAS error 20: IFH-0010: Data transmission to control unit
disturbed

Reason 1: When using the EDIC card, the error message is issued when executing the
IDENT job.
Solution 1: Changes must be made in the file “XEDICC.ini” in the “…EdiabasBin” directory.
There, the parameters set for high-speed must be commented out and the
parameters for low-speed must be enabled:

; highspeed:
;Interface=1;
;Presc=0x01;
;SJW=0x01;
;TSEG1=0x08;
;TSEG2=0x07;

; lowspeed:
Interface=2;
Presc=0x0A;
SJW=0x02;
TSEG1=0x05;
TSEG2=0x02;
Reason 2: A SGBD is loaded in the Tool Set when the diagnosis protocol UDS is being
used. You use the interface OMITEC but the connector isn’t stressed by the
voltage (no blue blinking).
Solution 2: Connect the OMITEC wit the vehicle. The OMITEC connector has to be stressed
by the voltage (blue blinking). If the connector can’t be stressed by the voltage
and You want to load the SGBD yet, You will use the simulation mode. You can
activate the simulation mode e.g. with the menue „configuration -> EDIABAS“.
Notice, if you want to use the simulation mode, a simulation file for the interface
will have to exist in the simulation path

12 INPA BMW EDIABAS Error 134: API-0014: Result not found

The error occurs if a SGBD is loaded in the Tool Set when the diagnosis protocol UDS is
being used and the Job FS_LESEN is being executed.
Reason: You use the setting “read error like INPA”, but the Toolset can’t support the
function yet for UDS-SGBDs.
Solution: Please remove the setting “read error like INPA” in the menue “configuration ->
Toolset”.

13 INPA BMW takes too long to load an SGBD in the Tool S

Loading motor or transmission SGBDs takes an above average amount of time.
Reason: Large SGBDs often contain many and extensive tables and their information has
to be loaded.
Solution: Under the Configuration menu item in the Tool Set and then Tool Set, the
checkmark by the selection of table information must be removed

14.INPA BMW Black Windows in the Tool Set

After loading a SGBD one or more windows of the Tool Set are black windows.
Reason: The registration of the richtextbox is invalid.
Solution: You have to register the richtextbox. Execute the batch file REGSVR32.BAT in
the directory C:Ediabasbin

Finally ,for more detail information about INPA BMW ,pls click:

Professional Diagnostic Solution & Service Supplier

Website：www.vxdas.com

Follow Us To Get More Free Resource

www.facebook.com/groups/vxdas/

Share This Story, Choose Your Platform!

About the Author: Lucy

Related Posts

Всем доброго времени суток.

Еще до покупки машины купил K-DCAN кабель. Думал разберусь за несколько дней и поеду в Краснодар за покупкой уже вооружившись каким-то минимальным набором знаний.
Но (то ли из-за лени то ли по каким-то другим причинам) посмотрев, что INPA какая-то мудреная программа, а Rheingold вроде дружелюбная, но в rar архиве весит 10гб… не сложилось.

В итоге уже после покупки и повторного изучения двух мануалов было решено найти старый ноутбук и попытаться приспособить его в качестве диагностического инструмента для своей BMW.

1) установка чистой windows XP SP3 системы на диск C
2) установка драйверов с диска который шел со шнурком (решил поставить дрова с диска как более безопасный вариант. т.к по отзывам в последних FTDI драйверах стоит защита от не родного ftdi чипа)
3) — далее все по манулам
Мануал INPA
Мануал по Rheingold

на удивление все прошло ровно без единой ошибки.

Но всплыла другая проблема — батарея в ноутбуке держала 5 минут от силы, а после совсем выдала ошибку и отказалась работать.

Решил все же попробовать подключиться к машинке.
Пошел с удлинителем на паркинг — нашли мне розетку и стал ковыряться.

Не сильно понимая что где нажимать, я аккуратно потыкал в inpa, посмотрел какие-то графики,
считал ошибки по двигателю и для проверки кабеля решил их стереть (не самое умное решение)
Но позже нашел их в error history — чему был очень рад:

потом запустил Rheingold — опять ничего не понял:

понял что все это вообщем-то бесполезно тк. что смотреть и что нажимать я не понимаю совершенно,
но цель была выполнена
— кабель работает
— inpa работает (правда коробку на сколько я знаю GA6L-45R — считать у меня не получилось, кто знает помогите)
— Rheingold тоже признаки жизни подает.

Далее было решено заняться батареей ноутбука.
— заказывать — долго
— покупать в минске — дорого… 80уе за какую-то китайскую батарею жалко
— тем же вечером я вспомнил про интересную чудо схему LTC3780 — которую когда-то заказал «на всякий случай» и кажется этот случай пришел.

LTC3780 — это схема которая может повышать-понижать напряжение. При входе от 5v до 30v, на выходе можем иметь от 0.8v до 32v.
я подумал что ее можно было бы приспособить для подмены родного блока питания ноутбука.

1) разрезал провод питающий ноутбук от блока питания и замерил его показания:

2) запаял в место разреза два коннектора (у меня в наличии дома были XT60) чтобы оригинальным блоком питания можно было пользоваться при необходимости.

3) достал из старых запасов экранчик на котором показывается напряжение и ток. (можно обойтись и без него просто мультиметром убедиться что на выходе у нас 19-19.5 вольт) Экранчик стоит баксов 5-7.
Искать на ebay «Universal Red Blue LED DC 0-100V 10A Dual Digital Voltmeter Amperemeter meter»
типо такого
4) схема подключения не сложная )
2 провода на вход и 2 на выход, подстроечными резисторами(конденсаторами) подстраиваем нужное нам напряжение и ток
как-то так:

черный к минусу, красный к плюсу. К сожалению черного провода под рукой не оказалось поэтому сделал все красными.
5) оформил все в картонную коробку чтоб провода не торчали (позже распечатаю на 3д принтере нормальный компактный корпус)

6) и чудо! работает! (правда не сразу) ограничитель тока стоял на 100ма. поэтому ноут вырубался, но покрутив подстроечные(синие) резисторы или конденсаторы выставил ток максимальный на 3ампера чего ноуту вполне хватает.

— вот так за 2 часа и 15уе я решил проблему отсутствия батареи в старом ноутбуке.
и наконец-то сделал себе источник любого напряжения с ограничением по току.

LTC3780

С данной схемой можно много чего придумать. Я когда-то я ее покупал чтоб выставить светодиодам такой ток чтоб они не грелись.

Теперь пойду разбираться что за ошибки и откуда они берутся.

In this article I will share solutions of BMW INPA Errors,belows list 12 errors of BMW INPA when installing BMW INPA Software.Hope it is helpful!

Error Message 0020: Incorrect or Missing Driver. The programme will be aborted!

Conditions:

You have access to  \smuc0900sg . You are linked to this drive and would like to start an INPA script.

Reason 1: Missing Ediabas.ini file in C:Winnt.

Reason 2: You are not connected to the controller.

For developers: Simulation is not switched on in the Ediabas.ini file.

Solution:  Copy the Ediabas.ini file from C:EdiabasBin to C:Winnt.

SYS-00002: ECU variation description file not found.

The error occurs when starting an INPA script.

Reason 1: The *.prg SGBD is not located in the path C:EdiabasEcu.

Solution 1: Copy the *.prg SGBD into the ECU directory.

Reason 2: The external table T_GRTB.prg doesn’t exist in the directory C:EDIABASECU

or it is obsolete.

Solution 2: Copy the file into the ECU directory or update the external table using the ECCO

Web Client.

INPA Error: Error at Compiling Abort!

The following error message appears when starting an INPA script.

Reason 1: An INPA script with the ending IPO was started by the programme INPA.EXE

instead of by the programme INPALOAD.EXE.

Solution 1: Only start INPA scripts that end with IPO with INPALOAD.EXE.

Reason 2: The selected INPA script doesn’t exist in the C:INPASGDAT directory.

Solution 2: Update the INPA scripts using the ECCO Web Client.

Reason 3: INPA Version 5.0.1: The INPA script *.IPO can’t be started with a double-click in

the directory C:INPASGDAT*.IPO.

Solution 3: Update to Version 5.0.2.

Reason 4: INPA Version 5.0.1: The desktop link of an INPA script doesn’t work.

Solution 4: The target path must be expanded to include the INPALOAD path. To do this,

click the desktop link once with the right mouse button and go to ‘Properties’.

Expand the target path to include C:INPABININPALOAD.exe for Windows NT

(see Fig.) and C:EC-AppsINPABININPALOAD.exe for Windows XP.

Reason 5:  The file startger.ipo of the german installation and the file startus.ipo of the

english installation don’t exist in the directory INPACFGDAT.

Solution 5: Install INPA once again.

IFH-0018: Inizialisation Error – INPA doesn’t work but Toolset yet

The error occurs if a SGBD is running by INPA or CASCADE. If the same SGBD is loaded in

the Toolset it will not occure an inizialisation error.

Reason 1: The communications port COM1 doesn’ exist, but COM3 yet. The Toolset is

working without the inizialisation error, because the file OBD.ini exists in the

directory C:Ediabasbin. But the file OBD.ini has to exist in the direcory

C:Windows.

Solution 1: Copy the file OBD.ini in the directory C:Windows or create a new one. (Creation

of OBD.ini q.v. 3.3).

Reason 2:  q.v. 3.3

Solution 2: q.v. 3.3

IFH-0027: IFH not found The Programm was aborted!

The error occurs when starting INPA.

Reason 1: The setting for the interface in the configuration file Ediabas.ini doesn’t exist.

Solution 1: Please do the settings for the interface e.g.:

Interface = STD:OBD

Reason 2: The setting for the interface in the configuration file Ediabas.ini is

Interface=STD:OMITEC, but the OMITEC driver isn’t installed correctly.

Solution 2: Install the OMITEC driver with the instructions

InstructionforOMITECInstallation.pdf via the GIS server.

Reason 3: The setting for the interface in the configuration file Ediabas.ini is

Interface=OMITEC, but the correct setting is Interface=STD:OMITEC.

Solution 3: Please do the settings for the interface Interface=STD:OMITEC.

Reason 4: The old OMITEC driver wasn’t uninstalled correctly.

Solution 4: Please uninstall the old OMITEC driver with the instructions

InstructionforOMITECInstallation.pdf via the GIS server.

INPA Error: Opening Inpa – Transmission error returned a_0x2

Reason:  During the installation of Ediabas/Inpa, the configuration “Without configuration”

was selected.

Solution:  When running the installation programme, select a configuration, e.g. “BMW

Plant 1.1 Munich”.

INPA Error: Only a white screen appears when you run INPALOAD.EXE.

Reason 1: The api.dll or api32.dll file has been manually copied into the WINDOWS

directory with Windows XP and into the WINNT directory with Windows NT.

Solution 1: Delete the file api.dll or alternatively api32.dll from the WINDOWS or alternatively

the WINNT directory. The file may only exist in the directory EDIBASBIN.

Reason 2: You have installed the 32-bit version of INPA (as of Version 5.0.1) and have not

performed an update of the INPA scripts.

Solution 2: Update the INPA scripts using the ECCO Web Client.

INPA Error: DTM is no longer supported

Reason:  This error message appears if INPA.INI has been copied from Version 4.7.7 to

Version 5.x.x.

Solution:  Since it can’t be excluded that even more files from the old version have been

mixed with the new ones, the old ones must be deleted, or alternatively

reinstalled (see Chapter 5). Reinstall INPA using the Global Information Service

(GIS) https://gis.bmw.com.

INPA Error: Bridge16.exe can’t be initialised

Reason 1:  A 16-bit INPA script has been started with the 32-bit version of INPA (as

of Version 5.0.1).

Solution 1:  Update the INPA scripts using the ECCO Web Client.

Solution 2:  Convert the INPA script to the standard ‘includes’ for the 32-bit version.

To do this, contact the respective person responsible for INPA at TI-43x

(see \smuc0900sgrefReferenzReferenz.inp)

Reason 2:  A 16-bit DLL has been found, which means the developer of the INPA

script is using a 16-bit DLL.

Solution 2: The developer of the INPA script must convert the DLL to 32-bit.

Error when opening the error file abort:

Reason:  This error occurs with Windows XP because the user doesn’t have the correct

rights to change files in the directory C:INPABin.

Solution: The user needs “Power user” rights or the user needs the appropriate write rights

to the “INPA” directory.

 Compiler: File: INPADEUTSCH***.OUT not found!

Reason:  The path C:EDIABASBIN has not been set in the ‘Path’ system variable.

Solution: Set the path C:EDIABASBIN in the ‘Path’ system variable. (q.v. chapter 2.1).

(Visited 499 times, 1 visits today)