Skip to content
English
More support Sign in
Go to www.brightorder.com
  • There are no suggestions because the search field is empty.

Understanding Automatic Driving and ON-Duty Logs

This article is intended for CloudHawk ELD users and explains how Electronic Logging Devices (ELDs) automatically record driving time (D) and prompt drivers to switch to on-duty (ON) status based on vehicle movement and user interaction.

Electronic Logging Devices (ELDs) use defined vehicle activity criteria to automatically record driving time and manage on-duty status. Understanding these rules is key to maintaining accurate Hours of Service (HOS) records. Here's how the automatic logging process works:

Automatic Driving Logs (D)

  • Your ELD automatically records driving time based on the vehicle's speed. Once the vehicle's speed reaches 8 km/h (5 mph), the ELD begins to record this time as Driving (D).

Automatic On-Duty Logs (ON)

  • When your vehicle comes to a complete stop for at least 5 consecutive minutes, the ELD system prompts you through the CloudHawk ELD App to confirm your current duty status.
    • You will be asked to indicate whether you are still on-duty or if your driving is finished.
    • If you confirm that you are no longer driving, or if you do not respond to the prompt within 60 seconds, the ELD will automatically change to On-Duty Not Driving (ON).

Important to Know

  • The speed threshold for automatic driving logs is 8 km/h (5 mph).
  • A prompt for duty status change occurs after being stopped for at least 5 minutes.
  • Failure to respond to the prompt within 60 seconds will result in an automatic change to On-Duty Not Driving (ON) status.

Critical Information

  • If your mobile device disconnects from the dongle's Bluetooth before you switch to ON-Duty (manually or automatically), the system will continue recording 'Driving' time—even if the vehicle is stopped and powered down. This will lead to an extended and unintentional 'Driving' event that by law, cannot be edited to remove or reduce driving time and will need to be annotated as a system or user issue.