ANSI ISA 62453-301-2011 Field device tool (FDT) interface specification C Part 301 Communication profile integration C IEC 61784 CPF 1 (103.00.03)《现场设备工具(FDT)接口规范.第301部分 通信剖面综合.IEC.pdf

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

2、ofile integration IEC 61784 CPF 1 ISBN: 978-0-876640-57-9 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. All

3、requests pertaining to the ANSI/ISA62453-301 (103.00.03)-2011 Standard should be submitted to ISA. ISA 67 Alexander Drive P.O. Box 12277 Research Triangle Park, North Carolina 27709 ANSI/ISA-62453-301 (103.00.03)-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-301 (103.00.03)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 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 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 stand

7、ards 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 the DTM shall provide support for the data described in 9.1.2; for each block in the device all standard block parameters shal

9、l be provided by the corresponding BTM object as specified in IEC ISA-62453 2 (103.00.02) It is recommended that all non-standard block parameters are also provided as specified in 9.2. A Device DTM shall provide access to the following groups of parameters if they are presented to the user: link pa

10、rameters; action parameters; alert parameters; ANSI/ISA-62453-301 (103.00.03)-2011 - 21 - trend parameters; domain objects; program invocation objects. 6.2 BTM BTMs built according to the function block specification shall expose all parameters for the corresponding block as defined for the DTM. All

11、 standard parameters defined for a block in the FF specification shall be exposed. The manufacturer specific parameters may be added to extend this list. User defined parameter shall be exposed if they exist. 7 Protocol specific behavior 7.1 Connection management The Connect service establishes an F

12、DT connection. The FDT connection acts as a container for FMS connections, as a container for SM connectionless services and as a container for FDA sessions. It is necessary to maintain the FMS connection separate from the underlying FDT connection. 7.1.1 FMS connection FDT implements all FMS and SM

13、 services as transactions in the respective protocols. This includes the services for the FMS connection management. FmsInitiate transaction and FmsAbort transaction manage the lifetime of a FMS connection. In order to open multiple FMS connections on the same FDT connection, a Transaction service r

14、equest is called with an FmsInitiateRequest element as argument. The communication reference passed with the FmsInitiateRequest element identifies the FDT connection to be used. The FmsInitiateResponse element returned with Transaction service response provides a communication reference used for all

15、 further FMS services on that FMS connection. This mapping allows multiple FMS connections on one FDT connection. ANSI/ISA-62453-301 (103.00.03)-2011 - 22 - Figure 4 FMS mapping in the FDT connection If the FDT connection is closed, the FMS connections for this connection are also closed automatical

16、ly (by the communication channel) before the FDT Disconnect service is completed. Any transactions requested after that will fail. No outstanding services will be processed. Figure 5 FDT Disconnect service FMSAbort service request closes a single FMS connection. IEC 1123/09 IEC 1124/09 ANSI/ISA-6245

17、3-301 (103.00.03)-2011 - 23 - 7.1.2 FDT connection FDT connection is using Connect service request: to establish an FDT connection intended for System Management services only. When FDT connections for SM services only are established, the OpenSessionRequest element is not part of the ConnectRequest

18、. Any request to establish an FMS connection on this type of FDT connection shall be rejected; to establish an FDT connection that represents a session as described with the specification FF-588 Field Device Access Agent. FMS connections can be established by using the FDT communication reference re

19、turned as a result of FDT connection establishment. Note that multicast SM services are not allowed in this connection. If an HSE device needs both types of connections it needs to create System management and FDT Session Connections. When a Frame Application requests the DTM to disconnect, all FMS

20、connections and FDT connections (SM and Session) shall be terminated. 7.2 Abort 7.2.1 OnAbort Indication At any moment during the lifetime of the (FDT or FMS) Connection an OnAbort event indication can be received by the DTM/BTM from the Communication Channel. There can be two reasons for OnAbort Ev

21、ent: FMS Connection Abort; FDT Connection Abort. The Communication reference uniquely identifies the Connection to be aborted. If a FDT Connection Abort is indicated, all FMS connections of the corresponding FDT Connection shall be terminated. No Abort requests are issued to the Communication Channe

