Jump to content
  • EN

Template:FTX System: Difference between revisions

From Teltonika Telematics Wiki
← Older edit
VisualWikitext
 
(34 intermediate revisions by 4 users not shown)
Line 1: Line 1:
==Ignition settings==
==Ignition settings==
[[File:FTC_ignition_resized.gif|right]]
[[File:TCT-Ignition-2.jpg|500px|right]]
Ignition source will be used to determine the ignition status of the vehicle.  
Ignition source will be used to determine the ignition status of the vehicle.  


Line 8: Line 8:
* '''Power Voltage''' - if the voltage is between High Voltage Level and Low Voltage Level (below ''Ignition Settings'' options) - ignition is ON; if the voltage is higher than High Voltage Level or lower than Low Voltage Level - ignition is OFF.
* '''Power Voltage''' - if the voltage is between High Voltage Level and Low Voltage Level (below ''Ignition Settings'' options) - ignition is ON; if the voltage is higher than High Voltage Level or lower than Low Voltage Level - ignition is OFF.
* '''Accelerometer''' - if movement sensor detects movement - ignition is ON; if movement is not detected - ignition is OFF;
* '''Accelerometer''' - if movement sensor detects movement - ignition is ON; if movement is not detected - ignition is OFF;
<!-- If model supports Manual CAN, then show -->
{{#if: {{FTX Pin Support List|model={{{model}}}|pin=Manual CAN}} | * '''Manual CAN''' - Ignition is on if configured Manual CAN frame is received and its value is within the configured limits. Ignition is off if the configured Manual CAN frame is received and its value is out of the configured limits. Manual CAN Ignition source needs to be configured in order to function properly;}}


More than one ignition source can be selected at the same time.  
More than one ignition source can be selected at the same time.  
Note:
Note:
When there are 2 or more sources selected, at least one condition has to be met to change Ignition status.<br> For Example, if both accelerometer and power voltage are selected, only one of the ignition detection conditions have to be met for ignition to be detected.
When there are 2 or more sources selected, at least one condition has to be met to change Ignition status.<br> For Example, if both accelerometer and power voltage are selected, only one of the ignition detection conditions have to be met for ignition to be detected.
<br>
<br>
Ignition status is used in power management and the following functionalities: [[{{{model}}} Features#Overspeeding|Overspeeding]], [[{{{model}}} Features#Odometer|Odometer]] and [[{{{model}}} Features#Trip|Trip]].<br>
{{#if: {{FTX Pin Support List|model={{{model}}}|pin=Manual CAN}} |
=== <u> Manual CAN Parameters list </u>===
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<tr>
<th style="width:1%; vertical-align: middle; text-align: center;">PARAMETER NAME</th>
<th style="width:1%; vertical-align: middle; text-align: center;">PARAMETER ID (RELATED AVL ID)</th>
<th style="width:5%; vertical-align: middle; text-align: center;">DESCRIPTION</th>
<th style="width:6%; vertical-align: middle; text-align: center;">VALUES</th>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;"> Manual CAN Slot </td>
<td style="vertical-align: middle; text-align: center;"> 321 </td>
<td style="vertical-align: middle; text-align: center;"> Manual CAN Ignition value source slot.</td>
<td style="vertical-align: middle; text-align: center;">
Minimum value = '''0'''  <br>
Maximum value = '''69''' <br>
Default value = '''0'''
</td>
</tr>
<tr>


Ignition status is used in power management and the following functionalities: [[{{{model}}} Features#Overspeeding|Overspeeding]], [[{{{model}}} Features#Odometer|Odometer]] and [[{{{model}}} Features#Trip|Trip]].<br>
<td style="vertical-align: middle; text-align: center;"> Data Mask </td>
<td style="vertical-align: middle; text-align: center;"> 322 </td>
<td style="vertical-align: middle; text-align: center;"> The mask to extract the Manual CAN Ignition value from CAN frame. </td>
<td style="vertical-align: middle; text-align: center;">
Minimum value = '''0(length)''' <br>
Maximum value = '''16(length)'''<br>
Default value = -
</td>
 
</tr>
<tr>
 
<td style="vertical-align: middle; text-align: center;"> Low range limit </td>
<td style="vertical-align: middle; text-align: center;"> 323 </td>
<td style="vertical-align: middle; text-align: center;"> The lower limit of the Manual CAN Ignition value.</td>
<td style="vertical-align: middle; text-align: center;">
Minimum value = '''0''' <br>
Maximum value = '''4294967295''' <br>
Default value = '''0''' </td>
 
</tr>
<tr>
 
<td style="vertical-align: middle; text-align: center;"> High range limit </td>
<td style="vertical-align: middle; text-align: center;"> 324 </td>
<td style="vertical-align: middle; text-align: center;"> The upper limit of the Manaual CAN Ignition value.</td>
<td style="vertical-align: middle; text-align: center;">
Minimum value = '''0''' <br>
Maximum value = '''4294967295''' <br>
Default value = '''1''' </td>
 
</tr>
<tr>
 
<td style="vertical-align: middle; text-align: center;"> MCAN data endianness </td>
<td style="vertical-align: middle; text-align: center;"> 320 </td>
<td style="vertical-align: middle; text-align: center;">Endianness of Ignition MCAN source frame.</td>
<td style="vertical-align: middle; text-align: center;">
Little endian.<br>
Big endian.</td>
 
</tr>
</table>
}}
 
 
== Smart Ignition ==
[[File:Smart Ignition TCT panel.png|right|right|500px]]
 
Smart Ignition feature detects ignition status by monitoring sudden external voltage jumps instead of manually predefined thresholds.
 
Smart Ignition is especially beneficial to clients who want to monitor the ignition status of a vehicle based on the voltage of the battery, regardless of the battery's health.
 
Smart Ignition Detection detects ignition “on” and “off” status automatically by monitoring last “Smart Ignition Duration” seconds of external voltage and comparing it to current external voltage value. Depending on whether external voltage value is higher or lower by Smart Ignition Delta value than external voltage set Smart Ignition Duration seconds ago, ignition state will change accordingly.
 
=== <u>Prerequisites and Important Settings </u> ===
* For Smart Ignition feature to work, Power voltage as ignition source must be selected in TCT Ignition settings.
* Smart Ignition feature executes Initial ignition detection process when enabled for the first time. More information [HERE – Initial Ignition detection].
 
=== <u> Basic Operation </u> ===
==== Initial ignition detection ====
* When the “Smart Ignition” feature is enabled for the first time, the system checks the ignition status by evaluating the external voltage for a period of 4 seconds.
The system does this by comparing the average voltage against predefined threshold values for different power sources (See Table: [[TEST-T#Initial Ignition Thresholds|Initial Ignition Thresholds]]. During this initial check, the ignition status will be considered “off.”
 
If the average voltage is higher than the “ignition threshold” for the selected power source, the ignition will be considered “on.”
If the average voltage is below the threshold, ignition is considered “off.”
 
* This process is done to avoid false ignition when the device is first powered on. After the initial check, Smart Ignition functionality will start monitoring external voltage for ignition state changes.
 
Initial ignition is checked after those events:
** Device was powered on.
** External voltage source was reconnected.
** Device was restarted.
** Ignition source of “Power Voltage” was disabled and enabled in the configurator.
** “Smart Ignition” was disabled and enabled in the configurator.
 
==== How the Power Source is Selected====
The voltage source is selected based on the current external voltage level. The system checks the voltage and compares it to predefined values for different power sources:
# The system starts with the 6V source.
# It checks if the external voltage is less than the maximum allowed voltage for that source (e.g., 8000mV for 6V).
# If the voltage is within the acceptable range for that source, it is selected, and the ignition threshold (e.g., 6100mV for 6V) is used to determine if ignition is on or off.
 
This process is repeated for higher voltage sources (e.g., 12V or 24V) if the voltage is too high for the initial 6V source.
 
==== Basic Operation ====
* When Smart Ignition is properly calibrated (see above information), it automatically monitors last “Smart Ignition Duration” seconds of external voltage and compares it to current external voltage value.
* If current external voltage value is higher than by “Smart Ignition Delta” than external voltage value  set “Smart Ignition Duration” seconds ago, “Ignition ON” event is detected.
* If current external voltage value is lower by “Smart Ignition Delta” than “Smart Ignition Duration” seconds ago “Ignition OFF” event is detected.
 
=== <u> Parameters list </u>===
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<tr>
<th style="width:1%; vertical-align: middle; text-align: center;">PARAMETER NAME</th>
<th style="width:1%; vertical-align: middle; text-align: center;">PARAMETER ID (RELATED AVL ID)</th>
<th style="width:5%; vertical-align: middle; text-align: center;">DESCRIPTION</th>
<th style="width:6%; vertical-align: middle; text-align: center;">VALUES</th>
</tr>
<tr>
 
<td style="vertical-align: middle; text-align: center;"> Smart Ignition  </td>
<td style="vertical-align: middle; text-align: center;"> 66201 </td>
<td style="vertical-align: middle; text-align: center;"> Turns ON or OFF Smart Ignition scenario. </td>
<td style="vertical-align: middle; text-align: left;"> '''0''' = Disable <br> '''1''' = Enable  </td>
 
</tr>
<tr>
 
<td style="vertical-align: middle; text-align: center;"> Smart Ignition Delta, mV </td>
<td style="vertical-align: middle; text-align: center;"> 66202 </td>
<td style="vertical-align: middle; text-align: center;"> How much external voltage must change, in miliVolts to detect ignition ON or OFF event.  </td>
<td style="vertical-align: middle; text-align: left;">
Minimum value = '''100''' <br>
Maximum value = '''2000'''  <br>
Default value = '''600'''
</td>
 
</tr>
<tr>
 
<td style="vertical-align: middle; text-align: center;"> Smart Ignition Duration, s </td>
<td style="vertical-align: middle; text-align: center;"> 66203 </td>
<td style="vertical-align: middle; text-align: center;"> Time interval, in seconds, used for comparing current external voltage against historical external voltage configured seconds ago.  </td>
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''2''' <br>
Maximum value = '''20'''  <br>
Default value = '''3'''  </td>
 
</tr>
</table>
 
 
==Movement settings==
[[File:TCT-Movement-2.jpg|500px|right]]
Movement source will be used to determine when a vehicle is on stop or moving.<br>
Possible movement sources:
* '''Accelerometer''' (movement) - if the accelerometer detects movement, the Vehicle is under MOVING mode; if there is no movement detected, the Vehicle on STOP mode;
* '''GNSS''' - if GPS fix is acquired and speed >= 5 km/h vehicle then the MOVING mode is used; if GPS speed <5 km/h, the Vehicle on STOP mode is used;
* '''Power voltage''' - Data acquisition > "moving" mode (Parameter state = 1) - when power voltage is >= low power voltage and <= high power voltage. By default low voltage is 13.2 V and the high voltage is 30 V;
<!-- If model supports DIN1/DIN2/DIN3, then show -->
{{#if: {{FTX Pin Support List|model={{{model}}}|pin=DIN1}} | * '''DIN 1''' - Data acquisition > "moving" mode (Parameter state = 1) - when voltage measured by DIN 1 is higher than 7.5V. Data acquisition > "on stop" mode (Parameter state = 0) - when voltage measured by DIN 1 is lower than 7.5V }} {{#if: {{FTX Pin Support List|model={{{model}}}|pin=DIN2}} | * '''DIN 2''' - Data acquisition > "moving" mode (Parameter state = 1) - when voltage measured by DIN 1 is higher than 7.5V. Data acquisition > "on stop" mode (Parameter state = 0) - when voltage measured by DIN 2 is lower than 7.5V }} {{#if: {{FTX Pin Support List|model={{{model}}}|pin=DIN3}} | * '''DIN 3''' - Data acquisition > "moving" mode (Parameter state = 1) - when voltage measured by DIN 1 is higher than 7.5V. Data acquisition > "on stop" mode (Parameter state = 0) - when voltage measured by DIN 3 is lower than 7.5V }}
<!-- If model supports Manual CAN, then show -->
{{#if: {{FTX Pin Support List|model={{{model}}}|pin=Manual CAN}} | * '''Manual CAN''' - Ignition is on if configured Manual CAN frame is received and its value is within the configured limits. Ignition is off if the configured Manual CAN frame is received and its value is out of the configured limits. Manual CAN movement source needs to be configured in order to function properly;
=== <u> Manual CAN Parameters list </u>===
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<tr>
<th style="width:1%; vertical-align: middle; text-align: center;">PARAMETER NAME</th>
<th style="width:1%; vertical-align: middle; text-align: center;">PARAMETER ID (RELATED AVL ID)</th>
<th style="width:5%; vertical-align: middle; text-align: center;">DESCRIPTION</th>
<th style="width:6%; vertical-align: middle; text-align: center;">VALUES</th>
</tr>
<tr>
 
<td style="vertical-align: middle; text-align: center;"> Manual CAN Slot </td>
<td style="vertical-align: middle; text-align: center;"> 325 </td>
<td style="vertical-align: middle; text-align: center;"> Manual CAN slot, where message with speed parameter is received. </td>
<td style="vertical-align: middle; text-align: center;">
Minimum value = '''0'''  <br>
Maximum value = '''69''' <br>
Default value = '''0'''
</td>
 
</tr>
<tr>
 
<td style="vertical-align: middle; text-align: center;"> Data Mask </td>
<td style="vertical-align: middle; text-align: center;"> 326 </td>
<td style="vertical-align: middle; text-align: center;"> Data mask used to extract speed parameter.</td>
<td style="vertical-align: middle; text-align: center;">
Minimum value = '''0(length)''' <br>
Maximum value = '''16(length)'''<br>
Default value = -
</td>
 
</tr>
<tr>
 
<td style="vertical-align: middle; text-align: center;"> Offset </td>
<td style="vertical-align: middle; text-align: center;"> 327 </td>
<td style="vertical-align: middle; text-align: center;"> Offset for speed value calculation.</td>
<td style="vertical-align: middle; text-align: center;">
Minimum value = '''-2147483647''' <br>
Maximum value = '''2147483647''' <br>
Default value = '''0''' </td>
 
</tr>
<tr>
 
<td style="vertical-align: middle; text-align: center;"> Coefficient </td>
<td style="vertical-align: middle; text-align: center;"> 328 </td>
<td style="vertical-align: middle; text-align: center;"> Coefficient for speed value calculation.</td>
<td style="vertical-align: middle; text-align: center;">
Minimum value = '''0.0000001''' <br>
Maximum value = '''1000000''' <br>
Default value = '''1''' </td>
 
</tr>
<tr>
 
<td style="vertical-align: middle; text-align: center;"> MCAN data endianness </td>
<td style="vertical-align: middle; text-align: center;"> 329 </td>
<td style="vertical-align: middle; text-align: center;">Endianness of Ignition MCAN source frame.</td>
<td style="vertical-align: middle; text-align: center;">
Little endian.<br>
Big endian.</td>
 
</tr>
</table>
}}
<br><br><br><br>
 
==Configuration password==
[[File:Configuration password.png|right|500 px]]
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.
<br><br><br><br><br><br><br><br><br><br><br><br>
 
==GNSS settings==
[[File:FTX gnss settings.png|right|500 px]]
In ''GNSS Source'' settings user can configure which GNSS system(s) to use.<br />
 
'''List of configurable GNSS sources:'''
* GPS
* GPS + GLONASS
* GPS + Galileo
* GPS + BeiDou
* GPS + GLONASS + Galileo + BeiDou
 
<br />
 
{{#switch: {{{model}}}
 
| FTC927
| FTM887
| FTC887
| FTC968 =
== Dead Reckoning ==


==Dead reckoning==
=== <u>Introduction</u> ===
=== <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>
'''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>
Line 22: Line 283:
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>
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 devices that support it. At the moment, it’s not possible to disable it.<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> ===
=== <u>Prerequisites</u> ===
Line 29: Line 290:
* Configuration
* Configuration
* Alignment
* Alignment


'''<u>Installation</u>'''<br>
'''<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
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 blocking the GNSS signal.
physical obstacles, like metal plates,  wires, are blocking the GNSS signal.


Good '''mounting''' examples:<br>
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>
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>


'''<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.''
''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 here
Parameter list can be found [[Template:FTX_System#Parameter_list|here]].


'''Dead Reckoning alignment status'''<br>
===== 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>
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>
Line 55: Line 326:
* '''3''' - Stable: Dead Reckoning alignment stage has been completed. Estimation stage is in progress.
* '''3''' - Stable: Dead Reckoning alignment stage has been completed. Estimation stage is in progress.


'''Turning alignment'''<br>
===== Turning alignment =====


The turning alignment is a 1-byte AVL ID ('''1434''') that indicates the current percentage of the turning alignment of the device.
The turning alignment is a 1-byte AVL ID ('''1434''') that indicates the current percentage of the turning alignment of the device.


'''Straight alignment'''<br>
===== Straight alignment =====


The straight alignment is a 1-byte AVL ID ('''1435''') that indicates the current percentage of the straight alignment of the device.
The straight alignment is a 1-byte AVL ID ('''1435''') that indicates the current percentage of the straight alignment of the device.
'''
Dead Reckoning realignment reason'''<br>
The Dead Reckoning realignment reason is a 1-byte AVL ID ('''1473''') that indicates the reason for the Dead Reckoning realignment. The possible values are:
* '''-1''' or '''-2:''' GNSS cross check failed. The algorithm detected that the estimated position differs from the GNSS position vastly.
* '''-3''' or '''-4:''' Unexpected vibrations detected.
* '''-5:''' Unexpected rotation detected.
* '''-6:''' GNSS signal quality dropped before the alignment was completed.
* '''-7:''' Abnormal reversing action detected.


'''<u>Alignment</u>'''<br>
'''<u>Alignment</u>'''<br>
Line 77: Line 338:
# The device must be '''stationary''' for at least 3 minutes.
# The device must be '''stationary''' for at least 3 minutes.
# A great number of '''left and right''' turns must be performed.
# A great number of '''left and right''' turns must be performed.
# The speed of the vehicle '''ideally''' must not exceed 50 km/h.
# 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.
# Avoid driving in underground tunnels or areas with poor GNSS signal.
[[File:Dead Reckoning TCT Swift .png|right|400px]]


'''Tip:''' To speed up alignment at the cost of some accuracy, you can enable swift alignment.
In order to speed up alignment at the cost of some accuracy, use '''Swift''' alignment.
 
=== <u>How It Works</u> ===
Dead Reckoning functionality consists of two stages:<br>
* '''Alignment stage''' - The algorithm tries to find the mounting orientation of the device.
* '''Estimation stage''' - The algorithm estimates the current position of the device based on IMU and ('''if available''') GNSS data.
 
'''<u>Alignment stage</u>'''
Before the algorithm can start estimating the position, it needs to calculate the mounting orientation of the device - this is called the '''alignment''' of IMU and vehicle frames. The result of the alignment is a set of angles that represent the orientation of the device in space, which is used to transform the IMU data into the vehicle frame during Estimation stage.<br>
 
Alignment is started automatically and constantly observes following parameters: <br>
 
* '''GNSS signal quality''' - The algorithm needs to have a good GNSS fix to calculate the mounting orientation. If during the alignment the signal quality drops below a certain threshold, the algorithm will trigger a realignment.
* '''IMU data''' - The algorithm constantly observes the received IMU data. If it detects that the device movement/rotation exceeded a certain threshold, it will trigger a realignment.<br>
 
'''Note:''' The Dead Reckoning alignment status AVL ID ('''1433''') will change from '''2''' (Coarse) to '''3''' (Stable). Positional data in records will contain Dead Reckoning data.
 
'''<u>Estimation stage</u>'''
Once the alignment stage is completed, the algorithm enters the estimation stage. The algorithm uses the IMU data to estimate the current position of the device, and if GNSS data is available, it uses it to correct the estimated position. The Dead Reckoning algorithm itself is based on the application of an extended Kalman filter (EKF), which operates in two main states:<br>
 
# '''Predict''' - The algorithm predicts the current position of the device using IMU sensor readings and the previously estimated position.
# '''Update''' - The predicted position is corrected using the calculated GNSS position from GNSS receiver.
 


=== <u>Limitations</u> ===
=== <u>Limitations</u> ===
Line 115: Line 355:


* '''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.
* '''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> ===
=== <u>Parameter list</u> ===
Line 136: Line 377:
<td style="vertical-align: middle; text-align: center;">1</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;"> </td>
<td style="vertical-align: middle; text-align: center;">Dead Reckoning alignment status</td>
<td style="vertical-align: middle; text-align: center;">[[Dead_Reckoning_feature#Dead_Reckoning_alignment_status|Dead Reckoning alignment status]]</td>
</tr>
</tr>
<tr>
<tr>
Line 146: Line 387:
<td style="vertical-align: middle; text-align: center;">1</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;">%</td>
<td style="vertical-align: middle; text-align: center;">Turning alignment</td>
<td style="vertical-align: middle; text-align: center;">[[Dead_Reckoning_feature#Turning_alignment|Turning alignment]]</td>
</tr>
</tr>
<tr>
<tr>
Line 156: Line 397:
<td style="vertical-align: middle; text-align: center;">1</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;">%</td>
<td style="vertical-align: middle; text-align: center;">Straight alignment</td>
<td style="vertical-align: middle; text-align: center;">[[Dead_Reckoning_feature#Straight alignment|Straight alignment]]</td>
</tr>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">1454</td>
<td style="vertical-align: middle; text-align: center;">Mounting angle - Z</td>
<td style="vertical-align: middle; text-align: center;">2</td>
<td style="vertical-align: middle; text-align: center;">-3600</td>
<td style="vertical-align: middle; text-align: center;">3600</td>
<td style="vertical-align: middle; text-align: center;">0.1</td>
<td style="vertical-align: middle; text-align: center;">°</td>
<td style="vertical-align: middle; text-align: center;">Device orientation in Z axis (yaw).</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">1455</td>
<td style="vertical-align: middle; text-align: center;">Mounting angle - Y</td>
<td style="vertical-align: middle; text-align: center;">2</td>
<td style="vertical-align: middle; text-align: center;">-3600</td>
<td style="vertical-align: middle; text-align: center;">3600</td>
<td style="vertical-align: middle; text-align: center;">0.1</td>
<td style="vertical-align: middle; text-align: center;">°</td>
<td style="vertical-align: middle; text-align: center;">Device orientation in Y axis (pitch).</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">1456</td>
<td style="vertical-align: middle; text-align: center;">Mounting angle - X</td>
<td style="vertical-align: middle; text-align: center;">2</td>
<td style="vertical-align: middle; text-align: center;">-3600</td>
<td style="vertical-align: middle; text-align: center;">3600</td>
<td style="vertical-align: middle; text-align: center;">0.1</td>
<td style="vertical-align: middle; text-align: center;">°</td>
<td style="vertical-align: middle; text-align: center;">Device orientation in X axis (roll).</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">1457</td>
<td style="vertical-align: middle; text-align: center;">Device position - X</td>
<td style="vertical-align: middle; text-align: center;">2</td>
<td style="vertical-align: middle; text-align: center;">-32768</td>
<td style="vertical-align: middle; text-align: center;">32767</td>
<td style="vertical-align: middle; text-align: center;">1</td>
<td style="vertical-align: middle; text-align: center;">m</td>
<td style="vertical-align: middle; text-align: center;">Linear displacement in X axis.</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">1458</td>
<td style="vertical-align: middle; text-align: center;">Device position - Y</td>
<td style="vertical-align: middle; text-align: center;">2</td>
<td style="vertical-align: middle; text-align: center;">-32768</td>
<td style="vertical-align: middle; text-align: center;">32767</td>
<td style="vertical-align: middle; text-align: center;">1</td>
<td style="vertical-align: middle; text-align: center;">m</td>
<td style="vertical-align: middle; text-align: center;">Linear displacement in Y axis.</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">1459</td>
<td style="vertical-align: middle; text-align: center;">Device position - Z</td>
<td style="vertical-align: middle; text-align: center;">2</td>
<td style="vertical-align: middle; text-align: center;">-32768</td>
<td style="vertical-align: middle; text-align: center;">32767</td>
<td style="vertical-align: middle; text-align: center;">1</td>
<td style="vertical-align: middle; text-align: center;">m</td>
<td style="vertical-align: middle; text-align: center;">Linear displacement in Z axis.</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">1460</td>
<td style="vertical-align: middle; text-align: center;">Fusion timestamp</td>
<td style="vertical-align: middle; text-align: center;">4</td>
<td style="vertical-align: middle; text-align: center;">0</td>
<td style="vertical-align: middle; text-align: center;">4294967295</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;">Fusion timestamp.</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">1461</td>
<td style="vertical-align: middle; text-align: center;">Fusion 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;">255</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;">Fusion status.</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">1462</td>
<td style="vertical-align: middle; text-align: center;">Sum of accelerometer axes std</td>
<td style="vertical-align: middle; text-align: center;">4</td>
<td style="vertical-align: middle; text-align: center;">0</td>
<td style="vertical-align: middle; text-align: center;">4294967295</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;">Sum of accelerometer axes standard deviation.</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">1463</td>
<td style="vertical-align: middle; text-align: center;">Sum of gyroscope axes std</td>
<td style="vertical-align: middle; text-align: center;">4</td>
<td style="vertical-align: middle; text-align: center;">0</td>
<td style="vertical-align: middle; text-align: center;">4294967295</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;">Sum of gyroscope axes standard deviation.</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">1464</td>
<td style="vertical-align: middle; text-align: center;">Accelerometer X axis std</td>
<td style="vertical-align: middle; text-align: center;">4</td>
<td style="vertical-align: middle; text-align: center;">0</td>
<td style="vertical-align: middle; text-align: center;">4294967295</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;">Standard deviation of accelerometer readings along x axis.</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">1465</td>
<td style="vertical-align: middle; text-align: center;">Accelerometer Y axis std</td>
<td style="vertical-align: middle; text-align: center;">4</td>
<td style="vertical-align: middle; text-align: center;">0</td>
<td style="vertical-align: middle; text-align: center;">4294967295</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;">Standard deviation of accelerometer readings along y axis.</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">1466</td>
<td style="vertical-align: middle; text-align: center;">Accelerometer Z axis std</td>
<td style="vertical-align: middle; text-align: center;">4</td>
<td style="vertical-align: middle; text-align: center;">0</td>
<td style="vertical-align: middle; text-align: center;">4294967295</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;">Standard deviation of accelerometer readings along z axis.</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">1467</td>
<td style="vertical-align: middle; text-align: center;">Gyroscope X axis std</td>
<td style="vertical-align: middle; text-align: center;">4</td>
<td style="vertical-align: middle; text-align: center;">0</td>
<td style="vertical-align: middle; text-align: center;">4294967295</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;">Standard deviation of gyroscope readings along x axis.</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">1468</td>
<td style="vertical-align: middle; text-align: center;">Gyroscope Y axis std</td>
<td style="vertical-align: middle; text-align: center;">4</td>
<td style="vertical-align: middle; text-align: center;">0</td>
<td style="vertical-align: middle; text-align: center;">4294967295</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;">Standard deviation of gyroscope readings along y axis.</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">1469</td>
<td style="vertical-align: middle; text-align: center;">Gyroscope Z axis std</td>
<td style="vertical-align: middle; text-align: center;">4</td>
<td style="vertical-align: middle; text-align: center;">0</td>
<td style="vertical-align: middle; text-align: center;">4294967295</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;">Standard deviation of gyroscope readings along z axis.</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">1470</td>
<td style="vertical-align: middle; text-align: center;">Acceleration X axis</td>
<td style="vertical-align: middle; text-align: center;">4</td>
<td style="vertical-align: middle; text-align: center;">-2147483648</td>
<td style="vertical-align: middle; text-align: center;">2147483647</td>
<td style="vertical-align: middle; text-align: center;">0.000001</td>
<td style="vertical-align: middle; text-align: center;">m/s^2</td>
<td style="vertical-align: middle; text-align: center;">Acceleration in x axis.</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">1471</td>
<td style="vertical-align: middle; text-align: center;">Acceleration Y axis</td>
<td style="vertical-align: middle; text-align: center;">4</td>
<td style="vertical-align: middle; text-align: center;">-2147483648</td>
<td style="vertical-align: middle; text-align: center;">2147483647</td>
<td style="vertical-align: middle; text-align: center;">0.000001</td>
<td style="vertical-align: middle; text-align: center;">m/s^2</td>
<td style="vertical-align: middle; text-align: center;">Acceleration in y axis.</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">1472</td>
<td style="vertical-align: middle; text-align: center;">Acceleration Z axis</td>
<td style="vertical-align: middle; text-align: center;">4</td>
<td style="vertical-align: middle; text-align: center;">-2147483648</td>
<td style="vertical-align: middle; text-align: center;">2147483647</td>
<td style="vertical-align: middle; text-align: center;">0.000001</td>
<td style="vertical-align: middle; text-align: center;">m/s^2</td>
<td style="vertical-align: middle; text-align: center;">Acceleration in z axis.</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">1473</td>
<td style="vertical-align: middle; text-align: center;">Dead Reckoning realignment reason.</td>
<td style="vertical-align: middle; text-align: center;">1</td>
<td style="vertical-align: middle; text-align: center;">-128</td>
<td style="vertical-align: middle; text-align: center;">127</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 realignment reason.</td>
</tr>
</table>
==Movement settings==
[[File:TCT-Movement-1.png|500px|right]]
Movement source will be used to determine when a vehicle is on stop or moving.<br>
Possible movement sources:
* '''Accelerometer''' (movement) - if the accelerometer detects movement, the Vehicle is under MOVING mode; if there is no movement detected, the Vehicle on STOP mode;
* '''GNSS''' - if GPS fix is acquired and speed >= 5 km/h vehicle then the MOVING mode is used; if GPS speed <5 km/h, the Vehicle on STOP mode is used;
* '''Power voltage''' - Data acquisition > "moving" mode (Parameter state = 1) - when power voltage is >= low power voltage and <= high power voltage. By default low voltage is 13.2 V and the high voltage is 30 V;
<!-- If model supports DIN1/DIN2/DIN3, then show -->
{{#if: {{FTX Pin Support List|model={{{model}}}|pin=DIN1}} | * '''DIN 1''' - Data acquisition > "moving" mode (Parameter state = 1) - when voltage measured by DIN 1 is higher than 7.5V. Data acquisition > "on stop" mode (Parameter state = 0) - when voltage measured by DIN 1 is lower than 7.5V }} {{#if: {{FTX Pin Support List|model={{{model}}}|pin=DIN2}} | * '''DIN 2''' - Data acquisition > "moving" mode (Parameter state = 1) - when voltage measured by DIN 1 is higher than 7.5V. Data acquisition > "on stop" mode (Parameter state = 0) - when voltage measured by DIN 2 is lower than 7.5V }} {{#if: {{FTX Pin Support List|model={{{model}}}|pin=DIN3}} | * '''DIN 3''' - Data acquisition > "moving" mode (Parameter state = 1) - when voltage measured by DIN 1 is higher than 7.5V. Data acquisition > "on stop" mode (Parameter state = 0) - when voltage measured by DIN 3 is lower than 7.5V }}
<br><br><br><br>


==Configuration password==
}}
[[File:Configuration password.png|right|500 px]]
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.
<br><br><br><br><br><br><br><br><br><br><br><br>
 
==GNSS settings==
[[File:FTX gnss settings.png|right|500 px]]
In ''GNSS Source'' settings user can configure which GNSS system(s) to use.<br />
 
'''List of configurable GNSS sources:'''
* GPS
* GPS + GLONASS
* GPS + Galileo
* GPS + BeiDou
* GPS + GLONASS + Galileo + BeiDou


<br />
==Movement delay==
==Movement delay==
[[File:Movement Delays.png|right|500 px]]
[[File:Movement Delays.png|right|500 px]]
Line 403: Line 415:


==Power Saving settings==
==Power Saving settings==
{{#switch: {{{model}}}
| #default =
[[File:FTX power saving settings.png|right|500 px]]
[[File:FTX power saving settings.png|right|500 px]]
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.
| ATC700
 
| ATM700 =
*'''Timeout''' - After timeout is reached, and conditions are met for the sleep mode, the device goes into sleep mode.
[[File:ATX power saving settings.png|right|500 px]]
 
}}
Puts the device into a power-saving mode, preserving the power consumption from the external source or the internal battery.
{{#switch: {{{model}}}
| #default =
| ATC700
| ATM700 =
}}
===Online sleep===
===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.
*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.
Line 426: Line 446:
**Jamming Detection
**Jamming Detection
**Eco Driving
**Eco Driving
*CAN (''After 5 seconds of no activity on CAN bus. If no CAN activity for 5 seconds, CAN commands, e.g. periodical manual CAN commands, are disabled'')


'''Online sleep entry conditions'''
'''Online sleep entry conditions'''
Line 441: Line 462:
*Data sockets are closed (ignored when permanent link is enabled)
*Data sockets are closed (ignored when permanent link is enabled)
*FOTA WEB connection is not in progress.
*FOTA WEB connection is not in progress.
'''CAN and BLE sleep entry conditions'''
All entry conditions must be met for CAN and BLE respectively:
*CAN
**No communication with Main module for 1 second.
**No configured CAN data is read for 5 seconds.
**At least 1 second has passed since the last module wake up.
*BLE
**Main module enters Online/Deep sleep modes
**No communication with Main module for 1 second.
**At least 1 second has passed since the last module wake up.


'''Online sleep exit conditions'''
'''Online sleep exit conditions'''
Line 450: Line 486:
*Periodic wake-up (if enabled).
*Periodic wake-up (if enabled).


'''CAN and BLE sleep exit conditions'''
*CAN
**Main module sends any request via UART.
**Any CAN data is present on the CAN bus.
*BLE
**The device can wake up from sleep when a DIN input changes (detected through the external MCU).
**DIN pins remain active in sleep mode and can be used as wake-up sources for the device.
{{#switch: {{{model}}}
| #default =
===Deep sleep===
===Deep sleep===
*During Deep Sleep mode, the device generates and stores periodic records.
*During Deep Sleep mode, the device generates and stores periodic records.
Line 467: Line 516:
*Data sockets are closed (checks if record sending socket link is open)
*Data sockets are closed (checks if record sending socket link is open)
*FOTA WEB connection is not in progress.
*FOTA WEB connection is not in progress.
'''CAN and BLE sleep entry conditions'''
All entry conditions must be met for CAN and BLE respectively:
*CAN
**No communication with Main module for 1 second.
**No configured CAN data is read for 5 seconds.
**At least 1 second has passed since the last module wake up.
*BLE
**Main module enters Online/Deep sleep modes.
**No communication with Main module for 1 second.
**At least 1 second has passed since the last module wake up.


'''Deep sleep exit conditions'''
'''Deep sleep exit conditions'''
Line 477: Line 539:
*Periodic wake-up (if enabled).
*Periodic wake-up (if enabled).


'''CAN and BLE sleep exit conditions'''
*CAN
**Main module sends any request via UART.
**Any CAN data is present on the CAN bus.
*BLE
**Main module sends any request related to 1 wire or DOUT overcurrent.
**BLE module sends an event - DIN.
'''Disabled modules in Deep sleep'''
'''Disabled modules in Deep sleep'''


Line 496: Line 567:
**Jamming Detection
**Jamming Detection
**Eco Driving
**Eco Driving
 
*CAN (''After 5 seconds of no activity on CAN bus. If no CAN activity for 5 seconds, CAN commands, e.g. periodical manual CAN commands, are disabled'')
*BLE scanning (''Active BLE scanning is being turned off on entering any sleep mode and turned back on when exiting sleep mode'')
| ATC700
| ATM700 =
}}
===Power off sleep===
===Power off sleep===


Line 518: Line 593:
**Jamming Detection
**Jamming Detection
**Eco Driving
**Eco Driving
 
*CAN (''does not receive requests, does not read CAN bus messages'')
{{#if: {{FTX Pin Support List|model={{{model}}}|pin=DIN1}} | *BLE
**Anything connected or enabled by BLE module, including PIN's (1 wire, DIN's, DOUT's, BLE as a peripheral) }} {{#if: {{FTX Pin Support List|model={{{model}}}|pin=DIN2}} | *BLE
**Anything connected or enabled by BLE module, including PIN's (1 wire, DIN's, DOUT's, BLE as a peripheral) }} {{#if: {{FTX Pin Support List|model={{{model}}}|pin=DIN3}} | *BLE
**Anything connected or enabled by BLE module, including PIN's (1 wire, DIN's, DOUT's, BLE as a peripheral)}} {{#if: {{FTX Pin Support List|model={{{model}}}|pin=DOUT1}} | *BLE
**Anything connected or enabled by BLE module, including PIN's (1 wire, DIN's, DOUT's, BLE as a peripheral)}} {{#if: {{FTX Pin Support List|model={{{model}}}|pin=DOUT2}} | *BLE
**Anything connected or enabled by BLE module, including PIN's (1 wire, DIN's, DOUT's, BLE as a peripheral)}}
{{#if: {{FTX Pin Support List|model={{{model}}}|pin=DOUT3}} | *BLE
**Anything connected or enabled by BLE module, including PIN's (1 wire, DIN's, DOUT's, BLE as a peripheral)}}
{{#if: {{FTX Pin Support List|model={{{model}}}|pin=1-Wire}} | *BLE
**Anything connected or enabled by BLE module, including PIN's (1 wire, DIN's, DOUT's, BLE as a peripheral)}} {{#if: {{FTX Pin Support List|model={{{model}}}|pin=Manual CAN}} | *BLE
**Anything connected or enabled by BLE module, including PIN's (1 wire, DIN's, DOUT's, BLE as a peripheral)}}
'''Power off entry conditions'''
'''Power off entry conditions'''


Line 536: Line 622:
{{#if: {{FTX Pin Support List|model={{{model}}}|pin=DIN1}} | *DIN1 is deactivated }} {{#if: {{FTX Pin Support List|model={{{model}}}|pin=DIN2}} | *DIN2 is deactivated }} {{#if: {{FTX Pin Support List|model={{{model}}}|pin=DIN3}} | *DIN3 is deactivated }}
{{#if: {{FTX Pin Support List|model={{{model}}}|pin=DIN1}} | *DIN1 is deactivated }} {{#if: {{FTX Pin Support List|model={{{model}}}|pin=DIN2}} | *DIN2 is deactivated }} {{#if: {{FTX Pin Support List|model={{{model}}}|pin=DIN3}} | *DIN3 is deactivated }}


'''CAN and BLE shutdown entry conditions'''
*CAN
**Main module enters power off sleep mode.
*BLE
**Main module enters power off sleep mode.
'''Power off sleep exit conditions'''
'''Power off sleep exit conditions'''


Line 542: Line 635:
*Ignition is ON.
*Ignition is ON.
*Movement is detected.
*Movement is detected.
'''CAN and BLE shutdown exit conditions'''
*CAN
**Main module wakes up and restarts CAN module.
*BLE
**Main module wakes up and restarts BLE module.
<!-- If model supports DIN1/DIN2/DIN3, then show -->
<!-- If model supports DIN1/DIN2/DIN3, then show -->
{{#if: {{FTX Pin Support List|model={{{model}}}|pin=DIN1}} | *DIN1 is activated }} {{#if: {{FTX Pin Support List|model={{{model}}}|pin=DIN2}} | *DIN2 is activated }} {{#if: {{FTX Pin Support List|model={{{model}}}|pin=DIN3}} | *DIN3 is activated }}
{{#if: {{FTX Pin Support List|model={{{model}}}|pin=DIN1}} | *DIN1 is activated }} {{#if: {{FTX Pin Support List|model={{{model}}}|pin=DIN2}} | *DIN2 is activated }} {{#if: {{FTX Pin Support List|model={{{model}}}|pin=DIN3}} | *DIN3 is activated }}
Line 603: Line 702:
<br>
<br>
<br>
<br>
{{#switch: {{{model}}}
| ATC700
| ATM700 =
== Power Bank Support ==
[[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.
=== 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 RTC sleep mode, indicated by the log: “USB disconnected, entering RTC sleep”.
If the device is in Power Off Sleep mode, but not yet in RTC sleep and the timer to generate a record expires, the device wakes up, creates the record, and then repeats the cycle. This is shown by the log: “Wakeup triggered. Current Mode: Power Off Sleep, Reason: RTC timer”.
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==
[[File:Location settings.png|right|500 px]]
[[File:Location settings.png|right|500 px]]
This feature allows switching between location sources.<br>
This feature allows switching between location sources.<br>
'''Location Source'''
Parameter: Location source (param ID = 128).
*'''GNSS''' - Enables GNSS, disables neighbouring cell tower IOs.
 
*'''LBS''' - Powers down GNSS, enables neighbouring cell tower IOs.
Values:
<br>
 
<br>
GNSS (0) - enables GNSS, disables neighbouring cell tower IOs.  
<br>
 
<br>
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==
==LED indication==
Line 695: Line 823:
*The device should be '''mounted securely''' in the vehicle to avoid incorrect readings.  
*The device should be '''mounted securely''' in the vehicle to avoid incorrect readings.  
*External interference affecting GNSS or accelerometer accuracy should be minimized.
*External interference affecting GNSS or accelerometer accuracy should be minimized.
==Time zone settings==
[[File:Time zone settings.png|right|500 px]]
The Time zone feature allows configuring the local time reference used for [[{{{model|}}}_Tracking_settings#Records_schedule|Records Schedule]]
It ensures that all wake-up and data transmission events follow the selected local time instead of UTC. When a specific time zone is set, the device automatically adjusts scheduled actions according to the defined offset,
This feature helps synchronize device behavior with the user’s regional time settings, ensuring accurate timing for periodic data transmission.
Default value: GMT+00:00
<br>
<br>
<br>
<br>


[[Category:{{{model}}} Configuration]]
[[Category:{{{model}}} Configuration]]

Latest revision as of 07:43, 19 January 2026

Retrieved from "https://wiki.teltonika-gps.com/index.php?title=Template:FTX_System&oldid=110477"