Feature #592
Invalid SCL file due to wrong allocation fo GoCBs
Added by Herbert Falk over 3 years ago.
Updated over 2 years ago.
Category:
Implementation - improve conformance testing
TF Unique ID:
IntApp # IOP_2019
WG10 Proposal:
Tissue #1445 ed2 and 61850-6 ed2.1 table 11 states that if GSE configuration is not fixed, SCT can add or delete GoCB in any LLN0. It has to be tested. Bruce to guarantee is going to be tested in conformance testing.Bruce answers: "New test procedure regarding the issue.Verify that GSEControl can be added to any LN0Add one GSEControl to first and last LN0 in the configuration of the deviceCondition: Services/GSESettings attribute cbName is not “fix” or absent and multiple Logical Devices exist and GOOSE max > 1"
Discuss in Upcoming Meeting:
No
Short Proposal:
It appears that the device allows GoCB but only in some LD. No way to express this in SCL currently.
Description
IED in the SCD contains access points (S1 and others) with GSE with ldInst = “Prot” and a single GoCB.
However, the GoCBs are instantiated only in the ldInst=”Master” and no MAC-Address is provided for GSE where ldInst=”Master”.
The Access Points should refer to “Master” not “Prot” for the GSE
The posted IID file for this device has IED name = TEMPLATE and no GoCBs in any LDs
While this is apparently a “simple” implementation error, not validating SCD files is causing numerous problems for some participants.
- Subject changed from IED in the SCD contains access points (S1 and others) with GSE with ldInst = “Prot” and a single GoCB.
However, the GoCBs are i to Invalid SCL file due to wrong allocation fo GoCBs
- Status changed from New to In Progress
- WG10 Proposal changed from Tissue #1445 ed2 and 61850-6 ed2.1 table 11 states that if GSE configuration is not fixed, SCT can add or delete GoCB in any LLN0. It has to be tested. Bruce to guarantee is going to be tested in conformance testing.
Bruce answers: "New test procedure regarding the issue.
Verify that GSEControl can be added to any LN0
Add one GSEControl to first and last LN0 in the configuration of the device
Condition: Services/GSESettings attribute cbName is not “fix” or absent and multiple Logical Devices exist and GOOSE max > 1" to Tissue #1445 ed2 and 61850-6 ed2.1 table 11 states that if GSE configuration is not fixed, SCT can add or delete GoCB in any LLN0. It has to be tested. Bruce to guarantee is going to be tested in conformance testing.Bruce answers: "New test procedure regarding the issue.Verify that GSEControl can be added to any LN0Add one GSEControl to first and last LN0 in the configuration of the deviceCondition: Services/GSESettings attribute cbName is not “fix” or absent and multiple Logical Devices exist and GOOSE max > 1"
- Discuss in Upcoming Meeting set to No
- Status changed from In Progress to Closed
Confirm to IEC 61850-6 editor the issue has been accounted for
Also available in: Atom
PDF