Inpa Error 159 !!top!! -

In the BMW diagnostic tool EDIABAS, typically indicates a NET-0009: TIMEOUT

. This communication fault occurs when EDIABAS does not receive a response from the interface or the vehicle within the specified timeframe. Most Common Causes & Solutions DIS - Fault 200 159 - Bimmerforums - The Ultimate BMW Forum

3. Incorrect COM Port & Latency Settings (Windows 10/11)

INPA is 1990s software expecting 1990s hardware. Modern USB ports are too fast and too aggressive.

  • Wrong COM Port: INPA is hardcoded to look for a specific COM port (usually COM1). If your USB cable shows up as COM7, INPA screams "Transmitter not ready."
  • Latency too low (or too high): The latency timer in Windows device manager must be set to 1 ms or 2 ms. Default is 16 ms – too slow for the K-Line timing.

Common causes

  • Faulty/loose OBD-II/K+DCAN adapter (FTDI/USB-to-serial issues, incorrect driver, or bad cable).
  • Wrong adapter mode or wiring (K-line vs. D-CAN/CAN; incorrect switch position on adapter).
  • COM port or USB driver issues on the PC (FTDI or Prolific drivers mismatched or virtual COM port conflict).
  • Incorrect INPA/EDIABAS configuration (wrong interface selected, wrong COM port, wrong VIN/module ID settings).
  • Power/ground problems in vehicle (ignition not on, low battery, blown fuses, bad ground).
  • Faulty module or CAN bus wiring (short/open on CAN high/low, terminated incorrectly, damaged wiring harness).
  • Module asleep or coding mismatch (module in sleep mode, or module addressing not matching expected bus).

2. Symptoms

If this error is present, you might experience:

  • Check Engine Light (CEL) / EML light.
  • Engine goes into "Limp Mode" (limited RPM/power).
  • Hard starting or Crank/No Start condition.
  • Rough idling.

Step 4: Force the COM Port to COM1

  • Open Device Manager > Ports (COM & LPT).
  • Right-click your USB Serial Port > Properties > Port Settings > Advanced.
  • Change the COM Port Number to COM1.
  • Note: If COM1 is in use, disable the device using it (like an internal modem) or use COM2 and edit EDIABAS.INI.

Step 1: Verify Physical Hardware

  1. Remove the 20-pin adapter (if used). Plug the 16-pin OBD cable directly into the cabin OBD port (on E90/E60/E70). If the error disappears with direct connection, your 20-pin adapter is faulty.
  2. Bridge pins 7&8 manually inside the round adapter with a small wire or upgrade to a "pin 7&8 bridged" adapter with a 100-ohm resistor.
  3. Clean the OBD port contacts with electrical contact cleaner.

Conclusion:

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.

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 inpa error 159

: 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 In the BMW diagnostic tool EDIABAS, typically indicates

: 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 Code 159 (DME Digital Motor Electronics)

In INPA, error code 159 typically refers to a specific manufacturer fault code when reading the DME (Digital Motor Electronics) on BMW vehicles (typically E46, E39, E38, etc.). Wrong COM Port: INPA is hardcoded to look

The error usually translates to: "Control Unit Self-Check Failed" or "Internal Control Unit Fault."

Here is a guide on how to diagnose and fix this issue.

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.”

3. Switch to ICOM Emulation

For DCAN vehicles (E90 onward), you can emulate an ICOM using software like INPA with ICOM Emulator (EDIABAS 7.3.0). This changes the job handling mechanism from "single job cancel on error" to "retry queue." It masks Error 159, though it doesn't fix the root cause.