Products with ELD "IELD01"
Below you will find a list of products with the ELD "" obtained from our database, including their available manuals, documentation, and images.
Click the corresponding vendor name to obtain additional information on the manufactorer, as well as contact information for further troubleshooting.
Isotrak ELD
| Vendor | Device Name | Model Number | Approved Version |
|---|---|---|---|
| | Isotrak ELD | CalAmp LMU-3640 | 196 |
Data Transfer and Reporting Procedures
The Isotrak ELD application provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. This can be done by selecting the Green “officer” Icon roadside Inspection button from the main HOS dashboard at the bottom. A list of supported data transfer options is displayed which include Bluetooth, Email, USB2, and FMCSA Web service. To submit the Output File to an authorized safety official, the driver selects the “Export ELD Data File” from the DOT Inspection screen top right. The driver then will select one of the following methods: •Agent External Storage: The ELD device will first verify the external USB2 storage device is present & 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 a 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 the FMCSA's endpoint and obtains submission ID. A space is provided for comments to be included. Press “Export” to submit. • Email: Tap on the email option, enter the destination email address and add any comments to be included and press “Export” to send.Malfunctions and Testing
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 P3TS 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)Certification Statement
The Isotrak ELD 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.
User Manual: 
Apollo ELD user guide v4.1 - English.pdf
Isotrak ELD
| Vendor | Device Name | Model Number | Approved Version |
|---|---|---|---|
| | Isotrak ELD | ISO100 | 196 |
Data Transfer and Reporting Procedures
>Malfunctions and Testing
The Isotrak ELD application provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. This can be done by selecting the Green “officer” Icon roadside Inspection button from the main HOS dashboard at the bottom. A list of supported data transfer options is displayed which include Bluetooth, Email, USB2, and FMCSA Web service. To submit the Output File to an authorized safety official, the driver selects the “Export ELD Data File” from the DOT Inspection screen top right. The driver then will select one of the following methods: •Agent External Storage: The ELD device will first verify the external USB2 storage device is present & 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 a 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 the FMCSA's endpoint and obtains submission ID. A space is provided for comments to be included. Press “Export” to submit. • Email: Tap on the email option, enter the destination email address and add any comments to be included and press “Export” to send.Certification Statement
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 P3TS 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)
User Manual: Apollo ELD user guide v4.1 - English.pdf