TAT140 Tracking settings - Revision history

Karolis.C: /* Tracking Scenarios */

2025-05-21T11:06:29Z

Tracking Scenarios

← Older revision		Revision as of 14:06, 21 May 2025
Line 32:		Line 32:
	<b>On Stop scenario</b><br>		<b>On Stop scenario</b><br>
	<b>On Stop periodic tracking</b> - enable or disable periodic data sending when device is On Stop. Device will generate and send normal record with event ID 0 and movement AVL ID 240 with a value of 0.<br>		<b>On Stop periodic tracking</b> - enable or disable periodic data sending when device is On Stop. Device will generate and send normal record with event ID 0 and movement AVL ID 240 with a value of 0.<br>
	<b>On Stop event record</b> - enable or disable record sending when device switches tracking scenario from On Move to On Stop. To trigger this event <b>On Stop detection time</b> ~~(see Record timestamp shift)~~ timer needs to reach set value. Once event is triggered GNSS module will wake up and obtain GNSS fix. Record will have AVL event 240 with a value of 0 that means "Movement event - On Stop".<br>		<b>On Stop event record</b> - enable or disable record sending when device switches tracking scenario from On Move to On Stop. To trigger this event <b>On Stop detection time</b> timer needs to reach set value. Once event is triggered GNSS module will wake up and obtain GNSS fix. Record will have AVL event 240 with a value of 0 that means "Movement event - On Stop".<br>
	<b>On Stop</b> time period between records when device is working in On Stop scenario.<br>		<b>On Stop</b> time period between records when device is working in On Stop scenario.<br>
	<br>		<br>
	<b>On Move scenario</b><br>		<b>On Move scenario</b><br>
	<b>On Move periodic tracking</b> enable or disable periodic data sending when device is On Move. Device will generate and send normal record with event ID 0 and movement AVL ID 240 with a value of 1.<br>		<b>On Move periodic tracking</b> enable or disable periodic data sending when device is On Move. Device will generate and send normal record with event ID 0 and movement AVL ID 240 with a value of 1.<br>
	<b>On Move event record</b> enable or disable record sending when device switches tracking scenario from On Stop to On Move. To trigger this event <b>On Move detection time</b> ~~(see Record timestamp shift)~~ timer needs to reach set value. Once event is triggered device will wake up and will trigger one of two records:<br>		<b>On Move event record</b> enable or disable record sending when device switches tracking scenario from On Stop to On Move. To trigger this event <b>On Move detection time</b> timer needs to reach set value. Once event is triggered device will wake up and will trigger one of two records:<br>
	1 - if last record did not have a GNSS fix, GNSS module will be turned on and fix obtained.<br>		1 - if last record did not have a GNSS fix, GNSS module will be turned on and fix obtained.<br>
	2 - if last record had a valid GNSS fix, GNSS module will not be turned on and record will contain last good coordinates.<br>		2 - if last record had a valid GNSS fix, GNSS module will not be turned on and record will contain last good coordinates.<br>

Karolis.C at 06:46, 13 December 2024

2024-12-13T06:46:44Z

← Older revision		Revision as of 09:46, 13 December 2024
Line 32:		Line 32:
	<b>On Stop scenario</b><br>		<b>On Stop scenario</b><br>
	<b>On Stop periodic tracking</b> - enable or disable periodic data sending when device is On Stop. Device will generate and send normal record with event ID 0 and movement AVL ID 240 with a value of 0.<br>		<b>On Stop periodic tracking</b> - enable or disable periodic data sending when device is On Stop. Device will generate and send normal record with event ID 0 and movement AVL ID 240 with a value of 0.<br>
	<b>On Stop event record</b> - enable or disable record sending when device switches tracking scenario from On Move to On Stop. To trigger this event <b>On Stop detection time</b> (see Record timestamp shift) timer needs to reach set value. Once event is triggered GNSS module will wake up and obtain GNSS fix. Record will have AVL event 240 with a value of 4 that means "Movement event - On Stop".<br>		<b>On Stop event record</b> - enable or disable record sending when device switches tracking scenario from On Move to On Stop. To trigger this event <b>On Stop detection time</b> (see Record timestamp shift) timer needs to reach set value. Once event is triggered GNSS module will wake up and obtain GNSS fix. Record will have AVL event 240 with a value of 0 that means "Movement event - On Stop".<br>
	<b>On Stop</b> time period between records when device is working in On Stop scenario.<br>		<b>On Stop</b> time period between records when device is working in On Stop scenario.<br>
	<br>		<br>
