< PreviousField Device Integration (FDI) – Part 101-2: Profiles – Foundation Fieldbus HSE RELEASED FCG TS62769-101-2 , Ed. 1.2.0, 09 Jul 2019 Page 19 of 27 Signature SetAddress( [in] String OPERATION, [in] ByteString Address, [in] String NewPDTag, [in] UInt32 ServiceId, [out] UInt32 DelayForNextCall, [out] Int32 ServiceError); Table 14 – Method SetAddress arguments Argument Description OPERATION a The argument value indicates the type of addressing operation. Allowed values are “SETASSIGNMENT”, “CLEARASSIGNMENT”. The argument values given with the arguments below may be ignored depending on the value of the OPERATION argument. 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.1. The argument value holds the device’s IPv4 or IPv6 address. NewPDTag b The argument value holds the new PD-Tag to set for the device. The argument value is ignored if the OPERATION argument value is “CLEARASSIGNMENT”. ServiceId The service transaction code establishes the relation between the service request and the corresponding response. ServiceError 0: OK / execution finished successfully -1: SetAddress Failed / canceled by caller -2: Call Failed / unknown service ID -3: SetAddress Failed / not initialized -4: SetAddress Failed / not connected to a network -5: SetAddress Failed / no device found responding to oldAddress -6: SetAddress Failed / duplicate address error -7: SetAddress Failed / device did not accept new address -8: SetAddress Failed / invalid oldAddress (in terms of syntax, data type, data format, and so on) -9: SetAddress Failed / invalid newAddress (in terms of syntax, data type, data format, and so on) -10: SetAddress Failed / not possible in status connected a The arguments OPERATION defined with the table are represented as entries of the Variant array in the order they are specified above. b The arguments NewPDTag defined with the table are represented as entries of the Variant array in the order they are specified above. 5.6.1.7 Scan The Method signature specified in IEC 62769-7 applies. The corresponding topologyScanResult schema is specified in Annex A. 5.6.1.8 ResetScan The Method signature specified in IEC 62769-7 applies. Field Device Integration (FDI) – Part 101-2: Profiles – Foundation Fieldbus HSE RELEASED FCG TS62769-101-2, Ed. 1.2.0, 09 Jul 2019 Page 20 of 27 Methods for Gateways Not supported. Field Device Integration (FDI) – Part 101-2: Profiles – Foundation Fieldbus HSE RELEASED FCG TS62769-101-2 , Ed. 1.2.0, 09 Jul 2019 Page 21 of 27 Annex A (normative) Topology scan schema A.1 General The topology scan result schema specified in Annex A describes the CP 1/2 specific format Method Scan argument topologyScanResult . The XML document content and structure shall correspond to the Information Model designed concept to describe a topology in order to enable generic matching between physical devices connected to the network and the FDI Server hosted Information Model. A.2 Network The root element that is used to return the scan result of a CP 1/2 network. The XML schema for a Network element is: <xsd:element name="Network" type="ff:FoundationHSENetworkT"/> A.3 FoundationHSEAddressT A simple type that defines the address structure for CP 1/2. The address can be encoded as IPv4 or IPv6. The XML schema for a FoundationHSEAddressT type is: <xsd:simpleType name="FoundationHSEAddressT"> <xsd:restriction base="xsd:string"/> </xsd:simpleType> A.4 FoundationHSEConnectionPointT A complex type that defines the Connection Point for CP 1/2. The XML schema for a FoundationHSEConnectionPointT type is: <xsd:complexType name="FoundationHSEConnectionPointT"> <xsd:sequence> <xsd:element name="Identification" type="ff:FoundationIdentificationT"/> <xsd:element name="BlockScanInstance" type="ff:FoundationBlockIdentificationT" minOccurs="0" maxOccurs="unbounded"/> </xsd:sequence> <xsd:attribute name="Address" type="ff:FoundationHSEAddressT" use="required"/> <xsd:attribute name="OrdinalNumber" type="xsd:unsignedInt" use="required"/> </xsd:complexType> The attributes of a FoundationHSEConnectionPointT type are described in Table A.1. Field Device Integration (FDI) – Part 101-2: Profiles – Foundation Fieldbus HSE RELEASED FCG TS62769-101-2, Ed. 1.2.0, 09 Jul 2019 Page 22 of 27 Table A.1 – Attributes of FoundationHSEConnectionPointT Attribute Description Address The Attribute value holds the address of the network connected device. OrdinalNumber The OrdinalNumber property reflects the position of the VFD within the System Management VFD list. Multiple VFDs are mapped to multiple ScanItem elements. The elements of a FoundationHSEConnectionPointT type are described in Table A.2. Table A.2 – Elements of FoundationHSEConnectionPointT Element Description Identification The element data holds the device type identification data. Compared to the Information Model (IEC 62769-5) the ConnectionPoint does not contain or refer to the device type identification data. But in order to support the FDI host system in finding the package that matches the connected device this schema associates the device type identification with the ConnectionPoint. BlockScanInstance Block instance information of the scanned device VFD. Used to create Block instances within the FDI Server IM. See IEC 62769-5. A.5 FoundationHSENetworkT A complex type that defines the network for CP 1/2. The XML schema for a FoundationHSENetworkT type is: <xsd:complexType name="FoundationHSENetworkT"> <xsd:sequence> <xsd:element name="ConnectionPoint" type="ff:FoundationHSEConnectionPointT" maxOccurs="unbounded"/> </xsd:sequence> </xsd:complexType> The elements of a FoundationHSENetworkT type are described in Table A.3. Table A.3 – Elements of FoundationHSENetworkT Element Description ConnectionPoint CP 1/2 Connection Point. A.6 FoundationBlockIdentificationT A complex type that defines the block instance information of the scanned device. The XML schema for a FoundationBlockIdentificationT type is: <xsd:complexType name="FoundationBlockIdentificationT"> <xsd:attribute name="BlockTag" use="required"/> <xsd:attribute name="DDItem" use="required"/> <xsd:attribute name="DirectoryPosition" use="required"/> </xsd:complexType> Field Device Integration (FDI) – Part 101-2: Profiles – Foundation Fieldbus HSE RELEASED FCG TS62769-101-2 , Ed. 1.2.0, 09 Jul 2019 Page 23 of 27 The attributes of a FoundationBlockIdentificationT type are described in Table A.4. Table A.4 – Attributes of FoundationBlockIdentificationT Attribute Description BlockTag The BlockTag attribute shall be mapped to the DisplayName of a block instance to be created within the FDI Server IM. DDItem This attribute is used to find the correct block type of a block instance to be created within the FDI Server IM. The block type is looked up within the SupportedTypes Folder in the Blocks component of a DeviceType. DirectoryPosition This attribute denotes the relative position of the block instance within the Directory object. The first block instance has a value of 0. See block instantiation rules in IEC 62769-5. A.7 FoundationIdentificationT A complex type that defines the content corresponding to the FunctionalGroup Identification. The XML schema for a FoundationIdentificationT type is: <xsd:complexType name="FoundationIdentificationT"> <xsd:attribute name="MANUFAC_ID" type="xsd:unsignedInt" use="required"/> <xsd:attribute name="DEV_TYPE" type="xsd:unsignedShort" use="required"/> <xsd:attribute name="DEV_REV" type="xsd:unsignedShort" use="optional"/> <xsd:attribute name="ITK_VER" type="xsd:unsignedShort" use="optional"/> <xsd:attribute name="HARDWARE_REV" type="xsd:string" use="optional"/> <xsd:attribute name="SOFTWARE_REV" type="xsd:string" use="optional"/> <xsd:attribute name="COMPATIBILITY_REV" type="xsd:unsignedInt" use="optional"/> <xsd:attribute name="CAPABILITY_LEV" type="xsd:unsignedByte" use="optional"/> <xsd:attribute name="SIF_ITK_VER" type="xsd:unsignedShort" use="optional"/> <xsd:attribute name="FD_VER" type="xsd:unsignedShort" use="optional"/> </xsd:complexType> The attributes of a FoundationIdentificationT type are described in Table A.5. Table A.5 – Attributes of FoundationIdentificationT Attribute Description MANUFAC_ID Manufacturer identification number. DEV_TYPE Manufacturer model number associated with the resource. DEV_REV Manufacturer revision number associated with the resource. Conditional: Shall be available if the device exposes a Function block VFD. ITK_VER ITK Profile Number. Conditional: Shall be available if the device exposes a Function block VFD. HARDWARE_REV Manufacturer hardware revision. SOFTWARE_REV Manufacturer software revision. COMPATIBILITY_REV This parameter is optionally used when replacing field devices. The correct usage of this parameter presumes the COMPATIBILITY_REV value of the replacing device should be equal to or lower than the DEV_REV value of the replaced device. Field Device Integration (FDI) – Part 101-2: Profiles – Foundation Fieldbus HSE RELEASED FCG TS62769-101-2, Ed. 1.2.0, 09 Jul 2019 Page 24 of 27 Attribute Description CAPABILITY_LEV This parameter may be included in a device to indicate the capability level supported by a device. SIF_ITK_VER SIF ITK Profile Number. FD_VER A parameter equal to the value of the major version of the Field Diagnostics specification that this device was designed to. Field Device Integration (FDI) – Part 101-2: Profiles – Foundation Fieldbus HSE RELEASED FCG TS62769-101-2 , Ed. 1.2.0, 09 Jul 2019 Page 25 of 27 Annex B (normative) Transfer service parameters Direct Access Services specified in IEC 62769-2 enable the User Interface Plug-in (UIP) to directly exchange data with the device. Direct data exchange means that data exchanged between a device and a UIP may not be reflected in the Information Model. IEC 62769-6 defined interface IDirectAccess corresponds to IEC 62769-2 specified Direct Access Services. Interface IDirectAccess defined functions BeginTransfer and EndTransfer need to convey protocol specific information. The protocol specifics shall be captured in an XML document. The schema for CP 1/2 is identical to CP 1/1 and is specified in IEC 62769-101-1. Field Device Integration (FDI) – Part 101-2: Profiles – Foundation Fieldbus HSE RELEASED FCG TS62769-101-2, Ed. 1.2.0, 09 Jul 2019 Page 26 of 27 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 EDD 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-2: Profiles – Foundation Fieldbus HSE RELEASED FCG TS62769-101-2 , Ed. 1.2.0, 09 Jul 2019 Page 27 of 27 Bibliography 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. _____________ Next >