TAT240 Tracking settings: Difference between revisions

(6 intermediate revisions by 3 users not shown)

Line 1:

__TOC__

~~==Tracking Scenarios - FW version before X.4.7==~~

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

==Tracking Scenarios==

{| 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:''' ~~

~~Device has up to 3 min. hardcoded time to get fixed position while it's awake from a 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 it stays in Sleep Mode.~~

|}

~~ ~~

~~Record timestamp shift: 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.~~

~~Time Zone: Set tracking scenario time zone. Time zone can be set in range of -12h to +14h. ~~

~~Periodic:~~

~~{| style="width: 100%;"~~

~~|[[File:TAT100TRACKINGPNG.png|border|class=tlt-border|right]]~~

~~{| 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:''' It means that device will wake up from Sleep Mode 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.

|}

~~Detailed example of default Periodic settings: ~~

~~1. Device wakes up after 28800 s. ~~

~~2. Device is looking for GPS Fix (can take up to 3 min., depends on the environment) ~~

~~3. Device saves record to memory and tries to send it via GPRS (can take up to 2 min., depends on the environment) ~~

~~4. Device goes to sleep for 28800 s. ~~

|}

~~{| 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:''' If On Move tracking period is configured to be greater than On Stop, when devices detects movement, On Move countdown will start and data package will be sent once On Move countdown completes.

|}

~~Scheduler:~~

~~{| 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. ~~

~~The main rules of making Schedule:~~

*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.

~~{| 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:''' 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;"

Line 58:

Line 7:

| style="width: 40px;height: 20px;padding: 10px;" | [[File:Note_icon.png|30 px|link=]]

|| '''Please note:'''

Device has up to 3 min. hardcoded time to get fixed position while it i's awake from a Sleep Mode.

* Device has up to 3 min. hardcoded time to get fixed position while it i's awake from a 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.

* 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 less than 3 satellites are visible in the first 60 seconds, satellite search is terminated early.

|}

Line 82:

Line 32:

On Stop scenario

On Stop periodic tracking - 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.

On Stop event record - enable or disable record sending when device switches tracking scenario from On Move to On Stop. To trigger this event On Stop detection time (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".

On Stop event record - enable or disable record sending when device switches tracking scenario from On Move to On Stop. To trigger this event On Stop detection time (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".

On Stop time period between records when device is working in On Stop scenario.

Line 90:

Line 40:

1 - if last record did not have a GNSS fix, GNSS module will be turned on and fix obtained.

2 - if last record had a valid GNSS fix, GNSS module will not be turned on and record will contain last good coordinates.

Record will have AVL event 240 with a value of 5 that means "Movement event - On Move" in both cases.

Record will have AVL event 240 with a value of 1 that means "Movement event - On Move" in both cases.

On Moving (s) time period between records when device is working in On Move scenario.

Line 144:

Line 94:

{| style="width: 100%;"

'''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.

'''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.

'''Recovery mode can be triggered by:'''

Line 153:

Line 103:

* '''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.

<code>  recovery:0</code> command can be sent to turn '''off''' Recovery mode.

* '''Tamper''' - ~~currently,~~ Recovery ~~Mode cannot be triggered with tamper detection. This feature is still under development~~.

* '''Tamper''' - tamper event can trigger Recovery mode (TAT240 only).

'''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.

Line 217:

Line 167:

#Recovery mode Val:<(0 if turned off, 1 if turned on)>

===Precautions===

==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;"