Electronic Logging Device Test Procedure Corrections – Part 2 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.4.2
Test step 1

Page 18

2021-03-23

Precondition(s):

  • Geo-location information of the test environment is known
  • Have the latest Canadian geo-location database (available on the CCMTA website) with geo-location information of nearby identifiable locations
  • Cellular communication network must not be available

Precondition(s):

  • Geo-location information of the test environment is known
  • Have the latest Canadian geo-location database (available on the CCMTA website) with geo-location information of nearby identifiable locations
  • Cellular communication network must not be available after authentication

Correction: Last bullet under Preconditions.

4.4.4.2.1
Test step 1
Test 1

Page 39

2021-03-23

Description of Test Step(s):

Test 1:

  1. Authenticate into the ELD using a driver user account
  2. Navigate to the driver's RODS (section for event records)
  3. Verify an event was automatically recorded by the ELD during the Login process and the event record status was set to “1” (active) for the record
  4. Verify the event record origin was also set to “1” (automatically recorded by ELD) for the record
  5. Logout

Expected Test Step Outcome:

Test 1:
User authenticated into the ELD using a driver user account and navigated to the driver's RODS.
When the ELD automatically recorded an event during the login process, the ELD successfully set the “Event Record Status” to “1” (active) and the “Event Record Origin” to “1” (automatically recorded by ELD). User logged out.

Precondition(s):

  • Test procedure 4.4.1.2-2 was completed, and an automatic change of duty status to on-duty not driving record already exists in the driver's RODS

Description of Test Step(s):

Test 1:

  1. Authenticate into the ELD using a driver user account
  2. Navigate to the driver's RODS (section for event records)
  3. Verify an event was automatically recorded by the ELD during the Login process the automatic change of duty status to on-duty not driving event from step 4.4.1.2-2 was recorded in the ELD and the event record status was set to “1” (active) for the record
  4. Verify the event record origin was also set to “1” (automatically recorded by ELD) for the record
  5. Logout

Expected Test Step Outcome:

Test 1:

User authenticated into the ELD using a driver user account and navigated to the driver's RODS.
When the ELD automatically recorded an event during the login process, a change of duty status to on-duty not driving event , the ELD successfully set the “Event Record Status” to “1” (active) and the “Event Record Origin” to “1” (automatically recorded by ELD). User logged out.

Corrections: Added a preconditions. Test 1, step c), expected test step outcome changed.

4.4.5.2
Test step 2
Test 1

Page 63

2021-03-23

Requirement: A line data check value must be calculated when cataloguing drivers' ELD RODS at a motor carrier's facility.

Precondition(s):

  • Test 1 is required only if the ELD is cataloguing driver's RODS at a motor carrier's facility

Description of Test Step(s):

Test 1:

  1. Authenticate into the ELD with a support personnel user account
  2. Review driver's RODS that were catalogued at the motor carrier facility
  3. Verify a line data check value was calculated and included for each line when the driver's RODS were catalogued
  4. Logout

Requirement: A line data check value must be calculated when cataloguing drivers' ELD RODS at a motor carrier's facility.

Delete the test step

Precondition(s):

  • Test 1 is required only if the ELD is cataloguing driver's RODS at a motor carrier's facility

Description of Test Step(s):
Test 1:

  1. Authenticate into the ELD with a support personnel user account
  2. Review driver's RODS that were catalogued at the motor carrier facility
  3. Verify a line data check value was calculated and included for each line when the driver's RODS were catalogued
  4. Logout

Instruction: Delete the test step.

4.5.1.2
Test step 1
Test 2

Page 83

2021-03-23

Test 2 (team drivers):

  1. Power on the CMV's engine
  2. Authenticate into the ELD using a driver 1 user account
  3. Authenticate into the ELD as a co-driver, using driver 2 user account
  4. Set the driver's duty status to on duty not driving
  5. Put the vehicle in motion
  6. Drive for 65 minutes without changing the duty status
  7. Bring the vehicle to a stop
  8. Navigate to the driver's RODS (section for event records)
  9. Verify an intermediate log event was recorded for each authenticated user after the vehicle was in motion for 60 consecutive minutes
  10. Power off the CMV's engine
  11. Logout

Test 2 (team drivers):

  1. Power on the CMV's engine
  2. Authenticate into the ELD using a driver 1 user account
  3. Authenticate into the ELD as a co-driver, using driver 2 user account
  4. Set the driver's driver 2 duty status to on duty not driving
  5. Put the vehicle in motion
  6. Drive for 65 minutes without changing the duty status
  7. Bring the vehicle to a stop
  8. Navigate to the driver's RODS (section for event records)
  9. Verify an intermediate log event was recorded for each authenticated user after the vehicle was in motion for 60 consecutive minutes
  10. Power off the CMV's engine
  11. Logout

Correction: Test 2, step d) changed.

4.5.1.5
Test step 3
Test 1

Page 100

2021-08-18

Precondition(s):

  • Test Procedure 4.5.1.5-2 was successful
  • Verify the CMV information (CMV power unit number and VIN) associated to the vehicle used for Test Procedure 4.5.1.5-1

Description of Test Step(s):

Test 1:

  1. Review the ELD output data file generated in previous Test Procedure 4.5.1.5-2
  2. Identify the segment for the CMV list
  3. Verify the CMV order number associated to the vehicle used for Test Procedure 4.5.1.5-1
  4. Identify the segment for the ELD event list for driver's login and logout activity
  5. Identify the event records from the previous Test Procedure 4.5.1.5-1
  6. Verify each record is associated with the vehicle (corresponding CMV order number from the CMV list)
  7. Logout

Expected Test Step Outcome:

Test 1:
User reviewed the ELD output data file generated in Test Procedure 4.5.1.5-2. User identified the segment for the ELD event list for driver's login and logout activity and verified the event records from the previous Test Procedure 4.5.1.5-1. ELD successfully associated each record with the vehicle. User logged out.

Precondition(s):

  • Test Procedure 4.5.1.5-1 and 4.5.1.5-2 were successful
  • Verify the CMV information (CMV power unit number and VIN ) associated to the vehicle used for Test Procedure 4.5.1.5-1

Description of Test Step(s):

Test 1:

  1. Review the ELD output data file generated in previous Test Procedure 4.5.1.5-2
  2. Identify the segment for the CMV list
  3. Verify the CMV order number associated to the vehicle used for Test Procedure 4.5.1.5-1
  4. Identify the segment for the ELD event list for driver's login and logout activity
  5. Identify the event records from the previous Test Procedure 4.5.1.5-1
  6. Verify each record is associated with the vehicle (corresponding CMV order number from the CMV list)
  1. Authenticate into the ELD with the same driver user account as previous Test Procedures 4.5.1.5-1
  2. Navigate to the driver's RODS (section for event records)
  3. Identify the event records (login and logout events) from the previous Test Procedure 4.5.1.5-1
  4. Verify vehicle information (CMV Power Unit Number) for each record corresponds to the vehicle used in Test Procedure 4.5.1.5-1.
  5. Logout

Expected Test Step Outcome:

Test 1:

User reviewed the ELD output data file generated in Test Procedure 4.5.1.5-2. User identified the segment for the ELD event list for driver's login and logout activity and verified the event records from the previous Test Procedure 4.5.1.5-1. User authenticated into the ELD using the same driver user account as previous Test Procedure 4.5.1.5-1. User navigated the driver's RODS. User Identified the event records (login and logout events) from the previous Test Procedure 4.5.1.5-1. ELD successfully associated each record with the vehicle. User logged out.

Correction: Precondition, test 1, expected test step outcome changed.

4.6.1.1
Test step 2
Test 1

Pages 142 and 143

2021-03-23

Test 1:

  1. Ensure there is no driver currently authenticated in to the ELD
  2. Power on the CMV's engine and note the time
  3. Keep the engine idling for 5 minutes without authenticating in to the ELD
  4. Power off the CMV's engine and note the time
  5. Power off the ELD, disconnect the ELD from the CMV or disconnect the ECM interface (handheld device), such that the ELD cannot determine if the CMV's engine is powered
  6. Power on the CMV's engine and keep idling for 15 minutes
  7. Power off the CMV's engine
  8. Power on the ELD, reconnect the ELD to the CMV or reconnect the ECM interface (handheld device)
  9. Power on the CMV's engine and note the time
  10. Authenticate into the ELD using a driver user account
  11. Verify the data diagnostic indicator is currently active
  12. Verify the malfunction indicator is not active
  13. Navigate to the event records associated to the unidentified driver profile
  14. Verify the ELD recorded a power-up and shut down event in previous steps (b) and (d)
  15. Verify the ELD did not record any power-up or shut down event when the ELD was powered off or was disconnected from the CMV (steps f and g)
  16. Verify the ELD recorded a power-up event in previous step (i)
  17. When the ELD was powered on in previous step (i), verify a power data diagnostics event was recorded under the unidentified driver profile
  18. Logout

Expected Test Step Outcome:

Test 1:
User powered on the CMV's engine without authenticating in to the ELD. User kept the engine idling for 5 minutes and powered off the engine. User powered off the ELD or disconnected the ELD from the CMV (ELD cannot determine if the CMV's engine is powered). User completed an ignition power on cycle and, powered on the ELD or reconnected the ELD to the CMV (ELD can determine if the CMV's engine is powered). When the user powered on the CMV's engine and authenticated into the ELD using a driver user account, ELD successfully activated the data diagnostic indicator. User navigated to the event records associated to the unidentified driver profile and ELD successfully recorded a power data diagnostics event under the unidentified driver profile. User logged out.

Test 1:

  1. Ensure there is no driver currently authenticated in to the ELD
  2. Power on the CMV's engine and note the time
  3. Keep the engine idling for 5 minutes without authenticating in to the ELD
  4. Power off the CMV's engine and note the time
  5. Power off the ELD, disconnect the ELD from the CMV or disconnect the ECM interface (handheld device), such that the ELD cannot determine if the CMV's engine is powered
  6. Power on the CMV's engine and keep idling for 15 10 minutes
  7. Power off the CMV's engine
  8. Power on the ELD, reconnect the ELD to the CMV or reconnect the ECM interface (handheld device)
  9. Power on the CMV's engine and note the time
  10. Authenticate into the ELD using a driver user account (different from Test Procedure 4.6.1.1-1)
  11. Verify the data diagnostic indicator is currently not active
  12. Verify the malfunction indicator is not active
  13. Navigate to the event records associated to the unidentified driver profile
  14. Verify the ELD recorded a power-up and shut down event in previous steps (b) and (d)
  15. Verify the ELD did not record any power-up or shut down event when the ELD was powered off or was disconnected from the CMV (steps f and g)
  16. Verify the ELD recorded a power-up event in previous step (i)
  17. When the ELD was powered on in previous step (i), verify a power data diagnostics event was recorded under the unidentified driver profile
  18. Logout

Expected Test Step Outcome:

Test 1:
User powered on the CMV's engine without authenticating in to the ELD. User kept the engine idling for 5 minutes and powered off the engine. User powered off the ELD or disconnected the ELD from the CMV (ELD cannot determine if the CMV's engine is powered). User completed an ignition power on cycle and, powered on the ELD or reconnected the ELD to the CMV (ELD can determine if the CMV's engine is powered). When the user powered on the CMV's engine and authenticated into the ELD using a driver user account, ELD successfully activated did not activate the data diagnostic indicator. User navigated to the event records associated to the unidentified driver profile and ELD successfully recorded a power data diagnostics event under the unidentified driver profile. 
User logged out.

Corrections: Test 1, steps f), j) and k), expected test step outcome changed.

