IEC 61499-2:2005

Function blocks - Part 2: Software tool requirements

defines requirements for software tools to support the following systems engineering tasks enumerated in Clause 1 of IEC 61499-1: -the functional specification of resource types and device types; -the configuration, implementation, operation, and maintenance of distributed IPMCSs; - the specification of function block types; -the specification, analysis, and validation of distributed IPMCSs; -the exchange of information among software tools.

General Information

• Status: Published
• Publication Date: 19-Jan-2005
• ICS: 25.040.40 - Industrial process measurement and control
• ICS: 35.240.50 - IT applications in industry
• Technical Committee: SC 65B - Measurement and control devices
• Drafting Committee: WG 15 - TC 65/SC 65B/WG 15
• Current Stage: DELPUB - Deleted Publication
• Start Date: 07-Nov-2012
• Completion Date: 26-Oct-2025

Relations

• Replaces: IEC PAS 61499-2:2001 - Function blocks for industrial-process measurement and control systems - Part 2: Software tools requirements
• Effective Date: 05-Sep-2023
• Revised: IEC 61499-2:2012 - Function blocks - Part 2: Software tool requirements
• Effective Date: 05-Sep-2023

Overview

IEC 61499-2:2005 - Function blocks, Part 2: Software tool requirements - defines the requirements for software tools that support engineering tasks for distributed Industrial-Process Measurement and Control Systems (IPMCSs). It complements IEC 61499-1 (Architecture) by specifying how tools must present, exchange, validate and implement library elements (function block types, device/resource types, system configurations) to enable consistent engineering, deployment and maintenance of distributed control applications.

Key topics and technical requirements

• Scope of tool support: tools shall support specification of function block types; functional specification of resource and device types; specification, analysis and validation of distributed IPMCSs; configuration, implementation, operation and maintenance; and information exchange among tools.
• Library element exchange: tools must be capable of exchanging library elements using the XML/DTD-based format defined in Annex A (normative), over media or networks to ensure portability and tool interoperability.
• Supplier and library metadata: software tool suppliers must declare the types of library elements and engineering tasks supported. Providers of library elements must supply sufficient information to determine functionality while optionally protecting implementation details (examples include instances in resources or implementation files).
• Display and modification: tools shall display declarations (graphical or textual) appropriate to the engineering task and enable modification of declarations (add/delete/change), supporting both textual and graphical editing.
• Validation features: tools shall provide validation facilities where required - syntax checking, semantic checks (e.g., allocation of FB instances to resources, interconnections), and simulation or testing of instances.
• Implementation support: where applicable, tools should assist with implementation of declarations into target devices/resources and support system operation, testing and maintenance.
• Supporting annexes: Annex A (DTD), Annex B (graphics model) and Annex C (examples) guide tool vendors and integrators on standard formats and representations.

Applications and who uses it

IEC 61499-2 is intended for:

• Software tool vendors building engineering environments and compilers for IEC 61499-based systems.
• System integrators and control engineers who design, validate and deploy distributed control applications.
• Device manufacturers implementing runtime support (resources/devices) and providing library elements.
• Engineering Support System (ESS) developers focused on lifecycle management, portability and interoperability.

Practical uses include creating reusable function block libraries, enabling cross-vendor tool exchange, validating distributed control configurations, simulating behavior, and automating deployment to devices.

Related standards

• IEC 61499-1 - Function blocks: Architecture (normative foundation).
• IEC 61499-4 - Rules for compliance profiles (references for implementation classes).
• IEC 61499-3 (Tutorial) / Part 3 - explanatory examples and FAQs (informative).

Standards Content (Sample)

INTERNATIONAL IEC
STANDARD 61499-2
First edition
2005-01
Function blocks –
Part 2:
Software tools requirements
Reference number
Publication numbering
As from 1 January 1997 all IEC publications are issued with a designation in the
60000 series. For example, IEC 34-1 is now referred to as IEC 60034-1.
Consolidated editions
The IEC is now publishing consolidated versions of its publications. For example,
edition numbers 1.0, 1.1 and 1.2 refer, respectively, to the base publication, the
base publication incorporating amendment 1 and the base publication incorporating
amendments 1 and 2.
Further information on IEC publications
The technical content of IEC publications is kept under constant review by the IEC,
thus ensuring that the content reflects current technology. Information relating to
this publication, including its validity, is available in the IEC Catalogue of
publications (see below) in addition to new editions, amendments and corrigenda.
Information on the subjects under consideration and work in progress undertaken
by the technical committee which has prepared this publication, as well as the list
of publications issued, is also available from the following:
• IEC Web Site (www.iec.ch)
• Catalogue of IEC publications
The on-line catalogue on the IEC web site (www.iec.ch/searchpub) enables you to
search by a variety of criteria including text searches, technical committees
and date of publication. On-line information is also available on recently issued
publications, withdrawn and replaced publications, as well as corrigenda.
• IEC Just Published
This summary of recently issued publications (www.iec.ch/online_news/ justpub)
is also available by email. Please contact the Customer Service Centre (see
below) for further information.
• Customer Service Centre
If you have any questions regarding this publication or need further assistance,
please contact the Customer Service Centre:

Email: [e-mail]
Tel: [phone]
Fax: [phone]
INTERNATIONAL IEC
STANDARD 61499-2
First edition
2005-01
Function blocks –
Part 2:
Software tools requirements
 IEC 2005  Copyright - all rights reserved
No part of this publication may be reproduced or utilized in any form or by any means, electronic or
mechanical, including photocopying and microfilm, without permission in writing from the publisher.
International Electrotechnical Commission, 3, rue de Varembé, PO Box 131, CH-1211 Geneva 20, Switzerland
Telephone: [phone] Telefax: [phone] E-mail: [e-mail] Web: www.iec.ch
PRICE CODE
Commission Electrotechnique Internationale
X
International Electrotechnical Commission
Международная Электротехническая Комиссия
For price, see current catalogue

– 2 – 61499-2 © IEC:2005(E)
CONTENTS
FOREWORD.3

1 Scope .6
2 Normative references .6
3 Terms and definitions .6
4 Software tool requirements .7
4.1 Information to be provided by the software tool supplier .7
4.2 Exchange of library elements .7
4.3 Information to be provided by the supplier of library elements.7
4.4 Display of declarations.8
4.5 Modification of declarations .8
4.6 Validation of declarations.8
4.7 Implementation of declarations .8
4.8 System operation, testing and maintenance .8

Annex A (normative) Document Type Definitions (DTDs) .9
Annex B (informative) Graphics model.25
Annex C (informative) Examples .28

Figure B.1 – Graphics model.25
Figure B.2 – ECC drawing example.27

Table A.1 – Document Type Definition (DTD) elements.9
Table A.2 – DataType DTD .10
Table A.3 – DataType DTD Elements .11
Table A.4 – Library Element DTD .14
Table A.5 – LibraryElement DTD Elements .19

61499-2  IEC:2005(E) – 3 –
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
FUNCTION BLOCKS –
Part 2: Software tool requirements

FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote
international co-operation on all questions concerning standardization in the electrical and electronic fields. To
this end and in addition to other activities, IEC publishes International Standards, Technical Specifications,
Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC
Publication(s)”). Their preparation is entrusted to technical committees; any IEC National Committee interested
in the subject dealt with may participate in this preparatory work. International, governmental and non-
governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely
with the International Organization for Standardization (ISO) in accordance with conditions determined by
agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all
interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence
between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in
the latter.
5) IEC provides no marking procedure to indicate its approval and cannot be rendered responsible for any
equipment declared to be in conformity with an IEC Publication.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees for any personal injury, property damage or
other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and
expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC
Publications.
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of
patent rights. IEC shall not be held responsible for identifying any or all such patent rights.
International Standard IEC 61499-2 has been prepared by IEC technical committee 65:
Industrial-process measurement and control.
This standard cancels and replaces IEC/PAS 61499-2 published in 2001. This first edition
constitutes a technical revision.
The following major technical changes have occurred between the PAS edition and this
edition:
a) Syntax for network segments, links and parameters has been added in Annex A for
consistency with IEC 61499-1.
b) Syntax for parameters instead of constant data connections has been included for
consistency with IEC 61499-1.
– 4 – 61499-2  IEC:2005(E)
The text of this standard is based on the following documents:
CDV Report on voting
65/339/CDV 65/347/RVC
Full information on the voting for the approval of this standard can be found in the report on
voting indicated in the above table.
This publication has been drafted in accordance with the ISO/IEC Directives, Part 2.
IEC 61499 consists of the following parts, under the general title Function blocks:
Part 1: Architecture
Part 2: Software tool requirements
Part 3: Tutorial information
Part 4: Rules for compliance profiles
The committee has decided that the contents of this publication will remain unchanged until
the maintenance result date indicated on the IEC web site under "http://webstore.iec.ch" in
the data related to the specific publication. At this date, the publication will be
• reconfirmed;
• withdrawn;
• replaced by a revised edition, or
• amended.
A bilingual version of this standard may be issued at a later date.
———————
Under consideration.
61499-2  IEC:2005(E) – 5 –
INTRODUCTION
The IEC 61499 series consists of four Parts:
• Part 1 contains:
– general requirements, including an introduction, scope, normative references,
definitions, and reference models;
– rules for the declaration of function block types, and rules for the behaviour of
instances of the types so declared;
– rules for the use of function blocks in the configuration of distributed Industrial-Process
Measurement and Control Systems (IPMCSs);
– rules for the use of function blocks in meeting the communication requirements of
distributed IPMCSs;
– rules for the use of function blocks in the management of applications, resources and
devices in distributed IPMCSs.
• Part 2 (this part of IEC 61499) defines requirements for software tools to support the
following systems engineering tasks enumerated in Clause 1 of IEC 61499-1:
- the specification of function block types;
- the functional specification of resource types and device types;
- the specification, analysis, and validation of distributed IPMCSs;
- the configuration, implementation, operation, and maintenance of distributed IPMCSs;
- the exchange of information among software tools.
It is assumed that such software tools may be used in the context of an Engineering
Support System (ESS) as described in Clause C.1 of IEC 61499-1.
• Part 3 has the purpose of increasing the understanding, acceptance, and both generic and
domain-specific applicability of IPMCS architectures and software tools meeting the
requirements of the other Parts, by providing:
- answers to Frequently Asked Questions (FAQs) regarding the IEC 61499 series;
- examples of the use of IEC 61499 constructs to solve frequently encountered
problems in control and automation engineering.
• Part 4 defines rules for the development of compliance profiles which specify the features
of IEC 61499-1 and 61499-2 to be implemented in order to promote the following attributes
of IEC 61499-based systems, devices and software tools:
- interoperability of devices from multiple suppliers;
- portability of software between software tools of multiple suppliers; and
- configurability of devices from multiple vendors by software tools of multiple suppliers.

