Device Driver: TSAP
The TSAP driver is configured similarly to the TCP/IP driver, with additional parameters TSAP. TSAP messages have specific headers automatically managed by Sym3 using the TSAPServerName and TSAPClientName parameters. The Sym3 header and body are encapsulated inside the TSAP message body.
Configuration
The configuration options available are:
Name | Type | Description | |
---|---|---|---|
Server | Boolean | Flag to indicate whether this is a server or client. | |
IPAddress | IP address/host name | Server IP address or name. Valid for client only. | |
Port | port number | port number Indicates the port to listen on, or connect to. | |
ReconnectTime | Unsigned Integer | Default = 5 seconds Time between client reconnection attempts (seconds). Valid for client only. |
|
NetworkByteOrder | Boolean | Default = False Identifies the endian order of the message header numeric values. The device IO contents are treated as single bytes therefore not swapped. |
|
TSAPServerName | String | Name of the TSAP server. (must match the server name configured on the PLC side) | |
TSAPClientName | String | (ignored if Server = True) Name of the TSAP client. (must match the server name configured on the PLC side) | |
Autoconnect | Boolean | (optional true if not specified). Default = True If false, Sym3 won’t connect to this device until an explicit call to ConnectDevice() is made from the script. |
Examples
Server Example
To configure Sym3 as the server
server = true
port = 16000
TSAPServerName = Sym3
Client Example
To configure Sym3 as the client a TSAP Server named “PLC1”
server = False
ipaddress = 192.168.25.56
port = 16000
reconnecttime = 10
NetworkByteOrder = false
TSAPServerName = PLC1
TSAPClientName = Sym3
NOTE: Configuration data is not case sensitive and white space is ignored.