Configurable Logical Devices; Protocol Implementation Conformance Statement (Pics); Basic Conformance Statement - GE B30 Communications Manual

Universal relay family
Hide thumbs Also See for B30:
Table of Contents

Advertisement

PROTOCOL IMPLEMENTATION CONFORMANCE STATEMENT (PICS)

Selected IED — The order codes in the input files must match for a device to appear in the list here. The device name,
order code, and firmware version of the device display.
61850 Settings — The source file for the Public section of IEC 61850 settings.
Non-61850 Settings — The source file for the Private section of the file.
Network Settings — The source file for the IP and subnet addresses; the content defined by <Communication>...</
Communication>.
Default — Merging common settings. This operation is necessary because of potential differences between the Public
and Private values for the same setting.
Output file — Name and location of the merged file.
Add to Offline Window — Enable to copy the output file to the Offline Window area of the software, resulting in a .urs
file visible in the Offline area. If the output file is not a CID file, it is renamed temporarily to .cid, imported, and renamed
back to the original name.
3
4.
Click the Merge button.
5.
If a window opens, specify the location for the file to be added to the Offline Window area in the Target Folder field
and a name for this device/folder in the Device Name field. Click the Finish button.
6.
The files are validated and the settings are imported from the files identified. When the option to Add to the Offline
Window was selected, the output generates as merged files in the ICD, CID, IID, and SCD formats. Otherwise, a single
file generates. Check the contents in a text editor. The _MergeReports.txt file indicates when the Default was used to
merge common settings.
7.
To use a merged file, drag-and-drop it into the Online Window area.

3.2.2 Configurable logical devices

The configurable logical devices feature available since UR 7.40 allows the assignment of logical nodes to logical devices
to be customized to user requirements, and the number of logical devices to be changed to any number from 1 to 16.
The one logical device that must remain is Master. The following logical nodes have fixed assignment to the Master logical
device:
LPHD1 — models common issues for physical devices
The LLN0 in the Master logical device, which includes group, GOOSE and report control blocks, and datasets
LGOS logical nodes — for GOOSE subscription
GGIO1 — for unmapped FlexLogic operands
GGIO2 — for Virtual Input control
GGIO3 — for RxGOOSE Inputs
GGIO4 — for unmapped FlexAnalog operands
Other than these, and other than the LLN0 logical nodes in logical devices other than Master, all LN elements can be
moved freely between LDevice elements. Note however that LN elements cannot be deleted, only moved.
An LDevice element that has no remaining LN elements (only LN0 remaining) can be deleted, effectively removing the
logical device from the information model as if it never existed.
LDevice elements can be added up to 16 in total and LN elements moved into it from other LDevice elements, provided
that it contains an LN0 element with lnType referencing a DOType equivalent to the LLN0_1 DOType contained in ICD files
generated by the UR or the EnerVista UR Setup software.
3.3 Protocol implementation conformance statement (PICS)

3.3.1 Basic conformance statement

The tables contain the basic conformance statement.
3-24
CHAPTER 3: IEC 61850 COMMUNICATION
UR FAMILY – COMMUNICATIONS GUIDE

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents