No vehicle selected Create a vehicle profile or read VIN
Workshop modeLocal processing
OBD gatewayELM · TOPDON · Carman · Autel · Snap-on S9 · DoIP
ECU programmingPreflight gate
Direct workshop accessNo site password required

WORKSHOP OVERVIEW

Vehicle health at a glance

Connection

Not connected

Scan for a BLE OBD adapter, then connect
0%

Vehicle profile

Unassigned vehicle

Year · make · model · engine

Programming protection

Programming gated

Autel J2534 / DoIP preflight available
🛡️

Live trend

RPM, load, voltage and temperature

Pre-tune gate

Automatic plausibility checks

Workshop workflow

Easy-to-hard calibration validation process

1Mechanical baselineCompression, leak-down, fluids, intake and exhaust integrity.
2Electrical baselineBattery support, charging voltage, grounds and network health.
3Sensor rationalityKOEO/KOER plausibility, trims, temperature and pressure correlation.
4Controlled load loggingRepeatable test conditions, knock, lambda, fuel pressure and EGT limits.

GENERIC OBD-II · SAE J1979 / ISO 15031

OBD-II Reader

Fast workshop scan mode for legislated emissions diagnostics: VIN, MIL status, readiness, confirmed/pending/permanent DTCs, freeze-frame and essential live data.

Generic OBD-II scope: this page covers standard emissions-related OBD data. Manufacturer-enhanced body/chassis/network functions require the appropriate OEM/J2534/proprietary diagnostic transport.
OBD interface disconnectedSelect an ELM/STN BLE or USB/COM interface, then connect.

Vehicle & adapter

Identity and transport used for this scan

NOT CONNECTED

Generic OBD service coverage

Standard modes used by the reader

01 Current data02 Freeze frame03 Confirmed DTCs04 Clear DTCs07 Pending DTCs09 Vehicle info0A Permanent DTCs

Connect a compatible ELM/STN interface to query the vehicle.

Confirmed DTCs

Mode 03

0
No scan completed.

Pending DTCs

Mode 07

0
No scan completed.

Permanent DTCs

Mode 0A

0
No scan completed.

I/M readiness

Monitor status since DTCs were cleared · PID 01

NOT READ
Run Quick Scan or Read Readiness.

Freeze frame

Mode 02 frame 00 where supported

NO DATA
Run Freeze Frame or Quick Scan.

Essential live data

Current generic OBD values; use Live Data for full PID selection and logging.

Clear emissions DTCs

Mode 04 normally clears confirmed emissions DTCs, freeze-frame information and resets readiness monitors. Record the scan before clearing.

VCI & NETWORK LAB

Connection centre

Use the exact transport that matches the hardware. MotiveTune separates ELM text-command adapters from proprietary VCIs and direct ISO 13400 Ethernet/DoIP so the wrong command set is never sent to a module.

Download Windows Bridge
BLE

ELM / STN Bluetooth

For verified BLE serial adapters using supported vLinker 18F0, FFF0, FFE0 or Nordic UART profiles.

COM

USB / Bluetooth Classic COM

For ELM/STN interfaces that Windows exposes as a serial port. Uses Web Serial; only one program can own the COM port.

TOPDON

CarPal / TopScan

Bluetooth inspection without blindly sending ATZ. If a standard ELM/STN BLE serial service is found, MotiveTune can switch to normal OBD mode.

S9

Snap-on Scan Module 9

Detects S9/EESM306B and S10/EESM317A hardware, Bluetooth Classic/USB exposure and Windows IDs. S9 vehicle-side Ethernet/DoIP capability is reported separately from the proprietary Snap-on host protocol.

DOIP

Direct Ethernet / DoIP

Uses the Windows Bridge to send an ISO 13400 vehicle-identification discovery request over active IPv4 interfaces. VIN/IP/logical address are shown when the vehicle replies.

J2534

Autel / Carman pass-thru

