initiated self when vehicle test at rest GF System System Audio and Driver to respond to sensor failure Fail startup and visual alert alerts. driver when vehicle initiated self is at rest test MCSAC Recommendation: Consistent with the recommendation to add paragraph (o)(3)(ii), as discussed above, the Committee recommends adding the following Table 4 to Appendix A (there may be additional data exceptions that are appropriate to add to this list): Appendix A Table 4: – Table 4 Data Diagnostic Events – Diagnostic Data Exception Criteria Event Code D1 Changes in GPS position per Driver ID indicate recording gaps or error D2 Changes in odometer per Driver ID indicate recording gaps or error D3 Date/Time stamps of duty status records indicate recording gaps or error D4 Duty status record missing required data fields D5 Diagnostic event record missing required data fields 2. Communications Standards for the Transmittal of Data Files From Electronic On-Board Recorders (EOBRs) MCSAC Recommendations: FMCSA should refer to the Technical Workgroup Notes (Appendix C) sections on Telematics (Section III) and Peer-to-Peer (Section II) in the Agency’s development of a technical working document (or Appendix to a regulation) on Telematics and Peer-to-Peer. Delete remainder of Section 2 below. 2.1 must produce and store RODS in accordance with the file format specified in this Appendix and must be capable of a one-way transfer of these records through wired and wireless methods to authorized safety officials upon request. 2.2 EOBRs must be capable of transferring RODS using the Serial Bus “Universal Specification (Revision 2.0)” (incorporated by reference, see §395.18). Each EOBR device must
initiated self test when vehicle at rest GF System Fail System startup and driver initiated self test Audio and visual alert when vehicle is at rest Driver to respond to sensor failure alerts. MCSAC Recommendation: Consistent with the recommendation to add paragraph (o)(3)(ii), as discussed above, the Committee recommends adding the following Table 4 to Appendix A (there may be additional data exceptions that are appropriate to add to this list): Appendix A – Table 4: Table 4 – Data Diagnostic Events Diagnostic Event Code Data Exception Criteria D1 Changes in GPS position per Driver ID indicate recording gaps or error D2 Changes in odometer per Driver ID indicate recording gaps or error D3 Date/Time stamps of duty status records indicate recording gaps or error D4 Duty status record missing required data fields D5 Diagnostic event record missing required data fields 2. Communications Standards for the Transmittal of Data Files From Electronic On-Board Recorders (EOBRs) MCSAC Recommendations: FMCSA should refer to the Technical Workgroup Notes (Appendix C) sections on Telematics (Section III) and Peer-to-Peer (Section II) in the Agency’s development of a technical working document (or Appendix to a regulation) on Telematics and Peer-to-Peer. Delete remainder of Section 2 below. 2.1 must produce and store RODS in accordance with the file format specified in this Appendix and must be capable of a one-way transfer of these records through wired and wireless methods to authorized safety officials upon request. 2.2 EOBRs must be capable of transferring RODS using the “Universal Serial Bus Specification (Revision 2.0)” (incorporated by reference, see §395.18). Each EOBR device must