IEC PAS 61499-2:2001

IEC/PAS 61499-2
Edition 1.0
2001-05
PRE-STANDARD
Function blocks for industrial-process
measurement and control systems –
Part 2:
Software tools requirements
PUBLI C LY AVAI LABLE SPECI F I CATI O N
IN TER N A TION AL Reference number
E L E C T R OT E CHNI CA L
IEC/PAS 61499-2
C O MMI S S I O N
IEC/PAS 61499-2
Edition 1.0
2001-05
PRE-STANDARD
Function blocks for industrial-process
measurement and control systems –
Part 2:
Software tools requirements
PUBLI C LY AVAI LABLE SPECI F I CATI O N
IN TER N A TION AL Reference number
E L E C T R OT E CHNI CA L
IEC/PAS 61499-2
C O MMI S S I O N
– 2 – Copyright © IEC, 2001
TABLE OF CONTENTS
1. GENERAL REQUIREMENTS .4

1.1 Scope.4

1.2 Normative references .4

1.3 Definitions.5

2. SOFTWARE TOOL REQUIREMENTS .5

2.1 Information to be provided by the software tool supplier.5

2.2 Exchange of library elements .5
2.3 Information to be provided by the supplier of library elements .5
2.4 Display of declarations .6

2.5 Modification of declarations.6

2.6 Validation of declarations .6
2.7 Implementation of declarations .6
2.8 System operation, testing and maintenance .6
ANNEX A - DOCUMENT TYPE DEFINITIONS (DTDs) (normative) .7
A.1 DataType.8
A.2 LibraryElement.13
A.3 Examples .22
A.3.1 Basic function block types.22
A.3.2 Service interface function block types.26
A.3.3 An adapter interface type.29
A.3.4 Resource types .30
A.3.5 Device types.32
A.3.6  A system configuration.33
ANNEX B - GRAPHICS MODEL (informative).37
B.1 Coordinate system .37
B.2 Location of graphical elements .38
B.3 Routing of connections.38
B.4 Default layouts .38

– 3 – Copyright © IEC, 2001
LIST OF TABLES
Table A.0 - Document Type Definitions (DTDs).7

Table A.1-1 - DataType DTD.8

Table A.1-2 - DataType DTD Elements.9

Table A.2-1 - Library Element DTD .13

Table A.2-2 - LibraryElement DTD Elements.17

Copyright © IEC, 2001
INTERNATIONAL ELECTROTECHNICAL COMMISSION

____________
FUNCTION BLOCKS FOR INDUSTRIAL-PROCESS MEASUREMENT

AND CONTROL SYSTEMS
PART 2: SOFTWARE TOOLS REQUIREMENTS

FOREWORD
A PAS is a technical specification not fulfilling the requirements for a standard, but made available to

the public and established in an organization operating under given procedures.

IEC-PAS 61499-2 has been processed by working group 6 of IEC technical committee 65: Industrial-process
measurement and control.
The text of this PAS is based on the This PAS was approved for
following document: publication by the P-members of the
committee concerned as indicated in
the following document:
Draft PAS Report on voting
65/260/PAS 65/265/RVD
Following publication of this PAS, the technical committee or subcommittee concerned will investigate
the possibility of transforming the PAS into an International Standard.
This is Part 2 of a projected three-part Standard under development by Working Group 6 of IEC
Technical Committee 65.
The projected parts of the standard are:
• Part 1 – Architecture,
• Part 2 – Software Tool Requirements,
• Part 3 – Application Guidelines
1) The IEC (International Electrotechnical Commission) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of the 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, the IEC publishes International Standards. 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. The 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 the 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 National Committees.
3) The documents produced have the form of recommendations for international use and are published in the form
of standards, technical specifications, technical reports or guides and they are accepted by the National
Committees in that sense.
4) In order to promote international unification, IEC National Committees undertake to apply IEC International
Standards transparently to the maximum extent possible in their national and regional standards. Any
divergence between the IEC Standard and the corresponding national or regional standard shall be clearly
indicated in the latter.
5) The IEC provides no marking procedure to indicate its approval and cannot be rendered responsible for any
equipment declared to be in conformity with one of its standards.
6) Attention is drawn to the possibility that some of the elements of this PAS may be the subject of patent rights.
The IEC shall not be held responsible for identifying any or all such patent rights.
Page i
– 4 – Copyright © IEC, 2001
1. GENERAL REQUIREMENTS
1.1 Scope
This Standard consists of two Parts:

• Part 1, "Architecture", 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 behavior 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;
- requirements to be met by compliant systems and standards.
• This Part defines requirements for software tools to support the following systems
engineering tasks enumerated in subclause 1.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 Annex C.1 of IEC 61499-1.
• Part 3, “Application Guidelines,” contains examples of the application of software tools in
various stages of engineering methodologies for the performance of the tasks
enumerated above.
It is beyond the scope of this Standard to specify the entire life cycle of industrial-process
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.
1.2 Normative references
The normative references given in IEC 61499-1 also apply to this Part. In addition, the
following document contains normative provisions that are used in an informative manner in

Annex A of this Part:
17B/1022/CD, Draft IEC 61915: Low-voltage switchgear and controlgear - Profiles for networked
industrial devices, 12 October 1999
All normative documents are subject to revision, and parties to agreements based on this
standard are encouraged to investigate the possibility of applying the most recent editions of
the normative documents indicated above. Members of the IEC and ISO maintain registers
of currently valid International Standards.

– 5 – Copyright © IEC, 2001
1.3 Definitions
The definitions given in IEC 61499-1 also apply to this Part. In addition, the following

definitions apply for the purposes of this Part.

1.3.1. library element: The collection of declarations applying to a data type, function block type,

adapter type, subapplication type, resource type, device type, or system configuration.

2. SOFTWARE TOOL REQUIREMENTS
This Clause defines the functional requirements of software tools which support the

performance of the systems engineering tasks enumerated in subclause 1.1.

2.1 Information to be provided by the software tool supplier
The supplier of a software tool shall specify the following information in addition to other
information which may be required in this Clause:
1. The type or types of library element to which the software tool applies.
2. The engineering task or tasks supported by the software tool. Task descriptions may be taken
from the enumeration of engineering tasks given in subclause 1.1, or may be defined by the
supplier.
2.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
2.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 specified in IEC 61499-1-5.1;
- an instantiable implementation of the function block type in a resource contained in a
device of Class 1 or higher as specified in IEC 61499-1-5.1;
- a file in an implementation-dependent format suitable for installation in a resource
contained in a device of Class 2 as specified in IEC 61499-1-5.1, for instance using

the IEC61499-FBMGT syntax defined in IEC 61499-1-F.3.1.2.
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-2.2.1, and its services as defined in IEC 61499-1-3.1.2;
- resource type and device type library elements showing the occurrence and
connections of the function block instances.

– 6 – Copyright © IEC, 2001
2.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.
2.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.
2.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:
1. Checking the correctness of the syntax of declarations.
2. Checking the semantic correctness of declarations, for instance, checking whether all function
block instances in an application and its associated sub applications are properly allocated to
resources, interconnected within resources, and intercommunicating among resources in a
system configuration.
3. 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.
2.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:
1. The production of executable code ("firmware") for embedding in instances of resource types
and device types.
2. 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.
2.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:
1. The facilities described in preceding subclauses of this Clause.
2. The information exchange facilities defined in subclause 3.2 and Annex F of IEC 61499-1.

– 7 – Copyright © IEC, 2001
ANNEX A - DOCUMENT TYPE DEFINITIONS (DTDs) (normative)

NOTE 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.

This Annex presents Document Type Descriptions (DTDs) for the exchange of IEC 61499

library elements between software tools. These DTDs are defined in the syntax defined in the

eXtendedn Markup Language (XML) specification at http://www.w3.org/TR/1998/REC-xml-

