| Symptom | Likely Cause | Fix | | :--- | :--- | :--- | | Error appears immediately after clicking battery | COM port mismatch | Change USB to COM1 | | Error appears after 5-10 seconds | Latency too high | Set latency to 1ms | | Error on E46 only (cable works on other cars) | Pin 7-8 bridge missing | Flip cable switch to "0" or bridge manually | | Error on all cars | Bad FTDI driver | Reinstall FTDI driver v2.8.30 | | Error after working for 10 minutes | USB selective suspend | Disable power saving on USB hubs | | Error when reading ABS or Airbag only | Faulty ABS/Airbag module | Unplug the module and retest |
This error is most common on pre-2008 BMWs using the K-Line (single-wire diagnostics). Specifically:
If you have an E90 or newer (using D-CAN), you might see this error too, but it usually points to a different root cause (usually a missing DCAN adapter or wrong cable).
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). inpa error 159
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.
Don’t just click “E46” and then “Engine.” Instead: | Symptom | Likely Cause | Fix |
If you see ??? next to the script name, your DATEN files are missing that ECU definition.
To fix the error, you must understand the "why." There are five primary culprits. Do not skip this section.
Open a command prompt as administrator. Navigate to: This error is most common on pre-2008 BMWs
cd C:\EDIABAS\BIN
Run the internal loopback test:
ediabas /t
If the result shows Error 159, EDIABAS cannot talk to the interface at all—check your COM port driver. If it passes, the issue is with the car’s specific ECU.