IEC 62769-101-1:2023

IEC 62769-101-1 ®
Edition 3.0 2023-04
REDLINE VERSION
INTERNATIONAL
STANDARD
colour
inside ®
Field device Integration (FDI) –
Part 101-1: Profiles - Foundation Fieldbus H1

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-101-1 ®
Edition 3.0 2023-04
REDLINE VERSION
INTERNATIONAL
STANDARD
colour
inside ®
Field device Integration (FDI) –
Part 101-1: Profiles - Foundation Fieldbus H1
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
ICS 25.040.40; 35.100.05 ISBN 978-2-8322-6847-6
– 2 – IEC 62769-101-1:2023 RLV © IEC 2023
CONTENTS
FOREWORD . 4
1 Scope . 6
2 Normative references . 6
3 Terms, definitions, abbreviated terms and conventions acronyms . 7
3.1 Terms and definitions . 7
3.2 Abbreviated terms and acronyms . 7
4 Conventions . 7
4.1 EDDL syntax . 7
4.2 XML syntax . 7
4.3 Capitalizations . 8
5 Profile for CP 1/1 (FOUNDATION™ H1) . 8
5.1 General . 8
5.2 Catalog profile . 8
5.2.1 Protocol support file (Capability File) . 8
5.2.2 CommunicationProfile definition . 9
5.2.3 Profile device . 9
5.2.4 Protocol version information . 9
5.3 Associating a Package with a CP 1/1 device . 9
5.3.1 Device type identification mapping . 9
5.3.2 Device type revision mapping . 9
5.4 Information Model mapping . 10
5.4.1 ProtocolType definition . 10
5.4.2 DeviceType mapping . 10
5.4.3 FunctionalGroup Identification definition . 10
5.4.4 BlockType property mapping . 11
5.4.5 Mapping to Block ParameterSet . 11
5.5 Topology elements . 11
5.5.1 ConnectionPoint definition . 11
5.5.2 Communication Device definition . 13
5.5.3 Communication service provider definition . 15
5.5.4 Network definition . 16
5.6 Methods . 16 ®
5.6.1 Methods for FDI Communication Servers . 16
5.6.2 Methods for Gateways . 23
Annex A (normative) Topology scan schema . 24
A.1 General . 24
A.2 Target Namespace . 24
A.3 FoundationH1AddressT . 24
A.4 FoundationH1ConnectionPointT . 24
A.5 FoundationH1NetworkT . 25
A.6 Network . 25
A.7 FoundationBlockIdentificationT . 26
A.8 FoundationIdentificationT . 26
Annex B (normative) Transfer service parameters . 28
B.1 General . 28
B.2 receiveData . 28

B.3 sendData . 28
B.4 OperationT . 29
B.5 ResponseCodeT . 29
B.6 TransferResultDataT . 29
B.7 TransferSendDataT . 30
Annex C (informative) Communication service arguments for Transfer Method . 31
Bibliography . 32

Table 1 – Capability File part . 8
Table 2 – CommunicationProfile definition . 9
Table 3 – Device type catalog mapping . 9
Table 4 – ProtocolType Foundation_H1 definition . 10
Table 5 – Inherited DeviceType Property mapping . 10
Table 6 – Identification parameters . 11
Table 7 – Inherited BlockType property mapping. 11
Table 8 – ConnectionPointType ConnectionPoint_Foundation_H1 definition . 12
Table 9 – Communication device ParameterSet definition . 15
Table 10 – Method Connect arguments . 17
Table 11 – Method Disconnect arguments . 18
Table 12 – Method Transfer arguments . 19
Table 13 – Method GetPublishedData arguments. 21
Table 14 – Method SetAddress arguments . 22
Table A.1 – Attributes of FoundationH1ConnectionPointT . 25
Table A.2 – Elements of FoundationH1ConnectionPointT . 25
Table A.3 – Elements of FoundationH1NetworkT . 25
Table A.4 – Attributes of FoundationBlockIdentificationT. 26
Table A.5 – Attributes of FoundationIdentificationT . 27
Table B.1 – Elements of receiveData . 28
Table B.2 – Enumerations of OperationT . 29
Table B.3 – Attributes of ResponseCodeT . 29
Table B.4 – Attributes of TransferResultDataT . 30
Table B.5 – Attributes of TransferSendDataT . 30

– 4 – IEC 62769-101-1:2023 RLV © IEC 2023
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________ ®
FIELD DEVICE INTEGRATION (FDI ) –

Part 101-1: Profiles – Foundation Fieldbus H1

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-101-1:2020. 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-101-1 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 2020. This edition
constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous
edition:
a) updated Transfer service;
b) added OPERATION “GETOD” and “GETDEVICETYPEINFO”;
c) added DeviceTag and Block_Index to FoundationIdentificationT and Target;
d) removed arguments “BlockTag” and “ServiceId”;
e) changed content type of CFF file to application/vnd.ff.cff.
The text of this International Standard is based on the following documents:
Draft Report on voting
65E/860/CDV 65E/917/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/standardsdev/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 "http://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.

– 6 – IEC 62769-101-1:2023 RLV © IEC 2023 ®
FIELD DEVICE INTEGRATION (FDI ) –

Part 101-1: Profiles – Foundation Fieldbus H1

1 Scope
®1
This part of IEC 62769 specifies the IEC 62769 an FDI profile of IEC 62769 for
IEC 61784-1_CP 1/1 (FOUNDATION™ Fieldbus H1) .
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 61158-5-9:2014, Industrial communication networks – Fieldbus specifications – Part 5-9:
Application layer service definition – Type 9 elements
IEC 61784-1, Industrial communication networks – Profiles – Part 1: Fieldbus Profiles
IEC 61784-2, Industrial communication networks – Profiles – Part 2: Additional fieldbus profiles
for real-time networks based on ISO/IEC/IEEE 8802-3
IEC 61784-3:20162021, Industrial communication networks – Profiles – Part 3: Functional
safety fieldbuses – General rules and profile definitions
IEC 61804 (all parts), Devices and integration in enterprise systems – Function blocks (FB) for
process control and electronic device description language (EDDL)
IEC 62541-6, OPC unified architecture – Part 6: Mappings
IEC 62541-100:–2015, 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: Server
® ®
IEC 62769-4, Field device integration (FDI ) – Part 4: FDI Packages
____________
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.
FOUNDATION™ Fieldbus is the trade name of the non-profit consortium Fieldbus Foundation. This information is
given for the convenience of users of this standard 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.
®
IEC 62769-5, Field device integration (FDI ) – Part 5: FDI Information Model ®
IEC 62769-6, Field device integration (FDI ) – Part 6: FDI Technology Mapping ®
IEC 62769-7, Field device integration (FDI ) – Part 7: FDI Communication Devices
3 Terms, definitions, abbreviated terms and conventions acronyms
3.1 Terms and definitions
For the purposes of this document, the terms and definitions listed in the normative references
given in IEC 61158-5-9, IEC 61784-1, IEC 61784-2, IEC 61784-3, IEC 61804 (all parts),
IEC 62541-6, IEC 62541-100, IEC 62769-1, IEC 62769-2, IEC 62769-4, IEC 62769-5,
IEC 62769-6, and IEC 62769-7 Clause 2 apply.
ISO and IEC maintain terminology databases for use in standardization at the following
addresses:
• IEC Electropedia: available at http://www.electropedia.org/
• ISO Online browsing platform: available at http:www.iso.org/obp
3.2 Abbreviated terms and acronyms
For the purposes of this document, the following abbreviations apply:
CFF common file format
CP communication profile (see IEC 61784-1 or IEC 61784-2)
CPF communication profile family (see IEC 61784-1 or IEC 61784-2)
EDD Electronic Device Description (see IEC 61804 series)
EDDL Electronic Device Description Language (see IEC 61804 series)
FB function block
IM Information Model
SMIB system management information base
VFD virtual field device
4 Conventions
4.1 EDDL syntax ®
This document specifies content for the EDD component that is part of an FDI Communication
Package. EDDL syntax uses the font Courier New. EDDL syntax is used for method signature,
variable, data structure and component declarations.
4.2 XML syntax
XML syntax examples use the font Courier New. The XML syntax is used to describe XML
document schema.
Example: .

– 8 – IEC 62769-101-1:2023 RLV © IEC 2023
4.3 Capitalizations ®
The IEC 62769 series uses capitalized terms to emphasize that these terms have an FDI
specific meaning.
Some of these terms use an acronym as a prefix for example ®
• FDI Client, or ®
• FDI Server.
Some of these terms are compound terms such as:
• Communication Servers, or
• Profile Package.
Parameter names or attributes are concatenated to a single term, where the original terms start
in this term with a capital letter such as:
• ProtocolSupportFile, or
• ProtocolType.
Parameter names or attributes can also be constructed by using an underscore character to
concatenate two or more terms such as:
• PROFILE_ID, or
• Profibus_PA_Network.
5 Profile for CP 1/1 (FOUNDATION™ H1)
5.1 General ®
This profile specifies the protocol specifics needed for FDI Packages describing
communication servers, gateways and devices. Requirements for Direct Access transfer service
parameters are given in Annex B.
Annex B defines the XML schema for Direct Access Services. Annex C provides an overview of
mapping PROFIBUS standard parameters to PA DIM.
5.2 Catalog profile
5.2.1 Protocol support file (Capability File) ®
Each CP 1/1 FDI Device Package shall contain a capability file. The capability file part is
described in Table 1.
Table 1 – Capability File part
Parameter Description
Content Type: txt/plain application/vnd.ff.cff
Root Namespace: Not applicable
Source Relationship: http://fdi-cooperation.com/2010/relationships/attachment-protocol
Filename: Use file extension .CFF

5.2.2 CommunicationProfile definition
IEC 62769-4 defines a CommunicationProfileT string type for the Catalog XML schema. Table 2
defines the CP 1/1 specific values for this string.
Table 2 – CommunicationProfile definition
CommunicationProfile Description
foundation_h1 CP 1/1 device type with a function block application

5.2.3 Profile device
Not supported in this document.
5.2.4 Protocol version information
IEC 62769-4 defines an element type named InterfaceT for the Catalog XML Schema. Element
type InterfaceT contains an element named Version which is supposed to provide version
information about the applied communication protocol profile. The value follows the
IEC 62769-4 defined version information schema defined in element type VersionT.
The major version part of VersionT shall be set to the ITK_VER parameter. The minor and builds
parts shall be set to 0.
EXAMPLE For ITK_VER 5, the value for InterfaceT is 5.0.0.
5.3 Associating a Package with a CP 1/1 device
5.3.1 Device type identification mapping
CP 1/1 device types are uniquely identified by the parameters MANUFAC_ID, DEVICE_TYPE
and DEV_REV found in the Resource Block. These parameters are used to associate a given
® ®
device instance to an FDI Device Package. These parameters are mapped to the FDI Device
Package Catalog according to Table 3.
Table 3 – Device type catalog mapping
Catalog Element CP Mapping
Manufacturer element of InterfaceT (IEC 62769-4) MANUFAC_ID
String format “0xdddd” where dddd is the
MANUFAC_ID number in hexadecimal format.
DeviceModel element of InterfaceT (IEC 62769-4) DEVICE_TYPE
String format “0xdddd” where dddd is the
DEVICE_TYPE number in hexadecimal format.
DeviceRevision element DEV_REV
ListOfSupportedDeviceRevisionsT (IEC 62769-4)
String format “x.0.0” where x is the DEV_REV in
decimal format (no leading zeros).

5.3.2 Device type revision mapping
Each device type is identified according to 5.3.1. A device may also include a parameter
COMPATIBILITY_REV from the Resource Block. This parameter specifies the lowest device
version (DEV_REV) that a new device can replace while maintaining compatibility with a prior ®
FDI Device Package.
– 10 – IEC 62769-101-1:2023 RLV © IEC 2023
5.4 Information Model mapping
5.4.1 ProtocolType definition
Table 4 defines the ProtocolType used to identify CP 1/1 network communications.
Table 4 – ProtocolType Foundation_H1 definition
Attribute Value
BrowseName Foundation_H1
IsAbstract False
References NodeClass BrowseName DataType TypeDefinition ModellingRule
Inherits the properties of ProtocolType defined in IEC 62541-100.

