Transflo T-Series ELD Diagnostics and Malfunction Codes

If your Transflo HOS app shows the following red warning, follow these steps to review the event codes and possible steps to fix the problem:

Follow these steps:

1. Your HOS app might show this red warning. If it does, tap Malfunction Notifications or the red bar.

   

2. Review the malfunction type.

   

3. Review the diagnostic and malfunction code table on this page.

4. Investigate the issue and address the root problem.

5. After the issue is resolved, the error notification typically clears itself. If not, press the Clear button.

   

6. Resume normal operation.

If you get a malfunction warning message as described above, review the following list of diagnostic codes (numbers) and malfunction codes (letters).

Code:	Transflo ELD Malfunction Diagnostic Event:	Driver Steps to Resolve:
1	Power data diagnostic: 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. Once investigated, and the problem is resolved, the system will auto clear the event.
2	Engine synchronization diagnostic: 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.	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.
3	Missing required data elements data diagnostic: 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.	This code can occur when the ELD temporarily loses a GPS signal and the driver manually creates a log entry. If the driver does not enter an address manually when prompted by the Where was this? message, this diagnostic code is triggered. To resolve, select the Where was this? associated with the record and manually enter the missing data. Once investigated, and the problem is resolved, the system will auto clear the event.
4	Data transfer data diagnostic: 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.	Check your internet connection. After the issue is investigated, and the problem is resolved, the system will auto clear the malfunction event. If problem persists, contact your carrier.
5	Unidentified driving records data diagnostic: 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.	Review all unassigned logs when logging in or logging out of the vehicle and ensure you have claimed any logs that may be applicable to yourself. If the unassigned logs are not yours, you can ignore this diagnostic event. Please note this event will automatically clear itself as logs get claimed.
6	"Other" ELD identified diagnostic: The other ELD identified is not supported.	The other ELD identified is not supported.
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. 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.
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 Transflo HOS device. Contact your carrier to get the install inspected- If problem still persists, replace the Transflo HOS device. Once investigated and the problem is found you may clear this event.
O	"Other" ELD identified malfunction: The other ELD identified malfunction is not supported.	The other ELD identified is not supported.
P	Power data malfunction: 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.	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.
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.
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 problem persists, contact your carrier. Once investigated and the problem is found you may clear this event.
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 phone time settings. Ensure it is set to acquire time automatically. Once investigated and the problem is found you may clear this event.

As an official Geotab partner, Transflo ELDs are powered by Geotab. When drivers log in to HOS and their MyGeotab or myTransflo ELD portals, their Geotab sessions expire after 14 days from the time of their last login (with or without any user activity in those 14 days).

As a driver, if you can't log in and resetting your password doesn't work, it likely means that you are locked out. As a driver, you might experience one or more of the following lockout problems:

• You cannot log in to the ELD, HOS app, or Telematics portal.

• You are prompted to enter your credentials and then asked to re-enter them again in a loop without a successful login.

• You are prompted to Force password change on next login but the setting is not saved and you experience the login loop above.

• You cannot log in to your account after creating a new password or after waiting for a preset lock out period to go by.

• You have no reset password option or cannot otherwise reset your driver password even after you attempt multiple logins and resets.

• You might be successful with your password reset but when you try logging in again, you receive a max number of attempts was reached please contact support error.

• You try to log in to Geotab and change your password one or more times but still get an error and cannot log in.

 

To resolve this issue, follow these steps:

1. As a driver, notify your fleet admin if you believe that you locked yourself out due to the 14-day Idle Session Timeout feature or the User Lockout features in MyGeotab.

2. As a driver, track how many times you attempted to login. Notify your admin if you reached the maximum number of failed login attempts during the authentication period.

3. As an admin, you can configure these settings under Administration, System, System Settings, User Account Policy.

   For security, to prevent malicious hackers or other malicious users from hijacking your account, your fleet admin typically sets the Enable User Lockout option to ON. The following settings now apply:

   • Failed Login Attempts: If this number is low, say under 5, you might experience a lockout. The solution is to remember your password, to try not to fail logging in more than 2 or 3 times, or to ask your admin to set this higher, for example to 5 or 6. Setting this higher can increase your risk exposure as malicious users have more opportunities to guess your credentials.

   • Authentication Period: Typically set to 15 minutes, your admin can decrease this to 12 or 10 minutes; however, setting this to a shorter time duration can increase your security risk. Setting the period to a longer duration, for example 30 minutes, can result in more locked out users.

   • Lockout time: Typically 30 minutes, this is how long your account is frozen, much like when a concerned consumer freezes their credit report history to prevent hard credit pulls or identity theft. Shorter lockout times can ease driver frustration but increase the security risk.

     

     Contact your admin to learn more.

4. User security clearance is default user. Contact your administrator to unlock you. Only the administrator security clearance can unlock profiles. Even if a user has the sub-clearance of an administrator, they will not be able to unlock profiles.

5. As an admin user with administrator clearance, to unlock the driver follow these sub-steps:

   1. In the main menu, navigate to Administration, Users.

   2. In the list of users, select the user that is locked out (use the search bar at the top to search for a specific user if the list is too long).

   3. At the top of the User Edit page, click Unlock.

   4. Select Unlock again in the pop-up window to confirm. The user can now attempt to log in again.

   

   Tip: Password resets done while the user was locked out may not work. Unlock the user or wait until the user lockout time has expired to reset the password again before logging in.