You are on page 1of 14

Experion PKS DeviceNet Interface Specifications and Technical Data

EP03-440-200 Release 200
Revision Date: December 2003 Version 1.0

.......................................................................................................................................................................5 Generic Function Block Constraints ............................................................... 2 Introduction .................................................................................................................................................................................................................................................................................................................................................................................. 10 Configuration...6 Data Sizes .................................9 SPECIFICATIONS.............................................................................................................8 Bit Offsets ..........................................................................................3 DNET_INCHAN Function Block .................... 10 Hardware Details............................................................................................4 DNET_OUTCHAN Function Block .................................................. 1 FUNCTIONAL DESCRIPTION ............................................................................. 2 DeviceNet Interface Library.......................8 Data Formats ...............................................................................................................................................Experion PKS DeviceNet Interface Specification and Technical Data Table of Contents Page INTRODUCTION ..................................................................................................................................................................................................................................... 2 DNET_IM Function Block..............................................................................................................................................................................................................................................................................................................................3 DNET_DEVICE Function Block .................................................................... 11 Experion PKS DeviceNet Interface Specifications and Models ii .................................................... 9 Numeric Data ............................................................................................

The module provides an interface between DeviceNet devices and the Experion PKS C200 controller.EP03-440-200 Release 200 December 2003 Version 1. The diagram below depicts a topology example. The DNB module is an Allen-Bradley-supplied device that can mount in both the Controller and the I/O rack. TM Server Supported on ControlNet via CNI PC with RSNetWorx for DeviceNet Configuration Tool Connect to ControlNet or DeviceNet Supervisory Network PCIC Module RS-232 Serial Link CNI C200 Red Mod CNI I/O Network CNI 1756DNB Module 1770-KFD Interface Module DeviceNet Network DeviceNet Devices Series 9000 Photoeye RediSTATION 1305 Drive FLEX I/O Rack Figure 1  Redundant Controller Experion PKS System with DeviceNet Interface Experion PKS DeviceNet Interface Specifications and Models 1 .0 Introduction The Experion PKS to DeviceNet interface provides a communication path from the DeviceNet network to the C200 controller through the dedicated DNB hardware interface card.

Additional devices can be certified by contacting a Honeywell representative. An associated output channel block representing data sent to a DeviceNet device. A block representing a Device. The DeviceNet Library contains generic DeviceNet Function Blocks. The Function Blocks comprising the Experion PKS DeviceNet library (DNETIF library) are packaged as an optional Control Component Library (CCL). The generic DeviceNet Function Blocks provide a simple interface to ODVA (Open DeviceNet Vendor Association) certified devices that support numeric and discrete data. Generic blocks offer a flexible configuration model for providing a simple interface to most devices. this library is visible on the Library tab of Control Builder.EP03-440-200 Release 200 December 2003 Version 1. An associated input channel block representing data received from a DeviceNet device.0 Functional Description Introduction Experion PKS-to-DeviceNet interfacing is performed using generic Experion PKS C200 Controller Function Blocks contained within a DeviceNet Interface library. The goal of the generic library is to utilize one set of Function Blocks that can be configured for use with most DeviceNet devices. DeviceNet Interface Library The DeviceNet Interface Library (DNETIF) supports Experion PKS R100 and later. This library is used with the Experion PKS Control Builder to create DeviceNet Function Blocks in the controller. Experion PKS DeviceNet Interface Specifications and Models 2 . The generic DeviceNet Function Blocks allow users to achieve read and write capability with DeviceNet devices. After installation of the DNETIF. The DNETIF library is comprised of the following blocks: DeviceNet Library Function Block Description DNET_IM block DNET_DEVICE block DNET_INCHAN block DNET_OUTCHAN block An IOM block representing the DNB module.

The Format of the input and output data of the device.EP03-440-200 Release 200 December 2003 Version 1. and the device communication status. Experion PKS DeviceNet Interface Specifications and Models 3 . identified by a unique network address. which has been configured previously using the RSNetWorx for DeviceNet configuration tool. The Input and Output data size. the device online/offline status. The DeviceNet network Address of the DeviceNet device that the Function Block represents. Use Control Builder to configure this DNET_DEVICE Function Block information: The DNET_IM block that serves its I/O data. it merely serves I/O data to each of its associated device blocks. The following table shows important information that is configured using Control Builder. In addition.0 DNET_IM Function Block The DNET_IM Function Block is an I/O module Function Block that represents the DNB Module. The following table shows important information that is configured using Control Builder. This table shows the network address of each device. The DNET_IM block itself does not interpret any I/O data. and the data connection update rate. DNET_DEVICE Function Block The DNET_DEVICE block is the generic device module block that represents the device of interest. it supports a maximum of 64 devices. Use Control Builder to configure this DNET_IM Function Block information: The name and type of module and the Rack Address. It supports communication to any/all DeviceNet devices within the valid station address range of 0-63. DeviceNet configurationA table of textual descriptors showing the configuration of the DeviceNet network.

