Posted inCardiagtech

Unlock BMW Diagnostics: Your Comprehensive Guide to K+DCAN Car Diagnosis Driver

No Comments

For BMW enthusiasts and professional mechanics alike, having the right diagnostic tools is essential for maintaining peak vehicle performance. INPA (Instrumentierungsprogamm für Producton und Aftersales) software, paired with a K+DCAN USB interface cable, emerges as a powerful solution for in-depth diagnostics and coding on BMW E-Chassis models manufactured between 1998 and 2008. This guide provides a detailed walkthrough of everything you need to know about the Kdcan Car Diagnosis Driver setup, software installation, cable usage, and troubleshooting, ensuring you can effectively diagnose and maintain your BMW.

Part 1: Understanding INPA Software for BMW Diagnostics

What is INPA BMW Software?

INPA is specialized diagnostic software designed for BMW vehicles. It facilitates communication with your car’s electronic control units (ECUs), allowing you to read diagnostic trouble codes (DTCs), access real-time data, perform coding, and execute various service functions. Specifically tailored for older BMW E-series models, INPA, when used with a kdcan car diagnosis driver and cable, provides capabilities often found in professional-grade diagnostic systems.

Alt Text: INPA BMW software interface displaying diagnostic options for vehicle modules.

Downloading INPA Software: Versions 5.0.2 and 5.0.6

Obtaining the INPA software is the first step in leveraging its diagnostic capabilities. Two commonly used and reliable versions are INPA 5.0.2 and 5.0.6. You can download these versions from trusted sources online. Be cautious and ensure you are downloading from reputable platforms to avoid malware.

Download Links:

Alt Text: INPA 5.0.2 download link preview on Mega file hosting service.

Alt Text: INPA 5.0.6 download link preview on Mega file hosting service.

Software Specifications:

  • Software Version: 5.0.2 & 5.0.6
  • Operating System Compatibility: Windows 7/10/XP
  • Language: English
  • Software Update: Not Updatable
  • Vehicle Compatibility: BMW E-Chassis vehicles (1998-2008)
  • Hardware Compatibility: INPA/Ediabas K+DCAN USB Interface

INPA Software Installation Guide for Windows 7

Installing INPA software correctly is crucial for proper operation. Follow these steps for a successful installation on Windows 7. The process is similar for other compatible Windows versions.

Important Pre-Installation Steps:

  1. Disable Antivirus Software: Temporarily disable your antivirus software as it might flag some INPA files as false positives.
  2. Extract to Local Disk (C:): Extract the downloaded INPA software files directly to your C: drive. Installing in other locations can lead to errors.
  3. Avoid Software Updates: Do not attempt to update the INPA software as it is not designed for updates and this can cause malfunctions.

Step-by-Step INPA Installation:

  1. Run INPA Installer: Locate the downloaded “BMW Inpa” folder, extract it to your desktop, then open the “Inpa V5.02” folder. Extract the “cicdaten”, “ediabas_7.2.0.504_”, and “NCSEXPER” compressed packages to your C: drive simultaneously.

Alt Text: Selecting compressed packages “cicdaten”, “ediabas_7.2.0.504_”, and “NCSEXPER” for extraction.

  1. Choose Extraction Destination: When prompted, click “Extract to”, select “System C”, and click “OK”.

Alt Text: Choosing “System C” drive as the destination for file extraction.

  1. Confirm File Overwrite: Click “Yes to All” if prompted to overwrite existing files.

Alt Text: Confirmation prompt to overwrite existing files during extraction.

  1. Create INPALOAD Shortcut: Open “My Computer”, navigate to the “Bin” folder within the INPA installation directory (usually C:INPABin or C:EDIABASBin). Right-click on “INPALOAD”, select “Send to”, and then “Desktop (create shortcut)”.

Alt Text: Creating a desktop shortcut for the INPALOAD application.

  1. Access System Properties: Right-click on “My Computer” and select “Properties”.

Alt Text: Accessing system properties from the “My Computer” context menu.

  1. Open Advanced System Settings: Click on “Advanced system settings” to open the System Properties window.

