User manual for "VDOS ELD"

Below you will find the vendor provided user manual for the ELD product "VDOS ELD".

For contact information and additional devices produced by the same vendor see their page Sunbelt Rentals.

Driver In Cab Instruction Card VDOS with ELD

Updated 11/17/2017

VDOS / Geotab HOS Driver Instruction Guide
VDOS with ELD is powered by Geotab and meets the requirements of section 395.15 of 49 CFR part 395.

STEP 1- Logging In
1

At the start of your shift launch the VDOS application from your mobile device and enter your
credentials. The user ID is your 5 digit clock ID, and the password is the last 4 digits in your social
security number. After entering your credentials select Clock In.

Once authenticated your mobile device will download your previous 7 days worth of logs.

If a vehicle that you are the last known operator of has been moved without a driver associated to it
you will be asked if the unidentified logs belong to you. At this point select any that belong to you and
press Claim, if none belong to you do not select any and press Claim.

4 The next step is to verify any logs that have not previously been verified in your electronic
logbook. This is done by reviewing, selecting individually, or all as a group and clicking the Accept
button in the upper right corner of the screen.

Updated 11/17/2017

STEP 2 - Vehicle Selection
1
2
3

Select Drive Vehicle from the Employee Menu.
A list of available vehicles at your profit center will populate, make your selection by taping on the
vehicle, and then tapping the Drive button.
Add your trailer on the screen that immediately follows or select No Trailer if you are not towing,
then tap Drive.

STEP 3 - Vehicle Inspection
1

After selecting your vehicle, you will be required to complete a thorough Daily Vehicle Inspection
Report or DVIR. The previous inspection report for the vehicle you have selected is available for
you to review at the top of the screen.
Any noted deficiencies will create a work order in Wynne, upon close of that work order the DVIR
will be updated with information relevant to that repair including the technician name, corrective
action taken, and date/time.
Once your DVIR has been completed you are required to certify the vehicle safe to operate, or
choose another vehicle if that one is not safe to operate.

Updated 11/17/2017

STEP 4 - Reviewing Hours of Service
1
2
3
4
5
6

From the Driver Menu choose the Hours of Service option.
The header page will display all relevant information regarding your current hours of service. This
includes a set of timers at the top of the page that will inform you of how many hours are
remaining in each status before a required break, or reset period is expected.
Driver, Vehicle, and ELD information, a graph log, and log entries are available for review from
here.
Previous days information is available by tapping on the book icon to the left of the log date. The
mobile device can be rotated to assist in viewing the logs.
The share button located in the upper right corner of the screen enables the driver to forward a
copy of their logbook to a requesting law enforcement officer via e-mail.
Along the bottom of the screen are tabs for other view options. The Chart tab will give a
graphical view of the current and previous seven day logs allowing the user to simply swipe left or
right, moving to the desired day. This is best viewed with the phone rotated to landscape. The
Log tab lists each log entry that is used to create the chart. The DVIR tab will allow you to
review your current Daily Vehicle Inspection Report.

Updated 11/17/2017

Troubleshooting
1

Unable to connect error received at login.
Resolve network connectivity issue with handheld device and reattempt to login. If you are unable
to correct the connection issue revert to paper logs and contact your supervisor.

Vehicle is not available in VDOS because the previous driver failed to punch out of it.
Physically type the asset number in at the top of the vehicle selection screen, and tap Drive. You
will be asked to confirm that the vehicle is correct because it is already assigned to a driver. Once
you confirm, you will receive a second notification and then you will be able to proceed. This
removes the other driver and associates you with that vehicle.

Alert received for expired driver license, or medical card.
Provide copy of renewed document to [email protected] so that it can be updated
in the system. Ensure that you have a valid copy of your driver license and medical card on your
person prior to operating any vehicle.

Continue to receive requests to claim unassigned driver logs.
You will be asked each day to claim logs that might potentially be yours as you are the last known
driver of the vehicle that created them. This will occur until your supervisor assigns them to the
appropriate driver or annotates them. If you continue to receive the same logs each day, ask your
supervisor to action them.

Logbook contains entries that are not mine because I accepted unidentified logs that did not
belong to me.
Request assistance from your supervisor to move the logs to the appropriate driver

VDOS is alerting me that the telematics device is malfunctioning, or is not connected to the
network.
Verify that the telematics device is securely plugged in and that the lights on the front are
illuminated. If you continue to have trouble immediately revert to paper logs and contact your
supervisor for assistance with the device.

Receiving alerts that I am overdue for a break or out of hours.
Confirm that you do in fact have hours remaining to work by reviewing your electronic logbook for
any missing punches, and appropriate reset times. Add missing punches if necessary on the Log
tab of the Hours of Service page on your VDOS mobile application by selecting the + in the
upper right hand corner of the screen.

Questions/Concerns contact the Sunbelt Rentals DOT Support Services Group @ 803-578-5300
or by email at [email protected]

Updated 11/17/2017

Data Diagnostics and Malfunction Events
Note: Data Diagnostic events cannot be cleared by the driver, these will auto clear once the
issue is resolved.
Diagnostic Data Diagnostic Event
Code
1

