Field Device Integration (FDI) – Part 101-2: Profiles – Foundation Fieldbus HSE FCG TS62769-101-2 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-2: Profiles – Foundation Fieldbus HSE RELEASED FCG TS62769-101-2 , Ed. 1.2.0, 09 Jul 2019 Page 1 of 27 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-2: Profiles – Foundation Fieldbus HSE RELEASED FCG TS62769-101-2, Ed. 1.2.0, 09 Jul 2019 Page 2 of 27 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 15 January 2016 Issue reports #1821, #1825 1.0.4 27 March 2016 Adaption to new template. Resolution for issues 1824, 1843,1844. 1.1.0.1 4 June 2016 Adaption to new versioning scheme. Fixed wrong references. Issue reports #1851, #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 October 2016 Removed ServiceId from methods Connect and GetPublishedData. DEV_REV and ITK_VER are only available if the HSE device exposes a function block VFD. Certain HSE Devices do not expose a 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 Minor 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-2: Profiles – Foundation Fieldbus HSE RELEASED FCG TS62769-101-2 , Ed. 1.2.0, 09 Jul 2019 Page 3 of 27 TABLE OF CONTENTS 1 Scope ........................................................................................................................................................... 5 2 Normative references .................................................................................................................................. 5 3 Terms, definitions, abbreviated terms and acronyms ................................................................................... 5 3.1 Terms and definitions .................................................................................................................... 5 3.2 Abbreviated terms and acronyms .................................................................................................. 5 4 Conventions ................................................................................................................................................. 6 4.1 EDDL syntax .................................................................................................................................. 6 4.2 XML syntax .................................................................................................................................... 6 5 Profile for CP 1/2 (F OUNDATION ™ HSE) ........................................................................................................... 6 5.1 General ......................................................................................................................................... 6 5.2 Catalog profile .............................................................................................................................. 6 Protocol support file ................................................................................................... 6 5.2.1.1 Capability file ......................................................................................................... 6 CommunicationProfile definition ................................................................................ 6 Profile device ............................................................................................................. 7 Protocol version information ...................................................................................... 7 5.3 Associating a Package with a CP 1/2 device ................................................................................... 7 Device type identification mapping ............................................................................. 7 Device type revision mapping ..................................................................................... 7 5.4 Information Model mapping .......................................................................................................... 7 ProtocolType definition .............................................................................................. 7 DeviceType mapping ................................................................................................... 8 FunctionalGroup Identification definition ................................................................... 8 BlockType property mapping ...................................................................................... 9 Mapping to Block ParameterSet .................................................................................. 9 5.5 Topology elements ........................................................................................................................ 9 ConnectionPoint definition ......................................................................................... 9 Communication Device definition ............................................................................. 10 Communication service provider definition .............................................................. 12 Network definition ................................................................................................... 12 5.6 Methods ..................................................................................................................................... 13 Methods for FDI Communication Servers .................................................................. 13 5.6.1.1 General ................................................................................................................ 13 5.6.1.2 Connect ................................................................................................................ 13 5.6.1.3 Disconnect ........................................................................................................... 14 5.6.1.4 Transfer ................................................................................................................ 15 5.6.1.5 GetPublishedData ................................................................................................. 17 5.6.1.6 SetAddress ........................................................................................................... 18 5.6.1.7 Scan ..................................................................................................................... 19 5.6.1.8 ResetScan ............................................................................................................. 19 Field Device Integration (FDI) – Part 101-2: Profiles – Foundation Fieldbus HSE RELEASED FCG TS62769-101-2, Ed. 1.2.0, 09 Jul 2019 Page 4 of 27 Methods for Gateways ............................................................................................. 20 Annex A (normative) Topology scan schema ...................................................................................................... 21 A.1 General ....................................................................................................................................... 21 A.2 Network ...................................................................................................................................... 21 A.3 FoundationHSEAddressT .............................................................................................................. 21 A.4 FoundationHSEConnectionPointT ................................................................................................ 21 A.5 FoundationHSENetworkT ............................................................................................................. 22 A.6 FoundationBlockIdentificationT ................................................................................................... 22 A.7 FoundationIdentificationT ........................................................................................................... 23 Annex B (normative) Transfer service parameters ............................................................................................. 25 Annex C (informative) Communication service arguments for Transfer Method ................................................ 26 Bibliography ...................................................................................................................................................... 27 Table 1 – Capability File part ................................................................................................................................ 6 Table 2 – CommunicationProfile definition .......................................................................................................... 6 Table 3 – Device type catalog mapping ................................................................................................................ 7 Table 4 – ProtocolType Foundation_HSE definition .............................................................................................. 8 Table 5 – Inherited DeviceType property mapping ............................................................................................... 8 Table 6 – Identification parameters ..................................................................................................................... 8 Table 7 – Inherited BlockType property mapping ................................................................................................. 9 Table 8 – ConnectionPointType ConnectionPoint_Foundation_HSE definition ...................................................... 9 Table 9 – Communication device ParameterSet definition .................................................................................. 12 Table 10 – Method Connect arguments .............................................................................................................. 13 Table 11 – Method Disconect arguments ........................................................................................................... 14 Table 12 – Method Transfer arguments .............................................................................................................. 16 Table 13 – Method GetPublishedData arguments ............................................................................................... 17 Table 14 – Method SetAddress arguments ......................................................................................................... 19 Table A.1 – Attributes of FoundationHSEConnectionPointT ................................................................................ 22 Table A.2 – Elements of FoundationHSEConnectionPointT .................................................................................. 22 Table A.3 – Elements of FoundationHSENetworkT .............................................................................................. 22 Table A.4 – Attributes of FoundationBlockIdentificationT ................................................................................... 23 Table A.5 – Attributes of FoundationIdentificationT ........................................................................................... 23 Field Device Integration (FDI) – Part 101-2: Profiles – Foundation Fieldbus HSE RELEASED FCG TS62769-101-2 , Ed. 1.2.0, 09 Jul 2019 Page 5 of 27 1 Scope This part of IEC 62769 specifies the IEC 62769 profile for IEC 61784-1, CP 1/2 (F OUNDATION ™ Fieldbus HSE) 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 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 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 FCG TS62769-101-1, Field Device Integration (FDI) – Part 101-1: Profiles – Foundation Fieldbus H1 3 Terms, definitions, abbreviated terms and acronyms 3.1 Terms and definitions For the purposes of this document, the terms and definitions given in IEC 61784-1, IEC 61784-2, IEC 61804, IEC 62541-100, IEC 62769-2, IEC 62769-3, IEC 62769-4, IEC 62769-5, IEC 62769-6, IEC 62769-7 and IEC 62769-101- 1 apply. 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) 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 technical report 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-2: Profiles – Foundation Fieldbus HSE RELEASED FCG TS62769-101-2, Ed. 1.2.0, 09 Jul 2019 Page 6 of 27 EDD Electronic Device Description (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 part of IEC 62769 specifies content for the EDD component that is part of FDI Communication Packages. 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"> 5 Profile for CP 1/2 (F OUNDATION ™ HSE) 5.1 General This profile annex specifies the protocol specifics needed for FDI Packages describing communication servers, gateways and devices. 5.2 Catalog profile Protocol support file 5.2.1.1 Capability file Each CP 1/2 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 .CFH CommunicationProfile definition IEC 62769-4 defines a CommunicationProfileT string type for the Catalog XML schema. Table 2 defines the CP 1/2 specific values for this string. Table 2 – CommunicationProfile definition CommunicationProfile Description foundation_hse CP 1/2 device type Field Device Integration (FDI) – Part 101-2: Profiles – Foundation Fieldbus HSE RELEASED FCG TS62769-101-2 , Ed. 1.2.0, 09 Jul 2019 Page 7 of 27 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/2 device Device type identification mapping CP 1/2 device types are uniquely identified by the parameters MANUFAC_ID, DEVICE_TYPE and DEV_REV found in the Resource Block of the function block VFD. 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 String format “0xdddd” where dddd is the DEVICE_TYPE number in hexadecimal format. (IEC 62769-4) DEVICE_TYPE String format “0xdddd” where dddd is the DEVICE_TYPE number in hexadecimal format. DeviceRevision element ListOfSupportedDeviceRevisionsT (IEC 62769-4) DEV_REV a String format “x.0.0” where x is the DEV_REV in decimal format (no leading zeros). a Conditional: Shall be available if the device exposes a Function block VFD. Device type revision mapping Each device type is identified per 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. 5.4 Information Model mapping ProtocolType definition Table 4 defines the ProtocolType used to identify CP 1/2 network communications. Field Device Integration (FDI) – Part 101-2: Profiles – Foundation Fieldbus HSE RELEASED FCG TS62769-101-2, Ed. 1.2.0, 09 Jul 2019 Page 8 of 27 Table 4 – ProtocolType Foundation_HSE definition Attribute Value BrowseName Foundation_HSE IsAbstract False References NodeClass BrowseName DataType TypeDefinition ModellingRule Inherits the properties of ProtocolType defined in IEC 62541-100. DeviceType mapping Each device type inherits the properties of DeviceType. The mapping of the inherited properties from 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) DeviceManual entry text string (not supported) a DeviceRevision DEV_REV (Resource Block) b 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. b Conditional: Shall be available if the device exposes a Function block VFD. 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/2 is defined in Table 6. Table 6 – Identification parameters BrowseName VariableType Optional/Mandatory MANUFAC_ID UInt32 Mandatory DEV_TYPE UInt16 Mandatory DEV_REV UInt8 Conditional a HARDWARE_REV String Optional SOFTWARE_REV String Optional COMPATIBILITY_REV UInt8 Optional CAPABILITY_LEV UInt8 Optional ITK_VER UInt16 Conditional a SIF_ITK_VER UInt16 Optional FD_VER UInt16 Optional a Conditional: Shall be available if the device exposes a Function block VFD. Next >