IEC 61804-3 PDF

IEC is available from the IEC at FieldComm Group does not license this document directly. Find the most up-to-date version of IEC at Engineering IEC Edition INTERNATIONAL. STANDARD. Function blocks (FB) for process control –. Part 3: Electronic Device Description Language .

Author: Yoshura Kagagal
Country: New Zealand
Language: English (Spanish)
Genre: Photos
Published (Last): 8 September 2013
Pages: 269
PDF File Size: 13.44 Mb
ePub File Size: 17.47 Mb
ISBN: 889-1-58629-356-4
Downloads: 48337
Price: Free* [*Free Regsitration Required]
Uploader: Tojagal

Home Documents IEC Post on Apr views. Consolidated editionsThe IEC is now publishing consolidated versions of its publications. For example, edition numbers 1. Information relating to this publication, including its validity, is available in the IEC Catalogue of 61840-3 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 uec, as well as the list of publications issued, is also iiec from the following: IEC Web Site www.

On-line information is also available on recently issued publications, withdrawn and replaced publications, as well as corrigenda.

Please contact the Customer Service Centre see below for further information. Customer 611804-3 Centre If you have any questions regarding this publication or need further assistance, 618043 contact the Customer Service Centre: Electronic Device Description Language EDDL IEC Copyright iiec all rights reservedNo 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.

The object of IEC is to promote international co-operation on all questions concerning standardization in the electrical and electronic fields. 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 nongovernmental 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.

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. Any divergence between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in the latter.

Use of the referenced publications is indispensable for the correct application of this publication. IEC take no position concerning the evidence, validity and scope of this patent right.

The holder of this patent right has assured the IEC that he is willing to negotiate licenses under reasonable and non-discriminatory iecc and conditions with applicants throughout the world. Ie this respect, the statement of the holder of this patent right is registered with IEC. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights other than those identified above.

IEC shall not be held responsible for identifying any or all such patent rights. This International Standard has been prepared by subcommittee 65C: Digital communications, of IEC technical committee Industrial-process measurement and control. The text of this standard is based on the following documents: 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: At this date, the publication will be reconfirmed; withdrawn; replaced by a revised edition, or amended.


A bilingual version of this publication may be issued at a later date. It allows the manufacturers to use the same description method for devices based on different technologies and platforms. Figure 1 shows these aspects. This standard specifies EDDL as a generic language for describing the properties of automation system components.

EDDL is capable of describing device parameters and their dependencies; device functions, for example, iwc mode, calibration; graphical representations, for example, menus; interactions with control devices graphical representations enhanced user interface graphing systempersistent data store.

Tool implementation is outside the scope of this standard. This standard specifies the semantic and lexical structure in a 618043 manner. A specific syntax is defined in Annex A, but it is possible to use the semantic model also with different syntaxes. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document including any amendments applies.

Typically, they provide status information or govern the operation of an object. Attributes may also affect the behaviour of an object. Attributes are divided into class attributes and instance attributes. NOTE 2 A device contains one or more resources.

NOTE 2 The system is considered to be separated from the environment and other external systems by an imaginary surface, which can cut the links between them and the considered system. A general form of the lexical structures is shown below. This element shall be coded in a concrete syntax. It is not required to code this element with the name ABC. It is also possible to code this element, for example, with a tag number.

IEC | IEC Webstore

Field1 and field2 are fields of the lexical element ABC. Each field is mandatory and may have more than one attribute. If a field has attributes, the presence of the attributes is specified in a table. A comma separates Field1 and 2. The comma is a lexical element and is not coded explicitly. If a field has additional attributes, the attributes are defined in a table. The table layout and the possible usage qualifiers are shown in Table 1.

Table 1 Field attribute descriptionsUsage m o s yyy xxx z1 Attribute Description The presence of this attribute is mandatory The presence of this attribute is optional The presence of this attribute is selectable with other attributes, which are also marked with s in the usage column. Only one of the selectable attributes z1 or z2 is present The presence of this attribute is selectable with other attributes, which are also marked with s in the usage column.

Only one of the selectable attributes z1 or z2 is present The presence of this 6180-3 is conditional and it is only present if the condition is truesz2cuuuThe characters in the Usage column have the following meanings. One, and only one, of the fields market with s Z1 or Z2 shall be present. The condition is described in the Description column. In the Attribute column, if more than one 6180-3 exists, which have the same usage, the attributes are sorted in alphabetical order.

It may be used more than once. If it is used it may be used more than once. The plus behind the closing bracket indicates that field1 and field2 are used at least once and may be used more than once as group. ABC field1, field2, field3 indicates that field2 and field3 are used in conjunction with the conditional expression, conditional constructs are specified in 7.

The expression refers only to the fields within the preceding curved brackets.


Device Integration

Usage of conditional expressions is optional. The EDDL provides a set of scalable basic language elements to handle simple, complex or modular devices. NOTE Data in a text field, which is marked with a country code like Japanese, may use multi-byte code. However, the EDD application uses the communication system to transfer its information. An EDD contains constructs that support mapping to a supporting communication system.

The device manufacturer defines the objects, which are reflected 661804-3 the logical representation of the objects within an EDD application. For that reason, EDDL has language elements, which map the EDD data to the kec representation of the communication system, so that the user of an EDD does not need to know the physical location address of a device object.

EDD describes the management of information to be displayed to the user. The resulting EDD contains information such as: EDD supports text strings common terms, phrases etc. Text strings may be stored in separate dictionaries. There may be more than one dictionary for one EDD. An EDD implementation includes sufficient information about the target device, for example, manufacturer, 16804-3 type, revision, etc.

This is used to match a specific EDD to a specific device. If the automation system supports the EDD method, a system integration can be made by the user. The EDDs for devices may be embedded in device memory or delivered using separate storage media or downloaded from an appropriate network server. EDDs are normally stored as source files or preprocessed files. Preprocessing supports, for example, substitution of definitions and inclusion of external text.

IEC 61804-3 2006

The output of the preprocessor is a complete EDD without any preprocessor directive. The lexical structure and its formal description use the same name. NOTE Instead of the specified formal definitions and syntax in Annex A, another specification may be developed as an additional option. The library of Builtins is defined in Annex B.

In addition to EDD profiles, implementing consortia also publish Device Profiles, which are used to support interchangeability of compliant devices. The EDDL provides a set of language elements for these purposes. For a specific EDD implementation it is not necessary to use all of the elements provided by the language.

Compatible subsets of EDDL are permitted and may be specified using profiles for example, choice of constructs, number of recursions, and selection of options. Profiles supported by some industrial consortia are specified in Annex D. EDD developers are required to identify within each device details as to which profile has been used.

NOTE Beside the defined syntax in this standard, it is possible to use other syntax definitions, which may be added in future to allow other features and representations for future progress.

Frequently used text strings, for example, help text and multi-lingual lists of labels should be separated in a text dictionary see 7. Identification information shall be the first entry in every EDD file and shall appear only once.

The identification information uniquely identifies the version of EDDL used, together with the specific device type, model codes and revision details covered by the EDD file. Some constructs have similar names and functions while differing in their detailed specification.