Motive ELD User Manual

This manual provides comprehensive instructions for using the Motive ELD system, including the Vehicle Gateway and the Motive Driver App.

Introduction

The Motive ELD is a mobile-based ELD system comprising the Motive Vehicle Gateway, the Motive Driver App, and the Motive Fleet Dashboard. It is designed to support ELD functionality in compliance with applicable regulations.

Important: As per FMCSA rules, this guide must be readily available in the vehicle at all times when using the Motive ELD.

Vehicle Gateway Compliance

This device contains license-exempt transmitter(s)/receiver(s) that comply with Part 15 of the FCC Rules and Industry Canada license-exempt RSS standards. Operation is subject to 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 complies with FCC radiofrequency radiation exposure limits for an uncontrolled environment and meets the RSS 102 radiofrequency exposure compliance requirements. Installation and operation should maintain a minimum distance of 20 cm between the radiator and the user's body. This transmitter must not be co-located or operated in conjunction with any other antenna or transmitter. Unauthorized changes or modifications by Motive could void the user's authority to operate this equipment.

Table of Contents

Downloading the Driver App

Ensure you have installed a Vehicle Gateway in your vehicle before proceeding. Refer to the Vehicle Gateway Manual for details.

Download the Motive Driver app from the Google Play Store (for Android phones/tablets) or the App Store (for iPhones and iPads).

How to Log In to the Driver App

  1. Open the driver app and select 'Log In'. If you do not have a Motive driver account, select 'Sign Up' or contact your fleet manager.
  2. Enter your email/username and password, then tap 'Submit'.

Connecting Your Mobile Device to the Vehicle Gateway

Using the Motive Vehicle Gateway requires connecting your driver app to the Vehicle Gateway to automatically record driving time on your ELD log.

  1. On the logs page, tap 'NO VEHICLE' in the upper right corner.
  2. A search bar and a list of all company vehicles will appear. Select the vehicle you wish to connect to. Ensure your vehicle's engine is on and Bluetooth is enabled on your mobile device before connecting to the Vehicle Gateway.
  3. Your mobile device will attempt to connect automatically to the Vehicle Gateway via Bluetooth.
  4. A green ELD icon will appear on the upper right of the main logs page, indicating a successful connection to the Vehicle Gateway.

Recording Driving Time on Your ELD Log

  1. When your vehicle moves at 5 mph or more, Motive considers the vehicle 'IN MOTION' and automatically updates your current duty status to 'DRIVING'.
  2. When your vehicle stops (0 mph), it is considered 'STATIONARY'.
  3. You can change the duty status of a stopped vehicle by tapping 'DRIVING' and selecting an alternative status: 'OUT OF SERVICE', 'SLEEPING', or 'ON DUTY'.
  4. If the vehicle remains stationary for five minutes, a prompt will appear asking if you wish to change your duty status or remain in it. You have one minute to make a selection; otherwise, your status will automatically change from 'STATIONARY' to 'ON DUTY'.

Allowing an Officer to Inspect Your ELD Log

Navigate to the main app menu by tapping the menu icon and select 'DOT Inspection Mode'.

To allow an officer to inspect your logs directly from your mobile device, select 'Start Inspection'. Press and hold the 'Start Inspection' button to set a 4-digit passcode. This restricts access to other parts of the app until the code is re-entered.

You can send your ELD output file to the DOT via email or web service by selecting 'Send Output File'. You will be prompted to enter your official comments.

To send a copy of your logs via email or fax to an official, select 'Send Logs'. You will be prompted to enter the recipient's fax number or email address.

Understanding the LEDs

Troubleshooting

What if my driver app doesn't pair with the Vehicle Gateway?

Navigate to the Logs page and select 'Current Vehicle' in the upper right corner. If a vehicle is currently selected, tap 'Exit Vehicle', then select the vehicle you wish to connect to again.

Option 1: Once the 'Connect Bluetooth Accessory' prompt appears, wait 30 seconds. If it doesn't connect, tap 'OK' and proceed.

Option 2: Turn your phone or tablet's Bluetooth off and then back on. Once Bluetooth is re-enabled, select the vehicle you want to connect to. When the 'Connecting to Vehicle' message appears, wait 30 seconds.

