IEC 62769-150-1:2023

IEC 62769-150-1 ®
Edition 2.0 2023-04
REDLINE VERSION
INTERNATIONAL
STANDARD
colour
inside
Field device integration (FDI)® –
Part 150-1: Profiles – ISA100 WIRELESS

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-150-1 ®
Edition 2.0 2023-04
REDLINE VERSION
INTERNATIONAL
STANDARD
colour
inside
Field device integration (FDI)® –
Part 150-1: Profiles – ISA100 WIRELESS
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
ICS 25.040.40; 35.100.05; 35.240.50 ISBN 978-2-8322-6897-1
– 2 – IEC 62769-150-1:2023 RLV © IEC 2023
CONTENTS
FOREWORD . 4
1 Scope . 6
2 Normative references . 6
3 Terms, definitions, abbreviated terms and 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 . 7
5 Profile for ISA100 WIRELESS. 8
5.1 General . 8
5.2 Catalog profile . 8
5.2.1 Protocol support 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 device . 9
5.3.1 Device type identification mapping . 9
5.3.2 Device type revision mapping . 10
5.4 Information Model mapping . 11
5.4.1 ProtocolType definition . 11
5.4.2 DeviceType mapping . 11
5.4.3 FunctionalGroup identification definition . 11
5.4.4 BlockType property mapping . 12
5.4.5 Mapping to Object ParameterSet . 12
5.5 Topology elements . 12
5.5.1 ConnectionPoint definition . 12
5.5.2 Communication Device definition . 14
5.5.3 Communication service provider definition . 15
5.5.4 Network definition . 16
5.6 Methods . 17 ®
5.6.1 Methods for FDI Communication Servers . 17
5.6.2 Methods for Gateways . 21
Annex A (normative) Topology Scan result schema . 22
A.1 General . 22
A.2 Target Namespace . 22
A.3 Network . 22
A.4 ISA100_WirelessNetworkT . 22
A.5 ISA100_WirelessConnectionPointT . 23
A.6 ISA100_WirelessIdentificationT. 23
A.7 ISA100_WirelessAddressT . 24
A.8 ISA_WirelessObjIdentificationT . 24
Annex B (normative) Transfer service parameters . 26
B.1 General . 26
B.2 sendData . 26

B.3 receiveData . 26
B.4 TransferSendDataT . 26
B.5 OperationT . 27
B.6 TransferResultDataT . 27
Bibliography . 28

Table 1 – Capability file part . 8
Table 2 – Protocol Version Information . 9
Table 3 – Device identification information mapping . 10
Table 4 – Device type catalog mapping . 10
Table 5 – Protocol type ISA100 WIRELESS . 11
Table 6 – Inherited DeviceType property mapping . 11
Table 7 – ISA100 Wireless Device Types identification attributes . 11
Table 8 – Inherited BlockType property mapping. 12
Table 9 – ConnectionPointType ConnnectionPoint_ISA100_Wireless definition . 13
Table 10 – Method Connect arguments . 17
Table 11 – Method Disconnect arguments . 18
Table 12 – Method Transfer arguments . 19
Table 13 – Method GetPublishedData arguments. 20
Table A.1 – Elements of ISA100_WirelessNetworkT . 22
Table A.2 – Elements of ISA100_WirelessConnectionPointT . 23
Table A.3 – Attributes of ISA100_WirelessIdentificationT . 24
Table A.4 – Attributes of ISA100_WirelessObjIdentificationT . 25
Table B.1 – Attributes of TransferSendDataT . 27
Table B.2 – Enumerations of OperationT . 27
Table B.3 – Attributes of TransferResultDataT . 27

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

Part 150-1: Profiles – ISA100 WIRELESS

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-150-1: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-150-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 second edition cancels and replaces the first 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 namespace to Annex A.
The text of this International Standard is based on the following documents:
Draft Report on voting
65E/866/CDV 65E/923/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-150-1:2023 RLV © IEC 2023 ®
FIELD DEVICE INTEGRATION (FDI ) –

