Engine diagnostics

Engine Diagnostics is for combustion and hybrid vehicles where the relevant control units answer. The screen shows which units were found, which requested readings returned a value and which functions are unavailable for that car.

What you may see#

Depending on the vehicle, the catalogue can include engine, transmission, mild-hybrid battery and diesel aftertreatment readings. The app labels each available reading with its source and status. It also keeps unresolved entries visible instead of assigning them a guessed value. A petrol car, for example, should not be expected to return diesel aftertreatment data.

The catalogue is broader than the set of readings verified on any one car. A unit appearing in the catalogue does not mean it is fitted or that every parameter will answer. Check the coverage shown on the screen before relying on a result.

Standard OBD values and emissions status#

On the Vehicle screen, the OBD card shows values the engine module reports: remaining HV battery charge, ambient temperature, 12 V voltage, speed, fuel type, the OBD standard, calibration ID and verification number. If the engine module answers the emissions requests, a second card shows the warning-lamp state, emissions code count, readiness monitors for spark or compression ignition, and the distance and time since codes were cleared. These are the standard OBD questions, read through the car's diagnostic channel.

The emissions card only appears when the engine module answers; a battery-electric car's module does not, so it is never shown for a BEV. "Distance since codes cleared" is also a useful used-car signal on its own: a very small number next to a clean fault-code list is worth a question.

How to use the screen#

Start with the units that answered, then read the measured values and their status. Compare a surprising value with the car's operating state and any related fault codes. An unavailable or provisional engine value should not be used as a basis for a repair decision without further checks.

The engine screen reads data. Service actions that change the car are separate and require their own support and confirmation. Do not infer from a readable engine parameter that Hanterill can run a workshop routine for it.