6,023
edits
Changes
mLine 1:
Line 1: − [[Image:System_settings_{{{model|X}}}.png|right|]] Line 6:
Line 5: + + + + + + + + + + + + + + Line 14:
Line 27: − + + + + + + − + Line 61:
Line 79: + Line 87:
Line 106: + + + + + + + + + + Line 95:
Line 124: + + + + + + + + + + + + + + + + + + Line 113:
Line 160: + + + + + + + + + + + + + Line 121:
Line 181: − + Line 129:
Line 189: − [[Image:LBS1.jpg|right]] − − Line 138:
Line 195: − + − + + + + + Line 168:
Line 229: − <br><br><br><br><br><br><br><br><br> Line 199:
Line 259: − + Line 205:
Line 265: − + Line 215:
Line 275: − + + + + + + + + + + + + + + Line 225:
Line 298: + + + + + + + + + + + + + + + + + + + + + + + + + + + + Line 238:
Line 339: − + − + − + + + + + + + Line 252:
Line 359: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Line 270:
Line 418: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
no edit summary
==System Settings==
==System Settings==
{|
{|
{{#if:{{{MM_Movement_source|}}}
{{#if:{{{MM_Movement_source|}}}
|===Movement Source===
|===Movement Source===
User can select which source will be used to determine when vehicle is on stop or moving. When multiple are selected, if any of selected are active, Vehicle MOVING mode is used.
User can select which source will be used to determine when vehicle is on stop or moving. When multiple are selected, if any of selected are active, Vehicle MOVING mode is used.
Available movement source:
[[Image:Screenshot 2024-03-01 at 14-04-10 5.2. System - Mobility documentation.png|right|300px]]
* Ignition: checks ignition settings which depends on Ignition Source settings;
* GNSS: movement detected if Fix position available and speed is bigger or equal to 5km/h;
* Accelerometer: movement detection depends on Accelerometer Delay Settings;
* CAN Speed: movement is detected if CAN speed retrieved from specific CAN protocol.
When multiple source are selected, if any of selected are active, Movemenet is detected.
}}
}}
|}
|}
|===Speed source===
|===Speed source===
If TFT100 is used with CAN modification extra settings option will we available for choosing Speed source.
If TFT100 is used with CAN modification extra settings option will we available for choosing Speed source.
[[Image:speed_source.PNG]]
Available speed source: GNSS or CAN.
If CAN Speed source enabled, it will retrieve speed from CAN data, but if the speed value from CAN data is 0, speed will be retrieved from GNSS data if Position Fix acquired, even though it is not configured.<br>
[[Image:Screenshot 2024-03-01 at 14-09-53 5.2. System - Mobility documentation.png]]
}}
}}
|}
|}
{|
{|
{{#if:{{{TAT100_no_show|}}}
{{#if:{{{AT_no_show|}}}
|
|
|===Records settings===
|===Records settings===
{|
{|
{{#if:{{{AT_no_show|}}}
{{#if:{{{AT_no_show|}}}
|
|===GNSS Source settings===
|===GNSS Source settings===
User can configure which GNSS system(s) to use.<br />
User can configure which GNSS system(s) to use.<br />
Here user can change battery charger settings, where charging is allowed.
Here user can change battery charger settings, where charging is allowed.
Battery will be charged: '''''On Need''''' (battery will be charged anytime when it needs to be charged) and '''''After Ignition ON''''' (battery will be charged only when ignition is on).
Battery will be charged: '''''On Need''''' (battery will be charged anytime when it needs to be charged) and '''''After Ignition ON''''' (battery will be charged only when ignition is on).
Three charging modes is available:
* On neeed: charger enabled if external voltage is higher than 5.05 voltage and Battery Voltage is below 3.90V. Charging is disabled if device enters any sleep mode.
* After Ignition On: charger enabled after ignition is turned on, except if the battery is fully charged or 10-minute timeout has not passed since the device was turned on for faster FIX receiving.
* Always: charger is always enabled, except if the battery is fully charged or 10-minute timeout has not passed since the device was turned on for faster FIX receiving.
[[Image:Screenshot 2024-03-01 at 14-11-41 5.2. System - Mobility documentation.png]]
}}
}}
|}
|}
|===Analog Input Value Range===
|===Analog Input Value Range===
User can choose analog input range of 15 V or 150 V.
User can choose analog input range of 15 V or 150 V.
Input range used to determine lowest voltage for DIN1 and DIN2 activation.
[[Image:Screenshot 2024-03-01 at 14-13-04 5.2. System - Mobility documentation.png]]
Lowest voltage to enabled DIN for 15V range - 2.5V
Lowest voltage to enabled DIN for 150V range - 9V
}}
|}
{|
{{#if:{{{TFT_DOUT_Overcurrent_protection|}}}
|
|===DOUT Overcurrent protection===
DOUTs have overcurrent protection that triggers after the current exceeds 300 mA. This protection works by generating pulses on the hardware. When the firmware detects at least 20 impulses on a DOUT it turns off that DOUT for 5 minutes. During this time all scenarios that try to turn this DOUT on will fail.
}}
}}
|}
|}
|
|
|===Power On By USB/Charger===
|===Power On By USB/Charger===
[[Image:PT Power on by usb.png|200px|right]]
'''Note''': This feature is available forwards from FW version 55.02.03.Rev.05<br>
Device supports two working modes: normal mode, where the device works as usual, and charging mode, which is entered when ''Power On By USB/Charger'' parameter is <b>disabled</b>. To enter normal mode, device can be turned on by power button or by USB charger, if ''Power On By USB/Charger'' parameter is set to <b>Enable</b>.
Device supports two working modes: normal mode, where the device works as usual, and charging mode, which is entered when ''Power On By USB/Charger'' parameter is <b>disabled</b>. To enter normal mode, device can be turned on by power button or by USB charger, if ''Power On By USB/Charger'' parameter is set to <b>Enable</b>.
}}
|}
{|
{{#if:{{{PT_Power_on|}}}
|
|===Continuous Charging Mode===
[[Image:PT continuous charging.png|200px|right]]
'''Note''': This feature is available forwards from FW version 55.02.03.Rev.05<br>
Battery protection mode to extend battery life. Should only be used when device is permanently connected to external charger. When enabled charge current is reduced preventing charging to maximum voltage. This results in lower battery temperature and extended battery lifetime. Please note, this also increases battery charge time and reduces overall charge to around 85%.
}}
}}
|}
|}
|
|
|==Location Settings==
|==Location Settings==
[[Image:Location_settings_{{{model|X}}}.png|right|]]
[[Image:Location_settings_{{{model|X}}}.png|right|300px]]
}}
}}
|}
|}
|
|
|===Location Source===
|===Location Source===
<b>LBS</b> - location based services. It helps us to find the approximate location without using a GNSS, but using cell towers information instead. Device cannot find the location using LBS by itself, approximate location is calculated on the server side according to the information provided by the device. Therefore, to locate a unit by LBS the device should send at least 4 parameters: mcc, mnc, lac, cell ID.
<b>LBS</b> - location based services. It helps us to find the approximate location without using a GNSS, but using cell towers information instead. Device cannot find the location using LBS by itself, approximate location is calculated on the server side according to the information provided by the device. Therefore, to locate a unit by LBS the device should send at least 4 parameters: mcc, mnc, lac, cell ID.
*If <b>LBS</b> is selected as a location source, the device will send information about the cell towers to the server and <b>will not use GNSS</b>.
*If <b>LBS</b> is selected as a location source, the device will send information about the cell towers to the server and <b>will not use GNSS</b>.
*If <b>GNSS or LBS</b> is selected, device will use GNSS if the satellites are visible, if not - it will start sending cell towers information to the server, which will be able to calculate the approximate location using LBS.
*If <b>GNSS or LBS</b> is selected, device will use GNSS if the satellites are visible, if not - it will start sending cell towers information to the server, which will be able to calculate the approximate location using LBS.
Also, <b>GSM Cell ID</b> and <b>Active GSM Operator</b> should have at least Low priority in I/O settings.[[Image:LBS IO.jpg|right]]
Also, <b>GSM Cell ID</b> and <b>Active GSM Operator</b> should have at least Low priority in I/O settings.<br>[[Image:LBS IO.jpg|left]]
<br><br><br>
<br><br><br>
}}
}}
|}
|}
===GNSS Source settings===
{|
{{#if:{{{Location_settings|}}}
|
|===GNSS Source settings===
User can configure which GNSS system(s) to use.<br />
User can configure which GNSS system(s) to use.<br />
User has a choice to use only one system between GPS, GLONASS, Galileo or Beidou and it is possible to choose two or three systems together. One exception is that you cannot combine BeiDou and GLONASS systems together.
User has a choice to use only one system between GPS, GLONASS, Galileo or Beidou and it is possible to choose two or three systems together. One exception is that you cannot combine BeiDou and GLONASS systems together.
|===GNSS control===
|===GNSS control===
User can manually turn ON/OFF the GNSS module. For example, if button 'Turn off GNSS' is pressed and device is trying to acquire GNSS fix for a record, it will turn GNSS back on. If GNSS module is turned ON using 'Turn on GNSS' button, it will be active for undefined period of time until USB is disconnected and device is going to sleep, record sending is finished or the 'Turn off GNSS' button is pressed again.
User can manually turn ON/OFF the GNSS module. For example, if button 'Turn off GNSS' is pressed and device is trying to acquire GNSS fix for a record, it will turn GNSS back on. If GNSS module is turned ON using 'Turn on GNSS' button, it will be active for undefined period of time until USB is disconnected and device is going to sleep, record sending is finished or the 'Turn off GNSS' button is pressed again.
}}
}}
|}
|}
{{#if:{{{AT_show|}}}
{{#if:{{{AT_show|}}}
|
|
|==Movement sensitivity==
|===Movement sensitivity===
This feature sets the sensitivity threshold levels for movement event registration. Higher configured level makes the device “less sensitive” and vice versa. Currently, there are 10 configurable Movement Sensitivity levels. Levels are measured in mG - thousandth parts of the gravitational force equivalent or gravitational acceleration of Earth (9.8 m/s). It means that if Movement Sensitivity is set to 1000 mG, the device has to be free falling, experience fierce stops/accelerations or vibrations to detect movement.<br />
This feature sets the sensitivity threshold levels for movement event registration. Higher configured level makes the device “less sensitive” and vice versa. Currently, there are 10 configurable Movement Sensitivity levels. Levels are measured in mG - thousandth parts of the gravitational force equivalent or gravitational acceleration of Earth (9.8 m/s). It means that if Movement Sensitivity is set to 1000 mG, the device has to be free falling, experience fierce stops/accelerations or vibrations to detect movement.<br />
}}
}}
{|
{|
{{#if:{{{TAT100_no_show|}}}
{{#if:{{{AT_no_show|}}}
|
|
|==Static Navigation Settings==
|==Static Navigation Settings==
{|
{|
{{#if:{{{TAT100_no_show|}}}
{{#if:{{{GH_section|}}}
|
|==Call Duration Limits==
[[Image:Call duration limits.png|right]]
These is two places for these settings. First one can be found in the SMS \ Calls Settings section. This setting applies to incoming and outgoing calls, except for the keyboard “Call” action and the Amber Alert feature.
[[Image:Cal duration limit2.png|right]]
Second one can be found in the Keyboard section. These settings are only visible when the button action is Call. There is only one parameter per button, so the same parameter applies to all button presses.
}}
|}
{|
{{#if:{{{AT_no_show|}}}
|
|
|==Sleep Mode==
|==Sleep Mode==
<td>[[Image:Sleep_mode_{{{model|X}}}.png|right]]</td>
<td>[[Image:Sleep_mode_{{{model|X}}}.png|right]]</td>
</table>
</table>
}}
|}
{|
{{#if:{{{BT/BLE_no_show|}}}
|
===BT/BLE module OFF during Sleep modes===
------------------
Power off sleep mode can be described as the lowest possible power consumption mode where the device can go into power off state.
<br>
From the version, 03.28.XX this new functionality includes new parameters:
*'''Periodic Wakeup''' – if value is greater than zero, device while being in Deep Sleep or Online Deep Sleep, will wake up after defined period for beacon collection. This is mainly should be used when Bluetooth is disabled in sleep.
*'''Bluetooth On While In Sleep'''- by default this parameter value is set to Enable and BT will work as in base functionality. If this value is set to Disable, Bluetooth will be turned off when device goes to Deep Sleep or Online Deep Sleep and will be turned on during Periodic Wakeup or if device enters normal state.
[[Image:PWU.jpg|right|300px]]
</br></br>
Note: In case when during scan after wakeup no BLE devices will be found FMB will be active for configured scan duration time in Bluetooth 4.0 tab. After that timeout FMB will go to sleep state.
<br>
Power off sleep mode can be described as the lowest possible power consumption mode where the device can go into power off state and can only wake up if one of the conditions is true:
*Movement is detected by accelerometer (not by the configured movement source);
*External power is applied;
*It is the time to make a new periodic record (new feature);
<br>
Please keep a note that Power OFF Sleep will not work if any USB cable is connected to the device.
}}
}}
|}
|}
{|
{|
{{#if:{{{TAT100_no_show|}}}
{{#if:{{{GH_TMT_section|}}}
|
|
|==Movement Settings==
|==Movement Settings==
[[Image:Accelerometer delay.gif|right]]
[[Image:Accelerometer settings.png|right]]
Here the user can set the movement start/stop delays. <br/>
Here the user can set the movement start/stop delays. <br/>
''For example'', if the '''''Movement Start Delay''''' is set to 1s and '''''Movement Stop Delay''''' to 60s, the movement will be detected after 1s of moving and defined as stopped after 60s when device stopped moving.
''For example'', if the '''''Movement Start Delay''''' is set to 1s and '''''Movement Stop Delay''''' to 60s, the movement will be detected after 1s of moving and defined as stopped after 60s when device stopped moving. Accelerometer Sensitivity in Sleep parameter defines how much movement device needs to experience to exit sleep mode. The lower the sensitivity - the more movement is required.
*<code>Minimal</code> – approximately 40% higher movement threshold comparing to Normal
*<code>Reduced</code> – approximately 20% higher movement threshold comparing to Normal
*<code>Normal</code> – recommended value for most users
*<code>Increased</code> – approximately 20% lower movement threshold comparing to Normal
*<code>Maximum</code> – approximately 40% lower movement threshold comparing to Normal
Changing Accelerometer Sensitivity in Sleep parameter might result in fake movement record or skipped movement events! Only change that if you experience problems with movement detection!
}}
}}
|}
|}
|[[Image:Time_synchronization.PNG|right]]
|[[Image:Time_synchronization.PNG|right]]
User can select which NTP server (it is possible to configure up to two servers) and what time period to use to re-synchronize time.
User can select which NTP server (it is possible to configure up to two servers) and what time period to use to re-synchronize time.
Configurable NTP server (it is possible to configure up to two servers) and what time period to use to re-synchronize time.
{| class="wikitable" style="width: 80%;"
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Parameter ID'''
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Name'''
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Value/Type'''
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Min'''
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Max'''
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Default'''
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 901
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Resync (hours)
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | uint8
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 24
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 902
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Server 1
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | char
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 55
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | avl1.teltonika.lt
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 903
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Server 2
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | char
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 55
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | pool.ntp.org
|}
Time synchronization works by waiting a minute on startup to acquire fix and consequently synchronizes the time via GNSS. If the firmware acquires the fix, it starts working in the syncing by GNSS state. This state checks the difference of RTC and GNSS times every second. If the difference of at least 3 seconds persists to be for 5 seconds, the firmware triggers a procedure by GNSS.
After that, the the time difference is still calculated, but the difference is expected to persist for at least 5 minutes to trigger a GNSS time resynchronization. This is done to prevent false GNSS timestamps (such as year 2080 and etc.). If there’s no time difference found, the difference is expected to persist again for a period of 5 seconds later on when calculating. In the case that there is no fix or it is lost during the syncing by GNSS state, the firmware goes to state of syncing by NTP.
Entering the state of NTP syncing, the firmware immediately attempts to synchronize the time by triggering NTP and later on, does this periodically every time the configured NTP resynchronization time is reached. If the NTP resynchronization time is set to 0, no periodical resynchronization is done in this state. Time synchronization by NITZ can occur any time.
[[File:Time sync chart.png|thumb]]
|}
|}
*<code>Disabled</code> – do not remove GRAVITY component from AXL/Crash data,
*<code>Disabled</code> – do not remove GRAVITY component from AXL/Crash data,
*<code>Enabled</code> – remove GRAVITY component from AXL/Crash.
*<code>Enabled</code> – remove GRAVITY component from AXL/Crash.
(An in-depth explanation for the auto calibration can be found here)
Calibration algorithm is used to recalculate accelerometer axes to represent vehicle’s axes (see Picture below). Vehicles axes are as follows:
* X is front.
* Y is left.
* Z is down.
[[File:Screenshot 2024-03-01 at 14-34-37 vehicleaxes.png (PNG Image 1186 × 596 pixels).png|thumb]]
Once vehicle’s axes are calculated, device is considered calibrated.
'''Note''': Moving forward along any axis will generate negative values. This means acceleration will generate -X values, accordingly braking will generate X values. Same goes for other axes.
Commands that can be used during calibration:
{| class="wikitable" style="width: 80%;"
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Command'''
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Response'''
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Description'''
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:set
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Request auto calibration task start
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:get
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Request calibration info (time, ground vector, side vector)
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:clear
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Request calibration clear from flash and stop calibration task
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:status
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Request calibration status and calibration task status
|}
Accelerometer Auto Calibration parameter has 3 options:
* Disabled - when this option is selected the device will be calibrated accordingly to its mounted position.
* Once - when this option is selected, the device only tries once to do calibrating. When calibration is done, the device will not try to recalibrate, even if the calibration is not correct. Calibration will be left as it is.
* Continuous - calibration process is going on continuously and is always updated, no matter if it is correct or not.
Gravity filter subtracts gravity from the vector when the device is calibrated or when auto calibration is disabled (default values). Parameter functionality is the same in all versions. This also influences the ECO/Green driving scenario algorithm.
* Disable - do NOT remove gravity component from AXL/Crash data.
* Enable - remove gravity component from AXL/Crash. Meaning that in calculations ground vector is subtracted from vehicle projection.
[[Image:Screenshot 2024-03-01 at 14-38-59 5.2. System - Mobility documentation.png|thumb]]
'''Important''':If Auto Calibration is disabled, in order for the Eco/Green Driving to work propertly, the device must be mounted according to the TFT100 Mounting Guidelines
}}
|}
{|
{{#if:{{{TFT_Mounting_Guidelines|}}}
|
|=== Mounting Guidelines ===
The device should be mounted according to the picture below. Logo/Antenna must be facing up.
[[File:Screenshot 2024-03-04 at 09-01-13 tft100-mounting-guidelines.jpg (JPEG Image 900 × 600 pixels).png|thumb]]
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
}}
|}
{|
{{#if:{{{TFT_Accelerometer_delay|}}}
|
|===Accelerometer delay===
Configurable movement start/stop delay settings.
[[Image:Screenshot 2024-03-01 at 14-40-45 5.2. System - Mobility documentation.png|thumb]]
{| class="wikitable" style="width: 80%;"
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Parameter ID'''
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Name'''
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Min'''
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Max'''
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Default'''
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 19001
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Movement Start delay
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 1
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 60
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 1
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 19002
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Movement Stop Delay
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 5
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 300
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 60
|}
For example, if the Movement Start Delay is set to 1s and Movement Stop Delay to 60s, the movement will be detected after 1s of moving and defined as stopped after 60s when device stopped moving.
}}
}}
|}
|}