Inventories SAE J2534 registrations, Windows PnP devices and network interfaces. Proprietary command channels and ECU programming stay locked until a verified provider API is available.

Connection status

Results from the current session

TOPDON

Not checkedUse one of the TOPDON checks above.

Snap-on S9/S10

Not checkedRun Windows Bridge detection.

Ethernet / DoIP

Not scannedRun ISO 13400 discovery with ignition ON.

J2534

Not checkedAutel/Carman provider inventory appears here.

What “supported” means

Working standard transportELM/STN BLE/serial and ISO 13400 vehicle discovery can be exercised directly by MotiveTune.
Hardware detected / protocol protectedSnap-on, TOPDON proprietary links and J2534 providers can be positively identified without sending guessed commands.
Write lockedECU calibration, coding, immobiliser and security-access commands are not enabled by the browser bridge.

OBD-II MODE 01

Live data and road-test logger

Select only the PIDs needed for the test to maintain useful sample rate.

Data stream

Idle — 0 samples

NormalAttention

PID selection

Fewer channels generally produce a faster refresh rate on ELM adapters.

Supported PID detection runs after connection.

Multi-channel graph

Last 60 samples

Adapter terminal

Read-only service commands; advanced use

Adapter output will appear here.

OBD-II MODE 03 / 04

Diagnostic trouble codes

Record codes and readiness state before clearing. Clearing codes also resets emissions monitors on most vehicles.

Current codes

No scan completed

Connect to a vehicle and select “Read DTCs”.

Code lookup

Generic powertrain reference. Manufacturer-specific diagnosis requires OEM service information.

Diagnostic discipline

1ConfirmActive, pending or history? Record freeze-frame and customer conditions.
2TestVerify power, ground, signal, mechanical condition and circuit loading.
3RepairCorrect the root cause rather than replacing the component named in the code.
4ValidateClear only after repair, complete drive cycle and confirm monitors.

CALIBRATION ENTRY CRITERIA

Pre-tune health inspection

A calibration cannot repair a mechanical, electrical, air-path or fuel-system fault.

Mandatory workshop checks

CONTROLLED CALIBRATION DEVELOPMENT

Tune workspace

Develop, compare and export calibration plans. Calibration planning is separate from the gated ECU Programming workspace.

Professional-use boundary: Do not alter emissions diagnostics, safety systems, immobilisers, odometers or road-speed controls. Validate every change against engine, transmission, turbocharger, fuel-system and thermal limits.

Project details

Saved locally in this browser

Saved

Safety limits

Target tables

Editable planning tables — not transmitted to the ECU

PLANNING ONLY

Change log

Record the reason and evidence for every revision

PROGRAMMING WORKSPACE

J2534 / DoIP preflight is available

Use the ECU Programming page to verify the provider, ECU identity, support voltage, package fingerprint, backup and recovery plan. Actual ECU writes require a validated ECU-specific programming-provider plugin.

CONTROLLED ECU PROGRAMMING

ECU programming

Programming is available only through a verified J2534/DoIP provider and an ECU-specific programming profile. MotiveTune blocks generic or guessed writes.

Workshop safeguard: connect a regulated battery support unit, record the original ECU identity and calibration, and have a recovery path before programming. MotiveTune does not provide emissions-delete, immobiliser, odometer or safety-system programming.
01
ProviderAutel/Carman J2534 or verified DoIP path
WAIT
02
ECU identityVIN, ECU family, HW/SW and calibration IDs
WAIT
03
Power supportStable programming voltage
WAIT
04
PackageCalibration file + SHA-256
WAIT
05
BackupOriginal calibration/recovery record
WAIT
06
Vehicle healthNo critical pre-tune findings
WAIT

Programming route

Use a standards-based provider. Snap-on and TOPDON proprietary hosts remain diagnostic-only unless a documented programming API is installed.

NOT VERIFIED
No programming provider verifiedStart Windows Bridge v0.4.2, then run preflight.

ECU identity

These values must match the approved programming profile before a write backend can be armed.

Calibration package

