User manual for "Rand McNally Vehicle Link"

Below you will find the vendor-provided user manual for the ELD product "Rand McNally Vehicle Link".

For vendor contact details and additional devices from the same company, see their page Rand McNally.

Manual text preview

User Manual
for Android

Navigating the Rand VL App
The Dashboard is the first screen you see after
you log in.
1. The WORK/BREAK TIMERS section
automatically shows your remaining drive and
shift times.

3

2. Tap a Status Button to change your duty status.
3. Tap the Main Menu to access the main
functions of DriverConnect.

1

4. In the Main Menu, tap:
 Inspection Mode to send your logs to 		
		 a Law Enforcement Officer (LEO)
 DVIR to create or edit a Driver-Vehicle 				
		Inspection Report
 Logbook to view and edit your HOS logs

2

4

Go On Duty: Select Rule Set
To go On Duty, you must define a Rule Set, set your trip information, and complete a DVIR. A green check
shows completed steps.
1. From the Dashboard, tap the ON icon in the
bottom duty status bar.
The Change Status page displays.

2. Verify your rule set. Your current rule set 		
displays to the right.

2

Tap Rule Set to make changes.
3. Select a new rule set, and any exemptions/		
exceptions that apply.
Tap CHANGE, then the Back arrow to return 		
to the Change Status screen.

1
Note: To go Off Duty again,
tap OFF on the Dashboard.

3

Go On Duty: Update Trip Information
Before you drive, you need to enter information
about your vehicle and your cargo. The Trip Info
setting allows you to set your Tractor Number,
Trailer Number, and up to 5 Bills of Lading (BOL).
You can change this information at any time.

3

1. On the Change Status page, tap Trip Info.
2. Enter your Trip Name, Tractor Number, Trailer
Number, Shipping Document Number, Fuel
Type, and up to 5 Bills of Lading (BOL) in the
fields, as needed.
3. Tap SAVE, then the Back arrow to return to
the Change Status screen.

Note: You can also access the Trip Info screen
by tapping Settings on the Main Menu,
then tapping Trip Info.

1
2

Go On Duty: Pre-Trip DVIR
1. On the Change Status page, tap DVIR.
2. On the DVIR page, tap + to create a
new DVIR.

1

2

3. On the Create New DVIR page, verify the
Tractor Number and Trailer Number.
4. Add defects by selecting the checkboxes in
the Tractor Defects and/or
Trailer Defects sections.

3
5

5. Enter comments (if needed) and your name.
6. Tap Upload to select a picture (up to 3)
to include on the DVIR.
7. Tap SAVE, then the Back arrow to return
to the Change Status screen.

4

6
7

Update Previous Duty Status
You can edit an HOS log that has not yet been
certified from the Log Detail screen.
1. From the Main Menu, tap Logbook, then
tap the HOS graph of the date to edit.
2. Tap the chart, or a status line, on the Log Detail
screen to edit the status.

1

2

3. Tap and drag the start and end time sliders,
or tap the time fields, to define a new
time frame.
If you tap the time fields to enter a time
manually, then tap SELECT TIME to
confirm the time.

5
3

4. Tap a status icon for the new time frame,
and enter a location and a note.
5. Tap SAVE.

4

Malfunction Indicators
1. Tap on the Connected to Device when the app
is connected to the ELD. The data diagnostic and
malfunction events indicators are shown.
2. Indicator lamps will display green when there are
no diagnostic or malfunction events. Otherwise
they will display red.
3. Tap on the diagnostic indicator to view the diagnostic events or tap on the malfunction indicator
to view the malfunction events when the indicator
lamp is red.

ELD Malfunctions
The instructions below outline the procedures set forth under FMCSA rule 395.34 - ELD malfunctions and data
diagnostic events.
Rand McNally records data diagnostic events automatically and stores them in the Fleet Portal. ELD malfunctions and
diagnostic events can be found in the HOS log page in the Rand McNally Fleet Portal. No action by the driver is required to
record diagnostic events
Driver
In case of an ELD malfunction, a driver must do the following:
1. Determine if the event is a data diagnostic event, or malfunction event. The malfunction of the ELD and provide written
notice of the malfunction to the motor carrier within 24 hours.
2. Reconstruct the record of duty status for the current 24-hour period and the previous 7 consecutive days, and record
the records of duty status on graph-grid paper logs that comply with  395.8, unless the driver already possesses the
records or the records are retrievable from the ELD.
3. Continue to manually prepare a record of duty status in accordance with  395.8 until the ELD is serviced and brought
back into compliance.

Fleet managers
When a malfunction of an ELD is discovered the fleet manager should do the following:
The fleet manager must service, repair or replace the ELD within 8 days of receiving such written notice or
discovering the malfunction. [To request more clarification regarding the data diagnostic or malfunction events
please contact Rand McNally support.]
If a fleet seeks extension period, then the FMCSA division administrator of the state for motor carriers principal place
of business shall be notified within 5 days of receiving such written notice or discovery of malfunction.
https://www.federalregister.gov/documents/2015/12/16/2015-31336/electronic-logging-devices-and-hours-of-servicesupporting-documents [Refer to section  395.34]

FCC Compliance Statement
This device complies with part 15 of the FCC rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2)
this device must accept any interference received, including interference that may cause undesired operation. This equipment has been tested and found to comply
with the limits for a Class B digital device, pursuant to part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses, and can radiate radio frequency energy and may cause harmful interference to radio communications if not installed and used in accordance with the instructions. However, there is no guarantee that interference will not occur in a particular install

Read the full extracted text