CLC/TR 61804-4:2007

SLOVENSKI STANDARD
01-december-2007
Funkcijski bloki (FB) za nadzor procesov - 4. del: Vodilo za interoperabilnost EDD
(IEC/TR 61804-4:2006)
Function blocks (FB) for process control - Part 4: EDD Interoperability Guideline
Ta slovenski standard je istoveten z: CLC/TR 61804-4:2007
ICS:
25.040.40 Merjenje in krmiljenje Industrial process
industrijskih postopkov measurement and control
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

TECHNICAL REPORT
CLC/TR 61804-4
RAPPORT TECHNIQUE
June 2007
TECHNISCHER BERICHT
ICS 25.040.40
English version
Function blocks (FB) for process control -
Part 4: EDD interoperability guideline
(IEC/TR 61804-4:2006)
Blocs fonction  Funktionsbausteine
pour les processus industriels - für die Prozessautomation -
Partie 4: Recommandations Teil 4: Leitfaden für die Interoperabilität
pour l'interopérabilité EDD von EDD-Anwendungen
(IEC/TR 61804-4:2006)
(CEI/TR 61804-4:2006)
This Technical Report was approved by CENELEC on 2007-04-09.

CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Cyprus, the
Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia,
Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain,
Sweden, Switzerland and the United Kingdom.

CENELEC
European Committee for Electrotechnical Standardization
Comité Européen de Normalisation Electrotechnique
Europäisches Komitee für Elektrotechnische Normung

Central Secretariat: rue de Stassart 35, B - 1050 Brussels

© 2007 CENELEC - All rights of exploitation in any form and by any means reserved worldwide for CENELEC members.
Ref. No. CLC/TR 61804-4:2007 E

Foreword
The text of the Technical Report IEC/TR 61804-4:2006, prepared by SC 65C, Industrial networks, of
IEC TC 65, Industrial-process measurement and control, was submitted to vote and was approved by
CENELEC as CLC/TR 61804-4 on 2007-04-09.
Annex ZA has been added by CENELEC.
__________
Endorsement notice
The text of the Technical Report IEC/TR 61804-4:2006 was approved by CENELEC as a Technical Report
without any modification.
__________
- 3 - CLC/TR 61804-4:2007
Annex ZA
(normative)
Normative references to international publications
with their corresponding European publications

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.

NOTE  When an international publication has been modified by common modifications, indicated by (mod), the relevant EN/HD
applies.
Publication Year Title EN/HD Year

1)
IEC 60050-351 - International Electrotechnical Vocabulary - -
(IEV) -
Part 351: Automatic control
IEC 61804-2 2006 Function blocks (FB) for process control - EN 61804-2 2007
Part 2: Specification of FB concept

IEC 61804-3 2006 Function blocks (FB) for process control - EN 61804-3 2007
Part 3: Electronic device description language
(EDDL)
ISO/IEC 15948 2004 Information technology - Computer graphics - -
and image processing - Portable Network
Graphics (PNG) - Functional specification

1)
Undated reference.
TECHNICAL IEC
REPORT TR 61804-4
First edition
2006-12
Function blocks (FB) for process control –
Part 4:
EDD interoperability guideline
© IEC 2006 ⎯ 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: +41 22 919 02 11 Telefax: +41 22 919 03 00 E-mail: inmail@iec.ch Web: www.iec.ch
PRICE CODE
Commission Electrotechnique Internationale XA

International Electrotechnical Commission
МеждународнаяЭлектротехническаяКомиссия
For price, see current catalogue

– 2 – TR 61804-4 © IEC:2006(E)
CONTENTS
FOREWORD.4
INTRODUCTION.6

