| Electronic Logging Device | Rigbot LLC Rigbot |
| Model Number | RBV002 |
| ELD ID Number | RBELD2 |
| Software Version | 11.0.22 and Newer |
Model Information
| Data Transfer Methods | Rigbot data transfer happens through Option1 specified by FMCSA via internet by email and data transfer to FMCSA Web services. Following is the step-by-step instructions for the driver to produce and transfer the ELD records to an authorized safety official: - 'DOT Inspection Mode' can be accessed by by tapping the main menu on top left corner of the screen - Device can be physically removed from the cradle and handed to the official with the DOT Inspection Mode screen for the officer to review on screen - As instructed by the official, 'Transfer' button can be clicked to transfer the ELD records electronically to the official - 'Transfer' button will open a window with options to either a) email or to b) transfer to FMCSA Web services - Tapping one of the two options will trigger automatic transfer of the ELD records to the authorized safety official - Above step will generate an acknowledgement indicating that the information has been sent via email per the selected option |
| Malfunction Notes | - Two LED lights will indicate any ELD malfunctions - Green LED light if not solid, suggests loss of power to the ELD, Orange light if not solid, loss of internet connectivity - In addition, driver receives an alert on the screen header - Following malfunctions with the ELD will be indicated with a ‘stop’ icon in the alert center and will require the driver to start using paper logs • P : Power Compliance malfunction • E : Engine Synchronization compliance malfunction • T : Timing Compliance malfunction • L : Positioning Compliance • R : Data recording Compliance malfunction • S : Data transfer Compliance malfunction • O : Other ELD detected malfunction - Following diagnostic codes will show in the Alert Center along with time stamp. Continued accumulation of such events will lead to the compliance malfunctions listed above • 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 | - The Rigbot ELD system was tested successfully with the test procedures described by FMCSA in the ELD Test Plan Procedures guide. - The Mobile ELD device that can be used by drivers for recording their activities compliant with the FMCSA Hours of Service rules was tested on different Android versions and in different screen sizes and form factors. - The truck’s Engine Control Unit activity interaction with the Rigbot ELD device was tested using both simulated Virtual Truck Device (AU Group Electronics - SAE J1939 Gen II) and using actual trucks following J1939 and J1708 protocols with Cummins ISX diesel engines. - A web portal to help the motor carrier(dispatch manager) to keep track of their drivers’ activities, daily records and their trucks was also against the relevant FMCSA ELD test plan procedures. |
Company Information
| Manufacturer | Rigbot LLC |
| Website | http://www.rigbot.com |
| Contact Email | [email protected] |
| Contact Phone Number | 1844 474 4268 |
| Address | 316, W Washington Avenue, Suite 675, Madison WI 53703 |
Devices From Rigbot LLC
| Device | ID |
|---|---|
| Rigbot LLC Rigbot | RBELD2 |
| Rigbot LLC Rigbot | RBELD1 |
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 |