Deep OBD App: Your Guide to VAG OBD2 Bluetooth Diagnostics

The Deep OBD app is a powerful tool for vehicle diagnostics, offering in-depth access to your car’s systems. This article will guide you on how to effectively use the Deep OBD app, with a particular focus on Vag Obd2 Bluetooth connectivity for Volkswagen, Audi, Skoda, and SEAT vehicles.

You can download the Deep OBD app from the Google Play Store: https://play.google.com/store/apps/details?id=de.holeschak.bmw_deep_obd

Understanding Manufacturers and VAG Support

The Deep OBD app is versatile, operating in both BMW and VAG modes. Initially, you need to select your car manufacturer within the app settings. While the app’s primary focus was initially BMW, it now includes an experimental VAG group mode to support Volkswagen, Audi, SEAT, and Skoda vehicles.

Currently, VAG support is focused on older protocols: KWP2000, KWP1281, and TP2.0. To utilize the VAG mode effectively, especially with Bluetooth, a replacement firmware for ELM327 adapters is often necessary. This firmware upgrade enhances the adapter’s compatibility with the VAG protocols.

Choosing the Right OBD2 Bluetooth Adapter for VAG Vehicles

Selecting the correct OBD2 adapter is crucial for successful communication between the Deep OBD app and your VAG vehicle. The app offers compatibility with several adapter types, but for VAG OBD2 Bluetooth specifically, certain considerations apply.

Here are the supported OBD2 adapters, with notes on VAG compatibility:

Standard FTDI based USB “INPA compatible” D-CAN/K-Line adapters: These are primarily designed for BMW and may not be ideal for VAG over Bluetooth.
ELM327 based Bluetooth and WiFi adapters: These are common and can work for VAG OBD2 Bluetooth, especially ELM327 versions 1.4b, 1.5, and original 2.1 (based on PIC18F25K80 processor, without MCP2515 chip). However, for full VAG protocol support, including KWP2000, KWP1281, and TP2.0, you’ll likely need an ELM327 adapter with replacement firmware. Standard ELM327 adapters typically only fully support CAN protocol, which may limit functionality with older VAG vehicles.
Custom Bluetooth D-CAN/K-Line adapter: While mentioned, this is more BMW-focused (“BMW-FAST protocol”) and less relevant for standard VAG OBD2 Bluetooth use.
ELM327 based adapters with Replacement firmware: This is the recommended adapter type for comprehensive VAG support. By flashing a replacement firmware onto your ELM327 adapter, you unlock full support for D-CAN and K-Line protocols, essential for older VAG vehicles and the Deep OBD app’s VAG mode. When you select “VAG” as the manufacturer in the Deep OBD app, using an adapter with replacement firmware becomes highly recommended for Bluetooth connectivity.
ENET WiFi adapters: These are designed for newer BMW F-models and are not relevant for VAG OBD2 Bluetooth diagnostics.

For detailed compatibility information, refer to: Supported adapter types

Getting Started with Deep OBD and Your VAG OBD2 Bluetooth Setup

When you launch the Deep OBD app for the first time, it will prompt you to extract ECU files. Be aware that these files are substantial, requiring approximately 2.5GB of storage on your device’s external SD card. Ensure you have a stable internet connection during this initial setup, as the app will also check for updates.

After the initial file extraction, you’ll need to create a configuration file (*.cccfg file). The easiest way to do this is using the app’s built-in configuration generator, which simplifies the process. For advanced users, manual configuration file creation is possible (see HowTo create Deep OBD pages).

Once your configuration file is loaded and compiled, the tabs defined in the configuration will appear on the main app screen. Before attempting to connect to your VAG vehicle via Bluetooth, ensure your Bluetooth adapter is selected within the app’s settings. It’s advisable to pre-pair your Bluetooth adapter in your Android device’s Bluetooth settings menu. This allows you to manage pairing passwords and ensures the adapter is recognized by your device.

Creating Your First VAG Configuration

Here’s a step-by-step guide to generate your first configuration for your VAG vehicle:

Access the Configuration generator from the Deep OBD app’s main menu.
Within the generator, select the appropriate interface type, which for VAG OBD2 Bluetooth will likely be “Bluetooth”. Choose your Bluetooth adapter if prompted.
Tap the “Read” button and wait for the ECU list to populate. This process retrieves data from your vehicle’s control units.
Select an ECU (Electronic Control Unit) from the list that you want to investigate.
On the subsequent page, choose a “job” (diagnostic function) and the corresponding “job result” for the data you wish to display on the main screen. Crucially, ensure you check the boxes next to the results you want to monitor. You can use the “Test” button to verify data reading.
Navigate back and select additional ECUs if needed, repeating steps 4 and 5.
Exit the Configuration generator. You’ll be prompted to save the configuration.
On the main app screen, you will now see tabs for the ECUs you selected, along with an “Error” tab for fault codes.
Press the “Connect” button in the app.
Select the tab corresponding to the ECU data you want to view.

Image: Selecting a Bluetooth device within the Deep OBD app.

Image: Example of an ECU list displayed in the Deep OBD app’s configuration generator.

Image: Job selection screen in the Deep OBD app, showing diagnostic functions.

Image: A sample “Motor” page within the Deep OBD app, displaying engine parameters.

Navigating the Main Menu for VAG Diagnostics

The Deep OBD app’s main menu provides access to various configuration options essential for VAG OBD2 Bluetooth diagnostics:

