Managing HOS Events

Which Connectivity Issues Lead to Unidentified Driving?

This is a printed page that might be out of date. To read the most up-to-date help content, visit https://fleet-help.verizonconnect.com.
  • Updated

This article describes the various scenarios where connectivity issues between your ELD and your vehicle can lead to unidentified driving or cause driving time to be automatically assigned to you.

If you have issues connecting to your vehicle, see Troubleshooting Connectivity Issues.

Unidentified driving when disconnected from vehicle

If you are unable to connect to your vehicle, any driving time is recorded as unidentified driving.

For example:

  1. You sign in to HOS.

  2. Your vehicle is out of range or you cannot establish a connection with it. You can select the vehicle anyway.

  3. You receive a message stating that your driving time is recorded as unidentified driving:

    img-en-us-hos_trips_recorded_when_disconnected.png

  4. You cannot manually select the Driving status on the HOS Status screen, but your driving time is recorded automatically when you start driving.

  5. You can claim the unidentified driving time under Review > Unidentified Driving when you have completed the driving for your shift.

Unidentified driving when disconnected during the entire trip

When you are disconnected from your vehicle during an entire trip, the driving time is recorded as unidentified driving.

For example:

  1. You sign in to HOS.

  2. You establish a connection to your vehicle, and you are on duty, not driving.

  3. The app loses connection to your vehicle.

  4. You start driving and complete your entire trip without a connection to your vehicle.

  5. You stop driving.

  6. If you change status; for example, to Off Duty or Sleeper Berth; you receive the following message:

    img-en-us-hos_trips_recorded_as_UD.png

    You can claim the unidentified driving time by tapping CLAIM NOW or by tapping Claim later and navigating to Review > Unidentified Driving.

    If you resume the app, you are taken to the Review Events screen directly.

Unidentified driving when app closes down unexpectedly

When you are disconnected from your vehicle because the app closes down unexpectedly, the driving time is recorded as unidentified driving.

For example:

  1. You sign in to HOS.

  2. You establish a connection to your vehicle, and you are on duty, not driving.

  3. The app closes down unexpectedly.

  4. You start driving and complete your entire trip without a connection to your vehicle.

  5. You stop driving.

  6. You resume the app.

  7. The driving time is recorded as unidentified driving.

  8. You are taken to the Review Events screen, from where you can claim the unidentified driving time:

    review_events.zoom35.png

Unidentified driving time for a partial trip when connected at the end

In the following scenario, partial driving time is not assigned to you, as the driver. Instead, it is recorded as unidentified driving time that you must claim on the Unidentified Driving screen.

In this scenario, you are assigned to the vehicle at the end of the driving period. At the start of the driving period, the app loses connectivity to the vehicle. This can happen if you walk away from your vehicle with the mobile device, and then return to the vehicle and start to drive before the connection has re-established.

  1. You sign in to HOS.

  2. You establish a connection to your vehicle, and you are on duty, not driving.

  3. The app loses connection to your vehicle; for example, because you walk away from the vehicle with the mobile device and then return.

  4. You start driving while there is no connectivity to your vehicle.

  5. The app resumes and reconnects to your vehicle while you are driving.

  6. The first part of the driving time is not assigned to you. It is recorded as unidentified driving time that you must claim on the Unidentified Driving screen.

Note

In rare cases, this scenario could be caused by the app closing down rather than loss of connectivity to the vehicle.

No unidentified driving for a partial trip when connected at the start

In the following scenario, partial driving time is assigned to you, as the driver.

In this scenario, you are assigned to the vehicle at the start of the driving period and the app closes unexpectedly. This can happen when the app crashes or your device’s battery runs out.

  1. You sign in to HOS.

  2. You establish a connection to your vehicle, and you start driving.

  3. The app closes down unexpectedly while you are driving.

  4. You stop driving.

  5. When you resume the app, the entire driving time that accumulated since you started driving is assigned to you.

Note

  • In rare cases, this scenario could be due to loss of connectivity to the vehicle rather than the app closing down.

  • If you stop driving and the connection to the vehicle is then restored, the status change from Driving to On Duty is automatically added for the correct time in the past.

  • If you stop driving and the app does not reconnect to the vehicle, you must change your status manually to On Duty, Off Duty, or Sleeper Berth to stop the driving event, and then add it to your logs.

Co-driver scenarios

The following scenarios involve two drivers. In some cases, connectivity issues lead to unidentified driving.

Both drivers are unable to connect to the vehicle

  1. Both drivers sign in to HOS.

  2. Driver A is the active user and current driver.

  3. Driver A cannot establish a connection with the vehicle, but selects the vehicle anyway.

  4. Driver A receives the following message, stating that driving time is recorded as unidentified driving:

    img-en-us-hos_trips_recorded_when_disconnected.png

  5. Driver A starts driving.

  6. Driver A stops driving.

  7. Driver B is now the active user and current driver.

  8. Driver B also cannot establish a connection with the vehicle, but selects the vehicle anyway.

  9. Driver B starts driving.

  10. Driver B stops driving.

  11. All driving is recorded as unidentified driving. Each driver must claim the driving time that belongs to them.

Vehicle disconnected for the entire duration of the trip

  1. Both drivers sign in to HOS.

  2. Driver A is the active user and current driver.

  3. Driver A establishes a connection to the vehicle and is in the On Duty status.

  4. Driver A loses connection to the vehicle.

  5. Driver A starts driving.

  6. Driver A stops driving.

  7. Driver B is now the active user and current driver.

  8. Driver B cannot establish a connection with the vehicle but selects the vehicle anyway.

  9. Driver B starts driving.

  10. Driver B stops driving.

  11. All driving is recorded as unidentified driving. Each driver must claim the driving time that belongs to them.

Vehicle disconnected for driver B

  1. Both drivers sign in to HOS.

  2. Driver A is the active user and current driver.

  3. Driver A establishes a connection with the vehicle and selects the vehicle.

  4. Driver A starts driving.

  5. Driver A stops driving.

  6. Driver A disconnects from the vehicle.

  7. Driver B is the active user and current driver.

  8. Driver B cannot establish a connection with the vehicle but selects the vehicle anyway.

  9. Driver B starts driving.

  10. Driver B stops driving.

  11. Driver A’s part of the driving is assigned to Driver A. Driver B’s part of the driving is recorded as unidentified driving.

Vehicle is disconnected for driver A

  1. Both drivers sign in to HOS.

  2. Driver A is the active user and current driver.

  3. Driver A establishes a connection with the vehicle and selects the vehicle.

  4. The vehicle loses the connection to the vehicle.

  5. Driver A starts driving.

  6. Driver A stops driving.

  7. Driver B is now the active user and current driver.

  8. Driver B establishes a connection with the vehicle and selects the vehicle.

  9. Driver B starts driving.

  10. Driver B stops driving.

  11. Driver A’s part of the driving is recorded as unidentified driving. Driver B’s part of the driving is assigned to Driver B.

Related articles

Comments

0 comments

Please sign in to leave a comment.