MALFUNCTIONS EXPLAINED
Malfunction events show up in the application header bar as a capital M. The M will flash red when activated. Malfunctions should be cleared, and any required action must be taken as soon as possible.
Individual malfunctions must be cleared separately and recorded by the carrier. If a Malfunction continuously records an event, you should contact your ELD provider's Help Center or your carrier administrator.
Power Compliance Malfunction
An ELD must set a power compliance malfunction if aggregated driving time exceeds 30 minutes or more on the ELD over a 24-hour period across all driver profiles, including the unidentified driver profile
What a driver needs to do
Ensure the application is connected via Bluetooth to the module connected to the vehicle's ECM and no unidentified is left unclaimed.
If unidentified events are active for more than 30 minutes during the current 24-hour period, a power compliance malfunction will occur.
Engine synchronization malfunction
An ELD must set a power compliance malfunction if aggregated driving time exceeds 30 minutes or more on the ELD over a 24-hour period across all driver profiles, including the unidentified driver profile
What a driver needs to do
Ensure the application is connected via Bluetooth to the module connected to the vehicle's ECM and no unidentified is left unclaimed.
If unidentified events are active during the current 24hr period that exceeds 30 mins, this will cause a power compliance malfunction to occur.
Timing compliance malfunction
The ELD RODS data is captured in the time zone of the driver’s home terminal. If the ELD UTC time does not match the time zone the device is in, by more than 10 minutes, the ELD will record a Timing Compliance Malfunction.
Example: Driver HOS profile is set to MST and the driver drives to PST time zone. The ELD device is set to Automatic Time Zone Detection or Automatic Time Zone Adjustment (Operating setting of the IOS or Android device). When the driver moves to the PST time zone this will be greater than 1hr from the driver’s home terminal UTC zone.
What a driver needs to do
Disable the Automatic Time Zone Detection or Automatic Time Zone Adjustment function on the device but, be prepared, you will need to accommodate for the time adjustment.
Positioning compliance malfunction
An ELD must monitor elapsed time during periods when the ELD fails to acquire a valid position measurement within 8 kilometers of vehicle movement. When such elapsed time exceeds a cumulative 60 minutes over a 24-hour period, the ELD must set and record a positioning compliance malfunction.
What a driver needs to do
Check and ensure the IOS or Android devices have all settings enabled to record location correctly. This can be found in the device’s settings under app settings for the Titan FeildDocs ELD, location should be set to allow all the time and physical activity to allowed
Data recording compliance malfunction
The ELD will automatically monitor its storage capacity and integrity if the ELD can no longer record or retain required events or retrieve logs which aren’t catalogued by the motor carrier a data recording compliance malfunction will occur.
What a driver needs to do
Contact support or your administrator.
Data transfer compliance malfunction
An ELD must inspect to verify that the in-service monitoring function is verifying, at least once every 7 days, when the monitoring function fails to confirm proper in-service operation of any data transfer mechanism supported by the ELD.
What a driver needs to do
Contact support or your administrator.
How to clear a Malfunction event
Tap the icon to display the malfunction event(s).
2. Tap Malfunction.
3. Tap Clear (right side of the event information).
DATA DIAGNOSTICS EXPLAINED
Data Diagnostic events appear in the application’s header bar as capital D. The D will flash red when activated. Data diagnostic events are less formal than malfunctions and do not require the same urgency. However, it is ideal to clear all data diagnostics at the end of the day (multiple data diagnostics can be cleared at the same time). There is no need to record the data diagnostic unless the same one is recurring. Recurring data diagnostics may indicate an issue that can trigger a malfunction.
Power Data Diagnostic
Occurs when the ELD cannot determine if the engine is powered on for any duration over 15 minutes but less than 30 minutes between ignition cycle.
What a driver needs to do
Ensure the application is connected via Bluetooth to the module connected to the vehicle ECM.
Engine-synchronization data diagnostics
An event when the ELD can no longer acquire updated values for the ELD parameters required for records within 60 seconds between an ignition cycle.
What a driver needs to do
Ensure the application is connected via Bluetooth to the module connected to the vehicle ECM.
Missing data elements data diagnostics event
ELD is to monitor all data elements of all events. If a data element is missing this would create a data elements data diagnostic event. Example: engine hrs. are missing during an event
What a driver needs to do
Contact their fleet admin to confirm what data is missing in the drivers RODS data, if this continues to happen a data elements Malfunction will be the next identifier (See data elements Malfunction).
How to clear data Diagnostic event
1. Tap the icon to display the data diagnostic event(s) dialog.
2. Tap Data Diagnostics.
3. Tap Clear (right side of the event information).
