Template:FTX Features - Revision history

Justinas.strelciunas: FTXXXX WIKI sync with 3.7.x Stage 2 - Resync

2026-04-30T07:02:43Z

FTXXXX WIKI sync with 3.7.x Stage 2 - Resync

← Older revision		Revision as of 10:02, 30 April 2026
Line 1,055:		Line 1,055:

	Settings here (see table below) will affect what can be configured in the „Output control“ section of a particular geozone.		Settings here (see table below) will affect what can be configured in the „Output control“ section of a particular geozone.
			<br><br><br><br><br><br><br><br><br><br><br><br><br><br>
	====Parameters in global settings====		====Parameters in global settings====
	<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">		<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">

Justinas.strelciunas: FTXXXX WIKI sync with 3.7.x Stage 2 - Resync

2026-04-30T05:51:17Z

FTXXXX WIKI sync with 3.7.x Stage 2 - Resync

← Older revision		Revision as of 08:51, 30 April 2026
Line 740:		Line 740:
	* 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.		* 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.
	}}		}}
			{{#switch: {{{model}}}
			\| #default =
	'''BLE Sensors'''		'''BLE Sensors'''
	* If no BLE device authorization list is used, any ID can be used for authorization.		* If no BLE device authorization list is used, any ID can be used for authorization.
Line 754:		Line 755:
	'''NOTE:'''<br>		'''NOTE:'''<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.		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.
			\| FTC305
			\| FTM305 =
			}}

	===Parameters===		===Parameters===

Justinas.strelciunas: FTXXXX WIKI sync with 3.7.x Stage 2 - Resync

2026-04-30T05:45:08Z

FTXXXX WIKI sync with 3.7.x Stage 2 - Resync

← Older revision		Revision as of 08:45, 30 April 2026
Line 731:		Line 731:
	* 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.		* 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:'''		5. '''Authorization list management:'''
			{{#switch: {{{model}}}
			\| FTC134
			\| FTM134
			\| FTC305
			\| FTM305 =
	'''1-Wire'''		'''1-Wire'''
	* If no 1-Wire authorization list is used, any ID can be used for authorization.		* 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.		* 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'''		'''BLE Sensors'''

Justinas.strelciunas: FTXXXX WIKI sync with 3.7.x Stage 2 - Resync

2026-04-30T05:16:07Z

FTXXXX WIKI sync with 3.7.x Stage 2 - Resync

