ABT-SYS-TSM01 2003-02

Configuring Netlinx Networks for Logix5000 Systems

Global Manufacturing Solutions Student Manual

Important User Information

Because of the variety of uses for the products described in this publication, those responsible for the application and use of this control equipment must satisfy themselves that all necessary steps have been taken to assure that each application and use meets all performance and safety requirements, including any applicable laws, regulations, codes and standards. The illustrations, charts, sample programs and layout examples shown in this manual are intended solely for purposes of example. Since there are many variables and requirements associated with any particular Allen-Bradley doesliability) not assume responsibility or liabilityinstallation, (to include intellectual property for actual use based upon the examples shown in this publication. Allen-Bradley publication SGI-1.1, Safety Guidelines for the Application, Installation, and Maintenance of Solid-State Control (available from your local Allen-Bradley office), describes some important differences between solid-state equipment and electromechanical devices that should be taken into consideration when applying products such as those described in this publication. Reproduction of the contents of this copyrighted publication, in whole or in part, without written permission of Allen-Bradley Company, Inc., is prohibited. Throughout this manual, we make references to other technical documents. When applying procedure s, you must consult all the references listed regarding more detailed safety information as it applies to specific circumstances. This material is intended for use by authorized Allen-Bradley instructors, in an Allen-Bradley training center or approved custome r location, using Allen-Bradley approved demonstration hardware and software. Throughout this manual we use notes to make you aware of safety considerations:

!

ATTENTION: Identifies information about practices or circumstances that can lead to personal injury or death, property damage or economic loss.

Attention statements help you to: •

Identify and avoid a hazard

•

Recognize the consequences

Important:

Identifies information that is critical for successful application and understanding of the product.

Suggestion and Comment Form GMS Training Student Manual Configuring Netlinx Networks for Logix5000 Systems Publication A BT -- SYS -- TSM01 Send your comments to:

Manager, Training Development Rockwell Automation 24701 Euclid Ave Euclid, Ohio 44117 U.S.A.

orFAX

(216) 266 --0290

Please provide the following information:

Date:

Page of1

Name: Company & location:

Phone:

Fax #:

Provide your suggestions/comments (include lesson title and part number, if applicable):

E Rockwell Automation. All rights reserved.


Page 2



Table of Contents

Workstations ControlLogix5000 Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DeviceNetWorkstation

1796 -- CLCUSTOM

........ ........ ........ ........ ......

ABT -- TDDNET1

ControlNetWorkstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ABT -- TDCNET1

CommunicationsWorkstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ABT -- TD05

Lessons Communicating with a Logix5000

Controller . . . . . . . . . . . . . . . . . . . . . . . . . . .

WhaYtoW u Lillearn ......... ........ ......... ......... ......... ......... ..... WhyTheseSkillsAreImportant ......... ......... ......... ......... ........ .... KTeryms ......... ......... ......... ......... ......... ......... ........ . BefoY reoBuegin ......... ......... ......... ......... ......... ......... ...... Logix5000CommunicationsOptions ......... ......... ......... ......... ........

1- 1 1 -- 1 1-- 1 1 -- 1 1 -- 1 1--1

SeriaClonnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 -- 2 NetworCk onnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 -- 2 CommunicationsNetworks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 -- 3 NetwoTrkypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 -- 3 NetwoM rkodels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 -- 4 Example: Data Transfer in the Producer/Consumer Model ......... ........ ......... . 1 -- 5 Example: Data Transfer in the Source/Destination Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 -- 5 NetwoO rkptions ......... ......... ........ ......... ......... ......... ..... 1 -- 6 ControlLogixt Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 -- 6 RSLinxt Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 -- 7 MBeanru ........ ......... ......... ......... ......... ......... ........ . 1 -- 8 Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 -- 8 RSWhWoindow ......... ......... ......... ......... ......... ......... ... 1 -- 8 Uploading, Downloading, and Going Online to a Logix5000 Controller . . . . . . . . . . . . . . . . . . . . . 1--9 OfflinvesO. nline ........ ......... ......... ......... ......... ......... ... 1-- 10 OnlinSetatus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OfflinSetatus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OnlinW e arning ......... ......... ......... ......... ......... ......... ... CommunicationP s ath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ControllerOperatingModes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-- 10 1-- 10 1-- 10 1-- 11 1-- 11

ii

Table of Contents

ManuallyChangingControllerOperatingMode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--12 RemotelyChangingControllerOperatingMode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-- 13 HerH e’osw ........ ......... ......... ......... ......... ......... ........ ... 1 -- 13 ExercAise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 -- 17 ExercBise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 -- 19 HoDwYidoDuo? ......... ......... ........ ......... ......... ......... ....... 1 -- 19 ExercA ise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 -- 20 Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--20

Creating Devicenet Whaa YtoW u Lillearn

. .N . .e. .tw . . o.r.k.C . .o. .n. f.ig.u. .r.a. t.i.o. n . . . .. ..... .. .. .. .. .. .. . . .. .. ... . .. .. ..... . .... .. .. .. ... .. . . . 2--1 2 - 1 WhyTheseSkillsAreImportant ........ ......... ......... ......... ......... .... 2 -- 1 Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--1 BefoY reoBuegin ......... ......... ........ ......... ......... ......... ....... 2--1 DeviceNeDtrivers ......... ........ ......... ......... ......... ......... .... 2--2 NetworPkroperties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-- 4 NetworkConfigurationOptions ........ ......... ......... ......... ......... .... 2-- 4 OfflineNetworkConfiguration ........ ......... ......... ......... ........ ...... 2--5 OnlineNetworkConfiguration ........ ......... ......... ......... ........ ...... 2-- 6 UploadingandDownloading ......... ......... ......... ......... ........ ...... 2-- 7 BrowsinNagetwork ......... ......... ......... ......... ......... ........ ... 2--7 HerHeo’sw ........ ......... ......... ......... ......... ......... ........ ... 2--8 Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--9 HoDwYidoDuo? ......... ......... ........ ......... ......... ......... ....... 2 -- 12 Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 -- 14 Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--14

Mapping DeviceNet Data in a 1756-DNB Scanner Module

........ ........ ...

3 -1

WhaYtoW u Lillearn ........ ......... ......... ......... ......... ........ ...... 3--1 WhyTheseSkillsAreImportant ........ ......... ......... ......... ......... .... 3 -- 1 ReviewofBasicDeviceNetConcepts ......... ......... ......... ........ ......... 3-- 1 BefoY reoBuegin ......... ......... ........ ......... ......... ......... ....... 3--1 1756-DNBScanneM r odule ........ ......... ......... ......... ......... ....... 3-- 2 Assigning a Node Address and a Baud Rate to a 1756-DNB Scanner Module . . . . . . . . . . . . . . . 3--3 NetworkConfigurationReview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-- 3 OnlineConnectiontoaDeviceNetNetwork ......... ......... ......... ......... .... 3-- 4 Configuringa1756-DNBScannerModule ......... ......... ......... ........ ...... 3-- 4 CreatinSagcanlist ......... ........ ......... ......... ......... ......... .... 3-- 5 MessagTeypR e eview ......... ........ ......... ......... ......... ......... . 3-- 6 Mapping Input and Output Data in a 1756-DNB Scanner Module ........ ......... ....... 3-- 6 DaMtaP aplan ......... ......... ........ ......... ......... ......... ....... Automatic Mapping Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ManuaMl appingReview ......... ......... ......... ......... ......... ........ WorDdatM a apping ......... ......... ......... ......... ......... ........ ... IdentifyingLogix5000Tags ........ ......... ......... ......... ......... .......

3--7 3-- 8 3--9 3-- 9

3--7

iii

Table of Contents

Example:DeviceNetAddresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HerH e’osw ......... ......... ........ ......... ......... ......... ......... .. Mapping Input Data for a RediSTATION Operator Interface ........ ......... ......... .. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mapping Input Data for a Series 9000 Photoelectric Sensor ........ ......... ......... .. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Output Mapping for a RediSTATION Operator Interface Module ........ ......... .... Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HoDwYidoDuo? ......... ......... ......... ......... ......... ......... ...... Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring a Logix5000 Controller to Control a DeviceNet Device

3 -- 9 3-- 10 3-- 10 3-- 11 3-- 11 3-- 13 3-- 13 3-- 15 3-- 15 3-- 16

3-- 20 3-- 22 3--22

........ ....

4-1

WhaYtoW u Lillearn ......... ........ ......... ......... ......... ......... ..... 4 -- 1 WhyTheseSkillsAreImportant ......... ......... ......... ......... ........ .... 4-- 1 Adding a 1756-DNB Scanner Module to the I/O Configuration of an RSLogix 5000 Project . . . . . . 4--1 BefoY reoBuegin ......... ......... ......... ......... ......... ......... ...... 4 -- 1 Example:InputandOutputWords ......... ......... ......... ......... ........ 4--2 1756-DNBScannerModuleDefinedTags ......... ......... ......... ......... ..... 4 -- 3 CommandRegisteBr its ........ ......... ......... ......... ......... ........ . 4 -- 3 SBeittting ......... ......... ......... ......... ......... ......... ........ . 4 -- 4 64-BTaitbles ......... ......... ........ ......... ......... ......... ........ 4 -- 4 Alias Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--4 WordDataMappingReview ........ ......... ......... ......... ......... ...... 4-- 5 HerHeo’sw ......... ......... ........ ......... ......... ......... ......... .. 4 -- 5 WritingLadderLogictoControlaDeviceNetDevice ......... ......... ........ ....... 4 -- 6 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 -- 6 ExercAise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 -- 6 HoDw YidoDuo? ......... ......... ......... ......... ......... ......... ...... 4 -- 8 ExercBise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 -- 9 HoDwYidoDuo? ......... ......... ......... ......... ......... ......... ...... 4-- 12 ExercA ise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-- 14 Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--14 ExercB ise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-- 16

Configuring an Offline ControlNet

N e tw o r k . . . . . . . . . . . . . . . . . . . . . . . . . . . .

WhaYtoW u Lillearn ......... ........ ......... ......... ......... ......... ..... WhyTheseSkillsAreImportant ......... ......... ......... ......... ........ .... t. o. .ft.w. a. r.e. . . .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. . . BeRSNetWorx foY reoBuegin t fo. rC . .o.n.t.ro. l.N. eS RSNetWorxforControlNetMainWindow ......... ......... ......... ........ .... RSNetWorxforControlNetToolbar ......... ......... ......... ......... ........ ConfiguratioFnile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5- 1 5 -- 1 5-- 1 5 -- 15 -- 1 5-- 2 5-- 2 5 -- 3

iv

Table of Contents

NetworC k onfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-- 3 HardwaLreist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--3 DevicPearameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-- 4 EFDilSes ........ ......... ......... ......... ......... ......... ........ 5--4 EW DSizard ......... ......... ........ ......... ......... ......... ....... 5--5 ChassiC s onfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-- 6 NetworPkroperties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-- 6 CTDMA(ConcurrentTimeDomainMultipleAccess) ......... ......... ......... .... 5-- 7 ScheduleB d andwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--7 Example:ScheduledBandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-- 8 UnscheduledBandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--8 Example:UnscheduledBandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--9 Guardband . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--9 NetworPkarameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-- 9 NetworU k pdatTeime ......... ......... ......... ......... ......... ........ 5--10 MaximumScheduledNode ........ ......... ......... ......... ........ ...... 5--10 MaximumUnscheduledNode ......... ......... ......... ......... ........ ... 5--10 MediR a edundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--11 MediaConfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--11 HerH e’osw ........ ......... ......... ......... ......... ......... ........ ... 5 -- 12 Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 -- 12 HoDwYidoDuo? ......... ......... ........ ......... ......... ......... ....... 5 -- 12 Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 -- 14 Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--14

GoingOnlinetoaControlNetNetwork

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6- 1

WhaYtoW u Lillearn ........ ......... ......... ......... ......... ........ ...... 6--1 WhyTheseSkillsAreImportant ........ ......... ......... ......... ......... .... 6 -- 1 RSLinSxoftware ........ ......... ......... ......... ......... ........ ...... 6--1 BefoY reoBuegin ......... ......... ........ ......... ......... ......... ....... 6--1 RSWhWoindow ......... ........ ......... ......... ......... ......... .... 6-- 1 CommunicationD s river . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-- 2 ControlNetCommunicationsCards ........ ......... ......... ......... ......... . 6-- 3 1784-KTCX15CommunicationsCard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-- 3 1784-PCCCommunicationsCard ......... ......... ......... ........ ......... 6-- 4 1784-PCICCommunicationsCard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-- 5 OnliPnaeth ......... ......... ......... ......... ......... ......... ........ 6--6 HerHeo’sw ........ ......... ......... ......... ......... ......... ........ ... 6--6 Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--7 HoDw YidoDuo? ......... ......... ........ ......... ......... ......... ....... 6--7 Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6--8

6--8

v

Table of Contents

Entering Scheduled Controlnet I/O Data Connections for Logix5000 Controllers . . WhaYtoW u Lillearn ......... ........ ......... ......... ......... ......... ..... WhyTheseSkillsAreImportant ......... ......... ......... ......... ........ .... RSLogi5x000Software ........ ......... ......... ......... ......... ........ . BefoY reoBuegin ......... ......... ......... ......... ......... ......... ...... I/O Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I/OConfigurationProperties ........ ......... ......... ......... ........ ....... CommunicationsFormat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ConnectionOptimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7- 1

7 -- 1 7-- 1 7 -- 1 7 -- 1 7 -- 2 7 -- 3 7 -- 3 7 -- 3

D cCtpolnenD 77----44 Exiraem : eirceticoC tnonn.e.c.t.io. n. . . . .. .. .. .. .. .. .. .. . . .. .. .. .. .. .. .. .. . . .. .. .. .. .. .. .. .. . . .. .. .. .. .. .. .. .. . . .. .. .. .. .. .. .. . . .. .. .. . RacOk ptimization ......... ........ ......... ......... ......... ......... .. 7 -- 5 ExampleR : ackOptimization ......... ......... ......... ......... ........ .... 7 -- 5 Example: Direct Connections vs. Rack Optimization ........ ......... ......... ..... 7 -- 6 Ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 -- 6 Owner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 -- 7 Listen-OnlyConnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 -- 8 ElectronK iceying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 -- 8 RequestedPacketInterva(l RPI) ........ ......... ......... ......... ........ .... 7-- 9 Actual Packet Interval (API) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--9 Example:ActualPacketInterval ........ ......... ......... ......... ......... .. 7 -- 10 NetworSkchedule ......... ......... ......... ......... ......... ........ .... 7-- 10 ExampleN : etworkSchedule ......... ......... ......... ......... ........ .... 7-- 10 HerH e’osw ......... ......... ........ ......... ......... ......... ......... .. 7-- 11 Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-- 12 HoDwYidoDuo? ......... ......... ......... ......... ......... ......... ...... 7-- 12 Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-- 14 Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--14

Configuring an Ethernet Networkin aLogix5000System

. . . . . . . . . . . . . . . . . . 8- 1

WhaYtoW u Lillearn ......... ........ ......... ......... ......... ......... ..... WhyTheseSkillsAreImportant ......... ......... ......... ......... ........ .... EtherneN t etworkOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BefoY reoBuegin ......... ......... ......... ......... ......... ......... ...... TCP/IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ethernet/IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ComponeTnet rms ......... ......... ......... ......... ......... ......... ... Addressing Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assigning a Computer I P Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DeterminingaComputerIPAddress ......... ......... ......... ........ ....... 1756-ENEM T odule ........ ......... ......... ......... ......... ......... ... HealthandStatusIndicators ......... ......... ......... ......... ........ .... AUI (Attachment Unit Interface) Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8 -- 1 8-- 1 8 -- 1 8 -- 1 8 -- 2 8 -- 2 8 -- 2 8 -- 2 8 -- 2 8--3 8-- 6 8 -- 6 8 -- 7

8--5

8--7

vi

Table of Contents

1B0aseC T onnector ......... ........ ......... ......... ......... ......... . 8-- 7 MAC(MediaAccessControl)ID ........ ......... ......... ......... ......... . 8--7 1756-ENETModuleIPAddress ........ ......... ......... ......... ......... .... 8-- 8 Assigning an IP Address to a 1756-ENET Module Using a BootP Utility . . . . . . . . . . . . . . . . . . 8--8 Assigning an IP Address to a 1756-ENET Module Using RSLinx Software . . . . . . . . . . . . . . . . 8--9 Adding a 1756-ENET Module to the I/ O Configuration of an RSLogix 5000 Project . . . . . . . . . . 8--9 Testinga1756-ENETModuleIPAddress ......... ......... ......... ........ ...... 8--10 ConfiguringaTCP/IPCommunicationsDriver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 -- 10 ViewingDataUsingtheRSLinxDataMonitor ......... ......... ........ ......... ... 8--11 Viewing Module Information Using 1756-ENET/B Module Web Pages . . . . . . . . . . . . . . . . . . . . . 8-- 11 HerH e’osw ........ ......... ......... ......... ......... ......... ........ ... 8 -- 12 Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 -- 13 HoDwYidoDuo? ......... ........ ......... ......... ......... ......... ....... 8 -- 14 Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 -- 16 Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8--16

vii

Table of Contents

Appendix NodeAddressAssignments

........ ........ ......... ........ ........

Input/OutputDeviceAssignments

........ ......... ........ ........ ....

160SSCVariableSpeedDriveData Assembly

....... ......... ........ ....

A- 1 B- 1 C- 1

Table1:Assembly21DataFormat

......... ......... ......... ......... ........

C -- 1

Table1:Assembly71DataFormat

......... ......... ......... ......... ........

C -- 1

FunctionaS l pecification

........ ......... ........ ........ ........ ...

D- 1

M 1.edSiaystem ......... ......... ......... ......... ......... ......... ...... D -- 1 2N. etworkConfiguration ......... ........ ......... ......... ......... ......... .. D -- 2 3. Scheduled I/O Data Connections for the PLC-5 Processor at Node One ........ ......... .. D--2 DFatilaes ......... ......... ........ ......... ......... ......... ........ D -- 2 SafetyCheckOne:LapBarsSecure ......... ......... ......... ........ ....... D-- 3 SafetyCheckTwo:DriveSystemSpeedNormal ........ ......... ......... ........ D -- 3 4. Scheduled Messages from the PLC-5 Processor at Node One ......... ......... ........ D-- 4 Safety Check One and Two Sent to Logix5000 Controller at Node Four, Slot One . . . . . . . . . . . D--4 5. Unscheduled Messages from the PLC-5 Processor at Node One ......... ........ ....... D -- 4 Entry Data Sent to Logix5000 Controller at Node Four, Slot One ......... ......... ..... D -- 4 6. Scheduled I/O Data Connections for the Logix5000 Controller at Node Four ......... ....... D--5 Logix5000ControlNetBridgeI/OConfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D -- 5 FlexControlNetI/OAdapterI/OConfiguration ......... ......... ........ ......... . D -- 5 FlexComboAnalogModuleI/OConfiguration ......... ......... ........ ......... . D-- 5 FlexComboDigitalModuleI/OConfiguration ......... ......... ........ ......... . D -- 6 7. Scheduled Messages from the Logix5000 Controller at Node Four ......... ......... ..... D--6 Safety Check Three Sent to the Processor at Node One ........ ......... ......... .. D -- 6 8. Unscheduled Messages from the Logix5000 Controller at Node Four ........ ......... .... D-- 7 ExitDataSenttotheProcessoratNodeOne ......... ......... ........ ......... . D -- 7

Input/OutputDeviceAssignments

........ ......... ........ ........ ....

PLC-5r ProcessorWorkstationI/ODeviceAssignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logix5000 Controller Workstattion I/O Device Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . .

E- 1 E -- 1 E -- 1

viii

Table of Contents

Lesson

1

Communicating with a Logix5000 Controller What You Will Learn

After completing this lesson, you will be able to communicate with a Logix5000 controller by performing the following tasks: •

Identify communications options in a Logix50 00 system

•

Upload, download, and go online to a Logix500 0 controller

•

Select and change a Logix5 000 controller’s operating mode

Why These Skills Are Important Establishing communications with the correct controller and ensuring that the controller is in the proper operating mode is critical to the operation and safety of a process or machine. If communications is established with the incorrect controller, or if the controller is in the wrong operating mode, problems with efficiency or late delivery of time sensitive data can occur. This can cause damage to equipment or harm to personnel.

Before You Begin

Key Terms Communications: The transfer of data between two or more devices. Driver: A software subroutine that handles the logic for communicating with a specific type of external device. Computers require drivers to communicate on a network. Node: A physical device on a communications network (e.g., controller, communications module, programming device). Network: A group of devices (i.e., nodes) connected by some type of communications medium.

Logix 5000 Communications Options There are two basic physical connectio ns for making a programming device (computer) communic ate with a Logix5000 controller:

Rev. September 2002

•

Serial connection

•

Network connection

E 2002 Rockwell Automation. All rights reserved. COMs56

1--2

Communicating with a Logix5000 t Controller

Serial Connection

A serial connection is a direct connection from one device to another through which data is transferred as a stream of electronic bits. Serial communications between a computer and controller have the following characteristics: •

Data transmission is limited to 50 ft (15.2 m) .

•

The serial communications port is loca ted on the front of the controller module.

•

Data is passed at a slower rate than with netw ork connections.

In Logix5000 systems, a serial connectio n involves running a serial cable between the serial ports on each device: ControlLogix Chassis with Controller Computer

Serial Cable (1756-CP3)

"

Serial Port (RS-232)

Serial connections are used for non-time critical tasks, such as testing programs, troubleshooting, and maintenance. Network Connection

The most common way to connect a computer to a controller is via a network. Severa l network options are available that allow communications between devices to take place over a great distance. A network connection using two networks (ControlNett and EtherNet/IP t) for communications between multiple nodes is shown in the following graphic: Node Node

Node

ControlNet Network Communications

E 2002 Rockwell Automation. All rights reserved.

Ethernet Network Communications

Rev. September 2002 COMs56


1 -- 3

Communications Networks Logix5000 systems utilize one or more communicatio ns networks to transfer data throughout the system. Network Types

Different types of networks are available to carry out the individual tasks that need to be completed. These three networks are used with Logix5000 systems: •

Information Network: Provides fast communications within plants and to outside sites. This option is ideal for the following tasks:

----•

Network management and maintenance Large data file transfer Internet connection Device programming and configuration

Control Network: Offers consistently reliable communications and constant, real-time performanc e for the following tasks:

-- Messaging between devices with equal ac cess to data -- Connection to controllers, comp uters, drive and moti on equipment, etc.

-- Device programming and configuration •

Device Network: Provides integration of individual discrete or process devices for the following tasks:

-- Device-level diagnostics -- Connection to multiple vendor’ s devices -- Reduction of wiring to the controller

Rev. September 2002


1--4


Multiple networks can be configured in the same system to control a variety of physical components :

Computing Systems

Information Network EtherNet/IP Network

Processors and Computing Systems

Control Network Data Highway Plus (DH+ ) Network

Processors and Devices

ControlNet Network Remote I/O

Device Network DeviceNet Network Operator Interface

Drive

Photoelectric Sensor

Limit Switch

Network Models Network Model: The manner in which data is transferred across a network.

Logix5000 systems make use of two distinct network models: •

Producer/Consumer: Communications model in which data is identified by its content rather than by its source or destination. The producer/consu mer network model has the following characteristics:

-- Data needs to be produced only onc e to reach multip le modules.

-- Data reaches multiple modules simultaneously. -- One network controls both programm ing and messaging.




1 -- 5

The following example shows the principle behind the producer/consumer model: 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

Student 5

Source/Destination: Communications model in which a data set is sent out multiple times to reach multiple devices. The source/destination network model has the following characteristics:

-- Devices do not receive information simultaneously with each other.

-- Different networks are required for messaging and for the transfer of time critical data.

-- Data arrives to different destinations at different times. The following example shows the principle behind the source/destination model: Example: Data Transfer in the Source/Destination Model

An instructional video presents information to one student at a time. Students receive the same information at the different times: Video

Student 1

Rev. September 2002

Video

Student 2

Video

Student 3

Video

Student 4

Video

Student 5


1--6


Network Options The network options supported by Logix5000 systems are grouped into two types of communications networks : • •

NetLinxt communications Legacy communications

NetLinx Communications: A combination of network service s that ensures a seamless flow of information and control data. All NetLinx networks follow the producer/consumer model: •

EtherNet/IP Network: A local area, information and control network designed for high-speed exchange of information between computers and related devices. EtherNet/IP networks are compatible with a wide range of equipment and can communicate over vast distances.

•

ControlNet Network: A reliable and consistent network for transmitting time-critica l and non time-critica l data on the same link. It provides real-tim e control and messaging services.

•

DeviceNet Network: A low-level communications network linking I/O devices directly to a controller without the need for I/O modules.

Legacy Communications: Networks that integrate existing products and networks, such as PLC-5 r or SLC 500 tprocessors, into a Logix5000 system. All legacy networks follow the source/destination model. The following legacy networks can be used with a Logix5000 system: •

Data Highway Plus (DH+ ) Network: A local area information and control network designed to support remote programming and data acquisition for factory-floor operations.

•

Universal Remote I/O Network: A network in which one device controls and initiates communications in supporting many legacy and third-party devices.

ControlLogix Gateway A ControlLogix system can be used as a communications hub (gateway) to bridge and route control and information data through EtherNet/IP, ControlNet, and DH+ networks.




1 -- 7

A ControlLogix Gateway uses the ControlBus t backplane to receive, translate, and pass data between communicat ions modules and networks: ControlLogix Chassis as Gateway

1756-DHRIO Module DH+Network

1756-ENBx or 1756-ENBT Module

1756-CNB Module ControlNetNetwork EtherNet/IP Network

PLC-5 System

RSLinx

ControlLogix Chassis with Controller

Programming Device

Software

RSLinx software creates a connection between an RSLogix 5000 t project and the hardware components. It can be used for maintaining a connection between plant floor devices and a range of software applications. The following graphic shows the RSLinx window:

Menu Bar Toolbar

RSWho Window

Rev. September 2002

RSLinx Window


1--8


Menu Bar

The RSLinx menu bar contains menus with items for handling all of RSLinx software’s capabilities. The following menus are unique to RSLinx software: •

Communications: Contains items for configuring drivers and network information, viewing communications diagnostic information, and creating shortcuts to networks.

•

Station: Contains items for monitoring controlle r data and modifying diagnostic information.

Toolbar

The toolbar contains tools used for providing connectivity and setting options for RSLogix 5000 software and the controller: Configure Drivers

What’s This?

RSWho

•

•

•

Configure Drivers: Displays the currently configured RSLinx software drivers and allows users to add additional drivers for use

with hardware devices. What’s This?: Changes the cursor to an arrow and a question mark to indicate you are in What’s This? help mode, which displays an RSLinx software component definition when a component is clicked. RSWho: Displays the RSWho window.

RSWho Window

The RSWho window is the network browser interfa ce for RSLinx software. It allows a user to view all the active network connections from two panels on a single screen:


•

The Tree Control shows netw orks and devices .

•

The List Control show s all the members of netw orks and devices that are bridges.



1 -- 9

Nodes can be accessed by expanding the configured networks in the Tree Control panel:

Configured Networks (Drivers)

Nodes on the Expanded network

Tree Control

List Control

Uploading, Downloading, and Going Online to a Logix5000 Controller When transferring an RSLogix 5000 t project between a computer and a controller, the following methods are used: •

Download: To transfer a copy of a project from a computer to a controller.

Important:

A controller can only hold one project at a time. Downloading the controller.overwrites the current project in

•

Upload: To transfer a copy of a project from a controller to a computer.

Important:

An uploaded file must be saved to the hard drive of the computer to avoid being lost.

The path a project takes when it is downloaded to a controller or uploaded from a controller is shown in the following graphic: Computer

Controller Download

Upload

Rev. September 2002


1--10


Offline vs. Online

Offline and online refer to the state of communications between a computer and controller . Each option serves a specific purpose in the development process: •

Online: The mode in which a computer running RSLogix 5000 software is monitoring or modifying the program file in a controller.

•

Offline: The mode in which a computer running RSLogix 5000 software is not monitoring or modifying the program file in a

controller. Online Status

Going online to a controller allows you to perform the following tasks: •

"

Monitor or modify a program in a proje ct loaded in a contro ller

•

Monitor data while it is being colle cted

•

Modify data stored in a controller

When computer running RSLogix 5000 software is online to a controller, the icon in the toolbar is animated. Offline Status

Offline status is used to perform the following tasks: • • •

Repair a system or equipment Develop or update project components Allow the control ler to run independently from the com puter running RSLogix 5000 software

Online Warning

!

ATTENTION: Use extreme caution when making changes to a project online. Mistakes can cause unintended machine motion or loss of process control, injuring personnel and damaging equipment. Before performing procedures online, complete these safety precautions: • •

• • • • •


Determine if changes must be made online. Verify that your company permits online entering and editing. Assess how machinery will respond to changes . Check proposed changes for accuracy. Notify all personnel of the changes. Verify that you are online to the correct controller. Ensure that multiple users are not going online to make changes on the same controller.



1--11

Communications Path

RSLinx software lets users create a communication s path that allows a computer to go online with a controller. The addresses (loca tions) of devices and networks through which data is sent are listed in the communications path: Network

Communications Backplane Controller Module

The communications path must be specified to go online and download or upload a project. It can be selected through the Who Active menu in RSLogix 5000 software:

Communication Options

Network Communications Module Backplane Controller Current Communications Path

Controller Operating Modes Controller Operating Mode: The state in which a controller operates. This mode determines the extent and type of communications that can occur between a computer and a controller.

The controller mode can be changed manually through the following keyswitch positions on a Logix5000 controller: •

Rev. September 2002

Run (RUN)

•

Program (PROG)

•

Remote (REM)


1--12


Manually Changing Controller Operating Mode

The keyswitch positions are shown in the following graphic of a Logix5550 t controller: Logix5550

Keyswitch Positions

Keyswitch

The keyswitch position dictates the available controller modes, as outlined in the following table: Keyswitch Position

Available Controller Modes

ATTENTION!

Run

Run mode -- The controller is actively controlling the process/machine. Projects cannot be edited when in Run mode.

Run mode should only be used when all conditions are safe.

Program

Program mode -- The process/machine stops, allowing modifications such as entering ladder logic to be safely made to the project.

Do not use Program mode as an emergency stop (E-stop). Program mode is not a safety device.

Remote Run mode -- Is identical to Run mode except you can edit the project online. Remote

Remote Program mode -- Is identical to Program mode. Remote Test mode -- Allows a program to run but disables its outputs for troubleshooting and diagnostics.

Any


!

Fault -- Most operations act as if the controller were in Program mode. It is entered when a major fault (error) occurs that is not handled by a fault routine.

Users are able to modify a project online in Remote Run mode. Be sure to control outputs with care to avoid injury to personnel and damage to equipment. Fault mode cannot be selected by a user. The fault condition must be cleared by the user before switching back to Run mode.



1--13

Remotely Changing Controller Operating Mode

Remote modes are changed through RSLogix 5000 software using the Online toolbar. The three Remote mode options are available within the Online (mode) drop-down list: Online (Mode) Drop-Down List

Remote Mode Selection Options

Here’s How

To upload, download, and go online to a Logix5000 controller

! Important:

ATTENTION: Performing this procedure online can cause dangerous situati ons. Making changes in a multiple-user environment can also cause dangerous situations. For specific information, refer to the Safety Precautions section at the beginning of this guide.

Before you can upload, download, or go online with a project, you must place the keyswitch on the controller in Program or Remote mode.

1. If the project will be downloa ded, open the RSLogix 5000 project file that will be transferred to the controller.

Rev. September 2002


1--14


2. Select a path to the controller by choosi ng the appropriate option : To . . .

Then perform the following actions . . . A. From the Communications menu, select Who Active. The RSLinx Who Active window opens, displaying the configured drivers. B. In the RSLinx Who Active window, expand the branch of any network containing the destination controller until the controller is displayed, as shown in the following graphic:

Modules Browse for a path

Network Backplane

C. Select the controller. D. To record the path in the Recent Paths list, click the Set Project Path button. A. In the Path toolbar, click The Select Recent Communications Path dialog box opens. Browse for a path

B. In the Select Recent Communications Path dialog box, click the path with the destination controller. C. Click Set Project Path D. Close the Select Recent Communications Path dialog box

3. Upload, download, or go online to the controller by choosing the appropriate option:

Important:

The slot number of the controller in the project must match the slot number of the controller selected for the transfer or the project cannot be downloaded.

Important:

To upload or go online, a file in the computer that matchesa the file in the the controller mustmay exist. Otherwise, project from controller be uploaded into a new file. Rung comments, descriptions, and alias chains will be lost.




To . . . Download the open project from the computer to the controller and then go online Go online to a project in a controller to monitor or edit the project

1--15

Then in the RSLinx Who Active window, perform the following actions . . .

A. Click Download. B. Verify that the controller listed is the destination controller and then click Download.

Click Go Online.

A. Click Upload. . . Important: Saving the project when prompted will replace the offline computer version with the controller version. Upload a project from the controller into the temporary memory of the computer

B. In the Connected to Upload dialog box, click Select File. . . The Select File dialog box opens. C. In the File name text box, type a new name for the file. D. Click Select. The Select File dialog box closes and returns to the Connected to Upload dialog box. Click Upload.

4. When going online or uploading, if a matching file wa s not found and a dialog box opens, read the given condition and option statements and then decide how to proceed.

The upload, download, or online connection is complete and the RSLinx Who Active dialog box closes.

Rev. September 2002


1--16


Here’s How

To select and change a controller’s operating mode:

Important:

!

Important:

The slot number of the controller in the project must match the slot number of the controller selected for the transfer or the project cannot be downloaded. ATTENTION: Performing these procedures online can cause dangerous situations. Making changes in a multiple-user environment can also cause dangerous situations. For specific information, refer to the Safety Precautions section at the beginning of this guide.

The controller’s keyswitch must be in the Remote position.

1. Go online to the Logix5000 controller s toring the project file to be monitored or edited.

"

Refer to the following graphics when changing the controller operating mode: Online Drop-Down List

Online Graphic

2. Change the control ler operating mode by choosi ng the appropriate option: To...

Then... A. From the Online drop-down list, select Run Mode. A prompt opens.

Operate in the Remote Run mode

B. Click Yes. The Online drop-down list in the upper left-hand corner of the Online Bar turns green and displays “Rem Run.” A. From the Online drop-down list, select Program Mode. A prompt opens.

Operate in the Remote Program mode

B. Click Yes. The Online drop-down list in the upper left-hand corner of the Online toolbar turns blue and displays “ Rem Prog.” A. From the Online drop-down list, select Test Mode.

Operate in the Remote Test mode to troubleshoot or test a project (i.e., scan a project without energizing outputs)


A prompt opens. B. Click Yes. The Online drop-down list in the upper left-hand corner of the Online toolbar turns yellow and displays “ Rem Test.” Rev. September 2002 COMs56


1--17

The controller is operating in the selected remote mode.

Exercise A

In this exercise, you will identify communications options in a Logix5000 system.

Directions: 1. What are the two basic phys ical connections for making a computer communic ate with a Logix5000 controller?

2. List three types of netw orks used by Logix 5000 systems :

3. What is the differenc e between the producer/ consumer and source/destination network models?

4. Write the corresponding commu nications option next to each description: Description

Communications Option

Links I/O devices to a controller without the need for I/O modules Designed to support remote programming and data acquisition for factory-floor operations Used for transmitting time critical and non-time critical data on the same link Provides high-speed exchange of information between computers and related devices Transfers data as a stream of electronic bits Can be used as both an information and control network Allows one devic e to control many legacy and third party devices

5. What is a driver?

Rev. September 2002


1--18


6. Label the elements of the following commun ications path:

Linx Gateways\10.88.247.44\AB_KTC-1\5\Backplane\3

7. How do you access RSLi nx software through RSLogix 5000 software?

8. Place a check in the box that indicates the ap propriate operating mode for each given situation: R un

Program

Remote Run

Remote Program

Remote Test

Fault

The mode in which a program runs but the outputs are disabled The mode in which project edits can be made safely The mode in which the controller actively controls the process/machine The mode that is identical to program mode The mode that is entered when a major fault occurs The mode that allows a project to be edited when it is online

9. What RSLogix 5000 toolbar lets you rem otely change a controller’s operating mode?




Exercise B

1--19

In this exercise, you will upload, download, and go online to a Logix5000 controller and select and change a Logix5000 controller’s operating mode.

Directions: 1. Change the controlle r’s keyswitch to Remote position. 2. Start RSLogix 5000 software. 3. Open the Bottling_Scenario1.acd file from the default RSLogix 5000 project directory. 4. Download the project to the controller in slot 1 of the workstati on and go online.

"

Download the project with the EtherNet/IP network unless your instructor specifies otherwise. 5. Verify that the Online (mode) drop down list in the Online toolbar is blue and displays “Remote Program” and that the icon is animated. 6. Verify that the OK lights on the controller and I/O modules are illuminated. 7. Using RSLogix 5000 software, chan ge the controller mode to Remote Run and verify that the RUN light on the controller is illuminated. 8. Change the contr oller mode to Remote T est, and then back to Remote Program. 9. Go offline 10. Upload the projec t to the RSLogix 5000 projects folder 11. Go offline 12. Close RSLogix 5000 softwa re without saving changes .

How Did You Do?

Rev. September 2002

If you did not receive the appropriate system response or if you have any questions, ask your instructor for assistance.


1--20


Answers

Exercise A 1. Serial and network connec tions are the two basic physical connections for making a computer communi cate with a Logix5000 controller. 2. Information, control, and device networks ar e three networks used by Logix 5000 systems. 3. The producer/consumer and source/destination network models have the following differences: •

•

The producer/consumer communications model identifies data by its content rather than by its source or destination. Data needs to be produced only once to reach multiple modules simultaneously. The source/destination communications mode l sends data out multiple times to reach multiple devices. Device s do not receive information simultaneously with each other.

4. Description

Communications Option

Links I/O devices to a controller without the DeviceNet Network need for I/O modules Designed to support remote programming and data acquisition for Factory floor operations Used for transmitting time critical and non-time critical data on the same link

Data Highway Plus (DH+)

ControlNet Network

Provides high-speed exchange of information between computers and related devices

Ethernet Network

Transfers data as a stream of electronic bits

Serial Connection

Can be used a both an information and EtherNet/IP Network control network Allows one dev ice to control many legacy and third party devices

Universal Remote I/O Network

5. A driver is a softwar e subroutine that hand les the logic for communicating with a specific type of external device. Computers require drivers to communicate on a network. 6. Communications Module

Network

Backplane Controller

Linx Gateways\10.88.247.44\AB_KTC-1\5\Backplane\3

7. RSLinx software is accessed through the Who Active menu item in RSLogix 5000 software.




1--21

8. Run

Program

Remote Run

Remote Program

The mode in which a program runs but the outputs are disabled The mode in which project edits can be made safely The mode in which the controller actively controls the process/machine

Remote Test

n

n

n

The mode that is identical to program mode

n

The mode that is entered when a major fault occurs The mode that allows a project to be edited when it is online

Fault

n

n

n

9. The online toolba r lets you remote ly change a contr oller’s operating mode

Rev. September 2002


1--22




Lesson Creating a DeviceNet Configuration What You Will Learn

2

Network

After completing this lesson, you will be able to create a network configuration by performing the following tasks: • •

Configure a DeviceNet driver Configure network properties

•

Create an offline network configuration

•

Go online to a network

• •

Upload a device or network configuration Browse a network

Why These Skills Are Important Correct configuration of a network ensures that all devices on the network are communicating. If one or more devices are not able to communicate on the network, data cannot be exchanged.

Before You Begin

Drivers Drivers are software mechanisms that link a computer containing programming or configuration software to a physical network. A properly configur ed driver makes it possible to view a software representation of an active network and make configuration changes and adjustments.

Rev. June 2002

E 2002 Rockwell Automation, Inc. All rights reserved. NETs100

2--2

Creating a DeviceNet t Network Configuration

Drivers used with Rockwell Software programs are configured using RSLinxt software. The following graphic shows the RSLinx window in which drivers are selected:

DeviceNet Drivers The following drivers can be used to go online to a DeviceNet network: •

1770-KFD Driver : Used in conjunction with an 1770-KFD (RS-232) module, which provides a point-to-point connection from a computer to a DeviceNet network.

Important:

"

E 2002 Rockwell Automation, Inc. All rights reserved.

For the 1770-KFD driver to be configured, a 1770-KFD module must be connected to the DeviceNet network and to the computer from which the driver is being configured via the computer’s serial port.

•

1784-PCD Driver : Used in conjunction with a 1784-PCD card, which fits into the PCMCIA slot of a laptop computer. The 1784-PCD driver is used to connect a laptop computer directly to a DeviceNet network.

•

1784-PCID Driver : Used in conjunction with a 1784-PCID card for the PCI bus of a personal computer. The 1784-PCID driver is used to connect a personal computer directly to a DeviceNet network.

RSLinx software comes with a variety of drivers already installed. However, the 1784-PCIDS driver must be installed separately.

Rev. June 2002 NETs100

Creating a DeviceNett Network Configuration

"

•

1771-SDNPT Driver : Used to connect to a DeviceNet network on a PLC-5 r platform through the backplane of the chassis in which a PLC-5 processor and companion 1771-SDN scanner module reside.

•

1747-SDNPT Driver : Used to connect to a DeviceNet network on an SLC 500 t platform through the backplane of the chassis in which an SLC 500 processor and companion 1747-SDN scanner module reside.

A connection to a DeviceNet network using either of these two pass through drivers is much slower than a direct connection and is therefore not recommended for use on a regular basis. •

"

2 -- 3

Ethernet Driver: Used to go online to a DeviceNet network via the ControlLogix t backplane.

Not exclusively a DeviceNet driver , an Ethernet driver can be used to access a variety of networks through a ControlLogix backplane. The follow graphic shows the RSLinx window where a 1770-KFD driver is configured:

Node Address Data Rate

Important:

Rev. June 2002

The data rate assigned to a DeviceNet driver must be the same as the data rate assigned to all other devices on the network.


2--4


Network Properties Network properties define a DeviceNet network in order to distinguish between networks. This is particularly helpful if more than one DeviceNet network exists in a plant. The following properties can be defined for a DeviceNet network: •

Network name

•

Network description

•

Online path (the path or driver to be used to go online t o the network)

Network properties can be viewed in the following RSNetWorx for DeviceNet software window:

Field to Enter Network Description

Command Button to Set Online Path

"

Only the Description field can be changed in this window. The Name field will become active after the network configur ation has been saved.

Network Configuration Options A network configuration is a graphic representation of a DeviceNet network that displays devices and their node addresses in RSNetWorx for DeviceNet software. The network configuration is the point from which all other configuration takes place. Network configurations can be created in either of the following ways:


•

Offline

•

Online Rev. June 2002 NETs100


2 -- 5

Offline Network Configuration An offline network configuration is created in RSNetWorx for DeviceNet software when access to the physical network is not possible. RSNetWorx for DeviceNet software contains a hardware view to which devices are added from a list of available devices:

Hardware View Hardware List

Important:

Devices added to an offline network configuration in RSNetWorx for DeviceNet software must exactly match the physical devices they represent. If the network configuration in RSNetWorx for DeviceNet software does not match the physical network, it will not be possible to obtain data from or send data to network devices once they are online.

Important:

"

Rev. June 2002

If a device is assigned a node address in an offline network configurat ion, unless a hardware node address has been assigned at the device itself, the address will not be valid until the node is commissioned online.

You can find devices quickly by placing your mouse pointer over any area of the hardware list, right-clicking, and then selecting Find Hardware.


2--6


Online Network Configuration Once devices are connected to the physical network and a driver has been configured, RSNetWorx for DeviceNet software can be used to go online and upload a network configuration:

Online Icon

Online network configuration provides the following benefits: •

The ability to view a ll devices that are available and communicating on the network before making any changes

•

The ability to view devices th at are no longer communic ating on the network

•

•

•

The ability toconfiguration view and resolv mismatches the network and eactual networkbetween devices devices in A choice to uploa d current device data from devices to the network configura tion or download device data from the network configuration to devices Diagnostic capabilities

Important:


To view an online network configuration, it is necessary to upload the network configuration after going online. Devices may show up in the network configuration before it is uploaded, but an upload must be performed to access configuration data.



2 -- 7

Uploading and Downloading To successfully create and work with an online network configuration, it’s important to understand the implications of uploading and downloading: •

Uploading: The process of obtaining data from a physical network and displaying it in a software program.

•

Downloading: The process of sending data from a software program to a physical network .

!

ATTENTION: Use extreme caution when downloading changes to an online network configuration. Incorrect configuration of devices online can cause erratic device behavior, injury to personnel or damage to equipment.

Keep the following considerations in mind when uploading from or downloading to a network: •

Uploading and downloading ca n only be perform ed when a network is online.

•

Going online to a network does not automatically upload the network.

•

In order for any changes ma de in an online network configur ation to take effect, the configuration must be downloaded to the network.

•

It is possible to download or uploa d configuration data to or from a single device or the entire network.

Browsing a Network Browsing is a way to determine the devices that are present on a DeviceNet network and their status. A network browse provides the following information: •

A graphic representation of all devices detec ted on the network at the time of the browse

•

The node addresses of the detected devices

•

Basic device status and identity inform ation

Important:

Rev. June 2002

A network browse does not provide device configuration data.


2--8


The following two browsing options exist: •

Single Pass Browse : A way to search for all devices present on a network during a single interval (i.e., all possible node addresses are scanned once).

•

Continuous Browse : A way to continuously search for network devices (i.e., when all possible node addresses have been scanned, the process of scanning for devices begins again).

Important:

Do not confuse browsing a network with uploading a network. A network browse can only indicate which devices present on the network, provide basic statusareinformation, and node addresses. Uploading a network provides specific device configur ation details and a means to edit them.

The following graphic shows the RSNetWorx for DeviceNet menu where browsing, uploading, and downloading options are selected:

Here’s How

To create a network configur ation by performing the following tasks: •

Configure a DeviceNet driver

•

Configure network properties

•

Create an offline network configuration

•


• •

Upload device and network properties Browse a network

As your instructor demonstrates these procedures, follow along in the DeviceNet Network Procedures Guide .




Exercise

2 -- 9

In this exercise, you will create a network configura tion.

Context: As a design engineer for Fast Foods Inc., you have installed the cable system for your DeviceNet network. Y ou are now ready to create a network configuration that will define the devices to be used on the network. This network configuration can then be used to go online to the network for future configuratio n tasks.

Directions: Using RSLinx software, RSNetWorx for DeviceNet software, and the steps below, create a network configuration for your DeviceNet workstation. 1. Open RSLinx software. 2. Configure the 1770- KFD driver as outli ned in the following table: For this parameter . . .

Select this option . . .

Port Select (in the Serial Port Setup panel)

The serial port on your computer

Data Rate (in the Serial Port Setup panel)

The highest rate available

Node Address (in the DeviceNet Port Setup panel)

62

Data Rate (in the DeviceNet Port Setup panel)

125

3. Open RSNetWorx for DeviceNet software. 4. Open a new (empty) offline netw ork configuration. 5. Configure network properties as outline d in the following table: For this property . . .

"

Rev. June 2002

Enter or select this . . .

Description

Fast Foods DeviceNet network

Online path

The 1770-KFD driver or the Ethernet driver

The software will not allow you to enter a network name in the Name text box at this time. When you save the network configuration for the first time, you can specify a network name in the File name text box.


2--10


6. Create an offline network conf iguration as outlin ed in the following table: Node Address

Device Name

1756-DNB/A scanner module (major revision 3)

00

1747-SDN scanner module (major revision 5)

01

E3 (1-- 5A) (solid state overload relay)

02

Bulletin 160 Analog 0.37kW 230v drive

03

871TM Unshielded 18mm with micro inductive proximity sensor

800Epushbuttonstation

"

04

05

DSA 4/2 (100--DNY42R) 22.5 mm (Bulletin 100 starter auxiliary))

