Diagnostics
Driving and display
What the instrument cluster logged: trips, the odometer verdict, service intervals and display data.
The Driving and display screen reads records from the instrument cluster: trips, mileage, service intervals and display data. Compare its odometer reading with copies stored elsewhere in the car before treating a disagreement as a fault.
The odometer verdict#
The car keeps copies of the mileage in the cluster, gateway, battery module and other control units. The odometer card reads them together:
- It states the cross-check outright, for example "6 of 6 copies agree".
- If copies disagree, or a tamper flag is set anywhere, the card says so with a warning tone.
- The Vehicle screen adds the wider picture: the mileage consensus across every module that keeps a copy, and the gateway's reset log as a dated odometer history.
Trip and usage#
One read brings the cluster's trip computer: trip distance and drive time, average speed and average energy use, and the range the car is showing. The overview also includes the long-term trip counters and the trip reset counters, so you can see whether the displayed figures were recently zeroed.
Service intervals#
The cluster tracks service intervals in its own counters. The screen shows the time and distance remaining before the next service and 12 V battery check. It warns when two counter records disagree about the service event; check the car's service history before drawing a conclusion.
Display data#
Below the overview, each display group has a card for decoded values and a timeline for dated records. A count such as "2 of 72 decoded" shows how much of the response Hanterill understands. Groups with no decoded values show that status in one line. The charging, message, driver-assistance and system panels read on first open, so opening this page does not query them all at once.
Learned energy use#
The screen shows the car's learned consumption in numbered bands and how often it recorded each band. On the test car, the values appear to use kWh/100 km and may correspond to speed ranges. The band boundaries have not been confirmed, so use the distribution as context rather than assigning a speed to a particular band.
Why some figures are marked *likely*
Hanterill marks a value likely when the car returned it but its scale has not yet been confirmed. Values shown without that label have a checked scale.
Where to go next#
- Module data: the same cluster groups in the full readout view, alongside every other module.
- Cross-checks in the app: how agreement between modules is judged.
- Service schedule: the service counters in detail.