Option 3: Unplug the Vehicle Gateway from your vehicle and wait for the light to turn off. Restart your phone or tablet before reconnecting the Vehicle Gateway. Once plugged in, the Vehicle Gateway LEDs will flash momentarily before turning red. After about a minute, the left LED will turn green, indicating a successful GPS connection. If the right LED flashes red, try connecting your iOS/Android device to your Vehicle Gateway again. Once connected, the right LED will turn green. Refer to page 8 for a complete guide to LED behaviors.

Understanding ELD Malfunctions

If the Vehicle Gateway is not functioning correctly, it indicates an ELD malfunction. Follow the procedures outlined in § 395.34.

What should a driver do if the Vehicle Gateway malfunctions?

Contact Motive support immediately at 855-434-3564 or support@gomotive.com to troubleshoot. Document the specific problem and report it to your fleet in writing within 24 hours. Maintain a paper log for the day and until the Vehicle Gateway is repaired or replaced. For inspections, show the past 7 days' logs from the Motive Driver App.

What should a carrier do if the Vehicle Gateway malfunctions?

If a carrier receives or discovers information about a Vehicle Gateway issue, they must take steps to correct the malfunction within eight days of discovery or notification by the driver, whichever comes first. Contact Motive support for prompt resolution. If an extension is needed, notify the FMCSA Division Administrator for the carrier's principal place of business within five days of the driver's notification, per § 395.34.

Visual Indicators of ELD Faults/Data Diagnostics (Vehicle Stationary)

Identifying and Resolving ELD Faults/Data Diagnostics

Step 1: Tap 'Current Vehicle' for more details.

Step 2: Tap 'Diagnostics' to learn more about any active faults/data diagnostics.

Step 3: On the diagnostic screen, scroll down and tap on a fault or diagnostic event. Existing events will be shown in red text.

Step 4: A message will appear with details on how to resolve the issue.

ELD Diagnostics

Power Compliance Fault (Code P)

Problem: The Vehicle Gateway is disconnected, and there is over 30 minutes of driving time within a 24-hour period across all driver profiles, including unidentified drivers.

Solution: Ensure you are connected to the vehicle in the driver app whenever the vehicle is in motion. For Vehicle Gateway issues, contact Motive technical support.

Engine Synchronization Event Diagnostic (Code 2)

Problem: The ELD loses ECM connectivity with required data sources and cannot acquire updated values for required ELD parameters within five seconds of need. Connectivity must be maintained between the driver app and the Vehicle Gateway while the vehicle is running.

Solution: Ensure your driver app remains connected to the vehicle while the engine is running. For Vehicle Gateway issues, contact Motive technical support.

Engine Synchronization Fault (Code E)

Problem: The Vehicle Gateway loses connection for over 30 accumulated minutes of missing data elements: GPS, VIN, date/time, engine hours. Engine synchronization faults will clear themselves after 24 hours from the last recorded fault event.

Solution: Ensure your driver app remains connected to the vehicle while the engine is running. For Vehicle Gateway issues, contact Motive technical support for assistance.

Position Compliance Fault (Code L)

Problem: The Vehicle Gateway cannot obtain a valid GPS position within five miles of the last valid position for more than 60 minutes of driving within a 24-hour period.

Solution: Ensure the left LED of the Vehicle Gateway is green for GPS connection. Move the Vehicle Gateway near a window with a clear view of the sky. If the LED remains red, try restarting the Vehicle Gateway. Contact Motive support for further assistance and manually log locations in the meantime. Position compliance faults will clear themselves after 24 hours from the last recorded fault event.

Missing Required Data Elements Diagnostic Event (Code 3)

Problem: Missing data elements (e.g., GPS location) in the ELD event log.

Solution: Contact Motive support for assistance.

Unidentified Driving Records Diagnostic Event (Code 5)

Problem: Over 30 minutes of unidentified driving time for the vehicle in the last 24 hours.

Solution: Drivers can claim unidentified trips from the Motive Driver App if they belong to them. Fleet managers can also assign unidentified trips to drivers in their logs. Unidentified Driving Records Diagnostic Events will be cleared when accumulated unidentified driving time is less than 15 minutes for the current day plus the previous 7 or 14 days (US or Canada).

Synchronization Compliance Fault (Code T)

Problem: The time on the Vehicle Gateway varies by more than 10 minutes from UTC time.

