Vdocuments - MX - Student Manual Abt CCP tsm143 Rslogix 5000 Level 3 Project Developmentpdf

8/16/2019 Student Manual _ ABT-CCP-TSM143 _ RSLogix 5000, Level 3 _ Project Development.
pdf
RSLogix™ 5000
Level 3: Project
Development
Student Manual
http://slidepdf.com/reader/full/student-manual-abt-ccp-tsm143-rslogix-5000-level-3-project-developmentpdf 1/375
8/16/2019 Student Manual _ ABT-CCP-TSM143 _ RSLogix 5000, Level 3 _ Project Development.pdf
Important User Information

This documentation, whether, illustrative, printed, “online” or electronic (hereinafter “Documentation”) is intended for
use only as a learning aid when using Rockwell Automation approved demonstration hardware, software and firmware.
The Documentation should only be used as a learning tool by qualified professionals.
The variety of uses for the hardware, software and firmware (hereinafter “Products”) described in this Documentation,
mandates that those responsible for the application and use of those Products must satisfy themselves that all necessary
steps have been taken to ensure that each application and actual use meets all performance and safety requirements,
including any applicable laws, regulations, codes and standards in addition to any applicable technical documents.
In no event will Rockwell Automation, Inc., or any of its affiliate or subsidiary companies (hereinafter “Rockwell
Automation”) be responsible or liable for any indirect or consequential damages resulting from the use or application of
the Products described in this Documentation. Rockwell Automation does not assume responsibility or liability for
damages of any kind based on the alleged use of, or reliance on, this Documentation.
No patent liability is assumed by Rockwell Automation with respect to use of information, circuits, equipment, or
software described in the Documentation.
Except as specifically agreed in writing as part of a maintenance or support contract, equipment users are responsible for:
 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.
Identifies information that is critical for successful

application and understanding of the product.
Identifies information about practices or circumstances

that can lead to personal injury or death, property
damage, or economic loss. Attentions help you:
 identify a hazard
 avoid a hazard
 recognize the consequence
Important User Information
Labels may be located on or inside the drive to alert

people that dangerous voltage may be present.
Labels may be located on or inside the drive to alert

people that surfaces may be dangerous temperatures.
Comment Form
Email: ratps@ra.rockwell.com
or Fax: 440.646.4425
Page 1 of
Date:
Contact Information:
Name:
Company and Location:
Phone: Email:
Comments (include lesson title, if applicable):
Course or Product Name (Important):
Page 2
Table of Contents
Introduction
Course Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I
Course Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I
Who Should Attend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . II
Agenda . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . II
Meeting Course Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . III
Student Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IV
Hands-On Exercises . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IV
Certificate Candidates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IV
Configuration and Programming Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . V
ControlLogix/RSLogix 5000 Curriculum Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . V
Lessons
Updating Logix5000 Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1- 1

What You Will Learn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--1
When You Will Do This . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--1
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--1
Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--1
Updating Module Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--1
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--3
Demonstration Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--3
Exercise: Updating Logix5000 Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1- 5

Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--5
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--6
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--8
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--8
Creating and Organizing a New RSLogix 5000 Project . . . . . . . . . . . . . . . . . . . . . . . 2- 1

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--1
Key Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--1
Project Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--1
Default Project Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--2
Creating a New Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--2
Continuous Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--3
Watchdog Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--3
ii Table of Contents
Inhibited Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--4

Creating a Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--4
Adjusting a Program Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--5
Actual Program Scan Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--5
Creating a Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--6
Program Control Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--8
System Overhead Timeslice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--8
Asynchronous Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--9
Project Organization Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--10
Example: Project Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--11
Verifying Tasks, Programs, and Routines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--11
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--12
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--12
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--13
Exercise: Creating and Organizing a New RSLogix 5000 Project . . . . . . . . . . . . . . . 2-15

Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--15
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--17
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--18
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--18
Creating a Periodic Task in an RSLogix 5000 Project . . . . . . . . . . . . . . . . . . . . . . . . 3- 1

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--1
Task Type Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--1
Periodic Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--2
Example: Periodic Task Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--2
Periodic Task Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--4
Period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--4
Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--5
Scan Time Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--6
Periodic Task Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--6
Example: Periodic Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--6
Example: Periodic Task and Continuous Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--7
Example: Multiple Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--7
Example: Equal Priorities (Timeslicing) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--7
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--8
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--8
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--9
Table of Contents iii
Exercise: Creating a Periodic Task in an RSLogix 5000 Project . . . . . . . . . . . . . . . . 3-11

Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--11
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--12
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--14
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--14
Organizing Data in an RSLogix 5000 Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 1

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--1
Controller Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--1
Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--2
Memory Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--3
Tag Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--4
Creating a Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--4
Tag Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--5
Data Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--5
Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--5
Defining an Alias Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--6
Produced and Consumed Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--6
Creating an Array of Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--7
Example: Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--7
Array Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--8
Example: Three Dimensional Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--8
Array Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--9
Numeric Element Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--9
Example: Numeric Element Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--9
Example: Numeric Element Addressing for Multiple Dimensions . . . . . . . . . . . . . . . . . . . . . . . 4--9
Variable Element Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--10
Example: Variable Element Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--10
Numeric Bit Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--10
Example: Numeric Bit Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--10
Variable Bit Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--11
Example: Variable Bit Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--11
Array Addressing Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--11
Verifying Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--11
Monitoring and Editing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--11

Monitor Tags Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--12
Tags and Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--12
Display Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--12
Example: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--12
Monitoring and Editing Tag Values through a Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--13
Example: Ladder Logic Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--13
Example: Function Block Diagram Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--14
Monitoring and Editing Tag Values in the Watch Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--15
iv Table of Contents
Quick Watch Tag Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--15

Persistent Quick Watch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--16
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--17
Monitor Data in RSLinx Classic Professional Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--17
Your Turn . . . . . . . . . . . . . . . . . . ......... ......... ......... ........ ......... ... 4--17
Data Access Control . . . . . . . . . ......... ......... ......... ........ ......... ... 4--18
Data Access Control Benefits ......... ......... ......... ........ ......... ... 4--18
Your Turn . . . . . . . . . . . . . . . . . . ......... ......... ......... ........ ......... ... 4--18
Exercise: Organizing Data in an RSLogix 5000 Project . . . . . . . . . . . . . . . . . . . . . . 4- 19

Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--19
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--21
Exercise B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--21
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--21
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--22
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--22
Exercise B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--25
Creating a User-Defined Data Type in an RSLogix 5000 Project . . . . . . . . . . . . . . . . 5-1

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--1
Creating a User-Defined Data Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--1
Example: User-Defined Data Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--2
Example: Arrays and User-Defined Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-- 3
User-Defined Data Type Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-- 3
User-Defined Data Type Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-- 3
Examples: User-Defined Data Type Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--3
Exporting and Importing User-Defined Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--4
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--5
Exercise: Creating a User-Defined Data Type in an RSLogix 5000 Project . . . . . . . . 5- 7

Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--7
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--9
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--10
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--10
Entering, Editing, and Verifying Ladder Logic in an RSLogix 5000 Project . . . . . . . . 6- 1

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--1
ASCII Mnemonic Editing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--2
Table of Contents v
Configuring Ladder Logic Quick Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--2

Copying and Reusing Ladder Logic Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--2
Example: Copied Ladder Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--3
Other Short-Cuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--4
Verifying a Project or a Project Component Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--4
Online Safety Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--4
Performing Online Ladder Logic Edits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--5
Finalize Edits Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--6
Edit Zone Markers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--7
Online Editing in a Multiple-User Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--8
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--9
Exercise: Entering, Editing, and Verifying Ladder Logic in an RSLogix 5000 Project 6- 11
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--11
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--13
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--14
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--14
Communicating with a Local 1756-I/O Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7- 1

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--1
Electronic Keying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--1
Keying Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--2
Example: Exact Match Keying Prevents Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--2
Example: Compatible Keying Prevents Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--3
Example: Compatible Keying Allows Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--3
Disabled Keying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--4
Asynchronous I/O Update Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--4
Digital Module Multicasting Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--4
RPI (Requested Packet Interval) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--4
COS (Change of State) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--5
Example: RPI and COS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--5
Analog Module Multicasting Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--5
RTS (Real Time Sampling Rate) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--6
Output States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--6
Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--7
Diagnostic Latching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--8
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--9
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--10
Exercise: Communicating with a Local 1756-I/O Module . . . . . . . . . . . . . . . . . . . . . 7- 11

Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--11
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--13
vi Table of Contents
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--14
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--14
Configuring a Logix5000 Controller to Produce and Consume Data . . . . . . . . . . . . . 8-1

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8--1
Scheduled Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8--1
Produced and Consumed Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8--2
Produced and Consumed Tag Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8--2
Configuring a Produced Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8--3
Adding a Controller to an I/O Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8--4
Configuring a Consumed Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8--4
Tag Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8--6
Produced and Consumed Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8--7
Produced Tag Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8--7
Produce/Consume Tag RPI Limits Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8--8
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8--10
Exercise: Configuring a Logix5000 Controller to Produce and Consume Data . . . . . 8- 11

Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8--11
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8--13
Exercise B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8--13
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8--14
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8--16
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8--16
Exercise B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8--18
Configuring Logix5000 Controllers to Share Data over an EtherNet/IP Network . . . . 9- 1

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9--1
EtherNet/IP Network Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9--1
Overview of IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9--2
Private IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9--3
Subnets and Subnet Masks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-- 3
How a Subnet Mask Operates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-- 4
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9--4
Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9--5
Configuration Overview and Software Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9--6
Adding an EtherNet/IP Module and Controller to an I/O Configuration . . . . . . . . . . . . . . . . . . . 9--6
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9--7
Table of Contents vii
Exercise: Configuring Logix5000 Controllers to Share Data over an EtherNet/IP

Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9- 9
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9--9
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9--11
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9--12
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9--12
Communicating with a 1756-I/O Module over an EtherNet/IP Network . . . . . . . . . . . 10-1

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10--1
Effect of RPI on EtherNet/IP Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10--1
Example: Effect of RPI on EtherNet/IP Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10--1
Communications Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10--2
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10--2
Example: No Rack Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10--2
Example: Rack--optimized Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10--3
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10--4
Exercise: Communicating with a 1756-I/O Module over an EtherNet/IP Network . . . . 10- 5

Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10--5
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10--6
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10--8
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10--8
Creating an Event Task in an RSLogix 5000 Project . . . . . . . . . . . . . . . . . . . . . . . . . 11- 1

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--1
Task Type Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--1
Event Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--2
Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--2
Event Task Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--2
Event Task Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--3
Trigger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--4
Consumed Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--4
Module Input Data State Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--5
1756 Local and Remote Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--5
Quick-Response Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--5
Short-Duration Input Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--6
Synchronized-Execution Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--6
Single Bit Triggers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--6
Module Input Data State Change -- Design Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--7
Automatic Output Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--7
viii Table of Contents
Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--8
Scan Time Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--9
Event Task Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--9
Event Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-- 9
IOT Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--10
UID/UIE Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--10
CPS Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--11
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--12
Exercise: Creating an Event Task in an RSLogix 5000 Project . . . . . . . . . . . . . . . . . 11-13

Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--13
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--13
Exercise B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--14
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--16
Exercise C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--16
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--18
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--20
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--20
Exercise B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--21
Exercise C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--23
Retrieving and Setting Logix5000 Controller Status Values with GSV/SSV

Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12- 1
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--1
Monitoring Controller System Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--1
GSV/SSV Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-- 2
Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--2
Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--2
Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--2
Source or Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-- 3
Example: GSV Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--4
Example: SSV Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-- 5
Status Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--5
Controller Status Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--6

Arithmetic Status Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--6
Fault Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--6
Non-Recoverable Major Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--7
Recoverable Major Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--7
Recoverable Major Fault Processing: Level 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--8
Fault Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--8
Controller Fault Handler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--8
Recoverable Major Fault Processing: Level 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--9
Table of Contents ix
Multiple Recoverable Major Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--10

Common Major Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--10
Minor Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--10
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--12
Exercise: Retrieving and Setting Logix5000 Controller Status Values with GSV/SSV
Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12- 13
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--13
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--14
Exercise B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--14
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--15
Exercise C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--15
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--17
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--18
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--18
Exercise B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--19
Exercise C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--22
Programming a BTD Instruction in an RSLogix 5000 Project . . . . . . . . . . . . . . . . . . 13-1

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13--1
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13--3
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13--3
BTD Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13--3
Your Turn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13--4
Exercise: Programming a BTD Instruction in an RSLogix 5000 Project . . . . . . . . . . 13- 5

Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13--5
Status Attribute for the Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13--5
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13--6
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13--8
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13--8
Configuring a Logix5000 Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14- 1

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14--1
Unscheduled Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14--1
Messages to Logix5000 Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14--1
Messages to Other Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14--2
Configuring a Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14--2
x Table of Contents
Read, Write, and Block Transfer Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14--3

Creating and Entering a Numeric Communications Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14--4
CIP Generic Message Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14--4
Message Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14--5
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14--6
Exercise: Configuring a Logix5000 Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14- 7

Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14--7
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14--9
Exercise B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14--9
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14--11
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14--12
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14--12
Exercise B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14--14
Developing an Add-On Instruction in Ladder Diagram . . . . . . . . . . . . . . . . . . . . . . . 15- 1

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--1
Add-On Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--1
Example of an Add-On Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--2
An Add-On Instruction Uses a Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--3
Key Parts of the Definition of an Add-On Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-- 4
Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--5
Local Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--5
Routine “Type” Control Editable in AOI Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--6
Changes to the Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--7
Add-On Instruction Design Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--8
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--9
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--9
Planning the Parameters of an Add-On Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--9
Your Turn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--9
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--10
Language for the Logic Routine of the Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--10
Organization of the Logic Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--10
Optional Scan Mode Routines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--11
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--12
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--12
Deciding If You Need an EnableInFalse Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--12
Your Turn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--12
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--13
Accessing Parameters via Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--13
Editing an Add-On Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--14
Exporting and Importing an Add-On Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--14
Table of Contents xi
Online Safety Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--15

Referenced Add-- On Instructions and User-Defined Data Types . . . . . . . . . . . . . . . . . . . . . . . 15-- 16
Example: When Not To Include Referenced Add-On Instructions and User-Defined Data Types 15--16
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--16
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--17
Creating an Add-On Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--17
Enter the General Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--17
Enter the Definition Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--18
Create the Parameters and Local Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--18
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--19
Looking for Previously Developed Add-On Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--19
Search the Sample Code Library (samplecode.rockwellautomation.com) . . . . . . . . . . . . . . . . . 15-- 19
Example of Search Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--19
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--20
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--20
Using the Detect_Jam Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--20
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--20
Exercise: Developing an Add-On Instruction in Ladder Diagram . . . . . . . . . . . . . . . 15-21

Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--21
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--22
Exercise B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--23
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--23
Exercise C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--24
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--27
Exercise D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--27
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--28
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--30
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--30
Exercise B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--31
Exercise B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--31
Exercise C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--31
Exercise C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--31
Exercise D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--33
Managing RSLogix 5000 Project Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16- 1

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16--1
File Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16--1
Exporting a .acd Project File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16--2
Importing a .l5k Text File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16--3
Importing a .l5x XML File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16--4
Multiple Backup Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16--5
Compare Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16--5
xii Table of Contents
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16--6

Exercise: Managing RSLogix 5000 Project Files . . . . . . . . . . . . . . . . . . . . . . . . . . . 16- 7

Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16--7
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16--9
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16--10
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16--10
Allocating Connections in a Logix5000 System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17- 1

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17--1
Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17--1
Connection Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17--1
Conserving Connections by Grouping Produced Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17--2
Example: Connection Requirements for Tags vs. an Array . . . . . . . . . . . . . . . . . . . . . . . . . . . 17--2
Message Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17--3
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17--3
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17--4
Exercise: Allocating Connections in a Logix5000 System . . . . . . . . . . . . . . . . . . . . 17- 5

Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17--5
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17--5
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17--6
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17--6
Integrated Practice — Developing an RSLogix 5000 Project . . . . . . . . . . . . . . . . . . . 18-1

Exercise: Integrated Practice — Developing an RSLogix 5000 Project . . . . . . . . . . . 18- 3

Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18--3
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18--8
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18--10
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18--10
Optional Lessons
Configuring Logix5000 Controllers to Share Data over a ControlNet Network . . . . . 19-1

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19--1
Key Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19--1
ControlNet Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19--1
Table of Contents xiii
Cable System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19--3

Network Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19--4
Scheduled Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19--4
Unscheduled Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19--4
Information Exchange on the ControlNet Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19--5
Network Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19--5
NUT (Network Update Time) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19--5
Example: NUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19--6
SMAX (Scheduled Maximum Node) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-- 6
Example: SMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19--7
UMAX (Unscheduled Maximum Node) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19--7
Example: UMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19--8
Media Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19--8
Update Intervals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19--9
RPI (Requested Packet Interval) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19--9
API (Actual Packet Interval) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19--9
Example: RPI and API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19--10
Configuration Overview and Software Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19--10
Adding a ControlNet Module and Controller to an I/O Configuration . . . . . . . . . . . . . . . . . . . . 19--11
Scheduling a New ControlNet Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19--11
Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19--14
Exercise: Configuring Logix5000 Controllers to Share Data over a ControlNet

Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19- 15
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19--15
........................................................................ 19--15
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19--17
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19--18
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19--18
Communicating with a 1756-I/O Module Over a ControlNet Network . . . . . . . . . . . . 20-1

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20--1
ControlNet Remote I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20--1

Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20--2
Exercise: Communicating with a 1756-I/O Module Over a ControlNet Network . . . . . 20- 3

Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20--3
How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20--4
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20--6
Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20--6
xiv Table of Contents
Appendices
I/O Wiring Diagrams For The Assembly Application . . . . . . . . . . . . . . . . . . . . . . . . . A- 1

Slot 0 -- 1756-OB16D Digital Output Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A--1
Slot 2 -- 1756-IB16D Digital Input Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A--2
Slot 4 -- 1756-OB16D Digital Output Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A--3
........................................................................ A--3
Slot 7 -- 1756-OF6VI Analog Output Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A--4
Slot 8 -- 1756-IF6I Analog Input Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A--5
ControlLogix Workstation I/O Device Assignments . . . . . . . . . . . . . . . . . . . . . . . . . B- 1

Local I/O Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B--2
Node Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C- 1
Course Overview I
Course Overview
Course Purpose Upon completion of this course, given a functional specification for
an RSLogix 5000 application, you will be able to develop a project
to meet the requirements of the specification.
This course covers tasks common to the following controllers, which

all use the Logix5000 control engine, or operating system:
 ControlLogix controllers
 CompactLogix controllers
 SoftLogix controllers
 DriveLogix controllers
This course builds upon your knowledge of common controller terms

and operation and your experience with basic ladder logic
programming.
This course presents a deeper understanding of project development

tasks that are common to all Logix5000 controllers. Such tasks
include organizing tasks and routines, organizing controller data,
configuring modules, and sharing data.
You will also use Producer/Consumer technology to multicast input

and output devices, share data between controllers, and control
remote I/O.
Who Should Attend Individuals who need to develop RSLogix 5000 projects for any
Logix5000 controller should attend this course.
Activity: Introduce yourself, say the company you work for, and tell
the instructor and others what you hope to take away from this
course.
II Course Overview
Prerequisites To successfully complete this course, the following prerequisites are

required:
 Ability to perform basic Microsoft Windows tasks
 Completion of the RSLogix 5000 Level 1: ControlLogix System
Fundamentals course (Course No. CCP146), or completion of the
RSTrainer for ControlLogix Fundamentals computer-based
training course (9393-RSTCLX), or knowledge of common
controller terms and operation
 Completion of the RSLogix 5000 Level 2: Basic Ladder Logic
Programming course (Course No. CCP151) or the ability to write
basic ladder logic with common instructions, such as bit, timer,
counter, move, and comparison instructions
Question: Is everyone comfortable with these skills?
Agenda This course consists of the following lessons:
Day 1
15 minutes  Course Overview
20 minutes (40 minutes with optional
exercise)  Updating Logix5000 Firmware
90 minutes  Creating and Organizing a New RSLogix 5000 Project
60 minutes  Creating a Periodic Task in an RSLogix 5000 Project
160 minutes  Organizing Data in an RSLogix 5000 Project
30 minutes  Creating a User-Defined Data Type in an RSLogix 5000 Project
Day 2
60 minutes  Entering, Editing, and Verifying Ladder Logic in an
RSLogix 5000 Project
185 minutes  Communicating with a Local 1756-I/O Module
90 minutes  Configuring a Logix5000 Controller to Produce and Consume
Data
90 minutes  Configuring Logix5000 Controllers to Share Data over an
EtherNet/IP Network
(continued)
Course Overview III
Day 3
45 minutes  Communicating with a 1756-I/O Module over an EtherNet/IP
Network
120 minutes  Creating an Event Task in an RSLogix 5000 Project
90 minutes 
Retrieving and Setting Logix5000 Controller Status Values with

GSV/SSV Instructions
60 minutes  Programming a BTD Instruction
105 minutes  Configuring a Logix5000 Message
Day 4
90 minutes  Developing an Add-On Instruction in Ladder Diagram
40 minutes  Managing RSLogix 5000 Project Files
60 minutes  Allocating Connections in a Logix5000 System
225 minutes  Integrated Practice -- Developing an RSLogix 5000 Project
120 minutes  Optional: Configuring Logix5000 Controllers to Share Data over
a ControlNet Network
65 minutes  Optional: Communicating with a 1756-I/O Module Over a
ControlNet Network
Meeting Course Objectives The following course structure is generally used to help you
understand the content and activities:
 One lesson is devoted to each task.
 Typical lesson includes most or all of these sections:
-- “What You Will Learn” -- lesson objectives
---- “Before You Begin” -- preparatory material

“Here’s How” - demonstration of procedures
-- “Exercise” -- opportunity to perform new skills, often in a
hands-on lab environment
-- “How Did You Do?” -- where to go for feedback on
performance
-- “Answers” -- answers to exercises
 Integrated practices provide an opportunity to perform tasks using
the skills obtained during the training.
IV Course Overview
Student Materials To enhance and facilitate your learning experience, the following
materials are provided as part of the course package:
 Student Manual, which contains the topical outlines and
exercises. Use this manual to follow presentations, take notes, and
work through your exercises.
 RSLogix 5000 and Logix5000 Procedures Guide, which provides
all of the steps required to complete basic RSLogix 5000 software
tasks that are common to all Logix5000 hardware platforms. By
following the procedures in this job aid, you can immediately
apply what is learned in the course to your own job.
 Logix5000 Controllers Design Considerations Reference Manual ,
which contains guidelines for designing a Logix5000 application.
 Logix5000 Documentation Reference Guide, which contains
several relevant technical publications. This searchable, electronic
resource contains the most frequently referenced programming
information and is a quick and efficient on-the-job resource.
Reference: Your instructor will show you these job aids now.
Hands-On Exercises Throughout this course, you will have the opportunity to practice the
skills you have learned through a variety of hands-on exercises.
These exercises focus on the skills introduced in each lesson.
You will also have the opportunity to combine and practice several
key skills by completing an integrated practice.
To complete the exercises and the integrated practice, you will use a
ControlLogix hardware workstation. Because the basic skills taught
in the course apply to all Logix5000 platforms, you can apply what
you have learned to the specific platform that you use in your plant.
Certificate Candidates If you are a candidate for a Certificate Exam, you must:
 Take notes
 Ask questions for clarification
 Follow along with demonstrations using the job aids
 Complete all labs
Tip " The Certificate Exam questions are scenario--based and may require
you to understand information from all of these areas.
To study for the exam, you must keep all class materials and your
written notes.
Course Overview V
Configuration and The configuration and programming examples shown in this course
Programming Examples are intended solely for purposes of example.
You will have different requirements associated with your

application. You must verify that the necessary steps have been
taken to meet all performance and safety requirements.

Reference: See the Important User Information in your Student
Manual for more details.
ControlLogix/RSLogix After completing this training, you may be interested in one or more
5000 Curriculum Map of the following courses:
 RSLogix Level 4: PhaseManager Project Design
[CCP711, 1 day]
 RSLogix 5000 Level 4: Motion Programming Using Ladder Logic
[CCN142, 3 days]
 GuardLogix Application Development [SAF-LOG101, 2 days]
Reference: See the curriculum map in the front of your Student

Manual for a complete listing of available ControlLogix/RSLogix
5000 courses.
VI Course Overview
Lesson 1
Note that this lesson briefly reviews Updating Logix5000 Firmware
prerequisite concepts before presenting
the firmware piece. Tailor this lesson as
needed.
What You Will Learn After completing this lesson, you should be able to update module
firmware.
When You Will Do This
You will perform these tasks in the following situations:

 You will need to update module firmware:
-- When installing a brand new ControlLogix controller
-- When upgrading to a newer version of RSLogix 5000
software to ensure hardware and software remain in lockstep
Before You Begin Review
The PowerPoint presentation Activity: Your instructor will briefly review uploading,
contains hidden slides that can downloading, and going online to a controller.
be used to conduct the review.
Topics include keyswitch positions;
uploading, downloading, and going
online; and interpreting a Updating Module Firmware
communications path.
To use all of the features of a new revision of RSLogix 5000
software, controller and servo module firmware must be in lock-step
State that customers can obtain the with software.
required revision levels at the
support.rockwellautomation.com/support
website for ControlFLASH. The firmware loaded in Logix5000 controllers and
Note that a minimum of one motion modules must match the version of
communications device is required RSLogix 5000 software you are using.
to update modules. Serial
communications can be
used, but data transfers
at the slowest rate.
There are three methods available for updating module firmware:
Method How Used Devices Supported Communication Supported

Standalone tool (can be
ControlFLASH Utility launched manually or through
RSLogix 5000 software). Controllers, communication Valid CIP path to device being
modules, I/O modules, updated (includes serial,
Integrated with RSLogix 5000
SERCOS drives, and other DeviceNet, ControlNet,
software. It automatically
AutoFlash Function devices. EtherNet/IP).
checks firmware during project
download.
(Continued)
Rev. August 2012 E 2012 Rockwell Automation, Inc. All rights reserved.
FW3sb56r
1--2 Updating Logix5000 Firmware
Method How Used Devices Supported Communication Supported

Supports local and remote
devices that:
 Are in the I/O tree and Supports all communication
Integrated on the controller configured as Exact Match. paths to devices in the
Firmware Supervisor CompactFlash card and runs  Support firmware upgrades controller I/O tree that also
without user intervention. via ControlFLASH. support ControlFLASH.
 Are at a hardware revision
that supports the firmware
stored for that device.
When updating a module’s firmware, note the

following key points:
 Updating a module will delete the current
module contents.
 Updating module firmware temporarily disables
the module from controlling other devices.
Evaluate
module maywhat portion(s)
control of starting
before a processanthe
update.
 Interrupting an update by disabling
communications or removing the module from
the chassis may damage the module.
Do not backflash a 1756-I/O module’s

firmware from firmware revision 3.x to 2.x .
Attempting to backflash or downgrade the
module’s firmware will irreversibly damage the
module. You must return modules damaged by an
attempt to backflash to firmware 2.x to Rockwell
Automation.
Do not flash a 1756-I/O module’s firmware

from firmware revision 2.x to 3.x . Attempting to
flash a module’s firmware will irreversibly
damage the module.
Do not backflash 1756-SOE (Sequence of

Events) modules at firmware revision 1.6 to
revision 1.5 or earlier. Backflashing SOE
modules at firmware revision 1.6 may cause the
SOE module to stop working and require that the
module be returned for repair.
E 2012 Rockwell Automation, Inc. All rights reserved. Rev. August 2012
FW3sb56r
Updating Logix5000 Firmware 1--3
Tip " If you have questions regarding the compatibility of RSLogix 5000
software with specific controllers or hardware modules, contact your
local distributor or Rockwell Automation Technical Support.
Here’s How
IMPORTANT: When performing
To update module firmware.
Exercise A, be sure to run the Activity: As your instructor demonstrates these procedures, follow
Quick Start video for the along in the associated job aid(s).
students on the overhead. This
will eliminate the need for
earphones or the distraction of
overlapping audio during the exercise.
Demonstration Checklist
IMPORTANT: To meet IACET CEU
requirements and fully
certificate students prepare
for the final exam,
you must demonstrate all lesson
objectives using the proper job aids. Pay attention to these critical aspects of the demonstration:
Use the steps below and the information
on the Demonstration Checklist to help - Download the first project and go online.
guide you during the demonstration:
- Download the second project to the controller.
IMPORTANT: Before performing this
demonstration, ensure that the controller
in slot 3 of your demonstration - What happens when the project is downloaded?
workstation has been back-flashed to
a firmware version below version 17. - How is this situation resolved?
Use the FW3_1756R_DEM1.acd file to - What tools are available for flashing module firmware?
download and go online to the controller
in Slot 1.
Use the FW3_1756R_DEM2.acd file to
download to the controller in slot 3.
When the firmware revision mismatch
occurs, show students how the
automatic firmware update feature
works.
Important: Emphasize that flashing
firmware will not be practiced in the lab.
FW3sb56r
1--4 Updating Logix5000 Firmware
FW3sb56r
Exercise: Updating Logix5000 Firmware 1--5
Exercise: Updating Logix5000

Firmware
Exercise A In this exercise, you will practice updating Logix5000 firmware.
Activity: As a group, you will view the Update a Module’s

Firmware Quick Start tutorial. The steps below will help you access
the file for later review or independent practice.
This exercise uses RSLogix 5000 Start Pages to

demonstrate the controller flashing procedure. Do
not perform this procedure on the workstation
unless authorized
perform to docan
this procedure Failure
so.make theto correctly
controller
inoperable.
Context:
Before flash updating the new ControlLogix controllers you recently

received, you will review the proper flash update procedure and
answer the corresponding questions.
Directions:
1. If it is closed, open RSLogix 5000 software.
2. View the Start Page.

3. Click the Learning Center tab.
4. From the How Do I? menu, select the Maintain folder.
5. View the Update a Module’s Firmware tutorial.
Tip " Although the video focuses on the CompactLogix platform, the basic
steps can be applied to any Logix5000 controller that supports flash
download.
6. Which modules must always be in lock-step with the version of

RSLogix 5000 you are using?
FW3e56r
1--6 Exercise: Updating Logix5000 Firmware
7. When is a maintainer most likely to update other modules (I/O,

communications, etc.)?
8. What tool can be used to update module firmware?
How Did You Do? Turn to the Answers section.
FW3e56r
Exercise: Updating Logix5000 Firmware 1--7
FW3e56r
1--8 Exercise: Updating Logix5000 Firmware
Answers Exercise A
6. Your controllers, motion modules, and SERCOS drives all must

match the version of RSLogix 5000 software you are using.
7. A maintainer is most likely to update other module firmware
when replacing a failed module.
8. The ControlFLASH tool can be used to update module
firmware.
FW3e56r
Lesson 2
Creating and Organizing a New
What You Will Learn After completing this lesson, you should be able to:
Important: This lesson covers the  Create a new RSLogix 5000 project file
default project organization. Periodic
tasks and event tasks are covered in  Modify controller properties
separate lessons.  Create a program and routine
 Adjust a program schedule
 Copy and reuse programs and routines
Stress that deleting project components  Delete a routine, program, and task
is not as simple as selecting delete from
a right-click menu. Because deleting can  Verify tasks, programs, and routines
be done online, it is a more detailed
procedure.
Note that the use of tasks and programs
is a major difference from RSLogix 5 and
500 softwares. Before you enter the logic for your application, you have to
configure the tasks, programs, and routines that will run the logic.
Before You Begin Key Terms
Project/Project File: The RSLogix 5000 software file used to store

Note that .l5k text files are part of a all programming and configuration information for a Logix5000
separate lesson. controller.
Project Organization
State that the multitasking system is like A Logix5000 controller is a preemptive, multitasking controller with
32 separate PLC-5 controllers that take the following characteristics:
turns controlling.
 Is single-threaded in that only one task will be active at a time
Note that task execution is based on  Has the ability to interrupt an executing task, switch to a different
priorities that are assigned by the user. task, then return control back to the original task when the
This will be discussed in detail later.
interrupting task is complete
TS2sb56r
2--2 Creating and Organizing a New RSLogix 5000 Project
Clarify that tasks and programs are To maximize these multitasking capabilities, the following
organizing elements (like folders in containers are available to organize an RSLogix 5000 project:
Windows Explorer). Routines contain the
actual ladder logic.  Task: A scheduling mechanism for executing its scheduled
programs.
 Program: A set of related routines and tags.
 Routine: A set or sequence of executable code.
Default Project Structure

By default, there is one task, program, and routine created in each
new project:
When reviewing this graphic, note the

following elements:
1. Each task can be divided into
programs based on function, area,
or some other attribute.
2. Each program can have as many Default Structure
routines as memory allows. One and Names
routine must be defined as the main
routine and the rest will be
subroutines.
Tip " The names and properties of these components can be modified to
suit your application.
Creating a New Task
A task triggers the execution of its scheduled programs. The

following table outlines the type of tasks that are available:
If students are familiar with PLC-5
controllers, relate the periodic task to an Task Type Usage Icon
STI.
A task that runs continuously but can be interrupted by
Continuous
periodic or event tasks (default task type).
A task that executes regularly at a user-specified rate.

Periodic
Important: Remind students that When called, it will interrupt any lower priority tasks.
periodic and event tasks are only
mentioned here as an overview. This A task that is triggered only when a specific event
topic is presented in more detail in a Event occurs. When called, it will interrupt any lower priority
later lesson. tasks.
TS2sb56r
Creating and Organizing a New RSLogix 5000 Project 2--3
? If a ControlLogix controller has one Reference: Logix5000 Controllers Design Considerations,

continuous task and 4 periodic, how 1756--RM094
many event tasks could it have?
Answer: 27 (27+4+1=32) 1. Find the Logix5000 Controller Comparison tables at the front of
the manual.
If a DriveLogix controller has zero
?
continuous tasks and 4 periodic, how
many event tasks could it have?
2. Compare the number of tasks you can have in various controllers.
Answer: 4 (4+4 = 8) Continuous Task

Compare this to the program files in an A continuous task has the following characteristics:
RSLogix 5 or 500 project.
 Is a background task that executes any time other operations, such
as periodic or event tasks, are not executing
Note that “self-triggered” means that as  Operates in a self-triggered mode (automatically restarts after
soon as it ends, the task begins again. It each completion)
also means that the routine does not
have to be called (activated).  Can be interrupted by a periodic or event task
If students are familiar with Basic  By default, has the lowest priority (one lower than the lowest
programming, compare this to periodic or event task)
programming a Goto 10 statement in the
last line.  Only ONE task can be continuous
Watchdog Timers
Note that the watchdog timer in a PLC-5 A watchdog timer monitors the execution of a task. The timer is
processor is for the entire controller. started when a task is initiated and stops when all programs within
Here, the watchdog timer is set for each
task. the task have executed.
Tip " A watchdog timer continues to run even if a task is interrupted, so

it’s important that the watchdog timer is set to a large enough value.
Point out that the last scan and max Ensure that the time period is longer than the sum
scan can be viewed online. In a different of the execution time of all the programs assigned
lesson, students will learn to monitor the
scan times using ladder logic to the task. If the controller detects that a periodic
instructions. task trigger occurs for a task that is already
operating, a minor fault occurs.
If a watchdog timer reaches its configured preset, a

major fault occurs.
fault handler, Depending
the controller onshut
may the down.
controller
TS2sb56r
To inhibit a task: Inhibited Task

1. Inhibit all tasks except one. The following icon in the Controller Organizer indicates that the task
2. Run the project and monitor the has been prevented from executing by a user option or instruction:
execution of the active task.
3. When the task meets the
requirements of the system, repeat
the process, testing a different task.
Inhibited Task
Tip " This inhibit option can be used to test, diagnose, or start up a project.
State that tasks can also be inhibited or If a task is inhibited, the controller still pre-scans
uninhibited using SSV instructions. the task when the controller transitions from
Program to Run or Test mode.
Mention that for information on Creating a Program

equipment phases, attend the
PhaseManager course. A program is the second level of scheduling within a project. A
program has the following characteristics:
 Each task can schedule up to 100 programs.

When
the firsta scheduled
task is triggered, its programs
to the last scheduled.execute in sequence from
Programs within a task can access input and output data directly
from controller-scoped memory:
 Code within any program can modify controller-scoped data.
 Code within a program can also modify program-scoped data:
-- Code within one program cannot access or modify the data
that is local to a different program.
The Create New Program button is shown in the following graphic:
Optional Toolbar
Create New Program
TS2sb56r
Adjusting a Program Schedule

Mention that the entire schedule can be Programs can be scheduled in a specific task or left unscheduled:
viewed in the Task Properties dialog
box. Otherwise, programs can be quickly  Original equipment manufacturers may create one project and
scheduled or unscheduled in the then schedule or unschedule a program depending on the
Controller Organizer. equipment’s required functionality.
Note that these methods will be  Maintenance or field service technicians may create
demonstrated in the Here’s How section.
troubleshooting programs that are left unscheduled until needed
Add that unscheduled programs do not to test a project.
use any scan time.
The following example shows a program schedule:
Adjust Order
Program
Schedule
Unscheduled
Programs
Actual Program Scan Time

The software can display the maximum scan time and the last scan
time in microseconds for a selected program:
State that a Compute instruction will  Scan time is based on the number and type of instructions.
take longer than using simple multiply
and divide instructions.  These values are execution times for the program and do not
include any time spent waiting for other programs or tasks.
Note that the GSV instructions that are  These values are for display only.
used to monitor program time are
presented in a different lesson. Tip " Values can also be monitored using specific instructions in code.
TS2sb56r
Creating a Routine
Note that ladder logic is the most A routine provides the executable code, or decision-making
common language used. instructions, for a project. Each routine contains a set of elements for
a specific programming language:
 Ladder Logic -- suited for relay or discrete applications
 Function Block Diagram - suited for continuous process and
drives control applications
 Sequential Function Chart -- suited for motion or batch
