Project

General

Profile

Issues #5959

sSvp3 remove random and allow synSourceID=TRUE for backwards compatible config

Added by Richard Schimmel about 2 years ago. Updated 9 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Richard Schimmel
Due date:
09/20/2022
Discuss in Upcoming Meeting:
No
Clause Reference:
61850 Standard:
9-2
Triggering Tissue:
Final Decision:
Initial Test Document:
Updated Test Document:
TP1.3
Test Case ID:
sSvp3
Closed Reason:
--Not Set---
Triggering Tissue 2:
Triggering Tissue 3:

Description

Step 1 shall not use the random but the "same configuration as sSvp1" (compare for example sSvp2)

Second issue: is the backward configuration with synchSourceID=True considered as a backward compatible config? The 9-2LE does not have synSourceID. But newer devices may use backward configuration with PTP and synchSourceID. Clarify for step 6 which steps shall be repeated or even better create step 6-7-8-9:

Proposal:
1. Configure the DUT with the same configuration as sSvp1
2. Generate current and/or voltage signals
3. if PTP is supported configure synchSourceId to TRUE and capture SV messages for at least 1 second
4. if PTP is supported configure synchSourceId to FALSE and capture SV messages for at least 1 second
5. Configure the DUT with the lowest rate backwards compatible configuration
6. Generate current and/or voltage signals
7. if PTP is supported configure synchSourceId to TRUE and capture SV messages for at least 1 second
8. if PTP is supported configure synchSourceId to FALSE and capture SV messages for at least 1 second

Also available in: Atom PDF