Ifh 0018 initialization error inpa ошибка

[Проблема решена, решение описано ниже]

Доброго времени суток уважаемые драйвовчане!
Обращаюсь к вам с мольбами помощи.

p.s. машину уже диагностировали, бобром через мой 20pin OBD1.
p.s.2 считывать пытаюсь E46 / Кузов / Подушка безопасности.

Собственно заказал я «чудесные» шнурки из всеми любимого Aliexpress.
( нравиться мне это дело )

Нашел замечательную статью dundukya — №12: Установка BMW Standard Tools 2.12 (INPA 5.0.6, EDIABAS 7.3, NCSExpert 4.0.1) для OBD1 + OBD2 (K-line) и OBD2 (DCAN).

Проделал всё тоже самое, позаимствовал у друга планшет на Win10 32bit.
Проблем с установкой софта не было, проблемы начались при подключении.

Первым, наперво схватил ошибку: IFH-0003: DATATRANSMISSION TO INTERFACE DISTURBED

Решилась (насколько я думаю) она путём выбора другого порта, так как 1 уже был кем-то или чем-то занят.
Сменил порт в диспетчере устройств на переходнике и изменил порт в obd.ini папочке Windows.

Подумал, ну всё, сейчас то я НАДИАГНОСТИРУЮ111
Вставляем ключ, заводимся.
БОЛТ

При попытке считать блок подушек, следующая ошибка — IFH-0018 INITIALIZATION ERROR

Почитав статью: №12: Установка BMW Standard Tools 2.12 (INPA 5.0.6, EDIABAS 7.3, NCSExpert 4.0.1) для OBD1 + OBD2 (K-line) и OBD2 (DCAN).

Есть 4 возможные причины:

1. Проверил, изображение ниже
— проверяем настройки порта и их соотвествие obd.ini
2. Заведена
— проверяем, заведена ли машина. на заглушенной, даже с повернутым ключомв положение зажигания, на некоторых блоках может выскакивать эта ошибка.
3. Разобрал, визуально всё ок. Зеленая плата с переключателем, фото ниже.
— возможно шнурок требует модификации или неисправен, что случается очень часто, так как это дешевый китай. Раскручиваем корпус и смотрим на начинку, в частности контакты 7 и 8. В зависимости от года выпуска машины их нужно/не нужно замыкать.
4. Не пробовал? Убрать переключатель? Если да, то как лучше? просто контакты выдернуть?
НО: При переключении ошибка меняется, то есть переключатель работает.

— в последнее время популярны шнурки с встроенными переключателями, чтобы замыкать-размыкать 7 и 8 пины. Переключатели часто бывают нерабочие (легко проверить мультиметром), в таком случае вы тоже получите похожие ошибки. Чтобы решить проблему, выключатель нужно убрать, и если нужно замкнуть контакты, сделать это самостоятельно.

Решение проблемы:

Всё получилось.
C:\EDIABAS\Bin есть тоже obd.ini в котором аналогично нужно менять КОМ Порт (если не стандартный 1), указал там такой же как и в папке Windows и всё заработало.

На замкнутом контакте 7+8 само собой.

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/

Working solution to INPA EDIABAS  INITIALIZATION ERROR.

Error message 1:

ApiCheckJobStatus: Error #95
SYS-0005: OBJECT FILE NOT FOUND
API job error or no such result !

Ediabas error #95 means that some INPA script (.IPO file) is requesting a result from some .prg file that does not exist. This is most probably caused by a missing .prg file.

Error message 2:

2.5 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 : 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:\Ediabas\bin\. But the file OBD.ini has to exist in the direcory

C:\Windows.

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

of OBD.ini q.v. 3.3).

Error message 3:

Edibas error:

ApiCheckJobStatus: Error #28

IFH-0018: INITIALIZATION ERROR.

API job error or no such result!

Varuantenkonrolle:

IFH-0018: INITIALIZATION ERROR. Das Programm wird abgebrochen!

Reason: Ediabas is attempting to access port COM1. However, the port doesn’t exist, or it

has been taken by another programme (e.g. HotSync from Palm, infrared).

Solution: Install a COM1 interface or free it.

Real feedback on INPA initialization error with solution above:

Yesterday my BMW INPA K+DCAN software showed error: INITIALIZATION ERROR. killed several hours with this knock-off. The car i connected to is BMW 2011 – e92 – LCI.

To set the COM to 1, obd.ini is also COM1.

I seek help from forums and one of them provided a solution to the problem:
(solution offered by an experienced user with K+Dcan cable)

Modify the EDIBAS.INI as follows
RemoteHost
; Description : server address/name
; Default = –
; RemoteHost = Desmo16
Desmo16 being my computer’s name (note that this must be maximum 8 chars)
and
Port
; Description : IP communication port
; Value : 1000 < port < 3000
;
; Spezialfall OP(P)S /ICOM:
; Value : 6801 ;OBD-Treiber (CAN)
; Value : 6802 ;Most-Treiber
;
; Default = –
; Port = 6801
OBD2 notice that you should be sure port is 6801 as mine was 3000. It worked like a charm after i made these mods.