52   Ambiguity GOOSE SqNum

Created: 15 Mar 2005

Status: In Force (green)

Part: Part 7-2 (2003)

Links:

Page:

Clause: 15.2.3.6

Paragraph:

Category: Issue may impact interoperability of implementations of Edition 1

Issue

There is a discrepancy between the 7-2 and 8-1 definitions of GOOSE SqNum.
7-2 clause 15.2.3.6 states:
'The initial value for SqNum shall be 1. The value of 0 shall be reserved.'
Whereas 8-1 clause 18.1.2.15 states:
'The value of 0 is reserved for the first transmission of a StNum change.'

Proposal

Change part 7-2 to match 8-1.
The SqNum shall be set to 0 to indicate the first GOOSE transmission initiated by a value (increment of StNum) change.
The first GOOSE message after a state change should be easily distinguishable from all other messages.

Discussion Created Status
As agreed at the UCAIUG telco of 16 april 2014 we updated the last sentence of the 15dec06 revised text to "The initial value for sqNum upon a transition of GoEna to TRUE is recommended to be 1." 16 Apr 14 In Force (green)
Editor meeting December 2006:
The revised Text is:

"Following a StNum change, the counter SqNum shall be set to a value of 0. If the counter SqNum overruns, it shall be set to a value of 1. The initial value for SqNum upon a transition of GoEna to TRUE shall be 1."
15 Dec 06 In Force (green)
Proposal accepted.
Changed to green.
18 Aug 05 In Force (green)
Final Proposal:
8-1 got it right. 7-2 got to change.
7-2 need to correct sqNum and stNum definition as proposed.
01 Apr 05 Ballot Period

 

Privacy | Contact | Disclaimer

Tissue DB v. 21.8.20.1