5.4.2 DeviceType mapping
Each device type inherits the properties of the DeviceType. The mapping of the inherited
properties from the DeviceType is defined in Table 5.
Table 5 – Inherited DeviceType Property mapping
Property CP Mapping
SerialNumber DEV_ID (System Management Information Base)
RevisionCounter -1 (not defined)
Manufacturer ®
String obtained from FDI package catalog
(ManufacturerName from PackageT)
Model ®
String obtained from FDI package catalog (Name of
DeviceTypeT, which is a localized name)
a
DeviceManual
entry text string (not supported)
DeviceRevision DEV_REV (Resource Block)
SoftwareRevision SOFTWARE_REV (if available, otherwise empty
string)
HardwareRevision HARDWARE_REV (if available, otherwise empty
string)
a ®
Device manuals are exposed as attachments of the FDI Device Package.

5.4.3 FunctionalGroup Identification definition ®
As defined in IEC 62541-100, each device representation in the FDI Server hosted Information
Model shall contain a protocol specific FunctionalGroup called Identification. This
FunctionalGroup organizes variables found in the Resource Block of the device type instance.
The FunctionalGroup Identification for CP 1/1 is defined in Table 6.

Table 6 – Identification parameters
BrowseName DataType Optional/Mandatory
MANUFAC_ID UInt32 Mandatory
DEV_TYPE UInt16 Mandatory
DEV_REV UInt8 Mandatory
HARDWARE_REV String Optional
SOFTWARE_REV String Optional
COMPATIBILITY_REV UInt8 Optional
CAPABILITY_LEV UInt8 Optional
ITK_VER UInt16 Mandatory
SIF_ITK_VER UInt16 Optional
FD_VER UInt16 Optional
DeviceTag String Optional
Block_index UInt16 Optional
5.4.4 BlockType property mapping
CP 1/1 device types are block-oriented according to IEC 62541-100. IEC 62769-5 specifies the
mapping of EDDL BLOCK_A elements to block types and instances.
The BLOCK_A maps as a subtype of the topology element BlockType and inherits the properties
per IEC 62541-100. The mapping of the inherited properties of the BlockType is specified in
Table 7.
Table 7 – Inherited BlockType property mapping
Property CP Mapping (Block ParameterSet)
RevisionCounter ST_REV
ActualMode MODE_BLK.ACTUAL
PermittedMode MODE_BLK.PERMITTED
NormalMode MODE_BLK.NORMAL
TargetMode MODE_BLK.TARGET
5.4.5 Mapping to Block ParameterSet
The ParameterSet is relative to each Block. The ParameterSet includes the
CHARACTERISTICS records of the block and all the parameters found in the PARAMETERS,
LOCAL_PARAMETERS and LIST_ITEMS.
The browse name of the parameters found in the PARAMETERS and LOCAL_PARAMETERS
is the member name in the respective lists. For example, ST_REV is the browse name of the
Static Revision parameter. LIST_ITEMS do not have member names; therefore the browse
name of each LIST in the LIST_ITEMS is the item name of the list.
5.5 Topology elements
5.5.1 ConnectionPoint definition
The ConnectionPoint type ConnectionPoint_Foundation_H1 shall be used to identify CP 1/1
network communication and is defined in Table 8. The ConnectionPoint_Foundation_H1 type is
a sub type of the abstract type ConnectionPointType defined in IEC 62541-100.

– 12 – IEC 62769-101-1:2023 RLV © IEC 2023
The Address property shall be the H1 node address.
The OrdinalNumber property reflects the position of the VFD within the SMIB VFD list. For
devices exposing multiple FB VFDs, the OrdinalNumber property is mandatory to address the
FB VFD. For devices with a single FB VFD, the OrdinalNumber property can be omitted. Devices
exposed as instances of type DeviceType define their connection points as components. Hence
Devices with multiple FB VFDs shall contain multiple Connection Points, one per FB VFD.
The SIFConnection property denotes whether a safety instrumented function (SIF) connection
is necessary or not according to the functional safety profile (IEC 61784-3:20162021, Clause 6).
CP 1/1 devices that implement the functional safety profile shall have a connection point as a
component that has set this property to true. Devices supporting standard connections and SIF
connections shall expose two Connections Points as components.
Table 8 – ConnectionPointType ConnectionPoint_Foundation_H1 definition
Attribute Value
BrowseName ConnnectionPoint_Foundation_H1
IsAbstract False
References NodeClass BrowseName DataType TypeDefinition ModellingRule
Inherits the properties of ConnectionPointType defined in IEC 62541-100.
HasProperty Variable Address Byte PropertyType Mandatory
HasProperty Variable OrdinalNumber Int32 PropertyType Optional
HasProperty Variable SIFConnection Boolean PropertyType Optional

