Electronic Logging Device Test Procedure Corrections – Part 1 of 3

From: Transport Canada

The corrections or updated instructions below correct minor typos or errors in interpretation which may have let to incorrect test results.

Sort the columns by Page(s) to list the corrections by their location in the Electronic Logging Device (ELD) Test Procedures, or by Date posted to list the corrections by the date they were posted.

Test Procedure No.

Page(s)

Date the correction was posted

Original text

Corrections or updated instructions

4.2
Test step 2
Test 1, 2 and 3

Pages 21 and 22

2021-08-18

Precondition(s):

  • CMV’s engine has an ECM

Test 1, 2 and 3 (mandatory): ELD can establish a link with the engine ECM and receive information through each serial (SAE J1587/J1708), CAN (SAE J1939) and (SAE J1979/OBD-II) engines communication protocol.

Description of Test Step(s):

Test 3 (ECM communication protocol – SAE J1979/OBD-II):

  1. Power on the CMV’s engine
  2. Wait until the ELD is powered on and fully functional
  3. Verify a link was established between the ELD and the engine’s ECM through the communication protocol
  4. Perform Test Procedure 4.3.1.1-1 to verify the ELD automatically receives the engine power status
  5. Perform Test Procedure 4.3.1.2-1 to verify the ELD automatically receives the vehicle motion status
  6. If information for total distance driven can be captured from the engine ECM, perform Test Procedure 4.3.1.3-1 to verify the ELD automatically receives the total distance driven value.  If not, perform Test Procedure 4.2-4
  7. If information for engine hours cannot be captured from the engine ECM, perform Test Procedure 4.2-4

Expected Test Step Outcome:

Test 2 (SAE J1939):

For each communication protocol (250 Kbps and 500 Kbps baud rate), user performed the test procedures specified in previous Test 1. ELD successfully received information for the engine’s power status, vehicle’s motion status, total distance driven value, and engine hours’ value.

Precondition(s):

  • CMV’s engine has an ECM
  • Test 1, 2 and 3 (mandatory): ELD can establish a link with the engine ECM and receive information through each serial (SAE J1587/J1708), CAN (SAE J1939) and (SAE J1979/OBD-II) engine s communication protocol supported by the ELD.

Description of Test Step(s):

Test 3 (ECM communication protocol – SAE J1979/OBD-II):

  1. Power on the CMV’s engine
  2. Wait until the ELD is powered on and fully functional
  3. Verify a link was established between the ELD and the engine’s ECM through the communication protocol
  4. Perform Test Procedure 4.3.1.1-1 to verify the ELD automatically receives the engine power status
  5. Perform Test Procedure 4.3.1.2-1 to verify the ELD automatically receives the vehicle motion status
  6. If information for total distance driven can be captured from the engine ECM, perform Test Procedure 4.3.1.3-1 to verify the ELD automatically receives the total distance driven value.  If not, perform Test Procedure 4.2-4
  7. If information for engine hours can be captured from the engine ECM, perform Test Procedure 4.3.1.4-1 to verify the ELD automatically receives the engine hours. If not information for engine hours cannot be captured from the engine ECM, perform Test Procedure 4.2-4

Expected Test Step Outcome:

For each communication protocol supported by the ELD a test was performed

Test 2 (SAE J1939):

For each communication protocol supported by the ELD (250 Kbps and/or 500 Kbps baud rate), user performed the test procedures specified in previous Test 1. ELD successfully received information for the engine’s power status, vehicle’s motion status, total distance driven value, and engine hours’ value.

Corrections: Precondition, test 3, step g), expected test step outcome for test 2 changed. Note added in expected test step outcome.

4.3.1.2.
Test step 1
Test 1

Page 27

2021-08-18

Description of Test Step(s):

Test 1:

  1. Power on the CMV’s engine
  2. Authenticate into the ELD using a driver user account
  3. Keep the engine idling for five minutes
  4. Verify the ELD is automatically set to a “stopped” state and allows for driver input when the engine is idling
  5. Put the CMV in motion and maintain a vehicle speed lower than the set speed threshold for 1 minute
  6. Verify the ELD remains in a “stopped” state and allows for driver input
  7. Accelerate to a speed greater than the set speed threshold
  8. Once the vehicle speed exceeds the set speed threshold, verify the ELD is automatically set to the “in motion” state.
  9. Maintain a speed greater than the set speed threshold for 1 minute
  10. Verify the ELD does not allow any driver input when the ELD is set to the “in motion” state.
  11. Bring the CMV back to a stop (CMV is stationery and vehicle speed stays at 0 km/h for 3 consecutive seconds)
  12. Verify the ELD is automatically set back to a “stopped” state and allows for driver input
  13. Power off the CMV’s engine
  14. Logout

