ISA 62453-2-2011 Field device tool (FDT) interface specification C Part 2 Concepts and detailed description (103 00 02).pdf

《ISA 62453-2-2011 Field device tool (FDT) interface specification C Part 2 Concepts and detailed description (103 00 02).pdf》由会员分享，可在线阅读，更多相关《ISA 62453-2-2011 Field device tool (FDT) interface specification C Part 2 Concepts and detailed description (103 00 02).pdf（182页珍藏版）》请在麦多课文档分享上搜索。

1、 AMERICAN NATIONAL STANDARD ANSI/ISA62453-2 (103.00.02)-2011 Field device tool (FDT) interface specification Part 2: Concepts and detailed description Approved 31 May 2011 ANSI/ISA62453-2 (103.00.02)-2011, Field device tool (FDT) interface specification - Part 2: Concepts and detailed description IS

2、BN: 978-0-876640-56-2 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 requests pertaining to the ANSI/ISA6

3、2453-3 (103.00.02)-2011 Standard should be submitted to ISA. ISA 67 Alexander Drive P. O. Box 12277 Research Triangle Park, North Carolina 27709 USA ANSI/ISA-62453-2 (103.00.02)-2011 - 3 - Preface This preface, as well as all footnotes and annexes, is included for information purposes and is not par

4、t of ANSI/ISA62453-2 (103.00.02)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. Toward this end, the Society welcomes all

5、 comments and cr iticisms 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 Standards and Practices Department i

6、s 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 standards of incorporating suitable refer

7、ences 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 reports to the greatest extent possi

8、ble. Standard for Use of the International System of Units (SI): The Modern Metric System , published by the American Society for Testing X service is available in this state. 3.3.2 Data type names and references to data types The conventions for naming and referencing data types are explained in Cl

9、ause A.1. 4 Fundamentals 4.1 General This clause introduces the FDT model and covers topics which are specific to the requirements of field device integration. ANSI/ISA-62453-2 (103.00.02)-2011 - 19 - 4.2 Abstract FDT model 4.2.1 FDT model overview Figure 2 provides an overview of the objects define

10、d in FDT and their relationships to each other. C h a n n e lD T MF r a m e A p p l i c a t i o nP r o j e c tP r e s e n t a t i o nH o s t C h a n n e l1*p r o j e c t sh o s t c h a n n e l s1*11F A c h a n n e l sa s s i g n e d c h a n n e l s*1*d e v i c e so p e n e d p r e s e n t a t i o n

11、s*11c h a n n e l p r e s e n t a t i o nD T M p r e s e n t a t i o nD T M c h a n n e l sl i n k e d c o m m u n i c a t i o n c h a n n e l s 1*l i n k e d D T M s*0 . . 10 . . 1Figure 2 Abstract FDT model Table 1 contains brief descriptions of all objects. More detail description of objects and

12、related services are provided in subsequent chapters. The FDT objects may be executed all on one platform or in a distributed system. For data exchange and for the interaction between objects, the data types as defined in 0 are used. The concrete implementation of these data types is defined in the

13、IEC 62453-4z documents describing the mapping to specific implementation technologies. Table 1 Description of FDT objects Object Description Frame Application The Frame Application is a logical object to represent an environment like an engineering system or a standalone tool (see 4.2.2). It control

14、s the lifetime of DTM-instances within the project. A Frame Application may handle several projects Project The Project belongs to the Frame Application. The Project is a logical object describing the management of device-instances. It controls the lifetime and dataset of device-instances within a F

15、rame Application. FDT does not define any services for the Project, since it is a pure Frame Application internal object IEC 1071/09 ANSI/ISA-62453-2 (103.00.02)-2011 - 20 - Object Description HostChannel A HostChannel belongs to the Frame Application. The HostChannel is a logical object representin

16、g a part of a function of a host system, such as DCS or PLC. It is required when additional information for the processing of device I/O data is needed, e.g. if DTM or BTM data refers to more than one I/O value. For example one Octet often is used to group the state values of eight digital I/O point

17、s. In these applications, the HostChannel object provides an association between contents of the channel data and individual process I/O points. To make the cyclic I/O data available within a Frame Application, there shall be an association between the I/O function blocks and the process values of a