The ConnectionPoint type ConnectionPoint_Foundation_H1 shall be described by an EDD ®
element contained in a Communication Device related FDI Package that can drive a CP 1/1
network. Actual ConnectionPoint_Foundation_H1 properties are declared by VARIABLE
constructs grouped together in a COLLECTION named
Foundation_H1_ConnectionPoint_Properties.
COMPONENT ConnectionPoint_Foundation_H1
{
LABEL "Foundation H1 Connection point";
CLASSIFICATION NETWORK_CONNECTION_POINT;
CAN_DELETE FALSE;
PROTOCOL Foundation_H1;
CONNECTION_POINT Foundation_H1_ConnectionPoint_Properties;
}
VARIABLE Address
{
LABEL "H1 Node address";
HELP "Address of the H1 Node";
CLASS DEVICE;
TYPE UNSIGNED_INTEGER (1)
{
MIN_VALUE 16;
MAX_VALUE 255;
}
HANDLING READ & WRITE;
}
VARIABLE OrdinalNumber
{
LABEL "OrdinalNumber address property";

HELP "OrdinalNumber property to address the Function Block
Application”;
CLASS DEVICE;
TYPE UNSIGNED_INTEGER (4);
HANDLING READ & WRITE;
}
VARIABLE SIFConnection
{
LABEL "SIFConnection address property";
HELP "Connection point supports SIF Connections";
CLASS DEVICE;
TYPE ENUMERATED (1)
{
{0,”NO_SIFCONNECTION”} ,
{1,”SIFCONNECTION”}
}
HANDLING READ & WRITE;
}
COLLECTION Foundation_H1_ConnectionPoint_Properties
{
LABEL "FF H1 Connection Point data";
MEMBERS
{
CONNECTION_POINT_ADDRESS, Address;
CONNECTION_POINT_ORDINALNUMBER, OrdinalNumber;
CONNECTION_POINT_SIFCONNECTION , SIFConnection;
}
}
5.5.2 Communication Device definition ®
Communication Package shall contain an EDD element
According to IEC 62769-7 each FDI ®
describing the device. The following EDDL source code is an example describing an FDI
Communication Server.
COMPONENT Foundation_H1_Communication_Server
{
LABEL "Foundation H1 communication server",
PRODUCT_URI "urn:Fieldbus Foundation:Foundation H1 Communication
Server";
CAN_DELETE TRUE;
CLASSIFICATION NETWORK_COMPONENT;
COMPONENT_RELATIONS
{
Foundation_H1_Communication_Device_Setup
}
}
COMPONENT_RELATION Foundation_H1_Communication_Device_Setup
{
LABEL "Relation between Device and communication device";
RELATION_TYPE CHILD_COMPONENT;
ADDRESSING { LinkId }
COMPONENTS
{
Foundation_H1_Communication_Device{AUTO_CREATE 1;}
}
MINIMUM_NUMBER 1;
MAXIMUM_NUMBER 4;
}
– 14 – IEC 62769-101-1:2023 RLV © IEC 2023

