Protocol options
t0 - Timeout of Connection establishment(s) - Time in seconds to receive an attempt to establish a TCP IP connection by a client. After this time close the connection and reopen to wait. Values allowed between 1 and 255.
t1 - Timeout of send OR test APDUs(s) -Time in maximum seconds acceptable by the slave to send or test APDUs, after receiving confirmation of the SEND OF START DT. Values allowed between 1 and 255.
t2 - Timeout for ack in case of no data(s)- Time in maximum seconds of waiting for the Customer of the arrival of a new information message, after having arrived any, for the customer to send an "acknowledgment" message of the receipt of the last received message. Values allowed between 1 and 255. And t2 should be less than t1.
t3 - Timeout for sending test frames(s) - Time in maximum seconds of waiting for the arrival of some information message, and the TCP-IP connection is established. A TEST-FR message will then be sent. Values allowed between 1 and 255.
Max time to send analog changes (ms) - This time is set to the maximum wait for sending a message with changes in analog measures. If since you started the accumulation of measurements for the same message this time is exhausted before the arrival of the number of measures defined above, this module will send the message with the measures that have already arrived. This time per default is set at 3 seconds. If get analog changes by sampling mode are used ( see below), this is the time to be used as an interval between two samples.
Maximum Changes to send a message - To improve the performance of the communication module when sending changes to analog measures, you can set this number as the maximum of changes that must be accumulated to be sent in a single message, rather than sending a measure in each message. The number considered good is 30 measures, which is the default value. This accumulation is used when changes in measurements are received by the communication module, such as events. (AccessType with WriteEventEnable)
Password for commands: To increase security when sending commands, typically initiated only by a change in the state of a tag, you can specify in client modules a 9-digit password for the command. Here in this server module must be specified the password used by this Server module to generate the command for the Client module that will send the command. This password must be the same as that used by the Client module that is the recipient of the command.
Logging Level - You can choose from this list the way the log works created by the communication module.
Logging level | MESSAGES |
Debug | All messages are logged in the LOG. |
Info | Only Info, Warning, and Error messages are logged in the LOG. |
Warning | Only Warning and Error messages are logged in the LOG. |
Error | Only Error messages are logged in the LOG. |
Get analog changes by sample - Alternatively, to the way of receiving changes to tag values(by using AccessType with WriteEventEnable), you can choose the use of sampling mode, by the communication module, of changes that have occurred in tags. In this mode, the current values are checked periodically against the last values sent. In this way, the change is only considered, and the new value is sent to the client if the absolute difference between the current value and the last sent is greater than the Deadband attribute of the tag. For the use of this mode, you must use the AccessType in table Points, for these measurement tags, with WriteEventEnable disabled. The time interval between every two checks will be the one defined in the parameter above, Max time to send analog changes (ms).
| Note |
|---|
The communication modules servers, need for their correct functioning periodic calls, even to allow them the control of time. If there is no continuous stream of calls its operation will be impaired. Thus, if the call is not used by WriteEventEnable, or if a periodic call is not guaranteed, you must create a dummy tag, and script to change it periodically, and place it with a point with AccesType that triggers a call trigger to the driver. |
Set all quality good on start - Server communication modules normally do not change the state or quality of tags. Its only function is to read these attributes and send them through protocol messages to the recipient of the communication. Even so, in certain cases it may be necessary, at the beginning of the module execution, to put all the qualities with GOOD value, If this is necessary, you can choose ENABLED in this option.
Bias time from GMT - This server module uses the standard IEC 104 timestamp, that is, in all ASDUs that include timestamp it will be sent in GMT time. If you want the timestamp corrected for local time, enter the local time zone in this field. Example: To use Brasilia-Brasil local time use -3.
Settings
Listening Port – Port number used to listen for connection. The use of port 2404 is standardized. In this implementation, other port numbers can be used by changing the default. You can also inform the IP address of the adapter on which this module should wait for the connection. Just include this address before the port number, separated by a colon: Ex 192.168.0.222:2404
NodeConnections: Defines the maximum number of parallel requests that will be sent to each node (asynchronous communication)
| Panelscroll-ignore | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
On this page: |