Jump to content

TEST-X: Difference between revisions

From Teltonika Telematics Wiki
No edit summary
DR - TEST
 
(72 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Immobilizer ==
== Dead Reckoning ==
[[File:Immobilizer TCT panel.png|right|500px]]
'''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>


The Immobilizer feature provides an additional layer of vehicle security by requiring driver authorization after the ignition is turned on. It is designed to block the vehicle's starter circuit, preventing the engine from being started until an authorized identification element is presented.
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>


This functionality is essential for preventing vehicle theft and ensuring that only permitted individuals can operate a vehicle. By linking vehicle operation to a physical token, it significantly enhances security for fleet management, rental services, and any application where control over vehicle access is a priority.
Key points to understand before utilizing the Dead Reckoning functionality:
* Installation
* Configuration
* Alignment


The feature operates based on the vehicle's ignition status. When the ignition is turned on, the system enters a "Waiting authorization" state, activating a digital output to keep the starter blocked. Upon successful presentation of an authorized element, the system transitions to an "Authorized" state, deactivates the output, and allows the engine to run. The authorization is automatically revoked after the ignition has been off for a configurable period.
=== <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>Prerequisites and Important Settings </u> ===
=== <u>Basic Operation</u> ===
* The vehicle's ignition status must be monitored by one of the device's digital inputs (DIN).
* A relay must be correctly installed to interrupt the vehicle's starter circuit and connected to one of the device's configurable digital outputs (DOUT).
* An iButton reader is required to detect the authorization element.
* The unique IDs of all authorized iButtons must be pre-configured in the device's authorization list.


=== <u> Basic Operation </u> ===
'''<u>Installation</u>'''<br>
The feature's logic is managed through three distinct states:<br>
1. '''Not Authorized State:'''
* This is the default, idle state when the vehicle's ignition is OFF. The immobilizer is armed and waiting.
2. '''Waiting Authorization State:'''
* When the ignition is turned ON, the system transitions to this state.
* If a Digital Output is configured, it is immediately activated to control the relay and block the starter circuit.
* The device actively waits for an authorization element to be presented.
3. '''Authorized State:'''
* Once an ID is detected and confirmed to be authorized, the system transitions to the Authorized state.
* The configured Digital Output is deactivated, which unblocks the starter circuit and allows the vehicle to be started and driven.
* The driver remains authorized as long as the ignition stays ON.
4. '''De-authorization Process:'''
* When the ignition is turned OFF, a de-authorization timer begins.
* If the ignition remains off for the entire duration of the configured "Authorization persist duration", the system revokes the authorization and returns to the Not Authorized state. If the ignition is turned back on before the timeout expires, the authorization remains active.
5. '''Authorization list management:'''


'''1-Wire'''
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.  
* If no 1-Wire authorization list is used, any ID can be used for authorization.
* If 1-Wire authorization list is used, device will allow authorization only by specifics IDs. Authorization list management can be done in ('''[[#1-Wire_settings|Accessories]]''') section of the TCT, the user can upload, preview and delete a .csv file with up to 10000 device IDs. ID format will be string of 8 bytes in hex format, e.g: AABBCCDDEEFFAABB. It is also possible to manage 1-Wire authorization list via FOTA using task type: Upload 1-Wire authorization list / Receive 1-Wire authorization list.


'''BLE Sensors'''
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>
* If no BLE device authorization list is used, any ID can be used for authorization.
<div style="display: flex; flex-direction: row;">
* If the BLE authorization list is used, the device will only allow authorization from specific BLE devices whose MAC addresses are included in the list.
[[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]]
The authorization list can be accessed in the Immobilizer window, where the user can upload, preview, or delete a .csv file containing up to 200 BLE device entries.
[[File:FTC927 beneath the speedometer panel.jpg|thumb|left|300px|link=Special:Redirect/file/FTC927 beneath the speedometer panel.jpg|Beneath the speedometer panel]]
* Each BLE device ID must be provided as a Bluetooth MAC address in the following hexadecimal format:AA:BB:CC:DD:EE:FF
[[File:FTC927 above the glove box.jpg|thumb|left|300px|link=Special:Redirect/file/FTC927 above the glove box.jpg|Above glove box]]
* Any BLE device can be used for authorization — not only Teltonika EYE sensors.
</div>
Authorization is performed exclusively by checking the Bluetooth MAC address.


'''NOTE:'''<br>
Bad '''mounting''' examples:<br>
It is also possible to manage the Beacon authorization list remotely via FOTA using the following task types:Upload Beacon authorization list and Receive Beacon authorization list.
<div style="display: flex; flex-direction: row;">
[[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|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|link=Special:Redirect/file/Dead Reckoning vibration could cause unwanted device movements.png|Places, where vibration could cause unwanted device movements]]
</div>


'''NOTE:'''<br>
'''<u>Configuration</u>'''<br>
Example files are provided to illustrate the correct structure for uploading authorization lists. The included [[Media:Ibutton list.zip|ibutton_list.csv]] and [[Media:Bluetooth mac list.zip|bluetooth_mac_list.csv]] files demonstrate the required formatting for 1 Wire and Beacon (BLE) entries.


[[File:Dead Recknonig TCT panel_2.png|right|500px]]


=== <u> Parameters list </u>===  
''The Dead Reckoning feature is configurable via the Dead Reckoning section in the GNSS settings group under System view in TCT.''
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
 
<tr>
Parameter list can be found [[{{{model}}}_System#Parameter_list|here]].
<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>
===== Dead Reckoning alignment status =====
<th style="width:5%; vertical-align: middle; text-align: center;">DESCRIPTION</th>
 
<th style="width:6%; vertical-align: middle; text-align: center;">VALUES</th>
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>
</tr>
* '''0''' - Unknown: Dead Reckoning status is unknown.
<tr>
* '''1''' - Init: Dead Reckoning alignment is initializing.
* '''2''' - Coarse: Dead Reckoning is in alignment stage.
* '''3''' - Stable: Dead Reckoning alignment stage has been completed. Estimation stage is in progress.
* '''99''' - Standby: Dead Reckoning is in standby mode ('''NOTE''': this status is availabe with 3.7.X or newer firmware version)
 
===== Turning alignment =====
The turning alignment is a 1-byte AVL ID ('''1434''') that indicates the current percentage of the turning alignment of the device.
 
===== Straight alignment =====
The straight alignment is a 1-byte AVL ID ('''1435''') that indicates the current percentage of the straight alignment of the device.
'''
 
'''<u>Alignment</u>'''<br>
Once device mounting adheres to the guidelines, alignment can be performed. The device '''must finish''' a specific alignment process to '''determine''' its mounting orientation. During this process, there are specific conditions that must be met:
# The device must be '''stationary''' with clear sky visibility for at least 3 minutes.
<!--# A great number of '''left and right''' turns must be performed.-->
# 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, otherwise alignment needs to be restarted from the second step.
[[File:Dead Reckoning TCT Swift .png|right|400px]]
 
=== <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'''


<td style="vertical-align: middle; text-align: center;"> Immobilizer </td>
The device can enter Standby Mode in two scenarios:
<td style="vertical-align: middle; text-align: center;"> 1024800 <br> (248}  </td>
* No movement detected
<td style="vertical-align: middle; text-align: center;"> Disables, or enables and sets priority of the event record generated upon successful or failed authorization attempts.Authorization source </td>
If the device detects absence of movement, Dead Reckoning enters Standby Mode after the timeout defined by '''Standby timeout (ID 124)''' elapses.
<td style="vertical-align: middle; text-align: left;"> '''0 =''' Disable scenario. <br>
* Device enters sleep mode
'''1 =''' Low priority Device makes an additional record with indication of event cause. <br>
When the device transitions into sleep mode, the GNSS receiver is switched to power saving mode.
'''2 =''' High priority - module makes additional record with high priority flag and sends event packet immediately to the server by GPRS.  
</td>
</tr>
<tr>


<td style="vertical-align: middle; text-align: center;"> Authorization mode</td>
Before GNSS powers down, Dead Reckoning enters Standby Mode '''immediately''', the scenario is paused, and the device proceeds into sleep mode.
<td style="vertical-align: middle; text-align: center;"> 11703 </td>
<td style="vertical-align: middle; text-align: center;"> Selects singular or multiple types of authorization elements to be used. </td>
<td style="vertical-align: middle; text-align: left;"> '''0 =''' No authorization selected. <br>
'''1 =''' 1-Wire authorization selected. Driver is authorized via iButton or RFID tag.<br>
</td>


</tr>
'''Exiting Standby Mode'''
<tr>


<td style="vertical-align: middle; text-align: center;"> Authorization persist duration (s)</td>
Standby Mode can be exited in the following cases:
<td style="vertical-align: middle; text-align: center;"> 60068 </td>
* Movement is detected
<td style="vertical-align: middle; text-align: center;"> Sets the time in seconds after the ignition is turned off before the driver's authorization is automatically revoked. </td>
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.
<td style="vertical-align: middle; text-align: left;"> Minimum value '''= 1''' <br>
Maximum value '''= 65535''' </td>


</tr>


<tr>
=== <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>


<td style="vertical-align: middle; text-align: center;"> Bypass authorization </td>
* '''Recovery after DR Standby (Sleep Mode)'''
<td style="vertical-align: middle; text-align: center;"> 11029</td>
** 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>
<td style="vertical-align: middle; text-align: center;"> Allows to bypass authorization when ignition is turned on and a set duration expires. </td>
<td style="vertical-align: middle; text-align: left;"> '''0 =''' Disabled <br>
'''0-65535 =''' Enabled <br>
Default value = '''0'''  </td>


</tr>
* '''Real world driving variability'''
<tr>
** Real world driving conditions may vary and can impact performance results.


<td style="vertical-align: middle; text-align: center;"> Bypass authorization timeout (s) </td>
=== <u>Limitations, Edge Cases & Additional Notes</u> ===
<td style="vertical-align: middle; text-align: center;"> 11029</td>
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.
<td style="vertical-align: middle; text-align: center;"> Sets duration which starts when ignition is turned on. When duration expires immobilizer is turned off, even if the user was not authenticated. </td>
* '''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.
<td style="vertical-align: middle; text-align: left;"> Minimum value '''= 1''' <br>
* '''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.
Maximum value '''= 65535''' </td>
[[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.
For example: If a courier spends up to 30 minutes unloading in the underground car park, DR will remain accurate. Otherwise, positioning information will become less accurate.
* '''Temperature effects''' - The accuracy of the position can change if the temperature is very different from when the device was last calibrated.
* '''Alignment reset''' - If the device loses power or goes into sleep mode, it will need to be calibrated again.


</tr>
'''Tip:''' If alignment auto-save is enabled, realignment will be faster.
<tr>


<td style="vertical-align: middle; text-align: center;"> Output control </td>
* '''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.
<td style="vertical-align: middle; text-align: center;"> 11702</td>
[[File:GNSS Multipath.png|350px]]
<td style="vertical-align: middle; text-align: center;"> Selects which Digital Output is used to control the immobilizer relay. </td>
<td style="vertical-align: middle; text-align: left;"> '''0 =''' None DOUTs are disabled in this scenario. <br>
'''1 =''' DOUT1 DOUT1 is enabled in this scenario. <br>
'''2 =''' DOUT2 DOUT2 is enabled in this scenario. <br>
'''3 =''' DOUT3 DOUT3 is enabled in this scenario. </td>


</tr>  
=== <u>AVL ID list</u> ===
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<tr>
<th style="width:8%; vertical-align: middle; text-align: left;">Property ID in AVL packet</th>
<th style="width:15%; vertical-align: middle; text-align: center;">Property Name</th>
<th style="width:5%; vertical-align: middle; text-align: center;">Bytes</th>
<th style="width:10%; vertical-align: middle; text-align: center;">Min Value</th>
<th style="width:10%; vertical-align: middle; text-align: center;">Max Value</th>
<th style="width:5%; vertical-align: middle; text-align: center;">Multiplier</th>
<th style="width:5%; vertical-align: middle; text-align: center;">Units</th>
<th style="width:32%; vertical-align: middle; text-align: left;">Description</th>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">1433</td>
<td style="vertical-align: middle; text-align: center;">Dead Reckoning alignment status</td>
<td style="vertical-align: middle; text-align: center;">1</td>
<td style="vertical-align: middle; text-align: center;">0</td>
<td style="vertical-align: middle; text-align: center;">99</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;">[[{{{model}}}_System#Dead_Reckoning_alignment_status|Dead Reckoning alignment status]]</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">1434</td>
<td style="vertical-align: middle; text-align: center;">Turning alignment</td>
<td style="vertical-align: middle; text-align: center;">1</td>
<td style="vertical-align: middle; text-align: center;">0</td>
<td style="vertical-align: middle; text-align: center;">100</td>
<td style="vertical-align: middle; text-align: center;">1</td>
<td style="vertical-align: middle; text-align: center;">%</td>
<td style="vertical-align: middle; text-align: center;">[[{{{model}}}_System#Turning_alignment|Turning alignment]]</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">1435</td>
<td style="vertical-align: middle; text-align: center;">Straight alignment</td>
<td style="vertical-align: middle; text-align: center;">1</td>
<td style="vertical-align: middle; text-align: center;">0</td>
<td style="vertical-align: middle; text-align: center;">100</td>
<td style="vertical-align: middle; text-align: center;">1</td>
<td style="vertical-align: middle; text-align: center;">%</td>
<td style="vertical-align: middle; text-align: center;">[[{{{model}}}_System#Straight alignment|Straight alignment]]</td>
</tr>
</table>
</table>


=== <u> Limitations, Edge Cases & Additional Notes </u> ===
=== <u>Parameter list</u> ===
* '''Installation Security:''' The overall effectiveness of the immobilizer is highly dependent on the secure and discreet installation of the control relay. If the wiring is easily accessible, it can be bypassed.
<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>

Latest revision as of 13:20, 30 April 2026

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.

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

Key points to understand before utilizing the Dead Reckoning functionality:

  • Installation
  • Configuration
  • Alignment

Prerequisites and Important Settings

  • 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).

Basic Operation

Installation

The device must be mounted firmly in the vehicle, with good visibility of the sky. Failure to ensure proper mounting will result in inability to calibrate the device or inaccurate position estimation. Following examples ensure that the GNSS antenna is facing towards the sky and there are no physical obstacles, like metal plates, wires, are blocking the GNSS signal.

Good mounting examples ( 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):

Dashboard in the middle of the car mount
Beneath the speedometer panel
Above glove box

Bad mounting examples:

Unwanted movements will be detected by the IMU
Metal parts above the mount
Places, where vibration could cause unwanted device movements

Configuration

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 [[{{{model}}}_System#Parameter_list|here]].

Dead Reckoning alignment status

The Dead Reckoning alignment status is a 1-byte AVL ID (1433) that indicates the current status of the Dead Reckoning alignment. The possible values are:

  • 0 - Unknown: Dead Reckoning status is unknown.
  • 1 - Init: Dead Reckoning alignment is initializing.
  • 2 - Coarse: Dead Reckoning is in alignment stage.
  • 3 - Stable: Dead Reckoning alignment stage has been completed. Estimation stage is in progress.
  • 99 - Standby: Dead Reckoning is in standby mode (NOTE: this status is availabe with 3.7.X or newer firmware version)
Turning alignment

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

Straight alignment

The straight alignment is a 1-byte AVL ID (1435) that indicates the current percentage of the straight alignment of the device.

Alignment
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:

  1. The device must be stationary with clear sky visibility for at least 3 minutes.
  2. Vehicle speed during alignment should be between 10 km/h and 100 km/h, with varying speeds preferred over extended constant-speed driving.
  3. Avoid driving in underground tunnels or areas with poor GNSS signal, otherwise alignment needs to be restarted from the second step.

Standby mode

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.


Prerequisites and important Settings

  • 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.

Basic Operation

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.


Key Performance Indicators (based on performed tests)

  • 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.
    • Dead Reckoning continues operating beyond 1 km; however, positional error may increase after this threshold.
  • 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.
  • Real world driving variability
    • Real world driving conditions may vary and can impact performance results.

Limitations, Edge Cases & Additional Notes

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.

  • Position accuracy may decrease - If the device cannot receive a GNSS signal for a long time, the estimated position may become less accurate. This is because the sensors inside the device can only estimate the position for a limited time without help from GNSS.

For example: If a courier spends up to 30 minutes unloading in the underground car park, DR will remain accurate. Otherwise, positioning information will become less accurate.

  • Temperature effects - The accuracy of the position can change if the temperature is very different from when the device was last calibrated.
  • Alignment reset - If the device loses power or goes into sleep mode, it will need to be calibrated again.

Tip: If alignment auto-save is enabled, realignment will be faster.

  • Position jumps after GNSS outages - 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.

AVL ID list

Property ID in AVL packet Property Name Bytes Min Value Max Value Multiplier Units Description
1433 Dead Reckoning alignment status 1 0 99 1 [[{{{model}}}_System#Dead_Reckoning_alignment_status|Dead Reckoning alignment status]]
1434 Turning alignment 1 0 100 1 % [[{{{model}}}_System#Turning_alignment|Turning alignment]]
1435 Straight alignment 1 0 100 1 % [[{{{model}}}_System#Straight alignment|Straight alignment]]

Parameter list

Property ID in AVL packet Property Name Bytes Min Value Max Value Multiplier Units Description
123 Alignment auto-save - 0 1 - - This option saves calibration data to device memory, enabling a faster recalibration after device restart.
0 = Disable
1 = Enable
124 Standby timeout - 1 65535 1 (s) seconds The standby timeout is the time after which device will attempt to correct the position based on correction strategy.
Default value = 1800
125 Standby mode - 0 1 - - The standby mode is the mode in which the device will attempt to correct the position based on correction strategy.
0 = Realignment
1 = Preserve alignment