VARIABLE LinkId
{
LABEL "Link Id address parameter of the Communication device";
HELP "Link Id address parameter of the Communication device";
CLASS DEVICE;
TYPE UNSIGNED_INTEGER (2)
{
MIN_VALUE 4096;
MAX_VALUE 65535;
}
HANDLING READ & WRITE;
}
Semantics of the EDDL constructs shown with the EDDL source code above are described in
® ®
IEC 62769-7. The EDDL COMPONENT will be utilized by the FDI server and FDI
Communication Server to create an instance of type CommunicationServerType as described
in IEC 62769-7.
The LinkId VARIABLE holds the address value for a Communication device instance. In the
Information model the LinkId will be represented as an instance of BaseDataVariableType and
as a component of the ParameterSet of the communication device. ®
According to IEC 62769-7, each FDI Communication Package shall contain at least one EDD
element describing at least one Communication Device component. The following EDDL source
code is an example for a communication device.
COMPONENT Foundation_H1_Communication_Device
{
LABEL "Foundation H1 communication device";
CAN_DELETE TRUE;
CLASSIFICATION NETWORK_COMPONENT;
COMPONENT_RELATIONS
{
Foundation_H1_Service_Provider_Relation
}
}
COMPONENT_RELATION Foundation_H1_Service_Provider_Relation
{
LABEL "Foundation H1 communication service provider”;
RELATION_TYPE CHILD_COMPONENT;
COMPONENTS
{
Foundation_H1_Service_Provider{AUTO_CREATE 1;}
}
MINIMUM_NUMBER 1;
MAXIMUM_NUMBER 16;
}
Semantics of the EDDL constructs shown with the EDDL source code above are described in
® ®
IEC 62769-7. The EDDL COMPONENT will be utilized by the FDI server and FDI
Communication Server to create an instance of type ServerCommunicationDeviceType as
described in IEC 62769-7.
An instance of ServerCommunicationDeviceType shall contain the following parameter(s) with
its ParameterSet. Table 9 shows the definition of Communication device ParameterSet.

