Project

General

Profile

Issues #5347

How should time correlated GOOSE change status in GOOSE Performance test

Added by Hua Qin 4 months ago. Updated 7 days ago.

Status:
In Progress
Priority:
Normal
Due date:
10/04/2022 (Due in 49 days)
Discuss in Upcoming Meeting:
No
Clause Reference:
61850 Standard:
Triggering Tissue:
Final Decision:
Initial Test Document:
Updated Test Document:
Test Case ID:
Closed Reason:
Test Procedure Update
Triggering Tissue 2:
Triggering Tissue 3:

Description

Please clarify how should the time correlated GOOSE change status in GOOSE performance test.

From what I read below and understand, there are 5 GOOSE which has the following scheme 1:
-4ms: GPFsubscribed1 only change status of 5th data
-2ms: GPFsubscribed2 only change status of 5th data
0ms: GPFsubcribed3 change status of 5th data, GPFPPing change the status
2ms: GPFsubscribed4 only change status of 5th data
4ms: GPFsubscribed5 only change status of 5th data

But there is another understanding - scheme 2:
-4ms: GPFsubscribed1/2/3/4/5 all change status of 5th data
-2ms: GPFsubscribed1/2/3/4/5 all change status of 5th data
0ms: GPFsubscribed1/2/3/4/5 all change status of 5th data, GPFPPing change the status
2ms: GPFsubscribed1/2/3/4/5 all change status of 5th data
4ms: GPFsubscribed1/2/3/4/5 all change status of 5th data

In device with contact inputs rather than GOOSE, there is a general setting like debounce time to filter the situation in scheme 2 and thus will not have 5 changes within 8ms.

Also available in: Atom PDF