Part 150-1: Profiles – ISA100 WIRELESS

1 Scope
®1
This part of IEC 62769 specifies an FDI profile of IEC 62769 for IEC 62734 (ISA100
WIRELESS.11a) .
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 62734:2014: Industrial networks – Wireless communication network and communication
profiles – ISA 100.11a
IEC 61804 (all parts), Devices and integration in enterprise systems – Function blocks (FB) for
process control and electronic device description language (EDDL)
IEC TR 62541-2, OPC unified architecture – Part 2: Security Model
IEC 62541-6, OPC unified architecture – Part 6: Mappings
IEC 62541-100:2015, OPC unified architecture – Part 100: Device Interface
IEC 62734:2014, Industrial networks – Wireless communication network and communication
profiles – ISA 100.11a
IEC 62769-2, Field Device Integration (FDI) – Part 2: FDI Client
® ®
IEC 62769-4, Field device integration (FDI ) – Part 4: FDI Packages ®
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
___________
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 TM
ISA100 WIRELESS is a trade name of the non-profit consortium Wireless Compliance Institute. 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.

3 Terms, definitions, abbreviated terms and acronyms
3.1 Terms and definitions
No terms and definitions are listed in this document.
For the purposes of this document, the terms and definitions given in, IEC 61804 (all parts),
IEC TR 62541-2, IEC 62541-100, IEC 62734, IEC 62769-4, IEC 62769-5, IEC 62769-7 and the
following apply.
ISO and IEC maintain terminological 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.1.1
Object
basic entity which defines standardized behavior and features in a ISA100 WIRELESS device
3.2 Abbreviated terms and acronyms
For the purposes of this specification, the following abbreviations apply.
EDD Electronic Device Description
EDDL Electronic Device Description Language (see IEC 61804 (all parts)) ®
FDI Field Device Integration
FCG FieldComm Group
XML Extensible markup language (see REC-xml-20081126)
CFF Common file format
UAP User Application Process
UAPMO User Application Process Management Object
DMO Device Management Object
IM  Information Model
SM  System Manager
WCI Wireless Compliance Institute
CP  Communication profile
4 Conventions
4.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.
4.2 XML syntax
XML syntax examples use font Courier New. The XML syntax is used to describe XML
document schema.
Example:

– 8 – IEC 62769-150-1:2023 RLV © IEC 2023
4.3 Capitalizations ®
The IEC 62769 series uses capitalized terms to emphasize that these terms have a FDI
specific meaning.
Some of these terms using 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:
• DEVICE_REV or
• DEVICE_MODEL
5 Profile for ISA100 WIRELESS
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.
5.2 Catalog profile
5.2.1 Protocol support file
5.2.1.1 Capability file ®
Each ISA100 WIRELESS 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
Root Namespace: Not applicable
Source Relationship: http://fdi-cooperation.com/2010/relationships/attachment-protocol
Filename: Use file extension .CFF

