With the Teltonika global install base increasing, examples have started to emerge where data from these devices can be represented incorrectly in MiX Fleet Manager.
Specifically, identified drivers are not reliably associated to trips and trips with poor GPS (especially at the start of the trip) can be missing from MiX Fleet Manager.
To address the above issues, changes have been made to the device config and data processing in MiX Fleet Manager to provide a robust and reliable implementation across a wide variety of real-world operating conditions.
Teltonika device config changes MUST be made and applied to all active devices to achieve a robust solution. The recommended default configs for these devices will be updated to reflect all of the required changes.
Please see the updated Teltonika settings guide. The latest changes have been made in these sections.
Changes have been made to these parts of the document in February 2024.
****************************************************************
System
- System Settings – Record Saving/sending Without TS, pg 10
Advanced features
- Driver ID via Dallas iButton, pg 26
- Feature Section – Read ID Notification, pg 26
- Trip/Odo Section – Remember iButton/RFID, pg 26
- I/O Section - iButton, pg 26
****************************************************************
Please note: that driver ID should not be offered without some form of driver feedback indicating that the driver tag has been read successfully. This could either be integrated into the reader device fitted or an LED or Buzzer added separately in the install.