Their INPA had DATEN v40 (released 2010). The MS43 DME in their car had a 2005 firmware update. The old script didn’t recognize the updated response.
[OBD] Port=Com5 ;Hardware=USB
By default, Windows sets USB serial ports to a latency of 16 milliseconds. INPA requires a latency of to maintain a stable connection with BMW modules. Plug your K+DCAN cable into your laptop's USB port. inpa error 159
INPA error 159 is a communication timeout that halts diagnostics dead in their tracks. The vast majority of cases are solved by correctly setting the and the Latency to 1ms in your Windows Device Manager. For more stubborn cases, check your firewall, your EDIABAS.INI settings, or consider the advanced solutions outlined above. By working through the steps in this guide, you will systematically identify the root cause and restore your connection to your BMW's inner workings.
The error also appears in official BMW documentation as “EDIABAS Fehler 159, NET-0009: TIMEOUT — The program will be aborted”. Regardless of the exact wording, the core problem is the same: INPA cannot establish a stable communication channel with your vehicle’s diagnostic interface. Their INPA had DATEN v40 (released 2010)
Ensure both circles in the top-left corner of the INPA home screen ( and Ignition ) are solid black.
BMW utilizes two distinct communication protocols over the OBD2 physical port. If your cable is pinned incorrectly for your chassis, the ECU will remain silent, forcing an Error 159 timeout. [OBD] Port=Com5 ;Hardware=USB By default, Windows sets USB
EDIABAS must be explicitly told to look for a USB cable rather than an old serial cable or network connection. Navigate to C:\EDIABAS\BIN\ . Open the file named EDIABAS.ini using Notepad. Use Ctrl + F to search for the word .
Incorrect interface definitions inside the initialization files send data packets down the wrong software pipelines. 📋 Step-by-Step Diagnostic and Resolution Workflow
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.
After fixing Error 159, you should be able to: