Jump to content
  • EN

Template:FTX Tracking settings: Difference between revisions

From Teltonika Telematics Wiki
← Older edit
VisualWikitext
No edit summary
FTXXXX WIKI sync with 3.7.x Stage 2 - Resync
 
(26 intermediate revisions by 4 users not shown)
Line 1: Line 1:
==Records settings==
==Records settings==
{{#switch: {{{model}}}
| #default =
[[File:FTX records settings.png|right|500 px]]


[[File:Record Settings latest.png|right|500 px]]
| ATM700
 
| ATC700 =
[[File:ATX Records setting.png|right|500 px]]
}}
'''Saving/sending mode'''
'''Saving/sending mode'''


Line 9: 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.  
 
{{#switch: {{{model}}}
| ATM700
| ATC700 =
'''GNSS position fix search timeout (s)'''
 
GNSS position fix search timeout in seconds, after timeout periodic and scheduled records are generated without position fix and sleep is allowed.
 
* This parameter is measured in seconds. Default value is 120 seconds.
* Minimal value = 0 seconds, maximum value = 86400 seconds.
}}


'''Sort by'''
'''Sort by'''
Line 32: Line 48:


In ''Data Protocol'' only protocol version ('''[[Codec#Codec 8 Extended|Codec 8 Extended]]''') is available for data sending to the server.<br></br>
In ''Data Protocol'' only protocol version ('''[[Codec#Codec 8 Extended|Codec 8 Extended]]''') is available for data sending to the server.<br></br>
{{#switch: {{{model}}}
| ATM700
| ATC700 =
== Asset tracking modes ==
[[File:Asset tracking modes.png|right|500 px]]
'''Note:'''This scenario is only available for asset tracking (''ATX'') devices.
Asset tracking modes functionality controls records profiles with conditions on when records are being saved and sent.
=== Basic movement mode ===
In Basic tracking mode, the accelerometer is disabled. The device relies only on periodic wake-ups. Records are generated and sent at a fixed interval. Depending on configured periodic record priority, records can be:
*Sent immediately when generated in High priority case.
*Stored until they are sent in batches in Low priority case.
Record generation and sending uses periodic record configuration parameters.<br>
Records are generated at a fixed interval, configurable via parameters “'''By time'''” - in Home network (ID 10000) and in Roaming network (ID 10100).
Records are sent at a separate fixed interval, configurable via parameters “'''Send period'''” - in Home network (ID 10005) and in Roaming network (ID 10105).
If the device is configured to send records in Low priority, minimum number of records have to be generated before sending occurs. This value can be configured via parameters “'''Min Saved Records'''” - in Home network (ID 10004) and in Roaming network (ID 10104).
===  Parameters list ===
<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:3%; vertical-align: middle; text-align: center;">VALUES</th>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;"> Asset tracking modes</td>
<td style="vertical-align: middle; text-align: center;"> 12150 </td>
<td style="vertical-align: middle; text-align: center;">In Basic tracking mode, the accelerometer is disabled. The device relies only on periodic wakeups whereas records are generated and sent at a fixed interval(s). 0 value in "Send period" field turns off periodic Low priority record sending.</td>
<td style="vertical-align: middle; text-align: left;"> '''0''' = Basic mode </td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;"> By time (s)</td>
<td style="vertical-align: middle; text-align: center;">10000 (''Home'')<br>10100 (''Roaming'')</td>
<td style="vertical-align: middle; text-align: center;">This parameter indicates a time interval in seconds in order to acquire a new record. If the value is 0 it means no records by min period will be saved.</td>
<td style="vertical-align: middle; text-align: left;"> Minimum value '''= 0''' <br>
Maximum value '''= 2592000'''</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">Send period (s)</td>
<td style="vertical-align: middle; text-align: center;">10005 (''Home'')<br>10105 (''Roaming'')</td>
<td style="vertical-align: middle; text-align: center;">This parameter indicates the frequency (time interval in seconds) of sending data to the server.</td>
<td style="vertical-align: middle; text-align: left;"> Minimum value '''= 0''' <br>
Maximum value '''= 2592000'''</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">Min saved records</td>
<td style="vertical-align: middle; text-align: center;"> 10004 (''Home'')<br>10104 (''Roaming'')</td>
<td style="vertical-align: middle; text-align: center;">This parameter defines a minimum number of records in one data packet that can be sent to the server. It has a higher priority than data send period (s).</td>
<td style="vertical-align: middle; text-align: left;"> Minimum value '''= 1''' <br>
Maximum value '''= 225'''</td>
</tr>
</table>
}}


==Network operators settings==
==Network operators settings==
Line 47: Line 121:
<br><br><br><br><br><br><br><br>
<br><br><br><br><br><br><br><br>


{{#switch: {{{model}}}
| #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 125: Line 201:
*'''Configuration Overrides'''
*'''Configuration Overrides'''
**Certain high-priority events (e.g., crashes, alarms) may override the data acquisition intervals and send records immediately, regardless of the configured mode.
**Certain high-priority events (e.g., crashes, alarms) may override the data acquisition intervals and send records immediately, regardless of the configured mode.
| ATM700
| ATC700 =
}}
{{#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]]
This feature, also known as the Scheduler, allows the device to wake up from a low-power sleep mode at pre-configured times to acquire a GNSS position and send a data record to a server. However, this feature can operate in any power Mode.
This functionality is essential for asset tracking scenarios where power conservation is critical, such as monitoring trailers, containers, or any equipment without a constant power source. By waking up only at specified intervals to report its location, the device can operate on its internal battery for extended periods.
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> ===
* The device must be configured to operate in a sleep mode that supports scheduled wake-ups, such as "Deep Sleep" or "Online Deep Sleep" mode. This is typically configured in System > Power saving settings > Mode.
* Accurate time synchronization is required for the scheduler to function correctly. The device must be able to acquire the current time, either from a GNSS satellite fix or through an NTP server, before the schedules can be reliably executed.
* The device must have a server configured for data sending in Mobile Network > Primary server settings.
=== <u> Basic Operation </u> ===
* 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:
** 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 main controller powers on the GNSS module to acquire a satellite fix and determine the current coordinates.
* Data Record and Transmission:
** Once a position fix is obtained, the device powers on the modem.
** It creates a new data record containing the latest location information and other configured I/O parameters.
** The device establishes a connection to the server and sends the record.
* Returning to Sleep:
** After successfully sending the record, the device powers down the GNSS and modem modules.
** It then returns to the low-power sleep mode, awaiting the next scheduled wake-up time.
** If the device fails to get a GNSS fix or send the data within a predefined timeout, it will abort the process and return to sleep to prevent battery drain.
=== <u> Parameters list </u>===
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<tr>
<th style="width:1%; vertical-align: middle; text-align: center;">PARAMETER NAME</th>
<th style="width:1%; vertical-align: middle; text-align: center;">PARAMETER ID (RELATED AVL ID)</th>
<th style="width:5%; vertical-align: middle; text-align: center;">DESCRIPTION</th>
<th style="width:6%; vertical-align: middle; text-align: center;">VALUES</th>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;"> Sunday Time 1-6 </td>
<td style="vertical-align: middle; text-align: center;"> 35100-35105 </td>
<td style="vertical-align: middle; text-align: center;"> Sets the times for scheduled records on Sunday </td>
<td style="vertical-align: middle; text-align: left;"> '''0-2359''' or '''2500''' </td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;"> Monday Time 1-6 </td>
<td style="vertical-align: middle; text-align: center;"> 35200-35205 </td>
<td style="vertical-align: middle; text-align: center;"> Sets the time for a scheduled record on Monday </td>
<td style="vertical-align: middle; text-align: left;"> '''0-2359''' or '''2500''' </td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;"> Tuesday Time 1-6 </td>
<td style="vertical-align: middle; text-align: center;"> 35300-35305 </td>
<td style="vertical-align: middle; text-align: center;"> Sets the time for a scheduled record on Tuesday </td>
<td style="vertical-align: middle; text-align: left;"> '''0-2359''' or '''2500'''  </td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;"> Wednesday Time 1-6 </td>
<td style="vertical-align: middle; text-align: center;"> 35400-35405</td>
<td style="vertical-align: middle; text-align: center;"> Sets the time for a scheduled record on Wednesday </td>
<td style="vertical-align: middle; text-align: left;"> '''0-2359''' or '''2500'''  </td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;"> Friday Time 1-6 </td>
<td style="vertical-align: middle; text-align: center;"> 35600-35605</td>
<td style="vertical-align: middle; text-align: center;"> Sets the time for a scheduled record on Friday </td>
<td style="vertical-align: middle; text-align: left;"> '''0-2359''' or '''2500'''  </td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;"> Saturday Time 1-6 </td>
<td style="vertical-align: middle; text-align: center;"> 35700-35705</td>
<td style="vertical-align: middle; text-align: center;"> Sets the time for a scheduled record on Saturday </td>
<td style="vertical-align: middle; text-align: left;"> '''0-2359''' or '''2500'''  </td>
</tr>
</table>
'''Note:''' Wakeup times in configuration are stored as a list of uint16 variables in format HHmm (range from 0 to 2359), for example: 12:00 -> 1200, 01:45 -> 145, 23:59 -> 2359. Default value for unconfigured timestamps is 2500.
=== <u> Limitations, Edge Cases & Additional Notes  </u> ===
* 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 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.
[[Category:{{{model}}} Configuration]]

Latest revision as of 09:15, 30 April 2026

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