Jump to content
  • EN

Template:ATX System: Difference between revisions

From Teltonika Telematics Wiki
← Older edit
VisualWikitext
 
(17 intermediate revisions by the same user not shown)
Line 19: Line 19:


<br />
<br />
{{#switch: {{{model}}}
| FTC927
| FTM887
| FTC887
| FTC968 =
== Dead Reckoning ==
=== <u>Introduction</u> ===
'''Dead Reckoning''' is a navigation technique used to estimate current position of vehicle  , direction of movement, based on its previous position and known speed.  It uses additional sensor data to correct the position received from GNSS receiver.<br>
Usage of Dead Reckoning is essential in scenarios where GNSS signal is weak or unavailable, such as underground parking lots, tunnels or dense forests.<br>
'''Note:''' Dead Reckoning is enabled for all FT platform devices with gyroscope. At the moment, it’s not possible to disable it.<br>
=== <u>Prerequisites</u> ===
Key points to understand before utilizing the Dead Reckoning functionality:
* Installation
* Configuration
* Alignment
'''<u>Installation</u>'''<br>
The device must be mounted firmly in the vehicle, with good visibility of the sky. Failure to ensure proper mounting will result in inability to calibrate the device or inaccurate position estimation. Following examples ensure that the GNSS antenna is facing towards the sky and there are no
physical obstacles, like metal plates,  wires, are blocking the GNSS signal.
Good '''mounting''' examples:<br>
<div style="display: flex; flex-direction: row;">
[[File:FTC927 under the front dashboard in the middle of the car.jpg|thumb|left|280px|Dashboard in the middle of the car mount]]
[[File:FTC927 beneath the speedometer panel.jpg|thumb|left|300px|Beneath the speedometer panel]]
[[File:FTC927 above the glove box.jpg|thumb|left|300px|Above glove box]]
</div>
Bad '''mounting'''  examples:<br>
<div style="display: flex; flex-direction: row;">
[[File:Dead Reckoning Unwanted movements will be detected by the IMU.png|thumb|left|280px|Unwanted movements will be detected by the IMU]]
[[File:Dead Reckoning Metal parts above the mount.png|thumb|left|300px|Metal parts above the mount]]
[[File:Dead Reckoning vibration could cause unwanted device movements.png|thumb|left|300px|Places, where vibration could cause unwanted device movements]]
</div>
'''<u>Configuration</u>'''<br>
[[File:Dead Recknonig TCT panel_2.png|right|500px]]
''The Dead Reckoning feature is configurable via the Dead Reckoning section in the GNSS settings group under System view in TCT.''
Parameter list can be found [[Template:FTX_System#Parameter_list|here]].
===== Dead Reckoning alignment status =====
The Dead Reckoning alignment status is a 1-byte AVL ID (1433) that indicates the current status of the Dead Reckoning alignment. The possible values are:<br>
* '''0''' - Unknown: Dead Reckoning status is unknown.
* '''1''' - Init: Dead Reckoning alignment is initializing.
* '''2''' - Coarse: Dead Reckoning is in alignment stage.
* '''3''' - Stable: Dead Reckoning alignment stage has been completed. Estimation stage is in progress.
===== Turning alignment =====
The turning alignment is a 1-byte AVL ID ('''1434''') that indicates the current percentage of the turning alignment of the device.
===== Straight alignment =====
The straight alignment is a 1-byte AVL ID ('''1435''') that indicates the current percentage of the straight alignment of the device.
'''<u>Alignment</u>'''<br>
Once device mounting adheres to the guidelines, alignment can be performed. The device '''must finish''' a specific alignment process to '''determine''' its mounting orientation. During this process, there are specific conditions that must be met:
# The device must be '''stationary''' for at least 3 minutes.
# A great number of '''left and right''' turns must be performed.
# The speed of the vehicle '''ideally''' must not be bellow 10 km/h or exceed 50 km/h.
# Avoid driving in underground tunnels or areas with poor GNSS signal.
[[File:Dead Reckoning TCT Swift .png|right|400px]]
In order to speed up alignment at the cost of some accuracy, use '''Swift''' alignment.
=== <u>Limitations</u> ===
There are some important things to keep in mind when using the Dead Reckoning functionality. The algorithm tries to correct for these issues, but sometimes they can still affect how well Dead Reckoning works.
* '''Position accuracy may decrease''' - If the device cannot receive a GNSS signal for a long time, the estimated position may become less accurate. This is because the sensors inside the device can only estimate the position for a limited time without help from GNSS.
For example: If a courier spends up to 30 minutes unloading in the underground car park, DR will remain accurate. Otherwise, positioning information will become less accurate.
* '''Temperature effects''' - The accuracy of the position can change if the temperature is very different from when the device was last calibrated. .
* '''Alignment reset''' - If the device loses power or goes into sleep mode, it will need to be calibrated again.
'''Tip:''' If alignment auto-save is enabled, realignment will be faster.
* '''Position jumps after GNSS outages''' - After the device has been in an area with no GNSS signal for a while (such as near tall buildings or obstacles), you might notice sudden jumps in the position when the signal returns. This happens because the device uses the GNSS signal to correct its estimated position, and the type of GNSS signal used is more sensitive to interference from nearby objects.
* '''Stand by mode''' - This feature allows calibration data to be stored for unlimited time, meaning that Dead Reckoning will work accurately even if a week has passed while vehicle was left in underground parking. Functionality will be present in 3.7.X firmware version, so current solution is  limited and tracker will lose Dead Reckoning alignment after an hour has passed since ignition OFF event. If vehicle was parked for less than 1 hour, track might be slightly tilted, but if parking lasts more than an hour - GNSS fix needs to be re-acquired. This applies for above and underground parking.
=== <u>Parameter list</u> ===
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<tr>
<th style="width:8%; vertical-align: middle; text-align: left;">Property ID in AVL packet</th>
<th style="width:15%; vertical-align: middle; text-align: center;">Property Name</th>
<th style="width:5%; vertical-align: middle; text-align: center;">Bytes</th>
<th style="width:10%; vertical-align: middle; text-align: center;">Min Value</th>
<th style="width:10%; vertical-align: middle; text-align: center;">Max Value</th>
<th style="width:5%; vertical-align: middle; text-align: center;">Multiplier</th>
<th style="width:5%; vertical-align: middle; text-align: center;">Units</th>
<th style="width:32%; vertical-align: middle; text-align: left;">Description</th>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">1433</td>
<td style="vertical-align: middle; text-align: center;">Dead Reckoning alignment status</td>
<td style="vertical-align: middle; text-align: center;">1</td>
<td style="vertical-align: middle; text-align: center;">0</td>
<td style="vertical-align: middle; text-align: center;">3</td>
<td style="vertical-align: middle; text-align: center;">1</td>
<td style="vertical-align: middle; text-align: center;"> </td>
<td style="vertical-align: middle; text-align: center;">[[Dead_Reckoning_feature#Dead_Reckoning_alignment_status|Dead Reckoning alignment status]]</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">1434</td>
<td style="vertical-align: middle; text-align: center;">Turning alignment</td>
<td style="vertical-align: middle; text-align: center;">1</td>
<td style="vertical-align: middle; text-align: center;">0</td>
<td style="vertical-align: middle; text-align: center;">100</td>
<td style="vertical-align: middle; text-align: center;">1</td>
<td style="vertical-align: middle; text-align: center;">%</td>
<td style="vertical-align: middle; text-align: center;">[[Dead_Reckoning_feature#Turning_alignment|Turning alignment]]</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">1435</td>
<td style="vertical-align: middle; text-align: center;">Straight alignment</td>
<td style="vertical-align: middle; text-align: center;">1</td>
<td style="vertical-align: middle; text-align: center;">0</td>
<td style="vertical-align: middle; text-align: center;">100</td>
<td style="vertical-align: middle; text-align: center;">1</td>
<td style="vertical-align: middle; text-align: center;">%</td>
<td style="vertical-align: middle; text-align: center;">[[Dead_Reckoning_feature#Straight alignment|Straight alignment]]</td>
</tr>
}}




Line 167: Line 34:
When device goes into sleep mode, some modules are turned off to consume less power. Listed below are the modules and scenarios that are turned off in common with all modes and those that are disabled specifically for the '''Online sleep''' mode:
When device goes into sleep mode, some modules are turned off to consume less power. Listed below are the modules and scenarios that are turned off in common with all modes and those that are disabled specifically for the '''Online sleep''' mode:
*GNSS
*GNSS
*Scenarios (Common):
**SNTP time synchronization


'''Online sleep entry conditions'''
'''Online sleep entry conditions'''
Line 179: Line 44:
**After Time Sync - device time is synchronized over NTP, NITZ, or GNSS satellites.
**After Time Sync - device time is synchronized over NTP, NITZ, or GNSS satellites.
**Always - device will enter sleep mode without time synchronization and GPS fix.
**Always - device will enter sleep mode without time synchronization and GPS fix.
*Sleep timeout is reached.
*There are no SMS messages being received.
*There are no SMS messages being received.
*Data sockets are closed (ignored when permanent link is enabled)
*Data sockets are closed (ignored when permanent link is enabled)
Line 188: Line 52:
At least one exit condition must be met:
At least one exit condition must be met:


*Movement is detected.
*Data sending as per Tracking settings.
*Periodic wake-up (if enabled).
*Periodic wake-up (if enabled).
*Button is pressed.


===Power off sleep===
===Power off sleep===
Line 198: Line 63:
*Modem
*Modem
*GNSS
*GNSS
*IMU (Inertial Measurement Unit)'''*'''
*FOTA WEB
*FOTA WEB
*Charger service'''*'''
'''*'''<sup>If power bank mode is selected and charger is enabled, device will not enter in Real Time clock sleep and stay in Power off sleep mode, which results in a similar mode to Deep Sleep.</sup>
*Scenarios (Common):
**LEDs (Navigation and Status)
**SNTP time synchronization


'''Power off entry conditions'''
'''Power off entry conditions'''
Line 218: Line 74:
**After Time Sync - device time is synchronized over NTP, NITZ, or GNSS satellites.
**After Time Sync - device time is synchronized over NTP, NITZ, or GNSS satellites.
**Always - device will enter sleep mode without time synchronization and GPS fix.
**Always - device will enter sleep mode without time synchronization and GPS fix.
*Sleep timeout is reached.
*There are no SMS messages being received.
*There are no SMS messages being received.
*Data sockets are closed (ignored when permanent link is enabled)
*Data sockets are closed (ignored when permanent link is enabled)
Line 224: Line 79:
*TCT is not connected.
*TCT is not connected.
*USB is not connected. This condition does not apply if Power bank mode is enabled.  
*USB is not connected. This condition does not apply if Power bank mode is enabled.  
'''Note:''' Starting with 3.7.0 Firmware,  USB presence check will be replaced with TCT connection check.


'''Power off sleep exit conditions'''
'''Power off sleep exit conditions'''
Line 231: Line 84:
At least one exit condition must be met:
At least one exit condition must be met:


*Movement is detected.
*USB is disconnected.
*USB is disconnected.
*Data sending as per Tracking settings.
*Button is pressed.
*Button is pressed.


Line 277: Line 130:


==Battery settings==
==Battery settings==
[[File:FTC_battery_settings_resized.gif|right]]


Battery settings allow selecting battery charge modes.
=== Power Bank Support ===
 
Possible charge modes:<br>
 
'''On need''' - battery will charge on need (will not charge in sleep mode)  <br>
'''After ignition ON''' - Battery will start charging when the ignition source is turned ON (will not charge in sleep mode) <br>
'''Always''' - battery will charge all the time, even in Online and Deep sleep modes. <br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
 
{{#switch: {{{model}}}
| ATC700
| ATM700 =  
== Power Bank Support ==
[[File:ATX Power Bank Support.png|right|500px]]
[[File:ATX Power Bank Support.png|right|500px]]
Asset Tracker devices have a power bank support functionality. It improves battery life by allowing for a larger discharge range for the battery and focusing on powering device from the connected power bank.
Power bank support functionality enhances battery longevity by enabling a wider discharge depth for the internal battery and prioritizing the use of external power, such as a connected power bank, to operate the device. Crucially, the internal battery will be protected from both undercharging and overcharging, ensuring optimal operational health.
 
=== Basic operation ===
Power bank support functionality checks for power bank connection via USB. When connection is established, it analyzes current battery voltage. If  current battery voltage value is in the range of minimum and maximum battery topoff threshold, device will prioritize external power source. If current battery voltage is not in the range (is too low), device will use switch charging mode or it is too high, it will stop charging.
 
'''Note:''' If the power bank is connected, but the battery is not charging, Asset tracker will check for USB connection status change every 10 seconds until battery charging starts. This logic will change with the new ATX hardware in future releases.
 
=== Power Bank mode and Power Off Sleep ===
When the battery reaches the upper topoff threshold, charging stops and the power bank enters sleep mode, causing the external voltage to drop below 4V. The device then shuts down remaining modules and enters Real Time Clock sleep mode.  
If the device is in Power Off Sleep mode, but not yet in Real Time Clock sleep mode and the timer to generate a record expires, the device wakes up, creates the record, and then repeats the cycle.
 
'''Note:''' Power bank detection relies on sensing external power, not the USB detection interrupt, because some power banks leave a small voltage (1-3V) on the line when sleeping.
}}


==Location settings==
==Location settings==
Line 335: Line 157:
==LED indication==
==LED indication==
[[File:FTC led settings.png|right|500 px]]
[[File:FTC led settings.png|right|500 px]]
This feature allows disabling or enabling status and navigation LEDs.
This feature allows disabling or enabling LED indication.  
<br>
<br>
<br>
<br>
Line 342: Line 164:


== Button settings ==
== Button settings ==
{{{model}}} button is being used for triggering various actions (e.g. ''Alarm'')
[[File:Button settings.png|right|500px]]
Multi action button functionality utilizes tracker button for various actions (e.g. ''Alarm''). Button employs click pattern logic.


===Click patterns ===
===Click patterns ===
Button has several click patterns, which allows to have possibility to control multiple actions by clicking it with different time intervals.  
Button has several click patterns, which allows to control multiple actions by clicking with different time intervals.  


<table class="nd-othertables_2" style="width:100%; margin-bottom: 30px;">
<table class="nd-othertables_2" style="width:100%; margin-bottom: 30px;">
Line 373: Line 196:
</table>
</table>


'''Note:''' If button pressed in such pattern, that it is not possible to detect any of the click patterns, then the button will be in tamper state. In this case, button will wait for release of the button and then at least 1 second of released state. After that, it will go back to normal state and wait for new click pattern.
'''Note:''' If a wrong pattern is pressed, the device will wait for the button to be released plus one second to reset. After the reset, it awaits a new click.
=== Power button ===
 
Power button has four click patterns, which can be used to trigger selected actions and generate event records with set event priority.
=== Actions ===
Available actions. They can bet set for all four click patterns. 
* '''Alarm''' - Generates high priority alarm event and sends to the server immediately.
* '''Alarm''' - Generates high priority alarm event and sends to the server immediately.
* '''None''' - Does not generate any events and does not send any data.  
* '''None''' - Does not generate any events.


=== Parameter list ===
=== Parameter list ===
Line 417: Line 239:
<tr>
<tr>
<td style="vertical-align: middle; text-align: center;">Power Off via Button</td>
<td style="vertical-align: middle; text-align: center;">Power Off via Button</td>
<td style="vertical-align: middle; text-align: center;"> 13087 <br> (236)</td>
<td style="vertical-align: middle; text-align: center;"> 13087 </td>
<td style="vertical-align: middle; text-align: center;"> Enable or disable powering off device via power off button. When functionality is enabled, the device can be turned off via power off button by holding it more than 5 seconds. </td>
<td style="vertical-align: middle; text-align: center;"> Enable or disable powering off device via power off button. When functionality is enabled, the device can be turned off via power off button by holding it more than 5 seconds. </td>
<td style="vertical-align: middle; text-align: left;"> - </td>
<td style="vertical-align: middle; text-align: left;"> - </td>

Latest revision as of 14:10, 4 December 2025

Configuration password

Protects the device from unauthorized access while using USB or Bluetooth to make any form of configuration changes.

  • Set password - Set the primary password for the device. Required to access the device every time using the USB or via Bluetooth connection.
  • Recovery password (optional) - in the event that the primary password is forgotten, the recovery password can be used as a backup to unlock the device configuration.













GNSS settings

In GNSS Source settings user can configure which GNSS system(s) to use.

List of configurable GNSS sources:

  • GPS
  • GPS + GLONASS
  • GPS + Galileo
  • GPS + BeiDou
  • GPS + GLONASS + Galileo + BeiDou



Power Saving settings

Puts the device into a power-saving mode, preserving the power consumption from the external source or the internal battery. The device enters this mode after the conditions are met.

Online sleep

  • In Online Sleep mode, the device manages the connection only when records need to be sent. The connection is opened at periodic intervals to send records and closed immediately after, without any timeout.
  • Changing the Permanent Link setting during Online Sleep will wake up the device to apply the new configuration.
  • With Permanent Link enabled, the device maintains a constant connection, sending records immediately as they are generated, rather than waiting for the next scheduled send. After sending connection remains open.

Disabled modules in Online sleep

When device goes into sleep mode, some modules are turned off to consume less power. Listed below are the modules and scenarios that are turned off in common with all modes and those that are disabled specifically for the Online sleep mode:

  • GNSS

Online sleep entry conditions

All entry conditions must be met:

  • Movement is not detected by the configured movement source.
  • Device time must be synchronized. This condition depends on the “Record Settings -> Saving / sending mode parameter.
    • After Position Fix - device time is synchronized with GNSS satellites and GPS fix is obtained.
    • After Time Sync - device time is synchronized over NTP, NITZ, or GNSS satellites.
    • Always - device will enter sleep mode without time synchronization and GPS fix.
  • There are no SMS messages being received.
  • Data sockets are closed (ignored when permanent link is enabled)
  • FOTA WEB connection is not in progress.

Online sleep exit conditions

At least one exit condition must be met:

  • Data sending as per Tracking settings.
  • Periodic wake-up (if enabled).
  • Button is pressed.

Power off sleep

Disabled modules in Power off sleep

When device goes into sleep mode, some modules are turned off to consume less power. Listed below are the modules and scenarios that are turned off in common with all modes and those that are disabled specifically for the Power off sleep mode:

  • Modem
  • GNSS
  • FOTA WEB

Power off entry conditions

All entry conditions must be met:

  • Movement is not detected by the configured movement source.
  • Device time must be synchronized. This condition depends on the “Record Settings -> Saving / sending mode parameter.
    • After Position Fix - device time is synchronized with GNSS satellites and GPS fix is obtained.
    • After Time Sync - device time is synchronized over NTP, NITZ, or GNSS satellites.
    • Always - device will enter sleep mode without time synchronization and GPS fix.
  • There are no SMS messages being received.
  • Data sockets are closed (ignored when permanent link is enabled)
  • FOTA WEB connection is not in progress.
  • TCT is not connected.
  • USB is not connected. This condition does not apply if Power bank mode is enabled.

Power off sleep exit conditions

At least one exit condition must be met:

  • USB is disconnected.
  • Data sending as per Tracking settings.
  • Button is pressed.

Time synchronization settings

Accurate system time is essential for proper event logging, record timestamping, and scheduling. The device supports 2 primary time synchronization sources: GNSS and SNTP. When one source becomes unavailable, the device can fall back to the other to maintain accurate time.

  • NTP Resync - how often a device should resynchronize its time. If the set value is not equal to zero, time resynchronization will occur periodically at time intervals to which this parameter is set.
  • NTP server 1 and NTP Server 2 let the user select which NTP server (s) will be used to re-synchronize time.

Prerequisites

Network Connectivity

  • To use SNTP, the device must connect to the internet

Configuration Access

  • TCT NTP settings (e.g., synchronization interval, NTP server domains) must be accessible for setup or modification.

Parameter Description

GNSS Time Synchronization

  • Trigger Condition: If a valid GNSS fix is available and the difference between the GNSS-provided time and the internal RTC is ≥ 3 seconds for a continuous period of 5 seconds, a time correction occurs.
  • Subsequent Synchronizations: After the first successful sync, the wait time before the device checks for another 3-second difference increases to 5 minutes to prevent excessive corrections.

SNTP Time Synchronization

  • Trigger Condition: If the device lacks a GNSS fix for 60 seconds, it attempts to synchronize time via SNTP'.
  • Resynchronization Interval: Defined by TCT NTP settings (default is 3 hours).
  • NTP Servers: 2 servers can be configured; by default, pool.ntp.org is the primary server and time.google.com is the fallback. If the first server is unreachable, the device automatically attempts the second.

Expected Behavior

GNSS Time Sync Process

  • When GNSS is active, the device continuously compares GNSS time to the internal clock.
  • If the 3-second offset persists for 5 seconds, the clock is updated immediately.
  • After the first correction, the device waits 5 minutes before checking for another large time discrepancy.

SNTP Time Sync Process

  • If no GNSS fix is available for 60 seconds (e.g., poor satellite signal, modem off, etc.), the device initiates an SNTP request.
  • If the primary NTP server is unreachable, it tries the secondary server.
  • The device repeats this SNTP synchronization after the configured interval (default 3 hours).

Fallback Mechanism

  • GNSS is the first choice for time synchronization.
  • When GNSS is not available, SNTP ensures the device clock remains accurate until a valid GNSS fix is restored.

Battery settings

Power Bank Support

Power bank support functionality enhances battery longevity by enabling a wider discharge depth for the internal battery and prioritizing the use of external power, such as a connected power bank, to operate the device. Crucially, the internal battery will be protected from both undercharging and overcharging, ensuring optimal operational health.

Location settings

This feature allows switching between location sources.
Parameter: Location source (param ID = 128).

Values:

GNSS (0) - enables GNSS, disables neighbouring cell tower IOs.

LBS (1) - Powers down GNSS, enables neighbouring cell tower IOs. Note, when Saving / Sending Mode (parameter ID: 107) is set to "After position fix" (SMS/GPRS parameter value = 0), Location Source "LBS" is not available.

Location Based Services (LBS)

The Location Based Services (LBS) feature manages and stores the information about detected network cells. This can be used to determine the approximate location of the device withou relying on GNSS. Activating this scenario disables GNSS.

Cell IOs settings are not user-configurable.

To represent a single cell, a total of 5 IOs are required: LAC, CellId, RSSI, MNC, MCC. A total of 4 neighbouring cells are supported, i.e. 5*4 = 20 IOs in total.

Note that depending on modem and network type, RSSI might not be available and is only roughly calculated.

LED indication

This feature allows disabling or enabling LED indication.



Button settings

Multi action button functionality utilizes tracker button for various actions (e.g. Alarm). Button employs click pattern logic.

Click patterns

Button has several click patterns, which allows to control multiple actions by clicking with different time intervals.

Click pattern Description
1 Click Button is pressed not longer than 2s.
2 Clicks Button is pressed not more than two times. If button was pressed more than 2 times, then double click will not be detected. Time between clicks can’t be longer than 1s.
Long Press Button is pressed and held for 2s to 5s.
Long Hold (Power Off via Button) Button is pressed and held for more than 5s.

Note: If a wrong pattern is pressed, the device will wait for the button to be released plus one second to reset. After the reset, it awaits a new click.

Actions

  • Alarm - Generates high priority alarm event and sends to the server immediately.
  • None - Does not generate any events.

Parameter list

[[Category:{{{model}}} Configuration]]
PARAMETER NAME PARAMETER ID (RELATED AVL ID) DESCRIPTION VALUES
Alarm - 1 Click 13014
(236)		 Action selection after 1 click method. Action will be triggered when button is pressed not longer than 2 seconds. 0 = Disable Disable scenario.

1 = Low priority Device makes an additional record with indication of event cause.

2 = High priority Device makes an additional record with high priority flag and immediately sends an event packet to the server by GPRS.
Alarm - 2 Clicks 13015
(236)		 Action selection after 2 clicks method. Action will be triggered when button is pressed not more than two times and time between clicks can not be longer than 1 second. 0 = Disable Disable scenario.

1 = Low priority Device makes an additional record with indication of event cause.

2 = High priority Device makes an additional record with high priority flag and immediately sends an event packet to the server by GPRS.
Alarm - Long Press 13016
(236)		 Action selection after long press method. Action will be triggered when button is pressed longer than 2 seconds. 0 = Disable Disable scenario.

1 = Low priority Device makes an additional record with indication of event cause.

2 = High priority Device makes an additional record with high priority flag and immediately sends an event packet to the server by GPRS.
Power Off via Button 13087 Enable or disable powering off device via power off button. When functionality is enabled, the device can be turned off via power off button by holding it more than 5 seconds. -
Retrieved from "https://wiki.teltonika-gps.com/index.php?title=Template:ATX_System&oldid=109570"