Abt-Ccp170-Tim 2008-07

ControlNett and RSNetWorxt Software Design and Configuration
Instructor Guide
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.
Summary of Changes
Feedback
Thank you to all of the instructors who provided input or reviewed this course. Additional feedback may be provided through the FTI Feedback Database. The ControlNet and RSNetWorx Design and Configuration course has been updated to reflect the most current software revision and instructor feedback. Please note the following changes: The information, graphics, exercises, and demonstrations in this course have been updated to reflect the latest version of RSNetWorx for ControlNet software (version 9.0) and RSLogix 5000 software (version 17).
Overview of Changes
Rev. July 2008
E 2008 Rockwell Automation, Inc. All rights reserved.
Rev. July 2008
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
Course Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Who Should Attend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Agenda . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Meeting Course Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Student Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Application Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I I II II II III III
Lessons
Designing a ControlNet Media System
What You Will Learn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Why These Skills Are Important . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NetLinx Open Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ControlNet Media System Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Application Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Media Needs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ControlNet Network Media Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Trunk Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Coaxial Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Coaxial Trunk Cable Segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example: Maximum Allowable Segment Length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fiber Optic Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fiber Optic Trunk Cable Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Redundant Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cable Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Repeaters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Coaxial Repeaters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fiber Repeaters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terminators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Taps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Programming Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Heres How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Heres How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--1 1--1 1--1 1--2 1--2 1--3 1--3 1--4 1--5 1--5 1--6 1--7 1--7 1--8 1--9 1--11 1--12 1--14 1--14 1--15 1--15 1--17 1--17 1--18 1--19 1--20 1--21
ii
Table of Contents
Exercise: Designing a ControlNet Media System

Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bill of Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--23 1--24 1--25 1--26
Configuring an Offline ControlNet Network

What You Will Learn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Why These Skills Are Important . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RSNetWorx for ControlNet Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RSNetWorx for ControlNet Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EDS Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EDS Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chassis Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CTDMA (Concurrent Time Domain Multiple Access) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scheduled Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example: Scheduled Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unscheduled Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example: Unscheduled Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Guardband . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Update Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maximum Scheduled Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maximum Unscheduled Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Media Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Media Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Keeper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scanner Signatures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Heres How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--1 2--1 2--1 2--2 2--3 2--3 2--3 2--4 2--5 2--5 2--6 2--7 2--7 2--8 2--8 2--9 2--9 2--10 2--10 2--11 2--11 2--12 2--12 2--12 2--12 2--13 2--14 2--15
Exercise: Configuring an Offline ControlNet Network

Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--17 2--17 2--18
Table of Contents
iii
Going Online to a ControlNet Network

What You Will Learn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Why These Skills Are Important . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RSWho Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Communications Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ControlNet Communications Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1784-KTCX15 Communications Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1784-PCC Communications Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1784-PCIC Communications Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Online Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Downloading an Offline Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uploading Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Heres How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--1 3--1 3--1 3--1 3--2 3--3 3--3 3--4 3--5 3--5 3--6 3--6 3--6
Exercise: Going Online to a ControlNet Network

Entering Scheduled ControlNet I/O Data Connections for Logix5000 Controllers

What You Will Learn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Why These Skills Are Important . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I/O Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I/O Configuration Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Communications Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connection Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Direct Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example: Direct Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rack Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example: Rack Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example: Direct Connections vs. Rack Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Owner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Listen-Only Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Electronic Keying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requested Packet Interval (RPI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Actual Packet Interval (API) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example: Actual Packet Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example: Network Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Heres How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--1 4--1 4--1 4--2 4--3 4--3 4--3 4--4 4--4 4--5 4--5 4--6 4--6 4--7 4--8 4--8 4--9 4--9 4--10 4--10 4--11 4--11
iv
Table of Contents
Exercise: Entering Scheduled ControlNet I/O Data Connections for Logix5000 Controllers
Entering ControlNet Messages for Logix5000 Controllers

What You Will Learn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Why These Skills Are Important . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Source-Destination Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example: Data Transfer in the Source-Destination Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . Producer-Consumer Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example: Data Transfer in the Producer-Consumer Model . . . . . . . . . . . . . . . . . . . . . . . . . . . Produced and Consumed Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Produced Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Consumed Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unscheduled Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CIP Generic Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connection Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Heres How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--1 5--1 5--1 5--1 5--2 5--2 5--3 5--3 5--4 5--5 5--6 5--7 5--7 5--8 5--8 5--9
Exercise: Entering ControlNet Messages for Logix5000 Controllers

Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exercise B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exercise B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--11 5--12 5--12 5--13 5--14 5--14
Entering Scheduled ControlNet I/O Data Connections for PLC-5 Processors

What You Will Learn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Why These Skills Are Important . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Diagnostic File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Status File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Input File (DIF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Output File (DOF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--1 6--1 6--1 6--2 6--3 6--3 6--4 6--4 6--5
Table of Contents
Data Connection Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Source-Destination Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example: Data Transfer in the Source-Destination Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . Producer-Consumer Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example: Data Transfer in the Producer-Consumer Model . . . . . . . . . . . . . . . . . . . . . . . . . . . Scheduled Data Connections on a ControlNet Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scheduled Connection Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exclusive Owner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Input Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Listen Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Redundant Owner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requested Packet Interval (RPI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Actual Packet Interval (API) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example: Actual Packet Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example: Network Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Heres How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6--6 6--6 6--7 6--7 6--8 6--8 6--8 6--9 6--9 6--9 6--10 6--10 6--10 6--11 6--11 6--12 6--12
Exercise: Entering Scheduled ControlNet I/O Data Connections for PLC-5 Processors
Entering ControlNet Messages for PLC-5 Processors

What You Will Learn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Why These Skills Are Important . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scheduled Message Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Send Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Receive Data From . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unscheduled Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message (MSG) Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mapping Data from a PLC--5 Processor to a ControlLogix Controller . . . . . . . . . . . . . . . . . . . . . . Communications Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ControlNet I/O (CIO) Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Communications Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Heres How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--1 7--1 7--1 7--2 7--2 7--2 7--3 7--3 7--3 7--5 7--6 7--6 7--6
Exercise: Entering ControlNet Messages for PLC-5 Processors

Exercise A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exercise B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How Did You Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exercise B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--7 7--8 7--8 7--9 7--10 7--10
vi
Table of Contents
Integrated Practice Configuring a ControlNet Network

What You Will Learn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Why These Skills Are Important . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8--1 8--1
Exercise: Integrated Practice Configuring a ControlNet Network

Appendices
Functional Specification
Media System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scheduled I/O Data Connections for the PLC-5 Processor at Node One . . . . . . . . . . . . . . . . . . . . . Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Safety Check One: Lap Bars Secure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Safety Check Two: Drive System Speed Normal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scheduled Messages from the PLC-5 Processor at Node One . . . . . . . . . . . . . . . . . . . . . . . . . . . . Safety Check One and Two Sent to Logix5000 Controller at Node Four, Slot One . . . . . . . . . . . Unscheduled Messages from the PLC-5 Processor at Node One . . . . . . . . . . . . . . . . . . . . . . . . . . Entry Data Sent to Logix5000 Controller at Node Four, Slot One . . . . . . . . . . . . . . . . . . . . . . . Scheduled I/O Data Connections for the Logix5000 Controller at Node Four . . . . . . . . . . . . . . . . . . Logix5000 ControlNet Bridge I/O Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Flex ControlNet I/O Adapter I/O Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Flex Combo Analog Module I/O Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Flex Combo Digital Module I/O Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scheduled Messages from the Logix5000 Controller at Node Four . . . . . . . . . . . . . . . . . . . . . . . . . Safety Check Three Sent to the Processor at Node One . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unscheduled Messages from the Logix5000 Controller at Node Four . . . . . . . . . . . . . . . . . . . . . . . Exit Data Sent to the Processor at Node One . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A--1 A--2 A--2 A--2 A--3 A--3 A--4 A--4 A--4 A--4 A--5 A--5 A--5 A--5 A--6 A--6 A--6 A--7 A--7
Bill of Materials Worksheet

Bill of Materials Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B--1
Input/Output Device Assignments

PLC-5 Processor Workstation I/O Device Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logix5000 Controller Workstation I/O Device Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C--1 C--1
Course Overview
Opening Comments: Welcome students. Give administrative details: 1. Class hours 2. Break times 3. Cafeteria information 4. Telephones 5. Restroom locations Ask each student to share: 1. Name and title 2. Company and location 3. How they use a ControlNet network on the job
Course Overview
Course Purpose
This course provides the skills necessary to efficiently design and configure ControlNet-capable hardware and software into an effective control network. You gain these skills from the ground up, practicing each step in the design and configure process from choosing the correct cable to configuring the connections that will transmit data across that cable. After completing this course, you will have designed a ControlNet media system that will serve as the backbone of your network and will have configured ControlNet-capable hardware to behave as a deterministic and repeatable control network. More importantly, you will have configured data connections between devices that transmit data where you need it, when you need it. Individuals who are responsible for designing and configuring a new ControlNet network or managing and modifying an existing ControlNet network should attend this course.
Who Should Attend
Rev. July 2008
E 2008 Rockwell Automation, Inc. All rights reserved. OVEi200
II
Course Overview
Prerequisites
Poll the class at this time to determine the amount of networking experience the students have. If the class has a significant amount of networking experience, the exercises in the course may take less time than indicated.
To successfully complete this course, the following prerequisites are required: Ability to perform basic Microsoft Windowsr tasks.
Ability to program ladder logic using Windows-based software

such as RSLogix 5, RSLogix 500, or RSLogix 5000.
Agenda
30 minutes 90 minutes 60 minutes 120 minutes 180 minutes
Day 1 Overview Designing a ControlNet Media System Configuring an Offline ControlNet Network
Going Online to a ControlNet Network Entering Scheduled ControlNet I/O Data Connections Logix5000
Controllers
120 minutes 120 minutes 120 minutes 120 minutes
Day 2 Entering ControlNet Messages for Logix5000 Controllers Entering Scheduled ControlNet I/O Data Connections for PLC-5 Processors
Entering ControlNet Messages for PLC-5 Processors Integrated Practice: Configuring a ControlNet Network
The following course structure is generally used to facilitate your ability to meet the course objectives: 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 Heres 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.
Meeting Course Objectives
Rev. July 2008 OVEi200
Course Overview
III
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 key concepts, definitions, and examples presented in the course and includes the hands-on exercises.
Hold up the Procedures Guide. Show the Table of Contents, one or two procedures, and the Glossary. Note that this guide will be a good reference when students are completing tasks back on the job. Hold up the ControlNet Documentation Reference Guide. Show the list of publications and icons in the How To Use This Guide section. Turn to a section in the guide and point out the identifying icon.
ControlNet and RSNetWorx Procedures Guide, which contains
clear and concise step-by-step procedures for performing the design and configuration tasks addressed in class, as well as other tasks associated with the configuration and management of a ControlNet network using RSNetWorx for ControlNet and RSLinx software. ControlNet Documentation Reference Guide, which contains several different technical publications. This guide contains the most frequently referenced design limitation and configuration information and is a quick and efficient on-the-job resource for ControlNet users.
Application Overview
The exercises in this course are based on a fictitious scenario in which you are the lead designer for Adventure World, an amusement park. You are responsible for the design and configuration of a ControlNet network for a new roller coaster, the CNET Coaster, being installed at the amusement park. As you design and configure the network, you will be given the opportunity to test it using a hardware workstation with devices that represent the applications inputs and outputs. This designing, configuring, and testing experience can then be transferred to your own job responsibilities. The roller coaster application is shown in the following graphic:
PLC-5 Processor Node 1
1794-ACN Node 2
1794-ACN Node 3
Logix5000 Controller Node 4
Communications Card Node 5
Rev. July 2008
E 2008 Rockwell Automation, Inc. All rights reserved. OVEi200
IV
Course Overview
Do not go into detail about the application at this point, instead open the CCP170_N200.exe file and simply present the functional components of the application. The application simulation will be an excellent tool to illustrate the application basics. It is not necessary to explain which devices control which functions of the application. These details will be presented in the lesson exercises and the appendix containing the functional specification.
The application operates in the following manner: A car is cleared to start after the following three safety checks:
- All lapbars are latched. - The drive system is up to speed. - The last car has successfully made it to the exit station. After clearance, the operator starts the ride. After the first hill, the ride runs a speed safety check. If the car fails the speed safety check, the following actions
occur:
- The safety brakes are engaged. - An alarm light is lit. When the car enters the exit station, the following actions occur: - The car is stopped by the exit station brakes. - The next car is signaled all clear. Entry and exit information is recorded and shared between both
stations of the ride to be collected by park operations. You will receive directions at the start of each exercise that will help guide you through the tasks performed in the exercises.
Rev. July 2008 OVEi200
Lesson Designing a ControlNet Media System

What You Will Learn
After completing this lesson, you should be able to design a ControlNet media system to fit the functional specification of an application by performing the following tasks: Determine application requirements Determine media needs
Why These Skills Are Important

Having the skills to correctly design a ControlNet media system is important for the following reasons: Determining application requirements will avoid unrealistic performance expectations on the media and ensure effective data transmission even in extreme environmental conditions. Correctly determining the media needs of a network will avoid malfunction caused by selecting the wrong media components or misunderstanding the limitations of those media components.
Mention that extreme environmental conditions would include heavy industrial, high and low temperature, festooning and flexing etc.
Before You Begin
ControlNet Network Overview

Network: A collection of connected devices that allows for the easy flow of data between one another. A ControlNet network is a state-of-the-art open network designed to provide the following functionality: Bandwidth for I/O, real-time interlocking, peer-to-peer messaging, and programming all on the same link Deterministic delivery of data that helps assure when data is sent Repeatable delivery performance that does not change when devices are added or removed from the network
Do not go into detail about data exchange on ControlNet networks. This will be discussed in detail later.
Producer-Consumer model network efficiency that permits all
devices on the network to simultaneously access the same data from a single source
Rev. July 2008
E 2008 Rockwell Automation, Inc. All rights reserved. DE1ib200
1-2
NetLinx Open Architecture

Trace the ControlNet network example in the graphic and point out some of the characteristic devices on the network. For example, the PLC-5 processor, Flex I/O and ControlLogix Gateway are some characteristic devices that can be found in the graphic and in the students workstations. Explain that open indicates that the specifications and technology are not managed or governed by Rockwell Automation and are available to all ControlNet users and vendors through ControlNet International.
ControlNet networks are one of the core networks of the NetLinx open architecture. A NetLinx open architecture has the following characteristics: Is a combination of network services to help ensure the efficient and seamless flow of information and control data through an application
Has a common wire-independent protocol Has open software interfaces

The following graphic shows how a ControlNet network fits within the NetLinx open architecture:
Windowsr Operating System with RSViewt Software RSLinxr Software and Windows Operating System
Ethernet Network
PLC-5r Processor
Modem
PCMCIA Communications Card
ControlLogix PanelViewt Terminal
ControlNet Network
PLC-5C Processor Flex I/Ot CN2FF Linking Device
1336 FORCE Drive
DeviceNett Network
FOUNDATION Fieldbust Network Transducer
SMP-3t Solid-State Overload
MicroLogixt Controller
Flowmeter
ControlNet Media System Design

Mention that the bulk of ControlNet problems are media related. The application requirements and media needs of a ControlNet network are extremely important in ensuring that the network functions properly.
The design of a ControlNet media system is a process of measurement and judgement. The objective is to select the ControlNet media that will serve as the foundation for network operations.
Rev. July 2008 DE1ib200
1-3
When designing a network for an application, the following deciding factors must be addressed in order to assure a steady control foundation: Application requirements
Media needs
Application Requirements Application requirements are environmental factors that if not considered in the design of a network could make network operation limited or impossible. Application requirements are important in making the following decisions: What type of cable is needed? What type of cable connectors are needed? The following example application requirements should be factored into a network design: High ambient temperature EMF noise
? What is another decision where it is

important to consider environmental factors? Possible Answer: Whether a redundant (back-up) network is necessary.
Flooding
Media Needs Media needs are the physical requirements of a network and are measured against the limitations of the media used. If the media needs are addressed without regarding the limitations of the media, the result may be a weak or unusable signal that could halt network operation. Media needs are important in making the following decisions: How much cable is needed? How is the programming device connected? The following example media needs should be factored into a network design: Length of network from the first device to the last device Ability to configure the network from any device connected to the network
? What is another decision where it is

important to consider the physical requirements of a network? Possible Answer: How many cable connectors are needed.
Rev. July 2008
1-4
ControlNet Network Media Components

Do not go into detail about each media component. The following sections will address each component in detail.
ControlNet network media components provide flexibility when designing a communications network for a particular application. A ControlNet network consists of a combination of the following media components: Trunk Cable: A bus or central part of a network media system that serves as a communications channel between any two points on a network. Cable Connector: A piece of hardware for mating and demating network media and devices.
Repeater: A piece of hardware that receives a signal on a cable,
amplifies the signal, and then retransmits it along the next leg of the cable. Terminator: A piece of hardware attached to the end points of a network to absorb signals that would otherwise reflect back and create interference with other signals. Tap: A piece of hardware that acts as a communications link between the network and a device, extracting a portion of the signal from the trunk cable.
Node: A connection point with the programmed or engineered

capability to recognize and process incoming data or transmit data to other nodes.
The following graphic shows how these components fit together to create a ControlNet media system:
Link Cable Connectors
Segment Terminator Repeater
Taps
Nodes
Trunk Cable Section
1-5
Trunk Cable
Pass around cable examples to the students.
A ControlNet trunk cable is the bus or central part of the system. Depending on the environmental factors associated with an application and installation site, a combination of the following types of cables can be used: Coaxial cable Fiber optic cable Coaxial Cable The most common type of cable used to construct trunk cable sections is standard quad-shield RG-6 coaxial cable, which has the following characteristics: Low cost
Mention that this type of cable is essentially the same cable that is used in the cable TV industry. However, it is important to note the strict ControlNet requirements or a mistake could hamper network operation. It is best practice to use RG-6 cable for ControlNet apps.
Wide availability Suitable for most light industrial applications

The coaxial cable must be quad-shield for a ControlNet network to operate without noise interference. The following graphic shows the identifying composition of a quad-shield RG-6 coaxial cable:
Braid Shield
Center Conductor
Outer Sheath
Tape Shield
Mention that standard PVC CM-CL2 cable is inappropriate for a harsh environment. For example, it was not manufactured for the wear and tear that comes with the constant flexing involved with some welding applications and it will fail.
Different types of quad-shield RG-6 coaxial cable are manufactured to meet unique application requirements. The following table shows different types of quad shield RG-6 coaxial cables and their recommended uses:
For . . . Festooning or flexing applications Moisture resistant applications; direct burial, with flooding compound, fungus resistant Light industrial applications Heavy industrial applications High and low temperature applications and corrosive areas (harsh chemicals) Use this type of quad-shield RG-6 coaxial cable . . . High flex Flood burial Standard-PVC CM-CL2 Lay-on armored and interlocking armour Plenum-FEP CMP-CL2P
Rev. July 2008
1-6
The capabilities of the coaxial cable chosen for an application should match the environment of the application.
Coaxial Trunk Cable Segments A coaxial trunk cable segment is comprised of several sections of coaxial trunk cable separated by taps, terminated at each end. The total length of a segment is equal to the sum of all of the coaxial trunk cable sections. The following graphic shows how the coaxial trunk cable and taps fit together to create a segment:
Tap Trunk Cable Section Terminator
In order to design a coaxial trunk cable segment to meet the media needs of a network, it is important to understand the limitations of the coaxial cable. The maximum allowable segment length for coaxial cable can be calculated after finding the following quantities: Amount of signal loss created by taps Amount of signal loss create by cable length Amount of signal loss permissible on a ControlNet network
1-7
? How long is the maximum segment

length for standard quad-shield RG-6 coaxial cable with 32 taps? Answer: Based on the graph, roughly 500 m (1640 ft)
Example: Maximum Allowable Segment Length The maximum allowable segment length of standard quad-shield RG-6 coaxial cable is 1,000 m (3,280 ft) with two taps connected. Each additional tap decreases the allowable segment length by 16.3 m (53 ft) because of the noise it creates. The following graphic represents the relationship between the number of taps and its effect on the maximum allowable segment length:
Segment Length m (ft)
1000 (3280) 750 (2460) 500 (1640)
250 (820) 2 16 32 48
Number of Taps
Fiber Optic Cable Fiber optic cable can be used to construct a trunk cable when coaxial cable cannot meet application requirements or media needs. While you cannot connect fiber optic cable directly to a device (with the exception of a few devices), fiber optic cable can provide the following added capabilities: Increases network length from meters to kilometers Provides galvanic isolation in a high-noise environment Avoids lightning problems when interconnecting equipment in different buildings
Mention that using fiber optic cable requires extensive training and practice. An expert should always check a media system with fiber optic cable before the network goes online.
The following table shows types of fiber optic cable and their recommended uses:
For distance requirements . . . 300 m (984 ft) or less 300 m (984 ft) or more Use this type of fiber optic cable . . . 200 Micron HSC 62.5/125 Micron cable
Rev. July 2008
1-8
Fiber Optic Trunk Cable Segment A fiber optic cable segment is comprised of a section of fiber optic cable that is connected on each end by a fiber repeater and a fiber adapter. The fiber adapter translates the signal from the fiber optic cables so that it can be transmitted over coaxial cable. The following graphic shows a basic fiber optic trunk cable configuration of fiber optic cable, fiber adapters, and fiber repeaters:
Tap Coaxial Trunk Cable
Fiber Adapter Fiber Repeater
Fiber Adapter
Fiber Repeater
Tap
Fiber Optic Cable
1-9
Mention that the amount of signal loss for cables, connectors, etc. should be available from the manufacturer.
In order to design a fiber optic trunk cable segment to meet the media needs of a network, it is important to understand the limitations of the fiber optic cable. The maximum allowable segment length for fiber optic cable can be calculated after finding the following quantities: Amount of signal loss by connectors, splices, bulkhead, etc.
Amount of signal loss by cable length Amount of signal loss permissible on a ControlNet network
The amount of permissible signal loss is contingent upon operating temperature for fiber optic cable. Check the valid temperature range of the permissible signal loss when calculating maximum cable length.
Length of the worst case signal delay (total delays through cable
and repeaters) between any two nodes and the network network
Permissible length of a worst case signal delay on a ControlNet
Tip "
Cable delays through taps are minimal and can be ignored. Redundant Media A second trunk cable can be connected between ControlNet devices to provide redundant media. With redundant media, devices send signals on two separate segments. The receiving device compares the quality of each signal and accepts the better signal. Redundant media can be used in an application that requires added security should one cable fail. The following graphic shows how media components fit together to create a redundant cable segment:
Trunk Cable A
Trunk Cable B
Devices Supporting Redundant Media
Rev. July 2008
1-10
Give some examples of where redundant media would be warranted. One example would be a steel mill, where hot steel is being run through an application. If there is a loss of network function in the application, then the steel will harden causing massive property loss.
A redundant media system fulfills unique media needs. However, with redundant media, there are added limitations. The following limitations must be observed to successfully design a redundant media system: The two trunk cables should be routed apart from one another to reduce the chance of both cables being damaged at the same time.
Each node on a redundant cable link must support redundant
coaxial cable connections. Each node must be connected to both trunk cables at all times. Any nodes connected to only one side of a redundant trunk cable segment will result in media errors on the trunk cable segment that is unconnected.
Each trunk cable of a redundant trunk cable segment can contain
different lengths of cable. The total difference in length between the two trunk cables of a redundant trunk cable segment must not exceed 800 m (2640 ft). on different segments. This will cause erratic operation. The following graphic shows this type of invalid network design:
Trunk Cable A
A single nodes redundant trunk cable connections should not be
Segment 1
Trunk Cable B
Trunk Cable B Trunk Cable A
Segment 2
Node Connected to Two Different Segments
1-11
Switching a nodes redundant trunk cable connections (i.e., trunk cable A is connected to the B connector and trunk cable B is connected to the A connector) will cause erratic network operation. The network will function, but it will be difficult to interpret cable fault indications and locate a bad trunk cable.
Both trunk cables of a redundant trunk cable segment must have
identical configurations. Each trunk cable must contain the same number of taps, nodes, and repeaters in the same relative sequence. The following graphic shows how taps, nodes, and repeaters should be used on a redundant media system:
Repeaters
Nodes Supporting Redundant Media
Trunk Cable A Trunk Cable B
Nodes Supporting Redundant Media
Trunk Cable B Trunk Cable A
Cable Connectors
Mention to the students that this information can be found in the ControlNet Networks Documentation Reference Guide and point out the section for them.
Cable connectors provide added flexibility when designing a ControlNet media system and, when utilized to match an applications requirements, help avoid unnecessary damage to the trunk cable.
Rev. July 2008
1-12
The following table shows types of cable connectors and their recommended uses:
To . . . Attach coaxial cable sections to a taps BNC connector Reserve a space in a coaxial cable for future installation of a tap or to splice a cable Connect two adjacent taps without a coaxial cable section between them Go through grounded panel walls while maintaining the shield isolation of a coaxial cable Cap off installed taps that have yet to be connected to a node Provide a 90_ bend in a coaxial cable (prevents bending cable excessively) Connect a short-distance fiber optic cable to a fiber repeater Connect a medium, long, or extra-longdistance fiber optic cable to a fiber repeater Use this type of cable connector . . . 1786--BNC cable connector 1786--BNCJ bullet (jack-to-jack) 1786-BNCP barrel (plug-to-plug) 1786-BNCJI isolated bulkhead (jack-to-jack) 1786-TCAP tap dummy load Right angle (jack-to-plug) V-pin plug and play type connector MT-RJ or ST connector
Repeaters
Pass around a repeater for the students to examine, pointing out the different features of coaxial repeaters and fiber repeaters and the status indicators.
Depending on the media needs of an application, a coaxial or fiber repeater may be required. Coaxial and fiber repeaters can be used to create the following functionality: Increase the number of taps allowed by the network Extend the total length of the trunk cable
Create a star topology

If an application requires more taps on a trunk cable segment or a longer trunk cable segment than the limitations allow, repeaters will need to be installed. The following graphic shows the limitations for a coaxial cable with a 5.99 db @ 10 MHz per 1000 ft cable attenuation:
Segment Length m (ft)
1000 (3280) 750 (2460) 500 (1640)
Repeater Required Repeater Not Required

2 16 32 48
250 (820)
Number of Taps
1-13
Mention that although the following topology examples show a specific repeater being used, both fiber and coaxial repeaters can be used. Mention that point-to-point topologies are generally less expensive to create, but offer less stability should one or more nodes malfunction.
The application requirements of a network can affect the physical shape of a network. Repeaters can be utilized to create different network topologies to meet the demands of an application: Repeaters can be used in a series to create a point-to-point or bus topology to meet standard application requirements. The following graphic shows how the coaxial repeaters could be used to create a point-to-point topology:
Repeaters in Series
? In what type of an application would

a star topology not be desirable? Answer: An assembly line. If a device fails on an assembly line, it is not desirable for the other devices to continue operation. For example, if the device for one of the conveyors fails, it is not desirable for the other conveyors to continue to operate, creating a pile-up of product.
Repeaters can be used in parallel to create a star topology. This is

useful in applications where one malfunctioning device must not affect the entire network. The following graphic shows how fiber repeaters could be used to create a star topology:
Repeaters in Parallel
Rev. July 2008
1-14
Repeaters can be used in a combination of series and parallel to

address unique network needs. Repeaters can be used to address the limitations of a cable and fulfill the media needs of a network. However, repeaters have their own limitations. The following limitations must be observed when using repeaters to address media needs: Only five repeaters in a series or 48 in a parallel can be used on a network.
The maximum number of addressable nodes per network (not
counting repeaters) is 99. Since repeaters do not require an address, they do not count against the total of 99. There can be only one path between any two nodes on a ControlNet network. Multiple repeater connections between two trunk cable segments are not allowed. Coaxial Repeaters Coaxial repeaters can be placed at any point on a trunk line using two taps to connect the repeater to two segments. The following types of coaxial repeaters are available: 1786-RPT high-voltage AC and DC repeater 1786-RPTD low-voltage DC repeater
Coaxial cables
Fiber Repeaters Fiber repeaters can be placed at any point on a trunk line where there is a tap. However, fiber repeaters also require a 1786-RPFA fiber adapter to translate the signal from a coaxial cable to the fiber optic cable. The following types of fiber repeaters are available: 1786-RPFS short-distance fiber repeater 1786-RPFM medium-distance fiber repeater 1786-RPFL long-distance repeater 1786-RPFXL extra-long-distance repeater
1-15
Fiber cables
Up to four repeaters with two fiber optic cable connections each can be directly plugged to a fiber adapter. Each port needs two fiber optic cable connections, one for receiving and another for transmitting signals.
Tip "
Fiber repeaters can also be used as a link from a non-hazardous area to a hazardous area. The 1797 series fiber repeaters are considered intrinsically safe.
Terminators
Terminators on a ControlNet network must meet the following requirements: Terminators must be a 75 ohm resistor mounted on a BNC plug.
Mention that 50 ohm Ethernetr terminators look the same as 75 ohm ControlNet terminators, but a ControlNet network will not operate correctly when terminated with the 50 ohm terminators.
Terminators must be installed at each end of every segment.

The following graphic shows a terminator with a 75 ohm resistor and a BNC plug:
75 Resistor BNC plug
ControlNet networks will not tolerate missing or wrong terminators like DH+t or RIO networks will.
Taps
? How far can a device be away from

the trunk cable? Answer: One meter, the length of the taps drop cable.
Rev. July 2008
Taps connect each node on a network to a coaxial trunk cable segment via an integral 1 m (39.6 in) drop cable.
1-16
The number of taps needed depends on the number of devices connected to the network. One tap is needed for every node and two taps are needed for every repeater on the network.
Tip "
When planning for future nodes, you should include the trunk cable and cable connectors for additional nodes when you design the initial network. It is not necessary to install a tap for future nodes. Instead, a BNC bullet connector should be used to reserve a place for each future node. This will minimize disruption to the network later when the additional nodes are installed. A disconnected tap can cause noise on a network. Because of this, it is recommended that you have only one unconnected drop cable per segment for maintenance purposes. If your media system requires more than one unconnected drop cable, unused drop cables should be terminated with a dummy load, 1786-TCAP.
Taps contain passive electronics and must be used for the network to function properly. Other methods of connecting to a coaxial cable will result in reflected energy that will disrupt communications.
Taps are available in the following configurations:

Straight T-Tap Straight Y-Tap Right-Angle T-Tap Right-Angle Y-Tap IP67 T-Tap
1-17
Nodes
? Is a repeater considered a node?

Answer: No, because it is not assigned an address.
Nodes are physical devices connected to the ControlNet media system. Nodes must meet the following requirements: Must have a network address in the range of 1 to 99 to function on the network A nodes network address cannot be duplicated by another node on the network.
Must be connected to the network with a tap

Programming Devices Programming devices are nodes that can be connected to a ControlNet network through the following means: A maintenance tap on a trunk cable segment for temporary connections
A dedicated tap on a trunk cable segment for permanent
connections. The following graphic shows a programming device connected to a network using a dedicated tap:
Connection to Network through a Tap
A ControlNet network access cable (1786-CP) that connects
programming devices to ControlNet nodes through a network access port (NAP) for temporary connections. The following graphic shows a programming device connected to a network using a network access port:
Rev. July 2008
1-18
Connection to Network through Network Access Port
When you connect a programming device to a network access port with a 1786-CP cable, it is counted as a node and must have a unique address. RSNetWorxt for ControlNet and RSLinx software automatically assign a node address to the node.
Use the 1786-CP cable when connecting a programming device to the network through the network access port. Using an RJ-style cable could result in possible network failures.
Heres How
The examples in these demonstrations should be performed as a discussion, focusing on the decision-making process involved with each of the components of the cable system. It is meant more to teach students the problem-solving tools needed to complete the tasks than to be an exhaustive demonstration of the tasks.
To determine application requirements for a ControlNet network. As your instructor demonstrates this procedure and the following example, follow along with the steps below and the associated job aid(s). The following steps are taken to determine the media that could fulfill the requirements of an application: 1. Determine if redundant media should be used by choosing the appropriate option:
If, for the application, downtime Cannot be tolerated because of extreme consequences (i.e. loss of life, extreme loss of capital, etc.) Can be tolerated Then . . . Use redundant media. Do not use redundant media.
? What would be an application that

warrants redundant media?
Answer: A chemical factory where a loss in network operation could create a significant safety risk.
? Why cant a network have only fiber

optic cable? Answer: Only a few drives can be connected to a network using fiber optic cable.
2. Determine what type(s) of cable will be used by performing the following actions: A. Determine what type(s) of cable will be used for the media system by choosing the appropriate option(s):
1-19
If the application requires . . . High-noise immunity, interconnecting equipment in different buildings, long distances, or intrinsic safety None of the above
Then use . . . Both fiber optic and coaxial cable. Coaxial cable only.
B. If you are using fiber optic cable, determine what type of fiber optic cable will be used by choosing the appropriate option:
If your application requires a fiber optic cable segment of . . . 300 m (984 ft) or less 300 m (984 ft) or more Then use . . . 200 Micron HSC pre-terminated short distance cable for 1786-RPFS short-distance repeaters 62.5/125 Micron cable for medium or long distance repeaters
Refer the students to the ControlNet Network Documentation Reference Guide whenever it is mentioned in the procedure to get them use to using it as a job aid.
C. Determine what type(s) of coaxial cable will be used by consulting the appropriate look-up table in the ControlNet Documentation Reference Guide 3. Determine what type(s) of cable connectors will be used by consulting the appropriate look-up table in the ControlNet Documentation Reference Guide
Example
Determining Application Requirements

The network will be required to fulfill the following application requirements: Process must be moisture resistant. Future nodes may be added. Process cannot tolerate any downtime.
The step numbers in this example directly correspond with step numbers of the previous Heres How procedure.
The following actions were taken to determine the media that could fulfill the requirements of an application: 1. Based on the decision table in the Heres How steps and the functional requirements of the network, it is determined that the application will require redundant media. 2. The type of cable that will be used was found by performing the following actions: A. Based on the decision table in the Heres How steps and the functional requirements of the network, the application will require only coaxial cable. B. Based on the previous decision table and the functional requirements of the network, the application will not require fiber optic cable.
Rev. July 2008
1-20
C. Based on the look-up table in the associated job aid(s) and the functional requirements of the network, the application will require flood burial coaxial cable for all coaxial trunk cable segments. 3. Based on the look-up table in the associated job aid(s) and the functional requirements of the network, the application will require the following cable connectors: 1786-BNC cable connectors to connect coaxial trunk cable to taps 1786-BNCJ bullet (jack-to-jack) connectors to reserve space on the coaxial trunk cable for future nodes 1786-BNCP barrel (plug-to-plug) connectors (if taps on the network are close enough together) to connect two adjacent taps without coaxial trunk cable between them
Heres How
The examples in these demonstrations should be performed as a discussion, focusing on the decision-making process involved with each of the components of the cable system. It is meant more to teach students the problem-solving tools needed to complete the tasks than to be an exhaustive demonstration of the tasks.
To determine media needs for a ControlNet network. As your instructor demonstrates this procedure and the following example, follow along with the steps below and the associated job aid(s) The following steps are taken to determine the media needs of the network: 1. Determine how much cable will be used by measuring the actual cable path as it is routed in the network. 2. Determine how many cable connectors will be used. 3. Determine trunk cable segment lengths by performing the following actions: A. If a network has coaxial trunk cable segments, use the following equation to determine maximum allowable segment length: Maximum allowable segment length = (20.29 db - number of taps in segment * .32 db) / cable attenuation @ 10 MHz per 1000 ft (304 m)) B. If a network has fiber optic trunk cable segments, use the following equation to determine maximum allowable segment length: Maximum allowable segment length (km) = (Power budget of the fiber repeater Total attenuation of cable connectors, splices, bulkhead, etc.)/ (Fiber cable attenuation in db/km)
1-21
C. If a network has fiber optic trunk cable segments, use the following formula to determine the worst case signal delay (propagation delay) between any two nodes : Maximum propagation delay = (Total of delays through coaxial cable, fiber cable, coax repeaters, fiber repeaters, and fiber modules) (121s) 4. Determine if and how many repeaters are needed by performing the following actions: A. Determine the topology of the network. B. Determine the constraints of the networks topology. 5. Determine how many terminators are needed by multiplying the number of trunk cable segments on the network by two. 6. Determine how a programming device will be connected to the network by choosing the appropriate option:
If a programming device must be. . . Capable of temporarily connecting to the network from any device Capable of temporarily connecting to the network from one location A permanent node on the network Then, connect the programming device to the network using a . . . Network access cable through a ControlNet nodes network access port. Maintenance tap on a trunk cable segment. Dedicated tap on a trunk cable segment.
7. Determine the number of taps needed by the network based on the number of nodes specified, the number of repeaters needed, and the method by which the programming device will be connected. 8. If redundant media will be used, multiply the quantity of any media component that will be used by two.
Example
Note and emphasize to the students that the step numbers in this example directly correspond with step numbers of the previous Heres How procedure.
Determining Media Needs

The network will be required to fulfill the following specifications: 46 nodes must be able to transmit data, including the programming device.
Computer used for programming must be available for other

tasks. Link must be 152 m (500 ft) long. Two potential nodes may be added in the future.
Tip "
Rev. July 2008
The step numbers in this example directly correspond with step numbers of the previous Heres How procedure.
1-22
The following steps are taken to determine the media needs of the network: 1. Based on the media requirements of the network, roughly 152 m (500 ft) of coaxial cable is required by the network. 2. Based on the media requirements of the network, at least 94 1786-BNC connectors will be used to connect the coaxial trunk cable to the taps for 46 nodes and two 1786-BNCJ barrel connectors to reserve space on the trunk cable for future nodes. 3. The trunk cable segment lengths were found by performing the following actions: A. Based on the look-up table in the associated job aid(s) for the flood burial coaxial cable attenuation and the media requirements of 46 taps and two possible future nodes, the maximum allowable length for a flood burial coaxial trunk cable segment on this network is 823 ft (250 m): ([20.29 db-48*.32 db]/5.99 db]*1000 ft) = [4.93 db/5.99 db]*1000 ft) = 823 ft (250 m) B. Because we are not using fiber optic cable, this step is not necessary. C. Because we are not using fiber optic cable, this step is not necessary. 4. Based on the calculated maximum segment length and the media requirements of the network, it has been determined that no repeaters will be used. 5. Based on the number of segments on the network, two terminators will be used. 6. Based on the number of media requirements of the network and the decision table, the programming device will be connected using a maintenance tap. 7. Based on the media requirements and no repeaters, 48 taps will be used. 8. Based on the application requirements, redundant media will be used, and the network will require twice the quantity of all media components.
1-23

Exercise A
In this exercise, you will practice designing a ControlNet media system. Context: As the lead designer for the CNET Coaster, your responsibility is to design a ControlNet media system that will be the foundation for communications over the ControlNet network. The objective is to select ControlNet media that will meet the application requirements of the roller coaster and the media needs of the network while maintaining steady network operations. You have received the functional specification for the CNET Coasters ControlNet network that will run the operation of the ride. A Bill of Materials will be used to record the components that will make up the media system you have designed. Directions: For help performing steps in this exercise, see the associated job aid(s). 1. Using the functional specification, determine the application requirements that must be addressed by the media system and record them in the Bill of Materials provided on the next page.
Tip "
To understand the requirements of the application, review the Media System section of the Functional Specification appendix. 2. Using the functional specification, determine the media needs of the network and record them in the Bill of Materials.
Rev. July 2008
E 2008 Rockwell Automation, Inc. All rights reserved. DE1e200
1-24
Bill of Materials 1. Nodes

Device Quantity*
2. Trunk Cable
Type Standard-PVC CM-CL2 Cable Lay-On Armoured or Interlocking Armoured Cable Plenum FEP CMP-CL2P Cable High Flex Cable Other: Quantity*
3. Cable Connectors
Type 1786-BNC Cable connector 1786-BNCJ Bullet Connector Other: Quantity*
4. Repeaters
Type 1786-RPT High Voltage AC and DC Coaxial Repeater 1786-RPTD Low Voltage DC Coaxial Repeater 1786-RPFS ShortDistance Fiber Repeater 1786-RPFM MediumDistance Fiber Repeater Quantity*
5. Taps
Type Straight T-Tap
(Catalog Number 1786-TPS)
Quantity*
1786-RPFA Fiber Adapter Other:
Right-Angle T-Tap
(Catalog Number 1786-TPYS)
Straight Y-Tap
(Catalog Number 1786-TPR)
6. Terminators (Number of Segments x 2)

Type 75 Ohm
(Catalog Number 1786-XT)
Quantity*
Right-Angle Y-Tap
(Catalog Number 1786-TPYR)
* If ordering materials for a redundant cable system, quantities must be doubled.

E 2008 Rockwell Automation, Inc. All rights reserved. Rev. July 2008 DE1e200
1-25
How Did You Do?
Turn to the Answers section.
Rev. July 2008
1-26
Answers
Exercise A
The worksheet on the following page is an example of how your Bill of Materials might look. The following determinations were made when designing the CNET Coasters network:
Nodes and their quantity could be found in the functional

specification. Standard PVC CM-CL2 was chosen because of the light industrial functional specification.
600 m (1966 ft) of coaxial cable will be needed. The quantity of
cable was found by adding the four distances in the functional specification. 1786-BNC cable connectors were chosen for their ability to attach coaxial cable sections to a taps BNC connector and terminating resistors. This information could be referenced in the ControlNet Documentation Reference Guide. 8 BNC cable connectors are needed to connect the trunk cable to each side of the tap for each node.
No repeaters are needed. The quantity was found from the cable
length, the number of nodes found in the functional specification, the cable attenuation information, and the maximum allowable segment equation found in the ControlNet Documentation Reference Guide. The maximum allowable segment length is 950 m (3120 ft), which is well above the length of 600 m (1966 ft).
Four right-angle T-taps are needed. The quantity was found from
the functional specification and adding the number of nodes that meet the specification for right-angle T-taps. One straight T-tap is needed. The quantity was found from the functional specification and adding the number of nodes that meet the specification for straight T-taps. Two terminating resistors are needed, one for each end of the trunk cable segment.
Rev. July 2008 DE1e200
1-27
1. Nodes
Device PLC-5r Processor 1794-ACN
Quantity* 1 2
2. Trunk Cable
Type Standard-PVC CM-CL2 Cable Lay-On Armoured or Interlocking Armoured Cable Plenum FEP CMP-CL2P Cable High Flex Cable Other: Quantity* 600m (1966ft)
1756-CNB ControlNet Communications Card
3. Cable Connectors
Type 1786-BNC Cable connector 1786-BNCJ Bullet Connector Other: Quantity* 8
4. Repeaters
Type 1786-RPT High Voltage AC and DC Coaxial Repeater 1786-RPTD Low Voltage DC Coaxial Repeater 1786-RPFS ShortDistance Fiber Repeater 1786-RPFM MediumDistance Fiber Repeater Quantity*
5. Taps
Type Straight T-Tap
Quantity* 1
Right-Angle T-Tap
Straight Y-Tap

Type 75 Ohm
(Catalog Number 1786-XT)
Quantity* 2
Right-Angle Y-Tap
(Catalog Number 1786-TPYR)
* If ordering materials for a redundant cable system, quantities must be doubled.
Rev. July 2008
1-28
Rev. July 2008 DE1e200
Lesson Configuring an Offline ControlNet Network

What You Will Learn
After completing this lesson, you should be able to configure an offline ControlNet network to fit the functional specification of an application by performing the following tasks: Create a configuration file Create an offline network configuration
Configure device parameters Configure a chassis Configure network properties Why These Skills Are Important
Having the skills to correctly configure an offline ControlNet network is important for the following reasons: Creating a configuration file will provide a back-up security for fast application recovery. Creating an offline network configuration, configuring device parameters, and configuring a chassis will ensure a networks physical components match those components for which that network was designed. Configuring network properties improperly can result in the failure of an application or make it impossible to access the network from a programming device.
Before You Begin

Ask if any students have had the opportunity to see or explore RSNetWorx for ControlNet software.
RSNetWorx for ControlNet Software

RSNetWorx for ControlNet software is the primary configuration tool for ControlNet networks. RSNetWorx for ControlNet software is used to perform the following tasks: Create or edit an offline network configuration Edit or monitor a network configuration that is active within all connected devices
Schedule communications
Rev. July 2008
E 2008 Rockwell Automation, Inc. All rights reserved. CO1ib200
2-2
RSNetWorx is supported on these Microsoftr operating systems: Windows 2000, Windows 2003, and Windows XP.
? How many of you are familiar with

software activation files and software key disks? If you choose to discuss or demonstrate this topic, refer students to the online Help procedures or technical documentation.
The software offers the following benefits: Flexible, easy-to-use, Windows-based editors and components
Point-and-click network configuration Ability to copy and paste network configurations, chassis, or
devices between configurations RSNetWorx for ControlNet Main Window
Also, tell students that they can obtain The RSNetWorx for ControlNet main window contains the following RSI software updates from the RSI Web components: page at http://support.software.rockwell.com/ Window Title Bar WebUpdates Minimize, Network Toolbar Maximize, and Point out each component in the main Usage View Close Buttons window to the students in order to Menu Bar familiarize them with the software. Check Box Hardware List Split Bar Scroll Bar Message View Network Configuration
Status Line
Tab
Open the ControlNet Networks Procedures Guide and point out the Glossary to the students.
Tip "
For your reference, graphics and definitions for these common components are provided in the Glossary of the ControlNet and RSNetWorx Procedures Guide.
Rev. July 2008 CO1ib200
2-3
RSNetWorx for ControlNet Toolbar

Point out the icon as you read the components. New Save Cut
The RSNetWorx for ControlNet toolbar provides easy access to the softwares most-commonly used components:
Paste Show Browse Diagnostic Display View Symbol Legend Zoom In Hardware Network
Open
Print
Copy
Whats This?
Zoom Out
Show Favorites
Online
Refresh
Configuration File
An RSNetWorx for ControlNet configuration file is a single file that is created when you save a network configuration using RSNetWorx for ControlNet software. It serves as both a record of a network and a safety measure, ensuring that a network can be returned to original working order should a malfunction occur. The configuration file must always have an .xc extension.
Mention that, by creating an offline configuration before the physical network is available, a designer is ensuring that the physical network is identical with the network designed. When the file is finally downloaded to the network, RSNetWorx for ControlNet software will point out any inconsistencies between the file and the installed network. This safety measure will help assure that application requirements are met.
Network Configuration
A network configuration is a graphic or spreadsheet representation of a physical ControlNet network. To design a ControlNet network before the physical network is available, a network configuration can be created offline using RSNetWorx for ControlNet software. The following graphic shows a spreadsheet representation of a network configuration:
Rev. July 2008
2-4
Hardware List When creating an offline ControlNet network configuration, a device is selected from the hardware list to be placed in the network configuration. The hardware list contains all available devices. A device can be found in the hardware list through searching by one of the following types: Vendor type
Category type
Remind students that the hardware list is located in the main window.
The following graphic partially shows the communications adapter category within the hardware list:
2-5
Device Parameters
Device parameters define a devices identity on a ControlNet network. The following general parameters for a device can be configured using RSNetWorx for ControlNet software: Name of device Description of device
Address of device Series and revision of device

EDS Files
Explain that most ControlNet devices already have an EDS file registered to RSNetWorx for ControlNet software. However, for new products released after the software revision date or third-party products, EDS files are provided and will have to be registered. Point out some of this information in the graphic or open an EDS file using RSNetWorx for ControlNet software.
EDS files are ASCII files created by device manufacturers that provide device information for a network. For a device to be available in the hardware list, a representative EDS (electronic data sheet) file must be registered to RSNetWorx for ControlNet software using the EDS Wizard tool. The following information can be found in an EDS file: Description of the EDS file history, which includes the following file information: - File name - Create time - Modification time - Revision number Description of the device, which includes the following device information: - Vendor - Product type - Revision number - Product name - Catalog number Input and output information
Device-configurable parameters
Rev. July 2008
2-6
The following graphic shows how this information is displayed in an EDS file:
EDS Wizard
Mention that it is necessary to register an EDS file for a third-party vendor device in order to use the device in a network configuration.
RSNetWorx for ControlNet software provides a tool for working with EDS files. The EDS Wizard allows users to perform the following actions with EDS files:

Register EDS-based devices Create an EDS stub Remove a device from the registry Change the graphic image associated with a device
2-7
Chassis Configuration
Chassis configuration defines a chassis identity on a ControlNet network. The following parameters for a chassis can be configured using RSNetWorx for ControlNet software: Type of chassis Addressing mode [1771 only]
Chassis contents
Network Properties
Do not go into detail about network properties at this point. This section is to establish the relationship between the network properties and the devices access to the network. Each component of the network properties will be presented in detail.
Network properties provide the guidelines that all devices on the network must follow in order to transmit data. These guidelines are defined by the following components: Network parameters that define the following guidelines: - What devices can access a network - When devices can transmit data on a network - What channel devices can use to transmit data Media configuration that defines the wait time between each devices data transmission
Rev. July 2008
2-8
Networks use an arbitration scheme to enforce these defined guidelines. ControlNet Networks use CTDMA (Concurrent Time Domain Multiple Access) as an arbitration scheme. Based on network properties, CTDMA allocates the following types of bandwidth: Scheduled bandwidth for qualifying network devices
Unscheduled bandwidth for qualifying network devices Guardband bandwidth for network maintenance
CTDMA (Concurrent Time Domain Multiple Access)
Explain the differences of CTDMA compared to other arbitration schemes. For example, CSMA/CD, used by Ethernet, does not reserve bandwidth in advance.
ControlNet networks arbitration scheme, CTDMA, allocates bandwidth based on the time critical nature of the data being transmitted. When network properties are configured, the time-sensitivity of a devices data is established. CTDMA then reserves bandwidth in the following manner: CTDMA reserves (schedules) bandwidth in advance for each node configured with time-sensitive data to deterministically and repeatably deliver its data. Remaining bandwidth is used to support any node that may have non-time critical data to send that does not require deterministic and repeatable delivery:
- Unscheduled bandwidth is not reserved for individual nodes

but is used as needed in a round-robin priority. - Delivery of unscheduled data does not impact the delivery of scheduled data. Scheduled Bandwidth Scheduled bandwidth on a ControlNet network has the following characteristics: The length of scheduled bandwidth is defined by how long it would require all scheduled nodes to transmit scheduled (i.e. time-critical) data, including I/O data and peer-to-peer interlocking data, during a user-defined interval.
Access to scheduled bandwidth is user-configured. Access to scheduled bandwidth is defined by the node with the
highest network address that requires the use of scheduled bandwidth on a ControlNet network.
2-9
Scheduled bandwidth is utilized in the following manner: Each node, from node one to the last node given access by the user, is allowed to transmit up to 510 bytes of data once during a user-defined interval.
If a node is present on the network but has no data to transmit, it
signals the network to move to the next scheduled node. Nodes wait a given amount of time for each missing node from node one to the last given access by the user. The boundary between scheduled bandwidth and unscheduled bandwidth moves depending on how much data each node sends during the scheduled bandwidth. Example: Scheduled Bandwidth Use the example as an opportunity to better illustrate the scheduled bandwidth The following graphic shows how scheduled bandwidth is used characteristics already outlined. This will help to student to better understand on a ControlNet network: what they are doing when they configure network properties. Network Update Interval Scheduled
Unscheduled Guardband 1 2 1 3 S
Nodes, one through the last given access by the user, transmit data every interval.
1 3 S
Nodes wait for each missing node.
3 S
The boundary moves depending on utilization of bandwidth.
Unscheduled Bandwidth
Point out that unlike the length of scheduled bandwidth that is defined by how long it would require for all scheduled nodes to transmit in an interval, the length of unscheduled bandwidth is only guaranteed to be long enough for one node to transmit data, but may be larger depending on the time left in the interval.
Unscheduled bandwidth has the following characteristics: The length of unscheduled bandwidth is defined by how long it would require at least one node to transmit unscheduled (i.e., non-time critical) data, including all programming and operator interface data, during an user-defined interval. Access to the network and unscheduled bandwidth is configured by the user. Access to the network is defined by the node with the highest network address that must communicate on the network.
Rev. July 2008
2-10
? What type of data would be

transmitted using unscheduled bandwidth? Possible Answer: A ladder logic project.
Unscheduled bandwidth is utilized in the following manner: Each node, from node one to the last node given access to the network, has a shared opportunity to send data on a round-robin basis until unscheduled bandwidth is exhausted.
If a node is present on the network but has no data to transmit, it
signals the network to move to the next node. Nodes wait a given amount of time for each missing node from node one to the last node given access to the network. At least one node will have an opportunity to transmit data during each user-defined interval.
First access to unscheduled bandwidth increases by one with each

interval. Example: Unscheduled Bandwidth The following graphic shows how unscheduled bandwidth is used on a ControlNet network:
Network Update Interval Scheduled Unscheduled Guardband 1 2 2 3 3 3 4 5 U 5U
1
Nodes wait for each missing node.
First access increases by one with each interval.
Sequence continues until unscheduled bandwidth is exhausted.
Guardband Guardband is the portion of each interval provided for network maintenance. Guardband is utilized in the following manner: The moderator (node with the lowest node number on the network) distributes network-wide parameters to all devices. The guardband contains the following data:
- Network parameter changes - Network parameters for newly added nodes
2-11
Explain the relationship for each parameter and the guideline that it sets for network operation. For example, network update time sets guidelines for the interval at which the network updates and also effects the amount of time available for scheduled bandwidth. If the network update time is small, then the interval is small and there is less bandwidth for scheduled nodes.
Network Parameters The following network parameters are configured using RSNetWorx for ControlNet software in order to configure how the CTDMA provides access to the networks nodes: Network update time (NUT)
Maximum scheduled node (SMAX) Maximum unscheduled node (UMAX) Media redundancy
Network Update Time

Emphasize to the students that you cannot set the RPI (Requested Packet Interval) to a rate faster than the NUT. The network cannot send data at a rate that is faster than NUT. For more information on understanding the effect of the NUT on the API or RPI, refer to lesson 4, Entering Scheduled ControlNet I/O Data Connections for Logix5000 Controllers or lesson 6, Entering Scheduled ControlNet I/O Data Connections for PLC-5 Processors.
The network update time is the user-configured repeatable base time at which the network can transmit data. One interval on the network (Network Update Interval) is equal to the network update time. In order for a network to operate properly, the network update time must meet the following requirements: Must be configured for between 2 and 100 milliseconds Must at least match the fastest rate any two nodes must communicate Must be large enough to allow the required amount of network traffic to pass
Rev. July 2008
2-12
Maximum Scheduled Node Maximum scheduled node is a user-configured parameter that defines access to scheduled bandwidth. In order for a network to operate properly, the maximum scheduled node should meet the following recommendations: Maximum scheduled node will be the address of the highest node to communicate on the scheduled bandwidth.
Maximum scheduled node will not leave empty node addresses

below maximum scheduled node, because it is a waste of scheduled bandwidth.
Tip "
Placing all scheduled nodes in a group before all unscheduled nodes will decrease the waste of scheduled bandwidth on a network. Maximum Unscheduled Node Maximum unscheduled node is a user-configured parameter defining access to the network. In order for a network to operate properly, the maximum unscheduled node should meet the following recommendations: Maximum unscheduled node will be the address of the highest node to communicate on the network. Maximum unscheduled node will not leave empty node addresses below maximum unscheduled node, because it is a waste of unscheduled bandwidth. Media Redundancy Media redundancy is a user-configured parameter that defines the channel on which data will be transferred. In order for a network to operate properly, media redundancy must be configured for one of the following options:
If you are using . . . One cable system using channel A only One cable system using channel B only Both channel A and B (redundant media) A only. B only. A/B. Use this option . . .
? Why is it important to create a media

configuration in RSNetWorx for ControlNet software? Answer: An accurate representation of media used on the network should be defined in RSNetWorx for ControlNet software to ensure optimization of data transmission.
Media Configuration In order for RSNetWorx for ControlNet software to create an accurate slot time to wait for missing nodes, a media configuration must be created. The media configuration consists of a list of any cable or repeaters used by the media system and their quantity. Inaccurate or incomplete media configurations can result in a slot time that is too fast. This will result in a loss of communications to the node.
2-13
A media configuration is created on the Media Configuration property page accessed from the network properties window:
The keeper keeps the network configuration. Redundant keepers can be configured as well.
Network Keeper
Every ControlNet network requires at least one module that stores programmed parameters for the network and configures the network with those parameters at startup: There can be multiple keepers on a network. A keeper has two characteristics. It is valid (invalid) and it is active (inactive). You can only have one active keeper on a network.
If there is no active keeper, then you have no scheduled communication or I/O control and you cannot use RSNetWorx software to edit or change the configuration.
Rev. July 2008
2-14
Mention to the students that this procedure is detailed in the ControlNet Procedures Guide. Point out the tip at the beginning: if the keeper is a single-keeper device, it must reside at node 1 and no multi-keeper devices can reside on the network. If these conditions do not exist, the problem is installation-related and the keeper should not be cleared.
Each keeper stores the network keeper signature in non-volatile memory. When using other than factory fresh keeper, always clear the keeper before configuring the network:
The active keeper and offline file hold a copy of the scanner signature for each connection originator.
Scanner Signatures Each keeper stores the scanner signatures for the entire network. The scanner signature is the unique value assigned by RSNetWorx to connection originators (scanners) owning scheduled connections when accepting the network schedule:
Tip "
Refer to the online Help for signature status summary definitions. The connection originator, not the keeper, has the original scanner signature.
2-15
Heres How
When demonstrating the procedures, use a fresh RSNetWorx for ControlNet file to point out alternative user options that will help students tailor RSNetWorx for ControlNet software to their particular workstyle and save them time in the configuration process. Some items to point out in your demonstration could include: S S S The Edits Enabled check box Hardware List display option Double-clicking a device for access to its parameters
To configure an offline ControlNet network by performing the following tasks: Create a configuration file
Create an offline network configuration Configure device parameters Configure a chassis Configure network properties
As your instructor demonstrates these procedures, follow along in the associated job aid(s).
Rev. July 2008
2-16
2-17

Exercise A
In this exercise, you will practice configuring an offline ControlNet network. Context: The CNET Coasters network is being installed. As the lead designer of the CNET Coaster, it is now your responsibility to configure the ControlNet network for the roller coaster offline. The network configuration file you create will be an excellent reference for network information and will act as a back-up should any malfunction occur. Directions: For help performing steps in this exercise, see the associated job aid(s). 1. Create a configuration file.
Tip "
To understand the requirements of the application, review the Network Configuration section of the Functional Specification appendix. 2. Use the hardware list to add devices in your workstations to create an offline network configuration. - Node 1: PLC-5 - Node 2: 1794-ACNR15 Flex I/O ControlNet Adapter - Node 3: 1794-ACNR15 Flex I/O ControlNet Adapter - Node 4: 1756-CNB or 1756-CN2 - Node 5: ControlNet PC Comms Card 3. Configure the device parameters. 4. Configure the chassis. 5. Configure the network properties.
NUT of 10 ms SMAX of 4 UMAX of 5 No Redundancy
6. Save the configuration.
How Did You Do?

Rev. July 2008

E 2008 Rockwell Automation, Inc. All rights reserved. CO1e200
2-18
Answers
Exercise A
The network configuration should look similar to the following graphic if you have completed the following actions correctly: Created a configuration file Created an offline network configuration
Configured all devices Configured all chassis
Rev. July 2008 CO1e200
2-19
If you have configured your network correctly, the Network Parameters property page should look like the following graphic:
If you have configured your network correctly, you should have made no alterations to the default configuration shown on the Media Configuration property page.
Rev. July 2008
E 2008 Rockwell Automation, Inc. All rights reserved. CO1e200
2-20
Rev. July 2008 CO1e200
Lesson Going Online to a ControlNet Network

What You Will Learn
After completing this lesson, you should be able to go online to a ControlNet network by performing the following tasks: Configure a communications driver Go online to a network

Having the skills to go online to a ControlNet network is important for the following reasons: Configuring a communications driver makes it possible for a user to upload, download, go online, update firmware, and send files over a network to its devices. Going online to a network allows a user to configure, monitor, or troubleshoot a network and its operations.
Before You Begin

Mention that RSLinx Lite software can be used with RSNetWorx for ControlNet software.
RSLinx Classic Software

RSLinx Classic software is used to create and edit the configuration of communications drivers required by various software programs to communicate with networks and their devices. RSLinx software is also used to select communications paths for uploading, downloading, going online, updating firmware, and sending files. RSWho Window After a driver is configured, the corresponding network can be found in the RSWho window. The RSWho window in RSLinx software is used to view active networks. Once opened, RSLinx software can be minimized or exited but not shut down. Shutting down the software while it is in use will end communications between the computer and the network.
Rev. July 2008
E 2008 Rockwell Automation, Inc. All rights reserved. GO1ib200
3-2
Stress that the user will not find a network in the tree structure unless a communications driver has been configured for that network.
The RSWho window, which shows networks in a tree structure similar to Windowsr Explorer, is show in the following graphic:
Available Networks
Devices on Selected Network
Communications Driver
A communications driver is a piece of software that acts as a translator between a device and any software program that communicates with that device. It provides the user with the following capabilities: Enables a user to access a network with a computers communications card
Allows a user to upload, download, or go online to a network
Rev. July 2008 GO1ib200
3-3
ControlNet Communications Cards

Mention that all the exercise files use a PCC card. The files can be modified depending on the hardware available in class.
With a driver, a ControlNet communications card allows a user to communicate from a computer to a network. In order to upload, download, or go online to a ControlNet network, one of the following communications cards must be installed in the computer: Ethernet (with necessary cables) 1784-PCC for access to a ControlNet network from any Microsoft Windows-based computer with a PC card interface such as a laptop/notebook computer
1784-PCIC for access to a ControlNet network from a desktop
? What is the network parameter that

Answer: Maximum unscheduled node or UMAX.
computer with a PCI bus 1784-KTCX15 for access to a ControlNet network from a 16-bit ISA or 32-bit EISA-compatible desktop computer For ControlNet scheduling, a communications card should be assigned a node address that meets the following guidelines in order to conserve bandwidth: A node address that is above maximum scheduled node (SMAX) but below maximum unscheduled node (UMAX). This will help better utilize scheduled bandwidth because the card will only be used for unscheduled communications. A node address that does not skip node numbers because skipping node numbers wastes unscheduled bandwidth. 1784-KTCX15 Communications Card A 1784-KTCX15 communication card lets a 16-bit ISA or 32-bit EISA compatible computer communicate directly with other ControlNet products. To configure a driver for a 1784-KTCX15 communications card, the following physical addresses must be set on the card: Base memory address (factory default is D000:0000), which will allow the card and the host computer to exchange data Base I/O address (factory default is 220), which will allow the cards I/O devices to receive commands from the computer When deciding which addresses to use, remember that each card in the computer must have a unique base memory address and a unique base I/O address. If another card in the host computer is using one or both of the factory-set addresses, you must change a cards dip switch settings to an available address.
defines what devices can communicate on unscheduled bandwidth?
Rev. July 2008
3-4
You will need to know the physical addresses set on the card to configure the driver in RSLinx software.
The addresses are set using dip switches on the card, as shown in the following graphic:
DIP Switches
1784-PCC Communications Card A 1784-PCC communications card allows you to connect a programming device such as a laptop/notebook computer to any device with a network access port (i.e. processors, scanners, adapters, etc.) to communicate with other ControlNet products. To configure a driver for a 1784-PCC communications card, a separate driver for the operating system must be installed in order for the communications card to function. The correct driver files must be used for the computers operating system: Windows 95/98/Me systems require a Virtual Device Driver (VXD). Windows NTr software requires an NT driver. Windows 2000 or Windows XP software requires a Windows Driver Model (WDM). Failure to install the correct driver files could result in unpredictable system operation.
3-5
1784-PCIC Communications Card A 1784-PCIC communications card enables PCI local bus-compatible computers to communicate directly with other ControlNet products. To configure a driver for a 1784-PCIC communications card, it is necessary to have the correct software. The drivers for the 1784-PCIC are included with the following software programs: RSLinx Classic software, version 2.54 or later
RSLinx Classic software, version 2.54 or later with SoftLogix on

Windows 2000 or Windows XP software The 1784-PCIC(S) communications card also will not operate correctly without one of the following operating systems: Windows NT 4.0, service pack 3 Windows 98, Windows 2000, or Windows XP
Mention that the S of 1784-PCICS stands for scanner. The 1784-PCICS card is capable of acting as a scanner for the network on SoftLogix systems like a PLC-5 processor or 1756-CNB ControlLogix bridge module.
A 1784-PCIC communications card is a messaging only card that provides ControlNet monitoring and configuration capabilities. A 1784-PCICS communications card provides ControlNet I/O bridging in addition to monitoring and configuration capabilities. A 1784-PCICS communications card is unique for its ControlNet I/O bridging capabilities and must have a node address below maximum scheduled node (SMAX) in order to utilize its ControlNet I/O bridging capabilities that take place during scheduled communications.
Tip "
RSNetWorx for ControlNet software will automatically adjust maximum scheduled node to accommodate the 1784-PCICS communications card if it is not done by the user.
Online Path
The Browse for Network dialog box in RSNetWorx for ControlNet software is used to set an online path between the computer and the network.
Rev. July 2008
3-6
With an online path, the computer will be able to go online to the network and will be able to download or upload configuration data:
Available Networks
Downloading an Offline Configuration File After selecting the appropriate communications path, downloading offline configuration allows you to send all configuration data from the offline file to each of the devices on the network. Uploading Network Configuration After selecting the appropriate communications path, uploading network information, allows you to receive network configuration information, including keeper data and scanlists from the devices.
Heres How
If resources allow, use a blank RSNetWorx for ControlNet file to try to show the students how to configure communications drivers for all three ControlNet communications cards. For the 1784-KTCX and the 1784-PCC, it is possible to demonstrate a mock scenario without the card. However, it is necessary to have a 1784-PCIC card in order to demonstrate how its driver is configured. If workstation devices are inconsistent or have been FLASH updated, it is likely that the network will not match with the offline configuration file. Remind the students that when going online with a configuration file to a network, RSNetWorx software will point out any inconsistencies between the file and the installed network, providing an assurance that application requirements are met.
To go online to a ControlNet network by performing the following tasks: Configure a communications driver Go online to a network As your instructor demonstrates these procedures, follow along in the associated job aid(s).
3-7

Exercise A
In this exercise, you will practice going online to a ControlNet network. Context: The CNET Coasters network has been installed and the offline network configuration file has been created. As the lead designer of the CNET Coaster, it is now your responsibility to configure the communications driver and go online to the network. This will provide all devices on the network with the basic guidelines of how the Coasters network will operate and will also act as a safety check that will ensure the network installed is identical with the network designed to meet the functional specifications. Directions: For help performing steps in this exercise, see the associated job aid(s). 1. Configure the appropriate communications driver for your communications card in RSLinx software. 2. If it is not open already, open the GO1_N200_A1.xc network configuration file. 3. Download the configuration file to go online to the network.
How Did You Do?
Rev. July 2008
E 2008 Rockwell Automation, Inc. All rights reserved. GO1e200
3-8
Answers
Exercise A
1. If you have a KTCX15 communications card and have configured the driver correctly, the driver configuration window should look similar to the following graphic:
Network Address
I/O Base Address as It Was Set Physically on the Card Memory Address as It Was Set Physically on the Card
If you have a PCC communications card and have configured the driver correctly, the driver configuration window should look similar to the following graphic:
Network Address
Rev. July 2008 GO1e200
3-9
If you have a PCIC communications card and have configured the driver correctly, the driver configuration window should look similar to the following graphic:
2. If you have downloaded the configuration successfully, you will receive the following system responses:
A online status icon appears to be scanning in the upper right All channel LEDs on all devices should match the media
redundancy configuration. No status icons appear over the nodes in the network configuration.
hand corner of the RSNetWorx for ControlNet main window.
Tip "
If status icons appear over the nodes in the network configuration, it is likely that the online device is not of the same revision as the device in the offline configuration file or that the EDS file for the device must be registered.
Rev. July 2008
E 2008 Rockwell Automation, Inc. All rights reserved. GO1e200
3-10
Rev. July 2008 GO1e200
Lesson

What You Will Learn
After completing this lesson, you should be able to enter scheduled I/O data connections for Logix5000 controllers to fit the functional specification of an application by performing the following tasks: Add a Logix5000 ControlNet bridge to an I/O configuration Add a Logix5000 I/O module to an I/O configuration Schedule communications for Logix5000 controllers

Having the skills to correctly enter scheduled I/O data connections is important for the following reasons: Entering scheduled I/O data connections defines how and when data is transferred over a network between devices. Scheduling communications enables any scheduled data connection ensuring that data is transferred over a network how and when the scheduled data connection dictates.
Before You Begin
RSLogix 5000 Software

As the main programming and configuration tool for all Logix5000 systems, RSLogix 5000 software is used to perform the following tasks: Create and edit ladder logic Monitor active data online Configure controller communications
Ask if any students have had the opportunity to see or explore RSLogix 5000 software.
Configure I/O modules and devices
Rev. July 2008
E 2008 Rockwell Automation, Inc. All rights reserved. SL1ib200
4-2
Potential Learning Problem: The Ladder Logic Window can also be called the Routine Window. Explain to students that this window can display several programming languages, including ladder logic, function blocks, Sequential Function Chart (SFC), and structured text.
The following graphic is a standard configuration of the RSLogix 5000 main window:
Controller Organizer
Ladder Logic Window
Quick View Pane
Results Window
I/O Configuration
Mention that the I/O configuration can be loosely associated with the Scanlist Configuration window used to configure PLC-5 processors scheduled data connections.
All devices that communicate with a controller must be added to the I/O configuration of the controller project:
Remote Devices Communicating over a ControlNet Network Local Device Communicating over the Backplane
Rev. July 2008 SL1ib200
4-3
I/O Configuration Properties

Explain that these are the major parameters related to establishing a data connection between devices. There are other important parameters that determine the operation of a device, but they are not directly linked to the task of entering scheduled data connections.
The following parameters must be configured in RSLogix 5000 software in order for a device to communicate with a Logix5000 controller: Name Device location
Communications format Electronic keying Revision level Requested packet interval
Communications Format
Clarify that in the I/O configuration, there is no parameter called ownership or connection optimization. Module ownership and connection optimization is established by the communications format that is selected
The communications format selected for an I/O module defines the following components of communications between the controller and the target device: Connection optimization Ownership
Connection Optimization
Stress that because connections are limited, it is important to be aware of the number of connections used and the ways to minimize the connections if required.
Each module in a Logix5000 system supports a limited number of active connections. The number of available connections for a device depends on the type of communications format selected, which defines the connection optimization. The following connection optimization options are available: Direct connection Rack optimization
Rev. July 2008
4-4
Direct Connection A direct connection is a real-time data transfer link between the controller and any I/O module in a local or remote chassis. A direct connection has the following characteristics: If a controller has an I/O configuration that references a slot in the chassis, the controller periodically checks for the presence of the device in the slot:
- If a module is detected in the slot, the controller will

automatically send the module configuration. - If the configuration is appropriate for the module in the slot, a connection is made and operation begins. - If the connection is inappropriate for the module in the slot, the connection is rejected. The controller maintains and monitors the connection. The module sends data at its configured rate. Module status and diagnostic data is available.
Any break in the connections causes the controller to set fault

status bits in the data area for the associated controller. Direct connections are required by all analog modules.
In the graphic, point out that each remote module is sending data at a different rate. Note that these modules can be digital or analog.
Example: Direct Connection With direct connections, data from three analog I/O modules in a remote ControlLogix chassis is sent at three different rates, as shown in the following graphic:
Controller Remote I/O Modules
5 ms 40 ms 20 ms
4-5
Rack Optimization
Stress that a Rack optimization connection is for digital remote I/O only. A direct connection is required for each analog module.
Rack optimization is a link that consolidates the connections between a controller and the digital I/O in a remote chassis. A rack optimized connection has the following characteristics: Data is sent to all rack-optimized digital modules at one rate, as specified by the remote 1756-CNB or 1756-CN2 module.
Mention that you would not want to purchase or use a diagnostic module if you are using a rack-optimized connection. Compare this example which uses one connection to the previous example which required three separate connections.
Device status and diagnostic information is limited. Eight bytes of data are automatically added per chassis slot when
producing arrays. Rack optimized connections can only be used by digital remote I/O modules.
Example: Rack Optimization

If most of the modules in the chassis are non-diagnostic digital I/O modules, select rack optimization for CNB or CN2.
Data from three digital I/O modules in a remote chassis is sent simultaneously at a rate specified by the 1756-CNB or 1756-CN2 module, as shown in the following graphic:
Controller Digital Remote I/O Modules
5 ms (Rate of 1756-CNB)
For remote chassis, rack optimization conserves ControlNet connections and bandwidth. However, it limits all modules to one rate, and it disables the transfer of status and diagnostic information.
Add that a remote chassis can have both a rack-optimized connection and direct connections. Tip
"
Placing remote digital I/O in the same chassis and selecting a Rack-Optimized option for the communications format of the remote communication device conserves connections when using remote I/O.
Remind students that rack optimization is a communications format selected in the module configuration.
Rev. July 2008 E 2008 Rockwell Automation, Inc. All rights reserved. SL1ib200
4-6
Example: Direct Connections vs. Rack Optimization

Indicate that even a minor difference of two to three connections can make a major difference in a large application.
The following table outlines the number of connections used when a direct connection communications format is selected for each module:
Connection Type Controller to local 1756-I/O modules Controller to remote 1756-I/O modules Controller to remote 1756-CNB or 1756-CN2 module Connections Per Module 1 1 1 Module Quantity 2 3 1 Total Total Connections 2 3 1 6
Draw the following conclusion: Although the number of connections for rack optimization is less than the direct connects (6 vs. 3), rack optimization limits diagnostic and fault information. Suggest that students base their communications format selection on the specific needs of their application. Students should consider whether conserving the number of connections is more important than having fault and diagnostic information.
The following table outlines the number of connections when using rack optimization for the same modules:
Connection Type Controller to local 1756-I/O module Controller to remote 1756-CNB or 1756-CN2 module Connections Per Module 1 1 Module Quantity 2 1 Total Total Connections 2 1 3
Ownership
Mention that these connection types closely mirror the connection types for a PLC-5 processor. Like the PLC-5 processor, there is an input-only connection type in theory, but currently it is only available for third-party generic ControlNet modules.
Controllers can be assigned varying levels of ownership that define their relationship to a module. The following connection types connote different levels of ownership a controller can have: Owner connection Listen-only connection
4-7
Owner The owner connection type is a connection between a single target and a controller. An owner connection type has the following characteristics: Every I/O module in a Logix5000 system must be owned by a Logix5000 controller:
- Output modules can have only one owner. - Input modules can have multiple owners. Owners can be local or remote. The owner controller sends configuration data to the module to
define behavior and begin operation. Each module must maintain communications with a minimum of one owner to continue operation.
Multiple owners of the same input module must have the

Tell students to think of multiple owners as alternate owners; if one owner drops out, another owner can take over and send the configuration information.
identical configuration for that module and conform to the following guidelines: - The first owner to establish a connection with the input module sends the configuration data. - The configuration data of all other owners is compared to the first modules configuration data. - If another controller attempts to connect with the module and any configuration parameter is different, the connection for the second controller will not be established and an error will occur. To ensure that the module configurations for two owner controllers projects are identical, copy the configured module from the I/O Configuration folder of one controllers project and paste it in the I/O Configuration folder of the second controllers project.
In the graphic, point out that because one connection is maintained, the input module continues to multicast data.
If an owner breaks connection with the module, the module will continue to multicast data because of the connection maintained by an alternate owner.
Rev. July 2008
4-8
Listen-Only Connection
To summarize, note that an I/O module must always have one owner to communicate.
The listen-only connection type is a connection that can be established only in addition to an owner connection and only after the owner connection has already been launched. A listen-only connection type has the following characteristics: Any module can listen to data from an I/O module even if it is not an owner.
The listen-only controller does not need to hold the I/O modules
configuration. A listen-only controller will not receive configuration data.
Note that having all connections lost may be the desired result. In the graphic, point out that because the owner connection is lost, the listen-only connection is lost and the module stops multicasting data.
If the connection between the owner and the module is broken, all listen-only connections are also lost.
A listen-only communications format uses one of the available 250 connections.
Electronic Keying
Explain that the compatible keying option is the default selection.
Electronic Keying is a feature that automatically compares the expected module (as shown in the I/O Configuration tree) to the physical module before I/O communications begin. Using electronic keying can help prevent communications to a module that does not match the type and revision expected. For each module in the I/O Configuration tree, the user-selected Keying Option determines if and how an electronic keying check is performed. Typically three keying options are available, though for some specific module types fewer options are available. The three options are: Exact Match Compatible Keying Disable Keying Each option has benefits and implications that the user must carefully consider when selecting between these options. For help understanding these options see the Glossary definitions for Electronic Keying, Compatible Module Keying, Disabled Keying, and Exact Match Keying in your Procedures Guide.
4-9
Requested Packet Interval (RPI)

If you are not using this lesson in a Tailored Training course, use the following sections (Requested Packet Interval, Actual Packet Interval, and Network Schedule) as review.
The requested packet interval (RPI) is a user-defined value assigned to every scheduled data connection. It is used to specify how often the data for a particular data connection must be updated. The requested packet interval has the following characteristics: Different requested packet intervals may be assigned for different scheduled connections. Up to eight different update intervals, each rate a binary multiple of the network update time, may be used by different scheduled data connections on the network.
Mention that RSNetWorx for ControlNet software defaults to 1*NUT for scheduled data connections to a digital I/O module and 4*NUT for analog I/O modules.
The requirements of the application should be the primary
determining factor when entering a requested packet interval.
Tip "
Do not try to match the requested packet interval with the network update time. Either let RSNetWorx for ControlNet software select the best possible rate, or enter the highest tolerable rate based on the application. This will utilize scheduled bandwidth more efficiently and possibly provide more unscheduled bandwidth for the network.
Actual Packet Interval (API)

Mention that it is currently not possible to see the actual packet interval for Logix5000 controllers.
The actual packet interval (API) is how often the data for a particular data connection is updated. It is defined by RSNetWorx for ControlNet software and is based on the network update time and requested packet interval defined by the user. The software defines the actual packet interval by comparing the requested packet interval to the closest binary multiple of the network update time that is equal to or faster than the requested packet interval. This binary multiple of the network update time is then assigned as the actual packet interval.
Rev. July 2008
4-10
Example: Actual Packet Interval

ControlNet will set this API rate equal to or faster than the RPI, based on the binary multiple of the NUT which is the next faster rate at which a module can send data. If this cannot be done, ControlNet will provide feedback that the configuration cannot be supported.
If your requested packet interval is 22 ms and your network update time (NUT) is 5 ms, then you could find the actual packet interval by comparing it to the closest binary multiple of the network update time that is equal to or faster than the requested packet interval. Binary multiples (1, 2, 4, 8, 16, 32, 64, 128) of the network update time are 5 ms (1*network update time), 10 ms (2*network update time), 20 ms (4*network update time), 40 ms (8*network update time), etc. The actual packet interval is 20 ms (binary multiple of 4 * network update time of 5), based on the following reasons:
The actual packet interval must be equal to or faster than the
requested packet interval of 22 ms. 40 ms would update the data too slowly, creating a possible hazard to application success. 10 ms would update the data too fast, creating an unnecessary drain on network resources that could be allocated to other scheduled data connections or to unscheduled bandwidth.
Network Schedule
Mention that with PLC-5 processors, scheduling is done by default whenever a RSNetWorx for ControlNet configuration is saved.
When you enter and configure scheduled data connections in RSLogix 5000 software, the software cannot schedule the connections so that their data is transferred over a ControlNet network. In order to schedule a ControlNet network, RSNetWorx for ControlNet software must be used. When the network configuration is saved, RSNetWorx for ControlNet software creates a network schedule. During this process, RSNetWorx for ControlNet software completes the following tasks: Calculates actual packet intervals of each data connection Evaluates the bandwidth requirements for actual packet intervals and data sizes of each data connection Schedules a connection pattern based on the evaluation of each data connection that most efficiently uses scheduled bandwidth
4-11
Example: Network Schedule The following graphic demonstrates a network schedule. The schedule operates in following manner: A. The network updates at an interval of 5 ms as defined by the network update time. B. Connection A updates every network update interval, because its actual packet interval is 5 ms. C. Connection B updates every second network update interval, because its actual packet interval is 10 ms. D. Connection C updates every fourth network update interval, because its actual packet interval is 20 ms. E. No more than two data connections are scheduled during each network update interval, using scheduled bandwidth more consistently. The following graphic shows the schedule:
Time_______5 ms________10 ms________15 ms_______20 ms_______25 ms_______30 ms Network Update Time = 5 ms Actual Packet Interval for Connection A = 5 ms Actual Packet Interval for Connection B = 10 ms Actual Packet Interval for Connection C = 20 ms
Network Update Network Update Network Update Interval 1 Interval 2 Interval 3 Connection A Connection B Connection C Connection A Connection A Connection B Network Update Network Update Network Update Interval 4 Interval 5 Interval 6 Connection A Connection A Connection B Connection C Connection A
Heres How
Open the SL1_N200_DEM1.xc and SL1_N200_DEM1.acd project.. During the demonstration of the following procedures, download the Logix5000 project file and show the students the controller errors that occur prior to scheduling. This will illustrate the importance of scheduling the network and help the students to avoid a common error.
To enter scheduled ControlNet I/O data connections for Logix5000 controllers by completing the following tasks: Add a Logix5000 ControlNet bridge to an I/O configuration Add an I/O module to an I/O configuration Schedule communications for Logix5000 controllers As your instructor demonstrates these procedures, follow along in the associated job aid(s).
Rev. July 2008
4-12
4-13
Exercise A
In this exercise, you will practice entering scheduled I/O data connections for a Logix5000 controller. Context: As the lead designer for the CNET coaster, you must configure the Logix5000 controller at node four to communicate with the analog module at node 3, slot 0. This connection will serve as a speed check for the car after the first hill. The analog module will monitor the speed of the coaster and display it on a meter. If the car is too fast or slow after the first hill, a safety brake will be engaged by the Logix5000 controller and an alarm light will illuminate. Directions: For help performing steps in this exercise, see the associated job aid(s).
Tip "
For help performing steps in RSLogix 5000 software, consult the Start Pages or the online Help. 1. Open SL1_N200_A1.acd using RSLogix 5000 software.
Tip "
To understand the requirements of the application, review the Scheduled I/O Data Connections for the Logix5000 Controller at Node Four section of the: Functional Specification Appendix. Use the Functional Specifications Appendix to configure the modules in this exercise. Failure to use the exact names and node numbers will cause errors in the RSLogix 5000 project.
2. Add the 1794-ACN(R)15 communications adapter at node 3 to the I/O configuration. 3. Add the 1794-IE4XOE2/B analog module at node 3, slot 0 to the I/O configuration. 4. Add the 1794-IB10XOB6/A digital module at node 3, slot 1 to the I/O configuration. 5. Download the project that contains the I/O configuration to the controller at node 4, slot 1.
Rev. July 2008 E 2008 Rockwell Automation, Inc. All rights reserved. SL1e200
4-14
6. Use RSNetWorx for ControlNet to schedule communications. 7. Change the controllers operating mode to Run. 8. To simulate the speed of the roller coaster car, turn the pot on the Logix5000 controller box.
How Did You Do?
Rev. July 2008 SL1e200
4-15
Rev. July 2008
E 2008 Rockwell Automation, Inc. All rights reserved. SL1e200
4-16
Answers
Exercise A When the I/O Configuration is done correctly, it should match the
following graphic:
To verify if the scheduled data connection is functioning properly, complete the following steps:
Verify that the meter changes with changes in the pot. Verify that if the pot is not in the range of 4 to 6, the third light
(speed out of range) in the Logix5000 controller box illuminates to signify an alarm condition.
Rev. July 2008 SL1e200
Lesson

What You Will Learn
After completing this lesson, you should be able to enter messages for Logix5000 controllers by performing the following tasks: Produce and consume a tag for scheduled ControlNet configuration
Enter unscheduled messages Why These Skills Are Important

Poll students to find out if they have programmed messages for any other types of controllers.
Having the skills to correctly and efficiently enter messages is important for the following reasons: Entering messages enables data-sharing between processors and controllers and defines how and when data is shared.
Entering unscheduled messages conserves scheduled bandwidth

for time-critical operations.
Before You Begin

Data connection models apply to both Logix5000 controllers and PLC-5 processors. Data connection models are covered in this lesson and Lesson 6: Entering Scheduled ControlNet I/O Data Connections for PLC-5 Processors. Before beginning this lesson, poll the students to find out if they use Logix5000 controllers or PLC-5 processors more frequently and depending on the poll, go into detail on that technology in more detail. Poll the students to see who has worked with Source-Destination networks.
Data Connection Models

All communications networks are based on one of the following data connection models: The Source-Destination model in which data is sent from one source to be received by one destination The Producer-Consumer model in which data is sent from one source to be received by possibly multiple destinations Source-Destination Model DH+ and Universal Remote I/O networks use the Source-Destination model. Source-Destination networks have the following characteristics: Synchronized action between nodes is very difficult because data arrives at a different time to each node.
Bandwidth is wasted because data must be sent multiple times

when only the destination is different. Multiple networks are needed to transmit I/O data and programming/messaging data.
Rev. July 2008
E 2008 Rockwell Automation, Inc. All rights reserved. UL1ib200
5-2
To transmit data, nodes on a Source-Destination network transmit packets of data that have a source address and a destination address. One of these packets is shown in the following graphic:
Source Address Destination Address Data
Example: Data Transfer in the Source-Destination Model An instructor approaches each student in a classroom individually and tells the student to take a break. As the instructor moves from one student to the next, time is increasing:
Instructor
Student 1
Student 2
Student 3
Student 4
Producer-Consumer Model
Poll the students to see who has worked with a Producer-Consumer network.
ControlNet and DeviceNet networks use the Producer-Consumer model. Producer-Consumer networks have the following characteristics: Multiple nodes can consume the same data at the same time from a single producer so nodes can be synchronized. Bandwidth is used more efficiently because data is sent only once.
Network has a higher degree of determinism and repeatability,

because all nodes receive data simultaneously. To transmit data, nodes on a Producer-Consumer network transmit packets of data that have a connection identifier instead of a source and a destination address. Nodes on the network then filter data using the connection identifiers, consuming the data they can use. One of these packets is shown in the following graphic:
Connection ID Data
Rev. July 2008 UL1ib200
5-3
Example: Data Transfer in the Producer-Consumer Model An instructor announces once to the entire class that it is time for a break. All students have the opportunity to hear the message at the same time:
Instructor
Student 1
Student 2
Student 3
Student 4
Produced and Consumed Tags

Poll the students to determine if they understand what a tag is. If they have not had experience with Logix5000 controllers, explain what a tag is and compare a common tag with a produced tag and consumed tag. The glossary of the ControlNet and RSNetWorx Procedures Guide is an excellent resource for this type of discussion.
Scheduled data that is shared between controllers over a ControlNet network must be sent using produced tags and received using consumed tags. Like I/O data exchange on a ControlNet network, scheduled messages are sent in the following way: A producer sends a packet of data with a connection ID.
The consumer filters all network traffic, looking for connection
IDs it can consume. The consumer finds the produced packet of data and consumes it. When configuring scheduled messages between controllers or processors, select a requested packet interval that is greater or equal to the network update time.
Note that these are the 32-bit data types.
Data that meets the following requirements can be shared by controllers on a ControlNet network without writing ladder logic messages: Tag that is a 32 bit or larger (e.g., DINT, REAL, TIMER, COUNTER, etc.) array of these data types, or user-defined data type
Data that is less than or equal to 500 bytes
Rev. July 2008
5-4
Produced Tag A produced tag is data that is available to one or more controllers.
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 member in the other structure B (e.g., a DINT).
If a user-defined structure is produced, there must be a structure with the identical size and layout in the consuming controller. To ensure accuracy, copy the structures between projects.
Note that if you attempt to create a tag that is too large, the tag will have an error mark in the Edit Tags list.
A tag defaults to be produced for two consumers (controllers). If the tag will only be produced for one controller, change the default value. The additional consumer, even if not used, takes up a connection.
5-5
Tip "
A tag that meets all requirements will have a produce option, specified in the properties of the tag:
Produced
Tag Properties Mention that the tag properties can be viewed when by right-clicking the tag in the tag editor and selecting edit properties. Specify Produced Type and Connections
Consumed Tag A consumed tag receives the produced data in the destination controller. You can only set up one consumed tag to get data from a produced tag in another controller. Setting up more than one consumed tag 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.
Rev. July 2008
5-6
Unscheduled Messages
Unscheduled messages can be used to transfer non-deterministic information that is not time critical. This type of message has the following characteristics: Transmits after all scheduled data has been sent Can be any of the following types of data exchange:
Stress again that scheduled data, such as control and I/O data, is given highest priority on the ControlNet network. Other information, such as programming or upload and download operations, does not interfere with the transport of control and I/O data.
- Unscheduled I/O data transfer through the use of a message

(MSG) instruction - Peer-to-peer messaging through the use of a message (MSG) instruction
Message (MSG) Instruction

A Logix5000 message (MSG) instruction can be used to create unscheduled messages initiated by one Logix5000 controller and sent to another Logix5000 controller, a processor from another control platform, or a 1756 I/O module. A message instruction has the following characteristics: It transfers data asynchronously. Its size depends on the data type and message type sent. The following graphic shows a message instruction:
Note that PLC-5 and SLC 500 processors require an Int data type.
When using a message to send data to or from a Logix5000 controller over a ControlNet network, keep in mind the following guidelines: Both the source and destination tags must be controller-scoped. Both the source and destination tags can be of any data type except Axis, Message, or Motion_Group. If transferring the data from an array, the entire array must be transferred. If it is necessary to send an element of an array, then an alias of the element must be used.
Tip "
5-7
Message Type
The message type parameter defines the operation of a message instruction. Message types are defined by the messages operation and target:
Target Device Logix5000 device or 1756-I/O module Available Message Types CIP Data Table Read CIP Data Table Write Generic CIP PLC-5 Typed Read PLC-5 Typed Write PLC-5 Word Range Read PLC-5 Word Range Write SLC Typed Read SLC Typed Write Block--Transfer Read Block--Transfer Write PLC 3 Typed Read PLC 3 Typed Write PLC 3 Word Range Read PLC 3 Word Range Write PLC 2 Unprotected Read PLC 2 Unprotected Write
PLC-5 processor
SLC 500 processor Block--transfer module over a Universal Remote I/O network PLC--3 processor
PLC--2 processor
CIP Generic Message A generic CIP message can be configured to complete the following operations: Transfer a block of data between Logix5000 controllers
Send configuration data from a Logix5000 controller to an I/O
module to complete the following tasks: - Perform a pulse test on a digital output module - Reset fuses on a digital output module - Reset latched diagnostics on a digital input or output module - Reset latched status on an analog module
Rev. July 2008
5-8
General Parameters
The following general parameters are configured in order to use a message instruction: Source: The tag or logical address currently containing the data to be transferred: - For a Read message type, the source element is the address of the data you want to read in the target device. The addressing syntax of the target device must be used. - 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. Number of Elements: The number of elements to be transferred. The number of elements you read/write depends on the type of data you are using.
Note that a read instruction helps identify the source of the data. Writes do not identify the destination.
Destination Tag: 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 you want to store the data you read from the target device. - For a Write message type, the destination element is the address of the location in the target device where you want to write the data.
Stress that the service codes cannot be determined. They must be taken from the Help system.
For a CIP generic message, the following parameters must also be set to specify the messages function: Service Code: Hexadecimal code for the service to be performed (e.g., resetting latched diagnostics or performing a pulse test). Class Name: Hexadecimal code identifying the I/O module type. Instance Name: Message type ID.
Attribute Name: The attribute to be reset (such as latched status

on an analog module).
Connection Parameters
The following connection parameters are configured in order to use a message instruction: Cache Bit: A bit that instructs the controller to maintain or close the connection after a message has executed.
Tip "
For a continuous message, enabling the cache bit will increase scan time, because the message will only have to be initiated once.
Communications Path: A path that instructs the controller as to

where it will connect. The path can be configured by using the browse feature or numerically.
5-9
Heres How
Open the UL1_N200_DEM1.xc, UL1_N200_DEM1.acd, and UL1_N200_DEM1.rsp project..
If resources allow, demonstrate the following procedures between two Logix5000 controllers. If resources do not allow, it still may be helpful to mock demonstrate for students how to configure a Logix5000 controller to consume a tag for a scheduled message.
To enter messages for Logix5000 controllers by performing the following tasks: Produce and consume a tag for scheduled ControlNet configuration
Enter unscheduled messages

Rev. July 2008
5-10
5-11

Exercise A
In this exercise, you will practice producing and consuming a tag for a scheduled ControlNet configuration. Context: As the lead designer for the CNET coaster, you must configure the Logix5000 controller at node 4, slot 1 to transfer data to the PLC-5 processor at node 1. Because this data is time-sensitive and essential to the safe operation of the coaster, it must be transferred using produced and consumed tags. The Logix5000 controller at node four, slot one will share data when the last car has entered the exit station with the PLC-5 processor at node one, so that the operator knows when to send the next car. This will ensure that two cars are not on the track at the same time. Directions: For help performing steps in this exercise, see the associated job aid(s).
Tip "
For help performing steps in RSLogix 5000 software, consult the Start Pages or the online Help. 1. Open the UL1_N200_A1.acd project file using RSLogix 5000 software. 2. Create a tag called Produced_Data of data type DINT that will transfer the safety data from the Logix5000 controller to the PLC-5 processor.
Tip "
To understand the requirements of the application, review the Scheduled Messages from the Logix5000 Controller at Node Four section of the Functional Specification Appendix. 3. Download the project that contains the produced tag to the controller at node 4, slot 1 and change the controllers operating mode to Run. 4. Schedule the network using UL1_N200_A1.xc configuration file in RSNetWorx for ControlNet software. 5. Open the UL1_N200_A1.rsp project file using RSLogix 5 and download to the processor at node 1.
Rev. July 2008
E 2008 Rockwell Automation, Inc. All rights reserved. UL1e200
5-12
6. To simulate the car entering the exit station, push the PB_2 in the Logix5000 controller box to simulate engaging the brake.
How Did You Do? Exercise B
Turn to the Answers section. In this exercise, you will practice entering an unscheduled message. Context: As the lead designer for the CNET coaster, you must configure the Logix5000 controller at node 4, slot 1 to share exit information with the PLC-5 processor at node 1. Because this data is not time-sensitive, it can be transferred using an unscheduled message. The Logix5000 controller will monitor the exit gate and tally the number of people that exit, and then the controller will update the exit data the PLC-5 processor contains whenever unscheduled bandwidth allows. At the end of the day, this data will be cross-checked with entry data and sent to park operations. Directions: For help performing steps in this exercise, see the associated job aid(s).
Tip "
For help performing steps in RSLogix 5000 software, consult the Start Pages or the online Help. 1. Open UL1_N200_B1.acd using RSLogix 5000 software. 2. Enter an unscheduled message on rung 6 of the main routine for the Logix5000 controller at node 4, slot 1 to write to the PLC-5 processor at node 1.
Tip "
To understand the requirements of the application, review the Unscheduled Messages from the Logix5000 Controller at Node Four section of the Functional Specification Appendix. 3. Download the RSLogix5000 project that contains the unscheduled message to the controller at node 4, slot 1. 4. Change the controllers operating mode to Run. 5. Go online with UL1_N200_A1.rsp, RSLogix5 project at node 1 (This is the same RSLogix 5 project file from Exercise A). 6. To simulate people exiting the gate of the coaster, toggle the first selector switch SS_0 on the Logix5000 controller box.
Rev. July 2008 UL1e200
5-13
How Did You Do?
Rev. July 2008
E 2008 Rockwell Automation, Inc. All rights reserved. UL1e200
5-14
Answers
Exercise A
To verify if the scheduled message is functioning properly, push the third pushbutton in the Logix5000 controller box and the following outputs should occur: The PL_3 in the Logix5000 controller box should illuminate to signify the brakes are engaged and the appropriate data table in the .rsp file shows the data from Produced_Data tag was sent.
N9:0/6
Tip "
Depending on your addressing, your answer may vary from what is shown.
Exercise B
To verify if the unscheduled message is functioning the following will occur:
After switching the SS_0 selector switch on the Logix5000 box

back and forth, double-click data file N7 in RSLogix5. Exit_Data.
Verify that the bit N7:1 contains the same data located in tag
Tip "
Depending on your addressing, your answer may vary from what is shown.
Rev. July 2008 UL1e200
Lesson

What You Will Learn
After completing this lesson, you should be able to enter scheduled I/O data connections for PLC-5 processors to fit the functional specification of an application by performing the following tasks: Enter data files Manually enter scheduled I/O data connections Automatically enter scheduled I/O data connections

Having the skills to correctly enter scheduled I/O data connections is important for the following reasons: Entering data files define where important I/O, configuration, status, and diagnostic data will be stored in a PLC-5 processors memory and serve as an aid when assigning an address to an instruction in a ladder logic program. Entering scheduled I/O data connections define how and when data is transferred over a network between devices.
Before You Begin

Stress that one would not use this window to make connections from a Logix5000 controller.
Scanlist Configuration Window

The Scanlist Configuration window is a tool in RSNetWorx for ControlNett software where data files and scheduled data connections are entered and configured for a PLC-5 processor. A separate Scanlist Configuration window is used for each PLC-5 processor on the network. To enter scheduled data connections for a processor, you must be in the correct window for that processor.
Tip "
Rev. July 2008
E 2008 Rockwell Automation, Inc. All rights reserved. SP1ib200
6-2
The following graphic shows the Scanlist Configuration window and some of its key components:
Node To Be Configured Resource Usage View
Scanlist
Data Files
Data Files
Mention that if a scheduled data connection is made, RSNetWorx for ControlNet software will automatically assign the necessary data files.
Data files are entered by the user in the Scanlist Configuration window and create a virtual map for where I/O, configuration, status, or diagnostic data will be stored in the processor. In order for this map to be transferred to the processor, a network configuration file (i.e., an .xc file) must be associated with the processors project file (i.e., an .rsp file). The following files are used to store data for a PLC-5 processor: Diagnostic file
Poll the students to verify if they know how to associate a file in RSLogix 5 software. If they do not, it may be necessary to walk them briefly through the steps. As you do so, also point out that the RSLogix 5 I/O configuration is populated for the ControlNet network when a configuration file is associated, allowing for the hardware configuration of I/O modules on that network.
Status file Configuration file Data input file (DIF) Data output file (DOF) If the project file is not associated with the network configuration file, the data files will not be transferred to the processors project file. This means there will be no location assigned to store ControlNet-specific data in the processors memory.
Rev. July 2008 SP1ib200
6-3
Diagnostic File A diagnostic file is any unused 40-word integer file starting at word zero. This file has the following characteristics: Contains the following ControlNet diagnostic information specific to the PLC-5 processor:
- Channel errors received - Good packets sent (i.e., the number of times a device is
successful sending data) - Good packets received (i.e., the number of times a device is successful receiving data) Is optional Is transferred to the processor when the network configuration file (i.e., the .xc file) is associated with the processors project file (i.e., the .rsp file). Causes a small amount of additional unscheduled traffic on the network and uses a small amount of PLC-5 processing power Status File
Mention that the meaning of each bit in the status file can be found in the ControlNet Documentation Reference Guide.
A status file is any unused integer file starting at word zero and varies in size depending on the number of data connections (three words for each connection) that are entered. This file has the following characteristics: Contains status information for all of the networks scheduled I/O connections
Is transferred to the processor when the network configuration
file (i.e., the .xc file) is associated with the processors project file (i.e., the .rsp file). Must be entered if there are any scheduled data entries Every data connection will have a data table address starting with the status file number in the Status Address column located in the Scanlist Configuration window:
Data Table Addresses for Status Files
Rev. July 2008
6-4
If any scheduled data is transmitted, this file must be assigned. If this is not done, RSNetWorx for ControlNet software will automatically assign an integer file for the scheduled data.
Configuration File A configuration file has the following characteristics: Is any unused integer file or group of contiguous integer files limited only by available memory and varies in size depending upon a networks configuration.
Is transferred to the processor when the network configuration
file (i.e., the .xc file) is associated with the processors project file (i.e., the .rsp file). Is sent only when establishing a connection. If a data connection uses the configuration file, there will be a data table address in the Config Address column located in the Scanlist Configuration window:
Data Table Addresses and Sizes for Configuration Files
Data Input File (DIF)

Mention that the data input file and data output file can be overlapped so that the data from the data input file will instantly be copied to the data output file without ladder logic. Remind the students that the available size of a data file will vary depending on the PLC-5 processor that is being used.
The data input file is any unused file or group of contiguous integer files. This file is transferred to the processor when the network configuration file (i.e., the .xc file) is associated with the processors project file (i.e., the .rsp file). The following table shows how many files each processor can support:
If the processor is a. . . PLC-5/20Ct PLC-5/40Ct PLC-5/80Ct Then it can support . . . 2 files or 2000 words maximum 3 files or 3000 words maximum 4 files or 4000 words maximum
6-5
Tip "
If you specify 4000 words as the data input file size with a data input file of N34, then RSNetWorx for ControlNet software will automatically create N34, N35, N36, N37, all 1000 words long. All data connections to a PLC-5 processor will use the Input Address column located in the Scanlist Configuration window for addressing information:
Data Table Addresses and Sizes for Data Input Files
Mention that using data input and data output files does not require the user to address devices based on their physical location. This frees up the addressing process for the user but also requires more organizational forethought. Again, remind the students that the available size of a data file will vary depending on the PLC-5 processor that is being used.
All data table addresses found in the Input Address column must be of the file type I (Input) or be specified as a data input file.
Data Output File (DOF) A data output file is any unused file or group of contiguous integer files. This file is transferred to the processor when the network configuration file (i.e., the .xc file) is associated with the processors project file (i.e., the .rsp file). The following table shows how many files each processor can support:
If the processor is a. . . PLC-5/20C PLC-5/40C PLC-5/80C Then it can support . . . 2 files or 2000 words maximum 3 files or 3000 words maximum 4 files or 4000 words maximum
Tip "
If you specify 4000 words as the data output file size with a data output file of N30, then RSNetWorx for ControlNet software will automatically create N30, N31, N32, N33, all 1000 words long.
Rev. July 2008
6-6
All data connections that send data from the PLC-5 processor will use the Output Address column located in the Scanlist Configuration window for addressing information:
Data Table Addresses and Sizes for Data Output Files
All data table addresses found in the Output Address column must be of the file type O (Output) or be specified as a data output file.
Data Connection Models

Data connections were covered in Lesson 5: Entering ControlNet Messages for Logix5000 Controllers. If Lesson 5 was already covered in detail, use this section as review.
All communications networks are based on one of the following data connection models: The Source-Destination model in which data is sent from one source to be received by one destination
The Producer-Consumer model in which data is sent from one

source to be received by possibly multiple destinations Source-Destination Model
Poll the students to see who has worked with Source-Destination networks.
DH+ and Universal Remote I/O networks use the Source-Destination model. Source-Destination networks have the following characteristics: Synchronized action between nodes is very difficult because data arrives at a different time to each node. Bandwidth is wasted because data must be sent multiple times when only the destination is different. Multiple networks are needed to transmit I/O data and programming/messaging data.
6-7
To transmit data, nodes on a Source-Destination network transmit packets of data that have a source address and a destination address. One of these packets is shown in the following graphic:
Source Address Destination Address Data
Example: Data Transfer in the Source-Destination Model An instructor approaches each student in a classroom individually and tells the student to take a break. As the instructor moves from one student to the next, time is increasing:
Instructor
Student 1
Student 2
Student 3
Student 4
Producer-Consumer Model
Poll the students to see who has worked with a Producer-Consumer network.
ControlNet and DeviceNet networks use the Producer-Consumer model. Producer-Consumer networks have the following characteristics: Multiple nodes can consume the same data at the same time from a single producer so nodes can be synchronized. Bandwidth is used more efficiently because data is sent only once.
Network has a higher degree of determinism and repeatability,

because all nodes receive data simultaneously. To transmit data, nodes on a Producer-Consumer network transmit packets of data that have a connection identifier instead of a source and a destination address. Nodes on the network then filter data using the connection identifiers, consuming the data they can use. One of these packets is shown in the following graphic:
Connection ID Data
Rev. July 2008
6-8
Example: Data Transfer in the Producer-Consumer Model An instructor announces once to the entire class that it is time for a break. All students have the opportunity to hear the message at the same time:
Instructor
Student 1
Student 2
Student 3
Student 4
Scheduled Data Connections on a ControlNet Network

Using the Producer-Consumer model, ControlNet scheduled data connections have the following characteristics: Connections are continuous.
Connections transfer data asynchronously to the ladder logic
Mention that data transfer is deterministic. When you look at the actual packet interval field, this is when the data will be transferred. This is one of ControlNet networks strongest features. While other networks may be faster, they cannot guarantee when data will be transferred. For example, Ethernet networks are much faster than ControlNet networks but it is impossible to determine when data will arrive due to the data collisions that occur on Ethernet networks.
program scan, updating in the following way: - The input data is moved from a private memory buffer to the processors input data file for use during the next logical scan. - The data from the output data file is put into a private memory buffer and is sent during the next scheduled communication cycle. Data transfer occurs at the rate displayed in the actual packet interval field of the Scanlist Configuration window.
Scheduled Connection Types

When configuring a scheduled data connection, connection types define the ownership of the data in the target device. The following connection types can be used for scheduled connections: Exclusive Owner
Input Only Listen Only Redundant Owner
6-9
Exclusive Owner
Mention that, unlike Logix5000 controllers, you cannot have two owners.
The Exclusive Owner connection type has the following characteristics: Specifies an independent connection where a single originator controls the output states in the target device
Allows an originator to listen to input states also

If you have an existing Exclusive Owner connection to a target device, you cannot specify another Exclusive Owner or Redundant connection to that same target device.
Input Only The Input Only connection type has the following characteristics: Specifies an independent data connection where an originator receives inputs from the target device and sends configuration data to the network Does not allow originator to send outputs Allows multiple Input Only connections to the target device from different originators
Will continue to receive inputs even if Exclusive Owner

connection is lost Listen Only The Listen Only connection type has the following characteristics: Specifies a dependent connection where an originator receives inputs from the target device but does not send configuration data over the network Functions properly only when an Exclusive Owner data connection exists to the same target device Does not allow an originator to send outputs
Will allow multiple Listen Only data connections to the target

device from different originators
Tip "
All Listen Only connections will be terminated when all associated Exclusive Owner data connections are terminated.
Rev. July 2008
6-10
Redundant Owner
Like redundant media, this connection type is used when downtime is too dangerous or costly.
The Redundant Owner connection type has the following characteristics: Specifies an independent data connection where both a primary and secondary originator share control of outputs and send configuration data to the network
Allows originators to listen to inputs also Allows two redundant connections to the same target device Does not allow an Exclusive Owner connection to the same target
device Only one device has control of outputs and can send configuration data at a time.
Tip "
The Redundant Owner connection type is used with a ControlNet PLC-5 hot backup system.
Requested Packet Interval (RPI)

Mention that RSNetWorx for ControlNet software defaults to 1*NUT for scheduled data connections to a digital I/O module and 4*NUT for analog I/O modules.
The requested packet interval (RPI) is a user-defined value assigned to every scheduled data connection. It is used to specify how often the data for a particular data connection must be updated. The requested packet interval has the following characteristics: Different requested packet intervals may be assigned for different scheduled connections. Up to eight different update intervals, each rate a binary multiple of the network update time, may be used by different scheduled data connections on the network. The requirements of the application should be the primary determining factor when entering a requested packet interval. Do not try to match the requested packet interval with the network update time. Either let RSNetWorx for ControlNet software select the best possible rate, or enter the highest tolerable rate based on the application. This will utilize scheduled bandwidth more efficiently and possibly provide more unscheduled bandwidth for the network.
Tip "
Actual Packet Interval (API)

The actual packet interval (API) is how often the data for a particular data connection is updated. It is defined by RSNetWorx for ControlNet software and is based on the network update time and requested packet interval defined by the user.
E 2008 Rockwell Automation, Inc. All rights reserved. Rev. July 2008 SP1ib200
6-11
The software defines the actual packet interval by comparing the requested packet interval to the closest binary multiple of the network update time that is equal to or faster than the requested packet interval. This binary multiple of the network update time is then assigned as the actual packet interval. Example: Actual Packet Interval
ControlNet will set this API rate equal to or faster than the RPI, based on the binary multiple of the NUT which is the next faster rate at which a module can send data. If this cannot be done, ControlNet will provide feedback that the configuration cannot be supported.
If your requested packet interval is 22 ms and your network update time is 5 ms, then you could find the actual packet interval by comparing it to the closest binary multiple of the network update time that is equal to or faster than the requested packet interval. Binary multiples (1, 2, 4, 8, 16, 32, 64, 128) of the network update time are 5 ms (1*network update time), 10 ms (2*network update time), 20 ms (4*network update time), 40 ms (8*network update time), etc. The actual packet interval is 20 ms (binary multiple of 4 * network update time of 5), based on the following reasons:
The actual packet interval must be equal to or faster than the
requested packet interval of 22 ms. 40 ms would update the data too slowly, creating a possible hazard to application success. 10 ms would update the data too fast, creating an unnecessary drain on network resources that could be allocated to other scheduled data connections or to unscheduled bandwidth.
Network Schedule
Mention that with PLC-5 processors, scheduling is done by default whenever a RSNetWorx for ControlNet configuration is saved.
When the network configuration is saved, RSNetWorx for ControlNet software creates a network schedule. During this process, RSNetWorx for ControlNet software completes the following tasks: Calculates actual packet intervals of each data connection Evaluates the bandwidth requirements for actual packet intervals and data sizes of each data connection Schedules a connection pattern based on the evaluation of each data connection that most efficiently uses scheduled bandwidth
Rev. July 2008
6-12
Example: Network Schedule The following graphic demonstrates a network schedule. The schedule operates in the following manner: A. The network updates at an interval of 5 ms as defined by the network update time. B. Connection A updates every network update interval, because its actual packet interval is 5 ms. C. Connection B updates every second network update interval, because its actual packet interval is 10 ms. D. Connection C updates every fourth network update interval, because its actual packet interval is 20 ms. E. No more than two data connections are scheduled during each network update interval, using scheduled bandwidth more consistently. The following graphic shows the schedule:
Time_______5 ms________10 ms________15 ms_______20 ms_______25 ms_______30 ms Network Update Time = 5 ms Actual Packet Interval for Connection A = 5 ms Actual Packet Interval for Connection B = 10 ms Actual Packet Interval for Connection C = 20 ms
Network Update Network Update Network Update Interval 1 Interval 2 Interval 3 Connection A Connection B Connection C Connection A Connection A Connection B Network Update Network Update Network Update Interval 4 Interval 5 Interval 6 Connection A Connection A Connection B Connection C Connection A
Heres How
Open the SP1_N200_DEM1.xc, SP1_N200_DEM1.rsp, project. During the demonstration of the Heres How tasks, point out what RSNetWorx for ControlNet software will do automatically for the students (i.e., Data files have defaults and all devices can automatically be assigned scheduled data connections.) Include in the discussion that, while these methods are faster, organization and flexibility is sacrificed, which could lead to more time deciphering how devices are addressed when writing ladder logic.
To enter scheduled I/O data connections for PLC-5 processors by performing the following tasks: Enter data files Manually enter scheduled I/O data connections Automatically enter scheduled I/O data connections As your instructor demonstrates these procedures, follow along in the associated job aid(s).
6-13
Exercise A
In this exercise, you will practice entering scheduled I/O data connections. Context: As the lead designer of the CNET Coaster, you must enter scheduled connections in order to transfer the data for two pre-ride safety checks. This will require you to first enter data files to define where data will be stored in the memory of the PLC-5 processor at node 1. Then, you will enter a scheduled data connection manually from the PLC-5 processor to the discrete output module at node 2, slot 1. This data connection will transfer the results of a safety check, verifying that all lap bars are closed. Finally, you will enter a scheduled data connection automatically from the PLC-5 processor to the analog input/output module at node 2, slot 0. The connection will serve as a safety check, verifying that the drive system is up to speed. Directions: For help performing steps in this exercise, see the associated job aid(s). 1. Open the SP1_N200_A1.xc configuration file. 2. Enter data files for the PLC-5 processor at node 1.
Tip "
To understand the requirements of the application, review the Scheduled I/O Data Connections for the PLC-5 Processor at Node One section of the Functional Specification Appendix. 3. Manually enter a scheduled I/O data connection between the PLC-5 processor at node one and the output module at node 2, slot 1 (Safety Check One). 4. Enter a scheduled I/O data connection automatically so that the PLC-5 processor at node 1 can communicate with the analog input/output module at node 2, slot 0. 5. Open the SP1_N200_A1.rsp project file using RSLogix5 software and download the project to the PLC-5 processor at node 1. 6. Change the PLC-5 processors operating mode to Run.
Rev. July 2008
E 2008 Rockwell Automation, Inc. All rights reserved. SP1e200
6-14
7. Turn all the selector switches to an on position in the PLC-5 processor box to simulate the closed safety bars. 8. Dial the analog pot in the PLC-5 processor box to simulate the speed of the drive on hill one. 9. Save the configuration.
How Did You Do?
Rev. July 2008 SP1e200
6-15
Rev. July 2008
E 2008 Rockwell Automation, Inc. All rights reserved. SP1e200
6-16
Answers
Exercise A If you entered the data files according to the Functional

Specification Appendix, your data tables at the bottom of the Scanlist Configuration window should match the following graphic:
If you entered the data connection between the processor and the
discrete output module according to the Functional Specification Appendix, your connection in the Scanlist Configuration window should match the following graphic and the lap bar safety button (i.e., PB_0 in the PLC-5 processor box) should illuminate when all of the lap bar switches (i.e., four selector switches in the PLC-5 processor box are closed):
If you entered the data connection between the processor and the
analog input/output module correctly, your connection in the Scanlist Configuration window should match the following graphic and the analog meter should respond to the pot:
If the drive system is at speed (i.e., between 4 and 6), the drive
system OK light (i.e., PB_1 in the PLC-5 processor box) will be illuminated.
Rev. July 2008 SP1e200
Lesson

What You Will Learn
After completing this lesson, you should be able to enter ControlNet messages for PLC-5 processors by performing the following tasks: Enter scheduled messages for PLC-5 processors Enter unscheduled messages for PLC-5 processors

Poll the students to find out if they have programmed messages for any other types of processors.
Having the skills to enter messages is important for the following reasons: Entering messages enables data-sharing between processors and controllers and defines how and when data is shared. Entering unscheduled messages conserves scheduled bandwidth for time-critical operations.
Before You Begin
Scheduled Messages
Scheduled messages have the following characteristics for ControlNet networks: Scheduled messages allow a ControlNet PLC-5 processor to communicate with any other ControlNet processor or controller with the same priority as I/O data transfer. A scheduled message can be up to 240 words long. A scheduled message can have a message number from one to the maximum allowable number of data connections. The following table shows the maximum allowable number of data connections for PLC-5 processors:
If you have a . . . PLC-5/20Ct PLC-5/40Ct PLC-5/60Ct or PLC-5/80Ct Then there are 64 data connections. 96 data connections. 128 data connections.
Mention that a ControlNet PLC-5 processor can communicate over a ControlNet network with Logix5000 controllers and SLC 500 processors.
A scheduled message does not have a destination associated with
it. Scheduled messages only have an ID; therefore, the destination node must be configured in order to receive the message.
Rev. July 2008
E 2008 Rockwell Automation, Inc. All rights reserved. UP1ib200
7-2
Scheduled Message Data Types

Mention that for all scheduled messages to operate successfully, there must be a processor that is configured to send the message and a peer that is configured to consume the message.
When configuring a scheduled message, the message data type defines the rules for how a PLC-5 processor shares data with the target device. The message data type indicates the processors relationship to the target processor. The following standard message data types are available for messages: Send Data Receive Data From Send Data The Send Data message data type has the following characteristics: Allows a PLC-5 processor to produce (send) scheduled data on a ControlNet network to other devices
Can only function if there is at least one matching Receive Data
From message in a different device Can permit multiple devices to consume (receive the same Send Data message) Cannot specify the requested packet interval. This is done by the consuming device. Receive Data From The Receive Data From message data type has the following characteristics: Allows a PLC-5 processor to consume (receive) scheduled data from another device on a ControlNet network Does not send configuration data
Can only function if there is a matching Send Data message in
another device Determines the requested packet interval in the following manner: - All receivers will receive data at the fastest requested packet interval. - A heartbeat for every Receive Data From message will be created at the requested packet interval of the message.
Rev. July 2008 UP1ib200
7-3
Unscheduled Messages
Stress again that scheduled data, such as control and I/O data, is given highest priority on the ControlNet network. Other information, such as programming or upload and download operations, does not interfere with the transport of control and I/O data.
Unscheduled messages can be used to transfer non-deterministic information that is not time critical. This type of message has the following characteristics: Transmits after all scheduled data has been sent Can be any of the following methods of data exchange:
- Unscheduled I/O data transfers through the use of the

ControlNet I/O (CIO) transfer instruction - Peer-to-peer messaging through the use of a message (MSG) instruction
Message (MSG) Instruction

Mention that the message instruction for a PLC-5 processor does not have the same functionality that a message instruction for a Logix5000 controller has. For example, the PLC-5 processors message instruction cannot read or write to an I/O module.
A PLC-5 message (MSG) ladder logic instruction can be used to create unscheduled messages that are initiated by one ControlNet PLC-5 processor and sent to another processor or controller. A message instruction has the following characteristics: Can originate from any ControlNet PLC-5 processor to any processor or controller on a ControlNet network Does not require a scheduled connection between the originator and the target
Can exist between the same processors that have scheduled

connections Uses a MG data type as a control block
Mapping Data from a PLC- 5 Processor to a ControlLogix Controller

A PLC-5 message (MSG) instruction is used to send data from a PLC-5 data file to data files in other processors and controllers. ControlLogix controllers do not have data files. To accept unscheduled data from a PLC-5 processor, the data must be mapped to a tag in the ControlLogix controller. The mapping is done in the ControlLogix Logic menu.
Rev. July 2008
7-4
A PLC-5 message instruction requires that the target device has a target data file. An example of a valid target device data file is a data location, N7:0, shown in the following graphic:
The MSG instruction also requires that a path for the data be specified. The path tool is called MultiHop. It defines how the data is passed from a ControlNet PLC-5 to the modules that communicate with the destination controller:
7-5
A ControlLogix controller does not have data files. The mapping tool in the ControlLogix software is used to equate the data file number to a tag:
Communications Command The communications command parameter defines the operation of a message instruction. Communications commands are defined by the messages operation and target:
If the target device is a . . . Another PLC-5 processor Logix5000t controller PLC-2r processor Then the available message types are . . . PLC-5 Typed Read PLC-5 Typed Write PLC-2 Unprotected Read PLC-2 Unprotected Write PLC-5 Typed Read from SLC PLC-5 Typed Write from SLC SLC Typed Logical Read SLC Typed Logical Write PLC-3 Word Range Read PLC-3 Word Range Write
SLC 500t processor
PLC-3r processor
Rev. July 2008
7-6
ControlNet I/O (CIO) Instruction

A ControlNet I/O (CIO) ladder logic instruction can be used to read or write data to or from a specific module on a ControlNet network. The ControlNet I/O instruction has the following characteristics: Can originate from any PLC-5 processor to any node on a ControlNet network Does not require a PLC-5 processor to have a scheduled connection to the target node
Can connect to the same node that has scheduled connections Behaves similar to a BTR or BTW block-transfer instruction Uses a CT data type as a control block, containing bits (e.g., .EN,
.DN, and .ER) that behave like their block transfer counterparts Communications Command A ControlNet I/O instruction can be configured to do more than read or write data. Communications commands are defined by the instructions operation and target:
If the communications command is . . . 1794 Read, 1794 Write, 1771 Read, 1771 Write 1794 Fault Action Then its operation is . . . A way of transferring unscheduled data of varying length to or from a module A way to configure what a specific module will do (reset outputs, hold last outputs, or outputs to safe state) when a loss of the Exclusive Owner connection occurs A way to configure what a specific module will do (reset outputs, hold last outputs, or outputs to safe state) when the Exclusive Owner connection processor goes from Run to Program mode An unscheduled method to configure a module An unscheduled method to configure a modules safe-state data
1794 Idle Action
1794 Config Data 1794 Safe State Data
Heres How
Open the UP1_N200_DEM1.xc, UP1_N200_DEM1.rsp, and UP1_N200_DEM1.acd project. If resources allow, demonstrate the following procedures between two PLC-5 processors. If resources do not allow, it still may be helpful to mock demonstrate for students how to configure a PLC-5 processor to receive a scheduled message.
To enter messages for PLC-5 processors by performing the following task: Enter scheduled messages for PLC-5 processors
Enter unscheduled messages for PLC-5 processors

7-7

Exercise A
In this exercise, you will practice entering a scheduled message for a PLC-5 processor. Context: As the lead designer of the CNET Coaster, you must configure the PLC-5 processor at node 1 to share safety-check data with the Logix5000 controller at node 4. The PLC-5 processor will share the status of its lap bar and drive system safety checks with the Logix5000 controller. This will alert the exit station of a ready condition at the start of the ride. Because this data is time-sensitive and essential to the safe operation of the coaster, it will be transferred using a scheduled message. Directions: For help performing steps in this exercise, see the associated job aid(s).
Tip "
For help performing steps in RSLogix 5000 software, consult the Start Pages or the online Help. 1. Open the UP1_N200_A1.xc configuration file. 2. Send a scheduled message from the PLC-5 processor at node 1 to the Logix5000 controller at node 4, slot 1.
Tip "
To understand the requirements of the application, review the Scheduled Messages from the PLC-5 Processor at Node One section of the Functional Specification Appendix. 3. Save and download the RSNetWorx for ControlNet .xc file. 4. Open the UP1_N200_A1.acd project file using RSLogix 5000 software and download the project to the Logix5000 controller at node 4, slot 1. 5. Open the UP1_N200_A1.rsp project file using RSLogix 5 software and download the project to the processor at node 1. 6. To schedule communications for the Logix5000 controller, complete the following actions: A. Go online to the network using RSNetWorx for ControlNet software.
Rev. July 2008
E 2008 Rockwell Automation, Inc. All rights reserved. UP1e200
7-8
B. If the Online/Offline mismatch dialog box opens, select the appropriate option:
If the network is . . . Scheduled Unscheduled Then select . . . Use Online Data (Upload). Use Offline Data (Download).
C. From the Network menu, select Enable Edits.
Tip "
Selecting the Edits Enabled check box in the Network Usage group box will also enable edits. D. Save the configuration. E. To continue scheduling, at the prompt, click Yes. The configuration is saved and downloaded to the ControlNet keeper and the network is scheduled. Any errors or messages are listed in the Messages window. 7. Save the project files running in the Logix5000 controller and PLC-5 processor.
How Did You Do? Exercise B
Turn to the Answers section. In this exercise, you will practice entering an unscheduled message for a PLC-5 processor. Context: As lead designer for the CNET Coaster, you must configure the PLC-5 processor at node 1 to share entry information with the Logix5000 controller at node 4, slot 1. Because this information is not time-critical, it can be transferred using an unscheduled message. The PLC-5 processor will monitor the entry data and tally the number of people that enter, and then the processor will update the entry data that the Logix5000 controller contains whenever unscheduled bandwidth allows. At the end of the day, the data will be cross-checked with exit data and sent to park operations.
Rev. July 2008 UP1e200
7-9
Directions: For help performing steps in this exercise, see the associated job aid(s).
Tip "
For help performing steps in RSLogix 5000 software, consult the Start Pages or the online Help. 1. Open UP1_N200_B1.rsp using RSLogix 5 software. 2. Enter an unscheduled message on rung 6 for the PLC-5 processor at node 1 to write to the Logix5000 controller at node 4.
Tip "
To understand the requirements of the application, review the Unscheduled Messages from the PLC-5 Processor at Node One section of the Functional Specification Appendix. 3. Download the project that contains the unscheduled message to the processor at node 1. 4. Change the processors operating mode to Run. 5. Go online with UP1_N200_A1.acd in node 4, slot 1 (This is the same RSLogix5000 project file from Exercise A). 6. To simulate people entering the entrance gate to the coaster, toggle the first toggle switch (00/10) on the 1771-SIM card several times.
How Did You Do?
Rev. July 2008
7-10
Answers
Exercise A To verify if the scheduled message is functioning properly, verify

that PL_0 and PL_1 illuminate in the Logix5000 controller box when both safety checks are successful (i.e., all safety bars, selector switches in the PLC box, are latched and drive speed, also from PLC, is at speed.) The scheduled message should be configured in the RSNetworx for ControlNet file as the following:
Exercise B
To verify if the unscheduled message is functioning properly, complete the following steps:
The unscheduled message instruction should match the following

graphic:
7-11
RSLogix 5, PLC Ladder Logic
RSLogix 5, Data table Watch this Logix5000 tag increment as you toggle 00/10 on the 1771-SIM Card
You can also configure mapping from PLC-5 processors to Logix5000 controllers in RSLogix5000 software
Rev. July 2008
7-12
Lesson

What You Will Learn
After completing this lesson, you should be able to configure a ControlNet network by performing the following tasks: Configure network properties Go online to the network
Enter scheduled I/O data connections Schedule communications Why These Skills Are Important
Configuring a ControlNet network provides deterministic, repeatable transfers of all application-critical control data (e.g., I/O updates and controller-to-controller interlocking) in addition to supporting transfers of non-time-critical data (e.g., program uploads and downloads and messaging).
Rev. July 2008
E 2008 Rockwell Automation, Inc. All rights reserved. IN1ib200
8-2
Rev. July 2008 IN1ib200
8-3

Exercise A
In this exercise, you will practice configuring a ControlNet network. Context: Due to the success of your first application, you have been assigned to configure the network of another amusement park ride, the CNET Spinner. The application operates in the following manner: Before the ride is clear to start, it is verified that all safety bars are latched. The ride is started from the control booth.
The speed of the ride is controlled by a dial in the control booth. If the force for riders is too great, an alarm will be illuminated
and the ride will be shut down. The ride is stopped from the control booth.
The following graphic below shows the nodes on the network:
Communications Card Node 5
1756-CNB Node 4
1794-ACN Node 3
1794-ACN Node 2
Rev. July 2008
E 2008 Rockwell Automation, Inc. All rights reserved. IN1e200
8-4
The I/O is distributed in the following manner: Node 2 is responsible for the analog inputs for the force of the ride and the analog outputs for the meter.
Node 3 is responsible for the following I/O data: - The analog inputs for speed control and the analog outputs for
the meter. - The digital inputs and outputs for the control panel. Node 4 is responsible for the control of all I/O and the digital inputs for the safety bar check. Directions: For help performing steps in this exercise, see the associated job aid(s).
Tip "
For help performing steps in RSLogix 5000 software, consult the Start Pages or the online Help. 1. Create a new, .xc, configuration file using RSNetWorx for ControlNet software. 2. Configure network properties for the CNET Spinner so that all nodes can communicate every 10 ms. 3. Go online to the network. 4. Open the IN1_N200_A1.acd project file using RSLogix 5000 software. 5. Add the scheduled I/O data connections in the I/O Configuration of the RSLogix5000 project to fulfill the needs of the application. The modules should be named in the following manner:
For the . . . 1794-ACN(R) at node 2 1794-IE4XOE2 at node 2, slot 0 1794-ACN(R) at node 3 1794-IE4XOE2 at node 3, slot 0 1794-IB10XOB6 at node 3, slot 1 1756-CNB at node 4, slot 0 1756-IB16D at node 4, slot 2 Force. Force_Analog. Speed. Speed_Analog. Control_Panel. Local_CNB. Safety_Bars. Name it . . .
Tip "
To understand the requirements of the application and how the I/O is used in the application, review the ladder logic in the .acd project file. 6. Download the project to the controller at node 4, slot 1. 7. Schedule communications. 8. To simulate the closing of the safety bars, switch all the selector switches in the Logix5000 controller box to the on position.
Rev. July 2008 IN1e200
8-5
9. To simulate the starting of the ride, push the PB_0 in the Logix5000 controller box. 10. To simulate the stopping of the ride, push the PB_1 in the Logix5000 controller box. 11. To simulate the speed of the ride, turn the pot in the Logix5000 controller box. 12. To simulate the force of the ride on the riders, turn the pot in the PLC-5 processor box.
How Did You Do?
Rev. July 2008
8-6
Answers
Exercise A
2. If you have configured your network correctly, your Network Parameters property page should match the following graphic:
configuration present on the Media Configuration property page. 3. If you have gone online successfully, you will receive the following system responses:
You should have made no alterations to the default
A online status icon appears to be scanning in the upper
right-hand corner of the RSNetWorx for ControlNet main window. All channel LEDs on all devices should match the media redundancy configuration. 5. If you have entered I/O data connections successfully, your I/O Configuration should match the following graphic:
8-7
You will receive the following system responses:

A. When all safety bars are closed (i.e., all selector switches in the Logix5000 controller box are in the on position) PL_3 illuminates. B. When the ride is started (i.e., PB_0 in the Logix5000 controller box is pressed) PL_0 illuminates to simulate rides state. C. When the ride is stopped (i.e., PB_1 in the Logix5000 controller box is pressed) PL_1 illuminates to simulate rides state. D. The force meter in the PLC-5 processor box changes with changes in the pot. E. The speed meter in the Logix5000 controller box changes with changes in the pot. F. The PB_2 in the Logix5000 controller box illuminates if the force meter in the PLC-5 processor box is beyond a value of 5 in order to simulate the alarm that trips when the force is too great for riders.
Rev. July 2008
8-8
Appendix Functional Specification

Media System
The following functional specifications are for the media system of the CNET Coaster: Downtime will not cause any noticeable loss in ride safety or park revenue. The application, while outside, should be considered a light industrial application. No future nodes will be added. A right-angle T-tap will be used for every node, except the 1756-CNB or 1756-CN2 nodes.
A straight T-tap will be used for any 1756-CNB or 1756-CN2

nodes. The following graphic shows the nodes that will reside on the network and the distance between them:
80 m (262 ft)
160 m (524 ft)
300 m (984 ft)
60 m (196 ft)
PLC-5 Processor Node 1
1794-ACN Node 2
1794-ACN Node 3
1756-CNB Communications or Card 1756-CN2 Node 5 Node 4
Rev. July 2008
E 2008 Rockwell Automation, Inc. All rights reserved. SP1a200
A-2
Network Configuration
The following functional specifications are for the network configuration of the CNET Coaster: In the 1794-ACN(R) Flex I/Ot rack at node two, a 1794-IE4XOE2/B analog input/output module will reside in slot zero and a 1794-OB16/A discrete output module will reside in slot one.
In the 1794-ACN(R) Flex I/O rack at node three, a
1794-IE4XOE2/B analog input/output module will reside in slot zero, and a 1794-IB10XOB6/A discrete input/output module in slot one. In the 1756-CNB or 1756-CN2 chassis, a 1756-CNB or 1756-CN2 will reside in slot zero, a 1756-L55 controller resides in slot one, and a 1756-IB16D/A discrete input module resides in slot two. All nodes except for the programming device should be able to transmit scheduled data. If the device used for programming has scanner capabilities (i.e., a 1784-PCIC(S) communications card), then the device should be able to transmit scheduled data.
The fastest time a node must transmit data is every 10 ms. Nodes will use channel A. 600 m (1966 ft) of standard-PVC CM-CL2 coaxial cable will be
used.
No repeaters will be used.
Scheduled I/O Data Connections for the PLC-5 Processor at Node One
The following parameters meet the functional specifications for all scheduled I/O data connections from the PLC-5 processor at node one. Data Files Data files for the PLC-5 processor at node zero should match the following parameters in order to fulfill the functional specifications of the CNET Coasters network:
Data File Status File Configuration File Data Input File Data Output File N/A 1000 1000 1000 File Size N12 N11 N9 N10 Address
Rev. July 2008 SP1a200
A-3
Safety Check One: Lap Bars Secure The I/O data connection that transfers all data relating to the lap bar safety check for the PLC-5 processor at node one should match the following parameters in order to fulfill the functional specifications of the CNET Coasters network:
Parameter Address Slot Device Name Connection Type Actual Packet Interval Requested Packet Interval Input Address Input Size Output Address Output Size Status Address Configuration Address Configuration Size N/A 01 1794-OB16/A Exclusive Owner 10 ms 10 ms N9:0 1 N10:0 1 N12:0 N11:0 2 Value
Safety Check Two: Drive System Speed Normal The I/O data connection that transfers all data relating to the drive system safety check for the PLC-5 processor at node one should match the following parameters in order to fulfill the functional specifications of the CNET Coasters network:
Parameter Address Slot Device Name Connection Type Actual Packet Interval Requested Packet Interval Input Address Input Size Output Address Output Size Status Address Configuration Address Configuration Size N/A 00 1794-IE4XOE2/B Exclusive Owner 40 ms 40 ms N9:1 5 N10:1 2 N12:3 N11:2 4 Value
Rev. July 2008
A-4
Scheduled Messages from the PLC-5 Processor at Node One
The following parameters meet the functional specifications for all scheduled messages from the PLC-5 processor at node one. Safety Check One and Two Sent to Logix5000 Controller at Node Four, Slot One The message that transfers all data relating to the lap bar and drive system safety check from the PLC-5 processor at node one to the Logix5000 controller should match the following parameters in order to fulfill the functional specifications of the CNET Coasters network:
Parameter Address Slot Device Name Buffer ID Connection Type Actual Packet Interval Requested Packet Interval Input Address Input Size Output Address Output Size Status Address Configuration Address Configuration Size 1 N/A PLC5/40C 1 Send Data N/A N/A N/A N/A N10:3 2 N12:6 N/A N/A Value
Unscheduled Messages from the PLC-5 Processor at Node One
The following parameters meet the functional specifications for all unscheduled messages from the PLC-5 processor at node one. Entry Data Sent to Logix5000 Controller at Node Four, Slot One The message that transfers all data relating to entry figures from the PLC-5 processor at node one to the Logix5000 controller at node four should match the following parameters in order to fulfill the functional specifications of the CNET Coasters network:
Parameter Control Block Communication Command Data Table Address (This PLC-5) Size in Elements Port Number Data Table Address (Target Device) Multihop Multihop Path MG13:0 PLC-5 Typed Write N7:0 1 2 N7:0 Yes From This PLC-5 at From Port 2 to 1756-CNB or 1756-CN2 Node at To Address 4 to From ControlLogix Backplane to 1756 Backplane Slot at To Address 1
Value
A-5
Scheduled I/O Data Connections for the Logix5000 Controller at Node Four
The following parameters meet the functional specifications for all scheduled I/O data connections from the Logix5000 controller at node four, slot one. Logix5000 ControlNet Bridge I/O Configuration The addition of the Logix5000 ControlNet bridge to the I/O configuration of the Logix5000 controller at node four, slot one should match the following parameters in order to fulfill the functional specifications of the CNET Coasters network:
Parameter Name Slot Electronic Keying 0 Compatible Keying Value Local_CNB and CN2
Flex ControlNet I/O Adapter I/O Configuration The addition of the Flex ControlNet I/O adapter to the I/O configuration of the Logix5000 controller at node four, slot one should match the following parameters in order to fulfill the functional specifications of the CNET Coasters network:
Parameter Name Node Chassis Size Communication Format Electronic Keying Speed_Check 3 2 None Compatible Keying Value
Flex Combo Analog Module I/O Configuration The addition of the Flex combo analog module to the I/O configuration of the Logix5000 controller at node four, slot one should match the following parameters in order to fulfill the functional specifications of the CNET Coasters network:
Parameter Name Slot Communication Format Electronic Keying RPI Input Configuration Output Configuration Speed_Check_IO 0 Data Compatible Keying 20 All channels = 0 to 10 V / 0 to 20 mA All channels = 0 to 10 V / 0 to 20 mA Value
Rev. July 2008
A-6
Flex Combo Digital Module I/O Configuration The addition of the Flex combo digital module to the I/O configuration of the Logix5000 controller at node four, slot one should match the following parameters in order to fulfill the functional specifications of the CNET Coasters network:
Parameter Name Slot Communication Format Electronic Keying RPI Remote_Digital 1 Data Compatible Keying 10 Value
Scheduled Messages from the Logix5000 Controller at Node Four
The following parameters meet the functional specifications for all scheduled messages from the Logix5000 controller at node four, slot one. Safety Check Three Sent to the Processor at Node One The produced tag that transfers all data relating to the all-clear safety check from the Logix5000 controller at node four, slot one to the PLC-5 processor at node one should match the following parameters in order to fulfill the functional specifications of the CNET Coasters network:
Parameter Name Data Type Consumers Style produced_data DINT 1 Decimal Value
A-7
Unscheduled Messages from the Logix5000 Controller at Node Four
The following parameters meet the functional specifications for all unscheduled messages from the Logix5000 controller at node four. Exit Data Sent to the Processor at Node One The message that transfers all data relating to exit information from the Logix5000 controller at node four, slot one to the PLC-5 processor at node one should match the following parameters in order to fulfill the functional specifications of the CNET Coasters network:
Parameter Control Block Communication Command Data Table Address (This PLC-5) Size in Elements Data Table Address (Target Device) Path Exit_Message PLC-5 Typed Write Exit_Data 1 N7:1 1,0,2,1 (or Processor) Value
Rev. July 2008
A-8
Appendix Bill of Materials Worksheet

1. Nodes
Device Quantity*
2. Trunk Cable
Type Standard-PVC CM-CL2 Cable Lay-On Armoured or Interlocking Armoured Cable Plenum FEP CMP-CL2P Cable High Flex Cable Other: Quantity*
3. Cable Connectors
Type 1786-BNC Cable connector 1786-BNCJ Bullet Connector Other: Quantity*
4. Repeaters
Type 1786-RPT High Voltage AC and DC Coaxial Repeater 1786-RPTD Low Voltage DC Coaxial Repeater 1786-RPFS Short Distance Fiber Repeater 1786-RPFM Medium Distance Fiber Repeater Quantity*
5. Taps
Type Straight T-Tap
Quantity*
Right-Angle T-Tap
Straight Y-Tap

Type 75 Ohm
(Catalog Number 1786-XT) E 2008 Rockwell Automation, Inc. All rights reserved. BI1a200
Quantity*
Right-Angle Y-Tap
(Catalog Number 1786-TPYR) Rev. July 2008
B-2
Bill of Materials Worksheet
Rev. July 2008 BI1a200
Appendix

PLC-5r Processor Workstation I/O Device Assignments
Lap Bar 1 SS_0 Lap Bar 2 SS_1 Lap Bar 3 SS_2 PB_0 Safety Check 1 PL_0 PB_1 Safety Check 2 PL_1 PB_2 Safety Check 3 PL_2 Start PB_3 SS_3 Start PL_3 Drive Speed
Lap Bar 4
Drive Speed Input
Logix5000t Controller Workstation I/O Device Assignments

Passenger Exit PB_0 SS_0 SS_2 Safety Check 1 PL_0 PB_1 SS_1 SS_3 Safety Check 2 PL_1 Brakes Engaged Car Enters Station Speed Out of Range PB_2 PL_2 PB_3 PL_3
Speed After First Hill
Speed After First Hill Input
Rev. July 2008
E 2008 Rockwell Automation, Inc. All rights reserved. IO1a200
C-2
Rev. July 2008 IO1a200
The following are trademarks of Rockwell Automation, Inc.: 1336 FORCE 1336 PLUS ControlBus Data Highway Plus DriveTools Flex Logix5000 PanelBuilder PLC-5 PowerFlex RSLinx RSView SCANPort SoftLogix 1336 IMPACT CompactLogix ControlLogix DH+ FactoryTalk FlexLogix Logix5550 PanelView PHOTOSWITCH RediSTATION RSLogix RSNetWorx SLC 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 Windows PowerPoint 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.
Catalog Number ABT-CCP170-TIM -- July 2008

Supersedes Catalog Number ABT--CCP170--TIM -- November 2006
E 2008 Rockwell Automation, Inc. All rights reserved. Printed in USA

Abt-Ccp170-Tim 2008-07

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Abt-Ccp170-Tim 2008-07

Încărcat de

Drepturi de autor:

Formate disponibile

ControlNett and RSNetWorxt Software Design and Configuration

Important User Information

Important User Information

Rev. July 2008

E 2008 Rockwell Automation, Inc. All rights reserved.

E 2008 Rockwell Automation, Inc. All rights reserved.

Rev. July 2008

Comments (include lesson title, if applicable):

Exercise: Designing a ControlNet Media System

Configuring an Offline ControlNet Network

Exercise: Configuring an Offline ControlNet Network

Going Online to a ControlNet Network

Exercise: Going Online to a ControlNet Network

Entering Scheduled ControlNet I/O Data Connections for Logix5000 Controllers

Entering ControlNet Messages for Logix5000 Controllers

Exercise: Entering ControlNet Messages for Logix5000 Controllers

Entering Scheduled ControlNet I/O Data Connections for PLC-5 Processors

Entering ControlNet Messages for PLC-5 Processors

Exercise: Entering ControlNet Messages for PLC-5 Processors

Integrated Practice Configuring a ControlNet Network

Exercise: Integrated Practice Configuring a ControlNet Network

Bill of Materials Worksheet

Input/Output Device Assignments

Who Should Attend

Rev. July 2008

E 2008 Rockwell Automation, Inc. All rights reserved. OVEi200

Ability to program ladder logic using Windows-based software

120 minutes 120 minutes 120 minutes 120 minutes

Meeting Course Objectives

E 2008 Rockwell Automation, Inc. All rights reserved.

Rev. July 2008 OVEi200

ControlNet and RSNetWorx Procedures Guide, which contains

PLC-5 Processor Node 1

Logix5000 Controller Node 4

Communications Card Node 5

Rev. July 2008

E 2008 Rockwell Automation, Inc. All rights reserved. OVEi200

E 2008 Rockwell Automation, Inc. All rights reserved.

Rev. July 2008 OVEi200

Lesson Designing a ControlNet Media System

Why These Skills Are Important

Before You Begin

ControlNet Network Overview

Producer-Consumer model network efficiency that permits all

Rev. July 2008

E 2008 Rockwell Automation, Inc. All rights reserved. DE1ib200

Designing a ControlNet Media System

NetLinx Open Architecture

Has a common wire-independent protocol Has open software interfaces

PCMCIA Communications Card

ControlLogix PanelViewt Terminal

1336 FORCE Drive

FOUNDATION Fieldbust Network Transducer

SMP-3t Solid-State Overload

ControlNet Media System Design

E 2008 Rockwell Automation, Inc. All rights reserved.

Rev. July 2008 DE1ib200

Designing a ControlNet Media System

? What is another decision where it is

? What is another decision where it is

Rev. July 2008

E 2008 Rockwell Automation, Inc. All rights reserved. DE1ib200