4.6.1.2
Test step 1
Test 1

Page 146

2021-08-18

Precondition(s):

  • Test Procedures 4.6.1.1-1 and 4.6.1.1-2 were successful
  • The CMV has an engine ECM, or the CMV does not have an engine ECM and uses alternate sources to obtain or estimate required engine parameters

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. Verify the data diagnostic indicator is not active
  4. Verify the malfunction indicator is not active
  5. Navigate to the driver's RODS (section for event records)
  6. When the ELD was powered on in previous test 1 step (j), verify the ELD recorded an engine-synchronization data diagnostics event for the driver
  7. Logout

Expected Test Step Outcome:

Test 1:
User powered on the CMV's engine and authenticated into the ELD using a driver user account. When the user powered on the CMV's engine, ELD did not activate the data diagnostic indicator. User navigated to the driver's RODS and ELD successfully recorded an engine-synchronization data diagnostics event for the corresponding user. User logged out.

Precondition(s):

  • Test Procedures 4.6.1.1-1 and 4.6.1.1-2 were was successful
  • The CMV has an engine ECM, or the CMV does not have an engine ECM and uses alternate sources to obtain or estimate required engine parameters

Description of Test Step(s):

Test 1:

  1. Power on the CMV's engine
  2. Authenticate into the ELD using a driver user account the same driver user account as previous Test Procedures 4.6.1.1-1 test 1
  3. Verify the data diagnostic indicator is currently not active
  4. Verify the malfunction indicator is not active
  5. Navigate to the driver's RODS (section for event records)
  6. When the ELD was powered on in previous test 1 Test Procedures 4.6.1.1-1 test 1 step (j), verify the ELD recorded an engine-synchronization data diagnostics event for the driver
  7. Logout

Expected Test Step Outcome:

Test 1:
User powered on the CMV's engine and authenticated into the ELD using a driver user account the same driver user account as previous Test Procedures 4.6.1.1-1 test 1. When the user powered on the CMV's engine, ELD successfully activated did not activate the data diagnostic indicator. User navigated to the driver's RODS and ELD successfully recorded an engine-synchronization data diagnostics event for the corresponding user. User logged out.

Corrections: Precondition, test 1, steps b) and f), expected test step outcome changed.

4.6.1.2
Test step 3
Test 1, 2 and 3

Pages 148 and 149

2021-08-18

Description of Test Step(s):

Test 1:

  1. Power on the CMV's engine
  2. Authenticate into the ELD using driver 1 user account
  3. Verify the data diagnostic indicator and the malfunction indicator are currently not active
  4. While the engine is idling, disconnect the ELD from the engine's ECM such that it cannot synch with the engine and retrieve the vehicle parameters
  5. Wait for 70 seconds
  6. Verify the data diagnostic indicator is now currently active
  7. Wait for 10 minutes
  8. Verify the malfunction indicator is not active
  9. Power off the CMV'S engine
  10. Logout

Test 2:

  1. Test 1 was completed during the last 24-hour period
  2. Ensure there is no driver currently authenticated in to the ELD
  3. Power on the CMV's engine
  4. While the engine is idling, disconnect the ELD from the engine's ECM such that it cannot synch with the engine and retrieve the vehicle parameters
  5. Wait for 10 minutes
  6. Power off the CMV'S engine

Test 3:

  1. Test 1 and Test 2 were completed during the last 24-hour period
  2. Power on the CMV's engine
  3. Authenticate into the ELD using driver 2 user account
  4. Verify the data diagnostic indicator and the malfunction indicator are currently not active
  5. While the engine is idling, disconnect the ELD from the engine's ECM such that it cannot synch with the engine and retrieve the vehicle parameters
  6. Wait for 70 seconds
  7. Verify the data diagnostic indicator is now currently active
  8. Wait for 15 minutes
  9. Verify the malfunction indicator is now currently active
  10. Navigate to the driver's RODS (section for event records)
  11. Verify the ELD recorded an engine synchronization compliance malfunction event
  12. Power off the CMV'S engine
  13. Logout

Expected Test Step Outcome:

Test 1:
User powered on the CMV's engine and authenticated into the ELD using driver 1 user account. User verified the data diagnostic indicator and the malfunction indicator were not active. When the engine was idling, user disconnected the ELD from the engine's ECM such that it can no longer synch with the engine and retrieve the vehicle parameters. After 60 seconds, the ELD successfully activated the data diagnostic indicator. User waited another 10 minutes and the malfunction indicator was not activated. User powered off the engine and logged out.

Test 2:
User completed previous Test 1 during the last 24-hour period. User powered on the CMV's engine without authenticating in to the ELD. When the engine was idling, user disconnected the ELD from the engine's ECM such that it can no longer synch with the engine and retrieve the vehicle parameters.
User waited another 10 minutes and powered off the engine.

Test 3:
User completed previous Test 1 and Test 2 during the last 24-hour period. User powered on the CMV's engine and authenticated into the ELD using driver 2 user account. User verified the data diagnostic indicator and the malfunction indicator were not active. When the engine was idling, user disconnected the ELD from the engine's ECM such that it can no longer synch with the engine and retrieve the vehicle parameters. After 60 seconds, the ELD successfully activated the data diagnostic indicator. User waited another 15 minutes.
Once the loss of connectivity reached a total of 30 minutes aggregated across all driver profiles. The ELD successfully activated the malfunction indicator. User navigated to the driver's RODS and ELD successfully recorded an engine synchronization compliance malfunction event. User powered off the engine and logged out.
Actual Test Step Outcome:

Description of Test Step(s):

Test 1:

  1. Power on the CMV's engine
  2. Authenticate into the ELD using driver 1 user account
  3. Verify the data diagnostic indicator and the malfunction indicator are currently not active
  4. While the engine is idling, disconnect the ELD from the engine's ECM such that it cannot synch with the engine and retrieve the vehicle parameters
  5. Wait for 70 seconds
  6. Verify the data diagnostic indicator is now currently active
  7. Wait for 10 minutes then reconnect the ELD to the engine's ECM
  8. Verify the malfunction indicator is not active
  9. Power off the CMV'S engine
  10. Logout

Test 2:

  1. Test 1 was completed during the last 24-hour period
  2. Ensure there is no driver currently authenticated in to the ELD
  3. Power on the CMV's engine
  4. While the engine is idling, disconnect the ELD from the engine's ECM such that it cannot synch with the engine and retrieve the vehicle parameters
  5. Wait for 10 minutes then reconnect the ELD to the engine's ECM
  6. Power off the CMV'S engine

Test 3:

  1. Test 1 and Test 2 were completed during the last 24-hour period
  2. Power on the CMV's engine
  3. Authenticate into the ELD using driver 2 user account
  4. Verify the data diagnostic indicator and the malfunction indicator are currently not active
  5. While the engine is idling, disconnect the ELD from the engine's ECM such that it cannot synch with the engine and retrieve the vehicle parameters
  6. Wait for 70 seconds
  7. Verify the data diagnostic indicator is now currently active
  8. Wait for 15 minutes
  9. Verify the malfunction indicator is now currently active
  10. Navigate to the driver's RODS (section for event records)
  11. Verify the ELD recorded an engine synchronization compliance malfunction event
  12. Power off the CMV'S engine
  13. Logout then reconnect the ELD to the engine's ECM

Expected Test Step Outcome:

Test 1:
User powered on the CMV's engine and authenticated into the ELD using driver 1 user account. User verified the data diagnostic indicator and the malfunction indicator were not active. When the engine was idling, user disconnected the ELD from the engine's ECM such that it can no longer synch with the engine and retrieve the vehicle parameters. After 60 seconds, the ELD successfully activated the data diagnostic indicator. User waited another 10 minutes, reconnected the ELD to the engine's ECM and the malfunction indicator was not activated. User powered off the engine and logged out.

Test 2:
User completed previous Test 1 during the last 24-hour period. User powered on the CMV's engine without authenticating in to the ELD. When the engine was idling, user disconnected the ELD from the engine's ECM such that it can no longer synch with the engine and retrieve the vehicle parameters.
User waited another 10 minutes, reconnected the ELD to the engine's ECM and powered off the engine.

Test 3:
User completed previous Test 1 and Test 2 during the last 24-hour period. User powered on the CMV's engine and authenticated into the ELD using driver 2 user account. User verified the data diagnostic indicator and the malfunction indicator were not active. When the engine was idling, user disconnected the ELD from the engine's ECM such that it can no longer synch with the engine and retrieve the vehicle parameters. After 60 seconds, the ELD successfully activated the data diagnostic indicator. User waited another 15 minutes.
Once the loss of connectivity reached a total of 30 minutes aggregated across all driver profiles. The ELD successfully activated the malfunction indicator. User navigated to the driver's RODS and ELD successfully recorded an engine synchronization compliance malfunction event. User powered off the engine and logged out then reconnect the ELD to the engine's ECM.

Actual Test Step Outcome:

Corrections: Test 1, 2 and 3, expected test step outcome for all 3 tests changed.

4.6.3
Test step 1

Page 178

2021-03-23

Precondition(s):

  • Test Procedure 4.6.1.4-4 was completed and ELD has set a positioning compliance malfunction for driver 1
  • User account for driver 2 must not have any active data diagnostic event

Precondition(s):

  • Test Procedure 4.6.1.4-4 4.6.1.4-7 was completed and ELD has set a positioning compliance malfunction missing required data elements data diagnostic event for driver 1
  • User account for driver 2 must not have any active data diagnostic event

Correction: First bullet under preconditions changed.

4.6.4
Test step 2,
Test 1

Page 184

2021-03-23

When variable DST is supported, test 1

  1. At 10:00 set duty status to driving until 19:00.                               (9H)
  1. Verify the ELD notifies at 18:30  that the driver is 30 minutes from the 70 hours limit of cycle 1  (9H)
  1. At 19:00 set duty status to off-duty until 07:00  (12H)                     (12H)

When variable DST is supported, test 1

  1. At 10:00 set duty status to driving until 13:15.                        (3:15H)
  1. Verify the ELD notifies at 12:45 that the driver is 30 minutes from the 70 hours limit of cycle 1
  1. At 13:15 set duty status to off-duty until 07:00.                 (17:45H)

Corrections: Test 1, steps bb), cc) and dd) changed.

4.6.4
Test step 2,
Test 2

Pages 187 and 188

2021-08-18

When variable DST is supported, test 2

  1. At 23:40 set duty status to off-duty until 08:00                        (20m+8:00H) 
  2. At 08:00 set duty status to driving until 22:00.                        (14H)
  3. At 22:00 set duty status to off-duty until 08:00                        (2+8H) 
  4. At 08:00 set duty status to driving until 16:00.                        (8H)
  5. At 16:00 set duty status to ODND until 18:50                            (2:50H)
  6. At 18:50 set duty status to SB until 02:35.                             (5:10+2:35H)
  7. At 02:35 set duty status to driving until 07:35.                        (5H)
  8. At 07:35 set duty status to SB until 09:20.                             (1:45H)
  9. At 09:20 set duty status to driving until 11:20.                        (2H)
  10. Verify the ELD notifies at 10:50 that the driver is 30 minutes from the driving time (shift) limitation
  11. Verify the ELD notifies at 11:00 that the driver is 30 minutes from the on-duty time (shift) limitation
  12. Verify the ELD notifies at 11:15 that the driver is 30 minutes from the elapsed time in the (shift) limitation                    (12:40+ 8H)
  13. At 11:20 set duty status to SB until 08:00.