5.2.1.2 FDI Communication Packages
The same rules as for FDI Device Packages applies.
5.2.2 CommunicationProfile definition
IEC 62769-4 defines a CommunicationProfileT string for the Catalog XML schema. The ISA100
WIRELESS specific value shall be “ISA100_Wireless”.
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. The
element type InterfaceT contains an element named Version which is supposed to provide
version information about the applied communication protocol profile. The value has to follow
the IEC 62769-4 defined version information schema defined in the element type VersionT.
ISA100 WIRELESS defines the version of the protocol as a value of the parameter
DMO.Comm_SW_Minor_Version. A value of 0 indicates protocol version 2009 and a value of 1
indicates protocol version 2011. The general rule is to use the value of
DMO.Comm_SW_Minor_Version parameter as the major version part of VersionT and the value
“0” for the minor version and build parts Table 2 shows the protocol version information:
Table 2 – Protocol Version Information
Protocol Version InterfaceT Version value
ISA100 WIRELESS 2009 1.0.0
ISA100 WIRELESS 2011 2.0.0
The Protocol Version defined in a package is provided for informational purposes
only, and shall not be used to determine the compatibility or applicability of a
package to a device.
5.3 Associating a Package with a device
5.3.1 Device type identification mapping ®
The purpose of device type identification mapping is to enable FDI host systems to compare ®
the scan result against the topology representation in the Information Model. FDI host systems ®
shall also be enabled to determine the FDI Device Package that fits for a device entry ®
contained in the scan result. This will enable the user of an FDI host system to synchronize
the Information Model with the actual installation.
The Communication Server implemented scan service (defined in 5.6.1.7 provides the scan
result through an XML document (the schema is defined in Clause A.6).
The scan result contains device type identification and device instance identification. ®
FDI host systems comparing the actual network topology configuration against the topology
representation in the Information Model shall be enabled to handle the following situations:
a) The physical Device instance identified at a specific device address is not logically present ®
in the Information Model (as Instance): Enable the FDI Host system to find the appropriate ®
FDI Device Package according to the device catalog information.

– 10 – IEC 62769-150-1:2023 RLV © IEC 2023
b) The physical Device instance identified by the device address is logically present in the ®
Information Model (as Instance): Enable the FDI Host system to compare device type
information presented in scan result (see the identification in Clause A.6) and the device
type specific information of the Instance present in the Information Model. ®
The FDI Device Package contains device type identification information that can be compared
to scan result based on the Catalog Schema in IEC 62769-4 defining the XML (simple) element
types “DeviceModel” and “Manufacturer”.
® ®
As a result of the FDI Package deployment the FDI Package information is then present in
the Information Model as the specified FunctionalGroup Identification containing SerialNumber
and Tag (see 5.4.3).
The mapping between different device identification data sources is described in Table 3. Since
scan results provided by the Communication Server can convey data that is produced by the
device (firmware) the device type identification mapping shall be supported by providing ®
corresponding data in the FDI Device Package contained Catalog and Information Model.
Table 3 – Device identification information mapping
® Information Model Communication Server provided
FDI Device Package
scan result
Catalog specified type FunctionalGroup: Element (path):
Identification ConnectionPoint/Identification
Manufacturer
Browse Name: Manufacturer Attribute: Manufacturer
Catalog specified type FunctionalGroup: Element (path):
Identification ConnectionPoint/Identification
DeviceModel
Browse Name: DeviceModel Attribute: DeviceModel

ISA100 WIRELESS device types are uniquely identified by the parameters
UAPMO.IDENT_NUMBER found in the UAPMO. The IDENT_NUMBER parameter contains the
Vendor ID, Model ID and Device Revision. 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 4.
Table 4 – Device type catalog mapping
Catalog Element ISA100 WIRELESS CP Mapping
Manufacturer element of InterfaceT (IEC 62769-4) UAPMO.IDENT_NUMBER 0x00FFFFFF00000000
String format “0xdddddd” where dddddd is theVendor ID
number in hexadecimal format.
DeviceModel element of InterfaceT (IEC 62769-4) UAPMO.IDENT_NUMBER 0x00000000FFFF0000String
format “0xdddd” where dddd is the Model ID number in
hexadecimal format.
DeviceRevision element
UAPMO.IDENT_NUMBER 0x000000000000FFFF
ListOfSupportedDeviceRevisionsT (IEC 62769-4)
String format “x.0.0” where x is the Device Revision in
decimal format (no leading zeros).

5.3.2 Device type revision mapping ®
IEC 62769-4 envisions a concept that allows to determine the compatibility between an FDI
Device Package and a Device. IEC 62769-4 specifies a life cycle management process bearing
on a single version information provided for the entire device. Mapping of version information
is defined in Table 4.
5.4 Information Model mapping
5.4.1 ProtocolType definition
In Table 5 a subtype of ProtocolType is defined to identify network communication using this
profile.
Table 5 – Protocol type ISA100 WIRELESS
Attribute Value
BrowseName ISA100_Wireless
IsAbstract False
References NodeClass BrowseName DataType TypeDefinition ModellingRule
Subtype of the ProtocolType defined in IEC 62541-100.

5.4.2 DeviceType mapping
Each device type inherits the properties of DeviceType. The mapping of the inherited properties
from DeviceType is defined in Table 6.
Table 6 – Inherited DeviceType property mapping
Property ISA100 WIRELESS Mapping
SerialNumber
DMO.EUI_64 – 8 byte Extended Unique Identifier defined in DMO
RevisionCounter UAPMO.Static_Revision_Level - 2 byte revision counter defined in UAPMO
Manufacturer ®
String taken from FDI package catalog (ManufacturerName from PackageT)
Model ®
String taken from FDI package catalog (Name of DeviceTypeT, which is a
localized name)
a
DeviceManual
empty text string (not supported)
DeviceRevision DEV_REV (UAPMO)
SoftwareRevision empty string (not defined)
HardwareRevision empty string (not defined)
a ®
Device manuals are exposed as attachments of the FDI Device Package.

5.4.3 FunctionalGroup identification definition ®
As defined in IEC 62541-100:2015, 5.3, each device representation in the FDI Server hosted
Information Model shall contain a protocol specific FunctionalGroup named Identification. This
FunctionalGroup organizes variables found in the UAPMO of the device type instance. The
FunctionalGroup Identification for ISA100 WIRELESS is defined in Table 7.
Table 7 – ISA100 Wireless Device Types identification attributes
BrowseName DataType Mandatory/Optional
MANUFAC_ID UInt32 Mandatory
DEV_TYPE UInt16 Mandatory
DEV_REV UInt16 Mandatory
HARDWARE_REV String Optional
SOFTWARE_REV String Optional
ITS_VER UInt16 Mandatory
– 12 – IEC 62769-150-1:2023 RLV © IEC 2023

