FMCSA - Federal Motor Carrier Safety Adminstration

Revoked ELDs

These devices were found by FMCSA to not meet the Electronic Logging Device technical specifications.

Device Name Model Number Software Version ELD Identifier Image User Manual Company Phone Email Company Website Address Data Transfer Methods ELD Malfunctions Certifying Statement
ZED ELD (Self-Revoked) IOT-02, IOT-03 3.8 ZEDELD Download Download Zed Connect Inc. (888) 315-9788 support@zed-eld.com https://zed-eld.com/ 23975 Park Sorrento Suite 100, Calabasas, CA 91302 In order to access the 8 Day DOT roadside inspection report, the driver must be logged in to the ZED application on the mobile device. To access the DOT Report, tap “History” tab along the bottom of the application screen. The “History” screen is also where the driver can edit and certify their logs. NOTE: Days with a “!” symbol beside the date are uncertified. NOTE: If a log is edited it must be recertified. Tap “RODS Report” in the upper left of the screen to view the RODS report within the device. A Driver then provides the DOT Report to a DOT Officer by tapping “Export” in the upper right of the application. A pop-up box appears, prompting the user to select the export method. The Export Options are: 1. PDF file that can be viewed on the device screen, printed (a wireless printer is needed), or e-mailed. 2. DOT Data File Transfer to FMCSA. Option 2 would take the user to a page to input the officer's PIN as output file comment, and complete the transfer via web upload or encrypted email. Note 1: There is an optional feature that allows e-mailing a PDF copy of the file to a user-specified e-mail address. This an optional feature and is not a FMCSA requirement and does not qualify as electronic data file submission. Note 2: The mobile device must be connected to the internet for electronic file submission. Summary of Implemented Malfunctions: 1) Power Compliance Malfunction: If the adapter is not powered on for an accumulated 30 minutes over a 24 hour period while the vehicle is in motion, then a power compliance malfunction is triggered. Once triggered, the system notifies both the driver and the motor carrier of the incident. 2) Engine Synchronization Compliance Malfunction: If the adapter portion of the ELD fails to retrieve any of the required ECM data within 5 seconds or the mobile device portion of the ELD fails to retrieve any of the required values within 5 seconds and the failure to retrieve the values in a timely manner fail for more than 30 minutes during a 24 hour period aggregated across all driver profiles, then an engine synchronization compliance malfunction is triggered. Once triggered, the system notifies both the driver and the motor carrier of the incident. 3) Timing Compliance Malfunction: the ELD cross-checks the time with the external GPS generated UTC source on the adapter. If there is a discrepancy, a timing compliance malfunction is generated. Once triggered, the system notifies both the driver and the motor carrier of the incident. 4) Positioning Compliance Malfunction: the ELD checks the positioning of the vehicle once every 5 miles, when an accumulated 60 minutes of invalid positioning has been logged over a 24 hour period, a positioning compliance malfunction is recorded. Once triggered, the system notifies both the driver and the motor carrier of the incident. 5) Data Recording Malfunction: the storage of the device is checked every time a new record is logged. If the device is running out of memory, the user will be warned. If the device runs out of memory and can no longer store new records, a data recording malfunction will be recorded. Once triggered, the system notifies both the driver and the motor carrier of the incident. ZED Connect retained a third-party consultant, who is a former state highway patrol officer, former FMCSA investigator, and industry-known subject matter expert, to conduct a comprehensive review of the ZED ELD solution. Intensive internal testing and field testing was conducted and feedback was incorporated into the product functionality requirements. All identified required changes were implemented. The ELD compliance test procedure was used to validate conformity to each of the technical specifications in the ELD ruleset.
ONE20 F-ELD for Android (Self-Revoked) PT30 1.1 or higher ONE20A Download Download ONE20, Inc. 1-888-986-6320 f-eld@one20.com www.ONE20.com 1300 Oakside Circle, Chanhassen MN 55317 ONE20’s F-ELD solution supports two methods of data transfer: Email and Web Services. Email: To send your logs via email, tap the Roadside icon at the bottom of the screen. The Roadside Inspection screen displays. In the Roadside Inspection screen, tap the Send button. You will be prompted to enter an optional Output File Comment. Enter this if directed by the roadside official, otherwise leave it blank and tap Next. Upon tapping Next, you will be prompted by which method you wish to transfer your logs: Email or Web Services. Tap on Email. Tap on “FMCSA LOGS”, not CSV. Available apps display. Note that depending on what apps you have installed on your device, you may see different sharing apps in this screen. Using your preferred Email method, send the automatically-attached CSV file. Web Services: To send your logs via Web Services, tap the Roadside icon at the bottom of the screen. The Roadside Inspection screen displays. In the Roadside Inspection screen, tap the Send button. You will be prompted to enter an optional Output File Comment. Enter this if directed by the roadside official, otherwise leave it blank and tap Next. Upon tapping Next, you will be prompted by which method you wish to transfer your logs: Email or Web Services. Tap on Web Services. Confirm the transfer by tapping Send Now. An XML file of your log will be transferred to the FMCSA for the roadside official to access and review. ONE20 F-ELD monitors, detects, and supports all standard required ELD system malfunctions and data diagnostics, including: - Power compliance malfunction - Engine synchronization compliance malfunction - Timing compliance malfunction - Positioning compliance malfunction - Data transfer compliance malfunction - Power data diagnostic event - Engine synchronization data diagnostic event - Missing required data elements data diagnostic event - Data transfer data diagnostic event - Unidentified Driving records data diagnostic event The ONE20 F-ELD has been tested against the FMCSA-provided Test Plan in the appendix to Subpart B of Part 395 of Title 49, Code of Federal Regulations. With the exception of the Web Service transfer tests, all in-truck and scripted tests that were included in the FMCSA Test Plan were executed and passed. The in-truck tests from the FMCSA Test Plan were executed by professional drivers in over twelve trucks over the past several months. The scripted tests from the FMCSA Test Plan were executed independently by ONE20 staff and third-party auditors. Two vehicles were used for testing. The first was a 2011 Roadmaster RV with a J1939 engine bus; the second was a 2005 Peterbilt 379 with a J1708 engine bus. Prior to these tests, months of simulated tests were performed on the PT30 Truck Adapter hardware device internally by ONE20 and externally at the device’s manufacturing facility.
ONE20 F-ELD for iOS (Self-Revoked) PT30 1.1 or higher ONE20I Download Download ONE20, Inc. 1-888-986-6320 f-eld@one20.com www.ONE20.com 1300 Oakside Circle, Chanhassen MN 55317 ONE20’s F-ELD solution supports two methods of data transfer: Email and Web Services. Email: To send your logs via email, tap the Roadside icon at the bottom of the screen. The Roadside Inspection screen displays. In the Roadside Inspection screen, tap the Send button. You will be prompted to enter an optional Output File Comment. Enter this if directed by the roadside official, otherwise leave it blank and tap Next. Upon tapping Next, you will be prompted by which method you wish to transfer your logs: Email or Web Services. Tap on Email. Tap on “FMCSA LOGS”, not CSV. Available apps display. Note that depending on what apps you have installed on your device, you may see different sharing apps in this screen. Using your preferred Email method, send the automatically-attached CSV file. Web Services: To send your logs via Web Services, tap the Roadside icon at the bottom of the screen. The Roadside Inspection screen displays. In the Roadside Inspection screen, tap the Send button. You will be prompted to enter an optional Output File Comment. Enter this if directed by the roadside official, otherwise leave it blank and tap Next. Upon tapping Next, you will be prompted by which method you wish to transfer your logs: Email or Web Services. Tap on Web Services. Confirm the transfer by tapping Send Now. An XML file of your log will be transferred to the FMCSA for the roadside official to access and review. ONE20 F-ELD monitors, detects, and supports all standard required ELD system malfunctions and data diagnostics, including: - Engine synchronization compliance malfunction - Timing compliance malfunction - Positioning compliance malfunction - Data transfer compliance malfunction - Power data diagnostic event - Engine synchronization data diagnostic event - Missing required data elements data diagnostic event - Data transfer data diagnostic event - Unidentified Driving records data diagnostic event The ONE20 F-ELD has been tested against the FMCSA-provided Test Plan in the appendix to Subpart B of Part 395 of Title 49, Code of Federal Regulations. With the exception of the Web Service transfer tests, all in-truck and scripted tests that were included in the FMCSA Test Plan were executed and passed. The in-truck tests from the FMCSA Test Plan were executed by professional drivers in over twelve trucks over the past several months. The scripted tests from the FMCSA Test Plan were executed independently by ONE20 staff and third-party auditors. Two vehicles were used for testing. The first was a 2011 Roadmaster RV with a J1939 engine bus; the second was a 2005 Peterbilt 379 with a J1708 engine bus. Prior to these tests, months of simulated tests were performed on the PT30 Truck Adapter hardware device internally by ONE20 and externally at the device’s manufacturing facility.