Products with ELD "TM0002"
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.
TM-ELD - Self Revoked as of 1580151210
| Vendor | Device Name | Model Number | Approved Version |
|---|---|---|---|
| | TM-ELD | TM-200 | 2.2.50 |
Data Transfer and Reporting Procedures
>Malfunctions and Testing
TM-ELD provides an easy way for authorized officers to inspect driver’s logs. After logging in to TM-ELD following the steps described in TM-ELD User Manual, a driver must tap on DOT Inspection Mode in the bottom of the main screen. TM-ELD supports three different ways to provide driver’s logs to DOT inspector: 1. Direct inspection • In order to let an authorized officer inspect a driver’s logs directly from mobile device, a driver has to tap Begin button. • Driver’s logs will appear on the screen in the standard daily log format. Driver needs to hand the authorized officer his/her mobile device. • An authorized officer can use the arrows to navigate days. • Driver must tap on the back arrow to exit DOT Inspection Mode. 2. E-mail driver’s logs • In this case driver needs to tap on Send logs button. • On the screen opened driver chooses Via E-mail and tap on Send button. • Before sending, driver can also add a comment. • Driver must tap on the back arrow to exit DOT Inspection Mode. 3. Send driver’s logs via Webservice • In this case driver needs to tap on Send logs button. • On the screen opened driver chooses Via Webservice and tap on Send button. • Before sending, driver can also add a comment. • Driver must tap on the back arrow to exit DOT Inspection Mode.Certification Statement
P Power compliance malfunction E Engine syncronization compliance malfunction T Timing compliance malfunction L Positioning compliance malfunction R Data record compliance malfunction S Data transfer compliance malfunction O Other ELD detected malfunction 1 Power data diagnostic error 2 Engine syncronization data diagnostic error 3 Missing required data elements data diagnostic error 4 Data transfer data diagnostic error 5 Unidentified driving records data diagnostic error 6 Other ELD identified diagnostic error ELD malfunctions and data diagnostic events (§ 395.34) (a) Recordkeeping during ELD malfunctions. In case of an ELD malfunction, a driver must do the following: - Note the malfunction of the ELD and provide written notice of the malfunction to the motor carrier within 24 hours; - Reconstruct the record of duty status for the current 24-hour period and the previous 7 consecutive days, and record the records of duty status on graph-grid paper logs that comply with § 395.8, unless the driver already possesses the records or the records are retrievable from the ELD; and - Continue to manually prepare a record of duty status in accordance with § 395.8 until the ELD is serviced and brought back into compliance with this subpart. (b) Inspections during malfunctions. When a driver is inspected for hours of service compliance during an ELD malfunction, the driver must provide the authorized safety official the driver's records of duty status manually kept as specified under paragraphs (a)(2) and (3) of this section. (c) Driver requirements during ELD data diagnostic events. If an ELD indicates that there is a data inconsistency that generates a data diagnostic event, the driver must follow the motor carrier's and ELD provider's recommendations in resolving the data inconsistency. (d) Motor carrier requirements: - Provide drivers with an instruction sheet describing the various ELD malfunction events and recordkeeping procedures (§395.22) - Provide drivers with a supply of 8 days’ worth of blank paper driver records (§395.22) - Repair, replace, or service (395.34)
User Manual: 
TM-ELD User Manual.pdf