This article describes the various diagnostic events and malfunctions that can be raised in the Hours of Service mobile app and the corresponding actions that you must take as a driver.
Diagnostic events:
Malfunctions:
When using WorkPlan as an AOBRD, the single diagnostic event "AOBRD Sensor Failure" is supported. It is raised when there is no GPS signal. The diagnostic events and malfunctions described below are applicable only to the ELD version of the app.
If you have any malfunctions in the US, you must correct them within 8 days. See below for required actions.
The following sections show the various types of diagnostic events that you might encounter.
Vehicle use was detected while the ELD was not powered on. Ensure that the VTU (vehicle tracking unit) is firmly connected and there are no loose wires to avoid going into malfunction.
If this issue leads to the aggregated driving time being reduced by 30 minutes over a 24-hour period across all drivers using this vehicle, including unidentified drivers, a power compliance malfunction is raised.
-
The VTU has lost power during operation.
-
The VTU has become unplugged.
-
The VTU did not start up within a minute of the engine being turned on.
Your mobile device lost connection to vehicle data. Ensure that Bluetooth is always enabled on your mobile device and that you shut down the vehicle before taking the tablet out of range.
While this diagnostic event is raised, the data on engine power status, vehicle motion status, miles driven, and engine hours can no longer be accessed. If the connection is lost for 30 minutes or more during a 24-hour period, an engine sync compliance malfunction is raised.
-
The VTU was not installed correctly.
-
The VTU is out of range of the mobile device; for example, because the driver walked away from the vehicle with the mobile device while the vehicle’s ignition was on.
-
The VTU is faulty.
-
The mobile device has Bluetooth turned off.
-
You did not log out or disconnect from the vehicle properly.
-
An intermittent or loose connection to the vehicle’s ECM.
-
Log out of the HOS app properly at the end of your shift.
-
Ensure that Bluetooth is turned on.
-
Ensure that you turn the vehicle’s ignition off before you take the mobile device out of range of the vehicle’s VTU.
-
Follow the instructions in Troubleshooting Connectivity Issues.
Follow the instructions in Troubleshooting Connectivity Issues.
-
Contact your carrier if the problem persists.
The automatic data transfer check has failed and now the check will be performed once within each 24-hour period. If this check fails four consecutive times for the same vehicle, a data transfer malfunction will be raised. This means that you might have issues if you try to transfer your data.
-
The most common cause for data transfer failures is missing data, such as carrier names, DOT numbers, and driver details.
-
A connection cannot be established for the data transfer.
-
Your vehicle has an unknown ELD hardware type.
-
You did not have an internet connection while the ELD connected to your vehicle tracker.
More than 30 minutes of unidentified driving was detected within a 24-hour period. To clear the unidentified driving events, review and claim any driving that belongs to you.
More than 30 minutes of unidentified driving was detected within a 24-hour period. To clear the unidentified driving events, review and claim any driving that belongs to you.
-
You did not log in prior to driving the vehicle.
-
You did not establish a connection to the selected vehicle prior to driving the vehicle.
-
Log in to the HOS app and select a vehicle prior to driving a vehicle.
-
Regularly claim all unidentified driving that belongs to you.
Regularly claim all unidentified driving that belongs to you.
Note
In the US, malfunctions must be corrected within 8 days. You can request an extension to this time period. To do this, follow the guidance on this FMCSA page.
In Canada, malfunctions must be corrected within 14 days after the day on which the malfunction was reported.
These are the actions that you must take immediately, independent of the type of malfunction that you received:
-
Provide written notice of the malfunction to your motor carrier within 24 hours.
-
Ensure that you have an accurate record of duty status (RODS) for the current 24-hour period and the previous 7 consecutive days in the US or for the previous 14 days in Canada. This can be either in the form of records from the ELD or RODS on compliant graph-grid paper. If necessary, manually reconstruct the RODS for any missing period. In Canada, the entries must include the malfunction code.
-
In the US, continue to manually prepare compliant RODS on graph-grid paper for up to 8 days or until the ELD is serviced and back in compliance.
In Canada, continue to manually prepare compliant RODS on graph-grid paper for up to 14 days after the day on which the malfunction was reported, or until your return to the home terminal from the current trip, if the trip lasts longer than 14 days. After this period, the ELD must be serviced and back in compliance.
For further information, see this FMCSA FAQ article for the US or Justice Laws Website for Canada.
The following sections show the various types of malfunctions that you might encounter, with corresponding actions that are specific to the malfunction, and in addition to the required actions described above.
More than 30 cumulative minutes of vehicle use were detected in the last 24 hours while the ELD was not powered on.
-
The VTU has lost power during operation.
-
The VTU has become unplugged.
-
The VTU did not start up within 30 minutes of the engine being turned on.
-
Confirm that the VTU has not been unplugged or tampered with.
-
If the vehicle has a low battery voltage (below 12 volts), the unit might not report correctly due to the low voltage. We recommend that you run the vehicle for a while to recharge the vehicle's battery. This could be a sign of a vehicle battery deteriorating and not keeping a charge. Report any voltage issue to your carrier.
-
As a driver, you must maintain paper logs until the issue has been resolved and you have completed your current shift or changed vehicles.
-
If the problem persists, contact Verizon Connect support.
Your mobile device lost its connection to vehicle data for 30 cumulative minutes in the last 24 hours. During this time, the data on engine power status, vehicle motion status, miles driven, and engine hours could not be accessed.
-
Confirm that Bluetooth is always enabled on your mobile device.
-
Shut down the vehicle before taking the mobile device out of range.
-
As a driver, you must maintain paper logs until the issue has been resolved and you have completed your current shift or changed vehicles.
-
If the problem persists, contact Verizon Connect support.
-
Ensure that your mobile device is set to the same time zone used at your home terminal.
-
As a driver, confirm that your mobile device is using the automatic update option for time.
-
On Android devices go to Settings > Date and Time and enable Automatic date and time.
-
On iOS devices go to Settings > General > Date & Time and enable Set automatically.
-
-
As a driver, you must maintain paper logs until the issue has been resolved and you have completed your current shift or changed vehicles.
-
If the problem persists, contact Verizon Connect support.
-
Confirm that your vehicle is not inside or under any cover.
-
Check your GPS aerial (if applicable).
-
As a driver, you must maintain paper logs until the issue has been resolved and you have completed your current shift or changed vehicles.
-
If the problem persists, contact Verizon Connect support.
Your mobile device does not have adequate storage space. The mobile device can no longer record new events and you might lose events that have not been uploaded yet.
-
Remove any unnecessary files and applications to free up storage space on your mobile device.
-
As a driver, you must maintain paper logs until the issue has been resolved and you have completed your current shift or changed vehicles.
-
If the problem persists, contact Verizon Connect support.
The automatic data transfer check that is done once within each 24-hour period has failed 4 times consecutively. This means that you might have issues if you try to transfer your data.
The most common cause for data transfer failures is missing data, such as carrier names, DOT numbers, and driver details.
-
Confirm that your mobile device has an internet connection.
-
As a driver, you must maintain paper logs until the issue has been resolved and you have completed your current shift or changed vehicles.
-
If the problem persists, contact Verizon Connect support.
Comments
0 comments
Please sign in to leave a comment.