ANSI ISA 62453-303-1-2011 Field device tool (FDT) interface specification C Part 303-1 Communication profile integration C IEC 61784 CP 3 1 and CP 3 2 (103.00.05)《现场设备工具(FDT)接口规范.第.pdf

《ANSI ISA 62453-303-1-2011 Field device tool (FDT) interface specification C Part 303-1 Communication profile integration C IEC 61784 CP 3 1 and CP 3 2 (103.00.05)《现场设备工具(FDT)接口规范.第.pdf》由会员分享，可在线阅读，更多相关《ANSI ISA 62453-303-1-2011 Field device tool (FDT) interface specification C Part 303-1 Communication profile integration C IEC 61784 CP 3 1 and CP 3 2 (103.00.05)《现场设备工具(FDT)接口规范.第.pdf（74页珍藏版）》请在麦多课文档分享上搜索。

1、 AMERICAN NATIONAL STANDARD ANSI/ISA62453-303-1 (103.00.05)-2011 Field device tool (FDT) interface specification Part 303-1: Communication profile integration IEC 61784 CP 3/1 and CP 3/2 Approved 31 May 2011 ANSI/ISA62453-303-1 (103.00.05)-2011, Field Device Tool (FDT) Interface Specification Part 3

2、03-1: Communication profile integration IEC 61784 CP 3/1 and CP 3/2 ISBN: 978-0-876640-59-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 pri

3、or written permission of ISA. All requests pertaining to the ANSI/ISA62453-303-1 (103.00.05)-2011 Standard should be submitted to ISA. ISA 67 Alexander Drive P.O. Box 12277 Research Triangle Park, North Carolina 27709 ANSI/ISA62453-303-1 (103.00.05)-2011 - 3 - Preface This preface, as well as all fo

4、otnotes and annexes, is included for information purposes and is not part of ANSI/ISA62453-303-1 (103.00.05)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 sho

5、uld be subject to periodic review. Toward 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-8

6、288; E-mail: standardsisa.org. The ISA 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

7、 the benefits to USA users of ISA standards 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

8、, recommended practices, and technical 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 RS 485 (ANSI TIA/EIA RS-485-A); optional RS 485-IS; plastic fiber; glass multi mode fibe

9、r or glass single mode fiber; PCF fiber 3.1.2 CP 3/2 Communication profile of CPF3, featuring synchronous transmission; manchester coded and bus powered (MBP); optional intrinsically safe (MBP-IS) and lower power (MBP-LP) 3.2 Symbols and abbreviated terms For the purposes of this document, the symbo

10、ls and abbreviations given in IEC ISA-62453-1 (103.00.01), IEC ISA-62453-2 (103.00.02) and the following apply. BIM Bus Interface Module BMCP Bus Master Configuration Part GSD General Station Description 3.3 Conventions 3.3.1 Data type names and references to data types The conventions for naming an

11、d referencing of data types are explained in IEC ISA-62453-2 (103.00.02), Clause A.1 ANSI/ISA62453-303-1 (103.00.05)-2011 - 15 - 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”

12、 or “recommended” Strong recommendation. It may make sense in special 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 the UML notation as d

13、efined in Annex A of IEC ISA-62453-1 (103.00.01). 4 Bus category CP 3/1 and CP 3/2 protocols are identified in the protocolId element of the structured data type fdt:BusCategory by the following unique identifiers (Table 1): Table 1 Protocol identifiers Identifier value ProtocolId name Description 0

14、36D1497-387B-11D4-86E1-00E0987270B9 Profibus DP/V0 Support of Profibus DP V0 protocol 036D1499-387B-11D4-86E1-00E0987270B9 Profibus DP/V1 Support of Profibus DP V1 protocol CP 3/1 AND CP 3/2 protocols are using the following unique identifiers in physicalLayer members within PhysicalLayer data type

15、(Table 2): Table 2 Physical layer identifiers Identifier value Description 036D1590-387B-11D4-86E1-00E0987270B9 IEC 61158-2 (Profibus PA) 036D1591-387B-11D4-86E1-00E0987270B9 RS485 036D1592-387B-11D4-86E1-00E0987270B9 Fiber 036D1593-387B-11D4-86E1-00E0987270B9 Ethernet 5 Access to instance and devic

16、e data 5.1 Process Channel objects provided by DTM The minimum set of provided data should be: Process values modelled as channel objects including the ranges and scaling ANSI/ISA62453-303-1 (103.00.05)-2011 - 16 - 5.2 DTM services to access instance and device data The services InstanceDataInformat

