ANSI ISA 62453-302-2011 Field device tool (FDT) interface specification C Part 302 Communication profile integration C IEC 61784 CPF 2 (103.00.04).pdf

《ANSI ISA 62453-302-2011 Field device tool (FDT) interface specification C Part 302 Communication profile integration C IEC 61784 CPF 2 (103.00.04).pdf》由会员分享，可在线阅读，更多相关《ANSI ISA 62453-302-2011 Field device tool (FDT) interface specification C Part 302 Communication profile integration C IEC 61784 CPF 2 (103.00.04).pdf（42页珍藏版）》请在麦多课文档分享上搜索。

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

2、ofile integration IEC 61784 CPF 2 ISBN: 978-0-876640-58-6 Copyright 2011 IEC and ISA. These materials are subject to copyright claims of IE C 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-302 (103.00.04)-2011 Standard should be submitted to ISA. ISA 67 Alexander Drive P.O. Box 12277 Research Triangle Park, North Carolina 27709ANSI/ISA62453-302 (103.00.04)2011 - 3 - Preface This preface, as well as all footnotes and annexes, is included for in

4、formation purposes and is not part of ANSI/ISA62453-302 (103.00.04)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

5、 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 St

6、andards 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 standar

7、ds 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 re

8、ports 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 IP address for EtherNet/IP. Since the size differs from protocol to protocol, structure is used which contains 2 attributes: exte

9、nded identifier (n bytes string) and short identifier (1 byte unsigned integer) and only one of them shall be used choice of M 11 ExtendedIdentifier S 11 ShortIdentifier S 11 ANSI/ISA62453-302 (103.00.04)2011 - 17 - Data type Definition Description Elementary data type Usage Multiplicity CIPObjectAd

10、dress STRUCT CIP object address as CIPObjectId, CIPSymbolicAddress or HexAddress choice of M 11 CIPObjectId S 11 CIPSymbolicAddress S 11 HexAddress S 11 CIPObjectId STRUCT The CIP classId, instanceId and (conditional) attributeId address information for a CIP object and attribute. If used in a Proce

11、ss Channel this is likely to be either an Assembly object or a Parameter object classId M 11 instanceId M 11 attributeId O 01 CIPPath STRUCT The full address of the CIP node (device). In general this consists of the Node ID stored in the CIPNodeID element. The RoutingPath element is used to transfer

12、 additional routing information that can be used by the CIP FDT communication component RoutingPath O 01 CIPNodeID M 11 CIPSymbolicAddress STRUCT classId, instanceId and attributeId does not necessarily be known, a symbolic address could also be used. CIPSymbolicAddress, HexAddress or CIPObjectId co

13、uld be used for DataExchangeRequest symbolicAddress M 11 Constant STRUCT A constant value constValue M 11 ExtendedIdentifier STRUCT See attribute extendedIdentifier extendedIdentifier M 11 HexAddress STRUCT CIP object address as ePath ePath O 01 LinkAddress STRUCT Represents the CIPNodeID within a S

14、egment CIPNodeID M 11 ParameterReference STRUCT Reference to a description of a parameter fdt:idref M 11 bitOffset O 01 ReservedBits STRUCT Used wherever reserved bits are needed ANSI/ISA62453-302 (103.00.04)2011 - 18 - Data type Definition Description Elementary data type Usage Multiplicity Routing

15、Path STRUCT Any additional CIP network routing information, which can be understood by the Communication Channel Segment M 11 Segment STRUCT Represents the path a message shall follow to reach the addressed CIP device portNumber M 11 LinkAddress M 11 Segment O 01 Service STRUCT CIP service identifie

16、d by serviceCode and serviceName. CIP service code. This is a function, or method, supported by a CIP object or attribute serviceCode M 11 serviceName O 01 ShortIdentifier STRUCT See attribute shortIdentifier shortIdentifier M 11 9 Network management data types 9.1 General The data types specified i

17、n this clause are used at following services: NetworkManagementInfoRead service; NetworkManagementInfoWrite service. 9.2 Node address The CIPNodeID will be stored in the busAddress element of the fdt:DeviceAddress data type. This is not used for CompoNet because the master has a fixed address since

18、this is a mandatory element, the recommendation is to use the value “0”. 9.3 Scanner/master Bus parameter set (CIP) Information is sent to the CIP scanner/master within the UserDefinedBus element of the NetworkInfo data type, using the data types specified in Table 5 and Table 6. This information sh

19、all be set to configure the scan list of scanner/master. The data types described in this clause are defined for following namespace: Namespace: cippar ANSI/ISA62453-302 (103.00.04)2011 - 19 - Table 5 Simple fieldbus configuration data types Data type Definition Description async USINT See Table 7-2

20、.3 of 13. This is a CIP Safety exclusive field. Only applies to producing connections. Field should be empty for consuming connections. Used to calculate Network Reaction Time base UINT Scaling parameters. See A.4.1.4.6 of ISO 15745-2 class0 BOOL See Table A.25 of ISO 15745-3 class1 BOOL class2 BOOL

