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'.
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
blue
Link Tissues
Enter the Tissue IDs for which a link will be posted (i.g.: 34, 573 adds two links):
View All Issues for Part 8-1 (2004)