1、 AMERICAN NATIONAL STANDARD ANSI/ISA62453-315 (103.00.09)2011 Field device tool (FDT) interface specification Part 315: Communication profile integration IEC 61784 CPF 15 Approved 3 June 2011 ANSI/ISA62453-315 (103.00.09)-2011, Field device tool (FDT) interface specification - Part 315: Communicatio
2、n profile integration IEC 61784 CPF 15 ISBN: 978-0-876640-63-0 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.
3、 All requests pertaining to the ANSI/ISA62453-315 (103.00.09)-2011 Standard should be submitted to ISA. ISA 67 Alexander Drive P.O. Box 12277 Research Triangle Park, North Carolina 27709 ANSI/ISA62453-315 (103.00.09)2011 - 3 - Preface This preface, as well as all footnotes and annexes, is included f
4、or informati on purposes and is not part of ANSI/ISA62453-315 (103.00.09)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.
5、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-8288; E-mail: standardsisa.org. The
6、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 the benefits to USA users of ISA s
7、tandards 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 techni
8、cal 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 unconfirmed private Modbus requests. 6.2 Broadcasting In broadcast mode, a DTM can send a Modbus request to all devices con
9、nected to the bus. This mode is only supported for devices, which are connected via Modbus Serial Line. The connection can either be a direct connection or a connection via a gateway. The broadcast mode must be initiated by a fdtmodbus:ConnectRequest with the slave address of the target device set t
10、o 0 (slaveAddress=0). For more detailed information about the address information which has to be provided for broadcast mode, see Table 2. Table 2 Address information for broadcast mode Data type Definition Description Elementary data types Usage Multiplicity ModbusSerial STRUCT Address information
11、 for Modbus Serial Line slaveAddress M 11 Shall be 0 for broadcast mode ModbusTCP STRUCT Address information for Modbus TCP: slaveAddress M 11 Shall be 0 for broadcast mode tcpAddress M 11 IP address of the Modbus TCP/ Modbus Serial Line gateway tcpPort O 01 Port for Modbus TCP connection (if no por
12、t information is provided, the default port 502 shall be used) Because in broadcast mode no response will be returned by the device, the broadcast mode shall be used only with the transaction requests shown in Table 3: ANSI/ISA62453-315 (103.00.09)2011 - 18 - Table 3 Broadcast transaction requests B
13、roadcast transaction requests Restrictions WriteSingleCoilReq None WriteSingleRegisterReq None DiagnosticsReq This transaction request shall be used in broadcast mode only with the following sub-functions: - 0x01: Restart Communication Option - 0x03: Change ASCII Input Delimiter - 0x04: Force Listen
14、 Only Mode - 0x0A: Clear Counters and Diagnostic Register - 0x14: Clear Overrun Counter and Flag WriteMultipleCoilsReq None WriteMultipleRegistersReq None WriteFileRecordReq None MaskWriteRegisterReq None PrivateModbusReq Shall be used only with private services where no response is required from th
15、e device Although in broadcast mode no response will be returned by the target devices a transaction response, which corresponds to the transaction request shall be generated. This transaction response shall be generated in order to inform the DTM that the broadcast request was sent on the bus. If a
16、 Modbus Communication DTM is used to establish the communication, it has to provide this generated transaction response (see Figure 2 and Figure 3). Figure 2 Broadcast sequence with Modbus Serial Line Communication DTM IEC 1137/09 ANSI/ISA62453-315 (103.00.09)2011 - 19 - Figure 3 Broadcast sequence
17、with Modbus TCP Communication DTM If no Modbus Communication DTM is used to establish the communication, the Modbus Gateway DTM, which provides the link to the higher communication level different from Modbus, has to provide this transaction response (see Figure 4). IEC 1138/09 ANSI/ISA62453-315 (10
18、3.00.09)2011 - 20 - Figure 4 Broadcast sequence without Modbus Communication DTM 6.3 Unconfirmed private Modbus request This transaction request can be used to send any unconfirmed private Modbus request. Although no response will be returned by the target device, a transaction response, which corre
19、sponds to the transaction request, shall be generated. This transaction response shall be generated in order to inform the DTM that the unconfirmed request was sent on the bus. If a Modbus Communication DTM is used to establish the communication, it has to provide this generated transaction response
20、 (see Figure 5 and Figure 6). IEC 1139/09 ANSI/ISA62453-315 (103.00.09)2011 - 21 - Figure 5 Unconfirmed request with Modbus Serial Line Communication DTM Figure 6 Unconfirmed request with Modbus TCP Communication DTM IEC 1140/09 IEC 1141/09 ANSI/ISA62453-315 (103.00.09)2011 - 22 - If no Modbus Commu
21、nication DTM is used to establish the communication, the Modbus Gateway DTM, which provides the link to the higher communication level different from Modbus, has to provide this transaction response (see Figure 7). Figure 7 Unconfirmed request without Modbus Communication DTM 7 Protocol specific usa
22、ge of general data types The following table (Table 4) shows how general data types, defined in IEC ISA-62453-2 (103.00.02) within the namespace fdt, are used with IEC 61784 CPF 15 devices. Table 4 Protocol specific usage of general FDT data types Data type Description for use fdt:dataType Identifie
23、r for the FDT data type of the channel object fdt:busCategory See Clause 4 deviceTypeInformation Modbus device description in form of human readable string, which can be provided with a DTM deviceTypeInformationPath Path to file which contains the Modbus device description if available fdt:readAcces
24、s Specifies whether the value can be read from the device: “0”, if reading access is not allowed “1”, if reading access is allowed fdt:systemTag Unique identifier of a device instance within a project of a Frame Application fdt:writeAccess Specifies whether the value can be written to the device: “0
25、”, if writing access is not allowed “1”, if writing access is allowed IEC 1142/09 ANSI/ISA62453-315 (103.00.09)2011 - 23 - 8 Protocol specific common data type.00.02) 8.1 General This clause specifies protocol specific common data types which are used in the definition of other data types. 8.2 Addre
26、ss information This subclause specifies the structure and the semantics of the protocol specific address information in FDT, which is used on the different underlying communication layers for Modbus TCP and Modbus Serial Line. For a detailed description of how the address information is mapped to da
27、ta types, see Table 5 and Table 6. The data types described in this subclause are defined for the following namespace. Namespace: mb Table 5 Simple address information data types Data type Definition Description slaveAddress USINT Slave address of a Modbus device tcpAddress STRING String representat
28、ion of the IP address as described in RFC 791 Internet Protocol (IP) tcpPort UINT Port for Modbus TCP connection (if no port information is provided the default port 502 shall be used) Table 6 Structured address information data types Data type Definition Description Elementary data types Usage Mult
29、iplicity ModbusSerial STRUCT Address information for Modbus Serial Line slaveAddress M 11 ModbusTCP STRUCT Address information for Modbus TCP: IP address of the target Modbus TCP server Slave address of the target device if the Modbus TCP server provides routing services over Modbus Serial Line slav
30、eAddress O 01 tcpAddress M 11 tcpPort O 01 ANSI/ISA62453-315 (103.00.09)2011 - 24 - 9 Network management data types The data types described in this clause are used in the following services: NetworkManagementInfoRead service; NetworkManagementInfoWrite service. This clause describes the information
31、, which has to be provided for Modbus devices, in the UserDefinedBus data type (see Table 7). Table 7 Structured network management data types Data type Definition Description Elementary data types Usage Multiplicity UserDefinedBus STRUCT The UserDefinedBus data type contains the address information
32、 of the device. It is required that the UserDefinedBus data type contains at least one address information data type of the target device mb:ModbusSerial O 0* mb:ModbusTCP O 0* Some devices and their modules require more than one address on the bus. It is possible that the UserDefinedBus data type m
33、ay contain several address-elements. In this case, the first address element shall contain the information about the principal address of the device. 10 Communication data types 10.1 General The data types described in this clause are used in the following services: connect service; disconnect servi
34、ce; transaction service. This clause describes the structure and the semantics of the protocol specific communication related data, which is exchanged between a DTM and its parent component. For a detailed description of the common communication data types used in these services, see Table 8. The da
35、ta types described in this clause are defined for the following namespace. Namespace: fdtmodbus ANSI/ISA62453-315 (103.00.09)2011 - 25 - Table 8 Simple common communication data types Data type Definition Description communicationReference UUID Mandatory identifier for a communication link to a devi
36、ce This identifier is allocated by the communication component during the connect. The address information has to be used for all following communication calls 10.2 Connection management data types For a detailed description of the information used in the connect service and in the disconnect servic
37、e see Table 9. Table 9 Structured connection management service data types Data type Definition Description Elementary data types Usage Multiplicity Abort STRUCT If the Abort command is sent to the next communication component or to the connected device, it terminates all pending requests and return
38、s without waiting for a result. The termination of the connection will not be confirmed communicationReference O 01 ConnectRequest STRUCT Describes the communication request: to establish a communication link to a Modbus TCP server device; to establish a communication link to a Modbus Serial Line sl
39、ave device. The request contains the address information of the target device fdt:systemTag M 11 choice of M 11 mb:ModbusSerial S 11 mb:ModbusTCP S 11 ConnectResponse STRUCT Describes the communication response to the connect request communicationReference M 11 DisconnectRequest STRUCT Describes the
40、 communication request to release a communication link communicationReference M 11 DisconnectResponse STRUCT Describes the communication response to a disconnect request communicationReference M 11 ANSI/ISA62453-315 (103.00.09)2011 - 26 - 10.3 Transaction service specific data types 10.3.1 General T
41、his subclause describes the information which is used in the transaction services. 10.3.2 Data item addressing This document specifies the mapping of Modbus parameters to FDT data types. For this reason , all address information provided as parameters and concerning the Modbus data items coils, disc
42、rete inputs, holding registers and input registers, shall be the same information as will be later sent on the bus (see Figure 8). Figure 8 Data item addressing 10.3.3 Read coils transaction service The parameters of the transaction service, which is equivalent to the Read Coils service defined in I
43、EC 61158-5-15, are described in Table 10, Table 11, Table 12 and Table 13. IEC 1143/09 ANSI/ISA62453-315 (103.00.09)2011 - 27 - Table 10 Simple ReadCoilsReq data types Data type Definition Description Equivalent IEC 61158-5-15 service parameter startAddress UINT Address of the first coil to be read
44、Address of first coil quantity UINT Number of coils to be read Quantity of coils Table 11 Structured ReadCoilsReq data types Data type Definition Description Elementary data types Usage Multiplicity ReadCoilsReq STRUCT Communication request equivalent to the Read Coils service request defined in IEC
45、 61158-5-15 communicationReference M 11 quantity M 11 startAddress M 11 Table 12 Simple ReadCoilsRsp data types Data type Definition Description Equivalent IEC 61158-5-15 service parameter multipleCoilValues STRING ASCII string with each coil state coded in one character, where the first character i
46、n the string represents the first coil to be read: “0” = FALSE or “OFF” “1” = TRUE or “ON” Data Table 13 Structured ReadCoilsRsp data types Data type Definition Description Elementary data types Usage Multiplicity ReadCoilsRsp STRUCT Communication response equivalent to the Read Coils service respon
47、se defined in IEC 61158-5-15 communicationReference M 11 multipleCoilValues M 11 ANSI/ISA62453-315 (103.00.09)2011 - 28 - 10.3.4 Read discrete inputs transaction service The parameters of the transaction service, which is equivalent to the Read Discretes service defined in IEC 61158-5-15, are descri
48、bed in Table 14, Table 15, Table 16 and Table 17. Table 14 Simple ReadDiscreteInputsReq data types Data type Definition Description Equivalent IEC 61158-5-15 service parameter startAddress UINT Address of the first discrete input to be read Address of first discrete quantity UINT Number of discrete
49、inputs to be read Quantity of discretes Table 15 Structured ReadDiscreteInputsReq data types Data type Definition Description Elementary data types Usage Multiplicity ReadDiscreteInputsReq STRUCT Communication request equivalent to the Read Discretes service request defined in IEC 61158-5-15 communicationReference M 11 quantity M 11 startAddress M 11 Table 16 Simple ReadDiscreteInputsRsp data types
