Quantcast
Channel: EdiabasLib Wiki Rss Feed
Viewing all 162 articles
Browse latest View live
↧

Updated Wiki: Replacement firmware for ELM327

April 8, 2016, 4:06 pm
$
0
0

Replacement firmware for ELM327

There is now a replacement firmware available for ELM327 based Bluetooth adapters, that has the following advantages over the standard firmware:
  • Faster and more stable CAN communication.
  • K-Line support (all protocols).
  • Contains a bootstrap loader that allows firmware update without opening the device.
  • Firmware updates are possible with Deep OBD for BMW.
  • Reduced power consumption due to use of sleep mode.
  • Two firmware versions are available:
    • Unmodified Bluetooth adapter: Baud rate 38400.
    • Modified Bluetooth adapter (recommended) with replaced OpenSource Bluetooth firmware: Baud rate 115200 and alterable Bluetooth pin (16 digits) and name (31 chars).
Bluetooth adapter topBluetooth adapter bottom

Buy an adapter

New adapters are available.
You could buy the Bluetooth adapter from EBAY.

Factory reset

Beginning with firmware version 0.6 there is the possibility to perform a factory reset of the adapter. This resets the Bluetooth pin to 1234, the Bluetooth name to Deep OBD BMW and the mode to D-CAN.
To perform the factory reset you have to open the adapter and connect the unused pad of R26 with GND during power on.

Use the adapter with INPA or Tool32

You could use the Bluetooth adapter on a windows PC with INPA or Tool32 as a replacement for a OBD or ADS adapter. The following steps are required to establish the connection:
  1. Install .NET framework 4.0 or higher and VS2015 C++ runtime
  2. Connect the Bluetooth adapter with the PC (the default Bluetooth pin is 1234). Two COM ports are generated (incoming and outgoing).
  3. With the standard DCAN.exe from dcan_Tools (for configuration of the USB adapters) set the operation mode (D-CAN or K-LINE) of the Bluetooth adapter. For the COM port use the outgoing port.
  4. Rename the api32.dll in the C:\Ediabas\bin directory.
  5. Copy Api32.dll and EdiabasLib.config to the C:\Ediabas\bin directory.
  6. Modify the following entries in EdiabasLib.config:
<add key="Interface" value="STD:OBD"/>
<add key="ObdComPort" value="BLUETOOTH:<Outgoing COM port>"/>

Programming of the processor

For the first programming of the processor simply attach a PICKit 3 programmer to the corresponding test points of the circuit board.
The source for the firmware could be found in the subdirectory CanAdapterElm. In this subdirectory there is also a flash tool (subdirectory UpdateLoader) that allows firmware updates using the bootstrap loader once the firmware is programed.
The latest firmware version will be always included in Deep OBD for BMW.
↧
Search

Updated Wiki: Deep OBD for BMW

April 12, 2016, 4:29 am
$
0
0

Deep OBD for BMW

This page describes how to use Deep OBD for BMW.
Download app from Google Play: https://play.google.com/store/apps/details?id=de.holeschak.bmw_deep_obd
Table of contents:

Supported adapters

Deep OBD for BMW supports several OBD II adapters:
  • Standard FTDI based USB "INPA compatible" D-CAN/K-Line adapters (all protocols)
  • ELM327 based Bluetooth and WiFi adapters. Recommended ELM327 versions are 1.4b, 1.5 and origin 2.1, which are based on PIC18F2480 processor (no MCP2515 chip) (D-CAN protocol only)
  • Custom Bluetooth D-CAN/K-Line adapter (BMW-FAST protocol over D-CAN and K-Line)
  • ELM327 based adapters with Replacement firmware for ELM327 D-CAN and K-Line (all protocols!)

First start

At the first start of Deep OBD for BMW you will be asked to download the ECU files. The file package is very large (100MB) and requires approximately 1GB on the external SDCard after extraction.
In the next step a configuration (*.cccfg file) must be created. The easiest way to do so is to use the configuration generator. For complex scenarios you could manually create configuration files (see HowTo create BMW deep OBD pages). After loading and compiling the configuration file, all tabs included in the file will be visible on the main page.
Before connecting to the vehicle a Bluetooth adapter has to be selected (or you will be asked when connecting). It's recommended to pair the adapter in the android Bluetooth menu before using it in Deep OBD for BMW, because this way a connection password could be assigned.

E61Bt.cccfgSelect Bluetooth device

The main menu

The application has a configuration menu with the following options:
  • Device: With this menu the Bluetooth adapter could be selected. If the device is not coupled already, searching for new devices is possible. This menu is only enabled if a configuration with interface type BLUETOOTH has been selected.
  • Adapter configuration: When using a FTDI USB or Bluetooth (non ELM327) adapter, this menu item opens the adapter configuration page. The following settings are available (depending from adapter type):
    • CAN baud rate: (500kbit/100kbit) or K-Line (CAN off)
    • Separation time: Separation time between CAN telegrams. The default is 0, only change this value if there are communication problems.
    • Block size: Size of CAN telegram blocks. The default is 0, only change this value if there are communication problems.
    • Firmware update: If a new firmware is available for the adapter, the update could be initiated with this button.
  • Configuration generator: Simple XML configuration files could be generated automatically using the informations obtained from the vehicle. This menu opens the configuration generator which allows to create new or modify existing XML files by simply selecting the ECU and job informations.
  • Configuration: This menu allows the selection of the configuration file (*.cccfg file). When using the configuration generator the configuration is selected automatically. After selection the file will be compiled.
  • Ediabas tool: This is a port of the tool32.exe windows application. Selecting the menu will open the Ediabas tool page.
  • Storage media: If the default storage media for the ECU files is not appropriate, a different media could be selected in this sub menu. The application storage directory on the media will be always fixed to de.holeschak.bmw_deep_obd.
  • Download ECU files: Since the BMW ECU files are very large (100MB), they are not included in the application package. When starting the application for the first time the ECU file download is requested automatically. With this menu entry the file download could be initiated manually if the ECU files are damaged.
  • Data logging: Selecting this menu entry will open a sub menu with multiple data logging options:
    • Create trace file: If the checkbox of this menu is active, a ifh.trc file will be created when the application is connected. The trace file will be created in the Log subdirectory.
    • Append trace file: If this checkbox is enabled the trace file is always appended. Otherwise the trace file will be overridden after selection of a new configuration or restart of the application.
    • Log data: This checkbox enables logging of the display data to a log file. Only those lines are logged, that have a log_tag property in the configuration file. The logfile property in the page node has to be specified as well to activate logging. When using the configuration generatorlog_tag is set by default to the job name and logfile to the ECU name. Data will be logged in the Log subdirectory.
  • Online help: Displays this help page.
  • App info: Displays the app version and unique id.
