General

Each node (node) is used to maintain communication with a server station (IED). You can configure several server stations for each channel.

TCP-IP Communication

• IP address – the Ip address of the IED must be specified.

• Port - Port number used for the connection. The use of the door is standardized 2404. In this implementation, you can use other port numbers

Primary Station

• Common Address - Is the IED address in the application layer

• Date sample time – The period in milliseconds between two consecutive Date and Time submissions for IED synchronization, if necessary. The sent object, with the local time of this computer, is the C_CS_NA_1(103) - Timing, with a 56-bit time tag. The Value Zero is used to indicate that there is no need for synchronization. Note that GPS-synchronized IEDs should not be synchronized by the master.

• General Interrogation (GI) sample time – The period in milliseconds between two consecutive request submissions General question C_IC_NA_1 (100), to the FDI. The IED responds by sending as many blocks of information as it takes to send all existing points.

• w - Send ack after received w IFormat APDUs - Number of information messages received spontaneously, after which the client should send an "acknowledgment" message with the sequence number of the last received message. Values between 1 and 32767.

• k - Messages received to send state variable - Maximum number of messages sent by the server still does not "acknowledge" After this number of messages received without the server receiving the "acknowledgment", it should stop sending messages, waiting for the "ack". It is recommended that w be a maximum of two-thirds of the value of k. Values between 1 and 32767.

• Clock Adjust - It can be chosen "True", to adjust the clock of this server computer or "false" to not adjust. Tuning will be done by changing the machine time to what came as a response to a timing send a message. To be effective it is necessary that the IED slave respond so responds with a time that comes for example from a GPS.

• IED time bias from GMT - However Action.NET, internally, all timestamps are stored with dates in GMT (UTC). Normally IEDs send these dates also in GMT, and no correction is made. The default for this option is Zero. If in the current deployment the IEDs send the timestamps in their local time, you must specify here the difference between this time and GMT. For example, in Brasilia, the local time is 3 hours less than GMT. For this case should be specified -3 in this table.

• Tag for Comm status - In this field, the name of an existing tag in the project can be indicated to receive an indication of success/failure in communication, from a functional point of view. When requests are made, the module waits for a maximum of T2 seconds (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.
  The figure below shows the completion of these fields for the main station.

• Test Command with time tag56 (ms) - The period in milliseconds between two consecutive shipments of an object of Test with a timestamp - C_TS_NA_1 (104). This submission is used, in certain cases, to maintain some activity on the channel, as well as to test whether the server on the other side of the communication is active.

• Counters Interrogation sample time (ms) - The period in milliseconds between two consecutive request submissions Accountant Squestionmation C_CI_NA_1 (101) to the FDI. The IED responds by sending as many blocks of information as it takes to send all existing points and counters.

Backup Station

The same settings made for the main station can be made for an IED backup station (alternative) defined for this same node if it exists in the installation.