INPA Error IFH-0006: Command not accepted, Help needed

[spitfire980]

Hi Guys

I purchased the diagnostic laptop from a member and Im having problem with INPA on my 98 E38 V12 and 95 E31 V12. I cant seem to access the DMEs but can access the EML

Laptop: Lenovo x131e


Inpa:



Im using these cables




I keep getting this once i try to access the DME on both my V12s



and then



Any help would be appreciated

Thanks

[MParallel]

In INPA/EDIABAS aer pdf files that explain all the errors.

Are you using ADS?

[spitfire980]

In INPA/EDIABAS aer pdf files that explain all the errors.

Are you using ADS?

Ill look into the PDF files,

I dont think this, the link for the cable says BMW INPA/Ediabas K+DCAN USB Interface TO OBD OBDII OBD2 Car Diagnostic Scanner Tool Cable

I posted pictures of the cables I got, guessing i need to order another set of cables?

[328 Power 04]

I haven't done the research whether the V12's DMEs are K line or L-line?

If they are L-line, then you need ADS interface, or an ICOM.


The K+DCAN can do K line diag just fine.

[spitfire980]

I haven't done the research whether the V12's DMEs are K line or L-line?

If they are L-line, then you need ADS interface, or an ICOM.


The K+DCAN can do K line diag just fine.

I can read the EML and gearbox but not the DME

Can you recommend a ADS cable thats has a USB end since my laptop doesn't have a serial port?

Thanks

[328 Power 04]

I have not seen an ADS interface actually work on USB. Some claim to work on USB, but I'm still waiting for one to say, yes, I connected to an L-line module through ADS on USB!



An alternative option is ICOM interface (significantly more money), which will work fine with newer laptops and L-line modules. It connects with Ethernet or wifi to the laptop.

But be very careful with the Chinese clones. Some of them are very poorly made. Do your research, or ask.

[MParallel]

Just to add, I finally got confirmation from Do It Auto that their USB-ADS interface does not work without a serial port.

So AFAIK, ADS still requiers a serial port laptop or fancy diaghead (Icom, GT1).

[MParallel]

Here's from the FAQ doc located in C:\EDIABAS\Doku\English

1.3 EDIABAS Error 16: IFH-0006: COMMAND NOT ACCEPTED


This error occurs if an SGBD is loaded into ToolSet and the OBD connector is being used.

Cause 1: ODB has actually been set as interface inside EDIABAS.INI, but ToolSet uses
multi instance with another interface, e.g. K-line. The setting for multi instance
and the interfaces used is made inside the file TOOL32.INI, in the directory
C:\WINDOWS (or alternatively C:\WINNT for Windows NT). Therefore the entries
in TOOL32.INI regarding the interfaces are used instead of the ones in
EDIABAS.INI. The use of multi-instance in the ToolSet is identified in the title
bar, for example with “Tool32:1”, for single multi-instance.

Solution 1: Enter the interface being used into TOOL32.INI or disable multi instance by the
entry “No”.

Cause 2: An SGBD using the diagnosis protocoll is loaded into ToolSet. For UDS-SGBDs
you have to use the interface OMITEC but in the EDIABAS.INI the setting for
the interface is
Interface = STD:OBD

Solution 2: Modify the interface setting inside EDIABAS.INI to
Interface = STD:OMITEC
The OMITEC connector must have power supply (blue blinking). If the connector is not supplied and you want to load the SGBD, you will have to use the simulation mode. You can activate the simulation mode inside the menue
Configuration -> EDIABAS


Notice, if you want to use the simulation mode, a simulation file for the interface
has to exist inside the simulation directory. for further ways of solution, see chapter 1.11

[328 Power 04]

Odd explanation from them, because OMITEC USB cannot do L-line communication. I have one and have tried everything. Omitec desktop does ADS, but OMITEC in general are so rare and expensive, you're better off with a genuine ICOM.

Maybe it's the same idea, but needs to be on ADS setting, with ADS interface.