Professional Documents
Culture Documents
Essentials with
RSLogix5000
Software
Rockwell Automation (SEA)
Student Manual
properly using, calibrating, operating, monitoring and maintaining all Products consistent with all Rockwell
Automation or third--party provided instructions, warnings, recommendations and documentation;
ensuring that only properly trained personnel use, operate and maintain the Products at all times;
staying informed of all Product updates and alerts and implementing all updates and fixes; and
all other factors affecting the Products that are outside of the direct control of Rockwell Automation.
Reproduction of the contents of the Documentation, in whole or in part, without written permission of Rockwell
Automation is prohibited.
Throughout this manual we use the following notes to make you aware of safety considerations:
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.
Comment Form
Email: ratps@ra.rockwell.com
or Fax:
440.646.4425
Page 1 of
Date:
Contact Information:
Name:
Company and Location:
Phone:
Email:
Page 2
Table of Contents
Lessons
Identifying Logix5000 System Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
What You Will Learn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Why These Skills Are Important . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Logix5000 Control Disciplines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Example: Bottling Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ControlLogix Platform and Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ControlLogix Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ControlLogix Backplane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ControlLogix Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Safety Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ControlLogix I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ControlLogix Communications Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ControlLogix Platform Modularity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Example: Platform Modularity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FlexLogix Platform and Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DIN Rail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FlexLogix Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FlexLogix I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FlexLogix Communications Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CompactLogix Platform and Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CompactLogix Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CompactLogix I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CompactLogix Communications Modules/Converters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DriveLogix Platform and Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SoftLogix Platform and Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1- 1
1--1
1--1
1--1
1--2
1--2
1--3
1--3
1--4
1--5
1--5
1--6
1--6
1--7
1--7
1--8
1--8
1--8
1--9
1--9
1--10
1--10
1--11
1--11
1--12
1--12
1--15
1--17
1--17
1--19
1--20
1--21
2- 1
2--1
2--1
2--1
ii
Table of Contents
2--1
2--1
2--2
2--2
2--4
2--6
2--8
2--9
2--11
2--13
2--14
2--14
3- 1
3--1
3--1
3--1
3--1
3--1
3--2
3--3
3--3
3--5
3- 7
3--7
3--7
3--8
3--9
3--10
3--10
3--10
3--10
4- 1
4--1
4--1
4--1
4--1
4--3
4--4
4--5
Table of Contents
iii
4--6
4--7
4--8
4- 9
4--9
4--10
4--10
4--11
4--12
4--12
4--13
4--13
5- 1
5--1
5--1
5--1
5--1
5--2
5--3
5--3
5--3
5--4
5--5
5--5
5--5
5--6
5--6
5--7
5--8
5--8
5--8
5--9
5--10
5--11
5--12
5--12
5--12
5--13
5--14
5--15
5--16
iv
Table of Contents
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exercise B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5--18
5--18
5--19
6- 1
6--1
6--1
6--1
6--1
6--2
6--3
6--4
6--5
6--5
6--5
6--5
6--6
6--7
6--7
6- 9
6--9
6--11
6--11
6--11
6--12
6--13
6--14
6--14
6--15
6--15
7- 1
7--1
7--1
7--1
7--1
7--1
7--2
7--2
7--3
7--3
7--3
7--4
Table of Contents
7--4
7--4
7--5
7--5
7- 7
7--7
7--11
7--12
7--12
8- 1
8--1
8--1
8--1
8--1
8--1
8--2
8--2
8--3
8--3
8--3
8--4
8--4
8--5
8--6
8- 7
8--7
8--8
8--10
8--10
9- 1
9--1
9--1
9--1
9--1
9--2
9--2
9--3
9--5
vi
Table of Contents
9- 7
9--7
9--9
9--10
9--10
10--1
10--1
10--1
10--1
10--2
10--3
10--3
10--4
10--5
10--6
10--7
10--7
10--7
10--8
10--8
10--9
10--10
10--17
10--21
10--22
11--1
11--1
11--1
11--2
11--2
11--2
11--3
11--4
11--5
11--5
11--6
11--7
11--7
Table of Contents
vii
11--7
11--8
11--8
11--8
11--9
11--10
11--15
11--19
11--20
11--21
12--1
12--1
12--1
12--1
12--2
12--2
12--3
12--3
12--3
12--4
12--5
12--5
12--6
12--7
12--9
12--10
12--10
13--1
13--1
13--1
13--1
13--2
13--2
13--3
13--5
viii
Table of Contents
Exercise: Forcing I/O and Toggling Bits in RSLogix 5000 Software . . . . . . . . . . . . 13- 7
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13--7
13--9
13--10
13--10
14--1
14--1
14--1
14--1
14--2
14--2
14--3
14--3
14--3
14--3
14--4
14--5
14--5
14--5
14--6
14--7
14--9
14--10
14--10
14--11
14--12
14--13
14--14
14--14
14--14
14--15
Appendix
I/O Wiring Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A- 1
Slot 0 -- 1756-OB16D Digital Output Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Slot 2 -- 1756-IB16D Digital Input Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Slot 4 -- 1756-OB16D Output Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Slot 7 -- 1756-OF6VI Analog Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Slot 8 -- 1756-IF6VI Analog Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A--1
A--2
A--3
A--4
A--5
Table of Contents
ix
B--2
Node Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C- 1
Table of Contents
Lesson
Logix5000 System
Logix Control Engine: The operating system common to all
Logix5000 controllers. It is avaialable in several platforms or
physical formats:
ControlLogixr: High-performance, multi-controller system in a
modular chassis format.
FlexLogixt: System for distributed control (i.e., control
platform is located at or close to the process/machine).
CompactLogixt: Small modular system for small stand-alone to
medium-sized connected systems.
ControlLogix
System
DriveLogix System
FlexLogix
System
CompactLogix
System
1--2
Tip "
Because all Logix5000 platforms have the same control engine, they
are all programmed in a similar manner using the same software.
Logix5000 Control Disciplines
1--3
Chassis
Controllers
ControlLogix Chassis
Inform students that not all Logix5000
platforms have a chassis. SoftLogix
platform has a virtual chassis rather
than a hardware chassis and the
FlexLogix platform sits on a DIN rail.
Tip "
Rev. February 2007
1--4
7-slot
10-slot
13-slot
17-slot
Slots
ControlLogix Backplane
The ControlLogix backplane, or ControlBust backplane, is a
printed circuit board at the back of the chassis that provides electrical
interconnection between modules:
Point out that this backplane has seven
module connectors.
Module
Connectors
Backplane
1--5
ControlLogix Controller
The ControlLogix controller is a 32-bit controller that combines
logic and data in modular memory:
Locking Tab
Backplane
Connecter
"
LEDs
Keyswitch
Battery
Door
Battery Label
Labels
RS-232 Serial Port
Locking Tab
1--6
Tip "
Tip "
EtherNet/IPt
1756-ENBT
ControlNett
DeviceNett
1756-DNB
1756-DHRIO
1--7
Tip "
Note that a remote chassis may contain
a controller, but it does not require one.
It requires a communications module to
connect to the network.
In the example graphic, one chassis
(top) contains controllers, while the other
chassis does not.
ControlLogix Chassis
DeviceNet Network
EtherNet/IP Network
ControlLogix Chassis
ControlNet
Network
CompactBlock
I/O
PLC-5r System
RediSTATIONt
Tip "
PanelViewt Plus
Terminal
1--8
Tip "
Communications Card
Controller
I/O System
DIN Rail
DIN Rail
If available, show a DIN rail
and how components slide on and off.
Tip "
DIN rails are devices that provide convenient and simple mounting
of components for easy access.
A DIN rail allows a FlexLogix controller and I/O to be placed in a
close proximity to the process or machine.
FlexLogix Controller
The main components of a FlexLogix controller are shown in the
following graphic:
24 V Power
8 Status and
Diagnostic
LEDs
RS-232 Port
Battery Backup
Three-Position Keyswitch
FlexBus Local 1
Connector (For Up to
8 Local FLEX I/O
Modules)
Rev. February 2007
CM3sb56r
1--9
Bank 1
Bank 2
Tip "
RS-232 Port
Two Communications
Daughtercard Slots
Rev. February 2007
1--10
Communications Module
Power Supply
Controller
Tip "
Tip "
CompactLogix Controller
Point out that the CompactLogix
controller is approximately 60% of the
size of a ControlLogix controller or an
SLC 500 processor.
Diagnostic
LEDs
RS-232 Port
1--11
Status Indicators
Module
Door
Communications Module/Card
EtherNet/IP
DeviceNet
DH-485
1761-NET-AIC Converter
1--12
Tip "
DriveLogix Controller
SoftLogix Platform
Virtual Chassis
Module
VersaViewr
Industrial
Computer
Slot Number
Tip "
1--13
1--14
1--15
1--16
10. What are the openings in a chassis or on a DIN rail that hold
individual modules?
11. Detach the RTB and remove a digital I/O module from the
chassis.
12. Name the devices that provide interconnection between I/O
modules and processes/machines.
1--17
13. How does a controller retain its memory when the power supply
is turned off?
Exercise B
1--18
3. Place a check in the box after you locate each of the following
controller components:
- Keyswitch
- Keyswitch positions
- Controller LEDs
- Battery (or battery port, if empty)
- Battery date label
- Serial cable and serial port
- Top and bottom locking clips
4. Using the module faceplates and the labels inside the module
doors, identify the name and the part number of each workstation
module in the provided spaces:
0
A. Slot 0:
B. Slot 1:
C. Slot 2:
D. Slot 3:
E. Slot 4:
1--19
G. Slot 6:
H. Slot 7:
I. Slot 8:
J. Slot 9:
1--20
Answers
Exercise A
1. The ControlLogix platform is a high-performance,
multi-controller system in a modular chassis format.
2. The SoftLogix platform uses a virtual chassis.
3. The CompactLogix platform has a set I/O count because it is
geared toward stand-alone control applications where panel
space is limited. Additional I/O is not necessary unless the
application is significantly changed.
4. The FlexLogix platform has a reduced size for smaller spaces.
This makes it possible to place the platform within a close
proximity to the machine or process.
5. The DriveLogix platform is a system for distributed drive
control.
6. All Logix5000 controllers share the Logix5000 control engine.
7. Answers may vary. The following responses are possible
correct answers:
Backplane
Connecter
LEDs
Keyswitch
Battery
Door
Battery Label
Labels
Serial Port
Locking Tab
1--21
10. Slots are the openings in a chassis or on a DIN rail that hold
individual modules.
12. RTBs and IFMs are devices that provide interconnection
between I/O modules and processes/machines. None of these
components are included with the I/O modules.
13. The battery in the controller maintains memory if the main
power source is lost.
14. The status indicators on the front of a controller can be checked
for module status information.
15. RSLinx Classic software provides an interface between
RSLogix 5000 software and the system hardware, including the
controller. RSLinx Classic software provides download and
upload, online editing, and data monitoring functionality for
Logix5000 systems.
Exercise B
1. The chassis size is ten slot.
4. The workstation contains the following hardware:
A. 1756-OB16D digital output module
B. 1756-L63 (Logix5563) controller
C. 1756-IB16D digital input module
D. 1756-L63 (Logix5563) controller
E. 1756-OB16D digital output module
F. 1756-CNB ControlNet bridge module
G. 1756-DHRIO DH+/RIO communications bridge module
H. 1756-OF6VI analog output module
I. 1756-IF6I analog input module
J. 1756-ENBT Ethernet/IP communications bridge module
If you are not using a standard ControlLogix
training workstation (Part No. ABT-TDCLX1),
your answers may vary.
1--22
Lesson
2--2
Tip "
Toolbars
Routine Editor/
Tags Window
Controller
Organizer
Results Window
Toolbars
The following toolbars are available:
Standard toolbar
Online toolbar
Path toolbar
Language Element toolbar
Standard Toolbar: An optional toolbar with standard Microsoft
options such as new, save, cut, copy, paste, and more.
Standard
Toolbar
2--3
Tabs
Keyswitch
Controller
Properties
Element Tabs
Element Buttons
Element Tabs
Element Buttons
New Program
Status Bar
Rev. February 2007
2--4
Controller Organizer
Point out that the Controller Organizer
represents the entire project, including
the tasks, data, and I/O configuration.
Tip "
Expanded
Branch
Collapsed Branch
Quick Pane
Tip "
2--5
Routine
Window Tabs
"
When more than one Routine Editor or Tags window is opened, tabs
across the bottom of the window are used to separate the editors or
windows.
Results Window: A window at the bottom of the main window that
contains the following tabs:
Errors Tab: Results of a verification for errors in the project.
Search Results Tab: Results of a search for a project component.
Watch Tab: Window for viewing data in an open routine.
Tabs
The Results window is not always present and only opens when there
is a specific command, or when initiated by the user.
E 2007 Rockwell Automation, Inc. All rights reserved.
PR3sb56r
2--6
Help System
Release notes
Online books in Adobet Acrobatt format
Sample RSLogix 5000 projects from Rockwell Automation and
other vendors
2--7
2--8
Search Word
Resulting Topics
Display Options
(Colors, Fonts, and
Documentation)
Reset to Default
2--9
To make the best use of screen space and functionality, the following
actions can be performed with toolbars:
Display/hide toolbars
Point out that only certain toolbars can
be customized. This will be discussed in
the Heres How demonstration.
View
User-Created
Toolbar
Reset to
Default
Heres How
Open the CCP146_1756r_DEM1.acd
file. Give the students an overview of the
Workstation Options dialog box. Do not
dwell on the terms or concepts that they
do not yet know. While demonstrating
this procedure, point out the following
elements:
S
2--10
2--11
Tip "
If you do not see all of the toolbars, from the View menu, select
Toolbars . . . then click Restore Factory Toolbar Layout.
5. In the Language Element toolbar, find and click the
Move/Logical tab.
6. On the Move/Logical tab, scroll to the last instruction button on
the right.
7. Use ToolTips to identify the button.
8. What is the instruction?
2--12
Tip "
Category
Option
Application
Tip "
2--13
29. To create data for the Results window, from the Logic menu,
select VerifyRoutine.
30. Scroll through the errors in the Results window.
31. Close the Results window.
32. Return to the Workstation Options dialog box and click Reset
Category for all applicable Editor categories.
Tip "
2--14
Answers
Exercise A
4. The software components can be found in the following default
locations:
Path Toolbar
Standard Toolbar
Online Toolbar
Routine Editor/
Tags Window
Controller
Organizer
Lesson
Tip "
Project Components
If you are teaching the standard
course, note that tags are data storage
mechanisms that will be covered later in
the course.
Tip "
3--2
Tasks Folder
Task_A
Program_A
Program Tags
Routine_A
Routine_B
Routine_C
Program_B
Task_B
Tasks
A task triggers the execution of its scheduled programs.
The following types of tasks can be created in a project:
Task Type
Tip "
Icon
Continuous
Periodic
Event
Usage
Number of
Continuous Tasks
32
4, 6, 8, or 16 (depending
on processor model)
3--3
Programs
A program is the second level of scheduling within a project:
Each ControlLogix or SoftLogix task can contain (schedule) up to
100 programs.
Tip "
to 32 programs.
When a task is triggered, its programs execute in sequence from
the first scheduled to the last scheduled.
Unscheduled Programs: Programs within a project that are not
scheduled by any task; they do not execute. Programs may be left
unscheduled until needed (to add future functionality or for
troubleshooting).
When a project is created, a default program is defined under the
MainTask (continuous task) and named MainProgram.
Tip "
3--4
Main Routine
Fault Routine
Subroutines
The routine types within the Controller Organizer are shown in the
following graphic:
Function Block
Diagram Routine
Note that the actual number of routines
depends on what is programmed in each
routine and how much memory
the code requires.
Tip "
Heres How
Create a new project in RSLogix5000
software. Assign it to the controller in
slot 1.
3--5
3--6
3--7
5. What is the name of the function block routine within the periodic
task?
6. What is the name of the fault routine within the Filling program?
3--8
Exercise B
Tip "
Package
There are many ways to organize a project. This is only one example
of how you might do so.
Directions:
For help performing steps in this exercise, see the associated job
aid(s).
1. Create a new project for the controller in slot 1.
Tip "
Tip "
To . . .
MainTask
Assembly
MainProgram
Station_One
MainRoutine
Press
Examine each tab of the the properties dialog box as you modify
these components.
3. Create a new program in the Assembly task named Station_Two.
4. Create a main routine in this program named Package.
Tip "
You now have two programs for the two stations on the conveyor:
Station One (Press) and Station Two (Package).
5. The pressure at the press machine must be monitored at regular
intervals. To do so, create a periodic task called Pressure.
Set the period for the task to 100 ms.
3--9
Tip "
You now have a task that is activated every 100 ms. Once code has
been entered to evaluate inputs and set outputs, this task will be able
to measure and monitor machine pressure.
13. Save all changes to the project and close the software.
3--10
Answers
Exercise A
3. The name of the continuous task is Bottling.
4. The name of the unscheduled program is Capping.
5. The name of the function block routine within the periodic task
is MainFBD.
6. AlarmLight is the fault routine within program Filling. It is
assigned as the fault routine within the Filling program
properties.
7. Conveyor is the subroutine within program Filling. It is not
assigned as the main or fault routine; therefore, it is a
subroutine.
8. Label_Glue_Low is the event task.
Exercise B
9. Your project should look similar to the following example:
Press
Package
Machine
Pressure
Lesson
Data
4--2
Data
Note that you can download in the
Remote Program and Program modes
only.
Data
Tip "
4--3
Tip "
4--4
Selected
Backplane
x
Missing or
Faulted Module
4--5
Current Path
Path Saved in Project
Correlation Errors
Various error messages may be displayed when a computer attempts
to communicate with a controller.
Rev. February 2007
4--6
Remote
The keyswitch positions are labelled on the front of the controller:
ControlLogixr
Controller Keyswitch
CompactLogixt
Controller Keyswitch
FlexLogixt Controller Keyswitch
4--7
Keyswitch
Position
Run
Program
Online (Mode)
Drop-Down List
Remote Mode
Selection Options
Physical
Keyswitch in REM
4--8
Heres How
Use the CCP146_1756r_DEM1.acd to
demonstrate.
Use the workstation to show students
how to manually change controller
modes. Emphasize the need to exercise
caution when changing modes.
4--9
4--10
Run
Program
Remote
Run
Program
Test
Exercise B
4--11
Tip "
4--12
Answers
Exercise A
1. To transfer a new project from your computer to a controller
you must download the project.
NO TAG
The computer must be online to monitor a
project as it is running in a controller.
3. To transfer a file from the controller to computer in order to
monitor a project running in a controller you must upload the
project.
4. Both RSLogix 5000 and RSLinx Classic software are used to
upload, download, and go online with a controller. RSLinx
Classic is automatically called by RSLogix 5000 software when
a communications option is selected.
5. Making mistakes online can cause unintended machine motion
or loss of process control, injuring personnel and damaging
equipment.
6. Before performing procedures online, complete these safety
precautions:
editing.
Assess how machinery will respond to changes.
Check proposed changes for accuracy.
Notify all personnel of the changes.
Verify that you are online to the correct controller.
Run
Remote
Program
Run
Program
Test
n
n
n
n
n
4--13
Exercise B
4. If you are using EtherNet or EtherNet/IP to download the
project, your selection in the RSWho window will appear
similar to the following graphic:
4--14
Lesson
Top Guide
Locking
Tab
Connector
Pins
Slots for
Keying
Bottom Guide
5--2
Tip "
5--3
I/O Status
LED indicators are located on the front of all I/O modules to show if
all connections and communications are functioning properly:
Fuse
Status
Fault Status
Diagnostic Module
Module Status
Electronically Fused
I/O Status: The yellow status indicator shows the ON/OFF state
of the field device.
communication status.
Fault Status: This display, found on some modules, indicates the
presence or absence of various field-side faults.
Fuse Status: This display, found on electronically fused modules,
indicates the state of the modules fuse.
Pushbuttons
Limit Switch
Photo-Electric Sensor
Motor
5--4
Gauges/Meters
Flow Meters
Thermometer
32-bit floating or 16-bit input and 13-16 bit output integer data
format depending on the module
Alarming
Rolling time stamp of data
Diagnostic choices
5--5
"
Remote I/O modules are not located in the same chassis as the
controller that configures them.
This allows I/O to be located in a closer proximity to the process:
Controller
Local ControlLogix
Chassis
Communications Module
Process/Machine
Communications Module
Remote ControlLogix
Chassis
Control-Level Network
Example: 1756-ENBT
Tip
modules must be included
in both chassis to create
an EtherNet/IP network connection.
"
5--6
number 1756--OB16D.
Tip "
I/O Configuration
I/O modules are not the only type of
module that can be configured in the I/O
Configuration folder. Module such as
bridges and controllers can also be
configured there.
Configured Local
1756-I/O Modules
Be sure to mention that this is a very
basic overview of module configuration.
For more details, students should attend
an advanced course in the curriculum.
Note that the Communications Format is
one parameter that cannot be changed
online.
Tip "
5--7
When you add a new I/O module to a project, you are first prompted
to enter general module properties in the New Module dialog box:
Once data has been entered in the New Module dialog box, you can
then continue module configuration from the Module Properties
dialog box.
Parameters for configuring a digital 1756-I/O module are entered on
the following tabs in the Module Properties dialog box:
General
Connection
Configuration
General Tab
The following graphic shows the General tab parameters:
Name
Slot Number
Communications
Format (Ownership)
Electronic Keying and
Revision Level
5--8
Electronic Keying
Explain that the compatible module
keying option is the most common
configuration choice.
Connection Tab
The following graphic shows the Connection tab parameters:
5--9
The RPI can vary from 200 microseconds (.2 ms) to 750 ms
Inhibit Module Connection Option: An option that allows
configuration data for a module to be written but prevents the
module from communicating with the owner controller.
Major Fault Option: An option that causes a major fault on the
controller if the connection to the module fails.
Configuration Tab
The following graphic shows an example of the Configuration tab
parameters:
Diagnostic Features
I/O Points
5--10
5--11
Because of the update process, input devices may change state within
one program scan and at a different rate than the program scan:
Photo-eye tag is set in database
100
End of Task
If enabled, input
module and the
physical devices
are updated
Location:Slot:Type.Member.Submember.Bit
I/O Point (Optional)
Emphasize that each component of a
base tag depends on the type of
hardware used.
Mention that submembers and bits are
optional.
Tip "
Rev. February 2007
5--12
Heres How
Create a new project in RSLogix5000
software. Configure digital I/O modules
in your workstation.
5--13
2. Why are devices wired to an RTB rather than directly to the I/O
module?
5--14
Input
Output
Digital
Analog
LED
Thermometer
Motor
Contactor
Pressure
Gauge
Pushbutton
Start/Stop
switch
Light Sensor
Exercise B
5--15
Default
Slot
Notes
Digital
Output
Module
Digital Input
Module
Tip "
If there are FLT (fault) LEDs illuminated on the face of the output
module, verify that the diagnostic selections on the Configuration tab
for the output module are cleared.
6. When all modules are configured and running correctly, go
offline and close the project.
5--16
5--17
5--18
Answers
Exercise A
1. The following answers are possible correct responses:
5--19
Input
LED
Thermometer
Output
Digital
Analog
Motor
Contactor
Pressure
Gauge
Pushbutton
Start/Stop
switch
Light Sensor
Exercise B
2. The following dialog boxes should match your configured I/O
module for slot 0:
5--20
5--21
5--22
Lesson
Optional: A lesson on Identifying
Numbering Systems and Converting
Numeric Values is available. This lesson
is not a requirement for the course.
Tags
Memory: A group of circuit elements in a controller where
programs and data are stored.
The following are common memory sizes:
Bit: The smallest unit of data represented by the digits 0 and 1
Byte: A string of 8 bits operated on as one unit.
6--2
Tip "
Data Types
Add that the data type maps out the data
just as it does in a PLC-5, SLC 500, or
other processor.
Data Type: The definition of how many bits, bytes, or words of data
a tag will use. The data type is based on the source of the
information.
Pre-Defined Data Types: Commonly used memory sizes that are
already defined in the software.
Atomic Data Type: A simple data type made of one piece of data:
Data Type
Definition
BOOL
SINT
INT
DINT
REAL
6--3
Using these definitions, tags for the given devices require the
following data types:
Drive_Speed Data
DINT, or 32 Bits
Controller Memory
Start Data
BOOL, or 1 Bit
Sensor Data
BOOL, or 1 Bit
Tip "
Data Type
Definition
COUNTER
TIMER
There are other less common, pre-defined data types that are used to
store specific data for function block instructions or motion
instructions.
Module Defined Data Types: Data types used for hardware data,
such as I/O tags.
Alias Tags
Tell students that if a base tag is used as
an address, any corresponding alias
tags will not be displayed.
Tip "
Alias Tag: An additional name for a tag (or other alias tag):
The tags refer to the same area of memory.
The tags, therefore, reflect the same values and changes.
An alias tag can be used to identify an automatically generated I/O
tag with a complex name. For example, Motor can be an alias tag for
Local:2:O.Data.15.
6--4
Scope
Scope: The definition of where a controller can access a tag or set of
tags.
Tags Icon
Controller-Scoped
Tags Collection
Program-Scoped
Tags Collection
Program-Scoped
Tags Collection
Tip "
Each Tags collection has a Monitor Tags tab and an Edit Tags tab.
6--5
Right- Click to
Hide/Show/Sort
Columns
Scope of Current
Blue
Collection
Arrow
Display Style
Filter
Tag and Members
Data Type
Operand (Tag)
Descriptions
Value in
Controller
Expand to See
Structure Members or
Bits within the Tag
Monitoring View
The Style parameter controls how data is displayed for certain tags.
Example: DINT Display Style
The default style for a tag of the DINT data type is decimal. This
can be changed to binary, octal, decimal, or hexadecimal.
Tip "
Style is for display only; it does not affect how data is stored in the
controller.
6--6
Tip "
The Edit Tags list lets users perform the following tasks:
Create and delete tags
Tag Name
What this is an
Alias Tag For
Display Style
Data Type
Operand (Tag)
Descriptions
White = Editable
Field
Editing View
Style: The format in which number system values for data type
6--7
Heres How
Use CCP146_1756r_DEM1.acd to
demonstrate the procedures.
6--8
6--9
Unit of Memory
6--10
11. If you opened a tag collection, which tab would you choose to
modify tag values in an active controller (online)?
12. If you opened a tag collection, which tab would you choose to
create and delete tags?
6--11
Exercise B
Type
Description
Conveyor_Moving
BOOL
Conveyor_Start
BOOL
Conveyor_Start_Time
TIMER
Conveyor_Stop
BOOL
Conveyor_Stop_Time
TIMER
Process
BOOL
Restart
BOOL
3. Sort the tags so that all tags of the same data type are together.
4. Filter the tags to show only the tags of the BOOL data type.
5. Filter the tags to Show All Tags.
6. Resort the tags to display the tags by name in alphabetical order.
7. Save the project.
6--12
Exercise C
In this exercise, you will practice creating tags and monitoring data
in an RSLogix 5000 project.
Directions:
For help performing steps in this exercise, see the associated job
aid(s).
1. Open the TAG_1756r_C1.acd project file.
2. Define the following controller-scoped tags as alias tags for the
local I/O tags:
Device/Tag Name
Conveyor_Moving
Local:0:O.Data.5
Conveyor_Start
Local:2:I.Data.0
Conveyor_Stop
Local:2:I.Data.1
Process
Local:0:O.Data.2
Process
Conveyor_Stop
Conveyor_Moving
10. What is the value of the Conveyor_Moving tag and the Process
tag?
6--13
6--14
Answers
Exercise A
1. The common memory sizes are labelled in the following table:
Description
Unit of Memory
Word
Bit
Byte
n
n
n
n
6--15
Exercise B
2. Your tag database should appear similar to the following example:
Controller Scope
Filter
Sort By Name
Exercise C
2. The following alias tags tags were created:
6--16
Lesson
Key Terms
Array: A numerically indexed sequence of elements of the same
data type. An array tag occupies a contiguous section of memory in
the controller with each element in sequence. Arrays can have one,
two, or three dimensions.
Element: A single position within an array.
Example: Array
A controller needs to store a piece of data for six different parts.
This data can be stored in an array of 6 INTs:
Array of 6 INTs
Group of 6 INTs
(Numbered 0 to 5)
One Element
7--2
Monitoring Arrays and Tags of User-Defined Data Types in an RSLogix 5000 Project
Array Addressing
Note that the number or expression in
the brackets is the subscript. Point out
the square brackets that enclose the
element number.
ArrayName
ArrayName
Add that an array might include data
stored by shift, day, and week. Or, x and
y coordinates (for retrieving a part in
storage).
Dimension 3
Dimension 2
Dimension 1
Storage[5,2,773]
Color
Part Number
Shift Number
Day
Tip "
Size
Weight
Monitoring Arrays and Tags of User-Defined Data Types in an RSLogix 5000 Project
7--3
Example
It is a . . .
ArrayName[Element]
Part[5]
Standard single
dimensional array
element
ArrayName[Tag]
ArrayName[Expression]
Station[Position]
Station[Position+5]
Changing
element
ArrayName[Element].Bit
Part[5].15
ArrayName[Epression].[Tag]
ArrayName[Expression].[Expression]
Part[IndexAND7].[MyIndex]
Part[IndexAND7].[MyIndex+31]
Changing bit in
the element
Temperature
Steam Valve State
Time Over Temperature
Level
7--4
Monitoring Arrays and Tags of User-Defined Data Types in an RSLogix 5000 Project
Members
Tank
Data Type
Monitoring Arrays and Tags of User-Defined Data Types in an RSLogix 5000 Project
7--5
Example: Addressing
To observe the temperature value for the tank in position [1,3],
the following tag would be addressed in the ladder logic:
Tank[1,3].Temperature
To observe the preset of the timer for the tank in position [1,3],
the following tag would be addressed in the ladder logic:
Answer: Tank[1,4].Level
Tank[1,3].Time_Over_Temp.PRE
Heres How
These procedures can be found in the
Procedures Guide under Monitoring and
Editing Tag Values through the Tags
Window which is a subprocedure of
Monitoring and Editing Data in a
Logix5000 Controller.
7--6
Monitoring Arrays and Tags of User-Defined Data Types in an RSLogix 5000 Project
Exercise: Monitoring Arrays and Tags of User-Defined Data Types in an RSLogix 5000 Project
7--7
Zone_Preset[
Zone_Preset[
Zone_Preset[
7--8
Exercise: Monitoring Arrays and Tags of User-Defined Data Types in an RSLogix 5000 Project
8. Check each of the following facts that you have now observed
about this simple array:
- An array is a sequence of tags of the same data type.
- Individual array elements are numbered beginning with 0.
- Individual array elements can be monitored in the
RSLogix 5000 Tags window.
- Individual array elements can be addressed in executable
code.
9. Open the controller-scoped tags collection and monitor the
OffDelayZone tag through the RSLogix 5000 Tags window.
10. How many elements are in the array?
Tip "
16. On rung 12, what is the tag address of the TOF instruction that
resembles one of the elements from Step 11.?
Exercise: Monitoring Arrays and Tags of User-Defined Data Types in an RSLogix 5000 Project
7--9
21. Display rung 27 and examine the MOV instruction (source tag).
Does the tag match your answer?
22. Check each of the following facts that you have now observed
about more complex arrays:
- An array is a sequence of tags of the same data type.
- Individual array elements are numbered beginning with 0.
- Individual array elements can be monitored in the
RSLogix 5000 Tags window.
- Individual array elements can be addressed in executable
code.
- Each array element can be expanded to view its separate
members.
- Members of individual elements can be addressed in
executable code (e.g., Part[5].DN).
Tip "
7--10
Exercise: Monitoring Arrays and Tags of User-Defined Data Types in an RSLogix 5000 Project
27. Monitor the ElapsedTime tag through the RSLogix 5000 Tags
window.
Tip "
32. Monitor the CTU tag on rung 23. Does the tag match your
answer?
34. Monitor the XIC ( --] [-- ) instruction and tag on rung 23. Does
the tag match your answer?
Exercise: Monitoring Arrays and Tags of User-Defined Data Types in an RSLogix 5000 Project
7--11
35. Check each of the following facts that you have now observed
about user-defined data types:
- A user-defined data type is a group of tags of different
data types.
- Individual members can be monitored in the RSLogix 5000
Tags window.
- Individual members can be addressed in executable code.
- Each tag can be expanded to view its separate members.
7--12
Exercise: Monitoring Arrays and Tags of User-Defined Data Types in an RSLogix 5000 Project
Answers
Exercise A
4. The elements are numbered beginning with 0:
Zone_Preset[0]
Zone_Preset[1]
Zone_Preset[2]
Zone_Preset[3]
5. All tags in an array are of the same data type -- in this case,
DINT.
7. The tag address of the source parameter of the MOV instruction
is Zone_Preset[2].
8. As you observed in the exercise, all of the following facts about
arrays are true:
n An array is a sequence of tags of the same data type.
n Individual array elements are numbered beginning with 0.
n Individual array elements can be monitored in the
RSLogix 5000 Tags window.
n Individual array elements can be addressed in executable
code.
10. OffDelayZone is an array of 5 elements.
11. The elements are numbered beginning with 0:
OffDelayZone[0]
OffDelayZone[1]
OffDelayZone[2]
OffDelayZone[3]
OffDelayZone[4]
12. All tags in an array are of the same data type -- in this case,
TIMER.
15. The members of each element are exactly the same (.PRE,
.ACC, etc.)
16. The TOF instruction on rung 12 that resembles one of the
elements from Step 11. is OffDelayZone[2].
18. The element specified in the ladder logic is 3
(OffDelayZone[3]).
19. The tag specified in the ladder logic would be
OffDelayZone[3].DN.
20. The tag specified in the ladder logic would be
OffDelayZone[3].ACC.
Exercise: Monitoring Arrays and Tags of User-Defined Data Types in an RSLogix 5000 Project
7--13
TIMER
Minutes
COUNTER
Hours
COUNTER
7--14
Exercise: Monitoring Arrays and Tags of User-Defined Data Types in an RSLogix 5000 Project
Lesson
Basic Instructions
Instructions are commands that evaluate data or control data during
the program scan.
The following list contains basic categories of ladder logic
instructions:
Conditional Bit Input Instructions
One Shot Instructions
Conditional Bit Output Instructions
Then select . . .
Examine if Closed
Name
Mnemonic
Symbol
XIC
Examine If Open
XIO
8--2
Then select . . .
Name
Output
Energize
Mnemonic
Symbol
OTE
XIC
Checks the Tag for a value of 1
Tip "
OTE
XIO
Checks the Tag for a value of 0
Tip "
OTE
If the Switch tag contains a 0, then the Conveyor tag is set (1).
8--3
Then select . . .
One Shot
ONS
"
8--4
The following table outlines the functions of the two retentive bit
output instructions:
Highlight the fact that the entire rung
does not have to be true. Only the
conditions leading up to (left of) the
instruction need to be true.
Example: A retentive bit output
instruction might be used to latch a
cooling pump so it restarts after a power
failure.
Then select . . .
Name
Mnemonic
Output
Latch
OTL
Output
Unlatch
OTU
Symbol
OTL
OTU
Tip "
Tip "
Seal-in logic is often used instead of the OTL and OTU instructions
for applications in which it is undesirable to have latched bits
following a power loss.
Tip "
Timer Instructions
Timer instructions count in time units. Operations then can be
controlled based on the status or value of the timer.
All timer instructions act on tags of the timer data type.
8--5
Timer Status Bits: .EN, .DN, and .TT are timer status bits. Their
function is to tell the controller the status of the timer instruction:
Description
.EN (enable)
.DN (done)
Timer status bits are referenced by entering the timer name followed
by the status bit: Conveyor_Timer.TT
8--6
Accumulated Time
Output Activated
Exercise: Selecting Basic Ladder Logic Instructions for an RSLogix 5000 Routine
8--7
Tip "
On the first rung, any user-specified input can be used to enable the
Emergency_Light output. Also, the second rung can have any
user-specified output.
8--8
Exercise: Selecting Basic Ladder Logic Instructions for an RSLogix 5000 Routine
Tip "
Exercise: Selecting Basic Ladder Logic Instructions for an RSLogix 5000 Routine
8--9
8--10
Exercise: Selecting Basic Ladder Logic Instructions for an RSLogix 5000 Routine
Answers
Exercise A
1. An OTL instruction will keep a bit set to one (or true, in this
case) even if a condition goes false. This instruction will keep
the machines indicator light on even after a power cycle
occurs.
2. An OTU instruction is paired with an OTL instruction to
deactivate, or unlatch, it. The indicator light can be turned off
with an OTU instruction.
3. An XIC (examine if closed) instruction should be selected if the
button used is wired normally-closed.
4. The input instruction in the second rung uses the same alias as
the output instruction in the first. Because the input instruction
references the output point, it becomes true every time the
output is set:
Exercise: Selecting Basic Ladder Logic Instructions for an RSLogix 5000 Routine
8--11
8--12
Exercise: Selecting Basic Ladder Logic Instructions for an RSLogix 5000 Routine
Lesson
After completing this lesson, you should be able to enter ladder logic
components in an RSLogix 5000 routine by performing the
following tasks:
Enter and edit ladder logic components
Assign tags to instructions
Verify a project or a routine
Tip "
RSLogix 5000 software offers the ability to enter and edit ladder
logic using any combination of the following basic methods:
Windowsr-based methods (dragging)
Insert key
Right-click menu
Other more advanced methods of entering ladder logic, such as
ASCII editing and neutral text, are available.
9--2
Valid
Placement
Location
When dragging ladder logic elements from this toolbar, keep in mind
the following tips:
Target squares indicate where an instruction can be placed.
A green target circle indicates where a ladder logic element will
be inserted when the mouse button is released.
An empty or completed rung can be selected and dragged to
another valid placement location.
including:
-- Cut, copy, and paste
-- Delete
-- Undo and redo
Insert Key
Ladder logic can be entered using the [Insert] key on a keyboard.
9--3
Selection Tree
Grouping Option
9--4
Drag to Expand
Column Width
Tag Scope
Resize Option
In the graphic, point out the main
options. If you are using the software,
expand different tags such as timers,
and I/O tags. Show the available
members.
If a tag is not already created, it can be created from the operand text
box in an instruction:
In the graphic, point out the main operand
and the create option.
Add that if a tag is created from the rightclick menu, spaces (underscores) cannot
be entered.
New Tag
Right-Click
Option
9--5
Tags with data types that are not valid for the instruction
Empty rungs
Projects with errors will not download to the
controller.
Tip "
Heres How
Open the CCP146_1756r_DEM1.acd
file. Create a new ladder logic routine to
enter ladder logic. While demonstrating
the procedures, point out the following
elements:
S
Verification buttons
Verify
Project
The auto rung verification option is available for users who want
errors to be displayed in the Results window as rungs are entered.
To enter ladder logic components in an RSLogix 5000 routine by
performing the following tasks:
Enter and edit ladder logic components
Assign tags to instructions
9--6
9--7
Tip "
9--8
Tip "
Tip "
Tip "
The Process tag does not exist. Create this tag after assigning it.
12. Verify the routine and correct any errors.
9--9
13. Download the project to the controller in slot 1 and then place the
controller in the Run mode.
14. Open the Watch tab in the Output window to monitor the tags and
ladder logic at the same time.
15. Enable the Conveyor_Start tag by typing a one as the tag value in
the Watch tab.
16. Describe what happens in the ladder logic:
17. Enable the Conveyor_Stop tag by typing a one as the tag value in
the Watch tab.
18. Describe what happens in the ladder logic:
9--10
Answers
Exercise A
16. If the ladder logic is entered correctly, the
Conveyor_Start_Time timer will accumulate until it reaches
5000 ms (5 seconds).
18. If the ladder logic is entered correctly, the system will reset. In
other words, the TON instruction will reset because the
accumulated (Accum) value will return to zero.
Lesson
10
After completing this lesson, you should be able to modify timer and
counter instructions.
Timer instructions are used when any of the following actions need
to occur:
After a timed delay, trigger an outcome to take place
Cause an event to transpire for a specified length of time
Time the duration of an event
Tip "
10--2
Preset Tag
Accumulated Tag
Enable Tag
Timer Timing Tag
Done Tag
Description
.EN (enable)
.DN (done)
10--3
Timer Instructions
Timer instructions control operations based on time:
To . . .
For Instance . . .
TON
timer on delay
TOF
timer off delay
Accumulate time
RTO
retentive timer on
delay
Reset a timer
RES
Tip "
10--4
.TT
.EN
.DN
=0
Reset (False)
< PRE
Timing (True)
= PRE
and then disabled (cleared), light_2 and light_3 are enabled (on)
for 2000 milliseconds (timer_2 is timing and the done (.DN) bit is
enabled).
When timer_2.ACC reaches 2000, light_2 and light_3 are
disabled (turn off).
A TOF instruction works in the following manner:
.EN
.TT
.DN
=0
Reset (False)
< PRE
Timing (True)
= PRE
10--5
Tip "
.TT
.DN
=0
Reset (False)
< PRE
Timing (True)
= PRE
= PRE
10--6
Counter
Status Bit
Description
.CU
.CD
.DN
DN
.OV
Specifies whether or not the counter instruction has counted above the
upper limit of +2,147,483,647 (overflow):
When .OV is 1 (set), the upper limit has been exceeded.
When .OV is 0 (cleared), it has not been exceeded.
.UN
Specifies whether or not the counter instruction has counted below the
lower limit of --2,147,483,648 (underflow):
When .UN is 1 (set), the lower limit has been exceeded.
When .UN is 0 (cleared), it has not been exceeded.
Rev. February 2007
MTCsb56r
10--7
Tip "
The COUNTER data type is a block of data that can be used to count
up, count down, and add or subtract from one total count.
Counter Instructions
Tip "
For Instance . . .
Count up
CTU
count up counter
Count down
CTD
count down
counter
Reset a counter
RES
10--8
A CTD instruction is used to count down by one every time the rung
is true and the instruction is enabled. It is usually used in conjunction
with a CTU, but can be used separately:
The CTU and CTD add or subtract from the same total count.
increments by 1.
Each time a part leaves, limit_switch_2 is enabled and part_count
decrements by 1.
If there are 100 parts in the buffer zone (part_count.DN is set),
conveyor_A is enabled (on) and stops the conveyor from bringing
in any more parts until the buffer has room.
RES (Reset) Instruction
An RES instruction is an output instruction used to reset timer and
counter instructions. An RES instruction will typically reference
either a TON, RTO, CTU, or CTD instruction by its tag.
10--9
When an RES instruction is true, the accumulated value and the bits
of either a timer or counter instruction of the referenced tag data type
are cleared to 0 (reset). The following graphic shows an example of
an RES instruction referencing a counter instruction:
Heres How
To demonstrate:
1. Go online to the controller with
MTC_1756R_DEM1.acd file.
10--10
Example
In the demonstration, show how the
timer resets when the rung goes false.
Expand the tag TON_Demo in the
Monitor Tags window during the
demonstration so the students can see
the correlation between the tags and the
ladder logic.
Point out that while the timer is enabled
and timing, the two yellow pushbuttons
Yellow_Light_DO1 and
Yellow_Light_DO4 are illuminated.
TON Instruction
The following graphic shows an example of a TON instruction. In
this example, note the following conditions:
Red_Light_DO2 will become enabled (turn on) five seconds after
Pushbutton_DI1 becomes enabled.
When Pushbutton_DI1 becomes true (enabled), the TON
instruction will be enabled and start timing. It continues timing
until the accumulated value reaches the preset value of 5 seconds
(5000 ms). The branch using the TON_Demo.TT bit is used to
seal-in around the momentary pushbutton to keep the rung true.
If rung 0 becomes false (0/open) after the timer starts timing, the
timer will stop timing, reset, and the accumulated value will
return to 0.
When accumulated = preset, the instruction is timed out and the
.DN bit is enabled.
TON_Demo.DN references the .DN bit and becomes true when
the .DN bit is enabled.
Example
10--11
TOF Instruction
The following graphic shows an example of a TOF instruction. In
this example, note the following conditions:
When Switch_DI14 becomes enabled (false to true)
Red_Light_DO11 will become enabled (on).
When Switch_DI14 becomes false (0/open), the TOF instruction
will be enabled and start timing. It continues timing until the
accumulated value reaches the preset value of 7 seconds (7000
ms).
10--12
Example
Display the RTO_Routine.
Demonstrate how when Switch_15 is
disabled while timing and when the
instruction times out, the RTO retains
the accumulated value.
Expand the tag RTO_Demo in the
Monitor Tags window during the
demonstration so students can see the
correlation between the tags and the
ladder logic.
The RTO instructions accumulated value and bits are not cleared
until Pushbutton_DI0 is enabled and the RES instruction resets
RTO_Demo.
Example
Display the CTU_Routine in the
Counters_Program.
Expand the CTU_Demo tag in the
Monitor Tags window during the
demonstration so the students can see
the correlation between the tags and the
ladder logic.
Point out the importance of using an
RES instruction on a CTU instruction, or
the counter will continue counting and
the .DN bit will remain set.
10--13
CTU Instruction
The following graphic shows an example of a CTU instruction. In
this example, note the following conditions:
When Count_Up_Pushbutton_DI4 is enabled (1/closed), the CTU
instruction will count up by one. This pushbutton must go
false-to-true three times for accumulated to = preset.
When accumulated = preset, the .DN bit is enabled and
Red_light_DO8 becomes enabled (true).
Once the .DN bit is set, it stays set until the counter is reset.
If Count_Up_Pushbutton_DI4 is enabled, the accumulated value
will continue to increase past three until the counter is reset.
10--14
Example
Display the CTD_Routine in the
Counters_Program.
Point out that accumulated must be less
than/go beyond --4 for the .DN bit to be
cleared.
Mention that the CTD instruction is
typically used with a CTU instruction that
references the same counter tag value.
Point out the importance of using an
RES instruction on a CTD instruction, or
the counter will continue counting and
the .DN bit will remain disabled.
CTD Instruction
The following graphic shows an example of a CTD instruction. In
this example, note the following conditions:
The .DN bit is set before the instruction is enabled because
accumulated preset.
When Pushbutton_DI0 is enabled (1/closed), the CTD instruction
will count down by one. Pushbutton_DI0 must go false-to-true
four times for accumulated to = preset and five times for
accumulated < preset and disable the .DN bit.
Example
Explain that the reset button must be
enabled to reset the counters. Also,
explain that the counters can be reset at
any time, for instance, before or after
accumulated is equal to, less than, or
more than the preset value.
10--15
RES Instruction
The following example shows a programmed RES instruction
referencing the CTU and CTD counter instructions. In this example,
note that when Reset_Counter_1_DI6 transitions from false-to-true,
counters CTU and CTD are reset:
10--16
10--17
It takes 8 seconds for the operator to load the coke onto each
conveyor system.
A ladder logic instruction will keep track of the time and retain
the time until it is reset, even if the loading process is interrupted.
A pushbutton on the workstation will reset the conveyor count
once every 24 hour period.
For help performing steps in this exercise, see the associated job
aid(s).
Directions:
1. Open the MTC_1756r_A1.acd project file.
2. Determine the tag name, base tag, and the workstation device for
the digital inputs used in the program North_Conveyor:
Workstation
Device
Tag Name
10--18
3. Determine the tag name, base tag and the workstation device for
the digital outputs used in the program North_Conveyor:
Workstation
Device
Tag Name
Base Tag
(output)
4. Determine the tag name, base tag and the workstation device for
the digital inputs used in the program South_Conveyor:
Workstation
Device
Tag Name
5. Determine the tag name, base tag and the workstation device for
the digital outputs used in the program South_Conveyor:
Workstation
Device
Tag Name
Base Tag
(output)
7. How many times will the operator need to enable the counter in
the North Conveyor program before the North_Conveyor output
will be enabled?
10. In the South Conveyor program, what is the preset value of the
counter on rung 1?
10--19
11. In the South Conveyor program, modify the preset value of the
counter on rung 1 so that each time the operator enables the rung
the South_Conveyor output will be enabled.
12. In the South Conveyor program, what did you change the preset
value of the counter on rung 1 to?
18. What type of timer is used to retain the accumulated value if there
is a power loss or the rung is disabled for some reason?
21. In the North and South Conveyor programs, modify the preset
value for the timers to time for 8 seconds.
22. In the North Conveyor program, what will cause rung 3 to
become false, and what will happen when it becomes false?
23. In the North Conveyor program, which bit will enable the counter
on rung 5?
10--20
24. In the North Conveyor program, modify the preset value of the
counter on rung 5 to the correct value.
Tip "
32. In the North Conveyor program, describe what will happen when
the inputs and outputs on rung 5 are enabled?
33. Go offline.
E 2007 Rockwell Automation, Inc. All rights reserved.
10--21
10--22
Answers
Exercise A
2. The following table lists the the tag name, base tag and the
workstation device for the digital inputs used in the program
North_Conveyor:
Workstation
Device
Tag Name
DI0
North_PushButton_Reset_Counter
Local:2:I.Data.0
DI1
North_Start_PushButton
Local:2:I.Data.1
DI2
North_Coke_Loading_PushButton
Local:2:I.Data.2
DI3
North_PushButton_Reset_Timer
Local:2:I.Data.3
DI4
North_Stop_PushButton
Local:2:I.Data.4
DI5
North_PushButton_Reset_PM_Counter
Local:2:I.Data.5
3. The following table lists the the tag name, base tag and the
workstation device for the digital outputs used in the program
North_Conveyor:
Workstation
Device
Tag Name
Base Tag
(output)
DO0
North_Conveyor
Local:0:O.Data.0
DO1
North_PM_Alarm
Local:0:O.Data.1
4. The following table lists the the tag name, base tag and the
workstation device for the digital inputs used in the program
South_Conveyor:
Workstation
Device
Tag Name
DI6
South_Stop_PushButton
Local:2:I.Data.6
DI7
South_PushButton_Reset_Counter
Local:2:I.Data.7
DI8
South_Start_PushButton
Local:2:I.Data.8
DI9
South_PushButton_Reset_Timer
Local:2:I.Data.9
DI10
South_Coke_Loading_PushButton
Local:2:I.Data.10
DI11
South_PushButton_Reset_PM_Counter
Local:2:I.Data.11
5. The following table lists the the tag name, base tag and the
workstation device for the digital outputs used in the program
South_Conveyor:
Workstation
Device
Tag Name
Base Tag
(output)
DO5
South_Conveyor
Local:0:O.Data.5
DO6
South_PM_Alarm
Local:0:O.Data.6
10--23
10--24
Lesson
11
Tip "
Mnemonic
JSR
SBR
RET
Jump to Label
JMP
Label
LBL
MCR
UID
UIE
Temporary End
TND
Disable a rung
AFI
No Operation
NOP
11--2
Subroutine Usage
Tell students another reason for using
subroutines is to break up the logic of
large or complex programming tasks into
multiple routines or subroutines.
Tell students these tasks are also
examples of parameters that may be
passed from the JSR to the SBR.
Output Instruction
The SBR instruction identifies the tags that store the incoming
parameters.
E 2007 Rockwell Automation, Inc. All rights reserved.
Tip "
11--3
Input Instruction
Output Instruction
Tip "
Mention that as with nesting branches,
nesting subroutines allows the
placement of one occurrence inside
another.
11--4
SBR
SBR
SBR
action_2
action_3
JSR
JSR
RET
RET
RET
Output Instruction
An LBL instruction is the target of the JMP instruction that uses the
same reference. Each label name must be unique within a routine.
The LBL instruction is an input instruction:
Input Instruction
11--5
Output Instruction
11--6
Output Instruction
11--7
Output Instruction
Tip "
11--8
Input Instruction
Heres How
To demonstrate:
1. Go online to the controller with
MPC_1756R_DEM1.acd file.
2. Review the JSR, SBR, RET, JMP,
LBL, MCR, UID, UIE,TND, AFI and
NOP instructions.
Example
11--9
The SBR instruction receives Height, Width, and Length from the
JSR instruction that calls the main routine, a major fault occurs.
Apply JSR instructions to get the program to jump to the other
routines from the main routine, when there is more than one
routine in a program.
11--10
Example
Example
Emphasize the criticality of correctly
programming ladder logic within MCR
zones to avoid programming errors.
11--11
MCR Instruction
The following graphic shows an example of an MCR instruction. In
this example, note the following conditions:
When the first MCR instruction is enabled (Switch_13 enables the
rung), the rungs in the MCR zone are scanned for normal true or
false conditions.
When the MCR zone is disabled, the controller still scans rungs
within the MCR zone, but scan time is reduced because
non-retentive outputs in the zone are disabled. The
rung-condition-in is false for all the instructions inside of the
disabled MCR zone.
11--12
Example
Tell students that UID and UIE
instructions are used primarily in
projects that contain multiple periodic
tasks.
Example
Emphasize that the next 3 instructions,
TND, AFI, and NOP are intended more
for troubleshooting or debugging ladder
logic, rather than normal programming.
TND Instruction
The following graphic shows an example of a TND instruction. In
this example, the controller will stop scanning at the TND and move
to the end of the routine:
Example
Point out that the AFI instruction will only
affect the rung where it is contained. It
will not affect the timer or the bits on the
previous or subsequent rungs.
Example
Tell students the NOP instruction is
useful when testing an output to
ensure it is operational. It may also be
used to troubleshoot individual
instructions on a branch.
11--13
AFI Instruction
The following graphic shows an example of an AFI instruction. In
this example, the AFI instruction will make the rung false and the
output will not be enabled:
NOP Instruction
The following graphic shows an example of a NOP instruction. In
this example, note the following conditions:
The NOP instruction is used as a place holder for future editing.
The Amber_Light_7 tag will be on all the time regardless of the
.DN bit.
11--14
11--15
Tip "
Description
Raw_Material_Coke
Raw_Material_Pellets
Tip "
Tip "
A retentive timer should time each raw material loaded into a skip
Tip "
11--16
Tip "
Tip "
The output indicator should be a red light on the workstation for each
raw material.
Tip "
travelling time.
The timer will represent one skip car travelling to the furnace top to
dump material and the other skip car travelling to the ground to be
loaded with more material.
Tip "
Raw Material
Loaded in the
Blast Furnace
Skip Car
Coke Loaded on
the Conveyor
11--17
Blast Furnace
Conveyor Taking
Coke to Stockhouse
Iron
Trough
Scale Readout
Molten Iron
Hot Metal Car
For help performing steps in this exercise, see the associated job
aid(s).
Directions:
1. Open the MPC_1756r_A1.acd file.
2. Open the MainRoutine and verify the routine.
3. Did you receive any errors or warnings?
4. How many JSR instructions are in the MainRoutine and what are
the user-created names of these instructions?
5. What is the tag name and base tag of the output that will be
enabled when the 2 JSRs are enabled?
11--18
11--19
11--20
Answers
Exercise A
3. No, there are no errors or warnings.
4. There are two JSR instructions named Raw_Material_Coke and
Raw_Material_Pellets in the MainRoutine.
5. The output tag name that will be enabled when the 2 JSRs are
enabled is JSRs_Initialized assigned to the base tag
Local:0:O.Data.3.
7. Yes, you should receive an error in the subroutine
Raw_Material_Coke that states Rung 0: Empty rung.
9. Yes, you should receive an error in the subroutine
Raw_Material_Pellets that states Rung 0: Empty rung.
14. Refer to the Project Example on the next page for one possible
way to modify ladder logic to jump to subroutines with operator
control after each process.
11--21
Project Example
The following graphic shows the MainRoutine. This is one possible
way to modify ladder logic to jump to subroutines with operator
control after each process:
11--22
Lesson
12
12--2
GSV/SSV Parameters
GSV/SSV instructions operate on the values for these parameters:
Class
Instance
Attribute
Source (SSV) or destination (GSV)
Class
The class is the category or type of object that is accessed:
Category
AXIS
CONTROLLER
CONTROLLERDEVICE
Controller hardware
CST
DF1
FAULTLOG
MESSAGE
MODULE
MOTIONGROUP
PROGRAM
ROUTINE
Instance of a routine
SERIALPORT
TASK
WALLCLOCKTIME
12--3
Instance
Note that this is one reason that naming
I/O modules with a descriptive name
(using purpose or location, for example)
is beneficial.
Specific Component
Attribute
The attribute is the particular property or value that is retrieved or
set:
Property to Monitor
Source or Destination
Add that the layouts of the required
source or destination data types are
detailed in the documentation reference
guide and in the online Help system.
12--4
Tag
User-Defined
Data Type
12--5
Fault Routine
Icon
Fault Routine Code
Status Flags
Stress that most controller values are
accessed using GSV and SSV
instructions.
Controller status and arithmetic status flags can also be examined for
specific data.
First scan
S:FS
Minor fault
S:MINOR
12--6
Heres How
Download CCP153_1756R_DEM6.acd
to the controller in slot 1. Open the
routines. Demonstrate how the GSV
instruction operates and then show
students how to go to the tag files to see
the data and how its mapped.
Overflow
S:V
Zero
S:Z
Negative
S:N
Carry
S:C
12--7
10. Access the Contents section of the online Help system and search
for GSV/SSV objects.
Rev. February 2007
12--8
14. In the program-scoped tags collection, access the tag that you
identified in Step 9.
15. What is the approximate value of the last scan time?
21. In the program-scoped tags, access the tag that you identified in
Step 20. and examine its structure.
22. Continue monitoring this tag. To simulate parts on a conveyor
passing the photo-eye, flip switch 12 (DI12) from left to right
three times.
23. What is the value of Fault_Data.Type?
12--9
25. In the Contents section of the online Help system, search for
minor fault types and codes.
26. According to the type and code, describe the fault that is
occurring?
28. What is the approximate value of the last scan time now?
29. Compare the value of the last scan time to the value identified for
Step 15. (approximately 200 microseconds).
30. Based on your answer, why would you want to clear a minor
fault?
31. Verify that the selector switch DI12 is set to the left.
32. Go offline.
12--10
Answers
Exercise A
6. The object being monitored is Program.
7. The specific instance being monitored is This, or the open
program.
8. The specific program-related data being monitored is
LastScanTime.
9. This data is being stored in the Program_Last_Scan_Time tag.
12. The data is a DINT value.
13. The LastScanTime is the last execution time recorded for the
program. Time is in microseconds.
15. Running in a ControlLogix 5563 controller, the program takes
approximately 50 to 80 microseconds to scan.
17. The class or type of data the GSV instruction is retrieving is
Program.
18. The specific instance being monitored is This, or the open
program.
19. The specific program-related data being monitored is
MinorFaultRecord.
20. This data is being stored in one member of the Fault_Data tag.
23. The value of Fault_Data.Type is 4.
24. The value of Fault_Data.Code is 4.
26. An arithmetic overflow has occurred in an instruction. The error
can be fixed by examining arithmetic operations (order) or
adjusting values.
27. No. A minor fault does not affect the control of the application
or process.
28. The scan time has doubled.
30. Scan time and execution are affected by minor faults.
Lesson
13
Force Functions
Forcing: A software function that allows a user to enable or disable
an input or output independent of the executable programming
language.
Forcing an I/O value can be used for any of the following
troubleshooting situations:
Checking field wiring
13--2
Tip "
State of Forces
exist in a project?
In the graphic,
explain that the state of
Forces
forces is displayed
Drop-Down
in the Online toolbar,
List
but individual forced
I/O are found in the ladder logic.
13--3
I/O Forces
Indicator
And the
background color
is . . .
Gray
None
Purple
Solid yellow
No Forces
Red
Flashing yellow
Forces
Red
Solid yellow
Emphasize that
the input is forced
on and the
output is forced
off. In the MOV
instruction, point
out that the analog
input value is
forced to a
different value.
13--4
Forced Value
CompactLogixt
Force LED
FORCE
FlexLogixt
Force LED
Off
Amber
Flashing Amber
13--5
Toggling Bits
Point out that after an internal bit is
toggled, it is acted on by the projects
programming language, just like any
other part of the project.
Toggling an internal bit changes the binary value of that bit. For
example, if a bit with a value of 0 is toggled, it will have a new value
of 1.
A tag of BOOL data type can be toggled directly from the instruction
in the Ladder editor:
Toggle a Bit by
Changing Its Value
Tip "
13--6
Heres How
Toggle bits
1. Go online to the
CCP153_1756R_DEM13.acd
project.
13--7
In this exercise, you will practice forcing I/O values and toggling bits
using RSLogix 5000 software.
For help performing steps in this exercise, see the associated job
aid(s).
Directions:
1. List the situations that might determine when forcing is used:
13--8
13--9
23. Disable all forces. Notice that all of the forces remain in the
program; however, they are no longer enabled.
24. What happens to the digital and analog I/O values?
25. Go offline.
13--10
Answers
Exercise A
1. Situations when forcing might be used include:
Lesson
14
Troubleshooting Logix5000
Controller Problems
What You Will Learn
Knowing how to properly address each type of fault will help you
return a system to proper order with minimal downtime.
Controller LEDs
Hardware
3.
3.
Software
1.
1.
2.
14--2
Minor fault
Non-Recoverable Major Fault
Non-Recoverable Major Fault: A fault within the controller that is
severe enough to shut it down. Hardware failure causes such a fault.
-- On
-- Off
-- Hold
The controller OK LED turns solid red.
The word Faulted is displayed in the Online toolbar.
Solid Red
14--3
-- Power loss
-- Loss of critical I/O
-- Array subscript errors
Recoverable Major Fault Processing: Level 1
When a recoverable major fault first occurs, the following changes
take place in the system:
A major fault bit is set in the controller.
Any user-programmed fault routines are executed:
-- Program-level fault routine
-- Controller-fault handler
Fault Routine
Tell students that the fault routine is
created in the program and assigned.
Additionally, a GSV instruction can be
used to retrieve the fault code and store
it in a tag.
14--4
Program
Main Routine
Subroutine
Flashing Red
14--5
If any of the faults are not cleared by the controller fault handler,
14--6
With a minor fault, the following changes take place in the system:
The program scan and normal I/O control continues.
Normal
Operating
State
Solid Green
14--7
14--8
CompactLogixt
Controller Keyswitch
FlexLogixt Controller Keyswitch
Tip "
Heres How
Download CCP153_1756R_DEM7.acd
to the controller in slot 1.
Beginning with tab two of the
troubleshooting guide, identify and clear
the major fault. Be sure to refer to the
software procedure for clearing the fault
in the appendix. Emphasize that you
must identify the cause of the fault and
remove it before clearing it. Do not save
the changes to the project.
This procedure does not clear the major fault log in the software. The
fault log is displayed on the Major Faults tab of the Controller
Properties dialog box.
To troubleshoot Logix 5000 controller problems by performing the
following actions:
Identify a fault type
Resolve a non-recoverable major fault
Find and clear a recoverable major or minor fault
As your instructor demonstrates these procedures, follow along in
the associated job aid(s).
14--9
Exercise: Troubleshooting
Logix5000 Controller Problems
Exercise A
Tip "
14--10
9. You discussed the cause of this fault with the project programmer.
The corrective action decided is to increase the task watchdog
timer value to 500.
10. Clear the fault.
Tip "
Exercise B
14--11
Tip "
9. You have discussed the cause of this fault with the project
programmer. Correct the cause of the fault by changing the
Record tag properties. Make the tag an array of 400.
10. Clear the fault.
Tip "
14--12
Exercise C
Directions:
The following changes have taken place in the system:
Outputs have changed. They are all off.
Solid Red
Tip "
14--13
4. After you replace the controller in the chassis and turn the power
back on, you notice that the I/O light is off. What might be the
problem if the I/O light is off?
Tip "
14--14
Answers
Exercise A
3. The controller OK LED is flashing red.
4. The fault is a recoverable major fault (Type 06, watchdog fault),
as indicated by the flashing OK LED.
6. Yes, the pilot lights are all off.
7. The outputs are set to the Program Mode -- in this case Off.
Program Mode may also be on or hold depending on safety
factors and the type of equipment.
8. The cause of the fault (recoverable major fault) is from the
expiration of the task watchdog. The software indicates that the
Assembly task contains the expired watchdog. According to the
error type and code (Type 06, Code 01), and using the online
Help, you can find Major Fault Types and Codes that list
corrective actions for each.
Tip "
Exercise B
5. The controller OK LED is flashing red.
6. The fault is a recoverable major fault (Type 04, program fault)
as indicated by the flashing OK LED.
7. The outputs are set to the Program Mode -- in this case Off.
Program Mode may also be on or hold depending on safety
factors and the type of equipment.
8. The fault was caused because the array subscript is too large
(e.g., ladder logic attempted to write a value to an array element
that is greater than the total number of elements), or the
CONTROL data type POS or LEN is invalid. An invalid array
subscript was specified. The software indicates that the
Assembly task contains the program fault. According to the
error type and code (Type 04, Code 20), and using the online
Help, you can find Major Fault Types and Codes that list
corrective actions for each.
Tip "
14--15
Exercise C
1. This is a non-recoverable major fault, also called a hardware
fault.
2. The outputs are set to the Fault Mode -- in this case Off. Fault
Mode may also be On or Hold depending on safety factors
and the type of equipment.
3. With ControlLogix RIUP capabilities, observing all safety
precautions, you can remove the faulted controller under power.
4. There are three possible reasons the I/O light might be off:
14--16
Appendix
+DC- 0
+DC- 0
+DC- 0
+DC- 0
+DC- 0
+DC- 0
+DC- 0
LABEL
DO0
DO1
OUT- 0
OUT- 1
OUT- 1
10
OUT- 3
DO3
12
OUT- 4
DO4
11
OUT- 5
6
8
14
DO2
DO5
16
28
DO2 = Local:0:O.Data.2
+DC- 1
30
DO3 = Local:0:O.Data.3
GND- 1
GND- 1
Not Used
32
DO4 = Local:0:O.Data.4
34
DO5 = Local:0:O.Data.5
BLACK
GND- 0
+DC- 1
+DC- 1
+DC- 1
+DC- 1
+DC- 1
+DC- 1
20
22
DO0 = Local:0:O.Data.0
24
DO1 = Local:0:O.Data.1
26
36
BLACK
RED
18
G
A
R
24VDC
RAU
Angle 1/2
Euclid, Ohio
Frac.1/64
.xx
Engineer
Date 05/01/99
.010
.xxx .005
.xxxx .0005
C
B
A
2/10/02
Changed Wire
Changed Wire
1/15/02
2/12/01
Added lights
Date
Approved By:
A--2
WORKSTATION
DEVICE
BLACK
BLACK
BLACK
BLACK
10
12
11
IN- 4
IN- 5
14
13
IN- 6
GND- 1
GND- 2
GND- 2
GND- 2
GND- 2
GND- 3
GND- 3
GND- 3
16
15
18
17
20
19
22
21
IN- 7
IN- 8
IN- 9
IN- 10
24
23
26
25
28
27
30
29
GND- 3
GND- 3
NOT USED
32
31
+ 24 DC
DI0
DI1
DI2
DI3
DI4
IN- 0
IN- 1
IN- 2
IN- 3
GND- 0
GND- 0
GND- 0
GND- 0
GND- 1
GND- 1
GND- 1
DI5
DI6
DI7
DI8
DI9
DI10
34
33
IN- 11
IN- 12
IN- 13
IN- 14
IN- 15
NOT USED
36
35
NOT USED
DI11
DI12
DI13
DI14
DI15
DI0 = Local:2:I.Data.0
DI8 = Local:2:I.Data.8
DI1 = Local:2:I.Data.1
DI9 = Local:2:I.Data.9
DI2 = Local:2:I.Data.2
DI10 = Local:2:I.Data.10
DI3 = Local:2:I.Data.3
DI11 = Local:2:I.Data.11
DI4 = Local:2:I.Data.4
DI12 = Local:2:I.Data.12
DI5 = Local:2:I.Data.5
DI13 = Local:2:I.Data.13
DI6 = Local:2:I.Data.6
DI14 = Local:2:I.Data.14
DI7 = Local:2:I.Data.7
DI15 = Local:2:I.Data.15
- NORMALLY OPEN PUSHBUTTON
- SELECTOR SWITCH
RAU
Angle 1/2
Euclid, Ohio
Frac.1/64
.xx
.xxx .005
.xxxx .0005
Engineer
.010
C
B
A
Changed Wire
Changed Wire
Added lights
1/15/02
2/12/01
Date
2/10/02
A--3
BLACK
RED
2
4
6
LABEL
WORKSTATION
DEVICE
10
12
OUT- 6
OUT- 7
DO6
14
13
GND- 0
+DC- 1
+DC- 1
+DC- 1
+DC- 1
+DC- 1
+DC- 1
+DC- 1
16
15
18
17
30
DO6 = Local:4:O.Data.6
GND- 1
GND- 1
NOT USED
32
DO7 = Local:4:O.Data.7
22
21
OUT- 8
OUT- 9
OUT- 10
24
23
OUT- 11
20
19
DO7
DO8
A
R
DO9
DO10
DO11
G
A
R
26
28
34
DO8 = Local:4:O.Data.8
36
DO9 = Local:4:O.Data.9
BLACK
RED
+DC- 0
+DC- 0
+DC- 0
+DC- 0
+DC- 0
+DC- 0
+DC- 0
DO10 = Local:4:O.Data.10
DO11 = Local:4:O.Data.11
24VDC
A
R
Angle 1/2
Euclid, Ohio
Frac.1/64
.xx
.010
.xxx .005
.xxxx .0005
Engineer
Date 05/01/99
C
B
A
Changed Wire
Changed Wire
Added lights
Approved By:
1/15/02
2/12/01
Date
2/10/02
A--4
AO1 (Channel 1)
AO0
Return
WORKSTATION
DEVICE
OUT- 1
OUT- 0
NOT USED
NOT USED
RTN- 1
RTN- 0
OUT- 3
OUT- 2
NOT USED
10
NOT USED
RTN- 3
12
11
RTN- 2
NOT USED
14
13
NOT USED
OUT- 5
16
15
OUT- 4
NOT USED
18
17
NOT USED
RTN- 5
20
19
RTN- 4
AO0 (Channel 0)
AO1
Return
AO0 = Local:7:O.Ch0Data
AO1 = Local:7:O.Ch1Data
RAU
Angle 1/2
Euclid, Ohio
Frac.1/64
.xx
.xxx .005
.xxxx .0005
Engineer
.010
Approved By:
Date 05/01/99
C
B
A
Rev.
Changed Wire
Changed Wire
Added lights
1/15/02
2/12/01
Date
2/10/02
A--5
AI1 (Channel 1)
AI0 Return
WORKSTATION
DEVICE
IN- 1/V
IN- 0/V
IN- 1/I
IN- 0/I
RET- 1
RET- 0
IN- 3/V
IN- 2/V
IN- 3/I
10
IN- 2/I
RET- 3
12
11
RET- 2
NOT USED
14
13
NOT USED
IN- 5/V
16
15
IN- 4/V
IN- 5/I
18
17
IN- 4/I
RET- 5
20
19
RET- 4
AI0 (Channel 0)
AI1 Return
AI0 = Local:8:I.Ch0Data
AI1 = Local:8:I.Ch1Data
Angle 1/2
Euclid, Ohio
Frac.1/64
.xx
.xxx .005
.xxxx .0005
Engineer
Approved By:
.010
C
B
A
Rev.
Changed Wire
Changed Wire
Added lights
2/10/02
1/15/02
2/12/01
Date
A--6
DI6
DI5
DI11
DO11
DI15
DI10
DO8
DI14
DO5
DI13
DI12
DO10
DI7
DI3
DO9
DI9
DO4
DO6
DO3
DO7
DI2
DI1
DI8
DO2
DI4
DO1
DI0
DO0
Ch01 Analog
Meter Output
Ch00 Analog
Meter Output
Ch01 Analog
Meter Input
Ch00 Analog
Meter Input
Appendix
B--2
The devices used in the workstation have the following I/O base
tags:
Module
Digital Input
wired to Slot 2
Digital Output
wired to Slot 0
Digital Output
wired to Slot 4
Workstation Device
DI0
DI1
DI2
DI3
DI4
DI5
DI6
DI7
DI8
DI9
DI10
DI11
DI12
DI13
DI14
DI15
D00
D01
D02
D03
D04
D05
D06
D07
D08
D09
D010
D011
Local:2:I.Data.0
Local:2:I.Data.1
Local:2:I.Data.2
Local:2:I.Data.3
Local:2:I.Data.4
Local:2:I.Data.5
Local:2:I.Data.6
Local:2:I.Data.7
Local:2:I.Data.8
Local:2:I.Data.9
Local:2:I.Data.10
Local:2:I.Data.11
Local:2:I.Data.12
Local:2:I.Data.13
Local:2:I.Data.14
Local:2:I.Data.15
Local:0.O.Data.0
Local:0.O.Data.1
Local:0.O.Data.2
Local:0.O.Data.3
Local:0.O.Data.4
Local:0.O.Data.5
Local:4:O.Data.6
Local:4:O.Data.7
Local:4:O.Data.8
Local:4:O.Data.9
Local:4:O.Data.10
Local:4:O.Data.11
Appendix
Node Assignments
If you are in an environment with multiple workstations on a
ControlNet or EtherNet/IP network, ask your network specialist to
supply the following information:
EtherNet or EtherNet/IP
Network
Workstation
Number
1756-ENET IP Address
ControlNet Network
1756-CNB
or
1756- CN2
Node
Address*
1784- PCICS
Card Node
Address
1784- PCC
Card Node
Address
1784-KTCX15 Interface
Card
10
C--2
Node Assignments
1336 IMPACT
CompactLogix
ControlLogix
DH+
FactoryTalk
FlexLogix
Logix5550
PanelView
PHOTOSWITCH
RediSTATION
RSLogix
RSNetWorx
SLC
Ultra
PowerPoint
Windows NT