19980210.
The correspondences between the DTDs given in this Annex, the library elements defined in

IEC 61499-1-C.1.1, and the textual syntax given in IEC 61499-1-B are given in Table A.0.

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.
NOTE 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.
Table A.0 - Document Type Definitions (DTDs)
DTD LibraryElement Textual Syntax
data_type_declaration
DataType DataTypeDeclaration
(IEC 61131-3-B.1.3)
fb_type_declaration
FBType FBTypeDeclaration
subapplication_type_declaration
SubapplicationType SubapplicationTypeDeclaration
adapter_type_declaration
AdapterType AdapterTypeDeclaration
resource_type_specification
ResourceType ResourceTypeDeclaration
device_type_specification
DeviceType DeviceTypeDeclaration
system_configuration
System SystemConfiguration
– 8 – Copyright © IEC, 2001
A.1 DataType
An XML document complying with the DTD in Table A.1-1 represents a

DataTypeDeclaration object as described in Annex C.1.1 of IEC 61499-1.

Table A.1-1 - DataType DTD


(Identification?,VersionInfo+,CompilerInfo?,ASN1Tag?,(DirectlyDerivedType

|EnumeratedType|SubrangeType|ArrayType|StructuredType))>
Name CDATA #REQUIRED
Comment 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|DATE_AND_TIME|STRING|BYTE|WORD|DWORD|LWORD|WSTRING)
#REQUIRED
InitialValue CDATA #IMPLIED
Comment CDATA #IMPLIED
>

InitialValue IDREF #IMPLIED
>

Name ID #REQUIRED
Comment CDATA #IMPLIED
>

BaseType (SINT|INT|DINT|LINT|USINT|UINT|UDINT|ULINT) #REQUIRED
InitialValue CDATA #IMPLIED
>

LowerLimit CDATA #REQUIRED
UpperLimit CDATA #REQUIRED
>
– 9 – Copyright © IEC, 2001
Table A.1-1 - DataType DTD


BaseType CDATA #REQUIRED
InitialValues CDATA #IMPLIED
Comment CDATA #IMPLIED
>
(VarDeclaration|ArrayVarDeclaration|SubrangeVarDeclaration)+>
Comment CDATA #IMPLIED
>


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

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

Name ID #REQUIRED
Type (SINT|INT|DINT|LINT|USINT|UINT|UDINT|ULINT) #REQUIRED
Comment CDATA #IMPLIED
InitialValue CDATA #IMPLIED
>
Explanations of the elements of the above DTD, and (where applicable) references to the
formal syntax for their attributes, are given in Table A.1-2.
Table A.1-2 - 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 per IEC 61131-3-2.1.5 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

– 10 – Copyright © IEC, 2001
Table A.1-2 - DataType DTD Elements

Element Textual Syntax Explanation
Attributes (IEC 61131-3, Annex B)

--
VersionInfo
Possibly one of several entries:

• First entry - Most recent version

• 2nd entry - Immediately preceding released version.

• 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 --
The release date of this version in YYYY-MM-DD format
Remarks --
Comments relating to this version
ASN.1 tag per ISO/IEC 8824-5.8
ASN1Tag
ASN.1 tag class per ISO/IEC 8824-5.8
Class
ASN.1 tag number per ISO/IEC 8824-5.8
Number
Information for and about compilers used with this class
CompilerInfo --
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
EnumeratedType
See IEC 61131-3 Tables 12 and 14, #2

InitialValue enumerated_value
EnumeratedValue
See IEC 61131-3 Table 14, #2
Name enumerated_value
Comment
A comment per IEC 61131-3-2.1.5 without (* and *) delimiters
SubrangeType --
See IEC 61131-3 Tables 12 and 14, #3
BaseType integer_type_name
InitialValue signed_integer
Subrange
See IEC 61131-3 Tables 12 and 14, #3
signed_integer
LowerLimit
signed_integer
UpperLimit
– 11 – Copyright © IEC, 2001
Table A.1-2 - DataType DTD Elements

