Diagnostic and Malfunction Alerts

Last updated
Save as PDF

Overview

The ELD Mandate requires that an ELD monitor its compliance with ELD technical requirements and detect malfunctions and data inconsistencies related to:

power
data synchronization
missing data
timing
positioning
data recording
data transfer
unidentified driver records

When an Electronic Logging Device (ELD) malfunctions, drivers are required to maintain paper logs for the current 24-hour period as well as the preceding seven days. This practice must continue until the ELD is restored to proper working order. The carrier is responsible for correcting, repairing, replacing, or servicing the malfunctioning ELD within eight days of either identifying the issue or receiving notification of the malfunction, whichever occurs first.

It is important to note that diagnostic events may be triggered frequently due to the stringent compliance thresholds established by the ELD Mandate. Occasional diagnostic messages do not necessarily indicate a vehicle issue and typically do not require corrective action. However, if a diagnostic event becomes persistent or results in a malfunction, corrective measures must be taken. Users are advised to monitor any events that remain active or recur over several days. Should a malfunction persist for eight days or longer, the affected vehicle must be removed from service until the ELD is repaired.

Omnitracs One(OT1) includes features that enable you to monitor and log diagnostics and malfunctions. The Omnitracs ELD Device also immediately sends a notification to the motor carrier, viewable on the Omnitracs Host website, that a malfunction has occurred.

When an ELD malfunction or an ELD diagnostic is detected, the mobile displays a red X (for malfunction) or orange exclamation mark (for diagnostic) as an indicator on the right side of the status indicator bar of the mobile dashboard.

Malfunction Indicator

Diagnostic Indicator

Malfunction and Diagnostic Indicator

Click on the indicator to open the Diagnostics and Malfunction screen, which lists any Diagnostic or Malfunction events that have been detected since login.

There are various types of diagnostic and malfunction events that indicate there is a problem with the device. Below is a list of the types of events you may see, and what causes them to be generated. These events can be seen in mobile and in the HOS Diagnostic and Malfunctions reports.