– 6 – 61499-2  IEC:2005(E)
FUNCTION BLOCKS –
Part 2: Software tool requirements

1 Scope
This part of IEC 61499 defines requirements for software tools to support the following
systems engineering tasks enumerated in Clause 1 of IEC 61499-1:
– the specification of function block types;
– the functional specification of resource types and device types;
– the specification, analysis, and validation of distributed IPMCSs;
– the configuration, implementation, operation, and maintenance of distributed IPMCSs;
– the exchange of information among software tools.
It is assumed that such software tools may be used in the context of an Engineering Support
System (ESS) as described in Clause C.1 of IEC 61499-1.
It is beyond the scope of this part of IEC 61499 to specify the entire life cycle of industrial-
process measurement and control systems (IPMCSs), or the entire set of tasks and activities
required to support an IPCMS over its life cycle. However, other standards which do specify
such tasks and activities may extend or modify the requirements specified in this Part.
2 Normative references
The following referenced documents are indispensable for the application of this document.
For dated references, only the edition cited applies. For undated references, the latest edition
of the referenced document (including any amendments) applies.
IEC 61499-1, Function blocks - Part 1: Architecture
IEC 61499-4, Function Blocks - Part 4: Rules for compliance profiles
The normative references given in IEC 61499-1 apply to this part of IEC 61499.
3 Terms and definitions
For the purposes of this document, the terms and definitions given in IEC 61499-1 as well as
the following apply.
3.1
library element
collection of declarations applying to a data type, function block type, adapter type,
subapplication type, resource type, device type, or system configuration.
———————
To be published.
61499-2  IEC:2005(E) – 7 –
4 Software tool requirements
4.1 Information to be provided by the software tool supplier
This Clause defines the functional requirements of software tools that support the
performance of the systems engineering tasks enumerated in Clause 1.
The supplier of a software tool shall specify the following information in addition to other
information required in this Clause:
a) The type or types of library element to which the software tool applies.
b) The engineering task or tasks supported by the software tool. Task descriptions may be
taken from the enumeration of engineering tasks given in Clause 1, or may be defined by
the supplier.
4.2 Exchange of library elements
A software tool shall be capable of exchanging its library elements with other software tools.
This exchange shall take the form of data in the format defined in Annex A, written on
physical media or exchanged over communication links or networks.
4.3 Information to be provided by the supplier of library elements
NOTE The provisions of this subclause are intended to provide the means by which the provider of a library
element may achieve protection of intellectual property while still providing sufficient information to permit the
effective use of the library element.
The provider of a library element may elect to provide an implementation of the library
element.
EXAMPLE 1 The provider of a function block type library element may provide an
implementation of the function block type as:
• one or more instances of the function block type in a resource contained in
a device of Class 0 or higher as described in IEC 61499-4;
• an instantiable implementation of the function block type in a resource
contained in a device of Class 1 or higher as described in IEC 61499-4;
• a file in an implementation-dependent format suitable for installation in a
resource contained in a device of Class 2 as described in IEC 61499-4, for
instance using an XML syntax which may be defined in a compliance profile
developed according to the rules given in IEC 61499-4.
When an implementation of a library element is provided, the provider is not required to
provide full details of the implementation. However, the provider shall provide sufficient
information to enable the user to fully determine the functionality of the provided library
element.
EXAMPLE 2 The requirement of the above paragraph would be met by the provider of an
instance of a function block type in a resource through the provision, at a
minimum, of the following information:
• a function block type library element specifying its event and data
interfaces as defined in IEC 61499-1, 5.2.1, and its services as defined in
IEC 61499-1, 6.1.3;
• resource type and device type library elements showing the occurrence and
connections of the function block instances.

