IEC 61850 Protocol
IEC 61850 Protocol
IEC 61850 Protocol
70022-0125-00
11/2010
NOTE
Not all ION meters support IEC 61850.
In this document
Appendix A: Conformity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Additional information
IEC (International Electrotechnical Commission) website at www.iec.ch
Your meter’s documentation
Your IEC 61850 configuration software’s documentation
More information about IEC 61850 and Schneider Electric devices is available
from www.schneider-electric.com.
Schneider Electric ION, PowerLogic and Schneider Electric are trademarks or registered trademarks of
2195 Keating Cross Road Schneider Electric in France, the USA and other countries. Other trademarks used are the
Saanichton, BC property of their respective owners.
Canada V8M 2A5
Tel: 1-250-652-7100 Electrical equipment should be installed, operated, serviced, and maintained only by qualified
personnel. No responsibility is assumed by Schneider Electric for any consequences arising
For technical support: out of the use of this material.
[email protected]
(00) + 1 250 544 3010
© 2010 Schneider Electric. All rights reserved.
Contact your local Schneider Electric sales representative
for assistance or go to
www.schneider-electric.com
Hazard Categories and Special Symbols IEC 61850 and ION Technology
The addition of either symbol to a “Danger” or “Warning” safety label indicates that
an electrical hazard exists which will result in personal injury if the instructions are
not followed.
This is the safety alert symbol. It is used to alert you to potential personal injury
hazards. Obey all safety messages that follow this symbol to avoid possible injury
or death.
DANGER indicates an imminently hazardous situation which, if not avoided, will result
in death or serious injury.
WARNING indicates a potentially hazardous situation which, if not avoided, can result
in death or serious injury.
CAUTION indicates a potentially hazardous situation which, if not avoided, can result in
minor or moderate injury.
CAUTION
CAUTION used without the safety alert symbol, indicates a potentially hazardous
situation which, if not avoided, can result in property damage.
NOTE
Provides additional information to clarify or simplify a procedure.
Please Note
Electrical equipment should be installed, operated, serviced and maintained only
be qualified personnel. No responsibility is assumed by Schneider Electric for any
consequences arising out of the use of this material.
Meter models
The following table lists the meter models that support IEC 61850:
Meter Models
5M logging memory
ION76501 Ethernet communication
5M logging memory
ION75501 Ethernet communication
1
Upgrading a 10 MB meter with IEC 61850 firmware will reduce the logging memory to 5 MB. Refer
to your meter’s User Guide for more information.
Meter firmware
The following table lists the meters and firmware that support IEC 61850:
Meter Firmware
NOTE
Changing your meter’s firmware will delete all IEC 61850 files stored on your meter.
Failure to follow these instructions can result in death, serious injury or equipment
damage.
Human Substation
Machine controller
Interface
Ethernet
IED
Gateway IED
ION7650
Terminology
The following table lists some of the terms used in IEC 61850 and their definitions.
For a complete listing of IEC 61850 terms, refer to IEC 61850-2.
Term Definition
Configured IED Description, which is an ICD that has been configured for a
CID specific IED using IEC 61850 configuration software. Refer to “IEC 61850
Files” on page 5.
An IEC 61850 system terminal that receives data, reports and controls the I/O
Client of the meter, and may provide real-time data or event viewing, or similar
functions. Only the client can initiate requests.
Data set A predefined or user-selected set of data that can be reported via IEC 61850.
FTP File Transfer Protocol, a method of transferring computer files over Ethernet.
IED Capability Description, which is supplied by the vendor of the IED. Refer
ICD
to “IEC 61850 Files” on page 5.
is one typical substation function of the IED, for example the MMTR logical
Logical node node, which contains energy information. Refer to “Logical nodes supported in
the ION implementation of IEC 61850” on page 10.
The IED’s physical device Ethernet access point. In the context of IEC 61850
Physical device this is the same as an IED. The physical device contains one or more logical
devices.
SCD file
CID file
NOTE
Ensure you are using the ICD file that matches your meter’s hardware configuration in order to support
your meter’s input and output hardware ports in IEC 61850.
The ICD file is loaded into an IEC 61850 configuration tool, such as
Schneider Electric’s CET850 IEC 61850 configuration software, and the
parameters are edited as required with the information specific to that instance of
the IED. Once the parameters are edited, the IEC 61850 configuration tool can
build the CID file. The CID file is then loaded into the IED via FTP.
IED’s with the same feature set will use the same ICD file. However, every IED will
require its own unique CID file. To create a CID file, begin with the correct ICD file
and then configure the ICD file using IEC 61850 configuration software.
Failure to follow these instructions can result in death, serious injury or equipment
damage.
NOTE
Changing the Ethernet settings on your meter will reset the meter’s IEC 61850 functions and delete any
unsent reports.
File Transfer
FTP is used to upload the CID file to the meter, using either WinSCP or Windows
Explorer as the FTP client software. Only one simultaneous FTP transfer
connection is permitted. The FTP timeout period is 90 seconds on a control port.
Once a valid CID file has been uploaded to the meter it will begin functioning as an
IEC 61850 server, and can provide information to the IEC 61850 client substation
systems. The meter communicates via FTP on the following ports:
Port Description
NOTE
Changing the firmware on your meter will delete the meter’s CID file.
The IEC 61850 folders on your meter are factory-configured and cannot be
modified. You cannot change the file structure of the FTP files on your meter; you
can only add or remove files in the existing folders.
File names are limited to standard ASCII characters, meaning they cannot contain
a blank space or \, /, “, *, ? “, < or >, and are limited to 68 characters in length,
including the file extension. The “/” character will be used as part of the FTP file
directory information.
NOTE
FTP files from your meter can only be accessed and modified by Windows-based machines.
CID files
CID files are created from the ICD file using an IEC 61850 configuration tool. The
CID file contains information specific to your meter, such as deadband values and
data sets and reports. Your IEC 61850 configuration tool may require that you
include Ethernet communications information in your CID file, but this information
is not used; the communications information for IEC 61850 is taken from the
meter’s configuration.
CID files can be created offline, without the meter present. Existing CID files can
be reconfigured/reused in other meters providing that they are of the same type
and have the same options (i.e., the meters would use the same ICD file).
A valid CID file must fit within the allocated directory space (including space for the
log file), with a maximum filename length of 68 characters (including file extension)
from the regular ASCII character set (no special characters). The CID file must also
be compatible with the IEC 61850 conformance of the meter. Refer to “Appendix
A: Conformity” on page 19. If the CID file is found invalid, an error message will be
written to the log.txt file.
NOTE
The CID file controls whether the meter is operating as an IEC 61850 server. If the meter does not have
a valid CID file loaded, the meter will not perform any IEC 61850 functions.
log.txt
The log.txt file is stored on your meter in the IEC 61850 folder. It contains up to fifty
of the most recent informational messages related to IEC 61850 operations on
your meter. Refer to “Appendix A: Conformity” on page 19 for details on how
IEC 61850 operates on your meter.
NOTE
The log.txt timestamp is in Coordinated Universal (UTC) time.
Refer to the log.txt file when transferring a new CID file to confirm that the CID file
is valid and the IEC 61850 aspects of your meter are operating. If the CID file is
invalid, the log.txt file will contain additional information to assist in creating a valid
CID file. You must delete the invalid CID file and use the ICD file (available from
www.schneider-electric.com) to correct the invalid attributes and build a new CID
file. Refer to “Appendix A: Conformity” on page 19 for details on the IEC 61850
attributes of your meter.
Meter Security
The ION7550/ION7650 can be configured with standard or advanced security.
These security settings should be reviewed for compatibility with your IEC 61850
client or FTP software.
If standard security is enabled, the FTP login name can be any value (not including
invalid characters), and the login password is the front panel password. If
advanced security is enabled, the login name and password must match with an
advanced user that has full read/write access. Once logged in, you will have read
and write access to the FTP files and subfolders.
NOTE
To connect to your meter using only a single FTP connection, you must have the login and password
included in the FTP connection string. For example, with standard meter security and the default front
panel password of 0, to connect to a meter with an IP address of 123.45.6.78, the Windows Explorer
connection string would be: ftp://0:[email protected]
Refer to your meter’s documentation for more information about meter security.
Device Information
These logical nodes have corresponding ION modules that map the information
from the ION protocol into IEC 61850.
NOTE
A valid CID file can only contain the supported Logical Nodes in their associated quantities.
Generic process I/O. There are four types of GGIO logical nodes:
onboard I/O (the meter’s onboard I/O status and control).
expanded I/O (the meter’s expansion I/O status and control).
GGIO
custom analog (to map additional numeric values into IEC 61850)
custom digital (to map additional Boolean values into IEC 61850).
For information on how to configure the GGIO, refer to your meter’s user guide.
LLN01 Logical node zero. Contains the data related to the associated IED
MHAI Harmonics. Consists of harmonic values such as THD, K factor, Crest factor.
Measurements. Contains per-phase and total current, voltage and power flow
MMXU
for operational purposes.
Metering statistics. Consists of average, min and max for metered (MMXU)
MSTA
data.
1
ION meters act like a single physical device, with one logical device. Only one instance of LLN0 and
LPHD can be defined.
ION modules
Within the device’s native ION architecture, specific ION modules map data to each
of the IEC 61850 logical nodes, performing data conversion in addition to
deadband monitoring calculations. The IEC 61850 data is updated once per
second, regardless of the update rate of the related ION data.
Because the ION modules are for mapping data only, the timestamps of the
IEC 61850 data is based on the timestamp of the ION module’s input. If a particular
ION module is not available, the associated IEC 61850 module’s data values will
be set to N/A, and the IEC 61850 data’s Quality attribute will indicate that no valid
data is available.
The IEC 61850 ION modules are created and connected by default in the meter
templates that support IEC 61850. Manual creation and configuration of most of
these modules, or modification of existing modules, is an advanced feature that
should only be undertaken by personnel with a thorough understanding of ION and
IEC 61850 protocols. If modifying existing modules, make sure you use inputs that
have the same units as the original register values to ensure consistency of the
IEC 61850 related data.
The GGIO Custom modules must be configured by the user to allow additional
numeric and Boolean data values to be mapped from your meter into IEC 61850.
Refer to your meter’s user guide for instructions on how to configure the GGIO
modules.
Feature Description
A collection of data values from any logical node. Data sets are configurable in
Data Sets the CID file using an IEC 61850 configuration tool. You can have a maximum of
6 data sets containing up to 50 data values each.
Report control blocks (RCBs) are associated with a specific data set. When
trigger conditions are met, the report is sent to a specific client. RCBs are
Report Control
configurable in the CID file using an IEC 61850 configuration tool. There are a
Blocks
total of 20 unbuffered reports and 4 buffered reports available to up to 4 client
connections.
Specified in the RCB options in the CID file, options include data change (using
Trigger Options deadband values), integrity, and general interrogation. Refer to “Configuring
Reporting Triggers” on page 17.
Refer to your meter’s user guide for instructions on how to add custom data values
into IEC 61850 and how to enable IEC 61850 status values or control of the
meter’s input/output hardware ports.
NOTE
IEC 61850 I/O control and status must be configured using ION Setup. Refer to your meter’s User
Guide for details.
You will need the ICD file that matches with your meter’s hardware options. The
ICD files for each meter option are available from www.schneider-electric.com.
You will need an IEC 61850 configuration tool (such as Schneider Electric’s
CET850 IEC 61850 configuration tool) in order to create the CID file, and an FTP
program (such as Windows Explorer or WinSCP) to load the CID file onto your
meter.
Offline Configuration
Generate your meter’s CID file
For instructions on how to use your IEC 61850 configuration tool, please refer to
the configuration tool’s documentation.
1. Access the ICD file using the IEC 61850 configuration tool.
2. Enter the file properties to configure your meter. Properties that must be
configured in the CID file include:
IED Name
Deadband values (refer to “Configuring Reporting Triggers” on page 17)
NOTE
Revision notes and change tracking information can be entered into the Header properties.
3. Review the default data sets (DS) and reports (RCB/URCB) and create, delete
and modify them as required. Refer to “Configurable Aspects of IEC 61850” on
page 15 for details on data sets, including permitted data members and
quantities.
4. If desired, configure the descriptions (‘d’ field) for any logical node leafs.
5. Build the CID file.
On-site Configuration
For on-site configuration you will need an Ethernet connection to your meter to
transfer files via FTP.
NOTE
If you load different firmware onto your meter, the CID file on your meter will be erased and you will need
to re-transmit the CID file to your meter.
These steps outline how to transmit your IEC 61850 CID file to your meter.
NOTE
To connect to your meter using only a single FTP connection, you must have the login and password
included in the FTP connection string. For example, with standard meter security and the default front
panel password of 0, to connect to a meter with an IP address of 123.45.6.78, the Windows Explorer
connection string would be: ftp://0:[email protected]
3. Open the IEC 61850 folder on your meter. If a CID file has already been loaded
onto your meter, you can either delete the old CID file or, if the old CID file and
new CID file have the same name, overwrite the old file with the new CID file.
NOTE
You may want to archive your previous CID file as part of your IED’s historical information.
4. Copy the CID file to the IEC 61850 folder on your meter.
5. The meter will validate the CID file and write the results to the log.txt file located
in the meter’s IEC 61850 directory.
NOTE
There will be a delay of several minutes while your meter validates the CID file before it updates the
log.txt file.
6. Open the log.txt file and review the CID file entry to confirm that the CID file is a
valid configuration file. If the CID file is invalid, the IEC 61850 aspects of the
meter will not function and an error description will be written in the log.txt file.
Use the error description information to correct your CID file.
Dataset Description
Use your IEC 61850 configuration tool to modify, create or delete datasets in the
CID file.
Data sets cannot contain members that are harmonics, or whose “doName” and
“daName” attributes are not configured.
NOTE
IEC 61850 data is only updated every second, even if the associated ION data is updated more
frequently.
Configuring Reports
Reports are configured using your IEC 61850 configuration tool. You can have up
to five unbuffered reports and one buffered report per client connection. Reports
will only be transmitted to the client if that client has enabled the report. Reports
must be located in LLN0 so that they can contain any data set.
Unbuffered reports, when enabled, are transmitted one time only, and if the client
is not connected or there is a communications issue, the report is lost. Buffered
reports are transmitted while the client is connected and the report has been
enabled. If the client is not connected the report is loaded into a circular, first-in-
first-out buffer, to be resent when client connection is re-established and the
buffered report is re-enabled. Data sets cannot be shared between buffered and
unbuffered reports.
NOTE
Make sure that you have consistent IEC 61850 client connections. Intermittent or limited connection
times may result in lost data reports.
The ICD file for your meter is preconfigured with four unbuffered reports and one
buffered report per client connection:
Buffered/
Report Description
Unbuffered
Use your IEC 61850 configuration tool to modify, create or delete reports in the CID
file.
connections are supported. If you exceed this limit, the resulting CID file will be
invalid and will not run on your meter.
gi (general-
Report is triggered upon client request.
interrogation)
Refer to the “ACSI Conformance Statement” on page 20 for a full listing of reporting
triggers.
Deadband values
In IEC 61850 certain parameters have an instantaneous value (which begins with
“inst”) and a deadbanded value. The instantaneous value is updated every second.
The deadbanded value is set to the new instantaneous value when the difference
between the new instantaneous value and the deadbanded value either equals or
exceeds the deadband for that parameter.
Deadband values are configured using the IEC 61850 configuration tool and are
contained in the CID file.
You must use the IEC 61850 configuration tool to configure a data point’s
deadband value in the CID file. This value is stored in the “db” parameter
associated with that data point. Deadband is an absolute value in the same units
as the banded data.
Example:
Configure the power quality report for client connection one (URCBPQ1) to be
triggered (sent) when phase A current changes by 5 A or more from one reading
to the next.
Use the IEC 61850 configuration software to build a CID file that includes the
following settings:
1. The phase A ‘db’ parameter (MMXU > A > phsA) value is set to 5.
2. The power quality report for client connection one (LLN0 > URCBPQ1 > TrgOps)
has the “dchg” option set to True.
NOTE
Reports are only sent if they have been enabled by the client.
Example of operation:
15 A Instantaneous Magnitude
Phase A current
Deadband Magnitude
Phase A current
10 A
5A
Time (seconds)
Appendix A: Conformity
This appendix describes the conformity with IEC 61850. It does not describe the
standard itself, only the details of the IEC 61850 implementation in the ION meter
in terms of services, modeling, exceptions, extensions and adaptations.
Client-server roles
SCSMs supported
B21 SCSM: IEC 61850-8-1 used X
M1 Logical device X
M2 Logical node X
M3 Data X
M4 Data set X
M5 Substitution
Reporting
M7-2 report-time-stamp X
M7-3 reason-for-inclusion X
M7-4 data-set-name X
M7-5 data-reference X
M7-6 buffer-overflow X
M7-7 entryID X
M7-8 BufTm X
M7-9 IntgPd X
M7-10 GI X
M8-1 sequence-number X
M8-2 report-time-stamp X
M8-3 reason-for-inclusion X
M8-4 data-set-name X
M8-5 data-reference X
M8-6 BufTm X
M8-7 IntgPd X
M8-8 GI X
Logging
M9 Log control
M9-1 IntgPd
M10 Log
Control
M11 Control X
Other
M16 Time X
S1 ServerDirectory X
S2 Associate X
S3 Abort X
S4 Release X
Logical device (Clause 8)
S5 LogicalDeviceDirectory X
S6 LogicalNodeDirectory X
S7 GetAllDataValues X
S8 GetDataValues X
S9 SetDataValues
S10 GetDataDirectory X
S11 GetDataDefinition X
S12 GetDataSetValues X
S13 SetDataSetValues
S14 CreateDataSet
S15 DeleteDataSet
S16 GetDataSetDirectory X
S18 SelectActiveSG
S19 SelectEditSG
S20 SetSGValues
S21 ConfirmEditSGValues
S22 GetSGValues
S23 SetSGCBValues
S24 Report X
S25 GetBRCBValues X
S26 SetBRCBValues X
Unbuffered report control block (URCB)
S27 Report X
S28 GetURCBValues X
S29 SetURCBValues X
S31 SetLCBValues
Log
S32 QueryLogByTime
S33 QueryLogAfter
S34 GetLogStatusValues
Multicast SVC
S45 SendMSVMessage
S46 GetMSVCBValues
S47 SetMSVCBValues
Unicast SVC
S48 SendUSVMessage
S49 GetUSVCBValues
S50 SetUSVCBValues
Control (17.5.1)
S51 Select
S52 SelectWithValue
S53 Cancel
S54 Operate X
S55 Command-termination
S56 TimeActivated-operate
S57 GetFile
S58 SetFile
S59 DeleteFile
S60 GetFileAttributeValues
Time (5.5)
Logical node
System logical nodes (L group)
Physical device information (LPHD) class:
ION7550/
Attribute name Attribute type Explanation/value M/O/C/E
ION7650
ION7550/
Attribute name Attribute type Explanation/value M/O/C/E
ION7650
ION7550/
Attribute name Attribute type Explanation/value M/O/C/E
ION7650
Hz MV Basic frequency O X
ION7550/
Attribute name Attribute type Explanation/value M/O/C/E
ION7650
ION7550/
Attribute name Attribute type Explanation/value M/O/C/E
ION7650
ION7550/
Attribute name Attribute type Explanation/value M/O/C/E
ION7650
ION7550/
Attribute name Attribute type Explanation/value M/O/C/E
ION7650
ION7550/
Attribute name Attribute type Explanation/value M/O/C/E
ION7650
ION7550/
Attribute name Attribute type Explanation/value M/O/C/E
ION7650
Functional attributes
ION7550/
Attribute name Attribute type Explanation/value M/O/C/E
ION7650
Functional attributes
ION7550/
Attribute name Attribute type Explanation/value M/O/C/E
ION7650
Functional attributes
ION7550/
Attribute name Attribute type Explanation/value M/O/C/E
ION7650
ION7550/
Attribute name Attribute type Explanation/value M/O/C/E
ION7650
Functional attributes
ION7550/
Attribute name Attribute type Explanation/value M/O/C/E
ION7650
ION7550/
Attribute name Attribute type Explanation/value M/O/C/E
ION7650
Functional attributes
Timestamp
Value/value
Attribute name Attribute type M/O/C Comments
range
See TimeQuality
TimeQuality TimeQuality M Default
table
TimeQuality
Value/value
Attribute name Attribute type M/O/C Comments
range
Quality
Value/value
Attribute name Attribute type M/O/C Comments
range
Vector
Value/value
Attribute name Attribute type M/O/C Comments
range
Analog value
Value/value
Attribute name Attribute type M/O/C Comments
range
Unit
Value/value
Attribute name Attribute type M/O/C Comments
range
Refer to
SIUnit SIUnit IEC 61850 M
standard
Refer to
multiplier Multiplier IEC 61850 O
standard
Sub-data attributes
CtlModel value
Supported/Not
Attribute name Attribute order
Supported
status-only 0 Supported
direct-with-normal-
1 Supported
security
sbo-with-normal-
2 Not Supported
security
direct-with-
3 Not Supported
enhanced-security
sbo-with-
4 Not Supported
enhanced-security
Sequence value
Supported/Not
Attribute name Attribute order
Supported
pos-neg-zero 0 Supported
stVal Boolean ST M
q Quality ST M
t Timestamp ST M
stVal INT32 ST M
q Quality ST M
t Timestamp ST M
stVal Enum ST M
q Quality ST M
t Timestamp ST M
d Visible string 255 DC O
actVal Int32 ST M
q Quality ST M
t Timestamp ST M
units Unit CF O
pulsQty Float32 CF O
instMag AnalogVal MX O
mag AnalogVal MX M
q Quality MX M
t Timestamp MX M
units Unit CF O
db Int32U CF O
d Visible string 255 DC O
instCVal Vector MX O
cVal Vector MX M
q Quality ST M
t Timestamp ST M
units Unit CF O
db Int32U CF O
WYE (WYE)
phsA CMV C
phsB CMV C
phsC CMV C
neut CMV C
net CMV C
Delta (DEL)
phsAB CMV C
phsBC CMV C
phsCA CMV C
Sequence (SEQ)
c1 CMV2 M
c2 CMV2 M
c3 CMV2 M
seqT SeqT MX M
d Visible string 255 DC O
q Quality ST M
t Timestamp ST M
phsAHar Vector MX M
phsBHar Vector MX O
phsCHar Vector MX O
neutHar Vector MX O
numHar Int16U CF M
numCyc Int16U CF M
evalTm Int16U CF M
frequency Float32 CF M
q Quality ST M
t Timestamp ST M
phsABHar Vector MX M
phsBCHar Vector MX O
phsCAHar Vector MX O
numHar Int16U CF M
numCyc Int16U CF M
evalTm Int16U CF M
frequency Float32 CF M
stVal Boolean ST M
q Quality ST M
t Timestamp ST M
ctlVal Boolean CO M
ctlModel CtlModel CF M
d Visible string 255 DC O
stVal Int32 ST M
q Quality ST M
t Timestamp ST M
ctlVal Int32 CO C
ctlModel CtlModel CF M
d Visible string 255 DC O
stVal Enum ST M
q Quality ST M
t Timestamp ST M
ctlVal Int32 CO C
ctlModel CtlModel CF M
ION7550/
Logical node
ION7650
LLN0 X
LPHD1 X
MHAI1 X
MMTR1 X
M03_MMXU1 X
MSQI1 X
MSTA1 X
RDRE1 X
RDRE2 X
ONB1_GGIO1 X
* The I/O expansion GGIO Logical Node is determined based on the input/output hardware option of
your meter. Only one instance of this Logical Node is present on your meter.
Profile Conformance
A-profile support
A1 Client/server X
A2 GOOSE/GSE Management
A3 GSSE
A4 Time sync
T-profile support
T1 TCP/IP profile X
T2 OSI T profile X
T3 GOOSE/GSE T profile
T4 GSSE T profile
MMS Conformance
status M X
getNameList C X
identify M X
rename O X
read C X
write C X
getVariableAccessAttributes C X
defineNamedVariable O X
defineScatteredAccess I
getScatteredAccessAttributes I
deleteVariableAccess O
defineNamedVariableList O X
getNamedVariableListAttributes C
defineNamedType I
getNamedTypeAttributes I
deleteNamedType I
input I
output I
takeControl I
relinquishControl I
defineSemaphore I
deleteSemaphore I
reportPoolSemaphoreStatus I
reportSemaphoreStatus I
initiateDownloadSequence I
downloadSegment I
terminateDownloadSequence I
initiateUploadSequence I
uploadSegment I
terminateUploadSequence I
requestDomainDownload I
requestDomainUpload I
loadDomainContent I
storeDomainContent I
deleteDomain I
getDomainAttributes C X
createProgramInvocation I
deleteProgramInvocation I
start I
stop I
resume I
reset I
kill I
getProgramInvocationAttributes I
obtainFile I
defineEventCondition I
deleteEventContition I
getEventConditionAttributes I
reportEventConditionStatus I
alterEventConditionMonitoring I
triggerEvent I
defineEventAction I
deleteEventAction I
alterEventEnrollment I
reportEventEnrollmentStatus I
getEventEnrollmentAttributes I
acknowledgeEventNotification I
getAlarmSummary I
getAlarmEnrollmentSummary I
readJournal C
writeJournal I
intializeJournal C
reportJournalStatus I
createJournal I
deleteJournal I
fileOpen C
fileRead C
fileClose C
fileRename I
fileDelete C
fileDirectory C
unsolicitedStatus I
informationReport C
eventNotification I
attachToEventCondition I
attachToSemaphore I
conclude M X
cancel M X
getDataExchangeAttributes C
exchangeData C
defineAccessControlList C
getAccessControlListAttributes C
reportAccessConrolledObjects C
deleteAccessControlList C
alterAccessControl C
reconfigureProgramInvocation C
SCL Conformance
You must configure the meter’s Ethernet settings using the front panel or
ION Enterprise or ION Setup software. Some IEC 61850 configuration tools
require that the communications information entered in order to generate the CID
file, however the CID communications values are not used by the meter.
ACSI models
Association model
Item Value/comments
Authentication Yes
Association parameters
TSEL 001
SSEL 001
PSEL 00000001
AP-title Not required, ignored if present
AE-qualifier Not required, ignored if present
1
Contact Technical Support for information on changing this value.
Server model
Item Value/comments
Maximum number of data values in Get/ Limited by Maximum MMS PDU size and the
SetDataValues requests1 device’s internal memory limitations
Item Value/comments
1
Recommended maximum of 100 data attributes per read/write request.
Dataset model
Item Value/comments
1 IEC 61850 configuration tools may not provide warning if maximum number of data elements is
exceeded. However, the resulting CID file will not be validated by the meter and an ‘invalid CID’
message will be logged in the log.txt file.
Reporting model
Item Value/comments
8 bytes total:
EntryID first 4 bytes = CID parse timestamp
last 4 bytes = new buffered report entry ID
Item Value/comments
Integrity Supported
EntryID Supported
Conf-rev Supported
Segmentation Supported
Control model
Item Value/comments
Not supported
Check conditions Meter executes control operation as usual
(ignores check value)
Not supported
Origin categories (orCat) Meter executes control operation as usual
(ignores orCat value)
Not supported
Local/remote operation Meter executes control operation as usual
(ignores local/remote operation value)
Item Value/comments
Item Value/comments
Maximum time to wait for time server responses 2 seconds
Data timestamp is set to instantaneous meter
Time synchronization signal loss
time
Timezone and DST Supported
Time quality bits
LeapSecondsKnown Supported, default value 0
ClockFailure Supported, default value 0
Supported, dependant on Clock ION module
ClockNotSynchronized1 Enable NTP Time Sync register setting.
SNTP response validated attributes
Leap year indicator does not equal 3 Yes
Mode is equal to SERVER Yes
Originate timestamp equals value sent by SNTP
Yes
client as transmit timestamp
RX/TX timestamp fields checked Yes
SNTP version 3 or 4 supported Yes
Time stamps
Item Value/comments
To control a meter’s digital output through IEC 61850, navigate to the GGIO
module for that digital output and set the ISC Control Mode register to 61850 CTVAL.
To have the meter control the digital output, set the ISC Control Mode register to
ION input. When the meter controls the digital output IEC 61850 control commands
will be ignored.
For detailed information about ION modules, refer to the ION Reference.
Analog values
Measurements
Units
Current 1A
Voltage 1V
Angle 1 degree
Rate 1%
Deadbands
Default deadband values are provided in the ICD file, and can be modified using
an IEC 61850 configuration tool. Unlike IEC 61850-7-3, which specifies deadband
values be expressed as a percentage, deadband values in ION devices are
expressed as integer values in the same physical units as the deadbanded data.
7-4 None
28 Definition of APC Na
30 Control parameter T Y
31 Typo Na
32 Typo in syntax Na
35 Typo syntax Control time Na
47 “.” in LD name? Y
1 Syntax Na
5 tExtensionAttributeNameEnum is restricted Na