Alt Text: Navigating to “Advanced system settings” in System Properties.

  1. Environment Variables: In the System Properties window, go to the “Advanced” tab and click on “Environment Variables”.

Alt Text: Opening “Environment Variables” in the Advanced System Properties tab.

  1. Edit Path Variable: Under “System variables”, select “Path” and click “Edit” or “New” depending on your Windows version.

Alt Text: Editing the “Path” system variable in Environment Variables.

  1. Add Bin Directory to Path: Add the path to the “Bin” directory of your INPA installation (e.g., C:EDIABASBIN) to the “Variable value” field. If you are creating a new entry, input “Path” as “Variable name” and the Bin directory path as “Variable value”.

Alt Text: Adding the INPA “Bin” directory path to the System “Path” variable.

  1. Confirm Environment Variables: Click “OK” on all Environment Variables and System Properties windows to save changes.

  2. Run INPA: Double-click the “INPALOAD_Shortcut” on your desktop to launch the INPA program.

Alt Text: INPA software successfully installed and running on Windows.

Congratulations! INPA BMW software is now installed successfully.

Operating System Specific Installation Tips:

For more detailed instructions tailored to your specific operating system, refer to these guides:

Installing the INPA Driver Software (K+DCAN Driver)

To ensure your K+DCAN cable properly communicates with your computer and the INPA software, you need to install the correct kdcan car diagnosis driver.

  1. Connect K+DCAN Cable: Plug your K+DCAN interface cable into a USB port on your laptop.

Alt Text: K+DCAN cable connected to a laptop USB port.

  1. Open Device Manager: Right-click on “My Computer” and select “Manage”.

Alt Text: Accessing Computer Management from “My Computer” context menu.

  1. Locate USB Serial Port: In the Computer Management window, click on “Device Manager”. Look for “USB Serial Port” under “Ports (COM & LPT)”. It might have a warning icon if the driver is not installed. Right-click on “USB Serial Port (COM)”, where is the COM port number assigned (e.g., COM6), and select “Properties”.

Alt Text: Locating “USB Serial Port” in Device Manager to update driver settings.

  1. Port Settings – Advanced: In the “USB Serial Port Properties” window, navigate to the “Port Settings” tab and click on the “Advanced” button.

Alt Text: Accessing “Advanced” port settings in USB Serial Port Properties.

  1. Configure COM Port and Latency: In the “Advanced Settings for COM*”, change the “COM Port Number” to “COM1”. Set the “Latency Timer (msec)” to “1”. Click “OK” to save these settings.

Alt Text: Configuring COM Port Number to COM1 and Latency Timer to 1 in Advanced Settings.

The kdcan car diagnosis driver is now configured correctly!

Basic INPA Usage Guide

After installing INPA and configuring the driver, you can start using it for BMW diagnostics. Here are some basic usage instructions and common questions answered:

How to Start INPA:

Run “Inpaload.exe” located in C:INPABin or C:EC-AppsINPABin. Alternatively, you can use the shortcut created on your desktop or find it in your Start Menu under EDIABAS INPA ELDI NCS NFS INPA(_.IPO).

Finding EDIABAS Package Version:

The version of your EDIABAS installation can be found in C:EDIABASversion.txt or C:EDIABASpackage.pdf.

Uninstalling INPA/EDIABAS:

To uninstall, simply delete the “Ediabas” and “Inpa” folders from your C: drive. INPA installation does not create registry entries, making uninstallation straightforward.

ToolSet.exe vs. Tool32.exe:

“Tool32.exe” is the newer version and starts the EDIABAS server as a 32-bit application. “ToolSet.exe” is an older version, primarily relevant for Windows 3.11.

Understanding SGBD Names with “_xxx”:

SGBDs (System Group Description files) starting with “_” (e.g., _LWS5) are for development purposes only, such as writing identification data, and are not intended for standard use or customer service.

KVP Editor Functionality:

The KVP Editor (Kontinuierlicher Verbesserungsprozess – Continuous Improvement Process) is accessible within INPA and is mainly used in development and plant environments. It allows users to input their information, error descriptions, and improvement requests for direct feedback to BMW.

