BMW ICOM NEXT | BMW NBT EVO FSC Codes | BMW NBT & CIC FSC Codes | BMW Rheingold , ISTA/P, KSD, ETK remote installation | BMW STANDARD TOOLS remote installation | BMW ESYS remote installation
Go Back   BMW forum. Diagnostics, coding, programming, repair BMW vehicles. > BMWelcome > BMW coding and programming > BMW GT1, OPS/OPPS, INPA

Reply
 
LinkBack Thread Tools Display Modes
  #1  
Old 04-13-2013, 01:28 PM
Junior Member
 
Join Date: Apr 2013
Location: Switzerland
Car: Z4 M Roadster (2006)
Posts: 4
Thanks: 0
Thanked 0 Times in 0 Posts
Default INPA 5.0.2 error IFH-003

Hi all,

I installed the INPA 5.0.2 on both my laptop (running Windows 7 starter 32 bit) and on my desktop (running Windows 8 64 bit).

Both installations went well (followed the installations instructions). When I start the INPALOAD.exe the program starts OK, I select the model (E85) and want to read a module, I get this screen:



The error is IFH-003 and appears even if the car is connected to the laptop, ignition on.

The EDIABAS.INI file looks like this:

;================================================= ============================
;EDIABAS 6.4.7 Configuration
[Configuration]
;================================================= ============================

;-----------------------------------------------------------------------------
; EcuPath
; Description : ECU file path
; Default = .
EcuPath =C:\EDIABAS\ECU

;-----------------------------------------------------------------------------
; SimulationPath
; Description : Simulation file path
; Default = .
SimulationPath =C:\EDIABAS\SIMULATION

;-----------------------------------------------------------------------------
; TracePath
; Description : Trace file path
; Default = .
TracePath =C:\EDIABAS\TRACE

;-----------------------------------------------------------------------------
; CodeMapping
; Description : Character mapping file path
; Default = .
;CodeMapping = C:\EDIABAS\BIN\ansi2oem.tab

;-----------------------------------------------------------------------------
; TraceSize
; Description : Maximum size of each trace file [KB]
; Value : 0..32767
; Default = 1024
TraceSize = 32767

;-----------------------------------------------------------------------------
; ApiTrace
; Description : Enable/Disable API/User trace
; Value : 0 = Trace disabled
; 1 = User trace
; 2 = User trace + time stamp
; 3 = User trace + time stamp + process id (Win32)
; 4 = Function trace
; 5 = Function trace + time stamp
; 6 = Function trace + time stamp + timing
; 7 = Function trace + time stamp + timing + process id (Win32)
; Default = 0
ApiTrace =0

;-----------------------------------------------------------------------------
; IfhTrace
; Description : Enable/Disable IFH trace
; Value : 0 = Trace disabled
; 1 = User trace
; 2 = User trace + interface
; 3 = User trace + interface + time stamp
; Default = 0
IfhTrace =0

;-----------------------------------------------------------------------------
; IfhnTrace
; Description : Enable/Disable IFH network trace (with XREMOTE)
; Value : 0 = Trace disabled
; 1 = User trace
; 2 = User trace + interface
; 3 = User trace + interface + time stamp
; Default = 0
;IfhnTrace = 0

;-----------------------------------------------------------------------------
; SystemTraceSys
; Description : Enable/Disable system trace (runtime system)
; Value : 0 = Trace disabled
; Trace levels 1..7
; Default = 0
SystemTraceSys = 0

;-----------------------------------------------------------------------------
; SystemTraceBip
; Description : Enable/Disable BIP trace (runtime system)
; Value : 0 = Trace disabled
; Trace levels 1..7
; Default = 0
SystemTraceBip = 0

;-----------------------------------------------------------------------------
; SystemTraceIfh
; Description : Enable/Disable IFH system trace
; Value : 0 = Trace disabled
; Trace levels 1..7
; Default = 0
SystemTraceIfh = 0

;-----------------------------------------------------------------------------
; SystemTraceNet
; Description : Enable/Disable network trace
; Value : 0 = Trace disabled
; Trace levels 1..7
; Default = 0
SystemTraceNet = 0