1 Scope.7
2 Normative references.7
3 Terms, definitions, abbreviated terms and acronyms .7
3.1 Terms and definitions .7
3.2 Abbreviated terms and acronyms .8
4 User interface support .8
4.1 Overview .8
4.2 Menu conventions for applications .8
4.3 Menu conventions for PC-based applications .8
4.4 Menu conventions for all applications.16
4.5 User interface extensions .16
4.6 Layout rules.21
4.7 Default menu styles .29
5 Additional user interface elements .30
5.1 Overview .30
5.2 Graph and chart.31
5.3 IMAGE .45
5.4 GRID.46
6 EDDL data description .47
6.1 Variables .47
6.2 EDDL application stored device data.48
7 EDDL built-in library.57
7.1 User interface built-ins.57

Annex A (informative) Technology specific guidance.59

Figure 1 – Example of an EDD application for diagnostics .13
Figure 2 – Example of an EDD application for process variables.14
Figure 3 – Example of an EDD application for primary variables .14
Figure 4 – Example of an EDD application for process-related device features.15
Figure 5 – Example of an EDD application for device features .15
Figure 6 – Example of an EDD application for a variable of type BIT_ENUMERATED.20
Figure 7 – Example of an EDD for an overview menu .22
Figure 8 – Example of an EDD application for an overview window .22
Figure 9 – Example of an EDD using COLUMNBREAK .22
Figure 10 – Example of an EDD application for an overview window .23
Figure 11 – Example of an EDD application for an overview window .23
Figure 12 – Example of an EDD application for an overview window .24
Figure 13 – Example of an EDD for in-line graphs and charts .24
Figure 14 – Example of an EDD application for an in-line graph .25
Figure 15 – Example of an EDD for full-width graphs and charts .25

TR 61804-4 © IEC:2006(E) – 3 –
Figure 16 – Example of an EDD application for a full-width graph .26
Figure 17 – Example of an EDD for nested containers .27
Figure 18 – Example of an EDD application for nested containers.27
Figure 19 – Example of an EDD for EDIT_DISPLAYS .28
Figure 20 – Example of an EDD application for EDIT_DISPLAYS.28
Figure 21 – Example of an EDD for images .29
Figure 22 – Example of an EDD application for images.29
Figure 23 – HEIGHT and WIDTH attributes for CHART and GRAPH .31
Figure 24 – EMPHASIS attribute to differentiate one or more SOURCEs or
WAVEFORMs .32
Figure 25 – Example of a chart with one curve in a dialogue .34
Figure 26 – Graph and the visual elements.37
Figure 27 – Result of the EDD example .47
Figure 28 – Example of a file declaration .49
Figure 29 – Example of comparing valve signatures .50
Figure 30 – Example of more complex file declaration .51
Figure 31 – Example of reviewing the stored radar signals.52

Table 1 – List of defined menu identifiers .9
Table 2 – List of defined menu identifiers .30
Table 3 – Image formats .45

– 4 – TR 61804-4 © IEC:2006(E)
INTERNATIONAL ELECTROTECHNICAL COMMISSION
___________
FUNCTION BLOCKS (FB) FOR PROCESS CONTROL –

Part 4: EDD interoperability guideline

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 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.
The main task of IEC technical committees is to prepare International Standards. However, a
technical committee may propose the publication of a technical report when it has collected
data of a different kind from that which is normally published as an International Standard, for
example, “state of the art”.
Technical reports do not necessarily have to be reviewed until the data they provide are
considered to be no longer valid or useful by the maintenance team.
IEC 61804-4, which is a Technical Report, has been prepared by subcommittee 65C: Digital
communications, of IEC technical committee 65: Industrial-process measurement and control.
The text of this Technical Report is based on the following documents:
Enquiry draft Report on voting
65C/410/DTR 65C/417/RVC
TR 61804-4 © IEC:2006(E) – 5 –

Full information on the voting for the approval of this Technical Report 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.
The list of all the parts of the IEC 61804 series, under the general title Function blocks (FB) for
process control, can be found on the IEC website.
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 publication may be issued at a later date.

– 6 – TR 61804-4 © IEC:2006(E)
INTRODUCTION
This Technical Report
• contains an overview of the use of EDDL;
• provides examples demonstrating the use of the EDDL constructs;
• shows how the use cases are fulfilled; and
• shows the proper EDD application interpretation for each example.
This Technical Report is not an EDDL tutorial and is not intended to replace the EDDL
specification.
Instructions are provided for the EDD application, which describe what is to be performed
without prescribing the technology used in the host implementation. For example, the FILE
construct describes data that is to be stored by the EDD application on behalf of the EDD. The
FILE construct does not specify how the data is to be stored. The EDD application can use a
database, a flat file, or any other implementation it chooses.

TR 61804-4 © IEC:2006(E) – 7 –
FUNCTION BLOCKS (FB) FOR PROCESS CONTROL –

Part 4: EDD interoperability guideline

1 Scope
This part of IEC 61804 is a guideline to support EDD interoperability.This Technical Report is
intended to ensure that field device developers use the EDDL constructs consistently and that
the EDD applications have the same interpretations of the EDD. It supplements the EDDL
specification to promote EDDL application interoperability and improve EDD portability between
EDDL applications.
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 60050-351, International Electrotechnical Vocabulary (IEV) – Part 351: Automatic control
IEC 61804-2:2006, Function blocks (FB) for process control − Part 2: Specification of FB
concept
IEC 61804-3:2006 Function blocks (FB) for process control − Part 3: Electronic Device Description
Language (EDDL)
ISO/IEC 15948:2004, Information technology – Computer graphics and image processing –
Portable Network Graphics (PNG) – Functional specification
3 Terms, definitions, abbreviated terms and acronyms
3.1 Terms and definitions
For the purposes of this document, some of the terms and definitions in IEC 60050-351, as
well as the following, some of which have been compiled from the referenced documents,
apply.
3.1.1
EDD developer
individual or team that develops an EDD
3.1.2
EDD application
software or programmes utilizing the EDD to guide the operation of the application
NOTE These applications include configuration tools, calibrators, instrument management packages, and
instrument simulators
3.1.3
end user
individual using the field device and/or the EDDL application

– 8 – TR 61804-4 © IEC:2006(E)
3.2 Abbreviated terms and acronyms

CP Communication Profile
CPF Communication Profile Family
EDD Electronic Device Description. A platform and application-independent model or
description of a field device written using EDDL. An EDD describes the properties,
standard procedures and status associated with a device.
EDDL Electronic Device Description Language
FF Fieldbus Foundation; see www.fieldbus.org ®
HCF HART Communication Foundation; see www.hartcomm.org
OPC Open connectivity; OPC Foundation; see www.opcfoundation.org
PC Personal computer
PNO PROFIBUS Nutzerorganisation e.V.; see www.profibus.com

4 User interface support
4.1 Overview
Most EDD applications can be characterized as either a PC application or a hand-held
application. Due to the relatively small screen of a hand-held device, hand-held applications
can only display a small amount of information at any given time. On the other hand, PC
applications can provide a much more beneficial user interface, largely due to their larger
screen size.
To support the capabilities of PC applications, the MENU construct has been extended in
IEC 61804-3 compared to IEC 61804-2. Due to the differences in the user interfaces of PC
applications and hand-held applications, it is expected that many devices will define two MENU
hierarchies – one for hand-held applications and the other for PC applications. Some MENUs
may be used in both hierarchies. Therefore, the entire hierarchy need not be specified twice.
Different menu structures for different classes of applications are possible. This guideline may
be used to create menu structures in an EDD that are interpreted by applications in an
unambiguous way. To promote interoperability across applications, it is highly recommended
that all EDD applications follow this guideline.
4.2 Menu conventions for applications
There are existing solutions for hand-held application menus and these solutions can be used.
This technical report does not provide specific conventions for hand-held applications.
4.3 Menu conventions for PC-based applications
4.3.1 Overview
EDD applications use special menus in the EDDs to show the user interface of the device.
Such menus are defined for diagnostic, process variables, device features, and offline
configuration. Defined identifiers are defined for the different root menus. Other submenus can
be underneath these root menus.
4.3.2 Diagnostic
The diagnostic menu includes views that show the device state, detailed diagnostic information
and may include graphical views that show, for example, a valve signature.

