C.5 IEC 61850 IMPLEMENTATION VIA ENERVISTA UR SETUP
The root file structure of an ICD file is illustrated below.
Header (id, version, revision, toolID, nameStructure)
IED (name, type, manufacture, configVersion)
Figure C–2: ICD FILE STRUCTURE, SCL (ROOT) NODE
The Header node identifies the ICD file and its version, and specifies options for the mapping of names to signals
The Communication node describes the direct communication connection possibilities between logical nodes by means of
logical buses (sub-networks) and IED access ports. The communication section is structured as follows.
ConnectedAP (iedName, apName)
Other P elements
GSE (IdInst, cbName)
Other GSE elements
Other P elements
Figure C–3: ICD FILE STRUCTURE, COMMUNICATIONS NODE
The SubNetwork node contains all access points which can (logically) communicate with the sub-network protocol and
without the intervening router. The ConnectedAP node describes the IED access point connected to this sub-network. The
Address node contains the address parameters of the access point. The GSE node provides the address element for stat-
ing the control block related address parameters, where IdInst is the instance identification of the logical device within the
IED on which the control block is located, and cbName is the name of the control block.
The IED node describes the (pre-)configuration of an IED: its access points, the logical devices, and logical nodes instanti-
ated on it. Furthermore, it defines the capabilities of an IED in terms of communication services offered and, together with
its LNType, instantiated data (DO) and its default or configuration values. There should be only one IED section in an ICD
since it only describes one IED.
L60 Line Phase Comparison System