One session on the record.
Play through a representative session on the reference vehicle, then read the same session step by step. Fixed sample data, so every figure can be checked against the rest of this site.
Click through a representative session
The values here are fixed samples. Every panel mirrors a real Hanterill view, but nothing is connected to a car.
Hanterill reached the vehicle over the local Ethernet link and opened a diagnostic channel.
One car, one complaint, start to finish.
A representative session on the reference vehicle: what came in, what the scan found, what the numbers said and what the second scan showed after the repair. Fixed sample data, so every figure below can be checked against the rest of this site.
- 01
The car arrives with a complaint
The owner reports that the range estimate dropped further than the weather explains, and that the car charged more slowly than usual on a DC charger twice last month. Nothing on the dashboard. No warning lamp.
- 02
Connect and identify
Connect the ENET cable between the car and a laptop. Hanterill finds the gateway on UDP port 13400, opens a TCP channel and activates routing. It identifies the vehicle before choosing the module registry and decoders for that platform.
- 03
Read the fault memory
The scan checks the CMA catalogue and records which control units answer. Three responding units carry fault codes. Hanterill keeps each code's status byte, which shows whether the fault is active now or belongs to an earlier event.
- 04
Read the conditions behind them
The BECM saved pack voltage, current, charge level and temperature when its code was set. The sample shows a pack at 62 % charge under load when the module flagged an imbalance; that context does not identify the cause by itself.
- 05
Read the pack itself
The sample shows a 94.72 % health estimate and an 8 mV spread across 108 cell groups, with the largest deviation in module 14. The dashboard's single percentage would not show that distribution.
- 06
Score it
The sample inspection report marks the battery finding for review and cites the rule behind it. No fault code is active, but one module sits at the edge of the report's band. The saved snapshot shows the conditions when the code was set; it cannot show how the reading changed over time.
- 07
Re-scan and diff
After the workshop's firmware update, save a second scan and compare it with the first. The comparison shows codes that cleared or changed status and any change in cell-group spread. Both sessions remain in the local archive.