22、l. All pending requests shall be cancelled. If an FMS Connection Abort is indicated, only the FMS Connection identified by that Communication Reference is terminated. 7.2.2 Abort request At any moment during the lifetime of the (FDT or FMS) connections a DTM/BTM can issue an Abort request to the Com

23、munication Channel. There can be two types of Communication References in the Abort request: FMS Communication Reference; FDT Communication Reference. The Communication reference uniquely identifies the Connection to be aborted. If an FDT Connection Abort is requested, all related FMS connections in

24、 the Communication channel shall be terminated. No separate Abort requests are issued to the Communication Channel for the individual FMS Connections. All pending requests shall be cancelled. ANSI/ISA-62453-301 (103.00.03)-2011 - 24 - If an FMS Communication Reference is used in the Abort, only the

25、FMS Connection identified by that Communication Reference is terminated. 7.3 Relation of FMS requests and FMS responses If a DeviceDTM (communication client) issues an FMS request as in Table 4, it shall expect a response as shown in the table. Table 4 Relation of FMS requests and FMS responses Requ

26、est Response (s) FmsInitiateRequest FmsInitiateResponse FmsInitiateError FmsAbortRequest FmsStandardResponse FmsReadRequest FmsReadResponse FmsServiceError FmsWriteRequest FmsStandardResponse FmsServiceError FmsStatusRequest FmsStatusResponse FmsServiceError FmsIdentifyRequest FmsIdentifyResponse Fm

27、sServiceError FmsDefineVariableListRequest FmsDefineVariableListResponse FmsServiceError FmsDeleteVariableListRequest FmsStandardResponse FmsServiceError FmsGetOdRequest FmsGetOdResponse FmsServiceError FmsGenericInitiateDownloadSequenceRequest FmsStandardResponse FmsServiceError FmsGenericDownloadS

28、egmentRequest FmsStandardResponse FmsServiceError FmsGenericTerminateDownloadSequenceRequest FmsGenericTerminateDownloadSequenceResponse FmsServiceError fms:FmsInformationReport fms:FmsInformationReport fms:CreateProgramInvocation FmsStandardResponse FmsServiceError fms:DeleteProgramInvocation FmsSt

29、andardResponse FmsServiceError fms:Start FmsStandardResponse FmsServiceError fms:Stop FmsStandardResponse FmsServiceError fms:Resume FmsStandardResponse FmsServiceError ANSI/ISA-62453-301 (103.00.03)-2011 - 25 - Request Response (s) fms:Reset FmsStandardResponse FmsServiceError fms:Kill FmsStandardR

30、esponse FmsServiceError H1SubscribeRequest H1SubscribeResponse H1UnSubscribeRequest H1UnSubscribeResponse HSESubscribeRequest HSESubscribeResponse HSEUnSubscribeRequest HSEUnSubscribeResponse Any Service fdt:CommunicationError A DTM or a BTM can receive a standard FDT CommunicationError response ins

31、tead of FMS Transaction response to indicate a general communication error. Communication clients shall be prepared to handle such a response. If the FMS connection in the Device DTM is shared between several BTMs, all connections will receive OnAbort event when the Device FMS connection is aborted.

32、 7.4 Subscription mechanism The FF subscription mechanism is based on the rules of the device initiated data transfer. For a DTM that supports Device Initiated Data Transfer there may be one or multiple subscribers expecting data at the same time. 7.4.1 General To support the device initiated data t

33、ransfer for IEC 61784 CPF 1 additional transaction request and transaction responses are defined. Two transaction requests are used to initiate the FMS subscription connection and four transaction responses are associated with the FMS subscriptions. These transactions are detailed below: transaction

34、 request for subscribing; transaction response for subscribing; transaction request for unsubscribing; transaction response for unsubscribing; transaction detailing the FMS Information Report; transaction response detailing the FMS EventNotification. 7.4.2 Transactions for subscribing H1 Device DTM/

