ELD Compliant: How to Be Sure Your ELD is Really Compliant

As full enforcement of the ELD Mandate is around the corner, the FMCSA has found malfunctioning and non-compliant devices, which means registered, self-certified devices could be removed from the FMCSA-approved list if the issues aren’t resolved. How can you be sure your device is really compliant?

The FMCSA recommends checking your device for these frequently reported issues prior to April 1:

Erroneous Fields in ELD Output File

The ELD rule lists the fields required in an ELD output file and the acceptable ranges for these values. Files missing required fields, or containing fields with invalid values, will not be accepted by the Web Service or eRODS, and therefore not viewable to the safety official. Some issues the FMCSA is noticing with invalid ELD output files include:

  • Invalid field lengths (e.g., CMV VIN, Shipping Document Number, Trailer Number)
  • Field values outside valid range (e.g., Elapsed Engine Hours, Accumulated Vehicle Miles)
  • Missing required fields (e.g., Event Sequence ID Number, CMV Order Number, Last Name, Carrier Name)
  • Incorrect line and file data check values
  • Invalid characters, dates, times, or numbers

All of the above issues are checked when an ELD output file is run through the FMCSA File Validator.

File Contains Invalid Delimiters

The ELD rule specifies that fields must be separated by commas and that lines must be separated by carriage returns (<CR>). If your ELD output file has a value that has a comma or <CR> in it, the rule requires that these be replaced with a semi-colon.

ELD Not Pre-Configured With the Web Service End Points or FMCSA Email Address

For telematics, the ELD must be able to transfer a file to the Web Service—this includes both the web services and email transfer methods, and it is required that all devices be pre-configured with this information. An ELD should never send an email directly to a safety official, and a driver or motor carrier should never have to request the email address or end points from FMCSA or a safety official.

ELD Support System Not Offering a Complete Set of the Data Transfer Option

While motor carriers are not required to use an ELD support system, any system they use must support data transfer through either the telematics (both web services and email) or local transfer (both USB and Bluetooth) options.

ELD Not Able to Send Files with 30+ Days of RODS

The ELD rule requires that ELDs have the ability to send records for the current 24-hour period and the previous consecutive 7 days for review during a roadside inspection. They must also produce ELD records via a data file or a series of data files for a subset of its drivers, vehicles, and the 6-month record retention period, to be specified by the safety official —this includes files with 30 days’ worth of RODS.

Event Times Provided Incorrectly

While date and time are recorded in UTC, the ELD output file must be provided in the time zone of the driver’s home terminal, otherwise this will result in the incorrect time displaying for the safety official. You can test this by viewing the safety official view of your ELD output files that have successfully run through the File Validator, or for test files successfully submitted to the Web Services test environment.

While these regulations may seem overwhelming, have no fear. FleetUp is here to help. As a premier provider of ELDs, FleetUp is committed to ensuring that our devices are fully FMCSA compliant and offer a variety of resources to provide guidance on how to properly and effectively install and utilize your device.

Get the latest insights delivered to your inbox

Stay up to date on industry updates and FleetUp events.