Table 9 – Communication device ParameterSet definition
Attribute Value
BrowseName ParameterSet
References NodeClass BrowseName DataType TypeDefinition ModellingRule
See IEC 62541-100:–2015, 5.2.
HasTypeDefinition ObjectType BaseObjectType
HasComponent Variable LinkId UInt16 BaseDataVariable Mandatory
Type
HasComponent Variable  BaseDataVariable Mandatory-
Type Placeholder ®
The LinkId parameter is an addressing parameter distinguishing multiple H1 Links. If an FDI
Communication Server supports multiple physical H1 Links these are mapped within the ®
Information Model to multiple communication device instances. If the FDI Communication
Server supports only one H1 Link it shall define only one communication device within the
Information Model. The value of the variable can be set to 0 in this case.
The EDD declaration of the variable LinkId is with the ADDRESSING attribute of the ®
COMPONENT_RELATION of the FDI Communication Server definition (see 5.5.2).
5.5.3 Communication service provider definition ®
According to IEC 62769-7 each FDI Communication Package shall contain at least one EDD
element describing at least one communication service provider component. The following
EDDL source code is an example for a CP 1/1 communication service provider component.
The component reference ConnectionPoint_Foundation_H1 corresponds to the related
Connection Point definition in 5.5.1.
COMPONENT Foundation_H1_Service_Provider
{
LABEL "Foundation H1 communication service provider";
CAN_DELETE FALSE;
CLASSIFICATION NETWORK_COMMUNICATION_SERVICE_PROVIDER;
COMPONENT_RELATIONS
{
Foundation_H1_Connection_Point_Relation
}
BYTE_ORDER BIG_ENDIAN;
}
COMPONENT_RELATION
Foundation_H1_Service_Provider_Connection_Point_Relation
{
LABEL "Relation between communication service provider and
connection point";
RELATION_TYPE CHILD_COMPONENT;
ADDRESSING {Address}
COMPONENTS
{
ConnectionPoint_Foundation_H1{ AUTO_CREATE 1;}
}
MINIMUM_NUMBER 1;
MAXIMUM_NUMBER 1;
}
– 16 – IEC 62769-101-1:2023 RLV © IEC 2023
Semantics of the EDDL constructs shown with the EDDL source code above are described in
® ®
IEC 62769-7. The EDDL COMPONENT will be utilized by the FDI server and FDI
Communication Server to create an instance of type ServerCommunicationServiceType as
described in IEC 62769-7.
5.5.4 Network definition ®
According to IEC 62769-7 each FDI Communication Package shall contain at least one EDD
element describing one Network for each of the protocols that are supported by the
Communication Device. The definition supports the network topology engineering.
COMPONENT Network_Foundation_H1
{
LABEL "Foundation H1 Network";
CAN_DELETE TRUE;
CLASSIFICATION NETWORK;
PROTOCOL Foundation_H1
COMPONENT_RELATIONS
{
Foundation_H1_Network_Connection_Point_Relation
}
COMPONENT_RELATION Foundation_H1_Network_Connection_Point_Relation
{
LABEL "Relation between network and connection point";
RELATION_TYPE CHILD_COMPONENT;
ADDRESSING {Address}
COMPONENTS
{
ConnectionPoint_Foundation_H1
}
MINIMUM_NUMBER 1;
MAXIMUM_NUMBER 32;
}
Semantics of the EDDL constructs shown with the EDDL source code above are described in ®
IEC 62769-7. The EDDL COMPONENT will be utilized by the FDI server and ®
FDI Communication Server to create an instance of type NetworkType as described in
IEC 62541-100.
5.6 Methods ®
5.6.1 Methods for FDI Communication Servers
5.6.1.1 General ®
The FDI Communication Server shall implement the services according to the method
signatures described in 5.6.1 and according to the Information Model.
5.6.1.2 Connect
Table 10 shows the Method Connect arguments. The connect transaction may need a significant
amout of time since configuration of communication endpoints is involved. Ensure the OPC UA
timeout is configured appropriately (e.g. 30 seconds).

Signature:
Connect(
[in] ByteString CommunicationRelationId,
[in] UInt16 LinkId
[in] byte Address,
[in] Int32 OrdinalNumber
[in] Boolean SIFConnection
[out] Int32 ServiceError);
Table 10 – Method Connect arguments
Argument Description
CommunicationRelationId The argument value contains the nodeId of the Device ConnectionPoint
representing the connection between a device and a physical network which ®
is directly connected to the FDI Communication Server hardware. The
nodeId allows finding the direct parent-child relation.
LinkId The argument name shall match with the corresponding BrowseName of the
Variable defined as a component of an instance of type
ServerCommunicationDeviceType (refer to 5.5.2). The argument value is
passed by the parent instance of a ServerCommunicationDeviceType. The
value may be obtained by the Scan Method or may be directly configured.
Address The argument name shall match with the corresponding attribute name
defined for the ConnectionPoint which is described by a corresponding EDD
element. The argument value holds the device’s node address.
OrdinalNumber The argument name shall match with the corresponding attribute name
defined for the ConnectionPoint which is described by a corresponding EDD
element specified in 5.5.1. The argument value holds the OrdinalNumber. The
OrdinalNumber is the position of the VFD within the SMIB VFD list. If a value
0 is passed with this argument the first FB VFD is selected.
SIFConnection The argument name shall match with the corresponding attribute name
defined for the ConnectionPoint which is described by a corresponding EDD
element specified in 5.5.1.
The argument value denotes whether a SIF Connection is necessary or not.
ServiceError 0: OK / execution finished, connection established successfully
-1: Connect Failed / canceled by caller
-2: Call Failed / unknown service ID
-3: Connect Failed / device not found
-4: Connect Failed / invalid device node address
-5: Connect Failed / invalid device identification
-6: Connect Failed / invalid LinkId argument
-7: Connect Failed / invalid OrdinalNumber argument
NOTE IEC 62769-7 defines the argument AddressData of the Connect Method as an array of Variant. The
address arguments defined with the table are represented as entries of the Variant array in the order they are
specified above. IEC 62769-7 defines the argument DeviceInformation as a protocol specific argument list in which
the Connect Method stores the resulting data. The DeviceInformation argument is defined as an array of Variant.
The DeviceInformation argument is not used.

– 18 – IEC 62769-101-1:2023 RLV © IEC 2023
5.6.1.3 Disconnect
Table 11 shows the Method Disconnect arguments.
Signature:
Disconnect(
[in] ByteString CommunicationRelationId,
[out] UInt32 ServiceError)
Table 11 – Method Disconnect arguments
Argument Description
CommunicationRelationId The argument value contains the nodeId of the Device ConnectionPoint
representing the connection between a device and a physical network which ®
is directly connected to the FDI Communication Server hardware. The
nodeId allows finding the direct parent-child relation.
ServiceError 0: OK / disconnect finished successfully
-1: Disconnect Failed / no existing communication relation
-2: Disconnect Failed / invalid communication relation identifier

5.6.1.4 Transfer
Table 12 shows the Method Transfer arguments.
Signature
Transfer(
[in] ByteString CommunicationRelationId,
[in] String OPERATION,
[in] String BlockTag,
[in] UInt32 INDEX,
[in] UInt32 SUB_INDEX,
[in] Byte[] WriteData,
[in] UInt32 ServiceId,
[out] Byte[] ReadData,
[out] Int32 ServiceError);
...