User manual for "TruckishELD"

05/21/2019

Instruction for drivers for ELD functionality in the Mobile App

Copyright
 Truckish 2019. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or by any means or stored in any
retrieval system of any nature without prior written permission except as expressly permitted by any
written contract signed by Truckish with the recipient.
The contents of this documentation are the confidential information of Truckish and are subject to the
provisions of Truckish Standard Customer Agreement or Non-Disclosure Agreement (as relevant) or any
similar agreement signed by Truckish and entered into with the recipient. The contents of this
documentation (or any part or it) must not be used or disclosed to any third party by the recipient except
as expressly permitted by the relevant agreement. If you (or your company) have not signed an
agreement with Truckish you must not use this documentation, must treat it as strictly confidential and
must promptly return it to Truckish.

V1.0
1

05/21/2019

Logging in:
When a user clicks on the app icon on their mobile screen, a splash screen opens while app is
loading. This screen then directs to the Login Screen.


Splash Screen



Login Screen
The user is able to login with his/her email address and password.
In case the driver is signing up for the first time he/she can contact the fleet manager for the
login credentials.

V1.0
2

05/21/2019

Select Duty Cycle
Once the driver is logged in, the next step is to select the relevant duty cycle for his/her driving duties.
As can be seen below:
- Select the cargo-type i.e. property or oil
- Cycle reset time period is auto-populated based on the cargo-type (34-hour or 24-hour)
- Select Short-Haul Exception, if applicable
- Then select the Duty Cycle
- And user is all set to start their driving assignment

V1.0
3

05/21/2019

Select Duty Status
After selecting the duty cycle, dashboard reflected the available cycle time for the driver. The duty status
settings can be accessed in the dashboard screen through the hamburger menu button on the left top
corner. As can be seen below in the dashboard view:
 To begin with, the current duty status button will show the driver as Off-Duty
 Driver can change the duty status by clicking on the duty status button and making a selected
from the list of available duty statuses on the subsequent screen. Driving duty status is
automatically turned on or off depending on whether the vehicle is moving or not.
 ELD device connectivity status is monitored and displayed on the app in the ELD status button.

V1.0
4

05/21/2019

Driver Vehicle Inspection Report (DVIR)


A driver can create a new DVIR by selecting Logs module from the left hamburger button menu,
select the date for which DVIR needs to be created and click on the DVIR tab.




Select the truck or the trailer from the list and create a new DVIR entry.
The defect/issue can be selected from the list of available defects/issues, and driver also has the
option to create a custom defect/issue if needed. Driver also has the option to attach images
wherever applicable.

V1.0
5

05/21/2019

Duty Log Edit
Duty logs are auto-generated based on duty status changes made by the driver, in addition to driving logs
from the ELD device. Duty Logs can be edited and submitted by the driver. Dispatchers/Fleet Managers
have the option to review driver logs and suggest edits. Such edits are sent to the driver for his/her
signature before being formally added to the duty log.

V1.0
6

05/21/2019

DOT Inspection




Past 7 days of driver duty logs submission to DOT can be easily made by browsing to DOT
Inspection Mode from the hamburger button menu on top left, and selecting email logs. Drivers
also have the option to send their logs to additional recipients by entering their email addresses.
Logs can be also made available for review by the DOT Inspector by clicking on the View Logs
button as shown below.

V1.0
7

05/21/2019

Data Diagnostic and Malfunction Events
Diagnostic
Code

Data Diagnostic Event

What should I do next?

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.

This may be caused by an intermittent or
disconnected connection to the vehicles
ECM. Once investigated, and the problem
is resolved, the system will auto clear the
event.

2

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.

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 Truckish
Customer Support if the problem persists.
Once investigated, and the problem is
resolved, the system will auto clear the
event.

3

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.

This can be caused by the creation of a
manual log by the driver when there is a
temporary loss of GPS by the Geotab 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.

4

Data transfer data diagnostic:
An ELD must implement in-service
monitoring functions to verify that the

Read the full extracted text