Emission system report
This report displays emission diagnostic trouble codes (DTCs) for light-duty and medium-duty vehicles that have a vehicle tracker (Vehicle Data Device) installed. The report does not include information for heavy-duty vehicles or electric vehicles (EVs).
For records to appear in the report, the vehicle must:
-
Have a compatible vehicle tracker installed (Vehicle Data Device).
-
Have a vehicle tracker with the latest firmware installed.
-
Have a vehicle tracker that is operating in ECM Mode.
-
Have active DTCs.
In this article:
-
What is in the report
-
How to run the report
-
FAQs
The report shows vehicle details, a summary of active DTCs, OBD-II readiness monitors, positive battery voltage and a detailed list of active DTC codes.
The Report totals section shows:
-
The total number of vehicles selected to be included in the report.
-
The number of vehicles with active emission-related DTCs.
The Vehicle details section of the report shows:
-
The vehicle’s vehicle identification number (VIN).
-
The vehicle’s registration number.
-
The vehicle’s year, make and model.
-
The vehicle’s OBD-II protocol.
The Check engine light and DTC details section shows:
-
The distance travelled with the check engine light (CEL) on.
-
Total duration of time the CEL has been on.
-
The total number of active emission DTCs.
-
The total number of OBD-II readiness monitors that recorded a failure.
In the table, you see the following information:
-
The date the DTC was triggered.
-
The OBD-II readiness monitors that recorded the failure.
-
The active DTCs codes triggered.
-
The positive battery voltage.
-
The engine’s RPM during the drive cycle when the DTCs were triggered.
When a vehicle does not return data for your specified date range, there are four reasons why this could happen:
-
There were no emission system related issues during the report period.
-
The vehicle did not complete the steps to cover a basic drive cycle.
Note
If the vehicle was driven regularly during the report period, check your device health in Reveal for potential issues.
-
The device wasn’t in ECM mode. This is required to collect data from the vehicle’s emission systems. To switch to ECM mode, contact Support.
-
The device was in backoff mode. This is a temporary mode of operation where the device doesn't have access to the vehicle's ECM connection. If you get this message, try to run the report again later.
-
Go to Reports > Emission system report.
-
In the Fleet selection section, select the vehicles to include in the report.
You can select: all vehicles in your fleet, selected vehicles, or all vehicles in one or more groups.
-
In the Date and time section, select the date range you want to cover in the report.
-
In the Report options section, select the checkbox if you want to include vehicles that do not have active DTCs.
-
Choose RUN REPORT.
What is the OBD-II protocol?
The OBD-II protocol is used to standardize the CAN bus interface for external test equipment. Most newer vehicles use the same protocol, however vehicle’s pre-2008 may use different protocols.
Why don’t I see this report listed on the Reports home page?
This report is currently in Limited Beta for a small number of customers in the US and Canada. It is also only available to Reveal and Reveal Pro customers.
Does this report help prepare for a periodic emission test or SMOG check?
Yes, this report is a useful tool when preparing for an emission check, it indicates ongoing issues with vehicle emission related systems like evaporative/catalyst system that can lead to a failed test.
What is an emission DTC?
When a malfunction occurs in a vehicle, such as the catalytic converter not working as efficiently as it should, the vehicle’s check engine light is turned on and a DTC is recorded to help troubleshoot the problem.
What is an OBD-II readiness monitor?
They are self-tests performed by the vehicle’s computer, purpose is to observe the performance of emission related systems in your vehicle.
The output of these monitors tells you whether the vehicle computer has completed the self tests.
The output can be “Ready” ,”Not Ready” and “Unsupported or Disabled” which can be interpreted as no issues found, issues found and self test is not supported for a specific system.