Subsystem telemetry

Hanterill has separate diagnostic screens for climate, drive units, charging, power, steering, telematics, GPS and service schedule. Each screen asks for the readings relevant to that system. The available fields depend on the car and on which control units answer.

Climate and heat pump#

Climate can show refrigerant pressure and temperature, compressor activity, cabin heater temperatures, battery cooling readings and fan output. A blank field means that value was not returned. The screen identifies the source unit for a reading when it can.

The heat pump and high-voltage heater keep lifetime records, and the screen reads them: compressor runtime (marked likely until its hour-scale is confirmed), stops from overheating and freeze protection, preconditionings done with the heat pump, energy the heat pump saved, and valve cycles, plus a chart of cooling, heat-pump and reheat runtime per outside-temperature band, and the heater's starts, runtime and temperatures.

Coolant circuits#

One read of the thermal manager shows the car's three coolant circuits as connected cards: the battery circuit (coolant in, pack average, coolant out), the drive-unit circuit (coolant, rear and front motor, rear and front inverter) and the climate circuit (heater in and out). Each card ends with its pump's speed and current. The same read brings charger and DC/DC temperatures, the pack voltage at the contactors, the contactor state and the battery current.

Drive units#

Drive Units can show front and rear motor readings such as speed, torque, voltage and temperature live, and compare the two sides when both answer. A missing rear unit on a car built with one motor is not a failed rear motor.

The drive units keep lifetime records too. The view shows operating and powered hours (marked likely until the hour scale is confirmed), time spent regenerating or producing torque, temperature history and the remaining share of full torque. A heat map puts time at each torque and speed combination beside the hottest reading there. On the reference car, the front unit does most of the regenerative braking; the two histories make that difference visible.

Power and the DC/DC converter#

Power groups high-voltage and 12 V supply readings. It also shows the 12 V battery's temperature history in numbered bands, with sample counts, and the car's recorded time asleep, parked, in use and driving. Sleep counts and time since the last wake-up appear where the car reports them.

The DC/DC converter in the front drive unit charges the 12 V system. Its history covers running time, output power, current and voltage, available power, high-voltage input and board temperature. The scales still need confirmation, so hours carry a likely label and heat-map axes stay numbered. Compare voltages from different units while accounting for the car's operating state; a mismatch alone does not identify a bad cable or ground.

Charging, steering, telematics, GPS and service schedule#

Charging has its own guide: see Charging for the live charger telemetry and the charger's health counters.

On cars tested so far, the steering angle and rate sensors have not answered these requests over the diagnostic channel. Steering shows that limit and points you to fault codes instead. Calibration is a separate service action that changes the car.

Telematics can show the backup battery and other available module readings. GPS reads the car's position only when you request a fix. Review location data before sharing an export. These screens report what the unit returned; they cannot by themselves identify the cause of a weak signal or an emergency-call warning.

Service Schedule shows the maintenance counters the car supplies, such as remaining distance, time and operating hours, together with the 12 V battery care interval. It also compares the cluster's two counter records and warns when they no longer describe the same service event. Some counters can be unavailable. Reading a counter does not reset it; a reset is a separate confirmed service action.

Across these screens, use the reading state and capture time. Do not turn a missing field into zero or treat a single outlying value as a diagnosis. What the car has learned about its own consumption lives on Driving and display, and every module's full readout groups are on Module data.