Inpa Error 159 May 2026

The INPA Error 159 (often appearing as Fault 200.159 in older DIS environments) is a high-level communication error between your computer and the vehicle's diagnostic interface. It most commonly indicates that the software has failed to initialize the API or cannot detect a valid battery/ignition signal. 🛠️ Root Causes

Hardware Connection: Your diagnostic cable (K+DCAN, ICOM, or VXDIAG) is not properly seated or recognized by Windows.

Ignition Signal Missing: The software does not "see" that the car is on. Many cheap K+DCAN cables lack a bridge between pins 7 and 8, or the "Battery" and "Ignition" dots in INPA remain white (off) even when connected.

EDIABAS Configuration: The EDIABAS.ini file is likely set to the wrong interface type (e.g., set to STD:OBD when it should be REMOTE for some wireless devices, or vice versa).

Driver Conflict: The COM port assigned to your cable in Windows Device Manager does not match the port defined in your OBD.ini file. ✅ Step-by-Step Fixes 1. Match the COM Ports

INPA requires the hardware and software to be on the exact same "channel." Open Device Manager > Ports (COM & LPT).

Right-click your cable (e.g., "USB Serial Port") > Properties > Port Settings > Advanced.

Ensure the COM Port Number is set to COM1 (or whichever port is listed in your C:\Ediabas\Bin\OBD.ini).

Set Latency Timer (msec) to 1. This is critical for preventing timeout errors like 159. 2. Verify EDIABAS Settings

Navigate to C:\EDIABAS\BIN\ and open EDIABAS.ini with Notepad.

Troubleshooting INPA Error 159: Comprehensive Guide to NET-0009 Timeout inpa error 159

INPA Error 159 (formally identified as EDIABAS Fehler 159, NET-0009: TIMEOUT) is a communication failure that occurs when the BMW diagnostic software fails to receive a response from the interface or control unit within the allocated timeframe. This error typically signals that the physical connection is broken, the network configuration is incorrect, or the diagnostic head is not properly initialized. Primary Causes of Error 159

Understanding why this timeout occurs is the first step toward a permanent fix. The most common culprits include:

Incorrect EDIABAS Configuration: The EDIABAS.INI file may have a false remotehost setting or the wrong interface type selected.

Hardware Connectivity Issues: A loose OBDII cable, a faulty K+DCAN interface, or a diagnostic head (like the VXDIAG VCX SE) that is not well-connected to the laptop or vehicle.

Interface Mismatch: Using an older ADS connector when the software expects a standard OBD setup, or using a poor-quality "blue board" cable that fails to maintain a stable data stream.

Software Interference: Antivirus programs or active firewalls can disrupt the communication bridge required for DIS (Diagnostic Information System) and INPA to talk to the car. Step-by-Step Solutions to Fix Error 159 1. Verify EDIABAS.INI Network Settings

If you are using a network-based diagnostic head or a virtual machine (VM) setup, ensure your configuration file is accurate. Path: Locate C:\EDIABAS\Bin\EDIABAS.INI.

RemoteHost: Set the RemoteHost to the correct network name or IP address (e.g., 192.168.68.1 for many standard DIS setups).

Interface: Ensure Interface = STD:OBD is selected if using a standard K+DCAN cable. 2. Configure COM Port and Latency

Most INPA communication errors, including the 159 timeout, stem from Windows COM port settings. DIS - Fault 200 159 - Bimmerforums - The Ultimate BMW Forum The INPA Error 159 (often appearing as Fault 200

3. Common Causes

Before assuming the DME is broken, check these three main causes, ordered from easiest to hardest:

6. Wrong INPA Version for the DME

Early versions of INPA (5.0.2) lack definition files for newer DMEs like the MSV70 or MSD80. When you select the DME, INPA builds a job based on an outdated .IPO file. The ECU receives a request with a wrong memory address or identifier. It responds with "Job not supported," which EDIABAS reports as Error 159.

When Is Error 159 Normal?

Error 159 is expected if:

You select an ECU that is not installed in your car (e.g., EKP for a non-returnless fuel system).
The vehicle is pre-1996 without full OBD2 support (use 20-pin round diagnostic port adapter).
The ECU is sleeping (e.g., after ignition OFF for >10 minutes).

Quick Reference Card

| If you see… | The fix is… | |-------------|--------------| | Error 159: Program version incorrect | Update DATEN files for that chassis | | Error 159: Identification error | Use F3 menu to pick exact ECU script | | IFH-0009 + Error 159 | Latency timer to 1ms + check cable termination switch (set to “Auto” or “K-Line”) |

Bottom line: Error 159 is frustrating but fixable. It’s INPA’s way of saying, “I see a computer, but I don’t speak its firmware language.” Update your DATEN, match your script, and you’ll be back to coding in 15 minutes.

Have a different error code? Mention it in the comments—include your BMW model, year, and INPA version.

INPA Error 159 (formally identified as EDIABAS Error 159, NET-0009: TIMEOUT

) typically occurs when the diagnostic software cannot establish or maintain a connection with the vehicle's control units. This is common in setups using virtual machines or networked interfaces like the ICOM. Bimmerforums.com Quick Fix: Error 159 (NET-0009: TIMEOUT) Check IP Configuration

If you are using an emulator or networked head (like ICOM), ensure your Ediabas.ini and network adapter (often "PC1") are correctly configured. Common Fix : Set your computer's IP address to 192.168.68.30 and the gateway/server in Ediabas.ini 192.168.68.1 IFHSrv32.exe

is running and correctly shows the assigned IP in its window. Verify Hardware Connection Battery/Ignition You select an ECU that is not installed in your car (e

: Ensure the software detects "Battery: ON" and "Ignition: ON." If these dots aren't black, the interface isn't seeing the car, leading to a timeout. Cable Switch

: On K+DCAN cables, ensure the physical toggle switch is in the correct position for your car's model year (usually "pinned" together for pre-2008 and separated for post-2008). Resolve Software Conflicts One App Rule

: Only one program (INPA, Tool32, WinKFP, or NCSExpert) can access EDIABAS at a time. If you try to open Tool32 while INPA is active, you may trigger communication errors. : Verify that your USB-to-Serial adapter is set to

and that the "Latency Timer" in Windows Device Manager is set to Network-Specific (ICOM/Remote) If using ICOM, open iTools Radar

to "Reserve" your ICOM device. If it isn't reserved, the diagnostic session cannot claim the interface. Interface = REMOTE is set in your Ediabas.ini file if using a network-based head. Bimmerforums.com modifying the Ediabas.ini file specifically?

Frequently Asked Questions: About EDIABAS, INPA ... - Scribd

In the BMW diagnostic tool EDIABAS, typically indicates a NET-0009: TIMEOUT

. This communication fault occurs when EDIABAS does not receive a response from the interface or the vehicle within the specified timeframe. Most Common Causes & Solutions DIS - Fault 200 159 - Bimmerforums - The Ultimate BMW Forum

INPA Error Code 159 (DME Digital Motor Electronics)

In INPA, error code 159 typically refers to a specific manufacturer fault code when reading the DME (Digital Motor Electronics) on BMW vehicles (typically E46, E39, E38, etc.).

The error usually translates to: "Control Unit Self-Check Failed" or "Internal Control Unit Fault."

Here is a guide on how to diagnose and fix this issue.