Expected Test Step Outcome:

Test 1:

User powered on the CMV’s engine and authenticated into the ELD using a driver user account. User kept the engine idling for 5 minutes and the ELD was successfully set to a “stopped” state and allowed for driver input.

User put the CMV in motion and maintain a vehicle speed lower than the set speed threshold for 1 minute. The ELD remained in a “stopped” state and, allowed for driver input.

User accelerated to a vehicle speed greater than the set speed threshold and maintained that speed for 1 minute.  Once the vehicle speed exceeded the set speed threshold, the ELD successfully set and maintained the “in motion” state and did not allow any driver input.

User brought back the CMV to a stop.  After the CMV remained stationary for 3 consecutive seconds, the ELD was successfully set to a “stopped” state and allowed for driver input.  User logged out.

Description of Test Step(s):

Test 1:

  1. Power on the CMV’s engine
  2. Authenticate into the ELD using a driver user account
  3. Keep the engine idling for five minutes
  4. Verify the ELD is automatically set to a “stopped” state and allows for driver input when the engine is idling
  5. Put the CMV in motion and maintain a vehicle speed lower than the set speed threshold for 1 minute
  6. Verify the ELD remains in a “stopped” state and does not allows for driver input
  7. Accelerate to a speed greater than the set speed threshold
  8. Once the vehicle speed exceeds the set speed threshold, verify the ELD is automatically set to the “in motion” state. The “in motion” state is demonstrated by the duty status of the driver automatically changing to driving.
  9. Maintain a speed greater than the set speed threshold for 1 minute
  10. Verify the ELD does not allow any driver input when and the ELD is set to the “in motion” state.
  11. Bring the CMV back to a stop (CMV is stationery and vehicle speed stays at 0 km/h for 3 consecutive seconds) *
  12. Verify the ELD is automatically set back to a “stopped” state and allows for driver input
  13. Power off the CMV’s engine
  14. Logout

Expected Test Step Outcome:

Test 1:

User powered on the CMV’s engine and authenticated into the ELD using a driver user account. User kept the engine idling for 5 minutes and the ELD was successfully set to a “stopped” state and allowed for driver input.

User put the CMV in motion and maintain a vehicle speed lower than the set speed threshold for 1 minute. The ELD remained in a “stopped” state and, as per the requirements of provision 4.3.2c), did not allowed for driver input.

User accelerated to a vehicle speed greater than the set speed threshold and maintained that speed for 1 minute.  Once the vehicle speed exceeded the set speed threshold, the ELD successfully set and maintained the “in motion” state and did not allow any driver input.

User brought back the CMV to a stop.  After the CMV remained stationary for 3 consecutive seconds, the ELD was successfully set to a “stopped” state and allowed for driver input.  User logged out.

* The CMV is stationery and vehicle speed stays at 0 km/h for 3 consecutive seconds requirement stated at step k) is a minimum, additional measures to ensure the vehicles is or remains stationary are acceptable.

Corrections: Test 1, steps f), h), j), k), expected test step outcome changed. A * (note) was added

4.3.1.2.
Test step 3
Test 1, 2 and 3

Page 29

2021-08-18

Precondition(s):

  • Test 1, 2 and 3 (mandatory): ELD can establish a link with the engine ECM and receive speed information through each serial (SAE J1587/J1708), CAN (SAE J1939) and (SAE J1979/OBD-II) engines communication protocol

Expected Test Step Outcome:

Test 2 (SAE J1939):

For each communication protocol (250 Kbps and 500 Kbps baud rate), user performed the test procedure specified in previous Test 1. ELD successfully received vehicle speed information from the engine’s ECM

Precondition(s):

  • Test 1, 2 and 3 (mandatory): ELD can establish a link with the engine ECM and receive speed information through each serial (SAE J1587/J1708), CAN (SAE J1939) and (SAE J1979/OBD-II) engines communication protocol supported by the ELD.

Expected Test Step Outcome:

For each communication protocol supported by the ELD a test was performed

Test 2 (SAE J1939):

For each communication protocol supported by the ELD (250 Kbps and/or 500 Kbps baud rate), user performed the test procedure specified in previous Test 1. ELD successfully received vehicle speed information from the engine’s ECM.

