ANSI ISA 62453-309-2011 Field device tool (FDT) interface specification C Part 309 Communication profile integration C IEC 61784 CPF 9 (103.00.08)《现场设备工具(FDT)接口规范.第309部分 通信子协议集成.IE.pdf

1、 AMERICAN NATIONAL STANDARD ANSI/ISA62453-309 (103.00.08)-2011 Field device tool (FDT) interface specification Part 309: Communication profile integration IEC 61784 CPF 9 Approved 31 May 2011 ANSI/ISA62453-309 (103.00.08)-2011, Field device tool (FDT) interface specification Part 309: Communication

2、profile integration IEC 61784 CPF 9 ISBN: 978-0-876640-62-3 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-309 (103.00.08)-2011 Standard should be submitted to ISA. ISA 67 Alexander Drive P.O. Box 12277 Research Triangle Park, North Carolina 27709 ANSI/ISA-62453-309 (103.00.08)-2011 - 3 - Preface This preface, as well as all footnotes and annexes, is included fo

4、r information purposes and is not part of ANSI/ISA62453-309 (103.00.08)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. To

5、ward this end, the Society welcomes all comments 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 IS

6、A 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 sta

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

8、al reports to the greatest extent possible. Standard for Use of the International System of Units (SI): The Modern Metr ic System, published by the American Society for Testing NetworkManagementInfoWrite service. The data type net:DeviceAddress (defined in IEC ISA-62453-2 103.00.02) is used for defi

9、ning the network address of a device. 10 Communication data types The data types described in 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