Part 2: Understanding the K+DCAN Cable for BMW Diagnosis

K+DCAN Cable Website and Purchase Information

The K+DCAN cable serves as the physical interface between your computer and your BMW vehicle. A reliable source to purchase a quality K+DCAN cable is obdii365.com.

http://www.obdii365.com/wholesale/bmw-inpa-k-can-with-ft232rq-chip.html

Current K+DCAN Cable Price: $17.99 (Price may vary)

Alt Text: K+DCAN cable product image for BMW INPA diagnostics.

Choosing the Right Cable: K+DCAN vs. ENET vs. ICOM

Selecting the correct cable depends on your diagnostic, coding, or programming needs, and the BMW model series you are working with (E, F, etc.).

  • K+DCAN Cable: Ideal for diagnosis and coding on BMW E-series vehicles.
  • ENET Cable: Used for F-series BMW models for diagnosis, coding, and programming.
  • ICOM Next: A professional-grade tool preferred for programming (flashing ECU’s) on E and F-series, especially necessary for E-series programming.

For basic diagnosis and coding of E-series BMWs, the K+DCAN cable is a cost-effective and capable choice. For more details on cable selection, refer to this comparison: http://blog.obdii365.com/2017/09/13/k-dcan-cable-vs-enet-cable-vs-bmw-icom/.

Advantages and Disadvantages of K+DCAN Cables

K+DCAN cables come in variations, primarily differing in the configuration of pin 8. Some have pin 8 enabled, while others have it disabled. Cables with pin 8 disabled are better suited for newer E90 models (post 03/07) but often include a black adapter to re-enable pin 8 for compatibility with older models like E46, E39, E63, etc. Cables with pin 8 active are typically older versions.

Alt Text: K+DCAN cable with a switch to toggle pin 7 and 8 connection for protocol selection.

Pin 7 & 8 Configuration:

  • DCAN Cars: Use one pin for Ethernet connection and the other for the K data line.
  • K-Line Cars: Both pins are connected to K data lines.

Solutions for Compatibility:

  • Adapter: Use an adapter to bridge pins 7 and 8 internally.
  • Switch: Use a K+DCAN cable with a built-in switch to manually bridge or separate pins 7 and 8 based on the vehicle’s protocol requirements.

DCAN.exe Utility:

After connecting the K+DCAN interface to your car and computer, run “DCAN.exe” (often included with the cable software) to configure the communication rate, especially when switching between modes. This utility typically needs to be run only when changing between K-line and DCAN modes.

Internal PCB Quality:

Quality K+DCAN cables feature well-soldered and intentionally bridged pins on the PCB to ensure proper signal transmission.

Alt Text: Internal PCB of a K+DCAN cable showing quality soldering and component arrangement.

Source: http://www.obdii365.com/wholesale/bmw-inpa-k-can-with-ft232rq-chip.html

How to Use the K+DCAN INPA Cable

Understanding how to switch between K-Line and DCAN modes is essential for using your K+DCAN cable effectively across different BMW models.

Switching Between K-Line and DCAN:

  • Physical Connection/Disconnection: For switching between K-Line and DCAN protocols, you may need to physically connect (for K-Line) or disconnect (for DCAN) pins 7 and 8, depending on your cable type and vehicle requirements. Cables with a switch simplify this process.

  • DCAN.exe Configuration: Run the “DCAN.exe” utility after connecting the cable to the car and computer, especially when switching between modes. This configures the communication rate and settings for the interface.

Usage Scenarios:

  • DCAN Mode: Typically used for newer BMW E-series models (post 2007). Ensure pins 7 and 8 are disconnected or set to DCAN mode via a switch. Run DCAN.exe to configure.

  • K-Line Mode: Required for older BMW E-series models. Pins 7 and 8 need to be connected or set to K-Line mode. Run DCAN.exe to configure for K-line if necessary.