– 8 – 61499-2  IEC:2005(E)
4.4 Display of declarations
A software tool shall be capable of displaying the declarations of its associated library
elements in a form appropriate to the engineering task. This display may utilize the graphical
or textual formats defined in IEC 61499-1, or a format defined by the supplier of the software
tool.
NOTE The declarations of a library element may define its interfaces (event and data inputs and outputs) and
internal variables as well as its algorithms and the control of their execution, for example via an execution control
chart (ECC), etc.
4.5 Modification of declarations
A software tool shall enable its user to modify the declarations of its associated library
elements as appropriate to the engineering task. Such modifications may include adding,
deleting or changing the contents of declarations, and may be performed either graphically or
textually or both.
4.6 Validation of declarations
If required by the associated engineering task, a software tool shall provide facilities for
validation of the declarations of its associated library elements. Such facilities may include,
but are not limited to:
a) Checking the correctness of the syntax of declarations.
b) Checking the semantic correctness of declarations, for instance, checking whether all
function block instances in an application and its associated subapplications are properly
allocated to resources, interconnected within resources, and intercommunicating among
resources in a system configuration.
c) Simulation and testing of the operation of an instance of a library element type, either by
itself or in association with other instances of the same or different types.
4.7 Implementation of declarations
If required by the associated engineering task, a software tool shall provide facilities for the
implementation of the declarations of its associated library elements. Such facilities may
include, but are not limited to:
a) The production of executable code ("firmware") for embedding in instances of resource
types and device types.
b) The creation and interconnection ("downloading") of function block instances in
resources and devices, for instance by using the management facilities defined in
subclause 3.3 and Annexes F and G of IEC 61499-1.
4.8 System operation, testing and maintenance
If required by the associated engineering task, a software tool shall provide facilities for the
operation, testing and maintenance of an Industrial Process Measurement and Control
System (IPMCS) specified by its associated library elements. Such facilities may include, but
are not limited to:
a) The facilities described in preceding subclauses of this Clause.
b) The information exchange facilities defined in subclause 6.2 and Annex F of
IEC 61499-1.
61499-2  IEC:2005(E) – 9 –
Annex A
(normative)
Document Type Definitions (DTDs)

A.1 General principles
This Annex presents Document Type Definitions (DTDs) for the exchange of IEC 61499 library
elements between software tools. These DTDs are defined in the syntax defined in the
eXtensible Markup Language (XML) specification (see www.w3.org/TR/2000/REC-xml-20001006).
The correspondences between the DTD elements given in this Annex, the library elements
defined in IEC 61499-1, C.2.2, and the textual syntax given in IEC 61499-1, Annex B are
given in Table A.1.
Table A.1 – Document Type Definition (DTD) elements
DTD element LibraryElement Textual syntax
DataType data_type_declaration
DataTypeDeclaration
(IEC 61131-3-B.1.3)
FBType fb_type_declaration
FBTypeDeclaration
SubapplicationType subapplication_type_
SubapplicationTypeDeclaration
declaration
AdapterType adapter_type_declaration
AdapterTypeDeclaration
ResourceType resource_type_
ResourceTypeDeclaration
specification
DeviceType device_type_specification
DeviceTypeDeclaration
System SystemConfiguration system_configuration

The first table of each subclause of this Annex contains the DTD for the corresponding library
element. The second table of each subclause provides a reference to the textual syntax (if
any) plus an explanation for the major elements and attributes in the DTD. Following this,
examples are given of the resulting XML files for typical library elements.
If there is a conflict between the provisions of this Annex and the provisions of Annex B of
IEC 61499-1, the provisions of the latter shall prevail.
NOTE 1 The examples given in this Annex provide a representative but not exhaustive sample of the features of
the associated DTDs. In particular, these examples are not intended to be used as a test suite for compliance to
the provisions of this part of IEC 61499.
A.2 DataType DTD
An XML document complying with the DTD in Table A.2 represents a DataTypeDeclaration
object as described in Clause C.1 of IEC 61499-1.

– 10 – 61499-2  IEC:2005(E)
Table A.2 – DataType DTD

ASN1Tag?, (DirectlyDerivedType | EnumeratedType | SubrangeType |
ArrayType | StructuredType))>
Name CDATA #REQUIRED
Comment CDATA #IMPLIED>

Standard CDATA #IMPLIED
Classification CDATA #IMPLIED
ApplicationDomain CDATA #IMPLIED
Function CDATA #IMPLIED
Type CDATA #IMPLIED
Description CDATA #IMPLIED>

