1、raising standards worldwideNO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAWBSI Standards PublicationField device tool (FDT) interfacespecification Part 309: Communication profile integration IEC 61784 CPF 9BS EN 62453-309:2009National forewordThis British Standard is the UK imp
2、lementation of EN 62453-309:2009. It isidentical to IEC 62453-309:2009.The UK participation in its preparation was entrusted to Technical CommitteeAMT/7, Industrial communications: process measurement and control, including fieldbus.A list of organizations represented on this committee can be obtain
3、ed onrequest to its secretary.This publication does not purport to include all the necessary provisions of acontract. Users are responsible for its correct application. BSI 2010ISBN 978 0 580 62565 7ICS 25.040.40; 35.100.05; 35.110Compliance with a British Standard cannot confer immunity fromlegal o
4、bligations.This British Standard was published under the authority of the StandardsPolicy and Strategy Committee on 31 January 2010Amendments issued since publicationAmd. No. Date Text affectedBRITISH STANDARDBS EN 62453-309:2009EUROPEAN STANDARD EN 62453-309 NORME EUROPENNE EUROPISCHE NORM October
5、2009 CENELEC European Committee for Electrotechnical Standardization Comit Europen de Normalisation Electrotechnique Europisches Komitee fr Elektrotechnische Normung Central Secretariat: Avenue Marnix 17, B - 1000 Brussels 2009 CENELEC - All rights of exploitation in any form and by any means reserv
6、ed worldwide for CENELEC members. Ref. No. EN 62453-309:2009 E ICS 25.040.40; 35.100.05; 35.110 English version Field device tool (FDT) interface specification - Part 309: Communication profile integration - IEC 61784 CPF 9 (IEC 62453-309:2009) Spcification des interfaces des outils des dispositifs
7、de terrain (FDT) - Partie 309: Intgration des profils de communication - CEI 61784 CPF 9 (CEI 62453-309:2009) Field Device Tool (FDT)-Schnittstellenspezifikation - Teil 309: Integration von Kommunikationsprofilen - Kommunikationsprofilfamilie (CPF) 9 nach IEC 61784 (IEC 62453-309:2009) This European
8、 Standard was approved by CENELEC on 2009-08-01. CENELEC members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references co
9、ncerning such national standards may be obtained on application to the Central Secretariat or to any CENELEC member. This European Standard exists in three official versions (English, French, German). A version in any other language made by translation under the responsibility of a CENELEC member in
10、to its own language and notified to the Central Secretariat has the same status as the official versions. CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Cyprus, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Irel
11、and, Italy, Latvia, Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and the United Kingdom. BS EN 62453-309:2009EN 62453-309:2009 - 2 - Foreword The text of document 65E/130/FDIS, future edition 1 of IEC 62453-309, prep
12、ared by SC 65E, Devices and integration in enterprise systems, of IEC TC 65, Industrial-process measurement, control and automation, was submitted to the IEC-CENELEC parallel vote and was approved by CENELEC as EN 62453-309 on 2009-08-01. Each part of the EN 62453-3xy series is intended to be read i
13、n conjunction with EN 62453-2. The following dates were fixed: latest date by which the EN has to be implemented at national level by publication of an identical national standard or by endorsement (dop) 2010-05-01 latest date by which the national standards conflicting with the EN have to be withdr
14、awn (dow) 2012-08-01 Annex ZA has been added by CENELEC. _ Endorsement notice The text of the International Standard IEC 62453-309:2009 was approved by CENELEC as a European Standard without any modification. _ BS EN 62453-309:2009- 3 - EN 62453-309:2009 Annex ZA (normative) Normative references to
15、international publications with their corresponding European publications The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including
16、any amendments) applies. NOTE When an international publication has been modified by common modifications, indicated by (mod), the relevant EN/HD applies. Publication Year Title EN/HD Year IEC 61158-5-20 1)Industrial communication networks - Fieldbus specifications - Part 5-20: Application layer ser
17、vice definition - Type 20 elements EN 61158-5-20 20082)IEC 61158-6-20 1)Industrial communication networks - Fieldbus specifications - Part 6-20: Application layer protocol specification - Type 20 elements EN 61158-6-20 20082)IEC 61784-1 1)Industrial communication networks - Profiles - Part 1: Fieldb
18、us profiles EN 61784-1 20082)IEC 62453-1 2009 Field device tool (FDT) interface specification - Part 1: Overview and guidance EN 62453-1 2009 IEC 62453-2 2009 Field device tool (FDT) interface specification - Part 2: Concepts and detailed description EN 62453-2 2009 1)Undated reference. 2)Valid edit
19、ion at date of issue. BS EN 62453-309:2009 2 62453-309 IEC:2009(E) CONTENTS INTRODUCTION.6 1 Scope.7 2 Normative references .7 3 Terms, definitions, symbols, abbreviated terms and conventions 7 3.1 Terms and definitions 7 3.2 Abbreviated terms .8 3.3 Conventions 8 3.3.1 Data type names and reference
20、s to data types 8 3.3.2 Vocabulary for requirements8 3.3.3 Use of UML .8 4 Bus category 8 5 Access to instance and device data8 5.1 Process Channel objects provided by DTM8 5.2 DTM services to access instance and device data .9 6 Protocol specific behavior.9 6.1 Overview .9 6.2 Burst mode subscripti
21、on 9 7 Protocol specific usage of general data types.10 8 Protocol specific common data types11 9 Network management data types11 10 Communication data types .11 11 Channel parameter data types15 12 Device identification .17 12.1 Protocol specific handling of data type STRING 17 12.2 Common device t
22、ype identification data types .17 12.3 Topology scan data types22 12.4 Scan identification data types23 12.5 Device type identification data types provided by DTM .24 Bibliography27 Figure 1 Part 309 of the IEC 62453 series .6 Figure 2 Burst mode subscription.10 Table 1 Protocol identifiers 8 Table
23、2 Protocol specific usage of general data types10 Table 3 Simple communication data types .11 Table 4 Structured communication data types12 Table 5 Simple channel parameter data types16 Table 6 Structured channel parameter data types 16 Table 7 Identification data types with protocol specific mappin
24、g.19 Table 8 Identification data types without protocol independent semantics 21 Table 9 Simple identification data types with protocol independent semantics22 BS EN 62453-309:200962453-309 IEC:2009(E) 3 Table 10 Structured identification data types with protocol independent semantics 22 Table 11 St
25、ructured device type identification data types .22 Table 12 Simple scan identification data types.23 Table 13 Structured scan identification data types .23 Table 14 Structured device type identification data types .25 BS EN 62453-309:2009 6 62453-309 IEC:2009(E) INTRODUCTION This part of IEC 62453 i
26、s an interface specification for developers of FDT (Field Device Tool) components for function control and data access within a client/server architecture. The specification is a result of an analysis and design process to develop standard interfaces to facilitate the development of servers and clie
27、nts by multiple vendors that need to interoperate seamlessly. With the integration of fieldbusses into control systems, there are a few other tasks which need to be performed. In addition to fieldbus- and device-specific tools, there is a need to integrate these tools into higher-level system-wide p
28、lanning- or engineering tools. In particular, for use in extensive and heterogeneous control systems, typically in the area of the process industry, the unambiguous definition of engineering interfaces that are easy to use for all those involved is of great importance. A device-specific software com
29、ponent, called DTM (Device Type Manager), is supplied by the field device manufacturer with its device. The DTM is integrated into engineering tools via the FDT interfaces defined in this specification. The approach to integration is in general open for all kind of fieldbusses and thus meets the req
30、uirements for integrating different kinds of devices into heterogeneous control systems. Figure 1 shows how IEC 62453-309 is aligned in the structure of the IEC 62453 series. Part 309Communicationprofile integration IEC 61784 CPF 9Figure 1 Part 309 of the IEC 62453 series IEC 1134/09 BS EN 62453-309
31、:200962453-309 IEC:2009(E) 7 FIELD DEVICE TOOL (FDT) INTERFACE SPECIFICATION Part 309: Communication profile integration IEC 61784 CPF 9 1 Scope Communication Profile Family 9 (commonly known as HART1) defines communication profiles based on IEC 61158-5-20 and IEC 61158-6-20. The basic profile CP 9/
32、1 is defined in IEC 61784-1. This part of IEC 62453 provides information for integrating the HART technology into the FDT standard (IEC 62453-2). This part of the IEC 62453 specifies communication and other services. This standard neither contains the FDT specification nor modifies it. 2 Normative r
33、eferences The following referenced documents are indispensable for the application of this specification. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies IEC 61158-5-20, Industrial communic
34、ation networks Fieldbus specifications Part 5-20: Application layer service definition Type 20 elements IEC 61158-6-20, Industrial communication networks Fieldbus specifications Part 6-20: Application layer protocol specification Type 20 elements IEC 61784-1, Industrial communication networks Profil
35、es Part 1: Fieldbus profiles IEC 62453-1:2009, Field Device Tool (FDT) interface specification Part 1: Overview and guidance IEC 62453-2:2009, Field Device Tool (FDT) interface specification Part 2: Concepts and detailed description 3 Terms, definitions, symbols, abbreviated terms and conventions 3.
36、1 Terms and definitions For the purposes of this document, the terms and definitions given in IEC 62453-1 and IEC 62453-2 and the following apply. 1HART is the trade name of the product supplied by HART Communication Foundation. This information is given for convenience of users of this document and
37、 does not constitute an endorsement by IEC of the product named. Equivalent products may be used if they can be shown to lead to the same results. BS EN 62453-309:2009 8 62453-309 IEC:2009(E) 3.1.1 burst mode mode in which the field device generates response telegrams without request telegram from t
38、he master 3.2 Abbreviated terms For the purposes of this document, the abbreviations given in IEC 62453-1, IEC 62453-2 and the following apply. BACK Burst ACKnowledge UML Unified Modelling Language 3.3 Conventions 3.3.1 Data type names and references to data types The conventions for naming and refe
39、rencing of data types are explained in IEC 62453-2, Clause A.1 3.3.2 Vocabulary for requirements The following expressions are used when specifying requirements. Usage of “shall” or “mandatory” No exceptions allowed. Usage of “should” or “recommended” Strong recommendation. It may make sense in spec
40、ial exceptional cases to differ from the described behaviour. Usage of “can or “optional Function or behaviour may be provided, depending on defined conditions. 3.3.3 Use of UML Figures in this document are using UML notation as defined in Annex A of IEC 62453-1. 4 Bus category IEC 61784 CPF 9 proto
41、col is identified in the protocolId element of structured data type fdt:BusCategory by the following unique identifier (Table 1): Table 1 Protocol identifiers Identifier value ProtocolId name Description 036D1498-387B-11D4-86E1-00E0987270B9 HART Support of IEC 61784 CPF 9 protocol 5 Access to instan
42、ce and device data 5.1 Process Channel objects provided by DTM The minimum set of provided data shall be: the first four provided process related values (PV, SV, ) - if available - are modeled as channel references. The referenced channel shall include ranges and scaling. BS EN 62453-309:200962453-3
43、09 IEC:2009(E) 9 5.2 DTM services to access instance and device data The services InstanceDataInformation and DeviceDataInformation shall provide access to at least to all parameters of the Universal and Common Practice commands (as far as the device supports the function). Furthermore, the Response
44、 Byte 0 and the Response Byte 1 for each command shall be exposed. The services InstanceDataInformation and DeviceDataInformation may also provide access to device specific parameters (e.g. diagnostic information). 6 Protocol specific behavior 6.1 Overview There is only one protocol specific sequenc
45、e defined for IEC 61784 CPF 9: burst mode subscription. This sequence explains how the sequence “”, defined in Part 2 of this standard, is applied in context of burst telegrams as defined by IEC 61784 CPF 9. 6.2 Burst mode subscription A subscription to device initiated data transfer can be requeste
46、d by sending a transaction request with SubscribeRequest content (see Figure 2). The Communication Channel may detect if the device is already in burst mode. NOTE In HART 5 this can be detected only when burst frames are received from the device. In HART 6 the burst mode can be detected using comman
47、d 105. The Communication Channel answers to a SubscribeRequest with a SubscribeResponse content. If burst frames are received, the device is in burst mode and burstModeDetected value is set to TRUE. This means that Device DTM will start to receive burst messages via the transaction response mechanis
48、m. In the case that no burst messages were received, burstModeDetected value is set to FALSE. It is up to Device DTM to set device into burst mode. Then Device DTM may call a transaction request with SubscribeRequest content again in order to receive burst messages. In order to unsubscribe, the Devi
49、ce DTM sends a transaction request with a UnsubcribeRequest. The Communication Channel answers with a SubscribeResponse where burstModeDetected value is set to FALSE. The Device DTM will not receive any more burst information via the transaction response mechanism. The Communication Channel does not switch off the burst mode in the device. The Device DTM may switch burst mode on or off by using normal transaction re