06

1792D--4BV0D 4 Input (ArmorBlockt MaXumt input module

07

1791D--0B16P 16 Source Out (CompactBlock output module)

08

PanelViewt operator interface

09

You can find devices quickly by placing your mouse pointer over any area of the hardware list, right-clicking, and then selecting Find Hardware. 7. Open a new (empty) netw ork configuration.

Important: When prompted, do not save the existing offline network configuration. 8. Go online by choosi ng the appropria te option: If you want to use this platform as your primary control platform . . . ControlLogix SLC500

Then go online using this driver . . . Ethernet 1770KFD

9. Upload the network configuration.




2--11

10. Verify that the following devices are pres ent in the online network configur ation and write the node address of each device in the following table: Device Name

Node Address



E3 (1--5A) solid state overload relay

Bulletin 160 Analog 0.37kW 230v drive

800E pushbutton station

DSA 4/2 (100--DNY42R) 22.5 mm (Bulletin 100 starter auxiliary)) 1792D--4BV0D 4 Input (ArmorBlock MaXum input module) 1791D--0B16P 16 Source Out (CompactBlock output module) PanelView operator interface 1770-KFD RS232 interface

11. Which device in the offlin e network configu ration is not present in the online network configuration? Why not?

Rev. June 2002


2--12


12. Attach the 871TM induct ive proximity sens or to the network by connecting its drop line to the second KwikLink t micro connector from the right at the bottom of the workstation.

