Jump to content
  • EN

Template:FTX System: Difference between revisions

From Teltonika Telematics Wiki
← Older edit
VisualWikitext
No edit summary
No edit summary
 
(48 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>
<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>
}}


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>


== Smart Ignition ==
== Smart Ignition ==
[[File:Smart Ignition TCT panel.png|right|500px]]
[[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 feature detects ignition status by monitoring sudden external voltage jumps instead of manually predefined thresholds.  
Line 101: Line 172:


==Movement settings==
==Movement settings==
[[File:TCT-Movement-1.png|500px|right]]
[[File:TCT-Movement-2.jpg|500px|right]]
Movement source will be used to determine when a vehicle is on stop or moving.<br>
Movement source will be used to determine when a vehicle is on stop or moving.<br>
Possible movement sources:
Possible movement sources:
Line 109: Line 180:
<!-- 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}} | * '''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: {{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>
<br><br><br><br>


Line 128: Line 267:
* GPS + BeiDou
* GPS + BeiDou
* GPS + GLONASS + Galileo + BeiDou
* GPS + GLONASS + Galileo + BeiDou
* GPS + QZSS
* GPS + QZSS + GLONASS
* GPS + QZSS + Galileo
* GPS + QZSS + BeiDou
* GPS + QZSS + GLONASS + Galileo + BeiDou


<br />
<br />
Line 133: Line 277:
{{#switch: {{{model}}}
{{#switch: {{{model}}}


| FTC927
| FTM887
| FTM887
| FTC887
| FTC887
| FTC968 =
| FTC968 =
== Dead Reckoning ==
== 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>
'''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 153: Line 296:
'''<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. DIN1 should be connected to the vehicle ignition (''' applicable to trackers with DIN1'''), it will be used to detect both ignition status and movement, ensuring optimal performance. 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.  
physical obstacles, like metal plates,  wires, are blocking the GNSS signal.


Good '''mounting''' examples:<br>
Good '''mounting''' examples ( <span style="color:red">'''If vehicle has a heated windshield, you should look for an alternative mounting location in the trunk, on some sturdy metal closer to backseat window'''</span>):<br>
<div style="display: flex; flex-direction: row;">
<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 under the front dashboard in the middle of the car.jpg|thumb|left|280px|Dashboard in the middle of the car mount]]
Line 185: Line 327:
* '''2''' - Coarse: Dead Reckoning is in alignment stage.
* '''2''' - Coarse: Dead Reckoning is in alignment stage.
* '''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.
* '''99''' - Standby: Dead Reckoning is in standby mode ('''NOTE''': this status is availabe with 3.7.X or newer firmware version)


===== Turning alignment =====
===== 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 =====
===== 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.
'''


'''<u>Alignment</u>'''<br>
'''<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:
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.
# The device must be '''stationary''' with clear sky visibility 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 be bellow 10 km/h or exceed 50 km/h.
# Vehicle speed during alignment should be between 10 km/h and 100 km/h, with varying speeds preferred over extended constant-speed driving.
# Avoid driving in underground tunnels or areas with poor GNSS signal.
# Avoid driving in underground tunnels or areas with poor GNSS signal, otherwise alignment needs to be restarted from the second step.
[[File:Dead Reckoning TCT Swift .png|right|400px]]
[[File:Dead Reckoning TCT Swift .png|right|400px]]


In order to speed up alignment at the cost of some accuracy, use '''Swift''' alignment.
=== <u>Standby mode</u> ===
 
Standby Mode preserves Dead Reckoning calibration indefinitely, ensuring accurate position estimation after extended GNSS outages (e.g., a week in underground parking), and supports unlimited duration in this mode while maintaining full calibration integrity.
 
Standby Mode has two behavior options:
* '''Realignment''' – Calibration alignment is discarded after the Standby Timeout period.
* '''Preserve alignment''' – Calibration alignment is retained during prolonged stationary periods.
 
 
'''<u>Prerequisites and important Settings</u>'''<br>
* If the device is remounted, send the DR_Reset SMS command and perform a full recalibration. This ensures all orientation- and sensor alignment parameters are refreshed, preventing inaccurate Dead Reckoning calculations after the installation change.
 
'''<u>Basic Operation</u>'''<br>
 
'''Entering Standby Mode'''
 
