goose connections

[beyond86]

Hello! I need your help. Can anyone show an example of circuit diagram where used goose protocol for connection between 2 terminals of relay protection? How can I depict connections between terminals on a circuit diagram?

 

[MikeHalloran]

1. I don't know; do you have the correct terminology?
2. With a black or colored line.


Mike Halloran
Pembroke Pines, FL, USA

 

[JG2828]

It is actually a pretty good question. How to show 61850 Goose Messaging between two relays on a schematic diagram. I don't have a good answer though. You may want to read through this PSRC report. It hits on this subject a few times and talks about using a separate spreadsheet or logic diagrams to detail this information.

http://www.pes-psrc.org/Reports/IEEE_I5_Schematic_Approved_Final.pdf

 

[beyond86]

JG2828, thanks for information.
May be somebody else to connect to discuss and share information.

 

[davidbeach]

How do you show other relay-to-relay communications? I would imagine that your goose traffic would be shown similarly to similar comms.

 

[MikeHalloran]

JG2828, thank you; I am now slightly less ignorant than I was yesterday.

As suggested, you just need another 'linetype'.
... but that highlights the complexity and difficulty of representing multiple communication/control modes and potential interactions without degrading understanding of the controlled system.






Mike Halloran
Pembroke Pines, FL, USA

 

[beyond86]

davidbeach, communications between relay must be understandable. Which information I have to show on a circuit? How make reading of circuit more easy?

 

[JG2828]

Take a look at the attached paper. It has some good ideas on how to document Goose messaging.

IV. SCHEME DESIGN PROCESS
Effectively documenting the design is one of the challenges associated with implementing GOOSE-based protection and control schemes. With GOOSE messaging being a relatively unfamiliar technology in the United States, there is not an established documentation method for GOOSE-based schemes. Traditional hard-wired protection and control logic is typically documented on a control schematic. Engineers and technicians are familiar with these drawings. When these hardwired schemes are replaced with communications-aided schemes and relay logic, information is removed from the schematic diagrams, but the end-user still needs some form of detailed documentation of the scheme functionality. To address the need for documentation, the team implemented a tiered approach to the communications-aided scheme documentation including a functional specification, GOOSE mapping spreadsheet, and IED logic diagrams. A document flow diagram is shown in Figure 4. The objective of these documents was two-fold. The documents needed to aid the team in the implementation of the schemes, and the documents also needed to serve as an intuitive set of reference materials for the end-user. After completion of these documents and diagrams, the actual relay programming and GOOSE configuration were executed. The following sections describe the approach taken to each tier of the documentation.​

 

[beyond86]

JG2828, thank you for the paper. It's really helpful.
I thought that goose messages are more spread in the United States and established documentation has been made already.