TR 61804-4 © IEC:2006(E) – 9 –
4.3.3 Process variables
The process variable menu includes views that show process measurements and set points
with their quality and important information for process operators, for example, ranges.
4.3.4 Device features
The device feature menu includes features for device support. These features can be split into
process-related and device-specific features. This structure is not required if the number of
features is too small for splitting. Submenus that represent any structuring are allowed on the
device feature menu. In case of such submenus, the menus that are underneath can be split
into process-related and device-specific features.
4.3.5 Offline configuring
This menu hierarchy includes parameters, variables, and methods for offline configuration. It
contains, in particular, all of the application-specific parameters of the device and may also
contain important read-only and writeable variables. For more information about application-
specific parameters, see 4.4. The menu can have offline methods, for example, configuration
assistants.
4.3.6 Overview defined identifiers
Table 1 lists defined menu identifiers.
Table 1 – List of defined menu identifiers
Menu Identifier Short description
diagnostic_root_menu Diagnostic view
process_variables_root_menu Process variable views
device_root_menu Device feature views
offline_root_menu Menu hierarchy for offline configuration

4.3.7 Example of EDD menu structure
This is an example of additional menus that can be added to an EDD for PC applications.
These menus are additional to the existing menus for the applications. This example is HART-
1 2
specific. Examples for Foundation Fieldbus and PROFIBUS would be very similar.
MENU diagnostic_root_menu
{
LABEL "Diagnostics";
STYLE MENU;
ITEMS
{
status_window,  /* menu: style=window */
self_test  /* method */
}
}
MENU status_window
{
LABEL "Status";
STYLE WINDOW;
ITEMS
{
standard_diagnostics_page, /* menu: style=page */
devspec_diagnostics_page /* menu: style=page */
}
}
___________
Communication Profile Family CPF 1 according to IEC 61784-1:2003, Digital data communications for
measurement and control – Part 1: Profile sets for continuous and discrete manufacturing relative to fieldbus
use in industrial control systems.
CP3/1 and CP3/2 of Communication Profile Family CPF 3 according to IEC 61784-1 (see footnote 3).

– 10 – TR 61804-4 © IEC:2006(E)
MENU standard_diagnostics_page
{
LABEL "Standard";
STYLE PAGE;
ITEMS
{
device_status  /* variable */
}
}
MENU devspec_diagnostics_page
{
LABEL "Device Specific";
STYLE PAGE;
ITEMS
{
xmtr_specific_status_1, /* variable */
xmtr_specific_status_2 /* variable */
}
}
METHOD self_test
{
LABEL "Self Test";
DEFINITION
{
/* elided */
}
}
MENU process_variables_root_menu
{
LABEL "Process Variables";
STYLE MENU;
ITEMS
{
overview_window, /* menu: style=window */
primary_vars_window /* menu: style=window */
}
}
MENU overview_window
{
LABEL "Overview";
STYLE WINDOW;
ITEMS
{
process_vars_page  /* menu: style=page */
}
}
MENU process_vars_page
{
LABEL "Process Variables";
STYLE PAGE;
ITEMS
{
pressure_group,  /* menu: style=group */
temperature_group  /* menu: style=group */
}
}
MENU pressure_group
{
LABEL "Pressure";
STYLE GROUP;
ITEMS
{
pv_digital_value, /* variable */
pv_upper_range_value, /* variable */
pv_lower_range_value /* variable */
}
}
MENU temperature_group
{
LABEL "Temperature";
STYLE GROUP;
ITEMS
{
sv_digital_value, /* variable */
sv_upper_range_value, /* variable */
sv_lower_range_value /* variable */

TR 61804-4 © IEC:2006(E) – 11 –
}
}
MENU primary_vars_window
{
LABEL "Primary Variables";
STYLE WINDOW;
ITEMS
{
pressure_chart_page, /* menu: style=page */
temperature_chart_page /* menu: style=page */
}
}
MENU pressure_chart_page
{
LABEL "Pressure";
STYLE PAGE;
ITEMS
{
pressure_chart  /* chart */
}
}
CHART pressure_chart
{
/* elided */
}
MENU temperature_chart_page
{
LABEL "Temperature";
STYLE PAGE;
ITEMS
{
temperature_chart /* chart */
}
}
CHART temperature_chart
{
/* elided */
}
MENU device_root_menu
{
LABEL "Device";
STYLE MENU;
ITEMS
{
process_related_window, /* menu: style=window */
device_specific_window, /* menu: style=window */
master_reset  /* method */
}
}
MENU process_related_window
{
LABEL "Process Related";
STYLE WINDOW;
ITEMS
{
identification_page, /* menu: style=page */
output_info_page /* menu: style=page */
}
}
MENU identification_page
{
LABEL "Identification";
STYLE PAGE;
ITEMS
{
tag,  /* variable */
manufacturer,  /* variable */
device_type,  /* variable */
device_revision, /* variable */
descriptor,  /* variable */
message  /* variable */
}
}
– 12 – TR 61804-4 © IEC:2006(E)
MENU output_info_page
{
LABEL "Output Information";
STYLE PAGE;
ITEMS
{
range_values_group, /* menu: style=group */
sensor_limits_group /* menu: style=group */
}
}
MENU range_values_group
{
LABEL "Range Values";
STYLE GROUP;
ITEMS
{
pv_units,  /* variable */
pv_urv,  /* variable */
pv_lrv  /* variable */
}
}
MENU sensor_limits_group
{
LABEL "Sensor Limits";
STYLE GROUP;
ITEMS
{
sensor_units,  /* variable */
upper_sensor_limit, /* variable */
lower_sensor_limit /* variable */
}
}
MENU device_specific_window
{
LABEL "Device Specific";
STYLE WINDOW;
ITEMS
{
identification_page, /* menu: style=page */
calibration_page /* menu: style=page */
}
}
MENU calibration_page
{
LABEL "Calibration";
STYLE PAGE;
ITEMS
{
sensor_limits_group, /* menu: style=group */
sensor_trim_group /* menu: style=group */
}
}
MENU sensor_trim_group
{
LABEL "Sensor Trim";
STYLE GROUP;
ITEMS
{
upper_sensor_trim_point, /* variable */
lower_sensor_trim_point, /* variable */
sensor_trim  /* method */
}
}
METHOD master_reset
{
LABEL "Master Reset";
DEFINITION
{
/* elided */
}
}
TR 61804-4 © IEC:2006(E) – 13 –
4.3.8 User interface
4.3.8.1 Diagnostics
Figure 1 shows an example of an EDD application for diagnostics.

Figure 1 – Example of an EDD application for diagnostics

– 14 – TR 61804-4 © IEC:2006(E)
4.3.8.2 Process variables
Figure 2 and Figure 3 show examples of EDD applications for process variables.

Figure 2 – Example of an EDD application for process variables

Figure 3 – Example of an EDD application for primary variables

TR 61804-4 © IEC:2006(E) – 15 –
4.3.8.3 Device features
Figure 4 and Figure 5 show examples of EDD applications for device features.

Figure 4 – Example of an EDD application for process-related device features

Figure 5 – Example of an EDD application for device features

