Difference between revisions of "TAT100 Short-term firmware"

From Wiki Knowledge Base | Teltonika GPS
m
m (Protected "TAT100 Short-term firmware" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)))
(2 intermediate revisions by 2 users not shown)
Line 61: Line 61:
 
{| class="wikitable" style="width: 100%;"
 
{| class="wikitable" style="width: 100%;"
 
|+
 
|+
{| class="wikitable" style="width: 100%; valign="top"; align="center";|"
+
{{Template:TAT100 short term FW&SW changelog}}
|+
+
</div></div>
! style="width: 5%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |VERSION
 
! style="width: 5%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |RELEASE DATE
 
! style="width: 35%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |CONFIGURATOR CHANGES
 
! style="width: 40%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |FIRMWARE CHANGES
 
! style="width: 30%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |KNOWN ISSUES
 
|-
 
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |Firmware version: 55.00.16.Rev.543*<br>BlueNRG version: 10.3.12 for TAT100 HW ver.: 31<br>
 
0.3.12 for TAT100 HW ver.: 62<br>Configurator version: 1.7.16_E.TAT100.R23 RELEASE<br><i>*was approved as STABLE</i>
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |2022.08.08
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |
 
*Updated Teltonika Configurator version to set Central device default IMEI to 300000000000000
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |
 
*SMS command created for getting device statistics
 
*Protection from writing other devices FW
 
*Added condition to prevent modem waking up at midnight if scheduler is configured
 
*Added reconfiguration mechanism that lets FW work with / without SMPS filterMissing
 
*Fixed issue of missing 4th sensor's data with Monitoring operand
 
*Fixed too frequent / unnecessary scans with all sensors configured as monitoring
 
*Fixed sensors scan starting with monitoring operand when Backup tracker is configured
 
*Backup tracker scan not starting right after
 
*Time synchronization every 24 hours
 
*Fixed LBS data sending issue
 
*New AVL ID 20015 for Modem UpTime (in seconds)
 
*Added response sending if recovery command is sent through GPRS
 
*The next periodic record after Recovery mode deactivation being sent with AVL ID 20012 - fixed
 
*Reduced EQ Core update frequency
 
*Fixed battery consumption issue when GSM is jammed.
 
*LED status changed from constant on to blinking mode to save the battery
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |
 
|-
 
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |Firmware version: 55.00.16.Rev.531<br>BlueNRG version: 10.3.6 for TAT100 HW ver.: 31<br>
 
0.3.6 for TAT100 HW ver.: 62<br>Configurator version: 1.7.16_R.TAT100.R5
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |2022.04.14
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |
 
* Added Recovery mode option
 
* Added I/O element of Recovery Mode
 
* Added more options of movement sensitivity threshold [50-1000mG]
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |
 
* Added Recovery mode feature
 
* Implemented Recovery mode activation from the Backup tracking alarm
 
* Added EYE sensors support
 
* Fixed Minor bugs regarding the sensors
 
* Fixed Short period Recovery Mode records
 
* Extended Backup Tracker: Central device IMEI range
 
* Backup tracker: Scanning logic has been changed, scan duration is not configurable anymore, it is up to 60 seconds by default now.
 
* Implemented Record timestamp shift feature
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |
 
* Sometimes sensor records are randomly generated when using Backup Tracking with the USB cable plugged in.
 
* Only 2 sensors are working correctly with Monitoring Operand, values from the 3rd and 4th sensor may not be received.
 
|-
 
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |Firmware version: 55.00.16.Rev.522<br>BlueNRG version: 10.2.21.Rev.01<br>Configurator version: 1.7.16_R.TAT100.R2-BACKUP
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |2021.12.21
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |
 
'''Backup firmware:'''
 
* Changed required packets amount in backup tracker scenario and minimal scan duration
 
* Fixed backup tracker alarm not triggering just before wakeup
 
* Fixed backup tracker not detecting enough packets during BLE scan
 
* Periodic records do not affect backup tracker alarm record generation
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |
 
* Sometimes <code>Periodic</code>/<code>Schedule</code> record overwrites backup alarm record if both records are created at a same time.
 
* Possible workaround would be to '''disable''' periodical records:
 
<b>Tracking</b> → <b>Tracking Mode:</b> <code>None</code>
 
|-
 
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |Firmware version: 55.00.16.Rev.522<br>BlueNRG version: 10.2.21.Rev.01<br>Configurator version:<br>1.7.16_R.TAT100.R2-BLE
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |2021.12.21
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |
 
'''BLE firmware:'''
 
* Fixed BLE sensor records with wrong event ID being sent
 
* Fixed BLE sensor record duplicates with <code>On change</code> operand
 
* Fixed BLE sensor <code>On Exit</code> record not generating when switching to sleep mode
 
* Fixed <code>Custom1</code> sensor data in SMS being sent as NaN ''(empty)''
 
* Fixed duplicate BLE sensor data after waking up
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |
 
|-
 
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |Firmware version: 55.00.15.Rev.519<br>BlueNRG version: 10.2.14<br>Configurator version: 1.7.16_R.TAT100.R2-BACKUP
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |2021.10.19
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |
 
* Fixed fake movement detection on startup
 
* Fixed problem when the device is stuck in <b>On Stop</b> tracking mode after reconfiguration
 
* Added Power-On reason data and fixed version changes to device statistics
 
* Fixed Backup tracker issue where the alarm mode is not immediately activated when the central device disappears
 
* Fixed empty GSM I/O elements
 
* Fixed an issue where UTC is added after each reconfiguration
 
* Added record printing to <code>Dump log</code>
 
* LBS data is not included in records if GNSS fix was caught
 
* Fixed NTP timesync failure if offset is zero
 
* Improved record creation (wake up from sleep) during <b>Backup tracker</b> alarms
 
 
<br>
 
<br>
<hr>
 
<div class="mw-collapsible mw-collapsed" data-expandtext="Expand changelog" data-collapsetext="Close this section" style="width:100%;">
 
<br>
 
<div class="mw-collapsible-content" >
 
<hr>
 
* Improved GNSS module control with <code>Static Navigation</code> and <code>LBS</code>
 
* Added prevention from inappropriate record generation if the battery is low (HW watchdog)
 
* Added statistic element for USB connected uptime
 
* Added timestamp to BlueNRG serial prints
 
* Minor improvement for BlueNRG firmware update via configurator
 
* Added filter for <code>LBS</code> cell_id duplicates
 
* Improved Bluetooth® sensor record creation with <code>'On Change'</code> operand
 
* Added Bluetooth® sensor support
 
* Added condition to skip LBS data update if location source is only GNSS
 
* Increased retries of AT+# command in order to avoid empty LBS data from modem
 
* Changed <code>Open link timeout</code> to 15s
 
* Fixed an issue where the tracking mode would change from the scheduler to periodic
 
* Improved logic for multiple <code>FOTA Web</code> tasks update in the same connection
 
* Implemented rule for additional connection to <code>FOTA Web</code> after baseband firmware update
 
* Added accelerometer version information inside '.info' serial command
 
* Fixed an issue with battery voltage <code>I/O element</code> when record saving is overlapping with a firmware update
 
* Fixed <code>Scheduler</code> record sending at midnight
 
* Fixed missed LBS values inside <code>I/O elements</code>
 
* Fixed an issue when GNSS speed is not zero while the device is in a stationary position
 
* General minor improvements
 
</div></div>
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |
 
|-
 
|}
 
  
</div></div>
+
[[Category:TAT100 Firmware and configurator]]
<br>
 

Revision as of 11:24, 6 April 2023


Warning.png CAUTION!
Both firmwares (Modem and BlueNRG) must be flashed into device. Failing so can lead to unexpected device behavior and rapid battery discharge.
TAT100 BlueNRG & Modem FIRMWARE UPDATE GUIDE

TATXYZ FIRMWARE UPDATE GUIDE

Download Firmware and Configurator from STABLE FIRMWARE or SHORT-TERM FIRMWARE pages.

After device connection to Configurator:
1) Select Update firmware;
2) Select to flash Firmware(*.e.XIM) file;
3) Click on file;
4) And select Open.

