IEC 61850 Tissue Database

Every status a technical issue can be in, and the steps the workflow allows between them. The status this tissue is in now is the box drawn in bold.

Hide the workflow

TissueDB status workflow back to Discussion Batch Triage Accepted Discussion Drafting Implementation Verify Draft Implementation Analysis Of Compatibility Conformance Test Preparation Conformance Test Verification Ballot Period Solution Accepted Must Implement In Force Approval (N/A) Approval (Duplicate) Approval (Editorial) Approval (Future Improvement) Not Applicable Duplicate Future Improvement Editorial Must Implement (Editorial) In Force (Editorial) Legend normal route of a technical solution accepted or released → in force classification branch (working group approval) back to Discussion for rework (lines are bundled) reaching the final state
The route a technical solution takes from Triage to In Force, the working group approvals that close an issue instead, and the ways back to Discussion for rework. Opens full size in a new tab.

131 GxCB in directory and SCL

Created
21 Mar 2005
Status
Not ApplicableClosed: the issue falls outside the scope of the standard. No further comments are taken. Hide the workflow
Part
Part 8-1 (2004)
Links
None
Page
Clause
Paragraph
Table 109/110
Category
No impact on this part

Issue

According to the standard it is allowed to have a GxCB defined in SCL that is not visible in the object directory (8-1, table 109/110, GxCB is optional). Is it allowed to have this GxCB at a different place in the object directory?
Or in principle, it is allowed to have a Goose Controlblock available in the object directory which is not defined in SCL ?

For example, in SCL it is defined that a GoCB would be at 'Ldevice1/Lnode1$FC$GO$MyGC', but the GoCB is revealed with another reference, like 'Ldevice2/Lnode2$FC$GO$RevealedGC'.

Proposal

Clarify.

DiscussionCreated
Not Applicable Q1: According to the standard it is allowed to have a GxCB defined in SCL that is not visible in the object directory (8-1, table 109/110, GxCB is optional). Is it allowed to have this GxCB at a different place in the object directory?

61850-7-2/-6 only allow GxCBs in the scope of LLN0. Therefore, only GxCB(s) in the scope LLN0 can be tested for conformance.

The schema in -6 does not allow GxCB(s)to be defined in any place but LLN0. Thus any GxCB defined in SCL with an MMS profile implementation must be visible within LLN0.


Q2: Or in principle, it is allowed to have a Goose Controlblock available in the object directory which is not defined in SCL ?

In certain cases it is possible to have a GxCB that is not defined in SCL. The specifics will need to be defined later.

Q3: For example, in SCL it is defined that a GoCB would be at 'Ldevice1/Lnode1$FC$GO$MyGC', but the GoCB is revealed with another reference, like 'Ldevice2/Lnode2$FC$GO$RevealedGC'.

This can’t exist since the GCRef would be different for each GOOSE issued. It is not possible to have a single GOOSE message bound to two GCRefs.
31 Mar 05