ISA 62453-306-2011 Field device tool (FDT) interface specification C Part 306 Communication profile integration C IEC 61784 CPF 6 (103 00 07).pdf

《ISA 62453-306-2011 Field device tool (FDT) interface specification C Part 306 Communication profile integration C IEC 61784 CPF 6 (103 00 07).pdf》由会员分享，可在线阅读，更多相关《ISA 62453-306-2011 Field device tool (FDT) interface specification C Part 306 Communication profile integration C IEC 61784 CPF 6 (103 00 07).pdf（36页珍藏版）》请在麦多课文档分享上搜索。

1、 AMERICAN NATIONAL STANDARD ANSI/ISA62453-306 (103.00.07)-2011 Field device tool (FDT) interface specification Part 306: Communication profile integration IEC 61784 CPF 6 Approved 31 May 2011 ANSI/ISA62453-306 (103.00.07)-2011, FIELD DEVICE TOOL (FDT) INTERFACE SPECIFICATION Part 306: Communication

2、profile integration IEC 61784 CPF 6 ISBN: 978-0-876640-61-6 Copyright 2011 IEC and ISA. These materials are subject to copyright claims of IEC and ISA. No part of this publication may be reproduced in any form, including an electronic retrieval system, without the prior written permission of ISA. Al

3、l requests pertaining to the ANSI/ISA62453-306 (103.00.07)-2011 Standard should be submitted to ISA. ISA 67 Alexander Drive P.O. Box 12277 Research Triangle Park, North Carolina 27709 ANSI/ISA62453-306 (103.00.07)2011 - 3 - Preface This preface, as well as all footnotes and annexes, is included for

4、information purposes and is not part of ANSI/ISA62453-306 (103.00.07)2011. This document has been prepared as part of the service of ISA toward a goal of uniformity in the field of instrumentation. To be of real value, this document should not be static but should be subject to periodic review. Towa

5、rd this end, the Society welcomes all comm ents and criticisms and asks that they be addressed to the Secretary, Standards and Practices Board; ISA; 67 Alexander Drive; P. O. Box 12277; Research Triangle Park, NC 27709; Telephone (919) 549 -8411; Fax (919) 549-8288; E-mail: standardsisa.org. The ISA

6、 Standards and Practices Department is aware of the growing need for attention to the metric system of units in general, and the International System of Units (SI) in particular, in the preparation of instrumentation standards. The Department is further aware of the benefits to USA users of ISA stan

7、dards of incorporating suitable references to the SI (and the metric system) in their business and professional dealings with other countries. Toward this end, this Department will endeavor to introduce SI-acceptable metric units in all new and revised standards, recommended practices, and technical

8、 reports to the greatest extent possible. Standard for Use of the International System of Units (SI): The Modern Metric System, published by the American Society for Testing NetworkManagementInfoWrite service. The data types describe the address information of an IEC 61784 CPF 6 device (see Table 4

9、and Table 5) Table 4 Simple parameter access data types Data type Definition Description systemNumber USINT System number of the address information according to the IEC 61784 CPF 6 specification segmentNumber USINT Segment number of the address information according to the IEC 61784 CPF 6 specifica

10、tion positionNumber USINT Position number of the address information according to the IEC 61784 CPF 6 specification Table 5 Structured parameter access data types Data type Definition Description Elementary data types Usage Multiplicity Address STRUCT The address information of an IEC 61784 CPF 6 de

11、vice. systemNumber M 11 segmentNumber M 11 positionNumber M 11 9.2 Parameter for boot sequence After the Offline-Parameterization the parameter should be exported via the IDtmParameter Interface. Then a Communication DTM can collect the data, configure the cyclic communication of the IEC 61784 CPF 6

12、 network and generate a boot sequence, where the parameter will be written to the physical devices. All boot parameters shall be included in a DTMVariables list named “BOOT_PARAMS”. The boot parameter will be written subsequently to the devices. 10 Communication data types The data types described i

13、n this clause are used in the following services: connect service; disconnect service; transaction service. The service arguments contain the address information and the communication data (explained in Table 6 and Table 7).The data types described in this clause are defined for the following namesp

14、ace. ANSI/ISA62453-306 (103.00.07)2011 - 16 - Namespace: fdtinterbus Table 6 Simple communication data types Data type Definition Description systemNumber USINT System number of the address information according to the IEC 61784 CPF 6 specification segmentNumber USINT Segment number of the address i

15、nformation according to the IEC 61784 CPF 6 specification positionNumber USINT Position number of the address information according to the IEC 61784 CPF 6 specification errorCode ARRAY OF USINT Contains information why a service could not be successfully executed index UINT Address information accor

16、ding to the IEC 61784 CPF 6 specification subIndex USINT Address information according to the IEC 61784 CPF 6 specification communicationReference UUID Mandatory identifier for a communication link to a device This identifier is allocated by the communication component during the connect. The addres

17、s information shall be used for all following communication calls NOTE This is not the communication reference of the PMS. invokeId USINT Job number for parallel services according to the IEC 61784 CPF 6 specification reasonCode USINT Cause for a connection abort abortDetail ARRAY OF USINT Additiona

18、l information for a connection abort password USINT Password for the communication relationship to access device objects accessGroup USINT Manufacturer specific assignment of the controller board to an access group for which an access authorization for device objects is specified versionOD UINT Vers

19、ion number of the object directory profile UINT Identification of the device profile protection USINT Indicates whether the access rights are checked when accessing device objects manufacturerName STRING Manufacturer name of the device deviceName STRING The name of the device revision STRING The rev

20、ision number of the device sequenceTime UDINT Period of time in ms for the whole sequence delayTime UDINT Delay time in ms between two communication calls schemaVersion INT Defines the version of the schema systemTag STRING System Tag of a DTM. It is strongly recommended to provide the attribute in

21、the Request document ANSI/ISA62453-306 (103.00.07)2011 - 17 - Table 7 Structured communication data types Data type Definition Description Elementary data types Usage Multiplicity Abort STRUCT Describes the abort communicationReference M 11 reasonCode M 11 abortDetail M 11 ConnectRequest STRUCT Desc

22、ribes the communication request to establish a connection to an IEC 61784 CPF 6 PCP device fdt:nodeId O 01 systemNumber M 11 segmentNumber M 11 postionNumber M 11 password M 11 accessGroup M 11 fdt:systemTag O 01 ConnectResponse STRUCT Describes the communication response to the ConnectRequest fdt:n

23、odeId O 01 systemNumber M 11 segmentNumber M 11 postionNumber M 11 versionOD M 11 profile M 11 protection M 11 communicationReference M 11 errorCode M 11 ReadRequest STRUCT Describes the communication request to read device objects fdt:nodeId O 01 invokeId M 11 index M 11 subIndex M 11 communication

24、Reference M 11 ANSI/ISA62453-306 (103.00.07)2011 - 18 - Data type Definition Description Elementary data types Usage Multiplicity ReadResponse STRUCT Describes the communication response to the ReadRequest fdt:nodeId O 01 communicationReference M 11 errorCode M 11 fdt:CommunicationDate M 11 Disconne

25、ctRequest STRUCT Describes the communication request to release a connection to an IEC 61784 CPF 6 PCP device (Abort_Request) fdt:nodeId O 01 reasonCode M 11 abortDetail M 11 communicationReference M 11 DisconnectResponse STRUCT Describes the corresponding response to a DisconnectRequest fdt:nodeId

26、O 01 communicationReference M 11 errorCode M 11 WriteRequest STRUCT Describes the communication request to write device objects fdt:nodeId O 01 invokeId M 11 index M 11 subIndex M 11 communicationReference M 11 fdt:CommunicationDate M 11 WriteResponse STRUCT Describes the communication response to t

27、he WriteRequest fdt:nodeId O 01 communicationReference M 11 errorCode M 11 IdentifyRequest STRUCT Describes the communication request to identify the device fdt:nodeId O 01 invokeId M 11 communicationReference M 11 IdentifyResponse STRUCT Describes the communication response to the IdentifyRequest f

28、dt:nodeId O 01 ANSI/ISA62453-306 (103.00.07)2011 - 19 - Data type Definition Description Elementary data types Usage Multiplicity communicationReference M 11 manufacturerName M 11 deviceName M 11 revision M 11 errorCode M 11 SequenceBegin STRUCT Describes the sequence begin sequenceTime O 01 delayTi

29、me O 01 communicationReference M 11 SequenceEnd STRUCT Describes the sequence end communicationReference M 11 SequenceStart STRUCT Describes the sequence start communicationReference M 11 11 Channel parameter data types It is up to a DTM whether it provides any channels. If a DTM allows a Frame Appl

30、ication, other DTMs, or a controller the direct access to its process values via IEC 61784 CPF 6 protocol, it should provide FDT-Channel objects as described in this clause. Only the complete description of all channels belonging to an IEC 61784 CPF 6 process value allows proper access for external

31、applications. The description of channels, especially of the process values, allows the Frame Application to support the device in a more efficient way. The data types are used at GetChannelParameters service and SetChannelParameters services. The information returned by the GetChannelParameters ser

32、vice describes how to access an I/O value via IEC 61784 CPF 6 protocol (see Table 8 and Table 9). The data types described in this clause are defined for the following namespace. Namespace: ibschannel ANSI/ISA62453-306 (103.00.07)2011 - 20 - Table 8 Simple channel parameter data types Data type Defi

33、nition Description index UINT Address information according to the IEC 61784 CPF 6 specification for channels accessible via PCP subIndex USINT Address information according to the IEC 61784 CPF 6 specification for channels accessible via PCP invokeId USINT Job number for parallel services bitLength

34、 UDINT Additional data type information especially for fieldbus specific data types like 12 bit integer bitPosition UDINT Address information for channels accessible via IEC 61784 CPF 6 frameApplicationTag STRING Frame Application specific tag used for identification and navigation. The DTM should d

35、isplay this tag at channel specific user interfaces gatewayBusCategory UUID Unique identifier for a supported bus type like IEC 61784 CPF 6 according to the FDT specific CATID invalidBit UDINT Bit position of the invalid status channel accessible via IEC 61784 CPF 6 logic enumeration ( positive | ne

36、gative ) Additional data type information: positive negative simulationBit UDINT Bit position of the simulation status channel accessible via IEC 61784 CPF 6 protectedByChannelAssignment BOOL TRUE if the channel is set to read only by the Frame Application. Usually set to TRUE if a channel assignmen

37、t exists schemaVersion INT Defines the version of the schema statusChannel BOOL TRUE if the channel is for status information only. substituteValueBit UDINT Bit position of the substitute channel accessible via IEC 61784 CPF 6 Table 9 Structured channel parameter data types Data type Definition Desc

38、ription Elementary data types Usage Multiplicity ProcessAddress STRUCT Address information for channels accessible via IEC 61784 CPF 6 fdt:nodeId O 01 bitPosition M 11 bitLenghtth M 11 PcpAddress STRUCT Address information for channels accessible via IEC 61784 CPF 6 PCP fdt:nodeId O 01 ANSI/ISA62453

39、-306 (103.00.07)2011 - 21 - Data type Definition Description Elementary data types Usage Multiplicity invokeId M 11 index M 11 subIndex M 11 bitPosition O 01 bitLength O 01 StatusInformation STRUCT Description of additional status information for channels accessible via IEC 61784 CPF 6 fdt:nodeId O

40、01 logic M 11 invalidBit O 01 simulationBit O 01 substituteBaluBit O 01 FDTChannel STRUCT Description of the channel fdt:nodeId O 01 fdt:tag M 11 fdt:id M 11 fdt:descriptor O 01 protectedByChannel-Assignment M 11 fdt:dataType M 11 fdt:signalType M 11 frameApplicationTag O 01 appId:applicationId O 01

41、 fdt:SemanticInformation O 0* fdt:BitEnumeratorEntries O 01 fdt:EnumeratorEntries O 01 fdt:Unit O 01 ProcessAddress O 01 PcpAddress O 01 StatusInformation O 0.1 fdt:Alarms O 01 fdt:Ranges O 01 fdt:Deadband O 01 fdt:SubstituteValue O 01 ANSI/ISA62453-306 (103.00.07)2011 - 22 - Data type Definition De

42、scription Elementary data types Usage Multiplicity FDTChannelType STRUCT Description of the channel component in case of channels with gateway functionality fdt:nodeId O 01 fdt:VersionInformation M 11 gatewayBusCategory O 01 statusChannel O 01 12 Device identification There are different IEC 61784 C

43、PF 6 specific identification elements. An IEC 61784 CPF 6 scan may detect different device types: IEC 61784 CPF 6 devices following the base profile, IEC 61784 CPF 6 PCP devices and simple IEC 61784 CPF 6 devices. The following rule shall be applied for IEC 61784 CPF 6 Communication Channels: if an

44、IEC 61784 CPF 6 base profile is available, create an IEC 61784 CPF 6 base profile identification; otherwise check IEC 61784 CPF 6 PCP; otherwise create a simple IEC 61784 CPF 6 device identification. 12.1 Protocol specific handling of data type STRING IEC 61784 CPF 6 char array rules In all strings

45、based on char ranges defined in the field bus protocol specification, the leading spaces are left trimmed. The char array is to be filled with 0x20h (blank). In VisibleStrings, invisible characters provided by a device have to be replaced by ?. Characters within VisibleStrings, which are not defined

46、 in the 7 bit ASCII/ANSI character set, are considered to be invisible. 12.2 Device type identification data types The IEC 61784 CPF 6 device type identification data types provide general data types with a protocol specific semantic (see Table 10, Table 11 and Table 12) as well as data types withou

47、t such a mapping (see Table 13). The data types described in this clause are defined for the following namespace. Namespace: ibsident ANSI/ISA62453-306 (103.00.07)2011 - 23 - 62453-306IEC:2009(E) - 23 - Table 10 Identification data types for simple IEC 61784 CPF 6 device IEC 61784 CPF 6 Attribute Se

48、mantic element name Data request in physical device Protocol specific name IEC 61784 CPF 6 Data Format FDT data type (display Format) Specification reference busProtocol IdBusProtocol For all non-IEC 61784 CPF 6 PCP device: “protocol_IBS” enumeration(protocol_IBS | protocol_IBS_PCP | protocol_IBS_BASE_PROFILE) systemNumber IdAddress Logical addressing information in Nested IEC 61784 CPF 6 Systems System Number Unsigned8 STRING (systemNumber. segmentNumber. positionNumber) segmentNumber Data from IEC 61784 CPF 6 Configuration Frame Segment Number Unsigned8 positionNumber Position Number Unsign