– 16 – TR 61804-4 © IEC:2006(E)
4.4 Menu conventions for all applications
4.4.1 Overview
This menu is used by hand-held and PC applications.
4.4.2 Upload and download
There are two kinds of parameters in a device:
• application-specific parameters; and
• device-specific parameters.
When a device is replaced at a particular plant location, the application-specific parameters
from the old device should be downloaded into the new device. However, the device-specific
parameters are never downloaded because they are specific to the physical device.
For loading the application-specific parameter two menus should be used.
• The “download_variables” menu specifies the order and the total set of the application-
specific parameters that should be read from the device.
• The “upload_variables” menu specifies the order and the total set of the application-specific
parameters that should be loaded to the device.
Both the upload and download menus should contain all of the application-specific parameters
for the device. If the device has special needs in terms of handling the data, errors, timing of
the commands, and so on, the upload and download menus may contain methods in addition
to, or instead of, variables.
HART and PROFIBUS supports the menu called upload_variables and download_variables.
The definition of these menus for both HART and PROFIBUS is consistent with the definition of
the upload and download menus described above. Therefore, these well-known names for the
upload and download menus are used. If upload and download menus are not included in the
EDD, then this capability, if supported by the device, is EDD application-specific.
The ordering in the off-line configuration menu (offline_root_menu) is user-aspect-orientated in
contrast to the upload/download menus that are ordered from a communications point of view.
4.5 User interface extensions
4.5.1 Overview
The user interface extensions are based on a simple user interface model. The model consists
of two concepts:
• containers; and
• contained items.
Containers are so named because they contain other user interface elements. Containers may
include: menus, windows, dialogue boxes, tables, pages, groups, and other containers.
Containers correspond to a MENU. They are distinguished from one another via the STYLE
attribute of the MENU. This STYLE attribute indicates how the MENU will be displayed. EDD
constructs for these user interface components are the same as a MENU except for their
display.
Contained items may contain: variables, methods, edit displays, graphs, charts, images, static
text and separators. The contained items correspond to various EDD constructs. For example,
a variable corresponds to a VARIABLE, a method corresponds to a METHOD, an edit display
corresponds to an EDIT_DISPLAY, a graph corresponds to a GRAPH and a chart corresponds
to a CHART.
TR 61804-4 © IEC:2006(E) – 17 –
4.5.2 Containers
4.5.2.1 Overview
This clause describes the general layout of containers.
4.5.2.2 Menu
A menu takes the form of a drop-down menu, a pop-up menu or a navigation bar. A menu may
contain windows, dialogue boxes, tables, methods, and separators.
4.5.2.3 Window
A window takes the form of a modeless window. A window may contain dialogue boxes, tables,
pages, groups, methods, variables, edit displays, graphs, charts, images, static text,
separators, and other windows. Windows may not contain menus.
When a container contains a window, the container should render this window as either a
button or a hyperlink. The LABEL of the corresponding MENU should appear on the button or
as the hyperlink text. When the button or hyperlink is pressed, the corresponding window
should be opened on top of the calling dialogue or window.
4.5.2.4 Dialogue box
A dialogue box takes the form of a modal window. It may contain windows, tables, pages,
groups, methods, variables, edit displays, graphs, charts, images, static text, separators, and
other dialogue boxes. Dialogue boxes may not contain menus.
When a container contains a dialogue box, the dialogue box should be rendered by the
container as either a button or a hyperlink. The LABEL of the corresponding MENU should
appear on the button or as the hyperlink text. When the button or hyperlink is pressed, the
corresponding dialogue box should be opened on top of the calling dialogue or window. If a
dialogue is called from a window, no interactions are possible unless the dialogue is closed.
4.5.2.5 Table
A table takes the form of a grid. A table may contain variables, methods and other menus. The
submenus build a hierarchy, which may show the device to the user in a compact way, for
example, a table in which each row is a variable, method or menu.
The STYLE attribute (STYLE = TABLE) should be defined only on the root menu of a hierarchy.
The EDD application also uses the style of the root for its items unless another style is defined.
4.5.2.6 Page
The pages within a container form a tabbed dialogue. A page may contain windows, dialogue
boxes, tables, groups, methods, variables, edit displays, graphs, charts, images, static text,
and separators. Pages may not contain menus of STYLE MENU or other pages.
A row break, a column break, and a SEPARATOR between pages will be ignored by the EDD
application.
4.5.2.7 Group
A group takes the form of a group box. A group may contain windows, dialogue boxes,
methods, variables, edit displays, graphs, charts, images, static text, separators, and other
groups. In order to maintain a clear arrangement on the user interface, the following restricting
rules apply.
– 18 – TR 61804-4 © IEC:2006(E)
• The nesting level of GROUP declarations is restricted to two. In other words, a GROUP
may contain further GROUPs but these may not contain further GROUPs.
• Groups may not contain menus or pages.
Within a GROUP, usually logically related parameters and methods are grouped. The title of
the GROUP indicates this relation, for example, “AnalogInput 1”. Often the same string is also
used in the labels of the GROUP items, for example, “AnalogInput1_StaticRevision” or “Analog
Input1_Blockmode”. In order to avoid this duplication of information, the EDD-editor may
assemble the items of a GROUP in a COLLECTION in order to override the original labels.
If the parameters are to be referred to in a GROUP the parameters can be referenced using
the COLLECTION; in other cases, especially without additional semantic context, the
parameters can be referenced direct.
Example of the use of a COLLECTION within a GROUP style MENU.
VARIABLE ai1_strev
{
LABEL "Analog Input 1: Static Revision";
TYPE INTEGER(4);
}
VARIABLE ai1_blomo
{
LABEL "Analog Input 1: Block Mode";
TYPE INTEGER(1);
}
MENU ai1_group_double  /* Leads to double display of */
“Analog_Input1” label
{
LABEL "Analog Input 1";
STYLE GROUP;
ITEMS
{
ai1_strev,
ai1_blomo
}
}
COLLECTION ai1_groupcol
{
MEMBERS
{
strev,ai1_strev,"Static Revision";
blomo,ai1_blomo,"Block Mode";
}
}
MENU ai1_group_single  /* Leads to single display of */ “Analog_Input1”
label
{
LABEL "Analog Input 1";
STYLE GROUP;
ITEMS
{
ai1_groupcol.strev,
ai1_groupcol.blomo
}
}
4.5.3 Contained items
4.5.3.1 Overview
This subclause describes how a container renders contained items. All containers render
contained items in the same way. Contained items, such as methods, variables and others,
have a LABEL attribute. In order not to disturb the layout of the EDD application, for example,
with oversized buttons for methods, the EDD developer should not use very long strings for
LABELs. For this reason, some EDD applications may truncate these labels.

