Feature #598
The SCT tool creates an invalid ReportControl element
Added by Herbert Falk over 3 years ago.
Updated about 2 years ago.
Category:
Standard extension required
TF Unique ID:
2108 # IOP_2019
WG10 Proposal:
There were more investigations done on the issue: The problem was, that the IED intended to have association specific control blocks. Association specific control blocks can not be buffered so we assume for the remaining discussion, that the issue is with unbuffered control blocks.For reports with indexed=false, max > 1 indicates the number of clients that can reserve the report; as they all have the same rcb name and hence it is association specific.Client LNs may be added to indicate to the client that he shall use that control block. There shall not be more ClientLNs added than maxTISSUE for part 6 – have a table representation of the use cases as TISSUE resolution.Feb-20: CBL:TISSUE for part 6 – have a table representation of the use cases as TISSUE resolution.
Estimated Completion:
20-Oct
Discuss in Upcoming Meeting:
No
Description
The SCT tool created an invalid ReportControl element.
<ReportControl desc="Created by HELINKS STS" datSet="ds_rcb1" name="rcb2" intgPd="0"
buffered="true" bufTime="100" confRev="10000" indexed="false"
rptID="INCB_BCUCFG/LLN0.rcb2">
<TrgOps dchg="true" dupd="false" gi="true" period="false" qchg="true"/>
<OptFields bufOvfl="true" configRef="true" dataRef="false" dataSet="true" entryID="false"
reasonCode="false" seqNum="true" timeStamp="true"/>
<RptEnabled max="7">
</RptEnabled>
</ReportControl>
Per the standard, a buffered report is limited to one instance.
- Subject changed from The SCT tool created an invalid ReportControl element.
<ReportControl desc="Created by HELINKS STS" datSet="ds_rcb1" name="rcb2 to The SCT tool creates an invalid ReportControl element
- Status changed from New to In Progress
- Standard(s) changed from 6 to IEC 61850-6
- WG10 Proposal changed from There were more investigations done on the issue: The problem was, that the IED intended to have association specific control blocks. Association specific control blocks can not be buffered so we assume for the remaining discussion, that the issue is with unbuffered control blocks.
For reports with indexed=false, max > 1 indicates the number of clients that can reserve the report; as they all have the same rcb name and hence it is association specific.
Client LNs may be added to indicate to the client that he shall use that control block. There shall not be more ClientLNs added than max
TISSUE for part 6 – have a table representation of the use cases as TISSUE resolution.
Feb-20: CBL:TISSUE for part 6 – have a table representation of the use cases as TISSUE resolution. to There were more investigations done on the issue: The problem was, that the IED intended to have association specific control blocks. Association specific control blocks can not be buffered so we assume for the remaining discussion, that the issue is with unbuffered control blocks.For reports with indexed=false, max > 1 indicates the number of clients that can reserve the report; as they all have the same rcb name and hence it is association specific.Client LNs may be added to indicate to the client that he shall use that control block. There shall not be more ClientLNs added than maxTISSUE for part 6 – have a table representation of the use cases as TISSUE resolution.Feb-20: CBL:TISSUE for part 6 – have a table representation of the use cases as TISSUE resolution.
- Discuss in Upcoming Meeting set to No
- Discuss in Upcoming Meeting changed from No to Yes
- Status changed from In Progress to Closed
- Discuss in Upcoming Meeting changed from Yes to No
- To discuss in WG10 set to No
Related TISSUE created - #1695.
Also available in: Atom
PDF