1828   Clarification on GOOSE/SV supervision with simulated message

Created: 02 Jun 2022

Status: Drafting Implementation

Part: Part 7-1 (2020; Edition 2.1)

Links:

Page: 63-64

Clause: 7.8.2

Paragraph: Second paragraph and figures

Issue

It is required to specify when supervision information are related to the simulated message and when they are related to the normal messages.
In addition, case of receiving a bad configured simulated GOOSE/SV has to be considered.

Note that clarification was required by Bruce and then discussed in TF Communication Supervision before deciding to open this tissue.

Proposal

LGOS/LSVS should start to supervise simulated message when subscriber is allowed to process simulated messages (LPHD.Sim = TRUE) and when first simulated message has been received. That happens when SimSt becomes TRUE. All diagnostic DOs (NdsCom, RxConfRevNum, LastStNum) should be impacted when receiving simulated GOOSE/SV. When leaving simulation mode, latest diagnostic information are kept.

In addition, subscriber is not expected to supervise simulated messages before being allowed to process simulated messages.




Discussion Created Status
No discussion... 28 Mar 23 Drafting Implementation
The standardized supervision information exposed in LGOS and LSVS apply to simulated GOOSE resp. SMV message when the SimSt becomes true, and to the non-simulated GOOSE resp. SMV message when the SimSt is false.
When leaving simulation mode, latest diagnostic information are kept until the next non-simulated GOOSE resp. SMV is processed. 		28 Feb 23 Discussion (red)
Proposal Accepted 28 Feb 23 Accepted
I agree with Christophe proposal stating that the stnadardized supervision information exposed in LGOS and LSVS apply to simulated GOOSE resp. SMV message when the SimSt becomes true, and to the non-simulated GOOSE resp. SMV message when the SimSt is false.
When leaving simulation mode, latest diagnostic information are kept until the next non-simulated GOOSE resp. SMV is processed.

Further supervision information may be provided but are out-of-scope of the standard: the semantic of logical node proprietary extension needs anyhow to be defined by the vendor in a MICS or User's manual.
02 Aug 22 Triage
Christophe,
I have not required anything, just explained (for information) how we do it in our test devices and just asked the question if and how this may also apply for IEDs.
I am absolutely fine with the way you explain it. The behavior of a test device and an IED can be well different under the mentioned circumstances, as the use cases are not identical. 		08 Jun 22 Triage
If I understand the proposal correctly, the LGOS/LSVS should "switch over" to the simulated messages. How about further supervision of the operational messages?
In our tools, we consider simulated messages (which come typically in addition to the operational messages) as distinct new traffic.
We still process the operational traffic and in addition the simulated one, which we consider useful for test equipment.
How do we see this for supervision in IEDs? 		02 Jun 22 Triage

 

Privacy | Contact | Disclaimer

Tissue DB v. 23.3.6.1