Solid state equipment has operational characteristics differing from those of electromechanical equipment. Safety Guidelines
for the Application, Installation and Maintenance of Solid State Controls (publication SGI-1.1
Automation sales office or online at http://www.rockwellautomation.com/literature/
between solid state equipment and hard-wired electromechanical devices. Because of this difference, and also because of the
wide variety of uses for solid state equipment, all persons responsible for applying this equipment must satisfy themselves that
each intended application of this equipment is acceptable.
In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from the use
or application of this equipment.
The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables and
requirements associated with any particular installation, Rockwell Automation, Inc. cannot assume responsibility or liability for
actual use based on the examples and diagrams.
No patent liability is assumed by Rockwell Automation, Inc. with respect to use of information, circuits, equipment, or software
described in this manual.
Reproduction of the contents of this manual, in whole or in part, without written permission of Rockwell Automation, Inc., is
prohibited.
Throughout this manual, when necessary, we use notes to make you aware of safety considerations.
available from your local Rockwell
) describes some important differences
Identifies information about practices or circumstances that can cause an explosion in a hazardous environment,
which may lead to personal injury or death, property damage, or economic loss.
Identifies information that is critical for successful application and understanding of the product.
Identifies information about practices or circumstances that can lead to personal injury or death, property damage,
or economic loss. Attentions help you identify a hazard, avoid a hazard, and recognize the consequence.
Labels may be on or inside the equipment, for example, a drive or motor, to alert people that dangerous voltage may
be present.
Labels may be on or inside the equipment, for example, a drive or motor, to alert people that surfaces may reach
dangerous temperatures.
Allen-Bradley, Rockwell Automation, Rockwell Software, RSLogix 5000, Logix5000, RSNetWorx, RSLinx, PowerFlex, DeviceNet, EtherNet/IP, Data Highway Plus-Remote I/O, and TechConnect are trademarks of
Rockwell Automation, Inc.
Trademarks not belonging to Rockwell Automation are property of their respective companies.
Summary of Changes
Introduction
New and Updated
Information
Changes throughout this manual revision are marked by change bars, as shown to
the right of this paragraph.
The table explains the new and updated information in this manual.
SectionChanges
Chapter 3
Chapter 4
Appendix A
Appendix D
Appendix F
and Chapter 6Caution for disabling all alarms because it affects the
Using electronic keying with examples of Exact Match,
Compatible, and Disabled Keying.
underrange/overrange detection feature.
Updated I/O specifications.
Updated power-sizing chart and link to an interactive
spreadsheet to calculate total power consumption for
modules in a chassis configuration.
Updated information on interface modules (IFMs)
and pre-wired cables that are available with
analog I/O modules.
This manual describes how to install, configure, and troubleshoot your
ControlLogix analog I/O module.
You must be able to program and operate a Rockwell Automation
ControlLogix controller to efficiently use your analog I/O modules. If you
need additional information, refer to the related documentation listed below.
The following table lists related ControlLogix products and documentation.
Logix5000 Controllers Common Procedures
Programming Manual, publication
Logix5000 Controllers General Instructions
Reference Manual, publication
1756-UM514
1756-SG001
1756-UM001
DNET-UM004
ENET-UM001
1756-PM001
1756-RM003
If you need more information on these products, contact your local Rockwell
Automation distributor or sales office. The documentation listed in the Related
Documentation table is available at
http://www..rockwellautomation.com/literature
.
Publication 1756-UM009C-EN-P - December 201013
Preface
Notes:
14Publication 1756-UM009C-EN-P - December 2010
Chapter
1
What Are ControlLogix Analog I/O Modules?
Introduction
This chapter provides an overview of the ControlLogix analog I/O modules
to explain to you how they operate.
TopicPage
I/O Module in the ControlLogix System17
Parts Illustration of the ControlLogix Analog I/O Module18
Module Identification and Status Information19
Preventing Electrostatic Discharge20
ControlLogix analog I/O modules are interface modules that convert analog
signals to digital values for inputs and convert digital values to analog signals
for outputs. Controllers can then use these signals for control purposes.
By using the producer/consumer network model, ControlLogix analog I/O
modules produce information when needed while providing additional system
functions.
The table lists several features available on ControlLogix analog I/O modules.
ControlLogix Analog I/O Module Features
FeatureDescription
Removal and insertion
under power (RIUP)
Producer/consumer
communication
Rolling timestamp of dataA 15-bit module-specific rolling timestamp with millisecond
Multiple data formatsAnalog I/O modules offer the option of IEEE 32-bit floating
Module resolutionAnalog input modules use 16-bit resolution, and analog
On-board featuresScaling to engineering units, alarming, and under/overrange
Publication 1756-UM009C-EN-P - December 201015
You can remove and insert modules and removable terminal
blocks (RTB) while power is applied.
This communication is an intelligent data exchange
between modules and other system devices in which each
module produces data without first being polled.
resolution that indicates when data was sampled and/or
applied. This timestamp may be used to calculate the
interval between channel or field-side updates.
point or 16-bit integer data formats.
output modules offer 13…16-bit output resolution
(depending on the module type), to detect data changes.
detection, are some examples of the I/O module features.
Chapter 1 What Are ControlLogix Analog I/O Modules?
ControlLogix Analog I/O Module Features
FeatureDescription
CalibrationControlLogix analog I/O module ships from the factory with
Coordinated system time
(CST) time stamp of data
Agency Certification
factory calibration. You can recalibrate the module
calibration on a channel-by-channel or module-wide basis to
increase accuracy in customer-specific applications,
if necessary.
A 64-bit system clock places a time stamp on the transfer of
data between the module and its owner-controller within
the local chassis.
Full agency certification for in any application that requires
approval.
Agency certification varies depending on the catalog
number. To see a list of the certifications associated with
each catalog number, see
Appendix A
.
16Publication 1756-UM009C-EN-P - December 2010
What Are ControlLogix Analog I/O Modules? Chapter 1
IMPORTANT
I/O Module in the
ControlLogix System
Types of ControlLogix Analog I/O Modules
Cat. No.DescriptionRTB UsedPage
1756-IF1616-point non-isolated analog current/voltage input module
1756-IF88-point non-isolated analog current/voltage input module289
ControlLogix modules mount in a ControlLogix chassis and use a removable
terminal block (RTB) or a Bulletin 1492 interface module
(1)
cable to connect
to all field-side wiring.
Before you install and use your module, you should do the following:
• Install and ground a 1756 chassis and power supply
(2)
. To install these
products, refer to the publications listed in Additional Resources
on page 13.
• Order and receive an RTB or IFM and its components for your
application.
RTBs and IFMs are not included with your
module purchase.
36-pin
294
1756-IF6CIS6-point sourcing current loop input module
20-pin
1756-OF44-point non-isolated analog current/voltage output module312
1756-OF88-point non-isolated analog current/voltage output module323
1756-OF6CI6-point isolated analog current output module316
1756-OF6VI6-point isolated analog voltage output module320
(1)
The ControlLogix system has been agency certified using only the ControlLogix RTBs (1756-TBCH, 1756-TBNH,
1756-TBSH and 1756-TBS6H). Any application that requires agency certification of the ControlLogix system
using other wiring termination methods may require application specific approval by the certifying agency. To
see what analog interface modules are used with each ControlLogix analog I/O module, see Appendix F
(2)
In addition to standard ControlLogix power supplies, ControlLogix Redundant Power Supplies are also available
for your application. For more information on these supplies, see the ControlLogix Selection Guide,
publication 1756-SG001
, or contact your local Rockwell Automation distributor or sales representative.
.
Publication 1756-UM009C-EN-P - December 201017
Chapter 1 What Are ControlLogix Analog I/O Modules?
Removable Terminal Block
1
2
3
4
5
6
40200-M
Parts Illustration of the ControlLogix Analog I/O Module
ItemDescription
1Backplane connector - Interface for the
ControlLogix system that connects the
module to the backplane.
2Top and bottom guides - Guides provide
assistance in seating the RTB or IFM cable
onto the module.
3Status indicators - Indicators display the
status of communication, module health,
and input/output devices. Indicators help in
troubleshooting anomalies.
4Connectors pins - Input/output, power,
and grounding connections are made to the
module through these pins with the use of
an RTB or IFM.
5Locking tab - The locking tab anchors the
RTB or IFM cable on the module,
maintaining wiring connections.
6Slots for keying - Mechanically keys the
RTB to prevent inadvertently making the
wrong wire connections to your module.
18Publication 1756-UM009C-EN-P - December 2010
What Are ControlLogix Analog I/O Modules? Chapter 1
IMPORTANT
Module Identification and
Status Information
Each ControlLogix I/O module maintains specific identification information
that separates it from all other modules. This information assists you in
tracking all the components of your system.
For example, you can track module identification information to be aware of
exactly what modules are located in any ControlLogix rack at any time. While
retrieving module identity, you can also retrieve the module’s status.
Module Identification and Status Information
ItemDescription
Product TypeModule’s product type, such as Analog I/O
or Digital I/O module
Catalog CodeModule’s catalog number
Major RevisionModule’s major revision number
Minor RevisionModule’s minor revision number
StatusModule’s status that shows the following information:
• Controller ownership (if any)
• Whether module has been configured
• Device Specific Status, such as:
• Self-Test
• Flash update in progress
• Communications fault
• Not owned (outputs in program mode)
• Internal fault (need flash update)
• Run mode
• Program mode (output mods only)
• Minor recoverable fault
• Minor unrecoverable fault
• Major recoverable fault
• Major unrecoverable fault
Vendor IDModule manufacturer vendor, for example Allen-Bradley
Serial NumberModule serial number
Length of ASCII Text StringNumber of characters in module’s text string
ASCII Text StringNumber of characters in module’s text string
You must perform a WHO service to retrieve this information.
Publication 1756-UM009C-EN-P - December 201019
Chapter 1 What Are ControlLogix Analog I/O Modules?
ATTENTION
Preventing Electrostatic
Discharge
This module is sensitive to electrostatic discharge.
This equipment is sensitive to electrostatic discharge, which
can cause internal damage and affect normal operation. Follow
these guidelines when you handle this equipment:
• Touch a grounded object to discharge potential static.
• Wear an approved grounding wriststrap.
• Do not touch connectors or pins on component
boards.
• Do not touch circuit components inside the equipment.
• If available, use a static-safe workstation.
• When not in use, store the equipment in appropriate
static-safe packaging.
20Publication 1756-UM009C-EN-P - December 2010
Analog I/O Operation in the
ControlLogix System
Chapter
2
Introduction
I/O modules are interfaces between the controller and the field devices that
comprise the ControlLogix system. Analog signals, which are continuous, are
converted by the module and used by the controller to mandate field-device
results.
This chapter describes how analog I/O modules operate within the
ControlLogix system.
TopicPage
Ownership21
Using RSNetWorx and RSLogix 5000 Software22
Direct Connections23
Input Module Operation24
Input Modules in a Local Chassis24
Real Time Sample (RTS)24
Requested Packet Interval (RPI)25
Input Modules in a Remote Chassis27
Output Module Operation29
Output Modules in a Local Chassis29
Output Modules in a Remote Chassis30
Listen-only Mode32
Multiple Owners of Input Modules33
Configuration Changes in an Input Module with Multiple Owners34
Ownership
Publication 1756-UM009C-EN-P - December 201021
Every I/O module in the ControlLogix system must be owned by a
ControlLogix controller. This owner-controller:
• stores configuration data for every module that it owns.
• can be local or remote in regard to the I/O module’s position.
• sends the I/O module configuration data to define the module’s
behavior and begin operation within the control system.
Each ControlLogix I/O module must continuously maintain communication
with its owner to operate normally.
Chapter 2 Analog I/O Operation in the ControlLogix System
Typically, each module in the system will have one owner only. Input modules
can have more than one owner. Output modules, however, are limited to a
single owner.
For more information on the increased flexibility provided by multiple owners
and the ramifications of using multiple owners, see
Input Module with Multiple Owners
on
page 34
Configuration Changes in an
.
Using RSNetWorx and
RSLogix 5000 Software
The I/O configuration portion of the RSLogix5000 programming software
generates the configuration data for each I/O module in the control system,
whether the module is in a local or remote chassis. A remote chassis, also
known as networked, contains the I/O module but not the module’s
owner-controller. A remote chassis can be connected to the controller via a
scheduled connection on the ControlNet network or an
EtherNet/IP network.
RSLogix 5000 configuration data is transferred to the controller during the
program download and subsequently transferred to the appropriate I/O
modules. I/O modules in the local chassis, and modules in a remote chassis
connected via the EtherNet/IP network, or unscheduled connections on the
ControlNet network, are ready to run as soon as the configuration data has
been downloaded. However, to enable scheduled connections to I/O modules
on the ControlNet network, you must schedule the network by using
RSNetWorx for ControlNet software.
Running RSNetWorx software transfers configuration data to I/O modules on
a scheduled ControlNet network and establishes a network update time (NUT)
for the ControlNet network that is compliant with the desired communication
options specified for each module during configuration.
Anytime a controller references a scheduled connection to I/O modules on a
scheduled ControlNet network, you must run RSNetWorx software to
configure the ControlNet network.
Refer to the following general steps when configuring I/O modules.
1. Configure all I/O modules for a given controller by using RSLogix 5000
programming software and download that information to the controller.
2. If the I/O configuration data references a scheduled connection to a
module in a remote chassis connected via the ControlNet network, run
RSNetWorx for ControlNet software to schedule the network.
22Publication 1756-UM009C-EN-P - December 2010
Analog I/O Operation in the ControlLogix System Chapter 2
IMPORTANT
3. After running RSNetWorx software, perform an online save of the
RSLogix 5000 project so the configuration information that
RSNetWorx software sends to the controller is saved..
You must run RSNetWorx for ControlNet software whenever a
new I/O module is added to a scheduled ControlNet chassis.
When a module is permanently removed from a remote chassis,
we recommend that you run RSNetWorx for ControlNet
software to reschedule the network and optimize the allocation
of network bandwidth.
Direct Connections
ControlLogix analog I/O modules use direct connections only.
A direct connection is a real-time data transfer link between the controller and
the device that occupies the slot that the configuration data references. When
module configuration data is downloaded to an owner-controller, the
controller attempts to establish a direct connection to each of the modules
referenced by the data.
If a controller has configuration data referencing a slot in the control system,
the controller periodically checks for the presence of a device there. When a
device’s presence is detected there, the controller automatically sends the
configuration data, and one of the following events occurs:
• If the data is appropriate to the module found in the slot, a connection
is made and operation begins.
• If the configuration data is not appropriate, the data is rejected and an
error message displays in the software. In this case, the configuration
data can be inappropriate for any of a number of reasons.
For example, a module’s configuration data may be appropriate except
for a mismatch in electronic keying that prevents normal operation.
The controller maintains and monitors its connection with a module. Any
break in the connection, such as removal of the module from the chassis while
under power, causes the controller to set fault status bits in the data area
associated with the module. The RSLogix 5000 programming software
monitors this data area to annunciate the module’s failures.
Publication 1756-UM009C-EN-P - December 201023
Chapter 2 Analog I/O Operation in the ControlLogix System
On-Board Memory
Status Data
Channel Data
Channel Data
Channel Data
Channel Data
Channel Data
Channel Data
Ch 0
Ch 1
Ch 2
Ch 3
Ch 4
Ch 5
Tim estamp
41361
1
2
Input Module Operation
Input Modules in
a Local Chassis
In traditional I/O systems, controllers poll input modules to obtain their input
status. In the ControlLogix system, a controller does not poll analog input
modules after a connection is established. Instead, the modules multicast their
data periodically. The frequency depends on the options chosen during
configuration and where in the control system that input module physically
resides.
An input module’s behavior varies depending upon whether it operates in the
local chassis or in a remote chassis. The following sections detail the
differences in data transfers between these set-ups.
When a module resides in the same chassis as the owner-controller, the
following two configuration parameters will affect how and when an input
module produces data:
Real Time Sample (RTS)
•
•
Requested Packet Interval (RPI)
Real Time Sample (RTS)
This configurable parameter, which is set during the initial configuration by
using RSLogix5000 software, instructs the module to perform two
basic operations:
1. Scan all of its input channels and store the data into on-board memory.
2. Multicast the updated channel data (as well as other status data) to the
backplane of the local chassis.
24Publication 1756-UM009C-EN-P - December 2010
Analog I/O Operation in the ControlLogix System Chapter 2
On-Board Memory
Status Data
Channel Data
Channel Data
Channel Data
Channel Data
Channel Data
Channel Data
Ch 0
Ch 1
Ch 2
Ch 3
Ch 4
Ch 5
Tim estamp
41362
IMPORTANT
Requested Packet Interval (RPI)
This configurable parameter also instructs the module to multicast its channel
and status data to the local chassis backplane.
The RPI, however, instructs the module to produce the current contents of its
on-board memory when the RPI expires, (that is, the module does not update
its channels prior to the multicast).
The RPI value is set during the initial module configuration by
using RSLogix 5000 software. This value can be adjusted when
the controller is in Program mode.
The module will reset the RPI timer each time an RTS is performed. This
operation dictates how and when the owner-controller in the local chassis will
receive updated channel data, depending on the values given to these
parameters.
If the RTS value is less than or equal to the RPI, each multicast of data from
the module will have updated channel information. In effect, the module is
only multicasting at the RTS rate.
Publication 1756-UM009C-EN-P - December 201025
Chapter 2 Analog I/O Operation in the ControlLogix System
If the RTS value is greater than the RPI, the module produces at both the RTS
rate and the RPI rate. Their respective values will dictate how often the
owner-controller will receive data and how many multicasts from the module
contain updated channel data.
In the example below, the RTS value is 100 ms and the RPI value is 25 ms.
Only every fourth multicast from the module will contain updated channel
data.
Triggering Event Tasks
When configured, ControlLogix analog input modules can trigger an event
task. The event task lets you execute a section of logic immediately when an
event (that is, receipt of new data) occurs.
Your ControlLogix analog I/O module can trigger event tasks every RTS, after
the module has sampled and multicast its data. Events tasks are useful for
synchronizing process variable (PV) samples and proportional integral
derivative (PID) calculations.
ControlLogix analog I/O modules can trigger event tasks at
every RTS but not at the RPI. For example, in the illustration
above, an event task can be only triggered every 100 ms.
26Publication 1756-UM009C-EN-P - December 2010
Analog I/O Operation in the ControlLogix System Chapter 2
ControlNet network
Multicast data
40947
Local ChassisRemote Chassis
Input Modules
in a Remote Chassis
If an input module physically resides in a remote chassis, the role of the RPI
and the module’s RTS behavior change slightly with respect to getting data to
the owner-controller, depending on what network type you are using to
connect to the modules.
Remote Input Modules Connected Via the ControlNet Network
When remote analog I/O modules are connected to the owner-controller via a
scheduled ControlNet network, the RPI and RTS intervals still define when
the module will multicast data within its own chassis (as described in the
previous section). However, only the value of the RPI determines how often
the owner-controller will receive it over the network.
When an RPI value is specified for an input module in a remote chassis
connected by a scheduled ControlNet network, in addition to instructing the
module to multicast data within its own chassis, the RPI also ‘reserves’ a spot
in the stream of data flowing across the ControlNet network.
The timing of this ‘reserved’ spot may or may not coincide with the exact value
of the RPI, but the control system guarantees that the owner-controller
receives data at least as often as the specified RPI.
As shown in the illustration below, the input data within the remote chassis is
multicast at the configured RPI. The ControlNet bridge module sends input
data back to the owner-controller at least as often as the RPI.
The ‘reserved’ spot on the network and the module’s RTS are asynchronous to
each other. This means there are best and worst Case scenarios as to when the
owner-controller will receive updated channel data from the module in a
networked chassis.
Publication 1756-UM009C-EN-P - December 201027
Chapter 2 Analog I/O Operation in the ControlLogix System
TIP
TIP
Best Case RTS Scenario
In the best case scenario, the module performs an RTS multicast with updated
channel data just before the ‘reserved’ network slot is made available. In this
case, the remotely-located owner-controller receives the data almost
immediately.
Worst Case RTS Scenario
In the worst case scenario, the module performs an RTS multicast just after
the ‘reserved’ network slot has passed. In this case, the owner-controller will
not receive data until the next scheduled network slot.
Because it is the RPI and not the RTS that dictates when the
module’s data will be sent over the network, we recommend
the RPI value be set less than or equal to the RTS to make sure
that updated channel data is received by the owner-controller
with each receipt of data.
Remote Input Modules Connected Via the EtherNet/IP Network
When remote analog input modules are connected to the owner-controller via
an EtherNet/IP network, data is transferred to the owner-controller in the
following way:
• At the RTS or RPI (whichever is faster), the module broadcasts data
within its own chassis.
• The 1756 Ethernet bridge module in the remote chassis immediately
sends the module’s data over the network to the owner-controller as
long as it has not sent data within a time frame that is one-quarter the
value of the analog input module’s RPI.
For example, if an analog input module uses an RPI = 100 ms, the
Ethernet module sends module data immediately on receiving it if
another data packet was not sent within the last 25 ms.
The Ethernet module will either multicast the module’s data to all
devices on the network or unicast to a specific owner-controller
depending on the setting of the Unicast box, as shown on
For more information, see the Guidelines to Specify an RPI
Rate for I/O Modules section in the Logix5000 Controllers
Design Considerations Reference Manual,
publication
1756-RM094
.
page 209
.
28Publication 1756-UM009C-EN-P - December 2010
Analog I/O Operation in the ControlLogix System Chapter 2
40949
Data sent from owner at the RPI
Owner-controllerOutput module
Output Module Operation
The RPI parameter governs exactly when an analog output module receives
data from the owner-controller and when the output module echoes data. An
owner-controller sends data to an analog output module only at the period
specified in the RPI. Data is not sent to the module at the end of the
controller’s program scan.
When an analog output module receives new data from an owner-controller
(that is, every RPI), the module automatically multicasts or ‘echoes’ a data
value that corresponds to the analog signal present at the output terminals to
the rest of the control system. This feature, called Output Data Echo, occurs
whether the output module is local or remote.
Depending on the value of the RPI, with respect to the length of the controller
program scan, the output module can receive and ‘echo’ data multiple times
during one program scan.
When the RPI is less than the program scan length, the controller effectively
allows the module’s output channels to change values multiple times during a
single program scan because the output module is not dependent on reaching
the end of the program to send data.
Output Modules in
a Local Chassis
When specifying an RPI value for an analog output module, you instruct the
controller when to broadcast the output data to the module. If the module
resides in the same chassis as the owner-controller, the module receives the
data almost immediately after the controller sends it.
Publication 1756-UM009C-EN-P - December 201029
Chapter 2 Analog I/O Operation in the ControlLogix System
If an output module resides in a remote chassis, the role of the RPI changes
slightly with respect to getting data from the owner-controller, depending on
what network type you are using to connect to the modules.
Remote Output Modules Connected Via the ControlNet Network
When remote analog output modules are connected to the owner-controller
via a scheduled ControlNet network, in addition to instructing the controller
to multicast the output data within its own chassis, the RPI also ‘reserves’ a
spot in the stream of data flowing across the ControlNet network.
The timing of this ‘reserved’ spot may or may not coincide with the exact value
of the RPI, but the control system will guarantee that the output module will
receive data at least as often as the specified RPI.
The ‘reserved’ spot on the network and when the controller sends the output
data are asynchronous to each other. This means there are best and worst case
scenarios as to when the module will receive the output data from the
controller in a networked chassis.
Best Case RPI Scenario
In the best case scenario, the controller sends the output data just before the
‘reserved’ network slot is available. In this case, the remotely-located output
module receives the data almost immediately.
30Publication 1756-UM009C-EN-P - December 2010
Loading...
+ 371 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.