TR 61804-4 © IEC:2006(E) – 19 –
4.5.3.2 Methods
A method should be rendered as a button or a hyperlink. The LABEL of the corresponding
METHOD should appear on the button or as the hyperlink text. When the button or hyperlink is
pressed, the corresponding METHOD should be executed.
4.5.3.3 Variables
The label, the value, and, if defined, the units of the variable should be displayed in a manner
consistent with the definition of the corresponding VARIABLE.
The general handling of variables is as follows.
• HANDLING = READ or menu item attribute is READ_ONLY: the value of the variable should
not be editable.
• CLASS = DYNAMIC: the value should be updated continuously with current read values
from the device.
4.5.3.3.1 Variable of type BIT_ENUMERATED
Multiple bits can be packaged in a single-bit enumerated variable. Each bit could have a
distinct meaning. It is possible to display each bit separately and, in addition, to display the
whole BIT_ENUMERATED variable.
In this case, the variable reference should be extended with a mask in square brackets and the
LABEL of the variable is not shown.
EXAMPLE Displaying single bits of a BIT_ENUMERATED variable.
VARIABLE var1
{
LABEL “Var 1”;
TYPE BIT_ENUMERATED
{
{ 1, “Bit 0”},
{ 2, “Bit 1”},
{ 4, “Bit 2”}
}
}
MENU diagnostic_info
{
LABEL “Diagnostic”;
ITEMS
{
var1[2], // Bit 2
var1[4] // Bit 3
}
}
BIT_ENUMERATED variables are always displayed as checkboxes, independent of whether
one bit or all bits are shown.
EXAMPLE The following EDD shows the differences between the full display of a BIT_ENUMERATED variable and
how it could be displayed if all bits are explicitly addressed.
VARIABLE var1
{
LABEL “Var 1”;
TYPE BIT_ENUMERATED
{
{ 1, “Bit 0”},
{ 2, “Bit 1”},
{ 4, “Bit 2”}
}
}
– 20 – TR 61804-4 © IEC:2006(E)
MENU var1_group
{
LABEL var1.LABEL;
STYLE GROUP;
ITEMS
{
var1[1], // Bit 0
var1[2], // Bit 1
var1[4] // Bit 2
}
}
MENU diagnostic_info
{
LABEL “Diagnostic”;
STYLE PAGE;
ITEMS
{
var1,  // all bit should be shown
COLUMNBREAK,
var1[1], // Bit 0
var1[2], // Bit 1
var1[4], // Bit 2
COLUMNBREAK,
var1_group
}
}
This EDD will result in an EDD application as shown in Figure 6.
Diagnostic
Var 1
Var 1 Bit 0 Bit 0
Bit 0
Bit 1 Bit 1
Bit 1
Bit 2 Bit 2
Bit 2
Figure 6 – Example of an EDD application for a variable of type BIT_ENUMERATED
4.5.3.3.2 Variable of type INDEX
When a VARIABLE of type INDEX is presented to the user, the text associated with the indices
of the array should be displayed. If the variable is editable, it should be presented as a combo
box.
4.5.3.4 Edit displays
When a container contains an edit display, the container should render the edit display as
either a button or a hyperlink. The LABEL of the corresponding EDIT_DISPLAY should appear
on the button or as the hyperlink text. When the button or hyperlink is pressed, the
corresponding dialogue box should be opened.
4.5.3.5 Graphs
A graph should be displayed in a manner that is consistent with the definition of the
corresponding GRAPH. The layout rules defined in 5.2.3 should be referred to for information
on the effect of the WIDTH attribute on the layout of the GRAPH.
4.5.3.6 Charts
A chart should be displayed in a manner that is consistent with the definition of the
corresponding CHART. The layout rules defined in 5.2.2 should be referred to for information
on the effect of the WIDTH attribute on the layout of the CHART.

