Jump to content

TEST-X: Difference between revisions

From Teltonika Telematics Wiki
No edit summary
FMC650 PCN v2 final
 
(206 intermediate revisions by the same user not shown)
Line 1: Line 1:
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
== 2026.06.04: Firmware update safety mechanism in FOTA Web ==
<tr>
<th style="width:1%; vertical-align: middle; text-align: center;">PARAMETER NAME</th>
<th style="width:1%; vertical-align: middle; text-align: center;">PARAMETER ID (RELATED AVL ID)</th>
<th style="width:5%; vertical-align: middle; text-align: center;">DESCRIPTION</th>
<th style="width:6%; vertical-align: middle; text-align: center;">VALUES</th>
</tr>
<tr>


<td style="vertical-align: middle; text-align: center;"> Immobilizer </td>
We would like to inform you about an upcoming improvement in the FOTA WEB system, designed to enhance the safety and reliability of firmware updates for the devices. 
<td style="vertical-align: middle; text-align: center;"> 11700 </td>
<td style="vertical-align: middle; text-align: center;"> Disables, or enables and sets priority of the event record generated upon successful or failed authorization attempts.Authorization source </td>
<td style="vertical-align: middle; text-align: left;"> '''0 =''' Disable scenario. <br>
'''1 =''' Low priority Device makes an additional record with indication of event cause. </td>
</tr>
<tr>


<td style="vertical-align: middle; text-align: center;"> Authorization source </td>
{| class="wikitable"
<td style="vertical-align: middle; text-align: center;"> 11703 </td>
|+
<td style="vertical-align: middle; text-align: center;"> Selects the type of authorization element to be used. </td>
! colspan="3" style="text-align: left; background: white;" |Change description
<td style="vertical-align: middle; text-align: left;"> '''0 =''' No authorization selected. <br>  
|-
'''1 =''' 1-Wire authorization selected.
| style="text-align: left; background: white;" |Change type
</td>
| colspan="2" style="text-align: left; background: white;" | Firmware update safety mechanism
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |We are introducing a new safety mechanism in FOTA WEB that prevents firmware updates from being executed on devices running an outdated bootloader version and in this case the firmware update task won’t be possible. This helps eliminate the risk of device malfunction during update procedures.
|-
| style="text-align: left; background: white;" |'''Required bootloader version:'''<br>Minimum required: 65.0E (displayed as 101.14 in FOTA Web).<br>Devices with an older version must first apply a bootloader patch before updating to newer firmware.
| style="text-align: left; background: white;" |'''Recommended update path:'''<br>Any firmware → FM65.Ver.03.01.00.Rev.28 → (if required) FM65.Ver.03.01.00.Rev.34_1666 → FM65.Ver.03.01.01.Rev.15 or newer
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" | Certain newer firmware versions, such as FM65.Ver.03.01.01.Rev.15 and later, exceed 1 MB in size. Devices with older bootloader versions may not support these updates safely. The new mechanism ensures that such updates are only performed when the device meets the required bootloader conditions.
|-
| style="text-align: left; background: white;" |Safety mechanism launch date
| colspan="2" style="text-align: left; background: white;" |Jun 15, 2026
|-
|}


</tr>
{| class="wikitable"
<tr>
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMC650
| style="text-align: left; background: white;" |All order codes
| style="text-align: left; background: white;" |-
|-
|}


<td style="vertical-align: middle; text-align: center;"> Ignition OFF timeout (s) </td>
{| class="wikitable"
<td style="vertical-align: middle; text-align: center;"> 60068 </td>
|+
<td style="vertical-align: middle; text-align: center;"> Sets the time in seconds after the ignition is turned off before the driver's authorization is automatically revoked. </td>
! colspan="3" style="text-align: left; background: white;" |Change impact
<td style="vertical-align: middle; text-align: left;"> Minimum value '''= 1''' <br>
|-
Maximum value '''= 65535''' </td>
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |The bootloader patch firmware (Rev.34_1666) is an intermediate step and not a full firmware version. Using it as a standalone firmware may lead to limited functionality or unexpected behavior.


</tr>
Starting from version 03.01.00.Rev.28, devices automatically block firmware updates if the bootloader is too old. This protection significantly reduces the risk of bricking.
<tr>
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |Only a limited number of devices require a bootloader update. We recommend avoiding unnecessary bootloader updates. To ensure a smooth and safe firmware update process, please follow the recommended update path sequence provided in the Change description.
|-
|}