Organization CDATA #REQUIRED
Version CDATA #REQUIRED
Author CDATA #REQUIRED
Date CDATA #REQUIRED
Remarks CDATA #IMPLIED>

Class (UNIVERSAL | APPLICATION | CONTEXT | PRIVATE) #IMPLIED
Number CDATA #REQUIRED>

header CDATA #IMPLIED
classdef CDATA #IMPLIED>

Language (Java | Cpp | C | Other) #REQUIRED
Vendor CDATA #REQUIRED
Product CDATA #REQUIRED
Version CDATA #REQUIRED>

BaseType (BOOL | SINT | INT | DINT | LINT | USINT | UINT | UDINT
| ULINT | REAL | LREAL | TIME | DATE | TIME_OF_DAY | TOD
| DATE_AND_TIME | DT | STRING | BYTE |WORD | DWORD |LWORD | WSTRING)
#REQUIRED
InitialValue CDATA #IMPLIED
Comment CDATA #IMPLIED>

InitialValue CDATA #IMPLIED
Comment CDATA #IMPLIED>

Name CDATA #REQUIRED
Comment CDATA #IMPLIED>

BaseType (SINT|INT|DINT|LINT|USINT|UINT|UDINT|ULINT) #REQUIRED
InitialValue CDATA #IMPLIED
Comment CDATA #IMPLIED>
61499-2  IEC:2005(E) – 11 –
Table A.2 – DataType DTD

LowerLimit CDATA #REQUIRED
UpperLimit CDATA #REQUIRED>

BaseType CDATA #REQUIRED
InitialValues CDATA #IMPLIED
Comment CDATA #IMPLIED>

Comment CDATA #IMPLIED>

Name CDATA #REQUIRED
Type CDATA #REQUIRED
ArraySize CDATA #IMPLIED
InitialValue CDATA #IMPLIED
Comment CDATA #IMPLIED>

Name CDATA #REQUIRED
Type (SINT|INT|DINT|LINT|USINT|UINT|UDINT|ULINT) #REQUIRED
InitialValue CDATA #IMPLIED
Comment CDATA #IMPLIED>
Explanations of the elements of the DTD given in Table A.2, and (where applicable)
references to the formal syntax for their attributes, are given in Table A.3.

Table A.3 – DataType DTD elements
Element Textual syntax Explanation
attributes (IEC 61131-3, Annex B)
DataType See IEC 61131-3
Name data_type_name
Comment -- A comment as per IEC 61131-3 without (* and *) delimiters
Identification Information for data base retrieval
Standard Primary reference standard in number-part-subclause format
Classification Classification code as defined in reference standard
ApplicationDomain
Application domain as defined in reference standard
Function
Function of this element as defined in reference standard
Type
Element type (e.g., device type) as defined in reference standard
Description
Descriptive phrase as defined in reference standard

– 12 – 61499-2  IEC:2005(E)
Table A.3 – DataType DTD elements
Element Textual syntax Explanation
attributes (IEC 61131-3, Annex B)
VersionInfo --
Possibly one of several entries:
First entry – Most recent version
Second entry – Immediately preceding released version, etc.
last entry – First released version
Organization --
The organization supplying this library element
Version digit [digit] '.'
The Version identification for this
digit [digit] [letter]
library element
Author --
The author of this library element
Date date_literal ['-'
The release date of this version
daytime]
Remarks --
Comments relating to this version
ASN1Tag
ASN.1 tag per ISO/IEC 8824-1
Class
ASN.1 tag class per ISO/IEC 8824-1
Number
ASN.1 tag number per ISO/IEC 8824-1
CompilerInfo --
Information for and about compilers used with this class
header --
Header information such as package, imports, etc.
classdef -- The class definition information such as superclass and
implemented interfaces. If none is given, a default abstract
superclass is used.
Compiler --
Possibly one of several compilers used with this version
Language --
The source language of this compiler
Vendor --
The vendor of this compiler
Product --
The product name of this compiler
Version --
The version of this compiler
DirectlyDerivedType
See IEC 61131-3, Tables 12 and 14, #1
BaseType elementary_type_name
InitialValue constant
Comment
A comment as per IEC 61131-3 without (* and *) delimiters
EnumeratedType See IEC 61131-3, Tables 12 and 14, #2
InitialValue enumerated_value
Comment
A comment as per IEC 61131-3 without (* and *) delimiters
EnumeratedValue
See IEC 61131-3, Table 14, #2
Name enumerated_value
Comment
A comment as per IEC 61131-3 without (* and *) delimiters
SubrangeType --
See IEC 61131-3, Tables 12 and 14, #3
BaseType integer_type_name
InitialValue signed_integer
Comment A comment as per IEC 61131-3 without (* and *) delimiters

