Professional Documents
Culture Documents
IEC 61850 Server Interface: User Manual
IEC 61850 Server Interface: User Manual
User Manual
www.kalkitech.com
Disclaimer
Information in this manual is subject to change without any notice.
Information provided in this manual is intended to be accurate and reliable. However,
Kalki Communication Technologies assumes no responsibility for its use. Kalki Communication
Technologies Pvt. Ltd. makes no commitment to update or keep the current information in this manual.
Contact Information
2. Getting Started 7
2.1. Application Setup and Configuration 7
2.2. Starting IEC 61850 Module Inside the Gateways 7
Appendix C - References 32
Glossary 33
1.3. Environment
For complete configuration of the protocol gateways ‘EasyConnect’ configuration utility is used
and ‘ICD Manager’ is required for creating the IEC 61850 ICDs. This section specifies the
hardware and software requirements to run ‘EasyConnect’/’ICDManager’ configuration utilities.
1.3.1. Hardware Requirements
The hardware requirements are as shown in Table 1:
Requirement Description
Configuration Tool's System Memory 512 MB or more
Configuration Tool's System CPU 1.5 GB or more
Configuration Tool's System Free disk space 96 DPI
Table 1: Hardware Requirements
EasyConnect will enable user to configure the required tags that need to be involved in the
conversion. User need to map data points available in the chosen master protocol to the specified
tags of IEC 61850 server. After completing the configurations, the final .xml file can be saved and
downloaded to the Protocol Gateway that is used while running the protocol conversion engine.
The details of EasyConnect configuration are explained in section – 3.2.
As the first step, the user needs to add IEC 61850 server (slave) channel (under peer channel)
and node under the channel as explained in SYNC user manual (similar to any other channel
addition). After completing the configurations of specific master (client) channel, node, and
profile, the process for mapping to 61850 server channel is as follows:
Figure 2 given below explains how the mapping can be done from a master node to the specific
IEC 61850 server node. First select the profile under the master node and click on the specific
row to be mapped. Now select the IEC 61850 server node to be mapped from the drop-down list
from the lower-right hand side panel. (The mapping will work only if suitable ICD file is selected
under IEC 61850 server channel)
Note: If any of the rows in a group in auto map window is not able to map (if there are
no tags available) the entire row in that particular group will be disabled and will not be
mapped.
Note: For every IEC 61850 channel with a GOOSE subscriber node, it is mandatory
that the channel contain an IEC 61850 server node.
1. Add GOOSE subscriber node under the IEC 61850 server channel. Right click on the IEC
61850 channel and choose GOOSE subscriber addition option.
3. Add a Profile.
4. Add the data set elements of the GOOSE that is to be received (the element types and
arrangement should be same as that of the publisher). To add the data set elements click ‘Add/
Edit Dataset Elements’ button available on the GCB window (shown in Figure 6). Choose the
type and name of the ‘data tag’ and ‘FCDA tag’.
All the logical devices The logical device under which the
Logical device –
inside the ICD GCB comes
All GCB names under the The GCB name inside the server that
GCB name –
chosen LD need to be considered under the client.
MAC - address
MAC -
corresponds to chosen – The multicast MAC address for Goose
address
GCB.
The parameter will be a visible string
Application Id corresponds
Application Id – that represents a LOGICAL-DEVICE in
to chosen GCB.
which the GCB is located.
Configuration Rev
Configuration Represent a count of the number of
corresponds to chosen –
rev times that the configuration of
GCB.
The DataSet corresponds The name of DataSet corresponds to
DataSet –
to the chosen GCB. the chose GCB.
Table 6: Goose Control Block Parameters
Profile Parameters
Both the options can be obtained by adding corresponding SNTP channel, right clicking the device
model name in easy connect and adding the corresponding channel. The channel parameters
are described in the following table:
’Operate-many‘ supported N
interlock-check N
Service error types are supported
instance-not-available N
instance-in-use N
access-violation Y
access-not-allowed-in-current-
N
state
parameter-value-inappropriate N
control-must-be-selected N
parameter-value-inconsistent N
class-not-supported N
instance-locked-by-other-client N
type-conflict Y
failed-due-to-communications N
constraint failed-due-to-server-
N
constraint
Table 26: PIXIT for Control Model
Note: KSGL series have been replaced by their functionally equivalent to SYNC series.
For details, refer KSGL/SYNC User Manual.