Corrections: Precondition, expected test step outcome test 2 changed. Note added in expected test step outcome.

4.3.1.3
Test step 2
Test 1, 2 and 3

Pages 33 and 34

2021-08-18

Precondition(s):

  • Test 1, 2 and 3 (mandatory): ELD can establish a link with the engine ECM and receive odometer information through each serial (SAE J1587/J1708), CAN (SAE J1939) and (SAE J1979/OBD-II) engines communication protocol

Description of Test Step(s):

Test 3 (ECM communication protocol - SAE J1979/OBD-II):

  1. If information for total distance driven can be captured from the engine ECM, perform test procedure specified in previous Test 1. If not, perform Test Procedure 4.3.1.3-4

Expected Test Step Outcome:

Test 2 (SAE J1939):

For each communication protocol (250 Kbps and 500 Kbps baud rate), user performed the test procedure specified in previous Test 1. ELD successfully received vehicle speed information from the engine’s ECM

Precondition(s):

  • Test 1, 2 and 3 (mandatory): ELD can establish a link with the engine ECM and receive odometer information through each serial (SAE J1587/J1708), CAN (SAE J1939) and (SAE J1979/OBD-II) engine s communication protocol supported by the ELD.

Description of Test Step(s):

Test 3 (ECM communication protocol - SAE J1979/OBD-II):

  1. If odometer information for total distance driven can be captured from the engine ECM, perform test procedure specified in previous Test 1. If not, perform Test Procedure 4.3.1.3-4

Expected Test Step Outcome:

For each communication protocol supported by the ELD a test was performed

Test 2 (SAE J1939):

For each communication protocol supported by the ELD (250 Kbps and/or 500 Kbps baud rate), user performed the test procedure specified in previous Test 1. ELD successfully monitored the engine ECM’s odometer message and use it to report total vehicle distance information in the driver’s RODS.

Corrections: Precondition, test 3, step a), expected test step outcome test 2 changed. Note added in expected test step outcome.

4.3.1.3
Test step 3
Test 1, 2 and 3

Pages 35 and 36

2021-08-18

Precondition(s):

  • Test 1, 2 and 3 (mandatory): ELD can establish a link with the engine ECM and receive odometer information through each serial (SAE J1587/J1708), CAN (SAE J1939) and (SAE J1979/OBD-II) engines communication protocol

Expected Test Step Outcome:

Test 2 (SAE J1939):

For each communication protocol (250 Kbps and 500 Kbps baud rate), user performed the test procedure specified in previous Test 1. ELD successfully monitored the engine ECM’s odometer message and use it to report accumulated vehicle distance since engine’s last power on instance.

Precondition(s):

  • Test 1, 2 and 3 (mandatory): ELD can establish a link with the engine ECM and receive odometer information through each serial (SAE J1587/J1708), CAN (SAE J1939) and (SAE J1979/OBD-II) engine s communication protocol supported by the ELD.

Expected Test Step Outcome:

For each communication protocol supported by the ELD a test was performed

Test 2 (SAE J1939):

For each communication protocol supported by the ELD (250 Kbps and/or 500 Kbps baud rate), user performed the test procedure specified in previous Test 1. ELD successfully monitored the engine ECM’s odometer message and use it to report accumulated vehicle distance since engine’s last power on instance.

Corrections: Precondition, expected test step outcome test 2 changed. Note added in expected test step outcome.

4.3.1.4
Test step 1

Precondition(s)

Page 42

2021-08-18

Precondition(s):

  • For each event type including engine hours information (step h), ELD event records have been recorded in the ELD for the driver account holder specified in Test 1 and Test 2

Precondition(s):

  • For each event type including engine hours information (step hf of Test 1 ), ELD event records have been recorded in the ELD for the driver account holder specified in Test 1 and Test 2

Corrections: Precondition changed.

4.3.1.4
Test step 2
Test 1, 2 and 3

Pages 44 and 45

2021-08-18

Precondition(s):

  • Test 1, 2 and 3 (mandatory): ELD can establish a link with the engine ECM and receive engine hour information through each serial (SAE J1587/J1708), CAN (SAE J1939) and (SAE J1979/OBD-II) engines communication protocol

Expected Test Step Outcome:

Test 2 (SAE J1939):

For each communication protocol (250 Kbps and 500 Kbps baud rate), user performed the test procedure specified in previous Test 1. The ELD successfully monitored the engine ECM’s total engine hours message broadcast and use it to record elapsed and total engine hour information.

