| Data Transfer Methods | To submit the Output File to an authorized safety official, the driver selects the “Export ELD Data File” from the Logbook screen. The driver, then, will select one of the following methods: Option 1—Telematics using both: Wireless Web services and Email (both) Option 2—Local using both: USB2 and Bluetooth (both) - Agent External Storage: The ELD will first verify the external storage device is compatible with FMCSA specifications by validating the contents of file "ELDUSBTX.TXT". After positive validation the ELD will save the data file on the FMCSA-provided external storage device. - Bluetooth Transfer: After selecting this option, the authorized safety official will pair and verify PIN with the driver. Once the Bluetooth devices are paired, the safety official’s technology equipment will transfer the output file to the FMCSA website using Web services. - FMCSA web service: This option securely communicates to FMCSA's end-point ad obtains submission ID. Description of the supported and certified data transfer mechanisms and step-by-step instructions for a driver to produce and transfer the ELD records to an authorized safety official Description of the supported and certified data transfer mechanisms and step-by-step instructions for a driver to produce and transfer the ELD records to an authorized safety official |
| Malfunction Notes | Low battery, network disconnection, low internal memory space, ECM data transfer failure, location sensor failure. In addition the following malfunctions are detected (and appropriate records created) by the StreetEagle ELD: - Power data diagnostic (diagnostic - 1) - Engine synchronization data diagnostic (diagnostic - 2) - Missing required data elements (diagnostic - 3) - Data transfer (diagnostic - 4) - Unidentified driving records data diagnostic (diagnostic - 5) - Other ELD diagnostics (diagnostic - 6 - Power compliance (malfunction - P) - Engine synchronization compliance (malfunction - E) - Timing compliance (malfunction - T) - Positioning compliance (malfunction - L) - Data recording compliance (malfunction - R) - Data transfer compliance (malfunction - S) - Other ELD malfunctions (malfunction - O) |
| Certifying Statement | The Mondo ELD HOS was tested on a diverse range of CMVs from different manufacturers and models as well drivers with different experience and backgrounds. Tests were also performed on different environments (indoor, outdoor, inside and outside CMVs). Procedures and areas of examinations were followed according to the “ELD Test Plan and Procedures” version 1.0 document released by FMCSA on April 25th 2016. The Requirement Traceability Matrix (RTM) was used and fully verified to ensure ELD compliance. Corrective actions and regression tests were made on all Failed test results. |
