oSIST prEN IEC 62769-101-1:2022
(Main)Field device Integration (FDI) - Part 101-1: Profiles - Foundation Fieldbus H1
Field device Integration (FDI) - Part 101-1: Profiles - Foundation Fieldbus H1
IEC 62769-101-1:2023 is available as IEC 62769-101-1:2023 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.
IEC 62769-101-1:2023 specifies an FDI®[1] profile of IEC 62769 for IEC 61784‑1_CP 1/1 (Foundation™ Fieldbus H1)[2].
[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] 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.
Feldgeräteintegration (FDI) - Teil 101-1: Profile - Foundation Fieldbus H1
Intégration des appareils de terrain (FDI) - Partie 101-1: Profils - Foundation Fieldbus H1
IEC 62769-101-1:2023 est disponible sous forme de IEC 62769-101-1:2023 RLV qui contient la Norme internationale et sa version Redline, illustrant les modifications du contenu technique depuis l'édition précédente.
L'IEC 62769-101-1:2023 spécifie un profil FDI®[1] de l'IEC 62769 pour le profil de communication CP 1/1 (Foundation™ Fieldbus H1)[2] défini dans l'IEC 61784‑1.
[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.
[2] Foundation™ Fieldbus est l'appellation commerciale du consortium Fieldbus Foundation, une organisation à but non lucratif. Cette information est donnée à l'intention des utilisateurs du présent rapport technique et ne signifie nullement que l'IEC approuve le détenteur des appellations commerciales ou l'emploi de ses produits. La conformité n'exige pas l'utilisation de l'appellation commerciale. L'utilisation de l'appellation commerciale exige l'autorisation du détenteur de l'appellation commerciale.
Integracija procesne naprave (FDI) - 101-1. del: Profili - Osnovno procesno vodilo H1
General Information
Relations
Standards Content (Sample)
SLOVENSKI STANDARD
oSIST prEN IEC 62769-101-1:2022
01-maj-2022
Integracija procesne naprave (FDI) - 101-1. del: Profili - Osnovno procesno vodilo
Field device Integration (FDI) - Part 101-1: Profiles - Foundation Fieldbus H1Feldgeräteintegration (FDI) - Teil 101-1: Profile - Foundation Fieldbus H1
Intégration des appareils de terrain (FDI) - Partie 101-1: Profils - Foundation Fieldbus H1
Ta slovenski standard je istoveten z: prEN IEC 62769-101-1:2022ICS:
25.040.40 Merjenje in krmiljenje Industrial process
industrijskih postopkov measurement and control
35.240.50 Uporabniške rešitve IT v IT applications in industry
industriji
oSIST prEN IEC 62769-101-1:2022 en,fr,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------oSIST prEN IEC 62769-101-1:2022
---------------------- Page: 2 ----------------------
oSIST prEN IEC 62769-101-1:2022
65E/860/CDV
COMMITTEE DRAFT FOR VOTE (CDV)
PROJECT NUMBER:
IEC 62769-101-1 ED3
DATE OF CIRCULATION: CLOSING DATE FOR VOTING:
2022-03-04 2022-05-27
SUPERSEDES DOCUMENTS:
65E/827/RR
IEC SC 65E : DEVICES AND INTEGRATION IN ENTERPRISE SYSTEMS
SECRETARIAT: SECRETARY:
United States of America Mr Donald (Bob) Lattimer
OF INTEREST TO THE FOLLOWING COMMITTEES: PROPOSED HORIZONTAL STANDARD:
Other TC/SCs are requested to indicate their interest, if any,
in this CDV to the secretary.
FUNCTIONS CONCERNED:
EMC ENVIRONMENT QUALITY ASSURANCE SAFETY
SUBMITTED FOR CENELEC PARALLEL VOTING NOT SUBMITTED FOR CENELEC PARALLEL VOTING
Attention IEC-CENELEC parallel votingThe attention of IEC National Committees, members of
CENELEC, is drawn to the fact that this Committee Draft for
Vote (CDV) is submitted for parallel voting.
The CENELEC members are invited to vote through the
CENELEC online voting system.
This document is still under study and subject to change. It should not be used for reference purposes.
Recipients of this document are invited to submit, with their comments, notification of any relevant patent rights of which they
are aware and to provide supporting documentation.TITLE:
Field device Integration (FDI) - Part 101-1: Profiles - Foundation Fieldbus H1
PROPOSED STABILITY DATE: 2025
Copyright © 2022 International Electrotechnical Commission, IEC. All rights reserved. It is permitted to download this
electronic file, to make a copy and to print out the content for the sole purpose of preparing National Committee positions.
You may not copy or "mirror" the file or printed version of the document, or any part of it, for any other purpose without
permission in writing from IEC.---------------------- Page: 3 ----------------------
oSIST prEN IEC 62769-101-1:2022
65E/860/CDV – 2 – IEC CDV 62769-101-1 © IEC:2022
NOTE FROM TC/SC OFFICERS:
---------------------- Page: 4 ----------------------
oSIST prEN IEC 62769-101-1:2022
65E/860/CDV – 3 – IEC CDV 62769-101-1 © IEC:2022
1 CONTENTS
3 FOREWORD .......................................................................................................................... 5
4 1 Scope ............................................................................................................................. 7
5 2 Normative references ...................................................................................................... 7
6 3 Terms, definitions, abbreviated terms and acronyms ....................................................... 8
7 3.1 Terms and definitions ............................................................................................. 8
8 3.2 Abbreviated terms and acronyms ........................................................................... 8
9 4 Conventions .................................................................................................................... 8
10 4.1 EDDL syntax .......................................................................................................... 8
11 4.2 XML syntax ............................................................................................................ 8
12 4.3 Capitalizations........................................................................................................ 8
13 5 Profile for CP 1/1 (FOUNDATION™ H1) ............................................................................. 9
14 5.1 General .................................................................................................................. 9
15 5.2 Catalog profile ........................................................................................................ 9
16 5.2.1 Protocol support file ........................................................................................ 9
17 5.2.2 CommunicationProfile definition ...................................................................... 9
18 5.2.3 Profile device .................................................................................................. 9
19 5.2.4 Protocol version information ............................................................................ 9
20 5.3 Associating a Package with a CP 1/1 device ........................................................ 10
21 Device type identification mapping ................................................................ 10
22 5.3.1 Device type revision mapping ........................................................................ 10
23 5.4 Information Model mapping .................................................................................. 10
24 ProtocolType definition ................................................................................. 10
25 5.4.1 DeviceType mapping ..................................................................................... 10
26 5.4.2 FunctionalGroup Identification definition ....................................................... 11
27 5.4.3 BlockType property mapping ......................................................................... 11
28 5.4.4 Mapping to Block ParameterSet .................................................................... 12
29 5.5 Topology elements ............................................................................................... 12
30 ConnectionPoint definition ............................................................................ 12
31 5.5.1 Communication Device definition .................................................................. 13
32 5.5.2 Communication service provider definition .................................................... 15
33 5.5.3 Network definition ......................................................................................... 16
34 5.6 Methods ............................................................................................................... 17
35 Methods for FDI Communication Servers ...................................................... 17
36 5.6.2 Methods for Gateways .................................................................................. 24
37 Annex A (normative) Topology scan schema ....................................................................... 25
38 A.1 General ................................................................................................................ 25
39 A.2 Target Namespace ............................................................................................... 25
40 A.3 FoundationH1AddressT ........................................................................................ 25
41 A.4 FoundationH1ConnectionPointT ........................................................................... 25
42 A.5 FoundationH1NetworkT ........................................................................................ 26
---------------------- Page: 5 ----------------------oSIST prEN IEC 62769-101-1:2022
65E/860/CDV – 4 – IEC CDV 62769-101-1 © IEC:2022
43 A.6 Network ................................................................................................................ 26
44 A.7 FoundationBlockIdentificationT ............................................................................. 27
45 A.8 FoundationIdentificationT ..................................................................................... 27
46 Annex B (normative) Transfer service parameters ............................................................... 29
47 B.1 General ................................................................................................................ 29
48 B.2 receiveData .......................................................................................................... 29
49 B.3 sendData .............................................................................................................. 29
50 B.4 OperationT ........................................................................................................... 30
51 B.5 ResponseCodeT ................................................................................................... 30
52 B.6 TransferResultDataT ............................................................................................ 30
53 B.7 TransferSendDataT .............................................................................................. 31
54 Annex C (informative) Communication service arguments for Transfer Method................... 32
55 Bibliography ......................................................................................................................... 33
57 No table of figures entries found.58 Table 1 – Capability File part .................................................................................................. 9
59 Table 2 – CommunicationProfile definition .............................................................................. 9
60 Table 3 – Device type catalog mapping ................................................................................ 10
61 Table 4 – ProtocolType Foundation_H1 definition................................................................. 10
62 Table 5 – Inherited DeviceType Property mapping ............................................................... 10
63 Table 6 – Identification Parameters ...................................................................................... 11
64 Table 7 – Inherited BlockType property mapping .................................................................. 11
65 Table 8 – ConnectionPointType ConnectionPoint_Foundation_H1 definition ........................ 12
66 Table 9 – Communication device ParameterSet definition .................................................... 15
67 Table 10 – Method Connect arguments ................................................................................ 17
68 Table 11 – Method Disconnect arguments ............................................................................ 18
69 Table 12 – Method Transfer arguments ................................................................................ 20
70 Table 13 – Method GetPublishedData arguments ................................................................. 21
71 Table 14 – Method SetAddress arguments ........................................................................... 23
72 Table A.1 – Attributes of FoundationH1ConnectionPointT .................................................... 26
73 Table A.2 – Elements of FoundationH1ConnectionPointT ..................................................... 26
74 Table A.3 – Elements of FoundationH1NetworkT .................................................................. 26
75 Table A.4 – Attributes of FoundationBlockIdentificationT ...................................................... 27
76 Table A.5 – Attributes of FoundationIdentificationT .............................................................. 28
77 Table B1 – Elements of receiveData ..................................................................................... 29
78 Table B2 – Enumerations of OperationT ............................................................................... 30
79 Table B3 – Attributes of ResponseCodeT ............................................................................. 30
80 Table B4 – Attributes of TransferResultDataT ...................................................................... 31
81 Table B5 – Attributes of TransferSendDataT ........................................................................ 31
---------------------- Page: 6 ----------------------oSIST prEN IEC 62769-101-1:2022
IEC CDV 62769-101-1 © IEC:2022 – 5 –
84 INTERNATIONAL ELECTROTECHNICAL COMMISSION
85 ____________
87 FIELD DEVICE INTEGRATION (FDI) –
89 Part 101-1: Profiles – Foundation Fieldbus H1
91 FOREWORD
92 1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising all national
93 electrotechnical committees (IEC National Committees). The object of IEC is to promote international co -operation on all
94 questions concerning standardization in the electrical and electronic fields. To this end and in addition to other activities, IE C
95 publishes International Standards, Technical Specifications, Technical Reports, Publicly Available Specifications (PAS) and
96 Guides (hereafter referred to as “IEC Publication(s)”). Their preparation is entrusted to technical committees; any IEC National
97 Committee interested in the subject dealt with may participate in this preparatory work. International, governmental and non -
98 governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely with the
99 International Organization for Standardization (ISO) in accordance with conditions determined by agreement between the two
100 organizations.101 2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international consensus
102 of opinion on the relevant subjects since each technical committee has representation from all interested IEC National
103 Committees.104 3) IEC Publications have the form of recommendations for international use and are accepted by IEC National Committees in
105 that sense. While all reasonable efforts are made to ensure that the technical content of IEC Publications is accurate, IEC
106 cannot be held responsible for the way in which they are used or for any misinterpretation by any end user.
107 4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications transparently to
108 the maximum extent possible in their national and regional publications. Any divergence between any IEC Publication and the
109 corresponding national or regional publication shall be clearly indicated in the latter.
110 5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity assessment
111 services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any services carried out by
112 independent certification bodies.113 6) All users should ensure that they have the latest edition of this publication.
114 7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and members of its
115 technical committees and IEC National Committees for any personal injury, property damage or other damage of any nature
116 whatsoever, whether direct or indirect, or for costs (including legal fees) and expenses arising out of the publication, use of,
117 or reliance upon, this IEC Publication or any other IEC Publications.118 8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is indispensable
119 for the correct application of this publication.120 9) Attention is drawn to the possibility that some of the elements of this IEC Publication may b e the subject of patent rights. IEC
121 shall not be held responsible for identifying any or all such patent rights.122 62769-101-1 has been prepared by subcommittee 65E: Devices and integration in enterprise systems, of
123 IEC technical committee 65: Industrial-process measurement, control and automation. It is an International
124 Standard.125 This third edition cancels and replaces the second edition published in 2021. This edition constitutes a
126 technical revision.127 This edition includes the following significant technical changes with respect to the previous edition:
128 a) updated Transfer service;129 b) added OPERATION “GETOD” and “GETDEVICETYPEINFO”;
130 c) added DeviceTag and Block_Index to FoundationIdentificationT and Target;
131 d) removed arguments “BlockTag” and “ServiceId”;
---------------------- Page: 7 ----------------------
oSIST prEN IEC 62769-101-1:2022
65E/860/CDV – 6 – IEC CDV 62769-101-1 © IEC:2022
132 e) changed content type of CFF file to application/vnd.ff.cff.
133 The text of this International Standard is based on the following documents:
Draft Report on voting
XX/XX/FDIS XX/XX/RVD
134
135 Full information on the voting for its approval can be found in the report on voting indicated in the above
136 table.137 The language used for the development of this International Standard is English.
138 This document was drafted in accordance with ISO/IEC Directives, Part 2, and developed in accordanc e
139 with ISO/IEC Directives, Part 1 and ISO/IEC Directives, IEC Supplement, available at
140 www.iec.ch/members_experts/refdocs. The main document types developed by IEC are described in
141 greater detail at www.iec.ch/standardsdev/publications.142 The committee has decided that the contents of this document will remain unchanged until the stability
143 date indicated on the IEC website under "http://webstore.iec.ch" in the data related to the specific
144 document. At this date, the document will be145 • reconfirmed,
146 • withdrawn,
147 • replaced by a revised edition, or
148 • amended.
149
---------------------- Page: 8 ----------------------
oSIST prEN IEC 62769-101-1:2022
IEC CDV 62769-101-1 © IEC:2022 – 7 –
150 FIELD DEVICE INTEGRATION (FDI) –
151
152 Part 101-1: Profiles – Foundation Fieldbus H1
153
154
155
156 1 Scope
157 This part of IEC 62769 specifies an FDI profile of IEC 62769 for IEC 61784-1_CP 1/1 (FOUNDATION™
158 Fieldbus H1) .159 2 Normative references
160 The following documents, in whole or in part, are normatively referenced in this document and are
161 indispensable for its application. For dated references, only the edition cited applies. For undated
162 references, the latest edition of the referenced document (including any amendments) applies.
163 IEC 61158-5-9:2007, Industrial communication networks - Fieldbus specifications – Part 5-9: Application
164 layer service definition – Type 9 elements165 IEC 61784-1, Industrial communication networks—Profiles—Part 1: Fieldbus Profiles
166 IEC 61784-2, Industrial communication networks – Profiles – Part 2: Additional fieldbus profiles for real-
167 time networks based on ISO/IEC 8802-3168 IEC 61784-3:2010, Industrial communication networks – Profiles – Part 3: Functional safety fieldbuses –
169 General rules and profile definitions170 IEC 61804 (all parts), Function blocks (FB) for process control and Electronic Device Description
171 Language (EDDL)172 IEC 62769-100, OPC Unified Architecture – Part 100: OPC UA for Devices
173 IEC 62769-1, Field Device Integration (FDI) – Part 1: Overview
174 IEC 62769-2, Field Device Integration (FDI) – Part 2: FDI Client
175 IEC 62769-3, Field Device Integration (FDI) – Part 3: FDI Server
176 IEC 62769-4, Field Device Integration (FDI) – Part 4: FDI Packages
177 IEC 62769-5, Field Device Integration (FDI) – Part 5: FDI Information Model
178 IEC 62769-6, Field Device Integration (FDI) – Part 6: FDI Technology Mapping
179 IEC 62769-7, Field Device Integration (FDI) – Part 7: FDI Communication Devices
180FOUNDATION™ 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.---------------------- Page: 9 ----------------------
oSIST prEN IEC 62769-101-1:2022
65E/860/CDV – 8 – IEC CDV 62769-101-1 © IEC:2022
181 3 Terms, definitions, abbreviated terms and acronyms
182 3.1 Terms and definitions
183 For the purposes of this document, the terms and definitions given in IEC 62769-100, IEC 62769-1,
184 IEC 62769-2, IEC 62769-3, IEC 62769-4, IEC 62769-5, IEC 62769-6, IEC 62769-7 and the following
185 apply.186 3.2 Abbreviated terms and acronyms
187 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)
EDDL Electronic Device Description Language (see IEC 61804)
FB function block
IM Information Model
SMIB system management information base
VFD virtual field device
188 4 Conventions
189 4.1 EDDL syntax
190 This part of IEC 62769 specifies content for the EDD component that is part of an FDI Communication
191 Package. EDDL syntax uses the font Courier New. EDDL syntax is used for method signature, variable,
192 data structure and component declarations.193 4.2 XML syntax
194 XML syntax examples use the font Courier New. The XML syntax is used to describe XML document
195 schema.196 Example: .
197 4.3 Capitalizations
198 The IEC 62769 series uses capitalized terms to emphasize that these terms have an FDI specific meaning.
199 Some of these terms use an acronym as a prefix for example200 • FDI Client, or
201 • FDI Server.
202 Some of these terms are compound terms such as:
203 • Communication Servers, or
204 • Profile Package.
205 Parameter names or attributes are concatenated to a single term, where the original terms start in this
206 term with a capital letter such as:---------------------- Page: 10 ----------------------
oSIST prEN IEC 62769-101-1:2022
IEC CDV 62769-101-1 © IEC:2022 – 9 –
207 • ProtocolSupportFile, or
208 • ProtocolType.
209 Parameter names or attributes can also be constructed by using an underscore character to concatenate
210 two or more terms such as:211 • PROFILE_ID, or
212 • Profibus_PA_Network.
213 5 Profile for CP 1/1 (FOUNDATION™ H1)
214 5.1 General
215 This profile specifies the protocol specifics needed for FDI Packages describing communication servers,
216 gateways and devices.217 5.2 Catalog profile
218 5.2.1 Protocol support file
219 5.2.1.1 Capability file
220 Each CP 1/1 FDI Device Package shall contain a capability file. The capability file part is described in
221 Table 1.222 Table 1 – Capability File part
Parameter Description
Content Type: application/vnd.ff.cff
Root Namespace: Not applicable
Source Relationship: http://fdi-cooperation.com/2010/relationships/attachment-protocol
Filename: Use file extension .CFF223 5.2.2 CommunicationProfile definition
224 IEC 62769-4 defines a CommunicationProfileT string type for the Catalog XML schema. Table 2 defines
225 the CP 1/1 specific values for this string.226 Table 2 – CommunicationProfile definition
CommunicationProfile Description
foundation_h1 CP 1/1 device type with a function block application
227
228 5.2.3 Profile device
229 Not supported in this standard.
230 5.2.4 Protocol version information
231 IEC 62769-4 defines an element type named InterfaceT for the Catalog XML Schema. Element type
232 InterfaceT contains an element named Version which is supposed to provide version information about
233 the applied communication protocol profile. The value follows the IEC 62769-4 defined version information
234 schema defined in element type VersionT.235 The major version part of VersionT shall be set to the ITK_VER parameter. The minor and builds parts
236 shall be set to 0.---------------------- Page: 11 ----------------------
oSIST prEN IEC 62769-101-1:2022
65E/860/CDV – 10 – IEC CDV 62769-101-1 © IEC:2022
237 EXAMPLE For ITK_VER 5, the value for InterfaceT is 5.0.0.
238 5.3 Associating a Package with a CP 1/1 device
239 Device type identification mapping
240 CP 1/1 device types are uniquely identified by the parameters MANUFAC_ID, DEVICE_TYPE and
241 DEV_REV found in the Resource Block. These parameters are used to associate a given device instance
242 to an FDI Device Package. These parameters are mapped to the FDI Device Package Catalog according
243 to Table 3.244 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).
245 5.3.1 Device type revision mapping
246 Each device type is identified according to 1.1.1. A device may also include a parameter
247 COMPATIBILITY_REV from the Resource Block. This parameter specifies the lowest device version
248 (DEV_REV) that a new device can replace while maintaining compatibility with a prior FDI Device Package.
249 5.4 Information Model mapping250 ProtocolType definition
251 Table 4 defines the ProtocolType used to identify CP 1/1 network communications.
252 Table 4 – ProtocolType Foundation_H1 definitionAttribute Value
BrowseName Foundation_H1
IsAbstract False
References NodeClass BrowseName DataType TypeDefinition ModellingRule
Inherits the properties of ProtocolType defined in IEC 62541-100.
253
254 5.4.1 DeviceType mapping
255 Each device type inherits the properties of the DeviceType. The mapping of the inherited properties from
256 the DeviceType is defined in Table 5.257 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)
---------------------- Page: 12 ----------------------
oSIST prEN IEC 62769-101-1:2022
IEC CDV 62769-101-1 © IEC:2022 – 11 –
Property CP Mapping
Model String obtained from FDI package catalog (Name of
DeviceTypeT, which is a localized name)
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)
Device manuals are exposed as attachments of the FDI Device Package.
258
259 5.4.2 FunctionalGroup Identification definition
260 As defined in IEC 62541-100, each device representation in the FDI Server hosted Information Model shall
261 contain a protocol specific FunctionalGroup called Identification. This FunctionalGroup organizes
262 variables found in the Resource Block of the device type instance. The FunctionalGroup Identification for
263 CP 1/1 is defined in Table 6.264 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
265 5.4.3 BlockType property mapping
266 CP 1/1 device types are block-oriented according to IEC 62541-100. IEC 62769-5 specifies the mapping
267 of EDDL BLOCK_A elements to block types and instances268 The BLOCK_A maps as a subtype of the topology element BlockType and inherits the properties per
269 IEC 62541-100. The mapping of the inherited properties of the BlockType is specified in Table 7.
270 Table 7 – Inherited BlockType property mappingProperty CP Mapping (Block ParameterSet)
RevisionCounter ST_REV
ActualMode MODE_BLK.ACTUAL
PermittedMode MODE_BLK.PERMITTED
NormalMode MODE_BLK.NORMAL
TargetMode MODE_BLK.TARGET
---------------------- Page: 13 ----------------------
oSIST prEN IEC 62769-101-1:2022
65E/860/CDV – 12 – IEC CDV 62769-101-1 © IEC:2022
271 5.4.4 Mapping to Block ParameterSet
272 The ParameterSet is relative to each Block. The ParameterSet includes the CHARACTERISTICS records
273 of the block and all the parameters found in the PARAMETERS, LOCAL_PARAMETERS and LIST_ITEMS.
274 The browse name of the parameters found in the PARAMETERS and LOCAL_PARAMETERS is the
275 member name in the respective lists. For example, ST_REV is the browse name of the Static Revision
276 parameter. LIST_ITEMS do not have member names; therefore the browse name of each L IST in the
277 LIST_ITEMS is the item name of the list.278 5.5 Topology elements
279 ConnectionPoint definition
280 The ConnectionPoint type ConnectionPoint_Foundation_H1 shall be used to identify CP 1/1 network
281 communication and is defined in Table 8. The ConnectionPoint_Foundation_H1 type is a sub type of the
282 abstract type ConnectionPointType defined in IEC 62769-100.283 The Address property shall be the H1 node address
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.