TR 61804-4 © IEC:2006(E) – 21 –
4.5.3.7 Images
The images that are referenced by the MENU should be displayed. The image width will be
adapted on the dialogue, window, page or group width. With the menu item attribute INLINE the
width of the image will be adapted on the width of the items in the same column. If an image is
used without an INLINE attribute, the EDD application makes an implicit row break.
4.5.3.8 Static text
The text that is referenced by the MENU should be displayed. The text will be wrapped in
multiple lines, if the text is longer than the width of the dialogue, window, page, group, or
column.
4.5.3.9 Grid
The LABEL of the grid is shown at first and below the grid area with the width of the dialogue,
window, page, group, or column and the height that is needed to show the data or what is
available on the screen. Scroll bars are used to scroll the grid area, if the width or height is too
small to show the complete data.
4.6 Layout rules
4.6.1 Overview
The general layout of containers is described above. This subclause describes in more detail
how the contents of the container are displayed.
Each container defines the bounding box of the container. This is the area of the container
where its contents may be displayed. For example, the bounding box of a window or dialogue
box is the entire window except the border and title bar.
The contents of the container should be displayed starting at the upper left-hand corner of the
container. The items should be displayed vertically down the left side of the container. When a
separator is encountered, a new column should be created. The items following the separator
should be displayed in the next column starting at the top of the page. This process continues
until all items have been displayed. Column breaks should only be introduced when a separator
is encountered, i.e., the EDD application should not introduce columns breaks on its own.
There is one exception to the layout rules defined in the previous paragraph. If a graph or chart
has a WIDTH attribute that equals LARGE, X_LARGE, and XX_LARGE, the graph and chart
should be displayed across the entire width of the container. Any items following the graph or
chart should be displayed starting at the left side of the container (effectively restarting a new
column beneath the graph or chart).
If static text contains carriage return and line feeds, then the text should be wrapped in lines if
the text is long.
4.6.2 La
...