;-----------------------------------------------------------------------------
; BipDebugLevel
; Description : BIP debug level of ECU files
; Value : 0..32767
; Default = 0
BipDebugLevel = 0

;-----------------------------------------------------------------------------
; UbattHandling
; Description : Ubatt ON/OFF handling
; Value : 0 = Ubatt ON/OFF: No EDIABAS error
; 1 = Ubatt ON/OFF: EDIABAS error
; Default = 1
UbattHandling = 0

;-----------------------------------------------------------------------------
; IgnitionHandling
; Description : Ignition ON/OFF handling
; Value : 0 = Ignition ON/OFF: No EDIABAS error
; 1 = Ignition ON/OFF: EDIABAS error
; Default = 1
IgnitionHandling = 0

;-----------------------------------------------------------------------------
; ClampHandling
; Description : automatic check of clamps for Ubatt and Ignition
; Value : 0 = no automatic clamp check with send_and_receive
; 1 = automatic clamp check with send_and_receive
; Default = 1
;ClampHandling = 1

;-----------------------------------------------------------------------------
; TaskPriority
; Description : EDIABAS process/thread priority (only Win32/16)
; Value : 0 = Optimal EDIABAS performance = 8
; 1 = Minimal EDIABAS performance
; ..
; 10 = Maximal EDIABAS performance
; Default = 0
TaskPriority = 0

;-----------------------------------------------------------------------------
; LoadWin32
; Description : Map EDIABAS Win16 calls to EDIABAS Win32
; Value : 0 = Win16/32 Mapping disabled (Win16-->Win16)
; 1 = Win16/32 Mapping enabled (Win16-->Win32)
; Default = 0 for Windows 9x/Me
; Default = 1 for Windows NT4/2000/XP
;LoadWin32 = 0

;-----------------------------------------------------------------------------
; SystemResults
; Description : Enable/Disable system results (ubatt/ignition/jobstatus)
; Value : 0 = Disable system results
; 1 = Enable system results
; Default = 1
SystemResults = 1

;-----------------------------------------------------------------------------
; RetryComm
; Description : Repeat failed communication automatically (1x)
; Value : 0 = Retry disabled
; 1 = Retry enabled (1x)
; Default = 1
RetryComm = 1

;-----------------------------------------------------------------------------
; Simulation
; Description : Enable/Disable ECU simulation
; Value : 0 = Simulation disabled
; 1 = Simulation enabled
; Default = 0
Simulation =0

;-----------------------------------------------------------------------------
; Interface
; Description : Connected diagnosis interface
; Default = STD:OBD

Interface =STD:OBD

; Additional information (in German) :
; Bitte beachten: Der HW-Treiber fuer das Interface muss installiert sein!

; Interface = STD:OBD
; Beschreibung : Serieller Pegelwandler (Nachfolger von ADS / Anschluss an OBD-Dose)
; Installation : \EDIABAS\HARDWARE\OBD\ODBSETUP (nur noetig fuer WIN NT4, WIN 2000, WIN XP)
; INI-Datei : Suchreihenfolge analog zu EDIABAS.ini
; Unterstuetzung : WIN3.xx : Nein
; WIN95,98 16-Bit : Ja
; WIN95,98 32-Bit : Ja
; WIN NT 4.0 : Ja
; WIN XP : Ja

; Interface = STD:FUNK
; Beschreibung : Funk-Diagnose Interface MDA von Fa. Siemens
; Installation : keine
; INI-Datei : FUNK.INI
; Unterstuetzung : WIN95,98 16-Bit : Ja
; WIN95,98 32-Bit : Ja
; WIN NT 4.0 : Ja
; WIN XP : Ja

; Interface = ADS
; Beschreibung : Serieller Pegelwandler (Anschluss an Diagnose-Dose)
; Installation : \EDIABAS\HARDWARE\ADS\ADS32\ADSSETUP (nur fuer WinNT4 noetig)
; INI-Datei : keine
; Unterstuetzung : WIN95,98 16-Bit : Ja
; WIN95,98 32-Bit : Nein
; WIN NT 4.0 : Ja
; WIN XP : Ja

