Diagnostics
Module data
Every named readout group per module: values, lifetime histories and timelines.
The Module data screen puts each control unit's named readout groups in one place. Open a group to inspect its current values, counters or dated records without hunting through the other screens.
How a readout works#
Each module exposes numbered readout groups: small sets of related records such as "charge history", "wake-up log" or "12 V statistics". On the Module data screen:
- A group reads as soon as you open it, and Read again in the group header refreshes it.
- A status line reports coverage, for example "All 17 values read." If nothing decoded, it says so.
- Key figures appear first, followed by a table of decoded values. Undecoded rows stay collapsed with a reason; the coverage count includes them.
- Raw identifiers (DID numbers, payload bytes) never clutter the screen; they are kept in the saved JSON if you archive the session.
What each module keeps#
- Battery module (BECM): lifetime charge counts (normal AC and fast DC, shown only when the charger's own tables agree), time spent in each charge band, per-cell class and capacity sets, temperature histograms by operating state, and the module's awake time.
- Central module (CEM): 12 V battery statistics (charge counts, standby currents, temperature bands), the power-mode history (minutes asleep, parked, in use, driving), wake-up and sleep history, and the gateway reset log.
- Gateway (VGM): security and diagnostic-access logs, network-management and Ethernet error histories, and the reset log with an odometer reading per reset.
- Instrument cluster (DIM): trip computer, odometer copies, service intervals, display and system data, and the message history. See Driving and display.
- On-board charger (OBC): charge cycles, restarts and lifetime alarms per power block.
- Climate, thermal manager, drive units, engine module: coolant circuits and pumps, heat-pump and heater lifetime figures, drive-unit operating hours and heat maps, and the OBD values the engine module mirrors.
Some groups also appear in place on the screen that owns the topic (the battery groups on Battery Health, the drive-unit groups on Drive Units), so you rarely need to leave the screen you are working in.
Histories and timelines#
Many groups contain dated events. Hanterill uses the module's clock to date a lock or wake event; a reset entry can also carry the odometer reading at the time. Where the module provides enough detail, the screen names the event and its reason instead of showing only a code.
Unconfirmed values#
Check the labels before using a value
The app leaves unknown values undecoded. It marks hours likely when their scale is unconfirmed and numbers histogram bands whose boundaries are not established. Check coverage and source before acting on a result.
Some groups need the module's extended diagnostic session; those carry an extended toggle in the group header and read once you allow it.
Where the data goes#
Every readout is part of the session archive, so a capture saved today can be compared with a later visit. See Sessions and evidence for how sessions, exports and the "Since your last visit" alerts work.