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.

128 Add DstAddr to GsCB, SV

Created
16 Mar 2005
Status
In Force (green)Closed: the solution is part of the standard. No further comments are taken. Hide the workflow
Part
Part 8-1 (2004)
Links
None
Page
Clause
18, 19
Paragraph
Category
No impact on this part

Issue

See also: #53 (IEC 61850-7-2)
Within the current scheme of 61850, the GSE and SMV control blocks do not contain the destination (multicast) MAC address, while the Goose control blocks do. This means that the only way of finding out the group addresses for GSE and SMV are through SCL. This is fine if everything is configured correctly, but does not allow for the validation of the configuration, and will make diagnostics needlessly difficult. If we made the addresses visible in MMS, life will be much simpler for utilities.

Proposal

Add the group addresses for GSE and SMV.

DiscussionCreated
In Force (green) Ballot date expired 19 Aug 05
Ballot Period 8-1 will add a DstAddress element to the GSCB per Table 51 of IEC 61850-8-1. The element will be mandatory "r". The VLAN information in the 8-1 datatype shall be ignored for the case of GSCB.

The SVCB is not an 8-1 issue. However, the DstAddress type will be added to 9-2 and this will be reflected into 9-2.
31 Mar 05