and

  1. Verify the ELD DOES NOT notify the driver for any limitation

Expected Test Step Outcome

Test 2
- At aa) Does the ELD count properly before and after each sleeper berth calculation.
If the ELD issues a warning, it should be a fail.

When variable DST is supported, test 2

After i) insert: At 08:00 set duty status to ODND until 09:00.               (1H)

  1. At 09:00 set duty status to driving until 23:00.                                 (14H)
  2. At 23:00 set duty status to off-duty until 08:00                                 (1+8H)
  3. At 08:00 set duty status to driving until 16:00.                                  (8H)
  4. At 16:00 set duty status to ODND until 17:50.                                 (1:50H) 
  5. At 17:50 set duty status to SB until 01:35.            (6:10+1:35H)
  6. At 01:35 set duty status to driving until 06:35.                        (5H)
  7. At 06:35 set duty status to SB until 07:20.                               (45m)
  8. At 07:20 set duty status to driving until 09:20.                         (2H)
  9. Verify the ELD notifies at 08:50 that the driver is 30 minutes from the driving time (shift) limitation
  10. Verify the ELD notifies at 11:00 that the driver is 30 minutes from the on-duty time (shift) limitation Delete that verification
  11. Verify the ELD notifies at 09:15 that the driver is 30 minutes from the 18 Hours elapsed time in the (shift) limitation.
  12. At 09:20 set duty status to SB until 08:00.                                 (14:40+8H)

and

  1. Verify the ELD DOES NOT notify the driver for any notifies at 18:30 that the driver is 30 minutes from the driving time (shift) limitation

Expected Test Step Outcome:

Test 2:
- At aa) Does the ELD count properly before and after each sleeper berth calculation. Step y) has to be used to calculate the Splitting of Daily Off-duty Time.
If the ELD issues a warning, it should be a fail.

Corrections:  Test 2, steps i) to k), m) to u), dd), and expected test step outcome at aa), changed.

4.6.4
Test step 2,
Test 3

Page 191

2021-03-23

When variable DST is supported, test 3

  1. At 11:35 set duty status to SB until 15:20.                                 (3:45H)
  1. At 15:20 set duty status to driving until 17:20.                            (2H)
  1. Verify the ELD notifies at 16:50 that the driver is 30 minutes from the driving time (shift) limitation
  1. Verify the ELD notifies at 17:00 that the driver is 30 minutes from the on-duty time (shift) limitation
  1. Verify the ELD notifies at 17:15 that the driver is 30 minutes from the elapsed time in the (shift) limitation
  1. At 17:20 set duty status to off-duty until 02:00.                         (8:20H)

And

  1. At 00:00 set duty status to driving until 02:20.                          (2:20H)
  1. Verify the ELD notifies at 01:50 that the driver is 30 minutes from exceeding the 120 hours of on-duty time limit in Cycle 2

When variable DST is supported, test 3

  1. At 11:35 set duty status to SB until 13:20.                               (1:45H)
  1. At 13:20 set duty status to driving until 15:20.                            (2H)
  1. Verify the ELD notifies at 14:50 that the driver is 30 minutes from the driving time (shift) limitation
  1. Verify the ELD notifies at 15:00 that the driver is 30 minutes from the on-duty time (shift) limitation
  1. Verify the ELD notifies at 15:15 that the driver is 30 minutes from the elapsed time in the (shift) limitation
  1. At 15:20 set duty status to off-duty until 02:00                    (10:40H)

And

  1. At 00:00 set duty status to driving until 02:10.          (2:10H)
  1. Verify the ELD notifies at 01:40 that the driver is 30 minutes from exceeding the 120 hours of on-duty time limit in Cycle 2

Corrections: Test 3, steps vv) to aaa), hhh) and iii) changed.

4.6.4
Test step 2,
Test 4

Pages 192 and 193

2021-08-18

When variable DST is supported, test 4

  1. At 01:40 set duty status to off-duty until 10:00.                       (6:20+2H)
  2. At 10:00 set duty status to driving until 00:00.                        (14H)
  3. At 00:00 set duty status to off-duty until 08:00.                       (8H)
  4. At 08:00 set duty status to driving until 16:00.                        (8H)
  5. At 16:00 set duty status to ODND until 18:50.                           (2:50H)
  6. At 18:50 set duty status to SB until 02:35.                             (7:45H)
  7. At 02:35 set duty status to driving until 07:35.                        (5H)
  8. At 07:35 set duty status to SB until 09:20.                             (25m+1:20H)
  9. At 09:20 set duty status to ODND until 09:30.                           (10m)
  10. At 09:30 set duty status to driving until 11:30.                        (2H)
  11. Verify the ELD notifies at 11:00 that the driver is 30 minutes from the driving time (shift) limitation
  12. Verify the ELD notifies at 11:10 that the driver is 30 minutes from the on-duty time (shift) limitation
  13. Verify the ELD notifies at 11:15 that the driver is 30 minutes from the elapsed time in the (shift) limitation
  14. At 11:30 set duty status to off-duty until 04:30.
  15. At 04:30 set duty status to driving until 09:30.                               (17:00H)
  16. At 09:30 set duty status to SB until 13:00.                                  (3:30+1:30H)
  1. At 08:00 set duty status to driving until 17:30.                                (3:30)
  1. Verify the ELD DOES NOT notify the driver for any limitation.      (9:30H)
  1. At 17:30  set duty status to off-duty until 10:30.                           
  1. At 10:30 set duty status to ODND until 11:30.                (14:30+2:30H) (1H)

