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

INPA Error 159 Report

Introduction

INPA (Interface for NCS & NCP) is a software tool used for diagnostics and programming of BMW vehicles. However, some users have reported encountering an error code, specifically "INPA Error 159". This report aims to provide an overview of the error, its possible causes, and potential solutions.

What is INPA Error 159?

INPA Error 159 is a communication error that occurs when the INPA software is unable to establish a connection with the vehicle's ECU (Engine Control Unit). The error code is typically displayed as "Error 159: No response from ECU".

Possible Causes of INPA Error 159

Based on user reports and forums, the following are possible causes of INPA Error 159:

  • Incorrect or faulty cable connections: Issues with the cable connections between the vehicle's OBD-II port and the INPA interface can prevent communication with the ECU.
  • INPA software configuration: Incorrect configuration of the INPA software, such as incorrect vehicle selection or settings, can lead to Error 159.
  • ECU not responding: In some cases, the ECU may not be responding to the INPA software, causing the error.
  • Vehicle's OBD-II port issues: Problems with the vehicle's OBD-II port, such as damage or corrosion, can prevent communication with the ECU.

Potential Solutions

To resolve INPA Error 159, try the following:

  • Verify cable connections: Check the cable connections between the vehicle's OBD-II port and the INPA interface to ensure they are secure and not damaged.
  • Check INPA software configuration: Review the INPA software settings and ensure that the correct vehicle and ECU are selected.
  • Restart the INPA software and vehicle: Sometimes, a simple reboot of the INPA software and the vehicle can resolve the issue.
  • Use a different INPA interface or cable: If possible, try using a different INPA interface or cable to rule out any issues with the current setup.

Conclusion

INPA Error 159 can be a frustrating issue for BMW enthusiasts and technicians. By understanding the possible causes and trying the potential solutions outlined in this report, users may be able to resolve the error and establish a successful connection with the vehicle's ECU. If the issue persists, further troubleshooting or seeking assistance from a qualified technician may be necessary.

Step 4: Run EDIABAS Loopback Test

Open a command prompt as administrator. Navigate to:

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.

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.

Step 7: Replace the K+DCAN Firmware (Last Resort)

Some cheap Chinese interfaces come with faulty firmware for the PIC microcontroller. You can re-flash them using MProg (for FTDI-based cables). Download the BMW Standard Tools compatibility firmware (version 1.5 or 1.6). After re-flashing, the interface will correctly handle job termination acknowledgments, eliminating Error 159.

Step 2 – Update Your DATEN Files (The Real Fix)

You need the latest DATEN files for your chassis. Here’s the workflow:

  1. Download the latest SP-DATEN (e.g., v68 or higher) for your specific chassis.
  2. Use BMW Standard Tools (EDIABAS) to import them:
    • Run EDIABAS\Bin\prg_file_replacer.exe or manually copy files.
    • Replace the contents of C:\EDIABAS\ECU with new .PRG files.
    • Replace C:\EC-APPS\INPA\SGDAT with updated .IPO files.

Pro Tip: If you’re using a pre-packaged INPA installation (like Mike’s Easy BMW Tools), re-run the installer and select “Update DATEN for E-series.”

What causes this?

  • Wrong COM port settings – INPA expects a fixed COM port (usually COM1).
  • USB-to-EDIABIAS driver issues – The cable is not on the correct latency or COM port.
  • Missing or incorrect EDIABIAS.ini or OBD.ini configuration.
  • Another program (e.g., Tool32, WinKFP) is still using the EDIC interface.

1. Understanding INPA Error Codes:

  • INPA (BMW Diagnostic Software) uses a variety of error codes to indicate issues with the vehicle's systems or with the software itself.
  • Error 159 might not be universally documented, so specific details can depend on the vehicle model, software version, and the operation being performed.

Common Names for Error 159:

  • IFH-0009: No response
  • SYS-0012: Identification error
  • Error 159: Program version incorrect for control unit
  • API-0012: Error on identifying ECU

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.