< PreviousField Device Integration (FDI) – Part 103-1: Profiles – PROFIBUS RELEASED FCG TS62769-103-1 , Ed. 1.2.0, 09 Jul 2019 Page 9 of 33 Table 1 – ProtocolSupportFile for FDI Device Packages Parameter Description Content Type text/plain Root Namespace empty Source Relationship http://fdi-cooperation.com/2010/relationship/attachment-protocol Filename According to PI Order No.: 2.122:2008 5.2.1.2 FDI Communication Packages A GSD file as specified in PI Order No.: 2.122:2008 is an optional attachment for FDI Communication Packages representing PROFIBUS DP and PROFIBUS PA devices. Table 2 specifies the parameters of ProtocolSupportFile for FDI Communication Packages. Table 2 – ProtocolSupportFile for FDI Communication Packages Parameter Description Content Type: text/plain Root Namespace: empty Source Relationship: http://fdi-cooperation.com/2010/relationship/attachment-protocol Filename: According to PI Order No.: 2.122:2008 CommunicationProfile definition IEC 62769-4 defines a CommunicationProfileT string for the Catalog XML schema. Table 3 defines the PROFIBUS specific values for this string. Table 3 – PROFIBUS CommunicationProfile definition schema Profile Identifier Protocol "profibus_dp" PROFIBUS DP/V0; PROFIBUS DP/V1; PROFIBUS DP/V2 “profibus_pa” PROFIBUS PA Profile device A Profile Package shall provide the catalog values for profile devices, enabling the FDI Server to leverage a generic device description, if a specific one is not available. The definitions in Table 4 focus on catalog content that is vendor independent. Table 4 – Catalog values for profile devices Element Attribute Content PackageType — Profile Manufacturer — Empty DeviceModel — The allowed profile identifier values (PROFILE_ID) are provided by PROFIBUS & PROFINET International (PI). PI provides and maintains an XML file (Profile_ID_Table) containing the assignment of PROFILE_ID to profiles. It is available at <http://www.profibus.com/IM/Profile_ID_Table.xml> Field Device Integration (FDI) – Part 103-1: Profiles – PROFIBUS RELEASED FCG TS62769-103-1, Ed. 1.2.0, 09 Jul 2019 Page 10 of 33 The file can be downloaded by any engineering or service tool whenever it is connected to the Internet. NOTE More information is provided in PI Order No.: 3.502 (I&M Profile) and related profile definitions are referred therein. The string format shall be hexadecimal starting with 0x, e.g. ‘0x3D00’. Protocol version information IEC 62769-4 defines an element type named InterfaceT for the Catalog XML schema. The element type InterfaceT contains an element named Version which is supposed to provide version information about the applied communication protocol profile. The value has to follow the IEC 62769-4 defined version information schema defined in the element type VersionT. Table 5 describes how to apply the currently known protocol versions defined by the non-profit consortium PROFIBUS & PROFINET International. The general rule is to apply the value “0” for parts of the version information according to IEC 62769-4 that are not used in currently known protocol versions. Table 5 – Version mapping examples 2 Protocol / Version InterfaceT Version value PROFIBUS DP/V0 0.0.0 a PROFIBUS DP/V1 1.0.0 a PROFIBUS DP/V2 2.0.0 a PROFIBUS PA 3.02 3.2.0 b , PROFIBUS PA 4.0 4.0.0 b , a The protocols PROFIBUS DP/V0, PROFIBUS DP/V1 and PROFIBUS DP/V2 contain a single number. This number is considered to be the major version. The minor and built numbers are set to “0”. b The currently known PROFIBUS PA profile numbers are considered to provide major and minor version information. Leading zeros are not considered in version value evaluation since only the actual decimal values are relevant. 5.3 Associating a Package with a device Device type identification mapping The purpose of device type identification mapping is to enable FDI host systems to compare the scan result against the topology representation in the Information Model. FDI host systems shall also be enabled to determine the FDI Device Package that fits for a device entry contained in the scan result. This will enable the user of an FDI host system to synchronize the Information Model with the actual installation. The Communication Server implemented scan service (defined in 5.6.1.7) provides the scan result through an XML document (the schema is defined in Clause A.5). The Gateway implemented scan service (defined in 5.6.2.7) provides the scan result by means of the Information Model that contains data structures created from EDD content as specified in 5.6.2.7. Common for both ways of presenting the scan result is that scan results contain device type identification and device instance identification. 2 The given table can be considered to be an example only since this document cannot foresee how future protocol versions will be defined. Field Device Integration (FDI) – Part 103-1: Profiles – PROFIBUS RELEASED FCG TS62769-103-1 , Ed. 1.2.0, 09 Jul 2019 Page 11 of 33 FDI host systems comparing the actual network topology configuration against the topology representation in the Information Model shall be enabled to handle the following situations: a) The physical Device instance identified at a specific device address is not logically present in the Information Model (as Instance): Enable the FDI Host system to find the appropriate FDI Device package according to the device catalog information. b) The physical Device instance identified by the device address is logically present in the Information Model (as Instance): Enable the FDI Host system to compare device type information presented in scan result (see the identification in Clause A.5) and the device type specific information of the Instance present in the Information Model. The FDI Device package contains device type identification information that can be compared to scan result based on the Catalog Schema in IEC 62769-4 defining the XML (simple) element types “DeviceModel” and “Manufacturer”. Both types are used in the (complex) element types “Protocol” and “RegDeviceType”. As a result of the FDI Package deployment the FDI Package information is then present in the Information Model as the specified FunctionalGroup Identification containing Ident_Number and Manufacturer_ID (see 5.4.3). The Ident_Number matches with the GSD specified Ident_Number. Manufacturer_ID is specified through the I&M profile defined VendorID and DeviceID (see 5.4.3). The mapping between different device identification data sources is described in Table 6. Since scan results provided by the Communication Server or Gateway can convey data that is produced by the device (firmware) the device type identification mapping shall be supported by providing corresponding data in the FDI Device Package contained Catalog and Information Model. Table 6 – Device identification information mapping FDI Device Package Information Model Communication Server provided scan result Gateway provided scan result Catalog specified type Manufacturer FunctionalGroup: Identification Browse Name: Manufacturer_ID Element (path): ConnectionPoint/Identification Attribute: Manufacturer_ID COLLECTION ConnectionPoint. Identification. Manufacturer_ID Catalog specified type DeviceModel FunctionalGroup: Identification Browse Name: Ident_Number Element (path): ConnectionPoint/Identification Attribute: Ident_Number COLLECTION ConnectionPoint. Identification. Ident_Number Device type revision mapping IEC 62769-4 envisions a concept that allows to determine the compatibility between an FDI Device Package and a Device. IEC 62769-4 specifies a life cycle management process bearing on a single version information provided for the entire device. NOTE PROFIBUS related specifications, for example PI Order No.: 2.122:2008 (GSD) and PI Order No.: 3.502:2009 (I&M) splits the device type revision into software and hardware related information. The GSD specifies the attributes Hardware_Release and Software_Release. The I&M specifies HARDWARE_REVISION and SOFTWARE_REVISION. Hardware_Release and HARDWARE_REVISION shall match always. Software_Release and SOFTWARE_REVISION shall match always. The goal of 5.3.2 is to describe the translation rules between PROFIBUS related specifications, describing their way of providing the version information, and the IEC 62769-4 specified way of containing the version information that can be compared against the version read from the device. The purpose is to determine the compatibility between an FDI Device Package and a Device. Figure 1 depicts the problem. Field Device Integration (FDI) – Part 103-1: Profiles – PROFIBUS RELEASED FCG TS62769-103-1, Ed. 1.2.0, 09 Jul 2019 Page 12 of 33 FDIPROFIBUS FDI specified Device revision GSD: Hardware_Release I&M: HARDWARE_REVISION GSD: Software_Release I&M: SOFTWARE_REVISION FDI Profile specifed translation Figure 1 – Version mapping problem The firmware of a device implements the data exchange interface which shall be described by means of the FDI Device Package content (EDD). A device firmware that implements the PROFIBUS PA profile enables the reading of the values SOFTWARE_REVISION and HARDWARE_REVISION. The access to these values shall be described in the EDD contained in the FDI Device Package. Firmware modifications that affect the firmware implemented data exchange interface shall be reflected in the FDI Device Package. Such firmware and device description modification shall be visible in the SOFTWARE_REVISION and Software_Release. Hardware related modifications shall be captured in the HARDWARE_REVISION and Hardware_Release. Hardware related modifications do not necessarily always require a firmware update. Thus HARDWARE_REVISION and Hardware_Release cannot be used to determine compatibility between a device and the FDI Device Package. But if a hardware modification requires firmware modifications both HARDWARE_REVISION and SOFTWARE_REVISION shall be changed. Hardware_Release and Software_Release shall be changed accordingly. The IEC 62769-4 specifies the Catalog schema and an element DeviceVersion which is used in the element type declaration ListOfSupportedDeviceVersions. The value of the DeviceVersion shall be compared to the device provided SOFTWARE_REVISION or the GSD provided Software_Release in order to determine the compatibility between an FDI Device Package and a device. The data format for the SOFTWARE_REVISION is a string while the DeviceVersion expects three numbers for major, minor, and revision. Therefore the following rules apply: If the string has the format <integer>.<integer>.<integer> this is transferred to major, minor, and revision (in the same order). <integer> references to simple integer number in the string such as ‘1’ or ‘12’, not to other representations such as hexadecimal format (e.g. 0x001A). If <integer>.<integer> is provided, this is transferred to major and minor and ‘0’ is used for revision. If only an <integer> is provided, this is transferred to major and ‘0’ is used for minor and revision. A leading character or a leading character and whitespace shall be ignored. For a string in any other format the revision number shall not be considered to select the correct FDI package. 5.4 Information Model mapping ProtocolType definition The concept to derive PROFIBUS DP and PROFIBUS PA specific Network Types applies to the protocol type definition. The protocol type Profibus_DP shall be used to identify the PROFIBUS DP communication. The type Profibus_DP is a sub type of the abstract type ProtocolType in IEC 62541-100. Table 7 specifies the allowed values of the ProtocolType attributes for the protocol type Profibus_DP. Field Device Integration (FDI) – Part 103-1: Profiles – PROFIBUS RELEASED FCG TS62769-103-1 , Ed. 1.2.0, 09 Jul 2019 Page 13 of 33 Table 7 – Protocol type Profibus_DP Attribute Value BrowseName Profibus_DP IsAbstract False References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the ProtocolType defined in IEC 62541-100. The network type Profibus_PA_Network shall be used to build PROFIBUS PA network topologies. The type Profibus_DP_Network is a sub type of the abstract type NetworkType in IEC 62541-100. Table 8 specifies the allowed values of the ProtocolType attributes for the protocol type Profibus_PA. Table 8 – Protocol type Profibus_PA Attribute Value BrowseName Profibus_PA IsAbstract False References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the ProtocolType defined in IEC 62541-100. DeviceType mapping The DeviceType property mapping of the DeviceType node is defined in Table 9. Table 9 – DeviceType property mapping Property PROFIBUS Mapping SerialNumber SERIAL_NUMBER (see Table 10) RevisionCounter REV_COUNTER (see Table 10) 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) DeviceRevision Not supported DeviceManual Not supported SoftwareRevision SOFTWARE_REVISION (see Table 10) HardwareRevision HARDWARE_REVISION (see Table 10) FunctionalGroup identification definition As defined in IEC 62541-100:–, 5.3, each device representation in the FDI Server hosted Information Model shall contain a protocol specific FunctionalGroup named Identification. The Parameters of this FunctionalGroup are defined for PROFIBUS devices types as follows: Table 10 – PROFIBUS Device Types identification attributes BrowseName DataType Mandatory/Optional Ident_Number UInt16 Mandatory MANUFACTURER_ID UInt16 Mandatory Field Device Integration (FDI) – Part 103-1: Profiles – PROFIBUS RELEASED FCG TS62769-103-1, Ed. 1.2.0, 09 Jul 2019 Page 14 of 33 BrowseName DataType Mandatory/Optional ORDER_ID String Optional SERIAL_NUMBER String Optional HARDWARE_REVISION UInt16 Optional SOFTWARE_REVISION String Optional REV_COUNTER UInt16 Optional PROFILE_ID UInt16 Optional PROFILE_SPECIFIC_TYPE UInt16 Optional IM_VERSION ByteString Optional IM_SUPPORTED UInt16 Optional The BaseDataVariable instances, except Ident_Number, shall be created from VARIABLE declarations with identifiers that correspond to the browse names listed in Table 10. The BaseDataVariable instances Ident_Number shall be created from the GSD file attribute Ident_Number. 5.5 Topology elements ConnectionPoint definition In order to support different network topology engineering needs related to different physical layers used by PROFIBUS DP and PROFIBUS PA two different ConnectionPoint types shall be defined. The ConnectionPoint type Profibus_DP shall be used to parameterize PROFIBUS DP network access points. The ConnectionPoint type Profibus_DP is a sub type of the abstract type ConnectionPointType defined in IEC 62541-100. Table 11 specifies the allowed values of the ConnectionPoint attributes for the protocol type Profibus_DP. Table 11 – ConnectionPoint type for Profibus_DP Attribute Value BrowseName ConnectionPoint_Profibus_DP IsAbstract False References NodeClass BrowseName DataType TypeDefinition ModellingRule Sub type of the ConnectionPointType defined in IEC 62541-100. HasProperty Variable Address Byte PropertyType Mandatory The ConnectionPoint type Profibus_DP shall be described by an EDD element contained in a Communication Device related FDI Package that can drive a PROFIBUS DP network. Actual ConnectionPoint properties are declared by VARIABLE constructs grouped together in a COLLECTION named ConnectionPoint. COMPONENT ConnectionPoint_Profibus_DP { LABEL "PROFIBUS DP Connection Point"; CLASSIFICATION NETWORK_CONNECTION_POINT; CAN_DELETE FALSE; PROTOCOL PROFIBUS_DP; CONNECTION_POINT ConnectionPoint; } VARIABLE Address { LABEL "Station address"; HELP "Address of the PROFIBUS slave"; Field Device Integration (FDI) – Part 103-1: Profiles – PROFIBUS RELEASED FCG TS62769-103-1 , Ed. 1.2.0, 09 Jul 2019 Page 15 of 33 TYPE UNSIGNED_INTEGER(1) { INITIAL_VALUE 126; MIN_VALUE 0; MAX_VALUE 126; } HANDLING READ & WRITE; CLASS LOCAL; } COLLECTION ConnectionPoint { LABEL "PROFIBUS DP Connection Point data"; MEMBERS { CONNECTION_POINT_ADDRESS, Address; } } The ConnectionPoint type Profibus_PA shall be used to parameterize PROFIBUS PA network access points. The ConnectionPoint type Profibus_PA is a sub type of the abstract type ConnectionPointType defined in IEC 62541-100. Table 12 specifies the allowed values of the ConnectionPoint attributes for the protocol type Profibus_PA. Table 12 – ConnectionPoint type for Profibus_PA Attribute Value BrowseName ConnectionPoint_Profibus_PA IsAbstract False References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the ConnectionPointType defined in IEC 62541-100. HasProperty Variable Address Byte PropertyType Mandatory The Property Address allowed values are 0..126. The ConnectionPoint type Profibus_PA shall be described by an EDD element contained in a Communication Device related FDI Package that can drive a PROFIBUS PA network. Actual ConnectionPoint properties are declared by VARIABLE constructs grouped together in a COLLECTION named ConnectionPoint. COMPONENT ConnectionPoint_Profibus_PA { LABEL "PROFIBUS PA Connection Point"; CLASSIFICATION NETWORK_CONNECTION_POINT; CAN_DELETE FALSE; PROTOCOL PROFIBUS_PA; } VARIABLE Address { LABEL "Station address"; HELP "Address of the PROFIBUS slave"; CLASS DEVICE; Field Device Integration (FDI) – Part 103-1: Profiles – PROFIBUS RELEASED FCG TS62769-103-1, Ed. 1.2.0, 09 Jul 2019 Page 16 of 33 TYPE UNSIGNED_INTEGER(1) { INITIAL_VALUE 126; MIN_VALUE 0; MAX_VALUE 126; } HANDLING READ & WRITE; CLASS LOCAL; } COLLECTION ConnectionPoint { LABEL "PROFIBUS PA Connection Point data"; MEMBERS { CONNECTION_POINT_ADDRESS, Address; } } Communication Device definition According to IEC 62769-7 each FDI Communication Package shall contain an EDD element describing the communication device. The following EDDL source code in is an example describing a Communication Server. COMPONENT Profibus_Communication_Server { LABEL "PROFIBUS communication server"; PRODUCT_URI "urn:PROFIBUS International:PROFIBUS Communication Server"; CAN_DELETE TRUE; CLASSIFICATION NETWORK_COMPONENT; COMPONENT_RELATIONS { Profibus_Communication_Device_Setup } } COMPONENT_RELATION Profibus_Communication_Device_Setup { LABEL "Relation between Device and communication device"; RELATION_TYPE CHILD_COMPONENT; COMPONENTS { Profibus_Communication_Device{AUTO_CREATE 1;} } MINIMUM_NUMBER 1; MAXIMUM_NUMBER 4; } According to IEC 62769-7 each FDI Communication Package shall contain at least one EDD element describing at least one communication device component. The following EDDL source code in is an example for a PROFIBUS DP communication device: COMPONENT Profibus_Communication_Device { LABEL "PROFIBUS communication device"; CAN_DELETE TRUE; CLASSIFICATION NETWORK_COMPONENT; COMPONENT_RELATIONS { Profibus_Service_Provider_Relation } BYTE_ORDER BIG_ENDIAN; } Field Device Integration (FDI) – Part 103-1: Profiles – PROFIBUS RELEASED FCG TS62769-103-1 , Ed. 1.2.0, 09 Jul 2019 Page 17 of 33 COMPONENT_RELATION Profibus_Service_Provider_Relation { LABEL "Relation to communication service provider"; RELATION_TYPE CHILD_COMPONENT; COMPONENTS { Profibus_Service_Provider{AUTO_CREATE 1;} } MINIMUM_NUMBER 1; MAXIMUM_NUMBER 1; } In an actual communication device the value “ConnectionPoint_Profibus_DP” needs to be adapted according to the supported protocol and the related connection point definitions given in 5.5. The attribute BYTE_ORDER value is to be set according to the protocol. Communication service provider definition According to IEC 62769-7 each FDI Communication Package shall contain at least one EDD element describing at least one communication service provider component. The following EDDL source code below is an example for a PROFINET IO communication service provider component: The component reference (ConnectionPoint_Profibus_DP) corresponds to the related connection point definition in 5.5. The attribute BYTE_ORDER value is to be set according to the protocol. COMPONENT Profibus_Service_Provider { LABEL "PROFIBUS communication service provider"; CAN_DELETE TRUE; CLASSIFICATION NETWORK_COMMUNICATION_SERVICE_PROVIDER; COMPONENT_RELATIONS { Profibus_Service_Provider_Connection_Point_Relation } BYTE_ORDER BIG_ENDIAN; // EDDL extension } COMPONENT_RELATION Profibus_Service_Provider_Connection_Point_Relation { LABEL "Relation between communication service provider and Connection Point"; RELATION_TYPE CHILD_COMPONENT; ADDRESSING {Address} COMPONENTS { ConnectionPoint_Profibus_DP{ AUTO_CREATE 1;} } MINIMUM_NUMBER 1; MAXIMUM_NUMBER 1; } Network definition According to IEC 62769-7 each FDI Communication Package shall contain at least one EDD element describing network configuration constraints using the component construct. COMPONENT Network_Profibus_DP { LABEL "PROFIBUS DP Network"; CAN_DELETE TRUE; Field Device Integration (FDI) – Part 103-1: Profiles – PROFIBUS RELEASED FCG TS62769-103-1, Ed. 1.2.0, 09 Jul 2019 Page 18 of 33 CLASSIFICATION NETWORK; COMPONENT_RELATIONS { Profibus_DP_Network_Connection_Point_Relation } } COMPONENT_RELATION Profibus_DP_Network_Connection_Point_Relation { LABEL "Relation between network and Connection Point"; RELATION_TYPE CHILD_COMPONENT; ADDRESSING {Address} COMPONENTS { ConnectionPoint_Profibus_DP } MINIMUM_NUMBER 1; MAXIMUM_NUMBER 32; } 5.6 Methods Methods for FDI Communication Servers 5.6.1.1 General The Communication Server contained Information Model shall implement services according to method signatures described in 5.6.1. 5.6.1.2 Connect Signature: Connect( [in] ByteString CommunicationRelationId, [in] byte Address, [out] Int32 ServiceError); Table 13 provides the description of the arguments. Table 13 – Method Connect arguments Argument Description CommunicationRelationId The argument value contains the nodeId of the ConnectionPoint representing the connection between a device and a physical network which is directly connected to the Communication Server hardware. The nodeId allows finding the direct parent-child relation. Address The argument name shall match with the corresponding attribute name defined for the ConnectionPoint which is described by a corresponding EDD element specified in 5.5. The argument value holds the device’s network address. ServiceError 0: OK / execution finished, connection established successfully -1: Connect Failed / canceled by caller -3: Connect Failed / device not found -4: Connect Failed / invalid device address -5: Connect Failed / invalid device identification Next >