User manual for "Big Rig ELD"

Below you will find the vendor-provided user manual for the ELD product "Big Rig ELD".

For vendor contact details and additional devices from the same company, see their page Big Rig Fleet Services.

Manual text preview

1

Big Rig ELD
Driver Guide

Topics:
Main Dashboard --------------------------------------------------- Page 2
Driver Options ------------------------------------------------------ Page 39
Driver Logs ---------------------------------------------------------- Page 53
Editing a Driver Logs ----------------------------------------------- Page 67
DVIR ------------------------------------------------------------------ Page 82
Data Transfer ------------------------------------------------------- Page 99
Switch Equipment ------------------------------------------------- Page 111
Switch Driver -------------------------------------------------------- Page 127
Team Driving -------------------------------------------------------- Page 133
Documents ---------------------------------------------------------- Page 139
Fuel Receipts -------------------------------------------------------- Page 145
Preferences/Settings Menu --------------------------------------- Page 151
Malfunction and Data Diagnostic Events ----------------------- Page 179

2

3

Main Dashboard
The Main Dashboard main screen is where you log your duty status events and which, in turn, determines your
compliance with FMCSA Hours of Service Regulations. This screen also serves as your gateway to the rest of the
apps features.

The main screen also provides essential information about the apps user:

4
Driver Name: Displays the name of the driver who is logged in and whose logs are displayed.

Vehicle Name: Displays the drivers vehicle name.

Trailer Name: Displays the drivers trailer.

Note: The layout shown above is the default arrangement of buttons for the Main Dashboard. The button layout for
the Main Dashboard and the Options screen can be configured and rearranged in the portals Button Editor
1. Using Hours of Service Action Bar
The Hours of Service Action Bar is the starting point for navigating to the different pages in the HOS app and is
always present in the apps topmost portion.

It features the following main navigational controls of the HOS app:
a.
b.

Main Navigation Hamburger Icon: Tap to open the main navigation menu of the HOS app.
Pending Edit Request Button: Icon only displays when there are request to edit events from Motor
Carrier Personnel and Co-Driver(s). Tap the icon to display the list of pending edit request(s) which driver(s)

5
will take action to accept or reject a specific request. Pending Edit Request(s) display includes requested
edits for a day that is beyond the 8 days log for USA cycle (14 days log for Canada cycle).

Note: On instances where the vehicle has been moving for more then 3 minutes while there is no driver
logged in, the ELD automatically records this activity as "Unidentified Driving Events" under the driver:
"Unidentified Driver". These events can be reassigned to actual drivers upon logging in to the app, under
Pending Request(s).

If the driver accepts the edit request(s) then the new status will be displayed on the events history list and
will replace the old status.

6

Accepting the requested edits of the day that is beyond the last 8 days log for USA cycle (14 days log for
Canada cycle) will display a warning dialog informing that driver needs to recertify the log at logout on the
app or driver can log into the drivers portal to certify the log for that day.

If the driver rejects the edit request(s) then it will not replace the original status however the status will still
be recorded in the events history list with a note Inactive Change Rejected (ICJ).

7
The Reject and Accept Event dialog shows the comparison of the Original status vs the changes (requested
edits) made by the Motor Carrier Personnel. Once the edit requests are accepted, it will require the driver to
fill in the annotation field (Required, maximum of 60 characters) to successfully save the changes.On the
Main Dashboard, Tap on Logs button then edit logs. The driver can check in the events history list for the
accepted and rejected event statuses.
Notes:
a. Odometer field is displayed for edit request(s) made by the Personnel
b. Vehicle Miles field is displayed for edit request(s) made by the Unidentified Driver
c. The Unidentified Driving Event pending edit request dialog has additional details like: From, To &
Equipment ID compared to that of the Personnels pending edit request dialog
c.

Refresh Button: Tap to manually refresh the data in the HOS app page. Hidden under
icon once all icons are present.

submenu

d.

Logout Button: Tap to log out of the app, this will also set your status to Off Duty. Hidden under
submenu icon once all icons are present.

Logging out of the HOS app when the status is "Driving/On Duty" will pop up a different message dialog and
will also set the driver status to Off Duty.

Note: Once the go off-duty option is checked, all the valid driver that logged into the HOS app will be
logged out and the HOS app will be close completely (with no Snaptraq service or VBUS service running in
the background). If the Driver is an Exempt Driver or a driver that operates under the short-haul exemption
(395.1 (e)), upon logging in or out, a dialog will display confirming whether the driver chooses to continue as
an exempt driver. By selecting the OK button, the No Logs for Non-CDL-Driver Short-Haul Drivers operating

8
within 150 air-miles exception will be enabled.

e.

Malfunction Button: Tap to display the Malfunction Event(s) dialog .

Malfunction and Data Diagnostic icon is displayed always in the toolbar. Malfunction Indicators acquired by
the driver will be displayed in the applications Header which is always visible across all screens. There will
also be a notification in the Android toolbar indicating a malfunction.

9
To clear the malfunction, tap on the Clear button. The Clear Malfunction dialog will then be displayed.

At each instance when an ELD malfunction or data diagnostic event is detected or cleared by the ELD, the
ELD records the event.
Note: A Power Malfunction & Diag

Read the full extracted text