Up to 8 numeric input parameters can be derived from the input channel. The following table shows important information that is configured using Control Builder. The position. This block type reserves one of the channels 0-15 of the DNET_DEVICE block for assignment. The position of each discrete input parameter used must be configured.0 DNET_INCHAN Function Block The DNET_INCHAN (Input Channel Block) represents the input received from a DeviceNet device. Input Channel Data Message Location Numeric Input Configuration The data offset and data size of the channel block’s message structure must be configured. the user must choose the appropriate parameters for pin exposure and connection to other blocks. Like other Experion PKS I/O modules. Pin Exposure The input channel block is capable of processing up to 8 numeric inputs and 32 discrete inputs or any combination thereof. Discrete Input Data Configuration Up to 32 discrete input parameters can be derived from the input channel. Experion PKS DeviceNet Interface Specifications and Models 4 . One numeric input parameter and one discrete input parameter are exposed as block pins by default.EP03-440-200 Release 200 December 2003 Version 1. type and scaling of each numeric input parameter used must be configured. both the device block and the CM containing the input or output channels must be assigned to the same control execution environment prior to assigning the channel to the device block. thus. Use Control Builder to Configure this DNET_INCHAN Function Block Information: Channel Assignment Description The input channel block (DNET_INCHAN) is assigned to a DNET_DEVICE block within the same C200 control execution environment.

One numeric output parameter and one discrete output parameter are exposed as block pins by default. The position of each discrete output parameter used must be configured. Access Level Constraints on Control Outputs A view-only access lock is enforced on the discrete and numeric output parameters of the DNET_OUTCHAN block. Experion PKS DeviceNet Interface Specifications and Models 5 . Like other Experion PKS I/O modules. The user must choose the appropriate parameters for pin exposures and connections to other blocks. Discrete Output Data Configuration Up to 32 discrete output parameters can be derived from the output channel. Any output parameter that must be capable of being changed by the operator or engineer should be exposed as a block pin and connected to another block.EP03-440-200 Release 200 December 2003 Version 1. Output Channel Data Message Location Numeric Output Configuration The data offset and data size of the device block’s message structure must be configured. prior to assigning the channel to the device block. both the device block and the CM containing the input or output channels must be assigned to the same control execution environment. the operator/engineer cannot change the value of these parameters directly. The position. therefore.0 DNET_OUTCHAN Function Block The DNET_OUTCHAN (Output Channel Block) represents the output sent to a DeviceNet device. Use Control Builder to Configure this DNET_OUTCHAN Function Block Information: Channel Assignment Description The output channel block (DNET_OUTCHAN) is assigned to a DNET_DEVICE block within the same control execution environment. This block type reserves channels 16-32 of the DNET_DEVICE block for assignment. Up to 8 numeric output parameters can be derived from the output channel. Pin Exposure The output channel block can process up to 8 numeric outputs and 32 discrete outputs. type and scaling of each numeric output parameter used must be configured. The following table shows important information that is configured using Control Builder.

can be used to effectively invert the polarity of the logical conditions. The following table lists the integer and floating point formats supported for data transport by the DeviceNet Interface Library generic channel blocks. respectively. for analog and discrete devices. whereby a “1” corresponds to an On/True condition and a “0” corresponds to an Off/False condition. Experion PKS DeviceNet Interface Specifications and Models 6 . However. The use of logic blocks. Integer and Floating-point formats supported by Generic Blocks Signed 8 bit integer Unsigned 8 bit integer Signed 16 bit integer 1 1 Unsigned 16 bit integer 1 16 bit data formats are only supported in Experion PKS Release 101 and later. where the byte and bit number can be specified.0 Generic Function Block Constraints Generic blocks provide the Experion PKS Control Execution Environment (CEE) with I/O data of FLOAT64 and BOOLEAN data types only. I/O parameters can be connected to blocks such as the TypeConvert block in order to effectively interpret other data types Although analog/numeric data is exposed to the control process in the FLOAT64 data type. Conventional logic polarity is assumed. the generic blocks interpret/package all numerical data in either integer or floating point format for transport from/to DeviceNet. Generic blocks interpret (or package) all discrete/Boolean data as an individual bit. as described above.EP03-440-200 Release 200 December 2003 Version 1. such as the NOT block.