Menu
Below are some screenshots from the example E61 configuration:

Motor pageMotor pageMotor pageMotor page

Log and trace files location

The location of the log and trace files depends from the Android version.
Beginning with Android KitKat (4.4) writing to the external SdCard is not possible any more. For older Android versions log and trace files are stored in a subdirectory relative to de.holeschak.bmw_deep_obd on the external SDCard. For KitKat and above the data could be found in the directory Android\data\de.holeschak.bmw_deep_obd\files of the external SDCard.
The standard log files are stored in the subdirectory Log, whereas the Ediabas tool uses the subdirectory LogEdiabasTool and the configuration generator the subdirectory LogConfigTool.

Background image

It's possible to replace the background image. Simply store a custom Background.jpg file in the subdirectory Images of the current de.holeschak.bmw_deep_obd data directory.
↧
↧

Updated Wiki: EdiabasLib.config file

April 12, 2016, 11:45 pm
$
0
0

Properties of the EdiabasLib.config file

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 or Api32.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: No broadcast, directly connect to specified host.
    • auto: Broadcast to 169.254.255.255, Identical to EDIABAS "RemoteHost = Autodetect.
    • auto:all: Broadcast to all network interfaces.
    • auto:<interface name>: Broadcast to all interfaces that start with <interface name> (case ignored).
  • EnetTesterAddress: Tester address for ENET protocol, standard is 0xF4
  • EnetControlPort: Control port for ENET protocol, standard is 6811
  • EnetDiagnosticPort: Diagnostic port for ENET protocol, standard is 6801