21、 class3 BOOL class4 BOOL class5 BOOL class6 BOOL compoNetDeviceCategory USINT Defines the different categories of CompoNet devices. See 14, Chapter 7-4 compoNetIOLength UINT See 14, Chapter 7-5 compoNetIOLengthUnit USINT connectionNameString STRING See Table A.24 of ISO 15745-3 connectionTypeMultica

22、st BOOL See Table A.26 of ISO 15745-3 connectionTypeNULL BOOL connectionTypePoint2Point BOOL consumedConnectionSize UINT Maximum number bytes received across this connection defaultConnection BOOL Indicates whether the CIPConnection is default or not defaultSafetyConnections USINT See Table 7-2.2 of

23、 13. Instance Number defaultValue STRING Represents the value of the attribute when in offline state div UINT Scaling parameters. See A.4.1.4.6 of ISO 15745-2 expectedPacketRate UINT Scanner determines this parameter. There might be some reason that the slave provides this parameter to the master fi

24、xedSizeSupported BOOL See Table A.26 of ISO 15745-3 helpString STRING See Table A.24 of ISO 15745-3 inhibitTime UINT Optional for COS, for other connection types it is not valid. Scanner determines this parameter. There might be some reason that the slave provides this parameter to the master maxCIP

25、Connections UINT Communication capacity, See Chapter 7-3.6.11.7 of 9 maxConsumerNumber USINT See Table 7-2.3 of 13. This is a CIP Safety exclusive field. When safety devices wish to define multi-cast connections and need to restrict the maximum number of consumers to a value less than the default ma

26、ximum of 15, this field can define the product limit. If this field is empty, the SNCT shall always use the default value of 15 for the maximum number of multi-cast connections. This field can be left empty for single-cast connections maxEMConnections UINT Communication capacity. See Chapter 7-3.6.1

27、1.7 of 9 maxIOConnections UINT maxSafetyConnections USINT See Table 7-2.2 of 13. Optional ANSI/ISA62453-302 (103.00.04)2011 - 20 - Data type Definition Description maxSafetyInputCnxns USINT maxSafetyOutputCnxns USINT multiplier UINT Scaling parameters. See A.4.1.4.6 of ISO 15745-2 offset INT precisi

28、on UINT priorityHigh BOOL See Table A.26 of ISO 15745-3 priorityLow BOOL priorityScheduled BOOL producedConnectionSize UINT Maximum number of bytes transmitted across this connection realTimeTransferFormat USINT See Table A.26 of ISO 15745-3 rpi UDINT See Table A.24 of ISO 15745-3 scId ARRAY OF USIN

29、T Safety Configuration Identifier. See 6.6.5.17 of IEC 61784-3-2 server BOOL See Table A.25 of ISO 15745-3 transportTypeExclusiveOwner BOOL transportTypeInputOnly BOOL transportTypeListenOnly BOOL transportTypeRedundantOwner BOOL triggerApplication BOOL triggerChangeOfState BOOL triggerCyclic BOOL u

30、nId ARRAY OF USINT See 6.6.5.18 of IEC 61784-3-2 variableSizeSupported BOOL See Table A.26 of ISO 15745-3 ANSI/ISA62453-302 (103.00.04)2011 - 21 - Table 6 Structured fieldbus configuration data types Data type Definition Description Elementary data types Usage Multiplicy AssemblyMemberDefinition STR

31、UCT Represents all members of an assembly fdt:id O 01 fdt:tag M 11 fdt:descriptor O 01 cip:dataType M 11 defaultValue O 01 Scaling O 01 cip:CIPObjectAddress O 01 fdt:BitEnumeratorEntries O 01 fdt:EnumeratorEntries O 01 fdt:Unit O 01 fdt:Ranges O 01 fdt:SubstituteValue O 01 AssemblyMemberDefinitions

32、STRUCT See AssemblyMember definition AssemblyMemberDefinition O 0* BitStrobeConnection STRUCT Represents the Bitstrobe IO connection MasterSlaveConnection M 11 Capacity STRUCT Communication capacity, See Chapter 7-3.6.11.7 of 9 MaxCIPConnections O 01 MaxIOConnections O 01 MaxEMConnections O 01 ANSI/

33、ISA62453-302 (103.00.04)2011 - 22 - Data type Definition Description Elementary data types Usage Multiplicy CIPConnection STRUCT Defines one supported CIP connection Contains attributes, see Table A.24 of ISO 15745-3 For safety devices, see Chapter 7-2.2.4.3, Table 7-2-3 of 13 connectionNameString M

34、 11 helpString M 11 cip:ePath M 11 defaultConnection O 01 Config1 O 01 Config2 O 01 TriggerAndTransport M 11 Originator2TargetParameters M 11 Target2OriginatorParameters M 11 CIPNode STRUCT Represents all connection information of the device fdt:readAccess O 01 fdt:writeAccess O 01 fdtpar:configurat