When variable DST is supported, test 4
After j ) insert: At 10:00 set duty status to ODND until 11:00.          (1H)

  1. At 11:00 set duty status to driving until 01:00.                          (14H)
  2. At 01:00 set duty status to off-duty until 09:00.                          (7+1H)
  3. At 09:00 set duty status to driving until 17:00.                          (8H)
  4. At 17:00 set duty status to ODND until 18:50.                         (1:50H)
  5. At 18:50 set duty status to SB until 02:35.                          (7:45H)
  6. At 02:35 set duty status to driving until 07:35.                         (5H)
  7. At 07:35 set duty status to SB until 08:25 .                          (25m+ 25m)
  8. At 08:25 set duty status to ODND until 08:35.                        (10m)
  9. At 08:35 set duty status to driving until 10:35 .                        (2H)
  10. Verify the ELD notifies at 10:05 that the driver is 30 minutes from the driving time (shift) limitation
  11. t) Verify the ELD notifies at 11:10 that the driver is 30 minutes from the on-duty time (shift) limitationDelete that verification
  12. Verify the ELD notifies at 10:15 that the driver is 30 minutes from the 18 Hours elapsed time in the (shift) limitation
  13. At 10:35 set duty status to SB until 06:00.                           (19:25H)
  14. At 06:00 set duty status to driving until 11:00.                          (2+3H)
  15. At 11:00 set duty status to SB until 13:00.                         (2H)
  1. At 08:00 set duty status to driving until 17:25.                           (9:25H)
  1. Verify the ELD DOES NOT notify the driver for any limitation.
  1. At 17:25 set duty status to off-duty until 10:25.     (14:35+2:25H)
  1. At 10:25 set duty status to ODND until 11:30.                        (1:05H)

Corrections: Test 4, steps i) to m), p) to x) and dd) ff), gg) changed.

4.6.4
Test step 2,
Test 4

Page 193

2021-08-18

When variable DST is supported, test 4

  1. Verify the ELD notifies at 15:40 that the driver is 30 minutes from the 80 hours in 7 days limit of cycle 2
  1. At 00:20 set duty status to off-duty until 08:00 on Tuesday 9             (31:40H)

When variable DST is supported, test 4

  1. Verify the ELD notifies at 15:40 that the driver is 30 minutes from the 80 hours in 7 days limit of cycle 2
  1. At 00:10 set duty status to off-duty until 08:00 on Tuesday the 9th              (31:50H)

Corrections: Test 4, steps jj) and kk) changed.

4.6.4
Test step 2,
Test 4

Page 194

2021-03-23

When variable DST is supported, test 4

  1. Verify the ELD notifies at 09:30 that the driver is 30 minutes from the 24 hours off in the previous 14 days limit

When variable DST is supported, test 4

  1. Verify the ELD notifies at 09:30 that the driver is 30 minutes from the 24 120 hours off on-duty time limit in the previous 14 days limit cycle 2.

Corrections: Test 4, step ww) changed.

4.6.4
Test step 4,
Test 1

Page 196

2021-08-18

When variable DST is supported, test 1

  1. Verify the ELD notifies at 21:30 that they are at least 30 minutes from the (shift) on-duty time limitations.
  2. At 21:50 set duty status to SB until 05:50.                        (8H)
  3. At 05:50 set duty status to driving until 11:50.                       (6H)
  4. At 11:50 set duty status to off-duty until 12:50.                      (1H)
  5. At 12:50 set duty status to driving until 17:50.                      (5H)
  6. At 17:50 set duty status to off-duty until 19:00.                      (1:10H)

When variable DST is supported, test 1

  1. Verify the ELD notifies at 21:30 that they are at least 30 minutes from the (shift) on-duty time limitations. Delete that verification
  2. At 21:50 set duty status to SB until 06:00.                     (8:10H)
  3. At 06:00 set duty status to driving until 12:00.                    (6H)
  4. At 12:00 set duty status to off-duty until 13:00.                    (1H)
  5. At 13:00 set duty status to driving until 18:00 .                   (5H)
  6. At 18:00 set duty status to off-duty until 19:00.                    (1H)

Corrections: Test 1, step g) to l) changed.

4.6.4
Test step 2,
Test 1

Page 201

2021-08-18

Expected Test Step Outcome:

Test 1:
Notification arrives at expected time
NOTE 30 Minutes warning is a minimum, if ELD is set for longer warning, adjust the time of the warning accordingly
Day test,
We want to ensure it calculates the day properly when the start is not midnight. Testing for:

Expected Test Step Outcome:

Test 1:
Notification arrives at expected time
NOTE 30 Minutes warning is a minimum, if ELD is set for longer warning, adjust the time of the warning accordingly
Day test,
We want to ensure it calculates the day properly when the start is not midnight.
Testing for:

Corrections: Expected test step outcome for test 1 changed.

4.6.4
Test step 2,
Test 1

Page 202

2021-03-23

When variable DST is not supported, test 1

  1. At 02:00 set duty status to driving until 11:00.                   (9H)
  1. Verify the ELD notifies at 10:30 that the driver is 30 minutes from the 70 hours limit of cycle 1
  1. At 11:00 set duty status to off-duty until 23:00.                   (12H)

When variable DST is not supported, test 1

  1. At 02:00 set duty status to driving until 05:15.                            (3:15H)
  1. Verify the ELD notifies at 04:45 that the driver is 30 minutes from the 70 hours limit of cycle 1
  1. At 05:15 set duty status to off-duty until 23:00.                            (17:45H)