Non standard properties

  • ObdComPort: COM port name for OBD interface.
  • AdsComPort: COM port name for ADS interface (if not specifed 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.

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]: select device by serial number
  • FTDI:DESC=[description]: select device by description (not supported for Android)
  • FTDI:LOC=[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> instead of COMx.
When using ELM327 adapters append ";ELM327" after the Bluetooth address to specify ELM327 mode.

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> for ObdComPort.

ELM327 WiFi

It's possible to use an ELM327 WiFi adapter. For this specify STD:OBD for the interface and ELM327WIFI for ObdComPort_.
↧

Updated Wiki: EdiabasLib.config file

April 12, 2016, 11:46 pm
$
0
0

Properties of the EdiabasLib.config file

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 or Api32.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: No broadcast, directly connect to specified host.
    • auto: Broadcast to 169.254.255.255, Identical to EDIABAS "RemoteHost = Autodetect.
    • auto:all: Broadcast to all network interfaces.
    • auto:<interface name>: Broadcast to all interfaces that start with <interface name> (case ignored).
  • EnetTesterAddress: Tester address for ENET protocol, standard is 0xF4
  • EnetControlPort: Control port for ENET protocol, standard is 6811
  • EnetDiagnosticPort: Diagnostic port for ENET protocol, standard is 6801

Non standard properties

  • ObdComPort: COM port name for OBD interface.
  • AdsComPort: COM port name for ADS interface (if not specifed 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.

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]: select device by serial number
  • FTDI:DESC=[description]: select device by description (not supported for Android)
  • FTDI:LOC=[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> instead of COMx.
When using ELM327 adapters append ";ELM327" after the Bluetooth address to specify ELM327 mode.

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> for ObdComPort.

ELM327 WiFi

It's possible to use an ELM327 WiFi adapter. You have to specify STD:OBD for the interface and ELM327WIFI for ObdComPort.
↧

Updated Wiki: Home

April 12, 2016, 11:46 pm
$
0
0
Project Description
.NET BMW Ediabas interpreter library

Features

This .NET assembly is small and fast replacement for the BWM Ediabas toolset.
It's running on all platforms that support .NET framework (Windows, Windows CE, Mono).
The code is speed optimized, but improved for multiple calls of the same job.
This means the first job call is slow and the next are faster.

The library can directly read and interpret .GRP and .PRG files, the internal interface is similar to the EDIABAS API or the Tool32.exe GUI interface.
At the moment the D-CAN, BMW-FAST, KWP-2000*, KWP-2000 BMW, DS2, DS1, Concept 3, ISO9141 (Concept 2) and Concept 1 concepts are supported. If you send me EDIABAS log files from other concepts I could add them if possible.

For testing there is a console application EdiabasTest with command line parameters.
More informations could be found in the Documentation section.

Binary Compatibility

A binary compatible api32.dll wrapper is existing, it's possible to replace the existing EDIABAS api32.dll with the EdiabasLib api32.dll and the applications are still working (The dll requires .NET framework 4.0 or higher and VS2015 C++ runtime to be installed)!
This has been tested with Tool32, INPA and Rheingold. Since EdiabasNet is ignoring the EDIABAS.INI file you have to put your own EdiabasLib.config in the api32.dll directory.

A compatible apiNET32.dll is also available, so it should be easy to port existing .NET applications that use the original EDIABAS library.

Android

Now there is also a library existing that is working with Mono for Android. For communication either FTDI USB or Bluetooth Serial Port Protocol (SSP) protocol could be used.

Deep OBD for BMW

Additionally an Android application Deep OBD for BMW is existing, that is configurable via XML. Generation of XML code could be simplified with the integrated configuration generator.
Download app from Google Play: https://play.google.com/store/apps/details?id=de.holeschak.bmw_deep_obd
Deep OBD for BMW supports several OBD II adapters:
  • Standard FTDI based USB "INPA compatible" D-CAN/K-Line adapters (all protocols)
  • ELM327 based Bluetooth and WiFi adapters. Recommended ELM327 versions are 1.4b, 1.5 and origin 2.1, which are based on PIC18F2480 processor (no MCP2515 chip) (D-CAN protocol only)
  • ELM327 based adapters with Replacement firmware for ELM327 D-CAN and K-Line (all protocols!). Programmed adapters are now available.
Bluetooth adapter top
BMW deep OBD

Hints

At the moment most BEST/1 commands are implemented, but a few are still missing.
The implemented commands are automatically tested and compared with EDIABAS output.
Because I have no BEST/1 command specification some commands are only guessed. If someone could supply me with a BEST/1 specification I could improve the library.
↧
↧

Updated Wiki: Replacement firmware for ELM327

April 18, 2016, 2:14 pm
$
0
0

Replacement firmware for ELM327

There is now a replacement firmware available for ELM327 based Bluetooth adapters, that has the following advantages over the standard firmware:
  • Faster and more stable CAN communication.
  • K-Line support (all protocols).
  • Contains a bootstrap loader that allows firmware update without opening the device.
  • Firmware updates are possible with Deep OBD for BMW.
  • Reduced power consumption due to use of sleep mode.
  • Two firmware versions are available:
    • Unmodified Bluetooth adapter: Baud rate 38400.
    • Modified Bluetooth adapter (recommended) with replaced OpenSource Bluetooth firmware: Baud rate 115200 and alterable Bluetooth pin (16 digits) and name (31 chars).
Bluetooth adapter topBluetooth adapter bottom

Buy an adapter

All adapters are sold at the moment. I will prepare new adapters soon.
You could buy the Bluetooth adapter from EBAY.

Factory reset

Beginning with firmware version 0.6 there is the possibility to perform a factory reset of the adapter. This resets the Bluetooth pin to 1234, the Bluetooth name to Deep OBD BMW and the mode to D-CAN.
To perform the factory reset you have to open the adapter and connect the unused pad of R26 with GND during power on.

Use the adapter with INPA or Tool32

You could use the Bluetooth adapter on a windows PC with INPA or Tool32 as a replacement for a OBD or ADS adapter. The following steps are required to establish the connection:
  1. Install .NET framework 4.0 or higher and VS2015 C++ runtime
  2. Connect the Bluetooth adapter with the PC (the default Bluetooth pin is 1234). Two COM ports are generated (incoming and outgoing).
  3. With the standard DCAN.exe from dcan_Tools (for configuration of the USB adapters) set the operation mode (D-CAN or K-LINE) of the Bluetooth adapter. For the COM port use the outgoing port.
  4. Rename the api32.dll in the C:\Ediabas\bin directory.
  5. Copy Api32.dll and EdiabasLib.config to the C:\Ediabas\bin directory.
  6. Modify the following entries in EdiabasLib.config:
<add key="Interface" value="STD:OBD"/>
<add key="ObdComPort" value="BLUETOOTH:<Outgoing COM port>"/>

Programming of the processor

For the first programming of the processor simply attach a PICKit 3 programmer to the corresponding test points of the circuit board.
The source for the firmware could be found in the subdirectory CanAdapterElm. In this subdirectory there is also a flash tool (subdirectory UpdateLoader) that allows firmware updates using the bootstrap loader once the firmware is programed.
The latest firmware version will be always included in Deep OBD for BMW.
↧

Updated Wiki: Replacement firmware for ELM327

April 19, 2016, 2:50 am
$
0
0

Replacement firmware for ELM327

There is now a replacement firmware available for ELM327 based Bluetooth adapters, that has the following advantages over the standard firmware:
  • Faster and more stable CAN communication.
  • K-Line support (all protocols).
  • Contains a bootstrap loader that allows firmware update without opening the device.
  • Firmware updates are possible with Deep OBD for BMW.
  • Reduced power consumption due to use of sleep mode.
  • Two firmware versions are available:
    • Unmodified Bluetooth adapter: Baud rate 38400.
    • Modified Bluetooth adapter (recommended) with replaced OpenSource Bluetooth firmware: Baud rate 115200 and alterable Bluetooth pin (16 digits) and name (31 chars).
Bluetooth adapter topBluetooth adapter bottom

Buy an adapter

Adapters are available again!
You could buy the Bluetooth adapter from EBAY.

Factory reset

Beginning with firmware version 0.6 there is the possibility to perform a factory reset of the adapter. This resets the Bluetooth pin to 1234, the Bluetooth name to Deep OBD BMW and the mode to D-CAN.
To perform the factory reset you have to open the adapter and connect the unused pad of R26 with GND during power on.

Use the adapter with INPA or Tool32

You could use the Bluetooth adapter on a windows PC with INPA or Tool32 as a replacement for a OBD or ADS adapter. The following steps are required to establish the connection:
  1. Install .NET framework 4.0 or higher and VS2015 C++ runtime
  2. Connect the Bluetooth adapter with the PC (the default Bluetooth pin is 1234). Two COM ports are generated (incoming and outgoing).
  3. With the standard DCAN.exe from dcan_Tools (for configuration of the USB adapters) set the operation mode (D-CAN or K-LINE) of the Bluetooth adapter. For the COM port use the outgoing port.
  4. Rename the api32.dll in the C:\Ediabas\bin directory.
  5. Copy Api32.dll and EdiabasLib.config to the C:\Ediabas\bin directory.
  6. Modify the following entries in EdiabasLib.config:
<add key="Interface" value="STD:OBD"/>
<add key="ObdComPort" value="BLUETOOTH:<Outgoing COM port>"/>

Programming of the processor

For the first programming of the processor simply attach a PICKit 3 programmer to the corresponding test points of the circuit board.
The source for the firmware could be found in the subdirectory CanAdapterElm. In this subdirectory there is also a flash tool (subdirectory UpdateLoader) that allows firmware updates using the bootstrap loader once the firmware is programed.
The latest firmware version will be always included in Deep OBD for BMW.
↧

Updated Wiki: Replacement firmware for ELM327

April 19, 2016, 3:54 pm
$
0
0

Replacement firmware for ELM327

There is now a replacement firmware available for ELM327 based Bluetooth adapters, that has the following advantages over the standard firmware:
  • Faster and more stable CAN communication.
  • K-Line support (all protocols).
  • Contains a bootstrap loader that allows firmware update without opening the device.
  • Firmware updates are possible with Deep OBD for BMW.
  • Reduced power consumption due to use of sleep mode.
  • Two firmware versions are available:
    • Unmodified Bluetooth adapter: Baud rate 38400.
    • Modified Bluetooth adapter (recommended) with replaced OpenSource Bluetooth firmware: Baud rate 115200 and alterable Bluetooth pin (16 digits) and name (31 chars).
Bluetooth adapter topBluetooth adapter bottom

Buy an adapter

Adapters are available again!
You could buy the Bluetooth adapter from EBAY.

Factory reset

Beginning with firmware version 0.6 there is the possibility to perform a factory reset of the adapter. This resets the Bluetooth pin to 1234, the Bluetooth name to Deep OBD BMW and the mode to D-CAN.
To perform the factory reset you have to open the adapter and connect the unused pad of R26 with GND during power on.

Use the adapter with INPA or Tool32

You could use the Bluetooth adapter on a windows PC with INPA or Tool32 as a replacement for a OBD or ADS adapter. The following steps are required to establish the connection:
  1. Install .NET framework 4.0 or higher and VS2015 C++ runtime
  2. Connect the Bluetooth adapter with the PC (the default Bluetooth pin is 1234). Two COM ports are generated (incoming and outgoing).
  3. With the standard DCAN.exe from dcan_Tools (for configuration of the USB adapters) set the operation mode (D-CAN or K-LINE) of the Bluetooth adapter. For the COM port use the outgoing port.
  4. Rename the api32.dll in the C:\Ediabas\bin and C:\ISTA-D\Ediabas\bin directory.
  5. Copy Api32.dll and EdiabasLib.config to the C:\Ediabas\bin and C:\ISTA-D\Ediabas\bin directory.
  6. Modify the following entries in EdiabasLib.config:
<add key="Interface" value="STD:OBD"/>
<add key="ObdComPort" value="BLUETOOTH:<Outgoing COM port>"/>

Programming of the processor

For the first programming of the processor simply attach a PICKit 3 programmer to the corresponding test points of the circuit board.
The source for the firmware could be found in the subdirectory CanAdapterElm. In this subdirectory there is also a flash tool (subdirectory UpdateLoader) that allows firmware updates using the bootstrap loader once the firmware is programed.
The latest firmware version will be always included in Deep OBD for BMW.
↧
Search

Updated Wiki: Replacement firmware for ELM327

April 20, 2016, 1:15 pm
$
0
0

Replacement firmware for ELM327

There is now a replacement firmware available for ELM327 based Bluetooth adapters, that has the following advantages over the standard firmware:
  • Faster and more stable CAN communication.
  • K-Line support (all protocols).
  • Contains a bootstrap loader that allows firmware update without opening the device.
  • Firmware updates are possible with Deep OBD for BMW.
  • Reduced power consumption due to use of sleep mode.
  • Two firmware versions are available:
    • Unmodified Bluetooth adapter: Baud rate 38400.
    • Modified Bluetooth adapter (recommended) with replaced OpenSource Bluetooth firmware: Baud rate 115200 and alterable Bluetooth pin (16 digits) and name (31 chars).
Bluetooth adapter topBluetooth adapter bottom

Buy an adapter

Adapters are available again!
You could buy the Bluetooth adapter from EBAY.

Factory reset

Beginning with firmware version 0.6 there is the possibility to perform a factory reset of the adapter. This resets the Bluetooth pin to 1234, the Bluetooth name to Deep OBD BMW and the mode to D-CAN.
To perform the factory reset you have to open the adapter and connect the unused pad of R26 with GND during power on.

Use the adapter with INPA or Tool32

You could use the Bluetooth adapter on a windows PC with INPA or Tool32 as a replacement for a OBD or ADS adapter. The following steps are required to establish the connection:
  1. Install .NET framework 4.0 or higher and VS2015 C++ runtime
  2. Connect the Bluetooth adapter with the PC (the default Bluetooth pin is 1234). Two COM ports are generated (incoming and outgoing).
  3. With the standard DCAN.exe from dcan_Tools (for configuration of the USB adapters) set the operation mode (D-CAN or K-LINE) of the Bluetooth adapter. For the COM port use the outgoing port.
  4. Rename the api32.dll in the C:\Ediabas\bin and C:\ISTA-D\Ediabas\bin directory.
  5. Copy Api32.dll and EdiabasLib.config to the C:\Ediabas\bin and C:\ISTA-D\Ediabas\bin directory.
  6. Modify the following entries in EdiabasLib.config:
<add key="Interface" value="STD:OBD"/>
<add key="ObdComPort" value="BLUETOOTH:<Outgoing COM port>"/>

In Administration -> VCI Config select as Interface type: Ediabas default settings (ediabas.ini)

Programming of the processor

For the first programming of the processor simply attach a PICKit 3 programmer to the corresponding test points of the circuit board.
The source for the firmware could be found in the subdirectory CanAdapterElm. In this subdirectory there is also a flash tool (subdirectory UpdateLoader) that allows firmware updates using the bootstrap loader once the firmware is programed.
The latest firmware version will be always included in Deep OBD for BMW.
↧
↧

Updated Wiki: Replacement firmware for ELM327

April 20, 2016, 1:17 pm
$
0
0

Replacement firmware for ELM327

There is now a replacement firmware available for ELM327 based Bluetooth adapters, that has the following advantages over the standard firmware:
  • Faster and more stable CAN communication.
  • K-Line support (all protocols).
  • Contains a bootstrap loader that allows firmware update without opening the device.
  • Firmware updates are possible with Deep OBD for BMW.
  • Reduced power consumption due to use of sleep mode.
  • Two firmware versions are available:
    • Unmodified Bluetooth adapter: Baud rate 38400.
    • Modified Bluetooth adapter (recommended) with replaced OpenSource Bluetooth firmware: Baud rate 115200 and alterable Bluetooth pin (16 digits) and name (31 chars).
Bluetooth adapter topBluetooth adapter bottom

Buy an adapter

Adapters are available again!
You could buy the Bluetooth adapter from EBAY.

Factory reset

Beginning with firmware version 0.6 there is the possibility to perform a factory reset of the adapter. This resets the Bluetooth pin to 1234, the Bluetooth name to Deep OBD BMW and the mode to D-CAN.
To perform the factory reset you have to open the adapter and connect the unused pad of R26 with GND during power on.

Use the adapter with INPA or Tool32

You could use the Bluetooth adapter on a windows PC with INPA or Tool32 as a replacement for a OBD or ADS adapter. The following steps are required to establish the connection:
  1. Install .NET framework 4.0 or higher and VS2015 C++ runtime
  2. Connect the Bluetooth adapter with the PC (the default Bluetooth pin is 1234). Two COM ports are generated (incoming and outgoing).
  3. With the standard DCAN.exe from dcan_Tools (for configuration of the USB adapters) set the operation mode (D-CAN or K-LINE) of the Bluetooth adapter. For the COM port use the outgoing port.
  4. Rename the api32.dll in the C:\Ediabas\bin and C:\ISTA-D\Ediabas\bin directory.
  5. Copy Api32.dll and EdiabasLib.config to the C:\Ediabas\bin and C:\ISTA-D\Ediabas\bin directory.
  6. Modify the following entries in EdiabasLib.config:
  7. In Administration -> VCI Config select as Interface type: Ediabas default settings (ediabas.ini)
<add key="Interface" value="STD:OBD"/>
<add key="ObdComPort" value="BLUETOOTH:<Outgoing COM port>"/>

Programming of the processor

For the first programming of the processor simply attach a PICKit 3 programmer to the corresponding test points of the circuit board.
The source for the firmware could be found in the subdirectory CanAdapterElm. In this subdirectory there is also a flash tool (subdirectory UpdateLoader) that allows firmware updates using the bootstrap loader once the firmware is programed.
The latest firmware version will be always included in Deep OBD for BMW.
↧

Updated Wiki: Documentation

May 5, 2016, 4:31 am
↧

Updated Wiki: ENET WiFi Adapter

May 5, 2016, 4:50 am
$
0
0

ENET WiFi Adapter

For the BMW F-models there is a WiFi adapter available, that allows to communicate directly with the BMW ENET protocol. It is based on the hardware of an A5-V11 3G/4G Router. The adapter has the following features:
  • MediaTek/Ralink RT5350F processor with 350MHz
  • OpenWrt operating system
  • Luci web interface for configuration and status display.
  • Firmware update possible over the web interface
  • ESSID: Deep OBD BMW
  • Default ip address: 192.168.100.1
  • Default root password: root
  • Default Wifi password: deepobdbmw
ENET adapter closedENET adapter openWeb interface
↧

Updated Wiki: ENET WiFi Adapter

May 5, 2016, 4:51 am
$
0
0

ENET WiFi Adapter

For the BMW F-models there is a WiFi adapter available, that allows to communicate directly using the BMW ENET protocol.
It is based on the hardware of an A5-V11 3G/4G Router. The adapter has the following features:
  • MediaTek/Ralink RT5350F processor with 350MHz
  • OpenWrt operating system
  • Luci web interface for configuration and status display.
  • Firmware update possible over the web interface
  • ESSID: Deep OBD BMW
  • Default ip address: 192.168.100.1
  • Default root password: root
  • Default Wifi password: deepobdbmw
ENET adapter closedENET adapter openWeb interface
↧
↧

Updated Wiki: ENET WiFi Adapter

May 5, 2016, 4:57 am
$
0
0

ENET WiFi Adapter

For the BMW F-models there is a WiFi adapter available, that allows to communicate directly using the BMW ENET protocol.
It is based on the hardware of an A5-V11 3G/4G Router. The adapter has the following features:
  • MediaTek/Ralink RT5350F processor with 350MHz
  • OpenWrt operating system
  • Luci web interface for configuration and status display.
  • Firmware update possible over the web interface
  • DHCP server
  • ESSID: Deep OBD BMW
  • Default Wifi password: deepobdbmw
  • Default IP address: 192.168.100.1
  • Default root password: root
ENET adapter closedENET adapter openWeb interface

Use the adapter with INPA, Tool32 or ISTA-D

You could use the Bluetooth adapter on a windows PC with INPA or Tool32 as a replacement for an ENET adapter cable. The following steps are required to establish the connection:
  1. Install .NET framework 4.0 or higher and VS2015 C++ runtime
  2. Connect the ENET adapter with the PC. The PC automatically gets and IP address from the adapter DHCP server.
  3. Rename the api32.dll in the C:\Ediabas\bin and C:\ISTA-D\Ediabas\bin directory.
  4. Copy Api32.dll and EdiabasLib.config to the C:\Ediabas\bin and C:\ISTA-D\Ediabas\bin directory.
  5. In Administration -> VCI Config select as Interface type: Ediabas default settings (ediabas.ini)
  6. Modify the following entries in EdiabasLib.config:
<add key="Interface" value="ENET"/>
<add key="EnetRemoteHost" value="auto:all"/>

↧

Updated Wiki: Replacement firmware for ELM327

May 5, 2016, 5:00 am
$
0
0

Replacement firmware for ELM327

There is now a replacement firmware available for ELM327 based Bluetooth adapters, that has the following advantages over the standard firmware:
  • Faster and more stable CAN communication.
  • K-Line support (all protocols).
  • Contains a bootstrap loader that allows firmware update without opening the device.
  • Firmware updates are possible with Deep OBD for BMW.
  • Reduced power consumption due to use of sleep mode.
  • Two firmware versions are available:
    • Unmodified Bluetooth adapter: Baud rate 38400.
    • Modified Bluetooth adapter (recommended) with replaced OpenSource Bluetooth firmware: Baud rate 115200 and alterable Bluetooth pin (16 digits) and name (31 chars).
Bluetooth adapter topBluetooth adapter bottom

Buy an adapter

Adapters are available again!
You could buy the Bluetooth adapter from EBAY.

Factory reset

Beginning with firmware version 0.6 there is the possibility to perform a factory reset of the adapter. This resets the Bluetooth pin to 1234, the Bluetooth name to Deep OBD BMW and the mode to D-CAN.
To perform the factory reset you have to open the adapter and connect the unused pad of R26 with GND during power on.

Use the adapter with INPA, Tool32 or ISTA-D

You could use the Bluetooth adapter on a windows PC with INPA or Tool32 as a replacement for a OBD or ADS adapter. The following steps are required to establish the connection:
  1. Install .NET framework 4.0 or higher and VS2015 C++ runtime
  2. Connect the Bluetooth adapter with the PC (the default Bluetooth pin is 1234). Two COM ports are generated (incoming and outgoing).
  3. With the standard DCAN.exe from dcan_Tools (for configuration of the USB adapters) set the operation mode (D-CAN or K-LINE) of the Bluetooth adapter. For the COM port use the outgoing port.
  4. Rename the api32.dll in the C:\Ediabas\bin and C:\ISTA-D\Ediabas\bin directory.
  5. Copy Api32.dll and EdiabasLib.config to the C:\Ediabas\bin and C:\ISTA-D\Ediabas\bin directory.
  6. For ISTA-D: In Administration -> VCI Config select as Interface type: Ediabas default settings (ediabas.ini)
  7. Modify the following entries in EdiabasLib.config:
<add key="Interface" value="STD:OBD"/>
<add key="ObdComPort" value="BLUETOOTH:<Outgoing COM port>"/>

Programming of the processor

For the first programming of the processor simply attach a PICKit 3 programmer to the corresponding test points of the circuit board.
The source for the firmware could be found in the subdirectory CanAdapterElm. In this subdirectory there is also a flash tool (subdirectory UpdateLoader) that allows firmware updates using the bootstrap loader once the firmware is programed.
The latest firmware version will be always included in Deep OBD for BMW.
↧
Search

Updated Wiki: ENET WiFi Adapter

May 5, 2016, 5:01 am
$
0
0

ENET WiFi Adapter

For the BMW F-models there is a WiFi adapter available, that allows to communicate directly using the BMW ENET protocol.
It is based on the hardware of an A5-V11 3G/4G Router. The adapter has the following features:
  • MediaTek/Ralink RT5350F processor with 350MHz
  • OpenWrt operating system
  • Luci web interface for configuration and status display.
  • Firmware update possible over the web interface
  • DHCP server
  • ESSID: Deep OBD BMW
  • Default Wifi password: deepobdbmw
  • Default IP address: 192.168.100.1
  • Default root password: root
ENET adapter closedENET adapter openWeb interface

Use the adapter with INPA, Tool32 or ISTA-D

You could use the Bluetooth adapter on a windows PC with INPA or Tool32 as a replacement for an ENET adapter cable. The following steps are required to establish the connection:
  1. Install .NET framework 4.0 or higher and VS2015 C++ runtime
  2. Connect the ENET adapter with the PC. The PC automatically gets and IP address from the adapter DHCP server.
  3. Rename the api32.dll in the C:\Ediabas\bin and C:\ISTA-D\Ediabas\bin directory.
  4. Copy Api32.dll and EdiabasLib.config to the C:\Ediabas\bin and C:\ISTA-D\Ediabas\bin directory.
  5. For ISTA-D: In Administration -> VCI Config select as Interface type: Ediabas default settings (ediabas.ini)
  6. Modify the following entries in EdiabasLib.config:
<add key="Interface" value="ENET"/>
<add key="EnetRemoteHost" value="auto:all"/>

↧

Updated Wiki: ENET WiFi Adapter

May 5, 2016, 5:06 am
$
0
0

ENET WiFi Adapter

For the BMW F-models there is a WiFi adapter available, that allows to communicate directly using the BMW ENET protocol.
It is based on the hardware of an A5-V11 3G/4G Router. The adapter has the following features:
  • MediaTek/Ralink RT5350F processor with 350MHz
  • OpenWrt operating system
  • Luci web interface for configuration and status display.
  • Firmware update possible over the web interface
  • DHCP server
  • ESSID: Deep OBD BMW
  • Default Wifi password: deepobdbmw
  • Default IP address: 192.168.100.1
  • Default root password: root
ENET adapter closedENET adapter openWeb interface

Buy an adapter

The ENET WiFi adapter will be available on EBAY soon!

Factory reset

If the adapter gets unreachable after a misconfiguration there is a possibility to perform a factory reset.
You have to open the adapter and press the reset button after the adapter has booted.

Use the adapter with INPA, Tool32 or ISTA-D

You could use the Bluetooth adapter on a windows PC with INPA or Tool32 as a replacement for an ENET adapter cable. The following steps are required to establish the connection:
  1. Install .NET framework 4.0 or higher and VS2015 C++ runtime
  2. Connect the ENET adapter with the PC. The PC automatically gets and IP address from the adapter DHCP server.
  3. Rename the api32.dll in the C:\Ediabas\bin and C:\ISTA-D\Ediabas\bin directory.
  4. Copy Api32.dll and EdiabasLib.config to the C:\Ediabas\bin and C:\ISTA-D\Ediabas\bin directory.
  5. For ISTA-D: In Administration -> VCI Config select as Interface type: Ediabas default settings (ediabas.ini)
  6. Modify the following entries in EdiabasLib.config:
<add key="Interface" value="ENET"/>
<add key="EnetRemoteHost" value="auto:all"/>

↧
↧

Updated Wiki: Deep OBD for BMW

May 5, 2016, 5:09 am
$
0
0

Deep OBD for BMW

This page describes how to use Deep OBD for BMW.
Download app from Google Play: https://play.google.com/store/apps/details?id=de.holeschak.bmw_deep_obd
Table of contents:

Supported adapters

Deep OBD for BMW supports several OBD II adapters:
  • Standard FTDI based USB "INPA compatible" D-CAN/K-Line adapters (all protocols)
  • ELM327 based Bluetooth and WiFi adapters. Recommended ELM327 versions are 1.4b, 1.5 and origin 2.1, which are based on PIC18F2480 processor (no MCP2515 chip) (D-CAN protocol only)
  • Custom Bluetooth D-CAN/K-Line adapter (BMW-FAST protocol over D-CAN and K-Line)
  • ELM327 based adapters with Replacement firmware for ELM327 D-CAN and K-Line (all protocols!)
  • ENET WiFi adapter (BMW F-models)

First start

At the first start of Deep OBD for BMW you will be asked to download the ECU files. The file package is very large (100MB) and requires approximately 1GB on the external SDCard after extraction.
In the next step a configuration (*.cccfg file) must be created. The easiest way to do so is to use the configuration generator. For complex scenarios you could manually create configuration files (see HowTo create BMW deep OBD pages). After loading and compiling the configuration file, all tabs included in the file will be visible on the main page.
Before connecting to the vehicle a Bluetooth adapter has to be selected (or you will be asked when connecting). It's recommended to pair the adapter in the android Bluetooth menu before using it in Deep OBD for BMW, because this way a connection password could be assigned.

E61Bt.cccfgSelect Bluetooth device

The main menu

The application has a configuration menu with the following options:
  • Device: With this menu the Bluetooth adapter could be selected. If the device is not coupled already, searching for new devices is possible. This menu is only enabled if a configuration with interface type BLUETOOTH has been selected.
  • Adapter configuration: When using a FTDI USB or Bluetooth (non ELM327) adapter, this menu item opens the adapter configuration page. The following settings are available (depending from adapter type):
    • CAN baud rate: (500kbit/100kbit) or K-Line (CAN off)
    • Separation time: Separation time between CAN telegrams. The default is 0, only change this value if there are communication problems.
    • Block size: Size of CAN telegram blocks. The default is 0, only change this value if there are communication problems.
    • Firmware update: If a new firmware is available for the adapter, the update could be initiated with this button.
  • Configuration generator: Simple XML configuration files could be generated automatically using the informations obtained from the vehicle. This menu opens the configuration generator which allows to create new or modify existing XML files by simply selecting the ECU and job informations.
  • Configuration: This menu allows the selection of the configuration file (*.cccfg file). When using the configuration generator the configuration is selected automatically. After selection the file will be compiled.
  • Ediabas tool: This is a port of the tool32.exe windows application. Selecting the menu will open the Ediabas tool page.
  • Storage media: If the default storage media for the ECU files is not appropriate, a different media could be selected in this sub menu. The application storage directory on the media will be always fixed to de.holeschak.bmw_deep_obd.
  • Download ECU files: Since the BMW ECU files are very large (100MB), they are not included in the application package. When starting the application for the first time the ECU file download is requested automatically. With this menu entry the file download could be initiated manually if the ECU files are damaged.
  • Data logging: Selecting this menu entry will open a sub menu with multiple data logging options:
    • Create trace file: If the checkbox of this menu is active, a ifh.trc file will be created when the application is connected. The trace file will be created in the Log subdirectory.
    • Append trace file: If this checkbox is enabled the trace file is always appended. Otherwise the trace file will be overridden after selection of a new configuration or restart of the application.
    • Log data: This checkbox enables logging of the display data to a log file. Only those lines are logged, that have a log_tag property in the configuration file. The logfile property in the page node has to be specified as well to activate logging. When using the configuration generatorlog_tag is set by default to the job name and logfile to the ECU name. Data will be logged in the Log subdirectory.
  • Online help: Displays this help page.
  • App info: Displays the app version and unique id.
Menu
Below are some screenshots from the example E61 configuration:

Motor pageMotor pageMotor pageMotor page

Log and trace files location

The location of the log and trace files depends from the Android version.
Beginning with Android KitKat (4.4) writing to the external SdCard is not possible any more. For older Android versions log and trace files are stored in a subdirectory relative to de.holeschak.bmw_deep_obd on the external SDCard. For KitKat and above the data could be found in the directory Android\data\de.holeschak.bmw_deep_obd\files of the external SDCard.
The standard log files are stored in the subdirectory Log, whereas the Ediabas tool uses the subdirectory LogEdiabasTool and the configuration generator the subdirectory LogConfigTool.

Background image

It's possible to replace the background image. Simply store a custom Background.jpg file in the subdirectory Images of the current de.holeschak.bmw_deep_obd data directory.
↧

Updated Wiki: Deep OBD for BMW

May 5, 2016, 5:09 am
$
0
0

Deep OBD for BMW

This page describes how to use Deep OBD for BMW.
Download app from Google Play: https://play.google.com/store/apps/details?id=de.holeschak.bmw_deep_obd
Table of contents:

Supported adapters

Deep OBD for BMW supports several OBD II adapters:
  • Standard FTDI based USB "INPA compatible" D-CAN/K-Line adapters (all protocols)
  • ELM327 based Bluetooth and WiFi adapters. Recommended ELM327 versions are 1.4b, 1.5 and origin 2.1, which are based on PIC18F2480 processor (no MCP2515 chip) (D-CAN protocol only)
  • Custom Bluetooth D-CAN/K-Line adapter (BMW-FAST protocol over D-CAN and K-Line)
  • ELM327 based adapters with Replacement firmware for ELM327 D-CAN and K-Line (all protocols!)
  • ENET WiFi adapter (for BMW F-models)

First start

At the first start of Deep OBD for BMW you will be asked to download the ECU files. The file package is very large (100MB) and requires approximately 1GB on the external SDCard after extraction.
In the next step a configuration (*.cccfg file) must be created. The easiest way to do so is to use the configuration generator. For complex scenarios you could manually create configuration files (see HowTo create BMW deep OBD pages). After loading and compiling the configuration file, all tabs included in the file will be visible on the main page.
Before connecting to the vehicle a Bluetooth adapter has to be selected (or you will be asked when connecting). It's recommended to pair the adapter in the android Bluetooth menu before using it in Deep OBD for BMW, because this way a connection password could be assigned.

E61Bt.cccfgSelect Bluetooth device

The main menu

The application has a configuration menu with the following options:
  • Device: With this menu the Bluetooth adapter could be selected. If the device is not coupled already, searching for new devices is possible. This menu is only enabled if a configuration with interface type BLUETOOTH has been selected.
  • Adapter configuration: When using a FTDI USB or Bluetooth (non ELM327) adapter, this menu item opens the adapter configuration page. The following settings are available (depending from adapter type):
    • CAN baud rate: (500kbit/100kbit) or K-Line (CAN off)
    • Separation time: Separation time between CAN telegrams. The default is 0, only change this value if there are communication problems.
    • Block size: Size of CAN telegram blocks. The default is 0, only change this value if there are communication problems.
    • Firmware update: If a new firmware is available for the adapter, the update could be initiated with this button.
  • Configuration generator: Simple XML configuration files could be generated automatically using the informations obtained from the vehicle. This menu opens the configuration generator which allows to create new or modify existing XML files by simply selecting the ECU and job informations.
  • Configuration: This menu allows the selection of the configuration file (*.cccfg file). When using the configuration generator the configuration is selected automatically. After selection the file will be compiled.
  • Ediabas tool: This is a port of the tool32.exe windows application. Selecting the menu will open the Ediabas tool page.
  • Storage media: If the default storage media for the ECU files is not appropriate, a different media could be selected in this sub menu. The application storage directory on the media will be always fixed to de.holeschak.bmw_deep_obd.
  • Download ECU files: Since the BMW ECU files are very large (100MB), they are not included in the application package. When starting the application for the first time the ECU file download is requested automatically. With this menu entry the file download could be initiated manually if the ECU files are damaged.
  • Data logging: Selecting this menu entry will open a sub menu with multiple data logging options:
    • Create trace file: If the checkbox of this menu is active, a ifh.trc file will be created when the application is connected. The trace file will be created in the Log subdirectory.
    • Append trace file: If this checkbox is enabled the trace file is always appended. Otherwise the trace file will be overridden after selection of a new configuration or restart of the application.
    • Log data: This checkbox enables logging of the display data to a log file. Only those lines are logged, that have a log_tag property in the configuration file. The logfile property in the page node has to be specified as well to activate logging. When using the configuration generatorlog_tag is set by default to the job name and logfile to the ECU name. Data will be logged in the Log subdirectory.
  • Online help: Displays this help page.
  • App info: Displays the app version and unique id.
Menu
Below are some screenshots from the example E61 configuration:

Motor pageMotor pageMotor pageMotor page

Log and trace files location

The location of the log and trace files depends from the Android version.
Beginning with Android KitKat (4.4) writing to the external SdCard is not possible any more. For older Android versions log and trace files are stored in a subdirectory relative to de.holeschak.bmw_deep_obd on the external SDCard. For KitKat and above the data could be found in the directory Android\data\de.holeschak.bmw_deep_obd\files of the external SDCard.
The standard log files are stored in the subdirectory Log, whereas the Ediabas tool uses the subdirectory LogEdiabasTool and the configuration generator the subdirectory LogConfigTool.

Background image

It's possible to replace the background image. Simply store a custom Background.jpg file in the subdirectory Images of the current de.holeschak.bmw_deep_obd data directory.
↧

Updated Wiki: Home

May 5, 2016, 5:10 am
$
0
0
Project Description
.NET BMW Ediabas interpreter library

Features

This .NET assembly is small and fast replacement for the BWM Ediabas toolset.
It's running on all platforms that support .NET framework (Windows, Windows CE, Mono).
The code is speed optimized, but improved for multiple calls of the same job.
This means the first job call is slow and the next are faster.

The library can directly read and interpret .GRP and .PRG files, the internal interface is similar to the EDIABAS API or the Tool32.exe GUI interface.
At the moment the D-CAN, BMW-FAST, KWP-2000*, KWP-2000 BMW, DS2, DS1, Concept 3, ISO9141 (Concept 2) and Concept 1 concepts are supported. If you send me EDIABAS log files from other concepts I could add them if possible.

For testing there is a console application EdiabasTest with command line parameters.
More informations could be found in the Documentation section.

Binary Compatibility

A binary compatible api32.dll wrapper is existing, it's possible to replace the existing EDIABAS api32.dll with the EdiabasLib api32.dll and the applications are still working (The dll requires .NET framework 4.0 or higher and VS2015 C++ runtime to be installed)!
This has been tested with Tool32, INPA and Rheingold. Since EdiabasNet is ignoring the EDIABAS.INI file you have to put your own EdiabasLib.config in the api32.dll directory.

A compatible apiNET32.dll is also available, so it should be easy to port existing .NET applications that use the original EDIABAS library.

Android

Now there is also a library existing that is working with Mono for Android. For communication either FTDI USB or Bluetooth Serial Port Protocol (SSP) protocol could be used.

Deep OBD for BMW

Additionally an Android application Deep OBD for BMW is existing, that is configurable via XML. Generation of XML code could be simplified with the integrated configuration generator.
Download app from Google Play: https://play.google.com/store/apps/details?id=de.holeschak.bmw_deep_obd
Deep OBD for BMW supports several OBD II adapters:
  • Standard FTDI based USB "INPA compatible" D-CAN/K-Line adapters (all protocols)
  • ELM327 based Bluetooth and WiFi adapters. Recommended ELM327 versions are 1.4b, 1.5 and origin 2.1, which are based on PIC18F2480 processor (no MCP2515 chip) (D-CAN protocol only)
  • ELM327 based adapters with Replacement firmware for ELM327 D-CAN and K-Line (all protocols!). Programmed adapters are now available.
Bluetooth adapter top
BMW deep OBD

Hints

At the moment most BEST/1 commands are implemented, but a few are still missing.
The implemented commands are automatically tested and compared with EDIABAS output.
Because I have no BEST/1 command specification some commands are only guessed. If someone could supply me with a BEST/1 specification I could improve the library.
↧
Viewing all 162 articles
Browse latest View live
Search