Products with ELD "HXE360"
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.
Hyper ELD
| Vendor | Device Name | Model Number | Approved Version |
|---|---|---|---|
| | Hyper ELD | HX+ | 4.4.1 |
Data Transfer and Reporting Procedures
> Telematic (Web Service, Email)Malfunctions and Testing
Hyper X ELD uses Telematics as the primary method for data transfer. To initiate this process, the driver should open the sidebar in the Driver Application and select the 'Inspection' option under the ELD component. Afterward, the driver must click the "Send Logs" button to submit via web services or the “Email Logs” button to submit via Email, either which will lead to a page requesting a comment. This page will also include a final confirmation button. When pressed, this will send the logs, along with the comment, to the FMCSA via a web service.Certification Statement
When a malfunction or diagnostic issue is detected, a visual alert appears on the Status page of the Driver Application. The malfunctions that are monitored, logged, and transmitted during inspections include power compliance malfunctions, which occur when the total engine hour difference between recorded events exceeds 30 minutes in a single day. Power data diagnostic events are triggered when the engine hour difference between the last recorded event with engine hours and the vehicle's last known engine hours on that day is 0.1 hours or greater. Timing compliance malfunctions happen if the Driver Application Device’s time is off by more than 10 minutes compared to the time on the device that originated the event when an event is received. Positioning compliance malfunctions occur while driving if no location information is received by the Driver Application within 5 seconds after every hour of driving. Data recording compliance malfunctions happen when a write to the local database on the Driver Application Device fails for any reason. Missing required data elements diagnostic events are triggered when an automatic event is received by the Driver Application with missing required fields. Lastly, unidentified driving records diagnostic events occur when more than 30 minutes of unidentified driving time for the vehicle is logged over a 24-hour period.
User Manual: 
ELD manual.pdf