Project

General

Profile

Issues #6208

sSvsN2 in TP1.2 does not check the situation where the DUT checks ConfRev

Added by Hua Qin over 1 year ago. Updated about 1 year ago.

Status:
Rejected
Priority:
Normal
Due date:
03/07/2023 (about 14 months late)
Discuss in Upcoming Meeting:
No
Clause Reference:
61850 Standard:
Triggering Tissue:
Final Decision:
Initial Test Document:
Updated Test Document:
Test Case ID:
Closed Reason:
--Not Set---
Triggering Tissue 2:
Triggering Tissue 3:

Description

Step 2 and 3 works for the DUT which does not check ConfRev.
For DUT checks ConfRev, it discards the SV after checking ConfRev version and may not really check the elements in the dataset.

It is suggested to add extra two steps:
4. SIMULATOR publishes SV stream with same ConfRev, with an extra dataset element parir at the end
5. SIMULATOR publishes SV stream with same ConfRev, with missing last dataset element pair


Files

Solution to redmine 6208 sSvsN2.docx Solution to redmine 6208 sSvsN2.docx 21.4 KB Richard Schimmel, 02/21/2023 09:51 AM

Also available in: Atom PDF