Power data diagnostic:
An ELD must monitor the data it receives from the engine
ECM and data record history to identify instances when it
may not have complied with the power requirements.

Engine synchronization diagnostic:
An ELD is required to establish a link to the engine ECM, and
must record an engine synchronization data diagnostics
event, when it no longer can acquire values for the ELD
parameters required for records within five seconds.

Missing required data elements data diagnostic:
An ELD must monitor the completeness of the ELD event
record information in relation to the required data elements
for each event type, and must record a missing data
element and data diagnostics event for the driver, if any
required field is missing at the time of recording.

Data transfer data diagnostic:
An ELD must implement in-service monitoring functions to
verify that the data transfer mechanism(s) are continuing to
function properly. An ELD must verify this functionality at
least once every seven days.

Unidentified driving records data diagnostic:
If more than 30 minutes of driving in a 24-hour period
shows unidentified driver on the ELD, the ELD must detect
and record an unidentified driving record data diagnostic
event, and the data diagnostic indicator must be turned on
for all drivers logged in to that ELD for the current 24-hour
period and the following seven days.

Other ELD Unidentified diagnostic:

What should I do next?
This may be caused by an intermittent or
disconnected connection to the vehicle ECM.
This is likely due to an install issue. Once
investigated, and the problem is resolved, the
system will auto clear the event.
This may be caused by an intermittent or
disconnected connection to the vehicle ECM.
This is likely due to an install issue. This may
also be caused if the ELD is unable to pick up
the required engine data from the vehicle ECM.
Contact your carrier if the problem persists.
Once investigated, and the problem is
resolved, the system will auto clear the event.
This can be caused by the creation of a manual
log by the driver when there is temporary loss
of GPS by the GO device. If the driver does not
enter an address manually when prompted by
the Where was this? message, this diagnostic
will be created. It can be resolved by selecting
the Where was this? associated with the
record and manually entering the missing
data. Once investigated, and the problem is
resolved, the system will auto clear the event.
Check your internet connection. If problem
persists, contact your carrier. Once
investigated, and the problem is resolved, the
system will auto clear the event

Review all unassigned logs when logging in or
logging out of the vehicle and ensure you have
claimed any logs that may be applicable to
yourself. If the unassigned logs are not yours,
you can ignore this diagnostic event.
Please note this event will automatically clear
itself as logs get claimed
The other ELD Unidentified is not supported.

The other ELD Unidentified is not supported.

Updated 11/17/2017

Data Diagnostics and Malfunction Events
Note: Data Diagnostic events cannot be cleared by the driver, these will auto clear once the issue is
resolved.
Malfunction Malfunction Event:
Code
P

Power data malfunction:
An ELD must monitor the data it receives from the engine
ECM or alternative sources, and data record history to
identify instances when it might not have complied with the
power requirements.

Engine synchronization compliance malfunction:
An ELD must set an engine synchronization compliance
malfunction, if connectivity to any of the required data
sources is lost for more than 30 minutes during a 24-hour
period aggregated across all driver pro les.

Timing compliance malfunction:
The ELD must periodically cross-check its time with an
external UTC source, and must record a timing compliance
malfunction when it can no longer meet the underlying timing
requirement of less than 10 minutes time deviation.

Positioning Compliance malfunction:
An ELD must monitor elapsed time during periods when the
ELD fails to acquire a valid position measurement within ve
miles of the CMVs movement. When such elapsed time
exceeds a cumulative 60 minutes over a 24-hour period, the
ELD must set and record a positioning compliance
malfunction.

Data recording compliance malfunction:
An ELD must monitor its storage capacity and integrity and
must detect a data recording compliance malfunction if it can
no longer record or retain required events, or retrieve
recorded logs that are not otherwise cataloged remotely by
the motor carrier.

Data transfer compliance malfunction:
After an ELD records a data transfer data diagnostic event,
the ELD must increase the frequency of the monitoring
function to check at least once every 24-hour period. If the
ELD stays in the unconfirmed data transfer mode following
the next three consecutive monitoring checks, the ELD must
detect a data transfer compliance malfunction.

What should I do next?
This may be caused by an intermittent or
disconnected connection to the vehicle ECM.
This is likely due to an install issue. Contact
your carrier to get the install inspected if
youre unable to check yourself. Once
investigated and the problem is found you
may clear this event.
This may be caused by an intermittent or
disconnected connection to the vehicle ECM.
This is likely due to an install issue. Contact
your carrier to get the install inspected if
youre unable to check yourself. Once
investigated and the problem is found you
may clear this event.
Check your mobile devices phone time.
Ensure it is set to acquire time
automatically. Once investigated and the
problem is found you may clear this event.

This can be caused by temporary or
permanent loss of GPS by the GO
device. Contact your carrier to get the
install inspected. If problem still persists,
replace the GO device. Once investigated
and the problem is found you may clear this
event.

Contact your carrier to get in touch with
Support as soon as possible. Once
investigated and the problem is found you
may clear this event.

Check your internet connection. If problem
persists, contact your carrier. Once
investigated and the problem is found you
may clear this event

Updated 11/17/2017