Skip to main content
ONE20 Help

Handling Data Diagnostic Events

This article covers the types of data diagnostic events and what they mean.

What the Data Diagnostic Events Mean and How to Fix Them

When a data diagnostic event displays in the ONE20 F-ELD app, it's important to know what the event means and how to fix it. 

DATA DIAGNOSTIC EVENT TYPE WHAT DOES IT MEAN? HOW TO FIX IT
Data Diagnostic Power Event

The F-ELD needs to monitor the data it receives from the engine ECM or other sources, its onboard sensors, and data record history. It needs to do this to identify instances when it may not have complied with the power requirements dictated by the FMCSA. If it can't connect to your engine's ECM or other sources, onboard sensors, or data record history, it records a data diagnostic power event for whoever is connected to the adapter or in the unidentified profile if no one is connected to the adapter. 

  • Confirm your adapter is plugged in
  • Test the 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 the green light is blinking quickly, wait for about one minute for adapter to power up
    • If the green light is blinking slowly:
      • Re-confirm the truck is turned on
        • If the adapter is plugged in and the issue is still happening, re-test the 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 that all of your events have the needed information entered (in your Activities list or in the Dashboard)
Data Diagnostic Engine Synchronization Event

The F-ELD needs to connect to the engine ECM to monitor its connectivity and its ability to retrieve the vehicle parameters. Additionally, it needs to record an engine synchronization data diagnostic event when it can no longer get updated information that it needs within five seconds of when the information is needed. 

  • Confirm your truck's engine is turned on
  • Confirm your adapter is fully plugged in
  • Confirm your adapter's cable housing is locked
  • Confirm you're using the correct diagnostic port
  • If your adapter is correctly plugged in and the issue is still happening, test the 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 your adapter has power
    • Test the 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
Data Diagnostic Missing Required Data Elements Event

The F-ELD must monitor and confirm that you have entered all of the required information that is needed for FMCSA compliance. If there is some required information missing, the F-ELD records a missing data elements data diagnostic event. 

  • Confirm that your HOS settings, profile, and truck profile information is fully filled out and complete
  • Confirm data is being received from your truck's engine (you can confirm this by checking that information is being populated in your logs)
    • If not, confirm your adapter is plugged in correctly
      • If the adapter is plugged in and the issue is still happening, test the 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 the F-ELD app has access to your location in your device's settings
Data Diagnostic Data Transfer Event

The F-ELD has an in-service monitoring function that confirms that the data transfer mechanisms that are needed for FMCSA compliance are functioning how they need to. It needs to do this at least once every seven days. If the monitoring mechanism fails to confirm the data transfer mechanisms are functioning like they need to, the F-ELD records a data transfer data diagnostic event. 

  • Confirm that you're regularly sending your logs (manually)
Data Diagnostic Unidentified Driving Records Event

The F-ELD records unidentified activity for each adapter. Unidentified activity is recorded when the F-ELD detects motion but no driver is connected to it. When an unidentified activity goes for longer than 30 minutes in a 24-hour period, a data diagnostic unidentified driving records event occurs. This event automatically clears when the total unidentified activity in the current and previous seven days is less than or equal to 15 minutes. 

  • Confirm that all of your unidentified activities are either accepted or rejected