1671   LGOS LastStNum behavior

Created: 12 Feb 2020

Status: Discussion (red)

Part: Part 7-4 (2010; Edition 2)

Links:

Page: 25

Clause: -

Paragraph: 5.3.6

Issue

It is unclear what is the required behavior for LGOS.LastStNum.stVal.
Should the stVal match the last received GOOSE message, as described in 7-4 (Last state number of received GOOSE), or should it take into account that some GOOSE messages are rejected (for example because of invalid header)

Proposal

-Clarify that only accepted (valid) GOOSE messages count for the LGOS.LastStNum.stVal value.
OR
-Clarify that all GOOSE messages, including invalid ones, count for the LGOS.LastStNum.stVal value.

Discussion Created Status
Tissue is open for discussion. 24 Feb 20 Discussion (red)
The observation of stNum allows the subscriber to monitor state changes at the publisher and to react on state changes, resp. allows the subscriber to detect replay message - message out of sequence.
Such observation is of no relevance when the message is NOT conform to the expected configuration.

For the supervision purpose, only observation of stNum of correct messages are relevant. There is no interest to display stNum of wrong configuration, as their state changes or replay will not be monitored and reported as such.

-> only telegram that are accepted and whose data content are forwarded to the application (St.stVal = true) lead to an update of LastStNum.
14 Feb 20 Accepted
The tissue will be discussed and clarified in the TF Goose Supervision considering the IEC 61850 V2.1 (part 7-2, 7-3 and 7-4 are already publihed). 13 Feb 20 Accepted

 

Privacy | Contact | Disclaimer

Tissue DB v. 25.2.18.2