Is mandatory for an Edition 2 IED to subscribe to FCDs in a GOOSE? I can´t find this is the Standard (that´s why I entered this tissue in General category).
But reading the PIXIT, Gs7 only applies to Edition 1 (May the GOOSE data set contain structured data objects (FCD). So I understand that for an Edition 2 IED you can´t answer NO.
Gs8 applies to Edition 2 (Subscribed FCD supported common data classes are...). If the answer to this Gs8 can be NONE, then it is clear that it is not mandatory to subscribe to FCDs, but if you have to list at least one CDC, then it is mandatory.
Thanks in advance.
Proposal
Discussion
Created
Status
Even if a subscriber does not support / use / understand a CDC (or a base type), it shall be able to skip the data of this CDC / base type inside a GOOSE message. As it does not support it, it should not be assigned to its internal inputs. Due to the ASN.1 notation (or using fixedOffset GOOSE) the receiver stack can skip this value.
31 May 16
Not Applicable
OK. Let´s take your sentence: otherwise GOOSE parameterization is not possible / interoperable having Publisher that can publish only FCDA and subscriber that can subscribed FCD. Imagine that this subscriber does not support all CDCs as subscriber and publisher needs to send a CDC not supported by the subscriber. Interoperability will be impossible in this case and FCDA will have to be used, so subscribing to FCDA is obviously mandatory. Why is it necessary to state subscription to FCDs as mandatory?
Subscription to FCDAs is obviously necessary (GOOSE will be composed by status or status+quality in a very high percentage of the real cases). If subscription to FCD is mandatory, then all CDCs should be implemented by the subscriber and Gs8 of the PIXIT should be keeped for Ed1 devices to ensure absolute interoperability.
26 May 16
Not Applicable
7-2 specifies GOOSE (18.1) as:
"The generic substation event model applies to the exchange of values of a collection of DataAttribute respective FCD / FCDA."
Therefore
- publisher shall be prepared to publish both FCD or FCDA (as soon as the dataset is configurable by the SCT).
- subscriber shall be prepared to subscribe both FCD or FCDA (based on the configuration),
otherwise GOOSE parameterization is not possible / interoperable having Publisher that can publish only FCDA and subscriber that can subscribed FCD.
Figure 35 also illustrate that both FCD or FCDA can be published.
18.2.1.5 DatSet - specifies that the MemberReference can be both FCD or FCDA.
As the Ed1 test procedures did not explicitly test the subscription of FCD ( which were already a prerequisite for interoperability in Ed1), the WG10 decided to mandate the test with Ed2 (also as a result of interop problem during the 2013 Interop Test).