Manufacturer: This is the first setting to configure. Select “VAG” to switch the app to VAG mode for VW, Audi, Skoda, and SEAT vehicles. Remember that VAG mode is currently experimental and best suited for vehicles manufactured before 2017-08 and often requires a [Bluetooth D-CAN/K-Line adapter](Build Bluetooth D-CAN adapter.md) with replacement firmware for optimal functionality.
Device: Use this menu to select your Bluetooth adapter for wireless communication. If your adapter isn’t paired, you can initiate a device search from this menu. This option is enabled when a configuration using “BLUETOOTH” interface type is selected.
Adapter configuration: This menu is relevant for FTDI USB or non-ELM327 Bluetooth adapters (primarily BMW). It offers settings like:
- CAN baud rate: (500kbit/100kbit) or K-Line (CAN off)
- Separation time: Adjust this only if you experience communication issues.
- Block size: Adjust this only if you experience communication issues.
- Firmware update: For updating the adapter’s firmware (if available and supported).
ENET IP & Adapter IP: These settings are for ENET WiFi adapters and WiFi adapters respectively, not typically relevant for standard VAG OBD2 Bluetooth setups.
Configuration generator: As previously described, this opens the configuration generator for creating or modifying XML configuration files for ECU selections and diagnostic jobs. This is the easiest way to set up your VAG OBD2 Bluetooth configuration.
Configuration: This submenu provides options for managing configuration files:
- Select: Choose your configuration file (*.cccfg file). Configuration files created by the generator are automatically selected.
- Recent configurations: Access recently used configurations for quick switching.
- Edit: Edit the main configuration file (*.cccfg file) using an installed XML editor.
- Edit pages list & Edit current page: Options for advanced users to customize page layouts and elements within the configuration.
- Edit other file: Select and edit any configuration file (*.cccpage file).
- Reset XML editor: Resets the selected XML editor if you need to choose a different one.
- Close: Closes the current configuration.
Ediabas tool: This is a port of the tool32.exe Windows application (Ediabas tool), offering more advanced diagnostic capabilities.
Coding: Provides access to BMW coding online services (primarily BMW focused, VAG coding functionality may be limited or require specific configurations).
Extract ECU files: Allows you to re-extract ECU files if needed. Requires internet connection for update checks.
Data logging: Offers various data logging options for recording diagnostic sessions:
- Create trace file & Append trace file: For creating and managing trace files (*.ifh.trc) for detailed communication logging.
- Log data: Enables logging of displayed data to a log file, based on settings in your configuration file.
Translations: (For non-German languages) This menu manages automatic ECU text translation using translation APIs.
- Translate ECU text & Translation configuration: Configure automatic translation settings and API keys for services like Google Translate.
- Clear translation cache: Clears the translation cache to force re-translation.
Trace file: Submenu for managing trace files:
- Send trace file, Open trace file, Resend trace file, Open last trace file: Options for sending and accessing trace files for analysis or support.
Resend trace file: Retry sending the last trace file if it failed previously.
Global settings: Opens the global app settings page for general app preferences.
Online help: Displays this help page.
App info: Shows the app version and unique app ID.

Image: The main menu of the Deep OBD app, showcasing various options.

Below are additional screenshots illustrating the app’s interface with example configurations:

Image: Example of a “Motor” page displaying real-time engine data in the Deep OBD app.

Image: Graph view of engine parameters within the Deep OBD app’s “Motor” page.

Image: “Climate” control page in the Deep OBD app, showing climate system data.

Image: Example of an “Axis” data display page within the Deep OBD app.

Image: “Read All Errors” page in the Deep OBD app, displaying vehicle fault codes.

Google Translation APIs (Optional)

For users needing text translation within the app (especially for ECU descriptions), Deep OBD supports Google Translation APIs. While these APIs are publicly available, their reliability and availability can change. You can find potential API URLs within the translatepy project. You can copy and paste these URLs into the “Translation configuration” section of the Deep OBD app. Note that free translation services often have usage limits, and you may need to pay for higher volumes of text translation.

https://clients5.google.com/translate_a/t?client=dict-chrome-ex https://translate.googleapis.com/translate_a/single?client=gtx&dt=t

Locating Log and Trace Files

The location of log and trace files generated by the Deep OBD app depends on your Android version.

Older Android versions (pre-KitKat 4.4): Log and trace files are stored in a subdirectory within the de.holeschak.bmw_deep_obd directory on your external SD card.
Android KitKat (4.4) and later: Due to Android security restrictions, files are located in the directory Androiddatade.holeschak.bmw_deep_obdfiles on your external SD card.

Within these locations, standard log files reside in the Log subdirectory. Ediabas tool logs are in LogEdiabasTool, and configuration generator logs are in LogConfigTool. Backup trace files (if sending fails) are stored in TraceBackup.

Customizing the Background Image

You can personalize the Deep OBD app by replacing the default background image. To do this, create an “Images” subdirectory within de.holeschak.bmw_deep_obdfilesImages and place a custom image file named Background.jpg inside it.

Android Auto Integration

The Deep OBD app now includes Android Auto integration in its release version, enhancing usability within vehicles that support Android Auto.

Visual Studio Settings for Compilation (Developer Information)

This section is for developers who might be compiling the Deep OBD app and provides recommended Visual Studio Android settings. It is advisable to have Android Studio installed and configured beforehand for a consistent environment.

Java SDK location: Microsoft: C:Program FilesMicrosoftjdk-17.0.8.101-hotspot or custom: C:Program FilesJavajdk-11.0.12
Android SDK location: C:Users<user>AppDataLocalAndroidandroid-sdk</user> (Replace <user> with your username)
Archive location: C:Users<user>AppDataLocalXamarinMono for AndroidArchives</user> (Replace <user> with your username)
Activate option: Keep application cache
Activate option: Install Android SDK automatically
Deactivate option: Use AndroidX migrator
Extra -> Android -> Android SDK Manager: Enable Repository complete list (if Android Studio is installed).