User:Jonas.kazlauskas/FTC305 Firmware Changelog demo

FTC305 Firmware Changelog

Latest firmware for FTC305: 3.7.1
The version history below is filtered to firmware that supports FTC305 (newest first). For the officially recommended & factory versions, see the Firmware Versions page.

Firmware versioning

Structure: [XX].[YY].[ZZ] — XX major / backward-incompatible change, YY new features or module support, ZZ fixes.

Version history

FIRMWARE VERSION	RELEASE DATE	CHANGES
3.7.1	2026-05-12	FIXES/IMPROVEMENTS Resolved issue where Modem status LED remained active when transitioning from Online Sleep to Critical Sleep Resolved an issue where BG95-based devices would sometimes could stop sending records during operation in Deep Sleep due to incorrect state handling
3.7.0	2026-04-27	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 | Standby Mode support for [FTXXX7], [FTXXX8] 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
3.0.10	2026-03-02	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
3.7.0-rc.25 RC	2026-02-05	FIXES/IMPROVEMENTS Improved LED brightness control for [ATC700, ATM700] devices with the latest assembly revision
3.7.0-rc.22 RC	2025-01-16	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
3.7.0-rc.19 RC	2025-12-19	HARDWARE SUPPORT NEW Added support for ATC700_21, ATM700_21 hardware modifications NEW FEATURES NEW Bluetooth MCU shutdown logic in sleep modes implemented NEW CAN MCU shutdown logic in sleep modes implemented NEW Authorized iButton list for Immobilizer feature NEW Added Software Defined Pins feature NEW Added Manual CAN option for Ignition and 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 User Button functionality for [ATC700, ATM700] devices NEW Added Power Bank functionality for [ATC700, ATM700] devices NEW Added Power Off via Button functionality for [ATC700, ATM700] devices NEW Added 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 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 [FTX88X, FTC96X, FTX134] 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
3.0.8	2025-12-08	HARDWARE SUPPORT NEW Added support for FTC134_32, FTM134_32 hardware modifications FIXES/IMPROVEMENTS Fixed a compatibility issue for [FTX305, FTX134] 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
3.0.7	2025-10-29	HARDWARE SUPPORT NEW Removed support for FTM305_31 hardware modification NEW FEATURES NEW Dead-Reckoning functionality support for [FTXXX7] devices NEW Teltonika EYE Sensors and Beacon support for [FTXXX4, FTXXX5, FTXXX7] 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
2.4.3	2025-04-15	FIXES/IMPROVEMENTS Manufacturing testing improvements
2.4.0	2025-03-14	HARDWARE SUPPORT NEW Added support for FTC305_31, FTM305_31 hardware modifications

Showing all firmware versions supported on FTC305, newest first. Pre-release and side-branch builds are tagged.