Aftertreatment expert review (sensors, monitors and indicators)
How to read, sensor by sensor, the system that cleans the exhaust gases and which indicators it gives, with what it does not claim.
Reviewed by Daniel Morales, founder of Reprorace SL, on
Where: Diagnostics › More tests › Service functions › Channel “v2 procedures (beta)” › “One-click full diagnosis” › box “Add Aftertreatment expert review”
Important: Only people with a current forensic authorization (expert, SERMI operator or authority agent) and the Hub administrator see it. It is read only: it writes, erases and resets nothing, forces no regeneration, activates or simulates no sensor and reads no PIN, keys or secrets.
- Choose car or van, truck or agricultural, the unit and the vehicle details, and tick the review box.
- Press the start button. Towards the end the test asks you to start the engine and leave it idling for about two minutes while it measures each sensor.
- Read the traffic light and the indicators: each one says what was read, the criterion with its threshold and the source.
- Open the sensor sheet to see everything each sensor measured: NOx before and after the treatment, lambda sensors, temperatures, pressures and state of the particulate filter, AdBlue, EGR, monitors and counters.
- If needed, save the reads in an open expert case file, which already has its legal basis.
| Light | What it means |
|---|---|
| Green | Nothing to highlight in what could be checked. It does not mean everything is fine: what was not read shows as “Not enough data”. |
| Amber | There are points worth looking at, or that could not be checked. |
| Red | A contradictory reading, a warning from the vehicle itself or three different rules that coincide. |
What it looks for:
- A NOx sensor that gives the same value in every sample with the engine running.
- NOx after the SCR almost equal to before while AdBlue is being dosed.
- AdBlue with a concentration out of range (or flagged as wrong by the control unit) and no consumption.
- Particulate filter pressure almost zero with a lot of soot or a lot of flow, and exhaust temperatures that do not change.
- Lambda sensors that do not move.
- Inducement without warnings (or not declared) with confirmed faults of the reagent, dosing, NOx sensors or EGR.
- Monitors reported as “not supported” when the vehicle itself gives data of that system.
- Fault memory cleared recently or more than once.
- NOx-tracking and Euro 7 OBM counters that do not fit the kilometres.
- The module's programming fingerprint, versions or secure-transmission entity identifier (F19F) different from an earlier reading.
The aftertreatment control module (acronym ACM) is identified and read with the “Exhaust aftertreatment control (ACM)” procedures of the forensic reading: full identification, programming trace, faults with their status and frozen data. It is only identified and read.
Important: An indicator does not by itself prove tampering or an offence: there are legitimate causes (dirty or faulty sensors, repairs, replacements, updates). The decision always rests with the expert or the person inspecting and the competent authority.
The thresholds are platform review criteria, not regulations or manufacturer values; the report quotes them. Euro 7 assigns no read identifiers to the OBM: its values are typed by hand in the optional section if they were read with the manufacturer's tool.
This is forensic mode and it only reads. The aftertreatment repair functions (forced regeneration, soot or ash reset after replacing the filter, adaptation after the replacement and resetting the inducement after the repair) belong to diagnosis mode and are in Service functions, with their usual permissions. More in “Forensic mode and diagnosis mode”.
More guides in this section
- How a remote session works
- Tunnel plan: connect a tool to the vehicle remotely
- Accept or withdraw remote access to your vehicle
- Collaborating in a session: messages, prompts and photos
- Unit PassThru mode from the app
- PassThru on Mac, Linux and iOS
- Assistance requests, appointments and work orders
- Legacy vehicle configuration and diagnostics: VAG and other makes
- Modern vehicle coding and programming
- How to diagnose each type of vehicle
- Automatic diagnosis: one tap and it explains
- Reading a vehicle and sharing the report
- CANopen diagnostics for machinery
- Vehicle details: identifying it by the VIN
- Live dashboard, service functions and battery test
- v2 procedures: beta and operational
- Control unit images: store, edit and prepare writing
- Forensic cases: custody of forensic reads
- Forensic mode and diagnosis mode
- Forensic authorizations: who can use the forensic reads
- Quick inspection for authority agents
- Compatibility notices for your tool
- CAN captures
- Pre-purchase report
- Vehicle report
- Battery health of electric and hybrid cars
- Asking Diaglana for help
- Your first read: understanding the result and what to do
- Diagnosis options: each setting and when to change it
- Workshop settings: requests, orders, network and notices
- Reading: choosing the protocol and understanding the OBD on UDS report
- What a fault code means
- Live data: dashboards, recording and export
- Attaching fault codes to a work order
- Procedures that write, program or authenticate
- ISOBUS: reading and changing an implement's NAME
- Diagnosis over Ethernet (DoIP)
- Download Diaglana PassThru for Windows, Mac and Linux
- Authorizing a PC for PassThru
- Diaglana PassThru updates
- AI diagnosis assistant: asking for help with a read
- Connect your AI (Claude or another) to your vehicle