Ediabas 6.4.3

This guide goes beyond basic installation, focusing on architecture, file roles, custom vehicle configuration, troubleshooting raw protocols (K-Line, DCAN, K-CAN via OBD), and using it with tools like INPA, WinKFP, NCS Expert, and Tool32.

1. What EDIABAS 6.4.3 actually is EDIABAS = E lektronische DI agnose A bfrage BA sis S ystem Version 6.4.3 is one of the last standalone versions before BMW moved to the EDIC / ICOM -first model. Key components:

EDIABAS.INI – master configuration ECU folder – .PRG files (diagnostic job interpreters per ECU type) SGDAT folder – *.IPO files (job descriptions for INPA) CFGDAT – configuration for API layers BIN – api32.dll , ediabas.exe , ifhsrv32.exe , odbc32.dll etc. Tracing – debugging logs Hardware – serial, USB (K+DCAN), or network (EDIC/ICOM) driver config

EDIABAS itself is not INPA. INPA calls EDIABAS API. ediabas 6.4.3

2. Core Architecture (6.4.3 specific) INPA / NCS Expert / WinKFP / Tool32 │ [api32.dll] ← job & result handling │ EDIABAS.DLL / EDIABAS.EXE (background process) │ IFH-Service (ifhsrv32.exe) for network EDIC/ICOM │ [OBD.INI / EDIABAS.INI / ECU.INI] │ Physical layer (Serial COMx, USB:STD:OBD, REMOTE)

6.4.3 still heavily relies on Serial or STD:OBD definitions, not purely the Remote interface of newer versions.

3. Critical configuration files – deep dive 3.1 EDIABAS.INI – master switch Location: C:\EDIABAS\BIN\ Key parameters for 6.4.3: [Configuration] Interface = STD:OBD ; or SERIAL, REMOTE, EDIC Simulation = 0 Tracing = 1 TracePath = C:\EDIABAS\TRACE TraceSize = 5000000 JobPriority = NORMAL TimeoutConnect = 3000 TimeoutReceive = 5000 TimeoutSend = 2000 ApiDll = api32.dll This guide goes beyond basic installation, focusing on

STD:OBD means “use whatever is defined in OBD.INI” (usually K-Line or DCAN). SERIAL means direct COM port without OBD.INI. 3.2 OBD.INI – physical layer definition (STD:OBD only) Example for K-Line (KWP2000 on 7-pin round diagnostic port) : [OBD] Port=COM1 Hardware=INTERFACE Protocol=KWP2000 Baudrate=9600 Retry=ON

For DCAN (USB cable on 16-pin OBD-II) : [OBD] Port=USB Hardware=DCAN Protocol=KWP2000 Baudrate=500000 Retry=ON

Deep note: 6.4.3 does not auto-switch baudrate for newer cars (e.g., 500k for D-CAN). You must match cable firmware and car generation. 3.3 ECU.INI – per-ECU overrides If certain ECUs need different timing/speed: [DME] TimeoutConnect=5000 Baudrate=9600 [EGS] TimeoutConnect=8000 Baudrate=9600 Key components: EDIABAS

3.4 IFHSRV.INI – remote interface (ICOM / EDIC network) For ICOM over Ethernet: [REMOTE] IP=192.168.0.1 Port=6801 Timeout=3000

4. Understanding .PRG vs .IPO vs .GRP | File | Purpose | Location | |------|---------|----------| | .PRG | Binary ECU interpreter (contains jobs like lesen_fgst , status_motor ) | ECU\ | | .IPO | INPA-specific job list with UI mapping (text, units) | SGDAT\ | | .GRP | Group file for INPA menu | SGDAT\ | When you select an ECU in INPA, EDIABAS loads the corresponding .PRG from ECU\ – e.g., MSV70.PRG for DME. Important: EDIABAS 6.4.3 has a .PRG limitation – it doesn’t support newer UDS protocols (most cars after ~2008 need partial workaround or switch to ISTA). For UDS, you need PRG files from later EDIABAS (7.x) but they often break.