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
• DC/DC converter for improved power consumption
• With additional CPU heat sink for over temperature protection
• OpenWrt operating system
• LuCi web interface
• Firmware update possible via web interface
• DHCP server
• ESSID: Deep OBD BMW
• Default Wifi password: deepobdbmw
• Default IP address: 192.168.100.1
• Default root password: root
• At the moment a new power supply concept is in preparation, by replacing the DC/DC converters with a TPS560200, that is able to use a maximum power supply voltage of 17V. The feedback resistors have to be changed to 49.9K/20K and 61.9K/20K because the feedback voltage is different. Additionally one input capacitor has to be replaced with a higher voltage type.

Buy an adapter

New adapters are available.
You could buy the ENET WiFi adapter from EBAY.
For BMW pre F-models use the Bluetooth adapter

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, Tool32 or ISTA-D 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 (recommended, but not required)
2. Optionally connect the ENET adapter with the PC. The PC automatically gets an IP address from the adapter DHCP server.
3. Download the latest Binary package and extract the .zip file. Start Api32\EdiabasLibConfigTool.exe and follow the instructions in the status window: Search the adapter, select it, optionally click Connect, click Check Connection and patch the required EDIABAS installations.
4. For ISTA-D: You have to select the EDIABAS\bin directory inside ISTA-D first.
5. Optionally you could also open the adapter configuration page in the web browser.
6. For ISTA-D: In Administration -> VCI Config select as Interface type: Ediabas default settings (ediabas.ini)

Project Description
.NET BMW and VAG Ediabas interpreter library

The project has now completely moved to GitHub https://github.com/uholeschak/ediabaslib, there will be no further changes here!

Features

This .NET assembly is small and fast replacement for the BWM and VAG 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.
Now a variant that can be used with cars from the VAG group has been released, but it requires an adapter with the replacement firmware for ELM327. In this mode the protocols KWP2000, KWP1281 and TP2.0 are supported (cars until 4.2012).

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 and VAG

Additionally an Android application Deep OBD for BMW and VAG 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, including VAG KWP2000, KWP1281 and TP2.0). Programmed adapters are now available.

• Custom Bluetooth D-CAN/K-Line adapter (BMW-FAST protocol over D-CAN and K-Line)
• ENET WiFi adapters (for BMW F-models)

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.