MotiveTune hashes the selected file locally. No calibration file is uploaded by the web app.

Recovery & authorisation

Programming cannot be armed without a recovery plan and technician confirmation.

WRITE AUTHORISATION

Programming is disarmed

Run the preflight. Actual ECU writes also require an ECU-specific MotiveTune programming-provider plugin; the generic bridge will not guess flash routines or memory addresses.

Programming audit

Local preflight events and package fingerprints

LOCAL ONLY
No programming preflight completed.

WORKSHOP ENGINEERING TOOLS

Calibration calculators

Results are engineering estimates and must be verified against manufacturer data and measured vehicle behaviour.

Boost pressure

Lambda / AFR

Injector flow estimate

Torque / power

Tyre speed correction

Fuel trim total

AUDITABLE WORKSHOP RECORDS

Reports and data logs

Vehicle data remains local unless you export it.

Samples0Current session
Snapshots0Saved events
DTCs0Last scan
Duration00:00Logging time

Workshop record summary

Vehicle, scan and pre-tune status

LOCAL RECORD

Session timeline

Latest events first

No session events yet.

AUSTRALIAN ROAD-USE CONTROLS

Compliance and workshop standards

This app supports diagnosis and calibration development; it does not certify that a modified vehicle is legal for road use.

ADR

Australian Design Rules

Vehicle safety and emissions performance must continue to satisfy the rules applicable to the vehicle. Calibration changes can affect emissions, drivability, thermal protection and safety-system interaction.

VSB 14

National modification code

Use VSB 14 as a technical starting point for modified vehicles, then confirm the administrative and approval requirements in the relevant state or territory.

OBD

Diagnostic integrity

Do not suppress DTCs, readiness monitors or malfunction indication solely to conceal a defect. Retain catalyst, DPF, EGR, SCR and evaporative-system diagnostic functions for road vehicles.

WORKSHOP

Controlled test conditions

Secure the vehicle, use ventilation, maintain battery support, verify tyre and brake condition, and use a chassis dynamometer or closed test environment for sustained load testing.

South Australia workshop note

Published South Australian light-vehicle modification guidance states that recalibrating or reprogramming an original ECU on an originally equipped engine is not allowed, while a non-original engine installation requires a modification application and may require emissions testing. Confirm the current position directly with Vehicle Standards before quoting or releasing any road-use calibration. This application does not provide modification approval or engineering certification.

OBD and programming capability matrix

Generic OBD-II live dataIncludedLegislated Mode 01 PIDs through supported ELM327/STN USB/COM or BLE serial-profile hardware.
VIN and generic powertrain DTCsIncludedModes 09, 03 and 04 where supported by the vehicle.
Enhanced manufacturer dataDefinition requiredRequires licensed OEM data, addressing and vehicle-specific PID definitions.
ECU programming preflightIncludedProvider, ECU identity, voltage, package fingerprint, backup and recovery gates are included.
ECU calibration writeECU-specific provider requiredActual writes require a validated programming-provider plugin with ECU-specific flash routines, checksums/signatures and recovery controls.

Release checklist

WORKSHOP GUIDE

How to use MotiveTune AU

Start with the transport, prove the adapter link, then prove vehicle communication. Do not change two variables at once when diagnosing a connection fault.

01

Prepare the vehicle

  1. Park safely, apply the park brake and use battery support for extended testing.
  2. Inspect DLC pins 4, 5 and 16 if power is questionable.
  3. Use one VCI at a time while establishing the connection.
  4. Ignition ON for vehicle communications unless the OEM procedure states otherwise.
02

Choose the correct transport

  1. ELM/STN BLE: generic BLE serial OBD adapters.
  2. USB / COM: ELM/STN USB or an OS-paired Bluetooth Classic serial adapter.
  3. TOPDON: inspect first; do not assume ELM commands.
  4. S9/S10, Autel, Carman, DoIP: start the Windows Bridge.
03