5.4.4 BlockType property mapping
ISA100 WIRELESS device types are object oriented referred as 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 8.
Table 8 – Inherited BlockType property mapping
Property ISA100 Wireless Mapping (Object
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 Object ParameterSet
The ParameterSet is relative to each Object. The ParameterSet includes 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_ISA100_Wireless shall be used to identify ISA100
WIRELESS network communication and is defined in Table 9. The ConnectionPoint type
ConnectionPoint_ISA100_Wireless is a sub type of the abstract type ConnectionPointType
defined in IEC 62541-100.
The DevAddr property shall be the IPV6 (16 bytes) address of the device.
The DevMfg property shall be the 4-byte UAPMO.IDENT_NUMBER.VendorID, and can be used
to help automate the process of assigning live devices in the scan list to offline placeholders.
The DevType property shall be the 2-byte UAPMO.IDENT_NUMBER.ModelID, and can be used
to help automate the process of assigning live devices in the scan list to offline placeholders.
The DevRev property shall be the UAPMO.UAPMO.IDENT_NUMBER.DeviceRevision, and can
be used to help automate the process of assigning live devices in the scan list to offline
placeholders.
The DevTag property shall be the DMO.Tag_Name (16 characters).
The DevPollAddr property shall be the DMO.ShortDMO.DL_Address_16_Bit (2 bytes).

Table 9 – ConnectionPointType ConnnectionPoint_ISA100_Wireless definition
Attribute Value
BrowseName ConnectionPoint_ISA100_Wireless
IsAbstract False
References NodeClass BrowseName DataType TypeDefinition ModellingRule
Inherits the properties of ConnectionPointType defined in IEC 62541-100.
HasProperty Variable IPAddress ByteString PropertyType Mandatory
HasProperty Variable DevMfg UInt32 PropertyType Optional
HasProperty Variable DevType UInt16 PropertyType Optional
HasProperty Variable DevRev UInt16 PropertyType Optional
HasProperty Variable DevTag String PropertyType Optional
HasProperty Variable DevPollAddr UInt16 PropertyType Optional

The ConnectionPoint type ISA100_Wireless shall be described by an EDD element contained ®
in a Communication Device related FDI Package that can drive an ISA100 Wireless network.
Actual ConnectionPoint properties are declared by VARIABLE constructs grouped together in
a COLLECTION named ConnectionPoint_ISA100_Wireless_Properties. The following EDDL
source code is an example describing ISA100 WIRELESS connection point.
COMPONENT ConnectionPoint_ISA100_Wireless
{
LABEL "ISA100 Wireless Connection point";
CLASSIFICATION NETWORK_CONNECTION_POINT;
CAN_DELETE FALSE;
PROTOCOL ISA100_Wireless;
CONNECTION_POINT ConnectionPoint_ISA100_Wireless_Properties;
}
COLLECTION ConnectionPoint_ISA100_Wireless_Properties
{
LABEL "ISA100 Wireless Connection Point data";

MEMBERS
{
ADDRESS,  IPAddress,  "Device Address";
MFG,    DevMfg,   "Manufacturer";
DEV_TYPE, DevType,   "Device Type";
DEV_REV,  DevRev,   "Device Revision";
TAG,    DevTag,   "Device Tag";
POLL_ADDR, DevPollAddr, "Poll Address";
}
}
VARIABLE IPAddress
{
LABEL "ISA100 Wireless Node Address";
HELP "Address of the ISA100 Node";
CLASS DEVICE;
TYPE OCTET (16 );
HANDLING READ & WRITE;
}
VARIABLE DevMfg
{
– 14 – IEC 62769-150-1:2023 RLV © IEC 2023
LABEL "Manufacturer";
CLASS DEVICE;
TYPE UNSIGNED_INTEGER(4);
HANDLING READ & WRITE;
}
VARIABLE DevType
{
LABEL "Model Id";
CLASS DEVICE;
TYPE UNSIGNED_INTEGER(2);
HANDLING READ & WRITE;
}
VARIABLE DevRev
{
LABEL "Device Revision";
CLASS DEVICE;
TYPE UNSIGNED_INTEGER(2);
HANDLING READ & WRITE;
}
VARIABLE DevTag
{
LABEL "Tag";
CLASS DEVICE;
TYPE ASCII(16);
HANDLING READ & WRITE;
}
VARIABLE DevPollAddr
{
LABEL "Poll Address";
HELP “Short address of the device”;
CLASS DEVICE;
TYPE UNSIGNED_INTEGER(2)
{
MIN_VALUE 01; //Define appropriate min value for various revisions
}
HANDLING READ & WRITE;
}
5.5.2 Communication Device definition ®
Communication Package shall contain an EDD element
According to IEC 62769-7 each FDI
describing the communication device. The following EDDL source code in is an example
describing a Communication Server.
COMPONENT ISA100_Wireless_Communication_Server
{
LABEL "ISA100 Wireless communication server",
PRODUCT_URI "urn:Wireless Compliance Institute:ISA100 Wireless
Communication  Server";
CAN_DELETE TRUE;
CLASSIFICATION NETWORK_COMPONENT;
COMPONENT_RELATIONS
{
ISA100_Wireless_Communication_Device_Setup
}
}
COMPONENT_RELATION ISA100_Wireless_Communication_Device_Setup
{
LABEL "Relation between Device and communication device";
RELATION_TYPE CHILD_COMPONENT;
ADDRESSING {IPAddress}
COMPONENTS
{
ISA100_Wireless_Communication_Device{AUTO_CREATE 1;}
}
}
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. ®
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 ISA100 WIRELESS communication device.
COMPONENT ISA100_Wireless_Communication_Device
{
LABEL "ISA100 Wireless communication device";
CAN_DELETE TRUE;
CLASSIFICATION NETWORK_COMPONENT;
COMPONENT_RELATIONS
{
ISA100_Wireless_Service_Provider_Relation
}
}
COMPONENT_RELATION ISA100_Wireless_Service_Provider_Relation
{
LABEL "ISA100 Wireless communication service provider”;
RELATION_TYPE CHILD_COMPONENT;
COMPONENTS
{
ISA100_Wireless_Service_Provider{AUTO_CREATE 1;}
}
MINIMUM_NUMBER 1;
MAXIMUM_NUMBER 1;
}
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.
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 below is an example for an ISA100 Wireless communication service provider
component:
The component reference (ConnectionPoint_ISA100_Wireless) corresponds to the related
connection point definition in 5.5.
COMPONENT ISA100_Wireless_Service_Provider
{
– 16 – IEC 62769-150-1:2023 RLV © IEC 2023
LABEL "ISA100 Wireless communication service provider";
CAN_DELETE FALSE;
CLASSIFICATION NETWORK_COMMUNICATION_SERVICE_PROVIDER;
COMPONENT_RELATIONS
{
ISA100_Wireless_Connection_Point_Relation
}
BYTE_ORDER BIG_ENDIAN;
}
COMPONENT_RELATION
ISA100_Wireless_Service_Provider_Connection_Point_Relation
{
LABEL "Relation between communication service provider and
connection point";
RELATION_TYPE CHILD_COMPONENT;
ADDRESSING {IPAddress}
COMPONENTS
{
ConnectionPoint_ISA100_Wireless{ AUTO_CREATE 1;}
}
MINIMUM_NUMBER 1;
MAXIMUM_NUMBER 1;
}
Semantics of the EDDL constructs shown with the EDDL source code above are described in
® ®
server and FDI
IEC 62769-7. The EDDL COMPONENT will be utilized by the 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 network configuration constraints using the component construct.
COMPONENT Network_ISA100_Wireless
{
LABEL "ISA100 Network";
CAN_DELETE TRUE;
CLASSIFICATION NETWORK;
PROTOCOL ISA100_WIRELESS;
COMPONENT_RELATIONS
{
ISA100_Wireless_Network_Connection_Point_Relation
}
COMPONENT_RELATION ISA100_Wireless_Network_Connection_Point_Relation
{
LABEL "Relation between network and connection point";
RELATION_TYPE CHILD_COMPONENT;
ADDRESSING {IPAddress}
COMPONENTS
{
ConnectionPoint_ISA100_Wireless
}
MINIMUM_NUMBER 1;
MAXIMUM_NUMBER 1;
}
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 Communication Server contained Information Model shall implement services according to
method signatures described in 5.6.1.
5.6.1.2 Connect
Table 10 shows the Method Connect arguments.
Signature:
Connect (
[in] ByteString CommunicationRelationId,
[in] ByteString IPAddress,
[in] UInt32 ConnectType,
[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.
IPAddress 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 device’s node address.
ConnectType ConnectType specifies the type of connection communication server shall make
with the ISA100 Wireless device. Below are valid connection types
0: Client
1: Server
2: Publisher
3: Subscriber
4: Bulk Transfer Client
6: Reserved
7: Alert Subscription
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
NOTE 1 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.
NOTE 2 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 for ISA100 Wireless devices.

– 18 – IEC 62769-150-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] UInt16 AppID,
[in] UInt16 ObjectID,
[in] UInt16 AttrOrMethID,
[in] UInt16 SubIndex,
[in] Byte][] WriteData,
[in] UInt32 RequestId,
[out] Byte][] ReadData,
[out] Int32 ServiceError);
Table 12 – Method Transfer arguments
Argument Description
CommunicationRelationId The argument value contains the nodeId of the ConnectionPoint
...