![]() The time thresholds for purposes of this section must not be configurable.Ĥ.4.1.3. If the driver does not respond to the ELD prompt within 1-minute after receiving the prompt, the ELD must automatically switch the duty status to on-duty not driving. When the duty status is set to driving, and the CMV has not been in-motion for 5 consecutive minutes, the ELD must prompt the driver to confirm continued driving status or enter the proper duty status. Automatic Setting of Duty Status to On-Duty Not Driving (b ) Sets the duty status to on-duty not driving and indicates yard moves, in which case duty status must remain on-duty not driving until driver's indication of the driving condition ends.Ĥ.4.1.2. ![]() Configuration of Available Categories Impacting Driving Time Recording If an ELD or a technology that includes an ELD function offers configuration options to the motor carrier or the driver that are not otherwise addressed or prohibited in this appendix, the configuration options must not affect the ELD's compliance with the requirements of this rule for each configuration setting of the ELD.Ĥ.3.3.1.1. The ELD must require each co-driver to confirm the change for the corrective action to take effect.Īn ELD must restrict availability of motor carrier entries outlined in this section only to authenticated “support personnel” account holders. In the case of team drivers, the driver account associated with the driving time records may be edited and reassigned between the team drivers if there was a mistake resulting in a mismatch between the actual driver and the driver recorded by the ELD and if both team drivers were respectively indicated in each other's records as a co-driver. (2 ) Correction of errors with team drivers. Sections 4.9 and 4.10, respectively, describe the data reporting requirements and the communications protocols. Section 4.8 explains ELD outputs, which are the information displayed to a user and the standard data output file an ELD must produce. Section 4.7 introduces technical functions that are intended to guard a driver against harassment and introduces a privacy preserving provision when a driver operates a CMV for personal purposes. Section 4.6 introduces device self-monitoring requirements and standardizes the minimal set of malfunctions and data diagnostic events an ELD must be able to detect. Section 4.5 describes the events an ELD must record and the data elements each type of event must include. The ELD requirements for internal processing and tracking of information flow are described in section 4.4, which includes conditions for and prohibitions against automatic setting of duty-status in section 4.4.1, required geo-location and date and time conversion functions in sections 4.4.2 and 4.4.3, respectively, use of event attributes for tracking of edit and entry history in section 4.4.4, and the use of data check functions in the recording of ELD logs in section 4.4.5 as standard security measures for all ELDs. Section 4.3 describes the inputs of an ELD which includes automatically measured signals by the ELD as covered in section 4.3.1, and manual entries by the authenticated driver as covered in section 4.3.2 and by the motor carrier as covered in section 4.3.3. ![]() Section 4.2 explains internal engine synchronization requirements and its applicability when used in recording a driver's record of duty status in CMVs. More specifically, section 4.1 describes the security requirements for account management within an ELD system and introduces the term “Unidentified Driver” account. (c ) Section 4 lists functional requirements for an ELD. Data Diagnostic Event Indicator Statusħ.9. In reviewing the Work with Database File (WRKDBF) command for the previous issue of Midrange Developer, I was reminded of the number of times I've needed to convert data from its character value to its hexadecimal representation.7.7. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |