< PreviousField Device Integration (FDI) – Part 109-1: Profiles - HART® and WirelessHART® RELEASED FCG TS62769-109-1 , Ed. 1.2.0, 23 Jul 2019 Page 9 of 43 Protocol version information FCG TS62769-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 has to follow the FCG TS62769-4 defined version information schema defined in element type VersionT. Subclause 5.2.4 describes how to apply the currently known protocol versions for CP 9/1 or CP 9/2 entries in the device catalog. The general rule is to use the Universal Revision of the protocol for the major version part of VersionT, and the value “0” for the minor version and build parts. Table 4 shows the Protocol Version Information. Table 4 – Protocol Version Information Protocol Version InterfaceT Version value HART Universal Revision 5 5.0.0 HART Universal Revision 6 6.0.0 HART Universal Revision 7 7.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. Associating a Package with a CP 9/1 device Device type identification mapping CP 9/1 device types are uniquely identified by parameters Manufacturer, Model and DeviceRevision. 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 5. Table 5 – Device type catalog mapping Catalog element CP mapping (SeeTable A.1) Manufacturer element of InterfaceT (FCG TS62769-4:–, Clause E.11) Manufacturer String format “0xdddd” where dddd is the MANUFACTURER_ID in hexadecimal format. DeviceModel element of InterfaceT (FCG TS62769-4:–, Clause E.11) Model String format “0xdddd” where dddd is the DEVICE_TYPE in hexadecimal format. DeviceRevision element ListOfSupportedDeviceRevisionsT (FCG TS62769-4:–, Clause E.21) DeviceRevision String format “x.0.0” where x is the DEVICE_REVISION in decimal format (no leading zeros). Device type revision mapping Each device type is identified as per 5.3.1. If a package with matching DeviceRevision is not available, any CP 9/1 FDI package for a corresponding manufacturer and model shall always be compatible with a field device as long as the device revision of the field device is equal to or greater than the device revision specified in the FDI package. Information Model mapping ProtocolType definition Table 6 defines the ProtocolType used to identify CP 9/1 network communications. Field Device Integration (FDI) – Part 109-1: Profiles - HART® and WirelessHART® RELEASED FCG TS62769-109-1, Ed. 1.2.0, 23 Jul 2019 Page 10 of 43 Table 6 – ProtocolType HART definition Attribute Value BrowseName HART 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 7. Table 7 – Inherited DeviceType Property mapping Property Foundation mapping SerialNumber Unique ID of a device, mapped to SERIAL_NUMBER of IdentificationT. RevisionCounter Configuration change counter, mapped to REV_COUNTER of IdentificationT 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) DeviceManual Entry text string (not supported) a DeviceRevision Device revision level of a device, mapped to DEVICE_REVISION of IdentificationT SoftwareRevision Software revision level of a device, mapped to SOFTWARE_REVISION of IdentificationT HardwareRevision Hardware revision level of a device, mapped to HARDWARE_REVISION of IdentificationT a Device manuals are exposed as attachments of the FDI Device Package. 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 device type instance. The FunctionalGroup Identification for CP 9/1 is defined in Table 8. Table 8 – Identification parameters BrowseName DataType Optional/Mandatory MANUFACTURER_ID UInt16 Mandatory DEVICE_TYPE UInt16 Mandatory DEVICE_REVISION UInt8 Mandatory UNIVERSAL_REVISION UInt8 Optional SERIAL_NUMBER UInt24 Optional HARDWARE_REVISION UInt8 Optional SOFTWARE_REVISION UInt8 Optional REVISION_COUNTER UInt16 Optional Field Device Integration (FDI) – Part 109-1: Profiles - HART® and WirelessHART® RELEASED FCG TS62769-109-1 , Ed. 1.2.0, 23 Jul 2019 Page 11 of 43 Topology elements ConnectionPoint definition 5.5.1.1 General CP 9/1 devices can support up to five different ConnectionPoint types that are used for network communications. 5.5.1.2 HART_TP5, HART_TP6, HART_TP7 The ConnectionPoint types HART_TP5, HART_TP6, and HART_TP7 shall be used to identify CP 9/1 token passing network communication and are defined in Table 9. HART_TP5, HART_TP6, and HART_TP7 all contain the same properties, but each provides different qualification information for some of the properties (described below). The Protocol Version (UNIVERSAL_REVISION) described in 5.2.3 can be used as an aid to determine which of the three token passing Connection Point types is the most appropriate. CP 9/1 token passing communications can be used on a variety of physical layers. FSK, PSK, RS485, and Infrared physical layer connections shall all use the HART_TP connection type. The ConnectionPoint types HART_TP5, HART_TP6, and HART_TP7 are subtypes of abstract type ConnectionPointType defined in FCG TS62769-5. The DevAddr property shall be the long address (5 bytes) for the device, and is the only parameter necessary to communicate with the field device. The DevMfg property shall be the 2-byte Manufacturer ID, 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 extended device type, 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 device revision, 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 long tag for HART ® protocol version 6 or 7 devices. The DevTag property shall be the tag for protocol version 5 devices. The DevTag property can be used to help automate the process of assigning live devices in the scan list to offline placeholders. HART_TP5 Connection Points shall limit the DevTag to 8 characters in length. HART_TP6 and HART_TP7 Connection Points shall limit the DevTag to 32 characters in length. The DevPollAddr property shall be the poll address, and can be used to identify which device is located at a specific poll address. HART_TP5 Connection Points shall be limited to values between 0 and 15 for the DevPollAddr property. HART_TP6 Connection Points shall be limited to values between 0 and 31 for the DevPollAddr property. HART_TP7 Connection Points shall be limited to values between 0 and 63 for the DevPollAddr property. For forward compatibility, a lower revision HART_TP Connection Point is compatible and can be used for a higher universal revision device connection. For example, if a future HART universal revision 8 device is encountered, and no HART_TP8 is available in the FDI server, HART_TP7 will be compatible and shall be used to connect to the device. If the Protocol Version (i.e. the Universal Revision) is unknown for any reason, the HART_TP5 Connection Point can be used, and will be forward compatible to later universal revisions. Field Device Integration (FDI) – Part 109-1: Profiles - HART® and WirelessHART® RELEASED FCG TS62769-109-1, Ed. 1.2.0, 23 Jul 2019 Page 12 of 43 Table 9 – ConnectionPointType HART_TP definition Attribute Value BrowseName ConnnectionPoint_HART_TP5 or ConnnectionPoint_HART_TP6 or ConnnectionPoint_HART_TP7 IsAbstract False References NodeClass BrowseName DataType TypeDefinition ModellingRule Inherits the properties of ConnectionPointType defined in FCG TS62769-5 HasProperty Variable DevAddr UInt40 PropertyType Mandatory HasProperty Variable DevMfg UInt16 PropertyType Optional HasProperty Variable DevType UInt16 PropertyType Optional HasProperty Variable DevRev UInt16 PropertyType Optional HasProperty Variable DevTag String PropertyType Optional HasProperty Variable DevPollAddr UInt8 PropertyType Optional The ConnectionPoint type HART_TP5, HART_TP6, and HART_TP7 shall be described by an EDD element contained in a Communication Device related FDI Package that can drive a CP 9/1 network. Actual ConnectionPoint properties are declared by VARIABLE constructs grouped together in a COLLECTION named ConnectionPoint_HART_TP5, ConnectionPoint_HART_TP6, or ConnectionPoint_HART_TP7. The following EDDL source code is an example describing a TP5 Connection Point. COMPONENT ConnectionPoint_HART_TP5 { LABEL "HART TP Connection Point"; CLASSIFICATION NETWORK_CONNECTION_POINT; CAN_DELETE FALSE; PROTOCOL HART; CONNECTION_POINT ConnectionPoint_TP5; } VARIABLE DevAddr { LABEL "Address"; CLASS DEVICE; TYPE UNSIGNED_INTEGER(5); HANDLING READ & WRITE; } VARIABLE DevMfg { LABEL "Manufacturer"; CLASS DEVICE; TYPE UNSIGNED_INTEGER(2); HANDLING READ & WRITE; } VARIABLE DevType { LABEL "Device Type"; CLASS DEVICE; TYPE UNSIGNED_INTEGER(2); HANDLING READ & WRITE; } Field Device Integration (FDI) – Part 109-1: Profiles - HART® and WirelessHART® RELEASED FCG TS62769-109-1 , Ed. 1.2.0, 23 Jul 2019 Page 13 of 43 VARIABLE DevRev { LABEL "Device Revision"; CLASS DEVICE; TYPE UNSIGNED_INTEGER; HANDLING READ & WRITE; } VARIABLE DevTag { LABEL "Tag"; CLASS DEVICE; TYPE ASCII(32); HANDLING READ & WRITE; } VARIABLE DevPollAddr { LABEL "Poll Address"; CLASS DEVICE; TYPE UNSIGNED_INTEGER { MAX_VALUE 15; //Define appropriate max value for various revisions } HANDLING READ & WRITE; } COLLECTION ConnectionPoint_TP5 { LABEL "Connection Point"; MEMBERS { ADDRESS, DevAddr, "Device Address"; MFG, DevMfg, "Manufacturer"; DEV_TYPE, DevType, "Device Type"; DEV_REV, DevRev, "Device Revision"; TAG, DevTag, "Device Tag"; POLL_ADDR, DevPollAddr, "Poll Address"; } } 5.5.1.3 HART_IP The ConnectionPoint type HART_IP shall be used to identify CP 9/1 IP network communication and is defined in Table 10. HART_IP communications can be used on a variety of physical layers. Ethernet connections shall all use the HART_IP connection type. Additional physical layers developed in the future may also use the HART_IP connection type. The ConnectionPoint type HART_IP is a subtype of abstract type ConnectionPointType defined in FCG TS62769-5. The IPAddress property shall indicate the IP Address (up to 16 bytes) used for the connection. The IPVersion property shall indicate the version of IP used for the connection (either 4 or 6). The IPPort property shall be the IP port number for the connection. The default port number used for HART IP is 5 094. Field Device Integration (FDI) – Part 109-1: Profiles - HART® and WirelessHART® RELEASED FCG TS62769-109-1, Ed. 1.2.0, 23 Jul 2019 Page 14 of 43 The DevAddr property shall be the long address (5 bytes) for the device. The DevMfg property shall be the 2-byte Manufacturer ID, 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 extended device type, 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 device revision, 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 long tag (with maximum 32 characters), and can be used to help automate the process of assigning live devices in the scan list to offline placeholders. Table 10 – ConnectionPointType HART_IP Definition Attribute Value BrowseName ConnnectionPoint_HART_IP IsAbstract False References NodeClass BrowseName DataType TypeDefinition ModellingRule Inherits the properties of ConnectionPointType defined in FCG TS62769-5 HasProperty Variable IPAddress ByteString PropertyType Mandatory HasProperty Variable IPVersion UInt8 PropertyType Mandatory HasProperty Variable IPPort UInt16 PropertyType Mandatory HasProperty Variable DevAddr UInt40 PropertyType Mandatory HasProperty Variable DevMfg UInt16 PropertyType Optional HasProperty Variable DevType UInt16 PropertyType Optional HasProperty Variable DevRev UInt16 PropertyType Optional HasProperty Variable DevTag String PropertyType Optional The ConnectionPoint type HART_IP shall be described by an EDD element contained in a Communication Device related FDI Package that can drive a CP 9/1 network. Actual ConnectionPoint properties are declared by VARIABLE constructs grouped together in a COLLECTION named ConnectionPoint_HART_IP. The following EDDL source code is an example describing an IP Connection Point. COMPONENT ConnectionPoint_HART_IP { LABEL "HART IP Connection Point"; CLASSIFICATION NETWORK_CONNECTION_POINT; CAN_DELETE FALSE; PROTOCOL HART; CONNECTION_POINT ConnectionPoint_IP; } ARRAY IPAddress { LABEL "IP Address"; CLASS DEVICE; TYPE OCTET(16); HANDLING READ & WRITE; } Field Device Integration (FDI) – Part 109-1: Profiles - HART® and WirelessHART® RELEASED FCG TS62769-109-1 , Ed. 1.2.0, 23 Jul 2019 Page 15 of 43 VARIABLE IPVersion { LABEL "IP Version"; CLASS DEVICE; TYPE ENUMERATED { { 4, "IPv4" }, { 6, "IPv6" } } HANDLING READ & WRITE; } VARIABLE IPPort { LABEL "IP Port"; CLASS DEVICE; TYPE UNSIGNED_INTEGER (2); DEFAULT_VALUE 5094; HANDLING READ & WRITE; } COLLECTION ConnectionPoint_IP { LABEL "Connection Point"; MEMBERS { IPADDRESS, IPAddress, "IP Address"; IPVERSION, IPVersion, "IP Version"; IPPORT, IPPort, "IP Port"; ADDRESS, DevAddr, "Device Address"; MFG, DevMfg, "Manufacturer"; DEV_TYPE, DevType, "Device Type"; DEV_REV, DevRev, "Device Revision"; TAG, DevTag, "Device Tag"; } } 5.5.1.4 HART_TDMA The ConnectionPoint type HART_TDMA shall be used to identify CP 9/2 time division media access network communication and is defined in Table 11. HART_TDMA communications can be used on a variety of physical layers. The ConnectionPoint type HART_TDMA is a subtype of abstract type ConnectionPointType defined in FCG TS62769-5. WirelessHART connections shall all use the HART_TDMA connection type. Additional physical layers developed in the future may also use the HART_TDMA connection type. The Network property shall be the network ID for the network. The DevAddr property shall be the long address (5 bytes) for the device. The DevMfg property shall be the 2 byte Manufacturer ID, 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 extended device type, 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 device revision, and can be used to help automate the process of assigning live devices in the scan list to offline placeholders. Field Device Integration (FDI) – Part 109-1: Profiles - HART® and WirelessHART® RELEASED FCG TS62769-109-1, Ed. 1.2.0, 23 Jul 2019 Page 16 of 43 The DevTag property shall be the long tag (with maximum 32 characters), and can be used to help automate the process of assigning live devices in the scan list to offline placeholders. Table 11 – ConnectionPointType HART_TDMA Definition Attribute Value BrowseName ConnnectionPoint_HART_TDMA IsAbstract False References NodeClass BrowseName DataType TypeDefinition ModellingRule Inherits the properties of ConnectionPointType defined in FCG TS62769-5 HasProperty Variable Network UInt16 PropertyType Mandatory HasProperty Variable DevAddr UInt40 PropertyType Mandatory HasProperty Variable DevMfg UInt16 PropertyType Optional HasProperty Variable DevType UInt16 PropertyType Optional HasProperty Variable DevRev UInt16 PropertyType Optional HasProperty Variable DevTag String PropertyType Optional The ConnectionPoint type HART_TDMA shall be described by an EDD element contained in a Communication Device related FDI Package that can drive a CP 9/2 network. Actual ConnectionPoint properties are declared by VARIABLE constructs grouped together in a COLLECTION named ConnectionPoint_HART_TDMA. The following EDDL source code is an example describing a TDMA Connection Point. COMPONENT ConnectionPoint_HART_TDMA { LABEL "HART TDMA Connection Point"; CLASSIFICATION NETWORK_CONNECTION_POINT; CAN_DELETE FALSE; PROTOCOL HART; CONNECTION_POINT ConnectionPoint_TDMA; } VARIABLE Network { LABEL "Network ID"; CLASS DEVICE; TYPE UNSIGNED_INTEGER (2); HANDLING READ & WRITE; Field Device Integration (FDI) – Part 109-1: Profiles - HART® and WirelessHART® RELEASED FCG TS62769-109-1 , Ed. 1.2.0, 23 Jul 2019 Page 17 of 43 } COLLECTION ConnectionPoint_TDMA { LABEL "Connection Point"; MEMBERS { NETWORK, Network, "Network ID"; ADDRESS, DevAddr, "Device Address"; MFG, DevMfg, "Manufacturer"; DEV_TYPE, DevType, "Device Type"; DEV_REV, DevRev, "Device Revision"; TAG, DevTag, "Device Tag"; } } Communication Device definition According to FCG TS62769-7 each FDI Communication Package shall contain an EDD element describing the communication device. The following EDDL source code is an example describing a FDI Communication Server. COMPONENT CommunicationServer_HART { LABEL "HART Communication Server"; CAN_DELETE TRUE; CLASSIFICATION NETWORK_COMPONENT; COMPONENT_RELATIONS { Communication_Device_Setup_HART} } COMPONENT_RELATION Communication_Device_Setup_HART { LABEL "Relation between Device and Communication Device"; RELATION_TYPE CHILD_COMPONENT; COMPONENTS { CommunicationDevice_HART{AUTO_CREATE 1;} } MINIMUM_NUMBER 1; MAXIMUM_NUMBER 4; } Semantics of the EDDL constructs shown above are described in FCG TS62769-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 FCG TS62769-7. According to FCG TS62769-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 CP 9/1 communication device. Field Device Integration (FDI) – Part 109-1: Profiles - HART® and WirelessHART® RELEASED FCG TS62769-109-1, Ed. 1.2.0, 23 Jul 2019 Page 18 of 43 COMPONENT CommunicationDevice_HART { LABEL "HART Communication Device"; CAN_DELETE TRUE; CLASSIFICATION NETWORK_COMPONENT; COMPONENT_RELATIONS { ServiceProviderRelation_HART} BYTE_ORDER BIG_ENDIAN; } COMPONENT_RELATION ServiceProviderRelation_HART { LABEL "Relation to communication service provider"; RELATION_TYPE CHILD_COMPONENT; COMPONENTS { CommunicationServiceProvider_HART {AUTO_CREATE 1;} } MINIMUM_NUMBER 1; MAXIMUM_NUMBER 1; } Semantics of the EDDL constructs shown above are described in FCG TS62769-7. The EDDL COMPONENT will be utilized by the FDI server and FDI Communication Server to create an instance of type CommunicationServerChannelType as described in FCG TS62769-7. Communication service provider definition According to FCG TS62769-7 each FDI Communication Package shall contain at least one EDD element describing at least one communication service provider component. The following EDDL source code is an example for a CP 9/1 communication service provider component. The component reference (ConnectionPoint_HART_IP) corresponds to one of the related Connection Point definitions in 5.5.1. The attribute BYTE_ORDER value is to be set according to the protocol. Next >