Addressing Common Questions:

  • Q: Do I need to physically connect/disconnect pins 7&8?

    • A: Yes, depending on your cable and the BMW model. Cables with switches provide easier mode switching. Adapters can also bridge pins 7 & 8.

  • Q: Anything else to do when switching from K-Line to DCAN?

    • A: Run DCAN.exe after connecting to configure the interface for DCAN mode.

  • Q: Do I need to run DCAN.exe every time I use DCAN?

    • A: No, only when switching modes. The settings are usually retained after the first run for a specific mode.

  • Q: How to switch back to K-Line?

    • A: Connect pins 7 and 8 (physically or via switch) and run DCAN.exe to set to K-Line mode if needed.

Source: http://blog.obdii365.com/2018/02/04/k-dcan-cable-with-switch-pin-7-8-good-or-not/

Part 3: INPA Vehicle Coverage and Supported Protocols

INPA Vehicle Compatibility (E-Chassis BMW Models)

INPA software with a K+DCAN cable is primarily designed for BMW E-Chassis vehicles manufactured from 1998 to 2008. This includes a wide range of models:

  • BMW 1-Series: E81, E82, E87, E88 (2004-2011)
  • BMW 3-Series: E90, E91, E92, E93 (2005-2011)
  • BMW 5-Series: E60, E61 (2003-2010)
  • BMW 6-Series: E63, E64 (2002-2010)
  • BMW 7-Series: E65, E66 (2000-2008)
  • BMW X-Series: E70 (X5), E71 (X6), E83 (X3), E84 (X1)
  • BMW Z-Series: E85, E86 (Z4), E89 (Z4 – early models)
  • MINI: R56, R55, R57, R58, R59, R60, R61 (early models)

Protocols Supported by INPA and K+DCAN

The K+DCAN interface and INPA software support a range of communication protocols used in BMW vehicles:

  1. Fast Magistral D-CAN and PT-CAN (500 kbit/s): Used in newer E-series models for high-speed communication between ECUs.
  2. Slow Magistral K-CAN (100 kbit/s): Used for body electronics and slower communication systems in E-series.
  3. Standard BMW OBD Interface Protocol: For older BMW models, particularly pre-2000, and for accessing certain modules in newer models via the OBD-II port.

D-CAN Compatibility (Examples):

  • E60, E61 from 03/2007
  • E83 from 09/2006
  • E81, E87 from 03/2007
  • E90, E91, E92, E93 from 03/2007
  • E70 (new X5 model)
  • R56 (new MINI model)

Protocol “For BMW OBD Interface” (Older Cars):

  • 1995 to 1998 models (K-line not needed)
  • 1998 to 03/2008 models (all E-series)

Part 4: Troubleshooting Common INPA BMW Software Errors

Encountering errors while using INPA is not uncommon. Here are solutions to some frequent issues:

1. Driver Error (COM Port Conflict)

Error Message: Typically appears with ADS or OBD connectors, indicating a COM port conflict.

Reason: Another program or device is using the COM1 port, which INPA requires.

Solution: Ensure no other applications are using COM1. Close any conflicting programs or reconfigure them to use a different COM port. Verify in Device Manager that no other devices are assigned to COM1 before using INPA.

2. EDIABAS Error 126

Alt Text: EDIABAS Error 126 message indicating concurrent access conflict.

Reason: This error occurs if you try to run ToolSet while an INPA script is already active, or vice versa. Only one program can access EDIABAS at a time.

Solution: Close INPA completely before starting ToolSet, and vice versa. Ensure only one of these programs is running at any given time.

3. ToolSet Error: Runtime error ’372’

Alt Text: ToolSet Runtime error 372 message related to msflxgrd.ocx file.

Reason: An outdated version of msflxgrd.ocx file exists in c:winntsystem32.

Solution: Register the msflxgrd.ocx file located in the c:Ediabasbin directory.

  • Windows XP/7/10: Open “Start”, type “Run”, and execute the command: regsvr32 c:ediabasbinmsflxgrd.ocx. Click “OK” to confirm the registration.

4. INPA: Vehicle Could Not Be Identified

