Start
Common tasks
Follow a short path through the app for an inspection, fault, repair or software check.
Choose the task closest to what you want to check. Each path starts with a read; actions that change the car require their own confirmation.
| If you want to | Go to |
|---|---|
| The car does not appear when I plug in | Troubleshooting |
| Is this used car's battery healthy? | Battery Health, then Inspection Report |
| Is this car worth buying? | Inspection Report |
| Which fault codes are currently active? | Fault Codes (DTCs) |
| Did my repair actually clear the fault? | DTC History Diff |
| Did the dealer update the software? | Firmware SBOM, then Firmware Diff |
| The battery goes flat overnight | 12V Sleep Drain |
| The car sags or loses power under load | Live Telemetry, Battery preset |
| It only faults sometimes while driving | Live Telemetry, record then replay |
| Which modules are even fitted to this car? | ECU Inventory |
| What does this identifier mean? | DID Explorer |
| I need something to hand a customer | Sessions & Reports, export PDF |
| What can this build actually do to the car? | Capabilities |
Check a used electric car#
- Connect and read the vehicle identity and fault codes. Check which control units answered.
- Open Battery Health. Read the car's reported SoH and SoC, then open the Cell Map if cell readings are available. Compare cell voltage spread only with readings taken under similar conditions.
- Open the Inspection Report and read its findings and coverage gaps. A missing battery or fault reading is not a pass.
- Save the session yourself so you can return to the captured evidence later. Choose VIN masking before sharing a PDF.
Investigate a warning#
- Open Fault Codes and scan. Start with active and pending codes, then include stored codes if you need the history.
- Select a code to see which unit reported it and whether it supplied a snapshot of the conditions at the time. The available snapshot fields vary.
- Record the result before repairing anything. A code indicates where to investigate; it does not identify the failed part by itself.
Verify a repair#
- Save a scan before the repair. After the repair, scan again and compare the results from the same car.
- Clear fault codes only if the installed app supports write actions and you intend to change the car's fault memory. Review the backup and verification options before confirming.
- Read the result for each unit and scan again. A code that returns needs further investigation.
Check a software update#
- Run Firmware Audit before the update and save its results.
- Repeat the audit afterward. Compare only version fields that were actually read on both visits.
- A changed version shows what the unit reports now. An unchanged or missing version does not prove exactly what the workshop did.
Investigate 12 V drain#
- After the car has been parked, open 12 V Sleep Drain and read the average current and sample distribution.
- Check whether the app marks the readings as consistent. Higher-current samples suggest more time awake or drawing power, but do not identify the cause.
- Check 12 V battery condition separately and compare readings under similar conditions. The drain screen has no wake-cause log.