35、BTM can subscribe to data by calling a H1SubscribeRequest Transaction. It can subscribe for data collected in a trend object H1TrendSubscriptionInfo; single device parameter H1ParameterSubscriptionInfo; an alarm or eventH1EventSubscriptionInfo. Additional information to identify the device is provid

36、ed in the transaction request. This information may be used by the Communication Provider to speed up the process of subscribing. ANSI/ISA-62453-301 (103.00.03)-2011 - 26 - The result of the subscription mechanism is provided in the H1SubscribeResponse transaction. The communication reference used i

37、s the communication reference of the FDT connection. The InvokeID of the subscription request will be used to provide the association between the subscription and FmsInformationReport or FmsEventNotification transaction. The InvokeID received during the subscription will be used for Unsubscribing. T

38、he InvokeID uniquely identifies all transactions related to the created subscription and shall not be used for any other transactions during the lifetime of the subscription. 7.4.3 Transactions for subscribing HSE The HSE Linking Device DTM can subscribe to data by calling an HSESubscribeRequest Tra

39、nsaction. DTMs can map the subscription from a H1 DTM to a HSE subscription. The HSE subscription can be used to subscribe for data from an H1 device via a HSE Linking device; an HSE device. It can subscribe for data in a trend object on an H1 device (HSETrendSubscriptionInfo); data in a trend objec

40、t on an HSE device (LocalTrendSubscriptionInfo); single parameter from an H1 device (HSEParameterSubscriptionInfo); single parameter from an HSE device (LocalParameterSubscriptionInfo), an Event from an H1 device (HSEEventSubscriptionInfo); an Event from an HSE device (LocalEventSubscriptionInfo). A

41、dditional information about the device is provided in the transaction request. This information may be used by the Communication Provider to speed up the process of subscribing. The result of the subscription mechanism is provided in the HSESubscribeResponse transaction. The communication reference

42、used is the communication reference of the FDT connection. The InvokeID of the subscription request will be used to provide the association between the subscription and FmsInformationReport or FmsEventNotification transaction. The same InvokeID will identify the subscription during the Unsubscribing

43、. The InvokeID uniquely identifies all transactions related to the created subscription and shall not be used for any other transactions during the lifetime of the subscription. 7.4.4 Transactions for subscribing BTM A BTM can subscribe for data by calling a BtmSubscribeRequest Transaction. The pare

44、nt DTM can map the subscription from a BTM to an H1 or HSE subscription. BTM can subscribe for ANSI/ISA-62453-301 (103.00.03)-2011 - 27 - single parameter (BtmParameterSubscriptionInfo); data collected in the Device Trend object (BtmTrendSubscriptionInfo); an alarm or event (BtmEventSubscriptionInfo

45、). The Device DTM shall provide association and configuration of the trend object if a subscr iption for trend data is requested. The result of the subscription mechanism is provided in the BtmSubscribeResponse transaction. The communication reference used is the communication reference of the FDT c

46、onnection. The InvokeID of the subscription request will be used to provide the association between the subscription and FmsInformationReport or FmsEventNotification transaction. The same InvokeID will identify the subscription during the Unsubscribing. The InvokeID shall not be used for any other t

47、ransactions during the lifetime of the subscription. If more than one BTM is subscribed for the same object, the Device DTM shall propagate the information to all subscribed BTMs. 8 Protocol specific usage of general data types 8.1 Address For all exposed parameters in DTMs and BTMs the address (def

48、ined in Part 2) shall be constructed according to the following model: VFD:xx.INDEX:yyy.SUBINDEX:zz, where xx is the VFD tag or a number presenting the index of the VFD (one based) ; yy is a number presenting the parameter index from the beginning of the VFD; zz is a number showing the parameter sub

49、-index. The values of xx, yy and zz shall be integers (some can be 32 bit) and are presented as decimals digits. There should be no leading zeros for the numbers. The sub-index portion of the address is optional and may be omitted or set to 0. Providing this information with the device data set is sufficient for accessing the device/block parameters and there is no need for process channel definition for BTMs. 8.2 protocolID See Clause 5. 8.3 applicationDomain The applicationDomain attr