Start Windows Bridge

  1. Download and extract MotiveTune Windows Bridge v0.4.2.
  2. Run START-MOTIVETUNE-BRIDGE.bat.
  3. Leave the PowerShell window open.
  4. MotiveTune automatically searches loopback ports 8765–8769.
04

Snap-on S9

  1. Confirm the rear label says EESM306B for S9.
  2. Power the S9 from the vehicle DLC.
  3. S9 host communication is Bluetooth 2.1; USB is used by Snap-on for pairing/update support rather than normal vehicle communication.
  4. Select Snap-on Scan Module 9 and press Detect S9 / S10.
  5. If using a vehicle that requires DoIP, S9 itself can provide vehicle-side Ethernet/DoIP in supported Snap-on software; MotiveTune does not reverse-engineer the proprietary Snap-on host protocol.
05

Direct Ethernet / DoIP

  1. Connect the PC to a genuine DoIP/ENET interface or supported vehicle Ethernet path.
  2. Check Windows Ethernet status is Up and an IPv4 address is present.
  3. Start the Windows Bridge and select Direct Ethernet / DoIP.
  4. Press Discover DoIP. A successful ISO 13400 response shows vehicle IP, VIN and logical address.
  5. No response usually means wrong cable/interface, vehicle not in DoIP mode, ignition state, network addressing or vehicle does not support DoIP.
06

TOPDON CarPal / TopScan

  1. Plug the TOPDON VCI directly into the DLC.
  2. Disconnect it from phones/tablets; TOPDON documents one active Bluetooth host at a time.
  3. Select TOPDON CarPal / TopScan and scan Bluetooth.
  4. If it is not shown by Web Bluetooth, use Check TOPDON in Windows.
  5. MotiveTune only sends ELM/STN commands if a known serial GATT service is positively identified. Proprietary TOPDON command services are not guessed.
07

Autel / Carman

  1. Install the manufacturer’s official Windows/J2534 software.
  2. Connect the VCI using the connection supported by that model.
  3. Select Autel J2534 / VCI or Carman VCI / J2534.
  4. Run detection to confirm the Windows PassThru registration, DLL path and PnP device.
  5. Detection proves the Windows provider path. Use ECU Programming preflight for identity, voltage, package and recovery gates; actual flashing still requires an ECU-specific provider plugin.
08

ECU programming preflight

  1. Use Autel J2534, Carman J2534 or a verified Direct DoIP route.
  2. Start Windows Bridge v0.4.2 and open ECU Programming.
  3. Record VIN, ECU family, hardware/software/calibration IDs and stable support voltage.
  4. Select the calibration package and original backup so MotiveTune can fingerprint both with SHA-256.
  5. Run preflight. A write remains unavailable until an ECU-specific programming-provider plugin is installed and positively matches the ECU/package.
09

Normal diagnosis

  1. Once an ELM/STN connection is established, read VIN and supported PIDs.
  2. Record DTCs and freeze-frame information before clearing anything.
  3. Select only the live PIDs needed for the fault to improve sample rate.
  4. Log a repeatable road test and export CSV/report data.
10

Use the OBD-II Reader

  1. Select ELM/STN Bluetooth BLE or ELM/STN USB / COM and establish the adapter connection.
  2. Open OBD-II Reader and press Quick Scan.
  3. Review MIL state, I/M readiness, confirmed/pending/permanent codes and freeze-frame data before clearing anything.
  4. Use Essential live data for a quick check or open Live Data for full PID selection and logging.
  5. Export the scan record before Mode 04 clear. Permanent DTCs are ECU controlled and may remain after clearing.

Connection fault quick checks

Timeout waiting for ATZThe selected interface is not answering as an ELM/STN adapter. Check the transport; TOPDON/Snap-on/J2534 interfaces should not be forced through ELM mode.
SerialPort failed to openClose other scan software/browser tabs, confirm the correct COM port and ensure Windows has not disconnected the Bluetooth SPP port.
Bluetooth device not visiblePower it from the DLC, disconnect other hosts, verify browser Web Bluetooth support and use the Windows inventory check for Classic/proprietary devices.
No DoIP responseVerify a genuine Ethernet/DoIP path, link status, IPv4 addressing, ignition state and actual vehicle DoIP support.
Bridge unavailableRun the bridge BAT file and allow local/loopback access. Another service on 8765 is okay; the bridge automatically tries 8766–8769.

