1828   Clarification on GOOSE/SV supervision with simulated message

Created: 02 Jun 2022

Status: Solution Accepted

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 comments. 19 Dec 23 Solution Accepted
No test change needed 21 Nov 23 Ballot Period
TPWG: No change needed. sGos6 and sSvs4 currently validate this. 05 Sep 23 Conformance Test Verification
No issues found. 22 Aug 23 Conformance Test Preparation
No issues found, proceed to compatibility analysis 11 Jul 23 Analysis Of Compatibility
No objection, proceed to next state. 09 Jun 23 Verify Draft Implementation
Add to 7.8.2:

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. 		02 May 23 Drafting Implementation

 

Privacy | Contact | Disclaimer

Tissue DB v. 23.12.13.1