Skip to main content
ONE20 Help

Handling System Malfunctions

This article covers the types of system malfunctions that can happen in the ONE20 F-ELD app and what they mean.

If you are notified that your F-ELD is experiencing a system malfunction, do these things: 

1: Confirm the Malfunction is Active

  1. In the ONE20 F-ELD app, choose the More option. Menu options display.
  2. Choose the System Issues option. The System Issues screen displays. 
  3. In the System Issues screen, malfunctions can display in two different categories:
  • Active: If your malfunction displays in the Active list, continue to 2: Do the Required Administrative Work.  
  • Historical: If your malfunction displays in the Historical list, you don't have any malfunctions on your system that need addressing so you don't need to do anything else.

2: Do the Required Administrative Work

  • Note the malfunction of the ELD and provide written notice of the malfunction to your motor carrier within 24 hours; 

  • Reconstruct the record of duty status (RODS) for the current 24-hour period and the previous seven consecutive days, and record the records of duty status on graph-grid paper logs that comply with 49 CFR 395.8, unless you already have the records or retrieve them from the ELD; and 

  • Continue to manually prepare RODS in accordance with 49 CFR 395.8 until the ELD is serviced and back in compliance.

IMPORTANT NOTE: The recording of your hours of service on a paper log cannot continue for more than eight days after the malfunction; if you choose to record your hours of service on a paper log for more than eight days, you may be placed out of service.

3: Learn About the Malfunction and Fix It

This section shows you what the different system malfunctions mean and how to clear them. A system malfunction is cleared when it no longer displays in your System Issues "Active" list. You can view the System Issues list by choosing More|System Issues. When there are no active issues in your list, you can use the F-ELD to record your logs. 

POWER

Quick Description

If your truck adapter couldn't detect power from your truck when it needed to for a long period of time, this displays. 

Nitty-Gritty Details

The F-ELD records a power system malfunction if the power data diagnostic events that your system is experiencing indicates an aggregated in-motion driving time understatement of 30 minutes or more on your F-ELD over a 24-hour period.

How to fix it...

  • Confirm your adapter is plugged in
  • Confirm the cable housing is locked
  • Confirm you're using the correct diagnostic port
  • Confirm your adapter is fully plugged in
  • Test different components (cord, adapter, engine)
    • If it's a cord or adapter hardware issue, call ONE20
    • If it's an engine problem, see a mechanic
  • Confirm your adapter's light is solid green
    • If a green light is blinking quickly, wait for about one minute for the adapter to power up
    • If a green light is blinking slowly:
      • Re-confirm your truck is turned on
        • If your adapter is plugged in and the issue is still happening, re-test different components (cord, adapter, engine) to identify the issue
        • If it's a cord or adapter issue, call ONE20
        • If it's an engine problem, see a mechanic
  • Confirm your adapter has power
  • If these troubleshooting steps do not fix the problem, start using manual logs and email support@one20.com 

NOTE: This malfunction will reset after all issues are fixed and a 30 minute timer is reached.

ENGINE SYNCHRONIZATION

 

Quick Description

If your truck adapter couldn't get the information or data it needed from your truck for a long period of time, this displays.

Nitty-Gritty Details

The F-ELD records an engine synchronization system malfunction if connectivity to any of the required data sources is lost for more than 30 minutes during a 24-hour period.

Note: This malfunction will not be generated until after you connect your truck adapter to the F-ELD app. 

How to fix it...

  • Confirm your engine is turned on
  • Confirm your adapter is fully plugged in
  • Confirm the cable housing is locked
  • Confirm you're using the correct diagnostic port 
  • If plugged in and issue is still happening, test different components (cord, adapter, engine) to identify the issue
    • If it's a cord or adapter hardware issue, call ONE20
    • If it's an engine problem, see a mechanic
  • Confirm that your adapter has power
    • Test different components (cord, adapter, engine) to identify the issue
    • If it's a cord or adapter hardware issue, call ONE20
    • If it's an engine problem, see a mechanic
  • If these troubleshooting steps do not fix the problem, start using manual logs and email support@one20.com 

NOTE: This malfunction will reset after all issues are fixed and a 30 minute timer is reached.

TIMING

Quick Description

If the F-ELD can't sync to a time zone for a long period of time, this displays. 

Nitty-Gritty Details

The F-ELD records a timing system malfunction when it cannot meet the underlying compliance requirement. The ELD time must be synchronized to Coordinated Universal Time (UTC) and the absolute deviation from UTC must not exceed 10 minutes at any point in time.

Note: This malfunction will not be generated until after you connect your truck adapter to the F-ELD app. 

How to fix it...

  • Confirm your device has an internet connection
  • Confirm your device has a GPS signal (adapter will have a solid green light)
  • Confirm your phone's time settings are correct
  • Confirm your phone's time zone is correct 
  • Confirm your device is placed in a location where it can establish a good internet connection (ONE20 recommends that it's placed on the dash in front of the windshield with a clear line of sight to the sky)
  • If these troubleshooting steps do not fix the problem, start using manual logs and email support@one20.com 

GPS

Quick Description

When the F-ELD can't get an accurate location reading for your truck for a long period of time, this displays. 

Nitty-Gritty Details

The F-ELD records a GPS system malfunction when it cannot get a valid position measurement within five miles of your truck's movement. When this time goes above a cumulative 60 minutes over a 24-hour period, the F-ELD records a position compliance malfunction. 

Note: This malfunction will not be generated until after you connect your truck adapter to the F-ELD app. 

How to fix it...

  • Confirm your device has an internet connection
  • Confirm your device has a GPS signal (adapter will have a solid green light) 
  • Confirm your device is placed in a location where it can receive a good internet connection (ONE20 recommends that it's placed on the dash in front of the windshield with a clear line of sight to the sky)
  • If these troubleshooting steps do not fix the problem, start using manual logs and email support@one20.com 

NOTE: This malfunction will reset after all issues are fixed and a 60 minute timer is reached.

DATA RECORDING

Quick Description

If you ran of out of storage space on your truck adapter, this displays. 

Nitty-Gritty Details

The F-ELD records a data recording system malfunction when it can no longer retain required events or retrieve recorded logs due to a space limitation on your adapter. 

How to fix it...

  • Confirm that you have accepted or denied all unidentified activity in your Unidentified Profile 
  • If you have accepted or denied all unidentified activities under your Unidentified Profile and the malfunction is still occurring, start using manual logs and email support@one20.com

NOTE: This malfunction will reset after all issues are fixed and a 30 minute timer is reached.

DATA TRANSFER

Quick Description

If the F-ELD isn't sending the information it needs to in the required timeline, this displays. 

Nitty-Gritty Details

The F-ELD monitors that the data transfer mechanisms that are needed for FMCSA compliance are functioning properly. Additionally, after the F-ELD records a data transfer diagnostic event, it must increase the frequency of the monitoring to check at least once every 24-hour period. If the F-ELD stays in the unconfirmed data transfer mode for the next three consecutive monitoring checks, the ELD records a data transfer compliance malfunction. 

How to fix it...

  • Manually certify your logs at the end of every day
  • If you are manually certifying your logs at the end of every day and the malfunction is still occurring, start using manual logs and email support@one20.com