Corrections: Test 1, steps cc) to ee) changed.

4.6.4
Test step 2,
Test 2

Pages 205 and 206

2021-08-18

When variable DST is not supported, test 2

  1. At 23:40 set duty status to off-duty until 08:00.                      (20m+8:00H)
  2. At 08:00 set duty status to driving until 22:00.                     (14H)
  3. At 22:00 set duty status to off-duty until 08:00                      (2+8H)
  4. At 08:00 set duty status to driving until 16:00.                     (8H)
  5. At 16:00 set duty status to ODND until 18:50                       (2:50H)
  6. At 18:50 set duty status to SB until 02:35.                       (5:10+2:35H)
  7. At 02:35 set duty status to driving until 07:35.                      (5H)
  8. At 07:35 set duty status to SB until 09:20.                      (1:45H)
  9. At 09:20 set duty status to driving until 11:20.                      (2H)
  10. Verify the ELD notifies at 10:50 that the driver is 30 minutes from the driving time (shift) limitation
  11. Verify the ELD notifies at 11:00 that the driver is 30 minutes from the on-duty time (shift) limitation
  12. Verify the ELD notifies at 11:15 that the driver is 30 minutes from the elapsed time in the (shift) limitation
  13. At 11:20 set duty status to SB until 08:00.                      (12:40+ 8H)
  1. Verify the ELD DOES NOT notify the driver for any limitation

and

Expected Test Step Outcome

Test 2
- At aa) Does the ELD count properly before and after each sleeper berth calculation.
If the ELD issues a warning, it should be a fail.

When variable DST is not supported, test 2
After j) insert: At 08:00 set duty status to ODND until 09:00.                 (1H)

  1.  At 09:00 set duty status to driving until 23:00.                           (14H)
  2. At 23:00 set duty status to off-duty until 08:00.                           (1+8H)
  3. At 08:00 set duty status to driving until 16:00.                          (8H)
  4. At 16:00 set duty status to ODND until 17:50.                          (1:50H)
  5. At 17:50 set duty status to SB until 01:35.                         (6:10+1:35H)
  6. At 01:35 set duty status to driving until 06:35.                         (5H)
  7. At 06:35 set duty status to SB until 07:20.                         (45m)
  8. At 07:20 set duty status to driving until 09:20 .                          (2H)
  9. Verify the ELD notifies at 08:50 that the driver is 30 minutes from the driving time (shift) limitation
  10. s)Verify the ELD notifies at 11:00 that the driver is 30 minutes from the on-duty time (shift) limitation Delete that verification
  11. Verify the ELD notifies at 09:15 that the driver is 30 minutes from the 18 Hours elapsed time in the (shift) limitation.
  12. At 09:20 set duty status to SB until 08:00.                       (14:40+8H)
  1. Verify the ELD DOES NOT notify the driver for any notifies at 18:30 that the driver is 30 minutes from the driving time (shift) limitation

and

Expected Test Step Outcome

Test 2
- At aa) Does the ELD count properly before and after each sleeper berth calculation. Step y) has to be used to calculate the Splitting of Daily Off-duty Time.
If the ELD issues a warning, it should be a fail.

Corrections: Test 2, steps i) to k), m) to u), dd) expected test step outcome at aa), changed.

4.6.4
Test step 2,
Test 3

Page 207

2021-03-23

When variable DST is not supported, test 3

  1. Verify the ELD notifies at 04:30 that the driver is 30 minutes from the day driving time limitation

When variable DST is not supported, test 3

  1. Verify the ELD notifies at 20:30 that the driver is 30 minutes from the day driving time limitation

Corrections: Test 3 step v) changed.

4.6.4
Test step 2,
Test 3

Page 209

2021-03-23

When variable DST is not supported, test 3

  1. At 03:35 set duty status to SB until 07:20.                   (3:45H)
  1. At 07:20 set duty status to driving until 09:20.                 (2H)
  1. Verify the ELD notifies at 08:50 that the driver is 30 minutes from the driving time (shift) limitation
  1. Verify the ELD notifies at 09:00 that the driver is 30 minutes from the on-duty time (shift) limitation
  1. Verify the ELD notifies at 09:15 that the driver is 30 minutes from the elapsed time in the (shift) limitation
  1. At 09:20 set duty status to off-duty until 18:00

And         (8:20H)

  1. At 16:00 set duty status to driving until 18:20.
  1. Verify the ELD notifies at 17:50 that the driver is 30 minutes from exceeding the 120 hours of on-duty time limit in Cycle 2         (2:20H)

When variable DST is not supported, test 3

  1. At 03:35 set duty status to SB until 05:20.                             (1:45H)
  1. At 05:20 set duty status to driving until 07:20.                        (2H)
  1. Verify the ELD notifies at 06:50 that the driver is 30 minutes from the driving time (shift) limitation
  1. Verify the ELD notifies at 07:00 that the driver is 30 minutes from the on-duty time (shift) limitation
  1. Verify the ELD notifies at 07:15 that the driver is 30 minutes from the elapsed time in the (shift) limitation
  1. At 07:20 set duty status to off-duty until 18:00                       (10:40H)

And

  1. At 16:00 set duty status to driving until 18:10.                         (2:10H)
  1. Verify the ELD notifies at 17:40 that the driver is 30 minutes from exceeding the 120 hours of on duty time limit in Cycle 2

Corrections: Test 3 , steps vv) to aaa), hhh) and iii) changed.

4.6.4
Test step 2,
Test 4

Pages 210 and 211

2021-08-18

