121   GOOSE subscriber behavior

Created: 16 Mar 2005

Status: In Force (green)

Part: Part 8-1 (2004)



Clause: 18.1.2


Category: Issue for edition 2 of this part


GOOSE subscriber behaviour in case of lost, double, out-of-order or missing GOOSE-messages isn’t described.
Currently it is a local issue how the receiving device reacts under these conditions. Part 10 specifies negative test cases for the transmission of GOOSE message, therefore the device reaction in case of faults has to be standardized too. Otherwise the local and vendor specific device behaviour has to be described in the PIXIT.


Add new clause “Receiving GOOSE messages”. The device behaviour shall be described for all the irregular cases.

Discussion Created Status
GoE-meeting 19.10.04 (agreed by Herb and George):
Final proposal
GOOSE subscriber behaviour is vendor or application specific and may be defined in the PIXIT.
16 Mar 05 In Force (green)


Privacy | Contact | Disclaimer

Tissue DB v.