Professional Documents
Culture Documents
Training Manual
Training Manual
TABLE OF CONTENTS
MODULE 1........................................................................................................................ 10
1.
INTRODUCTION................................................................................................... 11
2.
3.
MODULE 2........................................................................................................................ 38
4.
Training Manual
6.
7.
MODULE 3........................................................................................................................ 78
8.
9.
Training Manual
10.
GET SYSTEM VALUE (GSV) & SET SYSTEM VALUE (SSV)
INSTRUCTIONS ............................................................................................................ 88
10.1 GSV/SSV INSTRUCTION ATTRIBUTES ............................................................... 89
10.2 GSV/SSV INSTRUCTION PROGRAMMING........................................................... 90
10.2.1
Get Fault Information ............................................................................... 90
10.3 GSV/SSV INSTRUCTION FAULT CODES ............................................................. 93
11.
13.6
Training Manual
Training Manual
LIST OF FIGURES:
Figure 1: ControlLogix System ........................................................................................ 11
Figure 2: ControlLogix System Overview ........................................................................ 12
Figure 3: Local Area Connection ...................................................................................... 14
Figure 4: Local Area Connection Properties .................................................................... 15
Figure 5: Internet Protocol (TCP/IP) Properties ............................................................... 15
Figure 6: New Controller .................................................................................................. 16
Figure 7: Name of the Controller ...................................................................................... 17
Figure 8: Task Folder ........................................................................................................ 20
Figure 9: Control Properties.............................................................................................. 22
Figure 10: Control Property Window ............................................................................... 23
Figure 11: Control Application ......................................................................................... 25
Figure 12: Tasks, Programs and Routines ........................................................................ 26
Figure 13: Execution order ............................................................................................... 27
Figure 14: New Task ......................................................................................................... 28
Figure 15: New Task Window .......................................................................................... 28
Figure 16: Main Task ........................................................................................................ 29
Figure 17: New Program Window .................................................................................... 30
Figure 18: Creating a Routine ........................................................................................... 31
Figure 19: New Routine Window ..................................................................................... 32
Figure 20: Program Properties .......................................................................................... 33
Figure 21: Creating Tags .................................................................................................. 36
Figure 22: Defining Alias ................................................................................................. 37
Figure 23: New Tag Window ........................................................................................... 37
Figure 24: Configuring I/O Module .................................................................................. 39
Figure 25: New Module Window ..................................................................................... 42
Figure 26: Rack-Optimized Connection ........................................................................... 42
Figure 27: Owner Connection Window ............................................................................ 43
Figure 28: Listen Only Connection................................................................................... 44
Figure 29: Configuring a Major Fault To Occur .............................................................. 48
Figure 30: Health Monitoring Window ............................................................................ 48
Figure 31: Addressing I/O Data ........................................................................................ 50
Figure 32: Data Flowchart ................................................................................................ 53
Figure 33: Reconfigure an I/O Module ............................................................................. 54
Figure 34: Creating Structure............................................................................................ 56
Figure 35: Data Type Window ......................................................................................... 57
Figure 36: Indirect Addressing ......................................................................................... 59
Figure 37: Launch RSLinx from the Rockwell Softwares .............................................. 60
Figure 38: Launch RSLinx from the Rockwell Software ................................................. 61
Figure 39: RSLinx Serial Driver Configuration ............................................................... 61
Figure 40: RSLinx Serial Driver Configuration (Continued) ........................................... 62
Training Manual
Training Manual
Training Manual
LIST OF TABLES:
Table 1: Saving Changes .................................................................................................. 18
Table 2: Tasks of a controller ........................................................................................... 19
Table 3: Tasks for the Controller ...................................................................................... 21
Table 4: Types of Tags ..................................................................................................... 35
Table 5: Data Types .......................................................................................................... 35
Table 6: Request Packet Interval ...................................................................................... 40
Table 7: Electronic keying ................................................................................................ 45
Table 8: Electronic keying (Continued) ........................................................................... 46
Table 9: Electronic Keying Configuration ....................................................................... 46
Table 10: Loss of Connection ........................................................................................... 47
Table 11: I/O Address Details .......................................................................................... 51
Table 12: Arrays ............................................................................................................... 58
Table 13: GSV/SSV Instruction attributes ....................................................................... 89
Table 14: GSV/SSV Instruction Fault Code ..................................................................... 93
Table 15: Controller LEDs Status Indicator .................................................................. 109
Table 16: Controller BAT LED Indicator ...................................................................... 110
Table 17: Batteries Replacement Date ........................................................................... 112
Table 18: Worst-case Estimates of Battery Life ............................................................. 113
Table 19: DC Input Module Status Indicators Description ............................................ 116
Table 20: DC Output Module Status Indicators Description.......................................... 119
Table 21: Analog Input Module Status Indicators Description ...................................... 121
Table 22: Analog Output Module Status Indicators Description ................................... 123
Table 23: Ethernet Module Status Indicators Description .............................................. 126
Table 24: Ethernet Module Status Indicators Description (Continued) ......................... 127
Table 25: ControlNet Module Status Indicators Description ......................................... 131
Table 26: ControlNet Module Status Indicators & Display Diagnostics ....................... 135
Training Manual
MODULE 1
10
Training Manual
1. Introduction
This course provides students with the necessary resources and hands-on practice to efficiently
troubleshoot a ControlLogix. It builds upon the students fundamental knowledge of common
controller terms and operation, the students ability to identify and create fundamental
RSLogix 5000 project components and the students experience interpreting basic ladder logic.
This course adds to the students 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.
11
Training Manual
ControlLogix Controllers
ControlLogix Communication Modules
ControlLogix I/O Modules
ControlLogix Power Supplies
ControlLogix Chassis
12
2.1
Training Manual
ControlLogix Controller
13
Training Manual
14
Training Manual
6. Click on the properties Tab and select Internet protocol (TCP\IP) as shown in the figure.
15
Training Manual
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.
16
Training Manual
6. Select the type of chassis (number of slots) that contains the controller.
7. Select or type the slot number where the controller is installed
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.
17
Training Manual
Do this:
18
Training Manual
Will:
Continuously execute your logic (You can only
have one Continuous task.)
interrupt the continuous task
execute logic one time
return control to the continuous task
(You can have more than one periodic
task.)
Table 2: Tasks of a controller
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.
19
Training Manual
If you execute:
Then:
Detailed steps:
20
Training Manual
name_of_task.
B. Right-click name_of_program
and select
Routine.
C. Type:
name_of_main_routine
description (optional)
D. From the Type drop-down list,
select the Programming language for
the routine.
E. Click OK.
F. Right-click name_of_program
and select Properties.
G. Click the Configuration tab.
H. From the Main drop-down list,
select
name_of_main_routine
I. Click OK.
J. To add additional routines
(subroutines) To the program repeat
steps B. to E
21
Training Manual
22
Training Manual
DF1 point-to-point
23
DF1 slave
DF1 master
Training Manual
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
File view: information about the project file.
24
Training Manual
25
Training Manual
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:
26
Training Manual
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 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.
27
Training Manual
28
Training Manual
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 programs descriptive information if you wish.
29
Training Manual
30
Training Manual
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.
31
Training Manual
32
Training Manual
33
Training Manual
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.
34
Training Manual
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.
Description
1-bit Boolean
SINT
INT
DINT
REAL
1-byte integer
2-byte integer
4-byte integer
4-byte floating-point
number
Range
0 = off
1 = on
-128 to 127
-32,768 to 32,767
-2,147,483,648 to 2,147,483,647
-3.402823E38 to -1.1754944E38 (negative values)
and
0
and
35
Training Manual
4
Figure 21: Creating Tags
36
Training Manual
37
Training Manual
MODULE 2
38
Training Manual
39
Training Manual
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
Packet
Interval (RPI)
Typically, you configure an RPI in milliseconds (ms). The range is 0.2 ms (200
microseconds) to 750 ms.
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.
Table 6: Request Packet Interval
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.
40
Training Manual
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 tasks
execution.
An input value referenced at the beginning of a tasks 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).
Ownership
41
Training Manual
Rack-optimized connection
Figure 26: Rack-Optimized Connection
42
Training Manual
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.
43
Training Manual
Listen-only connection
44
Training Manual
input module
output
module
Controlling:
input modules
And another
controller:
does not own
the module
owns the
module
maintain communication
with the module if it loses
communication with the
other controller
stop communication with
the module if it loses
communication with the
other controller
does not own the module
45
output
modules
owner
listen-only
Training Manual
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.
If:
Then select:
all information must match:
Exact Match
type
catalog number
vendor
major and minor revision
number
all information except the minor Compatible Module
revision number
no information must match
Disable Keying
Table 9: Electronic Keying Configuration
46
Training Manual
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:
If you want the controller to:
Then:
continue operating
47
Training Manual
If the connection times out, continue operation without invoking a major fault on the controller.
48
Training Manual
If communication with a module times out, the controller produces these warnings:
The I/O LED on the front of the controller flashes green.
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:
49
Training Manual
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.
50
Training Manual
:Slot
:Type
.Member
.SubMember
.Bit
Where:
Location
Is:
Network location
LOCAL = same chassis or DIN rail as the controller
ADAPTER_NAME= identifies remote communication adapter or bridge module
Slot number of I/O module in its chassis or DIN rail
Slot
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.
Sub Member
Bit
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.
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 32point module)
Table 11: I/O Address Details
51
Training Manual
52
Training Manual
53
Training Manual
Use care when changing the configuration of an I/O module. You could inadvertently cause the
I/O module to operate incorrectly.
4.8.1
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.
54
Training Manual
55
Training Manual
56
Training Manual
57
Training Manual
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.
58
Training Manual
59
Training Manual
60
Training Manual
2. Click on the Communication on the menu bar and select Configure drivers.
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
61
Training Manual
62
Training Manual
For connecting with the controller through Ethernet select the Ethernet devices in the driver drop
down list as shown in the figure
63
Training Manual
RSWho
64
Training Manual
Who
Active
Go online
with the
Controller
Upload
program
from the
Controller
Download
program
into the
Controller
65
Training Manual
66
Training Manual
2. Now right click on the rung and select add new rung.
New Rung
67
Training Manual
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
Instruction
Element
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
68
Training Manual
6. The figure below shows when the tag is selected from the tag browser.
69
Training Manual
8. The figure below shows when the tag is selected from the tag browser
Accept
Edits
Error
Window
70
Training Manual
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
71
Training Manual
12. A new rung is added in the online program as shown in the figure.
72
Training Manual
73
Training Manual
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.
74
Training Manual
75
Training Manual
3. Below window will open which shows the current value of the Tag.
Current
Value
76
Training Manual
77
Training Manual
MODULE 3
78
Training Manual
Controller
Tag
79
Training Manual
Force Mask
Value
Figure 69: Controller Tag Window (Continued)
80
Training Manual
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
Installed
Value
Forced
Value
Figure 71: Forcing IO Tag (Continued)
81
Training Manual
6. Figure below shows the color of forces tab change after enabling all IO forces
Forced Tab
Color
82
Training Manual
83
Training Manual
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.
84
Training Manual
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.
85
Training Manual
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.
86
Training Manual
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.
87
Training Manual
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
Use the GSV and SSV instructions carefully. Making changes to
objects may cause unexpected controller operation or injury to
personnel. You must test and confirm that the instructions dont
change data that you dont want them to change. The GSV and SSV
instructions write or read past a member into other members of a tag.
If the tag is too small, the instructions dont write or read the data.
They log a minor fault instead.
88
Training Manual
Type
Attribute name
Destination (GSV)
Source (SSV)
Format
name
name
name
SINT
INT
DINT
REAL
Structure
SINT
INT
DINT
REAL
Structure
tag
tag
Description
name of object class
name of specific
object
attribute of object data
type depends on the
attribute you select
Destination of
attribute Data
89
Training Manual
90
Training Manual
Example2:
This example gets status information about program discrete and places the data in a user-defined
structure discrete_info.
91
Training Manual
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.
92
Training Manual
Fault Code
5
6
6
6
7
93
Training Manual
Trend
Toolbar
94
Training Manual
2. The following window will open the trend of the selected tag.
95
Training Manual
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.
96
Training Manual
6. The Trend chart will save in the Trend folder of Controller organization tree as shown in
the figure.
Log Trend
button
97
Training Manual
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
98
Training Manual
10. A window will open, select the file and press open button as shown in the figure
99
Training Manual
MODULE 4
100
Training Manual
101
Training Manual
102
Training Manual
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)
103
Training Manual
104
Training Manual
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:
105
Training Manual
106
Training Manual
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.
107
Training Manual
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.
108
Training Manual
109
Training Manual
110
Training Manual
111
Training Manual
To prevent possible battery leakage, even if the BAT LED is off, replace a battery according to
this schedule.
112
Training Manual
113
Training Manual
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
114
Training Manual
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 modules communication status.
"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.
115
Training Manual
116
Training Manual
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
117
Training Manual
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 modules communication status.
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.
118
Training Manual
119
Training Manual
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
120
Training Manual
121
Training Manual
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
122
Training Manual
123
Training Manual
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.
124
Training Manual
125
Training Manual
126
Training Manual
This table describes the transmit (TXD) and receive (RXD) indicator display:
127
Training Manual
128
Training Manual
129
Training Manual
130
Training Manual
131
Training Manual
Off
Display
Cause
Action
1. Check the power supply.
2. Check the cable
connectors.
3. Make sure the module is
firmly seated in the
chassis.
4. If the indicator remains
off, replace the module.
1. (Optional, see page 12.)
Turn chassis power supply
off.
2. Remove the module
from the chassis.
3.Set the network address
switches to a unique
address (01-99, or 01-98 if
redundant control)
4. Install the module in the
chassis.
5. If off, turn chassis
power supply on.
None
Msg scrolls(1)
BPA# ERR
BPRX ERR
Red
132
LED
Training Manual
Display
Cause
Action
DUPL NODE
1. (For redundant
systems only.) Wait 10
seconds; if the condition
persists, perform the
following steps:
2. (Optional, see page
12.)
Turn chassis power
supply off.
3. Remove the module
from the chassis.
4. Set the network
address switches to a
unique address (01-99).
5. Install the module in
the chassis.
6. If off, turn chassis
power supply on.
RACK ERR
STOP
BOOT
Flashing Red
133
LED
Training Manual
Display
Cause
Action
ROM
UPDT
None required.
SNGL KPR!
OK
Normal operation
None required
INIT
BW >MAX
None (temporary
condition).
If this happens frequently,
add another 1756-CNB or
1756-CNBR and split the
traffic between them.
CMPT(2)
None required.
DSNP(2)
GREEN
134
LED
Training Manual
Display
Cause
PwDS(2)
PwQg(2)
PwQS(2)
Action
SWERR
CNFG ERR
ControlNet network
configuration error.
Recheck configuration.
NETERR
PwNS(2)
FLASHING
GREEN
135
Training Manual
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.
136
Training Manual
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.
137