Element Textual Syntax Explanation
Attributes (IEC 61131-3, Annex B)

ArrayType
See IEC 61131-3 Tables 12 and 14, #4

BaseType non_generic_type_name

InitialValues array_initialization

StructuredType
See IEC 61131-3 Tables 12, #5 and 14, #5 and #6

VarDeclaration
See NOTE
structure_element_name
Name
elementary_type_name | simple_type_name
Type
See NOTE
| enumerated_type_name | structure_type_name
Comment
A comment per IEC 61131-3-2.1.5 without (* and *) delimiters
constant | enumerated_value
InitialValue
See NOTE
| initialized_structure
ArrayVarDeclaration
See IEC 61131-3-2.3.3.
structure_element_name
Name
array_type_name
Type
Comment
A comment per IEC 61131-3-2.1.5 without (* and *) delimiters
array_initialization
InitialValues
SubrangeVarDeclaration See IEC 61131-3-2.3.3.
structure_element_name
Name
integer_type_name
Type
Comment
A comment per IEC 61131-3-2.1.5 without (* and *) delimiters
signed_integer
InitialValue
NOTE - The Type and InitialValue syntax for this element must match each other according to the IEC
61131-3 Annex B syntax for structure_element_declaration.
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
A corresponding XML document could be:

– 12 – Copyright © IEC, 2001



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"/>


– 13 – Copyright © IEC, 2001
A.2 LibraryElement
An XML document complying with the DTD in Table A.2-1 represents a LibraryElement

object as described in Annex C.1.1 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

SubapplicationTypeDeclaration of the abstract superclass LibraryElement, respectively.

The DataTypeDeclaration subclass is represented separately by the DTD given in Annex

A.1 of this specification.
Table A.2-1 - 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
>

header CDATA #IMPLIED
classdef CDATA #IMPLIED
>

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


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
>
– 14 – Copyright © IEC, 2001
Table A.2-1 - Library Element DTD


(BasicFB | FBNetwork)?, Service?) >
Name CDATA #REQUIRED
Comment CDATA #IMPLIED
>
Sockets?, Plugs?)>










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

Var IDREF #REQUIRED
>

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

Name ID #REQUIRED
Type CDATA #REQUIRED
Comment 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 IDREF #IMPLIED
>
– 15 – Copyright © IEC, 2001
Table A.2-1 - Library Element DTD



Name CDATA #REQUIRED
Comment CDATA #IMPLIED
>

>

Text CDATA #REQUIRED
>
>

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

Language CDATA #REQUIRED
Text CDATA #REQUIRED
>

RightInterface CDATA #REQUIRED
LeftInterface CDATA #REQUIRED
Comment CDATA #IMPLIED
>

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
>

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

Name CDATA #REQUIRED
>
– 16 – Copyright © IEC, 2001
Table A.2-1 - Library Element DTD


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

Name CDATA #REQUIRED
>

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

(Identification?,VersionInfo+,Application*,Device+,DeviceParameters?,Mapping*)>
Name CDATA #REQUIRED
Comment CDATA #IMPLIED
>

Name CDATA #REQUIRED
Comment CDATA #IMPLIED
>

From CDATA #REQUIRED
To CDATA #REQUIRED
>

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


– 17 – Copyright © IEC, 2001
Table A.2-1 - Library Element DTD


SubAppNetwork?)>
Name CDATA #REQUIRED
Comment CDATA #IMPLIED
>
(SubAppEventInputs?,SubAppEventOutputs?,InputVars?,OutputVars?)>






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


Name CDATA #REQUIRED
Type CDATA #REQUIRED
Comment CDATA #IMPLIED
x CDATA #IMPLIED
y 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.2-2.
Table A.2-2 - LibraryElement DTD Elements
Element Syntax Explanation
Attributes (IEC 61499-1, Annex B.2)
Identification
VersionInfo
See Table A.1-2
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_reference
See NOTE 3.
Type
fb_type_name
Comment
A comment per IEC 61131-3-2.1.5 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 NOTES 3,4.
Destination
See NOTES 3,4.
dx1, dx2, dy
See Annex B.
FBType
An FBTypeDeclaration as described in IEC 61499-1-C.1.1.
Name fb_type_name
Comment
A comment per IEC 61131-3-2.1.5 without (* and *) delimiters

– 18 – Copyright © IEC, 2001
Table A.2-2 - LibraryElement DTD Elements

Element Syntax Explanation
Attributes (IEC 61499-1, Annex B.2)

Event
A declaration of an event interface.

event_input_name
Name See NOTE 5.
| event_output_name
event_type
Type
Comment
A comment per IEC 61131-3-2.1.5 without (* and *) delimiters

With
A declaration of an association between an event and a variable.
input_variable_name
Var
See NOTE 5.
| output_ variable _name
VarDeclaration A declaration of a variable.
input_variable_name
Name
See NOTE 6.
| output_variable_name
| internal_variable_name
identifier
Type
ArraySize
See NOTE 7.
InitialValue
See NOTE 8.
Comment
A comment per IEC 61131-3-2.1.5 without (* and *) delimiters
AdapterDeclaration A declaration of a plug or socket interface of a function block type.
plug_name | socket_name
Name
See NOTE 9.
adapter_type_name
Type
Comment
A comment per IEC 61131-3-2.1.5 without (* and *) delimiters
ECState
An EC state as defined in IEC 61499-1.
Name
ec_state_name
See NOTE 3.
Comment
A comment per IEC 61131-3-2.1.5 without (* and *) delimiters
x, y
See Annex B.
ECTransition
An EC transition as defined in IEC 61499-1.
Source ec_state_name
ec_state_name
Destination
ec_transition_condition
Condition
x, y
See Annex B.
ECAction
An EC action as defined in IEC 61499-1.
Algorithm algorithm_name
event_output_name
Output
Algorithm
An in a specified language (NOTE 1)
algorithm
algorithm_name
Name
Comment
A comment per IEC 61131-3-2.1.5 without (* and *) delimiters
ST
An algorithm in the IEC 61131-3 ST language
Text statement_list
per IEC 61131-3-B.3.2.
– 19 – Copyright © IEC, 2001
Table A.2-2 - LibraryElement DTD Elements

Element Syntax Explanation
Attributes (IEC 61499-1, Annex B.2)

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.

Language
The name of the programming language; see NOTE 1

