Error 159 ^hot^: Inpa
In INPA (BMW diagnostic software), is a common communication timeout error. It typically signals that the software is trying to talk to the car but isn't getting a response within the expected timeframe. Why Error 159 Happens Poor Connection
: The most frequent cause is a physical connection issue between your OBDII cable (K+DCAN) and the car, or between the cable and your computer's USB port. Driver/COM Port Settings
: Your computer might be using the wrong COM port (it usually needs to be
) or the "Latency Timer" in your device manager isn't set to Software Interference
: Antivirus or firewall programs can sometimes block the EDIABAS server from communicating properly. Ignition Status
: If the car's ignition isn't fully "On" (position 2), the modules won't wake up to respond to the request. Troubleshooting Steps Check Hardware
: Unplug and re-seat your cable on both ends. Ensure the pins in the OBDII port aren't bent. Verify COM Port Device Manager > Ports (COM & LPT) . Right-click your cable, go to , and ensure it is set to Latency Timer Update EDIABAS : Ensure your file (found in C:\EDIABAS\BIN ) matches the COM port you set in the Device Manager. Restart the Server inpa error 159
: Close INPA, look for the small "E" icon in your system tray (EDIABAS server), close it manually, and restart INPA.
For a deep dive into specific BMW error codes and setups, you can find detailed community discussions and guides on platforms like Bimmerpost Bimmerforums Are you using a device or a standard K+DCAN cable for your connection? VXDIAG BMW INPA API Initialization Error Solution
Troubleshooting INPA Error 159: Comprehensive Guide to NET-0009 Timeout
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. In INPA (BMW diagnostic software), is a common
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 Decoding INPA Error 159: The Ultimate Guide to
Most INPA communication errors, including the 159 timeout, stem from Windows COM port settings. DIS - Fault 200 159 - Bimmerforums - The Ultimate BMW Forum
Decoding INPA Error 159: The Ultimate Guide to the EDIABAS / SYS-0015 Mismatch
3. Switch to ICOM Emulation
For DCAN vehicles (E90 onward), you can emulate an ICOM using software like INPA with ICOM Emulator (EDIABAS 7.3.0). This changes the job handling mechanism from "single job cancel on error" to "retry queue." It masks Error 159, though it doesn't fix the root cause.
7. Failing K-Line or CAN Transceiver
On older cars, the K-Line from the DME to the OBD port can have high resistance due to corroded pins. Also, the 74HC125 or 74HCT125 driver chip inside your K+DCAN cable can overheat and fail partially—passing wake-up signals but failing on high-speed data.
Case 2: The E90 330i (N52 Engine) After a Battery Change
Symptoms: Worked fine before battery swap. After new battery, Error 159 on all DME jobs. Other modules (ABS, Airbag) work.
Root Cause: The new battery was not registered. The DME was in reduced power mode (emergency program) and disabled diagnostic KWP2000 responses.
Solution: Registered the battery using Tool32 (steuern_batterie job). Restarted INPA. Error resolved.
