Jump to content
  • EN

Template:FTX System: Difference between revisions

From Teltonika Telematics Wiki
← Older edit
VisualWikitext
No edit summary
No edit summary
 
(33 intermediate revisions by 4 users not shown)
Line 267: 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 />


{{#switch: {{{model}}}
{{#switch: {{{model}}}
 
| FTM927
| FTC927
| FTC927
| FTM887
| FTM887
| FTC887
| FTC887
| FTC968 =
| FTC308
| FTM308 =
== Dead Reckoning ==
== Dead Reckoning ==
 
'''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. For a detailed explanation and demonstration, check out '''[https://www.youtube.com/watch?v=TOVAL0zRuK0 Dead Reckoning Explained Youtube video]'''.<br>
=== <u>Introduction</u> ===
'''Dead Reckoning''' is a navigation technique used to estimate current position of vehicle   , direction of movement, based on its previous position and known speed. It uses additional sensor data to correct the position received from GNSS receiver.<br>


Usage of Dead Reckoning is essential in scenarios where GNSS signal is weak or unavailable, such as underground parking lots, tunnels or dense forests.<br>
Usage of Dead Reckoning is essential in scenarios where GNSS signal is weak or unavailable, such as underground parking lots, tunnels or dense forests.<br>


'''Note:''' Dead Reckoning is enabled for all FT platform devices with gyroscope. At the moment, it’s not possible to disable it.<br>
=== <u>Prerequisites</u> ===
Key points to understand before utilizing the Dead Reckoning functionality:
Key points to understand before utilizing the Dead Reckoning functionality:
* Installation
* Installation
* Configuration
* Configuration
* Alignment
* Alignment
=== <u>Prerequisites and Important Settings</u> ===
* Device mounting quality  – Correct device mounting is critical for Dead Reckoning operation. Improper mounting may result in incorrect sensor data and unreliable Dead Reckoning performance.
* Dead Reckoning alignment maintenance – If Dead Reckoning alignment parameters are no longer valid, send the DR_RESET command and perform calibration.
* Electric and hybrid vehicles – For electric and hybrid vehicles, DIN1 should be used for movement detection to ensure correct Dead Reckoning operation.
* Dead Reckoning is not supported for two‑wheeled vehicles (e.g., motorcycles, scooters).
=== <u>Basic Operation</u> ===


'''<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, 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|link=Special:Redirect/file/FTC927 under the front dashboard in the middle of the car.jpg|Dashboard in the middle of the car mount]]
[[File:FTC927 beneath the speedometer panel.jpg|thumb|left|300px|Beneath the speedometer panel]]
[[File:Dead reckoning Above glove box.jpg|thumb|left|300px|link=Special:Redirect/file/Dead reckoning Above glove box.jpg|Above glove box]]
[[File:FTC927 above the glove box.jpg|thumb|left|300px|Above glove box]]
[[File:FTC927 above the glove box.jpg|thumb|left|300px|link=Special:Redirect/file/FTC927 above the glove box.jpg|Above glove box]]
</div>
<div style="display: flex; flex-direction: row;">
[[File:Dead reckoning In the trunk-1.jpg|thumb|left|300px|link=Special:Redirect/file/Dead reckoning In the trunk-1.jpg|In the trunk]]
[[File:Dead reckoning In the trunk-2.jpg|thumb|left|300px|link=Special:Redirect/file/Dead reckoning In the trunk-2.jpg|In the trunk]]
[[File:FTC927 beneath the speedometer panel.jpg|thumb|left|300px|link=Special:Redirect/file/FTC927 beneath the speedometer panel.jpg|Beneath the speedometer panel]]
</div>
<div style="display: flex; flex-direction: row;">
[[File:Dead reckoning Under the hood.jpg|thumb|left|300px|link=Special:Redirect/file/Dead reckoning Under the hood.jpg|Under the hood]]
</div>
</div>


Bad '''mounting'''  examples:<br>
Bad '''mounting'''  examples:<br>
<div style="display: flex; flex-direction: row;">
<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 Unwanted movements will be detected by the IMU.png|thumb|left|280px|link=Special:Redirect/file/Dead Reckoning Unwanted movements will be detected by the IMU.png|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 Metal parts above the mount.png|thumb|left|300px|link=Special:Redirect/file/Dead Reckoning Metal parts above the mount.png|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]]
[[File:Dead Reckoning vibration could cause unwanted device movements.png|thumb|left|300px|link=Special:Redirect/file/Dead Reckoning vibration could cause unwanted device movements.png|Places, where vibration could cause unwanted device movements]]
</div>
</div>


Line 316: Line 332:
''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 [[Template:FTX_System#Parameter_list|here]].
Parameter list can be found [[{{{model}}}_System#Parameter_list|here]].


===== Dead Reckoning alignment status =====
===== Dead Reckoning alignment status =====
Line 325: Line 341:
* '''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>


=== <u>Limitations</u> ===
'''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>Key Performance Indicators (based on performed tests)</u> ===
* '''GNSS denied operation (1 km)'''
** When driving 1 km without a GNSS signal (including 15–20 turns), the positional error is ≤ 25 m, achieved in at least 8 out of 10 field tests.<br>
** Dead Reckoning continues operating beyond 1 km; however, positional error may increase after this threshold.<br>
 
* '''Recovery after DR Standby (Sleep Mode)'''
** After exiting DR Standby (Sleep Mode), the system correctly reconstructs the driven route for up to 5 minutes or 1000 m, with a positional error of ≤ 50 m, achieved in at least 8 out of 10 field tests.<br>
 
* '''Real world driving variability'''
** Real world driving conditions may vary and can impact performance results.
 
=== <u>Limitations, Edge Cases & Additional Notes</u> ===
There are some important things to keep in mind when using the Dead Reckoning functionality. The algorithm tries to correct for these issues, but sometimes they can still affect how well Dead Reckoning works.
There are some important things to keep in mind when using the Dead Reckoning functionality. The algorithm tries to correct for these issues, but sometimes they can still affect how well Dead Reckoning works.
 
* '''Loss of alignment during drifting''' – Dead Reckoning alignment will be lost during drifting, when the actual movement vector does not correspond to the vehicle heading. Re‑alignment is required.
* '''Overshooting''' - May occur when the vehicle travels straight for more than 50 m at speeds below 20 km/h. In such cases, positional overshoot may be observed. An example is shown in the attached image.
[[File:Dead Reckoning - Overshooting.png|300px|link=Special:Redirect/file/Dead Reckoning - Overshooting.png]]
* '''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 374: Line 432:
<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 387: Line 445:
<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 397: Line 455:
<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>
</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>
<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 414: Line 516:
<br />
<br />


==Power Saving settings==
==Power saving settings==
{{#switch: {{{model}}}  
{{#switch: {{{model}}}  
| #default =
| #default =
Line 428: Line 530:
| ATM700 =  
| ATM700 =  
}}
}}
===Online sleep===
<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 functions 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
*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'''
</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;">
*Configured '''Ignition source''' is on.<br>
*Movement is detected by the configured '''Movement source.<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.


'''CAN and BLE sleep entry 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>
}}


All entry conditions must be met for CAN and BLE respectively:
</tr>
<tr>


*CAN
{{#if: {{FTX Pin Support List|model={{{model}}}|pin=BT}}
**No communication with Main module for 1 second.
|<td style="vertical-align: middle; text-align: left;">'''''BLE'''''</td>
**No configured CAN data is read for 5 seconds.
<td style="vertical-align: middle; text-align: left;">
**At least 1 second has passed since the last module wake up.
*Main module enters Online/Deep sleep modes.
 
*No communication with Main module for 1 second.
*BLE
*At least 1 second has passed since the last module wake up.</td>
**Main module enters Online/Deep sleep modes
<td style="vertical-align: middle; text-align: left; min-width: 150px;"">
**No communication with Main module for 1 second.
*The device can wake up from sleep when a DIN input changes (detected through the external MCU).
**At least 1 second has passed since the last module wake up.
*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>
'''Online sleep exit conditions'''
}}
 
At least one exit condition must be met:
 
*Ignition is ON.
*Movement is detected.
*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.


</tr>
</table>
<br><br><br>
===Deep Sleep===
{{#switch: {{{model}}}  
{{#switch: {{{model}}}  
| #default =  
| #default =  
===Deep sleep===
*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>
'''CAN and BLE sleep entry conditions'''
<td style="vertical-align: middle; horizontal-align: center; min-width: 150px; border-bottom: 3px solid #336699;">
 
*Configured '''Ignition source''' is on.<br>
All entry conditions must be met for CAN and BLE respectively:
*Movement is detected by the configured '''Movement source.<br>
*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'''
 
At least one exit condition must be met:
 
*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 }}
*Periodic wake-up (if enabled).
*Periodic wake-up (if enabled).
</td>
<td style="vertical-align: middle; horizontal-align: center; min-width: 100px; border-bottom: 3px solid #336699;">
*Modem
*Record sending
*GNSS
*IMU (Inertial Measurement Unit)
*FOTA WEB
*LEDs (Navigation and Status)
*Odometer
*Data acquisition
*SNTP time synchronization
*Overspeeding
*Trip
*Jamming Detection
*Eco Driving
</td>
</tr>
<tr>


'''CAN and BLE 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.
*Any CAN data is present on the CAN bus.
</td>
<td style="vertical-align: middle; text-align: left; border-bottom: 3px solid #336699;">
*CAN
*CAN
**Main module sends any request via UART.
</td>
**Any CAN data is present on the CAN bus.
}}


*BLE
</tr>
**The device can wake up from sleep when a DIN input changes (detected through the external module).
<tr>
**DIN pins remain active in sleep mode and can be used as wake-up sources for the device.


'''Disabled functions in Deep sleep'''
{{#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>
}}


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:
</tr>
 
</table>
*Modem
*Record sending
*GNSS
*IMU (Inertial Measurement Unit)
*FOTA WEB
*Scenarios (Common):
**LEDs (Navigation and Status)
**Odometer
**Data acquisition
**SNTP time synchronization
**Overspeeding
**Trip
**Unplug Detection
**Jamming Detection
**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  
| ATC700  
| ATM700 =  
| ATM700 =  
}}
}}
===Power off sleep===
<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:
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse; border-bottom: 3px solid #336699;">


