ediabaslib

Properties of the EdiabasLib.config file

Current EDIABAS emulation version is 7.6.0.
The EdiabasLib.config file is a replacement for the standard EDIABAS.INI file. It must be located in the same directory as the EdiabasLib.dll, Api32.dll or Api64.dll file.
The following properties could be specified in this file:

Standard properties

• Interface: Interface to use: STD:OBD, ADS (ADS operates also with FTDI USB converter) or ENET.
• ApiTrace: API debug level (0..1)
• IfhTrace: Interface debug level (0..3)
• TraceBuffering: 1=Enable buffering of API trace files
• EcuPath: Path to the ecu files
• RetryComm: 1=Retry communication
• EnetRemoteHost: Remote host for ENET protocol. Possible values are:
  • ip address:<protocol>:<diag port>:<control port>: No broadcast, directly connect to specified host. Optionally the protcol (HSFZ or DoIP) and the communication ports could be specified.
  • auto: Broadcast to subnet HostIdentService, Identical to EDIABAS RemoteHost = Autodetect. When multiple network adapters are present, this may work unreliable. Use auto:all instead.
  • auto:all: Broadcast to all network interfaces.
  • auto:<interface name>: Broadcast to all interfaces that start with <interface name> (case ignored).
• EnetVehicleProtocol, VehicleProtocol: Order of vehicle protocols used, separated by comma. Possible vales are HSFZ and DoIP.
• EnetHostIdentService, HostIdentService: IPv4 netmask for vehicle searching. Default is 255.255.255.255. This has changed with Ediabas 7.6.0.
• EnetTesterAddress: Tester address for HSFZ protocol, standard is the hex value 0xF4.
• EnetDoIPTesterAddress, DoIPTesterAddress: Tester address for DoIP protocol with optional 0x prefix, default is the hex value 0EF3.
• EnetDoipGatewayAddress, DoipGatewayAddress: Gateway address for DoIP protocol with optional 0x prefix, default is the hex value 0010.
• EnetControlPort, ControlPort: Control port for HSFZ protocol, standard port is 6811.
• EnetDiagnosticPort, DiagnosticPort: Diagnostic port for HSFZ protocol, standard port is 6801.
• EnetDoIPPort, DoIPPort: Port for DoIP protocol, standard port is 13400
• EnetTimeoutConnect, TimeoutConnect: Connect timeout for ENET protocol, default is 5000

When using BMW ICOM, change the values of EnetControlPort and EnetDiagnosticPort to the output from the BMW ICOM web interface line:
Example: Diag Addr: 0x10 Diagnostic Port: 50160 Control Port: 50161
For automatic ICOM allocation set EnetIcomAllocate to 1, otherwise manual allocation via iToolRadar or the web interface is required!
Web interface URL: http://XXXX:60080/cgi-bin/channeldeviceconfig.cgi
Login user name: root
Login password: NZY11502 or NZY1150263
The standard ICOM configuration page could be found at: http://XXXX:58000 (no login required).

Non standard properties

• ObdComPort: COM port name for OBD interface.
• AdsComPort: COM port name for ADS interface (if not specified ObdComPort will be used).
• AppendTrace: 0=Override old log file, 1=Always append the logfiles.
• LockTrace: 0=Allow changing IfhTrace level from the application, 1=Prevent changing the IfhTrace level from the application.
• CompatMode: EDIABAS 7.6.0 has incomplatible changes in mathematical function. This prevents using old ECU files. Setting this value to 1 (what is the default), keeps the behaviour of EDIABAS 7.3.0.
• EnetAddRecTimeout: Additional ENET standard additional receive timeout, default is 1000
• EnetAddRecTimeoutIcom: Additional ENET ICOM additional receive timeout, default is 2000
• EnetIcomAllocate: 1=Allocate ICOM before connecting, default is 0. This parameter is only used, if the diagnostic port has been set.

FTDI D2XX driver properties

For improved timing (especially required for ADS adapter) it’s possible to access the FTDI D2XX driver directly. Android also supports access to FTDI USB D-CAN/K-Line adapters. To activate this mode use FTDI instead of COM in the com port name for ObdComPort or AdsComPort. There are multiply ways the select the USB device:

• FTDIx: select device by index x (starting with 0)
• FTDI:SER=[serial number](serial-number): select device by serial number
• FTDI:DESC=[description](description): select device by description (not supported for Android)
• FTDI:LOC=[location](location): select device by location id (either decimal or hex with 0x) (not supported for Android) To get the device location information you could use FT Prog from the FTDI web site.

Bluetooth (Android)

Since Android devices normally have no COM ports, it’s possible to connect via Bluetooth using the Bluetooth Serial Port Protocol (SPP). To select a specific Bluetooth device use BLUETOOTH:<device address>.
When using ELM327 adapters append ;ELM327 after the Bluetooth address to specify ELM327 mode. For adapters that simply send data without modification append ;RAW.

Bluetooth (PC)

It’s possible to use the Replacement firmware for ELM327 also with a PC. When connecting the adapter with the PC two serial COM ports are created (incoming and outgoing). To use the adapter specify STD:OBD for the interface and BLUETOOTH:<outgoing COM port> or BLUETOOTH:<device address> for ObdComPort.
The recommended way for setting up the configuration is to use the EdiabasLibConfigTool.

WiFi

For WiFi based ELM327 adapters you have to specify STD:OBD for the interface and ELM327WIFI for ObdComPort.
When using the Replacement firmware for ELM327 with WiFi devices specify DEEPOBDWIFI for ObdComPort.

This site is open source. Improve this page.