Text
The algorithm text in the programming language; see NOTE 1
Service
A declaration of a service per IEC 61499-1-3.1.2
service_interface_name
RightInterface
service_interface_name
LeftInterface
Comment
A comment per IEC 61131-3-2.1.5 without (* and *) delimiters
ServiceSequence
A declaration of a service sequence per IEC 61499-1-3.1.2
sequence_name
Name
Comment
A comment per IEC 61131-3-2.1.5 without (* and *) delimiters
InputPrimitive
An "input" service primitive per IEC 61499-1-3.1.2
service_interface_name
Interface
Event (([plug_name '.'] event_input_name)
| (socket_name '.' event_output_name))
['+' | '-']
Parameters input_variable_name {',' input_variable_name}
OutputPrimitive
An "output" service primitive per IEC 61499-1-3.1.2
service_interface_name
Interface
('NULL'
Event
| ([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-2.5

Name adapter_type_name
Comment
A comment per IEC 61131-3-2.1.5 without (* and *) delimiters
ResourceType
A declaration of a resource type per IEC 61499-1-4.1.1
Name resource_type_name
Comment
A comment per IEC 61131-3-2.1.5 without (* and *) delimiters
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-4.1.2
Name device_type_name
Comment
A comment per IEC 61131-3-2.1.5 without (* and *) delimiters

– 20 – Copyright © IEC, 2001
Table A.2-2 - LibraryElement DTD Elements

Element Syntax Explanation
Attributes (IEC 61499-1, Annex B.2)

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_instance_name
Type
resource _type_name
Comment
A comment per IEC 61131-3-2.1.5 without (* and *) delimiters
System
A declaration of a system configuration per IEC 61499-1-4.2
Name system_name
Comment
A comment per IEC 61131-3-2.1.5 without (* and *) delimiters
Application
A declaration of an application per IEC 61499-1-4.2.2
Name application_name
Comment
A comment per IEC 61131-3-2.1.5 without (* and *) delimiters
Mapping
Mapping of a function block instance from an application onto a function block
instance in a resource.
From fb_instance_reference
Hierarchical function block instance name in its
application, e.g., APP1.SUBAPP2.FB2
To fb_resource_reference
Hierarchical function block instance name in the
physical system, e.g., DEV1.RES2.FB2
Device
A declaration of a device configuration per IEC 61499-1-4.2.3
Name
device_instance_name
Type
device_type_name
Comment
A comment per IEC 61131-3-2.1.5 without (* and *) delimiters
DeviceParameters Declarations of the values of parameters of a device instance.
SubAppType A declaration of a subapplication type per IEC 61499-1-2.4
Name subapp_type_name
Comment
A comment per IEC 61131-3-2.1.5 without (* and *) delimiters

SubAppEvent
A declaration of an event interface of a subapplication type.
event_input_name
Name
See NOTE 10.
| event_output_name
event_type
Type
Comment
A comment per IEC 61131-3-2.1.5 without (* and *) delimiters
SubApp
A subapplication instance as defined in IEC 61499-1.
Name
subapp_instance_name
See NOTE 3.
Type
subapp_type_name
Comment
A comment per IEC 61131-3-2.1.5 without (* and *) delimiters
x, y
See Annex B.
– 21 – Copyright © IEC, 2001
Table A.2-2 - LibraryElement DTD Elements

Element Syntax Explanation
Attributes (IEC 61499-1, Annex B.2)

NOTE 1 - The specification of algorithms in languages other than FBD, ST and LD is beyond the scope of this

Part of IEC 61499.
NOTE 2 - Since the FBD and ST languages are available for the specification of complex algorithms, it is
recommended that the usage of the LD language in the context of this Standard be limited to rungs

performing the evaluation of assignment statements of the form := . For

portability between software tools, it is further recommended that the XML Expression element have

the following simple postfix-operator textual syntax with whitespace_separated terms:
expression ::= and_expression
and_expression ::= (variable_name ['!']) | or_expression

| and_expression and_expression '&'
or_expression ::= and_expression | or_expression or_expression '|'
See EXAMPLE 1 for an illustration of this recommended usage.
NOTE 3 - The appropriate subset of the production fb_instance_reference should be used, depending
on the context of the FBNetwork element. For instance, in the context of an FBType element, only
the fb_instance_name portion of the reference would be used.
NOTE 4 – Depending on the context, the syntax of a Source or Destination element should correspond
to the syntax of the respective element in one of the productions event_conn, data_conn,
adapter_conn, subapp_event_conn, subapp_data_conn, config_event_conn,
config_data_conn, config_adapter_conn, devtype_event_conn,
devtype_data_conn, or devtype_adapter_conn given in Annex B of IEC 61499-1.
NOTE 5 – The productions event_input_name and input_variable_name apply when the Event
element is part of an element, and and
EventInputs event_output_name
output_variable_name apply when it is part of an EventOutputs element.
NOTE 6 - The productions input_variable_name, output_variable_name and
internal_variable_name apply when the associated VarDeclaration element is part of an
InputVars, OutputVars or InternalVars element, respectively.
NOTE 7- The syntax of this element when present shall be 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 element is missing, the variable is not an array.
NOTE 8 - The syntax of this element is the syntax for initialization of the corresponding variable type as defined
in Annex B.1.4.3 of IEC 61131-3.
NOTE 9 - The productions plug_name and socket_name apply when the associated
AdapterDeclaration element is part of a Plugs or Sockets element, respectively.
NOTE 10 - The product
...