Products with ELD "RDLG01"
Below you will find a list of products with the ELD "RDLG01" obtained from our database, including their available manuals, documentation, and images.
Click the corresponding vendor name to obtain additional information on the manufacturer, as well as contact information for further troubleshooting.
VDO RoadLog ELD - Self Revoked as of 1598879704
| Vendor | Device Name | Model Number | Approved Version |
|---|---|---|---|
| | VDO RoadLog ELD | 3290 | 12.01.00 and above |
Data Transfer and Reporting Procedures
>Malfunctions and Testing
VDO RoadLog ELD provides an instant printout as a means of data transfer to the Enforcement. Furthermore Bluetooth and USB (optionally web services and e-mail) can be supported contingent upon FMCSA’s readiness with such infrastructure. Table of Content 1 USB Roadside Inspection Flow 2 Bluetooth Roadside Inspection 1 USB Roadside Inspection Flow To perform roadside inspection on RoadLog using the USB data transfer method, the enforcement officer needs to provide to the user of the RoadLog a USB device with the following characteristics: - Mass storage device (class 08) - File system : FAT 32 - A text file used for authentication, as described in section in section 4.10.1.3 Data Transfer via USB 2.0 from the ELD rule. The roadside inspection using the USB data transfer method can be trigged in 2 ways: - By inserting the US Enforcement USB flash drive in the USB port - By selecting [USB Transfer] option from the HOS Logs Roadside Inspection screen US HOS version - In both situations, in the HOS Logs Roadside Inspection screen, the user needs to select the driver for whom the roadside inspection is performed. If the roadside inspection was triggered by selection [USB Transfer] option in the HOS Logs Roadside Inspection screen and no USB was inserted at that moment, RoadLog device will prompt the user to insert the USB. After the enforcement USB drive is inserted and authenticated, RoadLog will allow the user to insert the output comment for the ELD data output file that is generated, if required: When the user is ready to transfer the data he will select [Continue] option. While the transfer of data is in progress, the RoadLog will display Transfer in Progress screen. When the transfer is completed, RoadLog will notify the user by displaying the Transfer Completed notification bar. 2 Bluetooth Roadside Inspection To initiate the roadside inspection via BT, the user has to select [Bluetooth Transfer] option in HOS Logs Roadside Inspection screen. When this is selected, RoadLog device will become discoverable and will be able to initiate the communication with a remote enforcement BT device. The name of the RoadLog visible on the enforcement’s BT device will be RoadLog followed by the Vehicle Number. The enforcement officer needs to select the RoadLog device to enable the transfer of data. After the RoadLog is selected, the device will generate the pairing key and display it on the screen. The enforcement BT device shall use the pairing key generated by RoadLog to enable the connection. After the BT connection is established, RoadLog will allow the user to insert the output comment for the ELD data output file that is generated, if required. When the user is ready to transfer the data he will select [Continue] option. While the transfer of data is in progress, the RoadLog will display Transfer in Progress screen. When the transfer is completed, RoadLog will notify the user by displaying the Transfer Completed notification bar. 3 Printout To initiate the roadside inspection via printout, the user has to select [Print] option in HOS Logs Roadside Inspection screen, after selecting the driver for whom the inspection shall be performed. When Print option is selected, RoadLog will prompt the user to select the number of days that need to be printed in the Log Printout Options screen. After selecting [Print] in the screen, RoadLog will generated the printout while displaying Printing in Progress screen.Certification Statement
The list of malfunctions include, but it is not limited to the following: Power Compliance Malfunction PWRFail Engine Synchronization Compliance Malfunction ECMFail Timing compliance malfunction TimeFail Positioning compliance malfunction PositionFail Data recording compliance malfunction RECFail Other ELD detected malfunction MEMFail Data transfer malfunction for the USB interface USBFail Data transfer malfunction for the Bluetooth interface BTError Power data diagnostic event PowerError Engine synchronization data diagnostic ECMError Missing required data elements data diagnostic ElemError Data transfer data diagnostic event for the USB interface USBError Data transfer data diagnostic event for the Bluetooth interface BTError Unidentified driving records data diagnostic event UDAError USB Communication Error self diagnostic EXTERR USB unknown file system self diagnostic FATERR USB unknown class self diagnostic CLSERR