Configuration

The point table in Action.NET must contain the correspondence between the point names (tags) in Action.NET and the names of the IEC61850 data objects in the remote IEDs, which are the source of the information, or which are remote-controlled objectives.
The address format of the point in Action.NET is separated by two points and necessarily composed of the Type and Address fields. However, some point types have additional fields after the address.

Types

The point type was created for registration purposes in order to organize, group, and categorize the addresses of IEC 61850.
Points with write access are updated when the tag changes the value. Points with reading access are read according to the read request period defined in the node configuration. Some types are more complex are explained in the subsections (4.1.x).

Binary output (BO)

Binary output (BO) type has additional field Command Parameter. This field is used to set a fixed value to be sent per command when the digital tag associated with the value swap point. Below is an example of use.

Associating the Tag (BREAKER_OFF) with a button "OPEN" and Tag (BREAKER_ON) "CLOSE" with action of ToggleValue. By switching the tag value from 0 to 1 or from 1 to 0. A command will be generated by passing the fixed value set in the address..

DataSet (DS) (DS1) (DS2) (DS3) (DS4)

A DataSet is an object that contains a list of Data Objects names. DataSets are typically preconfigured on the server IEDs. The contents (state, measure, timestamp, quality) of a DataSet's Data Object can be obtained in two ways:

• By requesting a reading of the DataSet, referencing its name. You must have a DataSet point configured in the points table, and the points for each Data Object of interest are available;

• By activating a Report that points to this Dataset, causing unsolicited submission of this content (which is described in the next item: Reports.)

DataSet points are configured for polling reading and are configured with type DS. Types DS1, DS2, DS3, and DS4 exist if you want to set different read time for each dataset point group.

Report (BR) (PR)

For each Report configured on the server, which you want to enable to be Action.NET, you must include an entry in the points table. This real-time point will contain the current state of the Report (0 - Off, 1 - On). The information of activated or not, is extracted from the reading of the current state of the attribute Rptena of the Report. The sampling period for this reading is defined by parameter Report polling, in NODES configuration.
The attributes Optflds and Trgops have the default values:

• Optflds = SEQ_NUM, TIME_STAMP, REASON_FOR_INCLUSION, DATA_SET, DATA_REFERENCE, ENTRY_ID and CONF_REV

• Trgops = DATA_CHANGED and GI

These fields can be customized to receive other values for each Report. This is possible by using a browser window function described in the session 5.7

Report Flags (BRF) (RPF)

Some attribute points of the Report must be registered for monitoring and control.

You must create tags to receive this data and register it in the Points table, with addresses that are the same address as the Report, plus $ and the attribute name. The figure shows an example of this registration:

Open

Address

Addresses generally follow the IEC 61850 format:

LogicalDevice/LogicalNode$FunctionalConstraint$DataObject$DataAttribute
For each Date Object you must create a point in the points table. However, there are cases of Data Objects such as Current, Three-Phase Voltage and etc. measurements. In these there is more than one hierarchical level of Data Attributes below you. The Communication Module knows some structures and automatically obtains each of the phases, but it is necessary to specify each of them in the point table (in this case, each of the Data Attributes at the first hierarchical level below of The Data Object must be a point in the points table).
Points where the Communication Module cannot identify what value to fetch in a given structure. Errors will be found at startup. This deficiency can be corrected by improving the knowledge of the Communication Module in relation to the structures or the address can be registered specifying the attribute that will be the value. The quality and time of these attributes will be read from the structure to which it belongs.
Example of address registered to the structure:
IED7SJ63MEAS/MMXU1$MX$PhV$phsA

• Ignore => IED7SJ63MEAS/MMXU1$MX$PhV$phsA$instCVal$mag$f

• Value => IED7SJ63MEAS/MMXU1$MX$PhV$phsA$cVal$mag$f

• Quality => IED7SJ63MEAS/MMXU1$MX$PhV$phsA$q

• Time => IED7SJ63MEAS/MMXU1$MX$PhV$phsA$t

Example of address registered up to the attribute:
IED7SJ63MEAS/MMXU1$MX$PhV$phsA$cVal$mag$f

• Value => IED7SJ63MEAS/MMXU1$MX$PhV$phsA$cVal$mag$f

• Quality => IED7SJ63MEAS/MMXU1$MX$PhV$phsA$q

• Time => IED7SJ63MEAS/MMXU1$MX$PhV$phsA$t

Access Type

Two types of access (Access Type) reading (Read) and writing (Write) must be created, configured, and associated with each point.

Reading

Write