hey guys,
I'm having some problems with my INPA to work proper.
I installed INPA 5.02 and Ediabas 6.4.7
When i start INPA it will say if i turned the ignition on or off.
but when I try to connect tot any module of my e36 325i I will keep getting the IFH-0006 error.
In the INPA faq it says:
3.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”.
so i went to look up the file ''tool32''
this is what is says in the file:
[Programm]
Name=Toolset
[KONFIGURATION]
INTERFACE01=,,
INTERFACE02=,,
INTERFACE03=,,
INTERFACE04=,,
INTERFACE05=,,
INTERFACE06=,,
INTERFACE07=,,
INTERFACE08=,,
INTERFACE09=,,
MULTIINSTANZ=N
LANGUAGE=E
TOOLBAR=-1
KOPFZEILE=-1
HINWEISZEILE=-1
JOB_INFO=-1
TAB_INFO=-1
ARG_INFO=-1
RES_INFO=-1
AUSGABE_SORTIERT=1
INPA_FS_MODE=1919
[WINDOWS]
JOB_LEFT=0
JOB_TOP=0
JOB_WIDTH=9600
JOB_HEIGHT=3075
JOB_VALUE=0
KON_LEFT=0
KON_TOP=0
KON_WIDTH=6480
KON_HEIGHT=3180
KON_VALUE=0
so I have absolutely no idea what I need to change in this file to get it working.
I hope anyone here can help me.
greetings,
Dennis
ps: sorry for the grammar mistakes, I'm dutch
Last edited by Denniz0229; 07-16-2011 at 09:43 AM.
Did you make the necessary path change to your computer environment variables when you installed INPA (c:\ediabas\bin) as per the ENGLISH SETUP.pdf and did you ensure that you only updated your existing INPA v3.01/EDIABAS v6.4.3 installation with v5.02 (which is only an upgrade version).
yes, i did both.
Which interface are you using?
STD:OBD
also tried ADS, witch gives me the same problem.
This may be a silly question, but did you install v5.02/6.4.7 by upgrading your original v3.01/6.4.3 installation? If not, you will probably have some files missing, as v5.02/6.4.7 is only an upgrade.
yes I did
What operating system are you running and have you made the appropriate changes to the LoadWIN32=* statement in Ediabas.ini (e.g. for XP, LoadWIN32=1)
running XP SP3
and yes loadwin32 is set to 1
When you start INPA are you using INPA (_.IPO)?
you mean to start inpa?
for that I just use the shortcut on my homescreen, witch leads to INPA in C:/Inpa/Bin
or did you mean something else?
yes i checked it, it is the .ipo
Last edited by Denniz0229; 08-04-2011 at 11:18 AM. Reason: Automerged Doublepost
no one?
If you have followed all installation instructions exactly, the only other possible causes are that you have:-
a). Not run the hardware setup to correct registry settings as per this ENGLISH SETUP.pdf; or,
b). Have another Ediabas suite program such as Tool32 running or have the Ediabas Server currently open in another application.
INPA works fine on my 98 Z3M, but on my wife's 94 325i it says: "IFH-0006: COMMAND NOT ACCEPTED. Program will be stopped!" I re-checked env variables, and that COM1 is correct in both places. (For my S52 I chose "M52", which is correct.) For my wife's car I chose "DME 3.31 for M50 2.5 1", which is her engine. The diff seems to be which car it is plugged into. One guess is that the plug is not connecting due to corrosion (I'm using the plug in the engine compartment). Any other ideas? thanks for any responses.
Pre OBD2 cars are a completely different diag system, which uses mostly the L - line diagnostic protocols. You will not be able to diagnose that car without a true ADS interface on a true serial port.
I would use the so called "stomp test" to identify codes on that car.
-Abel
- E36 328is ~210-220whp: Lots of Mods.
- 2000 Z3: Many Mods.
- 2003 VW Jetta TDI Manual 47-50mpg
- 1999 S52 Estoril M Coupe
- 2014 328d Wagon, self-tuned, 270hp/430ft-lbs
- 2019 M2 Competition, self-tuned, 504whp
- 2016 Mini Cooper S
^ That's backwards.
OP What people aren't telling you:
- You can read about 80% of modules in an E36 with a Vagcom / KKL / OBDII cable and 16 pin to 20 pin adapter
- ADS is needed for things like KOMBI (instrument cluster) and other ADS modules like ABS on my UK 328
- A Motronic ECU like in the 94 324 can be read with an ADS interface AND mistreku.zip files (or just use flash codes / stomp test)
- As for the L-Line stuff, most stuff is K. The difference with ADS modules IIRC is the L line flips between send and receive
No warranty of any kind implied or given and no liability for any loss, damage or injury, no matter how incurred accepted.
The DME is L-line on that car above, subject of the post was DME. The only reason why we use ADS interface on these older cars is for the L-line capabilities. Or else the simple usb cables (dual or single k lines) would work on all the modules if it was mostly K-line.
Sure the airbag module and some ABS modules are K-line. Not relevant to their check engine light.
-Abel
- E36 328is ~210-220whp: Lots of Mods.
- 2000 Z3: Many Mods.
- 2003 VW Jetta TDI Manual 47-50mpg
- 1999 S52 Estoril M Coupe
- 2014 328d Wagon, self-tuned, 270hp/430ft-lbs
- 2019 M2 Competition, self-tuned, 504whp
- 2016 Mini Cooper S
Bookmarks