Products with ELD "APOLLO"
- Apollo-ELD-(at.eDash) Version 185 or higher
- Apollo-ELD-(at.eDash) Version 192 or higher
- Apollo-ELD-(at.eDash) Version 195 or higher
- Apollo-ELD-(at.eDash) Version 200 or higher
- Apollo-ELD-(at.eDash) Version 203 or higher
- Apollo-ELD-(at.eDash) Version 210 or higher
- Apollo-ELD-(at.eDash) Version 215 or higher
- Apollo-ELD-(at.eDash) Version 215-Android 198-iOS
- Apollo-ELD-(at.eDash) Version 235-Android 198-iOS
- Apollo-ELD-(at.eDash) Version 252-Android 240-iOS
- Apollo-ELD-(at.eDash) Version 254-Android 240-iOS
- Apollo-ELD-(at.eDash) Version 4.05-And/4.05-iOS
- Apollo-ELD-(at.eDash) Version And4.05.008/iOS4.05
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.
Apollo ELD (at.eDash)
| Vendor | Device Name | Model Number | Approved Version |
|---|---|---|---|
| | Apollo ELD (at.eDash) | Apollo | 185 or higher |
Data Transfer and Reporting Procedures
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: - Email Transfer: An email will be preformatted with the .AES file attached to it. The destination email address will the one provided during this registration process - USB Transfer: The ELD will wait for the driver or safety official to connect the external storage device and will automatically enter Mass Storage mode. After the external storage device is detected, the driver will be prompted to re-authenticate before the transfer of the output data file is started - 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.Malfunctions and Testing
Low battery, network disconnection, low internal memory space, ECM data transfer failure, location sensor failure.Certification Statement
The Apollo 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: 
HOSappUserGuideV167R.pdf
Apollo ELD (at.eDash)
| Vendor | Device Name | Model Number | Approved Version |
|---|---|---|---|
| | Apollo ELD (at.eDash) | Apollo | 192 or higher |
Data Transfer and Reporting Procedures
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: - Email Transfer: An email will be preformatted with the .AES file attached to it. The destination email address will the one provided during this registration process - USB Transfer: The ELD will wait for the driver or safety official to connect the external storage device and will automatically enter Mass Storage mode. After the external storage device is detected, the driver will be prompted to re-authenticate before the transfer of the output data file is started - 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.Malfunctions and Testing
Low battery, network disconnection, low internal memory space, ECM data transfer failure, location sensor failure.Certification Statement
The Apollo 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: HOSappUserGuideV167R.pdf
Apollo ELD (at.eDash)
| Vendor | Device Name | Model Number | Approved Version |
|---|---|---|---|
| | Apollo ELD (at.eDash) | Apollo | 195 or higher |
Data Transfer and Reporting Procedures
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: - Email Transfer: An email will be preformatted with the .AES file attached to it. The destination email address will the one provided during this registration process - USB Transfer: The ELD will wait for the driver or safety official to connect the external storage device and will automatically enter Mass Storage mode. After the external storage device is detected, the driver will be prompted to re-authenticate before the transfer of the output data file is started - 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.Malfunctions and Testing
Low battery, network disconnection, low internal memory space, ECM data transfer failure, location sensor failure.Certification Statement
The Apollo 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: HOSappUserGuideV167R.pdf
Apollo ELD (at.eDash)
| Vendor | Device Name | Model Number | Approved Version |
|---|---|---|---|
| | Apollo ELD (at.eDash) | Apollo | 200 or higher |
Data Transfer and Reporting Procedures
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: - Email Transfer: An email will be preformatted with the .AES file attached to it. The destination email address will the one provided during this registration process - USB Transfer: The ELD will wait for the driver or safety official to connect the external storage device and will automatically enter Mass Storage mode. After the external storage device is detected, the driver will be prompted to re-authenticate before the transfer of the output data file is started - 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.Malfunctions and Testing
Low battery, network disconnection, low internal memory space, ECM data transfer failure, location sensor failure.Certification Statement
The Apollo 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: HOSappUserGuideV167R.pdf
Apollo ELD (at.eDash)
| Vendor | Device Name | Model Number | Approved Version |
|---|---|---|---|
| | Apollo ELD (at.eDash) | Apollo | 203 or higher |
Data Transfer and Reporting Procedures
>Malfunctions and Testing
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: - Email Transfer: An email will be preformatted with the .AES file attached to it. The destination email address will the one provided during this registration process - USB Transfer: The ELD will wait for the driver or safety official to connect the external storage device and will automatically enter Mass Storage mode. After the external storage device is detected, the driver will be prompted to re-authenticate before the transfer of the output data file is started - 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.Certification Statement
Low battery, network disconnection, low internal memory space, ECM data transfer failure, location sensor failure.
User Manual: HOSappUserGuideV167R.pdf
Apollo ELD (at.eDash)
| Vendor | Device Name | Model Number | Approved Version |
|---|---|---|---|
| | Apollo ELD (at.eDash) | Apollo | 210 or higher |
Data Transfer and Reporting Procedures
> Local (USB, Bluetooth) , Telematic (Web Service, Email)Malfunctions and Testing
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: - Email Transfer: An email will be preformatted with the .AES file attached to it. The destination email address will the one provided during this registration process - USB Transfer: The ELD will wait for the driver or safety official to connect the external storage device and will automatically enter Mass Storage mode. After the external storage device is detected, the driver will be prompted to re-authenticate before the transfer of the output data file is started - 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.Certification Statement
Low battery, network disconnection, low internal memory space, ECM data transfer failure, location sensor failure.
User Manual: apolloELDDriverManual_V7r.pdf
Apollo ELD (at.eDash)
| Vendor | Device Name | Model Number | Approved Version |
|---|---|---|---|
| | Apollo ELD (at.eDash) | Apollo | 215 or higher |
Data Transfer and Reporting Procedures
> Local (USB, Bluetooth) , Telematic (Web Service, Email)Malfunctions and Testing
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: - Email Transfer: An email will be preformatted with the .AES file attached to it. The destination email address will the one provided during this registration process - USB Transfer: The ELD will wait for the driver or safety official to connect the external storage device and will automatically enter Mass Storage mode. After the external storage device is detected, the driver will be prompted to re-authenticate before the transfer of the output data file is started - 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.Certification Statement
Low battery, network disconnection, low internal memory space, ECM data transfer failure, location sensor failure.
User Manual: apolloELDDriverManual_V7r.pdf
Apollo ELD (at.eDash)
| Vendor | Device Name | Model Number | Approved Version |
|---|---|---|---|
| | Apollo ELD (at.eDash) | Apollo | 215-Android 198-iOS |
Data Transfer and Reporting Procedures
> Local (USB, Bluetooth) , Telematic (Web Service, Email)Malfunctions and Testing
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: - Email Transfer: An email will be preformatted with the .AES file attached to it. The destination email address will the one provided during this registration process - USB Transfer: The ELD will wait for the driver or safety official to connect the external storage device and will automatically enter Mass Storage mode. After the external storage device is detected, the driver will be prompted to re-authenticate before the transfer of the output data file is started - 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.Certification Statement
Low battery, network disconnection, low internal memory space, ECM data transfer failure, location sensor failure.
User Manual: apolloELDDriverManual_V7r.pdf
Apollo ELD (at.eDash)
| Vendor | Device Name | Model Number | Approved Version |
|---|---|---|---|
| | Apollo ELD (at.eDash) | Apollo | 235-Android 198-iOS |
Data Transfer and Reporting Procedures
> Local (USB, Bluetooth) , Telematic (Web Service, Email)Malfunctions and Testing
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: - Email Transfer: An email will be preformatted with the .AES file attached to it. The destination email address will the one provided during this registration process - USB Transfer: The ELD will wait for the driver or safety official to connect the external storage device and will automatically enter Mass Storage mode. After the external storage device is detected, the driver will be prompted to re-authenticate before the transfer of the output data file is started - 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.Certification Statement
Low battery, network disconnection, low internal memory space, ECM data transfer failure, location sensor failure.
User Manual: apolloELDDriverManual_V7r.pdf
Apollo ELD (at.eDash)
| Vendor | Device Name | Model Number | Approved Version |
|---|---|---|---|
| | Apollo ELD (at.eDash) | Apollo | 252-Android 240-iOS |
Data Transfer and Reporting Procedures
> Local (USB, Bluetooth) , Telematic (Web Service, Email)Malfunctions and Testing
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: - Email Transfer: An email will be preformatted with the .AES file attached to it. The destination email address will the one provided during this registration process - USB Transfer: The ELD will wait for the driver or safety official to connect the external storage device and will automatically enter Mass Storage mode. After the external storage device is detected, the driver will be prompted to re-authenticate before the transfer of the output data file is started - 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.Certification Statement
Low battery, network disconnection, low internal memory space, ECM data transfer failure, location sensor failure.
User Manual: apolloELDDriverManual_V7r.pdf
Apollo ELD (at.eDash)
| Vendor | Device Name | Model Number | Approved Version |
|---|---|---|---|
| | Apollo ELD (at.eDash) | Apollo | 254-Android 240-iOS |
Data Transfer and Reporting Procedures
> Local (USB, Bluetooth) , Telematic (Web Service, Email)Malfunctions and Testing
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: - Email Transfer: An email will be preformatted with the .AES file attached to it. The destination email address will the one provided during this registration process - USB Transfer: The ELD will wait for the driver or safety official to connect the external storage device and will automatically enter Mass Storage mode. After the external storage device is detected, the driver will be prompted to re-authenticate before the transfer of the output data file is started - 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.Certification Statement
Low battery, network disconnection, low internal memory space, ECM data transfer failure, location sensor failure.
User Manual: apolloELDDriverManual_V7r.pdf
Apollo ELD (at.eDash)
| Vendor | Device Name | Model Number | Approved Version |
|---|---|---|---|
| | Apollo ELD (at.eDash) | Apollo | 4.05-And/4.05-iOS |
Data Transfer and Reporting Procedures
> Local (USB, Bluetooth) , Telematic (Web Service, Email)Malfunctions and Testing
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: - Email Transfer: An email will be preformatted with the .AES file attached to it. The destination email address will the one provided during this registration process - USB Transfer: The ELD will wait for the driver or safety official to connect the external storage device and will automatically enter Mass Storage mode. After the external storage device is detected, the driver will be prompted to re-authenticate before the transfer of the output data file is started - 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.Certification Statement
Low battery, network disconnection, low internal memory space, ECM data transfer failure, location sensor failure.
User Manual: apolloELDDriverManual_V7r.pdf
Apollo ELD (at.eDash)
| Vendor | Device Name | Model Number | Approved Version |
|---|---|---|---|
| | Apollo ELD (at.eDash) | Apollo | And4.05.008/iOS4.05 |
Data Transfer and Reporting Procedures
> Local (USB, Bluetooth) , Telematic (Web Service, Email)Malfunctions and Testing
The driver selects the “Export ELD Data File” from the Logbook screen to submit the Output File to an authorized safety official. The driver, then, will select one of the following methods: - Email Transfer: An email will be preformatted with the AES file attached to it. The destination email address will be provided during this registration process. Webservice: After selecting this option, the driver should tap on the “FMCSA” labeled image, add a comment, and tap on the “Export” button. The FMCSA web services will return a message with the Submission ID number, Status, and Message about the transfer. - Webservice: After selecting this option, the driver should tap on the 'FMCSA' labeled image, add a comment, and tap on the 'Export' button. The FMCSA web services will return a message with the Submission ID number, Status, and Message about the transfer. - USB Transfer: The ELD will wait for the driver or safety official to connect the external storage device and automatically enter Mass Storage mode. After the external storage device is detected, the driver will be prompted to re-authenticate before the transfer of the output data file is started. - Bluetooth Transfer: After selecting this option, the authorized safety official will pair and verify the 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.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): - 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: apolloELDDriverManual_V7r.pdf