61499-2  IEC:2005(E) – 13 –
Table A.3 – DataType DTD elements
Element Textual syntax Explanation
attributes (IEC 61131-3, Annex B)
Subrange
See IEC 61131-3, Tables 12 and 14, #3
LowerLimit signed_integer
UpperLimit signed_integer
ArrayType
See IEC 61131-3, Tables 12 and 14, #4
BaseType non_generic_type_nam
e
InitialValues array_initialization

StructuredType
See IEC 61131-3, Tables 12, #5 and 14, #5 and #6
VarDeclaration
Name structure_element_name
Type non_generic_type_name
ArraySize See NOTE 1
InitialValue See NOTE 2
Comment
A comment as per IEC 61131-3 without (* and *) delimiters
SubrangeVarDeclaration
See IEC 61131-3, 2.3.3.
Name structure_element_na
me
Type integer_type_name
InitialValue signed_integer
Comment
A comment as per IEC 61131-3 without (* and *) delimiters
NOTE 1 The syntax of this attribute when present is equivalent to the syntactic expression
(subrange {',' subrange}) | integer {',' integer}
where the non-terminals subrange and integer are as defined in Annex B of IEC 61131-3. Each term
of the second form is equivalent to the subrange 0.n-1, where n is the value of the corresponding
integer syntactic element. If this attribute is missing, the structure component is not an anonymously
defined array.
NOTE 2 The syntax of this attribute is the syntax for initialization of the corresponding variable type as defined in
Annex B.1.4.3 of IEC 61131-3.
EXAMPLE The structured data type ANALOG_CHANNEL_CONFIGURATIONI example is
expressed in IEC 61131-3, Table 14 as follows:
TYPE ANALOG_CHANNEL_CONFIGURATIONI :
STRUCT
RANGE : ANALOG_SIGNAL_RANGE ;
MIN_SCALE : ANALOG_DATA := -4095 ;
MAX_SCALE : ANALOG_DATA := 4095 ;
END_STRUCT ;
END_TYPE
– 14 – 61499-2  IEC:2005(E)
A corresponding XML document could be:

>
Name="ANALOG_CHANNEL_CONFIGURATIONI"
Comment="IEC 61131-3, Table 14#5">
Function="Configuration Data"
Standard="61131-3-2.3.3.2"
ApplicationDomain="Any"
Classification="Data type"
Type="Analog"
Description="Table 14, #5"/>
Organization="IEC SC65B/WG7/TF3"
Version="2.0"
Author="JHC"
Date="2000-01-31"/>

Type="ANALOG_SIGNAL_RANGE"/>
Type="ANALOG_DATA"
InitialValue="-4095"/>
Type="ANALOG_DATA"
InitialValue="4095"/>


A.3 LibraryElement DTD
An XML document complying with the DTD in Table A.4 represents a LibraryElement object
as described in Annex C of IEC 61499-1. Possible root elements of such a document are
FBType, AdapterType, ResourceType, DeviceType, System, and SubappType,
representing the concrete subclasses FBTypeDeclaration, AdapterTypeDeclaration,
ResourceTypeDeclaration, DeviceTypeDeclaration, SystemConfiguration, and Subapplication-
TypeDeclaration of the abstract superclass LibraryElement, respectively. The DataType-
Declaration subclass is represented separately by the DTD given in Clause A.1 of this
document.
Table A.4 – Library Element DTD



Standard CDATA #IMPLIED
Classification CDATA #IMPLIED
ApplicationDomain CDATA #IMPLIED
Function CDATA #IMPLIED
Type CDATA #IMPLIED
Description CDATA #IMPLIED>

Organization CDATA #REQUIRED
Version CDATA #REQUIRED
Author CDATA #REQUIRED
Date CDATA #REQUIRED
Remarks CDATA #IMPLIED>
61499-2  IEC:2005(E) – 15 –
Table A.4 – Library Element DTD

header CDATA #IMPLIED
classdef CDATA #IMPLIED>

Language (Java | Cpp | C | Other) #REQUIRED
Vendor CDATA #REQUIRED
Product CDATA #REQUIRED
Version CDATA #REQUIRED>
(FB*,EventConnections?,DataConnections?,AdapterConnections?)>

Name CDATA #REQUIRED
Type CDATA #REQUIRED
Comment CDATA #IMPLIED
x CDATA #IMPLIED
y CDATA #IMPLIED>




Source CDATA #REQUIRED
Destination CDATA #REQUIRED
Comment CDATA #IMPLIED
dx1 CDATA #IMPLIED
dx2 CDATA #IMPLIED
dy CDATA #IMPLIED
>

