Understanding and Fixing INPA Error 159 (Timeout Error) INPA Error 159 , often labeled as a Timeout Error or API Initialization Error , is a common communication failure that occurs when the INPA software is unable to establish or maintain a stable connection with the vehicle's Electronic Control Units (ECUs). This error typically indicates that the software sent a request but did not receive a response within the allotted timeframe. Whether you are using a standard K+DCAN cable or an advanced interface like VXDIAG, resolving this error usually requires checking hardware connections, driver settings, and software configuration. Common Causes of Error 159 Poor Physical Connection: Loose OBD-II port connections or faulty USB ports on your laptop. Latency Settings: The Windows COM port latency is often set too high (default is usually 16ms), causing the software to "time out" before the car responds. Incorrect COM Port Configuration: A mismatch between the COM port assigned in Windows Device Manager and the OBD.ini file. Cable Communication Speed: Some vehicles, especially E90/E92 LCI models, require specific K-Line or D-CAN speeds to be set manually. Software Conflicts: Attempting to run INPA while another EDIABAS-based tool (like ToolSet32 or DIS) is active. Step-by-Step Solutions to Fix Error 159 1. Adjust Latency Settings (Most Common Fix) For INPA to communicate reliably, the USB-to-Serial latency must be set to 1ms. Open Device Manager on your PC. Expand Ports (COM & LPT) and right-click your cable (e.g., USB Serial Port ). Select Properties > Port Settings > Advanced . Change the Latency Timer (msec) from 16 down to 1 . Ensure the COM Port Number is set to COM1 (unless your OBD.ini specifies otherwise). 2. Verify OBD.ini and Ediabas.ini Configuration Your software must be "looking" at the same port your cable is plugged into. DIS - Fault 200 159 - Bimmerforums - The Ultimate BMW Forum
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 : 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
Decoding INPA Error 159: The Ultimate Guide to the EDIABAS / SYS-0015 Mismatch Introduction: The Frustration of a Silent Connection You’ve just hooked up your K+DCAN cable to your E46, E90, or E39. You’ve launched INPA (the Standard BMW Diagnostic Tool). You select your chassis—E90, for instance. You click on the engine (DME). The status bar at the bottom turns green. You hold your breath. And then, instead of live data or fault codes, you are greeted by a pop-up window: "Error 159: API job canceled or incorrect result" Or, in some versions: "EDIABAS Error 159: SYS-0015 – Job status error." Your heart sinks. You check the ignition. You wiggle the USB cable. You restart the laptop. Nothing works. If this scenario sounds familiar, you have encountered the infamous INPA Error 159 . While it sounds cryptic, it is actually one of the most well-documented—and solvable—communication errors in the BMW diagnostic ecosystem. This article will dissect Error 159 from the transistor level to the software configuration, providing you with a definitive roadmap to a stable connection.
Part 1: What Exactly is INPA Error 159? The Technical Definition In the BMW diagnostic stack, INPA (Interpretierbare Programmiersprache für die BMW Diagnose) acts as the front-end user interface. It communicates with the car via the EDIABAS (Eigene Diagnose-Basis Software) middleware. EDIABAS translates high-level commands from INPA into low-level protocols (K-Line, DCAN, or K-CAN). Error 159 is an EDIABAS error code that translates to: "JOB_CANCELED" or "JOB_INCORRECT_RESULT." In plain English: The diagnostic request sent from your laptop reached the car’s control unit, but the answer was malformed, incomplete, or never arrived. The ECU either said "I don't understand the question" or the signal was corrupted during transmission. How It Appears on Screen You will typically see the error in a red dialog box. The full text often reads: inpa error 159
Error in job 'RDSYS' or 'RESULT' : Error 159
Sometimes the error is paired with SYS-0015 in the EDIABAS trace file, indicating a "transmission timeout." Which BMW Models Are Affected? Error 159 is not model-specific, but it is interface-specific . It plagues:
E36, E39, E46 (K-Line, round diagnostic port under the hood) E83, E85, E60 (Transitional K-Line to DCAN) E90, E92, E87, E70, R56 (DCAN with 20-pin adapter) Understanding and Fixing INPA Error 159 (Timeout Error)
It rarely appears on newer F-series or G-series cars using ENET or ICOM interfaces.
Part 2: The Root Causes – Why Does Error 159 Happen? Unlike a simple "cable not found" error (Error 128), Error 159 indicates partial communication. The handshake succeeded, but the conversation failed. Here are the seven most common root causes. 1. Battery Voltage Too Low (The Silent Killer) BMW ECUs are sensitive to voltage fluctuations. If your car battery is below 11.8V or the laptop USB port cannot supply stable 5V to the interface, the transceiver chips in the K+DCAN cable will produce corrupted data frames. Why this triggers Error 159: The DME (engine computer) receives the wake-up signal and prepares a response, but during transmission, the voltage dips. The DME's checksum calculation fails, and it aborts the job. 2. Ignition State Misdetection INPA and the interface must know whether the ignition is ON (Terminal 15) or OFF. Some aftermarket USB cables have poor ignition sense circuits. When you select a job (e.g., reading DME error memory), the ECU expects terminal 15. If it senses ground instead, it returns an "incorrect result." 3. Corrupted EDIABAS Configuration Files (EDIABAS.INI & OBD.INI) The file C:\EDIABAS\BIN\EDIABAS.INI contains the line Interface = STD:OBD . If this points to the wrong DLL (e.g., STD:OBD when you are using a serial port), the API job will cancel. Similarly, OBD.INI maps the COM port. A mismatch here is a guaranteed Error 159. 4. The 20-Pin Adapter Bridge Timing Issue If you are using a round 20-pin adapter (under the hood of E46/E39) with a 16-pin OBD2 cable, the adapter must bridge pin 7 (K-Line) and pin 8 (Battery+). Cheap adapters have no electronics—just wires. This creates a "bounce" in the K-Line signal during initialization. INPA starts a job, the line glitches, and the ECU cancels. 5. Driver Latency & USB Buffer Overrun BMW diagnostic interfaces use FTDI or CH340 chipsets. Windows default USB polling rates are too slow (16ms). When INPA requests a multi-frame response (e.g., reading 20 fault codes), the buffer overflows. The API job is canceled because the result is incomplete. 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. 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.
Part 3: Diagnostic Workflow – Systematic Steps to Kill Error 159 Do not randomly reinstall software. Follow this logical, step-by-step process. Step 0: Power Management Common Causes of Error 159 Poor Physical Connection:
Connect a battery tender or jump starter to the car’s jump points under the hood. Maintain at least 12.3V. For laptops, disable USB selective suspend in Windows Power Options. Use a USB 2.0 port (not USB 3.0, which has different signal voltage thresholds).
Step 1: Verify Physical Hardware