Hardware notes verified for this build

Snap-on S9: model EESM306B, Bluetooth 2.1 host connection, and Snap-on documents S9 as the Ethernet/DoIP-capable compact scan module for supported ZEUS/VERUS/TRITON configurations. S10: EESM317A is a different, newer generation. TOPDON CarPal/TopScan: TOPDON documents Bluetooth operation through its mobile app and states DoIP is not supported on TopScan/CarPal at present. MotiveTune therefore treats TOPDON as a proprietary VCI unless a standard ELM/STN service is actually discovered.

APP AND VEHICLE SETUP

Settings

Profiles and projects are stored locally on this device.

Vehicle profile

Adapter setup

Choose the transport that matches the hardware: ELM/STN modes send text commands such as ATZ. TOPDON inspection never sends AT commands until an ELM-compatible BLE serial profile is verified. Snap-on S9/S10, Carman and Autel use the local Windows Bridge for Windows/driver discovery. Direct Ethernet / DoIP supports discovery and programming preflight. ECU writes are only available through a validated ECU-specific programming-provider plugin.

Bluetooth device

No BLE device selectedUse Scan Bluetooth to open the browser device picker.

Previously approved by this site

No Bluetooth devices have been approved for this site yet.

TOPDON CarPal / TopScan

Not inspectedPower the VCI from the DLC, disconnect it from phones/tablets, then scan. MotiveTune will not send ATZ unless an ELM/STN serial profile is positively identified.
Windows check not runUse this when the browser cannot see the VCI.

TOPDON documents CarPal/TopScan as a Bluetooth VCI controlled by its mobile app. MotiveTune can safely verify BLE visibility or Windows pairing and will only use standard ELM/STN services when they are positively identified.

Autel J2534 / DoIP

Windows Bridge not checkedUse this for MaxiFlash/VCMI/JVCI-class hardware rather than USB/COM mode.

The bridge checks installed SAE J2534 providers, Windows PnP devices and active network adapters. Autel/Carman provider detection can feed ECU Programming preflight; an ECU-specific programming-provider plugin is still required for an actual write.

Snap-on Scan Module 9 (S9 / EESM306B)

Windows Bridge not checkedS9 uses Bluetooth 2.1 to the Snap-on host and supports vehicle-side Ethernet/DoIP through the DLC. MotiveTune detects the module through Windows without pretending to be Snap-on software.

The bridge listens only on loopback 127.0.0.1 using ports 8765–8769. It can identify S9 (EESM306B) and S10 (EESM317A), Bluetooth/USB exposure and hardware IDs. The proprietary Snap-on host protocol remains locked unless a documented interface becomes available.

Carman VCI / Carmanscan J2534

Windows Bridge not checkedFor genuine Carman VCI hardware with official PC/J2534 software installed.
Download Windows Bridge

Carman and TOPDON are separate manufacturers. This mode checks Carman/Carmanscan Windows devices and SAE J2534 registrations; it does not assume a TOPDON device is a Carman VCI.

Direct Ethernet / DoIP (ISO 13400)

Not scannedConnect the PC to a genuine DoIP/ENET path, ignition ON, then run discovery.
Download Windows Bridge

The bridge broadcasts the standard ISO 13400 vehicle-identification request on active IPv4 interfaces and reports responding VIN/IP/logical-address data. It provides ISO 13400 discovery for diagnostics/programming preflight. ECU writes require an ECU-specific DoIP/UDS programming provider.

Runtime capability check

Local data controls

Removing local data deletes vehicle profiles, tune projects, logs and checklist state from this browser.

Confirm action