applications or concurrent applications where more than one state
is active at one time. Also suitable for sequential applications
such as assemble or packaging machines.
 Structured Text -- suited for complex math or array applications
or for programs converted from other projects created in
high-level languages like C
Tip " The availability of these languages will depend on the options that
have been selected and installed.
A routine can be assigned as one of the following types:

 Main Routine: A routine that executes automatically when the
controller triggers the associated task and program:
-- Can be of any language
-- Is marked with a 1 in the Controller Organizer
 Fault Routine: A routine that is configured to execute when the
controller finds an instruction-execution fault within any routines
in the associated program:
-- Is marked with a yellow triangle in the Controller Organizer
 Subroutine: A routine that is called by another routine:
-- Is called by a JSR (Jump to Subroutine) instruction in the
main routine or another subroutine (conditioned or
unconditioned)
-- Returns to the other routine when complete or if a condition is
met
TS2sb56r
Stress that routines are not listed in the The main routine is always listed first, followed by a fault routine (if
order of execution. JSR instructions any), and then all subroutines in alphabetical order:
determine the order of the subroutine
execution.
For troubleshooting, mention that you

can
lists create
all JSRainstructions
cross-reference report
that call a that
subroutine and their locations in the
ladder logic. This will be presented in a
different lesson.
Main Routine Ladder Logic Routine

Fault Routine
Subroutines Structured Text Routine
Sequential Function
Chart Routine
Function Block
Diagram Routine
In the graphic point out the “1” on the The following is an example of subroutine structure:
main routine.
When the conditions are met, the main routine
calls the Level subroutine.
Example Ladder Logic in the Main Routine
Subroutine
If necessary, define a nested routine as The Create New Routine button is shown in the following graphic:
a subroutine that is activated from within
another subroutine.
Note that cross-reference reports are Optional Toolbar
part of the Documenting and Searching Create New Routine
For Ladder Logic Components lesson.
TS2sb56r
Program Control Instructions

Note that if there are no input When enabled, the ladder logic JSR instruction directs the logic
parameters, control passes from the execution to the specified subroutine and, if needed, passes
JSR instruction to the first rung of the
subroutine. parameters to the subroutine:
 Numeric, structured parameters, and BOOL data type tags can be
passed.
The SBR (Subroutine) instruction receives the input parameters and

copies their values into the specified tags:
 The optional SBR instruction identifies the tags that store the
incoming parameters.
 The RET (Return) instruction ends the subroutine and, if needed,
returns parameters to the JSR instruction:
-- Use the RET instruction only if you are returning parameters
to the JSR instruction.
System Overhead Timeslice
Note that the system overhead timeslice The user-configurable system overhead timeslice determines the
is located in the Advanced tab of the percentage of controller time that is available for the following
Controller Properties dialog box.
background functions:
 Communicating with programing devices and programming
software
Add that because the serial port is in the  Messaging
controller, it affects controller operation.
 Bridging communications from the controller’s serial port to
If necessary, review RIUP.
other devices via the backplane
 Re-establishing and monitoring I/O connections (RIUP
conditions)
In the graphic, point out that the far right The system overhead timeslice percentage does not affect executing
area is used for overhead functions. If periodic or event tasks:
there are no functions, the time is
available for the continuous task.
Controller Execution Time
If there is no continuous task, then the

system overhead timeslice is irrelevant.
Time for Periodic or Event Tasks
Note that 20% is the default. Time for the Continuous Task %
System Overhead
Timeslice Percentage
TS2sb56r
Mention in step one that the data is Asynchronous Updates

multicast to the backplane then received
by the controller. Asynchronous: Actions that occur independently of each other and
Chalk Talk: If students have a PLC or lack a regular pattern.
SLC background, you may want to draw
the PLC/SLC scan diagram on the board
for comparison. In Logix5000
execution controllers, I/O values update asynchronously with the
of code:
When reviewing the diagram, explain the
following steps based on the experience 1. Input modules multicast their data to the backplane at the RPI rate
of the class and the lessons already set in the modules.
covered:
1. Each rung of ladder logic (code) is 2. The code is scanned and the output tags are updated immediately
scanned. after the execution of each output instruction.
2. As higher numbered rungs are 3. Values are sent to the output modules at the RPI rate and at the
scanned, the inputs may change and
therefore, the outputs may change end of each task.
as reflected in the tag
database image. Tip " The automatic output processing that occurs at the end of a task can
be disabled in the properties of the task.
3. The RPI is the rate at which the user
configures the output modules to
update. Because of the update process, input devices may change state within
one program scan and at a different rate than the program scan:
Single Scan
Physical Device Data is Tag is set or cleared in controller
received by the input card
Rung
RPI Rate
100
COS Rung
250
Optional
Rung
RPI Rate
400
TS2sb56r
Relate the organizational tips to an Project Organization Best Practices

example compressor assembly project:
S The project has three assembly To efficiently organize a project:
machine stations in the first  Divide the process into functional groups or sections that
controller; therefore, an Assembly
task is created. represent one or more facets of the process:
S Each station (press, stake, and -- Sequence of related actions that operators perform
weld) becomes a program in the -- Group of related process events
Assembly task. Instead of having a
separate controller run the machine -- Machine or machine sections
at each station, one controller runs  Divide each program into routines, where each routine represents
them all.
one or more facets of the program:
S Each program has a control routine
for the machine. A main routine is -- Specific process within the program
used to call the control routine (and -- Section of application code that could be hidden to facilitate
any future routines).
troubleshooting
If available, give examples of naming -- Function that occurs at several instances during the program
conventions and how they are
constructed. -- A main routine that will call up the subroutines of the program
 Create and apply plant naming conventions for tasks, programs,
routines, and tags.
Give students a few minutes to Reference: Logix5000 Controllers Design Considerations,

read the section. 1756--RM094
1. Go to the Divide Logic into Tasks, Programs, Routines, and

Add--On Instructions chapter.
2. Go to the Decide When to Use Tasks, Programs, and Routines
section.
3. Briefly read the information on when to use a task, program, or

routine.
Have each student do this on Activity: For each of the situations below, decide if you would
their own. Then go over the separate the logic at the task, program, or routine level. Check the
answers as a group.
appropriate box:
Separate the logic at this level

For this situation
Task Program Routine
Program A. A conveyor line uses a series of diverters to sort packages. Each diverter uses
identical logic.
Task You only

B. your needdevices
discrete to update your
every 20analog
ms. devices every 250 ms, but you must update
Routine C. The logic for a conveyor performs these functions: initialize, run, return status
information, handle faults.
Task D. A grinding application monitors an over--current sensor on the feed motor. If the
sensor trips, the operation needs to immediately abort to prevent the stone from
shattering.
Routine E. A mixing tank uses a combination of 2--state devices to mix juice:
 Several valves open and close to add wet and dry ingredients.
 A single--speed motor mixes the ingredients.
 An outlet valve opens to drain the tank.
TS2sb56r
Example: Project Organization

In this example, a paper mill converted a time-tested PLC-5
Note that the organization of this project ladder logic project into an RSLogix 5000 project. All of the
is not very different from a typical PLC-5 logic was placed in one continuous task and follows the basic
project.
default project structure:
Single Continuous Task

Similar to Traditional
Controller Project Select tool windows can now
Program be docked in RSLogix 5000’s
main window, float on top of
the window, or become an
Main Routine Auto Hide tool window.
This applies to:
Controller Organizer
Subroutines Errors
Search results
Watch
Start page
Verifying Tasks, Programs, and Routines
Mention that the verification process is After organizing your controller project, you can verify it. In this
similar to the RSLogix 5 and 500 process, the software looks for errors such as unassigned routines.
process with the addition of tag
verification.
The following buttons are available to verify the entire controller
project or routine:
Standard Toolbar
Verify Open Routine Verify

Controller
TS2sb56r
Errors or warnings found in the verification process are displayed in

the Output window:
Double-Click to
Go to the Error
or Warning or
Press F4
Here’s How To access video-based help files:

IMPORTANT: To meet IACET CEU Follow along as your instructor demonstrates this procedure.
requirements and fully prepare
certificate students for the final
exam, you must demonstrate Tip " There are many video-based help files to assist in everything from
all lesson objectives using development of an RSLogix 5000 project to maintaining one.
the proper job aids.
Use thethe
during steps below to help guide you
demonstration:
Access the files through the Help menu’s
Learning Center “How Do I” section.
Show one or two examples of the video
help. You can stop them after a few
moments. This is just to show how the
system works. If Lesson 20 will be used,
skip this Here’s How.
Example Access the files through the Help menu’s Learning Center “How Do
I” section:
TS2sb56r
For example, under Controller Projects you would find subjects on

creating and downloading projects. Under Maintain you would find
information on clearing faults or searching.
Here’s How To perform the following tasks:

 Create a new RSLogix 5000 project file
 Modify controller properties

 Create a program and routine
 Adjust a program schedule
 Copy and reuse programs and routines
 Delete a routine, program, and task
 Verify tasks, programs, and routines
Activity: As your instructor demonstrates these procedures, follow
along in the associated job aid(s).
certificate students for the final exam,
objectives using the proper job aids.
Use the steps below to help guide you Pay attention to these critical aspects of the demonstration:
during the demonstration: - Location of the procedures in the job aid
Create a new RSLogix 5000 project.
When demonstrating the listed - Revision must match the major firmware revision of the
procedures, point out the following
items: controller
S The MainTask, MainProgram, and - Initial name of the project file

MainRoutine
S The Main Routine Assignment - What happens if you change the name of the controller
drop-down list or the name of the project file
S The max scan time - Which name shows up in RSWho
S The System Overhead Timeslice
option - Once you pick the firmware revision for a project, you
" The copying and reusing programs cannot change it to a lower revision
and routines procedure is part of the - Task, program, and routine hierarchy
“Copying and Reusing Project
Components” procedure in the
Procedures Guide. - Where you assign a main routine for a program
- How to see the maximum scan time of a task
- Where you change the system overhead timeslice value
TS2sb56r
TS2sb56r
Exercise: Creating and Organizing a New RSLogix 5000 Project 2--15
Exercise: Creating and Organizing

a New RSLogix 5000 Project
Exercise A In this exercise, you will practice creating and organizing a new
RSLogix 5000 project.
Context:
You are familiar with the system’s hardware and software

components. You are now ready to create a new RSLogix 5000
project file to hold your programming and configuration information.
You are also ready to organize the project and direct the execution of
the code.
When you see underlined text, refer to the related procedure or

information in your job aid.
Directions:
1. From the Help Menu open the Learning Center:

A. Select the How Do I tab.
B. Select Controller Projects.
C. View the Video “Create a New Project.”

D. Remember as you go through the additional lab and steps that
the Help system is there to assist you in your work.
2. Create a new RSLogix 5000 project file for the controller in slot 1
of your workstation. Give it this name: Paint.
3. Modify the following controller properties:
A. For an anticipated increase in communications, change the

system overhead timeslice to 25%.
4. Rename the Main Task as Paint.
TS2e56r
2--16 Exercise: Creating and Organizing a New RSLogix 5000 Project
5. Create the following programs and routines:
Task Programs Routines Purpose

Paint Ladder that enables the
Paint_line_1 MainRoutine
subroutine
(This task (Rename the
automatically MainProgram) Paint_Control Ladder that controls the
paint gun
restarts when it
is done.) Ladder that enables the
MainRoutine
subroutine
Paint_line_2
The watchdog Ladder that controls the
timer value must Paint_Control
paint gun
be 600 ms.
Ladder that enables the
MainRoutine
subroutine
Paint_line_3
Ladder that controls the
Paint_Control
paint gun
6. Copy the Paint_line_3 program (with all of its contents).

7. Paste the copied program into the Paint task and change its name
to Paint_line_4.
8. Adjust the program schedule in the Paint task so that the
programs execute in this order:
A. Paint_line_3
B. Paint_line_1
C. Paint_line_2
D. Paint_line_4
9. Delete the Paint_line_4 program (and all of its contents).
Tip " Remember that all elements must be unassigned and removed first.
10. Verify the tasks, programs, and routines and correct any errors.
11. Save the project file.
Tip " Another programmer was assigned to create and organize the project
for the controller in slot 3 for a quality check. Although this is not
the paint line, you still want to follow the same style and conventions
for easy troubleshooting.
12. Open the TS2_1756r_A1.acd file.
13. Examine all properties of the tasks (continuous and periodic),

programs, and routines programmed in the project.
TS2e56r
14. Which task is periodic?
15. Which task is continuous?
16. In which order do the programs in the continuous task execute?
17. What are the subroutines in the Station_4_Quality program?
TS2e56r
Answers Exercise A
3.
A. The System Overhead Time Slice is configured on the
Advanced tab of the Controller Properties dialog box.
5. The main routine for a program is assigned on the
Configuration tab of the program properties dialog box:
7. The tasks, programs, and routines entered in the Paint project

are shown in the following graphic:
Watchdog Timer
Set to 600 ms
Assigned as
Paint_line_3
Main Routine
Assigned as
Paint_line_1
Main Routine
Assigned as
Paint_line_2
Main Routine
Assigned as
Paint_line_4
Main Routine
TS2e56r
9. To delete the Paint_Line_4 program, you must perform the

following actions:
A. Unassign MainRoutine as the main routine.
B. Delete the MainRoutine and the Paint_Control routines.

C. Unschedule the program.
D. Delete the program.
14. Record_Shift_Number, identified by the clock icon, is the

periodic task:
15. Assembly, identified by the round arrow icon, is the continuous

task.
16. The programs in the continuous task execute in this order:

A. Common
B. Station_4_Quality
C. Station_5_Palletize
17. The Station_4_Quality program contains the following
subroutines:
 Check
 Data_Logging
 Reject
TS2e56r
TS2e56r
Lesson 3
Creating a Periodic Task in an
 Determine the period (rate) for a periodic task
 Create a periodic task
If you have logic you want to run at a specific time period, create a
period task for it.
Before You Begin Task Type Review

If students are familiar with PLC-5 or
SLC 500 controllers, relate the periodic Task Type Usage Icon
task to an STI (Selectable Timed
Interrupt). A task that runs continuously but can be interrupted by
Continuous
periodic or event tasks.

Periodic
When called, it will interrupt any lower priority tasks.
A task that is triggered only when a specific event
Event occurs. When called, it will interrupt any lower priority
tasks.
PERsb56r
3--2 Creating a Periodic Task in an RSLogix 5000 Project
Periodic Task
A periodic task has the following characteristics:

Add that a task that is 8 ms in duration  Is triggered by the controller at a regular, repeated time interval
and is executed every 8 ms will block all determined by the user
other tasks of lower priority from
executing.  Always interrupts and suspends the continuous task
 May interrupt other periodic or event tasks with a lower priority
level:
Fault Example: If a periodic task -- An interrupted task does not shift its start time.
executes every 8 ms and it is 11 ms in
duration, the controller will fault. -- An interrupted task will stop mid-instruction.
 When executing, scans all assigned programs once from top to
bottom
 After a single scan, an output update is triggered and controller is
returned to the interrupted task at the point it was interrupted
" Like a continuous or event task, periodic tasks require at least one
Tip program and one routine.
Example: Periodic Task Use

Periodic tasks are selected for processes that require accurate and
deterministic execution:
 Check pressure on a machine at regular intervals
 Correct a PID loop at regular intervals
PERsb56r
Creating a Periodic Task in an RSLogix 5000 Project 3--3

Note that this project takes advantage of In this example, the motion application includes two periodic
some of the Logix5000 organizational tasks to ensure execution at specific time intervals:
elements.
Periodic Task
(with Times
in Names)
PERsb56r
Periodic Task Properties
The user--defined properties for each periodic task determine when

the task is executed:
In the graphic, point out that the period

is “when the task starts” and not how
long it takes.
Start Interval
Priority Level
Important
Priority
Information
Period
The period determines the start interval for the task:
 The trigger time range is 1 ms (millisecond) to 2000 seconds.
 The default is 10 ms.
If a periodic task retriggers before the task is

done, a minor fault will occur.
The rate at which a periodic task is triggered

determines the period in which the logic is executed
and the data is manipulated within the task. Data
outputs established by the programs in a task retain
their values until the next execution of the task or
until they are manipulated by another task.
PERsb56r
Priority
Clarify that the lower number (1) gives Each periodic and event task in a controller has a priority level that
the task a higher priority or importance. determines which task executes when multiple tasks are triggered:
 Priorities are assigned by the user.

There
and 15are 15 levels
being of priority, with 1 being the highest priority
the lowest:
-- A task with a higher priority will execute first (i.e., 1 before 3)
Note that the fastest or shortest task will  Task priorities are relative:
not necessarily be the highest priority.
-- If there are only three tasks, priorities of 6, 7, and 8 will
Clarify that this means the continuous function the same as priorities of 1, 2, and 3.
task automatically has the lowest priority.
A user cannot configure the priority for a  Although no priority level is assigned, the motion task is always
continuous task. the highest priority.
 Although no priority level is assigned, the continuous task is
always one priority level lower than all other tasks.
Highest Priority Motion Task

Point out that periodic and event tasks Trend
use the same priority scale/levels.
Therefore, whichever task has the Event or Periodic Task - Priority 1 . . .
highest priority executes first, regardless
of the task type. Event or Periodic Task - Priority 5 . . .
Event or Periodic Task - Priority 10 . . .
Lowest Priority Continuous Task
PERsb56r
Scan Time Values

Note that this system creates slightly When executing, the software displays the maximum scan time and
more overhead, as the controller writes the last scan time in microseconds for the selected task in the Task
the I/O updates after each rung is
scanned and does not wait until all of the Properties dialog box:
rungs are scanned.
Online Properties
Length of Execution
Periodic Task Execution
The period and the priority assigned to each task determine the task
execution.
Execution time is based on:

 The amount of code in a project
 The complexity of the code
 Processor speed
Example: Periodic Task
In the graphic, point out that the rate is In the following example, the periodic task is triggered every
“when the task starts” and not how long 20 ms:
it takes.
5 ms
0 ms 40 ms 60 ms 80 ms
Task Execution Every 20 ms 20 ms
Task (Duration of 5 ms)
PERsb56r
Example: Periodic Task and Continuous Task

The following example shows how the periodic task interrupts
and suspends the continuous task:
Periodic Task Execution Every 20 ms

5 ms
Continuous Task
0 ms 20 ms 40 ms 60 ms 80 ms
Continuous Task Interrupted for 5 ms
Example: Multiple Tasks

The following example shows how a periodic task interrupts and
suspends the continuous task and another periodic task:
 Task A is triggered every 20 ms and has a priority of 3.
 Task B is triggered every 22 ms and has a priority of 1.
Therefore, task B will interrupt task A:
22 ms 44 ms 66 ms 88 ms
Task B (Every 22 ms) Priority 1
Task A (Every 20 ms) Priority 3
Continuous Task
0 ms 20 ms 40 ms 60 ms 80 ms
? How many periodic or event tasks Two tasks can be assigned the same priority. If this occurs, the tasks
will timeslice, or alternate execution, in 1 ms intervals.
and how many levels of priority can
there be in a ControlLogix project?
Answer: There can be up to 32 periodic Example: Equal Priorities (Timeslicing)
or event tasks (or 31 if there is a
continuous task). However, there are The following example shows how two tasks of equal priority
only 15 levels of priority. (Use this will timeslice:
difference to lead into the discussion on
timeslicing).
Task A, Priority 3
Task B, also Priority 3
0 ms 1 ms 2 ms 3 ms 4 ms 5 ms
Tip " Timeslicing takes slightly more time than having different priorities.
PERsb56r
Here’s How To determine the period (rate) for a periodic task.

1. Note the watchdog timer value.
2. Subtract the required time for the continuous task.
3. Subtract the time of any existing periodic tasks.

4. Divide the time remaining by the time it takes the new periodic
task to execute.
5. Divide the total time allowed by the number of times you want
the second task to execute.
Example Determining the Period (Rate) for a Periodic Task.
1. Note the watchdog timer value: 450 ms.
2. Subtract the required time for the continuous task: 450--300 =

150.
3. Subtract the time the existing periodic task takes: 150--90=60

90 ms comes from the following calculation:
Executes every 50 ms, or 9 times in 450 ms.
9 times executed * 10 ms each time = 90 ms.
4. Divide the time remaining by the time it takes the second periodic
task to execute: 60 / 20 = 3
5. Divide the total time allowed by the number of times you want
the second task to execute: 450 / 3 = 150
PERsb56r
Here’s How To create a periodic task.
Activity: As your instructor demonstrates this procedure, follow

Use the CCP143_1756r_DEM2.acd Pay attention to these critical aspects of the demonstration:
project.
- Location of the procedure in the job aid
When demonstrating the task, point out
the following items: - Period and priority of the task
S The routines within one periodic task
enables the slot 0 outputs while the - Max scan time (when online)
other disables them
S In Run mode, you can verify when
the task execute by the lights on the
workstation
PERsb56r
PERsb56r
Exercise: Creating a Periodic Task in an RSLogix 5000 Project 3--11
Exercise: Creating a Periodic Task

in an RSLogix 5000 Project
Exercise A In this exercise, you will practice creating and configuring a periodic
task in an RSLogix 5000 project.
Context:
You have already created an RSLogix 5000 project file to hold your
programming and configuration information. You are ready to add a
task that will execute on a regular basis.

Directions:
1. What type of application would require a periodic task?
2. Open the PER_1756r_A1.acd file.

3. Review the following information about your project:
Existing periodic task
at priority 2. Takes
about 20 ms and
executes every 50 ms.
Main task takes about

300 ms.
4. You want your new periodic task to have a higher priority than
the Existing_Periodic task. What priority number will you assign
for your task based on the previous information?
5. If your new periodic task was assigned the same priority as

Existing_Periodic task, what would happen if the tasks
attempted to execute simultaneously?
PERe56r
3--12 Exercise: Creating a Periodic Task in an RSLogix 5000 Project
6. Review the following application requirements:
 Your goal is to execute the new task every 150 ms.

 The new task must have a higher priority than
Existing_Periodic task.
7. Create a periodic task named Quality configured for the priority

and rate necessary to meet the application requirements.
8. Add the unscheduled program Quality_Monitor to the program
schedule of your new periodic task.
9. Download your project to the controller and go online.
10. Place the controller in Run or Remote Run mode.

11. What happens when the controller is placed in Run or Remote
Run mode?
12. If the controller experiences a watchdog fault while in Run or

Remote Run modes, how could the configuration of the periodic
task be changed to prevent this fault?
13. Clear the Major Fault from the Controller Properties dialog box.
14. Configure the Quality task to have a rate of 250 ms.

16. In the Task Properties window for the Main Task, verify that the
maximum scan time is not greater than the watchdog of 500ms.
PERe56r
Exercise: Creating a Periodic Task in an RSLogix 5000 Project 3--13
PERe56r
3--14 Exercise: Creating a Periodic Task in an RSLogix 5000 Project
Answers Exercise A
1. Any type of application that requires accurate and deterministic

control would be an appropriate response.
4. The only priority higher than 2 is 1.
5. If periodic tasks of the same priority attempt to execute
simultaneously, the tasks will timeslice execution in 1 ms
intervals.
7. Your New Task dialog box should look similar to the following
example:
11. Your controller should experience a major fault when the

controller is placed in Run or Remote mode. This is due to the
Main Task watchdog time expiring.
12. Increasing the period (rate) of the periodic task will reduce the
frequency the periodic task executes. Even a periodic task with
contains little code can fault a watchdog timer if executed
frequently enough. Another option would be to increase the
watchdog timer for the continuous task.
16. Your Task Properties window should look similar to the
following example (scan times will vary):
PERe56r
Lesson 4
Organizing Data in an
 Create a tag
 Define an alias tag
 Create an array of tags
 Verify tags
 Monitor and edit data
As you develop your logic, you will have to define tags, aliases, and
arrays to efficiently store your data.
Before You Begin Controller Memory
For example, a PLC-5 processor has a Traditional controllers have data files, such as Timer or Integer,
pre-created timer file, where all timers where groups of the same types of data are stored together.
are stored together.
There are no such pre-defined data files in a Logix5000 controller.
Users must define the memory in a Logix5000 controller by creating
tags.
Verify that students have an Tag: An area of controller memory where data from devices,
understanding of bit, byte, and word calculations, faults, etc. is stored. Each area is given a unique name:
lengths. If not, spend some time
reviewing these terms:
Bit: The smallest unit of data “Drive_Speed” Data
represented by the digits 0 and 1.
Controller Memory
Byte: A string of 8 bits operated on
as one unit.
Word: A unit of memory in a
controller composed of 16 individual
bits or two bytes that are treated as
one unit.
Remind students that the individual bits
of a byte or word can also be monitored “Sensor” Data
or addressed. “Start” Data
Emphasize that the graphic depicts only

a portion of the controller memory. Note
that in the graphic each line represents a
bit, or the smallest unit of memory.
TA2sb56r
4--2 Organizing Data in an RSLogix 5000 Project
Data Types
Add that the data type maps out the data Data Type: The definition of how many bits, bytes, or words of data
just as it does in a PLC-5, SLC 500, or a tag will use. The data type is based on the source of the
other processor.
information.
Note that a tag is similar to the symbolic Pre-Defined Data Types: Commonly used memory sizes or
address in a PLC-5 or SLC 500 structures that are already defined in the software.
controller. The main difference is that
tags are stored in the controller, where
symbols are stored in the computer only. Atomic Data Type: A simple data type made of one piece of data:
Data Type Definition

Indicate that BOOL, SINT, INT DINT, A single bit where 1 = on and 0 = off (e.g., the state of a
BOOL
and REAL data types are called atomic discrete device such as a pushbutton or sensor)
data types. SINT A short integer (8 bits) between --128 and +127
An integer or word (16 bits) between --32,768 and +32,767
INT
(e.g., PLC-5r data)
Note that the