Solution: The Vehicle Gateway will automatically resynchronize its local clock with GPS time once valid. Ensure the device is placed with a clear view of the sky. Contact Motive support for assistance.

Data Log Compliance Fault (Code R)

Problem: The Vehicle Gateway can no longer record new event data due to exceeded data storage.

Solution: Ensure an active internet connection before using Bluetooth to connect the Motive app with the Vehicle Gateway. Drivers must remain actively in the driver app for the Vehicle Gateway to transfer data to the Motive server. Contact Motive support for assistance.

Data Transfer Compliance Fault (Code S) / Data Transfer Event Diagnostic (Code 4)

Problem: The internal data transfer test fails, and the output file data cannot be sent.

Solution: Contact Motive support for assistance.

What to do in case of an active ELD fault that prevents a driver from accurately recording or presenting their duty status history (RODS) with the ELD?

Drivers

Identify the active ELD fault/Data diagnostic event and notify the carrier in writing within 24 hours. Reconstruct RODS for the current 24-hour period and report RODS on paper logbooks. Use the Motive ELD to retrieve the previous seven days' logs. If unavailable, drivers must reconstruct RODS on paper logs for the prior 7-day period.

Carriers

The carrier must take measures to fix active faults. In the US, carriers must correct the fault within eight days of discovery or driver notification, whichever comes first. If an extension is needed, the carrier must notify the FMCSA Division Administrator within five days of driver notification, per §395.34(2). In Canada, carriers must repair or replace an ELD within 14 days of notification of a fault. If a driver's planned trip prevents return to the terminal within this 14-day period, the ELD must be repaired or replaced upon return.

Need More Help?

If you cannot resolve your issue immediately, contact the Motive support team. A replacement device will be issued if the current one is found to be faulty.

About Motive

Motive creates technology to enhance the safety, productivity, and profitability of businesses driving the physical economy. The Motive Automated Operations platform combines IoT hardware with AI-driven applications to automate vehicle and equipment tracking, driver safety, compliance, maintenance, expense management, and more. Motive serves over 120,000 businesses. Visit gomotive.com for more information.

PDF preview unavailable. Download the PDF instead.

ELD-Driver-App-User-Manual-Spanish Adobe PDF Library 16.0.7 Adobe InDesign 17.4 (Macintosh)

Related Documents

Preview Motive ELD Inspection Reference Card: US & Canada Compliance Guide
Official reference card for Motive ELD users in the US and Canada, detailing DOT inspection procedures, compliance regulations, and how to share logs with officers.
Preview Motive & FedEx: ELD/VEDR Service Provider FAQs
Frequently asked questions for FedEx service providers regarding Motive's integrated Electronic Logging Device (ELD) and Video Event Data Recorder (VEDR) platform, including hardware, usage, and device requirements.
Preview Motive ELD & VEDR for FedEx Service Providers: FAQs and Guide
Comprehensive frequently asked questions and guide for FedEx service providers on using Motive's integrated ELD and VEDR platform, including hardware, software, and data requirements.
Preview Motive Road-Facing AI Dashcam: Advanced Fleet Safety and Video Specifications
Explore the Motive Road-Facing AI Dashcam, featuring industry-leading AI performance, HD video, comprehensive risk detection, and robust hardware for enhanced fleet safety and operational efficiency.
Preview Motive AI Dashcam: Advanced Driver Safety and Fleet Management
Discover the Motive AI Dashcam, a leading solution for preventing accidents, reducing risk, and enhancing fleet operations with advanced AI, high-quality video, and comprehensive driver coaching. Learn about its key features, specifications, and integration with the Motive platform.
Preview Motive Vehicle Gateway: Spec Sheet
Detailed specifications for the Motive Vehicle Gateway, a device that provides cellular connectivity for real-time vehicle and driver data synchronization, GPS tracking, maintenance monitoring, and compliance records.
Preview Motive Vehicle Gateway Installation Manual
A comprehensive guide for installing and activating the Motive Vehicle Gateway, including instructions for pickup trucks, vans, and large trucks, with details on basic and covert installations, cable options, LED indicators, and troubleshooting.
Preview Motive IDREAD-01 RFID Reader User Manual
Comprehensive user manual for the Motive IDREAD-01 RFID Reader Module (also known as DR102P), detailing its technical specifications, interface connections, operational status indicators, safety precautions, and regulatory compliance information for vehicle gateway systems.