Line 40:		Line 40:
	1 - if last record did not have a GNSS fix, GNSS module will be turned on and fix obtained.<br>		1 - if last record did not have a GNSS fix, GNSS module will be turned on and fix obtained.<br>
	2 - if last record had a valid GNSS fix, GNSS module will not be turned on and record will contain last good coordinates.<br>		2 - if last record had a valid GNSS fix, GNSS module will not be turned on and record will contain last good coordinates.<br>
	Record will have AVL event 240 with a value of 5 that means "Movement event - On Move" in both cases.<br>		Record will have AVL event 240 with a value of 1 that means "Movement event - On Move" in both cases.<br>
	<b>On Moving (s)</b> time period between records when device is working in On Move scenario.<br>		<b>On Moving (s)</b> time period between records when device is working in On Move scenario.<br>

Karolis.C at 05:38, 27 August 2024

2024-08-27T05:38:14Z

← Older revision		Revision as of 08:38, 27 August 2024
Line 167:		Line 167:
	#Recovery mode Val:<(0 if turned off, 1 if turned on)>		#Recovery mode Val:<(0 if turned off, 1 if turned on)>

	===Precautions===		{{Template:TAT Im alive}}

			==Precautions==

	{\| style="width: 800px;height: 60px; text-align: left; border: 1 px solid #FFCC33; border-bottom: 1px solid #FFCC33; border-left: 1px solid #FFCC33;border-top: 1px solid #FFCC33;border-right: 1px solid #FFCC33;background: #FEF6E7; color: black; text-align: left; padding: 10px;"		{\| style="width: 800px;height: 60px; text-align: left; border: 1 px solid #FFCC33; border-bottom: 1px solid #FFCC33; border-left: 1px solid #FFCC33;border-top: 1px solid #FFCC33;border-right: 1px solid #FFCC33;background: #FEF6E7; color: black; text-align: left; padding: 10px;"

Karolis.C at 08:39, 6 February 2024

2024-02-06T08:39:37Z

← Older revision		Revision as of 11:39, 6 February 2024
Line 7:		Line 7:
	\| style="width: 40px;height: 20px;padding: 10px;" \| [[File:Note_icon.png\|30 px\|link=]]		\| style="width: 40px;height: 20px;padding: 10px;" \| [[File:Note_icon.png\|30 px\|link=]]
	\|\| '''Please note:'''<br>		\|\| '''Please note:'''<br>
	Device has up to 3 min. hardcoded time to get fixed position while it i's awake from a Sleep Mode. <br>		* Device has up to 3 min. hardcoded time to get fixed position while it i's awake from a Sleep Mode. <br>
	If GNSS signal is poor - device will need more time to get fixed position. Battery usage is higher while device is looking for GNSS positions than when it stays in Sleep Mode.		* If GNSS signal is poor - device will need more time to get fixed position. Battery usage is higher while device is looking for GNSS positions than when it stays in Sleep Mode. <br>
			* If less than 3 satellites are visible in the first 60 seconds, satellite search is terminated early.
	\|}		\|}

Karolis.C at 08:24, 6 February 2024

2024-02-06T08:24:36Z

@@ Line 1: / Line 1: @@
 __TOC__
