0
edits
Changes
Created page with "__TOC__ ==Jamming== {|style="width: 100%;" |right When jamming is detected the scenario is activated, an event record is generated status is chang..."
__TOC__
==Jamming==
{|style="width: 100%;"
|[[Image:TST100_Jamming.png|right]]
When jamming is detected the scenario is activated, an event record is generated status is changed to 1 when configured once Jamming timeout runs out. If jamming ends during timeout countdown no event will be generated.
Eventual Records parameter can be configured: when it is disabled scenario status value will appear in each AVL record, otherwise it will be appended only to eventual records.
|}
==Unauthorized movement==
{|style="width: 100%;"
|[[Image:TST100 Unauthorized movement.png|right]]
If '''''scooter is unlocked''''', then '''''no event''''' will be generated on movement detection or stop. If '''''scooter is locked''''' and movement is detected for configured timeout, then '''''event generation and buzzer alarm will be triggered'''''.<br>
If no movement is detected for configured timeout, then event generation will be triggered and buzzer will be turned off. Event generation also depends on Generate event parameter: On Exit, On Entrance and On Both. Buzzer alarm does not depend on Generate event parameter and buzzer is triggered in any case if scooter is locked and instant movement is detected for configured timeout.
* <b>Pre-alarm timeout</b> - Defines delay in seconds prior to generate Unauthorized movement start event and trigger buzzer.
* <b>Time to stable</b> - Defines delay in seconds prior to generate Unauthorized movement end event and stop buzzer.
* <b>Buzzer On</b> - Defines time in seconds for how long buzzer should be turned on.
* <b>Buzzer Period</b> - Defines buzzer on period in seconds.
'''Note!''' It is NOT recommended to set Buzzer On and Buzzer Period parameters with same values, because accelerometer need some time to settle down. Buzzer sound vibes makes accelerometer to detect instant movement. As a result, accelerometer may never get back to stable position and buzzer will work continuously. It is advised to set Buzzer Period value at least 2 seconds bigger.
|}
==FallDown==
{|style="width: 100%;"
|[[Image:TST100_Fall_Down.png|right]]
An event will be generated when TST100 left in certain position
*<b>Autocalibration</b> - the device will automatically define ground vector if enabled and all FallDown conditions are met
*<b>Angle</b> - determines and which angle event is generated (e-scooter dropped on the ground)
*<b>Timeout</b> - time until even is generated
|}
==Last Known Position==
{|style="width: 100%;"
|[[Image:Last_Known_Position.png|right]]
This feature adds low priority record <code>AVL ID 386</code> to all records.<br>
The record shows how much time in seconds has passed since last GNSS fix.<br>
If the last good coordinate at the time the record is created is older than 60 seconds, then the new <b>high priority</b> record <code>AVL ID 69</code> will be sent immediately after GNSS fix appears. No matter how many different records have been created when there was no GNSS fix, only one high priority <code>AVL ID 69</code> record will be created when GNSS fix appears.
==Unplug Detection==
[[Image:TST100_Unplug_Detection.png|right]]
An event will be generated when TST100 is unplugged from external power or plugged back in again.
* '''Eventual records'''<br><code>Disable</code> - scenario status value is sent in each AVL record.<br><code>Enable</code> - scenario status value is sent only in eventual AVL records.
* '''Unplug Detection mode'''<br><code>Simple</code> - unplug detection according to external voltage only. Is used in kick e-scooters where power voltage is not dependent on ignition (recommended).<br><code>Advanced</code> - unplug detection according to external votage and accelerometer. Is used in kick e-scooters where power voltage is disconnected when ignition is switched off.
* '''Buzzer control'''<br><code>Enable</code> - buzzer will be active if unplug detected<br><code>Disable</code> - buzzer disabled and won't activated if unplug is detected<br><b>Buzzer ON duration in seconds</b> - determines how long buzzer will be active when unplug is detected (min 0 , max 65535)
==SIM Card Tamper Protection==
{| style="width: 100%"
|[[File:SIM_CArd_Tamper_Protection.png|right]]
<font color="red"><i><b>* This parameter is available only with FW 55.01.10.Rev.00 or newer</b></i></font><br><br>
This feature allows to detect if SIM card was removed of changed to other SIM cards by registered ICCID and lock scooter.
*<code><b>Enable/Disable SIM Tamper Protection</b></code> - Enables or disables the feature.<br>
*<code><b>ICCID</b></code> - SIM Card ICCID. If left "0", the first detected ICCID will be registered.
|}
{| class="wikitable" style="border-style: solid; border-width: 0px;"
|+
| style="width: auto; text-align: left; background: #F6F6FB;" |'''NOTE!'''
| style="width: auto; text-align: left; background: #F6F6FB;" |To force device to save record when SIM card is removed or another SIM card is inserted, configure ICCID IO in I/O window to be On Change.
|}
[[Category:TST100 Configuration]]
==Jamming==
{|style="width: 100%;"
|[[Image:TST100_Jamming.png|right]]
When jamming is detected the scenario is activated, an event record is generated status is changed to 1 when configured once Jamming timeout runs out. If jamming ends during timeout countdown no event will be generated.
Eventual Records parameter can be configured: when it is disabled scenario status value will appear in each AVL record, otherwise it will be appended only to eventual records.
|}
==Unauthorized movement==
{|style="width: 100%;"
|[[Image:TST100 Unauthorized movement.png|right]]
If '''''scooter is unlocked''''', then '''''no event''''' will be generated on movement detection or stop. If '''''scooter is locked''''' and movement is detected for configured timeout, then '''''event generation and buzzer alarm will be triggered'''''.<br>
If no movement is detected for configured timeout, then event generation will be triggered and buzzer will be turned off. Event generation also depends on Generate event parameter: On Exit, On Entrance and On Both. Buzzer alarm does not depend on Generate event parameter and buzzer is triggered in any case if scooter is locked and instant movement is detected for configured timeout.
* <b>Pre-alarm timeout</b> - Defines delay in seconds prior to generate Unauthorized movement start event and trigger buzzer.
* <b>Time to stable</b> - Defines delay in seconds prior to generate Unauthorized movement end event and stop buzzer.
* <b>Buzzer On</b> - Defines time in seconds for how long buzzer should be turned on.
* <b>Buzzer Period</b> - Defines buzzer on period in seconds.
'''Note!''' It is NOT recommended to set Buzzer On and Buzzer Period parameters with same values, because accelerometer need some time to settle down. Buzzer sound vibes makes accelerometer to detect instant movement. As a result, accelerometer may never get back to stable position and buzzer will work continuously. It is advised to set Buzzer Period value at least 2 seconds bigger.
|}
==FallDown==
{|style="width: 100%;"
|[[Image:TST100_Fall_Down.png|right]]
An event will be generated when TST100 left in certain position
*<b>Autocalibration</b> - the device will automatically define ground vector if enabled and all FallDown conditions are met
*<b>Angle</b> - determines and which angle event is generated (e-scooter dropped on the ground)
*<b>Timeout</b> - time until even is generated
|}
==Last Known Position==
{|style="width: 100%;"
|[[Image:Last_Known_Position.png|right]]
This feature adds low priority record <code>AVL ID 386</code> to all records.<br>
The record shows how much time in seconds has passed since last GNSS fix.<br>
If the last good coordinate at the time the record is created is older than 60 seconds, then the new <b>high priority</b> record <code>AVL ID 69</code> will be sent immediately after GNSS fix appears. No matter how many different records have been created when there was no GNSS fix, only one high priority <code>AVL ID 69</code> record will be created when GNSS fix appears.
==Unplug Detection==
[[Image:TST100_Unplug_Detection.png|right]]
An event will be generated when TST100 is unplugged from external power or plugged back in again.
* '''Eventual records'''<br><code>Disable</code> - scenario status value is sent in each AVL record.<br><code>Enable</code> - scenario status value is sent only in eventual AVL records.
* '''Unplug Detection mode'''<br><code>Simple</code> - unplug detection according to external voltage only. Is used in kick e-scooters where power voltage is not dependent on ignition (recommended).<br><code>Advanced</code> - unplug detection according to external votage and accelerometer. Is used in kick e-scooters where power voltage is disconnected when ignition is switched off.
* '''Buzzer control'''<br><code>Enable</code> - buzzer will be active if unplug detected<br><code>Disable</code> - buzzer disabled and won't activated if unplug is detected<br><b>Buzzer ON duration in seconds</b> - determines how long buzzer will be active when unplug is detected (min 0 , max 65535)
==SIM Card Tamper Protection==
{| style="width: 100%"
|[[File:SIM_CArd_Tamper_Protection.png|right]]
<font color="red"><i><b>* This parameter is available only with FW 55.01.10.Rev.00 or newer</b></i></font><br><br>
This feature allows to detect if SIM card was removed of changed to other SIM cards by registered ICCID and lock scooter.
*<code><b>Enable/Disable SIM Tamper Protection</b></code> - Enables or disables the feature.<br>
*<code><b>ICCID</b></code> - SIM Card ICCID. If left "0", the first detected ICCID will be registered.
|}
{| class="wikitable" style="border-style: solid; border-width: 0px;"
|+
| style="width: auto; text-align: left; background: #F6F6FB;" |'''NOTE!'''
| style="width: auto; text-align: left; background: #F6F6FB;" |To force device to save record when SIM card is removed or another SIM card is inserted, configure ICCID IO in I/O window to be On Change.
|}
[[Category:TST100 Configuration]]
