Products with ELD "RSSA01"
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.
ROAD STAR SOLUTIONS
| Vendor | Device Name | Model Number | Approved Version |
|---|---|---|---|
| | ROAD STAR SOLUTIONS | RSSE01 | RSSEA1.0 |
Data Transfer and Reporting Procedures
> Local (Bluetooth) , Telematic (Web Service)Malfunctions and Testing
TELEMATICS EMAIL: 1. Tap “Send Logs” from “Inspection Module” menu. 2. Checkbox next to each log you want to transfer. 3. Choose transfer method as “Email”. 4. Enter email address of the authorized safety official. 5. Tap “Send”. TELEMATICS WIRELESS TRANSFER: 1. Tap “Send Output File” from “Inspection Module” menu. 2. Enter the Investigation Code or News Code provided by authorized safety official. 3. Tap “Send”. *Federal Motor Carrier Safety regulation 49 CFR § 395.15 does not require a driver to provide a hard copy printout of their logs for an authorized safety official. However, you can email your logs from the ROAD STAR App if you choose to provide the authorized safety official a copy. ROAD STAR is made to transfer data wirelessly via Web Services and follows the below standards put forward by FMCSA in article 4.10.1.1. (a) Transfer of ELD data to FMCSA via Web Services must follow the following standards: (1)Web Services Description Language (WSDL) 1.1 (2)Simple Object Access Protocol (SOAP) 1.2 (incorporated by reference, see § 395.38) (3)Extensible Markup Language (XML) 1.0 5th Edition (b) If an ELD provider plans to use Web Services, upon ELD provider registration as described in section 5.1 of this appendix, (1) FMCSA will provide formatting files necessary to convert the ELD file into an XML format and upload the data to the FMCSA servers. These files include FMCSA’s Rules of Behavior, XML Schema, WSDL file, Interface Control Document (ICD), and the ELD Web Services Development Handbook, and (2)ELD Providers must obtain a Public/Private Key pair compliant with the NIST SP 800-32, Introduction to Public Key Technology and the Federal PKI Infrastructure, (incorporated by reference, see § 395.38), and submit the public key with their registration. (3)ELD Providers will be required to complete a test procedure to ensure their data is properly formatted before they can begin submitting driver’s ELD data to the FMCSA server. (c)ELD data transmission must be accomplished in a way that protects the privacy of the driver(s). (d)At roadside, if both the vehicle operator and law enforcement have an available data connection, the vehicle operator will initiate the transfer of ELD data to an authorized safety official. In some cases, an ELD may be capable of converting the ELD file to an XML format using an FMCSA-provided schema and upload it using information provided in the WSDL file using SOAP via RFC 7230, RFC 7231, and RFC 5246, Transport Layer Security (TLS) Protocol Version 1.2 (incorporated by reference, see § 395.38). Wireless Data Transfer tests will be conducted and detailed instructions will be provided upon FMCSA publishing specific test cases.Certification Statement
ROAD STAR will monitor and report malfunction data based on section 4.6 ELD’s Self-Monitoring of Required Functions table 4: 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
User Manual: 
ROAD STAR MANUAL.pdf