Changes

no edit summary
Line 6: Line 6:  
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:
 
Available movement source:
[[Image:Screenshot 2024-03-01 at 14-04-10 5.2. System - Mobility documentation.png|right|300px]]
+
[[Image:Screenshot 2024-03-01 at 14-04-10 5.2. System - Mobility documentation.png|right]]
 
* Ignition: checks ignition settings which depends on Ignition Source settings;
 
* Ignition: checks ignition settings which depends on Ignition Source settings;
   Line 15: Line 15:  
* CAN Speed: movement is detected if CAN speed retrieved from specific CAN protocol.
 
* 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.
+
When multiple source are selected, if any of selected are active, Movement is detected.
      Line 160: Line 160:  
|
 
|
 
|===Power On By USB/Charger===
 
|===Power On By USB/Charger===
[[Image:PT Power on by usb.png|200px|right]]
+
[[Image:PT Power on by usb.png|right]]
 
'''Note''': This feature is available forwards from FW version 55.02.03.Rev.05<br>
 
'''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>.
Line 171: Line 171:  
|
 
|
 
|===Continuous Charging Mode===
 
|===Continuous Charging Mode===
[[Image:PT continuous charging.png|200px|right]]
+
[[Image:PT continuous charging.png|right]]
 
'''Note''': This feature is available forwards from FW version 55.02.03.Rev.05<br>
 
'''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%.
 
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%.
Line 181: Line 181:  
|
 
|
 
|==Location Settings==
 
|==Location Settings==
[[Image:Location_settings_{{{model|X}}}.png|right|300px]]
+
[[Image:Location_settings_{{{model|X}}}.png|right]]
 
}}
 
}}
 
|}
 
|}
Line 332: Line 332:  
{{#if:{{{TFT_ignition_source|}}}
 
{{#if:{{{TFT_ignition_source|}}}
 
|
 
|
|==Ignition Source==
+
==Ignition Source==
 
[[Image:Mob_Ignition_source.png|right]]
 
[[Image:Mob_Ignition_source.png|right]]
 
User can choose an ignition source from digital input (1, 2 or 3), power voltage, CAN and accelerometer. More than one ignition source can be selected at the same moment. When there are 2 or more sources selected, at least one condition has to be met to change Ignition status. Example: DIN1 and Accelerometer are selected as Ignition source. When the device detects movement, Ignition status will change to 1, regardless that DIN1 value is 0. User can select movement start and movement stop delay time - those parameters are used when accelerometer is selected as an ignition source. Ignition status is used in power management and the following functionalities: Eco/Green driving, Excessive idling, Over speeding, Towing detection and trip.
 
User can choose an ignition source from digital input (1, 2 or 3), power voltage, CAN and accelerometer. More than one ignition source can be selected at the same moment. When there are 2 or more sources selected, at least one condition has to be met to change Ignition status. Example: DIN1 and Accelerometer are selected as Ignition source. When the device detects movement, Ignition status will change to 1, regardless that DIN1 value is 0. User can select movement start and movement stop delay time - those parameters are used when accelerometer is selected as an ignition source. Ignition status is used in power management and the following functionalities: Eco/Green driving, Excessive idling, Over speeding, Towing detection and trip.
 +
<br><br><br><br><br>
 
}}
 
}}
 
|}
 
|}
    