however. Numerics: • 128 Input Numeric values • 128 Output Numeric values Each of the 16 input and output channel blocks is capable of mapping up to 8 numeric values. 16 channels/device x 32 discretes/channel = 512 discretes/device A maximum of 512 discrete input values and 512 discrete output values per device is possible. Discretes: • 512 Input Discrete values • 512 Output Discrete values Each input and output channel is capable of mapping up to 32 discrete values.0 Device Block Configuration Limits Configuration Limit per Device Block Description Channels: • • 16 Input channel blocks 16 Output channel blocks Each Device block supports up to 16 input channel blocks and 16 output channel blocks. 24 character descriptors are configurable on each parameter. December 2003 Version 1. Input and output parameter names are fixed at the parameter names indicated in the following table.EP03-440-200 Release 200 The following table lists the configuration limits that apply to the use of generic blocks. DeviceNet Interface Library Block I/O Parameter Names Input Channel Block Output Channel Block Numeric Parameter Name Discrete Parameter Name PV[0-7] PVFL[0-31] OP[0-7] OPFL[0-31] Experion PKS DeviceNet Interface Specifications and Models 7 . 16 channels/device x 8 numerics/channel = 128 numerics/device A maximum of 128 numeric input values and 128 numeric output values per device is possible.

Experion PKS DeviceNet Interface Specifications and Models 8 . Bit offsets are “right justified”.EP03-440-200 Release 200 December 2003 Version 1. All data offsets are indicated in units of words and bits and are “left justified”.0 Data Sizes All data sizes are indicated in units of bytes. All byte and bit offsets are zero-based specifications. the entire byte (which contains the referenced bit) is read and written by the input/output channel blocks. Bit Offsets All bit offsets are made relative to a particular byte. meaning that when a byte is presented in binary numerical format. bit 0 is on the right side. respectively. In the following example. Although input and output channel blocks are capable of specifying and interpreting a discrete value in a single bit. and therefore span the range 0 to 7. only bit 0 is set: 00000001.

0 Data Formats Numeric Data Five integer formats are supported for both input and output channel blocks. Discrete/Boolean Data Type The generic blocks are configured with the necessary parameters to specify the particular byte and bit necessary to convert between discrete I/O data and integer format. The tables below list the data types. sizes and the minimum and maximum mathematical ranges for the integer data types.768 65. Numeric inputs and outputs do not support under range or over range protection in the form of fail-safe behavior nor are alarms generated at such limits. Experion PKS DeviceNet Interface Specifications and Models 9 . This information is a property of the device of interest and must be known by the configuration engineer in order to properly configure the generic input and output channel blocks.536 WORD_UNSIGND 1 Word data formats are only supported in Experion PKS Release 101 and later.767 0 127 256 32.EP03-440-200 Release 200 December 2003 Version 1. Integer Data Formats Supported with DeviceNet Interface Data Type Description Size (bytes) Minimum Value Maximum Value BYTE_SIGNED BYTE_UNSIGND WORD_SIGNED 1 1 Signed 8 bit integer Unsigned 8 bit integer Signed 16 bit integer Unsigned 16 bit integer 1 1 2 2 -128 0 -32.

single slot-width Provides a communication bridge between ControlNet and DeviceNet Controller or Remote I/O Chassis (as with other CIOM-A modules. Experion PKS DeviceNet Interface Specifications and Models 10 . 500 KBps.0 Specifications Hardware Details The DeviceNet Bridge Module possesses the following characteristics: Parameter Module Type Physical Interface Chassis Locations Specification 1756-DNB. is required based on the total number of DeviceNet Bridge Modules per Server actually in use. Maximum Number of DeviceNet Usage Licenses per Server (Redundant or Non-Redundant) Update Rates from the 1756-DNB Module to the C200 Configuration See EP03-300-200. CIOM-A form-factor. 492 Output 100 100 5ms CEE: Read at 5ms. 250 KBps and 125KBps 32 [6 supported with 5ms CEE] 12 [not supported with 5ms CEE] Communication update between module and DNB block Maximum Bytes per Network Maximum Number of 1756-DNB Modules per Server (Redundant or Non-Redundant) 50 ms 496 Input. A DeviceNet Usage License. Experion PKS CEE-based Controller Specifications and Technical Data for important Controller specifications. Write at 5ms 50ms CEE: Read at 25ms. Available from Allen-Bradley. Write at 25 ms Configured from a PC running the RSNetWorx for DeviceNet Configuration Tool connected to either DeviceNet through a 1770-KFD Interface Module or ControlNet through a PCIC Module. it is located in the I/O Chassis in a redundant Controller configuration) DeviceNet baud rates supported Maximum Number of 1756-DNB Modules per C200 Controller Maximum Number of 1756-DNB Modules per Downlink CNI A Downlink CNI can support the equivalent of 24 IOMs.EP03-440-200 Release 200 December 2003 Version 1. TC-DNLXxx.