<td style="vertical-align: middle; text-align: center;"> Eventual records </td>
{| class="wikitable"
<td style="vertical-align: middle; text-align: center;"> 11701</td>
|+
<td style="vertical-align: middle; text-align: center;"> Enables feature status sending only when the event happens (an eventual record). When disabled, feature status will be sent with both eventual and periodical records. </td>
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
<td style="vertical-align: middle; text-align: left;"> '''0''' = Disable <br>
|-
'''1''' = Enable </td>
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
 
|-
</tr>
|}
<tr>
 
<td style="vertical-align: middle; text-align: center;"> Bypass authorization </td>
<td style="vertical-align: middle; text-align: center;"> 11029</td>
<td style="vertical-align: middle; text-align: center;"> Allows to bypass authorization when ignition is turned on and a duration expires. </td>
<td style="vertical-align: middle; text-align: left;"> '''0 =''' Disabled
'''0-65535 =''' Enabled  </td>
 
</tr>
<tr>
 
<td style="vertical-align: middle; text-align: center;"> Bypass authorization timeout (s) </td>
<td style="vertical-align: middle; text-align: center;"> 11029</td>
<td style="vertical-align: middle; text-align: center;"> Sets duration which starts when ignition is turned on. When duration expires immobilizer is turned off, even if the user was not authenticated. </td>
<td style="vertical-align: middle; text-align: left;"> Minimum value '''= 1''' <br>
Maximum value '''= 65535''' </td>
 
</tr>
<tr>
 
<td style="vertical-align: middle; text-align: center;"> Output control </td>
<td style="vertical-align: middle; text-align: center;"> 65535</td>
<td style="vertical-align: middle; text-align: center;"> Selects which Digital Output is used to control the immobilizer relay. </td>
<td style="vertical-align: middle; text-align: left;"> '''0 =''' None DOUTs are disabled in this scenario. <br>
'''1 =''' DOUT1 DOUT1 is enabled in this scenario. <br>
'''2 =''' DOUT2 DOUT2 is enabled in this scenario. <br>
'''3 =''' DOUT3 DOUT3 is enabled in this scenario. </td>
 
</tr>
</table>

Latest revision as of 12:08, 2 June 2026

2026.06.04: Firmware update safety mechanism in FOTA Web

We would like to inform you about an upcoming improvement in the FOTA WEB system, designed to enhance the safety and reliability of firmware updates for the devices. 

Change description
Change type Firmware update safety mechanism
Detailed description We are introducing a new safety mechanism in FOTA WEB that prevents firmware updates from being executed on devices running an outdated bootloader version and in this case the firmware update task won’t be possible. This helps eliminate the risk of device malfunction during update procedures.
Required bootloader version:
Minimum required: 65.0E (displayed as 101.14 in FOTA Web).
Devices with an older version must first apply a bootloader patch before updating to newer firmware.
Recommended update path:
Any firmware → FM65.Ver.03.01.00.Rev.28 → (if required) FM65.Ver.03.01.00.Rev.34_1666 → FM65.Ver.03.01.01.Rev.15 or newer
Change reasons Certain newer firmware versions, such as FM65.Ver.03.01.01.Rev.15 and later, exceed 1 MB in size. Devices with older bootloader versions may not support these updates safely. The new mechanism ensures that such updates are only performed when the device meets the required bootloader conditions.
Safety mechanism launch date Jun 15, 2026
Affected products
Model Affected order codes Order code changes
FMC650 All order codes -
Change impact
Risk assessment The bootloader patch firmware (Rev.34_1666) is an intermediate step and not a full firmware version. Using it as a standalone firmware may lead to limited functionality or unexpected behavior.

Starting from version 03.01.00.Rev.28, devices automatically block firmware updates if the bootloader is too old. This protection significantly reduces the risk of bricking.

Suggested implementation plan Only a limited number of devices require a bootloader update. We recommend avoiding unnecessary bootloader updates. To ensure a smooth and safe firmware update process, please follow the recommended update path sequence provided in the Change description.
Acknowledgement of PCN receipt
If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above