"

The drop line for the 871TM inductive proximity sensor should be protruding from behind the display panel. 13. Does the 871TM inducti ve proximity senso r show up in the online network configuration? Why or why not?

14. Perform a single pass browse to display the 871TM inductive proximity sensor in the online network configuration. 15. Enable the continuous browsing option. 16. Disconnect the 871TM inductive proximity sensor . 17. What happens after about a minu te? Why?

18. Disable the continuous browsing option. 19. Delete the icon for the disc onnected 871TM induc tive proximity sensor. 20. Save the network configuration.

How Did You Do?


Turn to the end of the lesson for the answers. If you have any questions, ask your instructor for assistance.



Rev. June 2002

2--13


2--14


Answers

Exercise 10. The following devices wit h their correspondin g node addresses should appear in the online network configuration: Node Address

Device Name


00


01

E3 (1-- 5A) (solid state overload relay)

03

Bulletin 160 Analog 0.37kW 230v (drive)

09

800EPushbuttonStation

15

DSA 4/2 (100--D NY42R) 22.5 mm (Bulletin 100)

20

1792D--4BV0D 4 Input (ArmorBlock MaXum input module)

30

1791D--0B16P 16 Source Out (CompactBlock output module)

32

PanelViewoperatorinterface

40

1770-KFDRS232Interface

62

11. The 871TM inductive proxim ity sensor is not prese nt in the online network configuration because it is not connected to the network. 13. The 871TM inductive proxim ity sensor does not show up in the online network configuratio n because the network has not been browsed since the sensor was connected. Therefore , the sensor’s presence on the network has not yet been detected. 17. The 871TM inductive proximity sens or disappears fro m the online network configuration (as evidenced by the error icon)

because the network is being continuously browsed and any changes are immediately detected.



Lesson

3

Mapping DeviceNet Data in a 1756-DNB Scanner Module What You Will Learn

After completing this lesson, you will be able to map DeviceNet data in a 1756-DNB scanner module by performing the following tasks: •

• •

Assign a node address and a baud rate to a 1756-DNB sca nner module Configure a 1756-DNB scanner module Create a scanlist

•

Map input and output dat a in a 1756-DNB sc anner module

•

Identify Logix5000 t DeviceNet tags

Why These Skills Are Important Being able to correctly map DeviceNet data in a 1756-DNB scanner module is important for the following reasons: •

Correctly configuring a Devic eNet network allows you to enjoy the cost savings, reduced downtime, and diagnostic capabilities of a DeviceNet network.

•

Understanding how device dat a is mapped will allow you to control how device data is organized and optimize data storage.

•

Before You Begin

Being able to identify whi ch bits are mapped is requi red to safely and correctly program ladder logic.

Review of Basic DeviceNet Concepts DeviceNet Node: Any device on the network that is addressable and that contains DeviceNet communications circuitry: •

A network can have up to 64 nodes.

•

The maximum cable distance from any device on a branching drop line to the trunk line is 6 meters (20 ft).

Commissioning: The process of assigning a node and data rate before a device is added to a DeviceNet network:

Rev. February 2001

•

Most devices are factory com missioned with a node address of 63 and a data rate of 125 Kbps.

•

If these values do not conflict with the network, you can conne ct the node. If values conflict, they must be changed using hardware or software methods.

•

Node 0 is reserved for the scanner.

E 2001 Rockwell International Corporation. MAPs56r

3--2

Mapping DeviceNet

t Data in a 1756-DNB Scanner Module

1756-DNB Scanner Module A DeviceNet scanner module is a device that manages input and output data for a controller. In a Logix5000 t system, a 1756-DNB scanner module acts as the network scanner and performs the following actions: • •

Reads inputs from a device Writes outputs to a device

•

Downloads configuration data

•

Monitors a device’s operational status

•

Communicates with the controll er in the form of input, output and diagnostic tables

•

Reduces the burden on the contr oller by managin g all the device inputs and outputs

•

Bridges a DeviceNet network with another netw ork

A 1756-DNB scanner module is shown in the following graphic: DeviceNet Scanner LEDs

A#00

Module/Net

Node Address

Scanner OK

A#00

E 2001 Rockwell International Corporation.

Rev. February 2001 MAPs56r

Mapping DeviceNet t Data in a 1756-DNB Scanner Module

3 -- 3

Assigning a Node Address and a Baud Rate to a 1756-DNB Scanner Module A node address and baud rate are assigned to a scanner module using a manual configuration button:

A#00

Manual Configuration Button for Node and Baud Rate

Open-style 5 or 10-Position Connector

Network Configuration Review A network configuration is a graphical representation of a DeviceNet network that displays devices and their node numbers in RSNetWorxt for DeviceNet software. Once devices are connected to the physical network and a driver has been configured, RSNetWorx for DeviceNet software can be used to upload an online network configuration as shown in the following graphic: Browse Option

Online Option

Network Address

Rev. February 2001


3--4

Mapping DeviceNet


Important:

The software performs a one-shot browse when you go online or when you select browse. Continuous brows e can be selected; however, it uses bandwidth.

Online Connection to a DeviceNet Network For Logix5000 systems, any configured network driver can be used to connect to the Logix5000 backplane then to the DeviceNet network, as shown in the following graphic:

Ethernet Driver Backplane

Network Scanner Selected Network

Important:

If there are no other network bridge modules in the chassis, a 1770-KFD driver and interface module can connect a computer directly to a DeviceNet network.

Configuring a 1756-DNB Scanner Module Configuring a scanner sets the properties for the scanner and defines how it communicates on the network. Network configuratio ns can be uploaded from the module or downloaded to the module.




3 -- 5

Creating a Scanlist A scanlist is a list of devices on the network with which the scanner will communicate. The scanlist provides the following information to the scanner: •

Which device node addresses to scan

•

How to scan each device

•

How often to scan each device

•

Where data can be found in each devic e’s memory

• •

The size of input and output data Where input and out put data is to be mapped in orde r for the controller to read it

•

How the controller should read each dev ice:

-- Using M1/M0 file for SLC t processors -- Using discrete I/O for PLC r processors -- Directly for Logix5000 controllers The scanlist is entered in RSNetWorx for DeviceNet software in the following window:

Devices Available for Scanning

Rev. February 2001

Devices Scannedto be


3--6


Mapping DeviceNet

Message Type Review Devices can be configured to transmit the following types of data:

"

•

Polled messages are used for dev ices that have data that cha nges often so the data can be collected during each scan.

•

Strobed messages are useful for devices tha t have only input data. Instead of scanning for input data from each device, a single strobed command solicits inputs from all strobed devices

•

Change-of-state messages are configured to send a scanner module’s data at a user-configured “heartbeat” rate regardless of whether or not their data has changed since the last change-of-state message was sent.

•

Cyclic messages are similar to change-of-state messages, but they are only sent at a user-configured rate. A cyclic message may be sent by a device even if the device’s data has not changed since the last time it was sent.

Both change-of-state and cyclic messages greatly reduce network traffic and allow faster scanner module respons e time since they do not require the scanner module to scan every device during a scan. The following table provides an summary of the characteristics of devices configur ed for each of the four message types: Device

Sends Data?

Scanned During Every Scan Cycle?

Receives Data?

Polled

Yes

Yes

Yes

Strobed

Yes

No

Yes

Changeof-state

Yes

Cyclic

Yes

No No

No No

Mapping Input and Output Data in a 1756-DNB Scanner Module The scanner uses input and output data in the following manner: •

The scanner rece ives input data from I/O devices, org anizes the information into scanner data tables, and sends the input data to the controller when requested.

•

The scanner sends output data, whic h it receives from the controller, to the I/O devices.

To correctly map inputs and outputs, it is important to understand what is meant by inputs and outputs. The following definitions apply to inputs and outputs on a DeviceNet network:


•

Input data is data received by a controller from a d evice via a scanner module (read).

•

Output data is data sen t to a device from a controller via a scanne r module (write). Rev. February 2001 MAPs56r


Important:

3 -- 7

Inputs and outputs on a DeviceNet network are defined from the point of view of the controller, not the devices with which they communicate.

Take the following into consideration when working with device inputs and outputs: •

Devices vary in data informati on (e.g., status , I/O data, and configuration data) and type (i.e., poll, strobe, cyclic, or change-of-state).

•

All data sent and rece ived on a DeviceNe t network is in byte length even if aone device device (i.e., will produce byteproduces of data).two bits of information, the

"

•

Bits can be mapped to sepa rate memory locations (i.e. , map segmenting).

•

All data acted upon in a Logix5000 controll er is in Dint length (two words, or four bytes).

Logix5000 controller s use a separate status area for the command register. Therefore, it is acceptable to map to word 0 of the input or output data.

Data Map Plan Input and output maps determine where data will be stored in the scanner module’s memory. Planning a configuration before mapping data can help ensure that the following actions occur: •

Memory and bandwidth is used efficiently.

•

Device-specific needs and requirements are acknowledged.

•

Priority is given to critical I /O transfers.

•

Room is left for networ k expansion (addin g devices).

•

Device data does not overlap.

Automatic Mapping Review Input and output data can be configured using the automatic map feature. The following considera tions should be addressed when automatic mapping is selected:

Rev. February 2001

•

Automatic mapping does not allow much contr ol (i.e., data organization can not be optimized or consolidated).

•

Automatic mapping will assig n word numbers base d on the node number of each device (e.g., node 1 will be mapped to word 1 in the map table).

•

Future changes (e.g., addition or removal of devices) ma y not be easily addressed. E 2001 Rockwell International Corporation. MAPs56r

3--8

Mapping DeviceNet


The Automap option can be selected in several tabs as shown in the following graphic:

Automap Option (Automaps the Selected Input or OutputinThat Already the Is Scanlist)

Automap Option (Automaps When a Device is Added to the Scanlist)

Mapped data can be organized using the following alignment options: •

Byte Align : Ensures that data is used as efficiently as possible to the byte level:

-- Two devices can share the same word location. •

•

Word word. Align : Ensures that each device is mapped in a different DWord (Dint) Align : Ensures that each device is mapped in a different Dint.

Manual Mapping Review Data can also be configured using the manual mapping feature. The following consider ations should be made when manual mapping is selected:


•

Data can be organized and optimized.

•

Room can be left fo r future expansion.

•

Manual mapping can be more time-cons uming than automatic mapping.



3 -- 9

Word Data Mapping Some devices, such as drives, contain data in words. You can manipulate this type of data using one of the following methods: •

Use a BTD (Bit Dis tribute) instruction to move data into specified bits

•

Use a COP (Copy) instruction to copy the data to and fr om integer arrays:

-- Use ladder logic to manipulate the data in the arrays ins tead of •

the DeviceNet tags Use advanced mapping to ma p the upper portion of the da ta into its own word.

-- This option allo ws you to separate the data by bytes a nd place them into specific addresses, as shown in the following graphic:

Full Dint Separate Speed Word

Identifying Logix5000 Tags After the DeviceNet network is operational, ladder logic must be written to control the devices (i.e., read the device inputs and then set the outputs). Tags use a format similar to local inputs and outputs. Example: DeviceNet Addresses

Local:2.O.Data[4].1 Rev. February 2001


3--10


Mapping DeviceNet

ChassisB:3.I.Data.4 Note the following about the addresses of DeviceNet devices : •

The address prefix for any Device Net device is the name of the 1756-DNB module followed by the slot number:

-- A 1756-DNB scanner module in the local cha ssis will always

"

•

be named local The letter identifies the type of data, such as i nput or output

•

The remainder of the address identi fies the word and bit

At this point, per memory the mapping table,However, it is known mapped to which location. it iswhich not yetdevice is specifically known which bits are mapped (i.e., for a RediSTATIONt operator interface, which of the eight bits in the byte represents the start button).

Resources To help determine which bits are mapped, you must refer to one of the following resources: •

EDS Based Help in RSNetWorx for DeviceNet software

•

EDS file

•

Here’s How

Online Help system in RSNetWorx for DeviceNet software

•

Printed technical documentation (shipped with the device or other)

To map DeviceNet data in a 1756-DNB scanner module by performing the following tasks: •

• • •

Assign a node addre ss and a baud rate to a 1756-DNB sca nner module Configure a 1756-DNB scanner module Create a scanlist Map input and output data in a 175 6-DNB scanner module

As your instructor demonstrates these procedures, follow along in the Logix5000 Controllers Procedures Guide.




Here’s How

To identify Logix5000 DeviceNet tags.

Example

Mapping Input Data for a RediSTATION Operator Interface

3--11

In the following examples, the 1756-DNB scanner module is in slot one and the data is mapped on Word boundaries. The following RediSTATION input information was located in the RSNetWorx online Help system:

Input Bits

Per the Help system, it is known that bit one represents the green start button and bit zero represents the red stop button, as shown in the following graphic:

G R

G R

Input Byte 7 6

Rev. February 2001

5

4

3

2 1

0

Bits


3--12


Mapping DeviceNet

The input byte is automapped to the 1756-DNB module’s input data file. This data is then mapped to the Logix5000 controller’s input image table, as shown in the following graphic: Input Byte

G R

Map

Logix5000 Controller Input Image Table

1756-DNB Module Input Data File G R

15 14 13 12 11 10 9 8

Word 0,L Word 0,H Word 1,L Word 1,H Word 2,L Word 2,H

0000 0000 0000 00GR 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000

76543210

The bits are mapped as shown in the following graphic:

RediSTATION Operator Interface

Slot 1:Inputs Mapped Bits Dint

"


RediSTATION Input Byte

The identified addresses can then be used in ladder logic.



Example

3--13

Mapping Input Data for a Series 9000 Photoelectric Sensor The following information about series 9000 photoelectric sensor data was found in the EDS Based Help in RSNetWorx for DeviceNet software:

Input Help Option

Font Selection

Per the EDS Based Help system, one status bit and one data bit are mapped to the input data table, as shown in the following graphic:

S D

Input Byte 7 6

Rev. February 2001

5

4

3

2 1

0

Bits


3--14

Mapping DeviceNet


The input data is then mapped to the Logix5000 controller’s input image table, as shown in the following graphic: Input Byte

S D

Byte Used by RediSTATION Operator Interface

1756-DNB Module Input Data File

Logix5000 Controller Input Image Table 0000 00SD 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000

S D

15 14 13 12 11 10 9 8


76543210

When the photoelectric sensor is mapped, the data is placed in the second byte of the Logix5000 Dint, as shown in the following graphic:

Photoelectric Sensor Input Byte

Dint


Mapped Bits



Example

3--15

Data Output Mapping for a RediSTATION Operator Interface Module Per the RSNetWorx Help file, an output bit for the indicator light will be mapped to bit zero. A blink bit is also mapped to bit one, as shown in the following graphic:

Blink Bit

Output Light Bit B L

Output Byte 7

6

5

4

3

2 1

0 Bits

The data is then mapped to the Logix5000 controller’s output image table, as shown in the following graphic: B L

1756-DNB Output Byte

Logix5000 Controller Output Image Table

1756-DNB Module Output Data File B L Map

15 14 13 12 11 10 9 8

Rev. February 2001

0000 0000 0000 00BL 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000


76543210


3--16


Mapping DeviceNet

The bits are mapped as shown in the following graphic:


Slot 1:Outputs Dint

Important:

Exercise

Mapped Bits RediSTATION Output Byte

It is helpful to record which bits are mapped in order to write the ladder logic that will control the devices.

In this exercise, you will be able to map data in a 1756-DNB scanner module.

Context: You are part of a team that has programmed a Logix5000 compres sor assembly line. Because your plant’s production line has several small plant floor that are distant from of each other, and because want to usedevices the diagnostic capabilities these devices, your you company has retrofitted part of the production line with a DeviceNet network. The network and the devices on the network are already configured. You are now ready to edit the scanlist and map DeviceNet data in the 1756-DNB scanner module.




3--17

The DeviceNet portion of the compressor assemb ly project includes the following devices: Device

ApplicationUse

1756-DNB scanner module

Scan the network and map the data for the controller

RediSTATION operator input (2705T)

Start and stop the conveyor using pushbuttons and display a production-in-process light

Photoelectric sensor (Series 9000 photoelectric sensor)

Sense a compressor when it reaches the first machine station

ArmorBlockt MaXum I/O

Control the press output (mounted near station 1 where space is limited and temperatures can be elevated)

160 drive (160 SSC variable speed drive) PanelViewt terminal (PanelView 600 DeviceNet color terminal)

Control the conveyor motor Display values for each machine station, such as pressure, and make changes to production variables, such as drive acceleration time

Directions: 1. On your workstation, identify the follow ing devices and their

features: A. 1756-DNB scanner module in slot 7: - LED lights

- Manual configuration button B. RediSTATION operator input: - Two momentary pushbuttons

- Pilot light C. Photoelectric sensor: - LED lights (top)

- Reflector D. ArmorBlock MaXum I/O: - Outputs 0 and 1 E. 160 drive: - LED lights

- DeviceNet communication module (160-DN2) F. PanelView 600 DeviceNet color terminal: - Function and numeric keypads

- External power G. Cable connections to all devices Rev. February 2001


3--18


Mapping DeviceNet

2. Verify the a node addres s of 0 and a baud rate of 125k are assigned to the 1756-DNB scanner module.

"

If correct address and baud rate are not displayed on the LED, then reassign them. 3. Go online to the DeviceN et network through an Ether net network.

"

If the RSLinx window does not show the 1756-DNB module in slot seven, or the DeviceNet network channel, refresh the view. 4. Verify that the following devices are displayed: • • • • • •

1756-DNB module at node 0 ArmorBlock MaXum I/O at node 1 Series 9000 photoelectric sensor at node 2 RediSTATION operator input at node 3 Bulletin 160 drive at node 4 PanelView 600 color ter minal at node 5

5. Configure the 1756- DNB scanner module for your networ k by entering the following properties for the scanner module: Parameter

Setting

InterscanDelay

8milliseconds

Foreground to Background Poll Ratio

2

Slot

Yourworkstationslotnumber

6. Access the scanner and download the changes to the scanner . 7. To verify the operation of the photoelectric senso r, perform the following test: A. Access the Device Parameters tab for the photoelectric sensor.

"

Download the software configuration to the device. B. Start monitoring all paramete rs. C. What is the value for the Output param eter (ID 2)?

D. Place your hand between the photoelec tric sensor and the reflector.




3--19

E. What is the value for the Output param eter (ID 2) when your hand passes between the sensor and the reflector?

"

The functional specificatio n for the compressor assembly project requires the photoelectric sensor output value to be a 1 (on) when a compressor passes between the sensor and the reflector. F. If your hand represe nts a compressor on the conveyor , does this operation match the needs of the functional specification?

G. If the photoelectric sen sor is not operating as desired, change the Operate Mode parameter (ID 1) and download the change. H. Which mode did you choose?

I. Monitor all parameters again, and tes t your change. 8. Access the scanner module properties. 9. Click the Scanlist tab and cle ar the Automap on Add option.

"

If the scanlist is already created, remove all of the devices. 10. Create a scanlis t that includes the following devices in this order: A. ArmorBlock MaXum I/O at node 1 B. Series 9000 photoe lectric sensor at node 2 C. RediSTATION operator input at node 3

"

The 160 drive and the PanelView terminal require additional set up and will be configured in a different lesson. 11. Click the Input tab. 12. To match the data in the controller and to simplify its organization, set the alignment option to DWord Align. 13. Map each device input in the 1756-D NB scanner module. 14. Map each device outpu t in the 1756-DNB scanne r module.

Rev. February 2001


3--20


Mapping DeviceNet

15. Download the information to the scanner . 16. To write the ladder logic that will cont rol the devices in the next lesson, identify the Logix5000 tag addresses to be used by the DeviceNet devices: Device

InformationSource

Bit

Logix5000Address(s)

Green/Start input

RediSTATION operator

Red/Stop input RSNetWorx Help system

interface Light output (solid)

Series 9000 photoelectric sensor ArmorBlock MaXum I/O

EDS I/O Help

Output bit Output 0

RSNetWorx Help system Output 1

17. Apply and download the changes . 18. Save the RSNetWorx for DevieNet .dnt configuration using your name or station number in the Student folder located in C:\CCP144. 19. Record the total numbe r of input Dints that are mapped:

20. Record the total numbe r of output Dints that are mapped:

How Did You Do?





Rev. February 2001

3--21


3--22

Mapping DeviceNet

Answers


Exercise 4. An example RSNetWorx for DeviceNet screen is shown in the following graphic:

7. The photoelectric sensor should be operating in the following manner: F. Your hand (the compressor) should break the beam and change the value to on when it passes between the sensor and the reflector. H. If the parameter is correc tly set, change it to Dark Operate mode.




3--23

10. The devices should be added to the scanlist in the following manner:

Rev. February 2001


3--24


Mapping DeviceNet

13. The inputs should be mappe d to the following memory areas :

"


If you mapped in a different order or did not select DWord Align, your mapping may be different.



3--25

14. The outputs should be mapp ed to the following memory area s:

"

If you mapped in a different order, or did not select DWord Align, your mapping may be different.

16. The following tags should be iden tified:

" Device

If you mapped your device in a different order, or did not select DWord Align, your addresses will be different. InformationSource

Bit Green/Start input


RSNetWorx Help system

Series 9000 photoelectric sensor

EDSI/OHelp

Armor Block MaXum I/O

Red/Stop input Light output (solid) Outputbit

Output 0 RSNetWorx Help system

Logix5000Address(s) Local:7.I.Data[2].1 Local:7.I.Data[2].0 Local:7.O.Data[1].0 . . . Local:7.O.Data[1].1 Local:7.I.Data[1].0 Local:7.O.Data[0].0

Output 1

Local:7.O.Data[0].1

19. 3 Dints should be mapped. 20. 2 Dints should be mapped. Rev. February 2001


3--26

Mapping DeviceNet




Lesson

4

Configuring a Logix5000 Controller to Control a DeviceNet Device What You Will Learn

After completing this lesson, you will be able to configure a Logix5000 controller to control a DeviceNet device by performing the following tasks: •

Add a 1756-DNB sc anner module to the I/O config uration of an RSLogix 5000 project

•

Set a 1756-DNB scanner to Run mode

•

Write ladder logic to control a Device Net device

Why These Skills Are Important Being able to correctly configure a Logix5000 controller to control a DeviceNet device is important for the following reasons :

Before You Begin

•

Setting the scan ner to Run mode is required to have the scanne r communicate with the devices or the controller.

•

Programming ladder logic u sing the wrong ma pped inputs or outputs can cause dangerous situations.

Adding a 1756-DNB Scanner Module to the I/O Configuration of an RSLogix 5000 Project To configure a DeviceNet network in a Logix5000 system, the 1756-DNB scanner module must be added to the I/O configuration of the associated RSLogix 5000 project, as shown in the following graphic:

1756-DNB Scanner Module (Slot 4)

Rev. February 2001

E 2001 Rockwell International Corporation. LADs56r

4--2

Configuring a Logix5000 t Controller to Control a DeviceNet t Device

Adding the 1756-scanner module to the I/O configuration allows you perform the following actions: •

Monitor the 1756-DNB scanner tags

•

Address the scanner tags in ladder lo gic

•

Select the module as th e target device wh en configuring a message

Important:

When adding the module, the input and output data sizes in total Dints must be specified. To guarantee communications, each total must include the number of words mapped plus one additional word for status data.

Example: Input and Output Words

The number of words mapped can be determined in RSNetWorxt for DeviceNet software, as shown in the following graphic:

Mapped Dints


Rev. February 2001 LADs56r

Configuring a Logix5000t Controller to Control a DeviceNet t Device

4 -- 3

1756-DNB Scanner Module Defined Tags After adding a module to an I/O configuration, any module-defined tags become available. A 1756-DNB scanner module will contain the following module-defined tags: Input Tags

Output Tags

Status Tags

Command Register Bits The CommandRegister tags are part of the 1756-DNB Output tags. These tags contain bits that initiate the following actions: Bit

Run

Fault

Disable Network

Halt Scanner

Reset

Rev. February 2001

Actions(Modes) If this bit is set to 0, the scanner is in Idle mode. The scanner receives inputs from the slave devices on the network, but will not send active output data to the devices. If this bit is set to 1, it is in Run mode. Inputs are received from the slave devices and output data is sent back to the devices. When set, the scanner will not make any attempt to communicate on the network. It is useful to have the ladder logic set the module to Fault mode when a major error is detected and you want the module to stop communicating. If this bit is set, the scanner is in Disable mode. It will not make any attempt to communicate with the network. When set, the scanner is not communicating on the DeviceNet network. This is the most severe mode. The scanner will not resume communications until power is cycled to the 1756-DNB module. When set, the scanner will go through a powerup reset. This option is not available when the module has been placed in Halt mode through the command register. A 0 bit should be entered before the reset is complete or another reset will begin.


4--4


Bit Setting Any controller bit, including the CommandRegister.Run, bit can be set using the following technique s: •

Manually change the tag in the Monitor Tags w indow

•

Program ladder logic to auto matically set the bit

64-Bit Tables Some of the tags, such as the DeviceFailureRegister, are arrays of 8 bytes of data. The 8 bytes typically contain a bit for every possible node number (0 through 63) that is in the scanlist of the 1756-DNB module, as shown in the following graphic:

Node 0

Array

Node 63

Alias Review Alias tags are commonly used to rename the automatically generated I/O tags that have complex naming structures. For example, Motor_Start can be an alias tag for Local:2:I.Data.15

"


If ladder logic has already been written for a device that is being replaced by a DeviceNet device, and the tag is an alias, simply change the base tag to the DeviceNet address.



4 -- 5

Word Data Mapping Review Some devices, such as drives, contain data in words. You can manipulate the data using one of the following methods: •

Use a BTD (Bit Dis tribute) instruction to move data into specified bits

•

Use a COP (Copy) instruction to copy the data to and fr om integer arrays:

-- Use ladder logic to manipulate the data in the arrays ins tead of •

the DeviceNet tags Use advanced mapping to ma p the upper portion of the da ta into its own word:

-- This option allo ws you to separate the data by bytes a nd place them into specific addresses, as shown in the following graphic:

Full Dint Separate Speed Word

Here’s How

To configure a Logix5000 controller to control a DeviceNet device by performing the following actions: •

To add a 1756-DNB scanner mo dule to the I/O configurati on of an RSLogix 5000 project

•

Set a 1756-DNB scanner to Run mode

As your instructor demonstrates these procedures, follow along in the Logix5000 Controllers Procedures Guide .

Rev. February 2001


4--6


Here’s How

To configure a Logix5000 controller to control a DeviceNet device. As your instructor demonstrates, refer to the following example:

Example

Writing Ladder Logic to Control a DeviceNet Device The following rungs show devices that are controlled through ladder logic in an RSLogix5000 project: Slot of Scanner Word Bit

Slot of Scanner Word Bit

Input

Exercise A

Output

In this exercise, you will configure a Logix5000 controller to control DeviceNet devices.

Context: You are part of a team that has programmed a Logix5000 compres sor assembly line. Your company has just retrofitted part of the production line with a DeviceNet network. The 1756-DNB scanner module is configured, the scanlist is complete, and the device input and output data is mapped. You are now ready to configure a Logix5000 controller to control a DeviceNet device.

Directions:

"

In this lesson, the analog meters are inactive. 1. Open or maximize your RSNetWorx for DeviceNet configuration file stored in the Student folder in C:\CCP144. 2. Verify that your Slot_3.acd file is running in the controller in slot three.

"

If you have not been working on this file in previous lessons, open the LAD_Slot_3.ac d project stored in the DeviceNet_L adder folder located in C:\CCP144. Download the project to the controller and then change the controller operating mode to Remote Run. 3. In a second instance of RSL ogix 5000 software , open or maximize your Slot_1.acd project stored in the Student folder located in C:\CCP144.




"

4 -- 7

If you have not been working on this file in previous lessons, open the LAD_Slot_1.ac d project stored in the DeviceNet_La dder folder located in C:\CCP144. 4. Add the 1756-DN B scanner module in slot 7 to the I/O configuration of the project. 5. Examine the modul e tags that are create d. 6. In the Conveyor Main Routine , write the ladder logic req uired to set the 1756-DNB scanner to Run mode. 7. Based on your mapping in RSNetWorx software, retrofit several existing devices by performing the following actions: A. In the Conveyor progra m tags, change the alias of the Sta rt tag to the address for the RediSTATION green start pushbutton. B. In the Conveyor progra m tags, change the alias of the Stop tag to the address for the RediSTATION green stop pushbutton. C. In the Controller tags, change the alias of the Part_Sens or tag to the photoelectric sensor input. 8. Edit rung one in the Conveyo r_Control routine in the Conveyor program, to illuminate the RediSTATION output when the production line is in process:

Add Two Outputs

1

9. Edit rung zero in the Press_C ontrol routine in the Station_1 _Press program, to make both the existing operator panel light (Station_Output) and the new MaXum I/O output (the press machine) active at the same time: Add One Output

0

Rev. February 2001


4--8


10. Save the project as Slot _1.acd in the Student folder loc ated in C:\CCP144. 11. Download the project to the controller in slot one and go online. 12. Place the controller in Remote Run mode. 13. Verify that your ladder logic is correctly programmed by performing the following actions: A. Verify that the following action occurs:

- The CommandRegister.Run tag is set to Run mod e. - The scanner LED displays RUN. B. Press the green start button on the RediSTATION operator input and verify that the following actions occur: - The conveyor output light (D O1) is illuminated on the workstation - The red pilot light is illuminated on the RediSTATION operator interface C. Place your hand between the photoelec tric sensor and the reflector and verify that the following action occurs: - The process starts on the Lo gix5000 workstation (the press machine light (DO1) is illuminated) and the MaXum Armor Block I/O point one (not zero) is active D. After the machines st ops and the conveyor is on (DO1), place your hand between the photoelectric sensor and the reflector again and verify that the following action occurs: - The process cycles again: (the pr ess machine light (DO1) is illuminated, the MaXum Armor Block I/O point one is active, and then the stake machine light (D04) is illuminated). 14. Go offline.

How Did You Do?

If all boxes in Step 13. are checked, then you have successfully configured a Logix5000 controller to control DeviceNet devices. Turn to the end of the lesson for the answers. If you have any questions, ask your instructor for assistance.




Exercise B

4 -- 9

In this exercise, you will configure a Logix5000 controller to control a more complex DeviceNet device.

Context: You have just programmed the Logix5000 controller to control several DeviceNet devices. You have also tested your work. Confident with your first programming attempt, you are now ready to try creating more advanced ladder logic that accomplishes the following control of a 160 drive (160 SSC variable speed drive). • •

•

The 160 drive runs forward to 60 Hz. When the 160 drive reaches 60 Hz , the controller slow s down and reverses direction. Once the 160 drive is running in reve rse at 60 Hz, the s equence is restarted.

Important:

If the 160 drive faults at any time, turn off the chassis power and then the DeviceNet network power . After the LEDs on the 160 drive are off, in this order, restart the network power followed by the chassis power.

Directions: 1. In RSNetWorx for DeviceNet software, access the properties for the 160 drive and upload them.

"

Per the device documentation, several paramet ers must be set in order to send commands to the device (i.e., change speed, etc.). 2. Set the following par ameters and download all changes to the 160 SSC drive: A. Set the Input Mode (ID 46) to Network Cont rol. B. Set the Reset Funct ions (ID 56) to Reset Input Mode. C. Set the Frequency Selec t (ID 59) to Internal Freq. D. Set the Output Asse mbly (ID 107) to 21. E. Set the Input As sembly (ID 108) to 71.

"

Parameters 107 and 108 determine the data formats used by the 160 drive. 3. Review the data formats in the -- SSC 160 Variable Speed Drive Data Assembly appendix. 4. In your RSNetWorx for DeviceNet project, access the scanlist and clear the Automap on Add option. 5. Add the 160 drive to the sc anlist. 6. Using the DWord Align option, map the 160 drive inputs.

Rev. February 2001


4--10


7. Using the DWord Align option, map the 160 drive outputs. 8. In addition to the Dint just mapped for the 160 drive outputs, use Advanced Mapping to map the Speed Reference RPM to a separate word.

"

This will allow you to easily move a new value into a mapped word (instead of the bits 16 to 31 of a Dint). 9. Download the changes to the scanner . 10. From your scanne r mapping, identify the input and output words mapped for your 160 drive:

11. Save the network configuration usin g your name or station number for the file name. 12. Go offline to the projec t in the controller in slot one. 13. In the Conveyor progra m, create a Drive rou tine. 14. In the Conveyor Main Routine, create a JSR instruc tion to access the Drive routine. 15. Open the Conveyor program tags.

"

If youthese are working yourinstance own Slot_1.acd project, will not have tags. In awith second of RSLogix 5000you software, open the Copy.acd project stored in the Student folder located in C:\CCP144. Copy the tags from the Drive program into your project. 16. Based on your mapping for the 160 drive and the informa tion in the appendix, change the base tags for the following aliases:

"

To keep the tags grouped together, the same starting characters were used for each tag. A. Drive_Run_Fwd B. Drive_Run_Rev C. Drive_Fault_Reset D. Drive_Net_Control E.

Drive_Net_Ref F. Drive_Speed_Reference_RPM (separate word) G. Drive_Faulted H. Drive_Running_Forward E 2001 Rockwell International Corporation.



4--11

I. Drive_Running_Reverse J. Drive_Ctrl_From_Net K. Drive_Ref_From_Net L. Drive_At_Speed 17. To understand its function, review the follow ing ladder logic that will be used to control the drive:

18. In the Drive routine , program the given ladder logic .

"

You can also copy the completed ladder logic. In a second instance of RSLogix 5000 software, open the Copy.acd project stored in the Student folder located in C:\CCP144. Copy the ladder logic into the Drive routine in your project. 19. Save the project. 20. Download the project to the controller in slot one and go online. 21. Place the controller in Remote Run.

Rev. February 2001


4--12


22. Verify that you correctly progra mmed the ladder logic to control the 160 drive by performing the following actions and placing a check in each completed box:

-

The 160 drive runs forward to 60 Hz.

-

Once the 160 drive is running in reverse at 60 Hz, the sequence is restarted.

-

In RSNetWorx for DeviceNet software, the 160 driver ID 30 displays a speed close to 1500 RPM.

When the 160 drive reaches 60 Hz, the controller slows down and reverses direction.

23. Go offline.

How Did You Do?

If all boxes in Step 22. are checked, then you have successfully configured a Logix5000 controller to control a more complex DeviceNet device. Turn to the end of the lesson for the answers. If you have any questions, ask your instructor for assistance.




Rev. February 2001

4--13


4--14


Answers

Exercise A 4. The I/O configura tion should look like the following:

6. The following ladde r logic should be create d to set the scanner to Run mode:

7. The following chan ges were made to the alias tags: A. and B. Start and Stop tags:

C. Part_Sensor tag:




4--15

8. The following ladde r logic should be create d to control the output light:

"

Aliases were created for the pilot light bits. Added Logic

1

9. The following ladde r logic should be create d to control the ArmorBlock MaXum I/O point: Added Logic

0

Rev. February 2001


4--16


Exercise B 7. and 8.

The following advanced mapping was used to map all of the output data and then to separately map the speed word:

Full Dint

Separate Speed Word

15. With the module in slot 7, (input mappin g 7:1.Data[3] and output mapping 7:O.Data[2]), the following addresses are used: A. Drive_Run_Fwd: Local:7:O.Data[2].0 B. Drive_Run_Rev: Local:7:O.Data[2].1 C. Drive_Fault_Reset: Local:7:O.Data[2].2 D. Drive_Net_Control: Local:7:O.Data[2].5 E. Drive_Net_Ref: Local:7:O.Data[2].6 F. Drive_Speed_Reference RPM (Low Byte):Local:7:O.Data[3] G. Drive_Faulted: Local:7:I.Data[3].0 H. Drive_Running_Fwd: Local:7:I.Data[3].2 I. Drive_Running_Rev: Local:7:I.Data[3].3 J. Drive_Ctrl_From_Net: Local:7:I.Data[3].5 K. Drive_Ref_From_Net: Local:7:I.Data[3].6 L. Drive_At_Speed: Local:7:I.Data[3].7 E 2001 Rockwell International Corporation.


Lesson

5

Configuring an Offline ControlNet Network What You Will Learn

After completing this lesson, you will 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

•


Why These Skills Are Important Having the skills to correctly configure an offline ControlNet network is important for the following reasons:

Before You Begin

•

Creating a configuration file wil l provide a back-up securi ty for fast application recovery.

•

Creating an offline network conf iguration, conf iguring device parameters, and configuring a chassis will ensure a network’s physical components match those components for which that network was designed.

•

Configuring network proper ties improperly can result in the failure of an application or make it impossible to access the network from a programming device.

RSNetWorx

for ControlNet Software

RSNetWorx for ControlNet software is the main configuration tool for a ControlNet network. RSNetWorx for ControlNet software is used to perform the following tasks: •

Create or edit an offline ne twork configuration

•

Edit or monitor a netw ork configuration that is activ e within all connected devices

•

Schedule communications

Important:

Rev. March 2002

RSNetWorx is supported on these Microsoft r operating systems: Windowsr 95, Windows 98, Windows ME, Windows NTr 4.0 Service Pack 3 through 6, and Windows 2000.

E 2002 Rockwell Automation. All rights reserved. CO1s200

5--2

Configuring an Offline ControlNet t Network

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 networ k configurations, chassis, or devices between configurations

•

RSNetWorx for ControlNet Main Window

The RSNetWorx for ControlNet main window contains the following components: Minimize, Maximize, and Close Buttons

Window Title Bar Network Usage View

Toolbar Menu Bar Check Box Hardware List Split Bar Scroll Bar

Message View Tab

Status Line

"

Network Configuration

For your reference, graphics and definitions for these common components are provided in the Glossary of the ControlNet Networks Procedures Guide. RSNetWorx for ControlNet Toolbar

The RSNetWorx for ControlNet toolbar provides easy access to the software’s most-commonly used components: Save

New

Open


Print

Cut

Paste

Copy

Zoom In

Show Favorites

Display Symbol Online Legend

What’s Zoom Show Browse Hardware This? Out

Refresh

Rev. March 2002 CO1s200


5 -- 3

Configuration File An RSNetWorx for ControlNet configuration file is a single file that is created when you save a network configur ation using RSNetW orx for ControlNet software. It serves as both a record of a network (containing network parameters, device properties, media configuration, etc.) and a safety measure, ensuring that a network can be returned to srcinal working order should a malfunction occur. The configuration file must always have an .xc extension.

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 configura tion can be created offline using RSNetWorx for ControlNet software. The following graphic shows a spreadsheet representa tion of a network configuration:

Hardware List

When creating an offline ControlN et 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:

Rev. March 2002

•

Vendor type

•

Category type


5--4


The following graphic partially shows the communications adapter category within the hardware list:

Device Parameters Device parameters define a device’s identity on a ControlNet network. The following general parame ters 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

EDS files are ASCII files created by device manufacturers that provide device information for a network. For a device to be available the hardware list, to a representative EDS (electronisoftware c data sheet) fileinmust be registered RSNetWorx for ControlNet using the EDS Wizard tool.




5 -- 5

The following information can be found in an EDS file: •

Description of the EDS file history, whic h includes the following file information:

-----

•

File name Create time Modification time Revision number Description of the device, which incl udes the followin g device information:

------

• •

Vendor Product type Revision number Product name Catalog number Input and output information Device-configurable parameters

The following graphic shows how this information is displayed in an EDS file:

EDS Wizard

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 •

Rev. March 2002

•

Create an EDS stub

•

Remove a device from the registry

•

Change the graph ic image associated with a device E 2002 Rockwell Automation. All rights reserved. CO1s200

5--6


Chassis Configuration Chassis configuration defines a chassis’ identity on a ControlNet network. The following parame ters for a chassis can be configured using RSNetWorx for ControlNet software: • • •

Type of chassis Addressing mode [1771 only] Chassis contents

Network Properties 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 componen ts: •

Network parameters that defin e the following guidelines:

-- What devices can access a network -- When devices can transmit data on a networ k -- What channel devices can use to transmit data •

Media configuration that defin es the wait time betwe en each device’s data transmission

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 qualifyi ng network devices •


•

Unscheduled bandwidth for qua lifying network devices

•

Guardband bandwidth for netwo rk maintenance



5 -- 7

CTDMA (Concurrent Time Domain Multiple Access)

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 device’s 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 send us ed that to support anyrequire node tha t may have non-time critica l data to does not deterministic and repeatable delivery:

-- Unscheduled bandwidth is not rese rved for individua l nodes but is used as needed in a round-robin priority.

-- Delivery of unscheduled data does no t impact the delivery of scheduled data. Scheduled Bandwidth

Scheduled bandwidth on a ControlNet network has the following characteristics: •

The length of sch eduled bandwidth is defined by how lon g 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 bandw idth is defined by the node with the highest network addres s that requires the use of scheduled bandwidth on a ControlNet network.

Scheduled bandwidth is utilized in the following manner:

Rev. March 2002

•

Each node, from node one to the last node gi ven 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 transmi t, it signals the network to move to the next scheduled node.

•

Nodes wait a given amount of time for each missing node fro m node one to the last given access by the user.

•

The boundary betw een scheduled bandwidth and unsche duled bandwidth moves depending on how much data each node sends during the scheduled bandwidth.


5--8


Example: Scheduled Bandwidth

The following graphic shows how scheduled bandwidth is used on a ControlNet network: 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.

2

1 3

3 S

S Nodes wait for each missing node.

The boundary moves depending on utilization of bandwidth.

Unscheduled Bandwidth

Unscheduled bandwidth has the following characteristics: •

•

•

The length of unsc heduled bandwidth is defined by how lo ng 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 unschedu led bandwidth is conf igured by the user. Access to the network is defined by the node with the highest network addres s that must communicate on the network.

Unscheduled bandwidth is utilized in the following manner:


•

Each node, from node one to the last node gi ven 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 pres ent on the networ k but has no data to transm it, 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 oppor tunity to transmi t data during each user-defined interval.

•

First access to unscheduled bandwidt h increases by one with each interval.



5 -- 9

Example: Unscheduled Bandwidth

The following graphic shows how unscheduled bandwidth is used on a ControlNet network: Network Update Interval Scheduled Unscheduled Guardband 2 3

1 2 3

First access increases by one with each interval.

3 4

5U 5

U

1

1

Sequence continues until unscheduled bandwidth is exhausted.

Nodes wait for each missing node.

Guardband

Guardband is the portion of a each interval provided for network maintenance. Guardband is utilized in the following manner: •

The moderator (node with the lo west node number on the network) distributes network-wide parameters to all devices.

•

The guardband contains the fol lowing data:

-- Network parameter changes -- Network parameters for newly added 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 network’s nodes:

Rev. March 2002

•

Network update time (NUT)

•

Maximum scheduled node (SMAX)

•

Maximum unscheduled node (UMAX)

•

Media redundancy


5--10


Network Update Time

The network update time is the user-configured repeatable base time at which the network can transmit data. One interval on the network 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 millise conds

•

Must at least matc h the fastest rate any two nodes must communicate

•

Must be large enou gh to allow the required amount of networ k traffic to pass

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 schedule d node should meet the following recommendations:

"

•

Maximum scheduled node will be the addres s of the highest node to communicate on the scheduled bandwidth.

•

Maximum scheduled node will not leave emp ty node addresse s below maximum scheduled node, because it is a waste of scheduled bandwidth.

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 unschedule d node is a user-configured parameter defining access to the network. In order for a network to operate properly, the maximum unsched uled node should meet the following recommendations:


•

Maximum unscheduled node will be the addre ss of the highest node to communicate on the network.

•

Maximum unscheduled node will not leave em pty node address es below maximum unscheduled node, because it is a waste of unscheduled bandwidth.



5--11

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 must be configured for one of the following options: If you are using . . .

Use this option . . .

One cable system using channel A only

A only.

One cable system using channel B only

B only.

Both channel A and B (redundant media)

A/B.

Media Configuration

In order for RSNetWorx for ControlNet software to create an accurate slot time to wait for missing nodes, a media configura tion must be created. The media configuration consists of a list of any cable or repeaters used by the media system and their quantity.

Important:

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.

A media configuration is created on the Media Configuration property page accessed from the network properties window :

Rev. March 2002


5--12


Here’s How

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

•


As your instructor demonstrates these procedures, follow along in the ControlNet Network Procedures Guide .

Exercise

In this exercise, you will configure an offline ControlNet network.

Context: The CNET Coaster’s 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: 1. Create a configuration file.

"

To understand the requirements of the application, review section two of the Functional Specification appendix. 2. Create an offline netw ork configuratio n. 3. Configure device parameters. 4. Configure chassis. 5. Configure network properties. 6. Save the configuration.

How Did You Do?





Rev. March 2002

5--13


5--14


Answers

Exercise 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 netw ork configuration

•

configured all devices

•

configured all chassis

If you have configured your network correctly , the Network Parameters property page should look like the following graphic:




5--15

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. March 2002


5--16




Lesson

6

Going Online to a ControlNet Network What You Will Learn

After completing this lesson, you will be able to go online to a ControlNet network by performing the following tasks: •

Configure a communications driver

•


Why These Skills Are Important Having the skills to go online to a ControlNet network is important for the following reasons :

Before You Begin

•

Configuring a communicatio ns driver makes it poss ible for a user to upload, download, go online, update firmware, and send files over a network to its devices.

•

Going online to a network allow s a user to configure, monito r, or troubleshoot a network and its operations.

RSLinx

Software

RSLinx software is used to create and edit the configuration of communications drivers required softwar e programs communicate with networks and by theirvarious devices. RSLinx softwaretois also used to select communic ations 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.

Important:

Rev. March 2002

Once opened, RSLinx software can be minimized but not closed. Closing the softw are while it is in use will end communications betwe en the computer and the network.

E 2002 Rockwell Automation. All rights reserved. GO1s200

6--2

Going Online to a ControlNet t 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 acc ess a network with a computer’s communications card

•

Allows a user to upload, downl oad, or go online to a networ k

Rev. March 2002 GO1s200


6 -- 3

ControlNet Communications Cards With a driver, a ControlNet communication s 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: •

1784-KTCX15 for access to a ControlNet networ k from a 16-bit ISA or 32-bit EISA-compat ible desktop computer

•

1784-PCC for access to a ControlN et network from any Microsoft Windows-based computer with a PC card interface

•

such as a laptop/notebook computer 1784-PCIC for access to a ControlN et network from a deskt op computer with a PCI bus

1784-KTCX15 Communications Card

A 1784-KTCX15 communication card lets a 16-bit ISA or 32-bit EISA compatible computer communica te 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:

Rev. March 2002

•

Base memory address (factory default is D000:0000), whic h will allow the card and the host computer to exchange data

•

Base I/O address (factory default is 220), whi ch will allow the card’s I/O devices to receive commands from the computer

Important:

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 card’s dip switch settings to an available address.

Important:

You will need to know the phys ical addresses set on the card to configure the driver in RSLinx software.


6--4


The addresses are set using dip switches on the card, as shown in the following graphic:

DIP Switches

For ControlNet scheduling, the 1784-KTCX15 card should be assigned a node address that meets the following guidelines in order to conserve bandwidth: •

A node address tha t is above maximum sche duled node (SMA X) 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 tha t does not to skip node numbers becaus e skipping node numbers wastes unschedule d bandwidth.

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 communic ations 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 computer’s operating system: •

•

•

Windows 95/98/Me systems require a Virtual Device Driver (VXD), which contains .inf and .vxd files. Windows NT r requires an NT driver, which uses setup.exe, unpccnt.exe, and pcc_config.exe files. Windows 2000 requires a Windows Driver Model (WDM), which contains .inf and .sys files.

Important:


Failure to install the correct driver files could result in unpredictable system operation.



6 -- 5

For ControlNet scheduling , the 1784-PCC card should be assigned a node address that meets the following guidelines in order to conserve bandwidth: •

A node address th at is above maximum sch eduled node (SMA X) 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 tha t does not to skip node numbers becaus e skipping node numbers wastes unscheduled bandwidth.

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 Software, version 2.2 Service Pack 2 or later

•

The combination of RSLinx Software , version 2.2 Servic e Pack 1 and SoftLogix t 5800 software, version 6.0

A 1784-PCIC communications card is a messaging only card that provides ControlNe t monitoring and configuration capabilities. The 1784-PCICS communications card provides ControlNet I/O bridging in addition to monitoring and configuration capabilitie s. For ControlNet schedulin g, the 1784-PCIC card should be assigned a node address that meets the following guidelines in order to conserve bandwidth: •

A node address th at is above maximum sch eduled node (SMA X) 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 tha t does not to skip node numbers becaus e skipping node numbers wastes unscheduled bandwidth.

A 1784-PCICS communications card is unique for its ControlNet I/O bridging capabilitie s and must have a node address below maximum scheduled node (SMAX) in order to utilize its ControlNet I/O bridging capabilitie s that take place during scheduled communications.

"

Rev. March 2002

RSNetWorx for ControlNet software will automatically adjust maximum schedule d node to accommodate the 1784-PCICS communications card if it is not done by the user.


6--6


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. 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

Here’s How

To go online to a ControlNet network by performing the following tasks: Configure a communications driver • •


As your instructor demonstrates these procedures, follow along in the ControlNet Networks Procedures Guide.




Exercise

6 -- 7

In this exercise, you will go online to a ControlNet network.

Context: The CNET Coaster’s networ k has been installed and the offline network configur ation 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 Coaster’s 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: 1. Configure a communications driver. 2. If it is not open already , open the network3.xc net work configuration file. 3. Go online to the CNET Coaste r’s network. 4. Download the configuration file to the netwo rk.

" How Did You Do?

Rev. March 2002

For help, see the ControlNet Networks Procedures Guide.



6--8


Answers

Exercise 1. If you have a KTCX15 commun ications card and have configured the driver correctly , the driver configurat ion 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




6 -- 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 gone online successfull y, you will receive the following system responses: •

A online status icon appears to be scanning in the upp er right hand corner of the RSNetWorx for ControlNet main window.

•

All channel LEDs on all device s should match the media redundancy configuration. No status icons appear over the nodes in the net work configuration.

•

"

Rev. March 2002

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.


6--10




Lesson

7

Entering Scheduled ControlNet I/O Data Connections for Logix5000 Controllers What You Will Learn

After completing this lesson, you will 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 Cont rolNet bridge to an I/O configur ation

•

Add a Logix5000 I/O m odule to an I/O conf iguration

•

Schedule communications for Logix5000 controlle rs

Why These Skills Are Important Having the skills to correctly enter scheduled I/O data connections is important for the following reasons:

Before You Begin

•

Entering scheduled I/O data conne ctions defines how and when data is transferred over a network between devices.

•

Scheduling communications enables any sc heduled data connection ensuring that data is transferred over a network how and when the scheduled data connection dictates.

RSLogix 5000

Software

As the main programming and configuration tool for all Logix5000 systems, RSLogix 5000 software is used to perform the following tasks:

Rev. March 2002

•

Create and edit ladder logic

•

Monitor active data online

•

Configure controller communications

•

Configure I/O modules and devices

E 2002 Rockwell Automation. All rights reserved. SL1s200

7--2

Entering Scheduled ControlNet t I/O Data Connections for Logix5000 t Controllers

The following graphic is a standard configuration of the RSLogix 5000 main window:

Controller Organizer Ladder Logic Window

Results Window

I/O Configuration All devices that communicate with a controller must be added to the I/O configuration of the controller project, as shown in the following graphic:

Remote Devices Communicating over a ControlNet Network Local Device Communicating over the Backplane


Rev. March 2002 SL1s200


7 -- 3

