| Electronic Logging Device | Roadside Systems Roadside ELD |
| Model Number | RSELD |
| ELD ID Number | WLI001 |
| Software Version | 3.0.6 |
Model Information
| Data Transfer Methods | There is a one page document describing how the officer can enter “officer mode” by clicking on the icon on the top right “officer icon” present on all screens. Once in “officer mode” the Daily Header and Full Day ELD Record defined by the FMCSA are displayed. On the bottom of the page there is a button marked “send report.” Clicking this button brings up the window to email the report to any email address entered. The Web Services method is complete and functional. If there is an error, we will see a response similar to: {"Status":"Error","Errors":[" The submitted ELD file is blank and does not contain any usable information. Please check to make sure you have submitted the correct file. "]} If there is a success, we receive a message stating that the file was sent successfully: {"Status":"Information","Errors":["File Received"]} |
| Malfunction Notes | Each malfunction has been coded following the "Standard Coding for Required Compliance Malfunction and Data Diagnostic Event Detection" definitions regarding "Malfunction/Diagnostic Code", "Malfunction Description" and "Data Diagnostic Event." Power Compliance monitoring assures that the ELD will become fully functional within one minute of the engine on event and remain on as long as the vehicle's engine stays powered. Engine Synchronization monitoring determines our connection to the ECM. This alerts the driver if there is a loss of connectivity to the ECM. For Timing Compliance Monitoring, we periodically check UTC time via the internet. For Positioning Compliance the ELD records the location, and uses the last valid position measurement and includes the latitude and longitude coordinates and distance traveled in miles, since the last valid position measurement. We also measure the elapsed time during periods when the ELD does not require a valid position measurement within 5 miles. If the time exceeds 60 minutes in a 24 hour period, it is marked as a positioning compliance malfunction. An ELD monitors its storage capacity and integrity and detects data recording compliance malfunction if it can no longer record or retain required events or retrieve recorded logs that are not otherwise catalogued remotely by the motor carrier. The ELD monitors the completeness of the ELD event record information in relation to the required data elements for each event type and records a missing data elements data diagnostics event for the driver if any required field is missing at the time of recording. We check to make sure that our data transfer mechanism works properly at least once every 7 days. All Data Diagnostic events are handled similarly according to the mandate. |
| Certifying Statement | The Roadside ELD was certified by executing and successfully passing the FMCSA ELD Compliance Testing Procedures and ELD Output File Validation. The Roadside ELD runs on Android tablets and phones with Android 4.4 and higher. The system is routinely retested to insure that it continues to comply with all FMCSA regulations. The Roadside ELD has been tested on simulators as well as connected to vehicle engines. |
Company Information
| Manufacturer | Roadside Systems |
| Website | roadsidesystems.com |
| Contact Email | [email protected] |
| Contact Phone Number | 314-304-7000 |
| Address | 2601 S Big Bend Blvd, Saint Louis, MO 63143 |
Devices From Roadside Systems
| Device | ID |
|---|---|
| Roadside Systems Roadside ELD | WLI001 |
Related ELDs
| ELD | ELD ID |
|---|---|
| Navistar, Inc. OnCommand(R) Connection Electronic Driver Log | OCC001 |
| HCSS HCSSELD | GEO84A |
| GPS Trackit ELD Fleet | ELDFLT |
| AAMP Global (Formerly M2M In Motion) M2MIM ELD | M2M018 |
| GPS Trackit ELD Fleet | ELDFLT |
| InTouch InTouch ELD - Android | ITELD1 |
| Satinder Singh Keep Truckin | KTIELD |