Server. and DeviceNet network configuration) is performed using the appropriate DeviceNet tool such as the DeviceNet RediStation or a PC with a DeviceNet connection using RSNetWorx for DeviceNet and RSLinx. are configured as necessary using AllenBradley’s RSNetWorx for DeviceNet software. DeviceNet Control Blocks residing in the controller. Experion PKS configuration (Controller. 1 DNB TC-DNLX05: DeviceNet Usage License. Honeywell DeviceNet Interface System Requirements Element Experion PKS R100 system or later 1756-DNB . Hardware Requirements for DeviceNet Configuration Tools Hardware Optional/ Required Required Optional* Optional* No No No Purchasable from Honeywell PC/Laptop with Serial Port 1770-KFD Interface Module & RS-232 cabling ControlNet through a PCIC Module and cabling Either a ControlNet Interface Card (TC-PCIC01K) or a third-party 1770-KFD is required to configure devices. hardware. Station) is performed using the normal Experion PKS system configuration methods such as the Control Builder and Experion PKS Station. including the DNB modules. Configurations of the DeviceNet and Experion PKS networks are performed separately and differently. RSLinx or RSLinx Lite RSNetWorx for DeviceNet Experion PKS Control Builder Experion PKS DeviceNet Bridge Usage License DeviceNet Usage Licenses: TC-DNLX01: DeviceNet Usage License. The DeviceNet system (such as devices on DeviceNet. and system components required to implement the DeviceNet Interface with Experion PKS.EP03-440-200 Release 200 December 2003 Version 1.0 Configuration All devices on the DeviceNet. 10 DNBs (these licenses are additive and ordered in quantities required for the number of DNB Modules) Required Required Required Required Required Yes Yes No Yes Yes All software not purchased from Honeywell must be acquired from their respective supplier.Allen-Bradley DeviceNet Bridge device C200 Controller DeviceNet network Optional/ Required Required Required Required Required Experion PKS DeviceNet Interface Specifications and Models 11 . Honeywell DeviceNet Interface Software Requirements Software Package Optional/ Required Purchasable from Honeywell Honeywell's DeviceNet Interface Library . 5 DNBs TC-DNLX10: DeviceNet Usage License.included with the DeviceNet Usage Licenses. The following tables lists the various software. 1756-DNB.

Minato-ku.A.E. Honeywell Building... Muroor Rd. special or consequential damages..o. Sunrise. Republic of Singapore/Pacific Division: Honeywell Pty Ltd. Florida 33325/Japan: Honeywell K. Budejovicka 1. Abu Dhabi. Honeywell disclaims the implied warranties of merchantability and fitness for a particular purpose and makes no express warranties except as may be stated in its written agreement with and for its customer.. North Ryde NSW Australia 2113/Europe and Africa: Honeywell S. USA: Honeywell Industry Solutions. Japan 105-0023/Asia: Honeywell Pte Ltd. U. Technology Park.EP03-440-200 Release 200 December 2003 Version 1. Allen-Bradley. 1140 Brussels.. 5 Thomas Holt Drive. Singapore 486073.. While this information is presented in good faith and believed to be accurate. 14-6 Shibaura 1-chome.. North York.A. All other products and brand and product names shown herein are trademarks of their respective owners. Czech Republic/Middle East: Honeywell Middle East Ltd. Experion PKS DeviceNet Interface Specifications and Models 12 . RSLogix. The information and specifications in this document are subject to change without notice. In no event is Honeywell liable to anyone for any indirect. Process Knowledge System™ and PKS™ are trademarks of Honeywell International Inc. 17 Changi Business Park Central 1. Inc.r. 16404 N. Phoenix. 155 Gordon Baker Rd.com TotalPlant ® is a registered trademark and Experion PKS™. Suite 200. Tokyo. Ontario M2H 3N7/Latin America: Honeywell. Belgium/Eastern Europe: Honeywell Praha.experionpks. Cert Complex Block Q. DeviceNet. RSNetWorx. and RSLinx are trademarks of Rockwell Automation or its subsidiaries.0 www.K. Avenue du Bourget 3. AZ 85053 /Canada: The Honeywell Centre.. 140 21 Prague 4. 480 Sawgrass Corporate Parkway. Black Canyon Hwy. s.