If files are missing, consider reinstalling BMW Standard Tools or copying the correct SGBD files from a reliable source.
: Check the physical switch on your K+DCAN cable. If your car is pre-2007, you may need to bridge pins 7 and 8 on the cable connector. For post-2007 cars, these pins must be separated.
If your car battery drops below 12 volts during diagnostics, modules will shut down their communication lines. Connect a battery charger if you are running long diagnostic sessions.
: Ensure the cable's LED is active. If your car is pre-2007, check if you need a K+DCAN switch cable to bridge pins 7 and 8. inpa error 159
In the same Advanced settings window:
In the EDIABAS/INPA ecosystem, Error 159 is officially defined as: or Group file bad / Checksum error .
If the error persists, the setup is more complex. If files are missing, consider reinstalling BMW Standard
Download the latest files matching your BMW chassis (e.g., E90, E60, E46).
This single change eliminates 80% of INPA Error 159 occurrences on DCAN vehicles.
Without more specific information about the context in which the error 159 occurs (e.g., during a specific test, with a certain vehicle model), providing a precise solution is challenging. The steps above are general guidelines that can help you approach and potentially resolve the issue. For post-2007 cars, these pins must be separated
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:
EDIABAS can only handle one client program at a time. If you attempt to start ToolSet while an INPA script is already running—or vice versa—you will encounter communication errors. This also applies when trying to run INPA and DIS simultaneously.
: INPA typically requires the cable to be assigned to COM1 in the Windows Device Manager.
The prefix stands for Interface Handler . When INPA throws this specific error, it means the Ediabas server (the background engine driving INPA) sent a command to a vehicle control module, but that module failed to respond within the expected timeout window.
[OBD] Port=COM1 <-- Make sure this matches Device Manager Hardware=USB Use code with caution. Save the file. 4. Check Ignition/Voltage