Field Device Integration (FDI) – Part 101-1: Profiles – Foundation Fieldbus H1 FCG TS62769-101-1 Edition 1.2.0 09 Jul 2019 RELEASED S P E C I F I C A T I O N Field Device Integration (FDI) – Part 101-1: Profiles – Foundation Fieldbus H1 RELEASED FCG TS62769-101-1 , Ed. 1.2.0, 09 Jul 2019 Page 1 of 31 Document Distribution / Maintenance Control / Document Approval To obtain information concerning document distribution control, maintenance control, and document approval please contact FieldComm Group at the address shown below. Copyright © 2019 (2014, 2017) FieldComm Group, PROFIBUS Nutzerorganisation e. V., OPC Foundation, FDT Group FieldComm Group, PROFIBUS Nutzerorganisation e.V, OPC Foundation, and FDT Group are the joint publishers of this document. The information in this document is subject to change without notice and should not be construed as a commitment by the publishers. The publishers assume no responsibility for any errors that may appear in this document. In no event shall the publishers be liable for direct, indirect, special, incidental or consequential damages of any nature or kind arising from the use of this document. This document and parts thereof must not be reproduced or copied without written permission from the publishers, and the contents thereof must not be imparted to a third party nor used for any unauthorized purpose. All rights to copyrights, registered trademarks or applications, utility models and registered patents or applications reside with their respective owners. Trademark Information FieldComm Group ™ , F OUNDATION ™ Fieldbus and HART-IP ™ are trademarks, and HART ® , WirelessHART ® , ROM ® and SIF ® are registered trademarks of FieldComm Group, Austin, Texas, USA Any use of these terms hereafter in this document, or in any document referenced by this document, implies the trademark/registered trademark. All other trademarks used in this or referenced documents are trademarks of their respective companies. For more information, contact: FDT Group 5 Industrieweg 3001 Heverlee Belgium Phone: +32 (0)10 22 22 51 fdtgroup.org FieldComm Group 9430 Research Boulevard Suite 1-120 Austin, TX 78759, USA Phone: (512) 792-2300 Fax: (512) 792-2310 fieldcommgroup.org OPC Foundation Presidential Office 8455 Infirmary Rd., Ravenna, OH 44266 P.O. Box 808 (mailing address) Mantua, Ohio 44255 Phone: (330) 839-8718 opcfoundation.org PROFIBUS Nutzerorganisation e. V. (PNO) PROFIBUS & PROFINET International (PI) Haid-und-Neu-Str. 7 76131 Karlsruhe Germany Phone: +49 721 96 58 590 Fax: +49 721 96 58 589 profibus.com profinet.com Intellectual Property Rights The FieldComm Group (the Group) does not knowingly use or incorporate any information or data into the HART, F OUNDATION Fieldbus and FDI protocol standards, which the Group does not own or have lawful rights to use. Should the Group receive any notification regarding the existence of any conflicting private IPR, the Group will review the disclosure and either (A) determine there is no conflict; (B) resolve the conflict with the IPR owner; or (C) modify the standard to remove the conflicting requirement. In no case does the Group encourage implementers to infringe on any individual's or organization's IPR. Field Device Integration (FDI) – Part 101-1: Profiles – Foundation Fieldbus H1 RELEASED FCG TS62769-101-1, Ed. 1.2.0, 09 Jul 2019 Page 2 of 31 Revision Log Version Date Change Note / History / Reason 0.9.0 5 Nov 2013 Initial Public Version 1.0 31 July 2014 First Release 1.0.3 07 Dec 2015 Integrated IEC comments, fixed EDD constructs and addressed issue 1825 (referencing Manufacturer and Model from Package metadata) 1.0.4 20 March 2016 Adaptions to new template. Replaced CommunicationServerChannelType by correct term ServerCommunicationDeviceType. Resolution for issues 1824, 1843,1844. 1.1.0.1 4 June 2016 Adaption to new versioning scheme. Fixed wrong references. Issue report #1855 1.1.0.2 2 July 2016 Removed FDI Cooperation page. Updated copyright notice etc. 1.1.0.3 8 July 2016 Updated normative references. 1.1.0.4 28 Oct 2016 Removed ServiceId from methods Connect and GetPublishedData. Schema element FoundationIdentificationT: DEV_REV, ITK_VER properties are conditional due to HSE devices having no function block VFD. 1.1.0.5 19 Dec 2016 New document template 1.1.0.6 24 Feb 2017 New cover page and trademark information 1.1.0.7 15 Aug 2017 Editorial changes to address balloting comments 1.2.0.1 17 Oct 2018 Editorial changes 1.2.0.2 09 July 2019 Editorial changes Field Device Integration (FDI) – Part 101-1: Profiles – Foundation Fieldbus H1 RELEASED FCG TS62769-101-1 , Ed. 1.2.0, 09 Jul 2019 Page 3 of 31 TABLE OF CONTENTS 1 Scope ........................................................................................................................................................... 6 2 Normative references .................................................................................................................................. 6 3 Terms, definitions, abbreviated terms and acronyms ................................................................................... 6 3.1 Terms and definitions .................................................................................................................... 6 3.2 Abbreviated terms and acronyms .................................................................................................. 6 4 Conventions ................................................................................................................................................. 7 4.1 EDDL syntax .................................................................................................................................. 7 4.2 XML syntax .................................................................................................................................... 7 4.3 Capitalizations .............................................................................................................................. 7 5 Profile for CP 1/1 (F OUNDATION ™ H1) ............................................................................................................. 8 5.1 General ......................................................................................................................................... 8 5.2 Catalog profile .............................................................................................................................. 8 Protocol support file ................................................................................................... 8 Capability file ......................................................................................................... 8 CommunicationProfile definition ................................................................................ 8 Profile device ............................................................................................................. 8 Protocol version information ...................................................................................... 8 5.3 Associating a Package with a CP 1/1 device ................................................................................... 8 Device type identification mapping ............................................................................. 8 Device type revision mapping ..................................................................................... 9 5.4 Information Model mapping .......................................................................................................... 9 ProtocolType definition .............................................................................................. 9 DeviceType mapping ................................................................................................... 9 FunctionalGroup Identification definition ................................................................. 10 BlockType property mapping .................................................................................... 10 Mapping to Block ParameterSet ................................................................................ 10 5.5 Topology elements ...................................................................................................................... 10 ConnectionPoint definition ....................................................................................... 10 Communication Device definition ............................................................................. 12 Communication service provider definition .............................................................. 14 Network definition ................................................................................................... 15 5.6 Methods ..................................................................................................................................... 15 Methods for FDI Communication Servers .................................................................. 15 General ................................................................................................................ 15 Connect ................................................................................................................ 16 Disconnect ........................................................................................................... 17 Transfer ................................................................................................................ 17 GetPublishedData ................................................................................................. 19 SetAddress ........................................................................................................... 20 Scan ..................................................................................................................... 22 Field Device Integration (FDI) – Part 101-1: Profiles – Foundation Fieldbus H1 RELEASED FCG TS62769-101-1, Ed. 1.2.0, 09 Jul 2019 Page 4 of 31 ResetScan ............................................................................................................. 22 Methods for Gateways ............................................................................................. 22 Annex A (normative) Topology scan schema ...................................................................................................... 23 A.1 General ....................................................................................................................................... 23 A.2 FoundationH1AddressT ............................................................................................................... 23 A.3 FoundationH1ConnectionPointT .................................................................................................. 23 A.4 FoundationH1NetworkT .............................................................................................................. 24 A.5 Network ...................................................................................................................................... 24 A.6 FoundationBlockIdentificationT ................................................................................................... 24 A.7 FoundationIdentificationT ........................................................................................................... 25 Annex B (normative) Transfer service parameters ............................................................................................. 27 B.1 General ....................................................................................................................................... 27 B.2 receiveData ................................................................................................................................. 27 B.3 sendData ..................................................................................................................................... 27 B.4 OperationT .................................................................................................................................. 28 B.5 ResponseCodeT ........................................................................................................................... 28 B.6 TransferResultDataT .................................................................................................................... 28 B.7 TransferSendDataT ...................................................................................................................... 29 Annex C (informative) Communication service arguments for Transfer Method ................................................ 30 Bibliography ...................................................................................................................................................... 31 Table 1 – Capability File part ................................................................................................................................ 8 Table 2 – CommunicationProfile definition .......................................................................................................... 8 Table 3 – Device type catalog mapping ................................................................................................................ 9 Table 4 – ProtocolType Foundation_H1 definition ................................................................................................ 9 Table 5 – Inherited DeviceType Property mapping ............................................................................................... 9 Table 6 – Identification Parameters ................................................................................................................... 10 Table 7 – Inherited BlockType property mapping ............................................................................................... 10 Table 8 – ConnectionPointType ConnectionPoint_Foundation_H1 definition ...................................................... 11 Table 9 – Communication device ParameterSet definition .................................................................................. 14 Table 10 – Method Connect arguments .............................................................................................................. 16 Table 11 – Method Disconnect arguments.......................................................................................................... 17 Table 12 – Method Transfer arguments .............................................................................................................. 18 Table 13 – Method GetPublishedData arguments ............................................................................................... 19 Table 14 – Method SetAddress arguments ......................................................................................................... 21 Table A.1 – Attributes of FoundationH1ConnectionPointT .................................................................................. 23 Table A.2 – Elements of FoundationH1ConnectionPointT ................................................................................... 24 Table A.3 – Elements of FoundationH1NetworkT ................................................................................................ 24 Field Device Integration (FDI) – Part 101-1: Profiles – Foundation Fieldbus H1 RELEASED FCG TS62769-101-1 , Ed. 1.2.0, 09 Jul 2019 Page 5 of 31 Table A.4 – Attributes of FoundationBlockIdentificationT ................................................................................... 25 Table A.5 – Attributes of FoundationIdentificationT ........................................................................................... 25 Table 1 – Elements of receiveData ..................................................................................................................... 27 Table 2 – Enumerations of OperationT ............................................................................................................... 28 Table 3 – Attributes of ResponseCodeT .............................................................................................................. 28 Table 4 – Attributes of TransferResultDataT ....................................................................................................... 29 Table 5 – Attributes of TransferSendDataT ......................................................................................................... 29 Field Device Integration (FDI) – Part 101-1: Profiles – Foundation Fieldbus H1 RELEASED FCG TS62769-101-1, Ed. 1.2.0, 09 Jul 2019 Page 6 of 31 1 Scope This part of IEC 62769 specifies an FDI profile of IEC 62769 for IEC 61784-1_CP 1/1 (F OUNDATION ™ Fieldbus H1) 1 . 2 Normative references The following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application. 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:2007, 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 8802-3 IEC 61784-3:2010, Industrial communication networks – Profiles – Part 3: Functional safety fieldbuses – General rules and profile definitions FCG TS61804 (all parts), Function blocks (FB) for process control and Electronic Device Description Language (EDDL) IEC 62541-100, OPC Unified Architecture – Part 100: OPC UA for Devices FCG TS62769-1, Field Device Integration (FDI) – Part 1: Overview FCG TS62769-2, Field Device Integration (FDI) – Part 2: FDI Client FCG TS62769-3, Field Device Integration (FDI) – Part 3: FDI Server FCG TS62769-4, Field Device Integration (FDI) – Part 4: FDI Packages FCG TS62769-5, Field Device Integration (FDI) – Part 5: FDI Information Model FCG TS62769-6, Field Device Integration (FDI) – Part 6: FDI Technology Mapping FCG TS62769-7, Field Device Integration (FDI) – Part 7: FDI Communication Devices 3 Terms, definitions, abbreviated terms and acronyms 3.1 Terms and definitions For the purposes of this document, the terms and definitions listed in the normative references given in Clause 2 apply. 3.2 Abbreviated terms and acronyms For the purposes of this document, the following abbreviations apply: 1 F OUNDATION ™ 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. Field Device Integration (FDI) – Part 101-1: Profiles – Foundation Fieldbus H1 RELEASED FCG TS62769-101-1 , Ed. 1.2.0, 09 Jul 2019 Page 7 of 31 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) FB function block IM Information Model SMIB system management information base VFD virtual field device 4 Conventions 4.1 EDDL syntax This part of IEC 62769 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: <xsd:simpleType name="Example">. 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. Field Device Integration (FDI) – Part 101-1: Profiles – Foundation Fieldbus H1 RELEASED FCG TS62769-101-1, Ed. 1.2.0, 09 Jul 2019 Page 8 of 31 5 Profile for CP 1/1 (F OUNDATION ™ H1) 5.1 General This profile specifies the protocol specifics needed for FDI Packages describing communication servers, gateways and devices. 5.2 Catalog profile 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 Root Namespace: Not applicable Source Relationship: http://fdi-cooperation.com/2010/relationships/attachment-protocol Filename: Use file extension .CFF 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 Profile device Not supported in this standard. 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 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. Next >