1、raising standards worldwideNO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAWBSI Standards PublicationField device tool (FDT) interfacespecification Part 503-1: Communication implementation for common object model IEC 61784 CP 3/1 and CP 3/2PD CLC/TR 62453-503-1:2009National fore
2、wordThis Published Document is the UK implementation of CLC/TR 62453-503-1: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
3、be obtained 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 62570 1ICS 25.040.40; 35.100.05; 35.110Compliance with a British Standard cannot confer immunity fr
4、omlegal obligations.This Published Document was published under the authority of theStandards Policy and Strategy Committee on 31 January 2010Amendments issued since publicationAmd. No. Date Text affectedBRITISH STANDARDPD CLC/TR 62453-503-1:2009TECHNICAL REPORT CLC/TR 62453-503-1 RAPPORT TECHNIQUE
5、TECHNISCHER BERICHT November 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
6、 form and by any means reserved worldwide for CENELEC members. Ref. No. CLC/TR 62453-503-1:2009 E ICS 25.040.40; 35.100.05; 35.110 English version Field device tool (FDT) interface specification - Part 503-1: Communication implementation for common object model - IEC 61784 CP 3/1 and CP 3/2 (IEC/TR
7、62453-503-1:2009) Spcification des interfaces des outils des dispositifs de terrain (FDT) - Partie 503-1: Implmentation des communications pour le modle objet commun - CEI 61784 CP 3/1 et CP 3/2 (CEI/TR 62453-503-1:2009) Field Device Tool (FDT)-Schnittstellenspezifikation - Teil 503-1: Kommunikation
8、simplementierung mit dem allgemeinen Objektmodell (COM) - Kommunikationsprofile (CP) 3/1 und 3/2 nach IEC 61784 (IEC/TR 62453-503-1:2009) This Technical Report was approved by CENELEC on 2009-10-01. CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Cyprus, t
9、he Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and the United Kingdom. PD CLC/TR 62453-503-1:2009CLC/TR 6
10、2453-503-1:2009 - 2 - Foreword The text of document 65E/67/CDV, future edition 1 of IEC/TR 62453-503-1, prepared 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 appr
11、oved by CENELEC as CLC/TR 62453-503-1 on 2009-10-01. This standard is to be used in conjunction with EN 62453-3xy series. Annex ZA has been added by CENELEC. _ Endorsement notice The text of the Technical Report IEC/TR 62453-503-1:2009 was approved by CENELEC as a Technical Report without any modifi
12、cation. In the official version, for Bibliography, the following note has to be added for the standard indicated: IEC 61784-1 NOTE Harmonized as EN 61784-1:2008 (not modified). _ PD CLC/TR 62453-503-1:2009- 3 - CLC/TR 62453-503-1:2009 Annex ZA (normative) Normative references to international public
13、ations 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 any amendments) appl
14、ies. 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 series Industrial communication networks - Fieldbus specifications EN 61158 series IEC 62453-1 2009 Field device tool (FD
15、T) 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 IEC/TR 62453-41 2009 Field device tool (FDT) interface specification - Part 41: Object model integra
16、tion profile - Common object model CLC/TR 62453-41 2009 IEC 62453-303-1 2009 Field device tool (FDT) interface specification - Part 303-1: Communication profile integration - IEC 61784 CP 3/1 and CP 3/2 EN 62453-303-1 2009 _ PD CLC/TR 62453-503-1:2009 2 TR 62453-503-1 IEC:2009(E) CONTENTS INTRODUCTI
17、ON.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 Symbols and abbreviated terms.7 3.3 Conventions 8 3.3.1 Data type names and references to data types 8 3.3.2 Vocabulary for requirements8 4 Bus category 8 5 Acc
18、ess to instance and device data8 6 Protocol specific behavior.8 6.1 General .8 6.2 Representing modularity9 6.2.1 Monolithic DTMs9 6.2.2 Modular DTMs .10 6.3 Interfaces and Information related to Bus Master Configuration.13 6.4 Configuration changes in a device.13 6.5 Error behavior: DTM refuses new
19、 BMCP .14 7 Protocol specific usage of general data types.14 8 Network management data types15 8.1 General .15 8.2 PROFIBUS device address15 8.3 Master-bus parameter set15 8.4 Slave bus parameter set15 8.5 Module and channel data 15 9 Communication data types .18 9.1 General .18 9.2 DPV0 communicati
20、on FDTProfibusDPV0CommunicationSchema .18 9.3 DPV1 communication FDTProfibusDPV1CommunicationSchema .20 10 Channel parameter data types23 11 Device identification .25 11.1 Device type identification data types FDTProfibusIdentSchema25 11.2 Topology scan data types DTMProfibusDeviceSchema.26 11.3 Sca
21、n identification data types FDTProfibusScanIdentSchema 26 11.4 Device type identification data types FDTProfibusDeviceIdentSchema .29 11.5 XSLT Transformation 30 Annex A (informative) Example documents for a DTM representing a Remote I/O43 Bibliography46 Figure 1 Part 503-1 of the IEC 62453 series 6
22、 Figure 2 Example: Device DTM9 Figure 3 Example: Gateway DTM.10 Figure 4 Example: Modular DTM11 PD CLC/TR 62453-503-1:2009TR 62453-503-1 IEC:2009(E) 3 Figure 5 Example: Modular Gateway DTM .12 Figure 6 Interfaces and information related to bus master configuration.13 Figure 7 User changes the config
23、uration of a device in the DTMs user interface 14 Figure 8 Error case: DTM refuses the new BMCP from the frame.14 Table 1 Protocol specific usage of general data types15 PD CLC/TR 62453-503-1:2009 6 TR 62453-503-1 IEC:2009(E) INTRODUCTION This part of IEC 62453 is an interface specification for deve
24、lopers 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 clients by multiple vendors that need to
25、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 planning- or engineering tools. In par
26、ticular, 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 component, called DTM (Device Type Manag
27、er), 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 requirements for integrating different k
28、inds of devices into heterogeneous control systems. Figure 1 shows how IEC/TR 62453-503-1 is aligned in the structure of IEC 62453 series. Part 503-1Communicationimplementationfor common object model IEC 61784 CP 3/1and CP 3/2Figure 1 Part 503-1 of the IEC 62453 series PD CLC/TR 62453-503-1:2009TR 6
29、2453-503-1 IEC:2009(E) 7 FIELD DEVICE TOOL (FDT) INTERFACE SPECIFICATION Part 503-1: Communication implementation for common object model IEC 61784 CP 3/1 and CP 3/2 1 Scope IEC 62435-503-1, which is a technical report, provides information for integrating the PROFIBUS protocol into the FDT interfac
30、e specification (IEC 62453-2). This part of IEC 62453 specifies communication and other services. This specification neither contains the FDT specification nor modifies it. 2 Normative references The following referenced documents are indispensable for the application of this specification. For date
31、d references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies IEC 61158 (all parts), Industrial communication networks Fieldbus specifications IEC 62453-1:2009, Field Device Tool (FDT) interface specification Pa
32、rt 1: Overview and guidance IEC 62453-2:2009, Field Device Tool (FDT) interface specification Part 2: Concepts and detailed description IEC/TR 62453-41:2009 Field Device Tool (FDT) interface specification Part 41: Object model integration profile Common object model IEC 62453-303-1:2009 Field Device
33、 Tool (FDT) interface specification Part 303-1: Communication profile integration - IEC 61784 CP 3/1 and CP 3/2 3 Terms, definitions, symbols, abbreviated terms and conventions 3.1 Terms and definitions For the purpose of this document, the terms and definitions given in IEC 62453-1 and IEC 62453-2
34、apply. 3.2 Symbols and abbreviated terms For the purpose of this document, the symbols and abbreviations given in IEC 62453-1, IEC 62453-2 and the following apply. UML Unified Modelling Language ISO/IEC 19501 PD CLC/TR 62453-503-1:2009 8 TR 62453-503-1 IEC:2009(E) 3.3 Conventions 3.3.1 Data type nam
35、es and references to data types The conventions for naming and referencing 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”
36、 or “Recommended” Strong recommendation. It may make sense in special exceptional cases to differ from the described behavior. Usage of “can or “Optional Function or behavior may be provided, depending on defined conditions. 4 Bus category IEC 61784 CP 3/1 and CP3/2 protocols are identified in the a
37、ttribute busCategory of BusCategory element by the identifiers, as specified in IEC 62453-303-1. IEC 61784 CPF 3 protocols are using the identifiers in physicalLayer members within PhysicalLayer data type as specified in IEC 62453-303-1. 5 Access to instance and device data Used at methods: IDtmPara
38、meter:GetParameters() IDtmParameter:SetParameters() These methods shall provide access to at least to all parameters defined in IEC 62453-303-1. 6 Protocol specific behavior 6.1 General A DTM shall deliver its GSD information via method IDtmInformation:GetInformation() and IDtmParameter:GetParameter
39、s(). GSD information is provided in the attribute . Also it is required to provide a GSD file for each supported device type on the hard drive. The attribute in the DTMParameter document specifies the location of the GSD file. It is expected that a Profibus DTM in the attribute deviceTypeInformation
40、 is exposing exactly the GSD file which is referenced by the attribute deviceTypeInformationPath. If the GSD depends on bus settings, a DTMs configuration or parameterization dialog could be used to change bus settings. Based on these settings, updated GSD information can be inserted in the informat
41、ion document. Here too the DTM has to call IFdtContainer:SaveRequest() and IDtmEvents:OnParameterChanged(). PD CLC/TR 62453-503-1:2009TR 62453-503-1 IEC:2009(E) 9 Notice that the internal device structure () with its modules and channels has to be updated as well. An example for documents of a DTM r
42、epresenting a remote I/O can be found in Annex A. 6.2 Representing modularity 6.2.1 Monolithic DTMs Monolithic DTMs should always provide at least one element. A monolithic DTM that represents a modular device shall provide the structure information as part of the element. The IO values of the devic
43、e are represented by Process Channels, which are referenced by child elements of the elements. If any of the modules provides communication, the respective element shall reference a Communication Channel. Example 1: A monolithic DTM for a PROFIBUS PA device will provide the information about instant
44、iated modules in the element. Each instantiated module will be represented as a element. (Be aware: it is necessary to define an element for each element.) The IO values of the modules are represented as Process Channels, which are referenced by child elements of the elements. (see Figure 2) DTMProc
45、essChannelFigure 2 Example: Device DTM This means: The DTM shall provide an internal topology in the parameter document to inform the frame about the internal structure of the device. The internal topology shall also include the module structure (element ). The DTM shall provide all channels in the
46、channel collection based on the current configuration. When the DTM changes the configuration of the process data or the module configuration the Process Channels shall be updated. This means Process Channels shall be removed/added and the parameter document shall be updated (e.g. by adding/removing
47、 elements) if necessary. Each channel is represented by a channel reference that is child of a element in the parameter document. Each channel object delivers a document based on the FDTProfibusChannelParameterSchema in IFdtChannel:GetChannelParameters() for the supported protocol. Example 2: A mono
48、lithic Gateway DTM for a remote I/O system, which requires PROFIBUS communication and has some PD CLC/TR 62453-503-1:2009 10 TR 62453-503-1 IEC:2009(E) modules, which provide HART communication will provide Communication Channels for HART modules that are also Process Channels and “pure” Process Cha
49、nnels for non-HART modules. (see Figure 3) DTMCombinedProcessandCommunicationChannelProcessChannelFigure 3 Example: Gateway DTM This means: The DTM shall provide all channels in the channel collection based on the current configuration. When the DTM changes the configuration of the process data or the module configuration the Process Channels shall be updated. This means Process Channels shall be removed/added and the p
