Template:FTX Firmware Changelog: Difference between revisions
No edit summary |
No edit summary |
||
| (119 intermediate revisions by 7 users not shown) | |||
| Line 2: | Line 2: | ||
===Introduction=== | ===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.<br /> | 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.<br /> | ||
This document describes ''' | This document describes '''FT platform''' devices firmware improvements, changes, new features implementations as well as current firmware release version. | ||
<br/> | |||
'''Important:''' Please visit [[Product Maintenance Policy]] for detailed firmware update policy. | |||
<br/> | |||
===Firmware versioning=== | ===Firmware versioning=== | ||
| Line 18: | Line 20: | ||
<table class="nd-othertables_2" style="width:60%; margin-bottom: 30px;"> | <table class="nd-othertables_2" style="width:60%; margin-bottom: 30px;"> | ||
<tr> | |||
<th style="width:20%; text-align: left;">FIRMWARE VERSION</th> | <th style="width:20%; text-align: left;">FIRMWARE VERSION</th> | ||
<th style="width:40%; text-align: left;">SUPPORTED HARDWARE</th> | <th style="width:40%; text-align: left;">SUPPORTED HARDWARE</th> | ||
</tr> | |||
<tr> | |||
<td style="text-align: left; color:#000000;"><strong>3.7.0</strong></td> | |||
<td style="text-align: left;"> 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 </td> | |||
</tr> | |||
<tr> | |||
<tr> | |||
<td style="text-align: left; color:#000000;"><strong>3.7.0.rc-25</strong></td> | |||
<td style="text-align: left;"> 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 </td> | |||
</tr> | |||
<tr> | |||
<tr> | |||
<td style="text-align: left; color:#000000;"><strong>3.7.0.rc-22</strong></td> | |||
<td style="text-align: left;"> 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 </td> | |||
</tr> | |||
<tr> | |||
<tr> | |||
<td style="text-align: left; color:#000000;"><strong>3.7.0.rc-19</strong></td> | |||
<td style="text-align: left;"> 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 </td> | |||
</tr> | |||
<tr> | |||
<td style="text-align: left; color:#000000;"><strong>3.0.10</strong></td> | |||
<td style="text-align: left;">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 </td> | |||
</tr> | |||
<tr> | |||
<td style="text-align: left; color:#000000;"><strong>3.0.8</strong></td> | |||
<td style="text-align: left;">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 </td> | |||
</tr> | |||
<tr> | |||
<td style="text-align: left; color:#000000;"><strong>3.0.7</strong></td> | |||
<td style="text-align: left;">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 </td> | |||
</tr> | |||
<tr> | <tr> | ||
<td style="text-align: left; color:#000000;"><strong>2. | <td style="text-align: left; color:#000000;"><strong>2.4.3</strong></td> | ||
<td style="text-align: left;">FTC881_23</td> | <td style="text-align: left;">FTC921_26, FTC961_23, FTC881_23, FTC880_12, FTC880_24, FTM880_12, FTM880_24, FTM880_02, FTC305_31, FTM305_31</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td style="text-align: left; color:#000000;"><strong> | <td style="text-align: left; color:#000000;"><strong>2.4.0</strong></td> | ||
<td style="text-align: left;"> | <td style="text-align: left;">FTC921_26, FTC961_23, FTC881_23, FTC880_12, FTC880_24, FTM880_12, FTM880_24, FTM880_02, FTC305_31, FTM305_31</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td style="text-align: left; color:#000000;"><strong> | <td style="text-align: left; color:#000000;"><strong>2.1.4</strong></td> | ||
<td style="text-align: left;"> | <td style="text-align: left;">FTC921_26, FTC961_23, FTC881_23, FTC880_12, FTC880_24, FTM880_12, FTM880_24, FTM880_02</td> | ||
</tr> | </tr> | ||
<tr> | |||
<td style="text-align: left; color:#000000;"><strong>2.1.1</strong></td> | <td style="text-align: left; color:#000000;"><strong>2.1.1</strong></td> | ||
<td style="text-align: left;">FTC921_26</td> | <td style="text-align: left;">FTC921_26, FTC961_23, FTC880_12</td> | ||
</tr> | </tr> | ||
<tr> | |||
<td style="text-align: left; color:#000000;"><strong>1.5. | <td style="text-align: left; color:#000000;"><strong>1.5.1</strong></td> | ||
<td style="text-align: left;">FTC921_26</td> | <td style="text-align: left;">FTC921_26, FTC961_12, FTC881_12</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td style="text-align: left; color:#000000;"><strong>0. | <td style="text-align: left; color:#000000;"><strong>0.40.3</strong></td> | ||
<td style="text-align: left;">FTC921_26</td> | <td style="text-align: left;">FTC921_26, FTC961_12, FTC881_12</td> | ||
</tr> | </tr> | ||
<tr> | |||
<td style="text-align: left;"> | <td style="text-align: left; color:#000000;"><strong>0.26.2</strong></td> | ||
<td style="text-align: left;">FTC921_26, FTC961_12, FTC881_12</td> | |||
</tr> | |||
</table> | |||
<table class="nd-othertables_2" style="width:60%; margin-top:8px;"> | |||
<tr> | |||
<td style="background:#f8f9fa; padding:10px 12px; font-size:95%;"> | |||
<strong>Note:</strong> 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|Firmware Versions page]] | |||
</td> | |||
</tr> | |||
</table> | |||
<table class="nd-othertables_2" style="width:100%; margin-bottom: 30px;"> | |||
<tr> | |||
<th style="width:20%; text-align: left;">FIRMWARE VERSION</th> | |||
<th style="width:20%; text-align: left;">RELEASE DATE</th> | |||
<th style="width:60%; text-align: left;">CHANGES</th> | |||
</tr> | |||
</td> | |||
</tr> | |||
<td style="text-align: left; color:#000000;"><strong>3.7.0</strong></td> | |||
<td style="text-align: left;">2026-04-27</td> | |||
<td style="text-align: left;"> | |||
'''HARDWARE SUPPORT''' | |||
* '''NEW''' Added support for '''FTC164_24''' hardware modification | |||
* '''NEW''' Added support for '''FTCM64_24''' hardware modification | |||
* '''NEW''' Added support for '''FTC308_41''' hardware modification | |||
* '''NEW''' Added support for '''FTM308_41''' hardware modification | |||
* '''NEW''' Added support for '''FTC880_41''' hardware modification | |||
* '''NEW''' Added support for '''FTM880_41''' hardware modification | |||
'''NEW FEATURES''' | |||
* '''NEW''' Dead Reckoning | Sleep / Stand By mode support for [FTXXX'''7'''], [FTXXX'''8'''] devices | |||
* '''NEW''' Manual Geofence | Polygon zones support added | |||
* '''NEW''' Manual Geofence | Configurable DOUT control support added | |||
* '''NEW''' Immobilizer | Authorized Beacon list support added | |||
* '''NEW''' FTMFC (Firmware Bundle Container) support added | |||
* '''NEW''' Added SMS Events functionality | |||
* '''NEW''' QZSS Satellite system support added | |||
* '''NEW''' Added BASIC MQTT functionality | |||
* '''NEW''' Added SECO (Secure Engine Cut Off) functionality | |||
* '''NEW''' TLS/DTLS Encryption support added | |||
* '''NEW''' Added Private/Business mode functionality | |||
* '''NEW''' Added On Demand Tracking functionality | |||
* '''NEW''' Added Faulty Device Mounting functionality | |||
* '''NEW''' Added GNSS Fuel counter functionality | |||
* '''NEW''' Added "Faulty Device Mounting" I/O element | |||
* '''NEW''' Added "Fuel used GNSS" I/O element | |||
'''FIXES/IMPROVEMENTS''' | |||
* Refined Dead Reckoning behavior by fixing calibration inconsistencies, incorrect DR state changes during driving, and improper handling after sleep cycles. Reduced track jumps (e.g., underground parking), eliminated false movement after stop, and improved consistency between devices under identical conditions. | |||
* An empty mask is now used by default and functions as a pass-through, allowing unfiltered CAN data to be returned | |||
* Resolved an issue where devices could fail to send records in Deep Sleep mode due to premature GPRS task initialization | |||
* Changed default CAN baudrate setting to "Auto" | |||
* Resolved issues with DOUT control behavior when switching between different Output Control configurations for the immobilizer | |||
* Improved validation logic for domain names and IPv4/IPv6 addresses | |||
* 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. | |||
* 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. | |||
* Resolved an issue where the MAC address was inverted when configured via command | |||
* Resolved an issue where GPS log output format could change intermittently | |||
* Changed CAN Bitmask type to string and length to 64 bytes | |||
* Resolved an issue where DOUT1 could remain stuck if authorization occurred before ignition was turned on | |||
* Resolved an issue where the M2M SIM home network was identified as “unknown” in operator selection logic, causing it to be treated as a non-home network. This could lead to unintended behavior such as applying ban lists or prioritizing roaming operators over the actual home network. | |||
* Resolved an issue where operators could remain stuck on weak signal conditions without being properly banned. This has been corrected, and such failures now contribute to the PDP failure count, allowing the operator to be banned after the configured limit is reached | |||
* Resolved an issue where I/O elements for features with Eventual Records set to “Disabled” were not included in records while their state remained unchanged | |||
* Resolved an issue where modem status LED could incorrectly indicate active modem operation after external voltage or battery was disconnected. Modem status LED now correctly reflects modem state after power loss. | |||
* Resolved an issue where, after performing a configuration change, the device continued sending records to the previously configured server | |||
* Resolved an issue where lower priority scenarios did not take over DOUT control after a higher priority scenario ended | |||
* 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 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. | |||
* 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 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 | |||
* 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. | |||
* I/O elements accelerometer axis data is now displayed with ground vector being included | |||
</td> | |||
</tr> | </tr> | ||
</td> | |||
<td style="text-align: left; color:#000000;"><strong> | <td style="text-align: left; color:#000000;"><strong>3.0.10</strong></td> | ||
<td style="text-align: left;"> | <td style="text-align: left;">2026-03-02</td> | ||
<td style="text-align: left;"> | |||
'''HARDWARE SUPPORT''' | |||
* '''NEW''' Added support for '''FTM927_22''' hardware modification | |||
'''FIXES/IMPROVEMENTS''' | |||
* Resolved issue where devices with BG95-M3/M6 modems would fail to connect to the network when using roaming SIM cards due to insufficient network registration timeout | |||
* Updated network scan order to CAT-M1 → GSM → NB-IoT for devices with BG95-M3/M6 modems | |||
* Implemented special operator handling when EFad file does not provide MCC length information on the SIM card | |||
</td> | |||
</tr> | </tr> | ||
</td> | |||
<td style="text-align: left; color:#000000;"><strong>3.7.0-rc.25</strong></td> | |||
<td style="text-align: left;"> | <td style="text-align: left;">2026-02-05</td> | ||
<td style="text-align: left;"> | |||
'''FIXES/IMPROVEMENTS''' | |||
* Improved LED brightness control for ['''ATC700''', '''ATM700'''] devices with the '''[[ATC700_Product_Change_Notifications|latest assembly revision ]] | |||
</td> | |||
</tr> | </tr> | ||
<td style="text-align: left; color:#000000;"><strong>3.7.0-rc.22</strong></td> | |||
<td style="text-align: left;"> | <td style="text-align: left;">2025-01-16</td> | ||
<td style="text-align: left;"> | |||
'''FIXES/IMPROVEMENTS''' | |||
* Resolved issue where operator would be incorrectly banned after several attempts to open session | |||
* Resolved issue where DOUT2 or DOUT3 control would not work correctly after receiving setdigout or setdigout commands | |||
</td> | |||
</tr> | </tr> | ||
<td style="text-align: left; color:#000000;"><strong>3.7.0-rc.19</strong></td> | |||
<td style="text-align: left;">2025-12-19</td> | |||
<td style="text-align: left;"> | |||
'''HARDWARE SUPPORT''' | |||
* '''NEW''' Added support for '''ATC700_21''', '''ATM700_21''' hardware modifications | |||
'''NEW FEATURES''' | |||
* '''NEW''' '''[[FTC305_System#Power_saving_settings|Bluetooth MCU shutdown]]''' logic in sleep modes implemented | |||
* '''NEW''' '''[[FTC305_System#Power_saving_settings|CAN MCU shutdown]]''' logic in sleep modes implemented | |||
* '''NEW''' '''[[FTC305_Features#Immobilizer|Authorized iButton list for Immobilizer feature]]''' | |||
* '''NEW''' Added '''[[FTC305_Device_status#Pinout_selection|Software Defined Pins feature]]''' | |||
* '''NEW''' Added Manual CAN option for '''[[FTC305_System#Ignition_settings|Ignition]]''' and '''[[FTC305_System#Movement_settings|Movement]]''' Sources | |||
| | * '''NEW''' Added "Current LTE Band" I/O element | ||
* '''NEW''' Added logic to reconnect to the server immediately after server configuration change | |||
* '''NEW''' Added '''[[ATC700_System#Button_settings|User Button]]''' functionality for ['''ATC700''', '''ATM700'''] devices | |||
* '''NEW''' Added '''[[ATC700_System#Power_Bank_Support|Power Bank]]''' functionality for ['''ATC700''', '''ATM700'''] devices | |||
* '''NEW''' Added '''[[ATC700_System#Actions|Power Off via Button]]''' functionality for ['''ATC700''', '''ATM700'''] devices | |||
* '''NEW''' Added '''[[ATC700_Tracking_settings#Records_settings|GNSS fix search timeout]]''' parameter used after waking up from sleep for ['''ATC700''', '''ATM700'''] devices | |||
* '''NEW''' Added support for IMSI and ICCID reporting to FOTA | |||
* '''NEW''' Major version updated to '''3.7.0''' and downgrade protection added | |||
<!--->Country Blocking Service page does not have a category attached. The intended purpose is to provide more information on the functionality.<---> | |||
* '''NEW''' Conditions when device operation is prohibited updated, for more information please refer to '''[[Country Blocking Service]]''' | |||
'''FIXES/IMPROVEMENTS''' | |||
* Improved Instant Movement detection algorithm to more accurately represent status | |||
* Dynamic ground is now subtracted from IMU data used for Crash/Crash Trace scenarios | |||
* Implemented continuous parking vector updating using EMA filter to improve towing detection | |||
* Default Dead Reckoning alignment mode set to "Swift" mode | |||
* Resolved issue where operator would be incorrectly banned after several attempts to open session | |||
* Resolved issue where sleep timeout would not reset after receiving SMS | |||
* Resolved issue where movement would be detected for a short period of time after periodic wake-ups to send data in Power-Off Sleep mode | |||
* Resolved issue where DOUT2 and DOUT3 states would not be retained after waking up from Power-Off Sleep mode | |||
* Resolved issue where "Authorization persist duration" option could not be disabled via TCT | |||
* Resolved issue where device would sometimes wake up from Power-Off Sleep without valid wake-up reasons | |||
* Fixed status display of Immobilizer I/O element in TCT | |||
* Resolved issue where SIM card presence status would not update correctly in TCT | |||
* Network status is now updated immediately when SIM is removed | |||
* Resolved issue where Digital Output would not be disabled after timeout if device resets | |||
* Resolved issue where changing Charge Mode configuration would not take effect immediately | |||
* Resolved issue where removing SIM and inserting it back would prevent device from connecting to the network | |||
* Resolved issue where devices would not send High Priority records to server immediately when operating in Deep Sleep mode | |||
* Digital Output state is now saved in memory and retained after device restart | |||
* Improved Digital Output state control stability | |||
* Resolved issue where firmware update status was shown as failed in TCT even when update was successful | |||
* Improved battery detection algorithm for [FTX'''88X''', FTC'''96X''', FTX'''134'''] devices | |||
* Improved ban list functionality where operator-specific operator codes were not banned after 3 attempts as expected | |||
* Speed Jump filter implemented | |||
* Altitude Jump filter implemented | |||
* GNSS data filtering improvements | |||
* Resolved issue where advanced unplug detection generated an event without movement source for the first external voltage disconnection | |||
* Resolved issue where device in Online Sleep mode with Incoming Call feature failed to report last known position even though GNSS fix was available before entering sleep mode | |||
* Resolved issue where device goes to Power Off Sleep mode when connected to TCT via USB | |||
</td> | |||
</tr> | </tr> | ||
<td style="text-align: left; color:#000000;"><strong>3.0.8</strong></td> | |||
<td style="text-align: left;">2025-12-08</td> | |||
<td style="text-align: left;"> | |||
'''HARDWARE SUPPORT''' | |||
* '''NEW''' Added support for '''FTC134_32''', '''FTM134_32''' hardware modifications | |||
'''FIXES/IMPROVEMENTS''' | |||
* Fixed a compatibility issue for [FTX'''305''', FTX'''134'''] devices where software-defined pins (switch between DIN/AIN/1-Wire) were not initialized correctly after upgrading to newer firmware versions that support this feature | |||
* Fixed an issue where device current consumption increased when operating without cellular connectivity | |||
</td> | |||
</td> | |||
</tr> | |||
<tr> | <tr> | ||
<td style="text-align: left; color:#000000;"><strong> | <td style="text-align: left; color:#000000;"><strong>3.0.7</strong></td> | ||
<td style="text-align: left;"> | <td style="text-align: left;">2025-10-29</td> | ||
<td style="text-align: left;"> '''HARDWARE SUPPORT''' | |||
* '''NEW''' Removed support for '''FTM305_31''' hardware modification | |||
'''NEW FEATURES''' | |||
* '''NEW''' Dead-Reckoning functionality support for [FTXXX'''7'''] devices | |||
* '''NEW''' Teltonika EYE Sensors and Beacon support for [FTXXX'''4''', FTXXX'''5''', FTXXX'''7'''] devices | |||
* '''NEW''' Added Record Scheduler functionality | |||
* '''NEW''' Added "Time from last fix" I/O element | |||
* '''NEW''' Added accelerometer: "Axis X", "Axis Y", "Axis Z" I/O elements | |||
* '''NEW''' Added "Beacon Presence" I/O element | |||
* '''NEW''' Added Second Server funtionality | |||
* '''NEW''' Added Smart Ignition Detection functionality | |||
* '''NEW''' Added Ignition ON counter functionality | |||
* '''NEW''' Two-wheeler fall down detection functionality | |||
* '''NEW''' Added Inverted DOUT functionality | |||
* '''NEW''' Added DOUT extension for Network Jamming functionality | |||
* '''NEW''' Added DOUT recovery after overcurrent | |||
* '''NEW''' Added Location Based Service functionality | |||
* '''NEW''' Added eSIM Chip support | |||
* '''NEW''' Added Manual Geofence functionality | |||
'''FIXES/IMPROVEMENTS''' | |||
* Enhanced modem stability by ensuring recovery mechanism is triggered correctly after PDP context activation failure | |||
* Resolved issue where records stored in Retained RAM would get corrupted after firmware update, preventing the device from sending data | |||
* Improved handling of ambiguous PDP context states to ensure stable modem operation | |||
* Resolved issue with PDP context activation when the device had no AutoAPN file and the configured APN was not applied | |||
* Improved reliability of ExtMCU firmware updates | |||
* Improved deep sleep power consumption | |||
* Trip odometer IO initialization improvements | |||
* Fixed delays beetween server connections | |||
* Fixed authorized number input, by improving behaviour, when second digit is 0 | |||
* Resolved an issue that caused the sender task to hang during socket disconnection when the TCP/IP Server confirmation method was active and the open link timeout was reached after sending records | |||
* Improved modem update via FOTA WEB flow | |||
* General stability, connectivity and GNSS related improvements </td> | |||
</td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td style="text-align: left; color:#000000;"><strong>2. | <td style="text-align: left; color:#000000;"><strong>2.4.3</strong></td> | ||
<td style="text-align: left;"> | <td style="text-align: left;">2025-04-15</td> | ||
<td style="text-align: left;"> '''FIXES/IMPROVEMENTS''' | |||
* Manufacturing testing improvements | |||
</td> | |||
</td> | |||
</tr> | |||
</td> | |||
</tr> | </tr> | ||
<tr> | |||
</ | <td style="text-align: left; color:#000000;"><strong>2.4.0</strong></td> | ||
<td style="text-align: left;">2025-03-14</td> | |||
<td style="text-align: left;"> '''HARDWARE SUPPORT''' | |||
* '''NEW''' Added support for '''FTC305_31''', '''FTM305_31''' hardware modifications | |||
< | </td> | ||
</td> | |||
</tr> | |||
<tr> | <tr> | ||
< | <td style="text-align: left; color:#000000;"><strong>2.1.4</strong></td> | ||
<td style="text-align: left;">2025-07-21</td> | |||
< | <td style="text-align: left;"> '''HARDWARE SUPPORT''' | ||
< | |||
* '''NEW''' Added support for '''FTC880_24''', '''FTM880_12''', '''FTM880_24''', '''FTM880_02''', hardware modifications | |||
'''FIXES/IMPROVEMENTS''' | |||
* AutoAPN file upload in the factory | |||
* Added possibility to upload customer configuration files in factory | |||
* Manufacturing testing improvements | |||
*Fixed reversed logic in unplug detection feature | |||
</td> | |||
</tr> | |||
<tr> | |||
<tr> | |||
<td style="text-align: left; color:#000000;"><strong>2.1.1</strong></td> | <td style="text-align: left; color:#000000;"><strong>2.1.1</strong></td> | ||
<td style="text-align: left;">2025-06-04</td> | <td style="text-align: left;">2025-06-04</td> | ||
<td style="text-align: left;"> '''NEW FEATURES''' | <td style="text-align: left;"> '''HARDWARE SUPPORT''' | ||
* '''NEW''' Added support for '''FTC880_12''' and '''FTC961_23''' hardware modifications | |||
* '''NEW''' Hardware modifications '''FTC961_12''', '''FTC881_12''' no longer supported due to component change | |||
'''NEW FEATURES''' | |||
* '''NEW''' IPv6 protocol support | * '''NEW''' IPv6 protocol support | ||
| Line 124: | Line 458: | ||
* '''NEW''' Quectel BG95-M1 modem support | * '''NEW''' Quectel BG95-M1 modem support | ||
* '''NEW''' Quectel BG95-M3 modem support | |||
* '''NEW''' Custom scenarios feature | * '''NEW''' Custom scenarios feature | ||
| Line 136: | Line 472: | ||
* '''NEW''' Odometer feature | * '''NEW''' Odometer feature | ||
'''FIXES/IMPROVEMENTS''' | '''FIXES/IMPROVEMENTS''' | ||
| Line 163: | Line 498: | ||
* Fixed towing detection DOUT OFF time limits – now properly restricted to 0–5000 ms | * Fixed towing detection DOUT OFF time limits – now properly restricted to 0–5000 ms | ||
</td> | </td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
| Line 201: | Line 526: | ||
* '''NEW''' added Auto Geofence scenario | * '''NEW''' added Auto Geofence scenario | ||
'''FIXES/IMPROVEMENTS''' | '''FIXES/IMPROVEMENTS''' | ||
| Line 230: | Line 552: | ||
* Allow to turn on modem when USB cable and battery are connected | * Allow to turn on modem when USB cable and battery are connected | ||
</td> | </td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td style="text-align: left; color:#000000;"><strong>0.40.3 </strong></td> | <td style="text-align: left; color:#000000;"><strong>0.40.3</strong></td> | ||
<td style="text-align: left;">2024-08-01</td> | <td style="text-align: left;">2024-08-01</td> | ||
<td style="text-align: left;"> '''NEW FEATURES''' | <td style="text-align: left;"> '''NEW FEATURES''' | ||
| Line 268: | Line 590: | ||
* '''NEW''' added Device Live Status information feature | * '''NEW''' added Device Live Status information feature | ||
'''FIXES/IMPROVEMENTS''' | '''FIXES/IMPROVEMENTS''' | ||
| Line 307: | Line 628: | ||
* Modem init improved corrected when using roaming SIM. IMEI is now detected correctly.</td> | * Modem init improved corrected when using roaming SIM. IMEI is now detected correctly.</td> | ||
</td> | |||
</tr> | </tr> | ||
<tr> | |||
<td style="text-align: left; color:#000000;"><strong>0.26.2</strong></td> | |||
<td style="text-align: left;">2024-02-13</td> | <td style="text-align: left;">2024-02-13</td> | ||
<td style="text-align: left;"> '''NEW FEATURES''' | <td style="text-align: left;"> '''NEW FEATURES''' | ||
| Line 365: | Line 688: | ||
* '''NEW''' added the SMS "getver" | * '''NEW''' added the SMS "getver" | ||
'''FIXES/IMPROVEMENTS''' | '''FIXES/IMPROVEMENTS''' | ||
| Line 406: | Line 728: | ||
* Power management (sleep) improvements | * Power management (sleep) improvements | ||
* Subsequent connection to server failure timeout increase feature added | * Subsequent connection to server failure timeout increase feature added | ||
* DOUT stability improvements</td> | * DOUT stability improvements | ||
</td> | |||
</tr> | </tr> | ||
</table> | </table> | ||
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
|