Allen-Bradley 1756-L55M13, 1756-L55M22, 1756-L55M12, 1756-L55M14, 1756-L55M16 User Manual
...
ControlLogix
Controllers
1756-L55M12, 1756-L55M13,
1756-L55M14, 1756-L55M16,
1756-L55M22, 1756-L55M23,
1756-L55M24, 1756-L61, 1756-L62,
1756-L63, 1756-L64,
1756-L60M03SE
Firmware Revision 16
User Manual
Important User Information
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
available from your local Rockwell Automation sales office or online at
http://literature.rockwellautomation.com) describes some important
differences 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 we use notes to make you aware of safety
considerations.
WARNING
IMPORTANT
ATTENTION
SHOCK HAZARD
BURN HAZARD
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.
Summary of Changes
Introduction
Updated Information
Topic Page
1756-L64 ControlLogix Controller Throughout manual
Add-On Instructions 73
Select a System Overhead Percentage 79
Add Your Axes 100
Obtain Axis Information 108
The release of this document contains new and updated information.
To find new and updated information, look for change bars, as shown
next to this paragraph.
The document contains these changes.
3 Publication 1756-UM001G-EN-P - January 2007
Summary of Changes 4
Notes:
Publication 1756-UM001G-EN-P - January 2007
ControlLogix System Overview
Directly Connect to the Controller
via the Serial Port
Communicate over Networks
Table of Contents
Preface
About this Publication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Who Should Use This Publication . . . . . . . . . . . . . . . . . . . . . 9
Additional Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Chapter 1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Install Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Chapter 2
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Connect the Controller to via the Serial Port. . . . . . . . . . . . . 15
Configure the Serial Driver . . . . . . . . . . . . . . . . . . . . . . . . . 17
Select the Controller Path . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Chapter 3
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
EtherNet/IP Network Communication . . . . . . . . . . . . . . . . . 22
Connections Over an EtherNet/IP Network . . . . . . . . . . . 24
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
ControlNet Network Communication . . . . . . . . . . . . . . . . . . 25
Connections Over a ControlNet Network . . . . . . . . . . . . 27
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
DeviceNet Network Communication . . . . . . . . . . . . . . . . . . 28
Connections over DeviceNet . . . . . . . . . . . . . . . . . . . . . 30
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Serial Network Communication . . . . . . . . . . . . . . . . . . . . . . 31
Communicate with DF1 Devices. . . . . . . . . . . . . . . . . . . 32
Communicate with ASCII Devices. . . . . . . . . . . . . . . . . . 34
Modbus Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
DH-485 Network Communication . . . . . . . . . . . . . . . . . . . . 37
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
DH+ Network Communication. . . . . . . . . . . . . . . . . . . . . . . 41
Communicate over a DH+ Network . . . . . . . . . . . . . . . . 42
Universal Remote I/O Communication . . . . . . . . . . . . . . . . . 43
Communicate Over a Universal Remote I/O Network . . . 44
Foundation Fieldbus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
HART (Highway Addressable Remote Transducer) Protocol . 46
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Chapter 4
Manage Controller
Communication
5 Publication 1756-UM001G-EN-P - January 2007
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Connection Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
6 Table of Contents
Place, Configure, and Monitor I/O
Modules
Produce and Consume (Interlock) Data . . . . . . . . . . . . . . . . 48
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Send and Receive Messages. . . . . . . . . . . . . . . . . . . . . . . . . 49
Determine Whether to Cache Message Connections . . . . 49
Calculate Connection Use . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Connections Example. . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Chapter 5
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Select I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Place Local I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Configure I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
I/O Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Configure Distributed I/O on an EtherNet/IP Network . . . . . 57
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Configure Distributed I/O on a ControlNet Network . . . . . . . 58
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Configure Distributed I/O on a DeviceNet Network . . . . . . . 59
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Address I/O Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Add 1756 I/O at Runtime. . . . . . . . . . . . . . . . . . . . . . . . . . . 61
ControlNet I/O Considerations . . . . . . . . . . . . . . . . . . . . 61
EtherNet/IP I/O Considerations . . . . . . . . . . . . . . . . . . . 62
Determine When Data Is Updated . . . . . . . . . . . . . . . . . . . . 63
Reconfigure an I/O Module . . . . . . . . . . . . . . . . . . . . . . . . . 64
Reconfigure a Module via RSLogix 5000
Programming Software . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Reconfigure an I/O Module via a MSG Instruction. . . . . . 65
Develop Applications
Publication 1756-UM001G-EN-P - January 2007
Chapter 6
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Manage Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
DevelopPrograms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Define Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Define Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Define Routines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Sample Controller Projects . . . . . . . . . . . . . . . . . . . . . . . 71
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Organize Tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Select a Programming Language . . . . . . . . . . . . . . . . . . . . . 73
Add-On Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Configure PhaseManager
Table of Contents 7
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Monitor Controller Status. . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Monitor Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Determine if Communication Has Timed Out with
Any Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Determine if Communication Has Timed Out with
a Specific I/O Module . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Interrupt the Execution of Logic and Execute the
Fault Handler. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Select a System Overhead Percentage . . . . . . . . . . . . . . . . . 79
Chapter7
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
PhaseManager Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
State Model Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
How Equipment Changes States . . . . . . . . . . . . . . . . . . . 86
Manually Change States . . . . . . . . . . . . . . . . . . . . . . . . . 87
Compare PhaseManager to Other State Models. . . . . . . . . . . 87
Minimum System Requirements . . . . . . . . . . . . . . . . . . . . . . 88
Equipment Phase Instructions . . . . . . . . . . . . . . . . . . . . . . . 88
Develop Motion Applications
Chapter 8
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Make the Controller the CST Master . . . . . . . . . . . . . . . . . . . 90
Multiple Controllers in the Chassis . . . . . . . . . . . . . . . . . 90
Add the Motion Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Add SERCOS Interface Drives . . . . . . . . . . . . . . . . . . . . . . . 93
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Set Up Each SERCOS Interface Module . . . . . . . . . . . . . . . . 95
Add the Motion Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Add Your Axes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Set Up Each Axis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Check the Wiring of Each Drive. . . . . . . . . . . . . . . . . . . . . 104
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Tune Each Axis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Obtain Axis Information . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Program Motion Control . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Publication 1756-UM001G-EN-P - January 2007
8 Table of Contents
Configure Redundancy
SIL 2 Certification
Maintain Nonvolatile Memory
Chapter 9
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . 111
ControlLogix Redundancy Overview . . . . . . . . . . . . . . . . . 111
Build a Redundant System. . . . . . . . . . . . . . . . . . . . . . . . . 113
System Considerations . . . . . . . . . . . . . . . . . . . . . . . . . 114
ControlNet Considerations in Redundant Systems . . . . . . . . 114
EtherNet/IP Considerations in Redundant Systems . . . . . . . 115
IP Address Swapping . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Redundancy and Scan Time. . . . . . . . . . . . . . . . . . . . . . . . 116
Minimum System Requirements . . . . . . . . . . . . . . . . . . . . . 116
Chapter 10
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
SIL 2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
SIL 2 Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Chapter 11
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Choose a Controller That Has Nonvolatile Memory. . . . . . . 120
Prevent a Major Fault During a Load. . . . . . . . . . . . . . . 120
Use a CompactFlash Reader. . . . . . . . . . . . . . . . . . . . . . . . 121
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Maintain the Battery
LED Indicators
Chapter 12
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Check If the Battery Is Low . . . . . . . . . . . . . . . . . . . . . . . . 124
Estimate 1756-BA1 Battery Life . . . . . . . . . . . . . . . . . . . . . 124
Estimate 1756-BA2 Battery Life
(1756-L6x series B controllers only) . . . . . . . . . . . . . . . . . . 126
Estimate Warning Time . . . . . . . . . . . . . . . . . . . . . . . . 127
Maintain a 1756-BATM Battery Module . . . . . . . . . . . . . . . 128
Check the BAT LED Indicator. . . . . . . . . . . . . . . . . . . . 128
Store Batteries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Appendix A
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Index
Publication 1756-UM001G-EN-P - January 2007
Preface
About this Publication
Who Should Use This Publication
Additional Resources
Catalog Number Title Publication
1756-L55Mx
1756-L6x
Use this manual to become familiar with the ControlLogix controller
and its features. This version of the manual corresponds to controller
firmware revision 15.
This manual describes the necessary tasks to install, configure,
program, and operate a ControlLogix system. In some cases, this
manual includes references to additional documentation that provides
the more comprehensive details.
These core documents address the Logix5000 family of controllers:
Logix5000 Controllers Quick Start 1756-QS001
Logix5000 Controllers Common Procedures Programming Manual 1756-PM001
Logix5000 Controllers System Reference 1756-QR107
Logix5000 Process Control and Drives Instructions Reference
Manual
Logix5000 Process Control and Drives Instructions Reference
Manual
Logix5000 Controllers Motion Instructions 1756-RM007
1756-RM003
1756-RM006
To view or download manuals, visit
http://literature.rockwellautomation.com/literature.
To obtain a hard copy of a manual, contact your local Rockwell
Automation distributor or sales representative.
9 Publication 1756-UM001G-EN-P - January 2007
10
Notes:
Publication 1756-UM001G-EN-P - January 2007
ControlLogix System Overview
Chapter
1
Introduction
1756 I/O Modules in the
Same Chassis as the
ControlLogix Controller
This chapter provides an overview of the ControlLogix system. The
ControlLogix system provides sequential, process, motion, and drive
control together with communication and I/O in a chassis-based
system. A simple ControlLogix system consists of a stand-alone
controller and I/O modules in a single chassis.
ControlLogix Controller
For a more flexible system, use:
• multiple controllers in a single chassis.
• multiple controllers joined across networks.
• I/O from multiple platforms that is distributed in many locations
and connected over multiple I/O links.
ControlLogix System Overview
Communication Interface
Modules in the Same
Chassis as the
ControlLogix Controller
EtherNet/IP Link
1756 I/O modules in the
Same chassis as the
ControlLogix Controller
Remote I/O Modules
Drives
}
ControlNet Link
EtherNet/IP Link
ControlNet Link
Computers
Other Controllers
11 Publication 1756-UM001G-EN-P - January 2007
SERCOS Drives
SERCOS Link
DeviceNet Link
Universal remote I/O Link
12 ControlLogix System Overview
The ControlLogix controller is part of the Logix5000 family of
controllers. A ControlLogix system includes:
• the ControlLogix controller is available in different combinations
of user memory.
Controller Memory for Data
and Logic
I/O Nonvolatile
Backup Memory
1756-L55M12 750 KB 208 KB no
1756-L55M13 1.5 MB 208 KB no
1756-L55M14 3.5 MB 208 KB no
1756-L55M16 7.5 MB
208 KB no
≤ 3.5 MB of data
1756-L55M22 750 KB 208 KB Integrated
1756-L55M23 1.5 KB 208 KB Integrated
1756-L55M24 3.5 KB 208 KB Integrated
1756-L61 2 MB 478 KB
1756-L62 4 MB 478 KB
1756-L63 8 MB 478 KB
1756-L64 16 MB 478 KB
1756-L60M03SE 750 KB 478 KB
(1)
CompactFlash is optional and does not come with the controller.
CompactFlash
CompactFlash
CompactFlash
CompactFlash
CompactFlash
(1)
(1)
(1)
(1)
(1)
card
card
card
card
card
• RSLogix 5000 programming software.
• 1756 ControlLogix I/O modules that reside in a 1756 chassis.
• different communication modules for EtherNet/IP, ControlNet,
DeviceNet, DH+, and Universal remote I/O networks.
• other networks via third-party devices, such as Foundation
Fieldbus and the Highway Addressable Remote Transducer
(HART).
• a built-in serial port on every ControlLogix controller.
Publication 1756-UM001G-EN-P - January 2007
ControlLogix System Overview 13
The ControlLogix controller divides resources between a Logix CPU
and a backplane CPU.
Logix CPU and Backplane CPU
Design
Logic and Data Memory
Program Source Code
Tag Data
RSLinx Tag Group Lists
• The Logix CPU executes application code and messages.
• The backplane CPU communicates with I/O and sends and
When you design a ControlLogix system, select:
• I/O devices.
• motion control and drives requirements.
• communication modules.
• controllers.
• chassis.
• power supplies.
• software.
I/O Memory
I/O Data
Logix
CPU
I/O Force Tables
Message Buffers
Produced/consumed Tags
Backplane
CPU
receives data from the backplane. This CPU operates
independently from the Logix CPU, so it sends and receives I/O
information asynchronous to program execution.
Install Hardware
To install a ControlLogix controller:
• install memory options.
– on a 1756-L55, install a memory board for additional memory.
– on a 1756-L6x, install a 1784-CF64 CompactFlash card for
nonvolatile memory.
See the chapter Maintain Nonvolatile Memory.
• connect the battery.
See the chapter Maintain the Battery.
• install the controller in the chassis.
Publication 1756-UM001G-EN-P - January 2007
14 ControlLogix System Overview
• make serial connections.
See the chapter Directly Connect to the Controller via the Serial
Port.
• load controller firmware.
• make additional network connections.
See the chapter Communicate over Networks.
Publication 1756-UM001G-EN-P - January 2007
Chapter
2
Directly Connect to the Controller via the Serial Port
Introduction
Connect the Controller to via the Serial Port
This chapter explains how to connect the controller to the serial port
and how to upload and download a project to the controller.
Topic Page
Connect the Controller to via the Serial Port 15
Configure the Serial Driver 17
Select the Controller Path 19
To connect a serial cable, perform this procedure.
1. Obtain a 1756-CP3 serial cable.
You can also use a 1747-CP3 cable from the SLC product family,
but once the cable is connected you cannot close the controller
door.
15 Publication 1756-UM001G-EN-P - January 2007
16 Directly Connect to the Controller via the Serial Port
TIP
I
If you make your own serial cable:
• Limit the length to 15.2m (50 ft).
• Wire the connectors this way.
Workstation Controller
1 CD
2 RDX
3 TXD
4 DTR
COMMON
6 DSR
7 RTS
8 CTS
9
1 CD
2 RDX
3 TXD
4 DTR
COMMON
6 DSR
7 RTS
8 CTS
9
• Attach the shield to both connectors.
2. Connect the cable to the controller and to your workstation.
CP3 Cable
Publication 1756-UM001G-EN-P - January 2007
Directly Connect to the Controller via the Serial Port 17
Configure the Serial Driver
Use RSLinx software to configure the RS-232 DF1 Device driver for
serial communication.
To configure the driver, perform this procedure.
1. From the Communications pull-down menu in RSLinx software,
choose Configure Drivers.
The Configure Drivers dialog appears.
2. From the Available Driver Types pull-down menu, choose the
RS-232 DF1 Device driver.
3. Click Add New.
The Add New RSLinx Driver dialog appears.
4. Type the driver name and click OK.
Publication 1756-UM001G-EN-P - January 2007
18 Directly Connect to the Controller via the Serial Port
5. Specify the serial port settings.
a. From the Comm Port pull-down menu, choose the serial port
on the workstation to which the cable is connected.
b. From the Device pull-down menu, choose Logix 5550-Serial
Port.
c. Click Auto-Configure.
6. Was the auto configuration successful?
If Then
Yes Click OK.
No Go to step 5. and verify that you selected the correct Comm Port.
7. Click Close.
Publication 1756-UM001G-EN-P - January 2007
Directly Connect to the Controller via the Serial Port 19
Select the Controller Path
In RSLogix 5000 programming software, to select the controller path,
perform this procedure.
1. Open an RSLogix 5000 project for the controller.
2. From the Communications pull-down menu, choose Who
Active.
3. Expand the communication driver to the level of the controller.
4. Select the controller.
To Choose
Monitor the project in the controller Go Online
Transfer a copy of the project from the controller to
RSLogix 5000 software
Transfer the open project to the controller Download
Upload
Publication 1756-UM001G-EN-P - January 2007
20 Directly Connect to the Controller via the Serial Port
Notes:
Publication 1756-UM001G-EN-P - January 2007
Communicate over Networks
e
Chapter
3
Introduction
Network Support Example
Control distributed (remote) I/O
• EtherNet/IP network
• ControlNet network
• DeviceNet network
• Universal remote I/O network
• Foundation Fieldbus network
• HART network
Produce/consume (interlock) data between controllers
• EtherNet/IP network
• ControlNet network
This chapter explains over what networks you can communicate.
ControlLogix Controller
Control Network
Distributed (remot
I/O Platform)
ControlLogix Controller
Control Network
Other Logix5000
Controller
Send and receive messages to and from other devices.
This includes access to the controller via RSLogix 5000
programming software.
• EtherNet/IP network
• ControlNet network
• DeviceNet (to devices only) network
• serial network
• DH+ network
• DH-485 network
Topic Page
EtherNet/IP Network Communication 22
ControlNet Network Communication 25
DeviceNet Network Communication 28
21 Publication 1756-UM001G-EN-P - January 2007
ControlLogix Controller
Control Network
Other Remote
Devices
22 Communicate over Networks
Topic Page
Serial Network Communication 31
DH-485 Network Communication 37
DH+ Network Communication 41
Universal Remote I/O Communication 43
Foundation Fieldbus 45
HART 46
EtherNet/IP Network Communication
The EtherNet/IP network offers a full suite of control, configuration,
and data collection services by layering the Common Industrial
Protocol (CIP) over the standard Internet protocols, such as TCP/IP
and UDP. This combination of well-accepted standards provides the
capability required to both support information data exchange and
control applications.
The EtherNet/IP network also uses commercial, off-the-shelf Ethernet
components and physical media, providing you with a cost-effective
plant-floor solution.
For EtherNet/IP network communication, you have several
communication modules from which to choose.
EtherNet/IP Communication Modules
Functions Required
Module
• Control I/O modules.
• Require an adapter for distributed I/O on EtherNet/IP links.
• Communicate with other EtherNet/IP devices (messages).
• Share data with other Logix5000 controllers (produce/consume).
• Bridge EtherNet/IP links to route messages to devices on other
networks.
• Require remote access via Internet browser to tags in a local
ControlLogix controller.
• Communicate with other EtherNet/IP devices (messages).
• BridgesEtherNet/IP links to route messages to devices on other
networks.
• Does not support I/O or produced/consumed tags.
1756-ENBT
1756-EWEB
Publication 1756-UM001G-EN-P - January 2007
Communicate over Networks 23
Required Software for EtherNet/IP Communication
Software Functions Requirement
RSLogix 5000 • Configure ControlLogix projects.
• Define EtherNet/IP communication.
RSLogix 5000
BOOTP/DHCP Utility
RSNetWorx for
EtherNet/IP
Assign IP addresses to devices on an
EtherNet/IP network.
• Configure EtherNet/IP devices by IP
addresses and/or host names.
• Provide bandwidth status.
Yes
No
RSLinx • Configure communication devices.
• Provide diagnostics.
• Establish communication between devices.
Yes
The EtherNet/IP communication modules:
• support messaging, produced/consumed tags, HMI, and
distributed I/O.
• encapsulate messages within standard TCP/UDP/IP protocol.
• share a common application layer with ControlNet and
DeviceNet networks.
• connect via RJ45 cable.
• support half/full duplex 10 MB or 100 MB operation.
• support standard switches.
In this example:
• The controllers produce and consume tags.
• The controllers initiate MSG instructions that send and receive
data or configure devices.
• The personal computer uploads and downloads projects to the
controllers.
• The personal computer configures devices on an EtherNet/IP
network.
Publication 1756-UM001G-EN-P - January 2007
24 Communicate over Networks
EtherNet/IP Network Overview
FlexLogix Controller with
1788-ENBT Module
Distributed I/O
CompactLogix Controller
with Integrated
EtherNet/IP Port
PowerFlex 700S AC
Drive with DriveLogix
LINK NET OK
ControlLogix
Controller with
1756-ENBT
Module
Switch
Workstation
LINK NET OK
1756-ENBT Module
(as an adapter) with 1756
I/O Modules
1734-AENT Adapter with
1734 I/O Modules
Connections Over an EtherNet/IP Network
1794-AENT Adapter with
1794 I/O Modules
You indirectly determine the number of connections the controller
uses by configuring the controller to communicate with other devices
in the system. Connections are allocations of resources that provide
more reliable communication between devices compared to
unconnected messages.
All EtherNet/IP connections are unscheduled. An unscheduled
connection is triggered by the requested packet interval (RPI) for I/O
control or the program, such as a MSG instruction. Unscheduled
messaging lets you send and receive data when needed.
The 1756 EtherNet/IP communication modules support 128 CIP
(Common Industrial Protocol) connections over an EtherNet/IP
network.
Publication 1756-UM001G-EN-P - January 2007
Communicate over Networks 25
Additional Resources
For additional information, consult these publications:
• EtherNet/IP Modules in Logix5000 Control Systems User Manual,
publication ENET-UM001
• Logix5000 Controllers Design Considerations Reference Manual,
publication 1756-RM094
ControlNet Network Communication
The ControlNet network is a real-time control network that provides
high-speed transport of both time-critical I/O and interlocking data
and messaging data, including uploading and downloading of
programming and configuration data on a single physical-media link.
The ControlNet network’s highly-efficient data transfer capability
significantly enhances I/O performance and peer-to-peer
communication in any system or application.
The ControlNet network is highly deterministic and repeatable and
remains unaffected as devices are connected or disconnected from the
network. This robust quality results in dependable, synchronized, and
coordinated real-time performance.
The ControlNet network often functions as:
• a substitute/replacement for the remote I/O (RIO) network
because the ControlNet network adeptly handles large numbers
of I/O points.
• a backbone to multiple distributed DeviceNet networks.
• a peer interlocking network.
For ControlNet communication, you have two communication
modules from which to choose.
ControlNet Communication Modules
Functions Required
Module
• Control I/O modules.
• Require an adapter for distributed I/O on ControlNet links.
• Communicate with other ControlNet devices (messages).
• Share data with other Logix5000 controllers (produce/consume).
• Bridge ControlNet links to route messages to devices on other networks.
• Perform same functions as a 1756-CNB module.
• Support redundant ControlNet media.
Publication 1756-UM001G-EN-P - January 2007
1756-CNB
1756-CNBR
26 Communicate over Networks
Required Software for ControlNet Communication
Software Functions Requirement
RSLogix 5000 • Configure ControlLogix projects.
• Define ControlNet communication.
RSNetWorx
for ControlNet
RSLinx • Configure communication devices.
• Configure ControlNet devices by IP addresses
and/or host names.
• Schedule a network.
• Provide diagnostics.
• Establish communication between devices.
Yes
The 1756-CNB and 1756-CNBR ControlNet communication modules:
• support messaging, produced/consumed tags and distributed
I/O.
• share a common application layer with DeviceNet and
EtherNet/IP networks.
• require no routing tables.
• support the use of coax and fiber repeaters for isolation and
increased distance
• support redundant media (1756-CNBR module only)
In this example:
• the controllers produce and consume tags.
• the controllers initiate MSG instructions that send and receive
data or configure devices.
• the personal computer uploads and downloads projects to the
controllers.
• the personal computer configures devices on a ControlNet
network, and it can configure the network itself.
Publication 1756-UM001G-EN-P - January 2007
CompactLogix Controller
Communicate over Networks 27
ControlNet Network Overview
Workstation
Distributed I/O
PowerFlex 700S AC
Drive with DriveLogix
1756-CNB Module
(as an adapter) with
1756 I/O Modules
ControlNet Network
FlexLogix Controller with
1788-CNC Card
PanelView Terminal
PLC-5/40C Controller
1794-ACN15 Adapter
with 1794 I/O Modules
1734-ACNR Adapter with
1734 I/O Modules
Connections Over a ControlNet Network
You indirectly determine the number of connections the controller
uses by configuring the controller to communicate with other devices
in the system. Connections are allocations of resources that provide
more reliable communication between devices compared to
unconnected messages.
ControlNet Connections
Connection Definition
Scheduled
(unique to a
ControlNet
network)
Unscheduled An unscheduled connection is a message transfer between controllers that is triggered by the requested packet interval
A scheduled connection is unique to ControlNet communication. A scheduled connection lets you send and receive data
repeatedly at a predetermined interval, which is the requested packet interval (RPI). For example, a connection to an I/O
module is a scheduled connection because you repeatedly receive data from the module at a specified interval. Other
scheduled connections include connections to:
• communication devices.
• produced/consumed tags.
On a ControlNet network, you must use RSNetWorx for ControlNet software to enable all scheduled connections and
establish a network update time (NUT). Scheduling a connection reserves network bandwidth to specifically handle the
connection.
(RPI) or the program, such as a MSG instruction. Unscheduled messaging lets you send and receive data when you need to.
Unscheduled connections use the remainder of network bandwidth after scheduled connections are allocated.
Publication 1756-UM001G-EN-P - January 2007
28 Communicate over Networks
The 1756-CNB and 1756-CNBR communication modules support 64
CIP connections over a ControlNet network. However, for optimal
performance, only configure 48 connections for each module.
Additional Resources
For additional information, consult these publications:
• ControlNet Modules in Logix5000 Control Systems User Manual,
publication CNET-UM001
• Logix5000 Controllers Design Guidelines Reference Manual,
publication 1756-RM094
DeviceNet Network Communication
The DeviceNet network uses the Common Industrial Protocol (CIP) to
provide the control, configuration, and data collection capabilities for
industrial devices. The DeviceNet network uses the proven Controller
Area Network (CAN) technology, which lowers installation costs and
decreases installation time and costly downtime.
A DeviceNet network provides access to the intelligence present in
your devices by letting you connect devices directly to plant-floor
controllers without having to hard wire each device into an I/O
module.
DeviceNet communication requires a 1756-DNB DeviceNet
communication module. The DeviceNet network uses the Common
Industrial Protocol (CIP) to provide the control, configuration, and
data collection capabilities for industrial devices.
Functions Required Module
• Control I/O modules.
• Require an adapter for distributed I/O on DeviceNet links.
• Communicate with other DeviceNet devices (messages).
• Link an EtherNet/IP network to a DeviceNet network.
• Require multiple networks.
• Link a ControlNet network to a DeviceNet network.
• Require multiple networks.
1756-DNB
1788-EN2DN
1788-CN2DN
Publication 1756-UM001G-EN-P - January 2007
Communicate over Networks 29
Required Software for DeviceNet Communication
Software Functions Requirement
RSLogix 5000 • Configure ControlLogix projects.
• Define EtherNet/IP communication.
RSNetWorx for
DeviceNet
• Configure DeviceNet devices.
• Define the scan list for those devices.
RSLinx • Configure communication devices.
• Provide diagnostics.
• Establish communication between devices.
The DeviceNet communication module:
• supports messaging to devices, not controller to controller.
• shares a common application layer with ControlNet and
EtherNet/IP networks.
• offers diagnostics for improved data collection and fault
detection.
• requires less wiring than traditional, hardwired systems.
ControlLogix DeviceNet Network Overview
ControlLogix Controller
with 1756-ENBT Module
EtherNet/IP Network
CompactLogix Controller
FLEX Adapter and I/O
Linking
Devices
Yes
Personal Computer
Input/output
Devices
Motor
Starter
PowerFlex
ac Drive
DeviceNet Network
Sensor
PWR
PWR
STS
STS
PORT
MOD
PORT
NET A
MOD
NET B
NET A
NET B
Indicator
Lights
Publication 1756-UM001G-EN-P - January 2007
Pushbutton
Cluster
Bar Code
Scanner
30 Communicate over Networks
Connections over DeviceNet
The ControlLogix controller requires two connections for each
1756-DNB module. One connection is for module status and
configuration. The other connection is a rack-optimized connection
for the device data.
The 1756-DNB module has fixed sections of memory for the input and
output data of the DeviceNet devices on the network. Each device on
your network requires either some input or output memory of the
scanner. Some devices both send and receive data, so they need both
input and output memory. The 1756-DNB module supports up to:
• 124 DINTs of input data.
• 123 DINTs of output data.
Additional Resources
For more information, consult these publications:
• DeviceNet Modules in Logix5000 Control Systems User Manual,
publication DNET-UM004
• Logix5000 Controllers Design Considerations Reference Manual,
publication 1756-RM094
Publication 1756-UM001G-EN-P - January 2007
Loading...