Template:FTX Input/Output (I/O) - Revision history

Justinas.strelciunas at 09:12, 17 September 2025

2025-09-17T09:12:55Z

← Older revision		Revision as of 12:12, 17 September 2025
Line 156:		Line 156:
	* Once you have the parameter IDs, set or modify them in your configuration tool to match the desired priority, operand, or other CAN-related settings.<br>		* Once you have the parameter IDs, set or modify them in your configuration tool to match the desired priority, operand, or other CAN-related settings.<br>
	}}		}}
			<!-- If model supports Manual CAN, then show -->
			{{#if: {{FTX Pin Support List\|model={{{model}}}\|pin=Manual CAN}} \|
	==Manual CAN Commands==		==Manual CAN Commands==
	Manual CAN Commands functionality allows user to send configurable commands to CAN BUS.		Manual CAN Commands functionality allows user to send configurable commands to CAN BUS.
Line 201:		Line 202:

	After configuring, Manual CAN commands can be triggered with SMS/GPRS commands: [[{{{model}}} SMS/GPRS Command List#CAN Commands\|{{{model}}} SMS/GPRS Commands]].		After configuring, Manual CAN commands can be triggered with SMS/GPRS commands: [[{{{model}}} SMS/GPRS Command List#CAN Commands\|{{{model}}} SMS/GPRS Commands]].
			}}


	[[Category:{{{model}}} Configuration]]		[[Category:{{{model}}} Configuration]]

Justinas.strelciunas: /* Permanent I/O */

2025-09-17T06:54:11Z

Permanent I/O

← Older revision		Revision as of 09:54, 17 September 2025
Line 74:		Line 74:
	After enabling I/O element(s) AVL packet contains current value(s) of enabled I/O element(s) along with GNSS information.		After enabling I/O element(s) AVL packet contains current value(s) of enabled I/O element(s) along with GNSS information.

			<!-- If model supports DOUT1, then show -->
			{{#if: {{FTX_Pin_Support List\|model={{{model}}}\|pin=DOUT1}} \|
	===General I/O Settings===		===General I/O Settings===
	[[File:General IO settings - menu.png\|right\|500px]]		[[File:General IO settings - menu.png\|right\|500px]]
Line 94:		Line 96:

	'''IMPORTANT! DOUT state I/O element that is sent in the records represents the real state of the DOUT pin.'''		'''IMPORTANT! DOUT state I/O element that is sent in the records represents the real state of the DOUT pin.'''
			}}

	<!-- If model supports Manual CAN, then show -->		<!-- If model supports Manual CAN, then show -->

Donatas.Mazonas: Added "Command Enabler" parameter for "Manual CAN Commands"

2025-09-12T12:12:38Z

Added "Command Enabler" parameter for "Manual CAN Commands"

← Older revision		Revision as of 15:12, 12 September 2025
Line 191:		Line 191:
	*'''Send count''' - defines command sending count if Periodic send type is selected.		*'''Send count''' - defines command sending count if Periodic send type is selected.
	**If set to '''0''' - command will be sent '''infinitely''' until it is turned off by the user.		**If set to '''0''' - command will be sent '''infinitely''' until it is turned off by the user.

			*'''Command Enabler''' - toggles command.
			**If enabled - command will send CAN messages.
			**If disabled, the command will not be available to trigger sending, even if configured.


	After configuring, Manual CAN commands can be triggered with SMS/GPRS commands: [[{{{model}}} SMS/GPRS Command List#CAN Commands\|{{{model}}} SMS/GPRS Commands]].		After configuring, Manual CAN commands can be triggered with SMS/GPRS commands: [[{{{model}}} SMS/GPRS Command List#CAN Commands\|{{{model}}} SMS/GPRS Commands]].

	}}

	[[Category:{{{model}}} Configuration]]		[[Category:{{{model}}} Configuration]]

Donatas.Mazonas: /* Permanent I/O */ Added "General I/O Settings" menu button description and parameters "Overcurrent recovery" and "Inversion".

2025-09-12T07:15:19Z

Permanent I/O: Added "General I/O Settings" menu button description and parameters "Overcurrent recovery" and "Inversion".

@@ Line 69: / Line 69: @@
 ==Permanent I/O==
 When no permanent I/O elements are enabled, AVL packet comes with GNSS information only.
-[[File:FTX permanent io.png|center|thumb|1100x1100px]]
+After enabling I/O element(s) AVL packet contains current value(s) of enabled I/O element(s) along with GNSS information.
-After enabling I/O element(s) AVL packet contains current value(s) of enabled I/O element(s) along with GNSS information.
+===General I/O Settings===
 <!-- If model supports Manual CAN, then show -->

Justinas.strelciunas at 06:14, 12 September 2025

2025-09-12T06:14:48Z

← Older revision		Revision as of 09:14, 12 September 2025
Line 78:		Line 78:
	{{#if: {{FTX Pin Support List\|model={{{model}}}\|pin=Manual CAN}} \|		{{#if: {{FTX Pin Support List\|model={{{model}}}\|pin=Manual CAN}} \|

	~~==Manual CAN==~~
	== Manual CAN ==		== Manual CAN ==
	[[File:Manual CAN - menu.png\|right\|500px]]		[[File:Manual CAN - menu.png\|right\|500px]]

Justinas.strelciunas at 06:14, 12 September 2025

2025-09-12T06:14:15Z

← Older revision		Revision as of 09:14, 12 September 2025
Line 79:		Line 79:

	==Manual CAN==		==Manual CAN==
	Manual CAN ~~functionality allows~~ user ~~to read data from~~ CAN ~~BUS without requiring an additional~~ CAN ~~protocol development from the firmware side~~.		== Manual CAN ==
			[[File:Manual CAN - menu.png\|right\|500px]]
			The user can configure 70 Manual CAN I/O element by setting Priority, CAN Type, CAN ID, Data Mask, Operand. Each CAN I/O has its own parameters and can be configured independentely.

	'''~~Note:~~''' ~~Before using Manual CAN, make sure~~ to ~~select~~ the ~~correct CAN settings: [[{{{model}}} Accessories#CAN\|{{{model}}} CAN settings]]~~.		When configuring CAN IO elements, each parameter (like priority, operand, CAN type, CAN ID, etc.) requires a unique '''configuration ID'''. These IDs follow specific formulas to ensure no overlap with other parameters in the system. This guide explains how to calculate them.

	~~Up to~~ '''70''' ~~Manual CAN I/Os can be configured:~~		==='''Formula:'''===
			Parameter_ID = 1,000,000 + (AVL_ID * 100) + OPTION Parameter_ID = 1,000,000 + (AVL_ID * 100) + OPTION

	~~[[File~~:~~FTX manual can~~.~~png\|center\|thumb\|1100x1100px]]~~		* 1,000,000: Base offset for CAN-related parameters.
			* AVL_ID: The CAN AVL IO element identifier (within certain allowed ranges).
			* OPTION: A small integer offset indicating which setting is being adjusted (e.g., priority or operand).

	~~Configurable settings:~~		'''Valid AVL Ranges '''
	*'''~~Priority''' - defines the priority of '''Manual CAN I/O~~''':		* [10216:10235]
	**'''~~Low~~''' ~~- enables~~ the ~~I/O element~~, ~~adding its value to periodic or eventual record packets based on the "Operand" and "Event only" settings. Events are sent along with periodic data according to the "Data acquisition" configuration.~~		* [10298:10347]
	**'''High''' - enables the I/O element with high priority, ~~immediately sending its value to the server in a high-priority eventual record. If the "Operand" is set to "Monitoring~~,~~" it functions the same as "Low Priority."~~		'''
			Example:''' If AVL_ID is 10216 and the OPTION for “priority” is 1, then
			Parameter ID=1,000,000+(10216×100)+1=1,000,000+1,021,600+1=2,021,601

	*'''~~CAN type~~''' ~~- defines which CAN ID type will be received and requested~~:		=== '''MCAN IO Parameter Calculation''' ===
	**'''~~Standard~~''' ~~- uses~~ '''~~11 bits~~''' ~~to read the CAN ID, allowing for 2,048 unique IDs (0x000 to 0x7FF)~~.'''		For MCAN IO elements (e.g., MCAN0, MCAN1, MCAN2…), each has three specific parameters: '''CAN Type, CAN ID,''' and '''Data Mask'''. The '''MCAN IO''' '''number''' is the index of the MCAN entry (starting at 0, 1, 2, etc.).
	**'''~~Extended~~''' ~~- uses~~ '''~~29 bits''' to read~~ the ~~CAN ID~~, ~~allowing for 536~~,~~870~~,~~912 unique IDs (0x00000000 to 0x1FFFFFFF~~).

	*'''~~CAN ID~~''' ~~– depends on~~ CAN Type ~~parameter and defines which CAN~~ ID ~~will be received by device~~.		'''''Formulas'''''
	**This identifier is composed of '''~~4 bytes~~'''.		1. '''CAN Type'''
	**For '''~~SAE J1939~~''', the first and last bytes can vary depending on the vehicle make or model, while the bytes in between remain the same for all vehicles. Although the first and last bytes may hold any value, it is recommended to use FF for both.		Parameter ID=17,000+(10×MCAN IO number)
			2. '''CAN ID'''
			Parameter ID=17,001+(10×MCAN IO number)
			3. '''Data Mask'''
			Parameter ID=17,002+(10×MCAN IO number)

	*'''Data ~~mask~~''' ~~– defines which data bytes are sent to the server~~ (~~sometimes not all data bytes are necessary~~)~~. Up to 8 particular data bytes can be selected for each~~ CAN ID.		'''Examples'''
			* '''MCAN0''' (IO number = 0):
			** '''CAN Type:''' 17000 + (10 × 0) = 17000
			** '''CAN ID:''' 17001 + (10 × 0) = 17001
			** '''Data Mask:''' 17002 + (10 × 0) = 17002
			* '''MCAN1''' (IO number = 1):
			** '''CAN Type:''' 17000 + (10 × 1) = 17010
			** '''CAN ID:''' 17001 + (10 × 1) = 17011
			** '''Data Mask:''' 17002 + (10 × 1) = 17012
			* '''MCAN69''' (IO number = 69):
			** '''CAN Type:''' 17000 + (10 × 69) = 17690
			** '''CAN ID:''' 17001 + (10 × 69) = 17691
			** '''Data Mask:''' 17002 + (10 × 69) = 17692

	*'''~~Operand~~''' ~~– defines when to generate event:~~		'''Putting It All Together''' <br>
	**'''~~Monitoring~~''' ~~- continuously monitors~~ the ~~current I/O element value in with every periodical record~~. ~~No eventual records are created when using~~ the ~~"Monitoring" operand~~.		1. '''Check Your AVL ID Range''' <br>
	**'''~~On Change~~''' - ~~generates an eventual record whenever the input value changes~~.		* If your CAN IO element has an AVL ID in [10216–10235] or [10298–10347], use the '''first formula''' for Parameter_ID = 1,000,000 + (AVL_ID * 100) + OPTION. <br>
			2. '''Identify Your MCAN IO Number''' <br>
			* If you have an MCAN entry (e.g., MCAN0, MCAN1), use the '''second set of formulas''' to find the corresponding '''CAN Type, CAN ID, and Data Mask''' parameter IDs. <br>
			3. '''Plug In the Numbers''' <br>
			* Calculate step by step, ensuring you add the correct base offsets and multipliers. <br>
			4. '''Configure Your Device''' <br>
			* Once you have the parameter IDs, set or modify them in your configuration tool to match the desired priority, operand, or other CAN-related settings.<br>
			}}

	==Manual CAN Commands==		==Manual CAN Commands==

Irmantas.K at 18:10, 27 March 2025

2025-03-27T18:10:21Z

← Older revision		Revision as of 21:10, 27 March 2025
Line 76:		Line 76:

	<!-- If model supports Manual CAN, then show -->		<!-- If model supports Manual CAN, then show -->
	{{#~~switch~~: {{{model~~\|FTC305~~}}}		{{#if: {{FTX Pin Support List\|model={{{model}}}\|pin=Manual CAN}} \|
	\| ~~FTC305~~
	\| ~~FTM305 =~~

	==Manual CAN==		==Manual CAN==

Irmantas.K: Protected "Template:FTX Input/Output (I/O)" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

2025-03-26T14:48:40Z

Protected "Template:FTX Input/Output (I/O)" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

← Older revision		Revision as of 17:48, 26 March 2025
(No difference)

Irmantas.K at 16:30, 12 March 2025

2025-03-12T16:30:21Z

← Older revision		Revision as of 19:30, 12 March 2025
Line 83:		Line 83:
	Manual CAN functionality allows user to read data from CAN BUS without requiring an additional CAN protocol development from the firmware side.		Manual CAN functionality allows user to read data from CAN BUS without requiring an additional CAN protocol development from the firmware side.

	'''Note:''' Before using Manual CAN, make sure to select the correct CAN settings: [[{{{model}}} Accessories#CAN\|CAN]].		'''Note:''' Before using Manual CAN, make sure to select the correct CAN settings: [[{{{model}}} Accessories#CAN\|{{{model}}} CAN settings]].

	Up to '''70''' Manual CAN I/Os can be configured:		Up to '''70''' Manual CAN I/Os can be configured:
Line 111:		Line 111:
	Manual CAN Commands functionality allows user to send configurable commands to CAN BUS.		Manual CAN Commands functionality allows user to send configurable commands to CAN BUS.

	'''Note:''' Before using Manual CAN, make sure to select the correct CAN settings: [[{{{model}}} Accessories#CAN\|CAN]].		'''Note:''' Before using Manual CAN, make sure to select the correct CAN settings: [[{{{model}}} Accessories#CAN\|{{{model}}} CAN settings]].

	Up to '''10''' Manual CAN Command I/Os can be configured:		Up to '''10''' Manual CAN Command I/Os can be configured:

Irmantas.K at 16:27, 12 March 2025

2025-03-12T16:27:31Z

← Older revision		Revision as of 19:27, 12 March 2025
Line 146:		Line 146:
	**If set to '''0''' - command will be sent '''infinitely''' until it is turned off by the user.		**If set to '''0''' - command will be sent '''infinitely''' until it is turned off by the user.

	After configuring, Manual CAN commands can be triggered with SMS/GPRS commands: [[{{{model}}} SMS/~~GPRS_Commands~~#CAN Commands\|{{{model}}} SMS/GPRS Commands]].		After configuring, Manual CAN commands can be triggered with SMS/GPRS commands: [[{{{model}}} SMS/GPRS Command List#CAN Commands\|{{{model}}} SMS/GPRS Commands]].

	}}		}}

	[[Category:{{{model}}} Configuration]]		[[Category:{{{model}}} Configuration]]