Precondition(s):

  • Test 1, 2 and 3 (mandatory): ELD can establish a link with the engine ECM and receive engine hour information through each serial (SAE J1587/J1708), CAN (SAE J1939) and (SAE J1979/OBD-II) engine s communication protocol supported by the ELD.

Expected Test Step Outcome:

For each communication protocol supported by the ELD a test was performed

Test 2 (SAE J1939):

For each communication protocol supported by the ELD (250 Kbps and/or 500 Kbps baud rate), user performed the test procedure specified in previous Test 1. The ELD successfully monitored the engine ECM’s total engine hours message broadcast and use it to record elapsed and total engine hour information.

Corrections: Precondition, expected test step outcome test 2 changed. Note added in expected test step outcome.

4.3.1.6
Test step 1
Test 1

Pages 49 and 50

2021-08-18

Description of Test Step(s):

Test 1:

  1. Power on the CMV’s engine
  2. Authenticate into the ELD using a driver user account
  3. Navigate to the driver’s RODS (section for event records)
  4. Identify the event record associated to the engine power up recorded in previous step (a)
  5. Verify the distance information (distance since last valid coordinates) reported for this record is 0. If not 0, perform steps (1) to (7).
  6. If the value reported in step (e) is 0, verify the current location information reported in the RODS is in standard latitude/longitude coordinates and corresponds to the actual coordinates reported by the external GPS device
  7. Drive the vehicle for five kilometres
  8. Bring the vehicle to a stop
  9. Set the driver’s duty status to on duty not driving
  10. Navigate to the driver’s RODS (section for event records)
  11. Identify the event record associated to the change in driver’s duty status recorded in previous step (i)
  12. Verify the information (distance since last valid coordinates) reported for this record is 0. If not 0, perform steps (1) to (7).
  13. If the value reported in step (l) is 0, verify the current location information reported in the RODS is in standard latitude/longitude coordinates and corresponds to the actual coordinates reported by the external GPS device
  14. Repeat previous steps i to o until verifying a total of five different locations
  15. Logout

Description of Test Step(s):

Test 1:

  1. Power on the CMV’s engine
  2. Authenticate into the ELD using a driver user account
  3. Navigate to the driver’s RODS (section for event records)
  4. Identify the event record associated to the engine power up recorded in previous step (a)
  5. Verify the distance information (distance since last valid coordinates) reported for this record is 0. If not 0, perform steps (1) to (7).
  6. If the value reported in step (e) is 0, verify the current location information reported in the RODS is in standard latitude/longitude coordinates and corresponds to the actual coordinates reported by the external GPS device
  7. Drive the vehicle for five kilometres
  8. Bring the vehicle to a stop
  9. Set the driver’s duty status to on duty not driving
  10. Navigate to the driver’s RODS (section for event records)
  11. Identify the event record associated to the change in driver’s duty status recorded in previous step (i)
  12. Verify the information (distance since last valid coordinates) reported for this record is 0. If not 0, perform steps (1) to (7).
  13. If the value reported in step (l) is 0, verify the current location information reported in the RODS is in standard latitude/longitude coordinates and corresponds to the actual coordinates reported by the external GPS device
  14. Repeat previous steps (i) to (o) until steps (g) to (m) until verifying a total of five different locations
  15. Logout

Corrections: Test 1, step n) changed.

4.3.2.1.
Test step 1
Test 1

Page 61

2021-03-23

Description of Test Step(s):

Test 1:

  1. Authenticate into the ELD using a driver user account
  2. Navigate to driver’s RODS
  3. Verify the user can edit his RODS and manually enter the CMV power unit number and trailer number(s). in the ELD records
  4. Logout

Description of Test Step(s):

Test 1:

  1. Authenticate into the ELD using a driver user account
  2. Navigate to driver’s RODS
  3. Verify the user can edit his RODS and manually enter the CMV power unit number and trailer number(s). in the ELD records
  4. Logout

Corrections: Test 1, steps b) and c) changed.

4.3.2.1.
Test step 2
Test 1

Page 62

2021-03-23

Description of Test Step(s):

Test 1:

  1. Authenticate into the ELD using a driver user account
  2. Navigate to driver’s RODS
  3. Verify the data elements for the CMV power unit number and trailer number(s) in the event records were automatically populated by the ELD
  4. Verify the user can edit his RODS and make corrections to these fields
  5. Logout