Wait until the device will upload the firmware.

TAT100Firmware.png

When parameters successfully loaded:
1) Select Update firmware;
2) Select to flash BlueNRG firmware(*.bin);
3) Click on file;
4) And select Open.

TAT100NRG.png

Backup/BLE support Feature Firmware

SHORT-TERM FIRMWARE
FIRMWARE VERSION: Not Available
CONFIGURATOR VERSION: Not Available
BlueNRG VERSION: Not Available
RELEASE DATE:
Not Available


DOWNLOAD
Firmware & BlueNRG for [TATXY]
Firmware & BlueNRG for [TAT100 HW31]
Firmware & BlueNRG for [TAT100 HW62]
Configurator
DOWNLOAD ALL
DOWNLOAD ALL FOR [TATXY]
DOWNLOAD ALL FOR [TAT100 HW31]
DOWNLOAD ALL FOR [TAT100 HW62]
Backup FMB Firmware
On request via Teltonika HelpDesk

TAT100 Hardware version identification

  • If Serial Number [S/N] is greater than 1122473261, then device version: TAT100 HW: 62.
  • If Serial Number [S/N] is less than 1122473261, then device version: TAT100 HW: 31.

ORDERS AFTER 2022-03-17 WILL BE WITH TAT100 HARDWARE: 62

Warning.pngCAUTION!

When updating firmware via FOTA WEB, pay attention to notice above.


NOTE! THERE IS NO SHORT TERM FIRMWARE AVAILABLE. PLEASE USE THE STABLE VERSION.


CHANGELOG

VERSION RELEASE DATE CONFIGURATOR CHANGES FIRMWARE CHANGES KNOWN ISSUES
N/A N/A N/A N/A N/A