-{| class="main-table" style="background: #E7F1FE; color: black;"
+==Tracking Scenarios==
 {| class="main-table" style="background: #E7F1FE; color: black;"

Arnas.Zeb: Text replacement - "Bluetooth(?!®)" to "Bluetooth®"

2023-12-28T13:27:15Z

Text replacement - "Bluetooth(?!®)" to "Bluetooth®"

← Older revision		Revision as of 16:27, 28 December 2023
Line 144:		Line 144:
	{\| style="width: 100%;"		{\| style="width: 100%;"

	<br>'''Recovery mode''' is a special functionality that stops all ongoing tracking modes, ~~Bluetooth~~ scans, scenarios and sends records periodically with a configured '''Recovery period'''. However, it does not change options like Location and GNSS sources or Static navigation option. This mode is turned on by a configured number of events and can be turned on/off manually with a GPRS or SMS command. Once turned off, device will come back to a normal scenario that was configured before.<br>		<br>'''Recovery mode''' is a special functionality that stops all ongoing tracking modes, Bluetooth® scans, scenarios and sends records periodically with a configured '''Recovery period'''. However, it does not change options like Location and GNSS sources or Static navigation option. This mode is turned on by a configured number of events and can be turned on/off manually with a GPRS or SMS command. Once turned off, device will come back to a normal scenario that was configured before.<br>

	<br>'''Recovery mode can be triggered by:'''<br>		<br>'''Recovery mode can be triggered by:'''<br>

Martynas.paskauskas: /* Recovery mode */

2023-05-25T10:26:38Z

Recovery mode

← Older revision		Revision as of 13:26, 25 May 2023
Line 149:		Line 149:

	* '''Lost BLE sensor''' - for this trigger to work, Lost Sensor Alarm has to be enabled. When the sensor is not found, Recovery mode will turn on and a lost sensor alarm record will be sent. <br>		* '''Lost BLE sensor''' - for this trigger to work, Lost Sensor Alarm has to be enabled. When the sensor is not found, Recovery mode will turn on and a lost sensor alarm record will be sent. <br>
			* '''Lost BLE beacon''' - when TAT does not detect any beacons, it will start delayed Recovery mode - TAT will wake up to send a Lost BLE Beacon alarm record (AVL ID 20014) and then start Recovery mode timer to send Recovery alarm records (AVL ID 20012).<br>
	* '''Backup tracker''' - when TAT does not detect the central device, it will start delayed Recovery mode - TAT will wake up to send a Backup tracker alarm record (AVL ID 236) and then start Recovery mode timer to send Recovery alarm records (AVL ID 20012) periodically.<br>		* '''Backup tracker''' - when TAT does not detect the central device, it will start delayed Recovery mode - TAT will wake up to send a Backup tracker alarm record (AVL ID 236) and then start Recovery mode timer to send Recovery alarm records (AVL ID 20012) periodically.<br>
	* '''SMS/GPRS command''' - <code>  recovery:1</code> command can be sent to turn '''on''' Recovery mode. If Recovery mode is already activated, sending 1 won’t have any effect.<br>		* '''SMS/GPRS command''' - <code>  recovery:1</code> command can be sent to turn '''on''' Recovery mode. If Recovery mode is already activated, sending 1 won’t have any effect.<br>

Karolis.C at 06:46, 10 May 2023

2023-05-10T06:46:41Z

← Older revision		Revision as of 09:46, 10 May 2023
Line 77:		Line 77:
	<b>Record timestamp shift:</b> When disabled, the timestamp in records will not be modified and the timestamp will be in UNIX time (UTC +00), although functionality won’t be affected. <b>Time Zone:</b> Set tracking scenario time zone. Time zone can be set in range of -12h to +14h.<br>		<b>Record timestamp shift:</b> When disabled, the timestamp in records will not be modified and the timestamp will be in UNIX time (UTC +00), although functionality won’t be affected. <b>Time Zone:</b> Set tracking scenario time zone. Time zone can be set in range of -12h to +14h.<br>
	<b>On Stop detection time (s)</b> configurable amount of time until device switches to On Stop periodic tracking. Device needs to be stationary for configured amount of time to change state. Movement interrupts will reset this timer.<br>		<b>On Stop detection time (s)</b> configurable amount of time until device switches to On Stop periodic tracking. Device needs to be stationary for configured amount of time to change state. Movement interrupts will reset this timer.<br>
	<b>On Move detection time (s)</b> configurable amount of time until device switches to On Move periodic tracking. Instant movement will not change tracking scenario to On Move. Device needs to be interrupted at least once every 5 seconds during the configured time to change tracking scenario to On Move.<br>		<b>On Move detection time (s)</b> configurable amount of time until device switches to On Move periodic tracking. Instant movement will not change tracking scenario to On Move. Device needs to be interrupted <b>at least once every 5 seconds</b> during the configured time to change tracking scenario to On Move.<br>
	<br>		<br>
	<b>Periodic Tracking Options:</b><br><br>		<b>Periodic Tracking Options:</b><br><br>

Karolis.C at 06:43, 10 May 2023

2023-05-10T06:43:40Z

← Older revision		Revision as of 09:43, 10 May 2023
Line 1:		Line 1:
	__TOC__		__TOC__
	==Tracking Scenarios - FW version before X.4.3==		==Tracking Scenarios - FW version before X.4.7==

	{\| class="main-table" style="background: #E7F1FE; color: black;"		{\| class="main-table" style="background: #E7F1FE; color: black;"
Line 52:		Line 52:
	\|}		\|}

	==Tracking Scenarios - FW version after X.4.3==		==Tracking Scenarios - FW version after X.4.7==

	{\| class="main-table" style="background: #E7F1FE; color: black;"		{\| class="main-table" style="background: #E7F1FE; color: black;"

Karolis.C at 06:10, 10 May 2023

2023-05-10T06:10:28Z

← Older revision		Revision as of 09:10, 10 May 2023
Line 68:		Line 68:
	\|[[File:TAT140TRACKINGPNG.png\|border\|class=tlt-border\|right]]		\|[[File:TAT140TRACKINGPNG.png\|border\|class=tlt-border\|right]]
	{\| class="main-table" style="background: #E7F1FE; color: black;"		{\| class="main-table" style="background: #E7F1FE; color: black;"
	{\| style="width: ~~800px~~;height: 60px; text-align: left; border: 1 px solid #0054A6; border-bottom: 1px solid #0054A6; border-left: 1px solid #0054A6;border-top: 1px solid #0054A6;border-right: 1px solid #0054A6;background: #E7F1FE; color: black; text-align: left; padding: 10px;"		{\| style="width: 700px;height: 60px; text-align: left; border: 1 px solid #0054A6; border-bottom: 1px solid #0054A6; border-left: 1px solid #0054A6;border-top: 1px solid #0054A6;border-right: 1px solid #0054A6;background: #E7F1FE; color: black; text-align: left; padding: 10px;"
	\| style="width: 40px;height: 20px;padding: 10px;" \| [[File:Note_icon.png\|30 px\|link=]]		\| style="width: 40px;height: 20px;padding: 10px;" \| [[File:Note_icon.png\|30 px\|link=]]
	\|\| '''Please note:'''<br>		\|\| '''Please note:'''<br>

← Older revision		Revision as of 09:10, 10 May 2023
Line 68:		Line 68:
	\|[[File:TAT140TRACKINGPNG.png\|border\|class=tlt-border\|right]]		\|[[File:TAT140TRACKINGPNG.png\|border\|class=tlt-border\|right]]
	{\| class="main-table" style="background: #E7F1FE; color: black;"		{\| class="main-table" style="background: #E7F1FE; color: black;"
	{\| style="width: ~~800px~~;height: 60px; text-align: left; border: 1 px solid #0054A6; border-bottom: 1px solid #0054A6; border-left: 1px solid #0054A6;border-top: 1px solid #0054A6;border-right: 1px solid #0054A6;background: #E7F1FE; color: black; text-align: left; padding: 10px;"		{\| style="width: 700px;height: 60px; text-align: left; border: 1 px solid #0054A6; border-bottom: 1px solid #0054A6; border-left: 1px solid #0054A6;border-top: 1px solid #0054A6;border-right: 1px solid #0054A6;background: #E7F1FE; color: black; text-align: left; padding: 10px;"
	\| style="width: 40px;height: 20px;padding: 10px;" \| [[File:Note_icon.png\|30 px\|link=]]		\| style="width: 40px;height: 20px;padding: 10px;" \| [[File:Note_icon.png\|30 px\|link=]]
	\|\| '''Please note:'''<br>		\|\| '''Please note:'''<br>