Description of Test Step(s):

Test 1:

  1. Authenticate into the ELD using a driver user account
  2. Navigate to driver’s RODS
  3. Verify the data elements for the CMV power unit number and trailer number(s) in the event records were automatically populated by the ELD
  4. Verify the user can edit his RODS and make corrections to these fields
  5. Logout

Corrections: Test 1, steps b) and d) changed.

4.3.2.2.4
Test step 4
Test 1 and 2

Page 94

2021-03-23

Description of Test Step(s):

Test 1 (driver function):

  1. Perform Test Procedure 4.3.2.2.4-2 (Test 1) without logging out
  2. Verify the ELD prompts the user to affirmatively review and confirm the new cycle (cycle 2) and new duty-/driving-hour limitations
  3. Logout

Test 2 (support personnel function):

  1. Perform Test Procedure 4.3.2.2.4-2 (Test 2) without logging out
  2. Verify the ELD prompts the user to affirmatively review and confirm the new cycle (cycle 2) and new duty-/driving-hour limitations
  3. Logout

Expected Test Step Outcome:

Test 1:

User performed Test Procedure 4.3.2.2.4-2 (Test 1) without logging out. ELD successfully prompted the user to affirmatively review and confirm the new cycle (cycle 2) and new duty-/driving-hour limitations. User logged out.

Test 2:

User performed Test Procedure 4.3.2.2.4-2 (Test 2) without logging out. ELD successfully prompted the user to affirmatively review and confirm the new cycle (cycle 2) and new duty-/driving-hour limitations. User logged out.

Description of Test Step(s):

Test 1 (driver function):

  1. Perform Test Procedure 4.3.2.2.4-2 (Test 1) without logging out
  2. Verify the ELD prompts the user to affirmatively review and confirm the new cycle (cycle 2) (cycle 1) and new duty-/driving-hour limitations
  3. Logout

Test 2 (support personnel function):

  1. Perform Test Procedure 4.3.2.2.4-2 (Test 2) without logging out
  2. Verify the ELD prompts the user to affirmatively review and confirm the new cycle (cycle 2) (cycle 1) and new duty-/driving-hour limitations
  3. Logout

Expected Test Step Outcome:

Test 1:

User performed Test Procedure 4.3.2.2.4-2 (Test 1) without logging out. ELD successfully prompted the user to affirmatively review and confirm the new cycle (cycle 2) (cycle 1) and new duty-/driving-hour limitations. User logged out.

Test 2:

User performed Test Procedure 4.3.2.2.4-2 (Test 2) without logging out. ELD successfully prompted the user to affirmatively review and confirm the new cycle (cycle 2) (cycle 1) and new duty-/driving-hour limitations. User logged out.

Correction: Test 1 and test 2, steps b), expected test step outcome changed (cycle 2) to (cycle 1).

4.3.2.8.2
Test step 6,
Test 1

Page 148

2021-03-23

Expected Test Step Outcome:

Test 1:

User authenticated into the ELD using a support personnel user account and navigated to the driver’s RODS (driver 1 and driver 2).  For the current day, neither driver was respectively indicated in each other’s RODS as a co-driver, and the ELD successfully did not allow the ELD username associated with a driving record to be edited and reassigned.  For the previous day…

Expected Test Step Outcome:

Test 1:

This Test is to be performed only if the function at provision 4.3.3.1.3 is available on the ELD.

User authenticated into the ELD using a support personnel user account and navigated to the driver’s RODS (driver 1 and driver 2).  For the current day, neither driver was respectively indicated in each other’s RODS as a co-driver, and the ELD successfully did not allow the ELD username associated with a driving record to be edited and reassigned.  For the previous day…

Instruction: Test procedure at provision 4.3.2.8.2 / test step 6 / test 1 is to be performed only if the function at 4.3.3.1.3 (page 163) is available on the ELD.

4.3.2.8.2
Test step 7,
Test 2

Page 151

2021-03-23

Expected Test Step Outcome:

Test 2:

Users successfully authenticated in as a support personnel user account. User …

Expected Test Step Outcome:

Test 2:

This Test is to be performed only if the function at provision 4.3.3.1.3 is available on the ELD.

Users successfully authenticated in as a support personnel user account. User …

Instruction: Test procedure at provision 4.3.2.8.2 / test step 7 / test 2 is to be performed only if the function at 4.3.3.1.3 (page 163) is available on the ELD.

Report a problem with this page

Date modified: