Template:FTX Tracking settings - Revision history

Andrius.Grajevskis: /* Records settings */

2026-03-31T11:15:52Z

Records settings

← Older revision		Revision as of 14:15, 31 March 2026
Line 14:		Line 14:
	'''Possible options:'''		'''Possible options:'''

	'''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 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. “GNSS position fix search timeout” is not used here; therefore, records may lack GNSS location data.		'''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.

Andrius.Grajevskis: /* Records settings */

2026-03-31T11:15:11Z

Records settings

← Older revision		Revision as of 14:15, 31 March 2026
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.

Andrius.Grajevskis: /* Records schedule */

2026-03-24T08:21:01Z

Records schedule

← Older revision		Revision as of 11:21, 24 March 2026
Line 282:		Line 282:

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

Donatas.Mazonas at 12:59, 18 March 2026

2026-03-18T12:59:45Z

← Older revision		Revision as of 15:59, 18 March 2026
Line 219:		Line 219:
	* The available I/O triggers depend on the hardware of your device.		* 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)]]).		* 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 ([[~~{{{model}}} Tracking~~ settings]]):		* 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 '''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.		** 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.

Donatas.Mazonas at 12:57, 18 March 2026

2026-03-18T12:57:15Z

Donatas.Mazonas: Added section "On-demand tracking" [GPKTMA-1832]

2026-03-18T12:53:31Z

Added section "On-demand tracking" [GPKTMA-1832]

@@ Line 205: / Line 205: @@
 | ATC700 =
 }}
 == Records schedule ==
 [[File:Records Schedule TCT panel.png|right|500px]]

Justinas.strelciunas: FTX Tracking settings changes - X1

2026-03-10T11:01:15Z

FTX Tracking settings changes - X1

← Older revision		Revision as of 14:01, 10 March 2026
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]]

Justinas.strelciunas: /* Limitations, Edge Cases & Additional Notes */

2025-12-05T08:37:00Z

Limitations, Edge Cases & Additional Notes

← Older revision		Revision as of 11:37, 5 December 2025
Line 300:		Line 300:
	=== <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 ~~will~~ not send a record.		* 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]]

Justinas.strelciunas: /* Basic Operation */

2025-12-05T08:35:53Z

Basic Operation

← Older revision		Revision as of 11:35, 5 December 2025
Line 222:		Line 222:
	=== <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.		** 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.

Justinas.strelciunas at 08:21, 5 December 2025

2025-12-05T08:21:52Z

← Older revision		Revision as of 11:21, 5 December 2025
Line 48:		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}}}		{{#switch: {{{model}}}
	\| ATM700		\| ATM700
Line 106:		Line 107:
	}}		}}

	~~{{#switch: {{{model}}}~~
	~~\| #default =~~
	==Network operators settings==		==Network operators settings==
	[[File:FTX network operators settings.png\|right\|500 px]]		[[File:FTX network operators settings.png\|right\|500 px]]
Line 122:		Line 121:
	<br><br><br><br><br><br><br><br>		<br><br><br><br><br><br><br><br>

	~~\| ATC700~~		{{#switch: {{{model}}}
	~~\| ATM700 =~~		\| #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 202:
	**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 =
			}}
	== Records schedule ==		== Records schedule ==
	[[File:Records Schedule TCT panel.png\|right\|500px]]		[[File:Records Schedule TCT panel.png\|right\|500px]]

← Older revision		Revision as of 15:57, 18 March 2026
Line 218:		Line 218:
	* Related [[SMS/GPRS command - on_demand_tracking]].		* Related [[SMS/GPRS command - on_demand_tracking]].
	* The available I/O triggers depend on the hardware of your device.		* 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 ([[({{{model}}}~~_Input~~/~~output_~~(I/O)]]).		* 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 ([[({{{model}}}~~Tracking_settings~~]]):		* On-demand tracking interacts with periodic record acquisition ([[{{{model}}} Tracking 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 '''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.		** 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.
Line 243:		Line 243:
	<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">		<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
	<tr>		<tr>
	<th style="width:1%; vertical-align: middle; text-align: center;">PARAMETER NAME</th>		<th style="width:15%; 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:15%; 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:50%; vertical-align: middle; text-align: center;">DESCRIPTION</th>
	<th style="width:6%; vertical-align: middle; text-align: center;">VALUE(S)</th>		<th style="width:20%; vertical-align: middle; text-align: center;">VALUE(S)</th>
	</tr>		</tr>
	<tr>		<tr>