Jump to content
  • EN

Template:FMX Professional Trackers Firmware Changelog: Difference between revisions

From Teltonika Telematics Wiki
← Older edit
VisualWikitext
No edit summary
No edit summary
 
(2 intermediate revisions by one other user not shown)
Line 4: Line 4:
===Introduction===
===Introduction===
We are always improving our devices 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 devices performance, stability and reliability. That’s why Teltonika is one of the leading GNSS trackers manufacturers in the world.<br />
This document describes '''FMC650''' devices firmware improvements, changes, new features implementations as well as current firmware release version.
This document describes '''FMC650''' 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 181: Line 182:
===Introduction===
===Introduction===
We are always improving our devices 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 devices performance, stability and reliability. That’s why Teltonika is one of the leading GNSS trackers manufacturers in the world.<br />
This document describes '''FMM650''' devices firmware improvements, changes, new features implementations as well as current firmware release version.
This document describes '''FMM650''' 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 326: Line 328:
=== Introduction ===
=== Introduction ===
We are always improving our devices 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 devices performance, stability and reliability. That’s why Teltonika is one of the leading GNSS trackers manufacturers in the world.<br />
This document describes '''FMBXXX, FMCXXX, FMUXXX, FMMXXX platform''' devices firmware improvements, changes, new features implementations as well as current firmware release version.
This document describes '''FMBXXX, FMCXXX, FMUXXX, FMMXXX 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/>


<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
Line 1,316: Line 1,319:
===Introduction===
===Introduction===
We are always improving our devices 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 devices performance, stability and reliability. That’s why Teltonika is one of the leading GNSS trackers manufacturers in the world.<br />
This document describes '''FMBXXX, FMCXXX, FMUXXX, FMMXXX platform''' devices firmware improvements, changes, new features implementations as well as current firmware release version.
This document describes '''FMBXXX, FMCXXX, FMUXXX, FMMXXX 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/>


<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
Line 1,754: Line 1,758:
===Introduction===
===Introduction===
We are always improving our devices 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 devices performance, stability and reliability. That’s why Teltonika is one of the leading GNSS trackers manufacturers in the world.<br />
This document describes '''FMCXXX, FMUXXX, FMMXXX platform''' devices firmware improvements, changes, new features implementations as well as current firmware release version.
This document describes '''FMCXXX, FMUXXX, FMMXXX 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/>
 
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<tr>
<tr>
Line 2,056: Line 2,062:
===Introduction===
===Introduction===
We are always improving our devices 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 devices performance, stability and reliability. That’s why Teltonika is one of the leading GNSS trackers manufacturers in the world.<br />
This document describes '''FMCXXX, FMUXXX, FMMXXX platform''' devices firmware improvements, changes, new features implementations as well as current firmware release version.
This document describes '''FMCXXX, FMUXXX, FMMXXX 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/>
 


<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
Line 2,363: Line 2,371:
| FMC234 =  
| FMC234 =  
===Introduction===
===Introduction===
We are always improving our devices performance, stability and reliability. That’s why Teltonika is one of the leading GNSS trackers manufacturers in the world.<br />This document describes '''FMCXXX, FMUXXX, FMMXXX platform''' devices firmware improvements, changes, new features implementations as well as current firmware release version.
We are always improving our devices performance, stability and reliability. That’s why Teltonika is one of the leading GNSS trackers manufacturers in the world.<br />This document describes '''FMCXXX, FMUXXX, FMMXXX 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/>
 


<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
Line 2,611: Line 2,621:


| FMC225 =  
| FMC225 =  
===Introduction===
We are always improving our devices performance, stability and reliability. That’s why Teltonika is one of the leading GNSS trackers manufacturers in the world.<br />
This document describes '''FMBXXX, FMCXXX, FMUXXX, FMMXXX 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/>


