Malfunction Reporting Instruction Sheet - Canada


The following document is prepared in accordance with SOR-2005-313 Section 78 (2 - 7):


If this ELD device is found to be in a Malfunction state as indicated in the chart attached,
then the following MUST be complied to by the driver AND the motor carrier of the CMV.

If an ELD malfunctions, a driver must:

  1. Notify the motor carrier that is operating the commercial vehicle as soon as the vehicle is parked.

  2. Immediately switch to using a paper logbook until you return to the home terminal from your current trip.

  3. The driver shall record, in the record of duty status on the day on which he or she noticed the malfunction or data diagnostic code, the following information:

    1. The malfunction or data diagnostic code as set out in Table 4 of Schedule 2 of the Technical Standard;

    2. The date and time when the malfunction or data diagnostic code was noticed; and

    3. The time when notification of the malfunction or data diagnostic code was transmitted to the motor carrier.

  4. Record the code referred to in the point above in each record of duty status following the day on which the code was noticed, until the ELD is repaired or replaced.

If an ELD malfunctions, a motor carrier must:

  1. Within 14 days after the day on which it was notified of an ELD malfunction or data diagnostic code by the driver or otherwise became aware of it, or at the latest, upon return of the driver to the home terminal from a planned trip if that return exceeds the 14-day period, repair or replace the ELD.

  2. The motor carrier shall maintain a register of ELD malfunction or data diagnostic codes for ELDs installed or used in commercial vehicles that it operates for which a malfunction was noticed, and that register shall contain the following information:

    1. The name of the driver who noticed the malfunction or data diagnostic code;

    2. The name of each driver that used the commercial vehicle following the discovery of the malfunction or data diagnostic code until the ELD was repaired or replaced;

    3. The make, model and serial number of the ELD;

    4. The license plate of the commercial vehicle in which the ELD is installed or used, or the Vehicle Identification Number;

    5. The date when the malfunction or data diagnostic code was noticed and the location of the commercial vehicle on that date, as well as the date when the motor carrier was notified or otherwise became aware of the code;

    6. The date the ELD was replaced or repaired; and

    7. A concise description of the actions taken by the motor carrier to repair or replace the ELD.


Condition

State

Definition

Driver recourse



Diagnostic


Diagnostic




Malfunction 

No Driver action is required but recommended steps to resolve the issue (if any) are outlined in the chart below


Follow required malfunction reporting steps as stated above as well as any additional steps outlined in the following chart.

MISSING_DATA

 

Required data may be missing from the last ELD event that was recorded.

This should resolve itself after a short while. If it does not, then please contact your administrator.

UNIDENTIFIED_DRIVER

* Unidentified driving time occurs when the vehicle is moving without a Driver logged in.

 

When the ELD device has accumulated >30min of unidentified driving time in the past 7 days.

This state is cleared when <= 15min unidentified driving time remains.

Unidentified Driving Time can be claimed and added to your Driver Log via the Review Hours screen when logging in OR selecting Driver Logs > Unidentified Driving  from the Main Menu.

POWER

 

The ELD has failed to start up within 1 minute of your engine starting.

Make sure the ELD is powered on and at the login screen before turning your vehicle on

 

It’s possible that you’ve missed 30 minutes of driving time due to this.

Please check or have your administrator check to make sure your logs are correct.

ENGINE_SYNC 

 

We have not detected data from the ECM in the past 5 seconds.

Make sure your device USB cable is securely fastened to the ELD

 

When an accumulated 30 minutes of time has elapsed between the creation and receipt of these engine events, we raise this as a Malfunction state.

Please advise your administrator/installer so further troubleshooting can be performed

DATA_TRANSFER

 

The last data transfer test that was performed has failed.


 

We’ve started testing more frequently and still cannot transfer data.

You may be unable to send your onboard documents to an officer should they request them. Please contact your administrator so they can perform additional troubleshooting steps.

TIMING

 

The time on your ELD may be incorrect.

This should resolve itself after a short while. If it does not, then please contact your administrator. If this occurs we recommend keeping a paper log following the outline at the start of this document.

POSITIONING

 

You have been moving but we do not have a lock on your GPS location.

This should resolve itself after a short while. If it does not, then please contact your administrator. If this occurs we recommend keeping a paper log following the outline at the start of this document.