data type. DINT
More datawill
details typebeispresented
the main DINT
A double integer (32 bits), used to store a base integer number
in the range of --2,147,483,648 to +2,147,483,647 (e.g., serial
later in the lesson. number)
A 64-bit signed integer data type used to represent wall clock
LINT
time
A 32-bit floating point value (e.g., an analog value such as a
REAL
potentiometer value)
A data type that holds character data (e.g., “Car” or “this is
STRING
text”.
Using these definitions, tags for the given devices require the
following data types:
“Drive_Speed” Data
Controller Memory DINT, or 32 Bits
“Sensor” Data
“Start” Data
BOOL, or 1 Bit
BOOL, or 1 Bit
TA2sb56r
Organizing Data in an RSLogix 5000 Project 4--3
Structure: A more complex data type that is made up of several

Relate this to a timer relay where there pieces of data. E.g., a TIMER data type is made up of a combination
is on/off data as well as a preset value. of DINTs and BOOLs:
Data Type Definition
COUNTER Increasing or decreasing total

TIMER Increasing time total (milliseconds)
CONTROL Length and position for file level instructions
MESSAGE Control structure for a message instruction
Tip " There are other less common, pre-defined data types that are used to
Give an example, such as the store specific data for function block instructions or motion
TOTALIZER data type, which is used instructions.
with the TOTALIZER function block. The
data type contains a member for each
parameter of the function block. Module Defined Data Types: Data types used for hardware data,
such as I/O tags.
Memory Allocation
Add that a DINT is often called a D word The minimum memory allocation for a tag of any type is a DINT
or a double word. (double integer or 32 bits). A DINT is the main Logix5000 data type.
When data is assigned by the user, the controller assigns the next
available DINT(s) of memory to any data type.
Use the graphic to review the definitions When data types such as BOOL, SINT, and INT are assigned to a
of BOOL, SINT, INT, DINT, and REAL. tag, the controller still consumes a full DINT (four bytes) but only
After describing each data type, point
out the unused area. fills part of it:
Minimum Memory Allocation of 1 DINT Data
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Type
Unused Memory  BOOL
 SINT
 INT
 Used Memory DINT
 REAL
TA2sb56r
Add that students will learn how to To efficiently use memory for BOOLs, SINTs, or
create these components in the next INTs, an array or a user-defined data type should
lesson.
be created.
 A controller stores tags as they are created and as they fit into
controller memory.
 Tags of the same data type are not necessarily stored together in
memory.
Tag Scope
Add that for program-scoped tags, Tags can be created at two different scopes:
behind the scenes, the program name
becomes a prefix for each tag name.  Controller-Scoped: Tags, such as I/O tags, that are available to
This is how tags with the same names in
different programs are kept separate. every task and program within a project.
 Program-Scoped: Tags that are only available to the program to
which they are associated.
Scope requirements for specific tags are outlined in the following
Mention that if tags are correctly scoped, table:
ladder logic that uses the program tags
can be reused in different programs
To use a tag . . . Then select this scope . . .
without changing tag names.
That is generated when an I/O module is configured
Note that the I/O tags listed in the table (I/O status, data, etc.)
are the tags that are automatically
created when a module is configured. In more than one program within the project
This does not refer to any alias tags that
might be created. To produce or consume data (share it with other Controller-scoped
controllers)
Mention that the scope dictates the tags
folder in which you will create the tag. In a message instruction or with a PanelViewt 1000C
terminal
In only one program (and it is not a message
Program-scoped
instruction or a produced or consumed tag)
Note that tags can be defined through a Creating a Tag

dialog box or through the Edit Tags
worksheet. The worksheet may be faster To create a tag, the following parameters must be defined:
when creating multiple tags.
 Tag Name
 Data Type
Direct students to the “Description” entry  Style
in the Glossary of the Procedures Guide
for the description rules.  Data Access Control (optional)
Note that alias tags will be presented  Description (optional)
later in this lesson.
Note that the Monitor Tags tab is for
viewing data that is active in the
controller.
TA2sb56r
The parameters are defined in the Edit Tags tab of the Tags window:
Another Name Operand Descriptions Data Access Display

for the Tag Control Style
Tag Filter Data Type Wildcard Filter
Icon Indicating
Controller-Scoped
Tags
White = Editable
Field
Editing View
State that tag names are not Tag Name

case-sensitive. However, case
may help with readability. Tip " Naming conventions are listed in the “Name” entry in the Glossary
of the Procedures Guide.
Have the students turn to the Glossary
of the procedures guide. Review the
naming conventions.
Creating controller-scoped tags and
Note that these naming conventions program-scoped tags with the same names can
apply to most components in an cause confusion.
Data Type
Tags can be created using the following data types:
 Any pre-defined data type
 Any user-defined data type
Style
State that data from a BCD thumbwheel Style is the display radix for each data type:
could be viewed in the hexadecimal
radix.  For certain data types, the style can be changed to a different
display radix. E.g., the default style for a tag of the DINT data
type is decimal:
-- The style for DINT tags can be changed to binary, octal,
decimal, or hexadecimal.
TA2sb56r
Defining an Alias Tag
Alias Tag: An additional name for a tag (or other alias tag):
 The tags refer to the same area of memory.
Tell students that if a base tag is used as  The tags, therefore, reflect the same values and changes.
an address, any corresponding alias
tags will not be displayed. Base Tag: The tag to which the alias refers (i.e., the tag where data is
State that if the base tag is used directly actually stored).
in an instruction, that is all that is shown.
If an alias tag is used as the address for an instruction, the alias tag is
Compare this to calling someone by always displayed.
their name instead of their employee
number, or referring to a
module by a name instead Tip " When programming, it may be confusing to sometimes use an alias
of a part number. tag and other times directly use the tag to which the alias refers.
In the following graphic, trace the chain Alias tags are commonly used to rename I/O tags that are generated
of alias tags, beginning with Start. When with complex naming structures:
you reach Alias_4, it will be easier to
explain Base tags. Alias Tag Name What the Tag is an Alias for (e.g., an I/O Tag)
If this lesson is part of a standard

school, state that students will
learn how to configure I/O
modules and interpret the
generated I/O tags in the
Communicating with a
Local 1756 I/O Module lesson.
Base or Original Tag

(If There is a Chain of Alias Tags)
Note that the hierarchy of alias tags is Use caution in developing applications that utilize
available in the cross--reference report multiple alias tags for the same base tag.
for a tag. This can be a very helpful
troubleshooting tool.
You cannot create a program-scoped alias tag for a

controller-scoped tag of the same name.
Note that there is a separate lesson that Produced and Consumed Tags
presents the steps for these tasks.
The following controller-scoped tags can be created to share data
between controllers:
If students are familiar with producing  Produced Tag: A tag that is shared with other controllers over
and consuming tags, point out that the
setup in RSLogix 5000 software is the the backplane or a control network, such as ControlNet t or
same. For Ethernet, the producing EtherNet/IPt.
controller is connected to a remote
1756-ENET or 1756-ENBT module.  Consumed Tag: A tag that holds the value of a produced tag that
is received from another controller over the backplane or a
control network.
TA2sb56r
Creating an Array of Tags
Array: A numerically indexed sequence of elements of the same

Note that an array that is a member of data type. An array tag occupies a contiguous section of memory in
user-defined data type can only have the controller with each element in sequence. Arrays can have one,
one dimension.
two, or three dimensions.
Element: A single position within an array.
Note that the array Part[40] will have Example: Array

elements of Part[0] to Part[39].
To make INT records for 6 parts, a one-dimensional array of INTs
Point out that you can create an alias
tag for each element of an array. For is created:
example, Cold_Timer might be an alias
for TIMER [34]. 1 DINT (32 Bits)
Relate this to PLC-5 data, where N7:0 to 1 INT

N7:9 is a one-dimensional array of
integer data types.
Note that if maintenance personnel who Part_Data[1] Part_Data[0]
will work on the project are used to Part_Data[3] Part_Data[2]
working with PLC-5 controllers, you can Part_Data[5] Part_Data[4]
create an array named T4. Each
element, e.g., T4[11], will look similar to
a PLC-5 timer, with brackets instead of a
colon.
Point out that if you create an array tag The elements in the array occupy memory in order. The array always
from the Tags Editor window, and starts at 0 and extends to the number of elements minus 1.
manually
numbers, enter thevalue
the first brackets and in the
entered
brackets becomes the X value. The An array in the Tags window is shown in the following graphic:
second number entered is Y and the
third is Z. Same Data Type
Array of 6 (0- 5) INTs
Note that if you enter the dimensions
from the Tags Properties window Dim0
becomes Z if you create a three Single Element
dimensional array. Depending on how
the tag is created you could end up with
two different results.
? What is a structure? An array must be created with the following rules in mind:
 An array can have up to three dimensions unless it is a part of a
Answer: A data type made up of a
mixture of other data types, such as a UDT, where then it can have only one dimension.
timer (with a mix of DINTS and BOOLS).
 An array can be of one data type only. Arrays support the
following data types:
-- Any pre-defined data types except Axis data types, Message,
or Motion_Group
-- A user-defined data type
TA2sb56r
Tip " Data of the same type is not automatically grouped in memory. To
store all timers together, create an array of timer tags.
Array Storage
Arrays can have up to three dimensions and store data in the

Relate this to a Microsoft Excel following manner:
worksheet where one dimension is a
column, two dimensions are rows and Three Dimensions
columns (a standard worksheet), and Two Dimensions
three dimensions are several pages of
rows and columns.
One Dimension
Example: Three Dimensional Array

Add that an array might include data A three dimensional array might store the following data:
sorted by shift number, part type, and
part number. Note that data might also Part Number Part Number, Size Part Number, Size, Color
be stored by shift, day, and week. Or, x
and y coordinates (for retrieving a part in
storage).
Note that each square is an element.
Note that in memory, the first dimension

will not increment until the second
dimension reaches its upper limit.
= Part Number 2, Size 3, Color 0
Ask students to determine the total To determine the total number of elements in an array, multiply the
number of elements in each of the part number of elements in each dimension.
number arrays.
Tip " A tag uses a DINT (32 bits) even if it is smaller (8 bits). To conserve
data, put 32 BOOLs, four SINTs, or two INTs into an array.
TA2sb56r
Array Addressing
Note that this section presents the In an array, the following can be addressed:
formats for array addresses. Entering
the addresses will be presented in the  A numeric element (fixed)
Entering, Editing, and Verifying Ladder  A variable element
Logic
lesson.in an RSLogix 5000 Project  A numeric bit
 A variable bit
Numeric Element Addressing

Note that the number or expression in To access a specific array element (e.g., one DINT in an array of
the brackets is the subscript. Point out DINTs), use the following address format:
the square brackets that enclose the
element number. Remind students that
the elements begin with 0 (zero). ArrayName[Element Number]
Note that the subscript is the value or Example: Numeric Element Addressing
expression in the square brackets.
PartData[3]
Tip " This reference is fixed because the element value of 3 will not
change.
Data that is stored in two- and three-dimensional arrays can be

addressed using the same format. Additional dimensions are
separated by commas, as outlined in the following table:
Number of
Format Example
Dimensions
1 Array_name[0] Part[3]
2 Array_name[1, 0 ] Part[2,4]
3 Array_name[2, 1, 0] Part[3,5,1]
Example: Numeric Element Addressing for Multiple Dimensions

Array= Part[8,6,4]
Part[8,6]
Part[8]
Part[4,5
Part[2] Part[1,3] Part[2,3
TA2sb56r
Variable Element Addressing

Add that this is similar to indirect To change the array element that your logic references, use a tag or
addressing in PLC-5 programming. expression to point to the element, using the following address
format:
ArrayName[Tag or Expression]
Example: Variable Element Addressing

Part[SerialNumber]
Part[SerialNumber*5]
In the last example, add that if Part[Position1--Position2]
position1= 7, and position2 = 3, then the
part value is 4. You can use the following mathematical operators in an expression
to specify an array element:
Operator Description
+ Add
-- Subtract/Negate
* Multiply
/ Divide
And And
Frd BCD to integer
Not Complement
Or Or
Tod Integer to BCD
Sqr Square root
Xor Exclusive or
As an example, state that if Any array value that you enter must be within
Position1--Position2=48 and the array is the boundaries of the specified array.
an array of only 40, a major fault will
occur. Instructions that view arrays as a collection of
elements generate a major fault if a value
exceeds its corresponding dimension.
Numeric Bit Addressing

State that the delimiter before the bit is a A bit within one element of an array can be addressed using the
period. following address format:
ArrayName[Element Number].Bit
Note that the example addresses the Example: Numeric Bit Addressing
second bit in tag element 1 of the part
array. Part[1].2
Mix_Timer[5].DN
TA2sb56r
Variable Bit Addressing

To dynamically change the value of a bit, use the following address
format:
ArrayName[Element Number].[Tag or Expression]
Example: Variable Bit Addressing

Part[SerialNumber].[Position1--Position2]
Array Addressing Summary

Point out that a period signifies a bit or a The following table presents a summary of the array address types,
member. A tag without a period is the formats, and examples:
whole address.
Type Format Example
Numeric
ArrayName[Element Number] Part[5]
element
Variable ArrayName[Tag] Station[Position]
element
ArrayName[Expression] Station[Position+5]
Numeric
ArrayName[Element].Bit Part[5].15
bit
Variable ArrayName[Element Number].[Tag] Part[Index].[MyIndex]
bit ArrayName[Element Number].[Expression] Part[Index].[MyIndex+31]
Verifying Tags
Mention that the verification process is After tags are entered, they can be verified. In this process, the
similar to the RSLogix 5 and 500 software looks for tag errors.
process with the addition of tag
verification.
Errors found in the verification process are displayed in the Output
window:
Double-click to
Go to the Error or
Press F4
In the Tag window, tags with errors are also marked with an .
State that BOOL data types can now be Monitoring and Editing Data
toggled in the Monitor tags window
(right-click the tag value or press Tags values can be monitored and edited online through the Tags
[CTRL]+T).
window or certain instructions.
TA2sb56r
Point out the various unlabeled elements Monitor Tags Tab

of the spreadsheet, including the rows,
cells, columns, etc. The Monitor Tags tab is a direct view of a controller’s memory:
Mention that operand descriptions will
appear with the tag in logic if configured Scope of Current
to do so. Collection
Data Type
Tag and Members Blue
Arrow Operand Descriptions
Right-Click to (up to 512 characters)
Hide/Show
Columns
Value in
Controller
Expand to See
Structure Members or
Bits within the Tag
Monitoring View
A blue arrow at the top of a column signifies that

a change to any value in this column will
immediately take effect in the controller when you
press Enter or click another cell.
Stress that finding tags is a key step in Tags and Members

monitoring. The way in which tags are
filtered can help limit the number of tags Tags of the same data type are not automatically displayed together
displayed. If used improperly, it can also in the Monitor Tags tab:
hide required tags.
 Tags can be displayed alphabetically (default mode).
 Tags can be sorted and filtered (e.g., show DINT tags only).
 Tags can be filtered with wildcards (filtered based on their name
or description in addition to their scope, type, and classification).
 Tags that are structures (TIMER, etc.) can be expanded to display
members.
Display Style
State that data from a BCD thumbwheel The Style parameter controls how data is displayed for certain tags.
could be viewed in the hexadecimal
style.
Example:
The default style for a tag of the INT 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.
TA2sb56r
When online, only the tag name, style, and

description can be changed.
From the Tag Properties View window you can monitor a tag’s
properties, document, toggle values or Force. The Window can also
be docked, or set to auto hide, using the Auto Hide button
located in the banner:
Tag Properties
View Window
Docked or Auto
Hide Button
Tag
Information
Tag Value and

Force Mask
Stress the difference between editing the Monitoring and Editing Tag Values through a Routine
tag (e.g., tag name) and changing the
tag data, such as the preset. Tag values can be monitored and sometimes edited online through
In this ladder logic example, point out instructions in routines:
that values can be monitored and certain
values, such as timer presets, can be
edited. Example: Ladder Logic Routine
Tag values can be monitored through the corresponding
parameters of an instruction:
Blue Arrow: Change will

Immediately Take Effect
in the Controller
TA2sb56r
Example: Function Block Diagram Routine

Note that only the parameters with a Visible function block parameters can be monitored through the
checkmark in the Vis column (Visibility) instructions. Others can be monitored through the Properties
are displayed on the function block.
dialog box:
Parameter
Parameter Parameter Parameter Description (Up to
Names Values Data Types 128 Characters)
Visibility
Enabled
TA2sb56r
Note that the Watch tab is accessed Monitoring and Editing Tag Values in the Watch Tab
from the View menu.
The Watch tab displays all tags referenced by an active routine of
any type. Values can be monitored or edited:
Refresh Structured
Text Data Changing
Values Force
Create a
Custom
Monitor
Tag Scope
Because structured text values cannot be

monitored in the programming language, the
Watch tab is extremely useful when monitoring a
structured text routine online.
? Who has used Custom Data The Watch tab does not update as you make edits
Monitors in RSLogix 500 software? to a structured text routine. It is updated when you
verify the routine.
Quick Watch Tag Monitor
Note that the custom list of tags allows The Quick Watch Tag Monitor allows you to assemble a custom list
you to see only select tags while viewing of tags to monitor:
code. This helps you avoid the searching  Tags from the controller-scope
and scrolling necessary with the
Tags monitor.  Tags from the open routine
Tip " You can drag tags from the open routine editor to the Quick Watch
Tag Monitor.
Tip " The tags are maintained in the monitor only while the project is
open.
TA2sb56r
Persistent Quick Watch

Features of Persistent Quick Watch include:
 Enables creation of named tag groups (Quick Watch Lists)
-- Tags can be added via drag-and-drop from routine(s), from tag
editor/monitor or manually selected via tag browser
 Improves ease-of-use and simplifies maintenance
 Lists can be easily selected for debugging purposes during
integration or operation and are persistent within the
RSLogix 5000 project:
TA2sb56r

 Create a tag
 Define an alias tag
 Create an array of tags

Verify tags
 Monitor and edit data
for the final exam,
project.
- Location of the procedures in the job aid
- Using array dimensions text boxes
- Structure of a created array (in the Monitor Tags list)
- Show and Toggle Columns options in the Edit Tags

windows
- Using grid to pick a bit
Monitoring data in RSLinx isn’t an Monitor Data in RSLinx Classic Professional Software
objective of the lesson but it is useful for
the exercise and student. Tags can also be monitored (but not edited) in RSLinx Classic
Note that an RSLinx Classic activation Professional software.
file is required to access the data table
monitor.
Read-Only Values
Your Turn Now it’s your turn. Do Exercise A and return here when you’re done.
TA2sb56r
Data Access Control
The data access properties of a tag is used to control how people and
programs access the tag at run-time:
Mention that External Access Control  Use External Access to control how an external application, such
does not apply
or aliases to Module Defined tags
to them. as an HMI, historian, or OPC data server, can access a tag:
-- Arrays -- Top level only; UDTs -- by member
-- Possible values are:
-- Read/Write: External applications can both read and
modify the tag’s value
-- Read Only: External applications can read the tag’s value,
but not modify it
-- None: External applications can neither read nor write the
tag’s value
 Use Constant to control how controller logic can access a tag:
-- When this attribute is set, the tag’s value cannot be changed

programmatically
Data Access Control Selections are shown in the following graphic:
Tags Window
Data Access
Control Selections
User-Defined
Data Type
Mention that if a tag’s external access is Data Access Control Benefits

set to None, the tag will not show up in
other application browsers. These options give you a way to protect data from being accidentally
Note that if a tag is set to Constant and or intentionally written to. They can also speed-up HMI creation by
a program instruction tries to write a reducing the number of tags that are visible while browsing the
value to the tag, this would appear as an
error when verifying the project. controller from the HMI development environment.
Your Turn Now it’s your turn. Do Exercise B.
TA2sb56r
Exercise: Organizing Data in an RSLogix 5000 Project 4--19
Exercise: Organizing Data in an

Exercise A In this exercise, you will practice the following tasks:

 Creating a tag
 Defining an alias tag

 Creating an array of tags
 Verifying tags
 Monitoring and editing data
Context:
Sample code to test your production line has been developed. This
code was written before your hardware installation. The hard-wired
addresses wereand
to create base notalias
knowntagswhen thearray
and an codeof
was created.
tags so thatYou now need
the code will
function properly.

Directions:
1. Open the TA2_1756r_A1.acd file.
2. Review your project and verify the tags referenced in the

MainRoutine of the Line_1 program have not been created.
3. Create a new tag with the following properties:

 Name: Stop_Motor
 Type: Base
 Data Type: BOOL
 Scope: Program (Line_1)
4. Create a new alias tag with the following properties:
 Name: Start_Motor
 Type: Alias
 Alias For: Local:2:I.Data.0
 Name: Motor_On
 Type: Alias
 Alias For: Local:0:O.Data.0
TA2e56r
4--20 Exercise: Organizing Data in an RSLogix 5000 Project

 Name: Motor_Time
 Type: Base
 Data Type: TIMER
7. Within the Program Tags monitor, enter 10,000 for the
Motor_Time.PRE member of the Motor_Time tag.

 Name: Motor_Speed
 Type: Alias
 Alias For: Local:8:I.Ch0Data
 Name: Speed_Out
 Type: Alias
 Alias For: Local:7:O.Ch0Data
10. Create a single-dimension array that will be used to store the
system date and time. This array requires a separate element for
the system year, month, day, hour, minute, seconds, and
microseconds. Configure the array with the following properties:
 Name: ClockTime
 Type: Base
 Data Type: DINT
 Array Dimension 0: 7 elements
 Scope: Controller
 External Access: Read only
11. Download your project to the controller in slot 1 of your
workstation.
13. How could the individual members of this UDT be set so they
would not be accessible from any other application?
TA2e56r
14. Verify you properly created and aliased your tags by performing
the following actions:
A. Press DI0 and observe DO0 indicator light turn on.
B. Adjust pot AI0 and confirm potentiometer AO0 updates in
value while the motor is enabled.

C. Confirm that after ten seconds indicator DO0 turns off.
D. Monitor the ClockTime array and verify the tag is populating

with system date and time information.
Tip " The system date and time may not be current.
15. Go offline and close your project.
Exercise B In this exercise, you will practice setting a tag’s external access
option, and verify the setting.
Context:
You have created and organized a project file for your production
lines. You now want to protect certain tags from outside access.

Directions:
1. Open the TA2_1756r_B1.acd file.

2. Download your project to the controller in slot 1.
3. Make sure your processor is in Run mode.
4. Monitor the ClockTime tag in RSLinx software and make sure

some of the data is changing.
5. Return to the RSLogix 5000 software and go offline.
6. In the Controller tags, set the ClockTime tag’s external access to

None.
8. Is the ClockTime tag visible in RSLinx software?

TA2e56r
Answers Exercise A
3. Your Stop_Motor tag should have the following properties:
4. Your Start_Motor tag should have the following properties:
TA2e56r
5. Your Motor_On tag should have the following properties:
6. Your Motor_Time tag should have the following properties:
7. Your Motor_Time tag should be configured similar to the

following example:
TA2e56r
8. Your Motor_Speed tag should have the following properties:
9. Your Speed_Out tag should have the following properties:
10. Your ClockTime tag should have the following properties:
TA2e56r
13. Set the external access to none.

14.
D. Your ClockTime tag should contain data in each member of
the array like the following example:
Exercise B
6. After setting the ClockTime tag’s external access to None, your

screen should appear similar to the following:
8. No, the ClockTime tag is not visible. Your screen should appear
similar to the following:
TA2e56r
TA2e56r
Lesson 5
Creating a User-Defined Data Type
in an RSLogix 5000 Project
 Create a user-defined data type
 Export and import user-defined data types
As you develop your logic, you will typically take advantage of
user--defined data types to organize your data.
Before You Begin Creating a User-Defined Data Type
Some predefined data types, such as a TIMER, are structures of

Add that in RSLogix 5000 software, several different data types:
timers have some additional bits.
Note that in a PLC-5 controller, T4:5 has
its memory defined using the TIMER
template. Mixed
Data Type Data
Types
Members of a
TIMER Data Type
UDTsb56r
5--2 Creating a User-Defined Data Type in an RSLogix 5000 Project
Review: An element is one part of an User-Defined Data Type: A structure created by a user to group
array. data in an application.
A member is one part of a data type.
Member: One defined data type within the structure.
Example: User-Defined Data Type

There are several identical tanks in a plant. Each tank stores data
Chalk Talk: Before showing the next for the following values:
slide, have the students help you make
a list of the members that might go into
the user-defined data type for the tank
example. Have the students select the Temperature
data type of each member.
Steam Valve State
Time over Temperature
Level
Add that this is a more efficient use of To store this data, a user-defined data type can be created. The
memory than creating a single BOOL for data type is a template for storing the information:
the steam valve, as the single BOOL
would use a DINT (32 bits) by itself.
Size
Members of External
Tank Structure Access
Settings
Provide other examples, including A tag for each tank can be created using this user-defined data
examples of recipe parameters and type.
storage data types.
Note that creating an array is easier than

creating 20 individual tags.
UDTsb56r
Creating a User-Defined Data Type in an RSLogix 5000 Project 5--3
Note that in this scenario, the Example: Arrays and User-Defined Data Types
user-defined data type is created first,
and then the array of tags is created. If there are 25 tanks (5 rows of 5), a programmer can make an
array of tags that uses a user-defined data type:
Tank [0,0] Total Array = [5,5]
One Specific Element = Tank[1,3]
User-Defined Data Type Parameters

To create a user-defined data type, you must define the following
parameters for each member:
Stress that arrays embedded within a  A name of up to a maximum of 40 characters
user-defined data type can only have
one dimension.  A display style
 A description (optional)
 One of the following data types:
-- Any pre-defined data type
Note that memory size is updated after -- Another user-defined data type
each member is added and accepted in
the software’s Edit Data Type dialog box.
-- Single-dimension array of any pre-defined data types
-- Single-dimension array of any user-defined data types
Chalk Talk: On the board, write the
following data types in order: BOOL, The memory required by a user-defined data type depends on the
DINT, and then a BOOL. Discuss how number of members, the data type for each member, and how the
this structure would take more memory members are organized.
than the DINT followed by both BOOLs.
Add some additional examples.
User-Defined Data Type Addressing
Just as you addressed TIMER members in other projects (T4.EN or
Note that this is similar to how you T4.TT), you can address members of a user-defined structure using
address TIMER members in other the following addressing structure:
projects (T4.EN or T4.TT).
State that the delimiter is a period. Tag.Member
Examples: User-Defined Data Type Addressing

Point out that the last example contains SystemTimer.Pre
a structure (Load_Info) that is embedded
in the user-defined data type. WaterTank.Level
Input_Location.Load_Info.Height
UDTsb56r
Exporting and Importing User-Defined Data Types
Exporting and importing allows you to have more flexibility in your

programming and creates a user-defined data that:
 Is easy to deploy
 Creates reusable programming code
When you export a user-defined data type to an .L5X file, the file
contains the definition and any references to the project.
Export a UDT
using a .L5X File
Importing a user-defined data type allows you to perform several

edits in one operation.
When you import a user-defined data type, you can:

 Import offline or online (including Remote Run mode)
 Import into the same project or different one
 Create a new user-defined data type
 Update an existing user-defined data type
Import a UDT
into the same or
new project
Obtain
Specify final collision
name information
UDTsb56r
Creating a User-Defined Data Type in an RSLogix 5000 Project 5--5

Pay attention to these critical aspects of the demonstration:
Use thethe
demonstration:
Open the Start Pages and use the
following tools to demonstrate each task: - Location of the procedures in the Start Pages
S How Do I " Tags, Data Types &
Other Data " Create a - Difference between a user--defined data type and an
User-Defined Type array
S What’s New " Import Online -
Programs, Routine and Instructions - Overwriting a user--defined data type with a newer
version
S If the Start Pages are unavailable or
if students prefer, use the
CCP143_1756r_DEM2.acd project.
UDTsb56r
UDTsb56r
Exercise: Creating a User-Defined Data Type in an RSLogix 5000 Project 5--7
Exercise: Creating a User-Defined

Data Type in an RSLogix 5000
Project
Exercise A In this exercise, you will practice the following tasks:

Context:
You have just created and organized a project file for your line 1
production line. You are now ready to develop code for a second,
identical, production line. Your application requires that you store
each production line’s output information in user-defined tags.

Directions:
1. Open the UDT_1756r_A1.acd file.
2. Create a UDT named Motor_Status with the following

members:
Name Data Type

Active BOOL
Fault BOOL
ProcessTime DINT
MotorSpeed REAL

 Name: Line_1
 Type: Base
 Data Type: Motor_Status
4. Open MainRoutine within the Line_1 program.
5. Modify rung 4 so that member Line_1.Active is the operand of
the OTE instruction.
6. Modify rung 5 so that member Line_1.ProcessTime is the
Destination operand of the Move instruction.
7. Modify rung 6 so that member Line_1.MotorSpeed is the
UDTe56r
5--8 Exercise: Creating a User-Defined Data Type in an RSLogix 5000 Project

 Name: Line_2
 Type: Base

workstation.
15. Verify you properly created your UDT tags by monitoring them
and confirming they update in value when Lines 1 and 2 are
operating.
16. Export the Motor_Status user-defined data type project
component.
17. Go offline.
18. Open the UDT_1756r_A2.acd file.
19. Import the Motor_Status user-defined data type project

component into the UDT_1756r_A2.acd project.
20. From the Import Collision dialog box, click Collision Details.
21. What information changed in the imported UDT?
22. Click Close.
23. Overwrite the existing Motor_Status UDT and keep the same
final name.
24. Click OK .
UDTe56r

 Name: Line_3
 Type: Base
workstation.
32. Verify you properly created your UDT tags by monitoring them
and confirming they update in value when Line 3 is operating.
33. Go offline and close your projects.
UDTe56r
Answers Exercise A
2. Your Motor_Status UDT should look similar to the following

example:
7. Rungs 4--6 of the MainRoutine in the Line_1 program should

now look similar to the following example:
UDTe56r
21. The data type size and the structure changed.
23. You should have configured the imported UDT as follows:
UDTe56r

UDTe56r
Lesson 6
Note that this lesson briefly reviews Entering, Editing, and Verifying
some concepts from the prerequisite
course before presenting more Ladder Logic in an RSLogix 5000
advanced concepts such as Quick Keys.
Tailor this lesson as needed. Project
Poll the students to see how many have  Enter and edit ladder Logic using ASCII mnemonics
experience using a Window’s-based
programming software from their job, or  Configure ladder logic quick keys
pre-requisite classes.  Copy and reuse ladder logic components
Pace this lesson based on the general  Verify a project or a project component (online)
experience level of your class.
Describe which method you personally When You Will Do This

find to be fastest and/or easiest when
entering ladder logic. Once you have laid out your task and program structure and defined
your data types, you can begin to develop your ladder logic.
Before You Begin Entering and Editing Ladder Logic Components
Review the first two methods if needed. The RSLogix series of software offers the ability to enter or edit
Students should be familiar with these. ladder logic using the following basic methods:
 Dragging method
 Right-click/Insert key
The RSLogix series of software also offers faster methods for more
proficient programmers:
 ASCII mnemonic editing
 Quick keys
EN2sb56r
6--2 Entering, Editing, and Verifying Ladder Logic in an RSLogix 5000 Project
ASCII Mnemonic Editing

State that ASCII stands for the American ASCII mnemonics are text codes that represent instructions and
Standards Code for Information ladder logic elements:
Exchange.
ASCII Text
Entry Line
Graphical
Ladder
Logic
Read each mnemonic in the graphic and In the graphic, note the following items:
show the corresponding graphical
element.  The mnemonics are entered, followed by the tag to be operated
on or a “?” or a space.
Note that unlike RSLogix 5 and 500  Start and end points for branches can also be entered:
software, in RSLogix 5000 the ASCII line
is not highlighted by default and -- BST (Branch start)
therefore more difficult to accidentally -- NXB (Next Branch)
erase.
-- BND (Branch End)
Configuring Ladder Logic Quick Keys
To quickly enter instructions and other ladder logic elements using

Point out that Quick Keys are enabled in single keyboard keys, assign quick keys:
the Options for the Ladder Editor. This
step is included in the procedure in the  Quick keys for several common instructions including XIC, XIO,
Procedures Guide.
and OTE are already assigned.
 Quick keys must be enabled to be used.
Copying and Reusing Ladder Logic Components
Describe examples of real applications, If ladder logic contains program-scoped tags, the ladder logic can be
such as auto production lines, where easily copied and reused in different programs without changing the
common machine cells are repeated.
tag names.
EN2sb56r
Entering, Editing, and Verifying Ladder Logic in an RSLogix 5000 Project 6--3
Example: Copied Ladder Logic

Because the programs are local, the same ladder logic and the
tags (e.g., Station_Timer) can be copied to all programs.
Same
Program_Scoped
Tag Name
Different Program
Same
Program_Scoped
Tag Name
Easy Copy and Paste
The tags within the program are commonly alias

tags for different I/O points.
Remember that controller-scoped tags are shared

by all programs. Be careful when accessing the
same controller-scoped tag from different
routines.
EN2sb56r
Other Short-Cuts
These additional methods will also make you a more efficient
programmer:
 RSLogix 5000 software also offers the ability to open a second
instance of the software:
-- This allows you to easily copy and paste ladder logic between
two open files.
 For ladder logic and structured text, you can save instruction
defaults:
-- These defaults are saved to the computer and apply to all
projects opened on the computer.
State that up to four instances of the Verifying a Project or a Project Component Online
software can be opened at one time.
Modifying code online can help you quickly make changes without
Note that you
file, close can open
the file, also copy from one
a different file, stopping production.
and then paste into the other file. The
copied information is maintained
on the clipboard. Online Safety Warning
When editing ladder logic online, keep the following warning in
mind:
Describe any real-world situations that Use extreme caution when entering or editing
you are aware of in which online editing ladder logic or data, forcing values, or making other
caused extensive damage in a plant.
changes online that will affect the control of
devices. Mistakes can cause unintended machine
motion or loss of process control, possibly injuring
personnel and damaging equipment. Before
? Define offline and online? performing procedures online, complete these safety
Answer: Offline means that the precautions:
workstation (computer) is displaying a  Determine if changes must be made online.
copy of the project stored in the
computer memory only. Online means  Verify that your company permits online
that the workstation (computer) is entering and editing.
displaying and changing copy of the
project stored in the controller memory.  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.
Add that the Online graphic is animated Because changes in any online mode can affect
in any online mode. machine and process control, before entering
Also note that the left and right power ladder logic, verify the current communications
rails are illuminated in green in the mode using the Online toolbar.
online mode to indicate that the ladder
logic is being executed.
EN2sb56r
Performing Online Ladder Logic Edits

Editing ladder logic elements online requires different steps in
different modes:
State that the additional online steps are When editing in You must perform the
another reason that online editing is this mode . . . following actions . . . Description . . .
slower and more difficult. The extra Routine(s) edits exist only in the
steps are in place for user safety.
computer. Necessary when changing
Start edits
an existing rung, but not necessary to
add a new rung.
Tell students that the Verify edits step Online in the Remote The project is examined for errors.
can be considered optional since the Program mode Verification can be done separately or
verification process will automatically Verify edits
automatically if you skip to the Accept
take place with the Accept edits step.
edits step.
The revised routine(s) are transferred
Accept edits
to the controller.
Routine(s) edits exist only in the
computer. Necessary when changing
Start edits an existing rung, but not necessary to
add a new rung.
State that “accept” puts the change into The project is examined for errors.
the controller memory. Verification can be done separately or
Verify edits
automatically if you skip to the Accept
edits step.
The revised routine(s) are transferred
Online in the Remote
Accept edits to the controller but the previous
Run mode
program continues to execute.
Important: Stress the difference The revised routine(s) executes,
between controller Remote Test mode controlling the physical outputs, but the
(outputs set according to Program mode Test edits previous program still exists in the
state) and the Test edits step in Verify,
Accept, Test, Assemble (outputs controller. You can return to the
previous program using Untest edits.
scanned and set using the program).
Program mode state is set in the output The previous routine(s) language is
module configuration. Assemble edits discarded and the revised program
continues executing.
If students are interested, review the Online verification buttons can be used to complete this process:
names of all of the buttons during the
demonstration using the Tooltips. Standard Toolbar
Verify Open Routine Verify

Controller
Single-Rung Options Program-Level Options
Online Edit Toolbar
Cancel Pending Rung Edit Finalize Edits Option
Tip " Use tooltips to identify the buttons.

EN2sb56r
For the invalid data type error, clarify When verifying, the software looks for the following errors:
that a tag of the DINT data type cannot
be used in an XIC bit instruction unless it  Improper instruction placement
is specified to the bit level (e.g., DINT.0  Improper or incomplete addressing
and not just DINT).
 Tags with an invalid data type for the instruction (mismatches)

Improper tag creation
 Empty rungs
 Shorted branches (reported in error tab as a warning)
 Duplicate destructive bits (reported in error tab as a warning)
Point out that this option can be enabled The duplicate destructive bit option looks for
using Tools Options.

instructions that modify the same bit. This
Mention that this is known as “duplicate includes instructions such as OTE, ONS, OSF,
OTE detection” in PLC/SLC processors. and OSR instructions in ladder logic. This option
Note that this also includes bits used in is enabled by default.
other languages, such as OREFs in
FBD, bits in transitions in SFCs, and bit
assignments in ST.
 Presence of Always False Instruction (AFI) (reported in error tab
as a warning)
 Presence of forces (reported in error tab as a warning)
Note that this is an option found Auto Rung Verification: An option that can be enabled to
in the Tools Options dialog box.

automatically verify a rung.
Errors found in the verification process are displayed on the Errors

tab of the Output window:
Double-Click to
Go to the Error or
Press F4
Finalize Edits Option

Point out some benefits of this option: The Finalize Edits option allows you to complete online edits in one
S Fewer steps required to go from step.
change to running code
S Reduces system startup time by For equipment and personnel safety, the full
eliminating delays
sequence of steps (verify, accept, test, assemble)
Compare these benefits to some of the should be used as it requires the programmers to
inherit risks.
check the steps and test them before assembling
them in the controller. The Finalize Edits option
should be reserved for changes that will not impact
safety.
EN2sb56r
Edit Zone Markers

Poll the students to see if they are aware When you start editing online, a duplicate rung is displayed:
of online editing policies in their own
companies.
Edit Rung
Original Rung
(Active in Controller)
Rung numbers after the edit are temporarily

changed while the edit rung is being modified.
Mention that an asterisk “ :” on any During the editing and verifying process edit zone markers indicate
instruction, tab, etc., indicates that the the type of edit that is being performed:
element has been edited but not yet
accepted.
Once the edit in Remote Run mode is accepted
into the controller memory, the markers change to
uppercase letters.
Note that these markers are the same The following table summarizes the zone markers and their
as the edit markers in RSLogix 5 and meanings:
500 software.
Point out that for reference, this Zone Marker Description
information is in the Procedures Guide
Glossary under the term “Edit Zones.” Rung of ladder logic that is currently edited within
e
the computer RAM
Lowercase
i Rung of ladder logic that is to be inserted
r Rung of ladder logic that is to be replaced
I Rung of ladder logic that will be inserted
Uppercase (in
Rung of ladder logic that is going to be replaced by
controller R
the rung directly above it
memory)
D Rung of ladder logic that is marked for deletion
EN2sb56r
Online Editing in a Multiple-User Environment

RSLogix 5000 software allows more than one user to be online with
the same controller at the same time:
 Each user has an up-to-date view of the controller data

Changes
users. made by one user are immediately seen by all other
Two programmers may be online Question: In what situations might two programmers be online to
to the same controller during the same controller?
commissioning or if a controller
has a large main routine with multiple
blocks of code (i.e., each block of code
controls a different machine in a Status icons in the Online toolbar and bottom-right corner of the
system).
screen show if multiple users are editing an online project:
Online Toolbar Bottom Right

Corner of Screen
Selected
Controller Unlocked
Controller Locked
Controller Locked by Another User
Project Changed by Another User
Keep the following points in mind about editing ladder logic when
multiple users are online:
 A common best practice is to lock the controller:
-- This ensures only one person can be making edits to the logic
at one time.
 If more than one programmer must be making changes at the
same time, carefully coordinate your work so changes aren’t
being made to the same routine at the same time:
-- Edits to a routine by one programmer can wipe out pending

edits by other users.
 If possible, avoid having two programmers working on different
routines in the same program:
-- The routine edit commands (Accept, Test, Untest, Assemble,
and Cancel) are performed on a program basis.
-- Executing one of these commands affects another user’s edits,
causing potential loss of work.
EN2sb56r
Here’s How To enter ladder logic by performing the following tasks:

 Enter and edit ladder Logic using ASCII mnemonics
 Configure ladder logic quick keys
 Copy and reuse ladder logic components

Verify a project or a project component (online)
project during the demonstration:
" To copy and reuse rungs,
instructions, and branches, refer to - Entering logic using the ASCII text editor
the Copying and Reusing Project
Components procedure.
- Online verification buttons
- Locking the controller
EN2sb56r
EN2sb56r
Exercise: Entering, Editing, and Verifying Ladder Logic in an RSLogix 5000 Project 6--11
Exercise: Entering, Editing, and

Verifying Ladder Logic in an
Exercise A In this exercise, you will practice entering, editing, and verifying
ladder logic in an RSLogix 5000 project.
Context:
You have been asked to add the ladder logic that will be used to
control the sequential portion of your application to an existing
project.

Directions:
1. Open the EN2_1756r_A1.acd file.
2. Download the project and then change the controller to Remote

Run mode.
3. Lock the controller to prevent other users from making online
changes to your project.
4. Open SecondaryRoutine and perform the following actions:
A. Using any method you choose, create the following ladder
logic:
If the value from AI0 is greater than 500, turn on DO0.
B. Assign the existing AI0 and DO0 tags to the logic
components.
C. Verify the rung (online).
D. Test the operation by setting analog input 0 (AI0) to a value

over 500.
E. Check that digital output 0 (DO0) turns on. If not, return and
modify your work.
EN2e56r
6--12 Exercise: Entering, Editing, and Verifying Ladder Logic in an RSLogix 5000 Project
F. Use the ASCII mnemonic editing method to enter the

following rung:
G. What does your ASCII text entry line look like for this rung?
(What syntax did you use?)
H. Save and accept the edits and test for proper operation of this
rung.
I. Test the operation by setting analog input 0 (AI0) to a value
between 100 and 200.
J. Check that digital output 0 (DO1) turns on. If not, return and
modify your work.
K. Once your work is correct, turn analog input 0 all the way to
the left to shut off the light.
L. Copy the rung you created in step 4. A. and reuse it to
program the following logic, modifying the rung as
necessary:
If the value from AI0 exceeds 700, turn on DO2.
M. Save the edits.
N. Test the operation by setting analog input 0 (AI0) to a value

over 700.
O. Check that digital output 2 (DO2) turns on. If not, return and
modify your work.
P. Enable the quick keys.
EN2e56r
Q. Configure the F5 key to be the RUNG (Start of Rung -- End

of Rung) command.
R. Using the quick key method, create the following logic and
necessary tags:
If DO0 has been on for three seconds, turn on DO3. If DO0

is turned off, DO3 turns off as well.
S. Save and accept the edits and test for proper operation of
your rung.
T. Are any of these cases where you could use the Finalize Edits
option? Why or why not?
5. When you are finished editing the program, unlock the controller.
EN2e56r
Answers Exercise A
4.
A. The rung should look similar to the following example:
G. BST LIM 100 AI0 200 NXB EQU AI0 300 BND OTE DO1
L. The rung should look similar to the following example:
P. To enable the quick keys, from the Tools menu, perform the
following actions:
-- Select Options Ladder Editor.

-- Select the Enable Quick Key check box.

-- Select the Show Quick Key Configuration check box.
EN2e56r
Q. To assign F5 as the SOR command, perform the following

actions:
-- On the Workstation Options Ladder Editor window, click
the Configure button.
-- Scroll to F5 and then double-click _Free.
-- From the drop-down list, select Rung.
R. The rungs should look similar to the following example:
T. The Finalize Edits option should only be used when there is

no safety concern. If this indicator light is not a safety-related
indicator, the Finalize Edits option could be used.
EN2e56r
EN2e56r
Lesson 7
Communicating with a Local
1756-I/O Module
What You Will Learn After completing this lesson, you should be able to manually add a
1756-I/O module to an I/O configuration.
You can add your I/O modules to your project before, during, or after
you develop your application logic. At some point though, you have
to add the I/O modules so you can link your logic to specific devices.
Reference: RSLogix 5000 and Logix5000 Procedures Guide
1. Find the Adding a Local or Remote 1756--I/O Module to an I/O

Configuration procedure in your procedures guide.
2. Briefly read the Get Ready steps.
In this lesson you’ll focus on Question: What does the term local I/O mean? Remote I/O?
adding local modules.
Question: When do you usually add I/O modules to your projects?
Point out that in this lesson you’ll Question: Are the modules usually installed at that point? Do you
manually add the modules. usually have access to them?
Before You Begin Electronic Keying
Before you add an I/O module, plan your electronic keying:
Electronic Keying
and Revision Level
IO2sb56r
7--2 Communicating with a Local 1756-I/O Module
If you have already presented the The electronic keying feature:

Troubleshooting Logix5000 Analog I/O
Module Problems lesson, the discussion  Automatically compares the expected module (as shown in the
on electronic keying, keying attributes, I/O Configuration tree) to the physical module before I/O
keying examples, and disabled keying communications begin
can be skipped.
 Helps prevent communications to a module that does not match
the type and revision expected
 Determines if and how an electronic keying check is performed
Typically, three keying options are available:
 Exact Match
 Compatible Keying
 Disable Keying
Tip " The compatible keying option is the default selection.
Keying Attributes
Electronic keying is based on these attributes:
 Vendor
 Product Type
 Product Code
 Major Revision
 Minor Revision
Example: Exact Match Keying Prevents Communication
Module Configuration
Vendor = Allen-Bradley
Product Type = Digital Input Module
Catalog Number = 1756-IB16D
Major Revision = 3
Minor Revision = 1
Communication is Prevented
X
Physical Module
Major Revision = 3
Minor Revision = 2
IO2sb56r
Communicating with a Local 1756-I/O Module 7--3
Example: Compatible Keying Prevents Communication
Major Revision = 3
Minor Revision = 3
Physical Module
Communication is Prevented
X
Major Revision = 3
Minor Revision = 2
Example: Compatible Keying Allows Communication
Major Revision = 2
Minor Revision = 1
Communication is Allowed
Physical Module
Major Revision = 3
Minor Revision = 2
IO2sb56r
Disabled Keying
With Disabled Keying, I/O communication may occur with a module
other than the type specified in the I/O Configuration tree with
unpredictable results.
We generally do not recommend using Disabled Keying.
Be extremely cautious when using Disabled

Keying; if used incorrectly, this option can lead to
personal injury or death, property damage, or
economic loss.
Asynchronous I/O Update Review
Point out that this is different from other In Logix5000 controllers, I/O values update asynchronously with the
controllers that have an input scan, then execution of code:
a program scan (code), and then an
output scan within the operating cycle. 1. Input modules multicast their data to the backplane at the RPI rate
set in the modules.
2. The code is scanned and the output tags are updated immediately
after the execution of each output instruction.
3. Values are sent to the output modules at the RPI rate and at the
end of each task.
Tip " The automatic output processing that occurs at the end of a task can
be disabled in the properties of the task.
Digital Module Multicasting Rates
Note that these values must be set in The multicasting of digital I/O data is affected by the rates selected
the initial configuration but can be during module configuration:
adjusted at any time.
 RPI (Requested Packet Interval)
 COS (Change of State)
RPI (Requested Packet Interval)

The RPI controls the following actions:
 Specifies the time that elapses before the module multicasts the
current data in the on-board memory:
-- 200 microseconds (.2 ms) -- 750 ms
IO2sb56r
COS (Change of State)

When the COS option is enabled for digital I/O, data transfer occurs
whenever a specified terminal changes state (transitions from on to
off or off to on):
 All data is multicast whenever one point changes state.
To clarify, state that COS multicasts An RPI for digital I/O must be specified whether
module data on any change of state and or not the COS option is enabled. Data will be
RPI multicasts module data at a
specified time. multicast at the RPI rate whether or not a change
of state occurs.
Point out that the input data is changing Example: RPI and COS
within the scan of the logic.
Single Scan
Physical Device Data is Tag is set or cleared in controller
received by the input card
Rung
RPI Rate
100
COS Rung
250
Optional
Rung
RPI Rate
400
Analog Module Multicasting Rates
Note that analog module multicasting The multicasting of analog data is affected by the rates selected
rates are different from digital modules during module configuration:
that multicast based on RPI or COS
parameters.  RPI -- This parameter works in the same manner as it does for a
digital module
Note that RTS is actually set on a  RTS - (Real Time Sampling Rate)
different screen, but is discussed now
with RPI.
IO2sb56r
RTS (Real Time Sampling Rate)

The RTS instructs a module to perform the following operations:
 Scan all of the input channels and store the data in the on-board
memory

Multicast
backplanethe updated
of the local channel
chassis data and other status data to the
Tip " RPI multicasts the current contents of the on-board memory. RTS
scans the inputs prior to multicasting.
Output States
For output modules, output states during specific situations can be

set on the Configuration tab:
Output States During

Program Mode
Output States During

Fault Mode
Output State During

Communication Failure
in Program Mode
Output States are Set Per Point
Operators and other personnel should be aware of the configured

output states for these situations:
Example: An application that includes a  Program Mode: Sets the physical output devices to either on,
hot oven might set a fan output to on off, or hold during specific situations:
during Program, Test, or Fault mode.
-- Program or Remote Program mode
-- Remote Test mode
-- During a major recoverabl e fault
 Fault Mode: Sets the physical output devices to either on, off, or
hold during a major non-recoverable fault.
IO2sb56r
Diagnostics
On the Configuration screen of the wizard, the following other

parameters must be defined:
Diagnostic Features
I/O Points
? How are diagnostic modules Depending on the module, 1756 digital and analog diagnostic I/O
identified in the part number? modules have the following diagnostic features:
Answer: The part number has a “D” as
the suffix, e.g., 1756-IB16D. Open Wire Detection: Open wire detection senses removed or
disconnected field wiring on an input module:
 A leakage resistor must be placed across the contacts of an input
device.
 The modules must detect minimum leakage current or a
point-level fault is sent to the controller.
Field Power Loss Detection: When field power to a module is lost,

a point-level fault is sent to the controller.
No Load Detection: Senses the absence of field wiring or a missing

load from each output point in the off state only.
Field Side Output Verification: Indicates that the code changes are

accurately represented on the power side of a switching device (i.e.,
the output is on when it is commanded to be on).
Note that the pulse test is typically Pulse Test: Briefly sends a signal that verifies the output without
performed during commissioning or energizing the load.
troubleshooting.
IO2sb56r
Point-Level Electronic Fusing: To prevent too much current from

flowing through a module, certain digital modules have internal
electronic fusing. The fuses are cleared when one of the following
Mention that fault data can be monitored actions occurs:
in controller tags for each module. To
create a status window, collect fault data  A message instruction in the software resets the fuse.
in a user-defined structure.  A power cycle resets the fuse.
Add that latching can help you see Diagnostic Latching

where a fault occurred even if the cause
of the fault has already been cleared If any of the diagnostic faults are detected, the following events
(e.g., if the fault occurred and cleared occur:
overnight).
 The fault data is multicast to all controllers.
Note that diagnostic modules require the
most configuration. The workstation  The I/O module LED displays a fault.
modules are diagnostic. This will give
students the most practice. All other  A fault bit is latched and can be examined in the tags list.
modules are just subsets.
Even if the cause of an error has been cleared, the fault will remain
set until one of the following actions occurs:
 The fault bit is manually reset in the I/O Module Properties dialog
Note that resetting the module manually box.
is done by individual points. There is no
“reset all points” option.  A message instruction in a ladder logic routine resets the latch.
For a standard course, note that the CIP  A power cycle resets the output module.
message instruction that resets the
diagnostics will be presented in the
Configuring a Message in an You cannot enter a “0” into the I/O fault tag to
RSLogix 5000 Project lesson. reset it.
If the Diagnostic Latching parameter in
the configuration is not set, the fault bit
will clear when the source problem is
removed. Turn off the diagnostics for I/O points that will
not be wired. Otherwise, the LED fault lights on
the module will be active for unused I/O points,
possibly confusing maintenance personnel who do
not know that the points are unused.
IO2sb56r
Here’s How To plan your electronic keying decisions for the module.
Reference: RSLogix 5000 and Logix5000 Procedures Guide
1. Make sure you are still at the Adding a Local or Remote
1756--I/O Module
procedures guide. to an I/O Configuration procedure in your
2. Find the Manually Add an I/O Module section of the procedure.
Give students several situations. 3. Briefly read through the decision table for planning your
Have them use the decision table electronic keying decision.
to determine which keying option
to use.
Activity: Who’s got the lowest rev?
You have decided to use compatible keying in your project. Consider

the rest of the I/O modules in your classroom as possible
replacements. Determine the lowest revision level for each module:
1. Find the I/O wiring diagrams in the back of this manual.
2. Go to your workstation and open RSLinx software.
3. Browse to the backplane of your workstation.

4. Right--click the first module in the chassis and click Device
Properties.
5. Write the revision level for the module on its wiring diagram.
6. Repeat steps 4. and 5. for the rest of the I/O modules in the
chassis.
7. Compare your results with the rest of the class and determine the
lowest revision for each catalog number of module. Write that
number on the module’s wiring diagram, circle it, and plan to use
it in the exercise at the end of this lesson.
Result: When you are done, you should have a decision on which
revision level to use for each of your I/O modules.
IO2sb56r
Here’s How To manually add a 1756-I/O module to an I/O configuration.
IMPORTANT: To meet IACET Reference: RSLogix 5000 and Logix5000 Procedures Guide

CEU requirements and fully
prepare certificate students for
the final exam, you must Talk your instructor through the steps in your procedures guide while
demonstrate all lesson
using objectives
the proper job aids. he or she demonstrates them.
To demonstrate:
1. Open the
CCP143_1756r_DEM3.acd project.
2. Have students talk you through
adding a digital module.
3. Have student talk you through
adding an analog input module.
4. Have student talk you through
adding an analog output module. Pay attention to these critical aspects of the demonstration:
- Where to clear diagnostics for unused points
- Where to set analog scaling and alarm values
- Where to set clamping limits
- How to confirm communication is OK after you download

the project
- Where to find tags for point data, channel data, point

faults, and alarms
- Where to reset latched diagnostics
IO2sb56r
Exercise: Communicating with a Local 1756-I/O Module 7--11
Exercise: Communicating with a

Local 1756-I/O Module
Exercise A In this exercise, you will practice adding and configuring local
1756-I/O modules to the I/O Configuration of an RSLogix 5000
project.
Directions:
1. Review the partial I/O list below for your application:
Device Tag (Alias) Scope Slot Chan Signal Min / Off Max / On
Part Present
Part_Sensor IO2_1756r_A1 2 12 24 VDC Sink No Part Part
Photoeye
Press and Stake

Pressure CH0_Analog_Input Conveyor 8 0 0--10 VDC 0.0 100.0
Transmitter
Press and Stake
CH0_Analog_Meter Conveyor 7 0 0--10 VDC 0.0 100.0
Pressure Indicator
Weld Pressure
CH1_Analog_Input Conveyor 8 1 0--10 VDC 0.0 1000.0
Transmitter
Weld Pressure
CH1_Analog_Meter Conveyor 7 1 0--10 VDC 0.0 1000.0
Indicator
Conveyor Motor 24 VDC Start
Conveyor Conveyor 0 1
Starter Source Command
Conveyor Start
Start Conveyor 2 0 24 VDC Sink Start
Pushbutton
Conveyor Stop
Stop Conveyor 2 8 24 VDC Sink Stop
Pushbutton
24 VDC Press
Press Actuator Station_Output Station_1_Press 0 3
Source Command
24 VDC Stake
Stake Actuator Station_Output Station_2_Stake 0 4
Source Command
2. Review the partial alarm list below for your application:
Device Alarm (Alias tag) Scope Slot Chan Signal Trip

Part Present Photoeye Part_Sensor_PointFlt Conveyor 2 12 24 VDC Sink Point Fault
Conveyor Start Pushbutton Start_PointFlt Conveyor 2 0 24 VDC Sink Point Fault
Conveyor Stop Pushbutton Stop_PointFlt Conveyor 2 8 24 VDC Sink Point Fault
Conveyor Motor Starter Conveyor_PointFlt Conveyor 0 1 24 VDC Source Point Fault
Press and Stake Pressure
Alarm_High Station_1_Press 8 0 0--10 VDC >60
Transmitter
Press and Stake Pressure
Alarm_Low Station_1_Press 8 0 0--10 VDC <40
Transmitter
Weld Pressure Indicator Alarm_High Station_2_Weld 8 1 0--10 VDC >600
Weld Pressure Indicator Alarm_Low Station_2_Weld 8 1 0--10 VDC <400
IO2e56r
7--12 Exercise: Communicating with a Local 1756-I/O Module
3. Open the IO2_1756r_A1.acd file.
4. Add these modules to your project’s I/O Configuration. Use the

I/O list, alarm list, wiring diagrams, and your class notes for any
additional information you need:
Slot Suggested module name

- 0 Assembly_Digital_Outputs
- 2 System_Digital_Inputs
- 7 Assembly_Pressure_Meters
- 8 Assembly_Pressure_Sensors
5. Convert these tags to aliases for correct data:
- CH0_Analog_Input
- CH1_Analog_Meter
- CH1_Analog_Input
- CH0_Analog_Meter
6. Convert the tags on the alarm list to aliases for the correct fault or
alarm bits.
7. Save your project and download it to the controller.
IO2e56r
8. Test the application and verify that it meets the requirements

below. Correct any problems you find:
Requirement Test / verification method

- No I/O module faults. Visually check the controller and I/O Configuration folder.
- No point--level faults for any unused I/O points. Visually check the front of each digital I/O module.
Monitor the tag in logic and confirm that its minimum and
- CH0_Analog_Input shows the range of values.
maximum values match the I/O list specification.
- CH0_Analog_Meter shows the range of values.
- CH1_Analog_Input shows the range of values.
- CH1_Analog_Meter shows the range of values.
High and low alarms for Press and Stake Pressure Transmitter Monitor the alarm bits in logic and confirm they turn on at the
- trip on specified limits. specified limits.
High and low alarms for Weld Pressure Transmitter trip on Monitor the alarm bits in logic and confirm they turn on at the
-
specified limits. specified limits.
A. Remove the terminal block of the digital output module and
confirm the Conveyor_Flt bit turns on.
B. Replace the terminal block.
Conveyor_Flt bit turns on for any point fault of the conveyor C. Reset any latched diagnostic bits.
- equipment. D. Remove the terminal block of the digital input module and
confirm the Conveyor_Flt bit turns on.
E. Replace the terminal block.
F. Reset any latched diagnostic bits.
IO2e56r
Answers Exercise A
4. The complete I/O configuration for the should look like this:
Only these points need diagnostics:
Only points 0 to 5 are wired to

devices. Faults for points 6 to 15
are not set. Otherwise, faults will
be indicated on the module
LEDs.
IO2e56r
You should have configured the analog outputs like this:
IO2e56r
You should have configured the analog inputs like this:
IO2e56r
5. Your analog aliases should look like this:
6. Your alarm aliases should look like this:
IO2e56r
IO2e56r
Lesson 8
Configuring a Logix5000 Controller
to Produce and Consume Data
What You Will Learn After completing this lesson, you should be able configure a
Note that in the lesson, data will be Logix5000 controller to produce and consume data by performing
produced and consumed over the the following tasks:
backplane. While this might not be as
common as producing and consuming  Configure a produced tag
them over a network, it will allow
students to practice sharing data before  Add a controller to an I/O configuration
going into the details of the ControlNet  Configure a consumed tag
or EtherNet/IP network.
 Set RPI limits for a produced/consumed tag
Add that a separate lesson is available

for sharing data between controllers
over a ControlNet or EtherNet/IP When You Will Do This
network.
Use produced and consumed tags when you want to share data
between controllers.
Before You Begin Scheduled Data
Scheduled Data: Information that is sent across a control-level

network, such as ControlNet or EtherNet/IP, on a regular basis. This
data has the following characteristics:
?What type of data would be  Is time critical, such as I/O status and control interlocking data
considered time-critical for your

application?  Has top priority in information exchange
 Occurs in the same time frame during every data transmission
interval
Note that sharing unscheduled data with  Can be any of the following:
a MSG instruction is presented in a
separate lesson. -- Data from an I/O module
-- Peer-to-peer interlocking data of controllers
To control I/O or produce and consume tags in a

Logix5000 ControlNet application, data must be
scheduled.
PC3sb56r
8--2 Configuring a Logix5000 Controller to Produce and Consume Data
Produced and Consumed Tags
In the graphic, point out that the Total Produced Tag: Scheduled data (controller-scoped tag) that is
tag is available to any other controller on published (multicast) by a controller and available to one or more
the backplane.
other controllers:
Note
reachthat
twothe tag is stillit multicast.
controllers, To to
does not have Total
be passed to one (like a message) then
be passed to another.
Consumed Tag: A tag whose value comes from a remote controller.

The local controller is the consumer, and the remote controller is the
producer. Consumed tags are always at controller scope.
Produced and Consumed Tag Requirements
Data that meets the following requirements can be shared by

Note that these are the 32-bit data controllers without using messages:
types.
 Tag that is 32 bits or larger (e.g., DINT, REAL, TIMER,
Add that 500 bytes equals 125 DINTs or COUNTER, etc.), an array of these data types, or user-defined
250 INTs. data type
 Data that is less than or equal to 500 bytes
PC3sb56r
Configuring a Logix5000 Controller to Produce and Consume Data 8--3
Remind students that this is the tag Configuring a Produced Tag

being “sent”.
In the Tag Properties dialog box, you can configure a tag to be
produced:
Produce Option
Data Access
Options
Highest Possible Advanced

Number of Settings
Consumers
PC3sb56r
Note that this is the name of the Adding a Controller to an I/O Configuration
controller and not the project (if
different). To share data, a path is created by adding the producing controller to
Note that the I/O Configuration identifies the I/O configuration of the consuming controller and defining the
if the tag is being produced locally or following parameters:
over a network (and which network).
 Name of the producing controller
 Slot number
 Revision (major and minor):
-- Electronic keying is compatible.
 Optional:
-- Description
-- Major fault option
-- Inhibit option
Local Controllers
Add thatorthe
created consumed
it can tag cantag
be an existing be that Configuring a Consumed Tag
is modified.
A controller can only consume a single tag once.
Setting up more than one consumed tag in the
same controller results in unpredictable
controller-to-controller communications.
If a consumed tag connection faults, all other tags

being consumed from the producing controller
will also stop receiving data.
PC3sb56r
A consumed tag is also defined in the Tag Properties dialog box:
In the graphic, point out that

the RPI is per tag and not
controller.
Name of the Consumed Tag
Mention that you must be offline or

online in Program mode to
change the RPI.
Consumed Option
Mention that RPI in relation

to the ControlNet
detailed in a network will be
different lesson.
Source Controller
(as Named in the I/O
Configuration)
Exact Name of the Produced
Tag in the Producing Controller
The Amount of Time
Between Updates of the
Data
PC3sb56r
Tag Names
Point out that this is not the consumed The Remote Data (source tag name) must be exactly the same as the
tag name. produced tag name in the producing controller.
Tip " For accuracy,

should the source project should be opened and the tag names
be copied:
Producer
Consumer
Same
Note that consumed tag names do not If a user-defined structure is produced, there must
require naming conventions through the be a structure with the identical size and layout in
software. However, your plant may opt
to use naming conventions to make the consuming controller. To ensure accuracy,
troubleshooting easier. copy the structures between projects.
Emphasize that if structures are the
same size but different layout, data from
the first member in structure A (e.g., a
REAL) will incorrectly transfer to the first Producer
Data Consumer
member in the other structure B (e.g., a DINT TIMER
DINT).
DINT BOOL
BOOL DINT
TIMER DINT
Producer Data Consumer

DINT DINT
DINT DINT
BOOL BOOL
TIMER TIMER
PC3sb56r
Produced and Consumed Arrays
BOOL, SINT, and INT arrays can be indirectly produced and

consumed by performing the following actions:
 Create a user-defined data type containing a single member:
-- Make the single member an array of the desired type
 Copy this user-defined data type to both controllers
 Produce and consume tags of this data type
In addition, you can produce/consume an array of INTs to/from a
PLC-5C controller over a ControlNet network by performing the
following actions:
 Define a user-defined data type with two members:
-- Name the first member Status and assign it a DINT data type
-- Make the second member an array of INTs
Produced Tag Optimization
Note that a separate lesson reviews the The number (and not size) of consumed tags is totaled and counted
number of connections consumed by against the number of connections a system can support.
produced and consumed tags.
To limit the number of connections used, consider

grouping data into an array or a user-defined data
type and producing only that array or structure.
A produced or consumed tag cannot be greater

than 500 bytes (250 INTs or 125 DINTs).
PC3sb56r
Tell the students that when the RPI Produce/Consume Tag RPI Limits Check
request from a consumer is
out-of-range, an automatic negotiation
will allow the consumer to connect to the If someone types a wrong RPI value for a consumed tag, it could
producer by using the default RPI value overload the network and halt production. To prevent this, you can:
configured for the produced tag.
 Define a range of acceptable RPI values for each connection.
RPI negotiation
the user status will be
via the Consumed reported to
Tag  Define a default RPI value for out-of-range RPIs:
Connection dialog.
Produced Tag Values
Minimum, Maximum and
Default values can be modified
Offline only.
Set Min and Max

RPI Range
Set Default RPI
Consumer
is RPI of 2ms
out of range. = Consumer
get RPIdefault
set to the would
value of 10ms.
PC3sb56r
Configure the consuming controller to use the default RPI:
Advanced Tab
Enable RPI
Negotiation Here
PC3sb56r
Here’s How To configure a Logix5000 controller to share data across the

backplane by performing the following tasks:
 Configure a produced tag
 Add a controller to an I/O configuration

Configure a consumed tag

 Set RPI limits for a produced/consumed tag
for the final exam,
project during the demonstration.
Use the CCP143_1756r_DEM5.acd file
to download to the controller in slot 3. - Produced check box in the Edit Tags window
- Produced For default (2)
- Values in both controllers when the produced value

changes
- Tags filter to show produced or consumed tags only
PC3sb56r
Exercise: Configuring a Logix5000 Controller to Produce and Consume Data 8--11
Exercise: Configuring a Logix5000

Controller to Produce and
Consume Data
Exercise A In this exercise, you will practice configuring Logix5000 controllers

to produce and consume data across the backplane.
Context:
You have programmed the complete projects for the controller in slot
1 and the controller in slot 3. To exchange interlocking data between
the controllers, you must configure the controllers to produce and
consume data across the backplane.
Tank level information must be produced from the controller in slot

1 and consumed by the controller in slot 3:
Producer Consumer

Directions:
1. Open the PC3_1756r_A1.acd file.
2. What scope must tags be in order to be produced or consumed?
PC3e56r
8--12 Exercise: Configuring a Logix5000 Controller to Produce and Consume Data
3. Which data types can be produced?

 Name: Tank_Level
 Type: Produced
 Connection: 4 Consumers
 Data Type: DINT
 Set tag to allow Unicast Consumer Connections
5. Verify the project and correct any errors.
6. Save the project.
7. Download the project to the controller in slot 1.
8. Place the controller in the Remote Run mode.

9. Minimize RSLogix 5000 software.
10. Open a second instance of RSLogix 5000 software.
11. Open the PC3_1756r_A2.acd file.
12. To configure the consumed tag, perform the following actions:
A. Create a path by adding the producing controller in slot 1 to

the I/O configuration of the project (name the controller
Producing_Controller.)
B. Create a tag named Slot1_Tank_Level with the following
properties:
-- Select the appropriate data type to consume the data from the
Tank_Level tag in the slot 1 controller.
-- Configure the Slot1_Tank_Level tag to consume the data
from the Tank_Level tag in the slot 1 controller.
-- The consumed tag data must be received by the controller in
slot 3 every 2 ms.
PC3e56r
15. Verify that the data from the controller in slot 1 is being
consumed by the controller in slot 3 by performing the following:
 Open the Controller Tags editor for the project in slot 1 and
enter a value of 300 for the Tank_Level tag.
 Confirm that 300 is now the value of the Slot1_Tank_Level
tag in the slot 3 project.
16. Go offline and close both projects.
Exercise B In this exercise, you will practice configuring Logix5000 controllers

to produce and consume data from a user-define data type across the
backplane.
Context:
To exchange interlocking data between the controllers, you must

configure the controllers to produce and consume UDT data across
the backplane.

Directions:
1. Open the PC3_1756r_B1.acd file.

2. Configure the Controller_Status tag to be produced for 2
consumers.

6. Place the controller in Remote Run mode.
7. Minimize RSLogix 5000 software.

8. Open a second instance of RSLogix 5000 software.
9. Open the PC3_1756r_B2.acd file
PC3e56r
10. To configure the consumed tag, perform the following actions:

 Create a path by adding the producing controller in slot 1 to
the I/O configuration of the project.
 Copy the UDT from the producing controller and paste it into
the consuming controller.
 Create a new tag named Slot1_Controller_Status that will
consume the data from the Controller_Status tag in the slot 1
controller.
Tip " Controller_Status is a tag that uses a user-defined data type. To be

shared correctly, the UDT in the consuming controller must be set up
in the same order as the UDT in the producing controller.
13. Monitor the consumed tag.
14. Verify that the data from the controller in slot 1 is being
consumed by the controller in slot 3.
PC3e56r
PC3e56r
Answers Exercise A
2. Tags must be controller-scoped to be produced or consumed.

3. Data types that can be produced would include REAL, DINT,
and user-defined data types.
4. The following configurations are required for the Tank_Level
tag:
12.
A. The following is an example of how the I/O Configuration
should look in the slot 3 controller:
PC3e56r
B. The following configurations are required for the

Slot1_Tank_Level tag in the slot 3 controller project:
Data Type in the Consumed

tag must match Data Type in
the Produced tag.
The tag name here must match

the
in name of the produced
the Producing tag
Controller.
PC3e56r
Exercise B
2. The following configurations are required for the

Controller_Status tag:
10. You should first copy the Status UDT from the producing
controller’s project into the consuming controller’s project:
PC3e56r
The following configurations are required for the

Slot1_Controller_Status tag in the slot 3 controller project:
Data Type in the Consumed

tag must match Data Type in
the Produced tag.
The tag name here must match

the name of the produced tag
in the Producing Controller.
PC3e56r
PC3e56r
Lesson 9
Configuring Logix5000 Controllers
to Share Data over an EtherNet/IP
Network
Important: If this lesson is part of a  Add an EtherNet/IP module to an I/O configuration
national school and you are using
ControlNet for remote data sharing, this  Add a controller to an I/O configuration
lesson can be skipped.
Use the procedures in this lesson when you have to pass interlock
data between controllers over an EtherNet/IP network.
Before You Begin EtherNet/IP Network Overview
Ethernet Network: A high speed, information network designed

primarily for communications between computers and peripheral
devices:
 Is widely accepted and has become the “defacto” standard for
information networks
 Can be used with a wide range of devices available from many
different vendors
 Was widely used in office networks for decades and now is used
on the plant floor as well
 Allows data to be easily exchanged between the plant floor and
office networks
? Who owns or controls EtherNet/IP? EtherNet/IP (Industrial Protocol) Network : An Ethernet network
Answer: Technically, no one owns it;
that uses CIP (Common Industrial Protocol) at the application layer
however, EtherNet/IP is a trademark of of the OSI model, enabling interconnectivity with other networks
ControlNet International under license that use CIP at the application layer.
by ODVA (Open DeviceNet Vendor
Association).
CIP (Common Industrial Protocol): The application layer of the
OSI (open system interconnection) model that enables I/O control
over an EtherNet/IP network. This layer also bridges EtherNet/IP
devices with devices on networks such as ControlNet and DeviceNet
that also use CIP at the application layer.
ENTsb56r
9--2 Configuring Logix5000 Controllers to Share Data over an EtherNet/IP Network
Overview of IP Addresses
IP (Internet Protocol) Address: A user-defined software address

Let the students know that their will be a assigned to a device on an Ethernet network that identifies the
brief discussion on private IP addresses network and the node. An IP address is a 32-bit address that is
normally grouped into 4 bytes for ease of communication and
understanding (e.g., 10.88.244.130).
Tell the students that every Rockwell MAC (Media Access Control) Address: A static address that is
Automation/Allen-Bradley factory-assigned to an Ethernet and/or EtherNet/IP device. This
Ethernet/EtherNet/IP product has a MAC
address in the form address is a unique 6-byte address -- each digit is a hex number -- that
00:00:BC:XX:XX:XX. is embedded in the circuitry of every device that is on an EtherNet/IP
Inform the students that a device’s MAC network:
address is also referred to as the
device’s Hardware Address or Ethernet
Address.
How many possible Ethernet

MAC Address (also referred to
?
devices/components can Rockwell
Automation manufacture? as a module’s Ethernet address)
Answer: 166 (=16,777,216).
IP addresses are easy-to-use and remember notations for the user to
employ in communication networks:
 Devices use their hardware addresses to communicate with each
other.
 Each device converts its hardware address to an IP address before
it transmits a message on the network.
 As devices communicate with each other, they store information
in their memory that identifies a hardware device with its IP
address.
Ethernet networks support many different types of protocols,
including TCP/IP:
 TCP/IP is not limited to an EtherNet/IP network.
 EtherNet/IP addresses are used to communicate between devices
on different protocols.
 The different protocols that devices use to communicate on are
transparent to the user at the network layer of the OSI model.
ENTsb56r
Configuring Logix5000 Controllers to Share Data over an EtherNet/IP Network 9--3
Inform students that they should obtain a Private IP Addresses

list of available private IP addresses
from their IT department before There are a finite number of IP addresses that have been designated
randomly using one. The ability to reuse as private IP addresses. The private IP addresses prohibit message
an IP number extends between different
enterprises but not necessarily within a traffic from being routed to the Internet thereby avoiding conflicts
subnet. that would otherwise arise whenever two or more enterprises used
the same IP address:
Class Private IP Addresses

A 10.0.0.0 -- 10.255.255.255
B 172.16.0.0 -- 172.31.255.255
C 192.168.0.0 -- 192.168.255.255
The advantages of using private IP addresses include:

 Readily available for anyone to use at anytime (i.e., you do not
need to register these addresses or obtain approval from an
Internet registry prior to implementing them)
 Simultaneous usage by multiple companies thereby allowing
users to create their own private network
 Easily expandable number of networks and end devices a user can
employ (thereby addressing the concern of having an insufficient
number of IP addresses)
Inform the students that they will be Subnets and Subnet Masks
shown how to identify if two devices are
on the same network later in this lesson. Subnet Mask: An address that enables distinction between networks
This section may confuse your students. by “masking” IP address bits that denote the same network and
Network administrators are often
stymied by this topic. “exposing” bits that denote different networks:
 Networks are often divided up into smaller units called subnets.
If pressed for additional information,
refer them to the Internet. Entering the  Network administrators create subnets as a management tool:
terms subnet or subnet mask into their
favorite search engine will reward them -- Routes packets to the appropriate subnetwork based on IP
with a plethora of information. The addresses
search results will provide them
background information, subnet -- Easier to monitor the health of the entire network
calculators, and web and classroom -- Minimizes effort required to troubleshoot and isolate problems
learning opportunities.
-- Capable of isolating users based on:
-- Geography
-- Departments
---- Media protocols needs (e.g., plant floor I/O vs office

Communication
email).
 Plant environment communications benefit when plant floor
communications operate on a separate subnet from the office
communications:
-- Accommodates timeliness of operations
-- Enhances system maintenance and upgrade options
-- Adds levels of security.
ENTsb56r
? How would using subnets on a plant Subnet masks allow for two devices to determine whether or not they
floor assist your company’s operations? exist on the same subnet:
Answer: Subnets would make it  If two devices are on the same subnet, they are able to
possible to isolate different plant floor communicate directly with one another.
operations (e.g., welding, milling) from
each other and from the  If two devices are on different subnets, the data must first be sent
office/administrative systems. This to a router before the targeted device receives the data sent by the
allows one operation to be shut down
without directly impacting the whole source device.
plant. Subnets will reduce the risk of
security threats (e.g., Trojan horse
attacks). How a Subnet Mask Operates
A subnet mask, like an IP address, is a 32-bit address that is
? How many of you have ever normally grouped into 4 bytes for ease of communication and
programmed an MVM instruction? How understanding:
does it work?
Inform the students that a subnet mask Typical Subnet Mask
operates in a manner similar to an MVM
instruction; hopefully they will be able to 255.255.XXX.XXX
translate some of that familiarity when
identifying if two IP addresses are on the
same subnet.
Binary Equivalent: 1 1 1 1 1 1 1 1 . 1 1 1 1 1 1 1 1 . x x x x x x x x . x x x x x x x x
Consecutive “1’s” Represent Network Portion of IP Address
A subnet mask uses the “1’s” to do a bit-by-bit comparison of two IP

addresses to see if the devices associated with the IP address are on
the same subnet:
 As long as the IP address bits match each other (independent of
the subnet mask value) whenever there is a corresponding “1” in
the subnet mask, the devices are on the same subnet.
 If the network portions:
-- Match up, the devices communicate directly with each other.
-- Don’t match up, they are on separate networks and then
communicate through a router (commonly referred to as a
gateway).
Example
Compare the EtherNet/IP addresses of two devices and determine
if they are on the same subnet:
EtherNet/IP Address: 165.88.73.129
Subnet Mask: 255.255.240.0
ENTsb56r
Converting these decimal values to their binary equivalent yields:
EtherNet/IP Address: 1 0 1 0 0 1 0 1 . 0 1 0 1 1 0 0 0 . 0 1 0 0 1 0 0 1 . 1 0 0 0 0 0 0 1
Subnet Mask: 1 11 11 11 1. 11 11 11 11 .1 11 10 00 0. 00 00 00 00
Corresponding bits match

each other; therefore,
these two devices are on
the same subnet.
Compare the same two EtherNet/IP addresses of two devices

using a different subnet mask and determine if they are on the
same subnet:

Subnet Mask: 255.255.255.0
Converting these decimal values to their binary equivalent yields:
Subnet Mask: 1 11 11 11 1. 11 11 11 11 .1 11 11 11 1. 00 00 00 00
Corresponding bits do not match each other; therefore,

these two devices are not on the same subnet.
? What are some reasons you may As demonstrated by these examples, it is possible to expand (or
want to expand your network? Contract contract) the network environment by changing the subnet masks
it? associated with the devices on a network.
Answer: Isolate devices, processes,
and enhance security. Limiting the
number of subnets you have increases Gateways
the likelihood that two devices can Gateways: Nodes on a network that act as entrance and exit portals
communicate
This may reducedirectly with each
the number other.
of routers between external networks:
you must purchase, maintain, and  Data packets being shared between internal and external devices
monitor.
Gateways are glorified routers that must pass-through at least one gateway in establishing
control the flow of data between external communications.
networks and an enterprise’s internal
network.  Gateways often act as a firewall and protect the resources of a
private network from users from other networks.
 Gateways may have more than one IP address associated with
them -- one for internal users and one for external users.
ENTsb56r
Default Gateway: The router (gateway) to which all remote packets

must be sent in order to be routed to their final destination (i.e., if
two devices are not on the same network, the packet will be sent to
the gateway).
Gateway Address: The IP address of a device’s default gateway.
Configuration Overview and Software Interfaces
Note that this section is a general To share data across an EtherNet/IP network, it is necessary to
introduction to the flow of configuration complete the following procedures:
procedures. The step-by-step details
and software demonstrations will be 1. Create the required produced tag.
presented in the Here’s How section. If
this lesson is part of a national school, 2. In the controller that is consuming the data, perform the following
add that remote I/O will be discussed in actions:
a different lesson.
Encourage students to ask any A. Add the local EtherNet/IP module to the I/O configuration.
remaining questions from the
Configuring a Logix5000 Controller to B. Add the remote EtherNet/IP module to the I/O configuration.
Produce and Consume Data lesson.
C. Add the producing controller to the I/O configuration.
D. Create the required consumed tags.
Note that the controller was also added Adding an EtherNet/IP Module and Controller to an I/O
to the project to share data when Configuration
producing and consuming tags across
the backplane. However, the controller is The following graphic is an example of a remote EtherNet/IP module
now added under the remote ENBT.
and remote controller added to an I/O configuration in
RSLogix 5000 software:
Add that to
possible it isadd
notthe
necessary
controllerorrunning
even the
project to the configuration.
Local EtherNet/IP Module
Remote EtherNet/IP Module

Remote (Producing) Controller

Note that the produced and consumed Data that is shared over an EtherNet/IP network must be transferred
tags are created just as they were using produced tags and received (stored) in consumed tags.
created for transfers over the backplane.
ENTsb56r

 Add an EtherNet/IP module to an I/O configuration
Use thethe
demonstration:
Be sure to use the
CCP143_1756R_DEM6.acd file and - Parent--child relationship of the EtherNet/IP and the
CCP143_1756R_DEM7.acd file. When
demonstrating the listed procedures, be controller that you add to the I/O configuration
sure to point out the following items:
- Produced and consumed tags that you create
ENTsb56r
ENTsb56r
Exercise: Configuring Logix5000 Controllers to Share Data over an EtherNet/IP Network 9--9
Exercise: Configuring Logix5000

Controllers to Share Data over an
EtherNet/IP Network
Exercise A In this exercise, you will practice configuring a local Logix5000

controller to share data with a remote Logix5000 controller over an
EtherNet/IP network.
Context:
You have finished programming and testing a complete project for a

production line. To increase productivity, the plant has set up a
second production line. The second production line needs to receive
(consume) the Pressure data from the first assembly line over an
Production Line 1 Production Line 2
EtherNet/IP Network
Produced Consumed
In this exercise, you will share data with the other workstation on
your EtherNet/IP network. One controller will produce data and the
other will consume the data.

Directions:
1. Open the ENT_1756r_A1.acd file (the producer controller.)
2. Create a user-defined data type called Station_Data that will

store the following information from the local controller:
Member Data type Description

AI0 REAL Analog Input channel 0
DI DINT Digital Inputs
ENTe56r
9--10 Exercise: Configuring Logix5000 Controllers to Share Data over an EtherNet/IP Network
3. Create a controller scoped tag called Local_Station_Data with

the following properties:
 Uses the Station_Data data type
 Produced for 1 controller
4. Enter ladder logic to copy your analog channel 0 data and channel
1 data as well as your discrete input data to the respective
members of the Local_Station_Data tag.
5. Verify the project, correct any errors, and download the project to
the local controller in slot 1.
6. Place the controller in slot 1 in Remote Run mode.
7. Open the ENT_1756r_A2.acd file (the consumer controller.)
Tip " This project will be downloaded to the controller in slot 3 of the
remote workstation after you have completed the configuration.
8. Add the following modules to the I/O configuration (review

workstation configuration for appropriate IP addresses):
A. Add the local (relative to the project’s controller)
EtherNet/IP module to the I/O configuration.
B. Nested under the local EtherNet/IP module, add the remote
EtherNet/IP module to the I/O configuration.
C. Nested under the remote EtherNet/IP module, add the
controller in slot 1 of the remote workstation to the I/O
configuration and call it Producer_Controller.
9. Copy the Station_Data UDT from the ENT_1756r_A1 project

file into the ENT_1756r_A2 project file.
10. Consume the Local_Station_Data tag from the
Producer_Controller by performing the following actions:
 Create a controller scoped tag called Remote_Station_Data
that uses the Station_Data data type.
 Configure Remote_Station_Data as a consumed tag with a
rate of 100 ms.
11. Enter ladder logic to copy the Remote_Station_Data tag to your
analog channel 0 and analog channel 1 outputs.
12. Write the logic so that each of the green buttons pushed on your
workstation will light the corresponding light on the remote
workstation.
the remote consumer controller in slot 3.
ENTe56r
14. To verify that each production line is correctly configured to

share data, complete the following actions:
A. Verify that moving your analog channel 0 to the middle
position moves the analog channel 0 meter on the remote
workstation to its middle position.
B. Verify that moving your analog channel 1 to the middle
C. Verify that pushing the first four discrete buttons on your
workstation light the corresponding lights on the remote
workstation.
ENTe56r
Answers Exercise A
2. The user-defined data type should look similar to the following

example:
3. The tag created should look similar to the following example:
ENTe56r
4. Your ladder logic should look similar to the following example:
8. The I/O configuration should look similar to the following

example:
9. The Station_Data UDT should now be found in the

EN2_1756r_A2 project:
ENTe56r
10. The consumed tag should look similar to the following

example:
ENTe56r
ENTe56r
ENTe56r
Lesson 10
Communicating with a 1756-I/O
Module over an EtherNet/IP
Network
What You Will Learn After completing this lesson, you should be able to add a remote
1756-I/O module to an I/O configuration for communication over an
Just like with local modules, you can add remote I/O modules at any
point in your development process.
Have students find their Reference: RSLogix 5000 and Logix5000 Procedures Guide
procedures guide and use it for
the steps below. Give them a few 1. Find the Adding a Local or Remote 1756--I/O Module to an I/O
minutes to read the procedures
guide. Configuration procedure in your procedures guide.
Point out that in this lesson you’ll 2. Briefly read the Get Ready steps.
manually add remote modules.
Before You Begin Effect of RPI on EtherNet/IP Communication
Have students find the manual Reference: Logix5000 Controllers Design Considerations,

and use it for the steps below. 1756--RM094
Giveguidelines.
the them a few minutes to read
1. Go to the Communication with I/O chapter.
2. Go to the Guidelines to Specify an RPI Rate for I/O Modules

section.
3. Notice the guideline on how RPI affects change--of--state
communication over an EtherNet/IP network.
Point out that this also applies to the Example: Effect of RPI on EtherNet/IP Communication
RTS of an analog module.
If a digital input module uses an RPI = 100 ms, the
EtherNet/IP module sends module data immediately on receiving it
if another data packet was not sent within the last 25 ms.
RI2sb56r
10--2 Communicating with a 1756-I/O Module over an EtherNet/IP Network
Communications Formats

read the benefits and 1756--RM094
considerations of each, and then
ask the questions.
1. Go to the Communication Formats for I/O Modules section.
2. Briefly read the benefits and considerations of direct and
rack--optimized connections.
Question: Which type of connection uses more network resources?
Question: What is the advantage of a rack--optimized connection?
Point out that you can still have Question: Which type of connection do you need to use if you want
direct connections with modules diagnostic data from a module?
even if the chassis has a
rack--optimized connection.
Here’s How To decide which rack connection setting to use.

read the guidelines. 1756--RM094
1. Go to the Guidelines to Manage I/O Connections section.
2. Briefly look over the I/O Connection Guidelines.
Example: No Rack Connection

Suppose you have a remote 17--slot chassis with these modules:
 1 EtherNet/IP module
 15 analog input or output modules

 1 digital input module
In this case, set the remote EtherNet/IP module’s Rack Connection
setting to None. Choose a direct connection format when you
configure each I/O module.
RI2sb56r
Communicating with a 1756-I/O Module over an EtherNet/IP Network 10--3
Example: Rack--optimized Connection

Suppose you have a remote 10--slot chassis with these modules:
 1 analog input module
 1 fused output module
 5 non--diagnostic digital input modules
 2 non--fused digital output modules
In this case, set the remote EtherNet/IP module’s Rack Connection
setting to Rack Optimization. Choose a direct connection format for
each analog and fused output module. Choose a rack--optimized
format for the rest of the modules.
Have each student do this on Activity: For each situation below, decide which rack connection
their own. Then go over the setting to use and check the appropriate box:
answers as a group.
Rack Connection setting

Situation Rack
None
Optimization
None A. Remote 10--slot chassis with:
 2 analog input modules
 6 diagnostic digital input modules
 2 non--fused diagnostic output modules
Rack Optimization B. Remote 13--slot chassis with:
 2 analog input modules
Rack Optimization C. Remote 13--slot chassis with:
 2 EtherNet/IP modules
 2 empty slots for future expansion
RI2sb56r
10--4 Communicating with a 1756-I/O Module over an EtherNet/IP Network
Here’s How To manually add a remote 1756-I/O module to an I/O configuration

for communication over an EtherNet/IP network.
IMPORTANT: To meet IACET Reference: RSLogix 5000 and Logix5000 Procedures Guide

prepare certificate students for
the final exam, you must Talk
he or your instructor through
she demonstrates them.the steps in your procedures guide while
demonstrate all lesson objectives
using the proper job aids.
To demonstrate:
1. Continue with either the
CCP143_1756R_DEM6.acd file or
CCP143_1756R_DEM7.acd project.
adding a remote module using a
direct connection.
adding a remote module using a
rack optimization connection. Pay attention to these critical aspects of the demonstration:
- Tag names of the data for the remote module
- Rack Connection setting of the remote EtherNet/IP

module if you want a rack--optimized connection
- You must be offline to change the Rack Connection

setting of the remote EtherNet/IP module.
- The software automatically creates alias tags for the

packet of rack optimization data.
RI2sb56r
Exercise: Communicating with a 1756-I/O Module over an EtherNet/IP Network 10--5

1756-I/O Module over an
EtherNet/IP Network
Exercise A In this exercise, you will practice configuring a Logix5000 controller

to communicate with a 1756-remote I/O module over an EtherNet/IP
network.
Context:
You have programmed a complete project. As a safety feature for

plant personnel, you want to program an output light to be on when
the production line is active. Because you have used your available
I/O points in the local chassis, you must add a remote chassis to
accommodate the additional I/O requirements. You are now ready to
configure the controller to communicate with the 1756-remote I/O
module over an Ethernet I/P network.
The setup of the remote output is shown in the following graphic:
Production
Line Active
Local Remote
Chassis Ethernet I/P Network Chassis

Directions:
1. Download the Blank.acd file to the controller in slot 3.
2. Open the RI2_1756r_A1.acd file.
3. Add the local and remote EtherNet/IP modules to the project I/O
configuration (review your workstation configuration for the
appropriate IP address.)
4. Add and configure the remote output module in slot 4.
5. Add the local input module that is in slot 2 to your I/O
configuration. You will also be owning this module.
RI2e56r
10--6 Exercise: Communicating with a 1756-I/O Module over an EtherNet/IP Network
6. Make a new tag, DI12, an alias tag for bit 12 of the local digital
input card in slot 2.
7. Make a new tag, DO11, an alias tag for bit 11 of the the remote
digital output card in slot 4
8. Enter the following ladder logic in your MainRoutine:
9. Download the project to the controller in slot 1 of the

local chassis.
10. Test the project and verify that you have correctly configured the
remote I/O by performing the following actions:
A. Start the conveyor by energizing workstation label DI12.
B. Verify that the remote I/O light DO11 on the other

workstation is on.
C. Turn off DI12 and verify that the remote I/O light on the
other workstation is off.
D. When the project functions correctly, go offline.
RI2e56r
RI2e56r
Answers Exercise A
3. Your main configuration screen for the local EtherNet/IP

module in slot 6 should look similar to the example (The
module’s IP address will vary depending on your workstation
setup.):
The remote EtherNet/IP module is added to the I/O

Configuration by right-clicking the Ethernet network icon
displayed below the local EtherNet/IP module:
(Continued)
RI2e56r
Your main configuration screen for the remote EtherNet/IP

module’s IP address will vary depending on your workstation
setup.):
4. Add the remote output module by right-clicking the backplane

displayed beneath the remote EtherNet/IP module:
Your main configuration screen for the remote output module in

slot 4 should look similar to the example:
RI2e56r
5. Your main configuration screen for the local input module in

Your completed I/O Configuration within the Controller

Organizer should look similar to the following:
RI2e56r
Lesson 11
Creating an Event Task in an
What You Will Learn After completing this lesson, you should be able to create an event
task in an RSLogix 5000 project.
Use an event task when you have logic you want to execute
whenever a specific condition occurs.
Before You Begin Task Type Review

If students are familiar with other
controllers, relate the event task to a PII Task Type Usage Icon
(PLC) or DII (SLC) task.
A task that runs continuously but can be interrupted by
Continuous
periodic or event tasks.

Periodic
When called, it will interrupt any lower priority tasks.
A task that is triggered only when a specific event
Event occurs. When called, it will interrupt any lower priority
tasks.
EVTsb56r
11--2 Creating an Event Task in an RSLogix 5000 Project
Event Task
An event task is a task that performs a certain function only when
Note that the fastest or shortest task will triggered by a specified event:
 Each task is assigned a trigger.
In the graphic, point out that an event  Each task is assigned a priority level. When triggered, the event
task icon has a forward arrow because task interrupts any lower priority tasks (other event, continuous,
the task executes once based on a
certain conditional event. or periodic tasks).
 Once initiated, all programs assigned to the event task are
Also, note that like a continuous task or
periodic task, an event task contains executed or scanned once from top to bottom.
programs, tags, and routines.  Upon completion, control returns to the task that was interrupted,
at the point in which it was interrupted.
Benefits
Event tasks offer the following benefits:
 Improve performance and reduce costs because tasks execute
only when needed
Note that event tasks can provide an
alternate, more effective way of  Reduce the amount of code a controller must scan on a regular
balancing the need for high-speed basis
processing with CPU performance.
 Free up CPU resources for other operations
 Provide faster throughput and improved loop-closure times,
which translate to higher production output
Tip " Like a continuous or periodic task, event tasks require at least one
program and one routine.
Event Task Use

Event tasks are selected for processes that should only run when
needed, typically on an infrequent basis.
 Perform an operation when a part is rejected
 Execute a process when a certain count or time is achieved
EVTsb56r
Creating an Event Task in an RSLogix 5000 Project 11--3

Note that this project takes advantage of In this example, the event task is triggered only when the packing
some of the Logix5000 organizational tape is low:
elements.
Event Task
Event Task Properties
The properties for each event task determine when the task is
In the graphic, point out that the trigger executed:
option is where the user chooses how
the event task will be enabled. Tell
students that this means event tasks will
only execute if the required trigger has
occurred.
Enables the Task
Specific Data for Triggers

such as Consumed Tag
Data Arrival or 1756 Module
Input State Change
Timeout Value
All other properties are the same

as those for periodic tasks.
EVTsb56r
Trigger
The following triggers can initiate an event task:
To triggers an event task when . . . Select this trigger type . . .
Note
eventthat
taskthe Motion
permits Group Execution
a specialized A consumed
count tag changed value or its sequence
just changed Consumed Data State Change
algorithm to be synchronized with the COS input data on an input module has changed or
motion group processing. Since the Module Input Data State Change
planner is always a higher priority than its sequence count changed
the event task, this event always occurs EVENT instruction only
when the planner is complete. This An event instruction goes true " This code specifies the task to
allows you to use specialized control trigger. It is programmed outside
algorithms to override the normal motion of the event task.
loop processing.
The motion planner executed Motion Group Execution
The high speed registration input 1 on the motion
card or drive has fired trapping the current axis Axis Registration 1
position
Note that a physical device determines The high speed registration input 2 on the motion
the location and triggers Axis card or drive has fired trapping the current axis Axis Registration 2
Registration tasks on the off-to-on position
transition of these inputs.
The axis has crossed the assigned watch position.
A watch point is a software-based position that Axis Watch
serves as the trigger for the event
The triggers that are supported depend on the

controller type.
Multiple controllers can simultaneously Consumed Tag

consume the same produced tag. Because a controller produces and consumes data asynchronous to
the execution of its control program, the program may begin
processing with a mixture of old and new data.
This technique lets you use smaller, Event tasks provide a way to synchronize data exchange to ensure
more modular controllers in flexible that a consuming controller receives all of the data before processing
manufacturing cells. You can reconfigure
the cells while avoiding the begins:
interlock-wiring issues that would  After the producing controller loads the data into its produced tag,
otherwise exist.
the controller initiates an IOT (immediate output) instruction.
 The consuming controller simply configures an event task to look
for the trigger via the consumed tag.
EVTsb56r
This technique provides the following advantages:

 Automates the data detection processing for the consumer
 Eliminates complex handshaking code
 Improves the transfer rate

Coordinates the operations of multiple controllers in a distributed
system
 Initiates code in the distributed controllers (consumers) based on
? For digital modules, what is the an event in a master controller (producer):
difference between RPI and COS? -- Eliminates data change detection overhead
The RPI sends data at a pre-configured -- Simplifies programming
rate. COS sends data from a
digital input when the module
has detected that changes Module Input Data State Change
have occurred (off-to-on, on-to-off, or
both). When any point configured for Certain 1756 input modules support module input state change.
COS changes state, the module
multicasts its data for all points.
Tip " Refer to your module documentation for details.
?For analog modules, what is the Upon receipt of the information from a module, the controller
difference between RPI and RTS?
initiates the event task and executes the application code:
RTS (Real Time Sample Rate)
specifies when an analog  Saves valuable execution time by avoiding the need for the
module scans its channels and controller to poll the inputs and perform COS (change-of-state)
multicasts data. detection
Example: Module input data state  Captures and processes multiple events without additional CPU
change is valuable for applications such
as packaging and material handling, overhead
where detection of a package by an
input sensor must be processed quickly 1756 Local and Remote Options
to drive an output solenoid to manipulate
or divert product.
Remote input modules can be used to trigger an event:
 Input modules used to initiate an event task are generally in the
Poll the class to find out who is using same chassis as the controller that needs to respond to the event.
remote I/O in their application.
 Input modules can be placed in a remote chassis connected via a
ControlNet or EtherNet/IP network. The associated
communications module connecting the remote I/O must support
input events.
Point out that for many applications, the Each network adds additional delays.
benefit of reducing the CPU loading
overrides the need for speed.
Quick-Response Events
Example: A packaging line requires a Quick-Response Event: The delay between the input change and
label each time a product is detected. the control of an output must be minimized:
Because of the speed with which
product moves by the labeler, an event  Controls an output based on receipt of an input
task is the only way to guarantee that
every load is detected and labeled.  Isolates code to ensure that execution is not impacted by long
continuous task scan times
 Works for applications such as material handling, packaging,
gluing
EVTsb56r
Short-Duration Input Events

With a short-duration event, the input Short-Duration Input Event: An input whose duration is shorter
could change state once and then than the normal scan of the controller but the event does not occur
change back again faster than the
normal scan of the continuous or very often.
periodic task.
For short-duration input events, an event task performs the
following:
Example: In a bottling line, a sensor  Executes an operation based on a short-duration (pulsed) input
detects an improperly capped bottle that
must be rejected. Because of the high  Ensures capture of inputs that turn on and off faster than the
speed of the line, an event task is the continuous task scan time
only way to detect the reject and
respond to it.  Works for applications such as encoder inputs, position sensing,
proximity devices
Synchronized-Execution Event
Example: Synchronized-execution Synchronized-Execution Event: Typically used with analog data,
event tasks work
as packaging, for applications
process such
loops, drive where the arrival of new data triggers an operation:
control loops  Each analog module has its own internal sample period for
converting analog input signals to digital floating values.

 An asynchronous loop can exist between the receipt of new input
values and the execution of the code for the loop.
This discrepancy means that PID calculations

execute with stale data, which could result in
calculation errors.
With an event task, you can synchronize the PID calculation to the
arrival of flow transmitter data to avoid this potential error.
Throughput depends on module type, input

voltage, module temperature, filter and response
time settings, backplane size and loading, and
controller type.
Single Bit Triggers

A task can be triggered on a single bit change even when the task
configuration level is for the entire input module:
1. Access the Change of State options for the input module.
2. Select only the bit transition you want to trigger the event. By
default all transitions are enabled.
3. If there is more than one transition you want to monitor, use code
in the event task to find out what changed.
EVTsb56r
Change of State options are found on the Configuration tab of the

Module Properties dialog box:
Sends Data
When the
Input
Changes
from Off to
On and On
to Off
Module Input Data State Change -- Design Considerations

The following checklist will help you efficiently use input triggers:
- Limit the number of other modules that are in the same chassis
as the event module and controller. Additional modules
increase the potential for backplane delays.
- For digital inputs, restrict the triggering input to a single point
on the module. Disable COS for the other points. When you
enable COS, all inputs on the module trigger a single event,
increasing the chance of a task overlap.
At the time of printing, the modules with - In general, set the priority of your event task as the highest
the best response times are priority.
1756-IB32/B digital module and
1756-IF4FXOF2F analog module. - Increasing the number of event tasks increases the load on the
CPU, increasing the chance of a task overlap.
- Choose modules with the best current response times.
Automatic Output Processing
Review the wording of this option. To reduce task overhead, verify the disable automatic output
Selecting it will actually disable (not processing . . . option is selected and use an IOT instruction in a
enable) automatic output processing.
routine.
EVTsb56r
If you already covered this topic in the Priority

Periodic Task lesson, briefly review it
here. Each periodic and event task in a controller has a priority level that
determines which task executes when multiple tasks are triggered:
 Priorities are assigned by the user.

Clarify that the lower number (1) gives

There
and 15are 15 levels
being of priority, with 1 being the highest priority
the lowest:
the task a higher priority or importance.
-- A task with a higher priority will execute first (i.e., 1 before 3)
Note that the fastest or shortest task will  Task priorities are relative:
-- If there are only three tasks, priorities of 6, 7, and 8 will
Clarify that this means the continuous function the same as priorities of 1, 2, and 3.
task automatically has the lowest priority.
A user cannot configure the priority for a  Although no priority level is assigned, the motion task is always
continuous task. the highest priority.
 Although no priority level is assigned, the continuous task is
always one priority level lower than all other tasks:
Highest Priority Motion Task

Point out that periodic and event tasks Trend
use the same priority scale/levels.
Therefore, whichever task has the Event or Periodic Task - Priority 1 . . .
highest priority executes first, regardless
of the task type. Event or Periodic Task - Priority 5 . . .
Lowest Priority Continuous Task
EVTsb56r
If you already covered this topic in the Scan Time Values

Periodic Task lesson, briefly review it
here. When executing, the software displays the maximum scan time and
the last scan time in milliseconds for the selected task in the Task
properties dialog box:
Online Properties
Length of Execution
Event Task Timeout
Setting this option will trigger a task within a specified period of
time if the required event does not occur:
 This timer is reset and started when the task is completed.
 This is not the same as a periodic task.
These instructions are explained on the Event Instructions

following pages. For more detailed
information on how these instructions The following instructions impact event tasks:
impact event tasks, see the online Help.  IOT (Immediate Output)
 UID/UIE (User Interrupt Disable/Enable)
 CPS (Copy Synchronize)
EVTsb56r
IOT Instruction
An IOT instruction causes a value to be sent immediately, thus
improving response latency:
 Can operate on a produced tag or an output module tag

Causes value to be sent, thus improving response latency
 Avoids having to wait for another RPI to initiate an output update
 On a produced tag, permits you to trigger a task in the consuming
controller:
Triggers the Task in the

Consumer
UID/UIE Instructions
These instructions work together to prevent a small number of
critical rungs from being interrupted by other tasks:
 UID instruction prevents higher-priority tasks from interrupting
the current task but does not disable execution of a fault routine
or the Controller Fault Handler.
 UIE instruction enables other tasks to interrupt the current task:
EVTsb56r
CPS Instruction
The CPS instruction copies the value(s) in the Source to the values in
This instruction is considered part of the the Destination:
File/Misc. group of instructions. It can be
found on the File tab of the Language  Performs double buffering of values and manages interrupts/event
Elements toolbar. tasks:
-- Operation cannot be interrupted by another task.
 Reduces the need for application handshaking
 Avoids mixture of old/new data
EVTsb56r
Here’s How To create an event task.

- Location of the procedure in the job aid
- Trigger for the event task
- Timeout option
- Automatic output processing option
EVTsb56r
Exercise: Creating an Event Task in an RSLogix 5000 Project 11--13
Exercise: Creating an Event Task in

an RSLogix 5000 Project
Exercise A In this exercise, you will practice the basic steps for creating an
event task.

Directions:
1. Open the EVT_1756r_A1.acd project.
2. Create a new Event task with the following properties:



Name: Alarms
Trigger: EVENT Instruction Only
 Priority: 5
 Watchdog: 100 ms
3. Add the unscheduled Alarm_Control program to your new
Event task’s program schedule.
4. Open the MainRoutine within the MainProgram of the
Continuous task.
5. Create a rung of ladder that will momentarily trigger execution of
the Alarms Event task when DI12 (Local:2:I.Data.12,
program-scoped tag) is enabled.
6. Save your project.
7. Verify you correctly configured your Event task by performing

the following:
A. Download the project to the controller in slot 1.
B. Change the controller operating mode to Remote Run.
C. Toggle selector switch DI12 and confirm the output lights on

your workstation begin to flash.
8. Close your project.
EVTe56r
11--14 Exercise: Creating an Event Task in an RSLogix 5000 Project
Exercise B In this exercise, you will practice creating an event task.
Context:
The width of the roll of tape used in the palletizing station is

measured by an optical sensor. Two alarms must be generated for the
operator when the tape is below a certain width. On the standard
workstation, these inputs and outputs appear as shown:
Active Only When Tape is Low
When on (right), DI15 indicates that

the tape is low.
DI12 DI13 DI14 DI15

Directions:
1. Open the EVT_1756r_B1.acd project.
2. Download this project to the controller in slot 1.
3. Change the controller operating mode to Remote Run.

4. Minimize the project.
Tip " The assembly stations are now running.
5. Open the EVT_1756r_B2.acd project.

6. Configure the local input module to enable change of state (COS)
for bit 15 when it transitions from off to on.
7. Create a new event task named Tape_Low that will trigger when
DI15 (Local:2:I.Data.15) is turned on:
 Configure the new task’s trigger to be data state change from

the local input module Local:2:I.
 The existing periodic task has a priority level of 5. Your new
event task is more critical than the Clean_Conveyor task.
Configure the tasks priority to meet this requirement.
EVTe56r
8. In the space below, list your tasks from highest priority to lowest
priority according to the values assigned:
Tip " So far, this is a simple application with only a few short tasks and
little task overhead.
9. In the event task, create a new program named

Low_Tape_Alarms.
10. Create a ladder diagram routine named Alarm_Control within
the program.
11. Assign Alarm_Control as the main routine of the
Low_Tape_Alarms program.
12. Make the controller-scoped tag Alarm_1 an alias for

Local:4:O.Data.10.
13. Make the controller-scoped tag Alarm_2 an alias for
Local:4:O.Data.11.
14. Enter the ladder logic to enable two alarm lights when the task is
active: Alarm_1 and Alarm_2. Put these on an unconditional
rung.
Before performing Step 16., turn the bottom row

of inputs (selector switches) off (to the left).
16. Check the operation of this event task by performing the

following steps:
Tip " Two outputs (DO10 and DO11) should turn on as a visual indication
that the event

scanned occurred
only when the and
tapethe task(DI15
is low was scanned.
= 1). The task should be
A. Download your file to the controller in slot 3.
B. Change the controller operating mode to Remote Run.
C. On the workstation, start your conveyor by pressing the start

button (workstation label DI0).
EVTe56r
D. A low tape measurement has not yet been indicated. Did

outputs DO10 and DO11 turn on?
E. Enable
DI15). any of the other pushbuttons or switches (except
F. Did DO10 and DO11 turn on?
G. To indicate that the width of the tape is now low, set DI15 to
the right.
H. Did DO10 and DO11 turn on?
Exercise C In this exercise, you will practice creating an event task and
configuring an event instruction.
Context:
According to the functional specification, a task is required that will
inform the operator when a high percentage (3%) of the total parts
has been rejected. On the standard workstation, these inputs and
outputs appear as shown:
Reject Alarm (Flashes Only

When Percentage of
Rejected Parts is Greater
than or Equal to 3)

Directions:
1. Open the EVT_1756r_C1.acd project.
EVTe56r
Tip " The assembly stations are now running.
4. Minimize the project.
5. Open the EVT_1756r_C2.acd project.
6. Open MainRoutine of the Station_4_Quality program in the

Quality task. Look over rung 4. This is the rung that evaluates the
percent of rejected parts.
Contains the
percent of
rejects created.
7. Create a new event task named Reject_Percent that is triggered

by an Event instruction. This task is higher priority than the
periodic task.
8. Create a program in the task that will group the data and code
related to the reject alarms. Name the program Reject_Alarms.
9. Create and assign a main routine named Alarm_Control.
10. Enter ladder logic that will enable the alarm light DO6
(Local:4:O:Data.6) when the task is scanned. If you have time,
make the alarm light flash.
11. Turn off DI12, DI13, DI14, and DI15 on the workstation.
12. After the task is set up, enter the code necessary to enable the task
when the Percent_Rejected tag value is greater than or equal to
3. Enter this logic in the Station_4_Quality MainRoutine, rung
5.
14. Set both analog inputs to 0 in order to create poor quality parts.
16. On the workstation, start your conveyor by pressing the start

button (DI0).
17. To introduce a new part into the system, toggle the part sensor
switch (DI12) from left to right and then back to left.
You will see the first assembly station, Press, is active (DO3).
EVTe56r
18. When the station light (DO3) is off, toggle the part sensor switch
from left to right and then back to left.
Now there are two parts moving down the conveyor. You will see
two stations, Press and Stake active (DO3 and DO4).
19. When both station lights are off, toggle the part sensor switch
(DI12) from left to right and then back to left.
Now you will see all three assembly stations Press, Stake, and
Weld, activate.
Tip " When the first part has reached station four it will be evaluated for
quality. A part will be rejected if the pressure values are out of range
(40% to 60% is acceptable).
20. Monitor the ladder logic that you entered to enable the event task.
Tip " This ladder logic should be in the main routine of the
Station_4_Quality program in the Quality task.
Tip " As soon as the Parts_Rejected value is greater than or equal to 3,
the reject light will be enabled/flashing.
21. Continue to toggle selector switch DI12 as the Press, Stake, and
Weld lights go off until the reject light (DO6) is flashing or on.
22. Go offline with the controller and close the project.
EVTe56r
EVTe56r
Answers Exercise A
2. Your task should contain the following information:
3. Your Alarms task program schedule should now look similar to

the following:
5. Your rung of logic should look similar to the following

example:
EVTe56r
Exercise B
6. Your Enable Change of State options should look like the

following example:
Sends Data When the

DI15 Changes from Off to
On.
The input module is

identified.
This task is more important
than the others; therefore, it
has a lower priority number.
The task takes approximately
45 ms to execute, so the
watchdog timer value is set to 100
ms.
EVTe56r
8. The tasks have the following priorities:

 Tape_Low is the most important task. It should have a
priority value of 4 or less.
 The Clean_Conveyors task has a priority value of 5.

The Continuous task automatically has the lowest priority.
9. Your program should contain the following information:
10. Your routine should contain the following information:
15. The logic you created should look similar to the following:
EVTe56r
16.
D. No, outputs DO10 and DO11 did not turn on.
F. No, outputs DO10 and DO11 did not turn on.
H. Yes, outputs DO10 and DO11 did turn on.
Exercise C
With this trigger,

there is no tag
required.
8. Your program should contain the following information:
EVTe56r
9. Your routine should contain the following information:
Tip " Any routine type could be used.
10. The following ladder logic will flash the alarm light when the
task is enabled. To simply turn the alarm light on without
flashing it, program rung 1 only, without the input instruction:
EVTe56r
12. The following code will enable the task when the
Percent_Rejected value is more than (or equal to) 3:
Static Value Program Control

Instruction
EVTe56r
EVTe56r
Lesson 12
Retrieving and Setting Logix5000
Controller Status Values with
GSV/SSV Instructions
 Retrieve and set a controller status value using GSV (Get System
Value) and SSV (Set System Value) instructions
 Assign a fault routine

Poll students to see how many of them
are familiar with PLC-5 or SLC 500 With Logix5000 controllers, you use GSV and SSV instructions to
status files. access controller status values.
Before You Begin Monitoring Controller System Data
Unlike other controllers, a Logix5000 controller does not constantly

Poll students to see how many of them monitor controller system data and update status files.
are familiar with PLC-5 or SLC 500
status files. A Logix5000 controller stores controller system data in structures
Add that by removing the status files, the called objects.
controller can perform more efficiently
because it does not have to update
status files when it is not required. Objects are monitored and changed using specific ladder logic and
structured text instructions:
Point out that these instructions are not  GSV (Get System Value) Instruction: An instruction used to
available in function block diagram or monitor specific controller system data.

sequential function chart languages.
 SSV (Set System Value) Instruction: An instruction used to set
specific controller system data.
Mention that by default, the GSV and Use the GSV/SSV instructions carefully. Changes
SSV instructions are part of the to objects storing controller system data or based on
Input/Output tab on the RSLogix 5000
Instruction toolbar. controller system data can cause unintended
controller operation that may injure personnel and
damage equipment.
GS2sb56r
12--2 Retrieving and Setting Logix5000 Controller Status Values with GSV/SSV Instructions
To clarify, state that the object class is GSV/SSV Parameters

the general category, the instance name
is the specific occurrence, and the GSV/SSV instructions operate on the values for these parameters:
attribute is the specific piece of data.
 Class
Note that the source and destination are  Instance
similar to the source and destination in a  Attribute
MOV instruction.
 Source (SSV) or destination (GSV)
Class
Show students examples of object The class is the category or type of object that is accessed:
classes in the Online Help.
Category
Instance
Note that this is one reason that naming If more than one project component relates to the class selected, an
I/O modules with a descriptive name instance must be selected:
(using purpose or location, for example)
is beneficial.
Specific Component Specific Instance Name
? How would the “This” option help Select “THIS” to identify the current task,
programmers work more efficiently? program, or routine. The instruction can then be
Answer: The same code can be copied easily reused.
to another task, program, or routine and
still function properly without further edit.
Attribute
Note that not all attributes are able to be The attribute is the particular property or value that is retrieved or
retrieved and set. set:
Property to Monitor
GS2sb56r
Retrieving and Setting Logix5000 Controller Status Values with GSV/SSV Instructions 12--3
Source or Destination
A source contains values that will be set by an SSV instruction. A
Add that the layouts of the required destination stores the values that are retrieved by a GSV instruction:
source or destination data types are
detailed in the documentation reference
guide and in the online Help system.
Storage Tag for Value
The destination tag data type must match the size

and layout of the source as specified in the Help
system.
If the tag is a user-defined data type or an array of

data, select the correct member of the user-defined
data type or element of the array:
User-Defined Data Type Based on Data

Structure in the Help System
The first member of

the tag (Year) must
be selected.
GS2sb56r
Example: GSV Instruction

GSV instructions can be used to retrieve information about
program scan time:
Tag
User-Defined
Data Type
In
CIPtheobject
example
classinstructions,
and the CIPpoint out the
object This example shows how to retrieve status information from a
program class. The specified program is named “DISCRETE”:
name and then the attribute name. Note
that these instructions are not  One GSV instruction retrieves the value of the last scan time.
conditioned.
 The other GSV instruction retrieves the value of the max scan
time.
 Both instructions place the data in different members of a
user-defined structure named Discrete_Info.
GS2sb56r
Example: SSV Instruction

The following is an example of an SSV instruction:
Add that this method can also be used In this example, an SSV instruction is used to enable or disable a
to enable or disable an I/O module, program.
which is similar to inhibiting bits within a
PLC-5 controller. Based on the value moved into the Discrete_Progr_Flag tag, the
appropriate value is placed in the disable flag attribute of the
In the example instructions, point out the program named “DISCRETE.”
object class and the object name and
then the attribute name.
Status Flags
Stress that most controller values are Controller status and arithmetic status flags can also be examined for
accessed using GSV and SSV specific data.
instructions.
Note that flags are not base tags. Most controller configuration and status values are accessed using
Programmers will never see or create the GSV and SSV instructions. There is also a set of status and
alias tags for them.
arithmetic flags that can be accessed directly in relay instruction
operands.
These flags are not base tags and you cannot

create alias tags for them.
GS2sb56r
Controller Status Flags

Limited controller status can be examined using the following
controller status flags:
This status flag . . . Is set after the . . .

First scan S:FS First normal scan of the routines in the current program
Generation of an instruction-execution minor fault by program
Minor fault S:MINOR
execution
Arithmetic Status Flags

Arithmetic status flags can be used to view the results of an
Add that for on-the-job reference, the arithmetic operation:
status flags are listed in the
documentation reference guide.
This status flag . . . Is set when the . . .
Value being stored cannot fit into the destination because it is
Overflow S:V either greater than the maximum value or less than the
minimum value for the destination
Zero S:Z Instruction’s destination value is zero [0]
Sign S:N Instruction’s destination value is negative
Carry S:C Instruction generated a carry
Mention that a non-recoverable fault is Fault Types

often called a hardware fault.
The controller detects three main categories of faults:
 Non-recoverable major fault
 Recoverable major fault
 Minor fault
GS2sb56r
Mention that a non-recoverable fault is Non-Recoverable Major Fault

often called a hardware fault.
Non-Recoverable Major Fault: A fault within the controller that is
severe enough to shut it down.
The following changes take place in the system:

Note that students should have a basic  Outputs change to the Fault Mode state set in the I/O
understanding of digital I/O configuration configuration.

from the fundamentals course or
equivalent experience. More in-depth  The controller clears the project from its memory.
information is available in the
Troubleshooting Discrete I/O Modules  Depending on your controller and firmware, the controller OK
lesson. LED turns flashing red or solid red.
Mention in controllers with older  The word “Faulted” is displayed in the Online toolbar.
firmware (version 13 or earlier), a
non-recoverable fault is indicated
by a solid red OK LED.
Flashing Red
(Solid in Some Controllers)
Recoverable Major Fault
Recoverable Major Fault: A fault that is severe enough to shut

Note that the major fault types and down the controller if the condition is not cleared.
codes and the minor fault types and
codes can be found in the Help system A recoverable major fault can be of two categories:
and the appendices of the Procedures
Guide.  Instruction execution
 Other errors:
-- Power loss
-- Loss of critical I/O
-- Array subscript errors
GS2sb56r
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 Each program can have its own fault routine:
created in the program and assigned.
Additionally, a GSV instruction can be  The controller executes the program’s fault routine when an
used to retrieve the fault code and store instruction-related fault occurs.
it in a tag.
 If a fault is cleared, the routine continues executing at the
Remind students that non-instruction instruction immediately after the one that caused the fault:
level faults include I/O faults, task
watchdog faults, etc. -- The controller does not enter Fault mode.
Add that for non-instruction faults, no A fault routine normally contains logic to identify a fault and
program fault routines are called. sometimes clear it:
Fault Routine Icon

? How do you access another routine
from the main routine?
Answer: Program a JSR instruction to
call the specified routine (subroutine)
from the main routine. Fault Routine Code
Elements 0 to 1: 64-Bit Timestamp
Element 2: Fault Type (Lower 16 Bits) and Code (Upper 16 Bits)
Elements 3 to 10: Fault-Dependent

Information
Controller Fault Handler

Each project contains a Controller Fault Handler folder. A
programmer may add one optional program to it.
A controller fault handler executes in the following situations:

 When a recoverable major fault is not related to an instruction
 When a program fault routine does not exist or could not clear an
instruction-related fault
GS2sb56r
Note that the programming language At minimum, a main routine must be created and assigned:
works in the same manner as the
programming in a fault routine.
Program
Main Routine
Subroutine
Recoverable Major Fault Processing: Level 2

If the controller fault handler does not exist or cannot clear the
recoverable major fault, the controller enters Fault mode and shuts
down:
 Outputs change to the configured output state for Program mode.
 The controller OK LED flashes red.
 The word “Faulted” is displayed in the Online toolbar:
Logix5563
Flashing Red
GS2sb56r
Multiple Recoverable Major Faults

Remind students that the fault With multitasking capabilities, a controller can handle as many as 32
information is displayed on the Major simultaneous recoverable major faults.
Faults tab of the Controller Properties
dialog box.
If multiple recoverable major faults are reported, the following
actions take place:
 The controller processes the faults in the order that they occur.
 If any of the faults are not cleared by the controller fault handler,
the controller goes into Fault mode:
-- The fault that was not cleared and up to two additional faults
are logged.
-- This information can be viewed via the Major Faults tab in the
controller properties.
 If over 32 major faults occur at the same time, the controller goes
into Fault mode:
-- The first three major faults are logged into the controller fault
log.
Remind students that a watchdog fault  If a watchdog fault occurs a second time in the same logic scan,
occurs if the sum of the execution times the controller enters Fault mode, whether or not the controller
for all programs in a task is greater than
the watchdog value. fault handler clears the fault.
Common Major Faults
Common major faults include:

 Required I/O connection has failed

Array subscript is too big
 A timer has a negative preset or accumulated value
 Task watchdog timer has expired
 Others
Minor Fault
Minor Fault: A fault that is not severe enough to shut down the
controller:
 Low battery
 Serial port problems
GS2sb56r
With a minor fault, the following changes take place in the system:
 The program scan and normal I/O control continues.
 The controller OK LED remains solid green.
 A minor fault bit is set.
Logix5563
Normal
Operating
State Solid Green
A minor fault may only be detected if

programming language is written to monitor it or
if you monitor the Minor Faults tab in the
Controller properties.
A minor fault does not affect application
operation. However,
improve scan time. clearing a minor fault may
GS2sb56r

 Retrieve and set a controller status value using GSV and SSV
instructions
 Assign a fault routine

- Object and Attribute information found in the Help

system
- Fault Routine Assignment drop-down list
GS2sb56r
Exercise: Retrieving and Setting Logix5000 Controller Status Values with GSV/SSV Instructions 12--13
Exercise: Retrieving and Setting

Logix5000 Controller Status Values
with GSV/SSV Instructions
Exercise A In this exercise, you will practice retrieving controller status data.
Context:
You have completed and tested your project. You would like to test
your fault routine to verify it works correctly. For troubleshooting
purposes, you want to retrieve the maximum scan time for each
program in the project.

Directions:
1. Open the GS2_1756r_A1.acd file.
4. The controller has faulted because the logic in rung 3 of the Main

routine of the Conveyor program is attempting to place a value in
an element of an array that does not exist. Clear the fault from
within the Controller Properties dialog box.
5. Assign the Conveyor_Fault routine as the fault routine of the
Conveyor program.
6. Place the controller in Remote Run mode and verify the fault has
been corrected.
7. What instruction could be used to retrieve the maximum scan
time of a program?
8. In the MainRoutine of the Conveyor program, create the ladder

logic required to retrieve the maximum scan time for the
Conveyor program. Store this information in an existing program
tag named Max_Scan_Time.
Tip " Search Help for the MAXSCANTIME attribute for help configuring
your logic.
GS2e56r
12--14 Exercise: Retrieving and Setting Logix5000 Controller Status Values with GSV/SSV Instructions
9. Modify your ladder logic so that the rung could be copied to any
program and still retrieve the max scan time without additional
modification.
10. Copy the Max_Scan_Time tag and the ladder logic into the main
routines of the other three programs.
11. Verify and save your project.
12. To test your work, verify that a scan time is recorded in each of
the four ladder logic instructions.
Exercise B In this exercise, you will practice retrieving controller status data and
store this information in a user-defined data type.
Context:
Using the project in the controller in slot 3, you want to record shift
numbers based on controller status data. You are now ready to
retrieve the current controller wall clock value.

Directions:
1. Open the GS2_1756r_B1.acd file.

2. Based on the WallClockTime Date/Time information in the Help
system, create a user-defined data type called DateTime that will
store the current wall clock time.
3. Create a tag called Wall_Clock that uses the DateTime data type
that you just created.
4. Open the MainRoutine of the Shift_Calculation program in the
Periodic Task.
5. Draft the ladder diagram required to retrieve the current clock
time from the controller and store it in the Wall_Clock tag.
Tip " Be sure to select the correct member in the Wall_Clock tag.
6. In the Shift_Calculation program tags, create a new DINT tag

called Shift_Number.
GS2e56r
Tip " Shift times are calculated using the following parameters. 24-hour
times are used:
If the time is Between (Limited to). . . The Shift Number Is . . .

7 14:59 1
15 22:59 2
23 6:59 3
7. In the Shift_Calculation MainRoutine, enter the logic required to

move the correct shift number into the Shift_Number tag based
on the current Wall_Clock.Hour time.
11. Verify that the current shift is correctly calculated in the ladder
logic.
12. Monitor the Wall_Clock tag to see the values changing for all
members of the structure.
Exercise C In this exercise, you will practice retrieving controller status data and
assigning a fault routine.
Context:
You must program a fault routine that will capture a controller’s

major fault record and clear the fault record. You must develop logic
that faults the controller to test the fault routine.

Directions:
1. Open the GS2_1756r_C1.acd file.

2. Create a user-defined data type named MajorFaultRecord with
the following elements:
Name Data Type
TimeLow DINT
TimeHigh DINT
Type INT
Code INT
Info DINT[8]
GS2e56r
3. Create two new controller-scoped tags using the

MajorFaultRecord data type:
 Capture
 Clear
4. In the Controller Fault Handler folder within the Controller

Organizer create a new program name ProgramFaults.
5. Create a new routine within ProgramFaults named
Capture_Clear_Faults.
6. Assign Capture_Clear_Faults as the main routine of the

ProgramFaults program.
7. Open the Capture_Clear_Faults routine.

8. Add a GSV instruction that will store the MajorFaultRecord of
any program that calls this fault handler routine in the
Capture.TimeLow tag.
9. Add a SSV instruction that will use the Clear.TimeLow tag to
clear the MajorFaultRecord of any program that calls this fault
handler routine.
10. Configure the existing Clear_Fault tag as an enabling condition
for the SSV instruction.
11. Open the MainRoutine in the MainProgram of the MainTask .
12. Add the following logic to the MainRoutine:
Tip " This logic

into the will tag
Timer
generate
preseta when
controller faultswitch
selector by placing
12 is an invalid value
enabled.
13. Verify your project.
14. Download to the controller in slot 1 and place your controller in

Remote Run.
GS2e56r
15. Verify the project is working correctly by performing the

following:
A. Enable selector switch DI12.
B. Verify the controller faults.
C. Monitor the Capture tag and confirm it is populated with data

from the MajorFaultRecord.
D. Access Controller Properties and clear the fault.
E. Enable selector switch DI13.
F. Place the controller in Remote Run mode.

G. Confirm the controller does not enter a faulted state.
H. Go offline and close your project.
GS2e56r
Answers Exercise A
4. The fault can be cleared by selecting the Clear Majors button

from within the Controller Properties dialog box:
5. Assign the Conveyor_Fault routine from the Configuration tab

within the Program Properties dialog box:
7. The Get System Value (GSV) instruction retrieves controller

system data including the maximum scan time for a program.
GS2e56r
8. Based on the memory structure of the MaxScanTime attribute, a

program-scoped DINT tag was created in the Conveyor
program and the following ladder logic was programmed:
9. Because the “THIS” instance name was used, the ladder logic
could easily be copied to the three machine stations.
Exercise B
2. The following user-defined data type was created to store the

date/time information in a readable form:
Help System Information:
The data type must be the same order as the

date/time information or data will be stored
incorrectly.
GS2e56r
3. A tag named Wall_Clock (of the DateTime data type) was

created to store the retrieved wall clock values:
5. The following ladder logic was entered to retrieve the date/time

information and set the shift number:
This is a tag of a The first element of the

user-defined address (Year) must be
data type named selected.
DateTime.
GS2e56r
7. The following logic could be used to move the correct shift

number into the Shift_Number tag based on the current
Wall_Clock.Hour time:
Time Between 7 and 14:59
GS2e56r
Exercise C
2. The structure of your MajorFaultRecord data type should be

configured similar to the following:
3. You should have added the following controller-scoped tags:
6. Your Controller Fault Handler folder should now look similar to
the following:
8. Your GSV instruction should be configured similar to the

following:
Use the first member

of the Capture tag
GS2e56r
9. Your SSV instruction should be configured similar to the

following:
10. The rung you placed the SSV instruction on should now look
similar to the following:
GS2e56r
GS2e56r
Lesson 13
Programming a BTD Instruction in
What You Will Learn After completing this lesson, you should be able to program a Bit
Field Distribute (BTD) instruction in an RSLogix 5000 project.
Sometimes groups of bits within a value have a specific meaning. A

BTD instruction lets you extract those bits so they are easier to use.
Before You Begin BTD (Bit Field Distribute) Instruction
Mention that if the length of the bit field A BTD instruction copies specified bits from the Source, shifts the
extends beyond the destination (Dest), bits to the appropriate position, and writes the bits into the
the instruction does not save the extra
bits. Any extra bits do not wrap to the destination (Dest).
next word but instead are dropped.
When enabled, a BTD instruction copies a group of bits in the
following manner:
 The group of bits is identified by the Source value bit (lowest bit
number of the group) and the length (number of bits to copy).
 The destination (Dest) bit identifies the lowest bit number to start
with in the destination (Dest).
 The Source value remains unchanged.
BTDsb56r
13--2 Programming a BTD Instruction in an RSLogix 5000 Project
The following example copies 6 bits to a different location in the

same tag:
Destination (Dest) Bit Source Bit
value_1
Before BTD
Instruction
value_1
After BTD
Instruction
The shaded boxes show the bits that changed in value_1.
AFTER MOVE:
BTDsb56r
Programming a BTD Instruction in an RSLogix 5000 Project 13--3
Here’s How To program a BTD instruction.
Example BTD Instruction
This
BTDexample gets
instruction tostatus
make information about
the information an I/O
easier to module
use: and uses a
1.
2.
3.
4.
5.
To show why you are using bits 12 to 15: 1. The GSV instruction gets status information about some part of
1. Click the GSV instruction. the system.
2. Press F1. 2. In this example, the GSV instruction gets the status of the I/O
3. Scroll through the help and click the module in slot 2 of the workstation.
GSV/SSV Objects link. It is near the
end of the Description section. 3. Bits 12 to 15 give the status of the module.
4. Click the MODULE link. 4. The BTD instruction extracts bits 12 to 15 and stores them in a
separate tag.
Remove the I/O module from the 5. It is now a lot easier to use the status information. If the value is
chassis and point out the change in the not 4, there is a problem.
status value.
BTDsb56r
13--4 Programming a BTD Instruction in an RSLogix 5000 Project
requirements
certificate and fully
students prepare
for the final exam,
Use the BTD_1756R_DEM1.acd file for Pay attention to these critical aspects of the demonstration:
your demonstration.
- Which side of the bit pattern is the first bit
After you demonstrate, ask each key
point as a question and have the - At what number the source or destination bit starts
students tell you what they noticed.
Your Turn Now it’s your turn. Complete Exercise A.
BTDsb56r
Exercise: Programming a BTD Instruction in an RSLogix 5000 Project 13--5
Exercise: Programming a BTD

Instruction in an RSLogix 5000
Project
Exercise A Practice programming a Bit Field Distribute (BTD) instruction.
Context:
Suppose you need to know the physical position of the controller’s

keyswitch. You already have a GSV instruction that gets the status
attribute for the controller. You want to make it easier to read the
position of the keyswitch.
Status Attribute for the Controller

The status attribute for the controller provides the following
information. You want only the keyswitch position.
Bits Bit Pattern Meaning

Bits 3--0 Reserved
Bits 7--4 0000 reserved
0001 flash update in progress
0010 reserved
0011 reserved
0100 flash is bad
0101 faulted
0110 run
0111 program
Bits 11--8 0001 recoverable minor fault
0010 unrecoverable minor fault
0100 recoverable major fault
1000 unrecoverable major fault
Bits 13--12 01 keyswitch in run
10 keyswitch in program
11 keyswitch in remote
Bits 15--14 01 controller is changing modes
10 debug mode if controller is in Run
mode

BTDe56r
13--6 Exercise: Programming a BTD Instruction in an RSLogix 5000 Project
Directions:
1. Open the BTD_1756R_A1.acd project file.
2. Open MainRoutine.
The MainRoutine has a GSV instruction that retrieves the Status

attribute of the controller. The instruction stores the value in the
Controller_Status tag.
3. Extract the bits for the keyswitch position from the
Controller_Status tag and put them in their own tag. The
Controller_Status tag is an INT data type so create an INT tag to
store the keyswitch bits.
4. Download the project to slot 1 of your workstation.
5. Put the controller in Run mode.
6. Change the position of the keyswitch and check your work:

If you turn the keyswitch to . . . The status value should be . . .
RUN 1
REM 3
8. Go offline.
BTDe56r
Exercise: Programming a BTD Instruction in an RSLogix 5000 Project 13--7
BTDe56r
13--8 Exercise: Programming a BTD Instruction in an RSLogix 5000 Project
Answers Exercise A
3. The following graphic shows how to set up the BTD

instruction:
Rung 0 The GSV instruction that retrieves the Status attribute of the
controller and stores it in the Controller_Status tag.
The BTD instruction copies bits 12 and 13 (length = 2) of the
Rung 1 Controller_Status tag. It puts them in bits 0 and 1 of the
Keyswitch_Position tag.
BTDe56r
Lesson 14
Configuring a Logix5000 Message
 Configure a message (read, write, and CIP generic)
Remind students how this is different  Create and enter a numeric communications path
than the data they sent earlier across a
ControlNet network. Stress the
difference between produced and
consumed tags (scheduled with RPI) When You Will Do This
and messages (unscheduled).
Poll students to find out if they have Here are some situations when you may need to use a Message
programmed messages for any other (MSG) instruction:
types of controllers.
 Send data to other Logix5000 controllers
 Send data to PLC-5 and SLC 500 processors
 Reset faulted 1756-I/O modules
Before You Begin Unscheduled Data

Remind students that deterministic data
is data that arrives at the same time Unscheduled Data: Non-deterministic information that is not time
interval.
critical. This type of data has the following characteristics:
Stress that scheduled data, such as
control and I/O data, is given highest  Transmits after all scheduled data has been sent
priority on the ControlNet network. Other  Can be any of the following:
information, such as programming or
upload and download operations, does -- Connection establishment
not interfere with the transport of control
and I/O data. -- Programming data (uploads and downloads)
-- Ladder-initiated, peer-to-peer messaging data (MSG
? How is scheduled data sent? instruction)
Answer: Using produced and consumed
tags (locally and over a Control
network). Messages to Logix5000 Controllers
A message is unscheduled data that is exchanged over a

communications network. When using a message to send data to or
from a Logix5000 controller, keep in mind the following rules:
 Both the source and destination tags must be controller-scoped.
Note that PLC-5 and SLC 500  The source and destination tags cannot be Axis, Message, or
controllers require Integer data. Motion_Group tags.
 Array elements and structure members cannot be specified:
-- Use an alias tag to send these types of data.
 A portion of an array cannot be transferred:
-- Send the entire array using the array name, or send one
element of an array using an alias tag.
MS2sb56r
14--2 Configuring a Logix5000 Message
Messages to Other Controllers
A Logix5000 controller can also send a message to communicate

with the following controllers:
 A PLC-5 controller
 An SLC 500 controller
Configuring a Message
Remind students that in other To configure a message to any controller or module, the following
controllers, the data file is already items must be completed in this order:
created. In this controller, you must
define the memory area with a tag. 1. Add the destination controller to the I/O configuration (optional).
2. Create a controller-scoped tag of the message data type.

3. Along with any ladder logic conditions, program a message
(MSG) instruction with the new tag as the message control tag.
4. Configure the MSG instruction.
In the graphic, point out that the The flow of the configuration process is shown in the following
Message tag is the main operand in the graphic:
MSG instruction.
1. Add the Destination Controller
2. Create a Tag of the

Message Data Type
3. Program an
MSG Instruction
4. Configure the
MSG Instruction
MS2sb56r
Configuring a Logix5000 Message 14--3
Mention that complete demonstration To continuously enable a message, condition the message with an
including how to select the values used XIO instruction that examines the message control word enable bit:
in the dialog box will be presented in the
Here’s How demonstration.
Note that the message is continuous as

long as the task is active and the routine
is enabled.
Add that when using a message for fault
finding, use a pushbutton to enable the
rung. This will allow the entire message
code to be displayed. Read, Write, and Block Transfer Parameters
The following is an example of a configuration screen for a read

message:
Note that RSLogix 5000, version 10 and To configure a read, write, or block transfer message, the following
higher, provides many enhancements for parameters must be configured:
sharing data with SLC 500 controllers.
 Source Element: The tag or logical address currently containing
the data to be transferred:
Note that a read instruction helps -- For a read message type, the source element is the address of
identify the source of the data. Writes do the data you want to read in the target device. Use the
not identify the destination.
addressing syntax of the target device.
-- For a write message type, the source tag is the tag of the data
in the Logix5000 controller that you want to send to the target
device.
Example: The tag timer1 is one element  Number of Elements: The number of elements to be transferred.
that consists of one timer structure. The number of elements you read/write depends on the type of
data you are using.
 Destination Element: The tag or logical address to which the
data will be transferred:
-- For a read message type, the destination tag is the tag in the
Logix5000 controller where the data being read from the
target device will be stored.
-- For a write message type, the destination element is the
address in the other device (remote device) where the data will
be written.
MS2sb56r
 Cache Connections: A bit that instructs the controller to

maintain or close the connection after a message has executed:
-- Because initiating a message increases scan time, for a
continuous message, enable the cache bit.
-- For a message that is infrequently sent, disable the cache bit.
 Path:
Note that entering a numeric path is -- Select a module or port in the I/O configuration using the
included in the Procedures Guide. A Browse feature.
detailed example is also included.
-- If the module is not available in the network tree, create and
enter a numeric path.
Creating and Entering a Numeric Communications Path
The numeric path rules are provided in the Glossary of the

Review the path rules in the Procedures
Guide. Procedures Guide. Turn to the Glossary and review the rules now.
Tip " A combination of module name and numeric paths can be used:
Point out the following in the address:
1, ENET_Module, 2, 130.151.138.104, 1, 3
S 1 represents the path out the
backplane of the controller.
S ENET_Module is the name of the Numeric Communications Path
selected module.
Module Name
S 2 represents the Ethernet
port.
S The IP address is the IP address of
the destination module. Tip " Programmatic reconfiguration of the communications path, node
address, parameters, and source/destination permits one message to
S 1 represents the path from the target multiple devices, reducing the number of messages in a
destination module to the controller
across the backplane. project.
S 3 represents the slot number of the
destination controller.
CIP Generic Message Parameters
A CIP generic message is used to:

 Transfer a block of data between Logix5000 controllers
Note that a CIP message can send  Send configuration data from a Logix5000 controller to an I/O
configuration information to a module module:
that can be conditioned by an operator
input. -- Perform a pulse test on a digital output module
-- Reset electronic fuses on a digital output module
-- Reset latched diagnostics on a digital input or output module
-- Reset latched status on an analog module
 Perform a device reset or Device Who operation
 Perform custom operations
MS2sb56r
Configuring a Logix5000 Message 14--5
The following is an example of a configuration screen for a CIP

Note that a hex code for the Service generic message:
type is not always required as of
RSLogix 5000 software, version 10.
To configure a CIP generic message, the following parameters must
be defined:
 Service Type: The type of service to be performed on the module
(e.g., resetting latched diagnostics or performing a pulse test).

Depending on the service, some of the following Hex codes may
be required:
Note that these names were changed to -- Service code: Category of service to be performed.
match the Class, Instance, and Attribute
Names of DeviceNet objects (for
-- Class: The I/O module type.
DeviceNet explicit messaging). -- Instance: Message type ID.
Mention that logical address refers to an -- Attribute: The attribute to be reset (such as latched status on
address in a controller other than a an analog module).
Logix5000 controller.
 Source Element: The tag or logical address currently containing
Point out that
software, with10
version RSLogix 5000
or higher, the data to be transferred.
programmatic bumpless reconfiguration  Source Length: The number of elements to be transferred.
of an I/O module allows you to
reconfigure I/O module settings without  Destination: The tag or logical address to which the data will be
resetting the outputs, providing better transferred.
control of I/O.
Tip " Additional information on Service Type can be found in the
Procedures Guide.
Message Execution
Have the students open the
Documentation Reference Guide. While online, message errors can be identified in RSLogix t 5000
Review
Point outthe
theMSG bits andon
information their
MSG functions.
error software:
codes.  A message that is not received will not have the .DN bit set.
Note that the enhanced message debug  Error codes can be found in the configuration dialog box:
tools also provide error codes that
reduce ambiguity in error messages. -- Enhanced message debug tools identify which module
generated the run-time error code.
MS2sb56r

 Configure a message (read, write, and CIP generic)
 Create and enter a numeric communications path
Use the during
project CCP143_1756r_DEM2.acd
the demonstration.
- How to open the Message Configuration dialog box
- Cache Connections option
MS2sb56r
Exercise: Configuring a Logix5000 Message 14--7
Exercise: Configuring a Logix5000

Message
Exercise A In this exercise, you will practice configuring a message that is sent
from one Logix5000 controller to another Logix5000 controller.
Context:
You are part of a team that programmed a Logix5000 compressor

assembly line. This line is running successfully; therefore, you have
set up an identical production line. These lines are connected by a
network. To keep track of daily production, you want the master
controller to read the production total from the other line. You are
now ready to send a message from a Logix5000 controller to another
Logix5000 controller.
The plant setup is shown in the following graphic:
Remote Line
Network
Local Line

Directions:
1. Open the MS2_1756r_A2.acd file.
2. Download the project to the controller in slot 3 of the remote

workstation.
4. Open the MS2_1756r_A1.acd file.
MS2e56r
14--8 Exercise: Configuring a Logix5000 Message
5. To select the controller in the communication path in the message

configuration, add the controller in slot 3 of the remote
workstation to the I/O configuration of the project:
 Add a local communications module (the CNB or ENBT) to
the I/O Configuration
 Add the remote communications module
 Add the remote controller in slot 3, name it
Remote_Controller.
6. In the Conveyor program, create a ladder diagram routine named

Count_Total.
7. In the Conveyor program Main Routine, program a JSR
instruction to access the Count_Total routine.
8. At what scope must a message control tag be created?
9. Create a message control tag for the message execution called

Count_Message.
10. In the Count_Total routine, write ladder logic that enables a

message instruction when DI7 is pressed.
Tip " Create a tag named Read_Remote_Total and make it an alias for
DI7.
11. Configure the message instruction as follows:

 The message uses the Count_Message message control tag.
 The message type is CIP Data Table Read.

 When DI7 is pressed, the message reads the value of
Count_Passed.ACC from the controller in slot 3 of the
remote station.
Tip " The timer value (Count_Passed.ACC) is a DINT.
 The message stores the value in a new tag called

Count_Passed_Line_2.
Tip " Be sure that you have created the Count_Passed_Line_2 tag in your
application.
12. Identify the communication path in the communications

configuration of the MSG instruction.

MS2e56r
16. Test your system by performing the following actions and placing
a check in each completed box:
- Press DI7.
- Monitor the Count_Passed_Line_2 tag.
- Record the value: _____________________

- At the other production line (workstation) create one or
more new parts.
Tip " To create a new part, toggle DI12 from the left then to the right.
- Press DI7 on the remote workstation and verify that the

value of the Count_Passed_Line_2 tag increases.
- Using the other production line, create 1 more new part.
- Press DI7 again and verify that the value of the
Count_Passed_Line_2 tag increases again.
Exercise B In this exercise, you will practice configuring a CIP Generic

message.

Context:
During operation, you want the controller to monitor the part sensor
input for an open-wire condition. If an open-wire condition exists,
you want the controller to turn on an alarm light. When the condition
is cleared, you want the operator to unlatch the module fault bits
using a reset pushbutton.
Directions:
1. Open the MS2_1756r_B1.acd file.

3. Create a control tag for the message execution called
Part_Sensor_Reset_Message.
MS2e56r
4. In the I/O Diagnostics routine in the Common program, enter

the following ladder logic (the tags have already been created):
5. Make the Part_Sensor_Fault tag an alias tag for an open wire

fault on the part sensor (bit 12 of the input card in slot 2).
6. Read the ladder logic to gain an understanding of its purpose.
A. If the Part Sensor device has an open-wire fault, a pilot light
is illuminated.
B. If the operator pushes the reset button, a message is sent to
reset the module and turn off the light.
7. Create a controller-scoped tag named Part_Fault_Source of
DINT data type.
8. Modify the value of Part_Fault_Source tag so that each bit
within the tag has a value of 1.
Tip " Entering a value of --1 in the Part_Fault_Source tag will set each bit
to a value of 1.
9. Configure the message to reset the input module in slot 2.
 Message Type: CIP Generic
 Service Type: Reset Latched Diagnostics (O)
 Source Element: Part_Fault_Source
 Communications Path: Input module in slot 2
Tip " For help, go to the Reset Latched Diagnostics on a Digital Module
procedure within online Help.
10. Download the project to the controller in slot 3 and then place the
controller in the Remote Run mode.
11. To test the application, perform the following actions:
A. To simulate the open-wire fault for the part sensor, unlock

the module wiring arm on the input module in slot two and
then remove the wiring arm.
B. Verify that the operator alarm (DO7) is on.
MS2e56r
C. Verify that the diagnostic fault lights for the module are on
and that the fault tags each contain a 1.
D. Replace the wiring arm.
E. Acknowledge the alarm and reset the module by pressing

pushbutton DI6.
F. Verify that the module LEDs and the alarm light are reset.
G. Go offline.
MS2e56r
Answers Exercise A
5. The I/O configuration for an EtherNet/IP network should

appear as follows:
Local Comm Module
Remote Comm Module
Message Source
7. Your JSR instruction should be configured similar to the

following example:
8. The message execution tag must be controller-scoped.

10. The ladder logic that initiates the messages should appear as
follows:
New Tag of the MESSAGE Data Type
MS2e56r
11. The Configuration tab should appear as follows:
Count_Passed_Line_2 is a new tag that must be created.
The Communication tab should appear as follows:
MS2e56r
Exercise B
If your project is not functioning correctly, verify that you have

completed the following actions:
- Created a controller-scoped tag of the message type for the
message instruction
- Made the Part_Sensor_Fault tag an alias tag for
Local:2:I.OpenWire.12
- Created a source tag (DINT) with each reset value bit set to 1
- Created the ladder logic in the routine and configured the
MSG instruction
- Selected the input module in the Communications tab
The following alias tags and configurations were completed:
Alias for
Open-Wire an
Fault
on the Part
Sensor
Controller-Scoped Message Control Tag

Input Module Selected on
the Communications Tab
MS2e56r
Lesson 15
Developing an Add-On Instruction
in Ladder Diagram
Mention that you can also protect an  Plan the parameters of an add-on instruction
add-on instruction so that people can’t
change its logic and local data. Or you  Decide if you need an EnableInFalse routine
can hide the logic and local data  Create an add-on instruction
completely. Protecting an add-on
instruction is outside the scope of this  Use an add-on instruction in a routine
lesson.
 Monitor the values and logic of an add-on instruction
 Export and import an add-on instruction
Tip " Use RSLogix 5000 software to learn more. Go to Help > Learning
Center > What’s New.
Explain that add-on instructions are Use add-on instructions to save development time by making your
similar to subroutines. Point out the code more modular, re-usable, and easy to use:
advantages and tradeoffs of add-on
instructions as you go along.  Encapsulate your most commonly used logic as instructions,
similar to the controller’s built-in instructions
 Re-use the instructions in any of your projects
 Monitor an instruction and see its logic as it executes, even when
you use the instruction multiple times in a project
Before You Begin Add-On Instructions
Add-On Instruction: An instruction that you build from the built-in

instructions in the controller. An add-on instruction:
 Is similar to a subroutine
 Lets you encapsulate a routine of logic and use it as an instruction
AOILsb56r
15--2 Developing an Add-On Instruction in Ladder Diagram
Explain that an add-on instruction Example of an Add-On Instruction

executes similar to a subroutine. You
give it inputs, execute some code, and This add-on instruction checks for jammed product at the entry gate
get outputs. of a conveyor:
The instruction reads the state of a photoeye at the

entrance of a conveyor.
If the photoeye is on too long, it means that product

is jammed. When that happens, the instruction turns
on the Jammed bit.
When you execute the add-on instruction, it executes its logic:
The Detect_Jam instructionthis

executes
logic.
AOILsb56r
Developing an Add-On Instruction in Ladder Diagram 15--3
An Add-On Instruction Uses a Definition

Point out that with a subroutine you Add-on instructions are global in nature. You first create a definition
need a copy of it in each program that for the instruction. Then you enter instances of it into any of your
uses the subroutine.
programs:
This is the definition for the instruction.

It’s the template for each instance. These are instances of the instruction.
AOILsb56r
Key Parts of the Definition of an Add-On Instruction

The definition of an add-on instruction contains parameters, local
tags, and logic:
Parameters and local tags are the data that the instruction uses.
Logic is the code that the

instruction uses. It’s
comprised of one routine.
AOILsb56r
Parameters
When you create an add-on instruction, you set up parameters for the
instruction:
Parameter: A value or values that you give to an add-on instruction

or get back from it. Parameters create the interface to the code of the
instruction.
Here are some examples:

 Configuration values such as set points and timer presets
 Commands such as start, stop, and reset
 Input values from devices
 Output values for devices
 Status and health values such as done or faulted
Parameters reduce programming time and complexity.
Local Tags
When you create an add-on instruction, you can also set up local
tags:
AOILsb56r
Compare this to a subroutine. A Local Tag: An intermediate or storage value that an add-on
subroutine may show you more data instruction uses as it executes. It is a value that you don’t need to see
than you really need to see. This makes
it more difficult to monitor and or use outside of the instruction.
troubleshoot.
Here are some examples of local tags:
 Timers and counters
 Storage arrays
 Bits that store the sum of several input conditions
 Results of intermediate calculations
You can Alias a Local tag (or one of its members) to an input or
output parameter. In this way, the local tag can be easily
monitored/ modified outside of the AOI.
Routine “Type” Control Editable in AOI Definition

You can change the programming language of the Logic routine after
you develop the instruction. Keep in mind that changing the
language deletes the existing routine and replaces it with an empty
routine in the new language. This is helpful if you want to develop
several AOIs with similar interfaces but different languages for the
logic.
You can change the language type through the General tab of the
AOI:
AOILsb56r
Changes to the Definition

If you change the definition, it ripples through all the instances of the
instruction in your project:
Suppose you add a parameter to the It ripples through each instance of the instruction.
definition.
In version 17 and earlier, if you change a default

value for a parameter or local tag, it doesn’t
change existing instances of the instruction. They
keep their current values.
Starting with version 18, you can choose to send
changes you make to default values of a definition
to all its instances in the project.
AOILsb56r
Mention that default value changes can Change the default values within the Local Tags tab:
also be done in:
S Context menu
(Controller Organizer only)
S Data Monitor
S Logic Editor
S Watch Pane
Add-On Instruction Design Considerations

When a rung of ladder logic contains an add-on instruction, the
following actions occur during each scan:
 Data for each input parameter is passed to the instruction.
 If the rung-in condition is true, the instruction’s Logic routine is
executed.
 If the rung-in condition is false, the instruction’s Logic routine is
skipped.
? What happens to logic in a Tip " Version 18 improves the false scan times of AOIs that aren’t using an
subroutine if the JSR rung is False? EnableInFalse routine. See Knowledgebase IDan#53903 for ways to
Answer: Logic is not scanned and improve the false scan time if you need to use EnableInFalse
values in the subroutine remain routine.
unchanged.
Tell students the same thing would

happen if an AOI’s rung-in condition is
False. So if actions need to occur (like
resetting a timer or counter, unlatching a
bit,) when the rung goes False you could
add an EnableInFalse routine.
AOILsb56r
Here’s How To plan the parameters of an add-on instruction:

Keep the visuals open.
Example Planning the Parameters of an Add-On Instruction
Relate this to a real system. It could Suppose you want an instruction that checks for jammed product and
have many gates, all of which use the looks like this:
same logic to detect a jam.
Here are the parameters and local tags for the instruction:
Value Use? Required? Visible?

Input parameter
D. State of the photoeye that detects the product Output parameter
Local tag
Input parameter
E. How long to let the photoeye stay on before the instruction flags a jam. You
want to be able to configure this value. Output parameter
Local tag
Input parameter
F. Flag that there is a jam. You want to see this and use it in your application
Output parameter
code.
Local tag
Input parameter
G. Timer that times how long the photoeye is on. You really don’t care about
Output parameter
the accumulated value.
Local tag
Your Turn Now it’s your turn. Do Exercise A and return here when you’re done.
Tell the students to stay at their desk
and do the exercise. They don’t need
the workstation for it. Review the
answers when they’re done. Then
continue with the lesson.
AOILsb56r
Before You Begin After you plan the parameters for an add-on instruction, you have to
make these decisions about its logic:
 Language for the Logic routine
 Organization of the Logic routine

Optional scan mode routines
Language for the Logic Routine of the Instruction
You can program the Logic routine of an add-on instruction in any of
these languages:
 Ladder diagram
 Function block diagram
 Structured text
You can use the instruction in any language, regardless of which
language you use for the Logic routine.
Organization of the Logic Routine
If the students ask, tell them that there’s You can’t call subroutines within an add-on instruction. You can
no defined limit to the levels of nested organize the logic of an add-on instruction in two ways:
instructions. It seems to be around 62
instructions deep. They’ll get a major  Put all the logic in one routine
fault, stack overflow, if they go too deep.
 Nest smaller add-on instructions within a larger add-on
instruction
Here’s an example of nested instructions:
Main Instruction That

Controls a Conveyor
Sub-Activities, Such
as Starting the Motor
and Watching for Jams
AOILsb56r
Optional Scan Mode Routines
The controller executes the Logic routine of an add-on instruction

like this:
When this happens . . . The controller . . . Notes

As a general rule, prescan executes instructions as if all
conditions are false.
1. Controller goes to Run mode. Prescans the Logic routine
Some instructions don’t follow the general rule. See the
documentation for the instruction.
EnableIn is true in these situations:
EnableIn parameter of the add-on Ladder diagram — when the rung conditions are true.

2. Executes the Logic routine
instruction is true Function block diagram — True by default.

Structured text — Always true.


EnableIn is false in these situations:

EnableIn parameter of the add-on Doesn’t execute or stops executing Ladder diagram — when the rung conditions are false.

3. Function block diagram — when you write a zero to the


instruction is false the Logic routine
EnableIn parameter.
Structured text — Never. EnableIn is always true.

As a general rule, postscan executes instructions as if all

The last scan of a step of an SFC conditions are false.
4. Postscans the Logic routine
that’s configured for automatic reset Some instructions don’t follow the general rule. See the
documentation for the instruction.
You can add routines to an add-on instruction that take additional

actions during various scan situations:
The add-on instruction’s Prescan routine executes one

time after the main program prescan. It executes
according to its logic conditions.
The Postscan routine executes one time after the main
program postscan. It executes according to its logic
conditions.
The EnableInFalse routine executes when conditions
are false.
? What happens to logic in a

subroutine if the JSR rung is False?
Answer: Logic is not scanned and
values in the subroutine remain
unchanged.
Tell students the same thing would
happen if an AOI’s rung--in condition is
False. So if actions need to occur (like
resetting a timer or counter, unlatching a
bit,) when the rung goes False you could
add an EnableInFalse routine.
AOILsb56r
Here’s How To decide if you need an EnableInFalse routine:

Keep the visuals open. Present the
decision. Then apply it to the example. Ask this question:
Do you need to clear datyes
a or do other reset actions when rung conditions are false?
 Yes — Use an EnableInFalse routine.
 No — You don’t need an EnableInFalse routine.
Example Deciding If You Need an EnableInFalse Routine
Suppose your add-on instruction uses a non-retentive timer, like this:
And suppose you want to reset the timer when Conveyor_Running is

off. In that case, use an EnableInFalse routine to reset the timer.
Your Turn Now it’s your turn. Do Exercise B and return here when you’re done.
Tell the students to stay at their desk
and do the exercise. They don’t need
the workstation for it. Review the
answers when they’re done. Then
continue with the lesson.
AOILsb56r
Before You Begin Once you have your general design, it’s time to create and test the
definition. To do that, you’ll need to be familiar with:
 Accessing parameters via logic
 Editing the instruction

Exporting and importing
Accessing Parameters via Logic
When you define the parameters, RSLogix 5000 software puts them
into an add-on-defined data type. Use that data type as the first tag
(main operand) in each instruction:
Point out that this is similar to accessing To access a parameter via logic, use this address format:
the data of a timer or counter.
Add-On-Defined_Tag.Parameter
For example, use this address to read the value of the jammed bit:
AOILsb56r
Editing an Add-On Instruction
Point out that this is one advantage of If you need to change the logic of an add-on instruction, you must go
subroutines over add-on instructions. offline and edit the definition. You can’t :
You can edit a subroutine online.
 Edit the logic of an add-on instruction while online
 Edit just a single instance of the instruction
Exporting and Importing an Add-On Instruction
Compare this to a subroutine. You can You can export an add-on instruction to an .l5x file or import an
export a subroutine only if you wrote it in instruction into a project via an .l5x file:
ladder diagram.
Export
Import
When you import an add-on instruction, it changes

any existing instances of the instruction in your
project. Before you import an instruction, identify
the changes. After you import the instruction, check
that each instance of the instruction executes
correctly.
Tip " Beginning with version 17 of RSLogix 5000, you can import a new
add-on instruction while online to a running controller.
AOILsb56r
Online Safety Warning

When performing any tasks online, keep the following warning in
mind:
Describe any real-world situations that

you are aware of in which online editing Use extreme
ladder logic orcaution when entering
data, forcing values, orormaking
editing other
caused extensive damage in a plant.
changes online that will affect the control of
? Define offline and online? devices. Mistakes can cause unintended machine
motion or loss of process control, possibly injuring
Answer: Offline means that the personnel and damaging equipment. Before
workstation (computer) is displaying a
copy of the project stored in the performing procedures online, complete these safety
computer memory only. Online means precautions:
that the workstation (computer) is
displaying and changing copy of the  Determine if changes must be made online.
project stored in the controller memory.  Verify that your company permits online entering
and 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.
Also note that the left and right power Because changes in any online mode can affect
rails are illuminated in the Run and machine and process control, before importing
Remote Run modes to indicate that the
ladder logic is active in the controller. add-on instructions, verify the current
communications mode using the Online toolbar.
Add that the Online graphic is animated
in any online mode.
AOILsb56r
Referenced Add--On Instructions and User-Defined Data Types
You have to decide how to handle Referenced Add- On

Instructions and User- Defined Data Types.
Example: When Not To Include Referenced Add-On Instructions

and User-Defined Data Types
Suppose you have three add-on instructions that nest a fourth
add-on instruction inside them. And suppose you want to change
the nested add-on instruction. You’ll only have to change it once
if you don’t include it in the export file. Otherwise, you have to
change it in each instruction that uses it.
Here’s How To create an add-on instruction:

IMPORTANT: To meet IACET
CEU requirements and fully Activity: As your instructor demonstrates this procedure, follow
prepare certificate students for along in the associated job aid(s).
the final exam, you must
demonstrate all lesson objectives
using the proper
job aids.
Tip " You’ve already done the first part of this procedure when you
Use AOIL_1756R_DEM1.acd for planned the parameters for the instruction.
the rest of the demonstration.
The project already has the
workstation tags that you need.
AOILsb56r
Example Creating an Add-On Instruction
This example builds an add-on instruction that checks for jammed

product at the entry gate of a conveyor:
 The instruction turns on its Jammed bit if the photoeye at the gate
is on for too long.
 You’ll be able to set how long to wait before signaling a jam.
Enter the General Properties
AOILsb56r
You can copy this logic from the Enter the Definition Logic
Detect_Jam_Routine in the
Unscheduled Programs folder.
When you’re done,

the definition clickthe
and show thefinished
Help tab of Create the Parameters and Local Tags
instruction.
Input Parameter
DINT
Not Required
Not Visible
Input Parameter
BOOL Local Tag
Required
Output Parameter
BOOL
Not Required
Visible
AOILsb56r
Example Looking for Previously Developed Add-On Instructions
You can look for previously developed Add-On Instructions that may
fit your applications within the Rockwell website.
If“Faceplate/Add--On
you have time, show the VideoSets” to
Instruction Search the Sample Code Library
(samplecode.rockwellautomation.com)
the class.
Fill in the following:
Product Family
Product
Technologies
Example of Search Result
AOILsb56r

Add the example below to the project.  Use an add-on instruction in a routine
Then use the maintained switched on
the workstation to simulate a jam. Make  Monitor the values of an add-on instruction
sure to show the instruction’s logic as it  Monitor the logic of an add-on instruction
executes.
Example Using the Detect_Jam Instruction
Point out that you’re seeing the data for In this example, the Detect_Jam instruction continually checks for
this instance. This would be more jammed product at Gate_DI12.
difficult if this were a subroutine with
multiple calls to it. The data may be
constantly changing to reflect each call. If PE_DI12 = on for > 10 s, then Gate_DI12.Jammed = on.
If Gate_DI12.Jammed = on, then light DO2 = on.

IMPORTANT: To meet IACET  Export an add-on instruction
prepare certificate students for  Import an add-on instruction
the final exam, you mustobjectives
demonstrate all lesson Activity: As your instructor demonstrates these procedures, follow
using the proper job aids. along in the associated job aid(s).
Use the steps below to help guide
you during the demonstration:
1. Export the instruction.
2. Create a new project.
3. Import the instruction into the
project.
AOILsb56r
Exercise: Developing an Add-On Instruction in Ladder Diagram 15--21
Exercise: Developing an Add-On

Instruction in Ladder Diagram
Exercise A In this exercise, you will practice planning the parameters for an
add-on instruction that starts and stops a motor.
Context:
You want an instruction that starts and stops a single-speed motor

like a seal-in start/stop circuit. You want it to look like this:
Fault bit for the motor

Pushbutton that stops the motor
Pushbutton that starts the motor
Contact for the motor
You also want the option to do the following actions based on the
application:
 Jog the motor
 Set a fault if the auxiliary contact of the motor doesn’t open or
close within a specified time
Directions:
For each of the values in the following table, check whether you’ll
use it as an input parameter, output parameter, or local tag. Also
check if it will be required or visible. Use the context information to
help you decide.
AOILe56r
15--22 Exercise: Developing an Add-On Instruction in Ladder Diagram
Value Use? Required? Visible?

Input parameter
A. State of the pushbutton that starts the motor Output parameter
Local tag

Input parameter
B. State of the pushbutton that stops the motor Output parameter
Local tag
Input parameter
C. State of the pushbutton that jogs the motor. You want the option to use a
Output parameter
jog pushbutton or not use one based on the application.
Local tag
D. Bit that stores the combined status of the start and stop inputs. The Input parameter
instruction uses this bit and the jog input to determine whether to run the Output parameter
motor.
Local tag
Input parameter

E. Bit that signals the motor to start Output parameter
Local tag
F. State of the motor’s auxiliary contact. It signals the instruction that the Input parameter
motor is running. You want the option to use the auxiliary contact or not Output parameter
based on the application.
Local tag
G. Timeout value in milliseconds to wait for the auxiliary contact to open or
close. The instruction signals a fault if the contact doesn’t open or close Input parameter
within this time. You’ll use the auxiliary contact for some applications but Output parameter
not others. You also want to be able to set the timeout value based on the
Local tag
application.
H. Bit that tells the instruction that you’re using the auxiliary contact of the Input parameter
motor. You don’t want to have to set this bit. You’ll set up the instruction’s Output parameter
logic to control this bit based on whether or not there’s a timeout value. Local tag
Input parameter
I. Fault bit that shows you that the auxiliary contact timed out and the motor
Output parameter
didn’t start or stop as commanded
Local tag
Input parameter
J. Timer that creates a timeout for the auxiliary contact. You can easily write

code to move the timeout value from above into the timer’s preset value. Output parameter
Local tag
Input parameter
K. Bit that you’ll turn on to clear the fault bit. You want to option to use it or not. Output parameter
Local tag
AOILe56r
Exercise B In this exercise, you will practice deciding if an add-on instruction

needs an EnableInFalse routine.
Directions:
For the situations below, decide if you need an EnableInFalse routine

for the add-on instruction.
1. You plan to execute the instruction all the time and won’t use any
input conditions to disable it, like this:
Do you need an EnableInFalse routine?

- Yes
- No
2. The instruction controls a motor. You plan to execute the

instruction conditionally, like this:
Do you need an EnableInFalse routine?

- Yes
- No
AOILe56r
Exercise C In this exercise, you will practice creating and using an add-on
instruction.
Context:
In Exercise A, you made some decisions about the parameters for a

motor starter instruction. Now develop the instruction in
RSLogix 5000 software and verify that it works correctly.

Directions:
1. Open the AOIL_1756R_C1.acd project file.
2. Create the definition for the add-on instruction:
Property Value
Name Motor_Starter
Description Starts and stops a motor
Type Ladder diagram
Open Logic Routine Yes
Open Definition Yes
3. Open the Start_Stop_Motor_Routine in the unscheduled

programs folder:
4. Copy all the rungs from the Start_Stop_Motor_Routine and paste

them into the Logic routine of the Motor_Starter instruction.
AOILe56r
The Logic routine of the Motor_Starter instruction should look

like this:
5. Create these parameters and local tags for the Motor_Starter

instruction:
Name Usage Alias for Data type Description

Stop Input parameter BOOL Enter the tag that gives the stop command for the motor.
Start Input parameter BOOL Enter the tag that gives the start command for the motor.
Jog command for the motor. To jog the motor, turn on this bit.
Jog Input parameter BOOL
To stop the jog, turn off this bit.
Auxiliary contact of the motor. Make sure you set the
AuxContact Input parameter BOOL
FaultTime. Otherwise, this input doesn’t do anything.
ClearFault Input parameter BOOL To clear the fault of the motor, turn on this bit.
Output command to the motor starter. If on, the motor starts. If
Out Output parameter BOOL
off, the motor stops.
Fault Output parameter BOOL If on, the motor didn’t start or stop.
Enter the time (ms) to wait for the auxiliary contact to open or
Fault_Time Input parameter Fault_Timer.PRE DINT
close. The Fault bit turns on when that time is up.
RunCommand Local tag BOOL
CheckAuxContact Local tag BOOL
FaultTimer Local tag TIMER
AOILe56r
6. Click the Help tab of the instruction’s definition to see how the
instruction looks.
It should look like this:
7. Verify the routine and correct any errors.
8. Enter an instance of the Motor_Starter instruction into the

MainRoutine of the MainProgram:
Create this tag. Use the Motor_Starter
data type.
Assign these tags. They’re already

created for you.
Where this tag . . . Is tied to this workstation device . . . And simulates . . .

DI12_Stop Switch DI12 Stop pushbutton for the motor
DI0_Start Pushbutton DI0 Start pushbutton for the motor
DO1_Motor Light DO1 Motor
10. Download the project to the controller in slot 1 of your

workstation.
11. Put the controller in Run mode.
AOILe56r
12. Test the operation of Motor_Starter_01:
Do this . . . And check that this happens . . .

Nothing. This simulates the normally closed
A. Turn on DI12
position of the stop pushbutton.
B. Press DI0 DO1 turns on — the motor starts.
C. Turn off DI12 DO1 turns off — the motor stops.
Nothing. This simulates the normally closed
D. Turn on DI12
position of the stop pushbutton.
13. Add a rung of logic that lets Motor_Starter_01 read the state of
DI13_Aux_Contact. This simulates using the auxiliary contact of
the motor.
14. Add a rung of logic that turns on DO2_Fault if the fault bit of
Motor_Starter_01 turns on.
15. Set the Fault_Time parameter of Motor_Starter_01 to 1000 ms.
Make sure you set the Fault_Time for this

instance of the instruction. Don’t change the
definition.
16. Test that Motor_Starter_01 sets it’s fault bit if the auxiliary
contact of the motor doesn’t close:
Do this . . . And check that this happens . . .

A. Make sure DI12 is on. Nothing. This simulates the normally closed position of the stop pushbutton.
B. Press DI0 and then immediately turn on DI13. DO1 turns on — the motor starts.
C. Turn off DI12 and then immediately turn off DI13. DO1 turns off — the motor stops.
D. Turn on DI12. Nothing. This simulates the normally closed position of the stop pushbutton.
 DO1 turns on — the motor gets the command to start.
E. Press DI0 but leave DI13 turned off.  DO2 turns on — the motor didn’t start.
 DO1 turns back off — the instruction clears the start command.
F. Go to the properties of Motor_Starter_01 and clear
DO2 turns off.
the Fault bit.
Exercise D In this exercise, you will practice exporting and importing an add-on
instruction.
Context:
In Exercise C, you made made an add-on instruction that controls a

motor. Now export the instruction and import it into another project.

AOILe56r
Directions:
1. Export the Motor_Starter instruction.
2. Close the RSLogix project but leave RSLogix 5000 software

open.
3. Open the AOIL_1756R_D2.acd project file.
4. Import the Motor_Starter instruction.
AOILe56r
AOILe56r
Answers Exercise A
Value Use? Required? Visible? Reason

Input parameter It’s an input parameter because you pass this value
A. State of the into the instruction. Make it required so you can
pushbutton that Output parameter
starts the motor Local tag assign the tag
parameter. for the pushbutton
All required parametersdirectly to the
are also visible.
B. State of the into the instruction. Make it required so you can
pushbutton that Output parameter
stops the motor assign the tag for the pushbutton directly to the
Local tag parameter. All required parameters are also visible.
C. State of the into the instruction. It’s not required or visible
pushbutton that jogs Output parameter
the motor because you want the option to use it or not based
Local tag on the application.
D. Bit that stores the Input parameter This is a storage bit that the instruction’s logic sets
combined status of
Output parameter based on other parameters. Make it a local tag
the start and stop
since you don’t need to access it.
inputs. Local tag
Input parameter It’s an output parameter because the instruction
E. Bit that signals the returns this value based on input conditions. Make
Output parameter
motor to start it required so you can assign the tag for the motor
Local tag directly to the parameter.
F. State of the motor’s into the instruction. It’s not required or visible
auxiliary contact. Output parameter
because you want the option to use it or not based
Local tag on the application.
G. Timeout value in
milliseconds to wait Input parameter It’s an input parameter because you want to be
for the auxiliary Output parameter able to set the timeout value based on the
contact to open or application.
Local tag
close.
H. Bit that tells the
instruction that Input parameter
It’s an internal storage bit. There’s no need to
you’re using the Output parameter
auxiliary contact of access it.
Local tag
the motor.
Input parameter The instruction returns this value. It’s visible but not
I. Fault bit that shows required because you only want to see its state on
you that the auxiliary Output parameter
contact timed out the instruction. You don’t want to have to assign it
Local tag to a tag.
J. Timer that creates a Input parameter

timeout for the Output parameter There’s no need to access the timer.
auxiliary contact
Local tag
Input parameter
K. Bit that you’ll turn on You want to be able to see it, but you also don’t
to clear the fault bit Output parameter
want to have to use it.
Local tag
AOILe56r
Exercise B
1. No, you don’t need an EnableInFalse routine. The Logic routine

will execute all the time since the rung condition will always be
true.
2. Yes, you need the EnableInFalse routine if you use input
conditions to make the rung false. In that case, use the
EnableInFalse routine to reset outputs. Otherwise, the motor
could be left running even when the rung goes false.
Exercise C
2. The New Add-On Instruction dialog box should look like this:
AOILe56r
5. The Motor_Starter parameters should look like this:
The local tags of the Motor_Starter instruction should look like

this:
13. The logic must write the value of DI13_Aux_Contact to the

AuxContact parameter of Motor_Starter_01:
AOILe56r
14. The logic must read the value of Motor_Starter_01.Fault:
15. Open the properties for Motor_Starter_01 and enter 1000 into
Fault_Time:
Exercise D
4. The Add-On Instructions folder should look like this:
AOILe56r
AOILe56r
Lesson 16
Managing RSLogix 5000 Project
Files
What You Will Learn After completing this lesson, you should be able to manage
RSLogix 5000 project files by performing the following tasks:
 Export a .acd project file
 Import a .l5k text file
 Import a .l5x XML file
Export an RSLogix 5000 project file when you want to back it up or

save it for future use. Once you export it , you have to import it to
use it again.
Before You Begin File Storage
RSLogix 5000 projects can be stored using the following file

formats:
 .acd -- a standard file format
 .l5k -- an exported text file
 .l5x -- an exported XML file
Tip " In any format, the entire project, including tags, documentation,
ladder logic, etc. is contained in a single file.
FI2sb56r
16--2 Managing RSLogix 5000 Project Files
Add that some other software packages Exporting a .acd Project File
divide the components of a single
project into separate files. In either Using a Windowsr “save” procedure, a project is stored as a .acd
format, the entire project, including tags, file:
documentation, ladder logic, etc. is
contained in a single file.
Mention
Windowsthat saving
saving is just a Other
procedure. standard
standard windows procedures, such as Save Bottling.acd
copying files, can be found in an
appendix in the Procedures Guide.
Because RSLogix 5000 projects contain tag

names, the .acd files can be large.
Add that you should not open a project You cannot directly save a .acd file to a disk:
from a floppy disk or CD-ROM. By

default, the software
the file back willwhich
to the disk, attempt
willtonot
save If you attempt to do so, you will receive an
error message indicating insufficient space on
work.
the disk, regardless of the size of the project
When copying files from a CD-ROM, file.
they will be marked “Read-Only”. To
make the files useable, you must first  To save to a disk, a project file must be saved
copy them to the hard drive or network. to the hard drive and then copied to a disk.
Then you must clear the Read Only
check box in the file properties.
Note that in RSLogix 5000 software, Using the Windows “Save As” procedure, a .acd file can be exported
version 10, the export process was as a .l5k file, or text representation of the data for an entire project:
optimized to reduce the amount of time
required to perform a “Save As ”
operation. Programs
large quantity of tags that
with contain
commentsa
should have a significant decrease in the
time required for exporting.
Bottling.acd
Export Bottling.l5k - Export File
Note that the original .acd file is still (Save As) Original File Is Maintained
maintained as a separate file.
Note that the .l5k file is close in

size to a file that is compressed
Tip " A .l5k project file is much smaller than a .acd file.
using the WinZip utility. A .acd file can also be exported as a .l5x file, or XML-tagged code
Mention that when importing, if a file with of the data for an entire project:
the same name already exists, you will
overwrite it.
Mention that .l5x files can also be used

to import and export project components
Export Bottling.l5x - XML File
Bottling.acd
such as routines, programs, phases,
add-on instructions, and UDTs. (Save As) Original File Is Maintained
FI2sb56r
Managing RSLogix 5000 Project Files 16--3
Importing a .l5k Text File
To be used, a .l5k file must be imported. The original .l5k file will
remain and a separate .acd project file will be created:
Bottling.l5k Import Bottling.acd - Import File

(Open) (Original File Is Maintained)
Although you can change the extension of a

project file through Windows Explorer, this is not
recommended. To convert a file, use the
import/export functions.
The required Import/Export version for

RSLogix 5000 version 19 is 2.10. This version
can be modified and saved in older text files:
RSLogix 5000 Software Version
Import/Export Version
FI2sb56r
Importing a .l5x XML File
To be used, a .l5x file must be imported. The original .l5x file will
remain and a separate .acd project file will be created:
Bottling.l5x Import Bottling.acd - Import File

(Open) (Original File Is Maintained)
The .l5x file contains the project file in XML format, as shown in the
following graphic:
XML project files can only be imported into

projects created with RSLogix 5000 version 17 or
above.
If students are familiar with

add-on instructions, mention
Tip " The .l5x file allows users to manipulate the application source using
text editing tools; build tools to auto-generate projects; and extract or
that starting with v.16, add-on
instructions could be imported/exported merge code fragments to build new projects.
using .l5x files.
FI2sb56r
Managing RSLogix 5000 Project Files 16--5
Multiple Backup Files
By default, the software automatically saves incremental backup

Call out the benefits of this feature: project (.acd) files:
S Allows you to back out of unwanted  A backup file is created each time a “Save” operation is selected.
changes by moving to an earlier file  The quantity of files is configurable.
S Reduces likelihood of lost work from
disk or file corruption  The default is 3.
Tip " Files are stored in the same location as the original.
Note that the Compare tool must be

installed and launched separately from Compare Tool
the main software. It is available on the This tool allows you to perform project-to-project comparisons:
RSLogix 5000 software CD-ROM
(version 12 or later).  Project structure
 Tags and user-defined data types
Add that the report can be saved as an  Programming logic
HTML file or XML file.
 Data values (optional)
Tip " This tool can only be used for .acd files created in version 10 or later.
Tip " The report can be saved as an HTML file or XML file.
FI2sb56r
Here’s How To manage RSLogix 5000 project files by performing the following
tasks:
 Export a .acd project file
 Import a .l5k text file

- Directory where the export and import files can be found
- Files of Type drop down list
- How to examine files sizes using Windows Explorer
FI2sb56r
Exercise: Managing RSLogix 5000 Project Files 16--7
Exercise: Managing RSLogix 5000

Project Files
Exercise A In this exercise, you will practice managing RSLogix 5000 project
files.
Context:
You need to save and store a copy of an original HVAC file for
future reference.

Directions:
1. Open the FI2_1756r_A1.acd file.
2. Examine some of the file to become familiar with its contents.
3. Export the project file as a .l5k file.
4. Export the project as a .l5x file.
Tip " Save the project using the same name. Save it in the default project
directory.
5. Open Windowsr Explorer.
6. Locate the RSLogix 5000 software default project directory.
7. From the View drop-down list or using the toolbar icon shown
below, select Details so that the file sizes and dates of the projects
are displayed.
8. Under the Size column, compare the sizes of the FI2_1756R_A1

standard file (.acd) the text file (.l5k), and the XML file (.l5x).
FI2e56r
16--8 Exercise: Managing RSLogix 5000 Project Files
9. What are the file sizes?
10. From Windows Explorer, open the .l5k file.
11. In the text file, list the following elements:

A. RSLogix 5000 software version:
B. Import/Export version:
C. Major revision:
D. Minor revision:
E. Chassis size:
12. How would you find the elements listed in Step 11. using the .acd
file?
13. Which file would be easier for you to modify?
14. Close the file.

15. Open a new instance of RSLogix 5000 and import the .l5k file.
FI2e56r
Exercise: Managing RSLogix 5000 Project Files 16--9
16. Open the .l5x file to see how its structure is different from the .l5k
text file.
17. Open a new instance of RSLogix 5000 and import the .l5x file.
FI2e56r
16--10 Exercise: Managing RSLogix 5000 Project Files
Answers Exercise A
9. The approximate size of the .acd file is 400KB. The

approximate size of the .l5k file is 20KB. The approximate size
of the .l5x file is 65KB.
11. The text file uses this format:
RSLogix 5000 Software Version
Import/Export Version
Major Revision
Major Revision
Minor Revision
Chassis Size
12. Using the .acd file, you can find the RSLogix 5000 software
version from the Help menu. The Major revision, minor
revision, and chassis size information can be accessed using the
Controller Properties feature. The import/export version is not
viewable from the .acd file.
13. For some, RSLogix 5000 .acd files may be easier to modify
because of the graphical nature. For others, text files may be
easier to modify. XML files can offer more flexibility when
reusing code. Remember that text files and XML files cannot be
downloaded directly to a controller.
FI2e56r
Lesson 17
Allocating Connections in a
Logix5000 System
What You Will Learn After completing this lesson, you should be able to allocate
communications connections in a Logix5000 system by performing
the following actions:
 Determine the number of connections used by a Logix5000
controller
 Conserve the number of connections used by a Logix5000
controller
 Check connections in RSLogix 5000 with the Task Monitor tool

Depending on the size of your system, you may need to consider
how you allocate connections to stay within limits.
Before You Begin Connections
A connection is an established communications link between two

Clarify that a connection is a completed devices or components in a Logix5000 system. Connections may
communications link and not a physical take many forms, including the following:
connection on a network.
 Controller to I/O (local or remote)
 Controller to communications modules
 Produced tag controller to consumed tag controller
 Message source controller to message destination
Connection Limits
Have students find the manual Reference: Logix5000 Controllers Design Considerations,

and use it for the steps below. 1756--RM094
Give them a few minutes to look
through the tables.
1. Go to the Logix5000 Controller Resources chapter.
2. Go to the Controller Connections section.
3. Briefly read the tables on connection limits for controllers and

communication modules.
CO2sb56r
17--2 Allocating Connections in a Logix5000 System
Conserving Connections by Grouping Produced Data

To minimize the number of produced tags and therefore the number
of connections, data can be grouped into an array or a user-defined
structure and then produced.
The array or user-defined structure must be less

than 500 bytes.
When reviewing the table, note if the
producer used 250 produced and
consumed connections, there would be
no room for I/O modules. Example: Connection Requirements for Tags vs. an Array
? What is an array? Producing 5 individual tags for two consumers each requires 15
connections, as shown in the following table:
Answer: A numerically indexed
sequence of tags, for example,
Size[3,5]. Source Tags Produced Tags Connections
Height (Dint) Height 3 (1 tag plus 2 consumers)
What is a user-defined structure? Width (Dint) Width 3

?
Answer: A data type (similar to a timer)
Weight (Real) Weight 3
made of members different data types. W_Flag (Dint) W_Flag 3
The user-defined data type is also L_Flag (Dint) L_Flag 3
referred to as a user-defined structure.
15 connections
? Could you make an array within this Producing 1 user-defined data type requires only 3 connections,
data type? as shown in the following table:
Answer: Yes. You can embed a
one-dimensional array of certain data Load_Info User-Defined Data Type
types (such as Dint) within a Source Tags Produced Tag Connections
user-defined data type. Here you could Height (Dint)
make
Height,anWidth,
array W_Flag,
of four Dints
and for the
L_Flag. Width (Dint) Load_Info (user-defined
Weight (Real) data type made of source 3 (1 tag plus 2 consumers)
W_Flag (Dint) tags)
L_Flag (Dint)
3 connections
CO2sb56r
Allocating Connections in a Logix5000 System 17--3
Message Connections
Note that the cache bit is set or cleared Some types of messages always require a connection. Other
in the Message Configuration dialog messages (such as a CIP messages) maintain the connection based on
box, which is accessed through the
ellipses button in the MSG instruction. the configuration of the cache bit:
 Clear the cache bit for infrequent messages. This closes the
connection when not in use and frees it for other operations.
Note that opening a new connection for
each message execution increases  Set the cache bit for continuous messages.
execution time.
Continuous
Connection
Here’s How To determine the number of connections used by a Logix5000

IMPORTANT: To meet IACET controller.
prepare certificate students for Reference: Logix5000 Controllers Design Considerations,
the final exam, you must
1756--RM094
demonstrate all lesson
using objectives
the proper job aids.
1. Go to the Determine Total Connection Requirements section.
To demonstrate, tally the connections for 2. Briefly read the tables for local and remote connection tallies.
an example system this way:
1. Describe a device and its quantity 3. Use the tables to tally the connections for an example system
and have the students determine the your instructor gives you.
connection type and total connection
from the tables.
2. Continue giving them examples of
devices and quantities until you’ve
tallied the connections for your
example system.
3. total
Countconnections
the tallies tofrodetermine the
the system.
CO2sb56r
17--4 Allocating Connections in a Logix5000 System
Here’s How To check connections in RSLogix 5000 with the Task Monitor tool.
Use the steps below to help guide you
during the demonstration:
1. From the tools menu select
Logix5000 Task Monitor.
2. Under Communications select
Monitor.
3. From the RSWho screen select
the processor you want to monitor.
4. From the Logix5000 task Monitor
Screen select the Networking Tab.
CO2sb56r
Exercise: Allocating Connections in a Logix5000 System 17--5
Exercise: Allocating Connections

in a Logix5000 System
Exercise A In this group exercise, you will practice allocating connections used
by a Logix5000 controller.
You have just completed a basic project. You now need to determine
the number of connections used by the controller in slot 1.
Refer to the CO2_1756r_A1.acd file and the following key points:

 There are 4 local modules and 1 remote I/O module.
 There is 1 local and 1 remote ControlNet communication module.
 There are 2 produced tags:
-- Initialize System (produced for 1 local and 1 remote

controller)
-- Station_Data_For_Quality (produced for 1 local controller)
 There is 1 consumed tag: Stations_Off_Quality.
 There are 2 messages (1 Data Table Read and 1 CIP Generic).
Directions:
1. Tally the connections for the controller.
2. Producing 6 individuals tags for two consumers each requires 18

connections. How could the number of connections be reduced to
3?
3. Using direct connections, 2 connections are used to communicate

with 2 remote 1756 digital I/O modules and 1 remote ControlNet
communication module. If the communication format was
changed to Rack optimization, how many connections would be
established?
CO2e56r
17--6 Exercise: Allocating Connections in a Logix5000 System
Answers Exercise A
1. Your answer should be similar to the following example:
Connections per Total

Connection Type Device Quantity
Module Connections
Local I/O module (direct connections) 4 1 4
SERCOS Motion module 0 3 0
Local ControlNet communication module 1 0 0
Local EtherNet/IP communication module 0 0 0
Local DeviceNet communication module 0 2 0
Local DH+/Remote I/O communication module 0 1 0
Local DH--485 communication module 0 1 0
RSLogix 5000 software access to controller 1 1 1
Remote ControlNet communication module 1 0 0
Remote EtherNet/IP communication module 0 0 0
Other remote communication adapter 0 1 0
Remote I/O modules (direct connections) 1 1 1
Produced tags -- -- --
Produced tag and first consumer 2 2 4
Each additional consumer 1 1 1
Consumed tags 1 1 1
Connected message (CIP Data Table Read/Write and DH+) 2 1 2
Block-transfer message 0 1 0
14
2. Grouping the data into an array or user-defined data type would

reduce the number of connections to 3 (1 tag plus 2 consumers).
3. Rack optimization would consolidate the connections into a

single connection. Data would be sent at one rate specified by
the ControlNet module.
CO2e56r
Lesson 18
Integrated Practice — Developing
 Modify the default task, program, and routine
 Add a local 1756-I/O module to an I/O configuration
 Create a tag in the Edit Tags list
 Define alias tags
 Draft simple ladder logic
 Enter and edit ladder logic components
 Verify a project
 Select and change a controller’s operating mode
 Download a project to a Logix5000t controller
 Create an event task
 Copy and reuse ladder components
 Modify a communications path
 Create a communications path
 Configure a controller to produce and consume data
INPsb56r
18--2 Integrated Practice — Developing an RSLogix 5000 Project
INPsb56r
Exercise: Integrated Practice — Developing an RSLogix 5000 Project 18--3
Exercise: Integrated Practice —

Developing an RSLogix 5000
Project
Exercise A In this exercise, you will practice skills used in developing an

Context:
You have completed and tested the basic project for Line_A. Now
you have been asked to duplicate this logic for Line_B.

Directions:
1. Open the INP_1756r_A1.acd file.
Tip " If you are using a ControlNet network, open the INP_1756r_A3.acd
file.
2. Add an analog output module to slot 7 of the I/O configuration.

The following table outlines the parameters for the module:
Alarms Limits
Scaling
Catalog High High High
Channel High Signal High Eng.
Number High Clamp
Low Low
Low Signal Low Eng.
Low Low Clamp
--
10.0 10.0 10
--
0
--
0.0 0.0 --10
OF6VI --
(0--10V) --
10.0 10.0 10
--
1
--
0.0 0.0 -- --10
3. Modify the configuration of the local and remote communication

modules within the I/O Configuration to match the configuration
of your workstations.
4. From within the tag editor of the Line_A program, create a
program-scoped tag named Meter. This tag should be an alias for
the channel 0 analog output data.
INPe56r
18--4 Exercise: Integrated Practice — Developing an RSLogix 5000 Project
5. Draft ladder logic in the Process_Order routine that will move

the accumulated value of the Order_Counter tag into the new
Meter tag.
6. Edit the XIO instruction in rung 3 of the Process_Order routine

and change it to an XIC instruction.
7. Create a Line_B program.
8. Copy the program-scoped tags from the Line_A program and

paste them into the Line_B program.
9. Copy the routines from the Line_A program and paste them into
the Line_B program.
10. Configure the MainRoutine as the main routine in the Line_B
program.
11. For these slot 1 program-scoped tags, re-assign the alias
information to the correct I/O points based on the following chart:

LineA I/O Point LineB I/O Point
Routine Name Tag Name
(Line_A Program) (Line_B Program)
Read_Order Read_Order Local:2:I.Data.0 Local:2:I.Data.4
Process_Order Apply_Paint Local:0:O.Data.3 Local: 0:O.Data.4
Process_Order Meter Local:7.O.Ch0Data Local:7.O.Ch1Data
Process_Order Order_In_Progress Local:0:O.Data.0 Local:0:O.Data.1
Process_Order Process_Order Local:2:I.Data.1 Local:2:I.Data.5
Process_Order Shrink_Wrap Local:4.O.Data.6 Local: 4.O.Data.7
INPe56r
Tip " Devices on the standard workstation are arranged and wired in the
following manner:
AO0 AI0
DI0 DI1 DI2
DO0 DO3 DO6
DI4 DI5 DI6 Analog Meter

Analog Input
DO1 DO4 DO7
AO1 AI1
Analog Meter Analog Input
Label Description Slot I/O Tag I/O Tag for Alternate Wiring
Digital Inputs DI4 Digital Input 4 2 Local:2:I.Data.4

DI5 Digital Input 5 2 Local:2:I.Data.5
DO1 Digital Output 1 0 Local:0:O.Data.1
Digital Outputs DO4 Digital Output 4 0 Local:0:O.Data.4
DO7 Digital Output 7 4 Local:4:O.Data.7
Analog Outputs AO1 Analog Output 1 7 Local:7:O.Ch1Data
Tip " This chart lists controller-scoped base tags (no alias information) in
the slot 1 controller:
Program Name Routine Name Tag Name
Line_A Read_Order MSG_Read_LineA

Line_B Read_Order MSG_Read_LineB
Line_A Read_Order Order_QuantityA
Line_B Read_Order Order_QuantityB
12. Cross-reference the MSG_Read_LineA tag and go to the rung

within the Line_B program that uses this tag.
13. Modify the message instruction on the rung you identified in the
previous step by performing the following:
 Configure the control tag MSG_Read_LineB as the message
control tag for this instruction.
 Configure the message type to be a CIP Data Table Read.
 Configure Order_QuantityB as the Source and Destination
Element for the message instruction.
 Configure the communication path to point to the controller in
slot 3 of the remote workstation.
14. Within the same rung as the message instruction, make the
Order_QuantityB tag the source tag for the move instruction.
INPe56r
15. Within the same rung as the message instruction, change the
operand of the XIC instruction that utilizes the
MSG_Read_LineA.DN tag to the MSG_Read_LineB.DN tag.
16. Cross-reference the MSG_Read_LineA tag and go to the rung

within the Line_A program that utilizes this tag.
17. Modify the communications path of the MSG_Read_LineA
message control tag to point to the remote controller in slot 3
18. Verify your changes and correct any errors.

Tip " If you are using ControlNet, you may need to reschedule the
network.
21. Open another instance of RSLogix 5000 software.

22. Import the INP_1756r_A2.l5k file.
23. Create the Order_QuantityB tag and make it an alias for AI1.
24. Save your work and download the INP_1756r_A2.acd file to the
controller in slot 3 of the remote workstation.
25. To test your work, verify that the Line_A program of the project
functions as follows:
F A
B D
C, H E G Remote
Workstation
A. Set the potentiometer in the remote workstation to the desired

order quantity (the range is 0 to 10).
B. Push the Read Order button (DI0) of the local workstation.
C. The Order_In_Progress (DO0) light in the local workstation
should now be on.
D. Push the Process_Order button (DI1) in the local
workstation.
INPe56r
E. The Apply_Paint light (DO3) should go on and off the

number of times you have requested from the
Order_Quantity potentiometer in the remote workstation.
F. Each time a part is painted, the Meter should increment.
G. When all parts have been painted, the Shrink_Wrap light

(DO6) should go on for two seconds.
H. Once the Shrink_Wrap has been applied, the
Order_In_Progress (DO0) light should turn off.
26. To test your work, verify that the Line_B program of the project
functions as follows:
B
C, H D
E G Analog Meter Analog Input
F A
Remote
Workstation
A. Set the potentiometer in the remote workstation to the desired

order quantity (the range is 0 to 10).
B. With the controller in slot 3 of the remote workstation pulled
out of the chassis, push the Read_Order button (DI4) of the
local workstation. Explain why the Order_In_Progress light
in the local workstation does not go on:
C. Now insert the controller back into slot 3 and push the
Read_Order button again. The Order_In_Progress light
should now be on.
Tip " You may need to re-download the INP_1756r_A2.acd file to the
controller in slot 3 if the project was lost while the controller was
removed. If this is the case, press Read_Order button (DI4) again.
D. Push the Process_Order button (DI5).

INPe56r
E. The Apply_Paint light should go on and off the number of

times you have requested from the Order_Quantity
potentiometer in the remote workstation.
F. Each time a part is painted, the Meter should increment.
G. When all parts have been painted, the Shrink_Wrap light

should go on for two seconds.
H. Once the Shrink_Wrap has been applied, the
Order_In_Progress (DO0) light should turn off.
27. The shrink wrap roll must be measured continuously so that if it
is low, it can be re-filled immediately. A photoeye (at DI8) is in
place to detect sufficient width on the roll. If this sensor goes on,
the event task must be triggered. Configure this new event task
named Refill_Shrink_Wrap in the slot 1 controller.
Tip " Continue using the existing INP_1756r_A1.acd or INP_1756r_A3

file.
28. When the event task executes, it must increment a tag that tracks
the number of times the event task has executed. This tag is called
Event_Task_Count . Program the necessary logic for this in the
MainRoutine inside the MainProgram of the Event task you
created.
29. Produce the Event_Task_Count tag from the slot 1 controller,
and consume it from the slot 3 controller.
INPe56r
INPe56r
Answers Exercise A
2. The main configuration screens for the analog module are

shown in the following graphics:
(Continued)
INPe56r
INPe56r
4. The tag properties for Meter should look like the following

example:
5. The following ladder logic was entered to move the

accumulator value into the Meter tag:
INPe56r
6. The rung should look similar to the following example:
9. The Tasks folder within the Controller Organizer should like

similar to the example below:
10. MainRoutine should now be the main routine for the Line_B

program:
INPe56r
11. Your Line_B Program Tags editor should now look similar to

the following:
12. You should find the MSG_Read_LineA tag located on rung 0

of the Read_Order routine within the Line_B program:
13. Your message instruction should now have MSG_Read_LineB

as the message control tag:
(Continued)
INPe56r
Your message instruction configuration should look similar to

the following:
INPe56r
15. The rung with the message instruction in the Line_B program

should be configured similar to the following:
17. Your MSG_Read_LineA tag should be configured as follows:
23. Your Order_QuantityB tag should be configured similar to the

following:
INPe56r
26.
B. The Order_In_Progress light will not come on if the
controller in slot 3 is removed because the logic tests for the
done bit of a message instruction to that controller in slot 3.
If the controller is not there, the done bit will not go high.
27. The following examples show the event task configuration and
the Shrink_Wrap_Low tag alias information:
28. Your ladder logic should be similar to the example below:
INPe56r
29. The following example shows the produced tag in the slot 1
controller:
The following example shows the slot 3 I/O configuration for

an EtherNet/IP network:
(Continued)
INPe56r
The following example shows the slot 3 I/O configuration for a

ControlNet network:
Tip " Your ControlNet node numbers may vary based on network
configuration.
The following example shows the consumed tag in the slot 3

controller:
INPe56r
INPe56r
Optional Lesson 19
Configuring Logix5000 Controllers
to Share Data over a ControlNet
Network
Important: If this lesson is part of a  Add a ControlNet communication module to an I/O configuration
national school and you are using
EtherNet/IP for remote data sharing, this  Add a controller to an I/O configuration
lesson can be skipped.  Schedule a new ControlNet network
Stress that ControlNet and EtherNet/IP
are two Logix5000 networks designed to
share data between multiple controllers
in remote chassis or between a When You Will Do This
controller and I/O in remote chassis.
Use the procedures in this lesson when you have to pass interlock
Note that 1756-remote
introduced in a separateI/O will be
lesson. data between controllers over an ControlNet network.
Before You Begin Key Terms
The following terms are defined as they relate to a ControlNet

network in a Logix5000 system:
Remind students that the ControlNet Determinism: The ability to reliably predict when data will be
network is the technology of the delivered.
backplane in a network.
Repeatability: Transfer times that are constant and unaffected by
devices connecting to or leaving the network.
Producer/Consumer Model: A communications network model in

In the graphic, review the devices on the which nodes on a network can simultaneously receive the same data
ControlNet network. Cite specific from a single source.
examples.
ControlNet Network: A communications network used for
transmitting time-critical and non-time critical data on the same link.
ControlNet Nodes
Note that the 1784-PCICS

for computers card is used
with faster processing The physical ControlNet network in a Logix5000 system can contain
speeds. the following nodes:
If you do not have these cards available  A 1784-KTCX15 or 1784-PCIC(S) card to access the network
but there is a Logix5000 system on the from a desktop computer
network with an EtherNet/IP card, you
can use EtherNet/IP as a bridge to the  A 1784-PCC (PCMCIA) card to access the network from a laptop
ControlNet network when working with computer
RSNetWorx for ControlNet software.
 A configured ControlNet module in a Logix5000 chassis
 ControlNet-compatible devices
CN2sb56r
19--2 Configuring Logix5000 Controllers to Share Data over a ControlNet Network
Common nodes that are connected to a ControlNet network using a

cable system are shown in the following graphic:
Computer
ControlLogix System ControlLogix System
ControlNet Network
VersaView
Operator Interface PLC-5/40C Controller CompactLogix
System
ControlLogix System
Over a ControlNet network, a Logix5000 controller can share data

with the following controllers:
 Another Logix5000 controller (remote)
 A CompactLogix controller
 A PLC-5C processor
 An SLC 500 processor
There can be up to 99 nodes on a ControlNet network. Nodes on a
ControlNet network must meet the following requirements:
 Nodes must be in the range of 1 to 99.
 Node numbers cannot be duplicated.
 Node zero is invalid.
 Lowest keeper-capable node number (the keeper) in the system
receives information from RSNetWorx for ControlNet software:
-- The keeper is not a master.
-- The keeper only grants access to the network.
-- The keeper maintains the ControlNet schedule.
CN2sb56r
Configuring Logix5000 Controllers to Share Data over a ControlNet Network 19--3
Cable System
Nodes on the ControlNet network must be connected using a
Point out each component of the ControlNet cable system. The following graphic is an example of a
ControlNet cable system connecting ControlNet cable system and some of its components:
workstations in the classroom. If you
have a repeater, show it to the students.
Trunk Cable
Segment Section Connectors
Tap
Terminator
Repeater
Node
Note that the components of the

ControlNet network are carefully
selected by the network designers to This cable system contains the following basic components:
accommodate the current (and future)
needs of the network. Exceeding the  Taps with no minimum spacing requirements
length of cable or the number of taps  Cable connectors
may cause degradation of the signal and
eventual failure.  Trunk cable:
-- RG-6 coax cable or special-use cable
Note that repeaters
the signals, do notthem
they recreate just amplify
(and -- 1000 m with 2 devices and 250 m with 48 devices
therefore add some latency). Repeaters
-- Each tap subtracts 16.3 m from allowable segment length
can be purchased to create -- Flexible topology including bus, tree, and/or star
coax-to-coax, coax-to-fiber, or
fiber-to-fiber links.  Terminators
 Repeaters, depending on the design
Up to 99 nodes can be connected on a ControlNet

network. 48 nodes can exist on one segment; after
48, a repeater must be used.
Note that ControlNet is a proven Cable system design and installation is extremely
network. Most problems occur in the important. Most complications with ControlNet
installation or configuration.
networks can be linked to the network installation.
Tip " The cable system is used for permanent nodes. An RJ45 port is
Show the front of a ControlNet available to connect a computer to the ControlNet module without
module. Point out the channel A and B breaking a connection or adding a new node to the cable system.
connectors and the RJ45 port.
CN2sb56r
Tip " For more information on the ControlNet cabling system, refer to the
ControlNet Coax Cable System Planning and Installation Manual.
Note that this document is part of the
Logix5000 Documentation Reference
Guide.
Network Services
The ControlNet network’s function is to transmit the following two

types of information on the same link:
 Scheduled (time-critical data)
 Unscheduled (non-time critical data)
Scheduled Service
Data that is sent across a network on a regular basis is transmitted as
scheduled data. This data has the following characteristics:
?What type of data would be  Is time critical, such as I/O status and control interlocking data
considered time critical for your 
application? Has top priority in information exchange
 Occurs in the same time frame during every data transmission
interval
 Can be any of the following:
-- Data from an I/O module
-- Peer-to-peer interlocking data of controllers
Tip " Components that have an associated RPI (Requested Packet Interval)
send data as scheduled data.
To control I/O or produce and consume tags in a

Logix5000 application, scheduled data is required.
Unscheduled Service
Stress that scheduled data, such as Non-deterministic data that is not time critical is transmitted as
control and I/O data, is given highest unscheduled data. This type of data has the following characteristics:
priority on the ControlNet network. Other
information, such as programming or  Transmits after all scheduled data has been sent
upload and download operations, does
not interfere with the transport of control  Can be any of the following:
and I/O data. -- Connection establishment
-- Ladder-initiated, peer-to-peer messaging data (using a
Message instruction)
-- Programming data (uploads and downloads)
CN2sb56r
Information Exchange on the ControlNet Network
Note that this is an overview of the data The following graphic shows the transfer of information over the
transfer process. Details will be given ControlNet network using the Producer/Consumer model:
later in the lesson.
Establish Communication Close

Clarify that this is a ControlNet data Connection Connection
exchange not a message (MSG)
instruction.
A producer sends a If the node needs The connection is
message to the target the data, messages closed.
consumer by using a are then consumed.
network address.
The following statements describe information exchange on the

ControlNet network:

Note that source
CID. The the node number
and is part of the
destination Data sent by a producer will contain a numeric identifier called a
CID (Connection ID):
information is encoded in the CID.
-- This ID is created automatically when a ControlNet node is
connected to the network.
Chalk Talk: To help students learn the  Nodes that have been configured to recognize a particular CID
many acronyms in this lesson, keep a consume the data.
running list on the end of the board.
After learning a new acronym, have the  Access to the network is controlled by a time-slice algorithm.
students supply short descriptions to
define the new acronym.
Network Parameters
Note that thistosection

introduction serves asEntering
the parameters. an To schedule the network for information exchange, values for the
following network parameters must be selected:
these parameters using RSNetWorx for
ControlNet software will be presented  NUT
 SMAX (Scheduled Maximum node)
 UMAX (Unscheduled Maximum node)
 Media Redundancy
NUT (Network Update Time)

Add the term NUT to the acronym list on The NUT is the repeatable base time at which the network transmits
the board. Ask the students for a short data (scheduled, unscheduled, and maintenance data). The NUT has
definition.
the following characteristics:
Note that the NUT represents the  A configuration of 2 to 100 milliseconds is possible for the NUT.
aspects of determinism and repeatability

that set the ControlNet network apart  The value of the NUT includes peer-to-peer, digital, and analog
from other networks. data.
Data cannot be transferred faster than the NUT.

Add the term NUI to the acronym list on
the board. Ask the students
for a short definition.
CN2sb56r
Tip " One occurrence of the NUT is referred to as a NUI (Network Update
Interval).
Example: NUT
The priority of data transfer is shown in the following graphic:
NUT
? What will happen during the second
NUI shown? Scheduled Unscheduled Maintenance Update
Operations Operations (Guardband)
Answer: Data will be transmitted again
in priority order.
Note that the maintenance update

includes diagnostics and
communications.
... ...
With the given guidelines in mind, the graphic illustrates that:

 Scheduled data is transmitted first, followed by unscheduled
data and then maintenance data.
 When the NUT has occurred, the transmissions start over.
SMAX (Scheduled Maximum Node)

Add the term SMAX to the acronym list The SMAX is the maximum node number (1 to 99) that can transmit
on the board. Ask the students for a and receive data during the scheduled portion of the NUT. Keep in
short definition.
mind the following guidelines when determining the SMAX value:
Mention that it is inefficient to schedule a  Nodes at or below the maximum scheduled node transmit every
computer. Instead, assign computers NUT in the same sequential order (i.e., 1, 2, 3, then 1, 2, 3 . . .).
your highest node numbers.
 All nodes sending time-critical data should be at or below the
SMAX.
 Each node falling under SMAX can transmit up to 510 bytes of
data during its turn:
-- More than 500 bytes can be sent by one node. However, only
500 bytes can be transferred at one slot time.
-- The bandwidth in this portion of the NUT is reserved and
State that for an efficient network, node configured in advance to support real-time data transfer.
numbers should be assigned
sequentially starting at 1. The maximum
-- The boundary for the scheduled portion of the NUT will move
scheduled node should be set to the depending on the use of bandwidth.
highest number node that will need to
transmit scheduled data.  Slot time is the calculated time a node will wait for a missing
address before taking its turn to transmit:
-- Slot time is based on the physical attributes of the network
including the cable length and the number of repeaters.
CN2sb56r
Example: SMAX
Here is the order of scheduled data transfer:
NUT
1 1 1
2 2
3 3 3
4...n 4...n 4...n
... ...
SMAX Slot Time

 The first network update interval (NUI) shows nodes (numbers)
? Ask students to why it is inefficient falling below SMAX sending scheduled messages.
not to assign nodes sequentially?  The second NUI shows the nodes below SMAX sending
Answer: Because nodes will wait for messages again starting over from the first scheduled node to
other nodes to transmit. E.g., node five SMAX.
will wait the entire slot times for nodes
one to four to transmit even if they are  The third NUI shows a node (2) missing from the network.
not assigned. Therefore, node 3 will wait one time slot before it transmits data.
UMAX (Unscheduled Maximum Node)
The UMAX
transmit and is the maximum
receive ControlNet
unscheduled nodeinnumber
data. Keep that
mind the can
following
Add the term UMAX to the acronym list guidelines when determining the value of the UMAX:
on the board. Ask the students for a
short definition.  The time remaining after the scheduled and maintenance portions
of the NUT is allotted for unscheduled operations.
The right to transmit first in the unscheduled portion of the NUT
? What type of data might be included 
rotates one node number per NUI (i.e., 1, 2, 3, then 2, 3, 4 . . .).

in the unscheduled portion of the NUT?
 The unscheduled portion of the NUT may not provide enough
Answer: Unscheduled data can include
connection establishment, peer-to-peer time for every node to transmit data during every NUT.
messaging data, programming, and  A node will repeat transmission if there is time left in the NUT.
ladder-initiated communications.
Note that the 1784-KTCX15 driver node Nodes above the UMAX cannot communicate on
number default is set high, at 99. the network. Leave room for laptops to attach
Suggest that students change this to a
lower node number. Remind students using the RJ45 port. The added slot time will only
that as with all node numbers that affect the unscheduled service.
transmit and receive unscheduled data,
the driver/computer node number must
fall under the UMAX.
CN2sb56r
Time-critical data must not be included in the

unscheduled portion of the NUT, as it may not
have the opportunity to be sent every NUT.
Example: UMAX
Here is the rotating order of unscheduled data transfer:
? If UMAX was reached in the second
NUI, which node would transmit NUT
unscheduled data first in the
third NUI?
Answer: Node 1.
In the graphic, point out that
if time remains after the 7 8 9 1
UMAX is reached, the 8 9 10 2
remaining time starts over 9 10 11 3
with node one (scheduled 11 12
nodes). .. . ...
UMAX

Point out in the graphic that node 7  The opportunity to transmit is passed on a rotating basis.
transmits first in the first NUI, node 8
transmits first in the second NUI, and  In the third NUI, UMAX is reached. The remaining
node 9 transmits first in the third NUI. unscheduled time is now available to additional nodes on a
sequential basis starting with node 1.
Note that to send data over 500 bytes in An unscheduled message can transmit only 500
chunks, frame numbers are assigned to bytes per slot time. If the message is more than
the data.
500 bytes, the data will resume transmission on its
next turn.
The same node can transmit both scheduled and

unscheduled data. For example, the controller
might produce a tag (scheduled) and send a
message (unscheduled).
Media Redundancy
The network must be configured for one of the following media
redundancy options:
Add that all nodes on a network must be  A only, for one cable system using channel A
the same. That is, one node cannot be
set for channel A and another node set  B only, for one cable system using channel B
for channel B.  A and B, for redundant media
CN2sb56r
To ensure optimization of data transfer, an

accurate representation of the media used on the
network should be defined in RSNetWorx for
ControlNet software.
Update Intervals
The configured or requested node transmit time may be different

than the actual transmit time, as described in the following intervals:
 RPI (Requested Packet Interval)
 API (Actual Packet Interval)
RPI (Requested Packet Interval)

Add the term RPI to the acronym list on The RPI is a user-specified rate that is supplied when an I/O module
the board. Ask the students for a short
definition. or ControlNet module is configured. The RPI defines how long the
module will wait before multicasting its data.
When determining the value of the RPI to enter in the I/O

configuration, note the following:
Clarify that the RPI tells the modules  Each node may have different requirements for sending data
when to multicast its data. within the NUT.
 It is inefficient to send all data at the same rate.
 A node can support more than one rate depending on the data
being sent.
 RPI must be greater than or equal to the NUT.
API (Actual Packet Interval)

Add the term API to the acronym list on The API is the actual resulting interval. It can be described as
the white board. Ask the students for a follows:
short definition.
 This rate is based on the NUT and is less than or equal to the RPI.
 This rate supports values that are binary multiples (1, 2, 4, 8, 16,
32, 64, 128) of the NUT.
 ControlNet networks will always meet or beat the RPI:
-- If the RPI is 20 ms and the nut is 8 ms, the API will be 16 ms
(faster) because it cannot release at 20 ms.
CN2sb56r
Example: RPI and API

After reviewing the graphic and the The requested transmit time versus the actual transmit time is
corresponding statements, ask the illustrated in the following graphic:
students to determine the API for the
following RPI rates: NUT = 2 ms
1. 100 ms Answer: 64 ms RPI for discrete data = 10 ms API for discrete data = 8 ms
2. 31 ms Answer: 16 ms
2 ms 2 ms 2 ms 2 ms 2 ms
3. 2 ms Answer: 2 ms
After reviewing RPI and API, test the

students’ understanding of the first half Data Data
of the lesson, including the following key
concepts:
Interval 1 Interval 2 Interval 3 Interval 4 Interval 5
S Producer/Consumer model
S NUT, SMAX, UMAX, RPI, and API
Having a good understanding of the The example illustrates the following points:
parameters of the ControlNet network is

required
interfacestoand
begin examining steps.
configuration the software Discrete data generates
has an RPIanofAPI
ten milliseconds.
 The software of eight milliseconds (eight is
Break: Note that the introduction of the the closest binary multiple that is less than ten).
ControlNet network concepts ends here.  The data is sent every four NUTs.
This is a good place to take a short
break if necessary.
Configuration Overview and Software Interfaces
Note that this section is a general To schedule the ControlNet network in order to share data, it is
introduction to the flow of configuration necessary to complete the following procedures:
procedures. The step-by-step details
and software demonstrations will be 1. Create the required produced tag.
presented in the Here’s How section. If
this
add lesson is partI/O
that remote of will
a national school,in
be discussed 2. In the controller that is consuming the data, perform the following
actions:
a different lesson.
Encourage students to ask any A. Add the local ControlNet module to the I/O configuration.
remaining questions from the
Configuring a Logix5000 Controller to B. Add the remote ControlNet module to the I/O configuration.
Produce and Consume Data lesson.
C. Add the producing controller to the I/O configuration.
Note that the connection will be made
through a ControlNet or Ethernet D. Create the required consumed tags.
network.
3. Schedule the ControlNet network.
CN2sb56r
Note that the controller was also added Adding a ControlNet Module and Controller to an I/O
to the project to share data when Configuration
producing and consuming tags across
the backplane. However, the controller is The following graphic is an example of a remote ControlNet module
now added under the remote CNB.
and remote controller added to an I/O configuration in
RSLogix 5000 software:
In the graphic, point out that the remote
module is node 2.
Add that it is not necessary or even
possible to add the controller running the
project to the configuration.
Local ControlNet Module
Remote ControlNet Module

Remote (Producing) Controller

Note that the produced and consumed Data that is shared over a ControlNet network must be transferred
tags are created just as they were using produced tags and received (stored) in consumed tags.
created for transfers over the backplane.
As with I/O modules, when configuring consumed

tags, select an RPI that is greater than the NUT.
Scheduling a New ControlNet Network

RSNetWorx for ControlNet software schedules a network and
connects the local controller to any controllers or I/O modules in a
remote chassis by performing the following actions:
 Create a graphical representation of your network configuration
and configure the parameters that define your network.
 Analyze all of the intended traffic for the network and then
determine if the requested amount of traffic is possible.
 Display the current percentage of capacity as well as the
percentage of capacity that added traffic will cause:
-- The user can then decide whether to adjust the requested
traffic or schedule it.
 Download to network.
CN2sb56r
To read the connected nodes on the network and build a network

Point out that the procedure for
scheduling a ControlNet network is diagram, an online connection must be established using RSNetWorx
detailed in the Procedures Guide. Note for ControlNet software:
that the steps will be demonstrated in
the Here’s How section.
Online Option
Enable Edits
Option Online Bandwidth
Percentages
Network
Diagram
The online Average Scheduled Bandwidth

percentage should not exceed 50% or 60%.
CN2sb56r
Using the values in the Pending side of After going online, the NUT, SMAX, UMAX, and redundancy
the graphic, review the following terms: parameters are configured in RSNetWorx for ControlNet software:
S NUT -- Data updates every 5 ms.
S SMAX -- Up to 9 controllers or other
scheduled devices.
S UMAX -- Up to 24 programming or
other nonscheduled devices.
Current Online Pending

Values Changes
Note that the ControlNet scheduling Each time an additional device is added to a
information is saved in a .xc scheduled network or an RPI value is changed, the
configuration file.
ControlNet network must be rescheduled.
A controller must be in Program mode to be

scheduled.
? What other main function Tip " RSNetWorx software communicates with the controller through
requires RSLinx Classic software? RSLinx Classic software.
Answer: Drivers are configured in
RSLinx Classic software.
CN2sb56r
Here’s How To configure a local Logix5000 controller to share data with a

remote Logix5000 controller over a ControlNet network by
performing the following tasks:
 Add a ControlNet module to an I/O configuration
 Schedule a new ControlNet network
Be sure to use the Pay attention to these critical aspects of the demonstration:
CCP143_1756R_DEM6.acd file and
CCP143_1756R_DEM7.acd file. - Location of the procedures in the job aid
- Parent--child relationship of the ControlNet and the

controller that you add to the I/O configuration
- Produced and consumed tags that you create
- Number of scheduled (SMAX) and the number of

unscheduled (UMAX) nodes
- Values of the ControlNet network after it is configured
CN2sb56r
Exercise: Configuring Logix5000 Controllers to Share Data over a ControlNet Network 19--15
Exercise: Configuring Logix5000

Controllers to Share Data over a
ControlNet Network
Exercise A In this exercise, you will practice configuring a local Logix5000

controller to share data with a remote Logix5000 controller over a
ControlNett network.
Context:
You have finished programming and testing a complete project for a

production line. To increase productivity, the plant has set up a
second production line. The second production line needs to receive
(consume) the Pressure data from the first assembly line over a
ControlNet network.
Production Line 1 Production Line 2
ControlNet Network
Produced Consumed

In this exercise, you will share data with the other workstation on
your ControlNet network. Node 1 will produce data and node 2 will
consume the data.
Directions:
1. Open the CN2_1756r_A1.acd file (the producer controller.)
2. Create a user-defined data type called Station_Data that will

store the following information from the local controller:
Member Data type Description

DI DINT Digital Inputs
CN2e56r
19--16 Exercise: Configuring Logix5000 Controllers to Share Data over a ControlNet Network
3. Create a controller scoped tag called Local_Station_Data with

the following properties:
 Uses the Station_Data data type
 Produced for 1 controller
4. Enter ladder logic to copy your analog channel 0 data and channel
1 data as well as your discrete input data to the respective
members of the Local_Station_Data tag.
your local controller in slot 1.
6. Place the controller in slot 1 in Remote Run mode.
7. Open the CN2_1756r_A2.acd file (the consumer controller.)
Tip " This project will be downloaded to the controller in slot 3 of the
remote workstation after you have completed the configuration.
8. Add the following modules to the I/O configuration (review

workstation configuration for appropriate node addresses):
A. Add the local (relative to the project’s controller) ControlNet
module to the I/O configuration.
B. Nested under the local ControlNet module, add the remote
ControlNet module to the I/O configuration.
C. Nested under the remote ControlNet module, add the
controller in slot 1 of the remote workstation to the I/O
configuration and call it Remote_Controller.
9. Copy the Station_Data UDT from producer and paste it to the

consumer.
10. Consume the Local_Station_Data tag from the
Remote_Controller by performing the following actions:
 Create a controller scoped tag called Remote_Station_Data
that uses the Station_Data data type.
 Configure Remote_Station_Data as a consumed tag with a
rate of 100 ms.
11. Enter ladder logic to copy the Remote_Station_Data tag to your
analog channel 0 and analog channel 1 outputs.
12. Write the logic so that each of the green buttons pushed on your
workstation will light the corresponding light on the remote
workstation.
the remote consumer controller in slot 3.
CN2e56r
Do not schedule the ControlNet network until

both lines have downloaded the ladder logic.
14. When both production lines are ready, take turns scheduling the
ControlNet network.
15. To verify that each production line is correctly configured to
share data, complete the following actions:
A. Verify that moving your analog channel 0 to the middle
B. Verify that moving your analog channel 1 to the middle
C. Verify that pushing the first four discrete buttons on your
workstation light the corresponding lights on the remote
workstation.
CN2e56r
Answers Exercise A
2. The user-defined data type should look similar to the following

example:
3. The tag created should look similar to the following example:
CN2e56r
8. The I/O configuration should look similar to the following

example:
The node addresses of

your ControlNet
modules will vary based
on your setup
The slot 1 controller
9. The Station_Data UDT should now be found in the

CN2_1756r_A2 project:
CN2e56r
10. The consumed tag should look similar to the following

example:
CN2e56r
CN2e56r
CN2e56r
Optional Lesson 20

Communicating with a 1756-I/O
Module Over a ControlNet Network
Note that in the prerequisite ControlNet  Add a remote 1756-I/O module to an I/O configuration
lesson , students learned to schedule a
ControlNet network. In this lesson,  Reschedule an existing ControlNett network
students will practice rescheduling an
existing network, a common and
important task.
RSLogix 5000 software lets you add your I/O configuration to the
project before, during, or after you develop your application logic.
Do this task when:

Your I/O modules are connected to the controller by a ControlNet
network, and
 Your system is installed or you have drawings and specifications
that outline to location and configuration of your I/O modules
Before You Begin ControlNet Remote I/O
Configuring remote I/O using a ControlNet network requires the

following tasks to be performed:
1. Add the local and remote ControlNet module to an I/O
configuration.
In the standard school, note that the 2. Add a remote 1756-I/O module to an I/O configuration.
ControlNet network was previously
scheduled. This lesson will provide an 3. Schedule the ControlNet network.
opportunity to reschedule the network --
a common and important action. Here is a summary of when the data updates:
If data is multicast in the same

For this remote module If data Is transferred across a ControlNet network
chassis
The RPI only determines when the owner controller receives the data
over the network.
RPI and COS values define when the
Digital Input module multicasts data within its own
chassis. " The timingthe
however, may not coincide with
owner-controller willthe exactdata
receive value
at of theas
least RPI;
often as
the RPI.
Digital Output N/A An output receives data from the owner-controller only at the RPI rate.
The RPI and RTS rates define when the
The RPI only determines when the owner- controller receives the data
Analog Input module multicasts data within its own
over the network.
chassis.
Analog Output N/A An output receives data from the owner-controller only at the RPI rate.
RC2sb56r
20--2 Communicating with a 1756-I/O Module Over a ControlNet Network

 Add a remote 1756-I/O module to an I/O configuration
 Reschedule an existing ControlNet network
Continue
you used with the RSLogix
for sharing 5000a project
data over
ControlNet network. - Location of the procedures in the job aid
Note that if you saved the demonstration - Parent-child relationship with the ControlNet module and
file from the Configuring Logix5000
Controllers to Share Data over a
the remote modules
ControlNet Network lesson, it is not
required to configure the remote I/O - Module configuration, including the multicasting rates
module.
- Resulting module tags
RC2sb56r
Exercise: Communicating with a 1756-I/O Module Over a ControlNet Network 20--3

1756-I/O Module Over a ControlNet
Network
Exercise A In this exercise, you will practice configuring a Logix5000 controller

to communicate with a 1756-remote I/O module and reschedule the
ControlNet network.
Context:
You have programmed a complete project. As a safety feature for

plant personnel, you want to program an output light to be on when
the production line is active. Because you have used your available
I/O points in the local chassis, you must add a remote chassis to
accommodate the additional I/O requirements. You are now ready to
configure the controller to communicate with the 1756-remote I/O
module.
The setup of the remote output is shown in the following graphic:
Production
Production Line Line Active
Local Remote
Chassis ControlNet Network Chassis
Tip " In this exercise, you will share data with another workstation on a
ControlNet network. Your workstation will be the local chassis. The
other workstation will be the remote chassis.

Directions:
1. Download the Blank.acd file to the controller in slot 3.
2. Open the RC2_1756r_A1.acd file.
3. Add the local and remote ControlNet modules to the project I/O
configuration.
4. Add and configure the remote output module in slot 4. You will
be owning this module, which is located in the remote chassis.
RC2e56r
20--4 Exercise: Communicating with a 1756-I/O Module Over a ControlNet Network
5. Add the local input module that is in slot 2 to your I/O

configuration. You will also be owning this module.
6. Make a new tag, DI12, an alias tag for bit 12 of the local digital
input card in slot 2.
7. Make a new tag, DO11, an an alias tag for bit 11 of the remote
digital output card in slot 4.
8. Enter the following ladder logic in your MainRoutine:
9. Download the project to the controller in slot 1 of the

local chassis.
Do not reschedule the ControlNet network until

the projects have been downloaded to both the
local and remote controllers.
10. When both lines are ready, reschedule the ControlNet network.
11. Test the project and verify that you have correctly configured the
remote I/O by performing the following actions:
A.
Start the conveyor by energizing DI12.
B. Verify that the remote I/O light DO11 on the other
workstation is on.
C. Turn off DI12 and verify that the remote I/O light on the
other workstation is off.
D. When the project functions correctly, go offline.
RC2e56r
RC2e56r
Answers Exercise A
3. Your main configuration screen for the local ControlNet module

in slot 5 should look similar to the example (The ControlNet
node number will vary depending on your workstation setup.):
The remote ControlNet module is added to the I/O

Configuration by right-clicking the ControlNet network icon
displayed below the local ControlNet module:
RC2e56r
Your main configuration screen for the remote ControlNet

ControlNet node address will vary depending on your
workstation setup.):
4. Add the remote output module by right-clicking the backplane

displayed beneath the remote ControlNet module:
RC2e56r
Your main configuration screen for the remote output module in

5. Your main configuration screen for the local input module in

(Continued)
Your completed I/O Configuration within the Controller
Organizer should look similar to the following:
RC2e56r
10. If you did not receive the appropriate system response after
rescheduling the ControlNet network, verify that you have
completed the following actions:
- Set the SMAX to be equal to the highest number node that
can use scheduled time on the network
- Set the UMAX to be equal to the highest number node that
can use unscheduled time on the network
- Reschedule the network if any changes were made after the
first rescheduling
RC2e56r
RC2e56r
Appendix A
I/O Wiring Diagrams For The
Assembly Application
Slot 0 - 1756-OB16D Digital Output Module
WORKSTATION APPLICATION
DEVICE LABEL OUTPUT
RED
+DC-0 2 1 OUT-0 G DO0
A DO1 CONVEYOR
+DC-0 4 3 OUT-1
+DC-0 6 DO2
5 OUT-2
R
8
+DC-0 10 OUT-3 G DO3 STATION OUTPUT (PRESS)
+DC-0 7
+DC-0 12 DO4 STATION OUTPUT (STAKE)

9 OUT-4 A
+DC-0 14
DO5 STATION OUTPUT (WELD)
11 OUT-5 R
GND-0 16
+DC-1 18
+DC-1 20
K +DC-1 22
C
A +DC-1 24
L
B
+DC-1 26
+DC-1 28
RED
+DC-1 30
GND-1 32
GND-1 34
Not Used 36
K
C
A
L
B
G - GREEN PILOT LIGHT

