TFT100 CAN I/O settings - Revision history

Arijus.C at 06:44, 27 April 2026

2026-04-27T06:44:24Z

← Older revision		Revision as of 09:44, 27 April 2026
Line 154:		Line 154:
	===Debug===		===Debug===
	{\| style="width: 100%"		{\| style="width: 100%"
	\|[[File:Debug ~~CAN Protocol~~.png\|right]]		\|[[File:CAN Debug.png\|right]]
	Debug Protocol is used to read all incoming message through CAN, it works as a CAN reader. By default it will print incoming messages into Terminal, including CAN ID and Data.		Debug Protocol is used to read all incoming message through CAN, it works as a CAN reader. By default it will print incoming messages into Terminal, including CAN ID and Data.
	\|}		\|}

Arijus.C at 06:40, 27 April 2026

2026-04-27T06:40:44Z

← Older revision		Revision as of 09:40, 27 April 2026
Line 9:		Line 9:
	CAN interface '''does not work''' when device does not have external power available.		CAN interface '''does not work''' when device does not have external power available.
	\|}		\|}
	[[~~Image~~:CAN ~~protocol~~.png\|right~~\|260px~~]]		[[File:CAN Protocol.png\|right]]
	'''CAN I/O''' category offers users an ability to select one of CAN protocols to read specific data through TFT100 CAN interface.<br>		'''CAN I/O''' category offers users an ability to select one of CAN protocols to read specific data through TFT100 CAN interface.<br>

Line 30:		Line 30:
	<hr>		<hr>
	{\| style="width: 100%"		{\| style="width: 100%"
	\|[[~~Image~~:~~Bosch~~ CAN ~~Powertrain protocol~~.~~gif~~\|right]]		\|[[File:Boch CAN Protocol.png\|right]]
	'''Bosch CAN Powertrain protocol''' allows users to read parameters from their transport, if the transport uses ''Bosch'' motor. The protocol is enabled by selecting '''Bosch''' parameter in ''CAN Protocol'' field as shown in the image on the right hand side.		'''Bosch CAN Powertrain protocol''' allows users to read parameters from their transport, if the transport uses ''Bosch'' motor. The protocol is enabled by selecting '''Bosch''' parameter in ''CAN Protocol'' field as shown in the image on the right hand side.
	\|}		\|}
Line 49:		Line 49:
	<hr>		<hr>
	{\| style="width: 100%"		{\| style="width: 100%"
	\|[[~~Image~~:Askoll ~~protocol~~.~~gif~~\|right]]		\|[[File:Askoll CAN Protocol.png\|right]]
	'''Askoll''' CAN protocol allows users to read parameters from their e-scooters manufactured by ''Askoll''. The protocol is enabled by selecting '''Askoll''' parameter in ''CAN Protocol'' field as shown in the image on the right hand side.		'''Askoll''' CAN protocol allows users to read parameters from their e-scooters manufactured by ''Askoll''. The protocol is enabled by selecting '''Askoll''' parameter in ''CAN Protocol'' field as shown in the image on the right hand side.
	\|}		\|}