When variable DST is not supported, test 4

  1. At 17:40 set duty status to off-duty until 02:00.                        (6:20+2H)
  2. At 02:00 set duty status to driving until 16:00.                        (14H) 
  3. At 16:00 set duty status to off-duty until 24:00.                        (8H)
  4. At 00:00 set duty status to driving until 08:00.                        (8H)
  5. At 08:00 set duty status to ODND until 10:50.                        (2:50H)
  6. At 10:50 set duty status to SB until 18:35.                        (7:45H)
  7. At 18:35 set duty status to driving until 23:35.                        (5H)
  8. At 23:35 set duty status to SB until 01:20.                        (25m+1:20H)
  9. At 01:20 set duty status to ODND until 01:30.                       (10m)
  10. At 01:30 set duty status to driving until 03:30.                       (2H)
  11. Verify the ELD notifies at 03:00 that the driver is 30 minutes from the driving time (shift) limitation
  12. Verify the ELD notifies at 03:10 that the driver is 30 minutes from the on-duty time (shift) limitation
  13. Verify the ELD notifies at 03:15 that the driver is 30 minutes from the elapsed time in the (shift) limitation     (17:00H)
  14. At 03:30 set duty status to off-duty until 20:30.                           (3:30+1:30H)
  15. At 20:30 set duty status to driving until 01:30.                          (3:30H)
  16. At 01:30 set duty status to SB until 05:00.
  1. At 00:00 set duty status to driving until 09:30.                            (9:30H)
  1. Verify the ELD DOES NOT notify the driver for any limitation.
  1. At 09:30 set duty status to off-duty until 02:30.                        (14:30+2:30H)
  1. At 02:30 set duty status to ODND until 03:30.                        (1H)

When variable DST is not supported, test 4
After h ) insert: At 02:00 set duty status to ODND until   03:00.      (1H)

  1. At 03:00 set duty status to driving until 17:00.                            (14H)
  2. At 17:00 set duty status to off-duty until 01:00.                                 (7+1)
  3. At 01:00 set duty status to driving until 09:00 .                                 (8H)
  4. At 09:00 set duty status to ODND until 10:50.                               (1:50H)
  5. At 10:50 set duty status to SB until 18:35.                                 (7:45H)
  6. At 18:35 set duty status to driving until 23:35.                                 (5H)
  7. At 23:35 set duty status to SB until 00:25.                                 (25m+25m)
  8. At 00:25 set duty status to ODND until 00:35 .                                (10m)
  9. At 00:35 set duty status to driving until 02:35.                                (2H)
  10. Verify the ELD notifies at 02:05 that the driver is 30 minutes from the driving time (shift) limitation
  11. Verify the ELD notifies at 03:10 that the driver is 30 minutes from the on-duty time (shift) limitation Delete that verification
  12. Verify the ELD notifies at 02:15 that the driver is 30 minutes from the 18 Hours elapsed time in the (shift) limitation
  13. At 02:35 set duty status to SB until 22:00.                               (19:25H)
  14. At 22:00 set duty status to driving until 03:00.                                (2+3H)
  15. At 03:00 set duty status to SB until 05:00.                                (2H)
  1. At 00:00 set duty status to driving until 09:25.                           (9:25H)
  1. Verify the ELD DOES NOT notify the driver for any limitation.
  1. At 09:25 set duty status to off-duty until 02:25.            (14:35+2:25H)
  1. At 02:25 set duty status to ODND until 03:30.                           (1:05H)

Corrections:  Test 4, steps h) to l), o) to x ) and cc) to ff) changed.

4.6.4
Test step 2,
Test 4

Page 211

2021-08-18

When variable DST is not supported, test 4

  1. Verify the ELD notifies at 15:40 that the driver is 30 minutes from the 80 hours in 7 days limit of cycle 2
  1. At 16:20 set duty status to off-duty until 24:00  on Monday the 8th                 (31:40H)

When variable DST is not supported, test 4

  1. Verify the ELD notifies at 15:40 that the driver is 30 minutes from the 80 hours in 7 days limit of cycle 2
  1. At 16:10 set duty status to off-duty until 24:00 on Monday the 8th, (31:50H)

Corrections: Test 4, step ii) and jj) changed.

4.6.4
Test step 2,
Test 4

Page 212

2021-03-23

When variable DST is not supported, test 4

  1. Verify the ELD notifies at 01:30 that the driver is 30 minutes from the 24 hours off in the previous 14 days limit.

When variable DST is not supported, test 4

  1. Verify the ELD notifies at 01:30 that the driver is 30 minutes from the 24 120 hours on-duty time limit in the previous 14 days limit cycle 2.

Corrections: Test 4, step vv) changed.

4.6.4
Test step 4
Test 1

Page 214

2021-08-18

When variable DST is not supported, test 4

  1. Verify the ELD notifies at 13:30 that they are at least 30 minutes from the (shift) on-duty time limitations.
     
  2. At 13:50 set duty status to SB until 21:50.                           (8H)
  3. At 21:50 set duty status to driving until 03:50.                          (6H)
  4. At 03:50 set duty status to off-duty until 04:50.                     (1H)
  5. At 04:50 set duty status to driving until 09:50.                          (5H)
  6. At 09:50 set duty status to off-duty until 11:00.                     (1:10H)

When variable DST is not supported, test 4

  1. Verify the ELD notifies at 21:30 that they are at least 30 minutes from the (shift) on-duty time limitations. Delete that verification
     
  2. At 13:50 set duty status to SB until 22:00 .                        ( 8:10H)
  3. At 22:00 set duty status to driving until 04:00.                       (6H)
  4. At 04:00 set duty status to off-duty until 05:00.                       (1H)
  5. At 05:00 set duty status to driving until 10:00.                         (5H)
  6. At 10:00 set duty status to off-duty until 11:00.                         (1H)

Corrections: Test 1, step g) to l) changed.

Report a problem with this page

Date modified: