EXPERION PKS

RELEASE 501

DeviceNet Interface Implementation Guide

EPDOC-XX27-en-501A
November 2017
Disclaimer
This document contains Honeywell proprietary information. Information contained herein is to be
used solely for the purpose submitted, and no part of this document or its contents shall be
reproduced, published, or disclosed to a third party without the express permission of Honeywell
International Sàrl.
While this information is presented in good faith and believed to be accurate, Honeywell disclaims
the implied warranties of merchantability and fitness for a purpose and makes no express
warranties except as may be stated in its written agreement with and for its customer.
In no event is Honeywell liable to anyone for any direct, special, or consequential damages. The
information and specifications in this document are subject to change without notice.
Copyright 2017 - Honeywell International Sàrl

-2-
Contents 3
Chapter 1 - About This Document 9
Chapter 2 - Getting Started with DeviceNet Interface 10
2.1 Installation 10
2.1.1 Installation checklist 10
2.1.2 Release requirement 11
2.1.3 Related documentation 11
2.1.4 Terms and conventions 11

2.2 Configuration Overview 11

2.2.1 Database residency 11
2.2.2 Offline and inactivation considerations 12

2.3 System Requirements 12

2.3.1 Configuration Tools 13

2.3.2 Licensing 13

Chapter 3 - DeviceNet Block Configuration 14

3.1 Configuring a DNET_IM block 14
3.1.1 Main tab - Identification and Rack Address Groupings 15
3.1.2 Identification Group of DNET_IM Block 15
3.1.3 Rack Address Group of DNET_IM Block 15
3.1.4 Interface Module tab of DNET_IM Block 15
3.1.5 Status Group of DNET_IM Block 16
3.1.6 Interface Module Group of DNET_IM Block 16
3.1.7 Connection Size Group of DNET_IM Block 16
3.1.8 Device Configuration/Status tab of DNET_IM Block 16
3.1.9 Consistency of Configuration required 17

3.2 Configuring a DNET_Device block 18

3.2.1 Channel assignment of DNET_Device block 19
3.2.2 Data Format Groups of DNET_Device block 20
3.2.3 Validation requires accurate message size and format 20

3.3 Configuring a DeviceNet Channel Block 21

3.3.1 Discrete/Boolean Data 21
3.3.2 Application Constraints 22
3.3.3 Configuration Limits and Considerations 22

3.4 Configuring a DNET_INCHAN (Input Channel) Block 23

3.4.1 Channel Block Configuration Group of DNET_INCHAN (Input Channel) Block 24

-3-
 3.4.2 Channel Block to IO Module Assignment Group of DNET_INCHAN (Input
Channel) Block 24
3.4.3 Pin Exposure of DNET_INCHAN (Input Channel) Block 25
3.4.4 Input Data Location Tab of DNET_INCHAN (Input Channel) Block 25
3.4.5 PV Configuration Group of DNET_INCHAN (Input Channel) Block 26
3.4.6 PVRAW to PV Scaling Group of DNET_INCHAN (Input Channel) Block 26
3.4.7 PVFL Configuration of DNET_INCHAN (Input Channel) Block 27

3.5 Configuring a DNET_OUTCHAN (Output Channel) Block 28

3.5.1 Channel Assignment of DNET_OUTCHAN (Output Channel) Block 28
3.5.2 Channel Block to IO Module Assignment Group of DNET_OUTCHAN (Output
Channel) Block 28
3.5.3 Pin Exposure of DNET_OUTCHAN (Output Channel) Block 29
3.5.4 Access Level Constraints on Control Outputs 29
3.5.5 Output Data Location Tab of DNET_OUTCHAN (Output Channel) Block 29
3.5.6 OP Configuration Group of DNET_OUTCHAN (Output Channel) Block 30

3.5.7 OPRAW to OP Scaling Group 30

3.5.8 PVFL Configuration of DNET_OUTCHAN (Output Channel) Block 31

3.6 Upgrading the DNet firmware 31

3.7 Configuring using the DeviceNet Starter Kit 32
3.7.1 Network Topology for DeviceNet Starter Kit 32
3.7.2 RSNetWorx Configuration for DeviceNet Starter Kit 33
3.7.3 Experion Configuration 37
3.7.4 Device Configuration 39
3.7.5 Input Channel Configuration 41
3.7.6 Output Channel Configuration - Configure channel for Stack Light 42

3.8 Resolving Configuration Mismatch Errors 45

3.9 Managing Unavailability of DeviceNet 47
3.10 Adding a device to a running DeviceNet 50
3.10.1 Configuration of DeviceNet and Experion 50
3.10.2 Downloading and restart 51

3.11 Changing the address of the DNet Interface Module 51

Chapter 4 - DeviceNet Block Operation 52
4.1 Operating a DNET_Device Block 52
4.2 Operating a DNET_INCHAN Block 53
4.3 Operating a DNET_OUTCHAN Block 54
4.4 Activating the DeviceNet 55
4.4.1 Activate the CEE 55

-4-
 4.4.2 Activate the DNET_IM block 56
4.4.3 Activate the Device blocks 56
4.4.4 Set the 1756-DNB into RUN 57

4.5 Monitoring the DeviceNet Status Display 58

4.5.1 Normal operations status of DeviceNet 58
4.5.2 Command/Status of DeviceNet Status 59
4.5.3 Typical device status of DeviceNet 59

Chapter 5 - Troubleshooting DeviceNet Status Failures 60

5.1 Device not available 60
5.2 DNet Interface module faulted 62
5.3 Power removed from DNet Interface module 65
5.4 Power removed from DeviceNet Network 66
5.5 Status Codes 67
Chapter 6 - DeviceNet Interface Parameter Reference 69
6.1 DeviceNet Interface Module (DNET_IM) Function Block 71
6.1.1 Interface Module Tab of DeviceNet Interface Module (DNET_IM) 71
6.1.2 Device Configuration/Status Tab of DeviceNet Interface Module (DNET_IM) 72
6.1.3 Command/Status Tab of DeviceNet Interface Module (DNET_IM) 72

6.2 DeviceNet Device (DNET_DEVICE) Function Block 73

6.2.1 Main Tab of DeviceNet Device (DNET_DEVICE) 73
6.2.2 Module Configuration Tab of DeviceNet Device (DNET_DEVICE) 73

6.3 Input Channel (DNET_INCHAN) Function Block 74

6.3.1 Main Tab of Input Channel (DNET_INCHAN) Function Block 74
6.3.2 Input Data Location Tab of Input Channel (DNET_INCHAN) 74
6.3.3 Numeric Input Configuration Tab of Input Channel (DNET_INCHAN) 75
6.3.4 Discrete Input Configuration Tab of Input Channel (DNET_INCHAN) 75
6.3.5 Numeric Data Tab of Input Channel (DNET_INCHAN) 75
6.3.6 Discrete Data Tab of Input Channel (DNET_INCHAN) 75

6.4 Output Channel (DNET_OUTCHAN) Function Block 75

6.4.1 Main Tab of Output Channel (DNET_OUTCHAN) Function Block 76
6.4.2 Output Data Location Tab of Output Channel (DNET_OUTCHAN) 76
6.4.3 Numeric Output Configuration Tab of Output Channel (DNET_OUTCHAN) 76
6.4.4 Discrete Output Configuration Tab of Output Channel (DNET_OUTCHAN) 77
6.4.5 Numeric Data Tab of Output Channel (DNET_OUTCHAN) 77
6.4.6 Discrete Data Tab of Output Channel (DNET_OUTCHAN) 77

6.5 BADCONFIGFL 77

-5-
6.6 BADINPUTSTS 78
6.7 BADOPFLSTS[0..31] 78
6.8 BADOPSTS[0..7] 79
6.9 BADOUTPUTSTS 79
6.10 BADPVFLSTS[0..31] 80
6.11 BASEPERIOD 80
6.12 DATAOFFBIT 80
6.13 DATAOFFSIZE 81
6.14 DATAOFFWORD 82
6.15 DEVICE[0..63] 82
6.16 DEVICEADDRESS 82
6.17 DEVICESTS 83
6.18 DEVICESTS[0..63] 84
6.19 DEVICESTSCODE[0..63] 84
6.20 DEVICESTSMSG[0..63] 85
6.21 DNETFLTADDR 85
6.22 DNETFLTSTS 86
6.23 DNETIMADDR 86
6.24 DNETIMADDRESS 86
6.25 DNETIMCMD 87
6.26 DNETIMSTS 88
6.27 DNETIMSTSAUTOV 88
6.28 DNETIMSTSCFAIL 89
6.29 DNETIMSTSDFAIL 89
6.30 DNETIMSTSDISBL 90
6.31 DNETIMSTSDUP 90
6.32 DNETIMSTSFAULT 91
6.33 DNETIMSTSIDLE 91
6.34 DNETIMSTSPOWER 92
6.35 DNETIMSTSRUN 92
6.36 DNETIMTYPE 92
6.37 DNETSCANCNT 93

-6-
6.38 FLBITOFFSET[0..31] 93
6.39 FLBYTEOFFSET[0..31] 94
6.40 FLDESC[0..31] 94
6.41 FLENABLE[0..31] 94
6.42 INCONNSIZE 95
6.43 INOFFSETBIT[0..9] 95
6.44 INOFFSETWORD[0..9] 96
6.45 INSIZE[0..9] 96
6.46 IOCONNSTATUS 96
6.47 OP[0..7] 97
6.48 OPDESC[0..7] 98
6.49 OPENABLE[0..7] 98
6.50 OPFL[0..31] 98
6.51 OPHIACT[0..7] 99
6.52 OPHIRAW[0..7] 99
6.53 OPLOACT[0..7] 100
6.54 OPLORAW[0..7] 100
6.55 OPOFFSET[0..7] 101
6.56 OPRAW[0..7] 101
6.57 OPRAWSIZE[0..7] 102
6.58 OUTCONNSIZE 102
6.59 OUTOFFSETBIT[0..9] 103
6.60 OUTOFFSETWORD[0..9] 103
6.61 OUTSIZE[0..9] 104
6.62 PV[0..7] 104
6.63 PVDESC[0..7] 105
6.64 PVENABLE[0..7] 105
6.65 PVFL[0..31] 105
6.66 PVHIACT[0..7] 106
6.67 PVHIRAW[0..7] 106
6.68 PVLOACT[0..7] 107
6.69 PVLORAW[0..7] 107

-7-
6.70 PVOFFSET[0..7] 108
6.71 PVRAW[0..7] 108
6.72 PVRAWSIZE[0..7] 108
6.73 PVSTS[0..7] 109
6.74 SRCBLOCK 110

-8-
 CHAPTER

1 ABOUT THIS DOCUMENT

This document provides guidelines and procedures for interfacing DeviceNet network
components with an Experion system. It includes installation, configuration, operation, and
parameter reference details.

1.1 Revision history

Revision Date Description

A Date November 2017 Initial release of document

-9-
 CHAPTER

2 GETTING STARTED WITH DEVICENET INTERFACE

The document assumes that the user has an understanding of basic Control Builder terminology
and approach to building control strategies, and has an understanding of DeviceNet terminology
and configuration tools.
The DeviceNet Interface module can be supported in both a non-redundant and redundant
Experion Controller topology. The following diagrams depict the intended usage of the Experion
DeviceNet Interface in these hardware topologies.
l Installation
l Configuration Overview
l System Requirements

2.1 Installation
This document describes how to configure and monitor a DeviceNet network using the DeviceNet
Interface Library. The document assumes that the user has an understanding of basic Control
Builder terminology and approach to building control strategies, and has an understanding of
DeviceNet terminology and configuration tools.
l Installation checklist
l Release requirement
l Related documentation
l Terms and conventions

2.1.1 Installation checklist

This section identifies the high level activities necessary to install the various components in the
architecture. This section is not a comprehensive reference on the installation of the various
components.
In general, the following installation activities are required prior to the commissioning and use of
the Experion DeviceNet interface.
l Install/Upgrade Experion Software.
l Install the DeviceNet Interface Library.
l Install RSNetWorx configuration tool on a PC that will be used for configuration of the
DeviceNet.
l Install DeviceNet network, including DNet Interface, DeviceNet devices, wiring, and
termination.

Refer to the supporting documentation for each of these activities for more detailed instructions.

- 10 -
 Chapter 2 - Getting Started with DeviceNet Interface

2.1.2 Release requirement

The interface of DeviceNet to the Experion platform involves the provision of a communication
path from the DeviceNet network to the C200/C300 Controller through the use of a dedicated
hardware interface module 1756-DNB that also acts as the DeviceNet scanner device.

2.1.3 Related documentation

If you need to… Then use this reference…

Configure the DeviceNet Interface DeviceNet Interface Implementation Guide
Get the latest product release information DeviceNet Interface Software Change Notice

2.1.4 Terms and conventions

Term Definition
Industry term
DNet Interface Module DeviceNet Interface Module, specifically the 1756-DNB
EDS Electronic Data Sheets
ODVA Open DeviceNet Honeywell Association
Honeywell term
CEE Control Execution Environment
CNI ControlNet Interface Module
ICP Integrated Control Platform
IOC Input Output Channel
IOM Input Output Module

2.2 Configuration Overview

The following section describes about Configuration.

ATTENTION
When configuring the DeviceNet Interface
l Configure the DeviceNet first, then
l Configure the Experion blocks.

Several types of configuration operations require a change in both the DeviceNet configuration
and the Experion Control Builder. It is recommended that such changes are made in the
DeviceNet configuration first, and then included in the corresponding Experion blocks. The
RSNetWorx for DeviceNet tool includes a reporting tool that can be used to generate a report that
contains the majority of the configuration information needed in Control Builder.
l Database residency
l Offline and inactivation considerations

2.2.1 Database residency

ATTENTION

- 11 -
 Chapter 2 - Getting Started with DeviceNet Interface

Special attention must be paid to any operations that are applicable to multiple entities such
that when a change is made all affected entities are updated using the appropriate
configuration tool. Note that although this normally applies between DeviceNet and
Experion platform, this can also apply between multiple Experion blocks. Configuration
operations where this applies are highlighted in the following table.

Configuration Operation Configuration Tool

RSNetWorx Experion Control Builder
for DNET_ DNET_ DNET_
DeviceNet IM DEVICE INCHAN
Block Blocks
& DNET_
OUTCHAN
Blocks
Configuration of DeviceNet network parameters, including X X
network baud rate, scan list, device addresses, scan cycle
times, other network timing parameters
Device address for the 1756-DNB X X
DeviceNet device configuration (using EDS files) X
Device address of DeviceNet devices X X X
Device I/O data offsets into DNET_IM I/O assemblies X X
Device I/O message sizes/formats X X
I/O Channel data offset, size and format X
Selection of particular control I/O parameters from a X
DeviceNet device for connection to other PlantScape
blocks

2.2.2 Offline and inactivation considerations

The DNET_IM block must be INACTIVE in order to initiate most configuration operations such as
the addition of a device or a change to the configuration of any device when using the RSNetWorx
for DeviceNet configuration tool. Thus, unlike the native Experion modular I/O architecture, which
allows the addition and removal of I/O modules while on process, any changes on the DeviceNet
network require that the entire DeviceNet network is offline and that the supporting control is
temporarily suspended.

2.3 System Requirements

Following are the hardware and software requirements.
Hardware Requirements: Only PlantScape R500 Release or later Experion software supports the
DeviceNet Interface Library.
Software environment requirements include the following:
l Requires PlantScape R500 Release or later Experion software.
l The DeviceNet network is configured using the RSNetWorx for DeviceNet configuration tool.

The information in this section is intended to provide a set of specifications for the previously
described system topologies.

- 12 -
 Chapter 2 - Getting Started with DeviceNet Interface

1. The 1756-DNB is not a redundancy compliant device and therefore cannot be introduced into
a controller chassis of a redundant controller configuration. However in non-redundant
applications, the module can be located in either the C200 Controller or a downlink I/O
chassis. However, C300 is located on a separate downlink I/O chassis.
2. The communication update interval between the DNet Interface and the DNET_IM block
cannot be configured, but is dependant upon the Base Execution Rate of the CEE in which the
block is running

CEE Base Execution Rate Input Rate Output Rate

50 Ms 25 Ms 25 Ms
5 Ms 5 Ms 5 Ms

1. The DNET_IM block supports communication to a maximum of 64 unique devices, identified by

a unique network address within the valid network address range of 0-63.
2. The DNet Interface imposes the following constraints, which may restrict the number of
DeviceNet devices supported:
l The sum of all input message sizes from all input devices cannot exceed 496 bytes.
l The sum of all output message sizes from all output devices cannot exceed 492 bytes.

3. Regarding the existing system limit of 64 IOM connections per C200/C300 Control Processor
module (CPM) and 24 IOMs per downlink CNI:
l The DNET_IM block is the equivalent of 2 IOMs in this calculation
l The DNET_DEVICE blocks that are associated with a given DNET_IM block are not counted
in these limits. (Only the associated DNET_IM block is counted.)

4. The three DeviceNet baud rates: 500 KBps, 250 KBps and 125KBps are supported

l Configuration Tools
l Licensing

2.3.1 Configuration Tools

If you need to configure… Then use this configuration tool

DNet Interface Module (1756-DNB) RSNetWorx for DeviceNet
DeviceNet Devices RSNetWorx for DeviceNet
All Experion Blocks Experion Control Builder

2.3.2 Licensing
DNETIF Library: Use of the DNet Interface module with the DNETIF library requires the purchase
of one license for each interface module used.
RSNetWorx for DeviceNet Network Configuration: The DeviceNet network is configured using the
RSNetWorx for DeviceNet configuration tool. This tool, including supporting documentation, is
purchased as a separate license. Although this document includes some examples of DeviceNet
configuration, it does not attempt to duplicate the information provided in the RSNetWorx for
DeviceNet or any other DeviceNet documentation.

- 13 -
 CHAPTER

3 DEVICENET BLOCK CONFIGURATION

This section describes the information to be configured for each of the DeviceNet Blocks. Each
DeviceNet specific tab for each block is discussed. Standard tabs such as Server, Block Pins,
Configuration Parameters, Monitoring Parameters and Block Preferences, which contain only
standard parameters are not described in this section of the document. Complete descriptions of
the DeviceNet Interface specific parameters can be found in the document DeviceNet Interface
Parameter Reference Dictionary section.

ATTENTION
When configuring the DeviceNet Interface
l Configure the DeviceNet first, then
l Configure the Experion blocks.

l Configuring a DNET_IM block

l Configuring a DNET_Device block
l Configuring a DeviceNet Channel Block
l Configuring a DNET_INCHAN (Input Channel) Block
l Configuring a DNET_OUTCHAN (Output Channel) Block
l Upgrading the DNet firmware
l Configuring using the DeviceNet Starter Kit
l Resolving Configuration Mismatch Errors
l Managing Unavailability of DeviceNet
l Adding a device to a running DeviceNet
l Changing the address of the DNet Interface Module

3.1 Configuring a DNET_IM block

The following section describes about configuring a DNET_IM block.
l Main tab - Identification and Rack Address Groupings
l Identification Group of DNET_IM Block
l Rack Address Group of DNET_IM Block
l Interface Module tab of DNET_IM Block
l Status Group of DNET_IM Block
l Interface Module Group of DNET_IM Block
l Connection Size Group of DNET_IM Block
l Device Configuration/Status tab of DNET_IM Block

- 14 -
 Chapter 3 - DeviceNet Block Configuration

l Consistency of Configuration required

3.1.1 Main tab - Identification and Rack Address Groupings

The Main tab of the DNET_IM block is similar to that of other I/O module function blocks. From this
tab you specify the
l Identification Group
l Rack Address Group

3.1.2 Identification Group of DNET_IM Block

Parameter Narrative Parameter Name Description

Name NAME Name assigned to the DeviceNet Interface Module
Module Description DESC A textual description of the Interface Module
IO Module Type IOTYPE Always DeviceNet Interface Module.

3.1.3 Rack Address Group of DNET_IM Block

The parameters in this group specify the physical location of the DNet Interface module on the I/O
network.

Parameter Parameter Description

Narrative Name
IOM Slot IOMSLOT The physical slot number of the module in the chassis.
Number in
chassis
Uplink CNB Adrs ULCNBMAC MAC Address of the uplink CNI - in the chassis which contains the
in IO Rack module (0 if co-located with a non-redundant CPM)
Downlink CNB DLCNBSLOT Slot number of the downlink CNI - in the controller chassis (0 if co-
Slot Number located with a non-redundant CPM)

3.1.4 Interface Module tab of DNET_IM Block

From this tab you specify the general configuration of the Interface Module for:
l Status Group
l Interface Module Group
l Connection Size Group

- 15 -
 Chapter 3 - DeviceNet Block Configuration

3.1.5 Status Group of DNET_IM Block

Parameter Parameter Description

Narrative Name
Execution EXECSTATE Operational parameter, used to activate and inactivate the block.
State
IO IOCONNSTS Operational parameter, which shows the status of the connection
Connection between the block and DNet Interface module.
Status
Alarming ALARMENBL Used to enable/disable the reporting of alarms originating from the
Enabled block.

3.1.6 Interface Module Group of DNET_IM Block

Parameter Parameter Name Description

Narrative
Type DNETIMTYPE DeviceNet Interface Module 1756-DNB.
DeviceNet DNETIMADDRESS Rockwell recommends the Interface Module is located at
Address address 0, but can be any address in the range 0 - 63.
ControlNet DNETIMCNADDR Not used in this release.
MAC ID

3.1.7 Connection Size Group of DNET_IM Block

Although the DeviceNet Interface Module is capable of providing up to 496 bytes of input to and
492 bytes of output data from the C200/C300 Controller, in practice, dependent upon the
DeviceNet configuration, the entire input and output data may not be used. As a performance
optimization, the amount of data that is transported across the Input and Output data connections
can be reduced from the maximum values using the parameters INCONNSIZE and
OUTCONNSIZE.

Parameter Parameter Description

Narrative Name
Input Data INCONNSIZE The size of the Input data transferred from the DeviceNet Interface
Size (bytes) Module to the Controller.(Requires a minimum value of one (1), since
zero (0) is not allowed.)
Output OUTCONNSIZE The size of the Output data transferred from the Controller to the
Data Size DeviceNet Interface Module.
(bytes)

3.1.8 Device Configuration/Status tab of DNET_IM Block

This tab contains a table that is used for both configuration and operational information for

- 16 -
 Chapter 3 - DeviceNet Block Configuration

DeviceNet devices. The data entered in this table should be in agreement with the configuration of
the DeviceNet network performed using the RSNetWorx for DeviceNet configuration tool.

Parameter Parameter Description

Narrative Name
Device DEVICE Identifier for each device located on the DeviceNet. This identifier
can be any in use by the project.

Notes about the following for example configuration table:

l The table allows up to 64 entries, representing 64 devices. The first column represents the
Device Address of the device.
l The DNet Interface normally uses network Address 0. A description for the DNet Interface can
be added in this table at the appropriate address.
l Each entry appearing in the table should be referenced by the presence of a device function
block. However, Control Builder or the CCL does not validate this. If an entry in this table does
not have a related device function block, no alarms will be produced for the device, as these
originate from the device function block.
l Gaps (skipped entries) in the table are permitted.

3.1.9 Consistency of Configuration required

ATTENTION
The information configured in this table must be in agreement with the actual configuration
of the DeviceNet network, as configured using RSNetWorx for DeviceNet. Note however, that
there is no enforcement of this postulate.

For example, if a particular device were physically configured on DeviceNet: (using RSNetWorx for
DeviceNet) at a specific Network Address, it would be possible to configure the DNET_IM block, and
an associated device block with a different network address. Although illogical, provided that the
correct values were entered for the data offset and size, such a configuration would allow
successful interpretation of the I/O data and hence control of the device. However, when the
Device Configuration/Status tab is being used to view the status of the DeviceNet network (and
any display using the same group of parameters), the status of a device will be displayed at the
position in the table known to the DeviceNet Network, and no entry will be shown for the position
configured in the Experion system (unless it is the details of a different device).

ATTENTION
An error message with the information that the parameter ASAPATH is read only appears
during any of the following:

- 17 -
 Chapter 3 - DeviceNet Block Configuration

l Loading a controller
l Reloading a controller
l Restoring the checkpoint

You can ignore the message and proceed.

3.2 Configuring a DNET_Device block

The following section describes about configuring a DNET_Device block.
The Main tab of DNET_Device block is shown in the following figure:

The following table shows the Identification Group of DNET_Device block

Parameter Parameter Description

Narrative Name
Module NAME This would normally be the Name assigned to the Device.
Name
Module DESC A textual description of the Device
Description
Associated ASSOCASSET Enables you to select an asset from those configured in the Enterprise
Asset Model Database to set the Scope of Responsibility (SOR) for the point.

The following table shows the I/O Module Information Group of DNET_Device block

Parameter Narrative Parameter Description

Name
Module Type Always Generic DeviceNet Device.

- 18 -
 Chapter 3 - DeviceNet Block Configuration

Parameter Narrative Parameter Description

Name
Currently assigned The Input and Output Channels currently assigned to
channels the device.

l Channel assignment of DNET_Device block

l Data Format Groups of DNET_Device block
l Validation requires accurate message size and format

3.2.1 Channel assignment of DNET_Device block

The DNET_DEVICE block shows assignment of up to 32 channels. Channel assignment is
performed as part of DeviceNet Channel block configuration. The following considerations apply:
l Channels 0-15 are reserved for input channels (DNET_INCHAN).
l Channels 16-31 are reserved for output channels (DNET_OUTCHAN).
l Only a small subset of the 32 available channels is typically required to create an interface to a
device. For example:
o An input only device would not utilize any output channels, nor would an output-only
device utilize any input channels.
o An input (or output) device that supplies (or accepts) only a single parameter would
require the use of only one input (or output) channel.

Because each input and output channel block is capable of processing up to 8 numeric and 32
discrete I/O values, the user has some amount of flexibility in the channel assignment process.
For example, if a particular DeviceNet device supplies four input numeric parameters, the
configuration engineer could use as many as four input channel blocks (with one parameter
processed on each block) or as few as one input channel block (with four parameters processed on
each block).
This tab includes the detailed configuration of the device and its data. The following figure shows
the Module Configuration tab of DNET_Device block:

The following table shows information about Device Location Group of DNET_Device block:

Parameter Parameter Name Description

Narrative
Source SRCBLOCK A reference to the DNET_IM block that will serve the devices I/O
Block data. It is also identifying the DeviceNet on which the device is
located.

- 19 -
 Chapter 3 - DeviceNet Block Configuration

Parameter Parameter Name Description

Narrative
DeviceNet DEVICEADDRESS The address of the device on DeviceNet.
Address
Alarming ALMENBSTATE Enable/Disable Alarming on this block.
Enabled

WARNING
It is possible for the user to make configuration errors in the configuration of the DNET_IM
module configuration table and/or the associated device and channel blocks which
reference the DNET_IM block that could cause unpredictable behavior of output devices.
For example, it is possible to configure two blocks that are writing the same byte(s) in the
DNET_IM output assembly, without the generation of a configuration error. Therefore, it is
recommended that all address, offset, and data size parameters be checked for accuracy
prior to block activation.

3.2.2 Data Format Groups of DNET_Device block

The Data Format table provides for the configuration of fragments of Input and Output data for a
device. The table defines where the input data for the device is situated within the Input Data
Assembly and where the output data for the device is situated within the Output Data Assembly.
Although the normal operation will be to make all input and output data for a device contiguous
within the two data assemblies, the RSNetWorx tool allows data for a device to be split and located
anywhere in the assembly. This table therefore provides for an arbitrary 10 fragments of Input and
Output data for a device.
The following table shows the Input Data Format of DNET_Device block:

Parameter Parameter Description

Narrative Name
Data Offset INOFFSETWORD The starting position (in words) of the device data in the Input
(Words) Assembly.
Data Offset INOFFSETBIT The starting position (in bits) of the device data in the Input
(Bits) Assembly.
Data Length INSIZE The size of the Input data (in bits). This value must be a multiple of
(Bits) 8 (that is, must be an exact number of bytes.)

The following table shows the Output Data Format of DNET_Device block:

Parameter Parameter Name Description

Narrative
Data Offset OUTOFFSETWORD The starting position (in words), of the device data in the Output
(Words) Assembly.
Data Offset OUTOFFSETBIT The starting position (in bits) of the device data in the Output
(Bits) Assembly.
Data Size OUTSIZE The size of the Output data (in bits). This value must be a
(Bits) multiple of 8 (that is, must be an exact number of bytes.)

3.2.3 Validation requires accurate message size and format

ATTENTION

- 20 -
 Chapter 3 - DeviceNet Block Configuration

The device, input channel and output channel blocks require that the user input the size
and format of the data for the input and output messages. This information is validated
upon activation of the block to ensure that the data format for a device is consistent.
However, no data format validation is performed across blocks (device, inchan and outchan),
so it is possible to make errors in the configuration that are not detected and that could
cause unpredictable behavior of the process. Therefore it is important that care is taken
when entering this data, and it is recommended that the output report from RSNetWorx be
used to assist in it being accurate

For example it is possible to configure two blocks that are writing to the same byte(s) in the DNET_
IM output assembly, without the generation of a configuration error. Also, entering a value for the
input or output message that is too large or too small will not be detected and could be detrimental
to the process. For example, if a particular device outputs 8 bytes of data, but 10 bytes are specified
in the configuration of the output channels, 10 bytes will be written into the DNET_IM assembly
data each time the block executes, causing 2 bytes to be written into a memory area which (most
likely) is the output data message for a different device.

3.3 Configuring a DeviceNet Channel Block

The data formats for the messages for a particular device are generally specified in the technical
documentation that accompanies the device.
Typical Numeric Data Representation on DeviceNet: Numerical data (such as real or integer
numbers) is most commonly transported across DeviceNet in integer format. Real numbers are
converted to/from integer values through a simple linear conversion process. For example, the
following equations show how a 4-20 mA value could be represented using a 16 bit unsigned
integer.
Bottom of raw integer value range = -20,000 = 4 mA = 0%
Top of raw integer value range = 20,000 = 20 mA = 100%
Each equation represents a unique point on a linear equation, and (according to basic algebra)
any two points define a line, from which a linear conversion equation can be derived.
Numeric data handling capability in the generic channel blocks: The generic blocks are configured
with the necessary linear scaling parameters necessary to convert I/O data from/to integer
format. Five integer formats are supported for both input and output channel blocks. The table
below lists the data types, sizes and the minimum and maximum mathematical ranges for the data
types. 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.

Data Type Description Size (bytes) Minimum Value Maximum Value

BYTE_SIGNED Signed 8 bit integer 1 -128 127
BYTE_UNSIGND Unsigned 8 bit integer 1 0 256
WORD_SIGNED Signed 16 bit integer 2 -32,767 32,768
WORD_UNSIGND Unsigned 16 bit integer 2 0 65,536
IEEE32_Real 4 +/- 1.4 * E -45 +/- 3.4 * E38

l Discrete/Boolean Data
l Application Constraints
l Configuration Limits and Considerations

3.3.1 Discrete/Boolean Data

Discrete Data Representation on DeviceNet: Discrete (Boolean) data is generally represented on
DeviceNet as a specific bit, which may be packed into an array of bits, where each of 8 bits per byte

- 21 -
 Chapter 3 - DeviceNet Block Configuration

represents a unique discrete value.

Discrete data handling capability in the generic channel blocks: The generic blocks are configured
with the necessary parameters to specify the particular byte and bit necessary to convert discrete
I/O data from/to integer format.

3.3.2 Application Constraints

The data representation of various DeviceNet devices was evaluated in the design of the generic
blocks, which can interface with most, but not all, DeviceNet devices. The following constraints
bound the scope of application for the use of the generic blocks:

Application Constraint
1 The generic blocks provide the CEE with I/O data of FLOAT64 and BOOLEAN data types only, for
analog and discrete devices, respectively. Note that I/O parameters can be connected to blocks
such as the TypeConvert block in order to effectively interpret other data types
2 Although analog/numeric data is exposed to the control process in the FLOAT64 data type, as
described above, the generic blocks interpret/package all numerical data in integer format for
transport from/to DeviceNet. The following integer formats are supported for data transport by
the generic channel blocks
l Signed 8 bit integer
l Unsigned 8 bit integer
l Signed 16 bit integer
l Unsigned 16 bit integer
3 The generic blocks interpret/package all discrete/boolean data as an individual bit, where the
byte and bit number can be specified. Conventional logic polarity is assumed, whereby a '1'
corresponds to an On/True condition and a '0' corresponds to an Off/False condition. Note that
the use of logic blocks, such as the NOT block, can be used to effectively invert the polarity of the
logical conditions.
4 The generic blocks are capable of interpreting I/O data that is of a fixed format; I/O data of
variable format cannot be interpreted. An example of a fixed format device is a 4-channel AI
module that provides an 8-byte input data structure, with 2 bytes representing each channel.
An example of a variable format data structure is a 6-byte output data structure where the first
two bytes specify a numerical parameter identifier (selects one of several parameters) and the
remaining 4 bytes represent the value that is being stored.
5 The generic output channel blocks do not provide back-initialization capability to any regulatory
control blocks that are connected.

3.3.3 Configuration Limits and Considerations

The following configuration limits apply to the use of the generic DeviceNet blocks:

Configuration Limits and Considerations

1 A maximum of up to 16 input channels and 16 output channel blocks can be
associated with a device block
2 Each input and output channel is capable of mapping/interpreting up to 8 numeric
values. At 16 channels per module, this provides a maximum of 128 numeric values
per device.
3 Each input and output channel is capable of mapping/interpreting up to 32 discrete
values. At 16 channels per module, this provides a maximum of 512 discrete values per
device.
4 Input and output parameter names are fixed at the parameter names indicated in the
following table. However, 24 character descriptors are can be configured on each
parameter.
Input Channel Block Output Channel Block

- 22 -
 Chapter 3 - DeviceNet Block Configuration

Numeric PV[0-7] OP[0-7]

Parameter
Name
Discrete PVFL[0-31] OPFL[0-31]
Parameter
Name
5 When defining the Input/Output Channel data within the Input/Output data
assembly, data offsets are indicated in units of words and bits and are 'left justified',
meaning that word 0 bit 0, is the byte at the lowest memory address location.
6 When defining the Input/Output Channel data within the Input/Output data
assembly, data sizes are indicated in units of bits.
7 When defining individual numeric and discrete values within the Input/Output
Channel data, all byte and bit offsets are zero based specifications. Therefore, the first
byte of a data message is considered byte 0, not byte 1. A data message of 8 bytes in
size would span bytes 0-7.
8 When defining individual numeric and discrete values within the Input/Output
Channel data, all bit offsets are made relative to a particular byte, and therefore span
the range 0 to 7. Bit offsets are 'right justified', meaning that when a byte is presented
in binary numerical format, bit 0 is on the right side. In the following example, only bit
0 is set: 00000001.
9 Although the input and output channel blocks are capable of specifying and
interpreting a discrete value in a single bit, the entire byte (which contains the
referenced bit) is read and written by the input/output channel blocks, respectively.
Although this is not a problem for inputs, it does present a problem for outputs. For
example, if two different output channel blocks are used to write discrete output
values that are contained within the same byte of the channel output data message,
the execution order of the channel blocks and/or their containing Control Modules will
determine which values are written to the device. Thus it is recommended that all
discrete output channel values that are contained within a specific byte be referenced
from a single output channel block.
10 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.

3.4 Configuring a DNET_INCHAN (Input Channel) Block

The Main tab of DNET_INCHAN (Input Channel) Block is shown in the following figure:

- 23 -
 Chapter 3 - DeviceNet Block Configuration

l Channel Block Configuration Group of DNET_INCHAN (Input Channel) Block

l Channel Block to IO Module Assignment Group of DNET_INCHAN (Input Channel) Block
l Pin Exposure of DNET_INCHAN (Input Channel) Block
l Input Data Location Tab of DNET_INCHAN (Input Channel) Block
l PV Configuration Group of DNET_INCHAN (Input Channel) Block
l PVRAW to PV Scaling Group of DNET_INCHAN (Input Channel) Block
l PVFL Configuration of DNET_INCHAN (Input Channel) Block

3.4.1 Channel Block Configuration Group of DNET_INCHAN (Input

Channel) Block

Parameter Narrative Parameter Name Description

Channel Name NAME Identifier for the channel block within the CM
Execution Order in CM ORDERINCM Order in which the block is executed within the CM

3.4.2 Channel Block to IO Module Assignment Group of DNET_

INCHAN (Input Channel) Block
The input channel function block (DNET_INCHAN) is assigned to a DNET_DEVICE block within the
same CEE. This block type reserves channels 0-15 of the DNET_DEVICE block for assignment. Like
other Experion I/O modules, both the Device block and the CM containing the input or output
channels must be assigned to the same CEE prior to assigning the channel to the device block.

Parameter Narrative Parameter Name Description

Module Name The device to which the channel is assigned.
Module Type Always Generic DeviceNet Device

- 24 -
 Chapter 3 - DeviceNet Block Configuration

3.4.3 Pin Exposure of DNET_INCHAN (Input Channel) Block

Because the generic input channel block is capable of processing up to 8 numeric inputs and 32
discrete inputs or any combination thereof, the user must choose the appropriate parameters for
pin exposure (for connection with other blocks) as executed on the Block Pins tab of the Control
Builder form. One numeric input parameter and one discrete input parameter are exposed as
block pins by default

3.4.4 Input Data Location Tab of DNET_INCHAN (Input Channel)

Block

The input channel block extracts data from within the DNET_IM function block's input data
assembly, the size of which is specified during the configuration of the interface module. An offset
and a size parameter are specified to indicate the exact location of the data for this channel block
within the interface module input data message.
Additionally, the location of the data for a device was also defined when configuring the device.
Therefore, the data references made during the configuration of the input channel block must
also be contained within the boundaries of the input message structures for the device. Note that
this validation is not performed at configuration time, but when a Control Module containing an
input channel is activated. If the user enters incorrect values for the data size or offset, upon
activation of the containing CM, a 'configuration mismatch warning' is returned on the CM. Also,
the block containing the error will have its 'Bad Channel/Device Configuration Flag' asserted.

Parameter Parameter Description

Name Narrative
Assembly DATAOFFWORD The starting position in words, of the channel data in the Input
Offset (Words) Assembly.
Assembly DATAOFFBIT The starting position in bits, of the channel data in the Input
Offset (Bits) Assembly.
Assembly DATAOFFSIZE The size of the channel data in bits. This value must be a multiple
Length (Bits) of 8 (that is, must be an exact number of bytes.)

The Numeric Input Configuration Tab of DNET_INCHAN (Input Channel) Block is shown in the
following figure:

- 25 -
 Chapter 3 - DeviceNet Block Configuration

3.4.5 PV Configuration Group of DNET_INCHAN (Input Channel)

Block
Up to 8 numeric input parameters can be derived from the generic input channel. The
configuration and scaling of the numeric output parameters is performed using this tab.

Parameter Parameter Description

Name Narrative
PVENABLE Enable When selected activates the particular PV.
PVDESC Descriptor Used to document the PV.
of PV
PVOFFSET Byte Offset Data offset from the start of the channel data.
PVRAWSIZE Data Raw data size and format. This value must be a multiple of 8 (that is,
Size/Format must be an exact number of bytes). This value must be a multiple of 8
(that is, must be an exact number of bytes).

3.4.6 PVRAW to PV Scaling Group of DNET_INCHAN (Input Channel)

Block
This group represents the scaling for the appropriate PV Configuration group entry.

Parameter Name Parameter Narrative Description

PVLORAW Low Raw Value Lower range limit of the integer input value.
PVHIRAW High Raw Value Upper range limit of the integer input value
PVLOACT Low Actual Value The numeric equivalent of the PVLORAW parameter.
PVHIACT High Actual Value The numeric equivalent of the PVHIRAW parameter.

In the example configuration tab:

- 26 -
 Chapter 3 - DeviceNet Block Configuration

l The byte offset and data size that are specified on this form are relative to the channel block's
data message not the input data assembly.
l Only those indexes that are enabled will undergo configuration validation checking or
execution processing.
l In a normal configuration scenario, the supporting technical documentation for the device of
interest would specify the raw values and associated actual values that are entered into the
table.

The following table shows examples of scaling parameters.

Description Low Raw High Raw Low Actual High Actual

Value Value Value Value
PVLORAW PVHIRAW PVLOACT PVHIACT
Scale raw integer values into percent -4864 32511 -7.4 117.58
Scale raw integer values into -4864 32511 1.1852 22.8
engineering units (mA)

The Discrete Input Configuration Tab of DNET_INCHAN (Input Channel) Block is shown in the
following figure:

3.4.7 PVFL Configuration of DNET_INCHAN (Input Channel) Block

Up to 32 discrete input parameters can be configured in the input channel using this tab.

Parameter Narrative Parameter Name Description

Enable FLENABLE Activates the particular Discrete when selected.
Descriptor of Discrete FLDESC Used to document the Discrete.
Byte Offset FLBYTEOFFSET Data offset from the start of the channel data.
Bit Offset FLBITOFFSET Bit number within the specified byte of interest.
Input Bad Option FLBADOPT Operation parameter signifying bad output value.

In the example configuration:

l The byte offset specified on this form is relative to the channel block's data message, not the
input data assembly.
l Only those indexes that are enabled will undergo configuration validation checking or
execution processing.
l In the example, although 6 inputs are shown, 8 of the 32 available discrete input parameters
are enabled and configured.
l The supporting technical documentation for the device indicates the specific meaning of each
of the status bits.

- 27 -
 Chapter 3 - DeviceNet Block Configuration

3.5 Configuring a DNET_OUTCHAN (Output Channel) Block

The following section describes about Configuring a DNET_OUTCHAN (Output Channel) Block.
The Main tab of DNET_OUTCHAN (Output Channel) Block is shown in the following figure:

l Channel Assignment of DNET_OUTCHAN (Output Channel) Block

l Channel Block to IO Module Assignment Group of DNET_OUTCHAN (Output Channel) Block
l Pin Exposure of DNET_OUTCHAN (Output Channel) Block
l Access Level Constraints on Control Outputs
l Output Data Location Tab of DNET_OUTCHAN (Output Channel) Block
l OP Configuration Group of DNET_OUTCHAN (Output Channel) Block
l OPRAW to OP Scaling Group
l PVFL Configuration of DNET_OUTCHAN (Output Channel) Block

3.5.1 Channel Assignment of DNET_OUTCHAN (Output Channel)

Block

Parameter Narrative Parameter Name Description

Channel Name NAME Identifier for the channel block within the CM
Execution Order in CM ORDERINCM Order in which the block is executed within the CM

3.5.2 Channel Block to IO Module Assignment Group of DNET_

OUTCHAN (Output Channel) Block
The output channel function block (DNET_OUTCHAN) is assigned to a DNET_DEVICE block within
the same CEE. This block type reserves channels 16-31 of the DNET_DEVICE block for assignment.

- 28 -
 Chapter 3 - DeviceNet Block Configuration

Like other Experion I/O modules, both the Device block and the CM containing the input or output
channels must be assigned to the same CEE prior to assigning the channel to the device block.

Parameter Narrative Parameter Name Description

Module Name MODULE The device to which the channel is assigned.
Module Type IOMTYPE Always Generic DeviceNet Device

3.5.3 Pin Exposure of DNET_OUTCHAN (Output Channel) Block

Because the generic output channel block is capable of processing up to 8 numeric outputs and 32
discrete outputs or any combination thereof, the user must choose the appropriate parameters for
pin exposure (for connection with other blocks) as executed on the Block Pins tab of the Control
Builder form. One numeric output parameter and one discrete output parameter are exposed as
block pins by default.

3.5.4 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. Therefore, the operator/engineer cannot change the value of these parameters
directly. Any output parameter that is required to be capable of being changed by the operator or
engineer should be exposed as a block pin and connected to another block.

3.5.5 Output Data Location Tab of DNET_OUTCHAN (Output

Channel) Block
The following is the configuration tab for the output channel data message location:
The output channel writes data to the interface module function block's output message structure,
the size of which is specified during the configuration of the interface module. An offset and a size
parameter are specified to indicate the exact location of the data for this channel block within the
interface module output data message
Additionally, the location of the data for a device was also defined when configuring the device.
Therefore, the data references made during the configuration of the output channel block must
also be contained within the boundaries of the output message structures for the device. Note that
this validation is not performed at configuration time, but when a Control Module containing an
output channel is activated. If the user enters incorrect values for the data size or offset, upon
activation of the containing CM, a 'configuration mismatch warning' is returned on the CM. Also,
the block containing the error will have its 'Bad Channel/Device Configuration Flag' asserted.

Parameter Parameter Description

Narrative Name
Assembly Offset DATAOFFWORD The starting position in words, of the channel data in the
(Words) Input Assembly.
Assembly Offset DATAOFFBIT The starting position in bits, of the channel data in the
(Bits) Input Assembly.
Assembly Length DATASIZE The size of the channel data in bits.
(Bits)

Notes on the sample configuration form:

l Because 8 bytes are specified, it is expected that the associated generic device/module block be
configured with at least 8 bytes of output data (OUTCONNSIZE >= 8).
l Because the offset is listed as 0, it is expected that the first 8 bytes of the device/module block's
output data message is processed by this channel. Alternatively, if this channel block required
only bytes 2 and 3, the data size would be configured as 2, and the offset would be configured
as 2.

- 29 -
 Chapter 3 - DeviceNet Block Configuration

The Numeric Output Configuration Tab of DNET_OUTCHAN (Output Channel) Block is shown in
the following figure:

3.5.6 OP Configuration Group of DNET_OUTCHAN (Output Channel)

Block
Up to 8 numeric output parameters can be derived from the generic output channel. The
configuration and scaling of the numeric output parameters is performed using this tab.

Parameter Narrative Parameter Name Description

Enable OPENABLE When selected activates the particular OP.
Descriptor OPDESC Used to document the OP.
Byte Offset OPOFFSET Data offset from the start of the channel data.
Data Size/Format OPRAWSIZE Raw data size and format.

3.5.7 OPRAW to OP Scaling Group

This group represents the scaling for the appropriate OP Configuration group entry.

Parameter Narrative Parameter Name Description

Low Actual Value OPLOACT The numeric equivalent of the OPLORAW parameter.
High Actual Value OPHIACT The numeric equivalent of the OPHIRAW parameter.
Low Raw Value OPLORAW Lower range limit of the integer output value.
High Raw Value OPHIRAW Upper range limit of the integer output value

In the example configuration tab:

l The byte offset and data size specified on this form are relative to the channel block's data
message, not the output data assembly.
l Only those indexes that are enabled will undergo configuration validation checking or
execution processing.
l In the example, two of the eight available numeric parameters are enabled, and configured,
indicating that this channel block will be used to input two separate output parameters,
specifically for channels 1-2 of the analog output device of interest.
l In a normal configuration scenario, the supporting technical documentation for the device of
interest would specify the raw values and associated actual values that are entered into the
table.

The Discrete Output Configuration Tab of DNET_OUTCHAN (Output Channel) Block is shown in the
following figure:

- 30 -
 Chapter 3 - DeviceNet Block Configuration

3.5.8 PVFL Configuration of DNET_OUTCHAN (Output Channel)

Block
Up to 32 discrete output parameters can be derived from the generic output channel.

Parameter Narrative Parameter Name Description

Enable FLENABLE When selected activates the particular Discrete.
Descriptor of Discrete FLDESC Used to document the Discrete.
Byte Offset FLBYTEOFFSET Data offset from the start of the channel data.
Bit Offset FLBITOFFSET Bit number within the specified byte of interest.

In the example configuration tab:

l The byte offset specified on this form is relative to the channel block's data message, not the
output data assembly.
l Only those indexes that are enabled will undergo configuration validation checking or
execution processing.
l In the example, 1 of the 32 available discrete output parameters are enabled and configured.
l The supporting technical documentation for the device indicates the specific meaning of each
of the command parameter bits.

3.6 Upgrading the DNet firmware

ATTENTION
NTools does not support the DNet firmware upgrade and hence you must use Control Flash
to upgrade Dnet firmware. 1756-DNET firmwares are not maintained in the following path:
Experion PKS\ Engineering Tools\ SYSTEM\ Firmware directory.

3.6.1 Steps to upgrade the DNet firmware

1. Start Control Flash.
2. Click Next.
3. Click Browse to navigate to the directory/folder where the 1756main.nvs file is located.
4. In theFile name, click 1756main.cvs and click OK.
5. Click Next.
RSLinx starts.

- 31 -
 Chapter 3 - DeviceNet Block Configuration

6. On the left panel, navigate to the appropriate DeviceNet communications link.

Or
You can navigate to the DNB module via the backplane.
7. Click the scanner on the right panel to update if updating through DeviceNet.
Or
Click the DNB module in the chassis on the left panel if flashing over the backplane.
8. Click OK.
9. Click Finish.
10. Click Yes to start the update.
This update programs the following sections of the flash: Main
11. When complete, verify that the DNB resets and displays 07/001 on the front panel display.
12. Control Flash displays green update to display the complete status.
Flash update is complete.

3.7 Configuring using the DeviceNet Starter Kit

This section uses the configuration of a DeviceNet Starter Kit, which is sold by Allen-Bradley, as an
example of both the DeviceNet and Experion system parts of the configuration. The contents of the
Starter Kit used for this example are as follows:

Allen-Bradley Catalog Description

Number
1756-DNB DeviceNet Scanner for ControlLogix
1770-KFD DeviceNet Serial Interface
42EF-D1LDAK-F5 RightSight Photoelectric Sensor
871TM-D5ED18-D5 DeviceNet Inductive Proximity Switch
1791D-8B8P CompactBlock I/O (8in / 8out)
1792D-4BVT4D ArmorBlock MaXum (2in / 2 out)
855T-DM1BCBC DeviceNet ControlTower Stack Light Base (Stack Light Green / Stack
Light red)
872C-D2NP8-D4 Standard Proximity Switch

l Network Topology for DeviceNet Starter Kit

l RSNetWorx Configuration for DeviceNet Starter Kit
l Experion Configuration
l Device Configuration
l Input Channel Configuration
l Output Channel Configuration - Configure channel for Stack Light

3.7.1 Network Topology for DeviceNet Starter Kit

The following figure shows an example topology using the DeviceNet Starter Kit with a 1756-DNB
Module in a non-redundant C200 Controller configuration.

- 32 -
 Chapter 3 - DeviceNet Block Configuration

3.7.2 RSNetWorx Configuration for DeviceNet Starter Kit

This section shows the major steps involved with the configuration of the DeviceNet network using
RSNetWorx for DeviceNet. Note that this configuration can be performed online with the network,
so that RSNetWorx for DeviceNet will scan the network for devices that are present, or it can be
performed offline, where the devices to be configured on the network are created from the list of
hardware shown in the left hand window.

Figure 3.1 Figure 1. DeviceNet Layout diagram

1756-DNB scan list: The scan list for the DNet Interface must be configured. Only devices added to
the scan list will have their inputs and outputs added to the Input and Output Data Assembly.

- 33 -
 Chapter 3 - DeviceNet Block Configuration

DNet Interface Input Assembly: Configure the 496 byte Input Data Assembly. Note that the
RSNetWorx for DeviceNet dialog shows the Input Data Assembly as 124, 32-bit words, starting at
word 0, with each word comprising bits 0 - 31.

ATTENTION
Although the RSNetWorx for DeviceNet tool allows you to configure the Input and Output
Data Assembly so that the data for a device does not start on a byte boundary, Experion
platform does not support this, and if it is attempted the configuration will not be accepted.

- 34 -
Chapter 3 - DeviceNet Block Configuration

DNet Interface Output Assembly: Configure the 492 byte Input Data Assembly. Note that the
RSNetWorx for DeviceNet dialog shows the Input Data Assembly as 123, 32-bit words, starting at
word 0, with each word comprising bits 0 - 31.

- 35 -
 Chapter 3 - DeviceNet Block Configuration

RSNetWorx for DeviceNet configuration report: After the DeviceNet configuration has been
completed, use the reporting feature to print the configuration details. This report can be used as
an input document to the Experion configuration to minimize the chance of making configuration
errors.

- 36 -
 Chapter 3 - DeviceNet Block Configuration

3.7.3 Experion Configuration

The Experion configuration is performed using Control Builder (CB). As with all Control Builder I/O
Modules and Control Modules, they must be assigned to a CEE.

- 37 -
 Chapter 3 - DeviceNet Block Configuration

Device Net Interface Module: Create the DeviceNet Interface Module, locating the module in a
relevant CEE. Configure the module as follows.

Configure the parameters Input Data Size and Output Data Size to minimize the amount of data
transferred between the Controller and the DNet Interface.

- 38 -
 Chapter 3 - DeviceNet Block Configuration

Devices are added at the index position relating to their DeviceNet Network Address. This
information can be found on the scan list Summary part of the RSNetWorx for DeviceNet
configuration report. You may use whatever naming convention you wish.
Control Module: The Control Module shows input from the RightSight Diffuser and Proximity
Switch that switch on the Red and Green light of the StackLight. This dialog also shows the
DeviceNet Interface Module (DNET_01) and the DeviceNet Devices (Device01, Device02, Device03
and Device05) in the I/O section of the DNET_CEE.

3.7.4 Device Configuration

The Module Name can use any convention. It is this value that is shown in the Project view. The
currently assigned channels are displayed only after the related input and/or output channels are
configured.

- 39 -
 Chapter 3 - DeviceNet Block Configuration

The Device function block is associated with its DNET_IM function block, and it's network address
configured. The device's data format is configured. The data offsets are relative to the input/output
data assemblies. The data configuration can be found in the Input Memory section of the
RSNetWorx for DeviceNet configuration report. DeviceNet

Data for a device does not have to be contiguous within the data assembly, but normally would be.
Note that the data configuration is not validated at this time, but when the device is activated in the
Controller.

- 40 -
 Chapter 3 - DeviceNet Block Configuration

3.7.5 Input Channel Configuration

Configure channel for Right Sight device: The input channel is assigned to a device that has been
assigned to the same CEE as the CM in which the input channel is used.

The channel's data format is configured. The data offset is relative to the input data assembly.

Numeric and discrete inputs are configured. Note that if any inconsistent configuration is
performed, this is not reported during configuration, but when the CM is activated.

Configure channel for Proximity Switch

- 41 -
 Chapter 3 - DeviceNet Block Configuration

3.7.6 Output Channel Configuration - Configure channel for Stack

Light

- 42 -
Chapter 3 - DeviceNet Block Configuration

ATTENTION
Since these two outputs are writing to the same byte in the Output Assembly, they MUST be
configured using the same DNET_OUTCHAN block, otherwise data would be lost.

The following displays show the normal operation of the configuration described in the previous
sections

Example of Proximity Switch operation: This group of displays shows the effect of the Proximity
Switch touching a surface.
l The connection between the two blocks is shown in green.
l The Input Value for the input of interest is asserted.
l The Output Value for the output of interest is asserted.

The output to the StackLight causes the Green Light to be switched on.

- 43 -
 Chapter 3 - DeviceNet Block Configuration

Example of RightSight Standard Diffuser operation: This group of displays shows the effect of an
object within the range of the RightSight Standard Diffuser.
l The connection between the two blocks is shown in green.
l The Input Value for the input of interest is asserted.
l The Output Value for the output of interest is asserted.

The output to the StackLight causes the Red Light to be switched on.

- 44 -
 Chapter 3 - DeviceNet Block Configuration

3.8 Resolving Configuration Mismatch Errors

Causes of Configuration Mismatch errors: Care must be taken that you define the data offsets and
sizes the same on the DNET_DEVICE and DNET_INCHAN/DNET_OUTCHAN blocks. If you make an
error in this configuration, the error is not identified until you ACTIVATE the Control Module in
which the DNET_INCHAN/DNET_OUTCHAN block is located. At this time you will receive the
following error:

- 45 -
 Chapter 3 - DeviceNet Block Configuration

DNET_Proximity.EXECSTATE is the control module that is being activated. Configuration Mismatch

Warning is the message identifying that a DNET_DEVICE configuration does not match the
configuration of it's associated DNET_INCHAN/DNET_OUTCHAN block.

The BADCONFIGFL parameter is asserted for the DNET_INCHAN/DNET_OUTCHAN block which

contains the mismatch.
Configuration Mismatch - Example 1: In the following example, although the overall size defined in
the DNET_DEVICE block is 16 bits, it is not defined contiguously, so it actually extends over more
than 16 bits. If the data for a device is not contiguous within the Data Assembly, it is probably more
logical to create a DNET_INCHAN/DNET_OUTCHAN block for each piece of the data (in the above
case use 2 DNET_INCHAN blocks).
The following image shows the DNET_DEVICE Block:

- 46 -
 Chapter 3 - DeviceNet Block Configuration

The following image shows the DNET_INCHAN Block:

Configuration Mismatch - Example 2: In the following example, although the data offset (Bits) is
defined differently in the DNET_DEVICE block and DNET_OUTCHAN block.
The following image shows the DNET_DEVICE Block:

The following image shows the DNET_OUTCHAN Block:

3.9 Managing Unavailability of DeviceNet

Initialization data not supported: DeviceNet Input Channel and Output Channel blocks do not
support initialization data. These blocks do not talk directly to the device, but to the DNet Interface,
which is the scanner device controlling devices on the DeviceNet network.

- 47 -
 Chapter 3 - DeviceNet Block Configuration

Minimizing effects of unavailability of DeviceNet: To minimize the effect of devices becoming

unavailable, DNET_INCHAN and DNET_OUTCHAN blocks continue to transfer data to the DNET_IM
block (Input Data Assembly and Output Data Assembly) when a device becomes unavailable. This
ensures that the control engineer is able to manage the unavailability of devices within a control
strategy, and to determine the strategy to be used when a device becomes available again.
Detailed configuration is dependant on the functionality of the devices in use. The Device in use in
these examples is the A-B E3 Plus, which has inputs that define the current status of the device.
These inputs, in conjunction with the BADINPUTSTS parameter can be used in the control strategy
to determine the value that should be written to the output in the event of a device tripping or
being unavailable. In the case of a device that does not have a parameter that indicates the status
of the device, the BADINPUTSTS and BADOUTPUTSTS parameters can be used. These parameters
are asserted whenever the DNET_INCHAN or DNET_OUTCHAN block is unable to register with it's
associated DNET_DEVICE block. In this case the status of the DNET_DEVICE block will also show a
failure state.

In the input channel the BADINPUTSTS parameter has been added to the block as an output. This
enables the parameter to be used as an input to the rest of the control strategy.

- 48 -
Chapter 3 - DeviceNet Block Configuration

The device includes a numeric input that can be configured to provide any parameter to the
controller. In this case, the L1 current is used. Note the scaling of the value from the raw value
provided by the device to the actual value displayed.

The device also has discrete inputs that can be made available to the controller. In this case the
trip status of the device is being used. Note: The E3 Plus can be configured. The configuration of
this device is performed using RSNetWorx for DeviceNet, and must be consistent with the Experion
configuration.

- 49 -
 Chapter 3 - DeviceNet Block Configuration

The output channel is configured to write to the status of the device. The value written can be a
START, or in the case of a tripping of the device, the device being available can be STOP. Even
though the device is unavailable, the value (STOP) will continue to be written to the DeviceNet
Interface. Although this value is not written to the device in this situation, when the device
becomes available the first command written to the device will be STOP. When the BADINPUTSTS
is no longer asserted, or the device is no longer tripped, the START value will be written to the
device and it will revert to normal operation.

3.10 Adding a device to a running DeviceNet

If you wish to add a device to an already running DeviceNet, you must stop the DeviceNet before
you are able to download the updated scan list to the scanner.
Use the following procedure to add devices to a running DeviceNet. It is recommended that you
configure DeviceNet first, Experion second.
l Configuration of DeviceNet and Experion
l Downloading and restart

3.10.1 Configuration of DeviceNet and Experion

The following section describes about configuring DeviceNet and Experion:

- 50 -
 Chapter 3 - DeviceNet Block Configuration

DeviceNet Configuration: DeviceNet configuration can be performed either online, in which case
the new devices must be added to the DeviceNet early in the design process, or offline using the
EDS files for the devices of interest to perform configuration. You must update the scan list and
the input and/or output data configuration at a minimum. Whatever method is used, the
configuration report option in RSNetWorx can be used to perform Experion configuration
Experion Configuration: Using the RSNetWorx for DeviceNet configuration report, the following
Experion entities need to be configured.
l DeviceNet Interface Module - This will require making changes to an existing DeviceNet
Interface Module block. The additional devices to be added must be added to the Device
Configuration / Status tab. Also, if the Connection Size (Interface Module tab) has previously
been configured so that less than the maximum data size is transferred this also must be
configured.
l DeviceNet Devices - Create and configure Device blocks for the new devices to be added to the
DeviceNet network. These devices must be fully configured.
l DeviceNet I/O Channel blocks / Control Modules - DeviceNet Input Channel and DeviceNet
Output Channel blocks must be configured in Control Modules as required by the proposed
control strategy. All of these blocks must be fully configured.

3.10.2 Downloading and restart

Before downloading, you must first set the DNet Interface Module to IDLE using either a display or
Control Builder monitor mode.
DeviceNet Download: After the devices have been connected to the DeviceNet, download the
updated configuration to the DNet Interface Module.
Experion configuration Download: You need only to download the blocks that you have added and
any you may have changed during the configuration process. These blocks are all identified by
Control Builder in the project view. You may select all of these entities to download together, or
may select each individually.
Restarting the DeviceNet: You are now able to restart the DeviceNet.

3.11 Changing the address of the DNet Interface Module

Although Rockwell recommends that the DNet Interface Module is located at DeviceNet address 0,
it is possible to locate it at any address. If you need to change the address, you must not forget that
you have to update both the DeviceNet and Experion configurations. If you do not update both
configurations it will result in invalid information being displayed on the Experion displays.

3.11.1 To change the address of the DNet Interface Module

1. Change the state of the DNet Interface Module to IDLE.
2. Using RSNetWorx for DeviceNet commission the DNet Interface Module, selecting the new
address you want to use.
3. Using Control Builder, change the DeviceNet Address (Interface Module tab) to the new
address.
4. Download the updated DNET_IM block to the C200/C300 Controller.
5. Restart the DNet Interface Module.

- 51 -
 CHAPTER

4 DEVICENET BLOCK OPERATION

After the DNET_IM block is loaded, the Connection Status (IOCONNSTATUS parameter) is used to
verify that a communications connection has been successfully established with the DNet
Interface. Use of this parameter is helpful in debugging configuration errors. The I/O connection
status should assume the CONNECTED state if the module is present at the specified location. If
the physical location of the DNET_IM was improperly configured or if the DNET_IM card is
physically not present, the connection status will be IOMNOTFOUND.
l Operating a DNET_Device Block
l Operating a DNET_INCHAN Block
l Operating a DNET_OUTCHAN Block
l Activating the DeviceNet
l Monitoring the DeviceNet Status Display

4.1 Operating a DNET_Device Block

The following section describes about operating a DNET_Device Block.
Like all Experion I/O module blocks, the Execution State (EXECSTATE) parameter must be ACTIVE
in order for I/O data to be processed by the DNET_DEVICE function block. It is recommended that
the associated DNET_IM block be activated prior to the activation of the device/module block to
avoid warnings when activating the DNET_DEVICE function block.
The DNET_DEVICE function block is equipped with the following status parameter that is useful in
debugging configuration and communication problems:

Parameter Narrative Parameter Name Description

Device Status DEVICESTS DeviceNet Interface Module / Device composite status.

The DNET_DEVICE block generates diagnostic alarms. The block can be configured so that
alarming is disabled. The following diagnostic alarms are generated for the DNET_DEVICE block,
provided that the DNET_IM block is currently in the active state and alarming is enabled for the
block: The alarm is a composite status of the DeviceNet and the particular device. As such alarms
may be generated for all Devices on the DeviceNet or for a particular device. The alarms reflect
the value of the DEVICESTS parameter.

System Diagnostic Alarm Description

DnetNoIModuleRef No reference DnetIModule (SRCBLOCK) IOM FB specified
DnetIModuleInactive DnetIModule IOM FB is not Active (EXECSTATE)
DnetIModuleIdle DnetIModule IOM FB is Idle (DNETSTSIDLE)
DnetIModuleFault DnetIModule IOM FB is Faulted (DNETSTSFAULT)
DnetIModuleDisabled DnetIModule IOM FB is Disabled (DNETSTSDISBL)
DnetIModuleCommErr DnetIModule IOM FB is Comm Error (DNETSTSCFAIL)
DnetIModuleDup DnetIModule IOM FB is Dup address (DNETSTSDUP)
DnetIModulePower DnetIModule IOM FB is Power Fail (DNETSTSPOWR)
DevNotRegistered Device FB not registered with DnetIModule IOM FB (configuration

- 52 -
 Chapter 4 - DeviceNet Block Operation

System Diagnostic Alarm Description

error)
DevIdle Device Idle (DEVICESTS = Idle)
DevFail Device Fail (DEVICESTS = Fail)
DevAutoVerify Device Mismatch (DEVICESTS = Mismatch)
DevActive Device Active (DEVICESTS = Active)

4.2 Operating a DNET_INCHAN Block

The channel block is activated as part of the process of activating the Control Module in which it is
contained.
Two parameters show the overall state of the Input Channel block data.

Parameter Parameter Description

Narrative Name
Bad Config Flag BADCONFIGFL Configuration conflict between channel block and associated
device block.
Bad Input Status BADINPUTSTS Communications error or failure between block and input
device.

The Numeric data configured for an Input Channel is displayed on the Numeric Data tab.

The following table shows the PV Group:

Parameter Narrative Parameter Name Description

Process Input Scaled PV Process Input Scaled Value.
Process Input Raw PVRAW Process Input Raw Value.
Process Input Status PVSTS Process Input Status.

The current value of and status of the discrete data configured for an Input Channel is displayed
on the Discrete Data tab.

- 53 -
 Chapter 4 - DeviceNet Block Operation

The following table shows the Discrete Data Group:

Parameter Narrative Parameter Name Description

Input Value PVFL Process Input Value.
Bad PVFL Status BADPVFLSTS Bad Process Input Status.

4.3 Operating a DNET_OUTCHAN Block

The channel block is activated as part of the process of activating the Control Module in which it is
contained.
Two parameters show the overall state of the Output Channel block data.

Parameter Narrative Parameter Name Description

Bad Chan/Device BADCONFIGFL Configuration conflict between channel block and
Config associated device block.
Bad Output Status BADOUTPUTSTS Communications error or failure between block and
output device.

The Numeric data configured for an Output Channel is displayed on the Numeric Data tab.

The following table shows the OP Group:

Parameter Narrative Parameter Name Description

Output Value OP Output Value Scaled.
Scaled Raw Value OPRAW Output Value Raw.
Bad OP Status BADOPSTS Bad Output Status Flag.

- 54 -
 Chapter 4 - DeviceNet Block Operation

The current value of and status of the discrete data configured for an Output Channel are
displayed on the Discrete Data tab.

The following table shows the Discrete Data Group:

Parameter Narrative Parameter Name Description

Output Value OPFL Output Value.
Bad OPFL Status BADOPFLSTS Bad Output Status.

4.4 Activating the DeviceNet

This section describes the sequence in which to activate the DeviceNet devices, using the Control
Builder Monitor mode. In practice this is more likely to be performed using Group Displays, but the
sequence should remain the same.
l Activate the CEE
l Activate the DNET_IM block
l Activate the Device blocks
l Set the 1756-DNB into RUN

4.4.1 Activate the CEE

Before any DeviceNet devices can be activated the CEE must be active. Select the CEE in the CB
Monitor tree and use any of the methods available to activate the CEE.

l Use the Toggle State symbol located on the tool bar.

l Select Activate from the Right Mouse Button invoked context menu.

After confirming your intended action, the CEE will activate and the CEE in the CB Monitor tree will
change color to Green.

- 55 -
 Chapter 4 - DeviceNet Block Operation

4.4.2 Activate the DNET_IM block

Once the CEE is active you should activate the DNET_IM block. Again, select the DNET_IM module
in the CB Monitor tree and use any of the methods available to activate the DNET_IM block. After
confirming your intended action the DNET_IM block will activate and the block will change color to
Green. Note that the DNET_IM block can also be activated using the PCF for the block.

To activate the DNET_IM block

1. Select the DNET_IM block in the CB Monitor tree.

2. Open the PCF for the block.
3. Select the Interface Module tab.
4. Select the ACTIVATE option in the Execution State parameter.
Result: The DNET_IM will activate. The IO Connection Status will show as CONNECTED.

4.4.3 Activate the Device blocks

However, although the status of devices can be viewed, and the DeviceNet is now operational, data
is not yet being transferred any further than to the DNET_IM block.
To activate the Device blocks select all the devices on the CB Monitor tree and use any of the
methods available to activate the device blocks.
You may also activate device blocks individually using any of the methods available, including using
the PCF Module Configuration tab.

- 56 -
 Chapter 4 - DeviceNet Block Operation

When the Device blocks have been activated, but the DNet Interface module is still in IDLE, the CB
Monitor view will show the Devices in Red.

4.4.4 Set the 1756-DNB into RUN

Although the block that represents the 1756-DNB is active the 1756-DNB is still IDLE. Put the
1756-DNB into RUN using the following procedure.

To set the 1756-DNB into RUN:

1. Select the DNET_IM block in the CB Monitor tree.

2. Open the PCF for the block.
3. Select the Commands/Status tab.
4. Select the RUN option in the Command Register parameter.
Results:
l The 1756-DNB will transition to RUN.
l The Interface Module Status Register Group will show the Run selection checked.
l The 1756-DNB will show RUN on its display.
l The DeviceNet Status Data Group will display an increasing value in the I/O Scan Count.

The status of the DeviceNet can now be viewed on the Device Configuration/Status Tab.

- 57 -
 Chapter 4 - DeviceNet Block Operation

After the DNet Interface module is transitioned to RUN, the CB Monitor view will show the
devices in Green. At this point the DeviceNet network is running and the DNet Interface and
DNET_IM block are transferring data to one another.
Finally activate the control module(s) that use the devices running on the network.

4.5 Monitoring the DeviceNet Status Display

The following shows an example of the DNET_IM Block, Device Configuration/Status tab for a
DeviceNet where all configured devices work correctly.

l Normal operations status of DeviceNet

l Command/Status of DeviceNet Status
l Typical device status of DeviceNet

4.5.1 Normal operations status of DeviceNet

Notes about the display:

- 58 -
 Chapter 4 - DeviceNet Block Operation

l The Status of the Scanner (Address 0), is shown as RUN.

l Devices that are operating correctly show Status = ACTIVE, Status Code = 0 and Status
Message = OK.
l Network Addresses not in use show Status = blank, Status Code = -1 and Status Message = 'Not
Configured'

4.5.2 Command/Status of DeviceNet Status

The Command/Status screen is shown in the following figure.

The Status Register value is RUN. No other value is shown.

No Devices are shown as Faulted in the DeviceNet Status Data group.

4.5.3 Typical device status of DeviceNet

A typical Device appears as follows -- the Execution State = ACTIVE, the Device Status =
DEVACTIVE.

- 59 -
 CHAPTER

5 TROUBLESHOOTING DEVICENET STATUS FAILURES

The following sections describes about Troubleshooting DeviceNet Status Failures:

The following failure scenarios are described:
l Device not available.
l DNET Interface module faulted.
l Power removed from DNET Interface module.
l Power removed from DeviceNet network.

l Device not available

l DNet Interface module faulted
l Power removed from DNet Interface module
l Power removed from DeviceNet Network
l Status Codes

5.1 Device not available

When a configured device fails, a number of blocks are affected.
A Device Fail alarm appears on the Alarm Summary when a device is not available.

The following figure shows an example of the DNET_IM Block, Device Configuration/Status tab for
a DeviceNet where a configured device has failed and the DNet Interface Module is no longer able
to communicate with it.

- 60 -
Chapter 5 - Troubleshooting DeviceNet Status Failures

The Devices that are not operating correctly show Status = FAILED, Status Code = 78 and Status
Message = Device in Scan List does not exist. A complete list of Status Codes and associated Status
Message are included in this section.
The Command/Status screen is shown in the following figure.

Notes about the display:

l The Status Register value is RUN. The Device Failure checkbox is also selected.
l The Faulted Device Address and Faulted Device Status are shown in the DeviceNet Status Data
group. If multiple devices have failed these two parameters will show each device in turn.

DNET_DEVICE Block indications when a device is not available is shown in the following figure:

The Bad Input Status flag is also checked on any DNET_INCHAN block that is receiving data from
the failed device.

- 61 -
 Chapter 5 - Troubleshooting DeviceNet Status Failures

The Bad PVFL Status flags are asserted on the Discrete Data tab.

5.2 DNet Interface module faulted

The following displays show the effect of setting the DNet Interface to FAULT using the Command
Register (DNETIMCMD) parameter.
Alarms for the respective devices appear on the Alarm Summary with a DeviceNet IM Faulted
status.

The following section describes about the DNET_IM Block indications when a DNet Interface is set
to FAULT
Notes about the display:

- 62 -
Chapter 5 - Troubleshooting DeviceNet Status Failures

l The Interface Module Status Register value shows IDLE (the status before FAULT), FAULT and
DEVICE FAILURE.
l The DeviceNet Status Data shows that the Interface Module Status (DNETIMSTS), and the
Failed Device Address/Failed Device Status pair show the devices that have failed. This display
includes the DNet Interface Device.

Notes about the display:

l The Interface Module Status Register value shows the Status = FAILED, Status Code = 81,
Status Message = Network Fault.
l All devices on the network show Status = FAILED, Status Code = 72, Status Message = Device
Not Communicating'.
l Note that the E3 Plus, shown at Address 4 as Not Configured, identifies a mismatch between
the Experion and DeviceNet configurations.

Notes about DNET_DEVICE Block indications when a DNet Interface is set to FAULT:
l The Device Status of all DNET_DEVICE blocks is DNETIMODULEFAULT.

- 63 -
 Chapter 5 - Troubleshooting DeviceNet Status Failures

Notes about the DNET_INCHAN/DNET_OUTCHAN Block indications when a DNet Interface is set to
FAULT:
l The Bad Input Status/Bad Output Status parameter of all DNET_INCHAN / DNET_OUTCHAN
blocks is asserted.

Notes about the display:

l The Bad PVFL Status/Bad OPFL Status parameter of all DNET_INCHAN / DNET_OUTCHAN
blocks is asserted.

Notes about Control Module indications when a DNet Interface is set to FAULT:
l The BADINPUTSTS/BADOUTPUTSTS parameters are also shown on the control module
drawing for the DNET_INCHAN/DNET_OUTCHAN block assuming that the parameters are
displayed on the block in the Monitor View.

- 64 -
 Chapter 5 - Troubleshooting DeviceNet Status Failures

5.3 Power removed from DNet Interface module

The following displays show the effect of removing power from the DNet Interface Module. This is
most likely to happen if power is removed from the chassis in which the DNet Interface module
resides.
Notes about the Alarm Summary indications when Power is removed from DNet Interface module:
l A Communication Error alarm for the DNet Interface appears on the Alarm Summary.

Notes about DNET_IM Block indications when Power is removed from DNet Interface module:
l The IO Connection Status parameter shows IOMNOTFOUND.

- 65 -
 Chapter 5 - Troubleshooting DeviceNet Status Failures

Note: The Command/Status tab and the Device Configuration/Status tab show incomplete/out of
date information in this case, as the Controller and the DNet Interface are no longer able to
transfer data between each other.

5.4 Power removed from DeviceNet Network

The following displays show the effect of removing power from the DeviceNet Network. This is most
likely to happen if the cable is removed from the DNet Interface to the network, or if a network is
not terminated correctly.
Notes about Alarm Summary indications when Power is removed from DeviceNet Network:
l A DeviceNet IM Power Fail alarm appears for each device on the DeviceNet network.

Notes about DNET_IM Block indications when Power is removed from DeviceNet Network:
l The DNet Interface shows as Status = FAILED, Status Code = 92, Status Message = No network
power detected on comm. Port.
l All devices on the network show as Status = FAILED, Status Code = 72, Status Message = Device
not communicating.

Notes about the display:

- 66 -
 Chapter 5 - Troubleshooting DeviceNet Status Failures

l The Interface Module Status Register value shows RUN, POWER DETECT and DEVICE
FAILURE.
l The DeviceNet Status Data, Interface Module Status (DNETIMSTS) shows that the DNet
Interface module has failed, as this value is not zero.
l The DeviceNet Status Data, Failed Device Address/Failed Device Status pair show the devices
that have failed. This display includes the DNet Interface Device.

5.5 Status Codes

Status Code Status Message

70 Module Failed - Duplicate Node Address
71 Illegal data in scan list table
72 Device not communicating
73 Device info does not match key in scan table
74 Data overrun on port detected
75 No scan list is active in the module
76 No direct network traffic for module detected
77 Device data size does not match scan list entry
78 Device in Scan List table does not exist
79 Module has failed to transmit a message
80 Module Idle
81 Network Fault
82 Sequence error in I/O message from device
83 Device communication error with module
84 DeviceNet network is initializing
85 Data size error
86 Zero length data from device
87 The primary owner has not allocated the slave
88 Connection mismatch between primary and shared
89 Auto Device Replacement initialization failed
90 Communication port disabled by user
91 Communication error - bus off condition detected

- 67 -
 Chapter 5 - Troubleshooting DeviceNet Status Failures

Status Code Status Message

92 No network power detected on comm port
95 Application FLASH update in progress
97 Module operation halted by user command
98 General Firmware error

For further information about these error codes refer to the 1756-DNB User Manual provided by
Rockwell Automation.

- 68 -
CHAPTER

6 DEVICENET INTERFACE PARAMETER REFERENCE

This document describes the parameters appearing on the blocks that are contained in the
DeviceNet Interface library. The DeviceNet Library specific parameters are listed in alphabetical
order. Full descriptions of common parameters (for example, IOMTYPE) can be found in Experion
PDF Collection. Standard tabs such as Server, Block Pins, Configuration Parameters, Monitoring
Parameters and Block Preferences, which contain only standard parameters are not described in
this document. The DeviceNet Library specific parameters are listed by block type and are fully
described in the alphabetical order listing.

ATTENTION
This document supports users of the DeviceNet Interface Library developed for use with
Experion systems (PlantScape R500 and later). The information in this document is
applicable only the releases specified for the DeviceNet Interface Library, and should not be
used with any other earlier release prior to PlantScape R500.

l DeviceNet Interface Module (DNET_IM) Function Block

l DeviceNet Device (DNET_DEVICE) Function Block
l Input Channel (DNET_INCHAN) Function Block
l Output Channel (DNET_OUTCHAN) Function Block
l BADCONFIGFL
l BADINPUTSTS
l BADOPFLSTS[0..31]
l BADOPSTS[0..7]
l BADOUTPUTSTS
l BADPVFLSTS[0..31]
l BASEPERIOD
l DATAOFFBIT
l DATAOFFSIZE
l DATAOFFWORD
l DEVICE[0..63]
l DEVICEADDRESS
l DEVICESTS
l DEVICESTS[0..63]
l DEVICESTSCODE[0..63]
l DEVICESTSMSG[0..63]
l DNETFLTADDR
l DNETFLTSTS

- 69 -
Chapter 6 - DeviceNet Interface Parameter Reference

l DNETIMADDR
l DNETIMADDRESS
l DNETIMCMD
l DNETIMSTS
l DNETIMSTSAUTOV
l DNETIMSTSCFAIL
l DNETIMSTSDFAIL
l DNETIMSTSDISBL
l DNETIMSTSDUP
l DNETIMSTSFAULT
l DNETIMSTSIDLE
l DNETIMSTSPOWER
l DNETIMSTSRUN
l DNETIMTYPE
l DNETSCANCNT
l FLBITOFFSET[0..31]
l FLBYTEOFFSET[0..31]
l FLDESC[0..31]
l FLENABLE[0..31]
l INCONNSIZE
l INOFFSETBIT[0..9]
l INOFFSETWORD[0..9]
l INSIZE[0..9]
l IOCONNSTATUS
l OP[0..7]
l OPDESC[0..7]
l OPENABLE[0..7]
l OPFL[0..31]
l OPHIACT[0..7]
l OPHIRAW[0..7]
l OPLOACT[0..7]
l OPLORAW[0..7]
l OPOFFSET[0..7]
l OPRAW[0..7]
l OPRAWSIZE[0..7]
l OUTCONNSIZE
l OUTOFFSETBIT[0..9]
l OUTOFFSETWORD[0..9]
l OUTSIZE[0..9]
l PV[0..7]
l PVDESC[0..7]
l PVENABLE[0..7]

- 70 -
 Chapter 6 - DeviceNet Interface Parameter Reference

l PVFL[0..31]
l PVHIACT[0..7]
l PVHIRAW[0..7]
l PVLOACT[0..7]
l PVLORAW[0..7]
l PVOFFSET[0..7]
l PVRAW[0..7]
l PVRAWSIZE[0..7]
l PVSTS[0..7]
l SRCBLOCK
6.1 DeviceNet Interface Module (DNET_IM) Function Block
This section lists parameters associated with the DeviceNet Interface Module (DNET_IM) Function
Block. It is organized by parameters that appear on tabs on their respective dialogs.
Following table shows the Identification Group:

Parameter Name Parameter Narrative Description

NAME Name The Name assigned to the DeviceNet Interface Module
DESC Module Description A textual description of the Interface Module

Following table shows the Module Information Group:

Parameter Name Parameter Narrative Description

IOMTYPE IO Module Type Always DeviceNet Interface Module

Following table shows the Rack Address Group:

Parameter Parameter Description

Name Narrative
IOMSLOT IOM Slot The physical slot number of the module in the chassis.
Number in
chassis
ULCNBMAC Uplink CNB Adrs MAC Address of the uplink CNI - in the chassis which contains the
in IO Rack module (0 if co-located with a non-redundant CPM)
DLCNBSLOT Downlink CNB Slot number of the downlink CNI - in the controller chassis (0 if co-
Slot Number located with a non-redundant CPM)

l Interface Module Tab of DeviceNet Interface Module (DNET_IM)

l Device Configuration/Status Tab of DeviceNet Interface Module (DNET_IM)
l Command/Status Tab of DeviceNet Interface Module (DNET_IM)

6.1.1 Interface Module Tab of DeviceNet Interface Module (DNET_

IM)
Following table shows the Status Group:

Parameter Parameter Description

Name Narrative
EXECSTATE Execution Always DeviceNet Interface Module
State
IOCONNSTATUS IO Operational parameter, which shows the status of the connection
Connection between the block and DNet Interface module

- 71 -
 Chapter 6 - DeviceNet Interface Parameter Reference

Parameter Parameter Description

Name Narrative
Status
ALMENBSTATE Alarming Used to enable/disable the reporting of alarms originating from
Enabled the block.

Following table shows the Interface Module Group:

Parameter Name
DNETIMTYPE
DNETIMADDRESS

Following table shows the Connection Size Group:

Parameter Name
INCONNSIZE
OUTCONNSIZE

Following table shows the Connection Timing Group:

Parameter Name
BASEPERIOD

6.1.2 Device Configuration/Status Tab of DeviceNet Interface

Module (DNET_IM)
Following table shows the Device Addressing Group:
Configuration parameter

Parameter Name
DEVICE[0..63]

Operational Parameters

Parameter Name
DEVICESTS[0..63]
DEVICESTSCODE[0..63]
DEVICESTSMSG[0..63]

6.1.3 Command/Status Tab of DeviceNet Interface Module (DNET_

IM)
Following table shows the DeviceNet Commands Group

Parameter Name
DNETIMCMD

Following table shows the Interface Module Status Register Group

Parameter Name
DNETIMSTSAUTOV
DNETIMSTSIDLE
DNETIMSTSRUN
DNETIMSTSFAULT

- 72 -
 Chapter 6 - DeviceNet Interface Parameter Reference

Parameter Name
DNETIMSTSDISBL
DNETIMSTSCFAIL
DNETIMSTSDFAIL
DNETIMSTSPOWER

Following table shows the DeviceNet Status Data Group

Parameter Name
DNETSCANCNT
DNETIMADDRESS
DNETIMSTS
DNETFLTADDR
DNETFLTSTS

6.2 DeviceNet Device (DNET_DEVICE) Function Block

This section lists parameters associated with the DeviceNet Device (DNET_DEVICE) Function Block.
It is organized by parameters that appear on tabs on their respective dialogs.

l Main Tab of DeviceNet Device (DNET_DEVICE)

l Module Configuration Tab of DeviceNet Device (DNET_DEVICE)

6.2.1 Main Tab of DeviceNet Device (DNET_DEVICE)

Following table shows the Identification Group:

Parameter Name Parameter Narrative Description

NAME Name The Name assigned to the Device
DESC Module Description A textual description of the Device

Following table shows the IO Module Information Group

Parameter Parameter Narrative Description

Name
IOMTYPE Module Type Always DeviceNet Interface Module
Currently assigned The Input and Output Channels currently assigned to
channels the device.

6.2.2 Module Configuration Tab of DeviceNet Device (DNET_DEVICE)

Following table shows the Device Addressing Group:
Configuration Parameters:

Parameter Name
PVSTS[0..7]
SRCBLOCK
DEVICEADDRESS

Operational Parameters:

Parameter Name Parameter Narrative Description

EXECSTATE Execution State Used to Activate and Inactivate the block.

Following table shows the Data Format Group:

- 73 -
 Chapter 6 - DeviceNet Interface Parameter Reference

Parameter Name
INOFFSETWORD[0..9]
INOFFSETBIT[0..9]
INSIZE[0..9]
OUTOFFSETWORD[0..9]
OUTOFFSETBIT[0..9]
OUTSIZE[0..9]

6.3 Input Channel (DNET_INCHAN) Function Block

This section lists parameters associated with the Input Channel (DNET_INCHAN) Function Block. It
is organized by parameters that appear on tabs on their respective dialogs.
l Main Tab of Input Channel (DNET_INCHAN) Function Block
l Input Data Location Tab of Input Channel (DNET_INCHAN)
l Numeric Input Configuration Tab of Input Channel (DNET_INCHAN)
l Discrete Input Configuration Tab of Input Channel (DNET_INCHAN)
l Numeric Data Tab of Input Channel (DNET_INCHAN)
l Discrete Data Tab of Input Channel (DNET_INCHAN)

6.3.1 Main Tab of Input Channel (DNET_INCHAN) Function Block

Following table shows the Channel Block Configuration Group:

Parameter Name Parameter Narrative Description

NAME Channel Name The Name assigned to the Channel.
ORDERINCM Execution Order in CM The order in which the block will be executed in the CM.

Following table shows Channel Block to IO Module Assignment Group:

Parameter Parameter Narrative Description

Name
MODULE MODULE The Device to which the Channel is assigned.
MODTYPE Module Type Always Generic DeviceNet Device.
Currently assigned The Input and Output Channels currently assigned to the
channels selected device.

6.3.2 Input Data Location Tab of Input Channel (DNET_INCHAN)

Following table shows Data Location Group:

Parameter Name
DATAOFFWORD
DATAOFFBIT
DATAOFFSIZE

Following table shows Operational Status Group:

Parameter Name
BADCONFIGFL
BADINPUTSTS

- 74 -
 Chapter 6 - DeviceNet Interface Parameter Reference

6.3.3 Numeric Input Configuration Tab of Input Channel (DNET_

INCHAN)
Following table shows PV Configuration Group:

Parameter Name
PVENABLE[0..7]
PVDESC[0..7]
PVOFFSET[0..7]
PVRAWSIZE[0..7]

Following table shows PVRAW to PV Scaling Group:

Parameter Name
PVLORAW[0..7]
PVHIRAW[0..7]
PVLOACT[0..7]
PVHIACT[0..7]

6.3.4 Discrete Input Configuration Tab of Input Channel (DNET_

INCHAN)
Following table shows PVFL Configuration Group:

Parameter Name
FLENABLE[0..31]
FLDESC[0..31]
FLBYTEOFFSET[0..31]
FLBITOFFSET[0..31]

6.3.5 Numeric Data Tab of Input Channel (DNET_INCHAN)

Following table shows Numeric Data Group:

Parameter Name
PV[0..7]
PVRAWSIZE[0..7]
PVSTS[0..7]

6.3.6 Discrete Data Tab of Input Channel (DNET_INCHAN)

Following table shows Discrete Data Group:

Parameter Name
PVFL[0..31]
BADPVFLSTS[0..31]

6.4 Output Channel (DNET_OUTCHAN) Function Block

This section lists parameters associated with the Output Channel (DNET_OUTCHAN) Function
Block. It is organized by parameters that appear on tabs on their respective dialogs.

- 75 -
 Chapter 6 - DeviceNet Interface Parameter Reference

l Main Tab of Output Channel (DNET_OUTCHAN) Function Block

l Output Data Location Tab of Output Channel (DNET_OUTCHAN)
l Numeric Output Configuration Tab of Output Channel (DNET_OUTCHAN)
l Discrete Output Configuration Tab of Output Channel (DNET_OUTCHAN)
l Numeric Data Tab of Output Channel (DNET_OUTCHAN)
l Discrete Data Tab of Output Channel (DNET_OUTCHAN)

6.4.1 Main Tab of Output Channel (DNET_OUTCHAN) Function

Block
Following table shows the Channel Block Configuration Group:

Parameter Name Parameter Narrative Description

NAME Channel Name The Name assigned to the Channel.
ORDERINCM Execution Order in CM The order in which the block will be executed in the CM.

Following table shows the Channel Block to IO Module Assignment Group:

Parameter Parameter Narrative Description

Name
MODULE MODULE The Device to which the Channel is assigned.
MODTYPE Module Type Always Generic DeviceNet Device.
Currently assigned The Input and Output Channels currently assigned to the
channels selected device.

6.4.2 Output Data Location Tab of Output Channel (DNET_

OUTCHAN)
Following table shows the Output Data Location Group:

Parameter Name
DATAOFFWORD
DATAOFFBIT
DATAOFFSIZE

Following table shows the Operational Status Group:

Parameter Name
BADCONFIGFL
BADOUTPUTSTS

6.4.3 Numeric Output Configuration Tab of Output Channel (DNET_

OUTCHAN)
Following table shows the OP Configuration Group:

Parameter Name
OPENABLE[0..7]
PVDESC[0..7]
OPOFFSET[0..7]
OPRAWSIZE[0..7]

Following table shows the OP to OPRAW Scaling Group:

- 76 -
 Chapter 6 - DeviceNet Interface Parameter Reference

Parameter Name
OPLORAW[0..7]
OPHIRAW[0..7]
OPLOACT[0..7]
OPHIACT[0..7]

6.4.4 Discrete Output Configuration Tab of Output Channel (DNET_

OUTCHAN)
Following table shows the OPFL Configuration Group:

Parameter Name
FLENABLE[0..31]
FLDESC[0..31]
FLBYTEOFFSET[0..31]
FLBITOFFSET[0..31]

6.4.5 Numeric Data Tab of Output Channel (DNET_OUTCHAN)

Following table shows the Numeric Data Group:

Parameter Name
IOCONNSTATUS
OP[0..7]
OPRAW[0..7]
BADOPSTS[0..7]

6.4.6 Discrete Data Tab of Output Channel (DNET_OUTCHAN)

Following table shows the Discrete Data Group:

Parameter Name
OPFL[0..31]
BADOPFLSTS[0..31]

6.5 BADCONFIGFL

Specific to DNET_INCHAN and DNET_OUTCHAN

Block(s)
Description Configuration conflict between channel block and device/module block detected at
block activation.
Data Type Boolean
Range Off(0) No configuration conflict.
On(1) Configuration conflict/mismatch detected.
Default Off(0)
Config Load No
Access Lock View Only
Residence CEE
Related INCONNSIZE
Parameters
OUTCONNSIZE

- 77 -
 Chapter 6 - DeviceNet Interface Parameter Reference

Configured No
on
DeviceNet
Remarks l When asserted, this parameter indicates an invalid combination of
configuration parameters. Specifically, DATAOFFSET + DATASIZE must be less
than or equal to the INCONNSIZE or OUTCONNSIZE of the associated
device/module block.
l The configuration is validated against the device/module block when the CM is
activated. Thus, this parameter will not be asserted until the CM is activated.
l This parameter is not asserted if the module block is not loaded or is inactive.

6.6 BADINPUTSTS

Specific to DNET_INCHAN
Block(s)
Description Communications error or failure between block and input device
Data Type Boolean.
Range Off(0) No communications errors.
On(1) Communication error, resulting in no data
flow between block and end device.
Default Off(0)
Config Load No
Access Lock View Only
Residence CEE
Related About This Document
Parameters
DEVICESTS
Configured No
on
DeviceNet
Remarks l When asserted, this parameter indicates that data is not actively flowing from
the output device to the output channel block. This can occur due to any of the
following conditions
l If any of the containing CM, parent device/module block or DNET_IM block are
INACTIVE
l If the device/module block is not in the DEVONLINE state.

6.7 BADOPFLSTS[0..31]

Specific to DNET_OUTCHAN
Block(s)
Description Bad Communication Status Indicator for OPFL[x]
Data Type BOOLEAN
Range Off(0) Good status
On(1) Bad status
Default Off(0)
Config Load No
Access Lock View Only
Residence CEE
Related OPFL[0..31]

- 78 -
 Chapter 6 - DeviceNet Interface Parameter Reference

Parameters FLENABLE[0..31]
Configured No
on
DeviceNet
Remarks This bad status indicator will become asserted if the channel block's output data is
not actively being transferred to the output device for any reason, specifically if
either 1) BADOUTPUTSTS is asserted or 2) FLENABLE[x] is configured to the Off
state.

6.8 BADOPSTS[0..7]

Specific to Block DNET_OUTCHAN

(s)
Description Bad Output[x] Status Flag
Data Type BOOLEAN
Range 0 Off OP status is good
1 On OP status is bad
Default Bad
Config Load No
Access Lock View Only
Residence CEE
Related OPENABLE[0..7]
Parameters
Configured on No
DeviceNet
Remarks BADOPSTS[x] is asserted if either 1) BADOUTPUTSTS is asserted or 2)
PVENABLE[x] is configured to the Off state.

6.9 BADOUTPUTSTS

Specific to DNET_OUTCHAN
Block(s)
Description Communications error or failure between block and input device
Data Type Boolean.
Range Off(0) No communications errors.
On(1) Communication error, resulting in no data
flow between block and end device.
Default Off(0)
Config Load No
Access Lock View Only
Residence CEE
Related About This Document
Parameters
DEVICESTS
Configured No
on
DeviceNet
Remarks l When asserted, this parameter indicates that data is not actively flowing from
the output device to the output channel block. This can occur due to any of the
following conditions
l If any of the containing CM, parent device/module block or DNET_IM block are

- 79 -
 Chapter 6 - DeviceNet Interface Parameter Reference

INACTIVE
l If the device/module block is not in the DEVONLINE state.

6.10 BADPVFLSTS[0..31]

Specific to DNET_INCHAN
Block(s)
Description Bad Communication Status Indicator for PVFL[x]
Data Type BOOLEAN
Range Off(0) Good status
On(1) Bad status
Default Off(0)
Config Load No
Access Lock View Only
Residence CEE
Related PVFL[0..31]
Parameters
FLENABLE[0..31]
Configured No
on
DeviceNet
Remarks This bad status indicator will become asserted if the channel block is not actively
receiving valid input data from the input device for any reason, specifically if either 1)
BADINPUTSTS is asserted or 2) FLENABLE[x] is configured to the Off state.

6.11 BASEPERIOD

Specific to DNET_IM
Block(s)
Description CEE Base period (in ms)
Data Type ENUM
Range 50 Ms
5 Ms
Default 50 Ms
Config Yes
Load
Access Lock Application Developer
Residence CEE
Related
Parameters
Configured No
on
DeviceNet
Remarks Specifies the base period at which the CEE to which the DNET_IM is assigned is
running at. The value of this parameter determines the values of the PUBRATEREAD
and PUBRATEWRITE parameters. The 5 Ms value can only be used when the
Interface Module is located in the controller chassis.

6.12 DATAOFFBIT

Specific to DNET_INCHAN and DNET_OUTCHAN

- 80 -
 Chapter 6 - DeviceNet Interface Parameter Reference

Block(s)
Description Data Offset (Input or Output) in bits.
Data Type INT32
Range 0, 8, 16 or 24
The starting location (DATAOFFWORD + DATAOFFBIT) plus the data size (DATASIZE)
must be less than the connection size (INCONNSIZE, OUTCONNSIZE) of the
associated DNET_IM block.

Default 0
Config Load Yes
Access Lock Application Developer
Residence CEE
Related DATAOFFWORD
Parameters
INCONNSIZE
OUTCONNSIZE
Configured Yes
on
DeviceNet
Remarks This parameter, along with the DATAOFFWORD parameter, specifies the starting
location of the data referenced by this channel within the Data Assembly (Input or
Output).
Invalid configurations are detected after block activation is attempted.

6.13 DATAOFFSIZE

Specific to DNET_INCHAN and DNET_OUTCHAN

Block(s)
Description Data Offset (Input or Output) in bytes
Data Type INT32
Range Must be a multiple of 8.
The starting location (DATAOFFWORD + DATAOFFBIT) plus the data size
(DATAOFFSIZE) must be less than the connection size (INCONNSIZE,
OUTCONNSIZE) of the associated DNET_IM block.
Default 8
Config Load Yes
Access Lock Application Developer
Residence CEE
Related DATAOFFWORD
Parameters
DATAOFFBIT
INCONNSIZE
OUTCONNSIZE
Configured No
on
DeviceNet
Remarks l This parameter specifies the size (in bits) of the data referenced by this channel,
which is contained within the Data Assembly (Input or Output).
l Invalid configurations are detected after block activation is attempted.

- 81 -
 Chapter 6 - DeviceNet Interface Parameter Reference

6.14 DATAOFFWORD

Specific to DNET_INCHAN and DNET_OUTCHAN

Block(s)
Description Data Offset (Input or Output) in words
Data Type INT32
Range The starting location (DATAOFFWORD + DATAOFFBIT) plus the data size (DATASIZE)
must be less than the connection size (INCONNSIZE, OUTCONNSIZE) of the
associated DNET_IM block.
Default 0
Config Load Yes
Access Lock Application Developer
Residence CEE
Related INCONNSIZE
Parameters
OUTCONNSIZE
Configured Yes
on
DeviceNet
Remarks l This parameter, along with the DATAOFFBIT parameter, specifies the starting
location of the data referenced by this channel within the Data Assembly (Input
or Output).
l Invalid configurations are detected after block activation is attempted

6.15 DEVICE[0..63]
Device Address - The numbered column, 0 - 63, represents the Device Address of the Device
described at the index. Note that there is no parameter that holds the Device Address. This is
implied in the CCL code.

Specific to Block DNET_IM

(s)
Description Device
Data Type 40 Character Text String
Range N/A
Default
Config Load Yes
Access Lock Application Developer
Residence SR
Related
Parameters
Configured on Yes
DeviceNet
Remarks Although no checks are performed, this is expected to be the same description
used for the device on RSNetWorx.

6.16 DEVICEADDRESS

Specific to Block DNET_DEVICE

(s)
Description DeviceNet Address

- 82 -
 Chapter 6 - DeviceNet Interface Parameter Reference

Data Type INT16

Range 0 - 63
Default 0
Config Load Yes
Access Lock Application Developer
Residence CEE
Related About This Document
Parameters
Configured on No
DeviceNet
Remarks The entry should match the actual DeviceNet configuration, and the entry made
for the device in the DNET_IM function block.

6.17 DEVICESTS

Specific to DNET_DEVICE
Block(s)
Description DeviceNet Interface Module / Device composite status.
Data Type Enumeration of DEVICESTATUS
Range 0 Unknown Default value
1 DeviceNet Invalid or missing DNET_IM reference. Resolution: Reconfigure
IM Not the DNET_IM block reference and reload.
Specified
2 DeviceNet DNET_IM block is INACTIVE.
IM Not
Active
3 DeviceNet The DNET_IM is in IDLE.
IM Idle
4 DeviceNet The DNET_IM is in FAULT.
IM Faulted
5 DeviceNet The DNET_IM block is DISABLED.
IM Disabled
6 DeviceNet There is a communications error between the DNET_IM and the
IM Comm DNet Interface.
Error
7 DeviceNet The DNet Interface has tried to come online with a Device
IM Dup Address which is the same as an existing device.
Address
8 DeviceNet The DNet Interface cannot detect any power on the DeviceNet.
IM Power
Fail
9 Device The device block could not be registered with the appropriate
Registration DNET_IM block.
Err
Resolution: Ensure a matching configuration between DNET_IM
table and IOM block, including Device Address and Data Offsets
that correspond to the data expected by the block.
10 Device Idle The EXECSTATE of the device is INACTIVE
11 Device Fail The device has failed.
12 Device The configuration of the device in RSNetWorx is not the same as
Mismatch the data received by the DNet Interface.
Default 0 - Unknown
Config Load No

- 83 -
 Chapter 6 - DeviceNet Interface Parameter Reference

Access Lock View Only

Residence NOLOAD
Related
Parameters
Configured No
on
DeviceNet
Remarks

6.18 DEVICESTS[0..63]

Specific to DNET_IM
Block(s)
Description Device Status
Data Type STRING
Range 20 char
Default None
Config No
Load
Access AppDev Only
Lock
Residence CEE
Related
Parameters
Configured No
on
DeviceNet
Remarks The DNET_IM block maintains a 'device status' array for all device addresses on the
DeviceNet network. This array is an interpretation of 4 registers that are part of the
DNet Interface Status Structure. The registers are the Device Idle Register, Device
Failure Register, Autoverify Failure Register and the Active Node Register. The
following values are displayed for a device. RUN is only shown for the Device Address
that is occupied by the DNet Interface (as defined by parameter DNETIMADDRESS)
and is displayed even if an entry is not present in the register (that is, equal to 0)

Value Register
Device Idle Device Failure Autoverify Failure Active Node
MISMATCH x
FAILED x
ACTIVE x
IDLE x
RUN x

6.19 DEVICESTSCODE[0..63]

Specific to DNET_IM
Block(s)
Description Device status code.
Data Type INT16
Range 0, 70 - 97
Default 0

- 84 -
 Chapter 6 - DeviceNet Interface Parameter Reference

Config Load No
Access Lock AppDev Only
Residence CEE
Related DEVICESTSMSG[0..63]
Parameters
Configured on No
DeviceNet:
Remarks Shows the status of the device on the network. It is taken from the Device Status
Array that is part of the DNet Interface Status Structure.
0 - No error.
> 0 - The value is the error code being reported by the Interface Module.

6.20 DEVICESTSMSG[0..63]

Specific to Block(s) DNET_IM

Description Device status message array.
Data Type STRING
Range 50 character
Default OK
Config Load No
Access Lock AppDev Only
Residence CEE
Related Parameters DEVICESTSCODE[0..63]
Configured on No
DeviceNet:
Remarks Shows a textual description of the device Status being reported for the
device.
0 - OK
70 - 99 - Message as shown in DNet Interface User Manual.

6.21 DNETFLTADDR

Specific to DNET_IM
Block(s)
Description Network address of a Device that the Interface Module is having issues with
Data Type INT16
Range 0 - 63
Default 0 - No faulty devices.
Config Load No
Access Lock View Only
Residence NOLOAD
Related DNETFLTSTS
Parameters
Configured on No
DeviceNet
Remarks This parameter cycles around displaying the Device Address of all devices that the
Interface Module is having issues with, displaying each in turn

- 85 -
 Chapter 6 - DeviceNet Interface Parameter Reference

6.22 DNETFLTSTS

Specific to Block DNET_IM

(s)
Description Error Code of a Device that the Interface Module is having issues with.
Data Type INT16
Range N/A
Default 0
Config Load No
Access Lock View Only
Residence NOLOAD
Related DNETFLTADDR
Parameters
Configured on No
DeviceNet
Remarks This parameter cycles around all devices that the Interface Module is having
issues with, displaying each in turn.

6.23 DNETIMADDR

Specific to Block(s) DNET_IM

Description DeviceNet Interface Module Address
Data Type UINT16
Range N/A
Default 0
Config Load No
Access Lock View Only
Residence NOLOAD
Related Parameters
Configured on DeviceNet No
Remarks DeviceNet address of the interface module.

6.24 DNETIMADDRESS

Specific to Block(s) DNET_IM

Description DeviceNet Address of the DNet Interface.
Data Type INT16
Range 0 - 63
Default 0
Config Load Yes
Access Lock Application Developer
Residence CEE
Related Parameters DNETIMTYPE
Configured on Yes
DeviceNet
Remarks Rockwell recommends that the Interface Module is located at Device
Address 0.

- 86 -
 Chapter 6 - DeviceNet Interface Parameter Reference

6.25 DNETIMCMD

Specific to DNET_IM
Block(s)
Description DeviceNet Interface Module Command - Lets you control the operation of the
DeviceNet Interface Module by writing to the module Command Register.
Data Type Enumeration
Range 0 Idle Transition the Interface Module to Idle. Used to put the DNet
Interface module into Idle mode. When in Idle mode, the DNB
will not receive inputs from devices on the network, and will
not send active Output data to the devices.
Idle is displayed on the DNB status display.
1 Run Transition the Interface Module to Run. Used to put the DNet
Interface module into Run mode. When in Run mode, active
Outputs are sent on the network by the DNB and Inputs are
also received.
Run is displayed on the DNB status display.
2 Fault Transition the network to Faulted. Used to put the DNet
Interface module into Fault mode. When in Fault mode the
DNB will not make an attempt to communicate on the
network and will have the message Network Faulted on the
front of the DNB. This mode is useful when the user program
detects a major system error and wants to disable
communication of the DNB on the DeviceNet network along
with showing a fault indication on the front of the DNB visible
to operation personnel.
3 DisableNetwork Transition the network to Disabled. Used to put the DNet
Interface module into Communication Disable mode. When in
Disable mode the DNB will not make an attempt to
communicate on the network and will have the message
Network Disabled on the front of the DNB. This mode is useful
when the user program wants to disable all communication of
the DNB on the DeviceNet network along with showing a
disabled indication on the front of the DNB visible to
operation personnel.
4 HaltScanner Halt the Interface Module.
Used to put the DNet Interface module into Halt mode. When
in Halt mode, the DNB is not communicating on the
DeviceNet network and will have the message HALT on the
front of the DNB. This is the most severe mode to put the DNB
into because the only way to recover is to cycle power to DNB
in the chassis. This mode is used when operator intervention
is desired to clear an error detected by the user program. A
power cycle to the chassis or DNet Interface is necessary to
take the DNB out of Halt mode.
NOTE: So far it does not appear that this option works this
way. It cannot be cleared with a power cycle, but needs the
database to be cleared and a new download performed.
5 Reset Reset the Interface Module.
Used to cause the DNet Interface module to go through a
power up reset. Used when it is required that the DNet
Interface needs to be reset under user control. Note: This
reset is not operational when the DNB has been put into Halt
mode via the Command Register. A 1 in this bit puts DNB into
Reset mode. A 0 should be put into the bit before the reset