35、ionData O 01 scId O 01 unId O 01 cip:CIPDeviceIdentity M 11 cip:CIPNodeID M 11 PossibleConnections M 11 CurrentConnections M 11 AssemblyMemberDefinitions O 01 CompoNetIO STRUCT Defines the IO of a CompoNet device. See 14, Chapter 7-2 CompoNetInputInfo O 01 CompoNetOutputInfo O 01 compoNetDeviceCateg

36、ory M 11 CompoNetInputInfo STRUCT Represents the Inputs of the CompoNet device CompoNetIOInfo M 11 CompoNetIOInfo STRUCT Represents the Inputs or Outputs of the CompoNet device compoNetIOLengthUnit M 11 compoNetIOLength M 11 ANSI/ISA62453-302 (103.00.04)2011 - 23 - Data type Definition Description E

37、lementary data types Usage Multiplicy CompoNetOutputInfo STRUCT Represents the Outputs of the CompoNet device CompoNetIOInfo M 11 Config STRUCT Contains elements Size and Format Size O 01 Format O 01 Config1 STRUCT See Table A.24 of ISO 15745-3 Config M 11 Config2 STRUCT See Table A.24 of ISO 15745-

38、3 Config M 11 ConnectionParameters STRUCT Represents the Connection Parameters keyword of the Connection Manager Section of an EDS-file. See A.4.1.4.9 of ISO 15745-3 FixedSizeSupported O 01 VariableSizeSupported O 01 RealTimeTransferFormat O 01 ConnectionTypeNULL O 01 ConnectionTypeMulticast O 01 Co

39、nnectionTypePoint2Point O 01 PriorityLow O 01 PriorityHigh O 01 PriorityScheduled O 01 cip:ReservedBits O 01 ConsumedAssemblyReference STRUCT Gives CIPObjectAddress of the data consumed on this IO connection To reference what is the I/O assembly attached to this connection to allow the scanner to un

40、derstand the members of the consumed assembly cip:CIPObjectAddress M 11 COSConnection STRUCT Represents the COS IO connection. It is mutual exclusive with the Cyclic IO connection MasterSlaveConnection M 11 CurrentConnections STRUCT Represents all default connections of this device. CIPConnection O

41、0* MasterSlaveConnectionSet O 01 ANSI/ISA62453-302 (103.00.04)2011 - 24 - Data type Definition Description Elementary data types Usage Multiplicy CompoNetIO O 01 CyclicConnection STRUCT CyclicConnection Represents the Cyclic IO connection. It is mutual exclusive with the COS IO connection MasterSlav

42、eConnection M 11 Format STRUCT See Table A.24 of ISO 15745-3 choice of M 11 cip:ParameterReference S 11 fdt:ChannelReference S 11 MasterSlaveConnection STRUCT Defines one supported MasterSlave connection producedConnectionSize M 11 consumedConnectionSize M 11 expectedPacketRate O 01 inhibitTime O 01

43、 ConsumedAssemblyReference O 01 ProducedAssemblyReference O 01 MasterSlaveConnectionSet STRUCT Zero or more MasterSlaveConnection. MasterSlaveConnection elements can be combined according to the CIP specification (see IEC 62026-3). This element shall be provided for DeviceNet. If device does not sup

44、port I/O connections through the MasterSlave connection set, this list shall be empty PolledIOConnection O 01 BitStrobeConnection O 01 choice of O 01 COSConnection S 11 CyclicConnection S 11 MulticastPollingConnection O 01 MulticastPollingConnection STRUCT Represents the Multicast Polled IO connecti

45、on MasterSlaveConnection M 11 ANSI/ISA62453-302 (103.00.04)2011 - 25 - Data type Definition Description Elementary data types Usage Multiplicy Originator2TargetParameters STRUCT Originator to target connection parameters. See Table A.24 of ISO 15745-3 rpi O 01 ConnectionParameters M 11 choice of M 1

46、* Size S 11 Format S 11 PolledIOConnection STRUCT Represents the Polled IO connection MasterSlaveConnection M 11 PossibleConnections STRUCT Represents all possible connections that can be made to this device maxSafetyConnections O 01 maxSafetyInputCnxns O 01 maxSafetyOutputCnxns O 01 defaultSafetyCo

47、nnections O 01 Capacity O 01 CIPConnection O 0* PolledIOConnection O 01 BitStrobeConnection O 01 COSConnection O 01 CyclicConnection O 01 MulticastPollingConnection O 01 SafetyInputConnection O 0* SafetyOutputConnection O 0* CompoNetIO O 01 ProducedAssemblyReference STRUCT Gives CIPObjectAddress of

48、the data produced on this IO connection To reference what is the I/O assembly attached to this connection to allow the scanner to understand the members of the produced assembly cip:CIPObjectAddress M 11 ANSI/ISA62453-302 (103.00.04)2011 - 26 - Data type Definition Description Elementary data types Usage Multiplicy Target2OriginatorParameters STRUCT Target to originator connection parameters. See Table A.24 of ISO 15745-3 rpi O 01 ConnectionParameters M 11 choice of M 1* Size S 11 Format S 11 TransportTypeEx