Template:FTX Tracking settings: Difference between revisions
No edit summary |
FTXXXX WIKI sync with 3.7.x Stage 2 - Resync |
||
| (9 intermediate revisions by 3 users not shown) | |||
| Line 14: | Line 14: | ||
'''Possible options:''' | '''Possible options:''' | ||
'''After Position Fix''' - records will be saved and sent only after position fix. | '''After Position Fix''' - records will be saved and sent only after position fix. Coordinate acquisition time is configured via the "GNSS position fix search timeout" parameter. | ||
'''After Time Sync''' - records will be saved and sent only after time synchronization. | '''After Time Sync''' - records will be saved and sent only after time synchronization. “GNSS position fix search timeout” is not used here; therefore, records may lack GNSS location data. | ||
'''Always''' - records will always be saved and sent even if there is no time synchronization. | '''Always''' - records will always be saved and sent even if there is no time synchronization. “GNSS position fix search timeout” is not used here; therefore, records may lack GNSS location data. | ||
'''Note''': If the record is without valid coordinates – (there were no GPS fix at the moment of data acquisition) – Longitude, Latitude and Altitude values are sent as per the last valid fix, and Angle, Satellites and Speed will be 0. However, if there is a reboot then it will send zero coordinates. | '''Note''': If the record is without valid coordinates – (there were no GPS fix at the moment of data acquisition) – Longitude, Latitude and Altitude values are sent as per the last valid fix, and Angle, Satellites and Speed will be 0. However, if there is a reboot then it will send zero coordinates. | ||
| Line 122: | Line 122: | ||
{{#switch: {{{model}}} | {{#switch: {{{model}}} | ||
| #default | | #default = | ||
==Records profile settings== | ==Records profile settings== | ||
[[File:FTX_Records_profile_settings.png|right|500 px]] | [[File:FTX_Records_profile_settings.png|right|500 px]] | ||
| Line 205: | Line 205: | ||
| ATC700 = | | ATC700 = | ||
}} | }} | ||
== Records schedule == | |||
{{#switch: {{{model}}} | |||
| #default = | |||
==On-Demand Tracking== | |||
[[File:FTX_Tracking_On_demand_tracking.png|right|500px]] | |||
On-demand tracking is a feature that allows forcing the device to generate high priority records at a configured period and to initiate data sending to a server. | |||
On-demand tracking is useful for users who need to conveniently trigger records with certain periods in various situations, such as stolen vehicle recovery, precise company car usage tracking, and similar. | |||
When an SMS/GPRS command or the configured I/O trigger activates on-demand tracking, the device starts periodically generating and sending high-priority records until the pre-defined duration elapses or a stop command is received. | |||
===Prerequisites and Important Settings=== | |||
* Related [[SMS/GPRS command - on_demand_tracking]]. | |||
* The available I/O triggers depend on the hardware of your device. | |||
* The priority of the I/O trigger must be set at least to Low (see [[{{{model}}} Input/output (I/O)]]). | |||
* On-demand tracking interacts with periodic record acquisition (see [[#Records profile settings]]): | |||
** If the on-demand tracking “Period” is '''longer''' than the periodic record “Send period” - on-demand records will be generated '''in parallel''' with the regular periodic records. | |||
** If the on-demand tracking “Period” is '''shorter or equal''' than the periodic record “Send period” - periodic record acquisition will be '''suspended''' until on-demand tracking duration elapses or on-demand tracking stop command is received. | |||
* The only way to stop on-demand tracking before its duration elapses is by sending a stop SMS/GPRS command. | |||
===Basic Operation=== | |||
# The devices receives a trigger for on-demand tracking via either: | |||
## [[SMS/GPRS command - on_demand_tracking]]. | |||
## I/O trigger, e.g. signal on DIN1 from the vehicle. | |||
#The device generates high priority records every “Period” seconds, for the “Duration” of seconds, or until a stop command is received. | |||
#On-demand tracking stops. | |||
The number of generated records can be calculated using this formula: | |||
* Number of records = (Duration/Period)+1, e.g.: | |||
** Duration = 600, Period = 10 → (600/10)+1 = 60+1 = 61 records | |||
* The result is rounded down to the nearest integer, e.g.: | |||
** Duration = 19, Period = 10 → (19/10)+1 = 1.9+1 = 2.9 = 2 records | |||
* If the duration is shorter than the period, only 1 record will be generated and on-demand tracking will stop: | |||
** Duration = 59, Period = 60 → 1 record | |||
===Parameters=== | |||
''Attention! The following parameters or their values depend on hardware/firmware - you may not see them in software:'' | |||
* ''Triggers'' | |||
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;"> | |||
<tr> | |||
<th style="width:15%; vertical-align: middle; text-align: center;">PARAMETER NAME</th> | |||
<th style="width:15%; vertical-align: middle; text-align: center;">PARAMETER ID (RELATED AVL ID)</th> | |||
<th style="width:50%; vertical-align: middle; text-align: center;">DESCRIPTION</th> | |||
<th style="width:20%; vertical-align: middle; text-align: center;">VALUE(S)</th> | |||
</tr> | |||
<tr> | |||
<td style="vertical-align: middle; text-align: left;">Period (s)</td> | |||
<td style="vertical-align: middle; text-align: left;">10990</td> | |||
<td style="vertical-align: middle; text-align: left;">Time interval at which on-demand records will be generated.</td> | |||
<td style="vertical-align: middle; text-align: left;">Min=1<br>Max=60<br>Default="10"</td> | |||
</tr> | |||
<tr> | |||
<td style="vertical-align: middle; text-align: left;">Duration (s)</td> | |||
<td style="vertical-align: middle; text-align: left;">10991</td> | |||
<td style="vertical-align: middle; text-align: left;">Time interval at which on-demand records will be generated.</td> | |||
<td style="vertical-align: middle; text-align: left;">Min=10<br>Max=3600<br>Default="600"</td> | |||
</tr> | |||
<tr> | |||
<td style="vertical-align: middle; text-align: left;">Triggers</td> | |||
<td style="vertical-align: middle; text-align: left;">10992</td> | |||
<td style="vertical-align: middle; text-align: left;">Select zero or more events which can activate on-demand tracking.<br>The priority of corresponding I/O must be set to at least Low.<br>To set multiple triggers using the SMS/GPRS command, send the sum of required values, e.g. DIN1 (1) + DIN3 (4) = 5.</td> | |||
<td style="vertical-align: middle; text-align: left;">1=DIN1<br>2=DIN2<br>4=DIN3<br>8=DIN4<br>65536=AIN1<br>131072=AIN2<br>262144=AIN3<br>524288=AIN4</td> | |||
</tr> | |||
</table> | |||
| FTC305 | |||
| FTM305 | |||
| ATM700 | |||
| ATC700 = | |||
}} | |||
==Records schedule== | |||
[[File:Records Schedule TCT panel.png|right|500px]] | [[File:Records Schedule TCT panel.png|right|500px]] | ||
| Line 214: | Line 283: | ||
The user can define up to six unique scheduled times for each weekday. At each configured time, the device exits its sleep state, activates its GNSS module to determine its current location, establishes a connection to send the data, and then returns to the same Mode until the next scheduled event. This ensures periodic updates while maximizing battery life. | The user can define up to six unique scheduled times for each weekday. At each configured time, the device exits its sleep state, activates its GNSS module to determine its current location, establishes a connection to send the data, and then returns to the same Mode until the next scheduled event. This ensures periodic updates while maximizing battery life. | ||
When GNSS data is saved and transmitted according to the configured Scheduler, GNSS FIX acquisition for the next record is started earlier than the scheduled time. | |||
The advance start time is dynamically calculated based on the GNSS FIX acquisition duration of the previous record. | |||
Key points: | |||
* The advance time cannot exceed the configured GNSS FIX search timeout. | |||
* The maximum allowed advance offset is up to 10 minutes. | |||
=== <u>Prerequisites and Important Settings </u> === | === <u>Prerequisites and Important Settings </u> === | ||
| Line 222: | Line 298: | ||
=== <u> Basic Operation </u> === | === <u> Basic Operation </u> === | ||
* Entering Sleep Mode: | * Entering Sleep Mode: | ||
** After its initial configuration and data sending, the device enters the selected low-power sleep mode. In this state, most modules, including GNSS and the modem, are powered down to conserve energy. | |||
* Scheduled Wake-up: | * Scheduled Wake-up: | ||
** The device's internal clock continuously runs. When the current time matches one of the configured schedules, the device initiates the wake-up sequence. | ** The device's internal clock continuously runs. When the current time matches one of the configured schedules, the device initiates the wake-up sequence. | ||
| Line 300: | Line 376: | ||
=== <u> Limitations, Edge Cases & Additional Notes </u> === | === <u> Limitations, Edge Cases & Additional Notes </u> === | ||
* A maximum of six unique schedules can be configured per weekday. | * A maximum of six unique schedules can be configured per weekday. | ||
* The reliability of this feature is dependent on the device's ability to acquire a GNSS signal at the scheduled time. If the device is in a location with poor signal (e.g., indoors, underground garage), it may fail to get a fix and | * The reliability of this feature is dependent on the device's ability to acquire a GNSS signal at the scheduled time. If the device is in a location with poor signal (e.g., indoors, underground garage), it may fail to get a fix and may not send a record. | ||
* If the device's internal battery is completely drained, it will lose time synchronization and will not be able to execute scheduled wake-ups until it is powered on and can sync its clock again. | * If the device's internal battery is completely drained, it will lose time synchronization and will not be able to execute scheduled wake-ups until it is powered on and can sync its clock again. | ||
[[Category:{{{model}}} Configuration]] | [[Category:{{{model}}} Configuration]] | ||