<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<tr>
<th style="width:20%; vertical-align: middle; text-align: center;">FIRMWARE VERSION</th>
<th style="width:20%; vertical-align: middle; text-align: center;"> </th>
<th style="width:60%; vertical-align: middle; text-align: center;">HARDWARE</th>
</tr>
<tr style="text-align: center; vertical-align: middle;">
<td style="vertical-align: middle">'''03.29.00.Rev.157'''</td>
<td style="vertical-align: middle"> </td>
<td style="text-align: left; vertical-align: top">FMB150, FMC150, FMM150, FMC250, FMM250</td>
</tr>
<tr style="text-align: center; vertical-align: middle;">
<td style="vertical-align: middle">'''03.29.00.Rev.932'''</td>
<td style="vertical-align: middle"> </td>
<td style="text-align: left; vertical-align: top">FMB965, FMB930</td>
</tr>
<tr style="text-align: center; vertical-align: middle;">
<td style="vertical-align: middle">'''03.29.00.Rev.554'''</td>
<td style="vertical-align: middle"> </td>
<td style="text-align: left; vertical-align: top">FMP100, FMB020</td>
</tr>
<tr style="text-align: center; vertical-align: middle;">
<td style="vertical-align: middle">'''03.29.00.Rev.263'''</td>
<td style="vertical-align: middle"> </td>
<td style="text-align: left; vertical-align: top">FMB209</td>
</tr>
</table>
===Firmware versioning===
*Structure
FMB(T).VER.[<code>XX</code>].[<code>YY</code>].[<code>ZZ</code>].Rev.[<code>##</code>] _[<code>ID###</code>]
*Syntax description
**<code>XX</code> – major FW version.
**<code>YY</code> – branch number, shows major changes in firmware, i.e. new module support added or new major feature added.
**<code>ZZ</code> – major changes like bigger fixes, improvements and new features addition.
**<code>##</code> – minor changes like small fixes and improvements.
**<code>ID[###]</code> – Spec ID KEY – Specific clients FW changes.
===Firmware versions===
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<tr>
<th style="width:20%; vertical-align: middle; text-align: center;">FIRMWARE VERSION</th>
<th style="width:20%; vertical-align: middle; text-align: center;">RELEASE DATE</th>
<th style="width:60%; vertical-align: middle; text-align: center;">CHANGES</th>
</tr>
<tr style="text-align: center; vertical-align: middle;">
<td style="vertical-align: middle">'''04.00.00.Rev.14'''<br /> (recommended for FMC920, FMC880, FMC800)</td>
<td style="vertical-align: middle">2025.07.01</td>
<td style="text-align: left; vertical-align: top">
* Corrected an issue in the factory test procedure where the modem on Quectel EG915U-based devices failed to recover the correct baud rate, causing delayed startup
</td>
</tr>
<tr style="text-align: center; vertical-align: middle;">
<td style="vertical-align: middle">'''04.00.00.Rev.13'''<br /> (recommended for FMB900, FMB910, FMB920, FMC920, FMM920, FMT100, FMC880 (Quectel EG915U-EU), FMM880, FMC800, FMM800, FMB110, FMB120, FMB130, FMB202, FMB204, FMB230, FMC130 (MeiG SLM320-PE2C, SLM320-PE2H, SLM320-L16A, SLM320-L16B), FMC230, FMC234, FMM130 (Quectel BG95-M3), FMM230, FMB125, FMC125 (MeiG SLM320-PE2C, SLM320-PE2H, SLM320-L16A, SLM320-L16B), FMC225, FMB140)</td>
<td style="vertical-align: middle">2025.05.26</td>
<td style="text-align: left; vertical-align: top">
* '''NEW!''' <span style="color: yellow;">[[Major_version_update_to_4.0.0|Major version updated to 4.0.0 and downgrade protection added]]</span>
* '''NEW!''' Added support for [[FMC880|FMC880]], [[FMM880|FMM880]]
* '''NEW!''' Added support for [[FMC800|FMC800]], [[FMM880|FMM800]], [[FMM80A|FMM80A]]
* '''NEW!''' Added support for [[FMC234|FMC234]]
* '''NEW!''' Modem recovery mechanism to address modem hangs resulting from network issues or poor signal conditions
* '''NEW!''' Implemented support for encrypted CAN commands over Bluetooth
* '''NEW!''' Enhanced “Advanced Unplug Detection” with additional condition options for speed and delay
* '''NEW!''' Added Beacon option for “Authorized Read Notification” feature
* '''NEW!''' Added Dynamic Ground vector feature for more accurate accelerometer data
* '''NEW!''' Added “Window state” security state flag elements
* '''NEW!''' Enabled devices to send records to a duplicate server via TCP in Codec JSON, while the primary server uses MQTT with TLS encryption
* '''NEW!''' Enabled “Driving state” and “Driving records” I/O elements for FMC880/FMM880 devices
* '''NEW!''' Added a DIN3 option as a trigger for outgoing calls in HF settings
* '''NEW!''' Added "set calibration" command
* '''NEW!''' Added a new GNSS I/O status value '4' - GNSS ON with an active GNSS filter.
* '''NEW!''' “Stay Awake” parameter option added for “Sleep Mode”
* '''NEW!''' “DTC Request on Engine Start” feature to avoid conflicts with external diagnostic equipment
* '''NEW!''' Added support of PCB temperature I/O element for devices with NTC
* '''NEW!''' Added support for TCP BIN/ASCII data forwarding in JSON CODEC format
* '''CHANGED!''' Default logging filters updated
* '''CHANGED!''' Unplug detection events are allowed to be sent before device going to Low Power Mode
* '''CHANGED!''' Adjusted accelerometer sensitivity to be more suitable for crash detection
* '''CHANGED!''' Set GNSS jamming DOUT control to a higher priority over maintenance DOUT
* '''CHANGED!''' Modifications to calibration algorithm for greater accuracy
* '''CHANGED!''' BLE Advertising period changed to 500 ms
* '''CHANGED!''' Refactored the Immobilizer Authorized ID checking feature
* '''CHANGED!''' Conditions when device operation is prohibited updated
* '''CHANGED!''' Adjusted the operator ban list logic to have a search timeout of 5 minutes and a ban time of 30 minutes
* '''CHANGED!''' Incremental retry periods for AGPS EPO download to improve successful download time period
* '''CHANGED!''' Program number parameter ID 11120 size increased and max value to 99999
* '''CHANGED!''' Additional traces for GPS and GSM jamming status in device log
* '''CHANGED!''' Enabled band 26 selection for devices equipped with Quectel BG95-M3 modems
* Adjusted battery percentage table for FMC234
* Corrected the limit connections management in Low Power Mode
* Resolved issue where MCC calculation was done incorrectly forcing device to enter blocked state
* DualSIM switching process speed adjusted for devices with MeiG modems
* Improved socket status reading for BG9X modems to correcly handle data sending if socket is closed
* Corrected the byte inversion issue in 1-Wire Matrix (ReadROM) ID parsing
* Device abnormal working with dynamic bt name when using value of 16 characters with %imei function resolved
* Addressed issues where the device behaved abnormally after receiving a #FWD DAT command with the target set to Bluetooth and a NULL payload
* Fine-tuned the parsing for start and end delimiters in RS232 Delimiter mode to enhance functionality
* Fixed an issue where high priority records were not sent if a call was triggered by a feature activation
* Resolved an issue where link was not close properly sometimes after sending a record in Low Power Mode
* Enhanced the retry mechanism for SIM PIN entries if the initial attempt was unsuccessful
* Adjusted the saving of the Digital Output state post-firmware update when the inverted mode is selected
* Enabled missing CAN RSF parameters
* Resolved unexpected wake-ups from sleep due to repeated time-sync issues and server failures to close sockets correctly
* Patched the fail count algorithm for 1-wire data reading to improve stability
* Disallowed GSM updates during server response wait periods to prevent duplicate record sending in online deep sleep mode
* Removed disallowed MCCs (250, 257, 432, 368, 467) from the APN list
* Improved parsing of VIN and Trailer VIN values
* Resolved EYE Sensor filtering issue by MAC or Name when configuration parameter “Identifier” was changed
* Resolved an issue where UL202 record value was incorrectly parsed in device logs
* Changed the BLE advanced data offset type to signed to correct inaccuracies when negative offsets were used
* Updated the DOUT control from the Ignition FSM to prevent feature bypass when switching ignition on and off within 1 second
* Adjusted the conversion of EYE "Major" and "Minor" values, ensuring data is packed according to Bigger Endian format when "Lost&Found" record are generated
* Corrected a typographical error in the lvcangetinfo response
* Resolved an issue where the device was unable to enter sleep mode due to an NTP sync being stuck
* Fixed an issue where the first GPRS command was ignored after the device connected to a Backup Server
* Resolved an issue where DTC fault codes were not correctly packed into records for some EV and Hybrid vehicles
* Improved SIM switch logic in devices equipped with Quectel modems
* Removed an unnecessary filter for the instant movement element status
* Resolved an issue where private/business mode was not functioning according to the weekly schedule
* Improved device stability when NMEA logging is enabled via RS232 at 9600 baud
* Enhanced device stability when a 2kHz signal is detected by the device using "Advanced Pulse Counter" feature
* Resolved an issue where 2G devices could not open a socket for a period after disconnecting from the network due to poor network conditions
* Resolved an issue where duplicate records were created if UART communication with the modem stopped working while the device was in GNSS/ODS sleep mode and USB was connected
* Improved the handling of the socket closing for devices with MeiG modules when TLS and Deep Sleep are used
* Improved the stability of OBD dongle data reading after a Bluetooth module restart
* Resolved an issue where the device would sometimes fully wake up from Deep Sleep due to periodic record sending
* Resolved an issue where the "Advanced Pulse Counter" parameter ID 145 would not reset to default settings via configurator
* Resolved an issue where EYE Beacon flag 27 data voltage and temperature values was not included not into record when "Beacon Simple" mode was used
* Improved the accuracy of device tracking location in "Low Power Mode"
* Resolved an issue where the getinfo response was split into several SMS messages
* Improved device stability when Private Mode is triggered by Virtual DIN2
* Resolved an issue where firmware downloads would interrupt frequent record sending for devices with MeiG modules
* EYE sensors status are now shown correctly in device logs
* Resolved an issue where on random cases, a trip end event was received with the trip odometer already reset to 0
* Adjusted so that the movement off timeout would not reset after device restart
* Disabled unnecessary tasks to decrease current consumption in UDS mode
* Resolved an issue where the WD counter was not functioning as expected in ODS mode
* Reduced the delay for Immobilizer activation after waking up from sleep
* Resolved an issue where the GNSS module would not return to operation after being jammed
* Resolved an issue where the program number could not be changed sometimes with an SMS command
* Applied a patch to support APDU commands, preventing connectivity issues when the device uses specific SIMs and crosses borders
* Ensured odometer values are saved after a fix loss to prevent resetting when the device powers off
* Applied a patch so that timestamps in crash traces are calculated relative to the crash event, preventing trace damage if a time jump occurs during a crash
* Applied a patch to improve Bluetooth interface stability when detecting a large number of Beacons
* Resolved an issue where the "On-Demand Tracking", "Activation By" parameter ID 10992 would not reset to default via configurator
* Resolved an issue where EYE sensor I/O values would be included in the record even if the "Working Mode" parameter was configured as "Disabled"
* Movement will be accurately detected after the movement detection delay period, and not simultaneously with towing detection when it is activated
* Resolved an issue where the Immobilizer would not retrigger the Digital output immediately if the ignition was turned on for shorter than 1 second
* Adjusted the btgetlist 3 command to return a full scanned object list
* Resolved an issue where the "Odometer Calculation Source" parameter ID 11806 did not reset back to the default value when the configuration was reset
* Resolved an issue where Beacon info remained visible in the configurator UI even when detection was disabled
* Resolved an issue where the TTFF (Time to First Fix) result was sometimes reported as 0 even though a fix was acquired
* Resolved an issue where the Digital Output was not activated by the "Immobilizer" scenario when the "Ignition Off timeout" was set to longer than the "Sleep Timeout"
* Implemented a minor interface control tweak for 1-wire interface stability
* Removed unnecessary spam from device log prints
* Corrected the behavior to stop advertising BLE packets once a connection is established
* Resolved an issue where the device's 1-Wire interface functioned incorrectly if the 1-Wire in Sleep mode parameter value changed while the device was in sleep mode
* Resolved an issue where fake movement was detected due to incorrect GNSS speed data acquired from the GNSS module
* Tweaked the BLE GATTS disconnect process to enable correct disconnection
* Resolved an issue where devices in Deep Sleep mode would sometimes fail to report the disconnected status using MQTT
* Resolved an issue where devices with MeiG modules would repeat a call after the first one was rejected
* Resolved an issue where the Authorization ID List check by Beacon could not be configured for FMX1XY devices
* Inverted DOUT state no longer resets after a soft reset
* Resolved an issue where movement delay was not resetting correctly if the movement state changed
* Device external module startup time improved when waking from ODS
* Resolved an issue where logging to dump would stop after a soft reset.
* Resolved an issue where the FMX880 device would lose fix for a short amount of time
* Adjusted Watchdog behavior when the device is still connected to a network operator
* Beacon record generation now properly waits for the Bluetooth stabilization period
* Resolved an issue where devices with a Quectel module would save an incorrect timestamp when waking from GNSS sleep mode
* Resolved an issue where entering the Features paragraph in the configurator sets a new value for parameter 11703
* SIM detection and reading time improved for devices with Quectel BG95-M3 modules
* Improved battery percentage reading for FMB204 devices
* Adjusted communication with AG3335 to fix issues where FMX880 devices would sometimes take a longer period to acquire a GNSS fix
* Resolved an issue where the modem was not starting as expected when the device initiated record sending in Low Power mode
</td>
</tr>
<tr style="text-align: center; vertical-align: middle;">
<td style="vertical-align: middle">'''03.29.00.Rev.21'''<br /> (recommended for FMB122, FMB125, FMM125, FMC125 (SLM320-LA, SLM320-E2, EC21-EC), FMC225, FMC920)</td>
<td style="vertical-align: middle">2024.08.07</td>
<td style="text-align: left; vertical-align: top">
* Optimized the startup process of the network modules to improve pass-rate during manufacturing testing.
* Dual SIM switching enhancements to improve pass-rate during manufacturing testing.
* Return real SIM slot for factory testing commands.
</td>
</tr>
<tr style="text-align: center; vertical-align: middle;">
<td style="vertical-align: middle">'''03.29.00.Rev.18'''<br /> (recommended for FMT100, FMB900, FMB910, FMB920, FMC920, FMM920, FMB110, FMB120, FMB122, FMB130, FMC130 (SLM320-LA, SLM320-E2, EC21-EC, EC21-AU), FMC13A, FMM130 (BG95-M3, BG96), FMM13A, FMB202, FMB204, FMB206, FMB230, FMC230, FMM230, FMB140, FMB240, FMB125, FMC125 (SLM320-LA, SLM320-E2, EC21-EC), FMM125 (BG95-M3), FMB225, FMC225)</td>
<td style="vertical-align: middle">2024.05.13</td>
<td style="text-align: left; vertical-align: top">
* Improved reconnection to new operator time if GPRS was unavailable with initial operator
* Fixed pro-longed reconnection to new operator due to record tasks interrupting operator search
* Fixed network session closing when current operator is added to blacklist
* Improved module initialization time for devices with Quectel modems
* Fixed Digital Output state restore after firmware update
* RS232 interface stability improvements
* GNSS status element state improvements
* Time synchronization improvements
* Manufacture testing improvements
</td>
</tr>
<tr style="text-align: center; vertical-align: middle;">
<td style="vertical-align: middle">'''03.29.00.Rev.14'''<br /> (recommended for FMB120, FMB130, FMB140, FMB125, FMM130 with BG95-M3, FMM230, FMB920, FMT100, FMB910, FMB204, FMC125 with MeiG SLM320, FMC225, FMC13A)</td>
<td style="vertical-align: middle">2023.12.13</td>
<td style="text-align: left; vertical-align: top">
* '''NEW!''' '''[[EYE_SENSOR_/_BTSMP1#Teltonika_configurator_new_functionalities_.28Evaluation_firmware_.2F_EYE_Sensor_filtering_by_name.29|TELTONIKA EYE Beacon and EYE Sensor easy configuration]]''' functionalities added
* '''NEW!''' '''[[EYE_SENSOR_/_BTSMP1#Teltonika_configurator_new_functionalities_.28Evaluation_firmware_.2F_EYE_Sensor_filtering_by_name.29|TELTONIKA EYE Beacon Lost & Found and Proximity Event]]''' functionalities added
* '''NEW!''' '''[[Secure_vehicle_disabling|SECO]]''' functionality added
* '''NEW!''' '''[[{{{name|}}}_Bluetooth_4.0_settings#Backup_Tracker|Back-Up Tracker]]''' functionality added
* '''NEW!''' '''[[{{{name|}}}_Features_settings#GNSS_Jamming|GNSS jamming]]''' functionality added
* '''NEW!''' '''[[{{{name|}}}_System_settings#Low_Power_Mode|Low Power Mode]]''' functionality added
* '''NEW!''' MQTT support for '''[[Getting_Started_with_AWS_IoT_Core|AWS IoT Shadow/Custom]]''' and '''[[Getting_started_with_Azure_IoT_hub|Azure IoT]]''' added
* '''NEW!''' '''[[FMC125_RS-232_and_RS-485|RS485 Buffered]]''' functionality added
* '''NEW!''' '''[[FMC125_RS-232_and_RS-485|RS232 Delimiter mode]]''' functionality added
* '''NEW!''' '''[[{{{name|}}}_System_settings#The_1-wire_enabled_in_DS_and_ODS|1-Wire interface control in sleep modes]]''' functionality added
* '''NEW!''' '''[[{{{name|}}}_System_settings#BT.2FBLE_module_OFF_during_Sleep_modes|BT/BLE interface control in sleep modes]]''' functionality added
* '''NEW!''' '''[[NBL-2|NBL-2 Bluetooth RFID reader]]''' support added
* '''NEW!''' SMS/GPRS command '''[[FMB_lvcanhorn|"lvcanhorn"]]''' support added
* '''NEW!''' Added support for '''[[FMC13A|FMC13A]]''' and '''[[FMM13A|FMM13A]]'''
* '''NEW!''' Added support for '''[[FMC00A|FMC00A]]''' and '''[[FMM00A|FMM00A]]'''
* '''NEW!''' Added support for '''[[FMC920|FMC920]]''' and '''[[FMM920|FMM920]]'''
* '''NEW!''' Added support for '''[[FMC003|FMC003]]''' and '''[[FMM003|FMM003]]'''
* '''NEW!''' Added support for small OBD devices '''[[FMB003|FMB003]]''' and '''[[FMB020|FMB020]]'''
* '''NEW!''' Added support for FMC1XY/FMC2XY devices with MeiG modems
* '''NEW!''' SMS/GPRS command '''[[FMB_setigndigout|"setigndigout"]]''' added
* '''NEW!''' Jamming feature support added for FMC1XY/FMC2XY devices with MeiG modems
* '''NEW!''' Support of new electric vehicle '''[[{{{name|}}}_Parameter_list#OBD_II_.28Bluetooth.29|OEM parameters]]''' for FMX00X devices
* '''NEW!''' '''[[{{{name|}}}_Parameter_list#LVCAN|CAN service and LPG I/O elements]]''' added
* '''NEW!''' New I/O elements for each CAN adapter state flag added
* '''NEW!''' New I/O Digital Input 2 for FMX920, FMB910 and FMB900 devices
* '''CHANGED!''' Reworked recalibration logic
* '''CHANGED!''' '''[[Parameters_Update|Default parameter values]]'''
* '''CHANGED!''' '''[[{{{name|}}}_SMS_events|SMS Event]]''' logic reworked
* '''CHANGED!''' '''[[FMC125_RS-232_and_RS-485#LLS_mode|LLS address]]''' count expanded to 16
* '''CHANGED!''' Black list functionality reworked
* '''CHANGED!''' SMS/GPRS command '''[[FMB_cpureset|"cpureset"]]''' protection functionality
* '''CHANGED!''' '''[[Advanced_Pulse_Counter|Pulse Counter]]''' reworked
* 1-Wire Temperature sensor stability improvements
* Operator search procedure functionality improvements
* Record saving and sending improvements
* DOUT state saving improvements
* GPRS Session and PDP Context Activation logic improvements
* Trip state saving improvements
* CAN data reading improvements
* BLE data reading stability improvements
* TimeSync, SMS handling and connection stability improvements for FMC1XY/FMC2XY devices with MeiG modems
* AutoAPN multiple block file improvement for larger database capacity
* Manufacture testing improvements
* Improved system stability and fixed general bugs
</td>
</tr>
<tr style="text-align: center; vertical-align: middle;">
<td style="vertical-align: middle">'''03.27.13.Rev.443'''<br /> (recommended for FMC225 with SLM320-LA, SLM320-E2)</td>
<td style="vertical-align: middle">2023.03.14</td>
<td style="text-align: left; vertical-align: top">
*Fixed eSIM detection with SLM320 modules
*Improved SMS handling with SLM320 modules
*Fixed known issues with GPS jumps and time synchronization
*Improved PAP/CHAP authentication
*Fixed duplicate server issue when one of server is closed
*Improved communication with SLM320 module to ensure stable connection
*Improved system stability and fixed general bugs
</td>
</tr>
<tr style="text-align: center; vertical-align: middle;">
<td style="vertical-align: middle">'''03.27.13.Rev.03'''<br /> (recommended for FMB230, FMB225, FMB240, FMM230)</td>
<td style="vertical-align: middle">2022.09.12</td>
<td style="text-align: left; vertical-align: top">
* Improved system stability and fixed general bugs
* Manufacture testing improvements
</td>
</tr>
<tr style="text-align: center; vertical-align: middle;">
<td style="vertical-align: middle">'''03.27.13.Rev.57'''<br /> (recommended for FMC225)</td>
<td style="vertical-align: middle">2022.05.11</td>
<td style="text-align: left; vertical-align: top">
*Added SMS via LTE support for hardware`s with SLM320 modules
*Added [[FMC225_Features_settings#Jamming| '''Jamming support''']] for FMC225 hardware
*Fixed NITZ time synchronization with SLM320 modules
*Fixed connection to operator issue
*Improved system stability and fixed general bugs
</td>
</tr>
<tr style="text-align: center; vertical-align: middle;">
<td style="vertical-align: middle">'''03.27.12.Rev.00'''<br /> (recommended for FMM230, FMB230, FMB225, FMB240)</td>
<td style="vertical-align: middle">2022.02.17</td>
<td style="text-align: left; vertical-align: top">
*Added FMM230, FMC230, FMC225, FMB230, FMB225, FMB240 support
*Fixed manual frequency bands configuration for FMMx30 devices
*Improved system stability and fixed general bugs
</td>
</tr>
</table>
}}
}}


[[Category:{{{model}}}]]
[[Category:{{{model}}}]]

Latest revision as of 14:36, 11 November 2025


[[Category:{{{model}}}]]

Retrieved from "https://wiki.teltonika-gps.com/index.php?title=Template:FMX_Professional_Trackers_Firmware_Changelog&oldid=108852"