Channel configuration

Protocol options

t0 - Timeout of Connection establishment(s) – When a TCP IP disconnection or command response failure occurs, a reconnection attempt is promptly made, always by sending a Start-DT message. If there is no success, new attempts will be made after this time t0 has elapsed. This parameter is time in seconds, allowed values between 1 and 255.

t1 - Timeout of send or test APDUs(s) - Maximum acceptable time in seconds for receiving a response from the server, based on any request from the client. If this response does not come within this time, it will be considered a communication failure and the TCP IP connection will be forced to close. A new reconnection attempt will then be made, respecting what is described in parameter t0. This parameter is time in seconds, allowed values between 1 and 255.

t2 - Timeout for ack in case of no data(s) - Maximum time in seconds to wait for the arrival of a new, unsolicited information message, after some , to send an "acknowledgment" message upon receipt of the last message received. A message will be sent with the sequence number of the last one received. Time in seconds, allowed values between 1 and 255. And t2 must be less than t1.

t3 - Timeout for sending test frames(s) - Maximum time in seconds to wait for any information message to arrive, once the TCP-IP connection is established. A TEST-FR message will then be sent. Allowed values between 1 and 255.

Password for commands: To increase security when sending commands, typically initiated only by a change in the state of a tag, you can specify here a password of up to 9 digits, which will be checked by the communication module against the current value, at the time of receipt of the command, with the attribute EstimatedValue of the tag involved in the command. So in the command send operation by a window, script, etc. this number should be loaded into this attribute. The communication module, after executing the command, passes to ZERO the value of the Estimated Value. Leaving this option with zero, the check will not be done.
Logging Level - You can choose from this list the way the log works created by the communication module.

The figure below shows the completion of these fields in the channel:

Open

Maximum Changes per minute - This parameter is part of the real-time verification functionality of many changes suffered by digital input points. Here you can inform the maximum number of alterations of a BI or DI point, which is considered reasonable before blocking the point or node to which it belongs. The functionality is defined at the Channel level but applies to all Nodes in the channel. Setting it to ZERO disables the functionality, other values will be used as the maximum acceptable variations per minute. See the next item to define what will be done if the maximum is reached.

Unactivate Node if Tag maximum changes - If YES is chosen, when at least one point reaches the maximum number of changes, the entire Node will be Inactivated. This is will stop communicating with Action.NET. If NO is chosen, only the point that has exceeded the number of changes will have its Locked attribute equal to 1, and will no longer suffer any changes until an operator manually changes this attribute to Zero. In any of these cases, a message in the Operation summary will be generated to inform of what happened.

Time to reactivate node (minutes) - Time in minutes that can be specified for the communication module to activate the Node again, after being deactivated. Zero indicates that there is no automatic reactivation.

Quality changes timestamp – Marking this option as "Enabled", means that when a new reading of an object is received, with flag, even if there is no change in the status (or value) of the tag, but there is a change in quality, a change is made of the tag's current timestamp.

Settings

TCP/IP channels:

• NodeConnections: Defines the maximum number of parallel requests that will be sent to each node (asynchronous communication)