DATA_RECORDING

 

There is an issue saving data on the ELD.

Please contact your administrator.

If this occurs we recommend keeping a paper log following the outline at the start of this document.

Malfunction Reporting Instruction Sheet - USA


The following document is prepared in accordance with 49 CFR §395.22 (h) (3) which states:


(h) In-vehicle information. A motor carrier must ensure that its drivers possess onboard a commercial motor vehicle an ELD information packet containing the following items:

(3) An instruction sheet for the driver describing ELD malfunction reporting requirements and recordkeeping procedures during ELD malfunctions


If this ELD device is found to be in a Malfunction state as indicated in the chart below,
then the following MUST be complied to by the driver AND the motor carrier of the CMV.


If an ELD malfunctions, a driver must:

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

  2. Reconstruct the record of duty status (RODS) for the current 24-hour period and the previous 7 consecutive days, and record the RODS on graph-grid paper logs, or electronic logging software, that comply with 49 CFR 395.8, unless the driver already has the records or retrieves them from the ELD; and

  3. Continue to manually prepare RODS in accordance with 49 CFR 395.8 until the ELD is serviced and back in compliance. The recording of the driver's hours of service on a paper log, or electronic logging software, cannot continue for more than 8 days after the malfunction; a driver that continues to record his or her hours of service on a paper log, or electronic logging software, beyond 8 days risk being placed out of service.

If an ELD malfunctions, a motor carrier must:

  1. Correct, repair, replace, or service the malfunctioning ELD within eight days of discovering the condition or a driver's notification to the motor carrier, whichever occurs first; and

  2. Require the driver to maintain a paper record of duty status (RODS) until the ELD is back in service.


Note about when to use paper logs:

“A driver should only use paper logs, or electronic logging software, or other electronic means to record their HOS if the ELD malfunction hinders the accurate recording of the driver's hours-of-service data (i.e., 10/11, 14/15, 60/70 hours; or 30 minute).”


Condition

State

Definition

Driver recourse






 

Diagnostic




Malfunction 

No Driver action is required but recommended steps to resolve the issue (if any) are outlined in the chart below


Follow required malfunction reporting steps as stated above as well as any additional steps outlined in the following chart.

MISSING_DATA

 

Required data may be missing from the last ELD event that was recorded.

This should resolve itself after a short while. If it does not, then please contact your administrator.

UNIDENTIFIED_DRIVER

* Unidentified driving time occurs when the vehicle is moving without a Driver logged in.

 

When the ELD device has accumulated >30min of unidentified driving time in the past 7 days.

This state is cleared when <= 15min unidentified driving time remains.

Unidentified Driving Time can be claimed and added to your Driver Log via the Review Hours screen when logging in OR selecting Driver Logs > Unidentified Driving  from the Main Menu.

POWER

 

The ELD has failed to start up within 1 minute of your engine starting.

Make sure the ELD is powered on and at the login screen before turning your vehicle on

 

It’s possible that you’ve missed 30 minutes of driving time due to this.

Please check or have your administrator check to make sure your logs are correct.

ENGINE_SYNC 

 

We have not detected data from the ECM in the past 5 seconds.

Make sure your device USB cable is securely fastened to the ELD

 

When an accumulated 30 minutes of time has elapsed between the creation and receipt of these engine events, we raise this as a Malfunction state.

Please advise your administrator/installer so further troubleshooting can be performed

DATA_TRANSFER

 

The last data transfer test that was performed has failed.


 

We’ve started testing more frequently and still cannot transfer data.

You may be unable to send your onboard documents to an officer should they request them. Please contact your administrator so they can perform additional troubleshooting steps.

TIMING

 

The time on your ELD may be incorrect.

This should resolve itself after a short while. If it does not, then please contact your administrator. If this occurs we recommend keeping a paper log following the outline at the start of this document.

POSITIONING

 

You have been moving but we do not have a lock on your GPS location.

This should resolve itself after a short while. If it does not, then please contact your administrator. If this occurs we recommend keeping a paper log following the outline at the start of this document.

DATA_RECORDING

 

There is an issue saving data on the ELD.

Please contact your administrator.

If this occurs we recommend keeping a paper log following the outline at the start of this document.