The device can enter Standby Mode in two scenarios:
* No movement detected
If the device detects absence of movement, Dead Reckoning enters Standby Mode after the timeout defined by '''Standby timeout (ID 124)''' elapses.
* Device enters sleep mode
When the device transitions into sleep mode, the GNSS receiver is switched to power saving mode.
 
Before GNSS powers down, Dead Reckoning enters Standby Mode '''immediately''', the scenario is paused, and the device proceeds into sleep mode.
 
'''Exiting Standby Mode'''
 
Standby Mode can be exited in the following cases:
* Movement is detected
When movement is detected, the device exits Standby Mode and resumes normal Dead Reckoning operation. If '''no movement is detected''', Dead Reckoning remains in Standby Mode.
 


=== <u>Limitations</u> ===
=== <u>Limitations</u> ===
Line 209: Line 380:
* '''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.
* '''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.
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. .
* '''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.
* '''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.
'''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.
* '''Position jumps after GNSS outages''' - Multipath occurs when reflected or diffracted GNSS signals reach the receiver, causing position errors. Since Dead Reckoning depends on GNSS for continuous correction, these multipath induced inaccuracies can lead to visible position jumps, especially in urban areas with tall buildings or obstructions.
* '''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.
[[File:GNSS Multipath.png|350px]]


=== <u>Parameter list</u> ===
=== <u>AVL ID list</u> ===
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<tr>
<tr>
Line 234: Line 405:
<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;">0</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;">99</td>
<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_feature#Dead_Reckoning_alignment_status|Dead Reckoning alignment status]]</td>
<td style="vertical-align: middle; text-align: center;">[[{{{model}}}_System#Dead_Reckoning_alignment_status|Dead Reckoning alignment status]]</td>
</tr>
</tr>
<tr>
<tr>
Line 247: Line 418:
<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_feature#Turning_alignment|Turning alignment]]</td>
<td style="vertical-align: middle; text-align: center;">[[{{{model}}}_System#Turning_alignment|Turning alignment]]</td>
</tr>
</tr>
<tr>
<tr>
Line 257: Line 428:
<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_feature#Straight alignment|Straight alignment]]</td>
<td style="vertical-align: middle; text-align: center;">[[{{{model}}}_System#Straight alignment|Straight alignment]]</td>
</tr>
</table>
 
=== <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>
<tr>
<td style="vertical-align: middle; text-align: center;">123</td>
<td style="vertical-align: middle; text-align: center;">Alignment auto-save</td>
<td style="vertical-align: middle; text-align: center;">-</td>
<td style="vertical-align: middle; text-align: center;">0</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;">This option saves calibration data to device memory, enabling a faster recalibration after device restart. <br> '''0''' = Disable <br> '''1''' = Enable  </td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">124</td>
<td style="vertical-align: middle; text-align: center;">Standby timeout</td>
<td style="vertical-align: middle; text-align: center;">-</td>
<td style="vertical-align: middle; text-align: center;">1</td>
<td style="vertical-align: middle; text-align: center;">65535</td>
<td style="vertical-align: middle; text-align: center;">1</td>
<td style="vertical-align: middle; text-align: center;">(s) seconds</td>
<td style="vertical-align: middle; text-align: center;">The standby timeout is the time after which device will attempt to correct the position based on correction strategy.<br>  Default value = '''1800''' </td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">125</td>
<td style="vertical-align: middle; text-align: center;">Standby mode</td>
<td style="vertical-align: middle; text-align: center;">-</td>
<td style="vertical-align: middle; text-align: center;">0</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;">The standby mode is the mode in which the device will attempt to correct the position based on correction strategy. <br>'''0''' = Realignment<br>'''1''' = Preserve alignment</td>
</tr>
</table>


}}
}}
Line 274: Line 490:
<br />
<br />


==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]]
 
}}
===Online sleep===
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 =
}}
<br><br><br>
===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.
*Changing the Permanent Link setting during Online Sleep will wake up the device to apply the new configuration.
*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.
*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.
*All listed entry conditions must be met in order to enter Online Sleep.
*At least one exit condition must be met in order to wake up from Online Sleep.
<br>