'''Disabled functions in Power off sleep'''
<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>


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:
</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.
*No signal is detected on Digital Input 1
</td>
<td style="vertical-align: middle; horizontal-align: center; min-width: 150px; border-bottom: 3px solid #336699;">
*Movement detected by the accelerometer.
*Signal detected on Digital Input 1
'''Note:''' In Power Off Sleep mode, the main application is not running. Ignition and Movement sources are not monitored and cannot trigger a wake-up event.
</td>
<td style="vertical-align: middle; horizontal-align: center; min-width: 100px; border-bottom: 3px solid #336699;">
*Modem
*Modem
*Record sending
*Record sending
Line 584: Line 750:
*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
{{#if: {{FTX Pin Support List|model={{{model}}}|pin=Manual CAN}} |
</td>
 
</tr>
<tr>
 
{{#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'')
*CAN (''does not receive requests, does not read CAN bus messages'')
</td>
}}
}}
{{#if: {{FTX Pin Support List|model={{{model}}}|pin=BT}} | *BLE
 
**PIN's are unavailable while BLE module is off.
</tr>
**Anything connected or enabled by BLE module
<tr>
(1 wire, DIN's, DOUT's, BLE as a peripheral)
{{#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 power off sleep mode.
</td>
<td style="vertical-align: middle; text-align: left; min-width: 150px;"">
*Main module wakes up and restarts BLE module.
</td>
<td style="vertical-align: middle; text-align: left;">
*BLE Scanning
</td>
}}
}}
'''Power off entry conditions'''


All entry conditions must be met:
</tr>
 
</table>
*Ignition (configured ignition source) is off.
*Movement is not detected by the configured movement source.
*Device time must be synchronized. This condition depends on the “Record Settings -> Saving / sending mode parameter.
**After Position Fix - device time is synchronized with GNSS satellites and GPS fix is obtained.
**After Time Sync - device time is synchronized over NTP, NITZ, or GNSS satellites.
**Always - device will enter sleep mode without time synchronization and GPS fix.
*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.
<!-- If model supports DIN1/DIN2/DIN3, then show -->
{{#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'''
 
At least one exit condition must be met:
 
*Ignition is ON.
*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: {{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==

Latest revision as of 15:43, 9 June 2026

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