(Identification?,VersionInfo+,CompilerInfo?,InterfaceList,
(BasicFB | FBNetwork)?, Service?) >
Name CDATA #REQUIRED
Comment CDATA #IMPLIED
>
(EventInputs?,EventOutputs?,InputVars?,OutputVars?,
Sockets?, Plugs?)>







Name CDATA #REQUIRED
Type CDATA #IMPLIED
Comment CDATA #IMPLIED>

Var CDATA #REQUIRED>
– 16 – 61499-2  IEC:2005(E)
Table A.4 – Library Element DTD

Name CDATA #REQUIRED
Type CDATA #REQUIRED
ArraySize CDATA #IMPLIED
InitialValue CDATA #IMPLIED
Comment CDATA #IMPLIED>
Name CDATA #REQUIRED
Type CDATA #REQUIRED
Comment CDATA #IMPLIED
x CDATA #IMPLIED
y CDATA #IMPLIED>




Name CDATA #REQUIRED
Comment CDATA #IMPLIED
x CDATA #IMPLIED
y CDATA #IMPLIED>

Source CDATA #REQUIRED
Destination CDATA #REQUIRED
Condition CDATA #REQUIRED
Comment CDATA #IMPLIED
x CDATA #IMPLIED
y CDATA #IMPLIED>

Algorithm CDATA #IMPLIED
Output CDATA #IMPLIED>

Name CDATA #REQUIRED
Comment CDATA #IMPLIED>




Output CDATA #REQUIRED
Expression CDATA #REQUIRED
Comment CDATA #IMPLIED>

Language CDATA #REQUIRED >

RightInterface CDATA #REQUIRED
LeftInterface CDATA #REQUIRED
Comment CDATA #IMPLIED>
61499-2  IEC:2005(E) – 17 –
Table A.4 – Library Element DTD

Name CDATA #REQUIRED
Comment CDATA #IMPLIED>


Interface CDATA #REQUIRED
Event CDATA #REQUIRED
Parameters CDATA #IMPLIED>

Interface CDATA #REQUIRED
Event CDATA #REQUIRED
Parameters CDATA #IMPLIED>

(Identification?,VersionInfo+,CompilerInfo?,InterfaceList,Service?)>
Name CDATA #REQUIRED
Comment CDATA #IMPLIED>

FBTypeName*, VarDeclaration*, FBNetwork?)>
Name CDATA #REQUIRED
Comment CDATA #IMPLIED>

Name CDATA #REQUIRED>

VarDeclaration*, ResourceTypeName*, Resource*, FBNetwork?)>
Name CDATA #REQUIRED
Comment CDATA #IMPLIED>

Name CDATA #REQUIRED >

Name CDATA #REQUIRED
Type CDATA #REQUIRED
Comment CDATA #IMPLIED
x CDATA #IMPLIED
y CDATA #IMPLIED>
– 18 – 61499-2  IEC:2005(E)
Table A.4 – Library Element DTD

Mapping*, Segment*, Link*)>
Name CDATA #REQUIRED
Comment CDATA #IMPLIED>

Name CDATA #REQUIRED
Comment CDATA #IMPLIED>

From CDATA #REQUIRED
To CDATA #REQUIRED>

Name CDATA #REQUIRED
Type CDATA #REQUIRED
Comment CDATA #IMPLIED
x CDATA #IMPLIED
y CDATA #IMPLIED>

(Identification?,VersionInfo+,CompilerInfo?,SubAppInterfaceList,
SubAppNetwork?)>
Name CDATA #REQUIRED
Comment CDATA #IMPLIED>
(SubAppEventInputs?,SubAppEventOutputs?,InputVars?,OutputVars?)>



Name CDATA #REQUIRED
Type CDATA #IMPLIED
Comment CDATA #IMPLIED>
(SubApp*,FB*,EventConnections?,DataConnections?, AdapterConnections?)>

Name CDATA #REQUIRED
Type CDATA #REQUIRED
Comment CDATA #IMPLIED
x CDATA #IMPLIED
y CDATA #IMPLIED>
61499-2 © IEC:2005(E) – 19 –
Table A.4 – Library Element DTD


Name CDATA #REQUIRED
Type CDATA #REQUIRED
Comment CDATA #IMPLIED
x CDATA #IMPLIED
y CDATA #IMPLIED
dx1 CDATA #IMPLIED>

Name CDATA #REQUIRED
Value CDATA #REQUIRED
Comment CDATA #IMPLIED>