; Interface = KBUS
; Beschreibung : Serieller Pegelwandler (Anschluss direkt an K-Bus oder I-Bus)
; Installation : \EDIABAS\HARDWARE\ADS\ADS32\ADSSETUP (nur fuer WinNT4 noetig)
; INI-Datei : keine
; Unterstuetzung : WIN95,98 16-Bit : Ja
; WIN95,98 32-Bit : Nein
; WIN NT 4.0 : Ja
; WIN XP : Ja

; Interface = EDIC
; Beschreibung : Serielles , PCMCIA , PC-Card Interface von Fa. Softing
; Installation : \EDIABAS\HARDWARE\EDIC\SETUP.EXE
; INI-Datei : EDICFW.INI, EDICHW.INI
; Unterstuetzung : WIN95,98 16-Bit : Ja
; WIN95,98 32-Bit : Ja
; WIN NT 4.0 : Ja
; WIN XP : Ja

; Interface = EDICC
; Beschreibung : EDIC-Card C oder EDIC-Card 2 CAN-Interface von Fa. Softing
; Installation : \EDIABAS\HARDWARE\EDIC\SETUP.EXE
; INI-Datei : XEDICC.INI
; Unterstuetzung : WIN95,98 16-Bit : Ja
; WIN95,98 32-Bit : Ja
; WIN NT 4.0 : Ja
; WIN XP : Ja

; Interface = STD:CAN
; Beschreibung : PCMCIA CAN-Interface CanCardX/XL von Fa. Vector
; Installation : keine (ausser Installation der CAN-Karte)
; INI-Datei : CAN32.INI
; Unterstuetzung : WIN95,98 16-Bit : Nein
; WIN95,98 32-Bit : Nein
; WIN NT 4.0 : Ja
; WIN XP : Ja
; Ansprechpartner: Hr. Jusko
; Telefon : +49-(0)89/382-35891 (Hotline)
; email : [Only for registered users... ] (Hotline)

; Interface = STD:ADS4MOST
; Beschreibung : Most-Interfaces von Fa. Oasis
; Installation : keine (ausser Installation der Oasis-Karte)
; INI-Datei : ADS4MOST.INI
; Unterstuetzung : WIN95,98 16-Bit : ?
; WIN95,98 32-Bit : ?
; WIN NT 4.0 : Ja
; WIN XP : Ja
; Ansprechpart.: Hr. Rowedder
; Telefon : 089 / 382-29159
; email : [Only for registered users... ]

; Interface = REMOTE
; Beschreibung : Anbindung eines EDIABAS-Interfaces über TCP/IP
; Installation : Anpassung der Einträge in [TCP] auf beiden Seiten (ins.: RemoteHost, Port)
; INI-Datei : keine
; Unterstuetzung : WIN95,98 16-Bit : Nein
; WIN95,98 32-Bit : Ja
; WIN NT 4.0, XP : Ja
; WIN XP : Ja
; Sonderfall : Interface OPPS
; Ansprechpart.: Hr. Rowedder
; Telefon : 089 / 382-29159
; email : [Only for registered users... ]

; Interface = REMOTE:name
; Beschreibung : Anbindung eines EDIABAS-Interfaces über TCP/IP
; Installation : Anpassung der Einträge in [TCP] auf beiden Seiten (ins.: RemoteHost, Port)
; INI-Datei : REMOTE.INI (insbesondere für Parallelbetrieb notwendig)
; In REMOTE.INI stehen unter [name] spezif. Einstellungen(z.B.: RemoteHost, Port)
; Unterstuetzung : WIN95,98 16-Bit : Nein
; WIN95,98 32-Bit : Ja
; WIN NT 4.0, XP : Ja
; WIN XP : Ja
; Sonderfall : Interface OPPS
; Ansprechpart.: Hr. Rowedder
; Telefon : 089 / 382-29159
; email : [Only for registered users... ]

;-----------------------------------------------------------------------------
; NetworkProtocol
; Description : Network protocol
; Default =
NetworkProtocol = TCP