Line 63:		Line 63:
	<hr>		<hr>
	{\| style="width: 100%"		{\| style="width: 100%"
	\|[[~~Image~~:Default J1939 ss.png\|right]]		\|[[File:Default J1939 CAN Protocol.png\|right]]
	'''Default J1939''' protocol support was added to TFT100 device's firmware since it is one of the most popular CAN protocols used in heavy duty (i.e. ''forklifts'') machinery industry. If the machinery communicates via J1939 CAN protocol, the device will be able to read provided parameter's data and transmit readings to your configured server. To use '''Default J1939''' CAN protocol user should select '''Default J1939''' parameter in ''CAN Protocol'' field as shown in the image on the right hand side.		'''Default J1939''' protocol support was added to TFT100 device's firmware since it is one of the most popular CAN protocols used in heavy duty (i.e. ''forklifts'') machinery industry. If the machinery communicates via J1939 CAN protocol, the device will be able to read provided parameter's data and transmit readings to your configured server. To use '''Default J1939''' CAN protocol user should select '''Default J1939''' parameter in ''CAN Protocol'' field as shown in the image on the right hand side.

Line 86:		Line 86:
	===Manual CAN===		===Manual CAN===
	<hr>		<hr>
	[[~~Image~~:Manual CAN ~~protocol~~.~~gif~~\|right]]		[[File:Manual CAN Protocol.png\|right]]
	The '''Manual CAN''' protocol is enabled by selecting '''Manual CAN''' parameter in ''CAN Protocol'' field as shown in the image on the right hand side. Then user can configure CAN parameters in [[TFT100_Manual_CAN_settings\|Manual CAN Settings]] tab.		The '''Manual CAN''' protocol is enabled by selecting '''Manual CAN''' parameter in ''CAN Protocol'' field as shown in the image on the right hand side. Then user can configure CAN parameters in [[TFT100_Manual_CAN_settings\|Manual CAN Settings]] tab.
	{\| class="wikitable" style="border-style: solid; border-width: 0px;"		{\| class="wikitable" style="border-style: solid; border-width: 0px;"
Line 115:		Line 115:
	===Manual J1939===		===Manual J1939===
	<hr>		<hr>
	[[~~Image~~:Manual J1939.~~gif~~\|right]]		[[File:Manual J1939 Protocol.png\|right]]
	'''Manual J1939''' protocol support was added to TFT100 device's firmware as an addition to '''Default J1939''' protocol in case the given '''Default J1939''' I/O elements are not enough. With this functionality, the user is able to configure which '''J1939''' parameters he would like to read from the transport that uses '''J1939''' protocol. '''Manual J1939''' protocol is enabled by selecting '''Manual J1939''' parameter in ''CAN Protocol'' field as shown in the image on the right hand side. Then user can configure CAN parameters in [[TFT100_Manual_CAN_settings\|Manual CAN Settings]] tab.		'''Manual J1939''' protocol support was added to TFT100 device's firmware as an addition to '''Default J1939''' protocol in case the given '''Default J1939''' I/O elements are not enough. With this functionality, the user is able to configure which '''J1939''' parameters he would like to read from the transport that uses '''J1939''' protocol. '''Manual J1939''' protocol is enabled by selecting '''Manual J1939''' parameter in ''CAN Protocol'' field as shown in the image on the right hand side. Then user can configure CAN parameters in [[TFT100_Manual_CAN_settings\|Manual CAN Settings]] tab.
	{\| class="wikitable" style="border-style: solid; border-width: 0px;"		{\| class="wikitable" style="border-style: solid; border-width: 0px;"
Line 154:		Line 154:
	===Debug===		===Debug===
	{\| style="width: 100%"		{\| style="width: 100%"
	\|[[File:Debug ~~feature~~.png\|right~~\|260px~~]]		\|[[File:Debug CAN Protocol.png\|right]]
	Debug Protocol is used to read all incoming message through CAN, it works as a CAN reader. By default it will print incoming messages into Terminal, including CAN ID and Data.		Debug Protocol is used to read all incoming message through CAN, it works as a CAN reader. By default it will print incoming messages into Terminal, including CAN ID and Data.
	\|}		\|}

Arijus.C: Updating per GTPGTM-11729

2026-04-27T05:09:38Z

Updating per GTPGTM-11729

← Older revision		Revision as of 08:09, 27 April 2026
Line 141:		Line 141:
	<hr>		<hr>
	[[File:CAN Settings.png\|right]]		[[File:CAN Settings.png\|right]]
	The ~~<b>FLEX</b>~~ protocol is enabled by selecting '''~~FLEX~~''' parameter in ''CAN Protocol'' field.		The '''Govecs protocol''' is enabled by selecting '''Govecs''' parameter in ''CAN Protocol'' field.

			'''Govecs''' protocol version can be selected from '''FLEX''' and '''Olympus'''.

	====Govecs I/O====		====Govecs I/O====

Arijus.C at 07:38, 24 March 2026

2026-03-24T07:38:50Z

← Older revision		Revision as of 10:38, 24 March 2026
Line 18:		Line 18:
	*Manual CAN		*Manual CAN
	*Manual J1939		*Manual J1939
	*FLEX		*Govecs
			**FLEX
			**Olympus
	*Debug feature		*Debug feature

	'''Bosch''', '''Askoll''', '''Default J1939''' and <b>~~FLEX~~</b> CAN protocols come with specific CAN I/O parameters that can be read, monitored, configured and their values sent to the configured server.<br>		'''Bosch''', '''Askoll''', '''Default J1939''' and <b>Govecs</b> CAN protocols come with specific CAN I/O parameters that can be read, monitored, configured and their values sent to the configured server.<br>
	'''Manual CAN''' and '''Manual J1939''' protocols do not include dedicated specific I/O parameters however it welcomes user to configure what has to be read from the transport based on their transport CAN communication protocol.		'''Manual CAN''' and '''Manual J1939''' protocols do not include dedicated specific I/O parameters however it welcomes user to configure what has to be read from the transport based on their transport CAN communication protocol.

Line 136:		Line 138:
	[[Image:Manual J1939 29 IO.gif]]<br><br>		[[Image:Manual J1939 29 IO.gif]]<br><br>

	===~~FLEX~~===		===Govecs===
	<hr>		<hr>
	[[~~Image~~:~~FLEX~~.~~PNG~~\|right]]		[[File:CAN Settings.png\|right]]
	The <b>FLEX</b> protocol is enabled by selecting '''FLEX''' parameter in ''CAN Protocol'' field.		The <b>FLEX</b> protocol is enabled by selecting '''FLEX''' parameter in ''CAN Protocol'' field.

	====~~FLEX~~ I/O====		====Govecs I/O====
	Specific <b>~~FLEX~~</b> I/O parameters were implemented to our device's firmware that can be read, configured and sent to the server just like regular I/O parameters.		Specific <b>Govecs</b> I/O parameters were implemented to our device's firmware that can be read, configured and sent to the server just like regular I/O parameters.

	*<code>The '''AVL ID''' list of '''~~FLEX~~''' parameters can be found in [[~~Full_AVL_ID_List~~#~~FLEX_I.2FO_elements~~\|here]].</code><br>		*<code>The '''AVL ID''' list of '''Govecs''' parameters can be found in [[TFT100 AVL ID List#FLEX I/O elements\|here]].</code><br>

	[[Image:FLEX CAN.gif]]<br><br>		[[Image:FLEX CAN.gif]]<br><br>

Justinas.strelciunas: /* CAN I/O reset */

2024-03-01T13:09:06Z

CAN I/O reset

← Older revision		Revision as of 16:09, 1 March 2024
Line 195:		Line 195:
	[[Image:Screenshot 2024-03-01 at 15-06-15 5.13. CAN Modification - Mobility documentation.png\|thumb]]		[[Image:Screenshot 2024-03-01 at 15-06-15 5.13. CAN Modification - Mobility documentation.png\|thumb]]

	'''~~Separate~~ I/O reset description'''		'''I/O reset description'''

	* '''Disabled''' - All I/O's will be reset, when no CAN data received in at least one of I/O's.		* '''Disabled''' - All I/O's will be reset, when no CAN data received in at least one of I/O's.

Justinas.strelciunas: /* Separate I/O reset description */

2024-03-01T13:08:28Z

Separate I/O reset description

← Older revision		Revision as of 16:08, 1 March 2024
Line 195:		Line 195:
	[[Image:Screenshot 2024-03-01 at 15-06-15 5.13. CAN Modification - Mobility documentation.png\|thumb]]		[[Image:Screenshot 2024-03-01 at 15-06-15 5.13. CAN Modification - Mobility documentation.png\|thumb]]

	== Separate I/O reset description==		'''Separate I/O reset description'''

	* '''Disabled''' - All I/O's will be reset, when no CAN data received in at least one of I/O's.		* '''Disabled''' - All I/O's will be reset, when no CAN data received in at least one of I/O's.

Justinas.strelciunas: /* CAN I/O reset */

2024-03-01T13:07:45Z

CAN I/O reset

← Older revision		Revision as of 16:07, 1 March 2024
Line 192:		Line 192:
	\| style="width: auto; text-align: left; background: #F6F6FB;" \|CAN IO resets in any case after device restart or CAN Protocol switching.		\| style="width: auto; text-align: left; background: #F6F6FB;" \|CAN IO resets in any case after device restart or CAN Protocol switching.
	\|}		\|}

			[[Image:Screenshot 2024-03-01 at 15-06-15 5.13. CAN Modification - Mobility documentation.png\|thumb]]

			== Separate I/O reset description==

			* '''Disabled''' - All I/O's will be reset, when no CAN data received in at least one of I/O's.
			* '''Enabled''' - Only I/O's with Reset timeout ** parameter enabled (in Manual CAN Settings section) and which received no data will be reset.


	[[Category:TFT100 Configuration]]		[[Category:TFT100 Configuration]]

Ignas A.: /* CAN Protocol */

2024-02-12T08:57:14Z

CAN Protocol

← Older revision		Revision as of 11:57, 12 February 2024
Line 2:		Line 2:

	==CAN Protocol==		==CAN Protocol==
			{\| class="wikitable" style="border-style: solid; border-width: 0px; width: 1154px;"
			\|+
			\|-
			\| style="text-align: left; background: #F6F6FB;" \| [[Image:Warning.png\|50px]]
			\| style="text-align: left; background: #F6F6FB;" \| '''ATTENTION'''
			CAN interface '''does not work''' when device does not have external power available.
			\|}
	[[Image:CAN protocol.png\|right\|260px]]		[[Image:CAN protocol.png\|right\|260px]]
	'''CAN I/O''' category offers users an ability to select one of CAN protocols to read specific data through TFT100 CAN interface.<br>		'''CAN I/O''' category offers users an ability to select one of CAN protocols to read specific data through TFT100 CAN interface.<br>
Line 159:		Line 166:
	After downloading, follow <b>“Open directory”</b> button. After unzipping file there will be CAN folder with “0.log” file. Maximum file size is 5MB. After exceeding limit it will rewrite data.		After downloading, follow <b>“Open directory”</b> button. After unzipping file there will be CAN folder with “0.log” file. Maximum file size is 5MB. After exceeding limit it will rewrite data.
	\|}		\|}


	==J1939 Settings==		==J1939 Settings==

Martyna.D: Protected "TFT100 CAN I/O settings" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

2023-03-27T06:38:30Z

Protected "TFT100 CAN I/O settings" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

← Older revision		Revision as of 09:38, 27 March 2023
(No difference)

Martyna.D: Created page with "TOC ==CAN Protocol== 260px '''CAN I/O''' category offers users an ability to select one of CAN protocols to read specific data through TF..."

2023-03-27T06:38:23Z

Created page with "__TOC__ ==CAN Protocol== right|260px '''CAN I/O''' category offers users an ability to select one of CAN protocols to read specific data through TF..."

New page

__TOC__

==CAN Protocol==
[[Image:CAN protocol.png|right|260px]]
'''CAN I/O''' category offers users an ability to select one of CAN protocols to read specific data through TFT100 CAN interface. 

TFT100 currently has 6 implemented CAN protocols and DEBUG function: 
*Bosch CAN Powertrain
*Askoll
*Default J1939
*Manual CAN
*Manual J1939
*FLEX
*Debug feature

'''Bosch''', '''Askoll''', '''Default J1939''' and FLEX CAN protocols come with specific CAN I/O parameters that can be read, monitored, configured and their values sent to the configured server. 
'''Manual CAN''' and '''Manual J1939''' protocols do not include dedicated specific I/O parameters however it welcomes user to configure what has to be read from the transport based on their transport CAN communication protocol.

===Bosch CAN Powertrain===
<hr>
{| style="width: 100%"
|[[Image:Bosch CAN Powertrain protocol.gif|right]]
'''Bosch CAN Powertrain protocol''' allows users to read parameters from their transport, if the transport uses ''Bosch'' motor. The protocol is enabled by selecting '''Bosch''' parameter in ''CAN Protocol'' field as shown in the image on the right hand side.
|}

====Bosch CAN Powertrain I/O====
Specific '''Bosch CAN Powertrain''' I/O parameters were implemented to our device's firmware that can be read, configured and sent to the server just like regular I/O parameters. The parameters that were added can be seen in the image below. 
{| class="wikitable" style="border-style: solid; border-width: 0px;"
|+
| style="width: auto; text-align: left; background: #F6F6FB;" |'''NOTE!'''
| style="width: auto; text-align: left; background: #F6F6FB;" |The parameters were added upon clients' request. ''Bosch'' CAN protocol contains way more parameters that can be added by us if necessary.
|}
[[Image:Bosch CAN Powertrain IO.gif]] 

*<code>The '''AVL ID''' list of '''Bosch CAN Powertrain''' parameters can be found in [[Full_AVL_ID_List#CAN_BOSCH_I.2FO_elements|here]].</code> 
*<code>'''SMS/GPRS commands''' that were developed for '''Bosch CAN Powertrain''' protocol can be found in [[TFT100_SMS/GPRS_Commands#CAN_Commands|here]].</code>

===Askoll===
<hr>
{| style="width: 100%"
|[[Image:Askoll protocol.gif|right]]
'''Askoll''' CAN protocol allows users to read parameters from their e-scooters manufactured by ''Askoll''. The protocol is enabled by selecting '''Askoll''' parameter in ''CAN Protocol'' field as shown in the image on the right hand side.
|}

====Askoll I/O====
Specific '''Askoll''' I/O parameters were implemented to our device's firmware that can be read, configured and sent to the server just like regular I/O parameters. The parameters that were added can be seen in the image below. 
[[Image:Askoll CAN IO.gif]] 

*<code>The '''AVL ID''' list of '''Askoll''' parameters can be found in [[Full_AVL_ID_List#CAN_Askoll_I.2FO_elements|here]].</code> 
*<code>'''SMS/GPRS commands''' that were developed for '''Askoll''' protocol can be found in [[TFT100_SMS/GPRS_Commands#CAN_Commands|here]].</code>

===Default J1939===
<hr>
{| style="width: 100%"
|[[Image:Default J1939 ss.png|right]]
'''Default J1939''' protocol support was added to TFT100 device's firmware since it is one of the most popular CAN protocols used in heavy duty (i.e. ''forklifts'') machinery industry. If the machinery communicates via J1939 CAN protocol, the device will be able to read provided parameter's data and transmit readings to your configured server. To use '''Default J1939''' CAN protocol user should select '''Default J1939''' parameter in ''CAN Protocol'' field as shown in the image on the right hand side.

{| class="wikitable" style="border-style: solid; border-width: 0px;"
|+
| style="width: auto; text-align: left; background: #F6F6FB;" |'''NOTE!'''
| style="width: auto; text-align: left; background: #F6F6FB;" |''Default J1939'' can be tested on FW 55.00.09.rev.04 or newer
|}
To read data with this functionality, the user must have:

*'''TFT100 device with CAN interface''';
*'''55.00.09.Rev.04 or newer firmware''';
*'''Machinery with CAN interface, which communicates via J1939 protocol'''.
|}

====Default J1939 I/O====
All '''Default J1939''' CAN I/O parameters can be configured like standard I/O parameters. User can set priority, high level, low level parameter limits, eventual record, operand, SMS text and number to which SMS notification would be sent.
[[Image:Default J1939 IO.gif]] 

*<code>The '''AVL ID''' list of '''Default J1939''' parameters can be found in [[Full_AVL_ID_List#Default_J1939_I.2FO_elements|here]].</code>

===Manual CAN===
<hr>
[[Image:Manual CAN protocol.gif|right]]
The '''Manual CAN''' protocol is enabled by selecting '''Manual CAN''' parameter in ''CAN Protocol'' field as shown in the image on the right hand side. Then user can configure CAN parameters in [[TFT100_Manual_CAN_settings|Manual CAN Settings]] tab.
{| class="wikitable" style="border-style: solid; border-width: 0px;"
|+
| style="width: auto; text-align: left; background: #F6F6FB;" |'''NOTE!'''
| style="width: auto; text-align: left; background: #F6F6FB;" |''Manual CAN'' can be tested on FW 55.00.09.rev.04 or newer
|}
The main benefit, of using '''Manual CAN''' functionality is that user is able to read data via CAN BUS without requiring additional CAN protocol development from the device's firmware side. To read data with this functionality, the user must have:

*'''TFT100 device with CAN interface''';
*'''55.00.09.Rev.04 or newer firmware''';
*'''Transport with CAN interface''';
*'''Transport's CAN communication protocol (with information about frames, parameters, ID's, baud rate)'''.

====Manual CAN I/O====
Up to 30 I/O parameters (Priority, Event Only, Operand, Send SMS To, SMS text) for '''Manual CAN''' functionality can be configured in CAN I/O tab.
{| class="wikitable" style="border-style: solid; border-width: 0px;"
|+
| style="width: auto; text-align: left; background: #F6F6FB;" |'''NOTE!'''
| style="width: auto; text-align: left; background: #F6F6FB;" |It is important to not forget that [[TFT100_Manual_CAN_settings|Manual CAN Settings]] tab '''must be configured''' as well.
|}
[[Image:Manual CAN IO.gif]] 

*<code>The '''AVL ID''' list of '''Manual CAN''' parameters can be found in [[Full_AVL_ID_List#Manual_CAN_I.2FO_elements|here]].</code> 
*<code>Full '''Manual CAN''' and '''Manual CAN Settings''' description can be found in [[TFT100_Manual_CAN_settings|here]].</code>
*<code>Example on '''how to configure Manual CAN''' functionality can be found in [[How_to_configure_Manual_CAN_I/O_parameters|here]].</code>

===Manual J1939===
<hr>
[[Image:Manual J1939.gif|right]]
'''Manual J1939''' protocol support was added to TFT100 device's firmware as an addition to '''Default J1939''' protocol in case the given '''Default J1939''' I/O elements are not enough. With this functionality, the user is able to configure which '''J1939''' parameters he would like to read from the transport that uses '''J1939''' protocol. '''Manual J1939''' protocol is enabled by selecting '''Manual J1939''' parameter in ''CAN Protocol'' field as shown in the image on the right hand side. Then user can configure CAN parameters in [[TFT100_Manual_CAN_settings|Manual CAN Settings]] tab.
{| class="wikitable" style="border-style: solid; border-width: 0px;"
|+
| style="width: auto; text-align: left; background: #F6F6FB;" |'''NOTE!'''
| style="width: auto; text-align: left; background: #F6F6FB;" |''Manual J1939'' can be tested on FW 55.00.09.rev.08 or newer
|}
To read data with this functionality, the user must have:

*'''TFT100 device with CAN interface''';
*'''55.00.09.Rev.08 or newer firmware''';
*'''Machinery with CAN interface, which communicates via J1939 protocol''';
*'''Machinery's J1939 protocol documentation (with required SPN's and PGN's)'''.

====Manual J1939 I/O====
Up to 29 I/O parameters (Priority, Event Only, Operand, Send SMS To, SMS text) for '''Manual J1939''' functionality can be configured in CAN I/O tab the same way as for '''Manual CAN''' functionality.
{| class="wikitable" style="border-style: solid; border-width: 0px;"
|+
| style="width: auto; text-align: left; background: #F6F6FB;" |'''NOTE!'''
| style="width: auto; text-align: left; background: #F6F6FB;" |It is important to not forget that [[TFT100_Manual_CAN_settings#Manual_CAN_Settings_.28For_Manual_J1939_functionality.29|Manual CAN Settings]] tab '''must be configured''' as well.
|}
[[Image:Manual J1939 29 IO.gif]] 

===FLEX===
<hr>
[[Image:FLEX.PNG|right]]
The FLEX protocol is enabled by selecting '''FLEX''' parameter in ''CAN Protocol'' field.

====FLEX I/O====
Specific FLEX I/O parameters were implemented to our device's firmware that can be read, configured and sent to the server just like regular I/O parameters.

*<code>The '''AVL ID''' list of '''FLEX''' parameters can be found in [[Full_AVL_ID_List#FLEX_I.2FO_elements|here]].</code> 

[[Image:FLEX CAN.gif]] 

===Debug===
{| style="width: 100%"
|[[File:Debug feature.png|right|260px]]
Debug Protocol is used to read all incoming message through CAN, it works as a CAN reader. By default it will print incoming messages into Terminal, including CAN ID and Data.
|}
{| style="width: 100%"
|[[File:Debug-can-log.png|right]]
When the DEBUG protocol is selected, CAN Log option will appear. 
By Enabling CAN Log parameter it will store CAN received data and CAN ID in a file.
|}
{| style="width: 100%"
|[[File:Debug-can-dump.png|right]]
To download saved file go to Status Tab and Maintenance section, press “Dump” button.
|}
{| style="width: 100%"
|[[File:Debug-can-opendir.png|right]]
After downloading, follow “Open directory” button. After unzipping file there will be CAN folder with “0.log” file. Maximum file size is 5MB. After exceeding limit it will rewrite data.
|}

==J1939 Settings==
{| style="width: 100%"
|[[Image:J1939 Settings.png|right]]
Some J1939 PGN’s are not sent periodically, so they must be requested. In order to request PGN device must be registered to J1939 network. To register device user should configure '''J1939 Source Address''' and '''J1939 Name''' parameters:
 

*'''J1939 Source Address''' parameter is used to set TFT source address on J1939 network. If device with selected source address already exists on network, user should change it to another address which might be free, or PGN’s which must be requested will not be received.
*'''J1939 Name''' parameter is used to set TFT name on J1939 network.
|}

==CAN I/O reset==
{| style="width: 100%"
|[[File:CAN_IO_reset.png|right]]
* This parameter is available only with FW 55.01.10.Rev.00 or newer 
If CAN IO reset parameter configured as 0 it will keep captured CAN data, otherwise if data is not received anymore it will reset I/Os after configured timeout.
|}
Possible values (in seconds): 
<code>0</code> - Data will not be cleaned. If external power is removed it will still keep the value. 
<code>1-3600</code> - Data will be cleaned within timeout period if no more data is received or external power removed.

{| class="wikitable" style="border-style: solid; border-width: 0px;"
|+
| style="width: auto; text-align: left; background: #F6F6FB;" |'''NOTE!'''
| style="width: auto; text-align: left; background: #F6F6FB;" |CAN IO resets in any case after device restart or CAN Protocol switching.
|}

[[Category:TFT100 Configuration]]

TFT100 CAN I/O settings - Revision history

Arijus.C at 06:44, 27 April 2026

Arijus.C at 06:40, 27 April 2026

Arijus.C: Updating per GTPGTM-11729

Arijus.C at 07:38, 24 March 2026

Justinas.strelciunas: /* CAN I/O reset */

Justinas.strelciunas: /* Separate I/O reset description */

Justinas.strelciunas: /* CAN I/O reset */

Ignas A.: /* CAN Protocol */

Martyna.D: Protected "TFT100 CAN I/O settings" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

Martyna.D: Created page with "__TOC__ ==CAN Protocol== 260px '''CAN I/O''' category offers users an ability to select one of CAN protocols to read specific data through TF..."

Martyna.D: Created page with "TOC ==CAN Protocol== 260px '''CAN I/O''' category offers users an ability to select one of CAN protocols to read specific data through TF..."