ABT-CCP170-TIM 2008-07
-
Upload
german-parra -
Category
Documents
-
view
217 -
download
1
Transcript of ABT-CCP170-TIM 2008-07
-
7/28/2019 ABT-CCP170-TIM 2008-07
1/160
Instructor Guide
ControlNett andRSNetWorxtSoftware Designand Configuration
-
7/28/2019 ABT-CCP170-TIM 2008-07
2/160
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 circumstancesthat can cause an explosion in a hazardous environment,which may lead to personal injury or death, propertydamage, or economic loss.
Identifies information that is critical for successfulapplication and understanding of the product.
Identifies information about practices or circumstances
that can lead to personal injury or death, propertydamage, or economic loss. Attentions help you:
identify a hazardavoid a hazardrecognize the consequence
-
7/28/2019 ABT-CCP170-TIM 2008-07
3/160
Important User Information
Labels may be located on or inside the drive to alertpeople that dangerous voltage may be present.
Labels may be located on or inside the drive to alertpeople that surfaces may be dangerous temperatures.
-
7/28/2019 ABT-CCP170-TIM 2008-07
4/160
-
7/28/2019 ABT-CCP170-TIM 2008-07
5/160
Rev. July 2008 E 2008 Rockwell Automation, Inc. All rights reserved.
Summary of Changes
Thank you to all of the instructors who provided input or reviewed
this course. Additional feedback may be provided through the FTIFeedback 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).
Feedback
Overview of Changes
-
7/28/2019 ABT-CCP170-TIM 2008-07
6/160
E 2008 Rockwell Automation, Inc. All rights reserved. Rev. July 2008
-
7/28/2019 ABT-CCP170-TIM 2008-07
7/160
-
7/28/2019 ABT-CCP170-TIM 2008-07
8/160
-
7/28/2019 ABT-CCP170-TIM 2008-07
9/160
Comment Form
Email: [email protected]
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):
-
7/28/2019 ABT-CCP170-TIM 2008-07
10/160
-
7/28/2019 ABT-CCP170-TIM 2008-07
11/160
Page 2
-
7/28/2019 ABT-CCP170-TIM 2008-07
12/160
-
7/28/2019 ABT-CCP170-TIM 2008-07
13/160
Introduction
Course OverviewCourse Purpose I. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Who Should Attend I. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Prerequisites II. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Agenda II. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Meeting Course Objectives II. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Student Materials III. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Application Overview III. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Lessons
Designing a ControlNet Media SystemWhat You Will Learn 1--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Why These Skills Are Important 1--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Before You Begin 1--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NetLinx Open Architecture 1--2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ControlNet Media System Design 1--2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Application Requirements 1--3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Media Needs 1--3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ControlNet Network Media Components 1--4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Trunk Cable 1--5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Coaxial Cable 1--5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Coaxial Trunk Cable Segments 1--6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Example: Maximum Allowable Segment Length 1--7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fiber Optic Cable 1--7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fiber Optic Trunk Cable Segment 1--8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Redundant Media 1--9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cable Connectors 1--11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Repeaters 1--12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Coaxial Repeaters 1--14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fiber Repeaters 1--14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Terminators 1--15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Taps 1--15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Nodes 1--17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Programming Devices 1--17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Heres How 1--18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Example 1--19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Heres How 1--20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Example 1--21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents
-
7/28/2019 ABT-CCP170-TIM 2008-07
14/160
Table of Contentsii
Exercise: Designing a ControlNet Media SystemExercise A 1--23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Bill of Materials 1--24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How Did You Do? 1--25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Answers 1--26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring an Offline ControlNet NetworkWhat You Will Learn 2--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Why These Skills Are Important 2--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Before You Begin 2--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RSNetWorx for ControlNet Main Window 2--2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RSNetWorx for ControlNet Toolbar 2--3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration File 2--3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network Configuration 2--3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Hardware List 2--4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Device Parameters 2--5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .EDS Files 2--5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EDS Wizard 2--6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chassis Configuration 2--7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network Properties 2--7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CTDMA (Concurrent Time Domain Multiple Access) 2--8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Scheduled Bandwidth 2--8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Example: Scheduled Bandwidth 2--9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unscheduled Bandwidth 2--9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Example: Unscheduled Bandwidth 2--10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Guardband 2--10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network Parameters 2--11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network Update Time 2--11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Maximum Scheduled Node 2--12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Maximum Unscheduled Node 2--12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Media Redundancy 2--12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Media Configuration 2--12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network Keeper 2--13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Scanner Signatures 2--14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Heres How 2--15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exercise: Configuring an Offline ControlNet NetworkExercise A 2--17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How Did You Do? 2--17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Answers 2--18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-
7/28/2019 ABT-CCP170-TIM 2008-07
15/160
Table of Contents iii
Going Online to a ControlNet NetworkWhat You Will Learn 3--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Why These Skills Are Important 3--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Before You Begin 3--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RSWho Window 3--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Communications Driver 3--2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ControlNet Communications Cards 3--3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1784-KTCX15 Communications Card 3--3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1784-PCC Communications Card 3--4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1784-PCIC Communications Card 3--5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Online Path 3--5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Downloading an Offline Configuration File 3--6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Uploading Network Configuration 3--6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Heres How 3--6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exercise: Going Online to a ControlNet NetworkExercise A 3--7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How Did You Do? 3--7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Answers 3--8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Entering Scheduled ControlNet I/O Data Connections for Logix5000 ControllersWhat You Will Learn 4--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Why These Skills Are Important 4--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Before You Begin 4--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
I/O Configuration 4--2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
I/O Configuration Properties 4--3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Communications Format 4--3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connection Optimization 4--3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Direct Connection 4--4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Example: Direct Connection 4--4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Rack Optimization 4--5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Example: Rack Optimization 4--5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Example: Direct Connections vs. Rack Optimization 4--6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ownership 4--6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Owner 4--7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Listen-Only Connection 4--8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Electronic Keying 4--8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Requested Packet Interval (RPI) 4--9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Actual Packet Interval (API) 4--9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Example: Actual Packet Interval 4--10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network Schedule 4--10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Example: Network Schedule 4--11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Heres How 4--11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-
7/28/2019 ABT-CCP170-TIM 2008-07
16/160
Table of Contentsiv
Exercise: Entering Scheduled ControlNet I/O Data Connections for Logix5000 ControllersExercise A 4--13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How Did You Do? 4--14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Answers 4--16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Entering ControlNet Messages for Logix5000 ControllersWhat You Will Learn 5--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Why These Skills Are Important 5--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Before You Begin 5--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Source-Destination Model 5--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Example: Data Transfer in the Source-Destination Model 5--2. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Producer-Consumer Model 5--2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Example: Data Transfer in the Producer-Consumer Model 5--3. . . . . . . . . . . . . . . . . . . . . . . . . . .
Produced and Consumed Tags 5--3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Produced Tag 5--4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Consumed Tag 5--5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Unscheduled Messages 5--6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Message Type 5--7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CIP Generic Message 5--7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General Parameters 5--8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connection Parameters 5--8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Heres How 5--9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exercise: Entering ControlNet Messages for Logix5000 ControllersExercise A 5--11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How Did You Do? 5--12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Exercise B 5--12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How Did You Do? 5--13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Answers 5--14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exercise B 5--14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Entering Scheduled ControlNet I/O Data Connections for PLC-5 ProcessorsWhat You Will Learn 6--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Why These Skills Are Important 6--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Before You Begin 6--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data Files 6--2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Diagnostic File 6--3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Status File 6--3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration File 6--4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data Input File (DIF) 6--4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data Output File (DOF) 6--5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-
7/28/2019 ABT-CCP170-TIM 2008-07
17/160
Table of Contents v
Data Connection Models 6--6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Source-Destination Model 6--6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Example: Data Transfer in the Source-Destination Model 6--7. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Producer-Consumer Model 6--7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Example: Data Transfer in the Producer-Consumer Model 6--8. . . . . . . . . . . . . . . . . . . . . . . . . . .
Scheduled Data Connections on a ControlNet Network 6--8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Scheduled Connection Types 6--8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exclusive Owner 6--9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Input Only 6--9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Listen Only 6--9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Redundant Owner 6--10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Requested Packet Interval (RPI) 6--10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Actual Packet Interval (API) 6--10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Example: Actual Packet Interval 6--11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network Schedule 6--11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Example: Network Schedule 6--12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Heres How 6--12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exercise: Entering Scheduled ControlNet I/O Data Connections for PLC-5 ProcessorsExercise A 6--13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How Did You Do? 6--14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Answers 6--16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Entering ControlNet Messages for PLC-5 ProcessorsWhat You Will Learn 7--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Why These Skills Are Important 7--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Before You Begin 7--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Scheduled Message Data Types 7--2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Send Data 7--2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Receive Data From 7--2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unscheduled Messages 7--3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Message (MSG) Instruction 7--3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Mapping Data from a PLC-- 5 Processor to a ControlLogix Controller 7-- 3. . . . . . . . . . . . . . . . . . . . . .
Communications Command 7--5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ControlNet I/O (CIO) Instruction 7--6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Communications Command 7--6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Heres How 7--6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exercise: Entering ControlNet Messages for PLC-5 ProcessorsExercise A 7--7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How Did You Do? 7--8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exercise B 7--8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How Did You Do? 7--9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Answers 7--10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exercise B 7--10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-
7/28/2019 ABT-CCP170-TIM 2008-07
18/160
Table of Contentsvi
Integrated Practice Configuring a ControlNet NetworkWhat You Will Learn 8--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Why These Skills Are Important 8--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exercise: Integrated Practice Configuring a ControlNet NetworkExercise A 8--3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .How Did You Do? 8--5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Answers 8--6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Appendices
Functional SpecificationMedia System A--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network Configuration A--2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Scheduled I/O Data Connections for the PLC-5 Processor at Node One A-- 2. . . . . . . . . . . . . . . . . . . . .Data Files A--2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Safety Check One: Lap Bars Secure A--3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Safety Check Two: Drive System Speed Normal A--3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Scheduled Messages from the PLC-5 Processor at Node One A--4. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Safety Check One and Two Sent to Logix5000 Controller at Node Four, Slot One A--4. . . . . . . . . . .
Unscheduled Messages from the PLC-5 Processor at Node One A--4. . . . . . . . . . . . . . . . . . . . . . . . . .
Entry Data Sent to Logix5000 Controller at Node Four, Slot One A--4. . . . . . . . . . . . . . . . . . . . . . .
Scheduled I/O Data Connections for the Logix5000 Controller at Node Four A--5. . . . . . . . . . . . . . . . . .
Logix5000 ControlNet Bridge I/O Configuration A--5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Flex ControlNet I/O Adapter I/O Configuration A--5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Flex Combo Analog Module I/O Configuration A--5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Flex Combo Digital Module I/O Configuration A--6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Scheduled Messages from the Logix5000 Controller at Node Four A--6. . . . . . . . . . . . . . . . . . . . . . . . .
Safety Check Three Sent to the Processor at Node One A--6. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unscheduled Messages from the Logix5000 Controller at Node Four A-- 7. . . . . . . . . . . . . . . . . . . . . . .
Exit Data Sent to the Processor at Node One A--7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Bill of Materials WorksheetBill of Materials Worksheet B--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Input/Output Device AssignmentsPLC-5 Processor Workstation I/O Device Assignments C--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Logix5000 Controller Workstation I/O Device Assignments C--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-
7/28/2019 ABT-CCP170-TIM 2008-07
19/160
ICourse Overview
E 2008 Rockwell Automation, Inc. All rights reserved.Rev. July 2008OVEi200
Course Overview
This course provides the skills necessary to efficiently design andconfigure 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.
Opening Comments:
Welcome students.
Give administrative details:
1. Class hours2. 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 networkon the job
Course Purpose
Who Should Attend
-
7/28/2019 ABT-CCP170-TIM 2008-07
20/160
II Course Overview
E 2008 Rockwell Automation, Inc. All rights reserved. Rev. July 2008OVEi200
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.
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
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 ahands-on lab environment
-- How Did You Do? -- where to go for feedback onperformance
-- Answers -- answers to exercises
Integrated practices provide an opportunity to perform tasks usingthe skills obtained during the training.
Prerequisites
Poll the class at this time to determinethe amount of networking experience thestudents have. If the class has asignificant amount of networking
experience, the exercises in the coursemay take less time than indicated.
Agenda30 minutes
90 minutes
60 minutes
120 minutes
180 minutes
120 minutes
120 minutes
120 minutes
120 minutes
Meeting Course Objectives
-
7/28/2019 ABT-CCP170-TIM 2008-07
21/160
IIICourse Overview
E 2008 Rockwell Automation, Inc. All rights reserved.Rev. July 2008OVEi200
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.
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.
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:
1794-ACNNode 2
1794-ACNNode 3
Logix5000Controller
Node 4
CommunicationsCard
Node 5
PLC-5Processor
Node 1
Student Materials
Hold up the Procedures Guide. Showthe Table of Contents, one or twoprocedures, and the Glossary. Note thatthis guide will be a good reference whenstudents are completing tasks back onthe job.
Hold up the ControlNet DocumentationReference Guide. Show the list ofpublications and icons in the How ToUse This Guide section. Turn to asection in the guide and point out theidentifying icon.
Application Overview
-
7/28/2019 ABT-CCP170-TIM 2008-07
22/160
IV Course Overview
E 2008 Rockwell Automation, Inc. All rights reserved. Rev. July 2008OVEi200
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 bothstations 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.
Do not go into detail about theapplication at this point, instead openthe CCP170_N200.exe file and simplypresent the functional components of theapplication. The application simulationwill be an excellent tool to illustrate theapplication basics. It is not necessary to
explain which devices control whichfunctions of the application. Thesedetails will be presented in the lessonexercises and the appendix containingthe functional specification.
-
7/28/2019 ABT-CCP170-TIM 2008-07
23/160
Lesson 1
E 2008 Rockwell Automation, Inc. All rights reserved.Rev. July 2008DE1ib200
Designing a ControlNet MediaSystem
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.
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
Producer-Consumer model network efficiency that permits all
devices on the network to simultaneously access the same datafrom a single source
What You Will Learn
Mention that extreme environmentalconditions would include heavyindustrial, high and low temperature,festooning and flexing etc.
Before You Begin
Do not go into detail about dataexchange on ControlNet networks. Thiswill be discussed in detail later.
-
7/28/2019 ABT-CCP170-TIM 2008-07
24/160
1--2 Designing a ControlNet Media System
E 2008 Rockwell Automation, Inc. All rights reserved. Rev. July 2008DE1ib200
NetLinx Open Architecture
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:
EthernetNetwork
ControlNetNetwork
DeviceNettNetwork
FOUNDATIONFieldbustNetwork
SMP-3tSolid-StateOverload
MicroLogixtController
FlowmeterTransducer
Flex I/Ot
PLC-5r Processor
1336 FORCE Drive
PCMCIA Communications Card
PanelViewtTerminal
ControlLogix
Windowsr OperatingSystem with RSViewtSoftware Modem
RSLinxrSoftwareandWindowsOperating
System
PLC-5C Processor
CN2FFLinkingDevice
ControlNet Media System Design
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.
Trace the ControlNet network examplein the graphic and point out some of thecharacteristic devices on the network.For example, the PLC-5 processor, FlexI/O and ControlLogix Gateway are some
characteristic devices that can be foundin the graphic and in the studentsworkstations.
Explain that open indicates that thespecifications and technology are notmanaged or governed by Rockwell
Automation and are available to allControlNet users and vendors throughControlNet International.
Mention that the bulk of ControlNetproblems are media related. Theapplication requirements and medianeeds of a ControlNet network areextremely important in ensuring that thenetwork functions properly.
-
7/28/2019 ABT-CCP170-TIM 2008-07
25/160
1--3Designing a ControlNet Media System
E 2008 Rockwell Automation, Inc. All rights reserved.Rev. July 2008DE1ib200
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
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 isimportant to consider environmental
factors?
Possible Answer: Whether a redundant(back-up) network is necessary.
? What is another decision where it isimportant to consider the physicalrequirements of a network?
Possible Answer: How many cableconnectors are needed.
-
7/28/2019 ABT-CCP170-TIM 2008-07
26/160
1--4 Designing a ControlNet Media System
E 2008 Rockwell Automation, Inc. All rights reserved. Rev. July 2008DE1ib200
ControlNet Network Media Components
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
Trunk CableSection
SegmentCableConnectors
Terminator
Repeater
Taps
Nodes
Do not go into detail about each mediacomponent. The following sections willaddress each component in detail.
-
7/28/2019 ABT-CCP170-TIM 2008-07
27/160
1--5Designing a ControlNet Media System
E 2008 Rockwell Automation, Inc. All rights reserved.Rev. July 2008DE1ib200
Trunk Cable
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
Wide availability
Suitable for most light industrial applications
The coaxial cable must be quad-shield for aControlNet network to operate without noiseinterference. The following graphic shows theidentifying composition of a quad-shield RG-6coaxial cable:
Tape Shield
Braid Shield CenterConductor
OuterSheath
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 . . . Use this type of quad-shield RG-6coaxial cable . . .
Festooning or flexing applications High flex
Moisture resistant applications; direct
burial, with flooding compound, fungus
resistant
Flood burial
Light industria l applications Standard-PVC CM-CL2
Heavy industrial applications Lay-on armored and interlocking armour
High and low temperature applications and
corrosive areas (harsh chemicals)Plenum-FEP CMP-CL2P
Pass around cable examples to thestudents.
Mention that this type of cable isessentially the same cable that is usedin the cable TV industry. However, it isimportant to note the strict ControlNetrequirements or a mistake could hampernetwork operation.
It is best practice to use RG-6 cable forControlNet apps.
Mention that standard PVC CM-CL2cable is inappropriate for a harsh
environment. For example, it was notmanufactured for the wear and tear thatcomes with the constant flexing involvedwith some welding applications and itwill fail.
-
7/28/2019 ABT-CCP170-TIM 2008-07
28/160
1--6 Designing a ControlNet Media System
E 2008 Rockwell Automation, Inc. All rights reserved. Rev. July 2008DE1ib200
The capabilities of the coaxial cable chosen for anapplication should match the environment of theapplication.
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 Terminator
Trunk CableSection
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
-
7/28/2019 ABT-CCP170-TIM 2008-07
29/160
1--7Designing a ControlNet Media System
E 2008 Rockwell Automation, Inc. All rights reserved.Rev. July 2008DE1ib200
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:
2 16 32 48
250 (820)
500 (1640)
750 (2460)
1000 (3280)
Number of Taps
SegmentLengthm
(ft)
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 thefollowing 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
The following table shows types of fiber optic cable and their
recommended uses:
For distance requirements . . . Use this type of fiber optic cable . . .
300 m (984 ft) or less 200 Micron HSC
300 m (984 ft) or more 62.5/125 Micron cable
? How long is the maximum segmentlength for standard quad-shield RG-6coaxial cable with 32 taps?
Answer: Based on the graph, roughly
500 m (1640 ft)
Mention that using fiber optic cablerequires extensive training and practice.
An expert should always check a mediasystem with fiber optic cable before thenetwork goes online.
-
7/28/2019 ABT-CCP170-TIM 2008-07
30/160
1--8 Designing a ControlNet Media System
E 2008 Rockwell Automation, Inc. All rights reserved. Rev. July 2008DE1ib200
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 OpticCable
Fiber RepeaterFiber Adapter
Tap
Fiber Adapter Fiber Repeater
-
7/28/2019 ABT-CCP170-TIM 2008-07
31/160
1--9Designing a ControlNet Media System
E 2008 Rockwell Automation, Inc. All rights reserved.Rev. July 2008DE1ib200
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 iscontingent upon operating temperature forfiber optic cable. Check the valid temperaturerange of the permissible signal loss whencalculating maximum cable length.
Length of the worst case signal delay (total delays through cable
and repeaters) between any two nodes and the network
Permissible length of a worst case signal delay on a ControlNet
network
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 onecable fail.
The following graphic shows how media components fit together to
create a redundant cable segment:
Mention that the amount of signal lossfor cables, connectors, etc. should beavailable from the manufacturer.
"Tip
Trunk Cable A
Trunk Cable B
Devices Supporting Redundant Media
-
7/28/2019 ABT-CCP170-TIM 2008-07
32/160
1--10 Designing a ControlNet Media System
E 2008 Rockwell Automation, Inc. All rights reserved. Rev. July 2008DE1ib200
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 aredundant trunk cable segment will result inmedia errors on the trunk cable segment that isunconnected.
Each trunk cable of a redundant trunk cable segment can contain
different lengths of cable. The total difference in length betweenthe two trunk cables of a redundant trunk cable segment must not
exceed 800 m (2640 ft).
A single nodes redundant trunk cable connections should not be
on different segments. This will cause erratic operation. The
following graphic shows this type of invalid network design:
Trunk Cable A
Trunk Cable A
Trunk Cable B
Trunk Cable B
Node Connected to Two Different Segments
Segment 1
Segment 2
Give some examples of whereredundant media would be warranted.One example would be a steel mill,where hot steel is being run through anapplication. If there is a loss of networkfunction in the application, then the steelwill harden causing massive propertyloss.
-
7/28/2019 ABT-CCP170-TIM 2008-07
33/160
1--11Designing a ControlNet Media System
E 2008 Rockwell Automation, Inc. All rights reserved.Rev. July 2008DE1ib200
Switching a nodes redundant trunk cableconnections (i.e., trunk cable A is connected to theB connector and trunk cable B is connected to theA connector) will cause erratic network operation.The network will function, but it will be difficult
to interpret cable fault indications and locate a badtrunk 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:
Trunk Cable A
Trunk Cable A
Trunk Cable B
Trunk Cable B
Repeaters
Nodes Supporting Redundant Media
Nodes Supporting Redundant Media
Cable Connectors
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.
Mention to the students that thisinformation can be found in theControlNet Networks DocumentationReference Guide and point out thesection for them.
-
7/28/2019 ABT-CCP170-TIM 2008-07
34/160
1--12 Designing a ControlNet Media System
E 2008 Rockwell Automation, Inc. All rights reserved. Rev. July 2008DE1ib200
The following table shows types of cable connectors and their
recommended uses:
To . . . Use this type of cable connector . . .
Attach coaxial cable sections to a taps
BNC connector1786--BNC cable connector
Reserve a space in a coaxial cable for
future installation of a tap or to splice a
cable
1786--BNCJ bullet (jack-to-jack)
Connect two adjacent taps without a
coaxial cable section between them1786-BNCP barrel (plug-to-plug)
Go through grounded panel walls while
maintaining the shield isolation of a coaxial
cable
1786-BNCJI isolated bulkhead
(jack-to-jack)
Cap off installed taps that have yet to be
connected to a node1786-TCAP tap dummy load
Provide a 90_ bend in a coaxial cable
(prevents bending cable excessively)Right angle (jack-to-plug)
Connect a short-distance fiber optic cableto a fiber repeater
V-pin plug and play type connector
Connect a medium, long, or extra-long-
distance fiber optic cable to a fiber repeaterMT-RJ or ST connector
Repeaters
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:
2 16 32 48
250 (820)
500 (1640)
750 (2460)
1000 (3280)
Number of Taps
SegmentLengthm
(ft)
Repeater NotRequired
RepeaterRequired
Pass around a repeater for the studentsto examine, pointing out the differentfeatures of coaxial repeaters and fiberrepeaters and the status indicators.
-
7/28/2019 ABT-CCP170-TIM 2008-07
35/160
1--13Designing a ControlNet Media System
E 2008 Rockwell Automation, Inc. All rights reserved.Rev. July 2008DE1ib200
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 usedto create a point-to-point topology:
Repeaters in Series
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
Mention that although the followingtopology examples show a specificrepeater being used, both fiber andcoaxial repeaters can be used.
Mention that point-to-point topologiesare generally less expensive to create,but offer less stability should one ormore nodes malfunction.
? In what type of an application woulda star topology not be desirable?
Answer: An assembly line. If a devicefails on an assembly line, it is notdesirable for the other devices tocontinue operation. For example, if the
device for one of the conveyors fails, it isnot desirable for the other conveyors tocontinue to operate, creating a pile-up ofproduct.
-
7/28/2019 ABT-CCP170-TIM 2008-07
36/160
1--14 Designing a ControlNet Media System
E 2008 Rockwell Automation, Inc. All rights reserved. Rev. July 2008DE1ib200
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 RepeatersCoaxial 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 opticcable. 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
-
7/28/2019 ABT-CCP170-TIM 2008-07
37/160
1--15Designing a ControlNet Media System
E 2008 Rockwell Automation, Inc. All rights reserved.Rev. July 2008DE1ib200
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.
Fiber repeaters can also be used as a link from a non-hazardous areato 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.
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 orwrong terminators like DH+t or RIO networks
will.
Taps
Taps connect each node on a network to a coaxial trunk cable
segment via an integral 1 m (39.6 in) drop cable.
"Tip
Mention that 50 ohm Ethernetrterminators look the same as 75 ohmControlNet terminators, but a ControlNet
network will not operate correctly whenterminated with the 50 ohm terminators.
? How far can a device be away fromthe trunk cable?
Answer: One meter, the length of thetaps drop cable.
-
7/28/2019 ABT-CCP170-TIM 2008-07
38/160
1--16 Designing a ControlNet Media System
E 2008 Rockwell Automation, Inc. All rights reserved. Rev. July 2008DE1ib200
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.
When planning for future nodes, you should include the trunk cable
and cable connectors for additional nodes when you design the initialnetwork. 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 haveonly one unconnected drop cable per segment formaintenance purposes. If your media systemrequires more than one unconnected drop cable,unused drop cables should be terminated with adummy load, 1786-TCAP.
Taps contain passive electronics and must be usedfor the network to function properly. Othermethods of connecting to a coaxial cable willresult in reflected energy that will disruptcommunications.
Taps are available in the following configurations:
Straight T-Tap Straight Y-Tap Right-Angle T-Tap Right-Angle Y-Tap IP67 T-Tap
"Tip
-
7/28/2019 ABT-CCP170-TIM 2008-07
39/160
-
7/28/2019 ABT-CCP170-TIM 2008-07
40/160
1--18 Designing a ControlNet Media System
E 2008 Rockwell Automation, Inc. All rights reserved. Rev. July 2008DE1ib200
Connection to Networkthrough Network Access
Port
When you connect a programming device to anetwork access port with a 1786-CP cable, it iscounted as a node and must have a uniqueaddress. RSNetWorxt for ControlNet andRSLinx software automatically assign a nodeaddress to the node.
Use the 1786-CP cable when connecting aprogramming device to the network through thenetwork access port. Using an RJ-style cablecould result in possible network failures.
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 Then . . .
Cannot be tolerated because of extreme
consequences (i.e. loss of life, extreme loss
of capital, etc.)
Use redundant media.
Can be tolerated Do not use redundant media.
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):
Heres How
The examples in these demonstrationsshould be performed as a discussion,focusing on the decision-making processinvolved with each of the components ofthe cable system. It is meant more toteach students the problem-solving toolsneeded to complete the tasks than to bean exhaustive demonstration of thetasks.
? What would be an application thatwarrants redundant media?
Answer: A chemical factory where aloss in network operation could create asignificant safety risk.
? Why cant a network have only fiberoptic cable?
Answer: Only a few drives can beconnected to a network using fiber opticcable.
-
7/28/2019 ABT-CCP170-TIM 2008-07
41/160
1--19Designing a ControlNet Media System
E 2008 Rockwell Automation, Inc. All rights reserved.Rev. July 2008DE1ib200
If the application requires . . . Then use . . .
High-noise immunity, interconnecting
equipment in different buildings, long
distances, or intrinsic safety
Both fiber optic and coaxial cable.
None of the above 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 . . .Then use . . .
300 m (984 ft) or less
200 Micron HSC pre-terminated short
distance cable for 1786-RPFS
short-distance repeaters
300 m (984 ft) or more62.5/125 Micron cable for medium or long
distance repeaters
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
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 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 thefollowing 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.
Refer the students to the ControlNetNetwork Documentation ReferenceGuide whenever it is mentioned in theprocedure to get them use to using it asa job aid.
Example
The step numbers in this exampledirectly correspond with step numbers ofthe previous Heres How procedure.
-
7/28/2019 ABT-CCP170-TIM 2008-07
42/160
1--20 Designing a ControlNet Media System
E 2008 Rockwell Automation, Inc. All rights reserved. Rev. July 2008DE1ib200
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
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 thefollowing 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)
Heres How
The examples in these demonstrationsshould be performed as a discussion,focusing on the decision-making processinvolved with each of the components ofthe cable system. It is meant more toteach students the problem-solving toolsneeded to complete the tasks than to bean exhaustive demonstration of thetasks.
-
7/28/2019 ABT-CCP170-TIM 2008-07
43/160
1--21Designing a ControlNet Media System
E 2008 Rockwell Automation, Inc. All rights reserved.Rev. July 2008DE1ib200
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 thenetwork by choosing the appropriate option:
If a programming device must be. . .Then, connect the programming device
to the network using a . . .
Capable of temporarily connecting to the
network from any device
Network access cable through a ControlNet
nodes network access port.
Capable of temporarily connecting to the
network from one locationMaintenance tap on a trunk cable segment.
A permanent node on the network 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.
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.
The step numbers in this example directly correspond with step
numbers of the previous Heres How procedure.
Example
Note and emphasize to the students thatthe step numbers in this exampledirectly correspond with step numbers ofthe previous Heres How procedure.
"Tip
-
7/28/2019 ABT-CCP170-TIM 2008-07
44/160
1--22 Designing a ControlNet Media System
E 2008 Rockwell Automation, Inc. All rights reserved. Rev. July 2008DE1ib200
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 941786-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.
-
7/28/2019 ABT-CCP170-TIM 2008-07
45/160
1--23Exercise: Designing a ControlNet Media System
E 2008 Rockwell Automation, Inc. All rights reserved.Rev. July 2008DE1e200
Exercise: Designing a ControlNetMedia System
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 networkthat 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.
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.
Exercise A
"Tip
-
7/28/2019 ABT-CCP170-TIM 2008-07
46/160
1--24 Exercise: Designing a ControlNet Media System
E 2008 Rockwell Automation, Inc. All rights reserved. Rev. July 2008DE1e200
Bill of Materials
5. Taps
Straight T-Tap(Catalog Number 1786-TPS)
Type Quantity*
Right-Angle T-Tap
(Catalog Number 1786-TPYS)
Straight Y-Tap(Catalog Number 1786-TPR)
Right-Angle Y-Tap(Catalog Number 1786-TPYR)
2. Trunk Cable
Type Quantity*
Standard-PVCCM-CL2 Cable
Lay-On Armouredor InterlockingArmoured Cable
Plenum FEPCMP-CL2PCable
High FlexCable
Other:
3. Cable Connectors
Type Quantity*
1786-RPT HighVoltage AC and DCCoaxial Repeater
6. Terminators (Number of Segments x 2)
Type Quantity*
75 Ohm(Catalog Number
1786-XT)
4. Repeaters
Type Quantity*1786-BNCCable connector
1786-BNCJBullet Connector
1. NodesDevice Quantity*
* If ordering materials for a redundant cable system, quantities must be doubled.
1786-RPTD LowVoltage DC Coaxial
Repeater1786-RPFS Short-Distance Fiber Repeater
Other:
1786-RPFM Medium-Distance Fiber Repeater
1786-RPFA FiberAdapter
Other:
-
7/28/2019 ABT-CCP170-TIM 2008-07
47/160
-
7/28/2019 ABT-CCP170-TIM 2008-07
48/160
1--26 Exercise: Designing a ControlNet Media System
E 2008 Rockwell Automation, Inc. All rights reserved. Rev. July 2008DE1e200
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 CNETCoasters 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.
Answers
-
7/28/2019 ABT-CCP170-TIM 2008-07
49/160
1--27Exercise: Designing a ControlNet Media System
E 2008 Rockwell Automation, Inc. All rights reserved.Rev. July 2008DE1e200
5. Taps
Straight T-Tap(Catalog Number 1786-TPS)
Type Quantity*
Right-Angle T-Tap(Catalog Number 1786-TPYS)
Straight Y-Tap(Catalog Number 1786-TPR)
Right-Angle Y-Tap(Catalog Number 1786-TPYR)
2. Trunk Cable
Type Quantity*
Standard-PVCCM-CL2 Cable
Lay-On Armouredor InterlockingArmoured Cable
Plenum FEPCMP-CL2PCable
High FlexCable
Other:
3. Cable Connectors
Type Quantity*
1786-RPT HighVoltage AC and DCCoaxial Repeater
6. Terminators (Number of Segments x 2)Type Quantity*
75 Ohm(Catalog Number
1786-XT)
4. Repeaters
Type Quantity*1786-BNCCable connector
1786-BNCJBullet Connector
1. NodesDevice Quantity*
* If ordering materials for a redundant cable system, quantities must be doubled.
1786-RPTD LowVoltage DC CoaxialRepeater
1786-RPFS Short-
Distance Fiber Repeater
Other:
1786-RPFM Medium-Distance Fiber Repeater
1786-RPFA FiberAdapter
Other:
PLC-5r Processor
1794-ACN 2
1
1756-CNB 1
ControlNetCommunicationsCard
1
600m(1966ft)
2
1