← Older revision		Revision as of 08:16, 30 April 2026
Line 684:		Line 684:
	=VEHICLE PROTECTION=		=VEHICLE PROTECTION=
	{{#switch: {{{model}}}		{{#switch: {{{model}}}
			\| FTC924
			\| FTC927
	\| FTC965		\| FTC965
	\| FTC887		\| FTC887

Donatas.Mazonas: /* DOUT State in Sleep mode */ Resized table

2026-03-23T12:06:29Z

DOUT State in Sleep mode: Resized table

← Older revision		Revision as of 15:06, 23 March 2026
Line 75:		Line 75:
	==== DOUT State in Sleep mode ====		==== DOUT State in Sleep mode ====
	In different sleep modes, DOUT behavior and Private/Business states are:		In different sleep modes, DOUT behavior and Private/Business states are:
	<table class="nd-othertables_2" style="width:~~100~~%; border-collapse: collapse;">		<table class="nd-othertables_2" style="width:50%; border-collapse: collapse;">
	<tr>		<tr>
	<th style="width:15%; vertical-align: middle; text-align: center;">MODE</th>		<th style="width:15%; vertical-align: middle; text-align: center;">MODE</th>
Line 112:		Line 112:

	''NOTE! If Trigger type is set to '''External''', the user must press the button or switch again to re enable Private Mode. If Trigger type is set to '''Weekly Schedule''', the user must wait until the next scheduled activation time for Private Mode to be enabled again.''		''NOTE! If Trigger type is set to '''External''', the user must press the button or switch again to re enable Private Mode. If Trigger type is set to '''Weekly Schedule''', the user must wait until the next scheduled activation time for Private Mode to be enabled again.''

	====Feature Triggers====		====Feature Triggers====
	This section allows the user to configure the trigger logic that switches the feature between '''Private Mode''' and '''Business Mode'''.		This section allows the user to configure the trigger logic that switches the feature between '''Private Mode''' and '''Business Mode'''.

Donatas.Mazonas: /* Parameters for coordinates */ Typo, removed duplicate row from table

2026-03-23T09:54:57Z

Parameters for coordinates: Typo, removed duplicate row from table

← Older revision		Revision as of 12:54, 23 March 2026
Line 1,207:		Line 1,207:
	<th style="width:50%; vertical-align: middle; text-align: center;">DESCRIPTION</th>		<th style="width:50%; vertical-align: middle; text-align: center;">DESCRIPTION</th>
	<th style="width:20%; vertical-align: middle; text-align: center;">VALUES</th>		<th style="width:20%; vertical-align: middle; text-align: center;">VALUES</th>
	~~</tr>~~
	~~<tr>~~
	~~<td style="vertical-align: middle; text-align: left;">Frame Border (m)</td>~~
	~~<td style="vertical-align: middle; text-align: center;">900003</td>~~
	~~<td style="vertical-align: middle; text-align: left;">Border size of geozone.</td>~~
	~~<td style="vertical-align: middle; text-align: left;">Min = 0<br>Max = 1000000<br>Default = "0"</td>~~
	</tr>		</tr>
	<tr>		<tr>

Arijus.C: /* VEHICLE PROTECTION */

2026-03-20T09:39:51Z

VEHICLE PROTECTION

Show changes

Justinas.strelciunas: /* Private / Business mode */

2026-03-20T06:58:01Z

Private / Business mode

← Older revision		Revision as of 09:58, 20 March 2026
Line 55:		Line 55:
	==Private / Business mode==		==Private / Business mode==
	{{#switch: {{{model}}}		{{#switch: {{{model}}}
	\| # default = [[File:Private business mode TCT panel.png\|right\|500px]]		\| #default = [[File:Private business mode TCT panel.png\|right\|500px]]
	\| FTC887		\| FTC887
	\| FTM887		\| FTM887

Justinas.strelciunas: /* Private / Business mode */

2026-03-20T06:55:01Z

Private / Business mode

← Older revision		Revision as of 09:55, 20 March 2026
Line 55:		Line 55:
	==Private / Business mode==		==Private / Business mode==
	{{#switch: {{{model}}}		{{#switch: {{{model}}}
	# default = [[File:Private business mode TCT panel.png\|right\|500px]]		\| # default = [[File:Private business mode TCT panel.png\|right\|500px]]
	\| FTC887		\| FTC887
	\| FTM887		\| FTM887
	\| FTC880		\| FTC880
	\| FTM880 =		\| FTM880 = [[File:Private business mode TCT panel without DIN option.png\|right\|500px]]
	[[File:Private business mode TCT panel without DIN option.png\|right\|500px]]
	}}		}}
	This feature enables employees to use company vehicles for personal purposes while maintaining compliance with EU General Data Protection Regulation requirements. When Private mode is active, the device masks location data and other sensitive information to prevent unauthorized tracking. Business mode restores full data visibility for standard fleet operations.		This feature enables employees to use company vehicles for personal purposes while maintaining compliance with EU General Data Protection Regulation requirements. When Private mode is active, the device masks location data and other sensitive information to prevent unauthorized tracking. Business mode restores full data visibility for standard fleet operations.

Justinas.strelciunas: Create Private/Business Driving Mode Functionality page GPKTMA-1830

2026-03-20T06:51:55Z

Create Private/Business Driving Mode Functionality page GPKTMA-1830

← Older revision		Revision as of 09:51, 20 March 2026
Line 54:		Line 54:

	==Private / Business mode==		==Private / Business mode==
	[[File:Private business mode TCT panel.png\|right\|500px]]		{{#switch: {{{model}}}
			# default = [[File:Private business mode TCT panel.png\|right\|500px]]
			\| FTC887
			\| FTM887
			\| FTC880
			\| FTM880 =
			[[File:Private business mode TCT panel without DIN option.png\|right\|500px]]
			}}
	This feature enables employees to use company vehicles for personal purposes while maintaining compliance with EU General Data Protection Regulation requirements. When Private mode is active, the device masks location data and other sensitive information to prevent unauthorized tracking. Business mode restores full data visibility for standard fleet operations.		This feature enables employees to use company vehicles for personal purposes while maintaining compliance with EU General Data Protection Regulation requirements. When Private mode is active, the device masks location data and other sensitive information to prevent unauthorized tracking. Business mode restores full data visibility for standard fleet operations.