< PreviousField Device Integration (FDI) – Part 103-4: Profiles – PROFINET RELEASED FCG TS62769-103-4 , Ed. 1.2.0, 09 Jul 2019 Page 29 of 33 </xs:complexType> The attributes of a ProfinetConnectionPointT type are described in Table A.2. Table A.2 – Attributes of ProfinetConnectionPointT Attribute Description MAC The attribute value holds the devices MAC address. IPv4 The attribute value holds the IP/V4 address. DNSname The attribute holds the station name formatted after the "Domain Name System" (DNS). SubnetMask The attribute value holds the IP/V4 subnet mask. Gateway The attribute value holds the IP/V4 address of the gateway. The elements of a ProfinetConnectionPointT type are described in Table A.3. Table A.3 – Elements of ProfinetConnectionPointT Element Description Identification The Identification element holds the device type identification information of the network connected device that has been found during bus scan operations. A.5 ProfinetIdentificationT This type declaration corresponds partially to the "FunctionalGroup Identification". The XML schema for a ProfinetIdentificationT type is: <xs:complexType name="ProfinetIdentificationT"> <xs:attribute name="VendorID" type="PI:Hex4DigitT" use="required"/> <xs:attribute name="DeviceID" type="PI:Hex4DigitT" use="required"/> </xs:complexType> The attributes of a ProfinetIdentificationT type are described in Table A.4. Table A.4 – Attributes of ProfinetIdentificationT Attribute Description VendorID The attribute value contains the vendor specific part of the device identification number (DeviceIdentNumber) as defined in IEC 61158-5-10. The attribute corresponds to the GSDML defined attribute "VendorID". DeviceID The attribute value contains the device specific part of the device identification number (DeviceIdentNumber). The attribute corresponds to the GSDML defined attribute "DeviceID". A.6 MACT The XML schema for a MACT type is: <xs:simpleType name="MACT"> <xs:restriction base="xs:string"> Field Device Integration (FDI) – Part 103-4: Profiles – PROFINET RELEASED FCG TS62769-103-4, Ed. 1.2.0, 09 Jul 2019 Page 30 of 33 <xs:pattern value="([0-9a-fA-F][0-9a-fA-F]:){5}([0-9a-fA-F][0-9a-fA- F])"/> </xs:restriction> </xs:simpleType> A.7 IPv4T The XML schema for an IPv4T type is: <xs:simpleType name="IPv4T"> <xs:restriction base="xs:string"> <xs:pattern value="((25[0-5]|2[0-4][0-9]|[01]?[0-9]?[0-9])\.){3}(25[0- 5]|2[0-4][0-9]|[01]?[0-9]?[0-9])"/> </xs:restriction> </xs:simpleType> A.8 IPv6T The XML schema for an IPv6T type is: <xs:simpleType name="IPv6T"> <xs:restriction base="xs:string"> <xs:pattern value="(([A-Fa-f0-9]{1,4}:){7}[A-Fa-f0-9]{1,4})"/> </xs:restriction> </xs:simpleType> A.9 DNSNameT The XML schema for a DNSNameT type is: <xs:simpleType name="DNSNameT"> <xs:restriction base="xs:string"> <xs:pattern value="[0-9a-zA-Z]([0-9a-zA-Z\-]{0,61}[0-9a-zA-Z])?(\.[0-9a-zA- Z]([0-9a-zA-Z\-]{0,61}[0-9a-zA-Z])?)*"/> </xs:restriction> </xs:simpleType> A.10 Hex4DigitT The XML schema for a Hex4DigitT type is: <xs:simpleType name="Hex4DigitT"> <xs:restriction base="xs:string"> <xs:pattern value="[0][x][0-9a-fA-F]{1,4}"/> </xs:restriction> </xs:simpleType> Field Device Integration (FDI) – Part 103-4: Profiles – PROFINET RELEASED FCG TS62769-103-4 , Ed. 1.2.0, 09 Jul 2019 Page 31 of 33 Annex B (normative) Transfer service parameters B.1 General 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 is not reflected in the Information Model. The IEC 62769-6 defined interface IDirectAccess corresponds to the 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 following specifies the XML document schema. B.2 sendData The element described in the following contains data to be submitted through the IDirectAccess function BeginTransfer defined argument sendData. The XML schema for a sendData element is: <xs:element name="sendData" type="PI:TransferSendDataT"/> B.3 receiveData The element described in the following contains data that is returned through the IDirectAccess function EndTransfer defined return value. The XML schema for a receiveData element is: <xs:element name="receiveData" type="PI:TransferResultDataT"/> B.4 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: <xs:complexType name="TransferSendDataT"> <xs:attribute name="OPERATION" type="PI:OperationT" use="required"/> <xs:attribute name="SLOT" type="xs:unsignedShort" use="required"/> <xs:attribute name="SUBSLOT" type="xs:unsignedShort" use="required"/> <xs:attribute name="INDEX" type="xs:unsignedShort" use="required"/> <xs:attribute name="API" type="xs:unsignedInt" use="required"/> <xs:attribute name="REQUEST" type="xs:hexBinary" use="required"/> </xs:complexType> The attributes of a TransferSendDataT type are described in Table B.1. Field Device Integration (FDI) – Part 103-4: Profiles – PROFINET RELEASED FCG TS62769-103-4, Ed. 1.2.0, 09 Jul 2019 Page 32 of 33 Table B.1– Attributes of TransferSendDataT Attribute Description OPERATION The attribute corresponds to the Transfer method argument OPERATION. SLOT The attribute corresponds to the Transfer method argument SLOT. SUBSLOT The attribute corresponds to the Transfer method argument SUBSLOT. INDEX The attribute corresponds to the Transfer method argument INDEX. API The attribute corresponds to the Transfer method argument API. REQUEST The attribute corresponds to the Transfer method argument REQUEST. B.5 TransferResultDataT A complex type that defines the service parameter data format that shall be applied to Transfer defined receivedData return value. The XML schema for a TransferResultDataT type is: <xs:complexType name="TransferResultDataT"> <xs:attribute name="REPLY" type="xs:hexBinary" use="required"/> <xs:attribute name="RESPONSE_CODES" type="xs:hexBinary" use="required"/> </xs:complexType> The attributes of a TransferResultDataT type are described in Table B.2. Table B.2– Attributes of TransferResultDataT Attribute Description REPLY The attribute corresponds to the Transfer method argument REPLY. RESPONSE_CODES The attribute corresponds to the Transfer method argument RESPONSE_CODES. B.6 OperationT A simple type that defines possible service operations. The XML schema for an OperationT enumeration type is: <xs:simpleType name="OperationT"> <xs:restriction base="xs:string"> <xs:enumeration value="READ"/> <xs:enumeration value="WRITE"/> </xs:restriction> </xs:simpleType> Field Device Integration (FDI) – Part 103-4: Profiles – PROFINET RELEASED FCG TS62769-103-4 , Ed. 1.2.0, 09 Jul 2019 Page 33 of 33 Bibliography IEC 61784-1 2 , Industrial communication networks – Profiles – Part 1: Fieldbus Profiles IEC 61804-4 3 , Function blocks (FB) for process control and Electronic Device Description Language (EDDL) – Part 4: EDD interpretation ISO/IEC 11578, Information technology - Open Systems Interconnection - Remote Procedure Call (RPC) IEEE Std 802.3, IEEE Standard for Ethernet PI Order No.: 3.502:2009, Profile Guidelines Part 1: Identification & Maintenance Functions, available at <www.PROFIBUS.com> PI Order No.: 2.352:2011, GSDML Specification for PROFINET IO, available at <www.PROFIBUS.com> PI Order No.: 3.502:2009, Profile Guidelines – Part 1: Identification & Maintenance Function, available at <www.PROFIBUS.com>RFC 791: Internet Protocol, available at <www.rfc-editor.org> RFC 1035: Domain names – implementation and specification, available at <www.rfc-editor.org> RFC 1123: Requirements for Internet Hosts – Application and Support, available at <www.rfc-editor.org> RFC 2181: Clarifications to the DNS Specification, available at <www.rfc-editor.org> ___________ 2 To be published. 3 Under consideration. Next >