Template:FTX Firmware Changelog: Difference between revisions
No edit summary |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 119: | Line 119: | ||
'''NEW FEATURES''' | '''NEW FEATURES''' | ||
* '''NEW''' Dead Reckoning | Sleep / Stand By mode support for [FTXXX'''7'''] devices | * '''NEW''' Dead Reckoning | Sleep / Stand By mode support for [FTXXX'''7'''], [FTXXX'''8'''] devices | ||
* '''NEW''' Manual Geofence | Polygon zones support added | * '''NEW''' Manual Geofence | Polygon zones support added | ||
| Line 161: | Line 161: | ||
* Resolved an issue where PDP activation attempts were triggered despite no valid operator being selected | * Resolved an issue where PDP activation attempts were triggered despite no valid operator being selected | ||
* APN cycling is now performed even when the device is not registered to the network. Previously, APN switching was only triggered after successful operator registration, which could prevent connection to certain operators if an incorrect APN was used. | * APN cycling is now performed even when the device is not registered to the network. Previously, APN switching was only triggered after successful operator registration, which could prevent connection to certain operators if an incorrect APN was used. | ||
* Corrected MCAN service initialization failure caused by commands configured with Send type = “Response” without assigned Manual CAN IO. | * Corrected MCAN service initialization failure caused by commands configured with Send type = “Response” without assigned Manual CAN IO. Such misconfigurations previously caused the entire MCAN service to stop, making all commands unreachable. | ||
Such misconfigurations previously caused the entire MCAN service to stop, making all commands unreachable. | |||
* Resolved an issue where the MAC address was inverted when configured via command | * Resolved an issue where the MAC address was inverted when configured via command | ||
* Resolved an issue where GPS log output format could change intermittently | * Resolved an issue where GPS log output format could change intermittently | ||
| Line 175: | Line 174: | ||
* Resolved an issue where Auto Geofence “On Entrance” records were not generated while the device was powered by an external power source | * Resolved an issue where Auto Geofence “On Entrance” records were not generated while the device was powered by an external power source | ||
* Resolved an issue where DIN could trigger wake-up from Deep Sleep even when not configured as an Ignition or Movement source | * Resolved an issue where DIN could trigger wake-up from Deep Sleep even when not configured as an Ignition or Movement source | ||
* Resolved an issue where eventual I/O records were generated even when Events were not configured in the I/O section. | * Resolved an issue where eventual I/O records were generated even when Events were not configured in the I/O section. BLE Sensors configured for Temperature/Humidity monitoring could trigger unintended eventual records (e.g., on visibility changes), ignoring the “monitoring” operand. | ||
BLE Sensors configured for Temperature/Humidity monitoring could trigger unintended eventual records (e.g., on visibility changes), ignoring the “monitoring” operand. | |||
* Resolved an issue where duplicate Immobilizer Eventual records could be generated when authorization occurred before ignition transition (0 → 1) | * Resolved an issue where duplicate Immobilizer Eventual records could be generated when authorization occurred before ignition transition (0 → 1) | ||
* Resolved an issue where scheduled records set to a 1-minute interval where not saved | * Resolved an issue where scheduled records set to a 1-minute interval where not saved | ||
* Resolved an issue where DOUT control remained active after disabling Manual Geofence or performing a device configuration reset. | * Resolved an issue where DOUT control remained active after disabling Manual Geofence or performing a device configuration reset. DOUT now correctly stops being controlled when the feature is disabled or configuration is reset | ||
DOUT now correctly stops being controlled when the feature is disabled or configuration is reset | |||
* Corrected connection handling after Online Sleep wake-up, where multiple small data packets triggered repeated connect–send–disconnect cycles instead of being transmitted in a single continuous session | * Corrected connection handling after Online Sleep wake-up, where multiple small data packets triggered repeated connect–send–disconnect cycles instead of being transmitted in a single continuous session | ||
* Resolved an issue where a modem reset after FPLMN write cleared the FPLMN list, causing the device to repeatedly reconnect to the same banned operator, preventing stable data connection. | * Resolved an issue where a modem reset after FPLMN write cleared the FPLMN list, causing the device to repeatedly reconnect to the same banned operator, preventing stable data connection. | ||
Latest revision as of 10:40, 27 April 2026
Introduction
We are always improving our device's performance, stability, and reliability. That’s why Teltonika is one of the leading GNSS trackers manufacturers in the world.
This document describes FT platform devices firmware improvements, changes, new features implementations as well as current firmware release version.
Important: Please visit Product Maintenance Policy for detailed firmware update policy.
Firmware versioning
- Structure
[XX].[YY].[ZZ]
- Syntax description
XX– shows major backward incompatible changes in firmware, i.e. security feature.YY– shows major changes like new features or module support additions.ZZ– shows changes like critical issue fixes.
Firmware versions
| FIRMWARE VERSION | SUPPORTED HARDWARE |
|---|---|
| 3.7.0 | ATC700_21, ATM700_21, FTC305_31, FTC305_41, FTM305_41, FTC308_41, FTM308_41, FTC880_12, FTC880_24, FTC880_41. FTC881_23, FTM880_02. FTM880_12, FTM880_24, FTM880_41, FTC887_21, FTM887_21, FTC920_22, FTC921_26, FTC921_43, FTC924_22, FTC927_22, FTM927_22, FTC961_23, FTC961_32, FTC965_32, FTC134_32, FTM134_32, FTC164_24, FTM164_24 |
| 3.7.0.rc-25 | ATC700_21, ATM700_21, FTC305_31, FTC305_41, FTM305_41, FTC880_12, FTC880_24, FTC881_23, FTM880_12, FTM880_24, FTM880_02, FTC887_21, FTM887_21, FTC920_22, FTC921_26, FTC921_43, FTC924_22, FTC927_22, FTM927_22, FTC961_23, FTC961_32, FTC965_32, FTC134_32, FTM134_32 |
| 3.7.0.rc-22 | FTC305_31, FTC305_41, FTM305_41, FTC880_12, FTC880_24, FTC881_23, FTM880_12, FTM880_24, FTM880_02, FTC887_21, FTM887_21, FTC920_22, FTC921_26, FTC921_43, FTC924_22, FTC927_22, FTM927_22, FTC961_23, FTC961_32, FTC965_32, FTC134_32, FTM134_32 |
| 3.7.0.rc-19 | ATC700_21, ATM700_21, FTC305_31, FTC305_41, FTM305_41, FTC880_12, FTC880_24, FTC881_23, FTM880_12, FTM880_24, FTM880_02, FTC887_21, FTM887_21, FTC920_22, FTC921_26, FTC921_43, FTC924_22, FTC927_22, FTM927_22, FTC961_23, FTC961_32, FTC965_32, FTC134_32, FTM134_32 |
| 3.0.10 | FTC305_31, FTC305_41, FTM305_41, FTC880_12, FTC880_24, FTC881_23, FTM880_12, FTM880_24, FTM880_02, FTC887_21, FTM887_21, FTC920_22, FTC921_26, FTC921_43, FTC924_22, FTC927_22, FTM927_22 FTC961_23, FTC961_32, FTC965_32, FTC134_32, FTM134_32 |
| 3.0.8 | FTC305_31, FTC305_41, FTM305_41, FTC880_12, FTC880_24, FTC881_23, FTM880_12, FTM880_24, FTM880_02, FTC887_21, FTM887_21, FTC920_22, FTC921_26, FTC921_43, FTC924_22, FTC927_22, FTC961_23, FTC961_32, FTC965_32, FTC134_32, FTM134_32 |
| 3.0.7 | FTC305_31, FTC305_41, FTM305_41, FTC880_12, FTC880_24, FTC881_23, FTM880_12, FTM880_24, FTM880_02, FTC887_21, FTM887_21, FTC920_22, FTC921_26, FTC921_43, FTC924_22, FTC927_22, FTC961_23, FTC961_32, FTC965_32 |
| 2.4.3 | FTC921_26, FTC961_23, FTC881_23, FTC880_12, FTC880_24, FTM880_12, FTM880_24, FTM880_02, FTC305_31, FTM305_31 |
| 2.4.0 | FTC921_26, FTC961_23, FTC881_23, FTC880_12, FTC880_24, FTM880_12, FTM880_24, FTM880_02, FTC305_31, FTM305_31 |
| 2.1.4 | FTC921_26, FTC961_23, FTC881_23, FTC880_12, FTC880_24, FTM880_12, FTM880_24, FTM880_02 |
| 2.1.1 | FTC921_26, FTC961_23, FTC880_12 |
| 1.5.1 | FTC921_26, FTC961_12, FTC881_12 |
| 0.40.3 | FTC921_26, FTC961_12, FTC881_12 |
| 0.26.2 | FTC921_26, FTC961_12, FTC881_12 |
|
Note: The list of supported hardware versions shown above indicates compatibility from firmware side only and does not imply that the firmware version is recommended for device update or factory use. To verify the currently recommended and factory firmware versions for your device, please refer to the Firmware Versions page |
| FIRMWARE VERSION | RELEASE DATE | CHANGES |
|---|---|---|
| 3.7.0 | 2026-04-27 |
HARDWARE SUPPORT
NEW FEATURES
FIXES/IMPROVEMENTS
|
| 3.0.10 | 2026-03-02 |
HARDWARE SUPPORT
FIXES/IMPROVEMENTS
|
| 3.7.0-rc.25 | 2026-02-05 |
FIXES/IMPROVEMENTS
|
| 3.7.0-rc.22 | 2025-01-16 |
FIXES/IMPROVEMENTS
|
| 3.7.0-rc.19 | 2025-12-19 |
HARDWARE SUPPORT
NEW FEATURES
FIXES/IMPROVEMENTS
|
| 3.0.8 | 2025-12-08 |
HARDWARE SUPPORT
FIXES/IMPROVEMENTS
|
| 3.0.7 | 2025-10-29 | HARDWARE SUPPORT
NEW FEATURES
FIXES/IMPROVEMENTS
|
| 2.4.3 | 2025-04-15 | FIXES/IMPROVEMENTS
|
| 2.4.0 | 2025-03-14 | HARDWARE SUPPORT
|
| 2.1.4 | 2025-07-21 | HARDWARE SUPPORT
FIXES/IMPROVEMENTS
|
| 2.1.1 | 2025-06-04 | HARDWARE SUPPORT
NEW FEATURES
FIXES/IMPROVEMENTS
|
| 1.5.1 | 2024-12-16 | NEW FEATURES
FIXES/IMPROVEMENTS
|
| 0.40.3 | 2024-08-01 | NEW FEATURES
FIXES/IMPROVEMENTS
|
| 0.26.2 | 2024-02-13 | NEW FEATURES
FIXES/IMPROVEMENTS
|