Products with ELD "CTELD1"
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.
Counting Trucks ELD
| Vendor | Device Name | Model Number | Approved Version |
|---|---|---|---|
| | Counting Trucks ELD | 1.0 | 1.0 |
Data Transfer and Reporting Procedures
> Telematic (Web Service, Email)Malfunctions and Testing
Counting trucks supports Telematics as the primary data transfer method. The driver should navigate to the Inspection page of the Driver Application ELD component by expanding the sidebar and selecting the 'Inspection' option. The driver should click the "Send Logs" button which will open the next page that will prompt for the Comment, this page will have the final confirmation button that if pressed will transmit the logs to FMCSA over a web service with the comment included.Certification Statement
When a malfunction/diagnostic is recorded a visual indicator is shown on the Status page of the Driver Application. The following malfunctions are tracked, recorded and transmitted during inspections: Power compliance malfunction - When the total engine hour difference between recorded events that contain this value is greater than 30min in a single day. Power data diagnostic event - When engine hour difference between the last recorded event that had engine hours defined and the vehicles last known engine hours from this day are 0.1 or greater. Timing compliance malfunction - If Driver Application Device time is not matching the time of the device that has originated the event by more than 10min when an event is received by the Driver Application Device. Positioning compliance malfunction - When we're driving and no location information is received by the Driver Application within 5 seconds of the 1h mark. Data recording compliance malfunction - When a write to the local database stored on the Driver Application Device fails for any reason. Missing required data elements data diagnostic event - When an automatic event is being received by the Driver Application if required fields are missing. Unidentified driving records data diagnostic event - When more than 30 minutes of unidentified driving time for the vehicle has been recorded over the last 24 hours.
User Manual: 
Information Packet.pdf