{|
 
{|
 +
{{#if:{{{TFT_Accelerometer_delay|}}}
 +
|
 +
|==Accelerometer Delay Settings==
 +
[[Image:Screenshot 2024-03-01 at 14-40-45 5.2. System - Mobility documentation.png|thumb]]
 +
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.
 +
<br>
 +
<table style="border-collapse: collapse; width:50%;" border="1;">
 +
    <tr style="text-align: center; background:black; color:white>
 +
        <th width="20%">Parameter ID</th>
 +
        <th width="30%">Name</th>
 +
        <th width="15%">Min Value</th>
 +
        <th width="15%">Max Value</th>
 +
        <th width="20%">Default Value</th>
 +
    </tr>
 +
    <tr style="text-align: center;">
 +
        <td>19001</td>
 +
        <td>Movement Start Delay</td>
 +
        <td>1</td>
 +
        <td>60</td>
 +
        <td>5</td>
 +
    </tr>
 +
    <tr style="text-align: center;">
 +
        <td>19002</td>
 +
        <td>Movement Stop Delay</td>
 +
        <td>5</td>
 +
        <td>300</td>
 +
        <td>60</td>
 +
    </tr>
 +
</table>
 +
}}
 +
|}
 +
 
{{#if:{{{GH_TMT_section|}}}
 
{{#if:{{{GH_TMT_section|}}}
 
|
 
|
Line 362: Line 396:  
Configurable 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%;"
+
<table style="border-collapse: collapse; width:60%;" border="1;">
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Parameter ID'''
+
    <tr style="text-align: center; background:black; color:white>
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Name'''
+
        <th width="15%">Parameter ID</th>
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Value/Type'''
+
        <th width="20%">Name</th>
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Min'''
+
        <th width="15%">Value/Type</th>
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Max'''
+
        <th width="15%">Min Value</th>
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Default'''
+
        <th width="15%">Max Value</th>
|-
+
        <th width="20%">Default Value</th>
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 901
+
    </tr>
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Resync (hours)  
+
    <tr style="text-align: center;">
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | uint8
+
        <td>901</td>
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0
+
        <td>NTP Resync (hours)</td>
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 24
+
        <td>uint8</td>
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0
+
        <td>0</td>
|-
+
        <td>24</td>
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 902
+
        <td>3</td>
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Server 1
+
    </tr>
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | char
+
    <tr style="text-align: center;">
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0
+
        <td>902</td>
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 55
+
        <td>NTP Server 1</td>
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | avl1.teltonika.lt
+
        <td>char</td>
|-
+
        <td>0</td>
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 903
+
        <td>55</td>
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Server 2
+
        <td>avl1.teltonika.lt</td>
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | char
+
    </tr>
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0
+
    <tr style="text-align: center;">
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 55
+
        <td>903</td>
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | pool.ntp.org
+
        <td>NTP Server 2</td>
|}
+
        <td>char</td>
 +
        <td>0</td>
 +
        <td>55</td>
 +
        <td>pool.ntp.org</td>
 +
    </tr>
 +
</table>
    
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.
 
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.
Line 405: Line 444:  
{{#if:{{{TFT_accelerometer_calibration|}}}
 
{{#if:{{{TFT_accelerometer_calibration|}}}
 
|
 
|
|==Accelerometer auto calibration==
+
|==Accelerometer Auto Calibration==
 
[[Image:Accelerometer_auto_calibration.PNG|right]]
 
[[Image:Accelerometer_auto_calibration.PNG|right]]
 
User can disable or enable Accelerometer Auto Calibration and Gravity Filter features. Under Accelerometer Auto Calibration settings, user can choose: <br/>
 
User can disable or enable Accelerometer Auto Calibration and Gravity Filter features. Under Accelerometer Auto Calibration settings, user can choose: <br/>
   −
*<code>Disable</code> – do not use auto calibration feature (sends AXES raw data),
+
*<code>Disable</code> – do not use Auto Calibration feature (sends AXES raw data),
 
*<code>Once</code> – calibrate one time only,
 
*<code>Once</code> – calibrate one time only,
*<code>Continuous</code> – launch auto calibration every trip (note: trip function must be enabled! ). <br />
+
*<code>Continuous</code> – launch Auto Calibration every trip (note: trip function must be enabled! ). <br />
   −
'''''Important! ''''' If Auto calibration is disabled, device should be mounted according User manual for Eco/Green driving feature to work properly. If enabled, AXES will be reoriented to VEHICLE axes according User manual (+X – Forward, +Y – Left, +Z – Down).  <br />  
+
'''Important!''': If Auto Calibration is disabled, device should be mounted according User manual for Eco/Green driving feature to work properly. If enabled, AXES will be reoriented to VEHICLE axes according User manual (+X – Forward, +Y – Left, +Z – Down).  <br />  
 
Under Gravity Filter settings, user can choose:  
 
Under Gravity Filter settings, user can choose:  
   Line 419: Line 458:  
*<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)
+
(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:
 
Calibration algorithm is used to recalculate accelerometer axes to represent vehicle’s axes (see Picture below). Vehicles axes are as follows:
Line 430: Line 469:  
Once vehicle’s axes are calculated, device is considered calibrated.
 
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.
 
'''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:
 
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.
+
<table style="border-collapse: collapse; width:65%;" border="1;">
 
+
    <tr style="text-align: center; background:black; color:white>
* 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.
+
        <th width="25%">Command</th>
 
+
        <th width="15%">Response</th>
* Continuous - calibration process is going on continuously and is always updated, no matter if it is correct or not.
+
        <th width="60%">Description</th>
 
+
    </tr>
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.
+
    <tr style="text-align: center;">
 
+
        <td>auto_calibrate:set</td>
* Disable - do NOT remove gravity component from AXL/Crash data.
+
        <td>Yes</td>
 
+
        <td>Request Auto Calibration task start</td>
* Enable - remove gravity component from AXL/Crash. Meaning that in calculations ground vector is subtracted from vehicle projection.
+
    </tr>
 
+
    <tr style="text-align: center;">
[[Image:Screenshot 2024-03-01 at 14-38-59 5.2. System - Mobility documentation.png|thumb]]
+
        <td>auto_calibrate:get</td>
 
+
        <td>Yes</td>
'''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
+
        <td>Request calibration info (time, ground vector, side vector)</td>
 +
    </tr>
 +
    <tr style="text-align: center;">
 +
        <td>auto_calibrate:clear</td>
 +
        <td>Yes</td>
 +
        <td>Request calibration clear from flash and stop calibration task</td>
 +
    </tr>
 +
    <tr style="text-align: center;">
 +
        <td>auto_calibrate:status</td>
 +
        <td>Yes</td>
 +
        <td>Request calibration status and calibration task status</td>
 +
    </tr>
 +
</table>
    
}}
 
}}
Line 478: Line 508:  
|
 
|
 
|=== Mounting Guidelines ===
 
|=== Mounting Guidelines ===
 +
[[File:Screenshot 2024-03-04 at 09-01-13 tft100-mounting-guidelines.jpg (JPEG Image 900 × 600 pixels).png|thumb]]
 
The device should be mounted according to the picture below. Logo/Antenna must be facing up.
 
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>
Line 490: Line 520:  
<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.
      
}}
 
}}
Line 533: Line 529:  
|==Tracking Mode==
 
