Diagnostic events are displayed in the application notification bar as a capital D. The D is yellow if there are new diagnostics not yet reviewed, or white if the current diagnostic(s) have been reviewed. Diagnostics are more informational and do not have to be handled with the same importance as malfunctions. We do suggest that all diagnostics are cleared at the end of the day. All diagnostic messages can be cleared at once unlike malfunctions that need to be cleared individually. Generally, diagnostics can be ignored unless the same one is coming up over and over again, which could indicate an issue and that a Malfunction will be thrown.
If you are looking for information pertaining to Malfunctions, please see Malfunction Events.
|FMCSA Req. No.||Event Name||Description|
|126.96.36.199||Power Diagnostic||(a) An ELD must monitor data it receives from the engine ECM or alternative sources as allowed, its onboard sensors, and data record history to identify instances when it may not have complied with the power requirements, in which case, the ELD must record a power data diagnostics event for the corresponding driver(s), or under the unidentified driver profile if no drivers were authenticated at the time of detection.|
|188.8.131.52||Engine Synchronization Diagnostic||(a) An ELD must monitor the data it receives from the engine ECM or alternative sources as allowed, its onboard sensors, and data record history to identify instances and durations of its non-compliance with the ELD engine synchronization requirement. (b) An ELD required to establish a link to the engine ECM must monitor its connectivity to the engine ECM and its ability to retrieve the vehicle parameters and must record an engine-synchronization data diagnostics event when it no longer can acquire updated values for the ELD parameters required for records within 5 seconds of the need.|
|184.108.40.206(d)||Missing Data Elements Diagnostic||(d) If a new ELD event must be recorded at an instance when the ELD had failed to acquire a valid position measurement within the most recent elapsed 5 miles of driving, but the ELD has not yet set a positioning compliance malfunction, the ELD must record the character “X” in both the latitude and longitude fields, unless location is entered manually by the driver, in which case it must log the character “M” instead. Under the circumstances listed in this paragraph, if the ELD event is due to a change in duty status for the driver, the ELD must prompt the driver to enter location manually. If the driver does not enter the location information and the vehicle is in motion, the ELD must record a missing required data element data diagnostic event for the driver.|
|220.127.116.11||Data Transfer Diagnostic||(a) An ELD must implement in-service monitoring functions to verify that the data transfer mechanism(s) are continuing to function properly. An ELD must verify this functionality at least once every 7 days. These monitoring functions may be automatic or may involve manual steps for a driver. (b) If the monitoring mechanism fails to confirm proper in-service operation of the data transfer mechanism(s), an ELD must record a data transfer data diagnostic event and enter an unconfirmed data transfer mode. (c) After an ELD records a data transfer data diagnostic event, the ELD must increase the frequency of the monitoring function to check at least once every 24-hour period. If the ELD stays in the unconfirmed data transfer mode following the next three consecutive monitoring checks, the ELD must detect a data transfer compliance malfunction.|
|18.104.22.168||Unidentified Driver Diagnostic||(c) If more than 30 minutes of driving in a 24-hour period show unidentified driver on the ELD, the ELD must detect and record an unidentified driving records data diagnostic event and the data diagnostic indicator must be turned on for all drivers logged in to that ELD for the current 24-hour period and the following 7 days. (d) An unidentified driving records data diagnostic event can be cleared by the ELD when driving time logged under the unidentified driver profile for the current 24-hour period and the previous 7 consecutive days drops to 15 minutes or less.|
If you have any questions, please refer to ELD Flex – Driver Reference Guide.