ControlLogix Training Manual
ControlLogix Training Manual
TABLE OF CONTENTS
MODULE 1 ....................................................................................................................... 10
1. INTRODUCTION................................................................................................... 11
2. CONTROLLOGIX SYSTEM OVERVIEW ........................................................ 11
2.1 CONTROLLOGIX CONTROLLER .............................................................................................. 13
2.2 CONTROLLOGIX COMMUNICATION MODULES ................................................................ 13
2.3 CONTROLLOGIX POWER SUPPLIES ....................................................................................... 13
2.4 CONTROLLOGIX CHASSIS ........................................................................................................ 13
3. CONNECTING A COMPUTER TO NETWORK .............................................. 14
3.1 MANAGE PROJECT FILES ......................................................................................................... 16
3.1.1 Save your Changes ........................................................................................ 18
3.2 ORGANIZE TASKS ....................................................................................................................... 19
3.2.1 Organize your Logic ..................................................................................... 19
3.2.2 Verify the Controller ..................................................................................... 22
3.3 PROJECT PROPERTIES ................................................................................................................ 22
3.3.1 Tabs description ............................................................................................ 23
3.3.2 Project organization ...................................................................................... 24
3.4 TASKS, PROGRAMS AND ROUTINES ....................................................................................... 26
3.4.1 Definitions..................................................................................................... 26
3.4.2 Task ............................................................................................................... 26
3.4.3 Continuous Task ........................................................................................... 27
3.4.4 Periodic Task ................................................................................................ 27
3.4.5 Creating a periodic task................................................................................. 28
3.5 PROGRAM ...................................................................................................................................... 29
3.5.1 Creating a Program ....................................................................................... 29
3.6 ROUTINE ........................................................................................................................................ 31
3.6.1 Creating a Routine ........................................................................................ 31
3.6.2 Main Routine ................................................................................................ 32
3.7 DATA ORGANIZATION ............................................................................................................... 34
3.7.1 Properties of a tag ......................................................................................... 34
3.7.2 Naming Tags ................................................................................................. 34
3.7.3 Types of tags ................................................................................................. 35
3.7.4 Data Types .................................................................................................... 35
3.7.5 Creating Tags ................................................................................................ 36
3.7.6 Alias Tags ..................................................................................................... 37
MODULE 2 ....................................................................................................................... 38
4. COMMUNICATION WITH I/O........................................................................... 39
4.1 CONFIGURE AN I/O MODULE.................................................................................................. 39
10. GET SYSTEM VALUE (GSV) & SET SYSTEM VALUE (SSV)
LIST OF FIGURES:
LIST OF TABLES:
MODULE 1
1. Introduction
This course provides students with the necessary resources and hands-on practice to efficiently
troubleshoot a ControlLogix. It builds upon the student’s fundamental knowledge of common
controller terms and operation, the student’s ability to identify and create fundamental
RSLogix 5000 project components and the student’s experience interpreting basic ladder logic.
This course adds to the student’s skill set by introducing new tasks such as connecting to a
network, interpreting project execution, editing ladder logic, and more.
After practicing such skills, students will be presented with a systematic strategy for diagnosing
and troubleshooting a variety of system errors, for example, software configuration, electrical
noise, controller, I/O, and other possible problems.
ControlLogix Controllers
ControlLogix Communication Modules
ControlLogix I/O Modules
ControlLogix Power Supplies
ControlLogix Chassis
Different communication modules are available for different networks (i.e. ControlNet, Ethernet,
DeviceNet etc.).
2. Connect one end of the Ethernet cable to the NIC of the computer and other end to the
Ethernet switch of the network.
5. Double click on the Local Area Connection icon the following window will open.
6. Click on the properties Tab and select Internet protocol (TCP\IP) as shown in the figure.
7. Click on the Properties Tab and select “Use the following IP address” radio button as
shown in the figure
8. Asked IP address from your Network Administrator. Enter IP address in the “IP address”
field and click OK.
9. In order to verify that your computer is connected to network “ping” other systems on the
network by using command prompt. If you receive response from systems on the network
it means that your computer is successfully connected to the network.
Before you program a Logix5000 controller, you must create a project File:
87654 3
.
Figure 6: New Controller
6. Select the type of chassis (number of slots) that contains the controller.
8. To store the file in a different folder (other than the default Create In path), click
Browse and select a folder.
9. Click OK.
When you create a project, the name of the project file is the same as the name of the controller.
As you create logic and make configuration changes, save the project.
To: Do this:
save your changes From the File menu, select Save.
make a copy of the open
A. From the File menu, select Save As.
project
but keep the existing
B. Type a name for the project file. Use
name of
the controller Underscores [ _ ]in place of spaces.
C. Click Save.
make a copy of the
A. From the File menu, select Save As.
project and
assign a different name to B. Type a name for the project file. Use
the controller Underscores [_] in place of spaces.
C. Click Save.
F. Click OK.
After you create a project file, organize your project into tasks. To organize your project into
tasks, do the following steps:
To execute your logic, you use a task (s). There are two types of Tasks:
The Tasks folder contains the tasks for the controller (i.e., your logic).
Main Task is the default continuous task. It runs all the time and repeatedly executes Main
Program. Whenever Main Program executes, any logic in Main Routine will execute. You can
use Main Routine to call other routines (subroutines) within Main Program.
General: modify the controller name, description, and controller properties for the current
project.
Date/Time: online only view and edit the controller’s wall clock time and the coordinated system
time status.
Communications: configure communication information that is stored with the project file.
Serial Port: view and configure the serial port on the controller.
DF1 point-to-point
DF1 slave
DF1 master
Major Faults: online only view any major faults that have occurred on the controller.
Minor Faults: online only view any minor faults that have occurred on the controller.
Advanced: some features are online only view and edit advanced controller properties, which
include the system fault program, the power loss program, and system overhead time slice
3.4.1 Definitions
3.4.2 Task
A task provides scheduling and priority information for a set of one or more programs that
execute based on specific criteria. Once a task is triggered (activated), all the programs assigned
(scheduled) to the task execute in the order in which they are displayed in the controller
organizer. Tasks can be continuous or periodic.
Tasks can be scheduled, edited, and controlled. Each task can contain multiple programs, status
information, and configuration information.
The Logix5550 controller supports 32 separate tasks. One task, the Main Task, is always
continuous; the other 31 tasks are periodic. When you create a project, the Main Task is already
defined as a continuous task.
Once you create a task, there are other properties that you must configure, such as how the
programs within the task execute. You can prioritize the tasks up to 15 levels:
Tasks at the same priority execute on a time-slice basis at 1 ms intervals .Once you create
a task; you can later change its descriptive information if you wish.
The continuous task runs in the background. Any CPU time not allocated to other operations
(such as motion, communications, and periodic tasks) is used to execute the programs within the
continuous task.
The continuous task runs all the time. When the continuous task completes a full scan, it
restarts immediately.
A project does not require a continuous task. If used, there can be only one continuous
task.
A periodic task performs a function at a specific rate. Whenever the time for the periodic task
expires, the task interrupts the continuous task, executes one time, and then returns control to
where the continuous task left off. You can configure the time period from 1 ms to 2000 s. The
default is 10 ms. You can create up to 32 periodic tasks and assign a priority to each:
The highest priority task interrupts all lower priority tasks. A higher priority task can interrupt a
lower priority task multiple times. Tasks at the same priority execute on a time-slice basis at 1 ms
intervals. There are 15 configurable priority levels for periodic tasks, from 1 to 15, with 1 being
the highest and 15 being the lowest priority
Example:
Task execution order for a project with two periodic tasks and one continuous task
1. In the controller organizer, right-click the Tasks folder and choose New Task.
4. In the Watchdog list, type the watchdog time for the task.
5. In the Rate text box, type the rate at which you want the task to execute.
6. In the Priority text box, type the priority for the task.
7. Choose OK
3.5 Program
A program is a subdivision of a task. When a task is triggered, the scheduled programs within the
task execute to completion from first to last.
Each program contains a local data area (referred to as program tags), main executable routine,
subroutines, and a fault routine. The controller supports up to 32 programs. The programs within
a task execute from first to last.
When you create a project, the Main Program is already defined in the Main Task.
Once you create a program, you must then configure the main routine and, optionally, a fault
routine. You can later change the program’s descriptive information if you wish.
Each task requires at least one program. You can create multiple programs for a task.
1. In the controller organizer, right-click the task that will execute the program and choose
New Program.
3. Choose OK
3.6 Routine
Routines provide the executable code for the project in a controller (similar to a program file in a
PLC or SLC controller). Each routine uses a specific programming language, such as ladder
logic.
Each program must have a main routine configured. You can also specify fault routine and
additional subroutines. You can have as many routines per program as the controller memory
allows.
When you create a project, the Main Routine is already defined in the Main Program.
Once you create a routine, you can later change its descriptive information.
Each program requires at least one routine. Use a routine to execute your logic.
To create a routine:
1. In the controller organizer, right-click the program that will execute the routine and
choose New Routine.
3. From the Type list, choose the programming language for the routine
4. Choose OK
When a program executes, its main routine executes first. Use the main routine to call (execute)
other routines (subroutines). To call another routine within the program, use a Jump to Subroutine
(JSR) instruction.
Each program requires a main routine. The main routine executes whenever the program
executes.
1. In the controller organizer, right-click the program that will execute the routine and
choose Properties.
4. Choose OK
Logix5000 controllers store data in tags (in contrast to fixed data files that are numerically
addressed). With tags, you can
The controller stores tags as you create them and as they fit into the controller memory. There are
not pre-defined data tables, such as in PLC controllers. Tags of similar data types are not
necessarily grouped together in memory. To group data, use arrays.
The minimum allocation unit within the controller is four bytes.
Name: identifies the data (Tags with different scopes can have the same name.)
Data type: defines the organization of the data, such a bit, integer, or floating-point number
Base A base tag is a tag that actually defines the memory where a data element is
stored. It stores one value at a time.
Alias An alias tag is a tag that references memory defined by another tag. An alias
tag can refer to a base tag or another alias tag.
Alias tags are useful for creating standardized programs that can be duplicated
without having to readdress instructions. By using alias tags, each copy of the
program can reference different base tags.
Consumed A consumed tag is a tag whose data value comes from another controller.
3 4 5
Figure 21: Creating Tags
A tag alias lets you create one tag that represents another tag. This is useful for defining
simplified tag names for elements of structures or arrays.
To define an alias:
4. Click Alias.
5. Choose OK
MODULE 2
To communicate with an I/O module in your system, you add the module to the I/O
Configuration folder of the controller.
When you add the module, you also define a specific configuration for the Module. While the
configuration options vary from module to module, there are some common options that you
typically configure:
Term: Definition:
A communication link between two devices, such as between a controller and an I/O module,
Panel View terminal, or another controller.
Connections are allocations of resources that provide more reliable communications between
devices than Unconnected messages. The number of connections that a single controller can
have is limited.
Connection
You indirectly determine the number of connections the controller uses by configuring the
controller to communicate with other devices in the system. The following types of
communication use connections
• I/O modules
• Produced and consumed tags
• Certain types of Message (MSG) instructions (not all types use a connection)
The RPI specifies the period at which data updates over a connection. For example, an input
module sends data to a controller at the RPI that you assign to the module.
Requested • Typically, you configure an RPI in milliseconds (ms). The range is 0.2 ms (200
Packet microseconds) to 750 ms.
Interval (RPI) • If a Control Net network connects the devices, the RPI reserves a slot in the stream of data
flowing across the ControlNet network. The timing of this slot may not coincide with the
exact value of the RPI, but the Control system guarantees that the data transfers at least as
often as the RPI.
In Logix5000 controllers, I/O values update at a period that you configure via the I/O
configuration folder of the project. The values update asynchronous to the execution of logic. At
the specified interval, the controller updates a value independently from the execution of logic.
Take care to ensure that data memory contains the appropriate values throughout a task’s
execution. You can duplicate or buffer data at the beginning of the scan to provide reference
values for your logic.
Programs within a task access input and output data directly from controller-scoped
memory.
Logic within any task can modify controller-scoped data.
Data and I/O values are asynchronous and can change during the course of a task’s
execution.
An input value referenced at the beginning of a task’s execution can be different when
referenced later.
To prevent an input value from changing during a scan, copy the value to another tag and
use the data from there (buffer the values).
The communication format that you choose determines the data structure for the tags that are
associated with the module. Many I/O modules support different formats. Each format uses a
different data structure. The communication format that you choose also determines:
Ownership
The Logix5000 controller uses connections to transmit I/O data. These connections can be direct
connections or rack-optimized connections.
A direct connection is a real-time, data transfer link between the controller and an I/O module.
The controller maintains and monitors the connection with the I/O module. Any break in the
connection, such as a module fault or the removal of a module while under power, sets fault bits
in the data area associated with the module
For digital I/O modules, you can select rack-optimized communication. A rack-optimized
connection consolidates connection usage between the controller and all the digital I/O modules
in the chassis (or DIN rail). Rather than having individual, direct connections for each I/O
module, there is one connection for the entire chassis (or DIN rail).
Rack-optimized connection
Figure 26: Rack-Optimized Connection
4.3 Ownership
In a Logix5000 system, modules multicast data. This means that multiple devices can receive the
same data at the same time from a single device. When you choose a communication format, you
have to choose whether to establish an owner or listen-only relationship with the module.
The controller that creates the primary configuration and communication connection to a module.
The owner controller writes configuration data and can establish a connection to the module.
An I/O connection where another controller owns/provides the configuration data for the I/O
module. A controller using a listen-only connection only monitors the module. It does not write
configuration data and can only maintain a connection to the I/O module when the owner
controller is actively controlling the I/O module.
Listen-only connection
Figure 28: Listen Only Connection
listen-only
Once an input module has been configured (and owned by a
controller), other controllers can establish a listen-only
connection to that module. These controllers can receive
multicast data while another controller owns the module. If
all owner controllers break their connections to the input
module, all controllers with listen-only connections no
longer receive multicast data.
Be careful when you disable electronic keying. If used incorrectly, this option can lead to
personal injury or death, property damage, or economic loss.
When you configure a module, you specify the slot number for the module. However, it is
possible to place a different module in that slot, either on purpose or accidently. Electronic keying
lets you protect your system against the accidental placement of the wrong module in a slot. The
keying option you choose determines how closely any module in a slot must match the
configuration for that slot.
Outputs respond to the last, non-faulted state of the controlling inputs. To avoid potential injury
and damage to machinery, make sure this does not create unsafe operation. Configure critical I/O
modules to generate a controller major fault when they lose their connections to the controller.
Or, monitor the status of I/O modules.
If the controller loses communication with a module, data from that device does not update.
When this occurs, the logic makes decisions on data that may or may not be correct.
Controller B requires data from controller A. If communication fails between the controllers, then
controller B continues to act on the last data that it received from controller A.
If communication with a device in the I/O configuration of the controller does not occur for 100
ms, the communication times out. If this occurs, you have these options:
You can configure modules to generate a major fault in the controller if they lose their connection
with the controller. This interrupts the execution of logic and executes the Controller Fault
Handler. If the Controller Fault Handler does not clear the fault, then the controller shuts down.
If you do not configure the major fault to occur, you should monitor the module status. If a
module loses its connection to the controller, outputs go to their configured faulted state. The
controller and other I/O modules continue to operate based on old data from the module.
If the connection times out, continue operation without invoking a major fault on the controller.
If communication with a module times out, the controller produces these warnings:
A shows over the I/O configuration folder and over the device (s) that has timed out.
A module fault code is produced, which you can access through:
Module Properties window for the module
GSV instruction
To monitor the health of your connections, use a Get System Value (GSV) instruction to monitor
the MODULE object for either the controller or a specific module:
Each tag uses a structure of data. The structure depends on the specific features of the I/O
module.
The name of the tags is based on the location of the I/O module in the system.
Where: Is:
Location Network location
LOCAL = same chassis or DIN rail as the controller
ADAPTER_NAME= identifies remote communication adapter or bridge module
Slot Slot number of I/O module in its chassis or DIN rail
Type
Type of data
I = input
O = output
C = configuration
S = status
Member
Specific data from the I/O module; depends on what type of data the module can store.
• For a digital module, a Data member usually stores the input or output bit values.
• For an analog module, a Channel member (CH#) usually stores the data for a channel.
Sub Member Specific data related to a Member.
Specific point on a digital I/O module; depends on the size of the I/O module (0-31 for a 32-
Bit
point module)
Table 11: I/O Address Details
With RSLogix 5000 programming software, version 15, you can add 1756 I/O modules to the
Controller Organizer at runtime:
ControlLogix controllers update date asynchronous with the execution of logic. Use the following
flowchart to determine when a producer (controller, input module, or bridge module) will send
data.
If an I/O module supports reconfiguration, you can reconfigure the module via:
Use care when changing the configuration of an I/O module. You could inadvertently cause the
I/O module to operate incorrectly.
To change the configuration of an I/O module via RSLogix 5000 software, highlight the module
in the I/O Configuration tree. Right-click and select Properties.
Data structures allow storing a group of data. Each member can be a different data type. Each I/O
module has its own predefined structure. User can create specialized user defined structures using
any combination of predefined data type and other structures. Structures can be created, edited
and deleted in offline mode. Memory allocation depends on the data types for each member
within the structure. Each member is allocated memory to start on an appropriate byte, INT or
DINT. This makes a more efficient use of memory.
2. Click the right mouse button and select New Data Type.
4.9.3 Arrays
Arrays let you group a set of data (of the same data type) by the same name and to use subscripts
to identify individual elements. An array can have as many as three dimensions.
If the user wants an instruction to access different elements in an array, can use a tag in the
subscript of the array (an indirect address). By changing the value of the tag, you change the
element of the array that your logic references.
2. Click on the Communication on the menu bar and select Configure drivers.
There are two communication protocols available for communicating with the ControlLogix
Controller.
Serial (RS232)
Ethernet
For connecting with the controller through its serial port select the RS232 DF1 devices in the
driver drop down list as shown in the figure
5. Keeps the default setting. Click on auto configure button and press OK.
For connecting with the controller through Ethernet select the Ethernet devices in the driver drop
down list as shown in the figure
Click on RSWho icon and ensure that the controller is accessible through the configured drivers
as shown in the figure.
RSWho
1. Click on the Who Active button in RSLogix5000 as shown in the figure below
Who
Active
2. Click on the Configured driver in section 7.1 and select the target controller
Go online
with the
Controller
Upload
program
from the
Controller
Download
program
into the
Controller
Figure 47: RSWho Window (Continued)
If you want to download or Upload the program or go online with controller press the respective
button as shown in the above figure.
Following steps are required to add a new rung in the online program.
1. Select the routine where you want to add new rung according to your requirement.
2. Now right click on the rung and select add new rung.
3. After clicking add new rung a new rung will be added and it is identified with “e” which
means editable.
New Rung
4. When the new rung is added than go to language element toolbar and add logic
instructions as it is shown in the figure below.
Language
Toolbar
5. Double Click on instruction as it is shown in the figure below. The Tag Browser displays
with the Tag Name, Data Type, and Description. Use it to quickly select the tag to which
you would like to refer. The Tag Browser lists all the tags available in the current scope
6. The figure below shows when the tag is selected from the tag browser.
7. Double Click on the output instruction element as shown in the figure below. The Tag
Browser displays will get open with the Tag Name, Data Type, and Description of the
selected tag. Use it to quickly select the tag to which you would like to refer. The Tag
Browser lists all the tags available in the current scope
8. The figure below shows when the tag is selected from the tag browser
9. After making all the editing go to the Edit toolbar as shown in the figure below and click
Accept Pending Program Edits
Accept
Edits
Error
Window
10. After clicking Accept pending program edits make sure that all the program edits are
correct and no error log in the error window. Than after assuring it click on the tab
Finalize all edits in the program as shown in the figure below.
Finalize
Edits
11. Figure below will appear when you click on the tab Finalize all the edits in the program.
Click Yes the edits you made in your online program will be implemented.
12. A new rung is added in the online program as shown in the figure.
1. Select the rung which you want to edit as shown in the figure below
2. Double click on the rung. Now you can see there are two rungs one is denoted with “r”
which means replace and one is denoted with “I” which means instruction. You make
changes in the “I” rung.
3. Double Click on instruction as it is shown in the figure below. The Tag Browser displays
will get open with the Tag Name, Data Type, and Description of the selected tag. Use it
to quickly select the tag to which you would like to refer. The Tag Browser lists all the
tags available in the current scope.
4. Now After making all the editing click Accept Pending Program Edits. After clicking
Accept pending program edits make sure that all the program edits are right and no error
log in the error window. After assuring it click on the tab Finalize all edits. Following
window will appear when you click on the tab Finalize all the edits in the program. After
clicking Yes the edits you made in our online program will be implemented.
1. Select the tag which you want to monitor as shown in the figure below
2. Right click on the tag and select Monitor as shown in the figure.
3. Below window will open which shows the current value of the Tag.
Current
Value
Create a new Project file and navigate through the Project Properties
MODULE 3
Controller
Tag
3. Select the tag which you want to be forced, as it is shown in the figure below a tag has
been selected and its force mask value is empty.
Force Mask
Value
4. Click on the force mask value tab and enter the value which you want to be forced on the
desire tag. As you can see the color of forces in the online toolbar is turned to red. This
means forces have been installed but not enabled.
Force
Installed
Force
Figure 70: Forcing IO Tag Installed
Value
5. Now forces have been installed but not enabled yet. So go to online toolbar and click
forces to open a drop down menu. Click enables all IO forces which will enable all the IO
whose forces have been installed and afterwards whenever you force any IO it will be
forced directly.
Forced
Value
Figure 71: Forcing IO Tag (Continued)
6. Figure below shows the color of forces tab change after enabling all IO forces
Forced Tab
Color
2. Open the File menu and go to print. A sub menu will open select Controller Properties
from this sub menu as shown in the figure below.
1. Go to the Tasks and select routine from any program. As it is shown in the figure below.
2. Open the File menu and go to print. A sub menu will open select Routine from this sub
menu as shown in the figure below.
2. Open the File menu and go to print. A sub menu will open select Data Type from this sub
menu as shown in the figure below.
1. Double click on the controller tags and open the monitor tags window as shown in the
figure.
2. Open the File menu and go to print. A sub menu will open select Tags from this sub
menu as shown in the figure below.
10. Get System Value (GSV) & Set System Value (SSV)
Instructions
The GSV/SSV instructions get and set controller system data that is stored in objects. The
controller stores system data in objects. When enabled, the GSV instruction retrieves the
specified information and places it in the destination. When enabled, the SSV instruction sets the
specified attribute with data from the source. When you enter a GSV/SSV instruction, the
programming software displays the valid object classes, object names, and attribute names for
each instruction. For the GSV instruction, you can get values for all the available attributes. For
the SSV instruction, the software displays only those attributes are allowed to set (SSV).
DANGER
Example1:
This example gets fault information from the I/O module disc_in_2 and places the data in a user-
defined structure disc_in_2_info.
Example2:
This example gets status information about program discrete and places the data in a user-defined
structure discrete_info.
Example3:
This example gets status information about task IO_test and places the data in a user-defined
structure io_test_info.
Example4:
The following example uses the SSV instruction to enable or disable a program. You could also
use this method to enable or disable an I/O module.
Based on the status of SW.1, place the appropriate value in the disableflag attribute of program
discrete.
Fault Condition
At the top of the Trend Chart, the trend control bar is used to start and stop data sampling in the
controller, view trending errors, save or delete captured trend logs, or view a specific capture.
The control bar also provides information about the state of the trend in the controller, as well as
data collection and sampling information. A typical chart display with the default settings and at
least one tag configured also includes a Line Legend, Chart Title, Display Pen Values field, X
and Y axis scales, and scroll buttons.
Trend
Toolbar
1. Select the tag which you want to monitor as shown in the figure below
2. The following window will open the trend of the selected tag.
3. When you close the trend a message will prompt as shown in the following figure to
create trends. Click yes if you want to save the trend or NO if you don’t want.
4. After clicking Yes the following window prompt. Where you add the Name of the trend,
Description about the trend and sample period of the trend.
5. After clicking next the following window will prompt and you can add new tags in a
trend. The trend of new tag will be shown on the same trend sheet but with a different
color pen. By clicking on finish we can save the trend.
6. The Trend chart will save in the Trend folder of Controller organization tree as shown in
the figure.
7. If you want to save the trend data on the hard drive of the PC stop the trend and click on
the Log button on the Trend toolbar as shown in the figure.
Log Trend
button
8. Select “Save Trend log as”, a window will popup. Select the folder where you want to
save the trend data and type the file name as shown in the figure
9. If you want to import the trend data from the external file into RSlogix500, right click on
the trend folder and select “open trend log” as shown in the figure
10. A window will open, select the file and press open button as shown in the figure
MODULE 4
Being a modular system ControlLogix system requires a 1756 I/O chassis to contain the various
modules. Any module can be placed in any slot. The backplane provides a high-speed
communication path between modules. Multiple controller modules on the backplane can pass
messages between one another. With multiple communication interface modules on the
backplane, a message can be sent from across a link into a port on one module, routed across the
backplane and out another module’s port, and sent across another link to its ultimate destination.
The ControlLogix chassis are available in five different sizes 4, 7, 10, 13, 17 and slot number
beginning with zero.
For installing and maintenance of I/O Chassis following precautions should be observed.
Power supply can be directly mounted on the left end of the ControlLogix chassis, where it plugs
directly into the backplane. The power supply provides power for all modules installed in the
chassis.
For installing and maintenance of power supply following precautions should be observed.
Use the figure below to connect equipment protective earth ground from the power
supply to the chassis. Tighten the nut on the equipment protective earth ground terminal
stud to a torque of 12 inch pounds. (1.4 Nm)
Follow these steps for each wire (i.e., high side, low side and ground) to connect power.
ControlLogix power supplies have a green LED status indicator that remains ON during normal
operation.
If the indicator:
Turn ON:
a. Verify that the module leads in the system are within the output rating of the power
supply.
b. Power down the power supply.
c. Reinstall the power supply in the chassis.
Turns OFF:
Certain connections require shielded cables to help reduce the effects of electrical noise coupling.
Ground each shield at one end only. A shield grounded at both ends forms a ground loop which
could cause faulty PLC operation. Ground each shield at the end specified in the appropriate
publication for the product. Avoid breaking shields at junction boxes. Many types of connectors
for shielded conductors are available from various manufacturers. If you do break a shield at a
junction box:
You can install or remove a ControlLogix controller while chassis power is on and the
system is operating. If you remove the controller, all the devices owned by the controller
go to their configured fault state. When you install a ControlLogix controller, you can
place the controller in any slot. You can also place multiple controllers in the
same chassis
You can install or remove a ControlLogix controller while chassis power is on and the
system is operating.
Align the circuit board with the top and bottom guides in the chassis.
Slide the module into the chassis. The controller is fully installed when it is flush with the
power supply or other installed modules and the top and bottom latches are engaged.
1756 PBR2 battery is used for backup of the program in the controller.
For installing and maintenance of controller battery following precautions should be observed.
Use the following procedure for installing and replacing lithium batteries:
1. Maintain backplane power to the equipment. Loosen any mounting screws and open the
battery compartment.
2. Before removing the old battery, check for signs of damage. If the battery case is broken
4. Read the caution label. Locate the two date labels supplied with the new battery. Write
the current date on both labels. Place one date label on the front of the battery
compartment. If the battery has a space for a date, write directly on the battery; otherwise
place the second date label on the battery.
6. Check that the battery low indicator is off. If the battery low indicator is off, continue
with step 7. If the battery low indicator is on, check the battery connection and the
battery. If the battery low indicator remains on, contact your local Rockwell
Automation/Allen-Bradley representative.
7. If the battery low indicator is off and the battery is connected properly, place the battery
in the battery compartment. Replace the cover to the battery compartment and secure any
mounting screws.
When the battery is about 95% discharged, the controller gives these low-battery warnings:
To prevent possible battery leakage, even if the BAT LED is off, replace a battery according to
this schedule.
To estimate how long a 1756-PBR2 battery will support controller memory, perform this
procedure:
2. Determine the weekly percentage of time that the controller is turned on.
3. Determine the estimated worst-case battery life before and after the BAT LED turns on.
4. For each year of battery life, decrease the time before the BAT LED turns on by the
percentage that is shown in the table.
Control Bus connector - The backplane connector interface for the ControlLogix system
connects the module to the Control Bus backplane.
Connector’s pins - Input/output, power and grounding connections are made to the
module through these pins with the use of an RTB
Locking tab - The locking tab anchors the RTB cable on the module, maintaining wiring
connections.
Slots for keying - Mechanically keys the RTB to prevent inadvertently making the
wrong wire connections to your module.
Status indicators - Indicators display the status of communication, module health and
input/output devices. Use these indicators to help in troubleshooting.
Top and bottom guides - Guides provide assistance in seating the RTB cable onto the
module
I/O status - This yellow display indicates the ON/OFF state of the field device.
Module status - This bi-colored LED for module "OK" (red/green) display indicates the
module’s communication status.
During power up, an indicator test is done and the following occurs:
"OK" indicator turns red for 1 second and then turns to flashing green if it has passed the
self-test.
I/O status indicators turn ON for a maximum of 2 seconds and then turn OFF.
Control Bus connector - The backplane connector interface for the ControlLogix system
connects the module to the Control Bus backplane.
Connectors pins - Input/output, power and grounding connections are made to the
module through these pins with the use of an RTB
Locking tab - The locking tab anchors the RTB cable on the module, maintaining wiring
connections.
Slots for keying - Mechanically keys the RTB to prevent inadvertently making the
wrong wire connections to your module.
Status indicators - Indicators display the status of communication, module health and
input/output devices. Use these indicators to help in troubleshooting.
Top and bottom guides - Guides provide assistance in seating the RTB cable onto the
module
I/O status - This yellow display indicates the ON/OFF state of the field device.
Module status - This bi-colored LED for module "OK" (red/green) display indicates the
module’s communication status.
During power up, an indicator test is done and the following occurs:
The "OK" indicator turns red for 1 second and then turns to flashing green if it has passed
the self-test.
The I/O status indicators turn ON for a maximum of 2 seconds and then turn OFF.
Control Bus connector - The backplane connector interface for the ControlLogix system
connects the module to the Control Bus backplane.
Connector’s pins - Input/output, power and grounding connections are made to the
module through these pins with the use of an RTB
Locking tab - The locking tab anchors the RTB cable on the module, maintaining wiring
connections.
Slots for keying - Mechanically keys the RTB to prevent inadvertently making the
wrong wire connections to your module.
Status indicators - Indicators display the status of communication, module health and
input/output devices. Use these indicators to help in troubleshooting.
Top and bottom guides - Guides provide assistance in seating the RTB cable onto the
module
Control Bus connector - The backplane connector interface for the ControlLogix system
connects the module to the Control Bus backplane.
Connector’s pins - Input/output, power and grounding connections are made to the
module through these pins with the use of an RTB
Locking tab - The locking tab anchors the RTB cable on the module, maintaining wiring
connections.
Slots for keying - Mechanically keys the RTB to prevent inadvertently making the
wrong wire connections to your module.
Status indicators - Indicators display the status of communication, module health and
input/output devices. Use these indicators to help in troubleshooting.
Top and bottom guides - Guides provide assistance in seating the RTB cable onto the
module
The ControlLogix system supports the use of remote I/O via these networks:
EtherNet/IP
ControlNet
DeviceNet
Universal remote I/O
In this section we discuss the troubleshooting of the Ethernet and ControlNet communication
modules, because the remote IO connected with the controller through these communication
cards.
Control of real time I/O data (also known as “implicit messaging”) in conjunction with a Logix
5550 controller. The Ethernet module may serve as an adaptor, interfacing the I/O modules to the
network, or as a scanner, sending and receiving data between the controller and the network. The
1756-ENBT/E module supports both Rack Optimized and Direct Connections. 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. A rack optimized connection is a grouping of data
from more than one I/O module into a single block of data sent over a single connection.
Check the LED indicators to determine if the power supply and module are operating properly
The following table describes module health (OK) indicator displays, module status, and
recommended action:
This table describes the transmit (TXD) and receive (RXD) indicator display:
The ControlNet channel status indicators appear in one of the following states:
The Module Status Indicator LED and Module Status Display provide diagnostic information as
summarized in the following table.
ROM
Flash update is in progress. None required.
UPDT
OK Normal operation
None required
None (temporary
The module is receiving too
condition).
much network traffic and
If this happens frequently,
BW >MAX connections are timing out.
add another 1756-CNB or
The network bandwidth has
GREEN 1756-CNBR and split the
been exceeded.
traffic between them.
ControlNet network
CNFG ERR Recheck configuration.
configuration error.
FLASHING
GREEN Re-check your network
Network cabling error or no
cabling and make sure
NETERR other active nodes on
another node on the
network.
network is active (online).
Digital Input
Digital Output
Analog Input
Analog Output
Inputs and Outputs available on the workstation will be tied to the program and then will be used
to simulate the process.
13.2 Starting Up
Open up a new RSLogix 5000 Window and define hardware in that according to IO modules
available in the workstation.
To simplify the process, let us use some very simple tag names like DI1, DI2, DI3, DO1, DO2,
DO3, AI1, AI2, AO1 and AO2 etc and define these variables in the Controller Tags.
For convenience and easy to understand approach, it is better to write all the logic in the main
routine.
We will split our programming in the main routine in three major portions (at later stages these
portions will exist in different routines in the program). In first portion, data from hardware
addresses will be copied to Controller tags. In second portion, main logic (or program will be
executed and in third portion, output values will be copied to hardware addresses to make outputs
visible on the workstation.
13.6 Implementation
Let us discuss some common plant philosophy known to all the students in the classroom and
then implement it, in the mean time we also discuss some common errors and mistakes expected
to occur during Implementation and how to diagnose and Trouble shoot those errors.