|==Tracking Mode==
 
[[Image:Tracking_mode.png|right]]
 
[[Image:Tracking_mode.png|right]]
<br><b>Power Saving Mode</b> <br>
+
<b>Power Saving Mode</b> <br>
    
* <b>Performance</b> - In this mode GNSS module is constantly awake for maximum track quality.<br>
 
* <b>Performance</b> - In this mode GNSS module is constantly awake for maximum track quality.<br>
Line 540: Line 536:  
The purpose of this feature is to reduce power consumption and its main function is to turn off the GPS module when the device is stationary. For power saving functionality to run several conditions need to be met, one of them: ''Min Period'' value in ''Data Acquisition'' is more than or equal to 60 seconds. In device cold start state the GPS module is turned on for 180 sec. If GPS fix is obtained before this timeout elapses, GPS module turns off and a record is saved, and if not, no record will be saved. Before each new record saving period is expired the device is constantly checking for movement and if no motion has been detected, the GPS module does not turn on and the device waits for a periodic record to be eventually saved. If motion is detected at least 45 seconds before the record saving action, the GPS module will be turned on. If ''Records Saving/Sending Without TS'' configuration is set <span style=color:#F6A83E>Always</span> or <span style=color:#F6A83E>After Time Sync</span> a periodic record is saved and GPS is turned off again. Alternatively, if configuration is set to <span style=color:#F6A83E>After Position Fix</span>, the device will try to obtain GPS fix before record saving takes place and then allow extra ''GPS search period'' to obtain fix. Failing to do so within ''GPS search period'', GPS module will be turned back off and the record will be not saved at all. While this mode is enabled the data acquisition parameters min. distance, min. angle, min. speed delta, are disabled.
 
The purpose of this feature is to reduce power consumption and its main function is to turn off the GPS module when the device is stationary. For power saving functionality to run several conditions need to be met, one of them: ''Min Period'' value in ''Data Acquisition'' is more than or equal to 60 seconds. In device cold start state the GPS module is turned on for 180 sec. If GPS fix is obtained before this timeout elapses, GPS module turns off and a record is saved, and if not, no record will be saved. Before each new record saving period is expired the device is constantly checking for movement and if no motion has been detected, the GPS module does not turn on and the device waits for a periodic record to be eventually saved. If motion is detected at least 45 seconds before the record saving action, the GPS module will be turned on. If ''Records Saving/Sending Without TS'' configuration is set <span style=color:#F6A83E>Always</span> or <span style=color:#F6A83E>After Time Sync</span> a periodic record is saved and GPS is turned off again. Alternatively, if configuration is set to <span style=color:#F6A83E>After Position Fix</span>, the device will try to obtain GPS fix before record saving takes place and then allow extra ''GPS search period'' to obtain fix. Failing to do so within ''GPS search period'', GPS module will be turned back off and the record will be not saved at all. While this mode is enabled the data acquisition parameters min. distance, min. angle, min. speed delta, are disabled.
   −
Requerements:
+
Requirements:
 
* ''Min Period'' value in ''Data Acquisition'' is more than or equal to 60 seconds;
 
* ''Min Period'' value in ''Data Acquisition'' is more than or equal to 60 seconds;
 
* Tracking mode selected to “Low Power”.
 
* Tracking mode selected to “Low Power”.