< PreviousField Device Integration (FDI) – Part 101-1: Profiles – Foundation Fieldbus H1 RELEASED FCG TS62769-101-1 , Ed. 1.2.0, 09 Jul 2019 Page 29 of 31 <xsd:complexType name="TransferResultDataT"> <xsd:attribute name="DATA" type="xsd:hexBinary" use="optional"/> </xsd:complexType> The attributes of a TransferResultDataT type are described in Table 4. Table 4 – Attributes of TransferResultDataT Attribute Description DATA Data received after the service operation. This attribute is required for the GETOD and READ service operations. B.7 TransferSendDataT A complex type that defines the service parameter data format that shall be applied to Transfer defined argument sendData. The XML schema for a TransferSendDataT type is: <xsd:complexType name="TransferSendDataT"> <xsd:attribute name="OPERATION" type="ff:OperationT" use="required"/> <xsd:attribute name="OD_INDEX" type="xsd:unsignedInt" use="required"/> <xsd:attribute name="OD_SUB_INDEX" type="xsd:unsignedInt" use="required"/> <xsd:attribute name="DATA" type="xsd:hexBinary" use="optional"/> </xsd:complexType> The attributes of a TransferSendDataT type are described in Table 5. Table 5 – Attributes of TransferSendDataT Attribute Description OPERATION Data transfer operation OD_INDEX Object dictionary index relative to the Function Block application OD_SUB_INDEX To address a simple parameter a value of 0 shall be passed with this attribute. To address a specific member of a parameter of type RECORD or ARRAY a 1- relative value shall be passed with this attribute. To address the parameter of type RECORD or ARRAY as a whole a value of 0 shall be passed with this attribute DATA Mandatory attribute for data to be transferred in the service WRITE operation. This attribute is not used for the READ or GETOD service operation. Field Device Integration (FDI) – Part 101-1: Profiles – Foundation Fieldbus H1 RELEASED FCG TS62769-101-1, Ed. 1.2.0, 09 Jul 2019 Page 30 of 31 Annex C (informative) Communication service arguments for Transfer Method IEC 62769-3 details that communication service arguments for the Transfer Method (see 5.6.1.4) are obtained from COMMAND elements associated to the VARIABLE element. For variable read or write access the FDI server shall obtain the related COMMAND description and obtain the communication service arguments for the Transfer Method from the attributes of the COMMAND description via name matching. Since the CPF1 EDD profile does not provide a COMMAND EDD item this approach requires additional considerations. In order to keep the FDI Server as generic as possible the following solution is proposed. The COMMAND construct is introduced but only at a virtual level. This means there will be no means within the CPF1 EDD profile grammar to define a COMMAND item. The COMMAND item will have the following attributes: • INDEX • SUB_INDEX The COMMAND item shall be related to the PARAMETER of the block. The COMMAND item representation will be created automatically (on the fly) for each block parameter by the FDI (EDD) engine when a block is loaded by the engine. NOTE With today’s EDD services the creation of the COMMAND items for PARAMETERs can be accomplished during ddi_get_item() for the block when the list of parameters is created. For parameters of the type RECORD or ARRAY COMMAND DD items shall be created for each member of the RECORD or ARRAY. This is to ease operation for the FDI Server. When the EDD is loaded by the FDI Server the BlockTypes are created within the SupportedTypes Folder in the Blocks component of the DeviceType (see IEC 62769-5 and IEC 62541-100). For each parameter of the BlockType the COMMAND description is provided by the FDI (EDD) engine. Block instances are created with the result of the Scan Method as described in 5.6.1.7. Block instances are created as (child) components of the Blocks component. According to IEC 62769-5, the DisplayName of the Block instance is the BlockTag. For variable read or write access the FDI Server shall obtain the communication service arguments INDEX and SUB_INDEX from the COMMAND description of the parameter via name matching. For the communication service argument BlockTag the DisplayName of the block instance shall be used. Field Device Integration (FDI) – Part 101-1: Profiles – Foundation Fieldbus H1 RELEASED FCG TS62769-101-1 , Ed. 1.2.0, 09 Jul 2019 Page 31 of 31 Bibliography IEC 62769-3:– 2 , Field Device Integration (FDI) – Part 3: FDI Server NOTE IEC 62769-3 is technically identical to FDI-2023 FIELDBUS FOUNDATION. F OUNDATION Specification Common File Format. FF-103, Version 1.9. 4 June 2010. FIELDBUS FOUNDATION. F OUNDATION Specification Function Block Application Process – Part 1. FF-890, Version 1.10. 2 Aug. 2012. FIELDBUS FOUNDATION. F OUNDATION Specification Function Block Application Process – Part 2. FF-891, Version 1.10. 2 Aug. 2012. FIELDBUS FOUNDATION. FF-880: F OUNDATION Specification System Management. FF-980, Version 1.6. 1 Dec. 2005. _____________ 2 Under consideration. Next >