Products with ELD "ZEDELD"
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.
ZED ELD - Self Revoked as of 0
Vendor | Device Name | Model Number | Approved Version |
---|---|---|---|
Zed Connect Inc. | ZED ELD | IOT-02, IOT-03 | 3.8 |
Data Transfer and Reporting Procedures
>Malfunctions and Testing
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.Certification Statement
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.