;================================================= ============================
;TCP/IP Configuration
[TCP]
;================================================= ============================

;-----------------------------------------------------------------------------
; RemoteHost
; Description : server address/name
; Default =
RemoteHost =OPPS

;-----------------------------------------------------------------------------
; Port
; Description : IP communication port
; Value : 1000 < port < 30000
; Default =
Port = 3000

;-----------------------------------------------------------------------------
;TimeoutConnect
; Description : Timeout for establishing the connection
; Default = 5000
TimeoutConnect = 2000

;-----------------------------------------------------------------------------
;TimeoutReceive
; Description : Timeout for receiving a message
; Default = 5000
TimeoutReceive = 2000

;-----------------------------------------------------------------------------
;TimeoutFunction
; Description : Timeout for a long function
; Default = 59000
TimeoutFunction = 10000

;-----------------------------------------------------------------------------
;DisconnectOnApiEnd
; Description : Enable/Disable Disconnection with function call ApiEnd
; Value : 0 = Disconnection disabled
; 1 = Disconnection enabled
; Default = 0
;DisconnectOnApiEnd = 1

;-----------------------------------------------------------------------------
;InitCmd<n>
; Description : Initialization command <n> (normally for OPPS)
; Default =
;InitCmd0 = FE,04,00,03,01
;InitCmd1 = FD,05,00,03,01

;================================================= ============================
; End Of File EDIABAS.ini
;================================================= ============================









The OBD.INI file looks like this and is saved in the C:\Windows folder



[OBD]
Port=Com1
Hardware=USB
RETRY=OFF
TRACELEVEL=0
;Tracelevel=0xFFFFFFFF
;Tracelevel=0xFFFFFFFF
;Tracelevel=0xF0000000
;Tracelevel=0x0000FFFF
; Bit 0 = Funktionsaufruf
; Bit 1 = io Ergebnis
; Bit 2 = nio Ergebnis
; Bit 3 = Detailinfos
; Nibble 0 = readchar_wait
; Nibble 1 = main
; Nibble 2 = cmd
; Nibble 3 = obd
; Nibble 4 = send_and_receive_...
; Nibble 5 = read_telegram_...
; Nibble 6 = send_telegram
; Nibble 7 = SendData


[UNIT_A]
Port=Com2
Hardware=OBD

[UNIT_B]
Port=Com3
Hardware=OBD

[UNIT_C]
Port=Com4
Hardware=OBD

[UNIT_D]
Port=Com5
Hardware=OBD

[UNIT_E]
Port=Com6
Hardware=OBD

[UNIT_F]
Port=Com7
Hardware=OBD

[UNIT_G]
Port=Com8
Hardware=OBD

[UNIT_H]
Port=Com9
Hardware=OBD

[UNIT_I]
Port=Com10
Hardware=OBD

[UNIT_J]
Port=Com11
Hardware=OBD

[UNIT_K]
Port=Com12
Hardware=OBD

[UNIT_L]
Port=Com13
Hardware=OBD

[UNIT_M]
Port=Com14
Hardware=OBD

[UNIT_N]
Port=Com15
Hardware=OBD

[UNIT_O]
Port=Com16
Hardware=OBD



When I run OBDsetup.exe, I get this screen, so everything seems to fine with it:



My OBD cable is OBDlink SX with FTDI FT232 RL chipset. Its drivers are installed and it works completely OK with the OBDWiz and Scan XL Professional. The USB is set to COM1, the latency time is set to 1:



So what can be wrong?

Cheers,
Vladi


Reply With Quote
  #2  
Old 04-13-2013, 05:41 PM
Junior Member
 
Join Date: Mar 2013
Location: West Valley NY
Car: E39 528i
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Default

I played hell with it for several days, first make sure you only have it on 1 computer(not on 1 and also in a VMware on the same computer) Also I found if I changed in my Ediabas file

; Interface
; Description : Connected diagnosis interface
; Default = STD:OBD

Interface =STD:OBD

; Additional information (in German) :
; Bitte beachten: Der HW-Treiber fuer das Interface muss installiert sein

To:

; Interface
; Description : Connected diagnosis interface
; Default = EDIC

Interface =STD:OBD

; Additional information (in German) :
; Bitte beachten: Der HW-Treiber fuer das Interface muss installiert sein

Everything runs fine, give it a shot.
Reply With Quote
  #3  
Old 04-14-2013, 07:44 AM
Junior Member
 
Join Date: Apr 2013
Location: Switzerland
Car: Z4 M Roadster (2006)
Posts: 4
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by newwt357 View Post
I played hell with it for several days, first make sure you only have it on 1 computer(not on 1 and also in a VMware on the same computer) Also I found if I changed in my Ediabas file

; Interface
; Description : Connected diagnosis interface
; Default = STD:OBD

Interface =STD:OBD

; Additional information (in German) :
; Bitte beachten: Der HW-Treiber fuer das Interface muss installiert sein

To:

; Interface
; Description : Connected diagnosis interface
; Default = EDIC

Interface =STD:OBD

; Additional information (in German) :
; Bitte beachten: Der HW-Treiber fuer das Interface muss installiert sein

Everything runs fine, give it a shot.
Hi newwt,

I am running the programs on the original Windows platform, have not installed any virtual machines.

The proposed corrections of the .ini file would not have any effect since the symbol ; means simply a comment line and the software would not read and execute anything that is written on a line starting with ;

Made some more tests today, including soldering pin 7 to pin 8 of the cable and reprogramming the FT232RL chip from:

#C0 = TXLED#
#C1 = RXLED#
#C2 = TXDEN
#C3 = PWRON#
#C4 = SLEEP#


to

#C0 = RXLED#
#C1 = TXLED#
#C2 = PWRON#
#C3 = PWRON#
#C4 = SLEEP#


plus inverting the RI# and DSR# lines.

As a result now I can fool the battery and ignition check (both circles are black) but all other problems remain the same.

What I noticed, though, is that the LED of the USB cable (on the OBD II connector part) is blinking every time the EDIABAS is trying to communicate with the car. Both before and after the cable modification and reprogramming of the FT 232RL. This means that the communication with the cable is OK but from there to the car something goes wrong. I guess inappropriate pinout...

Another test that I ran was to use the DCAN tool and set the interface to K-CAN. When I try to do so there is an error message saying "Error: KCAN echo" or something. Which, of course, supports my hypothesis that there's something wrong between the car ant the cable.
Reply With Quote
  #4  
Old 05-20-2013, 04:06 PM
Junior Member
 
Join Date: Apr 2013
Location: Switzerland
Car: Z4 M Roadster (2006)
Posts: 4
Thanks: 0
Thanked 0 Times in 0 Posts
Default Problem solved!

Managed to solve the problem by buying a dedicated K+CAN cable and reinstalling the INPA + EDIABAS package:

[Only for registered users... ]

Had already the drivers installed (the previous cable had the same chipset).

Before soldering pins 7 and 8 to each other, INPA would read only the engine data. After soldering them the whole thing works perfectly.

Did not need to modify any of the files that were installed with the INPA + EDIABAS installation (EDIABAS.ini and OBD.ini). Since my cable was installed on COM2, during the installation of INPA +EDIABAS package simply selected COM2 instead of COM1 during the installation.

Now only need to start learning how to diagnose and code. After all the troubles I had so far with all this mess, it seems to be the easy part
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
Help inpa error chappy BMW GT1, OPS/OPPS, INPA 0 03-26-2013 01:26 AM
R56 error with INPA ? fxmartin BMW diagnostics and repair 1 03-11-2013 02:22 PM
INPA Error on install DHeffernan BMW GT1, OPS/OPPS, INPA 3 01-25-2013 04:26 PM
got a error msg when I install the inpa sch44000 BMW coding and programming 0 09-20-2012 01:09 PM
INPA error weiss BMW GT1, OPS/OPPS, INPA 5 08-21-2011 07:39 PM


All times are GMT. The time now is 10:31 PM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2017, vBulletin Solutions, Inc.
Search Engine Optimization by vBSEO 3.6.1
BMW forum: diagnostics, coding, programming.