A - AMBER PILOT LIGHT
R - RED PILOT LIGHT
24VDC
WDAa56r
A--2 I/O Wiring Diagrams For The Assembly Application
Slot 2 - 1756-IB16D Digital Input Module
WORKSTATION APPLICATION
LABEL +24VDC
DEVICE OUTPUT
DI0 START
GND-0 2 1 IN-0
DI1
GND-0 4 3 IN-1
DI2
GND-0 6 5 IN-2
BLACK DI3
GND-0 8 7 IN-3
DI4
GND-1 10 9 IN-4
12 DI5
GND-1 11 IN-5
DI6 PART SENSOR FAULT RESET
GND-1 14 13 IN-6
BLACK DI7 READ REMOTE TOTAL
GND-1 16 15 IN-7
DI8 STOP
GND-2 18 17 IN-8
DI9
GND-2 20 19 IN-9
GND-2 22 21 IN-10 DI10
BLACK GND-2 24 23
DI11
IN-11
DI12 PART SENSOR
GND-3 26 25
IN-12
GND-3 DI13
28 27 IN-13
DI14
GND-3 30 29 IN-14
DI15
GND-3 32 31 IN-15
GND-3 34 33 NOT USED
NOT USED 36 35
NOT USED
K
C
A
L
B
- NORMALLY OPEN PUSHBUTTON

- SELECTOR SWITCH
WDAa56r
I/O Wiring Diagrams For The Assembly Application A--3
Slot 4 - 1756-OB16D Digital Output Module
RED 2
+DC-0
+DC-0 4
+DC-0 6
+DC-0 8 APPLICATION
WORKSTATION LABEL
+DC-0 10
DEVICE OUTPUT
+DC-0 12
OUT-6 G DO6
+DC-0 14 13
OUT-7 A DO7 PART SENSOR FAULT INDICATOR

GND-0 16 15
DO8 STATION OUTPUT (REJECT)
+DC-1 18 17 OUT-8 R
DO9 STATION OUTPUT (PALLETIZE)
+DC-1 20 19 OUT-9 G
K DO10
C
+DC-1 22 21 OUT-10 A
A +DC-1 24 23 DO11 LINE ACTIVE
L OUT-11 R
B +DC-1 26
+DC-1 28
RED
+DC-1 30
GND-1 32
GND-1 34
NOT USED 36
K
C
A
L
B
G - GREEN PILOT LIGHT

A - AMBER PILOT LIGHT
+24VDC
R - RED PILOT LIGHT
WDAa56r
Slot 7 - 1756-OF6VI Analog Output Module
WORKSTATION WORKSTATION
DEVICE DEVICE
OUT-1 2 1 OUT-0
AO1 (Channel 1) AO0 (Channel 0)
NOT USED 4 3 NOT USED
RTN-1 6 5 RTN-0
AO0 AO1
Return Return
OUT-3 8 7 OUT-2
RTN-3 12 11 RTN-2
OUT-5 16 15 OUT-4
RTN-5 20 19 RTN-4
WDAa56r
I/O Wiring Diagrams For The Assembly Application A--5
Slot 8 - 1756-IF6I Analog Input Module
+10VDC +10VDC
WORKSTATION WORKSTATION
DEVICE DEVICE
IN-1/V 2 1 IN-0/V
AI1 AI0
(Channel 1) (Channel 0)
IN-1/I 4 3 IN-0/I
RET-1 6 5 RET-0
AI1 AI0
Return Return
IN-3/V 8 7 IN-2/V
IN-3/I 10 9 IN-2/I
RET-3 12 11 RET-2
IN-5/V 16 15 IN-4/V
IN-5/I 18 17 IN-4/I
RET-5 20 19 RET-4
WDAa56r
WDAa56r
Appendix B
ControlLogix Workstation I/O
Device Assignments
The following standard ControlLogix workstation inputs and outputs

