| Data Transfer Methods | The TraxTrax mobile application includes a ROADSIDE INSPECTION mode feature inside of the driver’s electronic logbook menu. Upon selecting the ROADSIDE INSPECTION mode the driver may select a time period of the current day + 7 previous days OR the current day + 14 previous days. The ROADSIDE INSPECTION is intended for HOS compliance for a roadside inspection and can: • Show a visual display summary of the electronic logbook and all events of the ELD Records of Duty Status information • Electronically transfer data of the electronic logbook and all events of the ELD Records of Duty Status information via email • Electronically transfer data of the electronic logbook and all events of the ELD Records of Duty Status information via web services • Save a PDF of the electronic logbook and all events of the ELD Records of Duty Status information which will allow the user to print these records The visual display summary, the electronic data transfer via email and web services and the PDF function for printing include the TruxTrax ELD authentication value when connected to the ELD. The electronic data transfer via email includes the TruxTrax ELD authentication value and is formatted as described in section 4.8.2.1 and encrypted using the Secure/Multipurpose Internet Mail Extensions as described in RFC 5751. This is contingent of the reception of the RFC 5321 Simple Mail Transfer Protocol (SMTP) to be provided by the FMCSA. The electronic data transfer via web services includes the TruxTrax ELD authentication value and is set to convert an WSDL to XML format using SOAP. This is contingent of the reception of the FMCSA schema for upload and WSDL file instructions for upload using SOAP, as well as the Rules of Behavior, Interface Control Document (ICD), and the ELD Web Services Development Handbook. The TruxTrax mobile application must be installed on an authorized mobile device (personal or fleet owned) and connected via Bluetooth/BLE to the TRUXBOX ELD which must be plugged in to the vehicles diagnostic port. |
| Malfunction Notes | TruxTrax provides the ELD Malfunction sheet for drivers included in the Truxbox ELD user manual, which they can present to a DOT officer during an inspection in case of an ELD malfunction. Data Diagnostics An ELD must have the capability to monitor its compliance with the technical requirements. It must detect and record events related to malfunctions and data inconsistencies. (Subpart B, section 4.6) Data Diagnostic Events: These events are when an ELD indicates there is a data inconsistency. The driver must follow the recommendations by the ELD provider to resolve the inconsistency, if it occurs. [Section 49 CFR 395.34(c)] Power data diagnostic code 1 An ELD must monitor the Data it receives from the engine ECM or alternative sources, and data record history to identify instances when it may not have complied with the power requirements Cause ? ELD not fully functional within one minute of the engine turning on ? Wiring or power source fault Response Drivers must check that their logs are correct by reviewing them on the mobile application. Then, they can resolve the diagnostic event by turning of the Truck engine and restarting. The driver must notify the carrier and TruxTrax by following the “hard malfunction” process if these events become a regular occurrence. Engine synchronization diagnostic code 2 An ELD is required to establish a link to the engine ECM, and must record an engine synchronization data diagnostics event, when it no longer can acquire values for the ELD parameters required for records within five seconds. Cause •Wiring or connection fault Response Drivers must notify the carrier as soon as possible and arrange for the ECM link to be restored. Once the ECM link is restored, drivers must thoroughly review their logs and edit, as necessary, to ensure they are correct. Then, they can resolve the diagnostic event by turning of the Truck engine and restarting. The driver must notify the carrier and TruxTrax by following the “hard malfunction” process if these events become a regular occurrence. Missing required data elements data diagnostic code 3 An ELD must monitor the completeness of the ELD event record information in relation to the required data elements for each event type, and must record a missing data element and data diagnostics event for the driver, if any required field is missing at the time of recording. Cause • Temporary or permanent loss of GPS • Intermittent or disconnected link to the vehicle ECM Response Drivers can resolve this data diagnostic by manually entering the missing data associated with their records along with an explanation. The driver must notify the carrier and TruxTrax by following the “hard malfunction” process if these events become a regular occurrence. Data transfer data diagnostic code 4 An ELD must implement in-service monitoring functions to verify that the data transfer mechanism(s) are continuing to function properly. An ELD must verify this functionality at least once every seven days. Cause • ELD fails to communicate records to EROAD Depot for seven continuous days Response Unless driving in an area with known cellular coverage issues, drivers should notify their carrier immediately. This fault auto-resolves, if the device begins to communicate successfully again. The driver must notify the carrier and TruxTrax by following the “hard malfunction” process if these events become a regular occurrence. Unidentified driving records data diagnostic code 5 If more than 30 minutes of driving in a 24-hour period shows unidentified driver on the ELD, the ELD must detect and record an unidentified driving record data diagnostic event, and the data diagnostic indicator must be turned on for all drivers logged in to that ELD for the current 24-hour period and the following seven days. Cause • More than 30 minutes combined vehicle use without a logged-in driver Response Drivers must review the unidentified journeys recorded on the ELD and accept any periods of drive time recorded, while they were driving and not logged in to the ELD system. Malfunctions management Malfunction events are when the ELD detects technical compliance issues. The driver must: (1) notify the motor carrier within 24 hours, (2) reconstruct the record of duty status for the current 24 hours and the last seven days on graph -grid paper logs that comply with Section 49 CFR 395.8. Keep paper logs until the ELD is serviced and brought back into compliance. [Section 395.34(a)] Power compliance code P An ELD must monitor the data it receives from the engine ECM or alternative sources, and data record history to identify instances when it might not have complied with the power requirements. Cause • More than 30 minutes of driving time lost in a 24-hour period Response Drivers should review and correct their logs, and notify their carrier of the fault. Once the fault has been corrected, the malfunction is cleared by explaining the fault and resolution in the ELogbook notes section. Engine synchronization code E 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. Cause • More than 30 minutes without ECM engine synchronization over a 24-hour period Response Drivers must notify their carrier as soon as possible and arrange for the ECM link to be restored. Once the ECM link is restored, drivers must thoroughly review their logs and edit, as necessary, to ensure they are correct. Then, they can resolve the diagnostic event by turning of the Truck engine and restarting. The driver must notify the carrier and TruxTrax by following the “hard malfunction” process if these events become a regular occurrence. Timing compliance code T 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. Cause • Vehicle has been out of service for sufficient time that the internal clock is no longer accurate, and the ELD has not yet synchronised its time Response Once the internal clock has been corrected, drivers are prompted to review their logs before resolving the malfunction. Then, they can resolve the diagnostic event by turning of the Truck engine and restarting. The driver must notify the carrier and TruxTrax by following the “hard malfunction” process if these events become a regular occurrence. Positioning compliance cone L 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. Cause • More than 60 minutes without a valid GPS fix in a 24-hour period This malfunction might appear during a temporary loss of a valid GPS fix, but it auto-resolves once GPS is restored. The driver must notify the carrier and TruxTrax by following the “hard malfunction” process if these events become a regular occurrence. Data recording compliance R 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. Cause • Hardware fault Response The driver must notify the carrier and TruxTrax by following the “hard malfunction” process. Data Transfer compliance code S 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. Cause •Failure to communicate for three days following a data transfer data diagnostic event Response Unless driving in an area with known cellular coverage issues, the driver must notify the carrier and TruxTrax by following the “hard malfunction” process if these events become a regular occurrence. This fault auto-resolves, when the device begins to communicate successfully. |
| Certifying Statement | TruxTrax “Truxbox” ELD Certifying statement TruxTrax Inc. (“TruxTrax”) is the manufacturer of the Truxbox ELD device and the TruxTrax web platform which, along with a connected Android or IOS device and the TruxTrax mobile application, comprises of an hours of service solution via Electronic Logbook and Electronic Logging Device (ELD) as described in the “Truxbox ELD user manual”. Subject to the terms set out in this certificate, TruxTrax certifies that the design of the Truxbox ELD has been tested to meet the FMCSA requirements of § 395.15 of title 49 Code of Federal Regulations Part 395 under the conditions that it will be used, as intended and described in the “Truxbox ELD user manual”. TruxTrax inc. certifies that the Truxbox ELD is compliant with the FMCSA technical specifications as set forth in § 395.15 of Part 395 of title 49, Code of Federal Regulations. It is the Carrier’s responsibility to ensure that drivers are adequately informed and trained regarding the proper operation of the Truxbox ELD device. The above certification is subject to and conditional upon the proper installation, configuration and use of the Truxbox ELD device in accordance with all applicable documentation. Failure to do so may result in inconsistencies in the ELD device performance. This certificate is not a substitute for, nor does it relieve an operator of its responsibilities under applicable law. This certificate is not intended to give rise to any enforceable agreement with or any undertaking to any person or persons whatsoever. Without limiting the generality of the foregoing: (a) TruxTrax disclaims all representations, warranties and conditions, express or implied, including without limitation any representations, warranties and conditions of merchantability, merchantable quality, durability, fitness for a particular purpose, non-infringement, title, quiet enjoyment or quiet possession and those arising by statute or in law, or from a course of dealing or usage of trade; and (b) in no event will TruxTrax inc. be liable or otherwise responsible for any loss or damages of any kind whatsoever, (b) Including without limitation special, incidental, indirect or consequential losses or damages, loss of revenue or profits, loss of data, business information or loss of use thereof, failure to realize expected profits or savings, loss of capital, loss of business opportunities lost goodwill or any other commercial or economic loss or damage of any kind. The foregoing exclusions and disclaimers above will apply irrespective of the nature of the cause of action, including breach of contract, tort, negligence, negligent misrepresentation, strict liability, product liability or any other legal or equitable theory This certificate is solely for the information of end users who have purchased or subscribed to the “Truxbox ELD” solution from TruxTrax inc. to facilitate their compliance with § 395.15 of 49 CFR Part 395 and is not to be used, circulated, quoted, relied upon or otherwise referred to by any other person, in any other manner for any other purpose. TruxTrax Inc. 5580 Boulevard Thimens, Saint-Laurent, QC H4R 2K9 514.594.1988 [email protected] https://www.truxtrax.com |
