TruckishELD

Electronic Logging DeviceTruckish TruckishELD
Model NumberTE1
ELD ID NumberTRUELD
Software Version1.1

Model Information

Data Transfer MethodsTruckish supports data transfer using FMCSA's ELD Web Service Interface & ELD Email Interface. To send the driver logs to FMCSA, driver needs to perform the following steps: 1. Click on the Hamburger Menu on the top-left corner 2. Select DOT Inspection Mode 3. Add comments to the logs as provided by the DOT Inspector. 4. Click on "Send Logs" button: Once driver clicks the "Send Logs" button, Truckish creates driver logs for last 7 days plus current day. Then Truckish server tries to send the logs to FMCSA using ELD web service interface. If the first method fails then Truckish server sends the logs to FMCSA using ELD Email Interface 5. Driver gets a confirmation that logs were sent to FMCSA
Malfunction NotesMalfunction Code P: Power data Malfunction: An ELD must monitor the data it receives from the engine ECM and data record history to identify instances when it may not have complied with the power requirements. This may be caused by an intermittent or disconnected connection to the vehicle ECM. This is likely due to an install issue. Contact your carrier to get the install inspected if you’re unable to check yourself. Once investigated and the problem is found you may clear this event. Malfunction Code E: Engine synchronization compliance Malfunction: An ELD must set an engine synchronization compliance malfunction, if connectivity to any of the required data sources is lost for more than 30 minutes during a 24-hour period aggregated across all driver profiles. This may be caused by an intermittent or disconnected connection to the vehicle ECM. This is likely due to an install issue. This may also be caused if the ELD is unable to pick up the required engine data from the vehicle ECM. Contact your carrier if the problem persists. Once investigated, and the problem is resolved, the system will auto clear the event. Malfunction Code T: Timing compliance malfunction: The ELD must periodically cross-check its time with an external UTC source, and must record a timing compliance malfunction when it can no longer meet the underlying timing requirement of less than 10 minutes’ time deviation. Check your mobile device’s phone time. Ensure it is set to acquire time automatically. Once investigated and the problem is found you may clear this event. Malfunction Code L: Positioning Compliance malfunction: An ELD must monitor elapsed time during periods when the ELD fails to acquire a valid position measurement within five miles of the CMV’s movement. When such elapsed time exceeds a cumulative 60 minutes over a 24-hour period, the ELD must set and record a positioning compliance malfunction. This can be caused by temporary or permanent loss of GPS by the Geotab GO device. Contact your carrier to get the install inspected. If problem still persists, replace the Geotab GO device. Once investigated and the problem is found you may clear this event. Malfunction Code R: Data recording compliance malfunction: An ELD must monitor its storage capacity and integrity and must detect a data recording compliance malfunction if it can no longer record or retain required events, or retrieve recorded logs that are not otherwise cataloged remotely by the motor carrier. Contact your carrier to get in touch with Support as soon as possible. Once investigated and the problem is found you may clear this event. Malfunction Code S: Data transfer compliance malfunction: After an ELD records a data transfer data diagnostic event, the ELD must increase the frequency of the monitoring function to check at least once every 24-hour period. If the ELD stays in the unconfirmed data transfer mode following the next three consecutive monitoring checks, the ELD must detect a data transfer compliance malfunction. Check your internet connection. If the problem persists, contact your carrier. Once investigated and the problem is found you may clear this event. Malfunction Code O: “Other” ELD identified diagnostic: The other ELD identified malfunction is not supported. The other ELD identified is not supported.
Certifying StatementTruckishELD was certified through successful testing and verification of FMCSA ELD Test Procedures. TruckishELD was installed in several Android devices and trucks and tested thoroughly. The Truckish web portal for Hours of Service edits was successfully accessed using any web browser.

Company Information

ManufacturerTruckish
Websitehttp://www.truckish.com
Contact Email[email protected]
Contact Phone Number7319037170
Address88 Union Ave. STE 200, Memphis/TN/38103

Devices From Truckish


Device ID
Truckish TruckishELD TRUELD

Related ELDs


This site's data is aggregated programmatically and provided "as is" without any representations or warranties, express or implied. Transportation.report is not affiliated with the DOT, the NHTSA, or the US government in any way.

© 2022 Transportation.Report | Definitions