are used in this course (Local I/O tags are listed on the next page):
g t g t
o u
l p o u
a I
n l p
n r a I
n
A e n r
A e
0 t 1 t
0 e 0 e
h M h M
C C
g t
g t o u
l p
o u
l p a t
a t n u
A
n O
u A O
1 r
e
0 r
e 0 t
h e
0 t
h e C M
C M
9 0 1 1

3
I O 7 1
I O
1 1
I 5
1
D D D D D O
D
I
D
) )
2 4
t t
o
l o
l
S
o S
n
i
t
d 1
e 1
r - 6 7 0 8 4
i 6
( 2
I O 6 1
W I O I O 1
I
l s
t D D D D D D D
l u
A
( p
t
t u
h O
g
i
R
o )
t 0
t
f t
e o
l
L S
n n
i 5 3
u 5 1 3
I O
4
5 O
I
9
I O 1
I
R - D D D
s 0 D D D D
t (
u s
p t
n
I u
p
t
u
O
2 2
0 1
0 O
I 4 1
I O
8
I O I
D
D D D D D D
WI3a56r
B--2 ControlLogix Workstation I/O Device Assignments
Local I/O Tags The devices used in the workstation have the following I/O base
tags:
Module Workstation Device I/O Base Tag

DI0 Local:2:I.Data.0
Digital Input DI7 Local:2:I.Data.7
wired to Slot 2 DI8 Local:2:I.Data.8
D00 Local:0.O.Data.0
Digital Output D02 Local:0.O.Data.2
wired to Slot 0 D03 Local:0.O.Data.3
D06 Local:4:O.Data.6
Digital Output D08 Local:4:O.Data.8
wired to Slot 4 D09 Local:4:O.Data.9
WI3a56r
Appendix C
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
ControlNet Network
Network
1756-CNB
Workstation
or 1784-PCICS 1784-PCC
Number 1784-KTCX15 Interface
1756-ENBT IP Address 1756-CN2 Card Node Card Node
Card
Node Address Address
Address*
10
NO3a56r
C--2 Node Assignments
NO3a56r
The following are trademarks of Rockwell Automation, Inc.:

1336 FORCE 1336 IMPACT
1336 PLUS CompactLogix
ControlBus ControlLogix
Data Highway Plus DH+
DriveTools FactoryTalk
Flex FlexLogix
Logix5000 Logix5550
PanelBuilder PanelView
PLC-5 PHOTOSWITCH
PowerFlex RediSTATION
RSLinx RSLogix
RSView RSNetWorx
SCANPort SLC
SoftLogix Ultra
EtherNet/IP and ControlNet are trademarks of ControlNet International Ltd.

DeviceNet is a trademark of the Open DeviceNet Vendor Association, Inc. (ODVA).
The following are registered trademarks of Microsoft Corporation:

MS-DOS PowerPoint
Windows Windows NT
IBM is a registered trademark of International Business Machines Corporation.
Pentium is a registered trademark of Intel Corporation.
All other trademarks are the property of their respective holders and are hereby acknowledged.

Vdocuments - MX - Student Manual Abt CCP tsm143 Rslogix 5000 Level 3 Project Developmentpdf

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Vdocuments - MX - Student Manual Abt CCP tsm143 Rslogix 5000 Level 3 Project Developmentpdf

Uploaded by

Copyright:

Available Formats

8/16/2019 Student Manual _ ABT-CCP-TSM143 _ RSLogix 5000, Level 3 _ Project Development.

Important User Information

Identifies information about practices or circumstances

Identifies information that is critical for successful

Identifies information about practices or circumstances

Important User Information

Labels may be located on or inside the drive to alert

Labels may be located on or inside the drive to alert

Comments (include lesson title, if applicable):

Course or Product Name (Important):

Updating Logix5000 Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1- 1

Exercise: Updating Logix5000 Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1- 5

Creating and Organizing a New RSLogix 5000 Project . . . . . . . . . . . . . . . . . . . . . . . 2- 1

Inhibited Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--4

Exercise: Creating and Organizing a New RSLogix 5000 Project . . . . . . . . . . . . . . . 2-15

Creating a Periodic Task in an RSLogix 5000 Project . . . . . . . . . . . . . . . . . . . . . . . . 3- 1

Table of Contents iii

Exercise: Creating a Periodic Task in an RSLogix 5000 Project . . . . . . . . . . . . . . . . 3-11

Organizing Data in an RSLogix 5000 Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 1

Monitoring and Editing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--11

Quick Watch Tag Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--15

Exercise: Organizing Data in an RSLogix 5000 Project . . . . . . . . . . . . . . . . . . . . . . 4- 19

Creating a User-Defined Data Type in an RSLogix 5000 Project . . . . . . . . . . . . . . . . 5-1

Exercise: Creating a User-Defined Data Type in an RSLogix 5000 Project . . . . . . . . 5- 7

Entering, Editing, and Verifying Ladder Logic in an RSLogix 5000 Project . . . . . . . . 6- 1

Configuring Ladder Logic Quick Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--2

Communicating with a Local 1756-I/O Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7- 1

Exercise: Communicating with a Local 1756-I/O Module . . . . . . . . . . . . . . . . . . . . . 7- 11

Configuring a Logix5000 Controller to Produce and Consume Data . . . . . . . . . . . . . 8-1

Exercise: Configuring a Logix5000 Controller to Produce and Consume Data . . . . . 8- 11

Configuring Logix5000 Controllers to Share Data over an EtherNet/IP Network . . . . 9- 1

Table of Contents vii

Exercise: Configuring Logix5000 Controllers to Share Data over an EtherNet/IP

Communicating with a 1756-I/O Module over an EtherNet/IP Network . . . . . . . . . . . 10-1

Exercise: Communicating with a 1756-I/O Module over an EtherNet/IP Network . . . . 10- 5

Creating an Event Task in an RSLogix 5000 Project . . . . . . . . . . . . . . . . . . . . . . . . . 11- 1

viii Table of Contents

Exercise: Creating an Event Task in an RSLogix 5000 Project . . . . . . . . . . . . . . . . . 11-13

Retrieving and Setting Logix5000 Controller Status Values with GSV/SSV

Controller Status Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--6

Multiple Recoverable Major Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--10

Programming a BTD Instruction in an RSLogix 5000 Project . . . . . . . . . . . . . . . . . . 13-1

Exercise: Programming a BTD Instruction in an RSLogix 5000 Project . . . . . . . . . . 13- 5

Configuring a Logix5000 Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14- 1

Read, Write, and Block Transfer Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14--3

Exercise: Configuring a Logix5000 Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14- 7

Developing an Add-On Instruction in Ladder Diagram . . . . . . . . . . . . . . . . . . . . . . . 15- 1

Online Safety Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15--15

Exercise: Developing an Add-On Instruction in Ladder Diagram . . . . . . . . . . . . . . . 15-21

Managing RSLogix 5000 Project Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16- 1

xii Table of Contents

Here’s How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16--6

Exercise: Managing RSLogix 5000 Project Files . . . . . . . . . . . . . . . . . . . . . . . . . . . 16- 7

Allocating Connections in a Logix5000 System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17- 1

Exercise: Allocating Connections in a Logix5000 System . . . . . . . . . . . . . . . . . . . . 17- 5

Integrated Practice — Developing an RSLogix 5000 Project . . . . . . . . . . . . . . . . . . . 18-1

Exercise: Integrated Practice — Developing an RSLogix 5000 Project . . . . . . . . . . . 18- 3

Configuring Logix5000 Controllers to Share Data over a ControlNet Network . . . . . 19-1

Table of Contents xiii

Cable System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19--3

Exercise: Configuring Logix5000 Controllers to Share Data over a ControlNet

Communicating with a 1756-I/O Module Over a ControlNet Network . . . . . . . . . . . . 20-1

ControlNet Remote I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20--1