I/O Configuration Properties The following parameters must be configured in RSLogix 5000 software in order for a device to communicate with a Logix500 controller: • •

Name Device location

•

Communications format

•

Electronic keying

• •

Revision level Requested packet interval

Communications Format The communicatio ns 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 Each module in a Logix5000 system supports a limited number of active connection s. 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:

Rev. March 2002

•

Direct connection

•

Rack optimization


7--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 con figuration that reference s 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 c ontroller will automatically send the module configuration. the configuration is appropriate for the mo dule in the slot, a -- If connection is made and operation begins.

-- If the connection is inappropr iate for the modul e in the slot, •

the connection is rejected. The controller ma intains and monitor s the connection.

•

The module sends data at its co nfigured rate.

•

Module status and diagnos tic data is available.

•

Any break in the connectio ns causes the con troller to set fault status bits in the data area for the associated controller.

Important:

Direct connections are required by all analog modules.

Example: Direct Connection

With direct connections, data from three analog I/O modules in a remote ControlLogix t chassis is sent at three different rates, as shown in the following graphic: Remote I/O Modules

Controller

5 ms 40 ms 20 ms




7 -- 5

Rack Optimization

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 digita l modules at one rate, as specified by the remote 1756-CNB module.

•

Device status and diagnosti c information is limited.

•

Eight bytes of data are autom atically added per chassis slot when producing arrays.

Important:

Rack optimized connections can only be used by digital remote I/O modules.

Example: Rack Optimization

Data from three digital I/O modules in a remote chassis is sent simultaneously at a rate specified by the 1756-CNB module, as shown in the following graphic: Digital Remote I/O Modules

Controller

5 ms (Rate of 1756-CNB)

Important:

"

Rev. March 2002

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.

Placing remote digital I/O in the same chassis and selecting a “Rack-Optimized” option for the communications format of the remote communicat ion device conserves connections when using remote I/O.


7--6


Example: Direct Connections vs. Rack Optimization

The following table outlines the number of connections used when a direct connection communications format is selected for each module: Connections Per Module

Connection Type Controller to local 1756-I/O modules

1

Module Quantity 2

Total Connections 2

Controller to remote 1756-I/O modules

1

3

Controller to remote 1756-CNB module

1

1

1

Total

6

3

The following table outlines the number of connections when using rack optimization for the same modules: Connections Per Module

Connection Type Controller to local 1756-I/O module Controller to remote 1756-CNB module

1

Module Quantity 2

1

Total Connections 2

1

1

Total

3

Ownership Controllers can be assigned varying levels of ownership that define their relationship to a module. The following connection types connote differe nt levels of ownership a controller can have:


•

Owner connection

•

Listen-only connection



7 -- 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 sys tem must be owned by a Logix5000 controller:

-- Output modules can have only one ow ner. -- Input modules can have multip le owners. •

Owners can be local or remote.

•

The owner contro ller sends configuration data to the module to define behavior and begin operation.

•

Each module mus t maintain communi cations with a minimu m of one owner to continue operation.

•

Multiple owners of the same input module mus t have the 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 com pared to the first module’s configuration data.

-- If another contr oller 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.

Important:

To ensure that the module configurations for two owner controller’s projects are identical, copy the configured module from the I/O Configuration folder of one controller’s project and paste it in the I/O Configuration folder of the second controller’s project.

Important:

If an owner breaks connection with the module, the module will continue to multicast data because of the connection maintained by an alternate owner, as shown in the following graphic: Ownership Maintained

Ownership Broken

Input Module

Rev. March 2002


7--8


Listen-Only Connection

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 a n I/O module even if it is not an owner.

•

The listen-only controller does not need to hold the I/O module’ s configuration.

•

A listen-only controller will not rece ive configuration data. Important: If the connection between the owner and the module is broken, all listen-only connections are also lost, as shown in the following graphic: Connection Broken

Listen-Only Connection Also Lost

Input Module

Important:

A listen-only communications format uses one of the available 250 connections.

Electronic Keying Electronic keying is a safety feature that compares the user-supplied information for a module to the actual module information that is read online. The following information is used for the comparison: •


Vendor

•

Product type

•

Catalog number

•

Major revision

•

Minor revision



7 -- 9

The following electronic keying levels are available: To allow a connection . . .

Then select the following level of electronic keying . . .

When all parameters match Exact Match the inserted module When all parameters except the minor revision match the inserted module

Compatible Match Disable Keying ATTENTION: Use the disable keying option

Regardless of inserted module’s type

!

with extreme caution. Allowing the wrong module to complete a connection can cause unpredictable machine operation that can lead to machine damage or personal injury.

Requested Packet Interval (RPI) 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 characteristi cs: •

Different requested packet intervals may be assigned for different scheduled connections.

•

Up to eight differe nt update interval s, each rate a binary multip le of the network update time, may be used by different scheduled

•

"

data connections on the network. The requirements of the applicati on 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 RSNetWorxt 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) 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. March 2002


7--10


Example: Actual Packet Interval

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 packe t interval must be equal to or faste r than the requested packet interval of 22 ms. 40 ms would update the data too slowly , creating a possibl e hazard to application success. 10 ms would update the data too fast, cre ating an unneces sary drain on network resources that could be allocated to other scheduled data connections or to unscheduled bandwidth.

Network Schedule 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, RSNetW orx 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 inter vals of each data connection

•

Evaluates the bandw idth requirements for actual packet interva ls and data sizes of each data connection

•

Schedules a connection patter n based on the evaluation of each data connection that most efficiently uses scheduled bandwidth

Example: Network Schedule

The following graphic demonstrates a network schedule. The schedule operate s in following manner: A. The network update s at an interval of 5 ms as defined by the network update time. B. Connection A updates ever y network update interval, because its actual packet interval is 5 ms. E 2002 Rockwell Automation. All rights reserved.



7--11

C. Connection B updates every second network update interva l, 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 sched uled during each network update interval, using scheduled bandwidth more consistently. The following graphic shows the schedule: Time_______5 ms________10 ms________20 ms_______30 ms_______40 ms_______50 ms Network Update Time = 5 ms Actual Packet Interval for Connection A = 5 ms Actual Packet Interval for Connection B = 10 ms

Network Update Network Update Network Update Network Update Network Update Network Update Interval 1 Interval 2 Interval 3 Interval 4 Interval 5 Interval 6 Connection A Connection B

Connection A

Co nnec ti on A

Connection B Connection C

Co nnec ti on A

Co nnec ti on A

Connec ti on A

Connection B Connection C

Actual Packet Interval for Connection C = 20 ms

Here’s How

To enter scheduled ControlNet I/O data connections for Logix5000 controllers by completing the following tasks: •

Add a Logix5000 Cont rolNet bridge to an I/O configur ation

•

Add an I/O module to an I/O configuration

•

Schedule communications for Logix5000 controlle rs

As your instructor demonstrates these procedures, follow along in the ControlNet Network Procedures Guide.

Rev. March 2002


7--12


Exercise

In this exercise, you will enter 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 three, 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: 1. Open controller6.acd using RSLogix 5000 softwa re. 2. Add the local 1756-CN B ControlNet bridg e at node four, slot zero to the I/O configuration.

"

To understand the requirements of the application, review section six of the Functional Specification appendix. 3. Add the 1794-ACN15 commu nications adapter at node three to the I/O configuration. 4. Add the 1794-IE4X OE2/B analog module at node thre e, slot zero to the I/O configuration. 5. Add the 1794-IB10X OB6/A digital module at node three, slot one to the I/O configuration. 6. Download the project that contains the I/O con figuration to the controller at node four, slot one.

"

For help, see the ControlNet Networks Procedures Guide. 7. Schedule communications. 8. Change the control ler’s operating mode to Run.

"

For help, see the ControlNet Networks Procedures Guide. 9. To simulate the speed of the roller coaster car , turn the pot on the Logix5000 controller box.

How Did You Do?





Rev. March 2002

7--13


7--14


Answers

Exercise To verify if the scheduled data connection is functioning properly, complete the following steps: 1. Verify that the meter changes with chang es in the pot. 2. Verify that if the pot is not in the range of 4 to 6, the third pushbutton in the Logix5000 controller box illuminates to signify an alarm condition.



Lesson

8

Configuring an Ethernet Network in a Logix5000 System What You Will Learn

After completing this lesson, you will be able to configure an Ethernet network in a Logix5000 system by performing the following tasks: •

Assign a computer IP (Interne t Protocol) addr ess

•

Determine a computer IP address Assign an IP address to a 1756- ENET module using RSLinx t software

•

•

Add a 1756-ENET module to the I/O conf iguration of an RSLogix 5000 t project

•

Test a 1756-ENET module IP address

•

Configure a TCP/IP (Transmission Control Protocol/Internet Protocol) communications driver

•

View data using the RSLinx Data M onitor

•

View module inform ation using 1756-EN ET/B module web pages

Why These Skills Are Important Correctly configuring an Ethernet network in a Logix5000 system will allow you to take advantage of the following benefits:

Before You Begin

•

At the information level, an Eth ernet network provides enterprise-wide access to plant-floor data.

•

With its high bandw idth, an Ethernet netw ork allows a great variety of equipment available from many vendors to communicate over vast distances.

Ethernet Network Overview Ethernet networks support protocols that provide sophistica ted data transfer and network manageme nt. Such protocols include: •

Rev. February 2001

TCP/IP (Transmission Control Protocol/Internet Protocol)

•

UDP (User Datagram Protocol)

•

Ethernet/IP (Industrial Protocol)

E 2001 Rockwell International Corporation. ETHs56r

8--2

Configuring an Ethernet r Network in a Logix5000 t System

TCP/IP

TCP/IP is a transport-layer protocol and network layer protocol commonly used for communications within networks and across internetworks. This protocol is used where time is not a critical factor, such as uploading and downloading. UDP

UDP is a simpler transport protocol used by devices that require minimal transport service. UDP is smaller, simpler, and faster than TCP andiscan operate in unicast, and broadcast mode. This network used for real time I/Omulticast, messaging. Ethernet/IP

Ethernet/IP is a protocol that supports both real-time I/O and non-time critical messaging.

Topologies The Ethernet network supports the following cabling topologies: • • •

Star Trunkline/dropline (bus) Ring

The cabling options and data rates of an Ethernet network are outlined in the following table: Cable Options

Data Transmission Rate

10Base5 1B0ase2

Maximum Cable Length 500m

10 Mbps

10 BaseT 10BaseFL

Maximum Drop Cable Length

100

50 m

18m5

Maximum Number of Nodes

30 100m

200m

N/A N/A

2 (peer-to-peer) 1,024 per LAN 2(peer-to-peer)

Component Terms The following components may be part of a Logix5000 Ethernet network: Gateway: A device used to connect networks that use different protocols so that information can be passed from one network to another.


Rev. February 2001 ETHs56r

Configuring an Ethernetr Network in a Logix5000 t System

8 -- 3

Transceiver: A device that connects a computer to a network. This device both receives and transmits signals. It switches the parallel data stream used on the computer into a serial data stream used in the cables connecting the computers. Bridge: A device used to connect two LANs. It allows devices on either network to access resources on the other. Bridges can be used to increase the length of a network or the number of nodes. A bridge makes connections at the data link layer of the Ethernet network model. Router: An address -sensitive repeate r used to connect networks of different types, such as those using different architectures and protocols. Routers work at the network layer of the Ethernet network model, determine the best path for sending information, and filter broadcast traffic to the local network. Hub: A connectivity component that provides a common connection among computers in a star topology. Active hubs require electrical power and are able to regenerate and retransmit network data. Switch: A network device that cross connects devices or network segments. A switch provides each sender/rece iver the full network bandwidth, reduces collisions, and increases determinism.

Addressing Terms The following terms are defined as they apply to Ethernet network addresses: TCP/IP: An industry standard suite of protocols providing a routable, enterprise networking and access to the Internet and its resources. IP Address: A logical 32-bit address used to identify a device on an Ethernet network. An IP address must be in the format xxx.xxx.xxx.xxx, where each xxx is from 0 to 255. E.g., 130.150.131.100 or 130.151.138.9

Important:

The first octet (level) of any IP address may not be 127, or a number greater than 223. These values are reserved.

Important:

Your available plant IP addresses are assigned. Check with yourIP plant IT person or network administrator for available addresses.

Rev. February 2001


8--4


IP addresses have a network portion and a node portion of the address. The class of the address determines how many octets are in the network portion and how many are in the node portion, as detailed in the following table: Class

Pattern

A

Network.Node.Node.Node

B

Network.Network.Node.Node

C

Network.Network.Network.Node

Important:

For Rockwell Automation equipment, the first three octets of the IP address should exactly match the other Ethernet equipment that is communicating on the same network.

Subnet Mask: A mask that identifies which bits of an IP address correspond to the network and which bits correspond to the node. The subnet mask uses the same format as the IP address. E.g., 255.255.255.0. DNS (Domain Name Service): A method for resolving (pairing) computer IP addresse s with alphanumeric computer names in a database. This allows computer users to identify computers and other devices by names rather than IP addresses. Default Gateway Address: The destination where an IP device sends data packets that are intended for remote networks: •

•


If a route to an exac t destination is n ot configured, the packet is sent to the default gateway address. If a default gatewa y address is not confi gured, the traffic is limited to the local network or gateway.



8 -- 5

Assigning a Computer IP Address

As with a node number in other networks, an IP address cannot be assigned to more than one device, including a computer. A computer IP address can be dynamically or manually set, as shown in the following graphic:

Dynamic Option Manual Option

Important:

Rev. February 2001

If the IP address is dynamically assigned by a DHCP server, it will affect existing message configurations that point to a specific IP address.


8--6


Determining a Computer IP Address

A computer IP address can be determined after it is assigned using an MS-DOSr IPConfig command, as shown in the following graphic:

Command

Command Prompt

Response

1756-ENET Module A 1756-ENET communications bridge module, shown in the following graphic, connects a Logix5000 backplane to an Ethernet network:

Health and Status Indicators:

Ethernet

RXD (Receive) TXD (Transmit) OK

MAC ID/Hardware Address

AUI Connector

10 BaseT Connector




8 -- 7

Health and Status Indicators

The states of the TXD and RXD indicators are described in the following table: If this indicator TXD RXD

OK

Is . . .

Then the module is . . .

Green

Transmittingdata

Off

Noat ctive

Green

Receivingdata

Off

Noat ctive

Off

Notoperating

Red, then flashing red or flashing green

Performing powerup diagnostics

Green

Operating

Red flashing

Not configured

Red

Unrecoverablefault

AUI (Attachment Unit Interface) Connector

An AUI connector is the connector used with standard Ethernet that often includes a cable running off of the main, or backbone, coaxial cable. If an application requires the module door to be closed, the following custom AUI connector s can be used: •

1756-TC02 -- 2 meters

•

1756-TC15 -- 15 meters

10 BaseT Connector

This port can be used to connect to the module using an RJ45 connector. MAC (Media Access Control) ID

The MAC ID is a hardware address assigned to each device by the vendor. This address is marked on a label on the module.

"

Rev. February 2001

Hardware addresses are limited to a unique band of numbers assigned to each vendor.


8--8


1756-ENET Module IP Address An IP and subnet address for a 1756-ENET module can be assigned using one of the following methods: •

Assign an IP address to a 1756- ENET module using a BootP (Bootstrap Protocol) utility

•

Assign an IP addre ss to a 1756-ENET module using RSL inx Software

•

Add a 1756-ENET module to the I/O conf iguration of an RSLogix 5000 project

Assigning an IP Address to a 1756-ENET Module Using a BootP Utility

An IP address can be assigned automatically using the BootP utility on a computer: •

This service as signs an available IP addres s, subnet mask, and gateway address to a device each time power is cycled to the device.

•

The user pairs IP address es with the fixed, factory-a ssigned MAC ID hardware addresses in a text file. The same IP address is then reassigned to the same hardware address each time power is cycled and the BootP utility is running.

Important:


When BootP is enabled, the module gets its configuration dynamically from a BootP server on the network and ignores any addresses you may have assigned. The factory default is BootP enabled.



8 -- 9

Assigning an IP Address to a 1756-ENET Module Using RSLinx Software

An IP address can be assigned using RSLinx software, version 2.2 or later, as shown in the following graphic:

Cleared Addresses

Adding a 1756-ENET Module to the I/O Configuration of an RSLogix 5000 Project

An IP address can be assigned using RSLogix 5000 software. The 1756-ENET module must be added to the I/O configuration. After downloading the project, the address can be set, as shown in the following graphic:

Addresses Assigned Online

Must be Clicked Cleared

Rev. February 2001


8--10


"

Adding a communications module to the I/O configuration of an RSLogix 5000 project allows you to select it as the target device in message procedures. This is much easier than manually building a communications path.

Testing a 1756-ENET Module IP Address Communications with the IP address of a 1756-ENET module can be tested using an MS-DOS Ping command, as shown in the following graphic: Command Command Prompt

Successful Response

