GOOSE Monitoring with LGOS Logical Nodes - Arc protection - Bay control and measurement - Merging unit - Transformer protection - 2 winding - Feeder protection - Voltage regulation - Capacitor bank protection - Grid automation - Busbar differential protection (high impedance) - Line differential protection - Back-up protection - Motor protection - Busbar protection (voltage and frequency) - Interconnection protection - Generator protection - Power management/Load shedding - IEC 61850 Engineering Guide - REX615 Protection and control - PCL3 - IEC - ANSI

REX615 IEC 61850 Engineering Guide

GOOSE network communication at the SCADA side can be monitored with LGOS logical nodes.

To enable LGOS Monitoring in PCM600, go to Tools > Options > IEC 61850 Configuration and select the Automatic GOOSE supervision configuration option. Note that this setting is global and can’t be selected only for a specific project or IED.

Figure 1. Enabling LGOS Monitoring in PCM600

Once selected, LGOS logical nodes will be automatically created in an IED when it is subscribed to receive data over GOOSE. PCM600 assigns LGOS LNs to GOOSE control blocks on a first-in-first-serve principle.

Note: The IEC 61850 Configuration tool tracks all LGOS LNs in a project and will keep them updated, e.g. when a sender is deselected for subscription, this will automatically erase all previously assigned logical nodes.

LGOS LN to GOOSE control block configuration can be verified from the device’s WHMI. In the WHMI go to Device > GOOSE and SMV > GOOSE Receiving.

Figure 2. LGOS LN monitoring

The assigned LGOS Logical node to a GOOSE Control block can be visible after its name in brackets. Alternatively, the sender’s GOOSE control block can be verified via the GocbRefVal data object over MMS.

Figure 3. LGOS LN GOOSE Control block reference

GOOSE Monitoring via LGOS LNs provide SCADAs with the possibility of checking the overall status of a GOOSE control block (St-DO) and if simulated GOOSE messages are accepted and being received (SimSt-DO). Also, it provides more information if there is a misconfiguration (NdsCom-DO), e.g. a mismatch between the configuration revision parameter (ConfRevNum-DO) and the value of the received one (RxConfRefVal-DO).

Additionally, GOOSE monitoring in WHMI has been completed to display misconfiguration issues with configuration revision and commissioning.

Figure 4. Improved monitoring for conf. revision and needs-commissioning issues