SyncUP FLEET HOS

Electronic Logging DeviceT-Mobile USA, Inc. SyncUP FLEET HOS
Model NumberSyncUP FLEET HOS 1.0
ELD ID NumberTMOELD
Software Version4.1

Model Information

Data Transfer MethodsOur data transfer description for drivers is outlined in this document: https://drive.google.com/file/d/1FGtE5BD4fhAn1NjFapIZw0dYOCnrkFwJ/view Data Transfer Description: SyncUP FLEET HOS supports the telematics (electronic) data transfer method via wireless Web services and email. To enable this during a roadside inspection, the following steps will apply: 1. From the Dashboard, select the Inspection tab. 2. Enter a one-time PIN and press Continue. Enter the PIN again and Confirm PIN. 3. If you choose not to set a PIN, press No PIN. 4. Do one of the following: a. To transfer HOS logs, enter the code provided by the Officer in the Comments field, and select Email or Web Services to transfer the report. b. To display the report, select the Compliance Print to display the report on your mobile device. Use the arrow buttons to move between days. Scroll through each report to display all information for that day 5. To review the DVIR, select the DVIR icon at the top of the screen, and select Review. Scroll down and select View to see the list of defects used in the inspection. 6. To exit the DVIR, close the defects list and select the back arrow at the top left corner of the screen. 7. To exit Inspection Mode, select the X icon at the top right corner of the screen, and enter the PIN.
Malfunction NotesOur malfunctions description for drivers is outlined in this document: https://drive.google.com/file/d/0Bx-Ij37uV33INHkxY0VnNzFBaVU/view Summary of Malfunctions: Malfunction Code P: Power data malfunction: The ELD records a power data malfunction when an ELD is not powered for a cumulative in-motion driving time of 30 minutes or more over a 24-hour period, for all drivers. • This may be caused by an intermittent or full disconnection from the vehicle ECM. This could be due to an installation issue with the telematics device. • Contact your motor carrier to inspect the installation if you are unable to check yourself. • When the problem is resolved, you may clear this event. Malfunction Code E: Engine synchronization compliance malfunction: The ELD records an engine synchronization compliance malfunction when ECM connectivity to any of the required data sources (i.e. engine power status, vehicle motion status, miles driven, engine hours) is lost for more than 30 minutes during a 24-hour period, for all drivers. • This may be caused by an intermittent or full disconnection from the vehicle ECM. This is could be due to an installation issue with the telematics device. • Contact your motor carrier to inspect the installation if you are unable to check yourself. • When the problem is resolved, you may clear the event. Malfunction Code T: Timing compliance malfunction: The ELD records a timing compliance malfunction when it fails to synchronize with an external UTC source, and can no longer meet the underlying timing compliance requirement not to exceed an absolute deviation of 10 minutes at any time. • Check the time on your mobile device to ensure it is set to acquire time automatically. • When the problem is resolved, you may clear the event. Malfunction Code L: Positioning Compliance malfunction: The ELD records a positioning compliance malfunction when it fails to acquire a valid position measurement within five miles of the commercial motor vehicle’s movement, after 60 minutes has elapsed. • This may be caused by a temporary or permanent loss of GPS on the telematics device. • Contact your motor carrier to inspect the installation. If the problem persists, replace the telematics device. • When the problem is resolved, you may clear the event. Malfunction Code R: Data recording compliance malfunction: The ELD records a data recording compliance malfunction when 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 motor carrier as soon as possible. • Once the problem is resolved, you may clear the event. Malfunction Code S: Data transfer compliance malfunction: The ELD records a data transfer compliance malfunction when the ELD stays in the unconfirmed data transfer mode following the next three consecutive monitoring checks. • Check your Internet connection. • Contact your wireless carrier if the problem persists. • When the problem is resolved, you may clear the event. Malfunction Code O: “Other” ELD identified malfunction: The other ELD identified malfunction is not supported. Diagnostic Code: 1 Power data diagnostic: The ELD records a power data diagnostic event when an ELD is not powered and fully functional within one minute of the vehicle’s engine turning on, and does not remain powered for as long as the vehicle’s engine stays powered. • This may be caused by an intermittent or full disconnection from the vehicle ECM. This could be due to an installation issue with the telematics device. • When the problem is resolved, the system will auto-clear the event. Diagnostic Code: 2 Engine synchronization data diagnostic: The ELD records an engine synchronization data diagnostic event when an ELD loses ECM connectivity to any of the required data sources (i.e. engine power status, vehicle motion status, miles driven, engine hours), and can no longer retrieve updated values for the required ELD parameters within five seconds of the request. • This may be caused by an intermittent or full disconnection from the vehicle ECM. This could be due to an installation issue with the telematics device. • This may also occur if the ELD is unable to record the required engine data from the vehicle ECM. • Contact your motor carrier if the problem persists. Diagnostic Code: 3 Missing required data elements data diagnostic: The ELD records a missing required data elements data diagnostic event when any required data field is missing at the time of its recording. • This may be caused by a manual log created by the driver when there is a temporary loss of GPS on the telematics device. • If the driver does not enter an address manually when prompted by the “Where was this?” message, this diagnostic is created. • This can be resolved by selecting the “Where was this?” message associated with the record, and manually entering the missing data. Diagnostic Code: 4 Data transfer data diagnostic: The ELD records a data transfer data diagnostic when the operation of the data transfer mechanism(s) cannot be confirmed. The ELD verifies this operation at least once every seven days. • Check your Internet connection. • Contact your wireless carrier if the problem persists. • When the problem is resolved, the system will auto-clear the event. Diagnostic Code: 5 Unidentified driving records data diagnostic: The ELD records an unidentified driving record diagnostic event when more than 30 minutes of driving time by an unidentified driver is recorded within a 24-hour period. When the diagnostic is recorded, the ELD turns on the data diagnostic indicator for all drivers logged into the ELD for the current 24-hour period, and the seven days that follow. • Review all unassigned logs when logging in or out of the vehicle to ensure you have claimed any applicable logs. • If the unassigned logs do not belong to you, you can ignore this diagnostic event. • When the logs are claimed, the system will auto-clear the event. Diagnostic Code: 6 “Other” ELD identified diagnostic: The other ELD identified is not supported. Driver’s actions for when an “other” ELD identified diagnostic occurs: The other ELD identified is not supported.
Certifying StatementT-Mobile certifies that its SyncUP FLEET HOS device and application have been tested by the original equipment manufacturer for compliance with the FMCSA regulations.

Company Information

ManufacturerT-Mobile USA, Inc.
Websitehttps://www.t-mobile.com/
Contact Email[email protected]
Contact Phone Number877-347-2127
Address3625 132nd Ave SE, Bellevue, WA, 98006

Devices From T-Mobile USA, Inc.


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