Configuring a TCP/IP Communications Driver RSLinx software is used to add, configure, and modify the TCP/IP communications drivers required by various Rockwell Software programs. One driver can be config ured for multiple Ethe rnet networks, as shown in the following graphic:

Networks

Important:


If you are using a ControlLogix system as a communications gateway, you must use the default driver name as assigned in RSLinx software. Change only the characters after the identifying portion of the driver name. For example, change TCP-1 to TCP-1PaperLine.



8--11

Viewing Data Using the RSLinx Data Monitor Note that in RSLinx software with an activation file, you can view controller tags by selecting a module and viewing the Data Monitor, as shown in the following graphic:

Expanded Tag

Read Only Data

Viewing Module Information Using 1756-ENET/B Module Web Pages Using the IP can address of a using 1756-ENET module in a chassis, or r Communicator information viewed Netscape Microsoftr Internet Explorer software. This information includes:

Rev. February 2001

•

Module information

•

TCP/IP configuration Information

•

Diagnostic configuration

•

Chassis configuration


8--12


Chassis configuration, which allows you to select and view information on each module, is shown in the following graphic:

IP Address of a 1756-ENET Module in the Chassis

Location/Go to Line

Chassis Configuration

Here’s How

To configure an Ethernet network in a Logix5000 system by performing the following tasks: •

Assign a computer IP address

•

Determine a computer IP address

•

Assign an IP addre ss to a 1756-ENET module using RSL inx software

•

Add a 1756-ENET module to the I/O conf iguration of an RSLogix 5000 project

•

Test a 1756-ENET module IP address

•

Configure a TCP/IP communications driver

•

View data using the RSLinx Data M onitor

•

View module informa tion using 1756-ENET/B module web pages

As your instructor demonstrates these procedures, follow along in the Logix5000 Controllers Procedures Guide.




Exercise

8--13

In this exercise, you will configure an Ethernet network in a Logix5000 system.

Context: You are part of a team that has programmed a Logix5000 compress or assembly line. In order to monitor and control the production line, a separate programming team has developed an RSView32 t HMI application. Your team has decided to use an Ethernet network to transfer data between the controllers and the HMI application. You are now ready to configure a high speed Ethernet network for use in a Logix5000 system.

"

For addresses and subnet masks, refer to the Node Address Assignments appendix.

Directions: 1. Manually assign the IP address, subnet mask, and defaul t gateway address to your computer.

"

If any address is changed, reboot the computer. 2. Write the IP address of your compute r:

3. Using an MS-DOS command, determin e your computer IP address. 4. If not already done, conne ct the provided Etherne t cable to the 1756-ENET/B module in your workstation. 5. In RSLinx softwar e, verify that a communications drive r other than Ethernet has been configured. If not, configure a serial, DH+, or ControlNet communications driver.

"

For help, see your instructor or refer to the Logix5000 Controllers Procedures Guide. 6. Open the ETH_Slot_3 .acd file stored in Ethernet folder locate d in C:\CCP144.

"

This project will be used to send data to the HMI project in another lesson. 7. Add the 1756-ENET/ B module to the I/O configuratio n of the

"

Rev. February 2001

RSLogix 5000 project. Be sure to download the project and assign the IP address, subnet mask, and default gateway address in the Node Address Assignments appendix. E 2001 Rockwell International Corporation. ETHs56r

8--14


8. Write the IP address assigned to the module:

9. Does this IP address mat ch the first three octets of your computer IP address as recorded in Step 2.?

10. Save this projec t as Slot_3.acd in the Student folde r located in C:\CCP144.

"

This file will be required for other lessons. 11. Using an MS-DOS command, tes t your 1756-ENET module IP address. 12. Configure a TCP/IP communica tions driver that communicates with each workstation the classroom.

"

If a TCP/IP driver has already been configured, stop the driver, and then delete it. Then, configure a new TCP/IP communica tions driver that communicates with each workstation the classroom. 13. When the driver is running, exam ine the LEDs on the 1756-ENET module in your workstation. 14. Is the OK light steady green?

15. Is the module receiving data?

16. In the RSLinx RSWho window , expand the network branc h for the TCP/IP driver that you created and view the modules in your backplane. 17. View the modules in another backplane. 18. View the data for the controll er in slot 1 of your workstation using the RSLinx Data Monitor . 19. View the firmware revisions and other module informa tion for the modules in your workstation using 1756-ENET/B module web pages.

How Did You Do?





Rev. February 2001

8--15


8--16


Answers

Exercise 1. The IP address, subne t mask, and default gateway addres s of your computer should be assigned in the following manner:

Manual Option Addresses and Subnet Mask from Appendix

3. The IP address, subne t mask, and default gateway addres s of the computer should be determined by typing IPConfig at the MS-DOS prompt. 7. The IP address and subnet mask of your 1756-ENET mo dule should be assigned in the following manner:

IP Address and Subnet Mask from the Appendix

Must Be Clicked to Send the Configuration Cleared




8--17

11. The module should be tested by typing Ping followed by the IP address of the module in at the MS-DOS command prompt. 12. Your communications driver should contain the following configuration information:

IP Address Assigned to the Module for Each Network

15. The module RXD ligh t should be flashing green to indicate tha t the module is receiving data. 19. Module information should be viewed by typing the IP addres s of a 1756-ENET module in the chassis in the Location/Go to line of a browser using the following format:

IP Address of a 1756-ENET Module in the Chassis

Rev. February 2001


8--18




Appendix

A

Node Address Assignments The following node addresses are used in the classroom: PLC Processor ControlNet Address

Station (Group) Number

Station 1 1 (Instructor)

PanelView Terminal ControlNet Address

1756-CNB Node Address

1784KTCX Address

1756-DHRIO Module DH+ Address

PLC Processor DH+ Address

IP Addresses**

Computer: 2

3

20

1

11

1756-ENET module: Computer:

Statio2n

4

5

6

21

2

12

3

20

3

13

1756-ENET module:

Separate ControlNet Network Computer: Statio3n

1

2

1756-ENET module: Computer:

Statio4n

4

5

6

21

4

14

1756-ENET module:

Separate ControlNet Network Computer: Statio5n

1

2

3

20

5

15

Statio6n

4

5

6

21

6

16

1756-ENET module: Computer: 1756-ENET module:

Separate ControlNet Network

* The Ethernet r subnet mask for the classroom is: ______________ * The default gatew ay address is: _______________________ ____ Each DeviceNett network uses these addresses: •

Rev. August 2001

1756-DNB module at node 0

•

ArmorBlockt MaXum I/O at node 1

•

Series 9000 photoelectric sensor at node 2

•

RediSTATIONt operator interface at node 3

•

160 SSC variable speed drive at node 4

•

PanelView 600 color Device Net terminal at node 5 E Rockwell Automation. All rights reserved. CAA_AP56r

A--2

Node Address Assignments

E Rockwell Automation. All rights reserved. CAA_AP56r

Rev. August 2001

Appendix

B

Input/Output Device Assignments The following inputs and outputs devices on the Logix5000 workstation are used in this course: t u p In e r u s s e s r e r P P e k a t S d n a

I0 A

e k a t S d n a s s e r P

0 O A

re u s s e r P

1 I A

t u p n I

l d e W

r te e M re u s s re P

e r u s s e r P ld e W

1 O A

9 3 I O D D

I7 D

0 1 O D

1 1 I D

r te e M

1 1 O D

5 I D

8 O D

I4 D

e iz t e ll a P

I2 D

I1 D

6 O D

3 O D

I6 D

7 O D

t e s e R

n re e i p W O

I5 D

s t u p n I

Rev. August 2001

ts u p t u O

rt ta S

0 O D

t c je e R

tl u a F

9 I D

4 I D

1 O D r o y e v n o C

5 O D

3 I D

d l e

e k a t S

s s e r P

0 I D

4 O D

0 I1 D

W

8 I D p to S

2 O D

2 I1 D In rt a P

r o s n e S

s e ic v e . d d e d u s lle e to b n la e n r U a

E Rockwell Automation. All rights reserved. CAB_AP56r

B--2

Input/Output Device Assignments

E Rockwell Automation. All rights reserved. CAB_AP56r

Rev. August 2001

Appendix

C

160 SSC Variable Speed Drive Data Assembly The information in this appendix is from the DeviceNet Communication Module -- Catalog Number 0160-DN2 (publication 0169-5.18): Table 1: Assembly 21 Data Format (Reversing Speed Control Output Assembly) Byte

Control Word

Bit7

0

Bit6 NetRef

Bit5

Bit4

Bit3

Bit2

Bit1

Net Control

Fault Reset

Bit0 RunRev

RunFwd

1

Speed Word

2

SpeedReferenceRPM(LowByte)

3

SpeedReferenceRPM(HighByte)

Table 1: Assembly 71 Data Format (Extended Speed Control Input Assembly) Byte

Control Word

0

Bit7 At Speed

Bit6

Bit5

Ref

Ctrl

From Net

From Net

Bit4

Ready

Bit3

Bit2 Running Reverse

Bit1 Running Forward

Bit0

Faulted

1

Speed Word

Rev. August 2001

2

SpeedActualRPM(LowByte)

3

SpeedActualRPM(HighByte)

E Rockwell Automation. All rights reserved. CAC_AP56r

C--2

160 SSC Variable Speed Drive Data Assembly

E Rockwell Automation. All rights reserved. CAC_AP56r

Rev. August 2001

Appendix

D

Functional Specification 1. Media System

The following functional specifica tions are for the media system of the CNET Coaster: •

Downtime will not cause any noticea ble loss in ride safet y or park revenue.

•

The application, while outside, sho uld be considered a light

•

industrial application. No future nodes will be added.

•

A right-angle T-tap will be used for every node, exc ept the 1756-CNB nodes.

•

A straight T-tap will be used for any 1756-CN B nodes.

The following graphic shows the nodes that will reside on the network and the distance between them:

80 m (262 ft)

PLC-5 Processor: Node 1

Rev. August 2001

160 m (524 ft)

1794-ACN Node 2

300 m (984 ft)

1794-ACN Node 3

60 m (196 ft)

1756-CNB Communications Node 4 Card Node 5

E Rockwell Automation. All rights reserved. SP1_AP

D--2

Functional Specification

2. Network Configuration

The following functional specificat ions are for the network configuration of the CNET Coaster: •

In the 1794-ACN(R) Flex I/O t 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 thr ee, 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 chas sis, a 1756-CNB 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 devic e should be able to transmit scheduled data.

Important:

3. Scheduled I/O Data Connections for the PLC-5 Processor at Node One

If the device used for programming has scanner capabilites (i.e., a 1784-PCIC(S) communications card), then the device should be able to transmit scheduled data.

•

The fastest time a node must transmi t data is every 10 ms.

•

Nodes will use channel A.

•

600 m (1966 ft) of standard-PV C CM-CL2 coaxial cable will be used.

•

No repeaters will be used.

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 parame ters in order to fulfill the functional specificatio ns of the CNET Coaster’s network: DataFile StatusFile ConfigurationFile


FileSize N/A 1000

A d d re s s N12 N11

DataInputFile

1000

N9

DataOutputFile

1000

N10

Rev. August 2001


D -- 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 specificatio ns of the CNET Coaster’s network: Parameter

Value

Address

N/A

Slot

01

DeviceName

1794-OB16/A

ConnectionType Actual Packet Interval

ExclusiveOwner 10 ms

Requested Packet Interval

10 ms

InputAddress

N9:0

InpuSt ize

1

OutputAddress

N10:0

OutpuSt ize

1

StatusAddress

N12:0

Configuration Address

N11:0

ConfigurationSize

2

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 Coaster’s network: Parameter

Value

Address Slot

N/A 00

DeviceName

1794-IE4XOE2/B

ConnectionType

ExclusiveOwner

Actual Packet Interval

40 ms

Requested Packet Interval

40 ms

InputAddress InpuSt ize

N9:1 4

OutputAddress OutpuSt ize StatusAddress

Rev. August 2001

N10:1 2 N12:3

Configuration Address

N11:2

ConfigurationSize

4


D--4


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 paramete rs in order to fulfill the functional specifica tions of the CNET Coaster’s network: Parameter

Value

Address

1

Slot

N/A

DeviceName

PLC5/40C

BuffeIDr

1

ConnectionType

SendData

Actual Packet Interval

N/A

Requested Packet Interval InputAddress

N/A N/A

InpuSt ize

N/A

OutputAddress

N10:3

OutpuSt ize

2

StatusAddress

5. Unscheduled Messages from the PLC-5 Processor at Node One

N12:6

ConfigurationAddress

N/A

ConfigurationSize

N/A

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 Coaster’s network: Parameter

Value

ControlBlock Communication Command

PLC-5 Typed Write

Data Table Address (This PLC-5)

N7:0

SizeinElements

1

PorNt umber

2

Data Table Address (Target Device) Multihop

Multihop Path


MG13:0

N7:0 Yes From This PLC-5 at From Port 2 to 1756-CNB Node at To Address 4 to From ControlLogix Backplane to 1756 Backplane Slot at To Address 1 Rev. August 2001


6. Scheduled I/O Data Connections for the Logix5000 Controller at Node Four

D -- 5

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 Coaster’s network: Parameter

Value

Name

Local_CNB

Slot

0

Electronic Keying

DisableKeying

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 Coaster’s network: Parameter

Value

Name

Speed_Check

Node

3

ChassisSize

2

CommunicationFormat

None

Electronic Keying RPI

DisableKeying 20

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 Coaster’s network: Parameter

Value

Name Slot

Speed_Check_IO 0

CommunicationFormat

Data

Electronic Keying RPI

Rev. August 2001

DisableKeying 20

Input Configuration

All channels = 0 to 10 V / 0 to 20 mA

Output Configuration

All channels = 0 to 10 V / 0 to 20 mA


D--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 Coaster’s network: Parameter

Value

Name

Remote_Digital

Slot

1

CommunicationFormat ElectronicKeying RPI

7. Scheduled Messages from the Logix5000 Controller at Node Four

Data 10

DisableKeying

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 paramet ers in order to fulfill the functional specifica tions of the CNET Coaster’s network: Parameter Name DataType


Value produced_data DINT

Consumers

1

Style

Decimal

Rev. August 2001


8. Unscheduled Messages from the Logix5000 Controller at Node Four

D -- 7

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 specificati ons of the CNET Coaster’s network: Parameter

Value

ControlBlock Communication Command

PLC-5 Typed Write

Data Table Address (This PLC-5)

Exit_Data

SizeinElements Data Table Address (Target Device) Path

Rev. August 2001

Exit_Message

1 N7:1 1,0,2,1


D--8



Rev. August 2001

Appendix

E

Input/Output Device Assignments PLC-5 Processor Workstation I/O Device Assignments PB_0

Lap Bar 1 SS_0

Safety Check 1

SS_1

Safety Check 2 PL_1

SS_2

Safety Check 3 PL_2

PB_1

Lap Bar 2

Start PB_3

Lap Bar 4 SS_3

Logix5000

SS_0

Drive Speed

PB_2

Lap Bar 3

Passenger Exit

PL_0

SS_2

Start

Drive Speed Input

PL_3

Controller Workstattion I/O Device Assignments

PB_0 Safety Check 1 PL_0

Car Enters Station Speed Out of Range

PB_1 SS_1

SS_3

Speed After First Hill

Rev. August 2001

Safety Check 2

PL_1

PB_2 PL_2 PB_3

Brakes Engaged

PL_3

Speed After First Hill Input

E Rockwell Automation. All rights reserved. IO1_AP

E--2

Input/Output Device Assignments

E Rockwell Automation. All rights reserved. IO1_AP

Rev. August 2001

The following are registered trademarks of Rockwell Internationa l Corporation or its subsidiaries: PLC PLC-3 PHOTOSWITCH

PLC-2 PLC-5

The following are trademarks of Rockwell International Corporation or its subsidiaries : 1336FORCE 1336PLUS A.I. Series DataHighwayPlus DriveTools Logix5000 PanelBuilder RSLinx RSLogix500 RSView SLC SLC5/01 SLC5/03

1336IMPACT 1336PLUSII ControlLogix DH+ FlexI/0 Logix5550 PanelView RSLogix5 RSLogix5000 SCANPort SLC 500 SLC5/02 SLC5/04

Belden and Blue Hose are trademarks of Belden, Inc. ControlNet is a trademark of ControlNet International. DeviceNet is a trademark of the Open DeviceNet Vendor Association, Inc. (ODVA). Ethernet is a registered trademark of Intel Corporation, Xerox Corporation, and Digital Equipment Corporation. The following are registered trademarks of Microsoft Corporation: MS-DOS Windows Windows NT

PowerPoint Windows95

IBM is a registered trademark of International Business Machines Corporation. Pentium is a registered trademark of Intel Corporation. WinZip is a registered trademark of WinZip Computing, Inc. All other trademarks are the property of their respective holders and are hereby acknowledged.

Catalog Number -- ABT--SYS--TSM01 -- February 2003

E Rockwell Automation. All rights reserved. Printed in USA

ABT-SYS-TSM01 2003-02

Recommend Documents