Each node is a server station (IED). For serial communication you can configure multiple stations for the same channel. In the case of TCP-IP communication only one node is supported for each channel. In this case, as many channels as the nodes should be configured.

Channel Data (primary and backup)

Set of attributes associated with the node (channel), referring to its address and other attributes presented below:

Figure 6 - Channel Data
In case of communication via Tcp-Ip:
IP address - Enter the Ip address of the server IED.
Port - Enter the server port number on which the IED must connect to the communication.
Note: In the case of serial communication these first two fields do not exist
For any case:
SlaveID - IED server address (slave mode) at the application layer.
IgnoreBitOnLine - If "enabled" indicates that the driver should ignore the indication of "BitOnLine" that is inserted by the IED when failure or normality occurs at a point, according to the IED criterion.
WaitForIdleToCmd - If "enabled" indicates that a command will only be sent when the sampling communication is at rest, that is, it is not occurring.
AI sample time(ms) - Time in milliseconds between two consecutive orders, requesting submission of the current values of analog points. (request for type 30 objects, all variations).
BI sample time(ms) - Time in milliseconds between two consecutive requests, requesting sending the current states of the digital dots. (request for type 1 objects, all variations).
Class 0 sample time(ms) - Time in milliseconds between two consecutive orders, requesting submission of the current values of all points.
Class 1 sample time(ms) - Time in milliseconds between two consecutive orders requesting submission of changes that occurred at the points defined in the specific class 1.
Class 2 sample time (ms) - Time in milliseconds between two consecutive orders requesting submission of changes that occurred at the points defined in the specific class 2.
Class 3 sample time (ms) - Time in milliseconds between two consecutive orders requesting submission of changes that occurred at the points defined in the specific class 3.
Counters sample time(ms) - Time in milliseconds between two consecutive orders, requesting submission of the current counter values. (request for type 21 objects, all variations).
Time-Date sample time (ms) - Time in milliseconds between two consecutive synchronization submissions, i.e. sending the current date and time to the IED (object 50), The time is sent only in GMT.
BI Event sample time(ms) - Time in milliseconds between two consecutive requests, requesting submission of the current EVENTS of the digital points. (request for type 2 objects, all variations).
BO sample time(ms) - Time in milliseconds between two consecutive orders, requesting submission of the current states of binary outputs points. (Request for Type 10 Objects, all variations).
AO sample time(ms) - Time in milliseconds between two consecutive orders, requesting submission of the current values of analog outputs points. (request for type 40 objects, all variations).
AI Event sample time(ms) - Time in milliseconds between two consecutive orders, requesting submission of the current values of analog events points. (request for type 32 objects, all variations).
Frozen Counter sample time(ms) - Time in milliseconds between two consecutive orders, requesting submission of the current values of frozen counters. (request for type 23 objects, all variations).
Counter Event sample time(ms) - Time in milliseconds between two consecutive requests, requesting submission of current counter events. (request for type 22 objects, all variations).
DBI sample time(ms) - Time in milliseconds between two consecutive requests, requesting submission of the current states of the double digital dots. (Request for Objects type 03, all variations).
DBI Event sample time(ms) - Time in milliseconds between two consecutive requests, requesting submission of the current EVENTS of the double digital points. (Request for Objects type 04, all variations).
Request Link Status sample time(ms) - Time in milliseconds between two consecutive requests, requesting the current state of the link (link status). In the trace these submissions and response receipts appear as "KeepAlive Initiate" and "KeepAlive response success" or "KeepAlive Failure.", the latter in case of failure to get the response to the request.
Tag for Comm status - In this field, the name of an existing tag in the project can be indicated to receive indication of success/failure in communication, from a functional point of view. When requests are made, the module waits for a maximum of Timeout milliseconds (defined in Protocol Options, above) for receiving a response. In case of failure the value of this tag will be placed at ZERO. In the event of success the value will be placed in UM.
Enable Unsolicited sample time(ms) - Time in milliseconds between two consecutive submissions, from request to unsolicited send enablement (function 22), to classes 1, 2, and 3.
Backup Station - The same settings made for the main station can be made for an alternative backup IED station, with identical point configuration, if it exists in the installation.