Firmware & Software

App Compatibility + Version Identification

Validate app compatibility for Drove West Bluetooth OBD2 adapters, identify device versions for faster support, and understand our update & version-control approach for OEM programs.

Submit a Version Question Submit a Support Ticket

CONNECTION REFERENCE

Bluetooth / BLE Connection Types

Use this table to match the adapter to the app's connection method and avoid unnecessary troubleshooting.

Wireless Model	Communication Method	Compatibility Note
V011	Bluetooth 5.x (revision may vary)	Confirm your unit's revision if your app requires a specific mode
V015	Bluetooth 4.0	Typically used for mainstream third-party app workflows
V019	Bluetooth 4.0	Often selected for stability-focused third-party app sessions
V020	Bluetooth 2.0/4.0 or BLE (revision may vary)	If pairing fails, confirm hardware revision and required app mode
DA100	Bluetooth 4.0 / Bluetooth 5.4 / BLE	Designed for broad app workflows; confirm whether your app uses Classic or BLE
DA200	Bluetooth 4.0 / Bluetooth 5.4 / BLE	Not compatible with third-party apps. Intended for Drove West programs / designated apps only.

Tip: If you are unsure which mode your app uses, run the 5-minute test below and include the results in your ticket.

Quick Validation

Run this before requesting firmware resources — most issues can be classified quickly.

VERSION IDENTIFICATION

What to Send (So We Can Help Fast)

When support receives complete version information, diagnosis time drops significantly.

Wireless Adapters (DA/V models)

Please provide:

Adapter model (DA100 / V011 / V015 / V019 / V020, etc.)

Any label/packaging identifiers (batch/lot, serial if available)

Phone model + OS version

App name + app version

Vehicle make/model/year/engine + region

Symptom category: "pairing fails" / "connects but no data" / "disconnects after X minutes"

Photos/screenshots or screen recordings (highly recommended)

Handheld Scanners

Please provide:

Scanner model

Hardware / firmware / software version (if shown in System Info or printed on the device/packaging)

Menu path used (what you clicked)

Vehicle details and symptoms

Photos/screenshots if available

Examples of Version Strings You May See

Different models show versions differently. Here are examples of how version info may appear:

V318: hardware version V1.1; software version V318_MCU_V00.01

V310: hardware version V1.1; software reference V310_FLASH_V01.01 / V310_MCU_V06.01

V519 Plus: firmware version V1.00.251124

Update Policy

Firmware / Software Updates: How We Handle Them

We avoid uncontrolled public firmware distribution because it creates version fragmentation and support risk for brands and platforms.

Standard catalog / retail use

Update methods and availability depend on the model and revision.

If an update is required, we provide guidance via a support ticket after reviewing your version details.

OEM / Private Label programs

We support version control for consistent reorders and stable field behavior.

Program customers can request controlled firmware baselines, revision tracking, and documentation aligned with support workflows.

Start an OEM Version-Control Discussion

Where to Find Version Info

Handheld Scanners

Settings or About menu on the device

Printed on the device label (back or bottom)

Printed on the retail packaging

Bluetooth Adapters

Printed on the adapter housing

Visible in Bluetooth device info on your phone

Printed on the retail packaging

FASTEST PATH

Submit a Version Question

To get a precise answer, send the following information with your ticket.

1 Model + connection mode (Classic vs BLE)

2 App + OS version

3 Vehicle details

4 What works / what fails

5 Any version strings shown or photos of labels

6 Results of the 5-minute compatibility test

Submit a Version Question Submit a Support Ticket

Have a Version Question?

Submit a support ticket with your device model, version details, and a description of the issue. We'll respond with guidance.

Submit a Ticket Downloads Center