IEC850
IEC850
IEC850
IEC850
v.7.10
© 2013 Ing. Punzenberger COPA-DATA GmbH
Distribution and/or reproduction of this document or parts thereof in any form are permitted solely
with the written permission of the company COPA-DATA. The technical data contained herein has been
provided solely for informational purposes and is not legally binding. Subject to change, technical or
otherwise.
Contents
2. IEC850 ......................................................................................................................................... 4
2.1 IEC850 - Data sheet ..................................................................................................................................... 5
2.2 Driver history .............................................................................................................................................. 6
2.3 Requirements .............................................................................................................................................. 8
2.3.1 PC.................................................................................................................................................. 9
2.4 Configuration .............................................................................................................................................. 9
2.4.1 Creating a driver ........................................................................................................................... 9
2.4.2 Settings in the driver dialog ........................................................................................................ 11
2.5 Creating variables...................................................................................................................................... 29
2.5.1 Creating variables in the Editor .................................................................................................. 29
2.5.2 Addressing .................................................................................................................................. 32
2.5.3 Driver objects and datatypes ..................................................................................................... 35
2.5.4 Creating variables by importing ................................................................................................. 40
2.5.5 Treibervariablen ......................................................................................................................... 50
2.6 Driver-specific functions ........................................................................................................................... 55
2.7 Reporting .................................................................................................................................................. 64
2.7.1 Unbuffered Reporting ................................................................................................................ 66
2.7.2 Buffered Reporting ..................................................................................................................... 68
2.7.3 Dynamic Data Sets ...................................................................................................................... 70
2.8 Driver commands ...................................................................................................................................... 71
2.9 Error analysis ............................................................................................................................................. 73
2.9.1 Analysis tool ............................................................................................................................... 73
2.9.2 Check list..................................................................................................................................... 75
2.10 Appendix A - Description of the ‘Functional Constraints’ (FCs): ............................................................... 76
2.11 Appendix B - Abbreviations for data object/data attribute ...................................................................... 77
2.12 Appendix C - Conformance statement ...................................................................................................... 90
2.12.1 Protocol implementation conformance statement (PICS) ......................................................... 90
2.12.2 Model implementation conformance statement (MICS) ........................................................... 98
2.13 Appendix D - PIXIT for COPA-DATA IEC61850 Client ................................................................................. 98
3
Welcome to COPA-DATA help
GENERAL HELP
If you cannot find any information you require in this help chapter or can think of anything that you
would like added, please send an email to documentation@copadata.com
(mailto:documentation@copadata.com).
PROJECT SUPPORT
You can receive support for any real project you may have from our Support Team, who you can contact
via email at support@copadata.com (mailto:support@copadata.com).
If you find that you need other modules or licenses, our staff will be happy to help you. Email
sales@copadata.com (mailto:sales@copadata.com).
2. IEC850
Communication between the driver and the PLC is based on the IEC 61850 protocol with client/server
services via TCP/IP (A1/T1 profile). The driver acts as a client (master) when communicating.
4
IEC850
Attention
Configurations that have been edited with a driver from version 3400 cannot be
opened with older drivers anymore.
General:
PLC manufacturer ABB; Siemens; IEC; SAT; Sprecher Automation; Kalki; GE Multilin;
Driver supports:
Addressing: Address-based -
Addressing: Name-based x
Spontaneous x
communication
Polling communication x
Online browsing x
Offline browsing x
Real-time capable x
Blockwrite -
5
IEC850
Modem capable -
Serial logging -
RDA numerical -
RDA String -
Prerequisites:
Hardware PLC -
Software PLC -
Requires v-dll -
Platforms:
6
IEC850
4/11/2007 400 Support for all models (SBO) of the control model
2/1/2010 3700 off-line import also from *.cid and *.scd files
2/17/2010 3700 Origin is sent to RT before all other attributes of a data object from
Report
3/24/2010 3900 possibility to split up Select and Operate for Command Processing
module
11/8/2010 4000 Off-line Import: LNs embedded directly into IEDs without LDs are
ignored
7
IEC850
The versioning of the drivers was changed with zenon 7.10. From now on, there is a build number that is
valid throughout all versions. This is the number in the 4th position of the file version, for example:
7.10.0.4228 means that the driver is for version 7.10 service pack 0, and has the build number 4228.
Expansions or error rectifications will be incorporated into a build in the future and are then available
form the next consecutive build number.
Example
A driver extension was implemented in build 4228. The driver that you are using is build
number 8322. Because the build number of your driver is higher than the build number of
the extension, the extension is included. The version number of the driver (the first three
digits of the file version) do not have any significance in relation to this. The drivers are
version-agnostic
2.3 Requirements
This chapter contains information on the requirements that are necessary for use of this driver.
8
IEC850
2.3.1 PC
XML Lite, which is part of Microsoft Internet Explorer 7.0, is necessary; xmllite.dll can also be
downloaded separately from the Microsoft website.
This driver supports a connection via the standard network card of the PC. Make sure that the PLC and
the PC are in the same network range and that the subnet masks are set accordingly on both devices.
2.4 Configuration
In this chapter you will learn how to use the driver in a project and which settings you can change.
Info
Find out more about further settings for zenon variables in the chapter Variables
(main.chm::/15247.htm) of the online manual.
1. Right-click on Driver in the Project Manage and select Driver new in the context menu.
9
IEC850
2. In the following dialog the control system offers a list of all available drivers.
10
IEC850
4. Confirm the dialog with OK. In the following dialog the single configurations of the drivers are
defined.
Only the respective required drivers need to be loaded for a project. Later loading of an additional driver
is possible without problems.
Info
For new projects and for existing projects which are converted to version 6.21 or higher,
the following drivers are created automatically:
Internal
MathDr32
SysDrv.
General
11
IEC850
Parameter Description
Mode Allows to switch between hardware mode and simulation mode
Hardware:
Keep update list Variables which were requested once are still requested from the control
in the memory even if they are currently not needed.
This has the advantage that e.g. multiple screen switches after the screen
was opened for the first time are executed faster because the variables
need not be requested again. The disadvantage is a higher load for the
communication to the control.
12
IEC850
Variable image This option saves and restores the current value, time stamp and the states
remanent of a data point.
Fundamental requirement: The variable must have a valid value and time
stamp.
The following states are not restored at the start of the Runtime:
SELECT(8)
WR-ACK(40)
WR-SUC(41)
Global Update time Aktiv: The set Global update time in ms is used for all
variables in the project. The priority set at the variables is not used.
Inactive: The set priorities are used for the individual variables.
Priority Here you set the polling times for the individual priorities. All variables with
the according priority are polled in the set time. The allocation is taken
13
IEC850
place for each variable separately in the settings of the variable properties.
The communication of the individual variables are graduated in respect of
importance or necessary topicality using the priorities. Thus the
communication load is distributed better.
For Set value, Advising of variables and Requests, a read cycle is immediately triggered for all drivers -
regardless of the set update time. This ensures that the value is immediately available for visualization after
writing. Update times can therefore be shorter than pre-set for cyclical drivers.
Parameters Description
Configuration file name Name of the file in which the driver-specific configurations
are saved. Click on the ... button to open the dialog for
selecting a drop folder.
Deactivate standard double Inactive : The values of double point values are
point value mapping adjusted to the operating elements of zenon. Use this
configuration if you want to use the modules of zenon
14
IEC850
Energy.
Default: Inactive
Use identification for Inactive : The variable name is used for addressing.
external name:
Active: The driver uses the entries of the
'identification' variable property for addressing.
Default: Inactive
Do not purge BRCB buffer at Active: The buffer of the BRCBs are not deleted when
start the connection is first established after Runtime has
started.
Requirements: For this BRBC, the last entry ID received
has been saved.
Originator category (orCat) The driver sends configured orCat values as commands.
Possible settings:
1 - Bay-control
2 - Station-control
3 - Remote-control
4 - Automatic-bay
5 - Automatic-station
6- Automatic-remote
7 - Maintenance
Default: 2- Station-control.
Directory for file transfer Directory for file transfer. All files loaded are saved in
this folder.
15
IEC850
The following is applicable to the Inactive setting of Deactivate standard double point value
mapping:
The driver depicts the double point values for Runtime according to the zenon column (stVal : CODED
ENUM in DPS and DPC Classes, IEC 61850-7-3).
off 1 01 0x40 0
on 2 10 0x80 1
bad state 3 11 0xC0 3
on 1 128
Read more about this in the chapter driver-specific functions (on page 55) -> Mapping.
16
IEC850
Connections
The connections of the IEC850 driver are set in the Connections tab of the driver dialog.
Parameters Description
Server List of connectiosn to the IEC 61850 server that have already been
configured (to the control objects).
New Creates a new connection to an IEC 61850 server. Opens the 'Server'
dialog.
17
IEC850
Server
Clicking on New or Edit in the dialog connection (on page 17) opens the dialog for the configuration of a
connection to an IEC 61850 server:
Parameters Description
Net address Corresponds to the Net address property in variable configuration.
Server name Freely definable name. Is used for the names of variables when variables
are imported.
Polling rate Defines the update frequency in milliseconds. The driver supports this rate
to poll data that is not in active reports. At this a possible failure of the
IEC61850 server is also considered.
18
IEC850
Default: 1000
: At least one variable should always be polled even if all data of the
project is present in the report. Otherwise a problem with the IEC61850
server cannot be detected if the TCP/IP connection still exists. Create a
*LLN0/Mod/cltModel[CF] variable for this and ensure that the variable
is always signed in with the driver.
IP address Alternative IP address. If the connection to the first IP address fails, the
(redundant) alternative IP address will be used after the net error waiting time has
passed (20-30 sec., depending on the network). The
alternative address will be kept until the driver is restarted (via driver
functions or restart of the zenon Logic Runtime) or until the connection
fails. Then, the first IP address will be used again.
Calling AP title Settings according to ISO 8650-1(ACSE), the value for the OSI ACSE
AP Title of the client in the Universal Identifier notation.
Should not normally be amended.
19
IEC850
Use Authentication Activate this checkbox if you want to use authentication according
to ISO 8650-1.
GetNameList on DO Active: The driver reads the Objekt Model by requesting data
objects (DO) for each available Logical Node pro in every
server in the IEC61850 standard defined Functional
Constraint (FC).
Default: inactive
Max. auto used Maximum number of Unbuffered Reports which the driver
URCBs activates at automatic allocaton, i.e. in addition to RCBs which were
configured in dialog RCB assignment/dynamic datasets.
Default: 1
Use preconfigured Active: Trigger options which are pre-configured in the IEC61850
TrgOps Server are used. In this case, the driver does not write the TrgOps
attribute to the Report Control Block during assignment.
inactive: the driver writes the TrgOps attribute during the activation
20
IEC850
of each RCB.
TrgOp: data-change
TrgOp: quality-change
TrgOp: data-update
TrgOp: integrity
TrgOp: general-interrogation
Use report ID for Active: The report ID is used instead of the report name in the client
RCB assignment configuration dialog for static RCB assignment.
Default: inactive
RCB assignment/dynamic Static Report Control Block allocations and settings for Dynamic Data Sets.
datasets
: If you have activated 'Use redundancy' in your zenon project,
(Network active property activated and Server and Standby
configured), you must create two entries here: one for the server and one
for the standby.
New Creates a new entry in the list. Opens the client configuraton
dialog.
Edit Opens the Client configuration dialog to edit the selected entry.
21
IEC850
Info
OSI value (ACSE)
The driver uses the following OSI selector values:
<P type="OSI-AP-Title">41,999,1,1</P>
- coded in accordance with Basic Encoding Rules (IEC 8825) for Object Identifier - corresponds
to standard values of the Universal Identifiers in the Called AP title.
<P type="OSI-AE-Qualifier">12</P>
- corresponds to standard values in the Called AE qualifier.
<P type="OSI-PSEL">00000001</P>
set in the driver; cannot be changed
<P type="OSI-SSEL">0001</P>
set in the driver; cannot be changed
<P type="OSI-TSEL">0001</P>
set in the driver; cannot be changed
22
IEC850
Client configuration
Clicking on New or Edit in the RCB assignments/dynamic datasets list in the server dialogs
(on page 18) opens the dialog for the client configuration settings:
23
IEC850
Parameters Description
Hostname Name of the computer on which the driver is running that receives the
reports:
in the zenon network: The computer name of the project server or project
standby.
static RCB assignment Settings for the static assignment of RCBs (the same for unbuffered and
buffered RCBs).
DataSet Displays the dynamic data set (if the RCB was allocated one).
New Creates a new entry in the list. Opens the 'statically assigned RCB' dialog
to create a new entry with a report ID (or a name) - you can either enter
it manually or browse the server
and if necessary with dynamic data set (is taken from the lower list).
Edit Opens the 'statically assigned RCB' dialog to edit the selected entry.
For more information, see dynamic data sets (on page 70).
24
IEC850
Name Displays the data sets that have already been enterd - that are already
present in the upper list.
Edit Opens the 'dynamic DataSet configuration' dialog to edit the selected
entry.
25
IEC850
Parameters Description
RCB name/report ID The name or the ID of the report (buffered or
unbuffered). Must correspond exactly to the name/report
ID in the PLC (IEC61850 server).
dynamic Dataset You can also optionally select a data set from the drop-
down list of the data sets that have already been entered
into the 'dynamic DataSet configuration (on page 27)'
dialog.
This list is displayed after you have browsed RCBs online on the IEC 61850 server:
26
IEC850
27
IEC850
Parameters Description
Name Name of the data set.
Add Starts the browsing of data objects dfrom the variable list
of the zenon project and displays all data objects for
which a variable has already been created in the project.
The list is displayed to you after you have prepared suitable project variables:
28
IEC850
The diriver displays all data objects - that are appropriate for data reporting - from the variable list of
the zenon project, except those that have already been selected for the data set. In the upper list, you
can filter and select the variable filters (multiple selection is also possible) and add these to the lower
list. Objects that have already been selected are kept. Use the OK button to add the selected variables to
the members of the dynamic data set.
as simple variables
in arrays (main.chm::/15262.htm)
VARIABLE DIALOG
29
IEC850
1. Select the New variable command in the Variables node in the context menu
30
IEC850
Property Description
Name Distinct name of the variable. If a variable with the same name already
exists in the project, no additional variable can be created with this name.
If no driver has been opened in the project, the driver for internal
variables (Intern.exe (Main.chm::/Intern.chm::/Intern.htm)) is
automatically loaded.
Driver object type Select the appropriate driver object type from the drop-down list.
(cti.chm::/28685.h
tm)
31
IEC850
Data type Select the desired data type. Click on the ... button to open the selection
dialog.
Array settings Expanded settings for array variables. You can find details in the Arrays
chapter.
Addressing options Expanded settings for arrays and structure variables. You can find details
in the respective section.
Automatic element Expanded settings for arrays and structure variables. You can find details
activation in the respective section.
If a change is made to a data type that does not support the set signal range, the
signal range is amended automatically. For example, for a change from INT to SINT, the signal
range is changed to 127. The amendment is also carried out if the signal range was not inherited from
the data type. In this case, the measuring range must be adapted manually.
2.5.2 Addressing
The addressing is based on the variable names.
32
IEC850
Name Description
Name Freely definable name
The name is used for addressing the variables and must be clear in each
control system project. As a result, the server name is also taken into account if the
driver identifies the connection with the help of the Net Address property.
Identification Enter any desired text; for example resource name, comments, ...
This address refers to the network address in the connection list of the driver
configuration. It defines the IEC 61850 server on which variables are saved.
String length Only available for String variables: Maximum number of characters from which a
variable can exist.
Driver object Dependent on the type of variable, the object type is selected when the variable is
type created; the type can be changed here later. For more information, see also the
driver objects (on page 35).
Data type Data type of variables that were selected when the variable was created; the type
can be changed here later.
If you subsequently change the data type here, you must check all
variable properties, such as value range for example, and change them if necessary.
The server name (on page 18) is separated by the exclamation mark (!) from the following
identifiers.
33
IEC850
Only if an identifier is a structure, their elements are separated by a dot (.); for example:
SERVER!LD/LN/DATA/DataAttr.item[FC].
Parameters Description
SERVER Freely definable name of the server.
Name should make sure that all variable names are identical.
Use the same names as defined in driver dialog Dialog Server (on page
18). The driver however does not recognize the used connection via the Server name
but via settings the Net address.
DATA Name of the 'data object', see Appendix B - data objects / data attributes
DataAttr Name of the 'data attribute', see Appendix B - data objects / data attributes
FC "functional constraint" of the "data attribute", see Appendix A - Description of the Functional
Constraints (FCs)
Attention
The naming convention for variables complies with the ObjectReference defined in
standard IEC61850-7-1.
In the standard a slash (/) is only used as separator between LD and LD and otherwise
separated by dots (.). If DATA or DataAttr is a structure, dots make it impossible to
differentiate between DATA and structure. Therefore an own naming conversion is used
for the variable addressing.
The logical node "XCBR1" (circuit breaker 1) has, among other things, a data object "Pos", which is a CDC
(Common Data Class) "Controllable Double Point" (DPC). This data point 'Pos' has, in turn, attributes
'stVal', 'q' and 't', the name and semantics of which is specific due to its CDC, which is defined in
IEC61850-7-3.
34
IEC850
All objects in the variable model are constructed in this way. For this reason, the driver knows, for
example, that the attributes 'q' and 't' contain quality and time stamps for the variables in 'stVal'. This
allows access to all attributes of the each object in the variable model. Existing values for quality and
time stamp are automatically assigned to the actual values of the driver.
Operate command: Thanks to the specific variable nomenclature, the driver automatically notices that
an operate command is to be created if a variable is written to, for example with the name
'*/Oper.ctlVal[CO]' (Operation.ControlValue). It the automatically sends the required sequence of
telegrams to the control object.
Time stamp and quality attribute are always parts of variables in zenon. Variables with attributes 'q' and
't' do not need to be created separately. The driver automatically uses the time stamp and the quality of
the data object for its variables with FC = ST and MX (FC stands for Functional Constraint (on page 76)).
Without taking into account whether a variable for attribute 't' was created, the time stamp received is
used for all ST and MX variables, for example the stVal variable for CEL, AML or Historian. Selected
quality bits that are received in attribute 'q' are also assigned the status bits of the stVal variable (see
also Driver-specific functions (on page 55)).
Driver objects
35
IEC850
36
IEC850
All variables in zenon are derived from IEC data types. The following table compares the IEC datatypes
with the datatypes of the PLC.
37
IEC850
INT8 SINT 10
INT8U USINT 9
INT16 INT 1
INT16U UINT 2
INT24 DINT 3
INT24U UDINT 4
INT32 DINT 3
INT32U UDINT 4
INT128 DINT 3
FLOAT32 REAL 5
FLOAT64 LREAL 6
ENUMERATED INT 1
EntryTime LREAL 6
38
IEC850
The property Data type is the internal numerical name of the data type. It is also used
for the extended DBF import/export of the variables.
MMS Bitstring: The data attribute types that were assigned to the MMS Bitstring in accordance
with the standard (see IEC61850-8-1), CODED ENUM, PACKED LIST und TrigerConditionsfor
example, correspond to the UDINT data type in zenon. Whereby in the case of PACKED LIST and
TrigerConditions, the bit 0 has the highest value in its octet. The driver also allows bit string
variables with the data type STRING instead of UDINT to be inserted manually. The value of the string
only contains the characters "0" and "1" in a sequence that is the same as that of the bits defined in the
standard and only in the length of the bit string, for example the value of the TrgOps Attribute -
Bitstring(6) - as String "011111" (in UDINT=124) means that all trigger condition bits except bit 0 -
'Reserved' are set and the value "000010" (in UDINT=8) - only bit 4 - 'intergity'.
If there is an array level in the IEC61850 Data Classs, this level is placed at the end of the variable
structure for display in zenon. This means that, from an ARRAY OF that may have nested structures,
there are one or several arrays of scaled values in the zenon variable model. This remapping is carried
out at the start of the configuration time during online import and in the runtime environment during
the allocation between the zenon variable list and the IEC61850 object model.
As a result of this, there is the restriction that only one array level is supported. The support for arrays is
also limited to the data attribute.
The data attribute HaAmp.har of the Common Data Class (CDC, -7-3) MHAN - as defined in the IEC61850
standard: ARRAY[0..numHar] of Vector - becomes the following array in zenon:
In addition, there are of course also the arrays for ang.i, mag.f and mag.i.
39
IEC850
Info
You can find details on the import and export of variables in the Import-Export
(main.chm::/13028.htm) manual in the Variables (main.chm::/13045.htm) section.
Online import
Variables in a zenon project can be created with the import of the driver. The driver can browse the
variable list of the IEC 61850 server.
Attention
If Runtime is running on the same computer at the same time, the variables in the editor
cannot be imported by the PLC, because the driver in Runtime uses the given settings for
communication.
You call up the import using the context menu of the driver in the driver list.
In the dialog that opens, select the PLC Browsing option and select a server from which the variables are
to be browsed.
40
IEC850
The connection to the server is established and the list of existing data points (LDs, LNs, data objects,
data attributes) is read.
If the reading in has ended, an important dialog opens in which you can filter the browsed variables
(capitalization, for example *XCBR1*stVal*), select them (including multiple selection) and add them
from the upper to lower list.
You create the selected variables in the project using the OK button.
Attention
The driver creates variables with default value ranges, for example a UDINT with <0...
4294967295> and a LREAL with <-1000..1000>, which may not correspond to the value
ranges of the attributes, for example stVal-attribute UDINT <0..3> or t-attribute
LREAL<0.. 2147483647> with three decimal places for milliseconds. Therefore ensure
after import after that all variables have the correct value range properties and the string
is the right length.
As a result of the limitation of only one array level being supported (on page 37), the support of arrays is
also limited to the data attributes.
The data attribute HaAmp.har of the Common Data Class MHAN - as defined in the IEC61850 standard:
ARRAY[0..numHar] of Vector - becomes up to four arrays in zenon, with the same respective
number of elements:
*/HaAmp.har.ang.f[MX][0..count-1]
*/HaAmp.har.ang.i[MX][0..count-1]
*/HaAmp.har.mag.f[MX][0..count-1]
*/HaAmp.har.mag.i[MX][0..count-1]
Offline import
Variables can also be imported offline. The following file endings are accepted:
41
IEC850
*.xml
*.scl
*.icd
*.cid
*.scd
The driver only imports DOI elements online. The ReportControl properties (report control block)
and SettingControl (Setting Control Block) are not supported during offline import. You can
create the variables for theses attributes by means of online import or manually.
Attention
Directly-linked logical nodes are ignored by the IED during offline import. This does not
affect Logical Devices. The driver can only import attributes from the object model that
are fully compliant with the IEC61850 standard.
42
IEC850
3. The following steps for the selection of variables are similar to online import.
43
IEC850
Attention
When importing/overwriting an existing data type, all variables based on the existing
data type are changed.
There is a data type XYZ derived from the type INTwith variables based on this data
type. The XML file to be imported also contains a data type with the name XYZ but
derived from type STRING. If this data type is imported, the existing data type is
overwritten and the type of all variables based on it is adjusted. I.e. the variables are now
no longer INT variables, but STRING variables.
DBF Import/Export
Info
Import and Export via CSV or dBase supported; no driver specific variable settings, such
as formulas. Use export/import via XML for this.
2. in the drop-down menu of Extended export/import... select the Import dBase command
44
IEC850
Info
Note:
Driver object type and data type must be amended to the target driver in the DBF file in order for
variables to be imported.
2. in the drop-down menu of Extended export/import... select the Import dBase command
Attention
DBF files:
must correspond to the 8.3 DOS format for filenames (8 alphanumeric characters for name, 3
character suffix, no spaces)
must be stored close to the root directory in order to fulfill the limit for file name length including
path: maximum 255 characters
Info
dBase does not support structures or arrays (complex variables) at export.
The dBaseIV file must have the following structure and contents for variable import and export:
45
IEC850
Attention
dBase does not support structures or arrays (complex variables) at export.
conform with there name to the 8.3 DOS format (8 alphanumeric characters for name, 3 characters
for extension, no space)
DESIGN
KANAL_R C 128 The original name of a variable that is to be replaced by the new
name entered under "VARIABLENNAME" (field/column must be
entered manually).
KANAL_D Log 1 The variable is deleted with the 1 entry (field/column has to be
created by hand).
DATENART C 3 Data type (e.g. bit, byte, word, ...) corresponds to the data type.
KANALTYP C 3 Memory area in the PLC (e.g. marker area, data area, ...)
corresponds to the driver object type.
BAUSTEIN N 3 Datablock address (only for variables from the data area of the
PLC)
ADRESSE N 5 Offset
46
IEC850
LES_SCHR R 1 Write-Read-Authorization
0: Not allowed to set value.
1: Allowed to set value.
UPDATERATE F 19 Update rate for mathematics variables (in sec, one decimal
possible)
not used for all other variables
HDRATE F 19 HD update rate for historical values (in sec, one decimal possible)
DRRATE F 19 Updating to the output (for zenon DDE server, in [s], one decimal
possible)
47
IEC850
VOMSTANDBY R 1 Get value from standby server; the value of the variable is not
requested from the server but from the standby-server in
redundant networks
ADJZENON C 128 Linked VBA macro for reading the variable value for non-linear
value adjustment.
ADJWVBA C 128 ed VBA macro for writing the variable value for non-linear value
adjustment.
Attention
When importing, the driver object type and data type must be amended to the target
driver in the DBF file in order for variables to be imported.
LIMIT DEFINITION
48
IEC850
ALARM1 R 1 Alarm
INVISIBLE1 R 1 Invisible
49
IEC850
2.5.5 Treibervariablen
The driver kit implements a number of driver variables. These are divided into:
Information
Configuration
Statistics and
Error messages
The definitions of the variables defined in the driver kit are available in the import file drvvar.dbf (on
the CD in the directory: CD_Drive:/Predefined/Variables) and can be imported from there.
Variable names must be unique in zenon. If driver variables are to be imported from drvvar.dbf
again, the variables that were imported beforehand must be renamed.
Info
Not every driver supports all driver variants.
For example:
Driver variables for the polling cycle only for pure polling drivers
Connection-related information such as ErrorMSG only for drivers that only edit one connection at
a a time
50
IEC850
INFORMATION
51
IEC850
CONFIGURATION
52
IEC850
53
IEC850
STATISTICS
MaxUpdateTimeNormal UDINT 56 Time since the last update of the priority group
Normal in milliseconds (ms).
MaxUpdateTimeHigher UDINT 57 Time since the last update of the priority group
Higher in milliseconds (ms).
MaxUpdateTimeHigh UDINT 58 Time since the last update of the priority group
High in milliseconds (ms).
MaxUpdateTimeHighest UDINT 59 Time since the last update of the priority group
Highest in milliseconds (ms).
54
IEC850
ERROR MESSAGES
ErrorTimeS STRING 2 Time (in seconds since 1.1.1970), when the last error
occurred.
RdErrPrimObj UDINT 42 Number of the PrimObject, when the last reading error
occurred.
RdErrStationsName STRING 43 Name of the station, when the last reading error occurred.
RdErrBlockCount UINT 44 Number of blocks to read when the last reading error
occurred.
RdErrHwAdresse DINT 45 Hardware address when the last reading error occurred.
RdErrDatablockNo UDINT 46 Block number when the last reading error occurred.
RdErrMarkerNo UDINT 47 Marker number when the last reading error occurred.
RdErrSize UDINT 48 Block size when the last reading error occurred.
ASSOCIATION
The driver only opens a connection to a Logical Device if at least one variable from the LD is created in the
project.
55
IEC850
After communication is broken off (due to a network failure, for example), the connection to the Logical
Device is then only reestablished automatically if at least one variable of the LD is being polled.
The driver supports the 'Direct Operate' and 'Select Before Operate' commands (SBO) with normal and
increased security. The driver automatically checks the actual Control Model and executes this command
accordingly.
If a value is set to a project variable that corresponds to the item ctlVal in a data attribute with the name
'Oper' and has the Functional Constraint CO or SP (*/Oper.ctlVal[CO|SP]), the driver automatically checks
which Control Model is required for a command with this data object.
To do this, the attribute */ctlModel[CF] of this data object is read off first. Depending on the value of
this attribute, the corresponding command is executed and the respective Control Model is used:
Info
The driver reads the ctlModel attribute from the server to execute the command, but
the driver does not transfer the ctlModel value to Runtime automatically. This includes
situations where a variable was created for the ctlModel. If a variable was created, it is
updated in accordance with the polling rate that is defined in the driver configuration.
Select command with normal security: read from */SBO[CO], write to */Oper[CO].
56
IEC850
In addition, the driver supports manual selection and cancellation, but only via the Command input
module in zenon.
If the command sends a command and the Select Before Operate property is active, the driver
carries out a select - in accordance with the ctlModel of the same object. This only applies for
Model=2 or 4. The values of the ctlModel=0, 1 or 3 are treated as a negative select response.
Select Before Operate means the property for the Oper.ctlVal variable in zenon and
must not be confused with the SBO attribute,
If the IEC 61850 server responds positively to the select, the driver saves the information on the selected
data object and in the following command (from the second stage of the command input), the driver
only executes the operate.
If the command is cancelled from the second stage, the driver sends a cancel.
The driver ignores the Select Before Operate property of the Oper.ctlVal variables if the value
of ctlVal is set directly and not replaced by a command input action.
The driver automatically creates the values of the ctlNum attributes. If a value is set to the project
variable and to the attribute */Oper.ctlVal[CO|SP] accordingly, the driver automatically
increases the value of */Oper.ctlNum[CO]. The driver restarts incrementing the ctlNum at 0 if the
value has reached 127.
The driver also counts ctlModel=0 (no action). For this model, the ctlNum variable is not updated in
Runtime, because in fact - in accordance with the standard (IEC61850-7-3) - the ctlVal attribute
should not exist.
STATE INFO
The IEC61850 server keeps AdditionalCauseDiagnosis ready for negative responses to a command
(AddCause in LastApplError structure). The possible values of the AddCause service parameter are listed
in the IEC 61850-7-2. The driver can relay the received AddCause to zenon and also the current state of
the current command (for example: Select/Operate/Cancel) and provide information on whether the
command was successful.
57
IEC850
The driver provides this information in 'State Info' driver object variables (see Driver objects (on
page 35)) if these have been created. Variables that relay the stage of the current command can be
created for each */Oper structure.
*/Oper.AddCause: After a failed command, the value displays error information that it has
received from the PLC.
You can create the following status variables for the variable
'PLC-Marker'-BOOL 'GE650!GEDeviceF650/XCBR1/Pos/Oper.ctlVal[CO]':
Case 1:
If you set the value to */Oper.ctlVal directly or the variable does not have the SBO property, the
sequence of states is as follows:
58
IEC850
If you use the two-stage command input for */Oper.ctlVal with the SBO property, the sequence of
states for each command serve (for select, operate and cancel) is the following:
2. */Oper.ControlState = x
For this, the following applies: x=1 or 2 or 3, depending on the command service.
Attention
The State Info variables do not have any value if no command was given. To evaluate
status variables, you must first send a value to */Oper.ctlVal[CO|SP].
There are two methods for setting check conditions with the following Operate or SelectWithValue
commands:
1. Check condition can be pre-defined by setting a value for */Oper.Check[CO]. The current value
of this attribute is used for the command service parameter.
: The Check attribute is a PACKED LIST (MMS bit string) with 2 bits. In accordance with
IEC61850-8-1 8.1.3.5, the first member of the PACKED LIST is mapped to bit(0) and this bit
should be the highest value (most significant) bit of the octet. This means that the valid target
values for the Check attribute are 0x80 (synchrocheck), 0x40 (interlock-check), 0xC0 (both check
bits) and 0x00.
2. In zenon by setting in the command input: Action - Qualifier of Command property. The
valid target values are 2 - synchrocheck (inverted 01b), 1 - interlock-check (inverted 10b), 3 (both
bits bits) and 0.
ORIGINATOR
The originator attribute orCat (Category) and orIdent (Identification) show which originator (for example a
client that is on bay level) caused the last change of data (such as issuing a command).
The Origin attributes are an obligatory part of Oper, SBOw and Cancel services and optional in some
cases, such as the 'Pos' data object. To analyze the originator of the values received in Runtime, for
example */Pos/stVal[ST], you can create project variables with corresponding names in zenon:
59
IEC850
When a Reports is received, the driver forwards this to Runtime before it forwards the other attributes of
the received data object (if only one origin with Functional Constraint ST exists in the data object that was
reported).
You can use orCat or orIdent variables to compile a dynamic limit value text for a reported
stVal variable.
Info
When a command is executed, the driver sets the following values for the originator
attribute in SBOw, Oper und Cancel:
orCat = 2 (station control)
You can adapt the value for orCat in the Basic Settings (on page 14).
orIdent = 'zenon: <Computer name> (string between quotation marks - CHAR(27)) ,
e.g. zenon: MyPC'
In accordance with the IEC61850-7-3 standard, the attribute stVal has, in common data classes Double
Point Status (DPS) and Controllable Double Point (DPC), the data type CODED ENUM with the value range:
intermediate-state (00) | off (01) | on (10) | bad-state (11). The driver therefore waits until a Double Point
attribute of the data type CODED ENUM is mapped to the communication protocol as an MMS of the
bit string data type and thus can have the following values: 0x00, 0x40, 0x80 and 0xC0. This
basic data type is permitted in the SCL language with the name 'Dbpos' (IEC61850-6 chapter 9.5.4.2
Attribute basis types). In zenon, it corresponds to a variable with UDINT data type (see Assignment of
data types (on page 37)).
As in the driver configuration, the option 'Deactivate standard double point value
mapping' remains inactive by default. To use the modules from zenon Energy, for example the
command input functions, the driver assigns values of the stVal attributes of DPS and DPC in accordance
with the following table:
60
IEC850
position value zenon Dbpos value - zenon Dbpos value - zenon Wert - value
STRING UDINT unmapped mapped
Difference '00' 0 2
position (00)
The driver only converts values for variables with the name *stVal and data type UDINT.
The driver can support received attributes 'q' and 't' in corresponding project variables if these have
been created.
However the driver always assigns the selected Quality Bits (of the 'q' attribute) and TimeQuality Bits (of
the 't' attribute) of the corresponding status bits to each zenon variable that was created for an
attribute of the data object and for which FC (on page 76)=ST or FC=MX, for example status bits of
stVal. The driver also assigns the value of the 't' attribute to the time stamp of all ST/MX variables of
the data object.
For example: Receiving the time stamp as a 't' attribute is used for the corresponding stVal variable in
the CEL. The driver automatically uses the time stamp and the quality of the data object for all its
variables that were created in the project. For this reason, no variables need to be created separately
for the attributes 'q' and 't', except if you want to analyze quality bits that have not been assigned any
status bits.
Info
The driver takes into account the precision value received from the TimeQuality. If this
value is specific (all bits), the driver shortens the time value accordingly.
For example: Precision value< 10 bit: the driver shortens the time value received down to
the milliseconds.
The selected Quality and TimeQuality bits are assigned to the status bits of the variables of the data
objects that respond as follows:
61
IEC850
ClockFailure T_INVAL (invalid time) The value of the 't' attribute is ignored
and - stVal has the time stamp of the local
T_INTERN (real time PC time.
internal)
ClockNotSynchronize T_INVAL (invalid time)
d
and
T_EXTERN (real time
external)
The variables of the data object without 't' attribute (or with 't' value of 0) and the variables with other
FC (on page 76) as ST/MX receive the time stamp of the local PC time.
Info
You can evaluate status bits (such as T_INVAL) by using a combined element or
reaction matrix ('multi' type) and you can also filter in the CEL or AML.
FILETRANSFER
3. Delete file
62
IEC850
1. Create, in your zenon project, two file transferdriver object type string variables
with the corresponding network address:
a) The first variable, hereafter called the command variable, with the name
"SERVER!Command" can also be used to get files and to delete them.
b) The second variable with the name "SERVER!Directory" is only used for the result of
the folder query. It receives the folder content as legible text. For this reason, its size
should correspond to the maximum size of the file name (including the folder) in the
PLC.
2. For the command variable, set the value "DIR" (for the root directory) or "DIR
<file_spec>".
<file_spec> is a string that is sent to the server as a transfer parameter.
The folder variable contains the received folder content as legible text. One line of this text has
the following format:
To get a file from the server, set the value "GET <File name> for the command variable".
It is saved in the folder that was defined as Directory for file transfer in the driver
dialog basic settings (on page 14).
Files from a subfolder are also stored in the main folder.
To delete a file from the server, set the value "DEL <File name>". for the command variable".
63
IEC850
If the file was deleted successfully, the command variable changes its value to "DEL OK"
If errors occur when carrying out the file transfer, such as the server responding negatively, the
command variable changes its value to "XXX ERROR" (XXX = DIR, GET or DEL) and the driver optionally
writes an entry into the log file (see also error analysis (on page 73)).
LIMITATIONS
Only one array level is supported. The support for arrays is limited to the data attributes. It is not
possible to write array elements. When reading via polling or reporting, the whole Data Object that
contains the array attribute is read, as with other data attributes.
You can find the information on supported or required services in Appendix C (on page 90).
2.7 Reporting
Reporting was introduced by the IEC 61850 standard for spontaneous communication. The variables that
are linked with a successfully activated Report are no longer polled, but a reported by the PLC if there is
a value change. The variables that are reported if a client activates a special report control block (RCB)
are saved in the DatSet (Data Set) attribute of the RCB. The DatSet attribute is a visible string for the
name of the data object, the value change of which is reported spontaneously by the IEC 61850 server.
The IEC850 driver supports Buffered and Unbuffered Reporting with the data predefined in the PLC and
with Dynamic Data Sets - with the DatSet attribute, which was dynamically defined during activation of
the RCB.
As envisaged by the IEC 61850 standard, data objects with Report (FC) are available for a report
Functional Constraints:
Status (ST)
Measurands (MX)
In a data set:
Data objects with different FCs can be used together if the IEC 61850 server supports this.
64
IEC850
The data set and the Reporting Control Block that uses the data set must be in the same Logical
Device.
At least one variable of the Logical Node, in which the RCB is included, must have been created in
the project. Otherwise the driver does not take this Logical Node into account at all.
Exception: LLN0. The logical node LLN0 is automatically taken into account for each logical
device if the LD has at least one variable that was created in the project variable list.
Attention
If you configure the data sets in the PLC, you cannot add data attributes, only whole
data objects. Otherwise the time stamp and quality information in the driver cannot
be edited, because they are not sent by the PLC (see also standard 61850-7-2
14.2.3.2.2.9, figure 23)
The driver only activates reports in which data sets contain whole data objects.
The basic configuration of the reporting is carried out in driver configuration - server (on page 18). The
configured Buffered Reports in the driver configuration has a higher priority than the Unbuffered Reports. If
the activation of the Buffered Reports is not successful, the driver will instead activate Unbuffered Reports,
which contain the required objects as well as the data sets. If you do not want the driver to activate the
Unbuffered Reporting, set the max. auto used URCBs property in the driver configuration to 0.
If the driver cannot activate the reports for any reason, polling is used instead.
Info
When activating reporting, the driver can (optionally) write log entries, in which it can be
seen which variables are no longer polled but were successfully activated in reporting (in
the 'general text' column).
TRIGGER OPTIONS
The driver supports all Trigger Conditions, that are used to trigger the sending of the report. The
Trigger Options (TrgOps) define which value change of a data instance is reported. The driver attempts to
activate all configured TrgOps when the report is activated, but ignores write errors. If writing is
unsuccessful, the Trigger Options that were already configured in the SCL file (or by the IED program) of
the IEC61850 server are used.
You can activate/deactivate the individual Trigger Options via checkbox if you deactivate checkbox Use
preconfigured TrgOps. This settings is true for all RCBs.
65
IEC850
The TrigerConditions data attribute type that was assigned to the MMS Bitstring(6) in
accordance with the standard if the corresponding *TrgOps[RP|BR] variable was created during import,
corresponds to the UDINT data type in zenon by default (Motorola format, bit 0 highest value in its
octet). In addition, the driver allows such variables with the data type STRING instead of UDINT. The
value of the string has a length of 6 and only contains the characters "0" and "1" in a sequence that is
the same as that of the bits defined in the standard, for example the value as a string "011111" (as
UDINT=124=01111100b) means that all trigger condition bits except bit 0 - 'Reserved' are set and
the value "000010" (as UDINT=8=00001000b) - only bit 4 - 'intergity'.
1. Automatic assignment: All existing Reporting Control Blocks is checked in terms of content(data
sets). Reports that contain most variables of a project are registered first;
2. Static assignment: The driver uses the assignment of Reporting Control Blocks to the client
computer as it is defined in the driver configuration - client configuration (on page 23).
AUTOMATIC ASSIGNMENT
Automatic assignment works with pre-defined data sets and pre-configured assignments of data sets to
Reporting Control Blocks in the PLC.
Whilst the driver starts, all data sets that are present in the server are read off and ordered according to
their usability (number of project variables included). This sorting indicates the sequence in which the
driver attempts to activate free URCBs for reporting. At most, only as many URSBs are activated as are
defined in Drive configuration (on page 18) in the max. auto used URCBs property. All data
objects of the data sets that are successfully linked to an active RCB are no longer polled but are
reported in the event of a value change.
When activating reporting, the driver also recognizes reports with the same content; the name of these
reports can be different. Before the RCBs are sorted for the zenon project according to their usability,
the driver first sorts the data objects of the data sets of each RCB and compares them in order to avoid
duplicates. The following applies for conflicts when activating the Reporting:
66
IEC850
For the same reports - with identical or different sequences of the same data objects: Only one
report is activated.
If a report is already occupied by another client, the next free report is activated.
If all reports are already occupied by other clients, the data points are polled.
The */urcbMXA01/* variables are for information only. The variables for the RCB attributes need not
necessarily exist in the zenon project in order for reporting to work. The PLC also contains a data set
GEDeviceF650/LLN0$MMXU1$MX with the following content.
67
IEC850
This data set is assigned to RCB LLN0$RP$urcbMXA01 in the PLC. To do this, enter the name of the data
set in the DatSet attribute of this RCB.
The RCBs LLN0$RP$urcbMXA01 and LLN0$RP$urcbMXB01 are activated when the driver starts (if they
are still free).
Because there are no further suitable RCBs that have project variables in their datasets, the remaining
RCBs are not used. If the project also contains a variable that is included in the data set
GEDeviceF650/LLN0$eveGGIO1$ST, this would mean the LLN0$RP$urcbSTA01 is also activated.
STATIC ASSIGNMENT
For static assignment, the Reporting Control Blocks that can be used is defined and fixed in the driver
configuration - statically assigned RCB (on page 25). The driver attempts to activate all listed Reporting
Control Blocks, regardless of its content.
If, in the driver configuration, a Dynamic Data Set was entered, the driver in the PLC assigns this data set
to the RCB, by changing the value of the DatSet attribute of this block before the report is activated.
If no Dynamic Data Set was entered, the data set pre-defined in the PLC is valid (just as with automatic
assignment).
If a block was activated successfully, all data objects that are contained in its data set are no longer
polled but are reported if a value is changed.
There is no automatic allocation for Buffered Reporting. The allocation of BRCBs to the driver is always
static:
68
IEC850
Either using the driver configuration as described for static allocation with unbuffered reporting;
Or for reasons of compatibility with older drivers that were used to configure the SCL file using
the Report ID of the BRCBs (the Use Report-ID for RCB assignment should be
activated in the driver configuration).
If the assignments are to be configured in the SCL file, the assigned report ID (RptID) of the BRCB must
contain a string with the following nomenclature: 'zenon_Computername_*'; for example:
zenon_MyPC_Measurands1. The driver thwen uses the data set of RCB, which has a fixed link to the SCL
file. A Buffered Report can only be activated by a host. To prevent the driver from activating all Buffered
Reports and blocking access for other IEC61850 clients, they must be explicity defined in the driver
configuration (on page 9).
Irrespective of this, the basic behavior is the same as with Unbuffered Reporting.
BRCB BUFFER
The driver automatically deletes the content of the BRCB buffer if the connection was only
established after Runtime has been started.
If the connection is lost and re-established without Runtime being started again, the buffer is
retained and the data is collected.
The driver saves the last received entry ID for each BRCB every minute or if the driver is closed in a fle in
the Runtime data directory.
Because zenon supports redundancy (see zenon network) and a BRCB can only be activated once by a
PC, you must define separately,for the project server and the standby server, which PC is to activate
which report. The driver is started on both the server and the standby and checks the driver
configuration (Host name property), to see if it finds a configuration that corresponds to the
computer names that is running on Runtime.
For this reason, you need two copies of the Buffered Report in the event of a redundant configuration;
one for the driver that runs on the project server and and one for the driver that runs on the standby
server. You also create two entries in the RCB assignment (on page 25) list in the driver configuration.
69
IEC850
One with the computer name of the project server and one with the computer name of the standby
server. When entering the configuration of the project server, the first copy of the BRCB is entered and
the second copy when entering the configuration of the standby-server.
Attention
Even if you do not use redundancy, you must nevertheless define which reports are
used for the PC (Host name property) in the driver configuration on which zenon
Runtime runs.
Dynamic Data Sets lists data objects and are configured in the dynamic DataSet configuration (on page 27)
dialog. They can be used for Unbuffered Reporting and for Buffered Reporting, but only if static assignments
with RCBs were configured in the driver configuration - client configuration (on page 23).
If, in the driver configuration, a Dynamic Data Set was entered for an RCB, the driver in the PLC assigns
this data set to the RCB, by changing the value of the DatSet attribute before the Report is activated.
The creation of a dynamic data set can be checked in the Diagnosis Viewer (on page 73):
Before the statically assigned Reporting Control Blocks is activated, all dynamic data sets that are linked to
them via driver configuration - client configuration (on page 23) are compared to those on the IEC 61850
server. All Dynamic Data Sets avaialbe on the server that are not (or no longer) required are deleted. All
70
IEC850
Dynamic Data Sets not available on the server are created and all data sets that are avaialable on both
sides are checked to see that they have the same content. If the content is different, they are deleted
and created again. However, the driver only deletes the data sets that it has created itself. If the driver
cannot delete a data set, the asigned RCB is activated with the pre-existing data set.
The deletion of a dynamic data set can be checked in the Diagnosis Viewer (on page 73):
The dynamic data sets that were created in Runtime (using the CreateDataSet() service) receive a
client-depenent name on the server, in order for them to be easily found again. The nomenclature of
the Dynamic Data Set name is as follows:
LLN0$ZENON_hostname_datasetname. Here:
Hostname is the computer name of the clients is as defined in the driver configuration - client
configuration (on page 23) under Hostname and
datasetname is the name that was defined iin the driver configuration - Dynamic DataSet
configuration (on page 25).
If no Dynamic Data Set was entered in the RCB configuration of the driver, the pre-defined data set in the
PLC is not valid.
Driver commands are used to influence drivers using zenon; start and stop for example.
The engineering is implemented with the help of function Driver commands. To do this:
71
IEC850
Parameters Description
Drivers Drop-down list with all drivers which are loaded in the project.
Current state Fixed entry which has no function in the current version.
72
IEC850
Establish connection Establish connection (for modem drivers) Opens the input fields
with modem for the hardware address and for the telephone number.
Show this dialog in the The dialog is shown in Runtime so that changes can be made.
Runtime
If the computer, on which the driver command function is executed, is part of the zenon network,
additional actions are carried out. A special network command is sent from the computer to the project
server, which then executes the desired action on its driver. In addition, the Server sends the same
driver command to the project standby. The standby also carries out the action on its driver.
This makes sure that Server and Standby are synchronized. This only works if the Server and the Standby
both have a working and independent connection to the hardware.
zenon driver log all errors in the log files. The default folder for the log files is
subfolder LOG in directory ProgramData, example:
C:\ProgramData\zenon\zenon7.10\LOG for zenon Version 7.10. Log files
are text files with a special structure.
With the default settings, a driver only logs error information. With the
Diagnosis Viewer you can enhance the diagnosis level for most of the drivers to
"Debug" and "Deep Debug". With this the driver also logs all other important tasks
73
IEC850
and events.
1. In Windows CE even errors are not logged per default due to performance
reasons.
2. The Diagnosis Viewer displays all entries in UTC (coordinated world time) and
not in local time.
3. The Diagnosis Viewer does not display all columns of a log file per default. To
display more columns activate property Add all columns with entry in
the context menu of the column header.
4. If you only use Error logging, the problem description is in column Error
text. For other diagnosis level the description is in column General text.
5. For communication problems many drivers also log error numbers which the
PLC assigns to them. They are displayed in Error text and/or Error code
and/or Driver error parameter(1 and 2). Hints on the meaning of error
codes can be found in the driver documentation and the protocol/PLC
description.
6. At the end of your test set back the diagnosis level from Debug or Deep
Debug. At Debug and Deep Debug there are a great deal of data for logging
which are saved to the hard drive and which can influence your system
performance. They are still logged even after you close the Diagnosis
Viewer.
Info
74
IEC850
You can find further information on the Diagnosis Viewer in the Diagnose Viewer
(main.chm::/12464.htm) chapter.
Is the device (IEC 61850 server) connected to the power grid and ready for use?
Can a TCP connection to the device be created (check this using a 'ping') via the
defined port (check this via Telnet)?
Is communication between this device and another IEC 61850 client possible?
Is the driver in hardware mode and not in simulation mode?
Have you evaluated the errors that are logged in the log file of the driver?
Which errors occurred?
Was the diagnosis logging activated, at least for the error level and for all driver
modules?
Have you taken into account that the times in the Diagnosis Viewer are always UTC?
Is the Diagnose Viewer set so that all registered and all columns are diplayed with
the content (filtering)?
Variable addressing:
Do all variables have the right addresses?
Are the names (or identifications) of the variables valid
(SERVER!LD/LN/DO/DA[FC])?
Do the variables have the right driver object type, data type and value range?
75
IEC850
FC Semantics Description
ST Status information Stands for status information, the value of which can be read,
replaced, reported and logged, but not written.
MX Measurands (analogue values) Stands for status information, the measured size of which can
be read, replaced, reported and logged, but not written.
76
IEC850
Term Description
f floating point (analog value)
d Visible String(255)
q Quality
t Timestamp
77
IEC850
A Current
Acs Access
Acu Acoustic
Age Ageing
Alm Alarm
To Analogue
Ang Angle
Auth Authorization
Auto Automatic
Aux Auxiliary
Av Average
B Bushing
Bat Battery
Beh Behavior
Bin Binary
Bnd Band
Bo Bottom
Cancel Cancel
Cap Capability
Capac Capacitance
Car Carrier
78
IEC850
CB Circuit Breaker
CE Cooling Equipment
Cf Crest factor
Cfg Configuration
CG Core Ground
Ch Channel
Cha Charger
Chg Change
Chk Check
Chr Characteristic
Cir Circulating
Clc Calculate
Cls Close
Cnt Counter
Col Coil
Cor Correction
Crd Coordination
Crv Curve
CT Current Transducer
Ctl Control
Ctr Center
Cyc Cycle
79
IEC850
Dea Dead
Den Density
Det Detected
DExt De-excitation
Diag Diagnostics
Dir Direction
Dis Distance
Dl Delay
Dlt Delete
Dmd Demand
Dn Down
Drv Drive
DS Device State
Dsch Discharge
Dur Duration
80
IEC850
EC Earth Coil
EE External Equipment
EF Earth Fault
Ena Enabled
Eq Equalization, Equal
Ev Evaluation
Ex External
Exc Exceeded
Excl Exclusion
Ext Excitation
FA Fault Arc
Fact Factor
Fan Fan
Flt Fault
Flw Flow
Fu Fuse
Fwd Forward
Gen General
Gn Generator
Gnd Ground
Gr Group
Grd Guard
Gri Grid
81
IEC850
H2 Hydrogen
H2O Water
Hi High, highest
HP Hot point
Hz Frequency
Imb Imbalance
In Input
Ina Inactivity
Incr Increment
Ind Indication
Inh Inhibit
Ins Insulation
Int Integer
82
IEC850
Km Kilometer
R Lower
LD Logical Device
Len Length
Lev Level
Lg Lag
Lim Limit
Lin Line
Liv Live
Lo Low
LO Lockout
Loc Local
Lok Locked
Los Loss
Lst List
83
IEC850
M minutes
Max Maximum
Mem Memory
Min Minimum
Mod Mode
Mot Motor
Ms Milliseconds
Mst Moisture
MT Main Tank
N Neutral
Nam Name
Ng Negative
Num Number
Ofs Offset
Op Operate, Operating
Oper Operate*
Opn Open
Out Output
Pa Partial
84
IEC850
Par Parallel
Pct Percent
Per Periodic
PF Power Factor
Ph Phase
Phy Physical
Pls Pulse
Plt Plate
Pmp Pump
Po Polar
Pol Polarizing
Pos Position
PP Phase to phase
Pres Pressure
Pri Primary
Pro Protection
Ps Positive
Pst Post
Pwr Power
Qty Quantity
R Raise
85
IEC850
Rch Reach
Rcl Reclaim
Re Retry
Rec Reclose
Red Reduction
Rel Release
Rem Remote
Res Residual
Ris Resistance
Rl Relation, relative
Rs Reset, Resetable
Rsl Result
Rst Restraint
Rsv Reserve
Rte Rate
Rtg Rating
Rv Reverse
Rx Receive, received
86
IEC850
S1 Step one
S2 Step two
Sch Scheme
Sec Security
Seq Sequence
Set Setting
Sh Shunt
Spd Speed
Src Source
St Status
Stat Statistics
Stop Stop
Std Standard
Str Start
Sup Supply
Svc Service
Sw Switch
Swg Swing
Syn Synchronization
87
IEC850
Tap Tap
Td Total distortion
Test Test
Thm Thermal
Tm Time
• Tmh = Time in h
• Tms = Time in s
• Tmms = Time in ms
To Top
Tot Total
TP Three pole
Tr Trip
Trg Trigger
Ts Total signed
Tu Total unsigned
Tx Transmit, transmitted
Type Type
Un Under
88
IEC850
V Voltage
VA Volt Amperes
Vac Vacuum
Val Value
Vlv Valve
VT Voltage Transducer
W Active Power
Wac Watchdog
Wh Watt hours
Wid Width
Win Window
Wrm Warm
89
IEC850
Z Impedance
Zer Zero
Zn Zone
90
IEC850
Client-Server roles
B11 Server side (of TWO-PARTY- - N for Server see
APPLICATION-ASSOCIATION) zenon Logic
SCSMs supported
B21 SCSM: IEC 61850-8-1 used Y
- = not applicable
Y = supported
91
IEC850
M2 Logical node Y
M3 Data Y
M4 Data set Y
M5 Substitution Y
Reporting
M7 Buffered report control Y
M7-1 sequence-number Y
M7-2 report-time-stamp Y
M7-3 reason-for-inclusion Y
M7-4 data-set-name Y
M7-5 data-reference Y
M7-6 buffer-overflow Y
M7-7 entryID Y
M7-8 BufIm Y
M7-9 IntgPd Y
M7-10 GI Y
M8-1 sequence-number Y
M8-2 report-time-stamp Y
M8-3 reason-for-inclusion Y
M8-4 data-set-name Y
M8-5 data-reference Y
M8-6 BufIm Y
M8-7 IntgPd Y
92
IEC850
M8-8 GI Y
Logging
M9 Log control N
M9-1 IntgPd N
M10 Log N
M11 Control N
M13 GSSE N
Y = service is supported
Application association
93
IEC850
S2 Associate Y
S3 Abort Y supported
on TCP/IP
S4 Release N
Logical device
S5 GetLogicalDeviceDirectory TP Y
Logical node
S6 GetLogicalNodeDirectory TP Y
Data
S8 GetDataValues TP Y
S9 SetDataValues TP Y
S10 GetDataDirectory TP Y
S11 GetDataDefinition TP Y =
GetDataDirect
ory
Data set
S12 GetDataSetValues TP N not supported
S14 CreateDataSet TP Y
S15 DeleteDataSet TP Y
S16 GetDataSetDirectory TP Y
Substitution
S17 SetDataValues TP Y
94
IEC850
Reporting
Buffered report control block (BRCB)
S24 Report TP Y
S25 GetBRCBValues TP Y
S26 SetBRCBValues TP Y
S28 GetURCBValues TP Y
S29 SetURBCValues TP Y
Logging
Log control block
S30 GetLCBValues TP Y not tested
Log
S32 QueryLogByTime TP N not supported
95
IEC850
S38 GetGoCBValues TP Y O
S39 SetGoCBValues TP Y O
GSSE-CONTROL-BLOCK
S40 SendGSSEMessage MC C8 C8 not supported
Unicast SVC
S48 SendUSVMessage TP N C10 not supported
96
IEC850
S52 SelectWithValue TP Y
S53 Cancel TP Y
S54 Operate TP Y
S55 Command-Termination TP Y
File Transfer
S57 GetFile TP Y
S59 DeleteFile TP Y
S60 GetFileAttributeValues TP Y
Time
T1 Time resolution of internal clock Operating
System
97
IEC850
Introduced by Edition 2 for common data class APC the data attribute ctlVal as AnalogValue (structure)
with FC=CO is supported in read-only Services; ctlVal[SP] in APC from Edition1 is supported in all
Services.
Info
The PIXIT document for the certification test of the IEC850 driver is only available in
English.
INTRODUCTION
This document specifies the protocol implementation extra information for testing (PIXIT) of the IEC
61850 interface in the client system: “COPA-DATA IEC850 - Driver for IEC61850 protocol”, further referred
to as “Client”.
Together with the PICS and the MICS the PIXIT forms the basis for a conformance test according to IEC
61850-10.
The following chapters specify the PIXIT for each applicable ACSI service model as structured in IEC
61850-10 and the “Conformance Test Procedures for Client System with IEC 61850-8-1 interface” by
KEMA.
98
IEC850
Describe how the client handles report control RCB configuration is read out at each associate.
block configuration revision mismatches
<additional items> The Client does not use items of pre-defined data
model until reading them from data model from an
online server.
The SCL file is used only by offline import of
variables to HMI project in the Editor for pre-
configuration.
Please refer Client documentation for more details.
Lost connection detection time range (default The current TCP/IP timeout of Operating System
range of TCP_KEEPALIVE is 1 – 20 seconds)
The connection loss to LD is only detected if at least
one its attribute is currently polled.
Please refer Client documentation for more details
Is authentication supported Y
What is the maximum and minimum MMS PDU Max MMS PDU size 65535
size Min MMS PDU size dependent of max. DO
What is the typical startup time after a power The Client works only together with the zenon
supply interrupt Runtime and both are Windows applications.
99
IEC850
Does client support autodescription In the Runtime the Client reads data model only via
MMS. Then the Client does not use data not
responded via MMS by association.
Which status value (ST) quality bits are used in the Y Good,
client Y Invalid,
Y Reserved,
Y Questionable
Y BadReference
Y Oscillatory
Y Failure
Y OldData
Y Inconsistent
Y Inaccurate
Y Process
Y Substituted
100
IEC850
Y Test
Y OperatorBlocked
Describe how to view/display quality values 1.zenon Status Bits by stVal variable in HMI (only
selected bits.
Please refer Client documentation for more details.),
Describe how to force a SetDataValues request Set value to the variable created in HMI.
Please refer HMI documentation for more details.
Describe how to force a DeletaDataSet request would be done automatically according Client
configuration for Dynamic Data Sets.
Please refer Client documentation for more details.
Describe how the client handles following dataset No mismatch possible - SCL file is not used in the
mismatches between the SCL and the data sets Client during communication; the Client only uses
exposed via MMS: data sets exposed via MMS.
101
IEC850
Describe how the client behaves in case of: log entry + data will be polled (no reporting)
GetLogicalNodeDirectory(DATA-SET) response-
GetDataSetDirectory response-
persistent datasets Y
non-persistent datasets N
Describe how to get the actual setting group create variables in the HMI project for attributes
102
IEC850
Describe how to edit setting group values set value of adequate variables in HMI project
<additional items> The Client was never tested with an IED supporting
Setting Group
LLN0
Does the client support IED's with indexed and Y Buffered RCB indexed
non-indexed report control blocks (RCB) Y Buffered RCB not indexed
Y Unbuffered RCB indexed
Y Unbuffered RCB not indexed
103
IEC850
Y data update
Y general interrogation
Does the client support reported data set Y reporting of data objects
containing structured data objects or data N* reporting of data attributes
attributes?
*the Client process report but ignores single data
attributes while they do not have time and quality.
Skipped daName items of data set will be polled.
Describe how the client does respond when an log entry + trying to use another one if dynamically
URCB is already reserved allocated, fallback polling
Describe how the client does respond when a log entry, data will be polled
BRCB is already reserved
Describe how the client does respond when a mismatches are not possible - dataset directory and
report has an unknown: dataset, RptId, RCB configuration is read out via MMS at each
unexpexted number of dataset entries, and/or associate
unexpexted data type format entries
Describe how the client detect reporting RCB configuration is read out at each associate,
configuration changes (mismatches). Does it "configuration revision" doesn’t care
check the "configuration revision" attributes
and/or does it check the dataset members?
Describe how to force the client to change the no setting in the Client configuration
RCB buffer time
For attributes with FC = BR|RP variables in the HMI
project can be created, read, written.
104
IEC850
105
IEC850
Is "operate-many" supported N
Describe if and how the client sets/increments the for each use of any ctlVal[CO|SP] the Client
ctlNum increments* ctlNum from 0 to 127 and next turns
to 0.
* also by ctlModel=0 (no control possible)
What does the client when its receives a The Client gives possibility to create (pro */Oper
LastApplicationError and describe how to view the structure) an internal "State Info" variable for
additional cause? received AddCause item value and variables
ControlRun and ControlState showing current state
and success/fail of command. These internal
variables can be display and store in the HMI
project.
106
IEC850
What does the client when it receives a Select, The Client sets corresponding values to intern
SelectWithValue or Operate respond negative ? variables ControlRun (-1=error) and AddCause.
Optionally writes a log entry.
Please refer Client documentation for more details.
What does the client when the ctlModel is not out of scope
initialized in the SCL? The Client does not read ctlModel from SCL, only via
MMS
<additional items>
When is the quality bit "Clock failure" set? The Client does not set any time quality bits, it
supports reception of ClockFailure
When is the quality bit "Clock not synchronized" The Client does not set any time quality bits, it
set? supports reception of ClockNotSynchronised
ClockNotSynchronised
- status bits T_INVAL & T_EXTERN
ClockFailure
- status bits T_INVAL & T_INTERN
(and changes time attribute to HMI time).
107
IEC850
Does the client support IED’s that include the path Y path included
in the file name in the GetServerDirectory(FILE) Y path not included
respond? Y list of files with a char separator
Does the client support IED’s that use the file N "/"
separator Y "\"
What is the maximum file name size including OS limit, e.g. Windows Vista - 256 chars
path
Describe how the client behaves in case of: Command Variable value changes to
"DIR ERROR" (or "GET ERROR" for GetFile
GetFileAttributes response- response-)
108