| Electronic Logging Device | ELD365 ELD365 |
| Model Number | ELD386 |
| ELD ID Number | ATS001 |
| Software Version | 2.1.399 |
Model Information
| Data Transfer Methods | 1. Open the app 2. Click on View Logs 3. Click on Email Logs 4. Click send Logs (this page will both email logs and send them through the web service) |
| Malfunction Notes | In addition to the malfunction and diagnostic event handling required by the ELD regulation, including all malfunction and data diagnostic events listed in table 4 of the FMCSA ELD Final Rule, we also alert the user when the vehicle is in motion and there is no identified driver, as well as instances where the driver’s business records indicate that he or she is not in the correct vehicle. P - "Power compliance" malfunction E - "Engine synchronization compliance" malfunction T - "Timing compliance" malfunction L - "Positioning compliance" malfunction R - "Data recording compliance" malfunction S - "Data transfer compliance" malfunction O - "Other" ELD detected malfunction 1 - "Power data diagnostic" event 2 - "Engine synchronization data diagnostic" event 3 - "Missing required data elements data diagnostic" event 4 - "Data transfer data diagnostic" event 5 - "Unidentified driving records data diagnostic" event 6 - "Other" ELD identified diagnostic event |
| Certifying Statement | A team of 11 developers and QA testers have performed unit and functional tests of the ELD across multiple version of Android software and hardware, using both simulators and actual vehicles to generate data. The Project Manager and Test Team Leader worked through the Requirements Traceability Matrix to create tasks for the developers to ensure every requirement was met in the ELD. As we came across any item we did not have available, we generated a project plan for that particular item and assigned it to a developer for completion. Once the item was complete, we released it to the testing team for testing. All of our testing is manual and done from the user’s point of view. We do not use any type of automated testing. For failed tests, the tester emails the result to the Test Team Leader. The developer assigned to the particular task fixes the error and completes the corrective action process. Once the corrective action process is complete, the new code is released and turned back over to the tester for regression testing. |
Company Information
| Manufacturer | ELD365 |
| Website | http://www.eld365.com |
| Contact Email | [email protected] |
| Contact Phone Number | 888-858-1928 |
| Address | 19083 COLIMA ROAD, ROWLAND HEIGHTS, CA 91748 |
Devices From ELD365
| Device | ID |
|---|---|
| ELD365 ELD365 | ATS001 |
| ELD365 ELD365 ELOG | ELD365 |
Related ELDs
| ELD | ELD ID |
|---|---|
| Zonar Zonar Logs | ZONAR1 |
| Nonda ZUS Smart Vehicle Health Monitor | ZUSOBD |
| Darex Logistics Company ZELD | AT3103 |
| Nonda ZUS Smart Vehicle Health Monitor Pro Edition | OBDPRO |
| Beacon Innovations Group Inc. ZoomLog | ZML001 |
| Gorilla Fleet Safety, LLC Webfleet - Android and PT30 | WFAND3 |
| Velocitor Solutions V-Track | VSIOS1 |