IEC 62769-7:2023
(Main)Field Device Integration (FDI®) - Part 7: Communication Devices
Field Device Integration (FDI®) - Part 7: Communication Devices
IEC 62769-7:2023 specifies the elements implementing communication capabilities called Communication Devices. The overall FDI®[1] architecture is illustrated in Figure 1. The architectural components that are within the scope of this document have been highlighted in this illustration. The document scope with respect to FDI® Packages is limited to Communication Devices. The Communication Server shown in Figure 1 is an example of a specific Communication Device.
[1] FDI® is a registered trademark of the non-profit organization Fieldbus Foundation, Inc. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the trade name holder.
Intégration des appareils de terrain (FDI®) - Partie 7: Appareils de Communication
L'IEC 62769-7:2023 spécifie les éléments de mise en œuvre des fonctions de communication, appelés Appareils de Communication. L'architecture FDI®[1] complète est représentée à la Figure 1. Les composants architecturaux qui relèvent du domaine d'application du présent document ont été mis en évidence dans cette représentation. Le domaine d'application du document relatif aux Paquetages FDI® est limité aux Appareils de Communication. Le Serveur de Communication représenté à la Figure 1 est un exemple d'Appareil de Communication spécifique.
[1] FDI® est une marque déposée de l’organisation à but non lucratif Fieldbus Foundation, Inc. Cette information est donnée à l'intention des utilisateurs du présent document et ne signifie nullement que l'IEC approuve le détenteur de la marque ou l'emploi de ses produits. La conformité n'exige pas l'utilisation de la marque. L'utilisation de la marque exige l'autorisation du détenteur de la marque.
General Information
Relations
Standards Content (Sample)
IEC 62769-7 ®
Edition 3.0 2023-04
REDLINE VERSION
INTERNATIONAL
STANDARD
colour
inside ®
Field Device Integration (FDI ) –
Part 7: Communication Devices
All rights reserved. Unless otherwise specified, 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
either IEC or IEC's member National Committee in the country of the requester. If you have any questions about IEC
copyright or have an enquiry about obtaining additional rights to this publication, please contact the address below or
your local IEC member National Committee for further information.
IEC Secretariat Tel.: +41 22 919 02 11
3, rue de Varembé info@iec.ch
CH-1211 Geneva 20 www.iec.ch
Switzerland
About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.
About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigendum or an amendment might have been published.
IEC publications search - webstore.iec.ch/advsearchform IEC Products & Services Portal - products.iec.ch
The advanced search enables to find IEC publications by a Discover our powerful search engine and read freely all the
variety of criteria (reference number, text, technical publications previews. With a subscription you will always have
committee, …). It also gives information on projects, replaced access to up to date content tailored to your needs.
and withdrawn publications.
Electropedia - www.electropedia.org
IEC Just Published - webstore.iec.ch/justpublished
The world's leading online dictionary on electrotechnology,
Stay up to date on all new IEC publications. Just Published
containing more than 22 300 terminological entries in English
details all new publications released. Available online and once
and French, with equivalent terms in 19 additional languages.
a month by email.
Also known as the International Electrotechnical Vocabulary
(IEV) online.
IEC Customer Service Centre - webstore.iec.ch/csc
If you wish to give us your feedback on this publication or need
further assistance, please contact the Customer Service
Centre: sales@iec.ch.
IEC 62769-7 ®
Edition 3.0 2023-04
REDLINE VERSION
INTERNATIONAL
STANDARD
colour
inside ®
Field Device Integration (FDI ) –
Part 7: Communication Devices
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
ICS 25.040.40; 35.100.05 ISBN 978-2-8322-6842-1
– 2 – IEC 62769-7:2023 RLV © IEC 2023
CONTENTS
FOREWORD . 6
INTRODUCTION .
1 Scope . 9
2 Normative references . 10
3 Terms, definitions, abbreviated terms, acronyms and conventions . 10
3.1 Terms and definitions . 10
3.2 Abbreviated terms and acronyms . 11
3.3 Conventions . 11
3.3.1 EDDL syntax. 11
3.3.2 Capitalizations . 11
3.3.3 Graphical notation . 11
4 General Overview . 11 ®
5 FDI Communication Package . 13
5.1 General . 13
5.2 EDD . 13
5.2.1 General rules . 13
5.2.2 Device component . 14
5.2.3 CommunicationDevice component . 15
5.2.4 Communication service provider component . 17
5.2.5 Connection Point component . 18
5.2.6 Connection Point collection. 18
5.2.7 Network component . 19
5.2.8 ValidateNetwork . 20
5.2.9 ValidateModules . 21
5.2.10 UIP specifics . 21
5.2.11 Deployment . 22
6 Communication relations . 22 ®
7 FDI Communication Server definition . 23
7.1 General . 23
7.2 General characteristics . 23
7.3 Information Model . 23
7.3.1 General . 23
7.3.2 CommunicationServerType . 27
7.3.3 ServerCommunicationDeviceType . 31
7.3.4 ServerCommunicationServiceType . 36 ®
7.4 OPC UA Server Profile for FDI Communication Server . 39
® ®
7.5 Mapping the FDI Server Information Model to the FDI Communication
Server IM . 40
7.5.1 General . 40
7.5.2 Information Model differences . 40
7.6 Installer. 42 ®
7.7 FDI Communication Package . 42
7.7.1 General . 42
7.7.2 EDD for lightweight Communication Server . 42
7.7.3 EDD for multi-channel Communication Server . 42 ®
7.7.4 COMMANDs in EDDs for FDI Communication Servers . 43
7.7.5 Documentation . 44
7.8 Handling and behaviour . 44
7.8.1 General . 44
7.8.2 Deployment . 45
7.8.3 Server configuration . 45
7.8.4 Start up . 46
7.8.5 Shutdown . 46
7.8.6 Watchdog . 46
7.8.7 Establish the OPC UA connection . 46
7.8.8 Instantiate the Communication Server . 47
7.8.9 Configure the communication hardware . 47
7.8.10 Configure the Network . 47
7.8.11 Parameterize . 47
7.8.12 Initialize . 47
7.8.13 Create the communication service object . 47
7.8.14 Communication relation . 48
7.8.15 Connect . 48
7.8.16 Disconnect . 48
7.8.17 Abort indication . 49
7.8.18 Scan . 49
7.8.19 SetAddress . 49 ®
8 FDI Communication Gateway definition . 49
8.1 General . 49
8.2 Information Model . 49
8.2.1 General . 49
8.2.2 CommunicationGatewayType . 50
8.2.3 GatewayCommunicationDeviceType . 51
8.2.4 GatewayCommunicationServiceType . 54 ®
8.3 FDI Communication Package . 58
8.3.1 General . 58
8.3.2 EDD . 59
8.4 Handling and behaviour . 60
8.4.1 General . 60
8.4.2 Deployment . 61
8.4.3 Start up . 61
8.4.4 Configure the communication hardware . 61
8.4.5 Configure the Network . 61
8.4.6 Parameterize . 61
8.4.7 Communication relation . 62
8.4.8 Connect . 62
8.4.9 Disconnect . 62
8.4.10 Abort indication . 62
8.4.11 Scan . 62
8.4.12 Communication Error Handling . 63
Annex A (informative) Layered protocols . 64
A.1 General . 64
A.2 Convention for protocol specific annex creation . 64
A.2.1 General . 64
A.2.2 Connection Point . 64
– 4 – IEC 62769-7:2023 RLV © IEC 2023 ®
A.3 FDI Communication Package definition . 66
A.3.1 Communication services . 66
A.3.2 Connection Point . 66
A.3.3 Network . 66
A.4 Representation in the Information Model . 66
Annex B (normative) Namespace and Mappings . 67
®
architecture diagram . 9
Figure 1 – FDI ®
Figure 2 – FDI communication infrastructure architecture . 12
Figure 3 – Communication relation . 22
Figure 4 – Communication relation state chart . 23 ®
Figure 5 – FDI Communication Server AddressSpace . 26
Figure 6 – CommunicationServerType . 27
Figure 7 – ServerCommunicationDeviceType . 32
Figure 8 – ServerCommunicationServiceType . 36
Figure 9 – Information Model differences (example) . 41 ®
Figure 10 – FDI Communication Server state machine . 45
Figure 11 – Communication relation state chart . 48
Figure 12 – Gateway information model . 50
Figure 13 – CommunicationGatewayType . 51
Figure 14 – GatewayCommunicationDeviceType . 52
Figure 15 – GatewayCommunicationServiceType . 55
Figure 16 – Nested Communication . 61
Table 1 – ValidateNetwork Action arguments . 21
Table 2 – ValidateModules Action arguments . 21
Table 3 – CommunicationServerType definition . 27
Table 4 – MethodSet of CommunicationServerType . 27
Table 5 – Reset Method arguments . 28
Table 6 – Reset Method AddressSpace definition . 28
Table 7 – Initialize Method arguments . 29
Table 8 – Initialize Method AddressSpace definition . 29
Table 9 – AddComponent Method arguments . 30
Table 10 – AddComponent Method AddressSpace definition . 30
Table 11 – RemoveComponent Method arguments . 31
Table 12 – RemoveComponent Method AddressSpace definition . 31
Table 13 – ServerCommunicationDeviceType definition . 32
Table 14 – MethodSet of ServerCommunicationDeviceType . 32
Table 15 – Scan Method arguments . 33
Table 16 – Scan Method AddressSpace definition . 33
Table 17 – Scan Method arguments . 34
Table 18 – Scan Method AddressSpace definition . 34
Table 19 – ResetScan Method arguments . 34
Table 20 – ResetScan Method AddressSpace definition. 35
Table 21 – SetAddress Method arguments . 35
Table 22 – ServerCommunicationServiceType definition . 36
Table 23 – MethodSet of ServerCommunicationServiceType . 36
Table 24 – Connect Method arguments . 37
Table 25 – Disconnect Method arguments . 38
Table 26 – Transfer Method arguments . 38
Table 27 – GetPublishedData Method arguments. 39 ®
Table 28 – FDI CommunicationServer_Facet definition . 40
Table 29 – CommunicationGatewayType definition . 51
Table 30 – GatewayCommunicationDeviceType definition . 52
Table 31 – MethodSet of GatewayCommunicationDeviceType . 52
Table 32 – Scan Method arguments . 53
Table 33 – Scan Method AddressSpace definition . 53
Table 34 – ScanNext Method arguments . 54
Table 35 – ScanNext Method AddressSpace definition . 54
Table 36 – GatewayCommunicationServiceType definition . 55
Table 37 – MethodSet of GatewayCommunicationServiceType . 56
Table 38 – Connect Method arguments . 57
Table 39 – Transfer Method arguments . 58
– 6 – IEC 62769-7:2023 RLV © IEC 2023
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________ ®
FIELD DEVICE INTEGRATION (FDI ) –
Part 7: Communication Devices
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 itself does not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any
services carried out by independent certification bodies.
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.
This redline version of the official IEC Standard allows the user to identify the changes
made to the previous edition IEC 62769-7:2021. A vertical bar appears in the margin
wherever a change has been made. Additions are in green text, deletions are in
strikethrough red text.
IEC 62769-7 has been prepared by subcommittee 65E: Devices and integration in enterprise
systems, of IEC technical committee 65: Industrial-process measurement, control and
automation. It is an International Standard.
This third edition cancels and replaces the second edition published in 2021. This edition
constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous
edition:
a) added ScanExtended Method.
The text of this International Standard is based on the following documents:
Draft Report on voting
65E/859/CDV 65E/916/RVC
Full information on the voting for its approval can be found in the report on voting indicated in
the above table.
The language used for the development of this International Standard is English.
This document was drafted in accordance with ISO/IEC Directives, Part 2, and developed in
accordance with ISO/IEC Directives, Part 1 and ISO/IEC Directives, IEC Supplement, available
at www.iec.ch/members_experts/refdocs. The main document types developed by IEC are
described in greater detail at www.iec.ch/publications.
A list of all parts in the IEC 62769 series, published under the general title Field device ®
integration (FDI ), can be found on the IEC website.
The committee has decided that the contents of this document will remain unchanged until the
stability date indicated on the IEC website under webstore.iec.ch in the data related to the
specific document. At this date, the document will be
• reconfirmed,
• withdrawn,
• replaced by a revised edition, or
• amended.
IMPORTANT – The "colour inside" logo on the cover page of this document indicates that it
contains colours which are considered to be useful for the correct understanding of its
contents. Users should therefore print this document using a colour printer.
– 8 – IEC 62769-7:2023 RLV © IEC 2023
INTRODUCTION
The IEC 62769 series has the general title Field Device Integration (FDI) and the following
parts:
– Part 1: Overview
– Part 2: FDI Client
– Part 3: FDI Server
– Part 4: FDI Packages
– Part 5: FDI Information Model
– Part 6: FDI Technology Mapping
– Part 7: FDI Communication Devices
– Part 100: Profiles – Generic Protocol Extensions
– Part 101-1: Profiles – Foundation Fieldbus H1
– Part 101-2: Profiles – Foundation Fieldbus HSE
– Part 103-1: Profiles – PROFIBUS
– Part 103-4: Profiles – PROFINET
– Part 109-1: Profiles – HART and WirelessHART
– Part 115-2: Profiles – Protocol-specific Definitions for Modbus RTU
– Part 150-1: Profiles – ISA 100.11a
®
FIELD DEVICE INTEGRATION (FDI ) –
Part 7: Communication Devices
1 Scope
This part of IEC 62769 specifies the elements implementing communication capabilities called
Communication Devices (IEC 62769-5).
®1
The overall FDI architecture is illustrated in Figure 1. The architectural components that are
within the scope of this document have been highlighted in this illustration. The document scope ®
with respect to FDI Packages is limited to Communication Devices. The Communication Server
shown in Figure 1 is an example of a specific Communication Device.
®
Figure 1 – FDI architecture diagram
___________
1 ®
FDI is a registered trademark of the non-profit organization Fieldbus Foundation, Inc. This information is given
for the convenience of users of this document and does not constitute an endorsement by IEC of the trademark
holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires
permission of the trade name holder.
– 10 – IEC 62769-7:2023 RLV © IEC 2023
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements 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 61804-3, Devices and integration in enterprise systems − Function blocks (FB) for process
control and electronic device description language (EDDL) − Part 3: EDDL syntax and
semantics
IEC 61804-4, Devices and integration in enterprise systems − Function blocks (FB) for process
control and electronic device description language (EDDL) − Part 4: EDD interpretation
IEC 62541 (all parts), OPC Unified Architecture
IEC TR 62541-1, OPC Unified Architecture – Part 1: Overview and concepts
IEC 62541-4, OPC Unified Architecture – Part 4: Services
IEC 62541-6, OPC Unified Architecture – Part 6: Mappings
IEC 62541-7, OPC unified architecture – Part 7: Profiles
IEC 62541-100, OPC Unified Architecture – Part 100: Device Interface ®
IEC 62769-1, Field Device Integration (FDI ) – Part 1: Overview ®
IEC 62769-2, Field Device Integration (FDI ) – Part 2: FDI Client ®
IEC 62769-3, Field Device Integration (FDI ) – Part 3: FDI Server
® ®
IEC 62769-4:20202023, Field Device Integration (FDI ) – Part 4: FDI Packages
® ®
IEC 62769-5, Field Device Integration (FDI ) – Part 5: FDI Information Model
3 Terms, definitions, abbreviated terms, acronyms and conventions
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in IEC 62769-1,
IEC 62769-3, IEC 62541-6 and the following apply.
ISO and IEC maintain terminology databases for use in standardization at the following
addresses:
• IEC Electropedia: available at https://www.electropedia.org/
• ISO Online browsing platform: available at https://www.iso.org/obp
3.1.1
Gateway
Communication Device that enables to bridge between different physical networks or different
protocols
3.2 Abbreviated terms and acronyms
For the purposes of this document, the abbreviated terms and acronyms given in IEC 62769-1,
IEC 62541-6 and the following apply.
HTTP Hypertext Transfer Protocol
IP Internet Protocol
PHY Physical communication hardware
SNMP Simple Network Management Protocol
TCP Transmission Control Protocol
URI Uniform Resource Identifier
3.3 Conventions
For the purposes of this document, the conventions given in IEC 62769-1 apply.
3.3.1 EDDL syntax ®
This part of IEC 62769 specifies content for the EDD component that is part of FDI
Communication Packages. The specification content using EDDL syntax uses the font Courier
New. The EDDL syntax is used for method signature, variable, data structure and component
declarations.
3.3.2 Capitalizations ®
Capitalization of the first letter of words is used in the IEC 62769 series to emphasize an FDI
defined term.
3.3.3 Graphical notation
This document uses the graphical notation defined in IEC 62769-5.
4 General Overview ®
The abstract term FDI Communication Device represents an entity implementing ®
communication functions over a network using a specific protocol. The group of FDI
Communication Devices splits into two main groups. ®
a) The FDI Communication Server is a dedicated OPC UA Server providing access to one or ®
more field device networks. The FDI Communication Server is specified in Clause 7. ®
b) The FDI Communication Gateway enables to bridge between different physical networks
or different protocols. The bridging business logic is implemented in the EDD component
® ®
that is provided with an FDI Communication Package. The FDI Communication Gateway
is specified in Clause 8.
NOTE The main differences between a Gateway and a Communication Server are as follows:
® ®
In terms of FDI , the FDI Communication Server is a dedicated OPC UA Server providing access to one or more
field device networks. A Gateway is a Communication Device that enables to bridge between different physical ®
networks or different protocols. The logical representation of a Gateway device within the FDI Server hosted ®
Information Model enables the FDI Server to process communication in heterogeneous network topologies.
– 12 – IEC 62769-7:2023 RLV © IEC 2023
®
Figure 2 – FDI communication infrastructure architecture ®
The FDI Server hosted Information Model contains a representation of the network topology.
(see also IEC 62769-5). The Information Model shown in Figure 2 is an example excerpt to
illustrate how the Information Model used elements reflect the actual network topology.
1) The instance of CommunicationServerType (named CommunicationServerName)
® ®
represents the FDI Communication Server. The FDI Communication Server implements
physical communication network access (Communication hardware). Clause 7 describes ®
related Information Model specifics, required FDI Communication Package content and
handling of elements therein. (For subdevices, see IEC 62769-5)
2) The instance of ServerCommunicationDeviceType and ServerCommunication-ServiceType ®
(named Network_B_Channel) maps to the FDI Communication Server implemented
communication services. The ServerCommunicationDeviceType is specified in 7.3.3. The
ServerCommunicationServiceType is specified in 7.3.4.
3) The instance of CommunicationGatewayType (named Gateway_B1) represents the physical ®
Gateway. Clause 8 describes the related Information Model specifics, the required FDI
Package content and the handling of elements therein.
4) The instance of GatewayCommunicationDeviceType (named Module 1) maps to a physical
or logical module enabling communication to the network to which this module is connected.
The GatewayCommunicationDeviceType is specified in 8.3.2.3. The related Gateway
specifics are described in Clause 8.
5) The instance of GatewayCommunicationServiceType (named
CommunicationServiceProvider_G) represents the Gateways’ ability to process
communication services. The Gateway specific implementation of
GatewayCommunicationServiceType is based on Business Logic that enables to run
communication services in heterogeneous communication networks.
6) A communication relation (more details are described in Clause 6) between a physical ®
device and the device representation managed by the FDI Server is always associated to
communication service objects that are instances of a GatewayCommunicationServiceType
or ServerCommunicationServiceType. The ability of instantiating multiple communication
service objects supports protocols enables to operate multiple logical connections between
a bus master and a device.
7) The Information Model represents the connections between the physical devices shown on
the left side of Figure 2 based on instances of ConnectionPointType NetworkType and the
depicted relations. ConnectionPointType and NetworkType are specified in IEC 62769-5
IEC 62541-100. ®
5 FDI Communication Package
5.1 General
® ® ®
Server imports the FDI Communication Package like any other FDI Device Package.
The FDI ®
Clause 5 specifies the FDI Communication Package details.
5.2 EDD
5.2.1 General rules ®
Communication Package contained EDD is not restricted but bound to a protocol
The FDI
specific profile (see IEC 62769-4:20202023, Annex F).
The EDD elements as specified in the protocol specific profile documents (see ®
IEC 62769-4:2023, Annex F), and provided with an FDI Communication Package shall
describe:
a) Parameter and parameter structures. Mandatory protocol specific parameter definitions are
found in the protocol specific profile documents (see IEC 62769-4:20202023, Annex F). The
parameters shall contain any parameter that requires adjustment for proper communication
service operation.
b) Physical Layer identification. Protocol specific definitions are found in
IEC 62769-4:20202023, Annex F.
c) Communication Devices modularity: The modularity information shall be based on using the
EDDL constructs COMPONENT (see IEC 61804-3). ®
FDI envisions Communication Device modularity to cope with communication hardware
providing multiple physical or logical communication channels to access multiple logical or
physical communication networks. Each module element of the whole Communication
Device shall be described by a separate EDD element.
d) The COMPONENT definition shall be used to support the system implemented topology
configuration. Protocol specific definitions are found in the protocol specific profile
documents (see IEC 62769-4:20202023, Annex F). The related COMPONENT definitions
are described in 5.2.2, 5.2.3, 5.2.4, and 5.2.7.
e) The Business Logic shall contain a method enabled to validate the network (see 5.2.8). The
validation function considers the elements only directly connected to the network. The
– 14 – IEC 62769-7:2023 RLV © IEC 2023
validation function shall be referred by the EDDL specified CHECK_CONFIGURATION
attribute.
f) The Business Logic can contain a method enabled to validate the module configuration (see
5.2.9) or the network configuration (see 5.2.8). The validation function considers the
elements only directly connected to the related parent element in the topology. The
validation function shall be referred by the EDDL specified CHECK_CONFIGURATION
attribute.
g) Connection Point data: The Connection Point (see 5.2.4 and 5.2.6) shall be described
through EDDL constructs COMPONENT, COLLECTION and VARIABLE. The COMPONENT
definition associates the Connection Point element to the Communication Device. The
VARIABLE definitions represent the properties of a specific Connection Point. The
COLLECTION represents the Connection Point structure as such. Protocol specific
definitions are found in IEC 62769-4:20202023, Annex F. Annex A describes a convention
for protocol specific annex creation.
h) MENU:
The Menu structure shall follow the Menu conventions for PC based applications according
to IEC 61804-4, enabling access to ®
1) FDI Communication Device Type (Bus) parameters: These parameters shall be made
accessible by means of "“offline_root_menu";
2) Topology Configuration Dialogs shall be made available by means of the menu entry
point "topology_configuration".
5.2.2 Device component ®
Each FDI Communication Package shall contain an EDD element describing the device.
COMPONENT
{
LABEL "
IEC 62769-7 ®
Edition 3.0 2023-04
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside ®
Field Device Integration (FDI ) –
Part 7: Communication Devices ®
Intégration des appareils de terrain (FDI ) –
Partie 7: Appareils de Communication
All rights reserved. Unless otherwise specified, 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
either IEC or IEC's member National Committee in the country of the requester. If you have any questions about IEC
copyright or have an enquiry about obtaining additional rights to this publication, please contact the address below or
your local IEC member National Committee for further information.
Droits de reproduction réservés. Sauf indication contraire, aucune partie de cette publication ne peut être reproduite ni
utilisée sous quelque forme que ce soit et par aucun procédé, électronique ou mécanique, y compris la photocopie et
les microfilms, sans l'accord écrit de l'IEC ou du Comité national de l'IEC du pays du demandeur. Si vous avez des
questions sur le copyright de l'IEC ou si vous désirez obtenir des droits supplémentaires sur cette publication, utilisez
les coordonnées ci-après ou contactez le Comité national de l'IEC de votre pays de résidence.
IEC Secretariat Tel.: +41 22 919 02 11
3, rue de Varembé info@iec.ch
CH-1211 Geneva 20 www.iec.ch
Switzerland
About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.
About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigendum or an amendment might have been published.
IEC publications search - webstore.iec.ch/advsearchform IEC Products & Services Portal - products.iec.ch
The advanced search enables to find IEC publications by a Discover our powerful search engine and read freely all the
variety of criteria (reference number, text, technical publications previews. With a subscription you will always have
committee, …). It also gives information on projects, replaced access to up to date content tailored to your needs.
and withdrawn publications.
Electropedia - www.electropedia.org
IEC Just Published - webstore.iec.ch/justpublished
The world's leading online dictionary on electrotechnology,
Stay up to date on all new IEC publications. Just Published
containing more than 22 300 terminological entries in English
details all new publications released. Available online and once
and French, with equivalent terms in 19 additional languages.
a month by email.
Also known as the International Electrotechnical Vocabulary
(IEV) online.
IEC Customer Service Centre - webstore.iec.ch/csc
If you wish to give us your feedback on this publication or need
further assistance, please contact the Customer Service
Centre: sales@iec.ch.
A propos de l'IEC
La Commission Electrotechnique Internationale (IEC) est la première organisation mondiale qui élabore et publie des
Normes internationales pour tout ce qui a trait à l'électricité, à l'électronique et aux technologies apparentées.
A propos des publications IEC
Le contenu technique des publications IEC est constamment revu. Veuillez vous assurer que vous possédez l’édition la
plus récente, un corrigendum ou amendement peut avoir été publié.
Recherche de publications IEC - Découvrez notre puissant moteur de recherche et consultez
webstore.iec.ch/advsearchform gratuitement tous les aperçus des publications. Avec un
La recherche avancée permet de trouver des publications IEC abonnement, vous aurez toujours accès à un contenu à jour
en utilisant différents critères (numéro de référence, texte, adapté à vos besoins.
comité d’études, …). Elle donne aussi des informations sur les
projets et les publications remplacées ou retirées. Electropedia - www.electropedia.org
Le premier dictionnaire d'électrotechnologie en ligne au monde,
IEC Just Published - webstore.iec.ch/justpublished
avec plus de 22 300 articles terminologiques en anglais et en
Restez informé sur les nouvelles publications IEC. Just
français, ainsi que les termes équivalents dans 19 langues
Published détaille les nouvelles publications parues.
additionnelles. Egalement appelé Vocabulaire
Disponible en ligne et une fois par mois par email.
Electrotechnique International (IEV) en ligne.
Service Clients - webstore.iec.ch/csc
Si vous désirez nous donner des commentaires sur cette
publication ou si vous avez des questions contactez-nous:
sales@iec.ch.
IEC Products & Services Portal - products.iec.ch
IEC 62769-7 ®
Edition 3.0 2023-04
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside ®
Field Device Integration (FDI ) –
Part 7: Communication Devices ®
Intégration des appareils de terrain (FDI ) –
Partie 7: Appareils de Communication
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
INTERNATIONALE
ICS 25.040.40; 35.100.05 ISBN 978-2-8322-6748-6
– 2 – IEC 62769-7:2023 © IEC 2023
CONTENTS
FOREWORD . 6
1 Scope . 8
2 Normative references . 9
3 Terms, definitions, abbreviated terms, acronyms and conventions . 9
3.1 Terms and definitions . 9
3.2 Abbreviated terms and acronyms . 9
3.3 Conventions . 10
3.3.1 EDDL syntax. 10
3.3.2 Capitalizations . 10
3.3.3 Graphical notation . 10
4 Overview . 10 ®
5 FDI Communication Package . 12
5.1 General . 12
5.2 EDD . 12
5.2.1 General rules . 12
5.2.2 Device component . 13
5.2.3 CommunicationDevice component . 14
5.2.4 Communication service provider component . 15
5.2.5 Connection Point component . 17
5.2.6 Connection Point collection. 17
5.2.7 Network component . 18
5.2.8 ValidateNetwork . 19
5.2.9 ValidateModules . 20
5.2.10 UIP specifics . 20
5.2.11 Deployment . 21
6 Communication relations . 21 ®
7 FDI Communication Server definition . 22
7.1 General . 22
7.2 General characteristics . 22
7.3 Information Model . 22
7.3.1 General . 22
7.3.2 CommunicationServerType . 25
7.3.3 ServerCommunicationDeviceType . 29
7.3.4 ServerCommunicationServiceType . 33 ®
7.4 OPC UA Server Profile for FDI Communication Server . 37
® ®
7.5 Mapping the FDI Server Information Model to the FDI Communication
Server IM . 38
7.5.1 General . 38
7.5.2 Information Model differences . 38
7.6 Installer. 39 ®
7.7 FDI Communication Package . 39
7.7.1 General . 39
7.7.2 EDD for lightweight Communication Server . 40
7.7.3 EDD for multi-channel Communication Server . 40 ®
7.7.4 COMMANDs in EDDs for FDI Communication Servers . 40
7.7.5 Documentation . 41
7.8 Handling and behaviour . 41
7.8.1 General . 41
7.8.2 Deployment . 42
7.8.3 Server configuration . 42
7.8.4 Start up . 43
7.8.5 Shutdown . 43
7.8.6 Watchdog . 43
7.8.7 Establish the OPC UA connection . 43
7.8.8 Instantiate the Communication Server . 44
7.8.9 Configure the communication hardware . 44
7.8.10 Configure the Network . 44
7.8.11 Parameterize . 44
7.8.12 Initialize . 44
7.8.13 Create the communication service object . 44
7.8.14 Communication relation . 45
7.8.15 Connect . 45
7.8.16 Disconnect . 45
7.8.17 Abort indication . 46
7.8.18 Scan . 46
7.8.19 SetAddress . 46 ®
8 FDI Communication Gateway definition . 46
8.1 General . 46
8.2 Information Model . 46
8.2.1 General . 46
8.2.2 CommunicationGatewayType . 47
8.2.3 GatewayCommunicationDeviceType . 48
8.2.4 GatewayCommunicationServiceType . 51 ®
8.3 FDI Communication Package . 55
8.3.1 General . 55
8.3.2 EDD . 56
8.4 Handling and behaviour . 57
8.4.1 General . 57
8.4.2 Deployment . 58
8.4.3 Start up . 58
8.4.4 Configure the communication hardware . 58
8.4.5 Configure the Network . 58
8.4.6 Parameterize . 58
8.4.7 Communication relation . 59
8.4.8 Connect . 59
8.4.9 Disconnect . 59
8.4.10 Abort indication . 59
8.4.11 Scan . 59
8.4.12 Communication Error Handling . 60
Annex A (informative) Layered protocols . 61
A.1 General . 61
A.2 Convention for protocol specific annex creation . 61
A.2.1 General . 61
A.2.2 Connection Point . 61 ®
A.3 FDI Communication Package definition . 63
– 4 – IEC 62769-7:2023 © IEC 2023
A.3.1 Communication services . 63
A.3.2 Connection Point . 63
A.3.3 Network . 63
A.4 Representation in the Information Model . 63
Annex B (normative) Namespace and Mappings . 64
®
Figure 1 – FDI architecture diagram . 8 ®
Figure 2 – FDI communication infrastructure architecture . 11
Figure 3 – Communication relation . 21
Figure 4 – Communication relation state chart . 22 ®
Figure 5 – FDI Communication Server AddressSpace . 24
Figure 6 – CommunicationServerType . 25
Figure 7 – ServerCommunicationDeviceType . 29
Figure 8 – ServerCommunicationServiceType . 34
Figure 9 – Information Model differences (example) . 38 ®
Figure 10 – FDI Communication Server state machine . 42
Figure 11 – Communication relation state chart . 45
Figure 12 – Gateway information model . 47
Figure 13 – CommunicationGatewayType . 48
Figure 14 – GatewayCommunicationDeviceType . 49
Figure 15 – GatewayCommunicationServiceType . 52
Figure 16 – Nested Communication . 58
Table 1 – ValidateNetwork Action arguments . 20
Table 2 – ValidateModules Action arguments . 20
Table 3 – CommunicationServerType definition . 25
Table 4 – MethodSet of CommunicationServerType . 25
Table 5 – Reset Method arguments . 26
Table 6 – Reset Method AddressSpace definition . 26
Table 7 – Initialize Method arguments . 27
Table 8 – Initialize Method AddressSpace definition . 27
Table 9 – AddComponent Method arguments . 28
Table 10 – AddComponent Method AddressSpace definition . 28
Table 11 – RemoveComponent Method arguments . 29
Table 12 – RemoveComponent Method AddressSpace definition . 29
Table 13 – ServerCommunicationDeviceType definition . 30
Table 14 – MethodSet of ServerCommunicationDeviceType . 30
Table 15 – Scan Method arguments . 31
Table 16 – Scan Method AddressSpace definition . 31
Table 17 – Scan Method arguments . 32
Table 18 – Scan Method AddressSpace definition . 32
Table 19 – ResetScan Method arguments . 32
Table 20 – ResetScan Method AddressSpace definition. 33
Table 21 – SetAddress Method arguments . 33
Table 22 – ServerCommunicationServiceType definition . 34
Table 23 – MethodSet of ServerCommunicationServiceType . 34
Table 24 – Connect Method arguments . 35
Table 25 – Disconnect Method arguments . 36
Table 26 – Transfer Method arguments . 36
Table 27 – GetPublishedData Method arguments. 37 ®
Table 28 – FDI CommunicationServer_Facet definition . 37
Table 29 – CommunicationGatewayType definition . 48
Table 30 – GatewayCommunicationDeviceType definition . 49
Table 31 – MethodSet of GatewayCommunicationDeviceType . 49
Table 32 – Scan Method arguments . 50
Table 33 – Scan Method AddressSpace definition . 50
Table 34 – ScanNext Method arguments . 51
Table 35 – ScanNext Method AddressSpace definition . 51
Table 36 – GatewayCommunicationServiceType definition . 52
Table 37 – MethodSet of GatewayCommunicationServiceType . 53
Table 38 – Connect Method arguments . 54
Table 39 – Transfer Method arguments . 55
– 6 – IEC 62769-7:2023 © IEC 2023
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________ ®
FIELD DEVICE INTEGRATION (FDI ) –
Part 7: Communication Devices
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 itself does not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any
services carried out by independent certification bodies.
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.
IEC 62769-7 has been prepared by subcommittee 65E: Devices and integration in enterprise
systems, of IEC technical committee 65: Industrial-process measurement, control and
automation. It is an International Standard.
This third edition cancels and replaces the second edition published in 2021. This edition
constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous
edition:
a) added ScanExtended Method.
The text of this International Standard is based on the following documents:
Draft Report on voting
65E/859/CDV 65E/916/RVC
Full information on the voting for its approval can be found in the report on voting indicated in
the above table.
The language used for the development of this International Standard is English.
This document was drafted in accordance with ISO/IEC Directives, Part 2, and developed in
accordance with ISO/IEC Directives, Part 1 and ISO/IEC Directives, IEC Supplement, available
at www.iec.ch/members_experts/refdocs. The main document types developed by IEC are
described in greater detail at www.iec.ch/publications.
A list of all parts in the IEC 62769 series, published under the general title Field device ®
integration (FDI ), can be found on the IEC website.
The committee has decided that the contents of this document will remain unchanged until the
stability date indicated on the IEC website under webstore.iec.ch in the data related to the
specific document. At this date, the document will be
• reconfirmed,
• withdrawn,
• replaced by a revised edition, or
• amended.
IMPORTANT – The "colour inside" logo on the cover page of this document indicates that it
contains colours which are considered to be useful for the correct understanding of its
contents. Users should therefore print this document using a colour printer.
– 8 – IEC 62769-7:2023 © IEC 2023 ®
FIELD DEVICE INTEGRATION (FDI ) –
Part 7: Communication Devices
1 Scope
This part of IEC 62769 specifies the elements implementing communication capabilities called
Communication Devices.
®1
The overall FDI architecture is illustrated in Figure 1. The architectural components that are
within the scope of this document have been highlighted in this illustration. The document scope ®
with respect to FDI Packages is limited to Communication Devices. The Communication Server
shown in Figure 1 is an example of a specific Communication Device.
®
Figure 1 – FDI architecture diagram
___________
1 ®
FDI is a registered trademark of the non-profit organization Fieldbus Foundation, Inc. This information is given
for the convenience of users of this document and does not constitute an endorsement by IEC of the trademark
holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires
permission of the trade name holder.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements 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 61804-3, Devices and integration in enterprise systems − Function blocks (FB) for process
control and electronic device description language (EDDL) − Part 3: EDDL syntax and
semantics
IEC 61804-4, Devices and integration in enterprise systems − Function blocks (FB) for process
control and electronic device description language (EDDL) − Part 4: EDD interpretation
IEC TR 62541-1, OPC Unified Architecture – Part 1: Overview and concepts
IEC 62541-4, OPC Unified Architecture – Part 4: Services
IEC 62541-6, OPC Unified Architecture – Part 6: Mappings
IEC 62541-7, OPC unified architecture – Part 7: Profiles
IEC 62541-100, OPC Unified Architecture – Part 100: Device Interface ®
IEC 62769-1, Field Device Integration (FDI ) – Part 1: Overview ®
IEC 62769-2, Field Device Integration (FDI ) – Part 2: Client ®
IEC 62769-3, Field Device Integration (FDI ) – Part 3: Server
® ®
IEC 62769-4:2023, Field Device Integration (FDI ) – Part 4: FDI Packages
® ®
IEC 62769-5, Field Device Integration (FDI ) – Part 5: FDI Information Model
3 Terms, definitions, abbreviated terms, acronyms and conventions
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in IEC 62769-1,
IEC 62769-3, IEC 62541-6 and the following apply.
ISO and IEC maintain terminology databases for use in standardization at the following
addresses:
• IEC Electropedia: available at https://www.electropedia.org/
• ISO Online browsing platform: available at https://www.iso.org/obp
3.1.1
Gateway
Communication Device that enables to bridge between different physical networks or different
protocols
3.2 Abbreviated terms and acronyms
For the purposes of this document, the abbreviated terms and acronyms given in IEC 62769-1,
IEC 62541-6 and the following apply.
– 10 – IEC 62769-7:2023 © IEC 2023
HTTP Hypertext Transfer Protocol
IP Internet Protocol
PHY Physical communication hardware
SNMP Simple Network Management Protocol
TCP Transmission Control Protocol
URI Uniform Resource Identifier
3.3 Conventions
3.3.1 EDDL syntax ®
This part of IEC 62769 specifies content for the EDD component that is part of FDI
Communication Packages. The specification content using EDDL syntax uses the font Courier
New. The EDDL syntax is used for method signature, variable, data structure and component
declarations.
3.3.2 Capitalizations ®
Capitalization of the first letter of words is used in the IEC 62769 series to emphasize an FDI
defined term.
3.3.3 Graphical notation
This document uses the graphical notation defined in IEC 62769-5.
4 Overview ®
The abstract term FDI Communication Device represents an entity implementing ®
communication functions over a network using a specific protocol. The group of FDI
Communication Devices splits into two main groups. ®
a) The FDI Communication Server is a dedicated OPC UA Server providing access to one or ®
more field device networks. The FDI Communication Server is specified in Clause 7. ®
b) The FDI Communication Gateway enables to bridge between different physical networks
or different protocols. The bridging business logic is implemented in the EDD component
® ®
that is provided with an FDI Communication Package. The FDI Communication Gateway
is specified in Clause 8.
NOTE The main differences between a Gateway and a Communication Server are as follows:
® ®
In terms of FDI , the FDI Communication Server is a dedicated OPC UA Server providing access to one or more
field device networks. A Gateway is a Communication Device that enables to bridge between different physical ®
networks or different protocols. The logical representation of a Gateway device within the FDI Server hosted ®
Information Model enables the FDI Server to process communication in heterogeneous network topologies.
®
Figure 2 – FDI communication infrastructure architecture ®
The FDI Server hosted Information Model contains a representation of the network topology.
(see also IEC 62769-5). The Information Model shown in Figure 2 is an example excerpt to
illustrate how the Information Model used elements reflect the actual network topology.
1) The instance of CommunicationServerType (named CommunicationServerName)
® ®
represents the FDI Communication Server. The FDI Communication Server implements
physical communication network access (Communication hardware). Clause 7 describes ®
related Information Model specifics, required FDI Communication Package content and
handling of elements therein. (For subdevices, see IEC 62769-5)
2) The instance of ServerCommunicationDeviceType and ServerCommunication-ServiceType ®
(named Network_B_Channel) maps to the FDI Communication Server implemented
communication services. The ServerCommunicationDeviceType is specified in 7.3.3. The
ServerCommunicationServiceType is specified in 7.3.4.
3) The instance of CommunicationGatewayType (named Gateway_B1) represents the physical ®
Gateway. Clause 8 describes the related Information Model specifics, the required FDI
Package content and the handling of elements therein.
– 12 – IEC 62769-7:2023 © IEC 2023
4) The instance of GatewayCommunicationDeviceType (named Module 1) maps to a physical
or logical module enabling communication to the network to which this module is connected.
The GatewayCommunicationDeviceType is specified in 8.3.2.3. The related Gateway
specifics are described in Clause 8.
5) The instance of GatewayCommunicationServiceType (named
CommunicationServiceProvider_G) represents the Gateways’ ability to process
communication services. The Gateway specific implementation of
GatewayCommunicationServiceType is based on Business Logic that enables to run
communication services in heterogeneous communication networks.
6) A communication relation (more details are described in Clause 6) between a physical ®
device and the device representation managed by the FDI Server is always associated to
communication service objects that are instances of a GatewayCommunicationServiceType
or ServerCommunicationServiceType. The ability of instantiating multiple communication
service objects supports protocols enables to operate multiple logical connections between
a bus master and a device.
7) The Information Model represents the connections between the physical devices shown on
the left side of Figure 2 based on instances of ConnectionPointType NetworkType and the
depicted relations. ConnectionPointType and NetworkType are specified in IEC 62541-100. ®
5 FDI Communication Package
5.1 General
® ® ®
The FDI Server imports the FDI Communication Package like any other FDI Device Package. ®
Clause 5 specifies the FDI Communication Package details.
5.2 EDD
5.2.1 General rules ®
The FDI Communication Package contained EDD is not restricted but bound to a protocol
specific profile (see IEC 62769-4:2023, Annex F).
The EDD elements as specified in the protocol specific profile documents (see ®
IEC 62769-4:2023, Annex F), and provided with an FDI Communication Package shall
describe:
a) Parameter and parameter structures. Mandatory protocol specific parameter definitions are
found in the protocol specific profile documents (see IEC 62769-4: 2023, Annex F). The
parameters shall contain any parameter that requires adjustment for proper communication
service operation.
b) Physical Layer identification. Protocol specific definitions are found in IEC 62769-4: 2023,
Annex F.
c) Communication Devices modularity: The modularity information shall be based on using the
EDDL constructs COMPONENT (see IEC 61804-3). ®
FDI envisions Communication Device modularity to cope with communication hardware
providing multiple physical or logical communication channels to access multiple logical or
physical communication networks. Each module element of the whole Communication
Device shall be described by a separate EDD element.
d) The COMPONENT definition shall be used to support the system implemented topology
configuration. Protocol specific definitions are found in the protocol specific profile
documents (see IEC 62769-4:2023, Annex F). The related COMPONENT definitions are
described in 5.2.2, 5.2.3, 5.2.4, and 5.2.7.
e) The Business Logic shall contain a method enabled to validate the network (see 5.2.8). The
validation function considers the elements only directly connected to the network. The
validation function shall be referred by the EDDL specified CHECK_CONFIGURATION
attribute.
f) The Business Logic can contain a method enabled to validate the module configuration (see
5.2.9) or the network configuration (see 5.2.8). The validation function considers the
elements only directly connected to the related parent element in the topology. The
validation function shall be referred by the EDDL specified CHECK_CONFIGURATION
attribute.
g) Connection Point data: The Connection Point (see 5.2.4 and 5.2.6) shall be described
through EDDL constructs COMPONENT, COLLECTION and VARIABLE. The COMPONENT
definition associates the Connection Point element to the Communication Device. The
VARIABLE definitions represent the properties of a specific Connection Point. The
COLLECTION represents the Connection Point structure as such. Protocol specific
definitions are found in IEC 62769-4:2023, Annex F. Annex A describes a convention for
protocol specific annex creation.
h) MENU:
The Menu structure shall follow the Menu conventions for PC based applications according
to IEC 61804-4, enabling access to ®
Communication Device Type (Bus) parameters: These parameters shall be made
1) FDI
accessible by means of "“offline_root_menu";
2) Topology Configuration Dialogs shall be made available by means of the menu entry
point "topology_configuration".
5.2.2 Device component ®
Each FDI Communication Package shall contain an EDD element describing the device.
COMPONENT
{
LABEL "
CAN_DELETE TRUE;
CHECK_CONFIGURATION ;
CLASSIFICATION NETWORK_COMPONENT;
COMPONENT_RELATIONS
{
}
}
COMPONENT_RELATION
{
LABEL "Relation type description";
RELATION_TYPE CHILD_COMPONENT;
ADDRESSING {}
COMPONENTS
{
{
AUTO_CREATE ;
REQUIRED_RANGES
{
{ MIN_VALUE ; MAX_VALUE ;}
}
}
}
MINIMUM_NUMBER ;
MAXIMUM_NUMBER ;
}
– 14 – IEC 62769-7:2023 © IEC 2023
: The COMPONENT identifier identifies the component description for
the device type.
function of the FDI Communication Server object.
: The Value refers to the METHOD implementing the module topology
configuration validation function. (Implementation details are specified in 5.2.9.)
The attribute COMPONENT_RELATIONS allows to describe how modules can be connected. The
definition of the COMPONENT_RELATIONS is optional. If used, it shall describe the relations to ®
the CommunicationDevice definitions. The construct enables to perform generic, FDI Server
driven (device) topology configuration. Syntax details are described in IEC 61804-3. The
subsequent text describes the semantic use of the COMPONENT_RELATION construct.
: The attribute value identifies the
COMPONENT_RELATION definition describing the relation between the device component and
the CommunicationDevice component.
: The attribute value needs to match with a
COMPONENT identifier used in a COMPONENT declaration that describes a
CommunicationDevice (see 5.2.3).
: The attribute value describes the number of CommunicationDevice
components that can be automatically instantiated with the Device component.
//: The attribute values define the instantiation
constraints. The definition of these attributes is optional. The attribute values can contain
conditional expressions.
The RELATION_TYPE shall be set to CHILD_COMPONENT.
: The attribute value is a reference to a VARIABLE declaration. This VARIABLE
holds the address value for a CommunicationDevice instance. The definition of this attribute is
optional.
/: Values define the address value range for a CommunicationDevice
instance. The value can, for example, correspond to a physical slot number. Usage of attributes
ADDRESSING and REQUIRED_RANGES enables generic configuration routines.
5.2.3 CommunicationDevice component ®
Each FDI Communication Package shall contain at least one EDD element describing at least
one CommunicationDevice component. A modular communication hardware structure shall be
described by multiple CommunicationDevice COMPONENT descriptions:
COMPONENT
{
LABEL "
CAN_DE
...










Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...