← ScanWrench home

Verified compatibility.
No asterisks.

A configuration reaches this registry only after it passes automatic ECU interrogation and eight physical checks on a real adapter, phone, and vehicle. No simulated session can publish a green badge.

No raw VINsNo tester identityNo paid placementNo “universal” shortcuts
THE PROTOCOL

What “verified” actually means.

01

Identity + power

Record the adapter identity and supply voltage without assuming the label tells the truth.

02

ECU interrogation

Verify protocol, PID map, readiness, all three code channels, Mode 06 coverage, and live-data response.

03

Clean reconnect

Disconnect and reconnect to the same adapter, then verify its identity again.

04

Eight physical checks

Fresh permissions, backgrounding, phone lock, interruption, weak signal, ignition cycle, 30-minute soak, and comparison rescan.

LIVE PUBLIC LEDGER

Field-verified configurations

Loading registry…

Reading the evidence ledger…

Only aggregated, privacy-safe, field-verified reports are returned.

A verified connection proves this adapter/phone/vehicle configuration completed the published protocol. It never means every manufacturer-specific module or feature is supported.