en05000830.vsdIED 3SendData-setReceiveReceiveLNLNLNLNLNIED 2SendData-setReceiveReceiveLNLNLN LNIED 1SendData-setReceiveReceiveLNLNLNLNLNLNIEC 61850 SubnetworkIEC05000830 V1 ENFigure 61: IEC 61850: horizontal communication principle, an example of threeIEDs where each IED communicate with all othersWhen a GOOSE message is to be sent, it is defined by configuring the data set with thedefined trigger option and GoCB. This engineering process is done in a stationconfiguration tool, for example, IEC 61850 Configuration tool or IET600. The taskinvolves configuring lists with the signal, value and quality (data attributes) that belongto the GOOSE message data set.In the opposite direction, the standard only defines the IED as a receiver of a GOOSEmessage. How the GOOSE input signals are handled must be defined in the IEDapplication configuration. The SCL data generated by the IEC 61850 Configurationtool or IET600 (or any other station configuration tool) contains the GOOSE data setsas input data. The input data must be connected to a GOOSE receive function blocks inthe Signal Matrix tool.7.2.2 Function view for IEC 61850 in PCM600The IED design is directly based on IEC 61850. Thus, the function blocks in PCM600tool use IEC 61850 logical node naming for function blocks. This relation isautomatically handled by the PCM600 tools.The concept in the IED is such that the IEC 61850 data for each function instance isavailable in the data model, even when the function is not used in the application. Thismeans that it is not necessary to handle any instance information for the functionsregarding IEC 61850.1MRS240044-IB A Section 7IEC 61850 communication engineeringREF615R 101Engineering Manual