'''Disabled modules in Online sleep'''
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse; border-bottom: 3px solid #336699;">


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:
<tr>
*GNSS
<th style="width:1%; vertical-align: middle; text-align: center;">Module</th>
*Scenarios (Common):
<th style="width:1%; vertical-align: middle; text-align: center;">Entry Conditions</th>
**Odometer
<th style="width:5%; vertical-align: middle; text-align: center;">Exit conditions</th>
**Data acquisition
<th style="width:6%; vertical-align: middle; text-align: center;">Disabled functions</th>
**SNTP time synchronization
**Overspeeding
**Trip
**Unplug Detection
**Jamming Detection
**Eco Driving


'''Online sleep entry conditions'''
</tr>
<tr>


All entry conditions must be met:
<td style="vertical-align: middle; text-align: left; border-bottom: 3px solid #336699;">'''''Main'''''</td>
<td style="vertical-align: middle; text-align: left; min-width: 550px; border-bottom: 3px solid #336699;">
*Configured '''Ignition source''' is off.<br>
*Movement is not detected by the configured '''Movement source'''.<br>
*Device time must be synchronized, as this condition depends on the ''Record Settings -> Saving / sending mode'' parameter<br>
**'''After Position Fix''' - device time is synchronized with GNSS satellites and GPS fix is obtained.<br>
**'''After Time Sync''' - device time is synchronized over NTP, NITZ, or GNSS satellites.<br>
**'''Always''' - device will enter sleep mode without time synchronization and GPS fix.<br>
*Sleep timeout is reached.<br>
*No SMS messages are being received.<br>
*No open Data sockets (ignored with enabled permanent link)<br>
*No active FOTA WEB connection progress.<br>
</td>
<td style="vertical-align: middle; horizontal-align: center; min-width: 150px; border-bottom: 3px solid #336699;">
*Ignition is ON.<br>
*Movement is detected.<br>
{{#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 }}
*Periodic wake-up (if enabled).<br></td>
<td style="vertical-align: middle; horizontal-align: center; min-width: 100px; border-bottom: 3px solid #336699;">
*GNSS<br>
*Odometer<br>
*Data acquisition<br>
*SNTP time synchronization<br>
*Overspeeding<br>
*Trip<br>
*Jamming Detection<br>
*Eco Driving<br>
</td>


*Ignition (configured ignition source) is off.
</tr>
*Movement is not detected by the configured movement source.
<tr>
*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.
*Sleep timeout is reached.
*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'''
{{#if: {{FTX Pin Support List|model={{{model}}}|pin=Manual CAN}}
|<td style="vertical-align: middle; text-align: left; border-bottom: 3px solid #336699;">'''''CAN'''''</td>
<td style="vertical-align: middle; text-align: left; border-bottom: 3px solid #336699;">
*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.</td>
<td style="vertical-align: middle; text-align: left; min-width: 150px; border-bottom: 3px solid #336699;"">
*Main module sends any request via UART.<br>
*Any CAN data is present on the CAN bus.<br></td>
<td style="vertical-align: middle; text-align: left; border-bottom: 3px solid #336699;">
*CAN
</td>
}}


At least one exit condition must be met:
</tr>
<tr>


*Ignition is ON.
{{#if: {{FTX Pin Support List|model={{{model}}}|pin=BT}}
*Movement is detected.
|<td style="vertical-align: middle; text-align: left;">'''''BLE'''''</td>
*Periodic wake-up (if enabled).
<td style="vertical-align: middle; text-align: left;">
*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.</td>
<td style="vertical-align: middle; text-align: left; min-width: 150px;"">
*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.</td>
<td style="vertical-align: middle; text-align: left;">
*BLE scanning</td>
}}


===Deep sleep===
</tr>
</table>
<br><br><br>
===Deep Sleep===
{{#switch: {{{model}}}
| #default =  
*During Deep Sleep mode, the device generates and stores periodic records.
*During Deep Sleep mode, the device generates and stores periodic records.
*All listed entry conditions must be met in order to enter Deep Sleep.
*At least one exit condition must be met in order to wake up from Deep Sleep.
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse; border-bottom: 3px solid #336699;">


'''Deep sleep entry conditions'''
<tr>
<th style="width:1%; vertical-align: middle; text-align: center;">Module</th>
<th style="width:1%; vertical-align: middle; text-align: center;">Entry Conditions</th>
<th style="width:5%; vertical-align: middle; text-align: center;">Exit conditions</th>
<th style="width:6%; vertical-align: middle; text-align: center;">Disabled functions</th>


All entry conditions must be met:
</tr>
<tr>


*Ignition (configured ignition source) is off.
<td style="vertical-align: middle; text-align: left; border-bottom: 3px solid #336699;">'''''Main'''''</td>
*Movement is not detected by the configured movement source.
<td style="vertical-align: middle; text-align: left; min-width: 550px; border-bottom: 3px solid #336699;">
*Device time must be synchronized. This condition depends on the “Record Settings -> Saving / sending mode parameter.
*Configured '''Ignition source''' is off.
**After Position Fix - device time is synchronized with GNSS satellites and GPS fix is obtained.
*Movement is not detected by the configured '''Movement source'''.
**After Time Sync - device time is synchronized over NTP, NITZ, or GNSS satellites.
*Device time must be synchronized, as this condition depends on the ''Record Settings -> Saving / sending mode'' parameter.
**Always - device will enter sleep mode without time synchronization and GPS fix.
**'''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.
*Sleep timeout is reached.
*Sleep timeout is reached.
*There are no SMS messages being received.
*No SMS messages are being received.
*Data sockets are closed (checks if record sending socket link is open)
*No open Data sockets (ignored with enabled permanent link)<br>
*FOTA WEB connection is not in progress.
*No active FOTA WEB connection progress.
 
</td>
'''Deep sleep exit conditions'''
<td style="vertical-align: middle; horizontal-align: center; min-width: 150px; border-bottom: 3px solid #336699;">
 
At least one exit condition must be met:
 
*Ignition is ON.
*Ignition is ON.
*Movement is detected.
*Movement is detected.
{{#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 }}
*Periodic wake-up (if enabled).
*Periodic wake-up (if enabled).
 
</td>
'''Disabled modules in Deep sleep'''
<td style="vertical-align: middle; horizontal-align: center; min-width: 100px; border-bottom: 3px solid #336699;">
 
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 '''Deep sleep''' mode:
 
*Modem
*Modem
*Record sending
*Record sending
Line 358: Line 630:
*IMU (Inertial Measurement Unit)
*IMU (Inertial Measurement Unit)
*FOTA WEB
*FOTA WEB
*Scenarios (Common):
*LEDs (Navigation and Status)
**LEDs (Navigation and Status)
*Odometer
**Odometer
*Data acquisition
**Data acquisition
*SNTP time synchronization
**SNTP time synchronization
*Overspeeding
**Overspeeding
*Trip
**Trip
*Jamming Detection
**Unplug Detection
*Eco Driving
**Jamming Detection
</td>
**Eco Driving
</tr>
<tr>


===Power off sleep===
{{#if: {{FTX Pin Support List|model={{{model}}}|pin=Manual CAN}}
|<td style="vertical-align: middle; text-align: left; border-bottom: 3px solid #336699;">'''''CAN'''''</td>
<td style="vertical-align: middle; text-align: left; border-bottom: 3px solid #336699;">
*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.
</td>
<td style="vertical-align: middle; text-align: left; min-width: 150px; border-bottom: 3px solid #336699;"">
*Main module sends any request via UART.
*Any CAN data is present on the CAN bus.
</td>
<td style="vertical-align: middle; text-align: left; border-bottom: 3px solid #336699;">
*CAN
</td>
}}


'''Disabled modules in Power off sleep'''
</tr>
<tr>


{{#if: {{FTX Pin Support List|model={{{model}}}|pin=BT}}
|<td style="vertical-align: middle; text-align: left;">'''''BLE'''''</td>
<td style="vertical-align: middle; text-align: left;">
*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.
</td>
<td style="vertical-align: middle; text-align: left; min-width: 150px;"">
*The device can wake up from sleep when a DIN input changes (detected through the external module).
*DIN pins remain active in sleep mode and can be used as wake-up sources for the device.
</td>
<td style="vertical-align: middle; text-align: left;">
*BLE scanning
</td>
}}
</tr>
</table>
| ATC700
| ATM700 =
}}
<br><br><br>
===Power Off Sleep===
*All listed entry conditions must be met in order to enter Power Off Sleep.
*At least one exit condition must be met in order to wake up from 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:
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:
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse; border-bottom: 3px solid #336699;">
<tr>
<th style="width:1%; vertical-align: middle; text-align: center;">Module</th>
<th style="width:1%; vertical-align: middle; text-align: center;">Entry Conditions</th>
<th style="width:5%; vertical-align: middle; text-align: center;">Exit conditions</th>
<th style="width:6%; vertical-align: middle; text-align: center;">Disabled functions</th>
</tr>
<tr>
<td style="vertical-align: middle; text-align: left; border-bottom: 3px solid #336699;">'''''Main'''''</td>
<td style="vertical-align: middle; text-align: left; min-width: 550px; border-bottom: 3px solid #336699;">
*Configured '''Ignition source''' is off.
*Movement is not detected by the configured '''Movement source'''.
*Device time must be synchronized, as 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.
*Sleep timeout is reached.
*No SMS messages are being received.
*No open Data sockets (ignored with enabled permanent link)<br>
*No active FOTA WEB connection progress.
{{#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 }}
</td>
<td style="vertical-align: middle; horizontal-align: center; min-width: 150px; border-bottom: 3px solid #336699;">
*Ignition is ON.
*Movement is detected.
{{#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 }}
</td>
<td style="vertical-align: middle; horizontal-align: center; min-width: 100px; border-bottom: 3px solid #336699;">
*Modem
*Modem
*Record sending
*Record sending
Line 380: Line 724:
*FOTA WEB
*FOTA WEB
*Charger service
*Charger service
*Scenarios (Common):
*LEDs (Navigation and Status)
**LEDs (Navigation and Status)
*Odometer
**Odometer
*Data acquisition
**Data acquisition
*SNTP time synchronization
**SNTP time synchronization
*Overspeeding
**Overspeeding
*Towing Detection
**Trip
*Trip
**Unplug Detection
*Unplug Detection
**Jamming Detection
*Jamming Detection
**Eco Driving
*Eco Driving
</td>


'''Power off entry conditions'''
</tr>
<tr>


All entry conditions must be met:
{{#if: {{FTX Pin Support List|model={{{model}}}|pin=Manual CAN}}
|<td style="vertical-align: middle; text-align: left; border-bottom: 3px solid #336699;">'''''CAN'''''</td>
<td style="vertical-align: middle; text-align: left; border-bottom: 3px solid #336699;">
*Main module enters power off sleep mode.
</td>
<td style="vertical-align: middle; text-align: left; min-width: 150px; border-bottom: 3px solid #336699;"">
*Main module wakes up and restarts CAN module.
</td>
<td style="vertical-align: middle; text-align: left; border-bottom: 3px solid #336699;">
*CAN (''does not receive requests, does not read CAN bus messages'')
</td>
}}


*Ignition (configured ignition source) is off.
</tr>
*Movement is not detected by the configured movement source.
<tr>
*Device time must be synchronized. This condition depends on the “Record Settings -> Saving / sending mode parameter.
{{#if: {{FTX Pin Support List|model={{{model}}}|pin=BT}}  
**After Position Fix - device time is synchronized with GNSS satellites and GPS fix is obtained.
|<td style="vertical-align: middle; text-align: left;">'''''BLE'''''</td>
**After Time Sync - device time is synchronized over NTP, NITZ, or GNSS satellites.
<td style="vertical-align: middle; text-align: left;">
**Always - device will enter sleep mode without time synchronization and GPS fix.
*Main module enters power off sleep mode.
*Sleep timeout is reached.
</td>
*There are no SMS messages being received.
<td style="vertical-align: middle; text-align: left; min-width: 150px;"">
*Data sockets are closed (ignored when permanent link is enabled)
*Main module wakes up and restarts BLE module.
*FOTA WEB connection is not in progress.
</td>
<!-- If model supports DIN1/DIN2/DIN3, then show -->
<td style="vertical-align: middle; text-align: left;">
{{#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 }}
*BLE Scanning
</td>
}}


'''Power off sleep exit conditions'''
</tr>
 
</table>
At least one exit condition must be met:
 
*Ignition is ON.
*Movement is detected.
<!-- 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 }}


==Time synchronization settings==
==Time synchronization settings==
Line 475: Line 828:
<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==
Line 576: Line 949:
*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 10:21, 14 April 2026

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