Jump to content

TEST-T: Difference between revisions

From Teltonika Telematics Wiki
Tag: Reverted
No edit summary
 
(64 intermediate revisions by the same user not shown)
Line 1: Line 1:
==2026.02: Base firmware update==
== Race mode ==
We would like to inform you about the base firmware update for {{{model}}} starting from '''February, 2026''', starting with batch 4. Other existing features are not impacted.
[[File:ATX Race mode.png|thumb|right|500px]]
<div>
<table class="wikitable" style="background-color: white;">
<tr>
<th colspan="3" style="text-align: left;">Change description</th>
</tr>
<tr>
<td style="text-align: left;">Change type</td>
<td colspan="2" style="text-align: left;">Firmware update</td>
</tr>
<tr>
<td rowspan="2" style="width: 221px; text-align: left;">Detailed description</td>
<td colspan="2" style="width: 908px; text-align: left;">
Optimized LED brightness through firmware changes. Note that this is only applicable to newly manufactured devices, starting with batch 4. Other existing features are not impacted.<br>
Hardware assembly change. Component change to optimize LED performance. Note that this is only applicable to newly manufactured devices, starting with batch 4. Existing features are not impacted. <br>
    Key improvements from last production firmware are listed in [[{{{model}}} Firmware Changelog]]</td>
</tr>
<tr>
<td style="text-align: left;">Old version: <br> 3.7.0-rc.19</td>
<td style="text-align: left;">New version: <br> 3.7.0-rc.25</td>
</tr>
<tr>
<td style="text-align: left;">Change reasons</td>
<td colspan="2" style="text-align: left;">{{{model}}} base firmware version update</td>
</tr>
<tr>
<td style="text-align: left;">Product release date</td>
<td colspan="2" style="text-align: left;">2026 February</td>
</tr>
</table>


<table class="wikitable" style="background-color: white;">
Race Mode is an accuracy focused operating mode that controls periodic record timestamps strictly by GPS time (NMEA). It is designed to improve timestamp precision and prevent unexpected coordinate jumps during movement.
<tr>
<th colspan="3" style="text-align: left;">Affected products</th>
</tr>
<tr>
<td style="width: 221px; text-align: left;">Model</td>
<td style="width: 448px; text-align: left;">Affected order codes</td>
<td style="width: 448px; text-align: left;">Order code changes</td>
</tr>
<tr>
<td style="text-align: left;">{{{model}}}</td>
<td style="text-align: left;">All order codes</td>
<td style="text-align: left;">New firmware version</td>
</tr>
</table>


<table class="wikitable" style="background-color: white;">
=== Prerequisites and Important settings ===
<tr>
Race Mode should be enabled only when short sending periods are used and high timestamp accuracy is required during movement.
<th colspan="3" style="text-align: left;">Change impact</th>
 
</tr>
=== Basic operation ===
<tr>
When Race Mode is enabled, periodic record generation is synchronized directly to GNSS time while the device is moving. Records are created only after the configured Min Saving Period elapses, using the timestamp provided by the GPS module together with all required GNSS data.
<td style="width: 221px; text-align: left;">Risk assessment</td>
 
<td colspan="2" style="width: 908px; text-align: left;">During the transition period, clients might receive devices with previous Firmware version used in manufacture.</td>
'''Compatibility conditions'''
</tr>
Race Mode is available only when all of the following conditions are met:
</table>
* Location source is set to GNSS
</div>
* Tracking mode is not Basic (for ATx mini devices)
* Device is in a movement capable tracking mode (e.g. Movement mode)
 
=== Limitations, Edge Cases & Additional Notes ===
Race Mode operates only while device movement is detected.  
If the device enters On Stop state, or if GNSS fix is lost, periodic records are generated using the standard flow:
* Without GPS data
* Without GPS based time synchronization

Latest revision as of 09:31, 27 May 2026