SegmentName CDATA #REQUIRED
CommResource CDATA #REQUIRED
Comment CDATA #IMPLIED >
Explanations of some of the elements of the above DTD, and (where applicable) references to
the formal syntax for their attributes, are given in Table A.5.
Table A.5 – LibraryElement DTD elements
Element Syntax Explanation
Attributes (IEC 61499-1, Annex B)
Identification
VersionInfo
See Table A.3
CompilerInfo
Compiler
FBNetwork
A function block network as defined in IEC 61499-1.
FB
A function block instance as defined in IEC 61499-1.
Name fb_instance_name
Type fb_type_name
Comment
A comment as per IEC 61131-3 without (* and *) delimiters
x, y
See Annex B.
Connection
An event connection, data connection or adapter connection as
defined in IEC 61499-1.
Source
See NOTE 3
Destination
See NOTE 3
dx1, dx2, dy
See Annex B
FBType
A function block type as described in IEC 61499-1.
Name
fb_type_name
Comment
A comment as per IEC 61131 without (* and *) delimiters

– 20 – 61499-2  IEC:2005(E)
Table A.5 – LibraryElement DTD elements
Element Syntax Explanation
Attributes (IEC 61499-1, Annex B)
Event
A declaration of an event interface.
Name event_input_name
See NOTE 4
| event_output_name
Type event_type
Comment
A comment as per IEC 61131-3 without (* and *) delimiters
With
A declaration of an association between an event and a
variable.
Var input_variable_name
See NOTE 4
| output_ variable
_name
VarDeclaration
A declaration of a variable.
Name input_variable_name
See NOTE 5
| output_variable_name
|
internal_variable_name
Type identifier
ArraySize
See NOTE 6
InitialValue
See NOTE 7
Comment
A comment as per IEC 61131-3 without (* and *) delimiters
AdapterDeclaration
A declaration of a plug or socket interface of a function block type.
Name plug_name | socket_name
See NOTE 8
Type adapter_type_name
Comment
A comment as per IEC 61131-3 without (* and *) delimiters
x, y
Location (See Annex B) of plug or socket in the internal
function block network of a composite function block type.
ECState
An EC state as defined in IEC 61499-1.

Name ec_state_name
Comment
A comment as per IEC 61131-3 without (* and *) delimiters
x, y
See Annex B
ECTransition
An EC transition as defined in IEC 61499-1.
Source ec_state_name
Destination ec_state_name
Condition ec_transition_condition

x, y
See Annex B
ECAction
An EC action as defined in IEC 61499-1.
Algorithm algorithm_name
Output event_output_name
61499-2 © IEC:2005(E) – 21 –
Table A.5 – LibraryElement DTD elements
Element Syntax Explanation
Attributes (IEC 61499-1, Annex B)
Algorithm
An algorithm in a specified language (NOTE 1)
Name algorithm_name
Comment
A comment as per IEC 61131-3 without (* and *) delimiters
ST An algorithm in the IEC 61131-3 ST language, whose contents are in
the syntax of a statement_list per IEC 61131-3, Annex B.
Rung
A rung of an algorithm in the LD language
Output
See NOTE 2
Expression
See NOTE 2
Other
An algorithm in a language other than FBD, ST or LD, whose contents
are in the syntax defined for the particular language; see NOTE 1.
Language
The name of the programming language; see NOTE 1
Service
A declaration of a service as per IEC 61499-1
RightInterface service_interface_nam

e
LeftInterface service_interface_nam

e
Comment
A comment as per IEC 61131-3 without (* and *) delimiters
ServiceSequence
A declaration of a service sequence as per IEC 61499-1
Name
sequence_name
Comment
A comment as per IEC 61131-3 without (* and *) delimiters
InputPrimitive
An "input" service primitive as per IEC 61499-1
Interface service_interface_nam

e
Event
(([plug_name '.'] event_input_name)
| (socket_name '.' event_output_name))
['+' | '-']
Parameters input_variable_name {',' input_variable_name}
OutputPrimitive
An "output" service primitive as per IEC 61499-1
Interface service_interface_nam

e
Event ('NULL'
| ([plug_name '.'] event_output_name)
| socket_name '.' event_input_name))
['+' | '-']
Parameters output_variable_name {',' output_variable_name}
AdapterType
A declaration of an adapter interface type per IEC 61499-1
Name
adapter_type_name
Comment
A comment as per IEC 61131-3 without (* and *) delimiters
ResourceType
A declaration of a resource type as per IEC 61499-1
Name
resource_type_name
Comment
A comment as per IEC 61131-3 without (* and *) delimiters

– 22 – 61499-2  IEC:2005(E)
Table A.5 – LibraryElement DTD elements
Element Syntax Explanation
Attributes (IEC 61499-1, Annex B)
FBTypeName
The name of a function block type supported by all instances of
a resource type
Name
fb_type_name
DeviceType
A declaration of a device type per IEC 61499-1
Name
device_type_name
Comment
A comment as per IEC 61131-3 without (* and *) delimiters
ResourceTypeName
The name of a resource type supported by all instances of a
device type
Name
resource_type_name
Resource
A resource instance present in all instances of a device type
Name
resource_instanc
...