DIAGNOSTIC/ MALFUNCTION CODES SCRIPT
G. Codes for Diagnostics:
1. Power Data Diagnostic: Occurs when ECM parameters are not available within 1 minute of powering the vehicle’s engine on and/ or the system does not remain powered for as long as the vehicle’s engine stays powered
➢ Resolution: Make sure the driver is connected to the ECM device on the application. Have the driver go to Scan Devices and select their specific ECM device. Have them check if all engine parameters pass the diagnostics (all green). If not perform steps II-D/E.
2. Engine Synchronization Data Diagnostic: Occurs when when an ELD loses ECM connectivity to any of the required data sources (engine power status, vehicle motion status, miles driven, and engine hours) and can no longer acquire updated values for the required ELD parameters within five seconds
➢ Resolution: Make sure the driver is connected to the ECM device on the application. Have the driver go to Scan Devices and select their specific ECM device. Have them check if the diagnostic passes all engine parameters (all green). If not perform steps II-D/E.
3. Missing Required Data Elements Data Diagnostic: Occurs when any other required data field (such as location/ coordinates) is missing when recording an event
➢ Resolution: Make sure the “ALWAYS ON” Location permission is enabled for the Apollo application on the driver’s mobile device
4. Data Transfer Data Diagnostic: Occurs when the operation of the data transfer mechanism(s) (i.e., the ability for the application to transfer log data via FMCSA Web Services) is not confirmed. An ELD must verify this functionality at least once every 7 days
➢ Resolution: Verify that the driver has an active cellular or Wi-Fi connection on their mobile device. Ideally, they should have this at all times.
5. Unidentified Driving Records Data Diagnostic: Occurs when more than 30 minutes of driving time for an unidentified driver is recorded within a 24-hour period
➢ Resolution: This diagnostic indicates that the driver is not logged in on the application even though the vehicle has been moving for a combined 30 minutes within a 24 hour period. Have the driver login and advise them that their admin will need to assign them any unidentified driving events that have occurred that they will then need to review and accept on their application.
H. Codes for Malfunctions: Most malfunctions relate to a Diagnostic, but a malfunction is generated when the same diagnostic occurs for at least 30 minutes in the last 24 hours
P. Power Compliance: Occurs when an ELD is not powered for a cumulative in-motion driving time of 30 minutes or more over a 24-hour period across all driver profiles using that particular ELD
➢ Resolution: Make sure the driver is connected to the ECM device on the application. Have the driver go to Scan Devices and select their specific ECM device. Have them check if all engine parameters pass the diagnostics (all green). If not perform steps II-D.
E. Engine Synchronization Compliance: Occurs when an Engine Synchronization Data Diagnostic occurs for a cumulative period of 30 minutes within a 24 hour period (for instance multiple periods of no ECM data that, when added together, are more than 30 minutes in the last 24 hours)
➢ Resolution: Make sure the driver is connected to the ECM device on the application. Have the driver go to Scan Devices and select their specific ECM device. Have them check if the diagnostic passes all engine parameters (all green). If not perform steps II-D/E.
T. Timing Compliance: Occurs when the timestamp on the ELD compared to an external time source are different (the ELD time must be synchronized with UTC, not to exceed an absolute deviation of 10 minutes at any time)
➢ Resolution: Make sure the driver has the Date and Time Settings on their mobile device set to “automatic.” Advise them that they can not manually change the date or the time on the application
L . Positioning Compliance: Occurs when an ELD fails to acquire a valid position measurement within 5 miles of the commercial motor vehicle moving and 60 minutes has passed
➢ Resolution: Make sure the “Always On” Location permission is enabled for the Apollo application on the driver’s mobile device R – Data Recording Compliance: Occurs when an ELD can no longer record or retain required events or retrieve recorded logs that are not kept remotely by the motor carrier ➢ Resolution: Make sure the driver has sufficient internal storage on their mobile device. Advise them to delete unneeded files/ data to make room if necessary
S. Data Transfer Compliance: Occurs when a Data Transfer Data Diagnostic triggers and the ELD stays in the unconfirmed data transfer mode following the next three consecutive monitoring checks
➢ Resolution: Verify that the driver has an active cellular or Wi-Fi connection on their mobile device.
I. References of ELD law for this issue:
1. List of all required data elements that ELD must collect: eCFR :: 49 CFR 395.26 -- ELD data automatically recorded.
2. Compliance Data Diagnostics & Malfunctions: eCFR :: Appendix A to Subpart B of Part 395, Title 49 -- Functional Specifications for All Electronic Logging Devices (ELDs), Section 4.6.1
© 2023 Transcare - All Rights Reserved