Block

Mask

Description

The OpIEC61850 GOOSE Subscriber block basically behaves as a reception unit of Generic Object Oriented Substation Event (GOOSE) messages (command, control or status). OpIEC61850 GOOSE Subscriber block gets all the necessary information to monitor a specific GOOSE message from SCL file. In order to subscribe to a GOOSE message, its Multi-cast address of publication, as well as its identifier (AppId), are used to produce control signals corresponding to the GOOSE message received through the IEC 61850 network.

This block adjusts automatically its outputs depending on the number of Data Objects (DOs) comprised within the selected GOOSE message.

Parameters

Inputs

Enable (En): This input controls the reception of GOOSE messages. An input of 1 activates reception and value of 0 disables it.

Outputs

Status: This output is a 3-element vector which is organized in the following manner:

Object Data: This output is dynamically created depending on the structure of the GOOSE message; the number of object data outputs and their size (number of vector elements) added to the Simulink block shall depend on the DataSet associated to GSEControl block in selected SCL file, i.e.

If GSEControl uses a DataSet named "Goose_TRIP5",

<GSEControl ... datSet="Goose_TRIP5" name="CB_Goose_TRIP5"/>Note1

and this DataSet consists of two object definitions "Op5" and "Op6" with two attributes each (intA and intB),

<DataSet name="Goose_TRIP5">
<FCDA ... doName="Op5" daName="intA" fc="ST"/>
<FCDA ... doName="Op5" daName="intB" fc="ST"/>
<FCDA ... doName="Op6" daName="intA" fc="ST"/>
<FCDA ... doName="Op6" daName="intB" fc="ST"/>
</DataSet>Note1

so the Simulink block shall look like this:

Figure 1 shows the two additional object data outputs added to the block which are represented by a 2-element vector. The order of object outputs and their attributes is the same order followed in DataSet definition, this can be exemplified as follows:

1st Object Output -> Op5 = [intA intB]

2nd Object Ouput -> Op6 = [intA intB]

The labels on each output of the form OpN[...] meansthat output OpN might contain just a partial number of attributes containedwithin the object, or all of them, since the data set was built using severalFCDA elements is it not possible to know if all attributes are present in<DataSet element.

On the other hand, if we have a <DataSet definition as follows:

<DataSet name="Goose_TRIP5">
<FCDA ... doName="Op5" fc="ST"/>
<FCDA ... doName="Op6" fc="ST"/>
</DataSet>Note1

so the Simulink block shall look like this:

Figure 2 shows the two additional object data outputs added to the block which are represented by a 2-element vector. The order of object outputs and their attributes is the same order followed in DataSet definition, this can be exemplified as follows:

1st Object Input -> Op5 = [intA intB]

2nd Object Input -> Op6 = [intA intB]

The labels on each output of the form OpN.All meanthat all attributes of object OpN respecting the constraint "fc" are present at the Simulink blockoutput.

Characteristics and Limitations

When selecting a new SCL file, for Matlab versions prior to 2009B, GoID pop-up menu is automatically updated when pressing "Apply" button on block's mask. Specifically for Matlab v2009B, it is necessary to close the mask by pressing OK button to get updated this pop-up menu.

Consider the following scenario: There are two or more OpIEC61850 GOOSE Subscriber blocks within the same Simulink model pointing to different SCL files and same IED. This scenario is NOT supported if any GOOSE message definition within IED is different across files; therefore the last block to be updated shall be the one to determine which GOOSE message definition shall be taken for all blocks falling into this case.

For structure types the user cannot access specific members, only the entire contents of the structure can be applied to Simulink output.

The following table shows which of the IEC61850 pre-defined basic types are supported (per standard 61850-6 © IEC:2009(E)).