Products with ELD "SOAR12"
- mySOAR-by-SOAR-Solutions Version 4.8 and higher
- mySOAR-by-SOAR-Solutions Version 5.0 and higher
- mySOAR-by-SOAR-Solutions Version 5.0 and higher
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.
mySOAR by SOAR Solutions
Vendor | Device Name | Model Number | Approved Version |
---|---|---|---|
SOAR Solutions, Inc. | mySOAR by SOAR Solutions | Android & GNX-6P and above | 4.8 and higher |
Data Transfer and Reporting Procedures
The mySOAR ELD provides a simple way to initiate an electronic data transfer to authorized safety officials as requested during a roadside inspection. The driver has an option to send the logs to FMCSA via email or web services from the application. Below are the step by step instructions: • Go to the eLog History page either by clicking on compliance section and swiping left or via the more section in the app. • Select the three vertical dot icon in the top right corner of the eLog History page. • Tap the ELD Output button. • Follow the instructions in the pop-up that appears to initiate the ELD file transfer. The driver can choose to send via data transfer (web service) or via email. A comment is required for email transfers. • Once the file transfer completes, a verification pop-up will appear. If there is an issue sending the file a pop-up will appear to alert the driver.Malfunctions and Testing
The mySOAR ELD monitors compliance for various malfunctions and displays a circle shaped icon with the letter M when a malfunction is detected on the driver’s eLog page. The icon clears when the malfunction clears. The detection and clear are both logged as events in the ELD. The mySOAR ELD supports the following malfunctions: • Power Compliance Malfunction – Occurs when the mobile device with the app or the ELD are unable retain sufficient power. It is the responsibility of the motor carrier and driver to ensure that the mobile device is charged and the ELD is connected to the vehicle. • Engine Synchronization Compliance Malfunction – Occurs when the mobile device with the app has lost connectivity to the vehicle ECM for more than 30 minutes in a 24-hour period. As a result, data such as: on engine power on/off, vehicle movement status, odometer, miles driven, VIN, and engine hours were not accessible. • Timing Compliance Malfunction – Occurs when was a discrepancy of more than 5 minutes between the mySOAR Server timestamp and the mobile device. • Positioning Compliance Malfunction – Occurs when the GPS signal is lost and the ELD is not been able to retrieve a valid location within 5 miles of the last location and more than 60 minutes has lapsed in a 24-hour period. • Data Recording Compliance Malfunction - Occurs when the mobile device or the ELD is unable to store data. • Data Transfer Compliance Malfunction – Occurs when the ELD has been unable to transfer required information to FMCSA servers for an extended period of time.Certification Statement
The SOAR Solutions mySOAR Android application and the hardware unit (GNX-6P) combined solution was certified and tested in accordance with testing procedures to be compliant with FMSCA regulation 49 CFR part 395, subpart B, appendix A; which describes the functional requirements for ELD solutions. The mySOAR app was installed on various types and sizes of Android phones and tablets. Extensive field testing was performed, to ensure compliance with the ELD and Hours of Service rules and regulations.
mySOAR by SOAR Solutions
Vendor | Device Name | Model Number | Approved Version |
---|---|---|---|
SOAR Solutions, Inc. | mySOAR by SOAR Solutions | Android & GNX-6P and above | 5.0 and higher |
Data Transfer and Reporting Procedures
>Malfunctions and Testing
The mySOAR ELD provides a simple way to initiate an electronic data transfer to authorized safety officials as requested during a roadside inspection. The driver has an option to send the logs to FMCSA via email or web services from the application. Below are the step by step instructions: • Go to the eLog History page either by clicking on compliance section and swiping left or via the more section in the app. • Select the three vertical dot icon in the top right corner of the eLog History page. • Tap the ELD Output button. • Follow the instructions in the pop-up that appears to initiate the ELD file transfer. The driver can choose to send via data transfer (web service) or via email. A comment is required for email transfers. • Once the file transfer completes, a verification pop-up will appear. If there is an issue sending the file a pop-up will appear to alert the driver.Certification Statement
The mySOAR ELD monitors compliance for various malfunctions and displays a circle shaped icon with the letter M when a malfunction is detected on the driver’s eLog page. The icon clears when the malfunction clears. The detection and clear are both logged as events in the ELD. The mySOAR ELD supports the following malfunctions: • Power Compliance Malfunction – Occurs when the mobile device with the app or the ELD are unable retain sufficient power. It is the responsibility of the motor carrier and driver to ensure that the mobile device is charged and the ELD is connected to the vehicle. • Engine Synchronization Compliance Malfunction – Occurs when the mobile device with the app has lost connectivity to the vehicle ECM for more than 30 minutes in a 24-hour period. As a result, data such as: on engine power on/off, vehicle movement status, odometer, miles driven, VIN, and engine hours were not accessible. • Timing Compliance Malfunction – Occurs when was a discrepancy of more than 5 minutes between the mySOAR Server timestamp and the mobile device. • Positioning Compliance Malfunction – Occurs when the GPS signal is lost and the ELD is not been able to retrieve a valid location within 5 miles of the last location and more than 60 minutes has lapsed in a 24-hour period. • Data Recording Compliance Malfunction - Occurs when the mobile device or the ELD is unable to store data. • Data Transfer Compliance Malfunction – Occurs when the ELD has been unable to transfer required information to FMCSA servers for an extended period of time.
mySOAR by SOAR Solutions
Vendor | Device Name | Model Number | Approved Version |
---|---|---|---|
SOAR Solutions, Inc. | mySOAR by SOAR Solutions | Android & PT40 | 5.0 and higher |
Data Transfer and Reporting Procedures
> Telematic (Web Service, Email)Malfunctions and Testing
The mySOAR ELD provides a simple way to initiate an electronic data transfer to authorized safety officials as requested during a roadside inspection. The driver has an option to send the logs to FMCSA via email or web services from the application. Below are the step by step instructions: • Go to the eLog History page either by clicking on compliance section and swiping left or via the more section in the app. • Select the three vertical dot icon in the top right corner of the eLog History page. • Tap the ELD Output button. • Follow the instructions in the pop-up that appears to initiate the ELD file transfer. The driver can choose to send via data transfer (web service) or via email. A comment is required for email transfers. • Once the file transfer completes, a verification pop-up will appear. If there is an issue sending the file a pop-up will appear to alert the driver.Certification Statement
The mySOAR ELD monitors compliance for various malfunctions and displays a circle shaped icon with the letter M when a malfunction is detected on the driver’s eLog page. The icon clears when the malfunction clears. The detection and clear are both logged as events in the ELD. The mySOAR ELD supports the following malfunctions: • Power Compliance Malfunction – Occurs when the mobile device with the app or the ELD are unable retain sufficient power. It is the responsibility of the motor carrier and driver to ensure that the mobile device is charged and the ELD is connected to the vehicle. • Engine Synchronization Compliance Malfunction – Occurs when the mobile device with the app has lost connectivity to the vehicle ECM for more than 30 minutes in a 24-hour period. As a result, data such as: on engine power on/off, vehicle movement status, odometer, miles driven, VIN, and engine hours were not accessible. • Timing Compliance Malfunction – Occurs when was a discrepancy of more than 5 minutes between the mySOAR Server timestamp and the mobile device. • Positioning Compliance Malfunction – Occurs when the GPS signal is lost and the ELD is not been able to retrieve a valid location within 5 miles of the last location and more than 60 minutes has lapsed in a 24-hour period. • Data Recording Compliance Malfunction - Occurs when the mobile device or the ELD is unable to store data. • Data Transfer Compliance Malfunction – Occurs when the ELD has been unable to transfer required information to FMCSA servers for an extended period of time.