Tool32 (found in C:\EDIABAS\BIN ) bypasses INPA’s job scheduler. Open Tool32, load the appropriate .PRG file (e.g., MSV70.PRG for E90 325i). Run a simple job like FS_LESEN (read status). If Tool32 returns valid data but INPA returns Error 159, your INPA installation has corrupt .IPO or *.ENG files.
Securely attach a dedicated (supplying at least 10–20 Amps) to the under-hood terminals of your BMW.
By systematically working through voltage checks, driver latency, EDIABAS configuration, and hardware integrity, you will not only fix Error 159 but also gain a deep, practical understanding of how BMW’s diagnostic stack operates. inpa error 159
Four primary issues cause the NET-0009: TIMEOUT message to trip: 1. Windows Latency Timer Misconfiguration
Your software must be "looking" at the same port your cable is plugged into. DIS - Fault 200 159 - Bimmerforums - The Ultimate BMW Forum Tool32 (found in C:\EDIABAS\BIN ) bypasses INPA’s job
Windows defaults USB serial ports to a 16ms latency timer. INPA requires an aggressive response time of 1ms to prevent connection timeouts.
These models utilize high-speed D-CAN signaling. Physical Pin 7 and Pin 8 must be completely separated . Bridging them on a D-CAN car shorts out the network bus and blocks communication. If Tool32 returns valid data but INPA returns
is an EDIABAS error code that translates to: "JOB_CANCELED" or "JOB_INCORRECT_RESULT."
At its heart, Error 159 is a on the NET-0009 layer. It means your interface and software failed to establish or maintain a communication channel with each other. This is almost always caused by one of the following:
A: Some counterfeit chips ignore latency settings. You need to use the FTDI Prog tool to write the latency value directly to the EEPROM of the cable. Or buy a better cable.