Issues #6886
Tissue 1897 Data-change and data-update inclusion bitstring bits set in a report
Added by IEC 61850 TPWG 7 months ago.
Updated 2 days ago.
Discuss in Upcoming Meeting:
No
Test Case ID:
sMdl18, sRp3/sBr3
Closed Reason:
No Action Taken
Description
append sentence in 6.3.3.3 and 6.3.3.4
"'data-change' and 'data-update' are mutually exclusive of each other"
with
"for each particular data attribute as specified in Table 5."
As stated in IEC 61850-7-3 Clause 7-1: Sometimes, both dchg and dupd are specified as a possible trigger option for the DataAttribute. In that case, the concrete implementation shall select one of them
- Due date set to 10/01/2024
- Status changed from New to In Progress
- Assignee set to Richard Schimmel
- Due date changed from 10/01/2024 to 10/29/2024
- Test Case ID set to sMdl18, sRp3/sBr3
sRp3/sBr3 already states in the expected result: "the reason code is one of the configured trigger options". This will prohibit dupd+dchg!
sMdl18 states that in the SCL the DA: "is conformant with 61850-7-3 Trigger option". That may be clarified.
- Due date changed from 10/29/2024 to 11/12/2024
- Status changed from In Progress to Resolved
Is sMdl18 verifying that only dchg="true" or dupd="true" are mutually exclusiv in the (DataTypeTemplate) DA declaration?
- Due date changed from 11/12/2024 to 12/10/2024
- Status changed from Resolved to In Progress
sMdl18 also checks the TrgOps in the SCL file do match with those in the NSD. If the NSD does not allow dupd than the SCL will fail. For sure dchg and dupd are mutually exclusive. This should in principle prevent a report with reason-code "dupd" and "dchg" for the same element. The tissue is about a report, not the SCL.
- Due date changed from 12/10/2024 to 02/04/2025
Waiting for TISSUE resolution.
BCR can have both dchg and dupd in some rare cases.
- Due date changed from 02/04/2025 to 03/04/2025
- Due date changed from 03/04/2025 to 04/01/2025
sMdl18 requires each attribute in the SCL has one trigger condition => no need to change
sRp3/sBr3 verifies the following trigger conditions:
- on integrity
- on update (dupd)
- on data-change
- on data-change and quality-change
- on data-change, quality-change and integrity with a valid integrity period
The special case of BCR that may have an attribute with dupd and another attribute with dchg, may result in a report with both reason codes. But that will never happen in sRp3/sBr3 because the trigger condition combination dupd and dchg is not tested!
I see no reason to change the existing test procedures.
- Status changed from In Progress to Closed
- Closed Reason No Action Taken added
- Closed Reason deleted (
--Not Set---)
No change to test procedures per Richard's explanation.
Also available in: Atom
PDF