420
edits
Changes
no edit summary
__TOC__
__TOC__
==Tracking Scenarios==
==Tracking Scenarios - FW version before X.4.7==
{| class="main-table" style="background: #E7F1FE; color: black;"
{| class="main-table" style="background: #E7F1FE; color: black;"
|| '''Please note:'''<br> The record will not be generated at configured specific time, but will be generated up to a few minutes later because of time needed to boot modem and to get position.
|| '''Please note:'''<br> The record will not be generated at configured specific time, but will be generated up to a few minutes later because of time needed to boot modem and to get position.
|}
|}
==Tracking Scenarios - FW version after X.4.7==
{| 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: 40px;height: 20px;padding: 10px;" | [[File:Note_icon.png|30 px|link=]]
|| '''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>
* 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.
|}
<b>Periodic:</b>
{| style="width: 100%;"
|[[File:TAT140TRACKINGPNG.png|border|class=tlt-border|right]]
{| class="main-table" style="background: #E7F1FE; color: black;"
{| 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=]]
|| '''Please note:'''<br>
It means that device will <b>wake up from Sleep Mode</b> periodically and send data of asset location information after fix is obtained. Data could be sent according to I/O parameters in I/O section.
|}
<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 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>
<b>Periodic Tracking Options:</b><br><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 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</b> time period between records when device is working in On Stop scenario.<br>
<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 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>
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>
Record will have AVL event 240 with a value of 5 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>Detailed example of default Periodic settings:</b> <br><br>
1. Device wakes up after 28800 seconds if no movement is detected for 20 seconds, see step 2. If movement is detected during this period, see step 5<br>
2. Device is looking for GPS Fix (can take up to 3 min., depends on the environment)<br>
3. Device saves record to memory and tries to send it via GPRS (can take up to 2 min., depends on the environment)<br>
4. Device goes to sleep for 28800 s.<br>
5. If movement is detected for 20 seconds device switches to On Move scenario.<br>
5.1 If <b>On Move event record</b> is <b>Disabled</b> device does not generate a new record and starts On Move scenario timer.<br>
5.2 If <b>On Move event record</b> is <b>Enabled</b> and valid fix <b>is present</b>, device sends last known good position.<br>
5.3 If <b>On Move event record</b> is <b>Enabled</b> and valid fix is <b>not present</b>, device will wake up, obtain and send new position (GPS fix - up to 3 minutes, record saved, sent via GPRS - up to 2 minutes)<br>
6. Device wakes up after 28800 seconds if device was not stationary for 600 seconds, see step 7. If device was stationary for 600 seconds, see step 10<br>
7. Device is looking for GPS Fix (can take up to 3 min., depends on the environment)<br>
8. Device saves record to memory and tries to send it via GPRS (can take up to 2 min., depends on the environment)<br>
9. Device goes to sleep for 28800 seconds.<br>
10. If device was stationary for 600 seconds during On Move scenario device switches to On Stop scenario.<br>
10.1 If <b>On Stop event record</b> is <b>Disabled</b> device does not generate a new record and starts On Stop scenario timer.<br>
10.2 If <b>On Stop event record</b> is <b>Enabled</b> device will wake up, obtain and send new position (GPS fix - up to 3 minutes, record saved, sent via GPRS - up to 2 minutes)<br>
11. Device goes to sleep for 28800 seconds, see step 1.<br>
|}
{| 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: 40px;height: 20px;padding: 10px;" | [[File:Note_icon.png|30 px|link=]]
|| '''Please note:'''<br> If On Move tracking period is configured to be greater than On Stop, when devices detects movement, On Move countdown will start.
|}
<b>Scheduler:</b>
{| style="width: 100%;"
[[File:Selecting days.gif|border|class=tlt-border|right]]
This mode is used to set up the actual schedule of data sending. Every day of the week data could be sent up to 6 times.<br><br>
<b>The main rules of making Schedule:</b>
*Time from 1st to 6th record must be set in ascending order.
*Intervals between different times must be at least 6 minutes.
*Days of the week must be selected by clicking on it.<br>
{| 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: 40px;height: 20px;padding: 10px;" | [[File:Note_icon.png|30 px|link=]]
|| '''Please note:'''<br> The record will not be generated at configured specific time, but will be generated up to a few minutes later because of time needed to boot modem and to get position.
|}
|}
|}
{| 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>
<br> '''Note : ''' Recovery mode will not turn off automatically. It can only be turned off by restarting the device using the switch or sending SMS/GPRS command which was earlier mentioned.<br>
<br> '''Note : ''' Recovery mode will not turn off automatically. It can only be turned off by restarting the device using the switch or sending SMS/GPRS command which was earlier mentioned.<br>
[[File:Recovery_mode2.png|border|class=tlt-border|right]]
[[File:Recovery mode.png|border|class=tlt-border|right]]
<br>'''Recovery mode configuration settings:'''
<br>'''Recovery mode configuration settings:'''
* <code>None</code> - no events will trigger Recovery Mode and it can only be controlled with commands manually.<br>
* <code>None</code> - no events will trigger Recovery Mode and it can only be controlled with commands manually.<br>