18、 device. The inputs and outputs of I/O function blocks are represented by HostChannels, the process value is represented by a Channel. The association between HostChannel and Channel is called channel assignment. FDT does not define any services for the Host Channel, since it is a pure Frame Applica

19、tion internal object DTM A DTM is a software component containing the device specific application software. It encapsulates all devicespecific data, functions and business rules. A DTM is generally not stand-alone executable. It needs a Frame Application (see 4.2.2) that acts as the runtime environm

20、ent. A DTM is typically developed by the device manufacturer and shipped together with the devices. It depends on the software design of the DTM, whether it can be used for one specific device type or a group of different device types or a device type family. Each device installed on a plant is repr

21、esented by a DTM object. Therefore one or several DTM objects are needed to handle the different devices. The DTMs are installed in the system, so that the system can be dynamically extended by installing new DTMs for new devices. A DTM may represent different types of devices, e.g. field devices, c

22、ommunication devices or gateway devices. (see 4.2.3) BTM A BTM (see 4.2.3.6) is used to represent flexible software objects within a device, like function blocks. These software blocks are more flexible than software modules, for instance they may be moved between devices. Also a protocol may requir

23、e modeling of device structures as blocks. Presentation Presentation objects (see 4.2.4) represent a (visual) user interface. The Presentation object belongs to the DTM, to the BTM or to the Channel. Channel Channel-Object could behave in three ways: As a Communication-Channel, a Process-Channel and

24、 a combination of both (see 4.2.5). All the associations shown in Figure 2 above are explained in Table 2 below. ANSI/ISA-62453-2 (103.00.02)-2011 - 21 - Table 2 Description of associations between FDT objects Association Description assigned channels To make the cyclic I/O data available within a F

25、rame Application there has to be an association between the I/O function blocks and the process values of a device. The I/O function blocks are represented by a host channel, the process value by a channel. The Frame Application (project) is responsible for handling this association. Use cases: chan

26、nel assignment Services: Informational services DTM service: GetChannels channel service: ReadChannelInformation Management services channel service: WriteChannelInformation Depending services proprietary DTM services for channel management channel presentation The instances of presentation objects

27、are associated to the instance of their DTM business object by this relationship. Use cases: all channel use cases with DTM specific GUI Services: Informational services (see also 7.3) channel service: GetChannelFuntions channel service: GetGuiInformation Depending services frame service: OpenPresen

28、tationRequest frame service: ClosePresentationRequest devices A project holds the list of DTM instances by the association devices. Releasing the project results in a release of all associated DTM instances. A DTM instance cannot be part of more than one project. Use cases: system generation system

29、planning Services: Informational services frame service: GetChildNodes Management services services related to sub-topology management see 7.6.2 ValidateAddChild ChildAdded ValidateRemoveChild ChildRemoved FA services related to topology management DTM channels A DTM can have a list of channels, whi

30、ch are associated by DTM channels. A channel is part of a DTM. Services: Informational services frame service: GetChannels Management services There are no services to manipulate this association. The lifetime of channel instances is controlled by a DTM ANSI/ISA-62453-2 (103.00.02)-2011 - 22 - Assoc

31、iation Description DTM presentation The presentation object instances are associated with their DTM instance by this relationship. Use cases: All DTM use cases with DTM specific GUI Services: open presentation close presentation FA channels The Frame Application (project) may have a list of Communic

32、ation Channels. There are no services to manipulate this association. See 4.2.2 host channels The FA maps the Process Channels of DTMs to internal IO management of the projects linked communication channels The topology of DTMs is shown with this association. Within the topology tree a DTM object is

33、 the child node of a channel. The association shows the connection from a device to a channel. The Frame Application (project) is responsible for handling this association. Services: linked channels can be explored by GetParentNodes SetLinkedCommunicationChannel ReleaseLinkedCommunicationChannel lin

34、ked DTMs The topology of field devices is shown with this association. Within the topology tree a channel object is the parent node for a device. The association shows the connection from a channel to a device. The Frame Application (project) is responsible for handling this association. Services: l

35、inked DTMs can be explored by GetChildNodes SetLinkedCommunicationChannel ReleaseLinkedCommunicationChannel opened presentations Open presentation objects are linked by this association to projects. The Frame Application (project) is responsible for handling this association projects A Frame Applica

36、tion can create and manage multiple projects, which are connected by the “projects” association. The Frame Application (project) is responsible for handling this association 4.2.2 Frame Application (FA) The Frame Application is the runtime environment for the DTMs. It provides the services described

37、 in 7.7 which may be used by the hosted DTMs. If the Frame Application has built-in communication capabilities, then it is able to provide Communication Channels (see 4.2.5.3) which provide the services to access the fieldbus. In this case it has full control over communication and is able perform l

38、ow-level actions such as monitoring or filtering. Frame Applications without build-in communication capabilities are using Communication DTMs (see 4.2.3.2). Figure 3 shows the relation between the Frame Application and Communication Channel object. ANSI/ISA-62453-2 (103.00.02)-2011 - 23 - F r a m e

39、A p p l i c a t i o nF r a m e A p p l i c a t i o n s e r v i c e sC o m m u n i c a t i o n C h a n n e lC o m m u n i c a t i o n C h a n n e l s e r v i c e s10 . . *F i e l d b u s I n t e r f a c e F i e l d b u sr e p r e s e n t sr e p r e s e n t sD e v i c eFigure 3 Frame Application with

40、integrated Communication Channel The Frame Applications channel objects represent the gateway from the FDT-specific to the Frame Application-specific communication. On the Frame Applications side the Communication Channel may be a PC I/O board or engineering topology with processing units and propri

41、etary bus systems. 4.2.3 Device Type Manager (DTM) 4.2.3.1 DTM Overview The DTM provides the services described in 7.2 (see Figure 4). From a Frame Applications point of view, all management and task-related interactions with the device functionality are available via these services. D T MD T M s e

42、r v i c e s Figure 4 Device Type Manager (DTM) A DTM may represent the device structure with data type net:DtmDeviceInstanceTopology. This information may be retrieved by service GetActiveTypeInfo (see 7.2.3.4). The structure of the device may be described by a list of net:Module. Each module may ha

43、ve a number of properties, including configuration data, Process Channels and Communication Channels. A DTM exposes a list of supported device types with the data type fdt:DtmDeviceTypes (see 4.7.1). Different types of devices, for example, communication devices, field devices, modules, gateways or

44、blocks are represented by different types of DTMs. 4.2.3.2 Communication DTM (COMM-DTM) A Communication DTM is a special type of DTM containing the application software for specific communication hardware. For example, it may support configuration settings like baud -rate, start and stop bits, etc.

45、IEC 1072/09 IEC 1073/09 ANSI/ISA-62453-2 (103.00.02)-2011 - 24 - A Communication DTM shall provide Communication Channels (see 4.2.5.3) which provide the services to access the fieldbus (see Figure 5). C O M M D T MC o m m u n i c a t i o n C h a n n e l10 . . *D T MD T M s e r v i c e sF i e l d b

46、u s I n t e r f a c e F i e l d b u sr e p r e s e n t sr e p r e s e n t sD e v i c eC o m m u n i c a t i o n C h a n n e l s e r v i c e sFigure 5 Communication DTM The advantage of Communication Channels provided by a DTM compared to the channels provided by a Frame Application (see 4.2.2) is, t

47、hat they may be integrated into a Frame Application and are thus extending the number of protocols the system is able to access. Both ways of providing Communication Channels may coexist in a Frame Application. 4.2.3.3 Device DTM A Device DTM is a special type of DTM containing the application softw

48、are for a normal field device, for example, a pressure transmitter or a valve. Such a DTM for example supports functions to configure and parameterize the device (see Figure 6). D e v i c e D T MP r o c e s s C h a n n e lP r o c e s s C h a n n e l s e r v i c e s10 . . *F i e l d b u s I n t e r f

49、 a c e D e v i c eD T M S e r v i c e sD T MI / O s i g n a l sF i e l d b u sr e p r e s e n t sr e p r e s e n t sFigure 6 Device DTM If it is required to make the devices I/O signals or process values accessible to the host system, then the Device DTM shall provide Process Channel objects (see 4.2.5.2). IEC 1074/09 IEC 1075/09 ANSI/ISA-62453-2 (103.00.02)-2011 - 25 - 4.2.3.4 Gateway DTM A Gateway DTM is a special type of DTM containing the application software for a device linking fi