This resource is a pure how-to guide that explains how to configure a second standalone EDIABAS installation to use RPLUS mode with a BMW ICOM interface. There are no downloads in this resource: all steps are performed with existing EDIABAS files and two configuration screenshots that you insert into the text.
Highlights
Package contents
This guide does not contain files to download. It describes how to work with the following components that are already present in a typical BMW diagnostic setup:
Compatibility notes
The procedure is written for EDIABAS 7.6.0 with BMW ICOM interfaces on standard Windows workshop laptops. Folder names and drive letters can vary between installations, but the logic is the same: ISTA keeps its own EDIABAS folder and a second EDIABAS tree under C:\EC-APPS is used by INPA and other tools. Your ICOM must already be reachable in the local network with a known static IP address.
Basic usage
Highlights
- Uses the EDIABAS 7.6.0 binaries copied from ISTA so that INPA, Tool32 and other tools share the same ICOM libraries.
- Configures the standalone EDIABAS instance under C:\EC-APPS\EDIABAS to use the RPLUS:ICOM_P interface.
- Shows how to point ECU, SIM and TRACE paths to the correct folders for the second installation.
- Explains how to set the correct REMOTEHOST IP address for your ICOM in Rplus.ini.
- Works without changing the original ISTA installation and without adding any extra launchers.
Package contents
This guide does not contain files to download. It describes how to work with the following components that are already present in a typical BMW diagnostic setup:
- Primary EDIABAS installation that belongs to ISTA (for example under C:\Program Files (x86)\BMW\ISPI\TRIC\ISTA\Ediabas\BIN).
- Second standalone EDIABAS installation (for example under C:\EC-APPS\EDIABAS\BIN).
- Configuration file EDIABAS.INI in the standalone BIN folder.
- Configuration file Rplus.ini in the standalone BIN folder.
Compatibility notes
The procedure is written for EDIABAS 7.6.0 with BMW ICOM interfaces on standard Windows workshop laptops. Folder names and drive letters can vary between installations, but the logic is the same: ISTA keeps its own EDIABAS folder and a second EDIABAS tree under C:\EC-APPS is used by INPA and other tools. Your ICOM must already be reachable in the local network with a known static IP address.
Basic usage
- Close ISTA, INPA, Tool32 and any other application that could be using EDIABAS.
- Open the ISTA EDIABAS BIN folder and copy all files from that directory into the second BIN folder at C:\EC-APPS\EDIABAS\BIN, overwriting the existing files there.
- In C:\EC-APPS\EDIABAS\BIN edit EDIABAS.INI. In the [Configuration] section set Interface = RPLUS:ICOM_P and verify that EcuPath, SimulationPath and TracePath all point to the C:\EC-APPS\EDIABAS subfolders.
- In the same folder edit Rplus.ini. In the [ICOM_P] section set REMOTEHOST to the IP address of your ICOM (for example 192.168.68.40). Leave the default port and timeout values unchanged unless you have a specific reason to modify them.
- Save the changes and start INPA or Tool32. Select the ICOM interface if required and test a connection to the vehicle. When configuration is correct the status line should show an active ICOM connection without communication errors.