Solution: This issue often arises from conflicts or incorrect configurations within the EDIABAS installation.

  1. Uninstall Supplemental Ediabas: If you have a separate Ediabas installation, uninstall it via Control Panel.
  2. Rename Existing BIN Directory: In your main ISTA/D (Rheingold) directory, rename C:RheingoldEdiabasBIN to C:RheingoldEdiabasOLD_BIN.
  3. Reinstall Ediabas MSI: Reinstall the Ediabas MSI package, changing the installation path to C:RheingoldEdiabas during installation. This will create a new C:RheingoldEdiabasBIN directory with necessary files.
  4. Modify EcuPath: Edit C:RheingoldEdiabasBINEDIABAS.INI and change the EcuPath parameter to C:RheingoldEcu.
  5. Configure Interface: In C:RheingoldEdiabasBINEDIABAS.INI, set Interface = STD:OBD.
  6. Configure OBD Port: In C:RheingoldEdiabasBINOBD.INI under the [OBD] section, set Port=Com1 (or the COM port your K+DCAN cable is using) and Hardware=OBD.

These steps ensure a clean and correctly configured EDIABAS setup for INPA.

5. INPA Error IFH-0009: NO RESPONSE FROM CONTROL UNIT

Reason: This is a common error, often stemming from issues with the interface cable, drivers, or configuration. Possible causes include:

  1. Poor Quality Interface: Low-quality or incorrectly wired K+DCAN cables are a frequent cause.
  2. Incorrect Drivers: Wrong or outdated USB drivers for the interface cable.
  3. Incorrect COM Port Settings: Improperly configured COM port settings in Windows Device Manager (COM port number, latency).
  4. Wiring Issues in Interface Cable: Pin 8 may be disconnected, bridged to pin 7, or incorrectly wired.
  5. Incomplete INPA Installation: Missing or corrupted configuration files in incomplete INPA versions.

Solution:

  1. Verify Interface Quality: Use a reputable vendor for your K+DCAN cable to ensure quality and correct wiring.

  2. Install Correct Drivers: Use the latest drivers for your interface cable. The software package often includes compatible drivers.

  3. Check COM Port Settings: Ensure the COM port for your USB Serial Port is set to COM1 and Latency Timer is set to 1 in Device Manager.

  4. Interface Wiring Configurations:

    • Option i) Pin 8 joined to Pin 7: Try bridging pins 7 and 8 with a small wire link inside the OBD socket of the cable.
    • Option ii) Pin 8 physically disconnected: Try disconnecting pin 8.
    • Option iii) Pin 7 and Pin 8 individually connected: Ensure pins 7 and 8 are individually connected without a bridge.

    Start by trying option i) as it’s the most common vehicle configuration. You may need to experiment with these configurations, especially if using the cable on different BMW models. Adapters are available to bridge pins 7 and 8 without soldering.

  5. Full INPA Version: Ensure you are using a complete and correctly installed version of INPA, including Ediabas and BMW Standard Tools.

Real Case Solution Example:

One user resolved IFH-0009 by noticing that pin #8 on their OBD/USB cable was bent and not making proper contact in the pin #8 slot of the OBD-II connector. Straightening the pin resolved the issue. Always check for physical defects or connection problems.

6. BMW INPA Edibas IFH-0018: INITIALIZATION ERROR

Solution: Refer to this detailed guide for troubleshooting IFH-0018 errors: http://blog.obdii365.com/2016/06/26/inpa-edibas-ifh-0018-initialization-error/

Continuous Updates:

This troubleshooting guide is continuously updated with new error solutions and tips. Check back regularly for more information.

Back to top

Conclusion

Mastering INPA software and utilizing a K+DCAN cable provides BMW owners and technicians with a powerful diagnostic tool. By following this comprehensive guide, from software and kdcan car diagnosis driver installation to cable configuration and troubleshooting, you can effectively diagnose and maintain your BMW E-Chassis vehicle, ensuring optimal performance and longevity. Remember to always use reliable software sources and quality hardware to achieve the best results in your BMW diagnostic endeavors.

Comments

No comments yet. Why don’t you start the discussion?

Leave a Reply

Your email address will not be published. Required fields are marked *