- 87 -
 Chapter 6 - DeviceNet Interface Parameter Reference

finishes, or another reset cycle will commence.

Default 0
Config No
Load
Access Operator
Lock
Residence NO LOAD
Related
Parameters
Configured No
on
DeviceNet
Remarks

6.26 DNETIMSTS

Specific to Block(s) DNET_IM

Description DeviceNet Interface Module Status
Data Type STRING
Range 10 character
Default 0
Config Load No
Access Lock View Only
Residence NOLOAD
Configured on DeviceNet
Related Parameters
Remarks

6.27 DNETIMSTSAUTOV

Specific to DNET_IM
Block(s)
Description DeviceNet Interface Module Status Auto Value - Indicates if the data Transmit and
Receive sizes in the DNB scan list are correct between the DNB and its devices.
Data Type BOOLEAN
Range 0 - Condition not applicable
1 - Condition applicable
Default 0 - Condition not applicable
Config No
Load
Access Lock View Only
Residence NOLOAD
Related
Parameters
Configured No
on
DeviceNet
Remarks Any node whose data sizes do not match the sizes defined in the scan list of the DNet
Interface scan list would cause the parameter to be checked. This parameter is used
in conjunction with Device Status table on the Device Configuration/Status tab to

- 88 -
 Chapter 6 - DeviceNet Interface Parameter Reference

determine which device(s) have incorrect data sizes.

This is one in a set of parameters that show the status of the DNet Interface, as
defined in the Status Register. The Status Register is contained in the first double
word of the Input Assembly. The group is a set of individual check boxes that show if
a certain condition exists.

6.28 DNETIMSTSCFAIL

Specific to DNET_IM
Block(s)
Description DeviceNet Interface Module Status Communication Failure - Indicates that some sort
of channel wide communication fault is happening with the DNet Interface
DeviceNet channel. For example if the DNet Interface detects severe communication
problems on the network it will go into a Bus Off condition and this parameter will be
checked.
Data Type BOOLEAN
Range 0 - Condition not applicable
1 - Condition applicable
Default 0 - Condition not applicable
Config No
Load
Access Lock View Only
Residence NOLOAD
Related
Parameters
Configured No
on
DeviceNet
Remarks This is one in a set of parameters that show the status of the DNet Interface, as
defined in the Status Register. The Status Register is contained in the first double
word of the Input Assembly. The group is a set of individual check boxes that show if a
certain condition exists.

6.29 DNETIMSTSDFAIL

Specific to DNET_IM
Block(s)
Description DeviceNet Interface Module Status Device Failure - Indicates if general
communication is OK between the DNB and its devices.
Data Type BOOLEAN
Range 0 - Condition not applicable
1 - Condition applicable
Default 0 - Condition not applicable
Config No
Load
Access Lock View Only
Residence NOLOAD
Related
Parameters
Configured No
on
DeviceNet

- 89 -
 Chapter 6 - DeviceNet Interface Parameter Reference

Remarks A node falling off the network or other communication problems to any device on the
DNet Interface scan list causes the parameter to be checked. This parameter is used
in conjunction with the Device Status table on the Device Configuration/Status tab to
determine which device(s) are having communication problems.
This is one in a set of parameters that show the status of the DNet Interface, as
defined in the Status Register. The Status Register is contained in the first double
word of the Input Assembly. The group is a set of individual check boxes that show if a
certain condition exists.

6.30 DNETIMSTSDISBL

Specific to DNET_IM
Block(s)
Description DeviceNet Interface Module Status Disabled - Indicates that the DNet Interface is in
Disable mode.
Data Type BOOLEAN
Range 0 - Condition not applicable
1 - Condition applicable
Default 0 - Condition not applicable
Config Load No
Access Lock View Only
Residence NOLOAD
Related
Parameters
Configured No
on
DeviceNet
Remarks This is one in a set of parameters that show the status of the DNet Interface, as
defined in the Status Register. The Status Register is contained in the first double
word of the Input Assembly. The group is a set of individual check boxes that show if
a certain condition exists.

6.31 DNETIMSTSDUP

Specific to DNET_IM
Block(s)
Description DeviceNet Interface Module Status Duplicate - Indicates that the DNet Interface is
attempting to go online on a DeviceNet network with the same node number as an
existing device on the network.
Data Type BOOLEAN
Range 0 - Condition not applicable
1 - Condition applicable
Default 0 - Condition not applicable
Config Load No
Access Lock View Only
Residence NOLOAD
Related
Parameters
Configured No
on
DeviceNet

- 90 -
 Chapter 6 - DeviceNet Interface Parameter Reference

Remarks This is one in a set of parameters that show the status of the DNet Interface, as
defined in the Status Register. The Status Register is contained in the first double
word of the Input Assembly. The group is a set of individual check boxes that show if
a certain condition exists.

6.32 DNETIMSTSFAULT

Specific to DNET_IM
Block(s)
Description DeviceNet Interface Module Status Fault - Indicates that the DNet Interface Module
is in Fault mode.
Data Type BOOLEAN
Range 0 - Condition not applicable
1 - Condition applicable
Default 0 - Condition not applicable
Config No
Load
Access Lock View Only
Residence NOLOAD
Related
Parameters
Configured No
on
DeviceNet
Remarks This is one in a set of parameters that show the status of the DNet Interface, as
defined in the Status Register. The Status Register is contained in the first double
word of the Input Assembly. The group is a set of individual check boxes that show if a
certain condition exists.

6.33 DNETIMSTSIDLE

Specific to DNET_IM
Block(s)
Description DeviceNet Interface Module Status Idle - Indicates that the DNet Interface Module is
in Idle mode.
Data Type BOOLEAN
Range 0 - Condition not applicable
1 - Condition applicable
Default 0 - Condition not applicable
Config No
Load
Access Lock View Only
Residence NOLOAD
Related
Parameters
Configured No
on
DeviceNet
Remarks This is one in a set of parameters that show the status of the DNet Interface, as
defined in the Status Register. The Status Register is contained in the first double
word of the Input Assembly. The group is a set of individual check boxes that show if a
certain condition exists.

- 91 -
 Chapter 6 - DeviceNet Interface Parameter Reference

6.34 DNETIMSTSPOWER

Specific to DNET_IM
Block(s)
Description DeviceNet Interface Module Status Power - Indicates that the DNet Interface Module
cannot detect a 24VDC power supply connected to the network.
Data Type BOOLEAN
Range 0 - Condition not applicable
1 - Condition applicable
Default 0 - Condition not applicable
Config Load No
Access Lock View Only
Residence NOLOAD
Related
Parameters
Configured No
on
DeviceNet
Remarks This is one in a set of parameters that show the status of the DNet Interface, as
defined in the Status Register. The Status Register is contained in the first double
word of the Input Assembly. The group is a set of individual check boxes that show if
a certain condition exists.

6.35 DNETIMSTSRUN

Specific to DNET_IM
Block(s)
Description DeviceNet Interface Module Status Run - Indicates that the DNet Interface Module is
in Run mode.
Data Type BOOLEAN
Range 0 - Condition not applicable
1 - Condition applicable
Default 0 - Condition not applicable
Config Load No
Access Lock View Only
Residence NOLOAD
Related
Parameters
Configured No
on
DeviceNet
Remarks This is one in a set of parameters that show the status of the DNet Interface, as
defined in the Status Register. The Status Register is contained in the first double
word of the Input Assembly. The group is a set of individual check boxes that show if
a certain condition exists.

6.36 DNETIMTYPE

Specific to Block(s) DNET_IM

Description The type of Interface Module being used to interface with DeviceNet.

- 92 -
 Chapter 6 - DeviceNet Interface Parameter Reference

Data Type ENUM

Range 1756-DNB
Default 1756-DNB
Config Load Yes
Access Lock Application Developer
Residence CEE
Related Parameters DNETIMADDRESS
DNETIMSTS
Configured on DeviceNet No
Remarks

6.37 DNETSCANCNT

Specific to Block(s) DNET_IM

Description DeviceNet Scan Count
Data Type INT32
Range N/A
Default 0
Config Load No
Access Lock View Only
Residence NOLOAD
Related Parameters
Configured on DeviceNet No
Remarks Incremented each time a DeviceNet scan is completed.

6.38 FLBITOFFSET[0..31]

Specific to DNET_INCHAN and DNET_OUTCHAN

Block(s)
Description Bit number that represents the process flag ( PVFL[x] or OPFL[x] ) within the
specified byte of interest.
Data Type INT32
Range 0 to 7
Default 0
Config Load Yes
Access Lock Application Developer
Residence CEE
Configured FLENABLE[0..31]
on
DeviceNet PVFL[0..31]
OPFL[0..31]
Related No
Parameters
Remarks Bit numbers are 'right justified', meaning that the lowest bit number is at the right
side of the byte. For example the following binary sequence has only bit 0 asserted:
00000001

- 93 -
 Chapter 6 - DeviceNet Interface Parameter Reference

6.39 FLBYTEOFFSET[0..31]

Specific to DNET_INCHAN and DNET_OUTCHAN

Block(s)
Description Data offset in bytes from the start of the channel's input data to the location of the
byte containing the bit that represents the process flag ( PVFL[x] or OPFL[x] )
Data Type INT32
Range 0 to (DATASIZE - 1), 496 is maximum for DNET_INCHAN and 492 is maximum for
DNET_OUTCHAN
Default 0
Config Yes
Load
Access Lock Application Developer
Residence CEE
Related FLENABLE[0..31]
Parameters
PVFL[0..31]
OPFL[0..31]
Configured No
on
DeviceNet
Remarks Invalid entries (which reference data outside the boundaries of the channel block
data message) are detected during load and indicated as a 'configuration mismatch
warning', causing FLENABLE[x] to be disabled, ensuring no processing of PVFL[x] on
a DNET_INCHAN block or OPFL[x] on a DNET_OUTCHAN block.

6.40 FLDESC[0..31]

Specific to DNET_INCHAN and DNET_OUTCHAN

Block(s)
Description Descriptor of the process flag ( PVFL[x] or OPFL[x] ).
Data Type 24 Character Text String
Range N/A
Default
Config Load Yes
Access Lock Application Developer
Residence SR
Related PVFL[0..31]
Parameters
OPFL[0..31]
Configured No
on
DeviceNet
Remarks Because the process flag ( PVFL[x] or OPFL[x] ) parameter cannot be renamed, this
text descriptor is useful in documenting the use of each enabled process flag (PVFL
[x] or OPFL[x])parameter.

6.41 FLENABLE[0..31]

Specific to DNET_INCHAN and DNET_OUTCHAN

Block(s)

- 94 -
 Chapter 6 - DeviceNet Interface Parameter Reference

Description Enable processing of the respective process flag ( PVFL[x] or OPFL[x] ) parameter.
Data Type BOOLEAN
Range Off(0) - Disable parameter
On(1) - Enable parameter
Default Off(0)
Config Load Yes
Access Lock Application Developer
Residence CEE
Related FLBYTEOFFSET[0..31]
Parameters
FLBITOFFSET[0..31]
PVFL[0..31]
OPFL[0..31]
Configured No
on
DeviceNet
Remarks Invalid configuration entries for FLBYTEOFFSET will cause the respective enable
processing parameter (PVENABLE[x], OPENABLE[x]) to be internally disabled during
block load.

6.42 INCONNSIZE

Specific to DNET_IM
Block(s)
Description Input Connection Size in bytes.
Data Type INT32
Range 1 - 496
Default 496
Config Load Yes
Access Lock Application Developer
Residence CEE
Related OUTCONNSIZE
Parameters
Configured Yes
on
DeviceNet
Remarks If less than the maximum amount of input data is being utilized based on the
DeviceNet configuration, reducing this parameter from the default value will
decrease the communications loading on the I/O sub network.
Requires a minimum value of one (1), since a value of zero is not allowed for Control
Builder Configuration.

6.43 INOFFSETBIT[0..9]

Specific to DNET_DEVICE
Block(s)
Description Input Data Offset (in words).
Data Type INT16
Range The value may only be 0, 8, 16 or 24.

- 95 -
 Chapter 6 - DeviceNet Interface Parameter Reference

Default NOTUSED
Config Load Yes
Access Lock View Only
Residence NOLOAD
Related INOFFSETWORD[0..9]
Parameters
INSIZE[0..9]
Configured Yes
on DeviceNet
Remarks The starting position in bits, which together with the INOFFSETWORD parameter,
defines the start position in the Input Assembly of the data for the device.

6.44 INOFFSETWORD[0..9]

Specific to DNET_DEVICE
Block(s)
Description Input Data Offset (in words).
Data Type INT16
Range
Default NOTUSED
Config Load Yes
Access Lock View Only
Residence NOLOAD
Related INOFFSETBIT[0..9]
Parameters
INSIZE[0..9]
Configured Yes
on DeviceNet
Remarks The starting position in words, which together with the INOFFSETBIT parameter,
defines the start position in the Input Assembly of the data for the device.

6.45 INSIZE[0..9]

Specific to Block(s) DNET_DEVICE

Description Input Data Size (in bits).
Data Type INT16
Range The value must be a multiple of 8.
Default NOTUSED
Config Load Yes
Access Lock ViewOnly
Residence NOLOAD
Related Parameters
Configured on DeviceNet Yes
Remarks The Size of the input data.

6.46 IOCONNSTATUS

Specific to All I/O Module Function Blocks

Block(s)
Description I/O Connection Status - Displays the status of the connection between the

- 96 -
 Chapter 6 - DeviceNet Interface Parameter Reference

C200/C300 Controller and the I/O Module. If the connection could not be
established, this will display the reason for the connection failure.
Data Type Enumeration
Range (0) Bad Schedule (6) No Configuration
(1) Communications Error (7) No Keeper
(2) Configuration Error (8) No Schedule
(3) Connected (9) Not Connected
(4) Connection in Use (10) Wrong Module
(5) I/O Module Not Found
Default (9) Not Connected
Config Load No
Access Lock View Only
Residence CEE
Related
Parameters
Configured No
on
DeviceNet
Remarks

6.47 OP[0..7]

Specific to Block(s) DNET_OUTCHAN

Description Output Value[x]
This parameter represents the floating-point output value.
Data Type FLOAT64
Range
Default 0.0
Config Load No
Access Lock Engineer
Residence CEE
Related Parameters OPENABLE[0..7]
OPDESC[0..7]
OPOFFSET[0..7]
OPRAWSIZE[0..7]
OPLORAW[0..7]
OPHIRAW[0..7]
OPLOACT[0..7]
OPHIACT[0..7]
OPRAW[0..7]
BADOPSTS[0..7]
Configured on No
DeviceNet
Remarks l OP[x] is processed only if OPENABLE[x] is asserted.
l The OP connection does not support back initialization, or automatic
passage of status.

- 97 -
 Chapter 6 - DeviceNet Interface Parameter Reference

6.48 OPDESC[0..7]

Specific to Block DNET_OUTCHAN

(s)
Description Descriptor of OP[x].
Data Type 24 Character Text String
Range N/A
Default
Config Load Yes
Access Lock Application Developer
Residence SR
Related IOCONNSTATUS
Parameters
Configured on No
DeviceNet
Remarks Because the OP[x] parameter cannot be renamed, this text descriptor is useful
in documenting the use of each enabled OP[x].

6.49 OPENABLE[0..7]

Specific to DNET_OUTCHAN
Block(s)
Description Enable processing of the respective OP[x] parameter
Data Type BOOLEAN
Range Off(0) - Disable parameter
On(1) - Enable parameter
Default Off(0)
Config Load Yes
Access Lock Application Developer
Residence CEE
Related OPOFFSET[0..7]
Parameters
OPRAWSIZE[0..7]
IOCONNSTATUS
Configured on No
DeviceNet
Remarks Invalid configuration entries for OPOFFSET[x] or OPRAWSIZE[x] will cause
OPENABLE[x] to be automatically disabled during block load.

6.50 OPFL[0..31]

Specific to Block DNET_OUTCHAN

(s)
Description Process Output Flag[x]
This parameter represents the Boolean (flag) Output Value, which is inserted
into the specified bit of the specified byte of interest.
Data Type BOOLEAN
Range Off(0)
On(1)

- 98 -
 Chapter 6 - DeviceNet Interface Parameter Reference

Default Off
Config Load No
Access Lock Engineer
Residence CEE
Related FLENABLE[0..31]
Parameters
FLDESC[0..31]
FLBYTEOFFSET[0..31]
FLBITOFFSET[0..31]
BADOPFLSTS[0..31]
Configured on No
DeviceNet
Remarks OPFL[x] is processed only if FLENABLE[x] is asserted.

6.51 OPHIACT[0..7]

Specific to DNET_OUTCHAN
Block(s)
Description High Actual Value
This parameter represents the numeric equivalent of OPHIRAW[x].
Data Type FLOAT64
Range
Default 100.0
Config Load Yes
Access Lock Application Developer
Residence CEE
Related OPHIRAW[0..7]
Parameters
OPLOACT[0..7]
IOCONNSTATUS
Configured No
on
DeviceNet
Remarks Although this parameter is usually greater than OPLOACT[x] (representing the
highest numerical input value), if the inputs are scaled in a reverse fashion, this
parameter can also be less than OPLOACT[x] (thus representing the lowest
numerical input value).

6.52 OPHIRAW[0..7]

Specific to Block(s) DNET_OUTCHAN

Description Upper range limit of the integer output value.
Data Type INT32
Range See OPRAWSIZE[..], upon which this parameter is dependent.
Default 32,767
Config Load Yes
Access Lock Application Developer
Residence CEE
Related Parameters OPRAWSIZE[0..7]

- 99 -
 Chapter 6 - DeviceNet Interface Parameter Reference

OPHIACT[0..7]
IOCONNSTATUS
Configured on No
DeviceNet
Remarks l Output values greater than OPHIRAW[x] are invalid.
l OPHIACT[x] is configured with the actual numeric value that is
equivalent to OPHIRAW[x].

6.53 OPLOACT[0..7]