17、ion and DeviceDataInformation shall provide access to at least all parameters of the Physical Block and the status and Out value of the Function Blocks shall be exposed. According to IEC ISA-62453-2 (103.00.02), at least one set of semantic information (one per supported fieldbus protocol) shall be

18、provided for each accessible data object, using the SemanticInformation general data type. The corresponding data type applicationDomain shall have a value defined for Profibus and the data type semanticId shall have an appropriate value, as specified in Table 9. 6 Protocol specific behavior 6.1 PRO

19、FIBUS device model FDT extends the PROFIBUS device model by using Process Channels for description of I/O values (see Figure 2). ANSI/ISA62453-303-1 (103.00.05)-2011 - 17 - Figure 2 FDT PROFIBUS device model 6.2 Configuration and parameterization of PROFIBUS devices 6.2.1 General In a GSD-based conf

20、iguration tool the user defines the configuration and sets the appropriate parameters for the modules. The configuration tool creates the configuration string and the parameter string that are used to set up the slave properly. With FDT the configuration and parameterization of the devices is no lon

21、ger executed only by a central component; it moved partly into the DTMs. A DTM is responsible for pr oviding configuration and parameterization information for the cyclic master that puts the PROFIBUS slaves in operation. IEC 1128/09 ANSI/ISA62453-303-1 (103.00.05)-2011 - 18 - A DTM is used to adjus

22、t a field device to its specific application. Within PROFIBUS, there are three different aspects of adjustment: parameterization: usr prm data (used in the PROFIBUS service SET_PRM for setting up the cyclic communication and the specific behavior of the device); application parameterization: applica

23、tion specific parameters (transmitted via acyclic read/write PROFIBUS services); configuration: configuration data (used in the PROFIBUS service CHK_CFG for definition of the format and length of the input/output data that are transmitted within cyclic communication). The application parameterizatio

24、n transmitted via acyclic communication is not in the scope of this document. Within this document the term parameterization represents communication parameterization (SET_PRM). 6.2.2 Monolithic DTM for a modular PROFIBUS device A monolithic DTM is one single DTM that represents the complete device

25、with its Bus Interface Module (BIM) and its I/O modules. In general, such a DTM offers a configuration dialog (presentation object) that allows definition of the used BIM and modules. The configuration dialog must be available via the FDT standard function “Configure” (see 1 4.3 Operation Configurat

26、ion). Not all PROFIBUS devices require a configuration dialog. That is why not all DTMs provide the “Configure” function. This is valid only for non-modular PROFIBUS devices if the Usr_Prm-Data cannot be changed. The configuration dialog allows changing the data only in offline mode if the data set

27、can be locked. 6.2.3 Modular DTM for a modular PROFIBUS device Separate DTMs represent the BIM (Device DTM) and the particular I/O modules (Module DTMs). The effort developing such a modular DTM is normally higher than in the case of a monolithic DTM, because: a private protocol has to be implemente

28、d between BIM and I/O modules to ensure that only a Module DTM can be added to the BIM DTM. This requires an own protocol ID and the adaptation / creation of communication; in some cases, additional private interfaces are necessary to exchange information between Device DTM for BIM and Module DTMs.

29、Implementing a Modular DTM results in the following advantages: the project represents the device structure; the user is able to access module-related information directly as a function of the Module DTM; the FDT specification defines a mechanism to identify DTMs. With these mechanisms it is possibl

30、e to provide support for scanning the modules below the BIM and generate the topology automatically; supporting a new type of BIM or I/O module requires an additional DTM “only” and does not affect existing components. This may result in reduced test effort. ANSI/ISA62453-303-1 (103.00.05)-2011 - 19

31、 - The configuration data to set up the PROFIBUS configuration must be provided by the Device DTM (representing the BIM). This configuration data may be generated from information of the instantiated Child DTMs and by using a configuration dialog. Modular DTMs should be provided for modular devices

32、(e.g. a plant operator may add/remove modules). Monolithic DTMs are used to represent devices that show no modularity (e.g. PA devices). 6.3 Support for DPV0 configuration A PROFIBUS slave is configured by a cyclic master and communicates via PROFIBUS DP. In addition to this the slave may support DP

33、V1 communication. A Gateway DTM for a PROFIBUS slave does not have to provide communication for the DPV0 communication schema. For example, there is a remote I/O system with HART modules. It may have a Gateway DTM that requires the DPV1 protocol and provides the HART protocol (defined in the informa

34、tion document and in the parameter document). This enables HART Device DTMs to communicate with their devices via the Gateway DTM and via Communication DTM for DPV1. Following the specification the Gateway DTM delivers channel parameter documents for both protocols DPV1 and HART. The protocolId is a

35、 member of NetworkManagementInfo data type. The Process Channels must provide ChannelParameter documents for DPV1 including all information to allow integration into the control system (e.g. DPAddress of the IO value if available). 6.4 PROFIBUS slaves operating without a cyclic PROFIBUS master In mo

36、st cases, a PROFIBUS slave is configured and parameterized by a cyclic PROFIBUS master device. So a running master device in the network is required. Some slaves are able to allow acyclic communication without a running cyclic master. Especially in the case of gateway functionality this is an eminen

37、t advantage because they allow the parameterization of field devices connected to them by using an acyclic bus master. So instrument specialists are able to work with field devices also in case the controller is not yet working. If a master starts communication, these devices start to detect bus spe

38、ed and settings to react properly. This may take some time. In the following, two cases are described that a user may keep in mind when working with such devices. Use Case 1: The user performs a network scan. The Communication DTM tries to read diagnostic data via a GetDiagnose Request but does not

39、receive a response. The device is not detected by the Communication DTM. This occurs mostly when the device has a low PROFIBUS address. The reason is that the device has not completed bus speed / bus setting detection as it was asked for their diagnostic data. The workaround is to give these devices

40、 a higher PROFIBUS address. Use Cases 2: ANSI/ISA62453-303-1 (103.00.05)-2011 - 20 - The user tries to connect a field device linked to the gateway that supports DPV1 without a running cyclic master. This can lead to an error message because the gateway device has not completed bus speed / bus setti

41、ng detection as it was asked for a connection. So the user has to try to connect again. This happens only in very rare situations. 6.5 PROFIBUS-related information of a slave DTM 6.5.1 General The information used by a cyclic master device to set up the PROFIBUS network properly and allow cyclic com

42、munication between control system and slave devices is provided by a DTM in Bus Master Configuration Part (BMCP); GSD information; internal topology, process channels. A DTM of a PROFIBUS slave must deliver these parts of PROFIBUS-related information to get integrated into a FDT-based Engineering Sy

43、stem. In the next subclauses, a more detailed description is given on how to generate and how to provide this information. This depends on the kind of DTM (see 6.2 Configuration and parameterization of PROFIBUS devices). 6.5.2 Bus Master Configuration Part (BMCP) 6.5.2.1 BMCP introduction The BMCP o

44、f one single DTM instance describes the actual parameter and configuration data of the corresponding PROFIBUS slave. Each DTM representing a PROFIBUS slave device must provide a Bus Master Configuration Part. The BMCP is provided in the busMasterConfigurationPart member of NetworkManagementInfo data

45、 type. This information is obtained by calling service NetworkManagementInfoRead. The BMCP includes information about the configuration and the parameters for the slave. The BMCP is provided by the DTM and is required in order to generate the master configuration. The BMCP contains data which might

46、be changed during master configuration. That means that the BMCP may be changed and transferred back to the slave DTM by calling NetworkManagementInfoWrite. A Slave DTM must accept the new information and recompute the configuration / internal parameters to match the new BMCP. DTM must check whether

47、 the new values are according to the capabilities of the device. The NetworkManagementInfoWrite call will be refused if the device can not handle the new values. 6.5.2.2 Creating the BMCP This subclause explains the meaning of the individual elements of the BMCP in details. The BCMP may be generated

48、 from the GSD information of a PROFIBUS device. The BMCP is divided into four parts that are explained in the following subclauses. ANSI/ISA62453-303-1 (103.00.05)-2011 - 21 - The explanations use the GSD keywords and reference the PROFIBUS specification. See also the table with complete BMCP in 6.5

49、.2.2.1. 6.5.2.2.1 Part 1: From Slave_Para_Len to Octet 15 The first part consists of a fixed set of bytes described in the table b elow. Table 3 BMPC Part1 General configuration Byte Name Defined in Notice 0 Slave_Para_Len 5 6.2.12.1 Length of the BMCP including this value 1 2 Sl_Flag 5 6.2.12.2 The following GSD values are used 6: Bit 0 : reserved, Bit 1: Extra_Alarm_SAP, Bit 2: DPV1_Data_Types, Bit 3: DPV1_Supported, Bit 4: Publisher_Enable, Bit 5 : Fail_Safe, . The following bits are not based on