Using Tiny ADS. INPA sees battery/ignition dots but getting IFH - 0009 error

[DanB]

I'm trying to access control modules on my 1998 540i through the 20 pin connector and using a Tiny ADS cable. (I've got a 16 pin and a 20 pin on my car) FIFO is set up correctly, and I followed the installation instructions carefully.

As stated in the title, INPA sees the battery / ignition, but can't access anything past that. It thinks for about 4 seconds and then throws the 0009 error. DIS also won't connect, and I'm not even going to try and install SSS until I can establish a basic connection.

Can anyone see where I'm going wrong?

Setup:
Dell D630
Windows XP
Tiny ADS cable
INPA 5.02
EDIABAS 6.4.7

EDIABAS.bin:

;================================================= ============================
;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 = 1

;-----------------------------------------------------------------------------
; 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 = ADS

Interface =ADS

; 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 : FLASH.SERVICE@BMW.DE (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 : Michael.Rowedder@bmw.de

; 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 : Michael.Rowedder@bmw.de

; 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 : Michael.Rowedder@bmw.de

;-----------------------------------------------------------------------------
; 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
;================================================= ============================

[IcemanBHE]

Well DIS wont work because your remote host isnt correct.

But INPA should as far as I know. Remove the comm before the LOADWIN. Doubt that it though...

Did you start with INPA 5x/EDIABAS 6.4.7? Or did you upgrade from 3x/6.4.3? There is ZERO benefit, (Actually you lose functionality) with 5x over 3x for the E31.

Did you run the ADS setup (Ediabas/hardware/ADS) and reboot?

[David Mc]

The serial port on some DELLs needs a special driver. Put this http://www.4shared.com/file/RWJRyeB0/ads32-dell.html in your EDIABAS\Bin folder and try your setup again. (You may need to use the password INPA to download the driver).

[DanB]

Trying to also install SSS (I decided to do it before I fix the connectivity issue b/c I can't get to the car right now), and I'm running into a memory error during installation. I've allocated the HD to 20GB and I keep getting this message.

I should add that the swapfile is set to have the OS manage.

My primary HD is 80GB and there's around 4.8GB free after SSS's 20GB allocation.





Help!

[Beemer187]

Trying to also install SSS (I decided to do it before I fix the connectivity issue b/c I can't get to the car right now), and I'm running into a memory error during installation. I've allocated the HD to 20GB and I keep getting this message.

I should add that the swapfile is set to have the OS manage.

My primary HD is 80GB and there's around 4.8GB free after SSS's 20GB allocation.

Help!

You need to set the HDD to 80GB.

[DanB]

Ok back to INPA...

I reformatted everything (and stayed with XP per iceman's advice) and reinstalled INPA. Same issue; sees battery and ignition (turning ignition on and off toggles the dot), but still getting that IFH-0009 can't access module error. \

On my TinyADS connector, the green lights on the board for battery/ignition are lit, however all the other lights (K/L/etc) are off.

Is there some process to connecting the cable to the car before switching on the ignition or booting up the laptop I should be following?

edit: again, this is on a 1998 540i with both the 20 pin and the 16 pin plugs, and I am using a TinyADS cable with the 20 pin port. My mechanic was able to connect his autologic to the car.

[benemorius]

Same issue; sees battery and ignition (turning ignition on and off toggles the dot), but still getting that IFH-0009 can't access module error. \

On my TinyADS connector, the green lights on the board for battery/ignition are lit, however all the other lights (K/L/etc) are off.

This is rather telling. The fact that the INPA ignition dot toggles means that you've got the right serial port, yet the fact that the K and L LEDs never flash means that the data packets from INPA are not getting all the way to the diagnostic bus. This can result from a broken serial port, serial cable, or interface. Since your mechanic can access your DME (was that through the 20 pin connector?) we can assume for now that the problem is not with the vehicle.

Except for this business with the special dell driver, which I know nothing about, it's difficult for me to imagine how this behavior could arise from a software configuration issue.

Since you are so close (most Tiny ADS interfaces I ship have international destinations and take weeks to arrive) I'll go ahead and send another interface your way in case that's the problem. It seems silly not to take advantage of your close proximity.

In the mean time, you can try what's often called a loopback test on your serial port (as well as any serial extension cables you may be using) in order to try to narrow down the fault. To do this, you want to simply short the TXD and RXD (transmit and receive) pins together at the end of your serial cable (or right at the laptop if you aren't using any extension cable). You can use google images to get some pictures of the serial port pinout (pay attention to whether you're looking at a female end or a male end since the pinouts are reversed) but if you're able to read the tiny numbers on your serial connector, TX is pin 3 and RX is pin 2.

With the pins shorted, you'll then want to open up any serial terminal program, send some characters to the correct serial port, and verify that the characters appear in your terminal. This will verify the functionality of the serial port transmit and receive hardware as well as any wiring included in the loop.

You can use Hyperterminal to do this if it still comes with windows by default, but there are surely much simpler terminal programs out there. Maybe someone else can chime in with another recommendation. On linux I use Picocom.

You can probably google "serial port loopback test" and get a heck of a lot more information if necessary.

[DanB]

FIXED!

I happen to have an identical laptop & I swapped out hard drives. Turns out my first laptop has a bad serial port.

I'm in and I'm able to access modules.

Thanks for the troubleshooting help guys, and if you've already sent that extra cable benemorious, I'll drop it right back in the mail to you. It's a slick piece of hardware!

[benemorius]

FIXED!

I happen to have an identical laptop & I swapped out hard drives. Turns out my first laptop has a bad serial port.

I'm in and I'm able to access modules.

Thanks for the troubleshooting help guys, and if you've already sent that extra cable benemorious, I'll drop it right back in the mail to you. It's a slick piece of hardware!

That's some funny timing right there! I'm literally just walking in the door from my trip to the post office.

I'll take the extra one back if you have no other use for it, but I'd rather you send it to a friend or anyone else who can use it instead.

I'm really glad to hear it's working for you now. I guess it must have been only the output driver for the TXD pin that was fried in the serial port since it otherwise seemed to work. There's nothing impossible about that, but it's certainly a first in my book!

[KevinMullins]

Ya'll got me itchin' to play with one of these now. Would like to compare functionality to our DIY version we doinked with for so long, which is still going strong.

[fabiosouzajr]

I am having the same issue although with a thinkpad using a serial expresscard I can connect to most modules in inpa except the DME. The car uses MS 41.0, so ADS it is. I can however gain access to the dme with tool32.exe, reading and reseting codes is all good but sometimes throws the same error as mentioned above.
Anyone got any ideas?
maybe the expresscard? some config?

[stooge75]

its something to do wi response times i think. i have got latest daten files ecu etc & i still get ifh009 errors but can connect ok & read things but every now & then the error reappears. my wurth,delphi etc all connect flawlessly

[Deron]

Hi Benemorious. Recently bought one of your interface. Connected to my lap top using a serial port adapter to the usb with driver installed. However it doesn't seem as if it is connected. No black dot by battery with ignition on. By the way I read references to lights on the interface. This one doesn't have any.
Is it that it cannot work through the usb connection?

[Deron]

Hi benemorious
The interface worked fine thanks. Just need to learn how to use the software. I had scanned the codes I got last night.

[Deron]

Didn't realize they had uploaded as I was getting error messages. Hope they're clear.

[Deron]

Hi, have one of your tiny ADS interface. Can it work with USB to serial adapter. Trying to connect a 1998 520i ADS. When I use the other ADS connector the best I get is IFH0003 error.

[MParallel]

Having a similar issue. ADS setup. Two black dots in INPA. Can for example communicate with gauge cluster, but not the ZKE or DME.

In a VM with WinXP SP3.

Weird thing, doing the same on an older laptop, 32 bit OS, same cable, ADS works on all modules. If I install the same VM Player with same WinXP SP3, i run into the same error. Serial port configures to use the host's.

Tried different send/receive buffers. Made no difference.

Really weird. Like data gets lost between host and guest. But then why on some modules?

[2JZ E36]

Having a similar issue. ADS setup. Two black dots in INPA. Can for example communicate with gauge cluster, but not the ZKE or DME.

In a VM with WinXP SP3.

Weird thing, doing the same on an older laptop, 32 bit OS, same cable, ADS works on all modules. If I install the same VM Player with same WinXP SP3, i run into the same error. Serial port configures to use the host's.

Tried different send/receive buffers. Made no difference.

Really weird. Like data gets lost between host and guest. But then why on some modules?

I remember that I had some wierd connection issues in a VM once, but I solved it with an older version of VirtualBox... So if you have tried everything else, might want to try that. Or try it via USB without a VM, I made a thread about it

[MParallel]

I’ll give virtual box a try. hope it works as nice as
VM (albeit the weird problem). The link you posted, very interesting.

I’d like a native 32-bit OS install, but the computer has a 64-bit UEFI which doesn’t allow 32-but OS install.
I tried a bootable USB with “Legacy” option turned on, but no cigar. Unless some hidden bios functions prevent this.

Noticed that under Device Manager, with my Com1 set at IRQ4/3F8, that there is a UART serial controller, also on IRQ4, with exclamation point saying it has no resources. Hope that is not interferring with the com1 port control, or controller of the port itself.
Default RS232 settings were Com1,IRQ3, 2F8. Which is not the usual standard config.