Specific to DNET_OUTCHAN
Block(s)
Description Low Actual Value
This parameter represents the numeric equivalent of OPLORAW[x].
Data Type FLOAT64
Range
Default 0.0
Config Load Yes
Access Lock Application Developer
Residence CEE
Related OPLORAW[0..7]
Parameters
OPHIACT[0..7]
IOCONNSTATUS
Configured No
on
DeviceNet
Remarks Although this parameter is usually less than OPHIACT[x] (representing the lowest
numerical input value), if the inputs are scaled in a reverse fashion, this parameter
can also be greater than OPHIACT[x] (thus representing the highest numerical input
value).

6.54 OPLORAW[0..7]

Specific to Block(s) DNET_OUTCHAN

Description Lower range limit of the integer output value.
Data Type INT32
Range See OPRAWSIZE[..], upon which this parameter is dependent.
Default -32,768
Config Load Yes
Access Lock Application Developer
Residence CEE
Related Parameters OPRAWSIZE[0..7]
OPLOACT[0..7]
IOCONNSTATUS
Configured on No
DeviceNet
Remarks l Input values less than OPLORAW[x] are invalid.

- 100 -
 Chapter 6 - DeviceNet Interface Parameter Reference

l OPLOACT[x] is configured with the actual numeric value that is

equivalent to OPLORAW[x].

6.55 OPOFFSET[0..7]

Specific to DNET_OUTCHAN
Block(s)
Description Data offset in bytes from the start of the channel's input data to the starting location
of the raw data representation of OP[x].
Data Type INT32
Range 0 to (DATASIZE - 1), 492 maximum
Default 0
Config Yes
Load
Access Lock Application Developer
Residence CEE
Related OPRAWSIZE[0..7]
Parameters
OPENABLE[0..7]

IOCONNSTATUS
Configured No
on
DeviceNet
Remarks l OPOFFSET + (Size of OPRAWSIZE in bytes) must less than or equal to the
OUTCONNSIZE of the associated device/module block.
l Invalid combinations of OPOFFSET[x] and OPRAWSIZE[x] (which reference data
outside the boundaries of the channel block data message) are detected during
load and indicated as a 'configuration mismatch warning', causing PVENABLE[x]
to be disabled, ensuring no processing of OP[x].

6.56 OPRAW[0..7]

Specific to DNET_OUTCHAN
Block(s)
Description Output Value, as a scaled integer representation of OP[x]
This value is the raw field value that is transported via DeviceNet. It is scaled by the
block from OP[x].
Data Type INT32
Range Varies based on OPRAWSIZE[..]
Default 0
Config Load No
Access Lock Engineer
Residence CEE
Related IOCONNSTATUS
Parameters
Configured on No
DeviceNet
Remarks This parameter is primarily useful as a debugging parameter, but can be used
directly as a control output, providing an output as an integer data type.

- 101 -
 Chapter 6 - DeviceNet Interface Parameter Reference

6.57 OPRAWSIZE[0..7]

Specific to Block(s) DNET_OUTCHAN

Description Output (OP) Raw Size - Represents the raw
integer data size and format
Data Type Enumeration of DNET_Datasize
Range The additional columns below indicate the
physical size of each integer format and
the associated minimum and maximum
values for use in configuring the raw
integer scaling parameters.
# Enum text Size in Min. Raw Max. Raw
bytes Value Value
0 BYTE_SIGNED 1 -128 127
1 BYTE_UNSIGND 1 0 255
2 WORD_SIGNED 2 -32,767 32,768
3 WORD_UNSIGND 2 0 65,535
4 DWORD_SIGNED 4 - 2,147,483,647
2,147,483,648
5 IEEE32_Real 4 +/- 1.4 * E -45 +/- 3.4 * E38
Default 0
Config Load Yes
Access Lock Application Developer
Residence CEE
Related Parameters OPOFFSET[0..7]
OPLORAW[0..7]
OPHIRAW[0..7]
IOCONNSTATUS
Configured No
on
DeviceNet
Remarks OPOFFSET + (Size of OPRAWSIZE in
bytes) must be less than or equal to the
OUTONNSIZE of the associated
device/module block.
Invalid combinations of OPOFFSET[x] and
OPRAWSIZE[x] (which reference data
outside the boundaries of the channel
block data message) are detected during
load and indicated as a 'configuration
mismatch warning', causing OPENABLE
[x] to be disabled, ensuring no processing
of OP[x].

6.58 OUTCONNSIZE

Specific to DNET_IM
Block(s)
Description Output Connection Size in bytes.
Data Type INT32

- 102 -
 Chapter 6 - DeviceNet Interface Parameter Reference

Range 0 - 492
Default 492
Config Load Yes
Access Lock Application Developer
Residence CEE
Related INCONNSIZE
Parameters
Configured Yes
on
DeviceNet
Remarks If less than the maximum amount of output data is being utilized based on the
DeviceNet configuration, reducing this parameter from the default value will
decrease the communications loading on the I/O sub network.

6.59 OUTOFFSETBIT[0..9]

Specific to DNET_DEVICE
Block(s)
Description Output Data Offset (in bits).
Data Type INT16
Range The value may only be 0, 8, 16 or 24.
Default NOTUSED
Config Load Yes
Access Lock ViewOnly
Residence NOLOAD
Related OUTOFFSETBIT[0..9]
Parameters
OUTSIZE[0..9]
Configured Yes
on DeviceNet
Remarks The starting position in words, which together with the OUTOFFSETBIT parameter,
defines the start position in the Output Assembly of the data for the device.

6.60 OUTOFFSETWORD[0..9]

Specific to DNET_DEVICE
Block(s)
Description Output Data Offset (in words).
Data Type INT16
Range
Default NOTUSED
Config Load Yes
Access Lock ViewOnly
Residence NOLOAD
Related OUTOFFSETBIT[0..9]
Parameters
OUTSIZE[0..9]
Configured Yes
on DeviceNet
Remarks The starting position in words, which together with the OUTOFFSETBIT parameter,
defines the start position in the Output Assembly of the data for the device.

- 103 -
 Chapter 6 - DeviceNet Interface Parameter Reference

6.61 OUTSIZE[0..9]

Specific to Block(s) DNET_DEVICE

Description Output Data Size (in bits).
Data Type INT16
Range The value must be a multiple of 8.
Default NOTUSED
Config Load Yes
Access Lock View Only
Residence NOLOAD
Related Parameters OUTOFFSETBIT[0..9]
Configured on DeviceNet Yes
Remarks The Size of the output data in bits.

6.62 PV[0..7]

Specific to DNET_INCHAN
Block(s)
Description Process Input[x], Scaled
This parameter represents the floating point Present Value (PV), as a scaled
representation of the raw integer input value.
Data Type FLOAT64
Range
Default 0.0
Config Load No
Access Lock View Only
Residence CEE
Related PVENABLE[0..7]
Parameters
PVDESC[0..7]
PVOFFSET[0..7]
PVRAWSIZE[0..7]
PVLORAW[0..7]
PVHIRAW[0..7]
PVLOACT[0..7]
PVHIACT[0..7]
PVRAW[0..7]
PVSTS[0..7]
Configured No
on
DeviceNet
Remarks PV[x] is processed only if PVENABLE[x] is asserted.
The PV connection is ‘intelligent’ in that it will automatically pass value and status to
any block that accepts status information, such as the P1 connection of a DATAACQ
block or the PV connection of a PID block.

- 104 -
 Chapter 6 - DeviceNet Interface Parameter Reference

6.63 PVDESC[0..7]

Specific to Block DNET_INCHAN

(s)
Description Descriptor of PV[x]
Data Type 24 Character Text String
Range N/A
Default
Config Load Yes
Access Lock Application Developer
Residence SR
Related PV[0..7]
Parameters
Configured on No
DeviceNet
Remarks Because the PV[x] parameter cannot be renamed, this text descriptor is useful in
documenting the use of each enabled PV[x] .

6.64 PVENABLE[0..7]

Specific to DNET_INCHAN
Block(s)
Description Enable processing of the respective PV[x] parameter
Data Type BOOLEAN
Range Off(0) - Disable parameter
On(1) - Enable parameter
Default Off(0)
Config Load Yes
Access Lock Application Developer
Residence CEE
Related PVOFFSET[0..7]
Parameters
PVRAWSIZE[0..7]
PV[0..7]
Configured on No
DeviceNet
Remarks Invalid configuration entries for PVOFFSET[x] or PVRAWSIZE[x] will cause
PVENABLE[x] to be automatically disabled during block load.

6.65 PVFL[0..31]

Specific to DNET_INCHAN
Block(s)
Description Process Input Flag[x]
This parameter represents the Boolean(flag) Present Value, as extracted from the
specified bit of the specified byte of interest.
Data Type BOOLEAN
Range Off(0)
On(1)

- 105 -
 Chapter 6 - DeviceNet Interface Parameter Reference

Default Off
Config Load No
Access Lock View Only
Residence CEE
Related FLENABLE[0..31]
Parameters
FLDESC[0..31]
FLBYTEOFFSET[0..31]
FLBITOFFSET[0..31]
BADPVFLSTS[0..31]
Configured No
on
DeviceNet
Remarks PVFL[x] is processed only if FLENABLE[x] is asserted.
The PV connection is ‘intelligent’ in that it will automatically pass value and status to
any block that accepts status information, such as the P1 connection of a DATAACQ
block or the PV connection of a PID block.

6.66 PVHIACT[0..7]

Specific to DNET_INCHAN
Block(s)
Description High Actual Value
This parameter represents the numeric equivalent of PVHIRAW[x].
Data Type FLOAT64
Range
Default 100.0
Config Load Yes
Access Lock Application Developer
Residence CEE
Related PVHIRAW[0..7]
Parameters
PVLOACT[0..7]
PV[0..7]
Configured No
on
DeviceNet
Remarks Although this parameter is usually greater than PVLOACT[x] (representing the
highest numerical input value), if the inputs are scaled in a reverse fashion, this
parameter can also be less than PVLOACT[x] (thus representing the lowest
numerical input value).

6.67 PVHIRAW[0..7]

Specific to Block(s) DNET_INCHAN

Description Upper range limit of the integer input value.
Data Type INT32
Range See PVRAWSIZE[..], upon which this parameter is dependent.
Default 32,767

- 106 -
 Chapter 6 - DeviceNet Interface Parameter Reference

Config Load Yes

Access Lock Application Developer
Residence CEE
Related Parameters PVRAWSIZE[0..7]
PVHIACT[0..7]
PV[0..7]
Configured on No
DeviceNet
Remarks Output values greater than PVHIRAW[x] are invalid.
PVHIACT[x] is configured with the actual numeric value that is equivalent
to PVHIRAW[x].

6.68 PVLOACT[0..7]

Specific to Block(s) DNET_INCHAN

Description Low Actual Value This parameter represents the numeric equivalent of
PVLORAW[x].
Data Type FLOAT64
Range
Default 0.0
Config Load Yes
Access Lock Application Developer
Residence CEE
Related Parameters PVLORAW[0..7]
PVHIACT[0..7]
PV[0..7]
Configured on No
DeviceNet

6.69 PVLORAW[0..7]

Specific to Block(s) DNET_INCHAN

Description Lower range limit of the integer input value.
Data Type INT32
Range See PVRAWSIZE[..], upon which this parameter is dependent.
Default -32,768
Config Load Yes
Access Lock Application Developer
Residence CEE
Related Parameters PVRAWSIZE[0..7]
PVLOACT[0..7]
PV[0..7]
Configured on No
DeviceNet
Remarks Input values less than PVLORAW[x] are invalid.
PVLOACT[x] is configured with the actual numeric value that is equivalent
to PVLORAW[x].

- 107 -
 Chapter 6 - DeviceNet Interface Parameter Reference

6.70 PVOFFSET[0..7]

Specific to DNET_INCHAN
Block(s)
Description Data offset in bytes from the start of the channel's input data to the starting location
of the raw data representation of PV[x].
Data Type INT32
Range 0 to (DATASIZE - 1), 496 maximum
Default 0
Config Yes
Load
Access Lock Application Developer
Residence CEE
Related PVRAWSIZE[0..7]
Parameters
PVENABLE[0..7]
PV[0..7]
Configured No
on
DeviceNet
Remarks PVOFFSET + (Size of PVRAWSIZE in bytes) must be less than or equal to the
INCONNSIZE of the associated device/module block.
Invalid combinations of PVOFFSET[x] and PVRAWSIZE[x] (which reference data
outside the boundaries of the channel block data message) are detected during load
and indicated as a 'configuration mismatch warning', causing PVENABLE[x] to be
disabled, ensuring no processing of PV[x].

6.71 PVRAW[0..7]

Specific to DNET_INCHAN
Block(s)
Description Process Input[x] raw value
This value is the raw field value that is transported via DeviceNet. It is scaled by the
block to calculate PV[x].
Data Type INT32
Range Varies based on PVRAWSIZE[..]
Default 0
Config Load No
Access Lock View Only
Residence CEE
Related PV[0..7]
Parameters
Configured on No
DeviceNet
Remarks This parameter is primarily useful as a debugging parameter, but can be used
directly as a control input, providing an input as an integer data type.

6.72 PVRAWSIZE[0..7]

Specific to DNET_INCHAN
Block(s)

- 108 -
 Chapter 6 - DeviceNet Interface Parameter Reference

Description Process Variable (PV) Raw Size - Represents raw integer data size and format
Data Type Enumeration of DNET_Datasize
Range The additional columns below indicate the physical size of each integer format and
the associated minimum and maximum values for use in configuring the raw
integer scaling parameters.
# Enum text Size in bytes Min. Raw Value Max. Raw Value
0 BYTE_SIGNED 1 -128 127
1 BYTE_UNSIGND 1 0 255
2 WORD_SIGNED 2 -32,767 32,768
3 WORD_UNSIGND 2 0 65,535
4 DWORD_SIGNED 4 -2,147,483,648 2,147,483,647
5 IEEE32_Real 4 +/- 1.4 * E -45 +/- 3.4 * E38
Default 0
Config Load Yes
Access Lock Application Developer
Residence CEE
Related PVOFFSET[0..7]
Parameters
PVLORAW[0..7]

PV[0..7]
IOCONNSTATUS
Configured No
on
DeviceNet
Remarks PVOFFSET + (Size of PVRAWSIZE in bytes) must be less than or equal to the
INCONNSIZE of the associated device/module block.
Invalid combinations of PVOFFSET[x] and PVRAWSIZE[x] (which reference data
outside the boundaries of the channel block data message) are detected during load
and indicated as a 'configuration mismatch warning', causing PVENABLE[x] to be
disabled, ensuring no processing of PV[x].

6.73 PVSTS[0..7]

Specific to Block DNET_INCHAN

(s)
Description Process Variable (PV) Status - Indicates process Input[x] Status.
Data Type Enumeration of PVSTS
Range 0 Bad
1 Uncertain (not used by this block)
2 Normal
3 Manual (not used by this block)
4 InitAck (not used by this block)
Default Bad
Config Load No
Access Lock View Only
Residence CEE
Related PVENABLE[0..7]
Parameters
PV[0..7]
Configured on No
DeviceNet

- 109 -
 Chapter 6 - DeviceNet Interface Parameter Reference

Remarks PVSTS[x] assumes the BAD state if either 1) BADINPUTSTS is asserted or 2)

PVENABLE[x] is configured to the Off state.

6.74 SRCBLOCK

Specific to Block(s) DNET_Device

Description DeviceNet Interface Module Name.
Data Type BLOCKID
Range N/A
Default 0
Config Load Yes
Access Lock Application Developer
Residence CEE
Related
Parameters
Configured on No
DeviceNet
Remarks Each DeviceNet Device block must be configured to identify the DNET_IM
block that will serve its I/O data.

- 110 -
Notices
Trademarks
Experion®, PlantScape®, SafeBrowse®, TotalPlant®, and TDC 3000® are registered trademarks of
Honeywell International, Inc.
OneWireless™ is a trademark of Honeywell International, Inc.

Other trademarks
Microsoft and SQL Server are either registered trademarks or trademarks of Microsoft Corporation
in the United States and/or other countries.
Trademarks that appear in this document are used only to the benefit of the trademark owner,
with no intention of trademark infringement.

Third-party licenses
This product may contain or be derived from materials, including software, of third parties. The
third party materials may be subject to licenses, notices, restrictions and obligations imposed by
the licensor. The licenses, notices, restrictions and obligations, if any, may be found in the
materials accompanying the product, in the documents or files accompanying such third party
materials, in a file named third_party_licenses on the media containing the product, or at
http://www.honeywell.com/ps/thirdpartylicenses.

Documentation feedback
You can find the most up-to-date documents on the Honeywell Process Solutions support website
at:
l http://www.honeywellprocess.com/support

If you have comments about Honeywell Process Solutions documentation, send your feedback to:
l [email protected]

Use this email address to provide feedback, or to report errors and omissions in the
documentation. For immediate help with a technical problem, contact your local Honeywell
Process Solutions Customer Contact Center (CCC) or Honeywell Technical Assistance Center
(TAC).

How to report a security vulnerability

For the purpose of submission, a security vulnerability is defined as a software defect or weakness
that can be exploited to reduce the operational or security capabilities of the software.
Honeywell investigates all reports of security vulnerabilities affecting Honeywell products and
services.
To report a potential security vulnerability against any Honeywell product, please follow the
instructions at:
https://honeywell.com/pages/vulnerabilityreporting.aspx
Submit the requested information to Honeywell using one of the following methods:
l Send an email to [email protected].
or
l Contact your local Honeywell Process Solutions Customer Contact Center (CCC) or Honeywell
Technical Assistance Center (TAC) listed in the “Support” section of this document.

- 111 -
Support
For support, contact your local Honeywell Process Solutions Customer Contact Center (CCC). To
find your local CCC visit the website, https://www.honeywellprocess.com/en-US/contact-
us/customer-support-contacts/Pages/default.aspx.

Training classes
Honeywell holds technical training classes about Experion PKS. These classes are taught by
experts in the field of process control systems. For more information about these classes, contact
your Honeywell representative, or see http://www.automationcollege.com.

- 112 -