10、 3 and Table 4. The data types described in this clause are defined for the following namespace. Namespace: fdthart Table 3 Simple communication data types Data type Definition Description address1 USINT Address information according to the IEC 61784 CPF 9 specification ANSI/ISA-62453-309 (103.00.08

11、)-2011 - 16 - Data type Definition Description address2 USINT Address information according to the IEC 61784 CPF 9 specification address3 USINT Address information according to the IEC 61784 CPF 9 specification burstFrame BOOL Information whether the IEC 61784 CPF 9 response is a burst frame (messag

12、e or not burstModeDetected BOOL Indicates whether the Communication Channel has detected that the device is already in burst mode. This is detected during a subscription request commandNumber USINT Address information according to the IEC 61784 CPF 9 specification communicationReference UUID Mandato

13、ry identifier for a communication link to a device This identifier is allocated by the communication component during the connect. The address information has to be used for all following communication calls delayTime UDINT Minimum delay time in ms between two communication calls deviceStatus USINT

14、Status information. This is the second status byte returned in command responses according to the IEC 61784 CPF 9 specification deviceTypeId USINT Address information according to the IEC 61784 CPF 9 specification longFrameRequired BOOL Address information according to the IEC 61784 CPF 9 specificat

15、ion manufacturerId USINT Address information according to the IEC 61784 CPF 9 specification (Table: VIII, MANUFACTURER IDENTIFICATION CODES) preambleCount USINT At the connect request the attribute is optional and contains a hint for the communication component about the number of preambles, require

16、d by the device type. At the connect response the attribute is mandatory and contains the information about the currently used preambleCount primaryMaster BOOL At the connect request the attribute is optional and contains a hint for a communication component that a DTM requires communication as prim

17、ary or secondary master. At the connect response the attribute is mandatory and contains the information about the current state of the master sequenceTime UDINT Period of time in ms for the whole sequence shortAddress USINT Address information according to the IEC 61784 CPF 9 specification. This va

18、lue is accessible via the attribute slaveAddress. SlaveAddress is part of the BusInformation structure. These values shall be set by the responsible component as described in clause Nested Communication of IEC ISA-62453-2 (103.00.02) value USINT Variable for status information systemTag String Syste

19、m Tag of a DTM. It is strongly recommended to provide the attribute in the Request document. ANSI/ISA-62453-309 (103.00.08)-2011 - 17 - Table 4 Structured communication data types Data type Definition Description Elementary data types Usage Multiplicity Abort STRUCT Describes the abort communication

20、Reference O 01 CommandResponse STRUCT Status information. This is computed from the first status byte returned in command responses according to the IEC 61784 CPF 9 specification. If bit 7 of the first status byte is clear this value contains the value in the first status byte. If bit 7 is set this

21、element is not returned in the status structure value M 11 CommunicationStatus STRUCT Status information. This is computed from the first status byte returned in command responses according to the IEC 61784 CPF 9 specification. If bit 7 of the first status byte is set this value contains the value i

22、n the first status byte (This is where we need to state whether it is the first status byte or bits 0-6 of the first status byte). If bit 7 is clear this element is not returned in the status structure value M 11 ConnectRequest STRUCT Describes the communication request fdt:tag M 11 preambleCount O

23、01 primaryMaster O 01 longFrameRequired O 01 fdt:systemTag O 01 LongAddress O 01 ShortAddress M 11 ConnectResponse STRUCT Describes the communication response fdt:tag M 11 preambleCount M 11 primaryMaster M 11 communicationReference M 11 LongAddress O 01 ShortAddress M 11 ANSI/ISA-62453-309 (103.00.

24、08)-2011 - 18 - Data type Definition Description Elementary data types Usage Multiplicity DataExchange-Request STRUCT Describes the communication request commandNumber M 11 communicationReference M 11 fdt:CommunicationData O 01 DataExchange-Response STRUCT Describes the communication response comman

25、dNumber M 11 communicationReference M 11 burstFrame O 01 fdt:CommunicationData O 01 Status M 11 DisconnectRequest STRUCT Describes the communication request communicationReference M 11 DisconnectResponse STRUCT Describes the communication response communicationReference M 11 SubscribeRequest STRUCT

26、Describes the subscription request for device initiated data transfer (IEC 61784 CPF 9 burst mode) communicationReference M 11 SubscribeResponse STRUCT Describes the subscription response request for device initiated data transfer (IEC 61784 CPF 9 burst mode) communicationReference M 11 burstModeDet

27、ected M 11 fdt:communicationError O 01 UnsubscribeRequest STRUCT Describes the request to release the subscription for device initiated data transfer (IEC 61784 CPF 9 burst mode) communicationReference M 11 Unsubscribe-Response STRUCT Describes the response request to release the subscription for de

28、vice initiated data transfer (IEC 61784 CPF 9 burst mode) communicationReference M 11 fdt:communicationError O 01 LongAddress STRUCT Address information according to the IEC 61784 CPF 9 specification (only supported by devices based on HART revision 5, see related documentation) ANSI/ISA-62453-309 (

29、103.00.08)-2011 - 19 - Data type Definition Description Elementary data types Usage Multiplicity In the IEC 61784 CPF 9 protocol Manufacturer ID and Device type ID are contained in the longaddress If the channel delivers different values in fdthart:manufacturerId / fdthart:deviceTypeId and in the co

30、rresponding bytes in fdthart:LongAddress, the following rule applies: * the fdthart:LongAddress has to be used for communication and * the fdthart:manufacturerId and fdthart:deviceTypeId may be used only as information about the manufacturer and the type of device manufacturerId M 11 deviceTypeId M

31、11 address1 M 11 address2 M 11 address3 M 11 SequenceBegin STRUCT Describes the sequence begin sequenceTime O 01 delayTime O 01 communicationReference M 11 SequenceEnd STRUCT Describes the sequence end communicationReference M 11 SequenceStart STRUCT Describes the sequence start communicationReferen

32、ce M 11 ShortAddress STRUCT Address information according to the IEC 61784 CPF 9 specification shortAddress M 11 Status STRUCT Status information according to the IEC 61784 CPF 9 specification deviceStatus M 11 choice of M 11 CommunicationStatus S 11 CommandResponse S 11 NOTE The property fdt:tag, i

33、s part of the DtmDevice data type and contains the IEC 61784 CPF 9-specific value called TAG, which is used, for example within command #11, READ UNIQUE IDENTIFIER ASSOCIATED WITH TAGThese value shall be set by the responsible component as described in the Nested Communication publication IEC 62453-

34、2. ANSI/ISA-62453-309 (103.00.08)-2011 - 20 - 11 Channel parameter data types It is up to a DTM whether it provides any channels. If a DTM allows a Frame Application, other DTMs, or a controller the direct access to its process values via IEC 61784 CPF 9 protocol, it should provide FDT-Channel objec

35、ts as described in this clause. Only the complete description of all channels belonging to a command allows proper access for external applications. The description of channels, especially of the process values, allows the Frame Application to support the device in a more efficient way. Used at Read

36、ChannelData service and WriteChannelData service. The information returned by the ReadChannelData service describes how to access an I/O value via a command (see Table 5 and Table 6). The data types described in this clause are defined for the following namespace. Namespace: hartchannel Table 5 Simp

37、le channel parameter data types Data type Definition Description byteLength USINT Number of static bytes in a Request or in a Reply commandNumber UDINT Number of the command containing the channel value frameApplicationTag STRING Frame Application specific tag used for identification and navigation.

38、 The DTM should display this tag at channel specific user interfaces gatewayBusCategory UUID Unique identifier for a supported bus type according to the FDT specific CATID protectedByChannelAssignment BOOL TRUE if the channel is set to read only by the Frame Application. Usually set to TRUE if a cha

39、nnel assignment exists value STRING Current value of a channel for read or write Table 6 Structured channel parameter data types Data type Definition Description Elementary data types Usage Multiplicity CommandParameters STRUCT Static command parameter bytes in a Request or in a Reply fdt:binData O

40、01 byteLength M 11 FDTChannel STRUCT Description of the channel fdt:tag M 11 fdt:id M 11 fdt:descriptor O 01 protectedByChannel-Assignment M 11 ANSI/ISA-62453-309 (103.00.08)-2011 - 21 - Data type Definition Description Elementary data types Usage Multiplicity fdt:dataType M 11 byteLength M 11 fdt:s

41、ignalType M 11 frameApplicationTag O 01 appId:applicationId O 01 fdt:SemanticInformation O 0* fdt:BitEnumeratorEntries O 01 fdt:EnumeratorEntries O 01 fdt:Unit O 01 ReadCommand O 01 WriteCommand O 01 fdt:Alarms O 01 fdt:Ranges O 01 fdt:Deadband O 01 fdt:SubstituteValue O 01 FDTChannelType STRUCT Des

42、cription of the channel component in case of channels with gateway functionality fdt:VersionInformation M 11 gatewayBusCategory O 01 ReadCommand STRUCT Description of the command to read the channel from a device commandNumber M 11 Request O 01 Reply O 01 ResponseCodes O 01 Reply STRUCT Description

43、of the reply structure of a command according to the IEC 61784 CPF 9 specification collection of M 11 fdt:ChannelReference 0* CommandParameters 0* ResponseCodes O 01 Request STRUCT Description of the request structure of a command according to the IEC 61784 CPF 9 specification collection of M 11 fdt

44、:ChannelReference 0* CommandParameters 0* ANSI/ISA-62453-309 (103.00.08)-2011 - 22 - Data type Definition Description Elementary data types Usage Multiplicity ResponseCodes STRUCT Collection of specific response codes according to the IEC 61784 CPF 9 specification (known as COMMAND-SPECIFIC RESPONSE

45、 CODES) fdt:EnumeratorEntry M 1* WriteCommand STRUCT Description of the command to write the channel to a device commandNumber M 11 Request O 01 Reply O 01 ResponseCodes O 01 12 Device identification 12.1 Protocol specific handling of data type STRING IEC 61784 CPF 9 char array rules: in all strings

46、 with char ranges, 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 ? 12.2 Common device type identification data types The data types described in this subclause are reused as

47、defined by 12.3 and 12.5. The IEC 61784 CPF 9 device type identification data types provide general data types with a protocol specific semantic (see Table 7 and Table 8) as well as data types without such a mapping (see Table 9 and Table 10). The data types described in this subclause are defined f

48、or following namespace. Namespace: hartident ANSI/ISA-62453-309 (103.00.08)-2011 - 23 - 62453-309 IEC:2009(E) - 23 - Table 7 Identification data types with protocol specific mapping IEC 61784 CPF 9 Attribute Semantic element name Data request in physical device Protocol specific name IEC 61784 CPF 9

49、 data format FDT data type (display format) Specification reference shortAddress IdAddress Poll possible address range (HART5 : 0-15, HART 6 : 0-63 ) by calling Cmd 0. If Cmd 0 response is available, a physical device is connected to this address. Cmd #0 response does not contain short address value whether the short or long format is us