Compliance Area	Diagnostic	Malfunction	Possible Cause	Suggested Action
Power Compliance	A power compliance data diagnostic event occurs when an ELD is not powered and fully functional within one minute of the vehicle’s engine receiving power and does not remain powered for as long as the vehicle’s engine stays powered. It is triggered when the telematics detects a gap in engine running time while powered down, or when Omnitracs Mobile identifies distance accumulation (using odometer data) during a period when the device was powered down. Upon powering up, the system checks for vehicle activity during the power-down period. If detected, paired “logged” and “cleared” events are created, with timestamps marking when the device was powered down and powered back up, respectively.	A power compliance malfunction occurs when an ELD is not powered for an aggregated in-motion driving time of 30 minutes or more over a 24-hour period across all driver profiles. It is identified when the distance between odometer readings at the time of the diagnostic logged and cleared events exceeds 15 miles in the current log day. Omnitracs Mobile uses a mileage gap to determine the 30 minutes of in-motion time specified by the ELD. The driver will not be placed into paper log mode when this malfunction occurs.	This may occur if the telematics device was unplugged, lost power due to poor cabling, a weak vehicle battery, or cold cranking. It can also result from the mobile device battery needing recharging, the truck being on or off during reboot, or the mobile device being turned off.	Drivers should keep their mobile device on and the Omnitracs telematics device plugged in while the vehicle is in motion. Vehicle maintenance crews should ensure the telematics device is securely connected and follow recommended mounting procedures, checking vehicle battery voltage as needed.
Engine Synchronization Compliance	An engine synchronization data diagnostic event occurs when there is a loss of any required parameters or a loss of connection/data from the vehicle network. Monitored parameters include engine power status (rpm), vehicle motion status (speed), miles driven (odometer), and engine hours and can no longer acquire updated values for the required ELD parameters within five seconds of the need.	An engine synchronization compliance malfunction is triggered when more than 30 minutes accumulate during the log day without ECM connectivity to any required data parameters. The driver will remain in paper log mode until disassociating from the vehicle or until the end of the log day.	Causes include sensor failure (such as speed sensor, ECM, or other controller), cabling problems, use of incorrect cable, vehicles manufactured prior to 2000 lacking a vehicle network, or non-class 8 vehicles unable to produce required data.	Check the Fault Code report for related issues. Maintenance crews should use diagnostic tools to examine fault codes, troubleshoot the vehicle network, and inspect sensors and cabling. Ensure the correct cable is used for the vehicle type, and initiate the Device Swap Process if needed. Refer to the Knowledge Base for more information.
Data Recording Compliance	A Missing Required Data Elements diagnostic event occurs when the ELD attempts to create an event but one or more required data fields are missing at the time of recording. The missing element is displayed as “N/A” in the driver’s log event list.	A data recording compliance malfunction 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. Could occur when available memory on the mobile device falls below 15% or storage space drops below 100MB. The driver will be placed into paper log mode until memory exceeds 30% or storage is above 200MB.	Diagnostic issues may be related to other diagnostics causing missing data, or an ELD event being created while the mobile device lacks connectivity with the telematics device . Malfunctions may be caused by insufficient storage space or a memory leak on the mobile device.	For diagnostics, if the cause is an ELD event created without vehicle connectivity, no action is necessary. If related to another diagnostic, review the secondary cause. For malfunctions, clear files to increase free space and reboot the mobile device.
Data Transfer Compliance	A Data Transfer Data Diagnostic event occurs when the eRODS file generation automatic self-test (performed every 7 days) fails to generate a file. When triggered, the self-test frequency increases to once every 24 hours (while a driver is logged in). The test does not attempt to transfer a file to FMCSA.	A data transfer compliance malfunction occurs when the self-test fails to generate a file three times in a row (performed every 24 hours). The malfunction is cleared when a valid eRODS file is generated.	Insufficient storage space on the mobile device to generate the eRODS file.	Increase available storage by removing non-essential files such as photos or videos.
Unidentified Driving Profile	An unidentified driving records data diagnostic event occurs when more than 30 minutes of driving time for an unidentified driver is recorded for the current vehicle within the current log day or any of the previous seven days. The diagnostic is cleared when driving time for an unidentified driver falls below 15 minutes within the current log day and previous seven days. The event will appear on the ELD Driver Log Report for each driver who connects to the vehicle during the seven-day period after the event is recorded.	N/A	Occurs when Vehicle was operated without a driver connecting to telematics device.	Drivers must log into Omnitracs Mobile and associate with the telematics device before moving the vehicle. Use the mobile app for all drivers, including short haul or ELD exempt drivers. The diagnostic is cleared once the UVA in the currenty duty cycle is under 15 minutes
Position Compliance	N/A	A Position Compliance Malfunction occurs when both the Omnitracs telematics GPS and the mobile GPS fail to acquire a valid position within 5 miles of vehicle movement and 60 minutes of movement have been recorded during the current log day without a valid location. The driver will be prompted to keep paper logs, but the mobile app will not enter Paper Log Mode automatically. If the driver does not enter Paper Log Mode manually, the malfunction indicator will display until the driver disassociates from the vehicle or until the end of the log day. When the malfunction clears (at the start of a new company day), the message “You may resume use of the ELD as your Record of Duty status” appears.	Can occur if the telematics device is improperly installed or blocked from receiving a GPS signal, or if location services are not enabled on the mobile device. Both telematics device and mobile must fail to provide coordinates for the issue to occur.	Maintenance crews should follow mounting procedures and properly install the telematics device . Enable location services on the mobile device.
Timing Compliance	N/A	A timing compliance malfunction occurs when the mobile application's time deviates from its reference UTC source (either the Omnitracs website or mobile device GPS time) by more than 10 minutes. The driver will remain in paper log mode until the time deviation falls below 10 minutes.	Occurs when there is no data network availability and no GPS connectivity at the same time.	Log out and back into the mobile app, enable location services, and restore cell network connectivity. 1. Open Settings 2. Select System (or General Management, depending on the device) 3. Tap Date & time 4. Turn on Set time automatically or Use network‑provided time
Other ELD (Bluetooth) Malfunction	N/A	An Other ELD (Bluetooth) malfunction occurs when there is a Bluetooth connectivity issue between Omnitracs Mobile and the telematics device . When the driver logs out or disassociates from the vehicle, paper log mode ends and the malfunction is cleared. This issue is caused when the mobile device cannot connect to the telematics device due to loss of Bluetooth connectivity and the driver opts to enter Paper Log Mode. The malfunction will not occur if the driver does not elect to begin Paper Log Mode.	Omnitracs Mobile unable to connect to the telematics device due to Bluetooth connectivity loss and driver selection of Paper Log Mode.	Check that Bluetooth is enabled and the mobile device is within range. Toggle Bluetooth off and on if needed.

Here is the Standard Coding for Required Compliance Malfunction and Data Diagnostic Event Detection:

The diagnostic/malfunction status indicator and related code will display on the Driver Log Header tab whenever there is an active diagnostic/malfunction event (see image).

Omnitracs One(OT1) provides two reports that help monitor compliance with these requirements. The ELD Diagnostic and Malfunction Summary Report and Diagnostic and Malfunction Detail Report provide users with information about malfunctions and data diagnostic events that occur within a specified date range. These reports provide insight into the frequency and causes of diagnostic or malfunction events, enabling users to assess whether corrective action is warranted. Refer to the corresponding section for more information.