CONTROLLOGIX

ControlLogix Essentials with RSLogix5000 Software Rockwell Automation (SEA)

Student Manual

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

• properly using, calibrating, operating, monitoring and maintaining all Products consistent with all Rockwell Automation or third--party provided instructions, warnings, recommendations and documentation; • ensuring that only properly trained personnel use, operate and maintain the Products at all times; • staying informed of all Product updates and alerts and implementing all updates and fixes; and • all other factors affecting the Products that are outside of the direct control of Rockwell Automation. Reproduction of the contents of the Documentation, in whole or in part, without written permission of Rockwell Automation is prohibited. Throughout this manual we use the following notes to make you aware of safety considerations: Identifies information about practices or circumstances that can cause an explosion in a hazardous environment, which may lead to personal injury or death, property damage, or economic loss.

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

Identifies information about practices or circumstances that can lead to personal injury or death, property damage, or economic loss. Attentions help you: • identify a hazard • avoid a hazard • recognize the consequence

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

Labels may be located on or inside the drive to alert people that surfaces may be dangerous temperatures.

Comment Form

Email: [email protected] or Fax:

440.646.4425

Page 1 of Date:

Contact Information: Name: Company and Location: Phone:

Email:

Comments (include lesson title, if applicable): Course or Product Name (Important):

Page 2

Table of Contents

Lessons IdentifyingLogix5000SystemComponents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1- 1

WhaYtoW u Lillearn ......... ........ ......... ......... ......... ......... ..... 1--1 WhyTheseSkillsAreImportant ......... ......... ......... ......... ........ .... 1-- 1 BeforYeoBuegin ......... ......... ......... ......... ......... ......... ...... 1--1 Logix5000ControD l isciplines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-- 2 ExampleB: ottlingLine ......... ........ ......... ......... ......... ........ 1-- 2 ControlLogixPlatformandComponents ......... ......... ......... ........ ....... 1-- 3 ControlLogiC x hassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-- 3 ControlLogixBackplane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-- 4 ControlLogixController . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-- 5 SafetCy ontrollers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-- 5 ControlLogixI/OModules ........ ......... ......... ......... ........ ....... 1--6 ControlLogixCommunicationsModules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-- 6 ControlLogixPlatformModularity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-- 7 Example:PlatformModularity ........ ......... ......... ......... ........ .... 1-- 7 FlexLogixPlatformandComponents ......... ......... ......... ......... ........ 1-- 8 R DaINil ......... ......... ......... ......... ......... ......... ........ . 1--8 FlexLogiC x ontroller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-- 8 FlexLogiIx/OModules ......... ........ ......... ......... ......... ........ 1--9 FlexLogixCommunicationsCards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CompactLogixPlatformandComponents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CompactLogixController . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CompactLogixI/OModules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CompactLogix Communications Modules/Converters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DriveLogixPlatformandComponents ........ ......... ......... ......... ........ SoftLogixPlatformandComponents ......... ......... ......... ......... ........

Exercise: Identifying Logix5000 System Components . . . . . . . . . . . . . . . . . . . . . .

1-- 9 1--10 1--10 1--11 1--11 1--12 1--12

1 -1 5

ExercAise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 -- 15 HoDwYidoDuo? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 -- 17 ExercBise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 -- 17 HoDwYidoDuo? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 -- 19 Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--20 ExercB ise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 -- 21

Identifying RSLogix 5000 Software Components

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

WhaYtoW u Lillearn ......... ........ ......... ......... ......... ......... ..... WhyTheseSkillsAreImportant ......... ......... ......... ......... ........ .... BeforYeoBuegin ......... ......... ......... ......... ......... ......... ......

2 -1 2--1 2-- 1 2--1

ii

Table of Contents

RSLogix5000ProgrammingSoftware ......... ......... ......... ......... ....... SoftwarBeenefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IdentifyingRSLogix5000SoftwareComponents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Toolbars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ControlleOr rganizer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HeSlypstem ........ ......... ......... ......... ......... ......... ........ ConfiguringtheRSLogix5000SoftwareDisplay ........ ......... ......... ......... . HerHeo’sw ........ ......... ......... ......... ......... ......... ........ ...

2--1 2 -- 1 2--2 2 -- 2 2 -- 4 2 -- 6 2-- 8 2 -- 9

ExercisEexe: rIcdAiseenti.fy. .i.n.g. .R. .SL. .o. g. .i.x. 5. .00. .0. S . .o. .ft. w . a. .r.e. C . . o. .m . p. o . .n. e . .n. t. s.

. . .. ..... .. .. .. .. .. . .. ... .. .. . ..... . . . 2 -- 12-1 1 1 HoDwYidoDuo? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-- 13 Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--14 ExercA ise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-- 14

Creating and Modifying an RSLogix 5000 Project

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

WhaYtoW u Lillearn ........ ......... ......... ......... ......... ........ ...... WhyTheseSkillsAreImportant ........ ......... ......... ......... ......... .... BefoY reoBuegin ......... ......... ........ ......... ......... ......... ....... RSLogix5000ProjecFt iles ........ ......... ......... ......... ......... ....... ProjecCt omponents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Routines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HerHeo’sw ........ ......... ......... ......... ......... ......... ........ ...

Exercise: Creating and Modifying an RSLogix 5000 Project

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

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

3 -7

ExercAise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 -- 7 HoDwYidoDuo? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 -- 7 ExercBise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 -- 8 HoDwYidoDuo? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 -- 9 Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--10 ExercA ise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-- 10 ExercB ise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-- 10 ExercB ise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-- 10

Transferring a Project File to a Logix5000 Controller

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

WhaYtoW u Lillearn ........ ......... ......... ......... ......... ........ ...... WhyTheseSkillsAreImportant ........ ......... ......... ......... ......... ....

4 -1 4 -- 1 4--1

BefoY reoBuegin ......... ......... ........ ......... ......... ......... ....... 4 -- 1 Uploading, Downloading, and Going Online to a Logix5000 Controller . . . . . . . . . . . . . . . . . . . . . 4--1 RSLinxClassicSoftware ......... ......... ......... ......... ......... ........ 4-- 3 CommunicationPs ath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 -- 4 CorrelatioEnrrors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 -- 5

iii

Table of Contents

Selecting and Changing a Controller’s Operating Mode ........ ......... ......... ..... RemotelyChangingControllerOperatingMode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HerHeo’sw ......... ......... ........ ......... ......... ......... ......... ..

Exercise: Transferring a Project File to a Logix5000 Controller

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

4-- 6 4-- 7 4--8

4-9

ExercAise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--9 HoDwYidoDuo? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 -- 10 ExercBise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 -- 10 HoDwYidoDuo? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--11 Answers ExercA ise. . . ............ .. .. .. ............ .. .. .. ............ .. .. .. ............ .. .. .. ............ .. .. .. ............ .. .. .. ............ .. .. .. ExercB ise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ExercB ise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ConfiguringLocal1756-I/OModules

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

4 -- 12 4--12 4 -- 13 4 -- 13

5- 1

WhaYtoW u Lillearn ......... ........ ......... ......... ......... ......... ..... 5--1 WhyTheseSkillsAreImportant ......... ......... ......... ......... ........ .... 5-- 1 BeforYeoBuegin ......... ......... ......... ......... ......... ......... ...... 5--1 1756-I/OModuleComponents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--1 RIUP(RemovalandInsertionUnderPower) ......... ......... ......... ........ .... 5-- 2 LEDStatusInformation ......... ......... ......... ......... ......... ........ . 5-- 3 Digitaal ndAnalogI/OModules ......... ......... ......... ......... ........ .... 5-- 3 Digita1l 756-I/OModules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--3 Analog 1756-I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--4 Locaal ndRemoteI/OModules ......... ......... ......... ......... ........ .... 5--5 LocaI/lO Modules ......... ........ ......... ......... ......... ......... .. 5--5 RemotIe/O Modules ......... ......... ......... ......... ......... ........ . 5--5 1756-I/OModuleIdentification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--6 I/O Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--6 GeneTrabl ........ ......... ......... ......... ......... ......... ........ . 5--7 ElectroniKceying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-- 8 CommunicationsFormat(Ownership) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-- 8 ConnectioTnab ........ ......... ......... ......... ......... ......... ...... 5--8 ConfiguratioTnab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--9 Asynchronous Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--10 IdentifyinganI/OModuleTag ........ ......... ......... ......... ......... ..... 5-- 11 ExampleI:npuBt aseTag ........ ......... ......... ......... ........ ....... 5--12 ExampleO : utpuBt aseTag ........ ......... ......... ......... ......... ..... 5-- 12 HerH e’osw ......... ......... ........ ......... ......... ......... ......... .. 5 -- 12

Exercise: Configuring Local 1756-I/O Modules

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

5 -1 3

ExercAise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 -- 13 HoDwYidoDuo? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 -- 14 ExercBise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 -- 15 HoDwYidoDuo? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 -- 16

iv

Table of Contents

Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ExercA ise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ExercB ise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Creating Tags and Monitoring Data in an RSLogix 5000 Project

5--18 5-- 18 5-- 19

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

WhaYtoW u Lillearn ........ ......... ......... ......... ......... ........ ...... WhyTheseSkillsAreImportant ........ ......... ......... ......... ......... .... BefoY reoBuegin ......... ......... ........ ......... ......... ......... ....... Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6-1 6 -- 1 6--1 6 -- 1 6 -- 1

D TaytapeTsags . .. .. .. .. .. .. .. .. . . .. .. .. .. .. .. .. .. . . .. .. .. .. .. .. .. . .. . .. .. .. .. .. .. .. . .. . .. .. .. .. .. .. .. . .. . .. .. .. .. .. .. .. . .. . .. .. .. .. .. .. .. . . 6 -- 2 6--3 Alias Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 -- 4 MonitoTragTsab ......... ......... ......... ......... ......... ........ ... 6-- 5 TagasnMdembers ........ ......... ......... ......... ......... ........ ... 6-- 5 DisplaSytyle ......... ......... ......... ......... ......... ......... ..... 6 -- 5 ExampleD : INTDisplayStyle ........ ......... ......... ......... ......... .... 6--5 ETdaitTgasb ......... ......... ......... ......... ......... ......... ..... 6 -- 6 MonitoringandEditingTag Values throughaRoutine ........ ......... ......... ....... 6-- 7 HerHeo’sw ........ ......... ......... ......... ......... ......... ........ ... 6 -- 7

Exercise: Creating Tags and Monitoring Data in an RSLogix 5000 Project . . . . . . .

6- 9

ExercAise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 -- 9 HoDwYidoDuo? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 -- 11 ExercBise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 -- 11 HoDwYidoDuo? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 -- 11 ExercC ise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-- 12 HoDwYidoDuo? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-- 13 Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--14 ExercA ise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-- 14 ExercB ise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-- 15 ExercC ise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-- 15

Monitoring Arrays and Tags of User-Defined Data Types in an RSLogix 5000 Project

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

WhaYtoW u Lillearn ........ ......... ......... ......... ......... ........ ...... WhyTheseSkillsAreImportant ........ ......... ......... ......... ......... .... BefoY reoBuegin ......... ......... ........ ......... ......... ......... ....... KTeryms ......... ......... ........ ......... ......... ......... ......... . ExamplAe:rray ......... ........ ......... ......... ......... ......... .... Array Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example:ThreeDimensionalArrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Advanced Array Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User-DefinedDataTypes ........ ......... ......... ......... ......... ........ Example:User-DefinedDataType ......... ......... ......... ........ ......... User-DefinedDataTypeAddressing ......... ......... ......... ........ .........

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

v

Table of Contents

Examples:User-DefinedDataTypeAddressing ........ ......... ......... ........ Example:ArraysandUser-DefinedDataTypes ......... ......... ......... ........ ExampleA: ddressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HerHeo’sw ......... ......... ........ ......... ......... ......... ......... ..

Exercise: Monitoring Arrays and Tags of User-Defined Data Types in an RSLogix 5000 Project ExerciAse HoDwYidoDuo?

7-- 4 7-- 4 7-- 5 7--5

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

7 -7

......... ......... ........ ......... ......... ......... ......... .. 7--7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--11

Answers ExercA ise. . . ............ .. .. .. ............ .. .. .. ............ .. .. .. ............ .. .. .. ............ .. .. .. ............ .. .. .. ............ .. .. ..

7 -- 12 7--12

Selecting Basic Ladder Logic Instructions for an RSLogix 5000 Routine . . . . . . . .

8- 1

WhaYtoW u Lillearn ......... ........ ......... ......... ......... ......... ..... 8--1 WhyTheseSkillsAreImportant ......... ......... ......... ......... ........ .... 8-- 1 BeforYeoBuegin ......... ......... ......... ......... ......... ......... ...... 8--1 BasiIcnstructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-- 1 ConditionalBitInputInstructions ......... ......... ......... ......... ........ . 8-- 1 ConditionalBitOutputInstruction ......... ......... ......... ......... ........ . 8-- 2 Example: ConditionalInput and Output Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 -- 2 OnS e hoInt struction ......... ......... ......... ......... ......... ........ . 8-- 3 ExampleO : NSInstruction ........ ......... ......... ......... ........ ....... 8-- 3 RetentiveBitOutputInstructions ......... ......... ......... ......... ........ . 8 -- 3 Example:OTLandOTUInstructions ......... ......... ......... ........ ....... 8 -- 4 TimeInr structions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-- 4 TON(TimeOr D n elay) ......... ........ ......... ......... ......... ........ 8--5 ExampleT: ONInstruction ........ ......... ......... ......... ........ ....... 8-- 6

Exercise: Selecting Basic Ladder Logic Instructions foranRSLogix5000Routine ........ ........ ......... ........ ........

8- 7

ExercAise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8--7 HoDwYidoDuo? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8--8 Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8--10 ExercA ise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 -- 10

Entering Ladder Logic Components in an RSLogix 5000 Routine

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

WhaYtoW u Lillearn ......... ........ ......... ......... ......... ......... ..... WhyTheseSkillsAreImportant ......... ......... ......... ......... ........ .... BeforYeoBuegin ......... ......... ......... ......... ......... ......... ...... EnW terinindgoawnsd-EBdaitsinegdM LaedthdoedrLs(oDgriacC ggoim ngp)onen. .ts. . . . . .. .. . .. .. .. .. .. .. . .. .. . .. .. .. .. .. .. . .. .. . .. .. .. .. .. . .. .. . .. .. .. .. .. .. . . InsKeerty ......... ......... ........ ......... ......... ......... ........ Assigning a Tag to an Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VerifyingProjectsandRoutines ......... ......... ......... ......... ........ ....

9-1

9--1 9-- 1 9--1 99---1- 2 9--2 9--3 9-- 5

vi

Table of Contents

Exercise: Entering Ladder Logic Components in an RSLogix 5000 Routine . . . . . .

9- 7

ExercAise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 -- 7 HoDwYidoDuo? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 -- 9 Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9--10 ExercA ise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-- 10

Modifying Timer and Counter Instructions in an RSLogix 5000 Project

. . . . . . . . . 10-1

WhaYtoW u Lillearn ........ ......... ......... ......... ......... ........ ...... WhyTheseSkillsAreImportant ........ ......... ......... ......... ......... ....

10-- 1 10--1

BeforYeoBuegin ......... ........ ......... ......... ......... ......... ....... 10 -- 1 TIMEDRaT taype ........ ......... ......... ......... ......... ........ ...... 10 -- 1 TimerInstructionComponents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10--2 TimeInr structions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10--3 TON(TimerOnDelay)Instruction ......... ......... ......... ........ ......... 10--3 TOF(TimerOffDelay)Instruction ......... ......... ......... ........ ......... 10 -- 4 RTO(RetentiveTimerOnDelay)Instruction ......... ......... ......... ......... . 10 -- 5 COUNTER DatTaype ........ ......... ......... ......... ......... ........ ... 10 -- 6 CounterInstructionComponent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10--7 CounteIrnstructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10--7 CTU(CounU t p)Instruction ........ ......... ......... ......... ........ ...... 10--7 CTD(CountDown)Instruction ......... ......... ......... ......... ........ ... 10--8 RES(ResetI)nstruction ........ ......... ......... ......... ......... ....... 10 -- 8 HerH e’osw ........ ......... ......... ......... ......... ......... ........ ... 10 -- 9 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-- 10

Exercise: Modifying Timer and Counter Instructions inanRSLogix5000Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 - 17 ExerciAse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-- 17 HoDwYidoDuo? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-- 21 Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10--22

Modifying Program Control Instructions in an RSLogix 5000 Project . . . . . . . . . . . 11- 1 WhaYtoW u Lillearn ........ ......... ......... ......... ......... ........ ...... 11-- 1 WhyTheseSkillsAreImportant ........ ......... ......... ......... ......... .... 11--1 BeforYeoBuegin ......... ........ ......... ......... ......... ......... ....... 11 -- 1 SubroutinUesage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 -- 2 JSR(JumptoSubroutine)Instruction ........ ......... ......... ......... ....... 11 -- 2 SBR(Subroutine)Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-- 2 RET(ReturnfromSubroutine)Instruction ........ ......... ......... ......... .... 11--3 JMMCPR((JMuamsptetorCLoabnetrlo)alRnedsLeBt)LIn(Lstarbuectl)ioInnstruct.io. n. s. . . . . .. . .. .. .. .. .. .. . .. .. . .. .. .. .. .. .. . .. .. . .. .. .. .. .. .. . .. .. . .. .. .. .. 1111----45 MCRInstructionUsage ........ ......... ......... ......... ........ ......... 11--5 UID (User Interrupt Disable) and UIE (User Interrupt Enable) Instructions . . . . . . . . . . . . . . . . 11--6 UID anUdIU Esage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-- 7 TND(TemporaryEnd)Instruction ........ ......... ......... ......... ......... . 11 -- 7

vii

Table of Contents

AFI (Always False Instruction) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NOP(NoOperationInstruction) ........ ......... ......... ......... ......... .. HerH e’osw ......... ......... ........ ......... ......... ......... ......... .. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . JSRInstructionGuidelines ........ ......... ......... ......... ......... ..... Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11--7 11-- 8 11--8 11--8 11-- 9 11 -- 10

Exercise: Modifying Program Control Instructions inanRSLogix5000Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 - 15 E ewrYicdoiA HxoD Dsueo? . . . . . . .. .. . .. .. .. .. .. .. . .. .. . .. .. .. .. .. .. . .. .. . .. .. .. .. .. .. . .. .. . .. .. .. .. .. .. . .. .. . .. .. .. .. .. .. . .. .. . .. .. .. .. .. .. . .. .. . .. .. .. 11 --1119-- 15 Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--20 ProjecEtxample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11--21

Monitoring GSV/SSV Instructions in an RSLogix 5000 Project

. . . . . . . . . . . . . . . . 12-1

WhaYtoW u Lillearn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-- 1 WhyTheseSkillsAreImportant ......... ......... ......... ......... ........ .... 12-- 1 BeforYeoBuegin ......... ......... ......... ......... ......... ......... ...... 12--1 MonitoringControllerSystemData . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-- 1 GSV/SSVParameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-- 2 Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--2 Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--3 Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--3 SourceoDr estination ........ ......... ......... ......... ......... ........ . 12-- 3 ExampleG : SVInstruction ........ ......... ......... ......... ........ ....... 12-- 4 StatFuslags ......... ......... ........ ......... ......... ......... ........ 12--5 ControlleSr tatusFlags ........ ......... ......... ......... ......... ........ 12-- 5 Arithmetic Status Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--6

Exercise: Monitoring GSV/SSV Instructions in an RSLogix 5000 Project . . . . . . . . 12- 7 ExercAise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--7 HoDwYidoDuo? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--9 Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12--10 ExerciAse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 -- 10

Forcing I/O and Toggling Bits in RSLogix 5000 Software

. . . . . . . . . . . . . . . . . . . . 13 -1

WhaYtoW u Lillearn ......... ........ ......... ......... ......... ......... ..... WhyTheseSkillsAreImportant ......... ......... ......... ......... ........ .... BeforYeoBuegin ......... ......... ......... ......... ......... ......... ...... ForRcFueulenfsocFrtoiorcnisng . . . .......... .. .. .. ............ .. .. .. ............ .. .. .. ............ .. .. .. ............ .. .. .. ............ .. .. ........ SafetPy recautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . StaFoteforces ........ ......... ......... ......... ......... ......... ...... TogglinBgits ......... ......... ........ ......... ......... ......... ........

13-- 1 13-- 1 13--1 131--32--1 13--2 13--3 13--5

viii

Table of Contents

Exercise: Forcing I/O and Toggling Bits in RSLogix 5000 Software

. . . . . . . . . . . . 13- 7

ExercAise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 -- 7 HoDwYidoDuo? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 -- 9 Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13--10 ExerciAse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-- 10

Troubleshooting Logix5000 Controller Problems . . . . . . . . . . . . . . . . . . . . . . . . . . WhaYtoW u Lillearn ........ ......... ......... ......... ......... ........ ...... WhyTheseSkillsAreImportant ........ ......... ......... ......... ......... ....

14 -1 14-- 1 14--1

BeforYeoBuegin ......... ........ ......... ......... ......... ......... ....... 14 -- 1 ControlleLrEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 -- 1 IdentifyingFaulTt ypes ......... ........ ......... ......... ......... ......... . 14-- 2 Non-RecoverableMajorFault ........ ......... ......... ......... ........ ...... 14 -- 2 RecoverableMajoFr ault ......... ......... ......... ......... ........ ......... 14 -- 3 RecoverableMajorFaultProcessing:Level1 ........ ......... ......... ......... . 14--3 FauRltoutine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 -- 3 ControlleFr aulH t andler ........ ......... ......... ......... ......... ....... 14 -- 3 RecoverableMajorFaultProcessing:Level2 ........ ......... ......... ......... . 14--4 MultipleRecoverableMajorFaults ......... ......... ......... ........ ......... 14 -- 5 CommoM n ajoFraults ........ ......... ......... ......... ......... ........ ... 14 -- 5 MinFoarult ......... ......... ......... ......... ......... ......... ........ 14 -- 5 ResolvingaNon-RecoverableMajorFault ......... ......... ......... ......... .... 14-- 6 Finding and Clearing a Recoverable Major or Minor Fault ........ ......... ......... .... 14-- 7

ExercisEexe: rTcAirsoeub.l.e.s. h. .o. o. .tin. .g. .L. o. .g. i. x.5.0. 0. .0. .C. o. n. t. r. o. .ll.e. r. .P.r.o.b. .le. .m. .s . . .. ..... .. .. .. .. .. . .. ..... .. . ..... . . . 14 --194-9 HoDwYidoDuo? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-- 10 ExerciBse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-- 10 HoDwYidoDuo? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 -- 11 ExerciCse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-- 12 HoDwYidoDuo? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-- 13 Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14--14 ExerciAse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-- 14 ExerciBse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 -- 14 ExerciC se . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 -- 15

Appendix I/OWiringDiagrams

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

Slot0--1756-OB16DDigitalOutputModule ........ ......... ......... ......... .... Slot2--1756-IB16DDigitalInputModule ......... ......... ......... ........ ...... Slot4--1756-OB16DOutputModule ......... ......... ......... ........ ......... Slot7--1756-OF6VIAnalogOutput ........ ......... ......... ......... ......... . Slot8--1756-IF6VIAnalogInput ......... ......... ......... ......... ........ ...

A- 1 A--1 A -- 2 A-- 3 A-- 4 A -- 5

ix

Table of Contents

ControlLogix Workstation I/O Device Assignments LocIT/aOal gs

NodA e ssignments

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

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

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

B -1 B --2

C- 1

x

Table of Contents

Lesson

1

Identifying Logix5000 System Components What You Will Learn

After completing this lesson, you should be able to identify Logix5000 system components by performing the following tasks: • Identify the Logix5000 platforms • Identify the hard ware components of each Logix5000 platf orm

Why These Skills Are Important These skills are important for the following reasons: • Understanding control sys tem products will help you identify those that most efficiently meet your application needs. • The ability to identify Logix5000 sys tem components pr ovides a solid base for learning programm ing or maintenance tasks.

Before You Begin Clarify that the control engine is an operating system for Logix5000 platforms. Compare this to Microsoft Windows which is an operating system for most personal computers.

Logix5000 System Logix Control Engine: The operating system common to all Logix5000 controller s. It is avaialable in several platforms or physical formats:

r: High-performance, multi-controller system in a • ControlLogix modular chassis format. Note that the GuardLogix safety controller is an optional feature of the ControlLogix system. The GuardLogix controller door is red.

• FlexLogixt: System for distributed control (i.e., control platform is located at or close to the process/machine).

Explain the SoftLogix platform as a system in which all the hardware modules and their tasks are in software form.

• DriveLogixt: System for distributed drive control.

• CompactLogixt: Small modular system for small stand-alone to medium-sized connected systems. • SoftLogixt: System that combines control , information, and visualization on an open-control system (e.g., the control engine is housed in a computer or other terminal). SoftLogix System

ControlLogix System DriveLogix System

Rev. February 2007

FlexLogix System

CompactLogix System

E 2007 Rockwell Automation, Inc. All rights reserved. CM3sb56r

1--2

Identifying Logix5000 System Components

Tip "

Because all Logix5000 platforms have the same control engine, they are all programmed in a similar manner using the same software. Logix5000 Control Disciplines

Note that Logix5000 controllers can communicate with PLC, SLC, and other traditional controllers.

The Logix5000 family of controller is capable of supporting the following control disciplines:

Explain that motion and process control are handled by modules developed specifically for Logix5000 systems. Drive control is managed by integrating existing drive devices (i.e., devices not developed specifically for Logix5000 systems) into Logix5000 systems.

• Motion Control: To direct movement by controlling current,

• Sequential Control: To sequence process units through a series of discrete states (e.g., conveyor systems).

acceleration, position, and speed (e.g., labeling, packaging, picking and placing). • Drive Control: To manage the speed, torque, horsepower, and direction of a motor (e.g., mixing, winding). • Process Control: To operate a machine or manufacturing environment using regulated parameters (e.g., batching, filling).

Note that safety is addressed through GuardLogix controllers in the ControlLogix platform.

• Safety Control: To monitor safety circuitry and safety devices, like light curtains, to minimize risks .

Example: Bottling Line Point out that the different parts of the system communicate to act as one system, rather than separate systems.

The various tasks in a bottling line can all be controlled using Logix5000 platforms: • Sequential control - high speed counting • Motion control - capping and labeling • Process control - batch ing and filling • Drive control - conveyor motor • Safety -- operator safety

High Speed Bottling Line

E 2007 Rockwell Automation, Inc. All rights reserved.

Rev. February 2007 CM3sb56r


1 -- 3

ControlLogix Platform and Components Note that the ControlLogix platform is similar to the modular format of PLC systems.

The ControlLogix platform is a high-performance, multi-controller system in a modular chassis format. ControlLogix systems have the following capabilities:

If you are teaching the standard course, point out to students that their workstation utilizes the ControlLogix platform and that they will be working with this platform throughout the rest of the course.

• Enable easy integration with any exis ting systems (i.e., PLC-5 r, SLCt) • Are capable of high-sp eed communications and data transfer s • Allow multiple cont rollers, I/O module s, and communicatio ns modules in any order and location within the chassis

The main components of a ControlLogix system are shown in the following graphic:

? Are you familiar with the terms called

Chassis

out in the graphic from your own experience? Several of these components will be described in the following sections. Power Supply

Point out that communications modules all have purple labels.

I/O and Communication Modules

Controllers

ControlLogix Chassis Inform students that not all Logix5000 platforms have a chassis. SoftLogix platform has a “virtual chassis” rather than a hardware chassis and the FlexLogix platform sits on a DIN rail.

Tip " Rev. February 2007

Chassis: A hardware assembly that houses devices such as controllers, I/O, and communications modules: Chassis

Slots are the openings in a chassis that hold individual modules.


1--4


The following ControlLogix chassis sizes are available:

? How many slots does the

• 4-slot

ControlLogix chassis in the classroom have?

• 7-slot • 10-slot • 13-slot • 17-slot

Slots are numbered from left to right starting with 0: Note that the last slot number is always one less than the total number of slots in the chassis (e.g., a 4-slot chassis is numbered 0--3, a 7-slot chassis is numbered 0--6).

01

32

5 64

7

8

9

Slots

1756 (ControlLogix) modules are not slot-dependent (i.e., any 1756 module can be placed in any slot in the chassis).

ControlLogix Backplane

The ControlLogix backplane, or ControlBus t backplane, is a printed circuit board at the back of the chassis that provides electrical interconnection between modules: Point out that this backplane has seven module connectors.

Module Connectors Backplane

Note that the multicast capability is the key to communications between modules and between the chassis and other devices. E 2007 Rockwell Automation, Inc. All rights reserved.

The backplane allows data to be multicast (i.e., an input module sends data once that is received by multiple controllers simultaneously). Rev. February 2007 CM3sb56r


1 -- 5

ControlLogix Controller

The ControlLogix controller is a 32-bit controller that combines logic and data in modular memory:

Review the flow of information in a controller: 1. Measures and receives data from input devices via input modules

Locking Tab

2. Executes user programs and makes decisions based on input data 3. Send information based on its decisions to output modules to control output devices

Backplane Connecter

LEDs

Remove controller a chassis and allow the astudents to from examine it as you point out the components.

Keyswitch Battery

Note that on the door there is space to write the date when the battery was last changed. This graphic shows a Series A controller. Students with new ControlLogix applications may use L63 Series B (or newer) controllers. If asked, point out the physical differences in Series B controllers:

S The door swings open in the opposite direction.

S A CompactFlash memory Tip card is available for storing backup programs.

Labels RS-232 Serial Port Locking Tab

All controllers have two main internal components: • Central Processing Unit (CPU): The decision-making component that executes the program stored in memory.

S. The redesigned battery is in a different location. S The serial port is in a different location.

Door Battery Label

• Memory: A group of circuit elements where programs and data

"

are stored. A battery will maintain controller memory when power is turned off. There are also controllers that support nonvolatile memory. Safety Controllers

A GuardLogix safety controller is a ControlLogix controller capable of SIL 3, CAT 4 safety control: Mention that safety controllers are not used in the exercise for this lesson.

• Primary controller:

-- 1756-L61S (2 MB s tandard memory and 1 MB safe ty memory)

-- 1756-L62S (4 MB s tandard memory and 1 MB safe ty memory) • Safety partner (1756-LSP -- safety memory only) The primary controller and safety partner are located side-by-s ide in a ControLogix chassis:

Rev. February 2007


1--6


ControlLogix I/O Modules Clarify that digital modules are often also called “discrete” modules, however, the

ControlLogix I/O modules (1756-I/O ) provide input and output capability to span many applications, from high-speed sequentia l to

term digital is correct.

process control.

Define electronic keying as a software safety feature that compares software descriptions of the modules to the actual inserted modules.

These I/O modules offer the following capabilities: • Easy configuration using a wizard • Electronic keying (module ide ntification) • Scaling of analog values • Diagnostics (depending on the module)

The wiring from the process/machine is connected to I/O modules through one of the following special devices: Emphasize that the module must be unlocked. Show the locking tab to the students. Remove a digital I/O module from a chassis, detach the RTB, and show the students the device.

Tip "

• RTB (Removable Terminal Block): A field wiring connector for I/O modules. Field wiring is connected to an RTB rather than directly to a module terminal block. • IFM (Prewired Interface Module): A field wiring arm that uses prewired/factory-wired cable to connect to an I/O module.

RTBs and IFMs allow for easy replacement or interchanging of I/O modules without rewiring them. RTBs and IFMs are not included with I/O modules. They must be purchased separately.

Identify each module in the workstation as you review them in the table. If you are teaching the standard course, mention that these networks will be discussed in later lessons. If students ask, mention that the 1756-CN2 and 1756-CN2R are enhanced versions of the CNB.

ControlLogix Communications Modules Communications Modules: Modules used for creating communications between a controller and a network: Network

EtherNet/IPt ControlNett

Mention that modem combinations, for those migrating from SLC systems, is also possible.

Tip "

Remind students that the RS-232 serial port is on the Logix55xx controller module.


Required Communications Module

1756-ENBT 1756-CNB, 1756-CNBR, 1756-CN2, 1756-CN2R

DeviceNett

1756-DNB

Data Highway Plust (DH+t) or Universal Remote I/O

1756-DHRIO

For serial communicatio ns, the computer connects direct ly to the controller. Rev. February 2007 CM3sb56r


1 -- 7

ControlLogix Platform Modularity Clarify that modularity refers to the modules within a chassis and the different devices throughout a system.

The modular format of the ControlLogix platform allows users to design, build, and modify flexible systems by performing the following tasks: • Select the numbe r of controllers an d appropriate me mory size • Select the number and type of I/O m odules • Select the number and type of com munications modules

Tip " Note that a remote chassis may contain a controller, but it does not require one. It requires a communications module to connect to the network. In the example graphic, one chassis (top) contains controllers, while the other chassis does not.

Modularity allows for easy reconfigura tion and repair by replacing individual units. A ControlLogix system can range in complexity: • A simple stand-alone controller and I/O modules in a single chassis • A complex system wit h multiple controller s, chassis, and networks in different locations

Example: Platform Modularity

The following system uses three different networks to communicate with various devices, including another chassis: ControlLogix Chassis

ControlLogix Chassis DeviceNet Network

EtherNet/IP Network ControlNet Network

CompactBlock I/O

PLC-5 System

1336 FORCE

Drive

System

PanelView Plus Terminal

RediSTATION

Tip "

Rev. February 2007

Flex I/O

The ControlLogix system is ideal for network bridging, or sharing information between different networks.


1--8


FlexLogix Platform and Components The FlexLogix platform is a system for distributed control (i.e., control platform is located at or close to the process/machine). This allows the application to be simplified by dividing it.

Tip "

Distributed control application examples include machine control, small processes, SCADA (Supervisory Control and Data Acquisition), assembly line, oven control, and filling stations.

Clarify that although the FlexLogix controller is in a different format, it holds the same high-performance control engine as the other platforms.

This system has the following characteristics:

Note that the term “card” is sometimes used for “modules” in FlexLogix, SoftLogix, and CompactLogix platforms.

• Can be mounted ve rtically or horizontally

• Is reduced size for smaller spaces • Can be mounted on a DIN rail or in panels • Is modular

The size and number of modules varies according to the application: Communications Card

Controller

I/O System

DIN Rail

DIN Rail If available, show a DIN rail and how components slide on and off.

Tip "

DIN rails are devices that provide convenient and simple mounting of components for easy access. A DIN rail allows a FlexLogix controller and I/O to be placed in a close proximity to the process or machine. FlexLogix Controller

The main components of a FlexLogix controller are shown in the following graphic: FlexBus Local 2 Connector (For up to 8 FLEX I/O Modules via an Adapter)

Two Optional Communications Daughtercard Slots

24 V Power

8 Status and Diagnostic

RS-232 Port

DIN Rail or Panel Mount


LEDs

Battery Backup

Three-Position Keyswitch

FlexBus Local 1 Connector (For Up to 8 Local FLEX I/O Modules)



1 -- 9

The FlexLogix controller has the following feature s: • Up to 512 Kbyte fixed memory:

-- Selected controllers s upport non-volat ile memory to retain a project without a battery • Two communications slots installed in the controller

Note that the EtherNet/IP network became available this year.

• Support for these NetLinx networks:

Mention that networks will be discussed later in the course.

-- EtherNet/IP -- ControlNet -- DeviceNet FlexLogix I/O Modules

Note that the FlexLogix system achieves distributed control without the reduced processing power and programming capability common to other distributed control solutions.

FlexLogix I/O modules (1794-IO) are placed on a DIN rail: • Supports one or two banks (up to 8 local I/O m odules and 8 extended local I/O modules) • Extended local I/O modules can be located 1m to 3m fr om the local I/O modules • FlexLogix systems support up to 512 I/O points

Bank 1

Local I/O Modules Extended Local I/O Modules

Bank 2

Tip "

With an extender cable, FlexLogix banks can extend up to 10ft (3m) in horizontal and vertical directions. FlexLogix Communications Cards

Mention that communications cards plug into one of the two communications daughtercard slots in the side of a FlexLogix controller.

FlexLogix communic ations cards are connected directly to the controller in the daughtercard slots:

RS-232 Port Two Communications Daughtercard Slots Rev. February 2007


1--10


CompactLogix Platform and Components The CompactLogix platform is a small modular system for small stand-alone to medium-sized connected systems.

If students are familiar with PLC/SLC systems, explain that CompactLogix systems are to ControlLogix systems what SLC systems are to PLC systems (i.e., a simpler, smaller system).

The fixed I/O count of the CompactLogix platform is geared toward stand-alone control applications where panel space is limited: I/O System

Communications Module

Power Supply

Controller

Tip "

CompactLogix systems can be mounted on DIN rails or in panels.

Tip "

Application examples include machine-level control, material handling, data acquisition, machine control, food, beverage, packaging, and other applications requiring limited I/O count.

Note that CompactLogix is also ideal for machine builders.

CompactLogix Controller Point out that the CompactLogix controller is approximately 60% of the size of a ControlLogix controller or an SLC 500 processor.

The main components of a CompactLogix controller are shown in the following graphic:

If available, compare the size of the CompactLogix system to a ControlLogix system and/or a PLC-5 system.

Diagnostic LEDs

Point out that the system is rackless. Three-Position Keyswitch CompactFlash Card (Behind Cover)


RS-232 Port



Note that the CompactLogix system can be mounted horizontally or vertically.

1--11

CompactLogix controllers offer the following benefits: • Has memory sizes from 512 Kbytes to 2 MBytes • Supports these NetLinx networks:

-- EtherNet/IP -- ControlNet -- DeviceNet • L4x controllers support integra ted motion control (SER COS)

CompactLogix I/O Modules

CompactLogix I/O modules contain a set I/O count for simple, stand-alone processes: • Supports up to 3 banks of lo cal I/O (up to 30 Compac tLogix I/O modules) • Supports up to 1024 I/O points

Status Indicators

Module Door

CompactLogix I/O modules have the following features : • Removeable terminal bloc ks and module-ready cables • Status indicators

CompactLogix Communications Modules/Converters If available, show a CompactLogix communications module. If students ask, explain that for L32x and L35x controllers, Ethernet/IP and ControlNet networks are connected through onboard connectors. DH485 networks require a converter for connection to a CompactLogix system.

Rev. February 2007

CompactLogix communications modules let users configure a system for information exchange betwe en a range of devices and platforms: Network

EtherNet/IP

Communications Module/Card

1768-ENBT (L4x controllers only)

DeviceNet

1769-SDN or1769-ADNModules

DH-485

1761-NET-AICConverter


1--12


DriveLogix Platform and Components The DriveLogix platform is a system for distributed drive control that provides the following benefits : • Embedded Logix50 00 controller in a high-perf ormance PowerFlext 700S drive

Note that RSLogix 5000 software contains many function block instructions specific to drives.

• Local Flex I/O t modules • NetLinx cards for high-speed communications capabilities

Tip "

Application examples include coordinated sectional drive systems, high-speed, inter-drive communications, and sophisticated drive control.

Note that the PowerFlex 700S drive is the drive used in a DriveLogix system.

A PowerFlex 700S Phase I drive with DriveLogix is shown in the following graphic: Drive Status Indicators LCD HIM Communications LEDs

DriveLogix Controller

Explain the SoftLogix platform as a system in which all the hardware modules and their tasks are in software form.

SoftLogix Platform and Components

If necessary, briefly review what is meant by HMI. Give examples, such as the PanelView terminal.

It provides a software interface where modules can be created, configured, and controlled through images in a “virtual chassis”:

The SoftLogix platform combines control, information, and visualization on an open-control system (e.g., the control engine is housed in a computer or HMI (Human Machine Interface ) terminal.

SoftLogix Platform Virtual Chassis

Module

VersaView Industrial Computer

Slot Number




Note that SoftLogix platform is often referred to as the SoftLogix5800 platform. Explain the SoftLogix platform as a system in which all the hardware modules and their tasks are in software form.

Tip "

Rev. February 2007

1--13

The SoftLogix platform provides the following benefits : • Is compatible with a range of Rockwell Aut omation and Microsoftr products • Communicates with existing I/O • Supports the NetLinx networks:

-- DeviceNet -- ControlNet -- EtherNet/IP Application examples include tightly integrated HMI and data-intensive applications.


1--14




Exercise: Identifying Logix5000 System Components

1--15

Exercise: Identifying Logix5000 System Components Exercise A

In this exercise, you will practice identifying Logix5000 system components:

Directions: 1. Which platform consists of a multi-controller, high-performance system installe d in a modular chassis format?

2. Which platform uses a “virtual chassis?”

3. Why does the CompactL ogix platform have a set I/O cou nt?

4. What is one benefit of the FlexLogi x platform?

5. Which platform is a sys tem for distribu ted drive control?

6. Name one trait that all Logix5 000 controllers s hare:

Rev. February 2007

E 2007 Rockwell Automation, Inc. All rights reserved. CM3e56r

1--16


7. Name two benefits of system mod ularity:

8. Label the componen ts in the ControlLogix controll er:

9. Which component of a Logix5000 system allows one me ssage to be received by multiple modules and devices?

10. What are the openings in a chass is or on a DIN rail that hold individual modules?

11. Detach the RTB and remove a digital I/O module fr om the chassis. 12. Name the devices that provide inte rconnection between I/O modules and processes/machines.


Rev. February 2007 CM3e56r


1--17

13. How does a contro ller retain its memo ry when the power supply is turned off?

14. What component of a controller gives status inf ormation for the module?

15. What software application is used to create a connection betwe en RSLogix 5000 software and the controller?

How Did You Do?

Turn to the Answers section.

Exercise B

In this exercise, you will practice identifying the main components of a Logix5000 platform and a Logix5000 controller.

Context: Because your plant’s compressor assembly application is complex, a ControlLogix system has been selected for your plant. You must identify and become familiar with your system’s hardware before you can begin working with it.

Directions: Use the following list to examine your ControlLogix system: 1. Check the workstation chassis size:

- Four slot - Seven slot - Ten slot - Thirteen slot - Seventeen slot 2. Place a check in the box after you locate eac h of the following components:

Rev. February 2007

Power supply Power On/Off switch Power LED Module LEDs I/O module locking tabs E 2007 Rockwell Automation, Inc. All rights reserved. CM3e56r

1--18


3. Place a check in the box after you locate eac h of the following controller components:

- Keyswitch - Keyswitch positions - Controller LEDs - Battery (or battery port, if empty) - Battery date label - Serial cable and serial port - Top and bottom locking clips 4. Using the module fac eplates and the labe ls inside the module doors, identify the name and the part number of each workstation module in the provided spaces: 0

1

2

3

4

5

6

7

8

9

A. Slot 0:

B. Slot 1:

C. Slot 2:

D. Slot 3:

E. Slot 4:

F. Slot 5 (the door will not open):


-

Remove the module in slot 5

-

View the backplane Find the node address dials Replace the module



1--19

G. Slot 6:

-

Remove the module in slot 6 Find the network type dials Find the node address dials Replace the module

H. Slot 7:

I. Slot 8:

J. Slot 9:

How Did You Do?

Rev. February 2007



1--20


Answers

Exercise A 1. The ControlLogix platfor m is a high-performanc e, multi-controller system in a modular chassis format. 2. The SoftLogix platform use s a “virtual chassis .” 3. The CompactLogix platform has a set I/O cou nt because it is geared toward stand-alone control applications where panel space is limited. Additional I/O is not necessary unless the application is significantly changed. 4. The FlexLogix platfor m has a reduced size for smaller space s. This makes it possible to place the platform within a close proximity to the machine or process. 5. The DriveLogix platfo rm is a system for distributed drive control. 6. All Logix5000 controll ers share the Logix50 00 control engine. 7. Answers may vary. The following responses are possible correct answers: • Modularity allo ws for reconfiguration and repai r by replacing individual units. • The modular form at of Logix5000 systems a llow users to design, build, and modify systems according to the needs of their application.

8. Locking Tab

Backplane Connecter

LEDs Keyswitch

Battery Door Battery Label Labels Serial Port Locking Tab

9. The backplane all ows data to be multicas t to multiple destinations.




1--21

10. Slots are the openin gs in a chassis or on a DIN rail that hold individual modules. 12. RTBs and IFMs are devices that provide inter connection between I/O modules and processes/machines. None of these components are included with the I/O modules. 13. The battery in the controlle r maintains memory if the main power source is lost. 14. The status indic ators on the front of a controller can be chec ked for module status informatio n. 15. RSLinx Classic software provides an interface between RSLogix 5000 software and the system hardware, including the controller. RSLinx Classic software provides download and upload, online editing, and data monitoring functionality for Logix5000 systems.

Exercise B 1. The chassis size is ten slot. 4. The workstation contains the following hardwa re: A. 1756-OB16D digital output module B. 1756-L63 (Logix5 563) controller C. 1756-IB16D digital input module D. 1756-L63 (Logix5563) controller E. 1756-OB16D digital output module F. 1756-CNB ControlNet bridge module G. 1756-DHRIO DH+/RIO communications bridge module H. 1756-OF6VI analog output module I. 1756-IF6I analog input module J. 1756-ENBT Ethernet/IP comm unications bridge module

If you are not using a standard ControlLogix training workstation (Part No. ABT-TDCLX1), your answers may vary.

Rev. February 2007


1--22




Lesson

2

Identifying RSLogix 5000 Software Components What You Will Learn

After completing this lesson, you should be able to perform the following tasks: • Identify RSLogix 5000 softw are components • Configure the RSLogix 5000 soft ware display

Why These Skills Are Important Being introduced to the main Logix5000 t programming software is important for the following reasons: • Being able to quickly identif y and locate softwar e options and software components will reduce programming and maintenance time. • Being able to customi ze the software to fit your working style will improve your programing speed and ease.

Before You Begin

? Is anyone familiar with RSLogix 5000

RSLogix 5000 Programming Software Because of the common control engine, RSLogix 5000 software is

software? Mention that RSLogix 5000 software is similar in use to RSLogix 5 software for PLC systems and RSLogix 500 software for SLC systems. If you are teaching the standard course, mention that ladder logic will be discussed later in the course.

used to program and configure perform the following tasks: all Logix5000 systems. It is used to • Develop and modify code (e.g ., ladder logic, function block diagrams, etc.) • Monitor project and system compon ents during operat ion • Configure hardware modules

Software Benefits

RSLogix 5000 software offers the following benefits: • Flexible, easy-to-use, Windows r-based editors and components • I/O configuration wizards • Ability to copy and paste compo nents between projects • Same look and feel as RSLogix 5 and RS Logix 500 softwa re:

-- Ladder logic instruction set built on PLC-5 r instruction set • Multiple programming language options (ladder logic , function block diagram, sequential function chart, and structured text): -- Your configuration will depend on the language options selected and installed.

Rev. February 2007

E 2007 Rockwell Automation, Inc. All rights reserved. PR3sb56r

2--2


Tip "

For information on software package options, system requirements, or installation, refer to the Release Notes in RSLogix 5000 software.

Identifying RSLogix 5000 Software Components Mention that users can configure the main window layout to match individual preferences.

The following are the main sections in the default configuration of the RSLogix 5000 main window:

Toolbars Routine Editor/ Tags Window

Controller Organizer Results Window

Mention that there are more toolbars available within the software but the Online and Language Element toolbars are the most useful.

Toolbars

The following toolbars are available: • Standard toolbar • Online toolbar • Path toolbar • Language Element toolbar

Standard Toolbar:An optional toolbar with standard Microsoft options such as new, save, cut, copy, paste, and more. Standard Toolbar


Rev. February 2007 PR3sb56r


If you are teaching the standard course indicate that the course will not cover forcing.

2 -- 3

Online Toolbar:A toolbar that provides controller status. Tab/drop-down lists are available for viewing related information: LEDs

Tabs

Keyswitch Controller Properties

Path Toolbar: A toolbar specific ally used for communicating with the controller and viewing communica tion status:

Online Graphic Current Communications Path

Note that the Language Element toolbar is also referred to as the Instruction toolbar. Add that the programming language’s toolbar is shown when that language is being programmed in an active Routine window.

Language Element Toolbar: A toolbar containing programmin g elements, grouped by tabs, for entry into an active routine. Each language has its own element toolbar: Example: Ladder Logic Language Element Toolbar

Element Tabs

Element Buttons

Example: Function Block Diagram Language Element Toolbar

Element Tabs

Mention that tooltips can give you information on the name, data type, scope, etc. for a tag. These parameters will be detailed in another lesson.

Element Buttons

Tooltips and Status bar messages are easy ways of identifying components, such as buttons in the New Components toolbar :

Add that this information is often also available in the Status bar.

New Program

Status Bar Rev. February 2007


2--4


Controller Organizer Point out that the Controller Organizer represents the entire project, including the tasks, data, and I/O configuration.

Tip "

The Controller Organizer is a tree structure that is used to organize an entire project. The tree structure shows all major areas of a project and the hierarchy of components. The Controller Organiz er is used in the same manner as Windows Explorer:

Expanded Branch

Contents (Sub Folders) of Expanded Branch

Collapsed Branch

Quick Pane

Tip "

The Controller Organize r can be closed or opened using the Toggle Controller Organizer Window button:




2 -- 5

Routine Editor/Tags Window: A window that displays the open routine or tags collection opened through the Controller Organizer:

Indicate that this graphic shows a Routine window and that, if this is a standard course, the Tags windows will be covered to a greater extent in later lessons.

Routine Window Tabs

There is a routine editor to view or edit each type of routine: • Ladder Diagram (LD) • Function Block Diagram (FBD) • Structured Text (ST) • Sequential Function Chart (SFC)

Note that windows can be moved, minimized, maximized, to suit your working style. closed, etc. Tip

"

Explain the components found in the Results window.

When more than one Routine Editor or Tags window is opened, tabs across the bottom of the window are used to separate the editors or windows. Results Window: A window at the bottom of the main window that contains the following tabs: • Errors Tab : Results of a verification for errors in the project. • Search Results Tab : Results of a search for a project component. • Watch Tab : Window for viewing data in an open routine.

Tabs

Mention to students that the Tip " Results window can be opened by selecting View from the main menu. Rev. February 2007

The Results window is not always present and only opens when there is a specific command, or when initiated by the user. E 2007 Rockwell Automation, Inc. All rights reserved. PR3sb56r

2--6


Help System The Help menu contains the following options: • Contents, with the following tabs: Point out that the instruction help section is an excellent resource for ladder logic or function block instruction information. Clarify that the online books are available in RSLogix 5000 software versions 2.25 and greater.

-- Contents (to browse by category) -- Index -- Find (to search for phrases or words) • Instruction help grouped by instruction type s or alphabetica lly • Release notes • Online books in Adobe t Acrobatt format • Sample RSLogix 5000 projects from Rock well Automation and other vendors • Quick Start inter active tutorial for new RSLogix 5000 users :




2 -- 7

• Learning Center that provides interact ive access to the following topics:

-- Information about new Logix5000 hardw are, software, and features

-- Animated tutorials on perfor ming common tasks -- A listing of “Did You Know?” hints , tips, and tricks:

Mention that students will need Internet access when using the Resource Center

Rev. February 2007

• Resource Center, which provides links to online books, available downloads, and helpful web sites:


2--8


• About RSLogix 5000 softw are, which lists the fo llowing details :

-- Current software version -- Rockwell Software technical support contact information The following is an Index search screen in the online Help system:

Search Word

Resulting Topics

Configuring the RSLogix 5000 Software Display State that setting a default data type is useful if you plan to create multiple tags of the same type.

The RSLogix 5000 software display can be configured to suit a user’s work preference, improving performance and efficiency:

Default Project Directory, Etc.

Display Options (Colors, Fonts, and Documentation)

Reset to Default




2 -- 9

Display and toolbar configurations apply to the computer and not to particular projects. Changes will affect all projects that are opened on the same computer.

To make the best use of screen space and functionality, the following actions can be performed with toolbars: • Display/hide toolbars Point out that only certain toolbars can be customized. This will be discussed in the Here’s How demonstration.

• Move toolbars on the screen • Customize buttons

Add, Remove, or Rearrange Buttons View User-Created Toolbar

Reset to Default

Here’s How Open the CCP146_1756r_DEM1.acd file. Give the students an overview of the Workstation Options dialog box. Do not dwell on the terms or concepts that they do not yet know. While demonstrating this procedure, point out the following elements:

To configure the RSLogix 5000 software display. As your instructor demonstrates this procedure, follow along in the associated job aid(s).

S The tree structure and all categories S The Reset Category option S The Apply vs. OK buttons

Rev. February 2007


2--10




Exercise: Identifying RSLogix 5000 Software Components

2--11

Exercise: Identifying RSLogix 5000 Software Components Exercise A

In this exercise, you will practice identifying RSLogix 5000 software components.

Directions: For help performing steps in this exercise, see the associated job aid(s). 1. Start RSLogix 5000 software. 2. Open the PR3_1756r_A1.acd project file. 3. In the Controller Orga nizer, expand the MainProgram folder and then double-click the Lights routine. 4. Place a check in the box after you locate eac h of the following software components: - Standard toolbar

-

Tip "

Online toolbar Path toolbar Language Element toolbar Routine Editor/Tags window

If you do not see all of the toolbars, from the View menu, select Toolbars . . . then click Restore Factory Toolbar Layout. 5. In the Language Eleme nt toolbar, find and click the Move/Logical tab. 6. On the Move/Logic al tab, scroll to the last instruc tion button on the right. 7. Use ToolTips to identify the button. 8. What is the instruction?

9. In the Language Eleme nt toolbar, find and click the Favorites tab.

Rev. February 2007

E 2007 Rockwell Automation, Inc. All rights reserved. PR3e56r

2--12


10. Customize the Favorites tab of the Langua ge Element toolbar by performing the following actions: A. Add one new instruction button. B. Move one button to a diff erent position. 11. In the main screen, in the Language Element toolbar , review the resulting changes to the Favorites tab. 12. In the Controller Organizer, double-click the Controller Tags icon. 13. Switch between the Monitor Tags and Edit Tags windows. 14. Hide the Controller Organizer. 15. Close the Tags window. 16. Configure the RSL ogix 5000 software dis play by performing the following actions: Category

Tip "

Option

Application

Set the number of project backups to 1

Tag Editor Display

Set the Default Data Type to DINT

Ladder Editor Display

Show Routine Descriptions

Ladder Editor Font/Color

Change the end rung color to a color other than black

FBD Editor Font/Color

Change the FBD wire color

Be sure to apply these changes. 17. Re-open the Controller Organizer. 18. In the Help system , locate informa tion about the Online bar (toolbar) in the Index. 19. In the Instruction Help section of the Help sys tem, locate information on the XIC bit instruction.

Tip "

Click the link to the Alphabetical Listing and then click X . 20. Access the Quick Start page . 21. View the tutorial on crea ting a new project. 22. Access the Learning Center and explore some of the available topics. 23. Close the Help system. 24. Close the file without saving it. 25. Open the PR3_1756r_A2.acd project file. 26. In the Controller Organizer, in the MainProgram folder, double-click the Ladder routine.


Rev. February 2007 PR3e56r


2--13

27. Scroll to the end rung. 28. Are your changes to the softwar e display still maintained ?

29. To create data for the Results window, from the Logic menu, select Verify Routine. 30. Scroll through the errors in the Results window . 31. Close the Results window. 32. Return to the Workstation Options dialog box and click Reset Category for all applicable Editor categories.

Tip "

Some Editor categories cannot be reset automatica lly. If changes are needed to the options in these categories, they must be made manually. 33. Close the project file without saving it.

How Did You Do?

Rev. February 2007


E 2007 Rockwell Automation, Inc. All rights reserved. PR3e56r

2--14


Answers

Exercise A 4. The software components ca n be found in the following default locations: Path Toolbar

Language Element Toolbar

Standard Toolbar Online Toolbar Routine Editor/ Tags Window

Controller Organizer

8. The last instruc tion is BTD, or Bit Field Distri bute. 28. Yes. Your configuration will be maintained because display and toolbar configurations apply to the computer and not to particular projects.


Rev. February 2007 PR3e56r

Lesson

3

Creating and Modifying an RSLogix 5000 Project What You Will Learn

After completing this lesson, you should be able to create and modify an RSLogix 5000 project by performing the following tasks: • Identify tasks, programs, and routines • Create a new RSLogix 5000 project file • Modify the default task, progr am, and routine • Create a task, program, and routine

Why These Skills Are Important Outputs are controlled based on the organization and execution of a project. Having the skills to properly organiz e or interpret project structure may reduce errors and future downtime.

Before You Begin

RSLogix 5000 Project Files

Note that by default project files will save back to the directory where they were opened. If this is a disk or CD-ROM, the save will not work.

Tip "

Project/Project File: An RSLogix 5000 software file that stores all programming and configuration information for a Logix5000 t controller.

RSLogix 5000 project files have the extension .acd. Project files should be opened directly from the computer hard drive or network. Files on a disk or CD-ROM should first be copied to the hard drive or network.

Project Components If you are teaching the standard course, note that tags are data storage mechanisms that will be covered later in the course.

The following three components are used to organize a project and direct the execution of code: • Task: A scheduling mechanism for executing programs. • Program: A set of related routines and tags. • Routine: A set or sequence of programming code executed as a

block.

Tip "

Rev. February 2007

Code is executed to completion when a routine runs.

E 2007 Rockwell Automation, Inc. All rights reserved. ORGsb56r

3--2


These three components also serve as containers within the Controller Organizer: Note that this graphic is a portion of the Controller Organizer and represents the organization of the main components of a project.

Tasks Folder Task_A Program_A

When reviewing this graphic, note the following elements:

Program Tags

S The tasks folder holds the three main components.

Routine_A Routine_B

S A project can have several tasks.

Routine_C Program_B

S Each task can be divided into programs based on function, area, or some other attribute. S Each program can have several ladder logic and function block routines.

Task_B

Tasks

A task triggers the execution of its scheduled programs. The following types of tasks can be created in a project: TasTkype

Clarify that a project can have either one or no continuous tasks. Describe the continuous task as the “background” task that runs when other operations are not.

Continuous

Periodic

Icon

A task that executes regularly at a user-specified rate. When called, it will interrupt any lower priority tasks. Example: A periodic task can be used to execute a PID loop every 100 ms. A periodic task can also be used to check pressure on a machine at regular intervals.

Clarify that periodic tasks run at time intervals specified by the user.

Event

? If a ControlLogix controller has one

U sage

A task that runs continuously but can be interrupted by periodic or event tasks.

A task that is triggered only when a specific event occurs. When called, it will interrupt any lower priority tasks. Example: An event task can be used to set an alarm only when packing tape is below a certain amount. Events can also be used for high-speed counting applications

For any controller, only one task can be configured as continuous:

continuous task and 4 periodic tasks, how many event tasks could it have? Controller Type

Answer: 27 (27+4+1 = 32)

? If a ControlLogix controller has ZERO continuous tasks and 4 periodic tasks, how many event tasks could it have? Answer: 28 (28+4 = 32)

Tip "

Mention that the CompactLogix L31 supports 4 tasks, the L32x supports 6 tasks, the L35x supports 8 tasks, and the L43 supports 16 tasks.


Total Number of Tasks

Number of Continuous Tasks

ControlLogixr and SoftLogixt

32

1

FlexLogixt and DriveLogixt

8

1

CompactLogixt

4, 6, 8, or 16 (depending on processor model)

1

When a project is created, the continuous task is defined and named MainTask by default.

Rev. February 2007 ORGsb56r


3 -- 3

Programs

A program is the second level of scheduling within a project: • Each ControlLogix or SoftLogix task can contai n (schedule) up to 100 programs. • Each CompactLogix or FlexLogix task can cont ain (schedule) up to 32 programs. Give possible reasons a program would be unscheduled (e.g., a troubleshooting program for testing or a program for a specific type of application that is left unscheduled until needed).

Tip "

• When a task is triggere d, its programs exe cute in sequence fr om the first scheduled to the last scheduled.

Unscheduled Programs: Programs within a project that are not scheduled by any task; they do not execute. Programs may be left unscheduled until needed (to add future functionality or for troubleshooting).

When a project is created, a default program is defined under the MainTask (continuous task) and named MainProgram. Special programs are available to handle various functions: • Controller Fault Handler : A program that executes when a fault occurs. These programs are stored in the Controller Fault Handler folder. • Power Up Handler: A program that executes when a power cycle occurs. These programs are stored in the Power Up Handler folder.

Routines If students are familiar with PLC/SLC systems, note that routines are similar to a program file in PLC/SLC systems

A routine provides the executable code, or decision-making instructions, for a project. Each routine contains a set of elements for a specific programming language:

Note that ladder logic is the most common language used.

• Ladder Logic • Function Block Diagram • Structured Text • Sequential Function Chart

Tip "

Rev. February 2007

The availability of these languages will depend on the options that have been selected an installed.


3--4


A routine can be assigned as one of the following types: • Main Routine: A routine configured to execute first when the program runs. There is always one main routine in each program. Give the example of the bottling line as an application that may require subroutines. One routine can handle the filling, another handle the capping, another handle the labeling, etc.

• Subroutine: A routine that is called by another routine. Subroutines are used for large or complex programs or programs that require more than one programming language.

-- A JSR (Jump to Subrouti ne) instruction must be programme d in the code in another routine to call, or scan, a subroutine.

-- A JSR may be conditioned or uncond itioned (always active). If students ask, mention that add-on instructions became Tip " available in version 16. Also, mention that add-on instructions are covered in more detail as part of the RSLogix 5000 Level 3: Project Development standard course. Reference the glossary for definitions of program fault and fault.

As a possible alternative subroutines, users can create add-on instructions that combineto commonlyused logic into a single, user-defined instruction. Add-on instructions can be reused throughout a project or as part of multiple projects. • Fault Routine: A routine that executes if the controller finds a recoverable major fault within the executing program.

The main and fault routines must be assigned within a program’s properties. If a routine is not assigned as the main or fault routine, it is automatically a subroutine.

Remind students that a subroutine such as B5_Run must be called by a JSR instruction in another routine. This can be the main routine or another subroutine.

The routine types within the Controller Organizer are shown in the following graphic:

Main Routine

Ladder Logic Routine

Fault Routine Subroutines

Structured Text Routine Sequential Function Chart Routine

Function Block Diagram Routine

Note that on thewhat actual number of routines depends is programmed in each routine and how much memory the code requires. Tip "


A program can have as many routines as the memory of the controller allows, up to 65,535.



Here’s How Create a new project in RSLogix5000 software. Assign it to the controller in slot 1.

3 -- 5

To create and modify an RSLogix 5000 project by performing the following tasks: • Create a new RSLogix 5000 project file • Create a task, program, and routine

As your instructor demonstrates these procedures, follow along in the associated job aid(s).

Rev. February 2007


3--6





3 -- 7

Exercise: Creating and Modifying an RSLogix 5000 Project Exercise A

In this exercise, you will practice identifying tasks, programs , and routines.

Directions: For help performing steps in this exercise, see the associated job aid(s). 1. Start RSLogix 5000 software. 2. Open the ORG_1756r_A1.acd project file. 3. What is the name of th e continuous task?

4. What is the name of the unschedu led program?

5. What is the name of the function block routine w ithin the periodic task?

6. What is the name of the fault routine with in the Filling program?

7. What is the name of the subroutine w ithin the Filling program?

8. What is the name of t he event task?

9. Close the project.

How Did You Do?

Rev. February 2007


E 2007 Rockwell Automation, Inc. All rights reserved. ORGe56r

3--8


Exercise B

In this exercise, you will practice the following tasks: • Creating a new RSLogix 5000 project file • Modifying the de fault task, program, and routine • Creating a task, program, and routine

Context: You need to create a new project for a simple assembly line that has two major functions: Press

Tip "

Package

There are many ways to organize a project. This is only one example of how you might do so.

Directions: For help performing steps in this exercise, see the associated job aid(s). 1. Create a new proje ct for the controller in slot 1.

Tip "

Check your workstation for the controller type in slot 1. 2. Modify the default tas k, program, and routine by making the following changes: Renam..e.

MainTask

Tip "

T..o.

Assembly

MainProgram

Station_One

MainRoutine

Press

Examine each tab of the the properties dialog box as you modify these components. 3. Create a new program in the Assemb ly task named Station_T wo. 4. Create a main routi ne in this program named Pac kage.

Tip "

You now have two programs for the two stations on the conveyor: Station One (Press) and Station Two (Package). 5. The pressure at the press machine must be monitored at regular

intervals. To do so, create a periodic task called Pressure. Set the period for the task to 100 ms.

6. In the Pressure task , create a program called Level. E 2007 Rockwell Automation, Inc. All rights reserved.

Rev. February 2007 ORGe56r


3 -- 9

7. In the Level program , create a function block diagr am routine called Measure. 8. In the Level program , create a ladder logic rout ine called High_Level_Alarm. 9. Assign the routines: • Assign the Measure routine as the main routine. • Assign the High_Level_Alarm routine as the fau lt routine.

10. Examine the icons for the new routines. 11. If you added a third rou tine, what type of ro utine would it be?

12. How would this rout ine be accessed or scanned?

Tip "

You now have a task that is activated every 100 ms. Once code has been entered to evaluate inputs and set outputs, this task will be able to measure and monitor machine pressure . 13. Save all changes to the project and close the softw are.

How Did You Do?

Rev. February 2007


E 2007 Rockwell Automation, Inc. All rights reserved. ORGe56r

3--10


Answers

Exercise A 3. The name of the cont inuous task is Bottling. 4. The name of the unschedul ed program is Capping . 5. The name of the function block routine w ithin the periodic task is MainFBD. 6. AlarmLight is the fault routine within progr am Filling. It is assigned as the fault routine within the Filling program properties. 7. Conveyor is the subro utine within program Fi lling. It is not assigned as the main or fault routine; therefore, it is a subroutine. 8. Label_Glue_Low is the event task .

Exercise B 9. Your project should look similar to the following example:

Press

Package

Machine Pressure

11. All other routines w ould be subroutines . 12. A JSR (Jump to Subroutine) instruc tion must be programmed in the code of another routine to call, or scan, a subroutine. E 2007 Rockwell Automation, Inc. All rights reserved.

Rev. February 2007 ORGe56r

Lesson

4

Transferring a Project File to a Logix5000 Controller What You Will Learn

After completing this lesson, you should be able to transfer a project file to a Logix5000 controller by performing the following tasks: • 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 These skills are important for the following reasons: • Establishing communications with the correct controlle r 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 establis hed with the incorrect controlle r, or if the controller is in the wrong operating mode, problems with efficiency or late delivery of data can occur. This can cause damage to equipment or harm to personnel.

Before You Begin

In the next several graphics, point out that the arrows(s) show the direction that data flows. Note that uploading is commonly used when a maintenance person needs to monitor and troubleshoot a project.

Uploading, Downloading, and Going Online to a Logix5000 Controller Upload: Transfer a copy of a project file from a controller to a computer over a network:

Data

? Define the term “Save.” Answer: To write a copy of a project file to the computer hard drive, which will retain project files even when power is removed from the computer.

Uploading transfers the file in the controller into the temporary memory (RAM) of the computer. To create a permanent copy, the file must be saved to the hard drive of the computer.

Note that by default project files will save back to the directory where they were opened. If this is a disk or CD-ROM, the save will not work.

Rev. February 2007

E 2007 Rockwell Automation, Inc. All rights reserved. COMsb56r

4--2


Add that downloading is typically a one-time event. Students will practice downloading several files in this class. This is for learning purposes and is not typical.

Download: Transfer a copy of a project file from a computer to a controller over a network:

Data Note that you can download in the Remote Program and Program modes only.

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

State that when you attempt to go online with the controller, the computer must have a matching offline file. The software looks for this file in the default directory only.

Online: Viewing or editing a project file that is active in the controller:

Data Stress that while online, the computer remains in continuous communications with the controller.

Clarify that a project/application can be running without RSLogix 5000 software being online to the controller. RSLogix 5000 software acts as a “window” to the project/application.

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

Tip "


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

Rev. February 2007 COMsb56r


Add that for safety, the current communications status between the computer and the controller can be verified in the Online toolbar.

4 -- 3

Remind students that the Online graphic is animated in online mode and that power flow is highlighted in the Run mode. The default color for power flow is green. This can be changed by the user.

Use extreme caution when entering or editing ladder logic or data, forcing values, or making other changes online that will affect the control of devices. Mistakes can cause unintended machine motion or loss of process control, injuring personnel and damaging equipment. Before performing procedures online, complete these safety precautions:

? Define the term “Offline.”

• Determine if changes must be made online. • Verify that your company permits online

Answer: or communicating working with a with project fileViewing while not a controller.

• • • •

enteringhow andmachinery editing. will respond to change s. Assess Check proposed changes for accuracy. Notify all personnel of the cha nges. Verify that you are online to the correc t controller.

Offline: Viewing or editing a copy of a project file that is in the computer only.

Working offline allows you to perform the following tasks: • Repair a system or equipment • Develop or update project components

RSLinx Classic Software RSLinx Classic softwar e creates a connection between an RSLogix 5000 project and other system components . RSLinx Classic softw are is used for a variety of communications tasks: There are 5 levels of RSLinx Classic software. If you do not use an activation file with RSLinx Classic, it will open as RSLinx Classic Lite, the lowest level.

Tip "

Rev. February 2007

• Uploading, downloading, an d going online to a controller • Maintaining a connection betwe en plant floor devices an d other software applications while monitoring or editing a project online

RSLinx Classic softwar e is automatically called anytime a communications option is selected in RSLogix 5000 software.


4--4


The following graphic shows the RSLinx Classic main window: RSLinx Classic Window Backplane Modules RSWho Window Autobrowse Feature Configured Networks Selected Backplane

x Missing or Faulted Module

Mention that RSWho can be accessed both through RSLinx Classic software and RSLogix 5000 software as Who Active, but that Who Active contains more user options.

The RSWho window is the network browser interfa ce for RSLinx Classic 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.

Communications Path

Communication can be initiated using several options: • Who Active dialog box • Current Path toolbar • Recent Path dialog box




Point out that using the RSLogix 5000 Who Active, an option is provided to automatically change the controller type on download. The controllers must be in the same slot. If the controllers are from different platforms, I/O and other platform-specific data will be lost. Selected Driver

4 -- 5

Using the Who Active dialog box is the safest route:

Communications Module Address Backplane Controller

Who Active User Options

Current Path Path Saved in Project

As a safety feature, the type and slot number for the controller selected in RSLinx Classic softwar e must match the project settings .

The addresses (locations ) of devices and networks through which Example: Using the workstation, point out the devices as you review the path a data is sent are listed in the current communications path: project takes when it is downloaded from Communications the computer to a controller: Driver Name for Selected Network Module Address Backplane Controller Slot Number S From the computer through the network cable (TCP-1, EtherNet/IP) S From the network cable into the communications module (130.151.138.103, 1756-ENBT module) S From the module to the backplane (backplane) S From the backplane to the controller (slot 1)

When communicating with the controller, monitoring a project online, etc., RSLinx Classic software can be minimized or closed but not shut down. Shuting down the software will discontinue communications.

Correlation Errors

Various error messages may be displayed when a computer attempts to communicate with a controller.

Rev. February 2007


4--6


Several errors relate to matching project files. Mention that a detailed list of all possible correlation errors and any corrective actions is available in the Help system.

Matching Project File: A computer project file that matches the project file in a controller: • The file was downlo aded to or uploaded from the controlle r. • The file is a copy.

Note that the default project directory is set using Tools→ Options.

If a matching file is not found in the default directory when attempting to communicate, the following options are available: • Browse to and Select the File: Browse to a matching file. • Create a New File: Create a new project file without documentation. • Upload: Upload from controller to update non-matchi ng project file.

Selecting and Changing a Controller’s Operating Mode

? Why might the key be removed from

Logix5000 controllers have three keyswitch positions: • Run

a controller?

• Program

Answer: Controller operating modes dictate when outputs are active. For safety reasons, some companies may remove the keys from the controller to prohibit unauthorized personnel from changing controller modes.

• Remote

The keyswitch positions are labelled on the front of the controller: ControlLogix Controller Keyswitch

CompactLogix Controller Keyswitch

FlexLogix


Controller Keyswitch



The keyswitch position dictates the available controlle r modes:

Remind students that the controller mode is important because of the possible impact on s afety. Add that the mode defines the amount of programming tasks that are available. For example, you cannot configure I/O modules online.

Keyswitch Position

Run

Important: Stress the difference between controller Testtomode (outputs set according Program mode state) and the Test edits step in Verify, Accept, Test, Assemble (outputs scanned and set using the programming language).

4 -- 7

Available Controller Modes

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

Program

during which programming language is not executing, I/O is not controlled, and editing operations are available. Output modules are commanded to their Program mode state (on, off, or hold). Remote Run mode -- This mode is identical to Run mode except you can edit the project online.

Note that Program mode state is set in the output module configuration.

Remote

Note that the Run Mode selection option is inactive (not available) because the controller is already in Remote Run mode.

Remote Program mode -- This mode is identical to Program mode. Remote Test mode -- The controller mode during which code is executing, I/O is not controlled, and limited editing operations are available. Output modules are commanded to their Program mode state (on, off, or hold).

Run mode should only be used when all conditions are safe. Do not use Program mode as an emergency stop (E-stop). Program mode is not a safety device. Outputs are commanded to their Program mode state, which could cause a dangerous situation. Users are able to modify a project file online in Remote Run mode. Be sure to control outputs with care to avoid injury to personnel and damage to equipment.

Outputs are commanded to their Program mode state, which could cause a dangerous situation.

Remotely Changing Controller Operating Mode

With the controller keyswitch in Remote (REM) position, Remote modes can be selected using the Online toolbar:

Online (Mode) Drop-Down List

Remote Mode Selection Options Physical Keyswitch in REM

Rev. February 2007


4--8


Here’s How Use the CCP146_1756r_DEM1.acd to demonstrate. Use the workstation to show students how to manually change controller modes. Emphasize the need to exercise caution when changing modes.


To transfer files to a Logix5000 controller by performing the following tasks: • Select and change a Logix50 00 controller’s operating mode • Upload, download, and go online to a Logix5000 co ntroller

As your instructor demonstrates these procedures, follow along in the associated job aid(s) .



4 -- 9

Exercise: Transferring a Project File to a Logix5000 Controller Exercise A

In this exercise, you will demonstrate your understandin g of project file transfer options in a Logix5000 system.

Directions: For help performing steps in this exercise, see the associated job aid(s). 1. Which option would you chose to trans fer a new project from your computer to a controller?

2. If you wanted to mon itor a project as it is r unning in the controller, would you go offline or online?

3. If you needed to monitor a project running in a controlle r and you do not have a copy of the project on your hard drive, how would you transfer the file from the controller to the computer?

4. Which softwares are used to upload, dow nload, or go online to a controller?

5. Why must you use extreme ca ution when enterin g or editing ladder logic or data, or making other changes online that will affect the control of devices?

Rev. February 2007

E 2007 Rockwell Automation, Inc. All rights reserved. COMe56r

4--10


6. Name at least two safety preca utions to take before making any changes online:

7. Place infor theeach boxes that description: indicates the appropriate opera ting mode aorcheck modes given Description

R un

P ro g ra m

Remote R un

P r o g ra m

Test

The mode in which code is executing, I/O is not controlled, limited editing operations are available, and output modules are commanded to their Program mode state (on, off, or hold). The mode(s) in which project edits can be made safely The mode(s) in which the controller actively controls the process/machine The mode that is identical to program mode

8. How can Run (RUN), Progra m (PROG), and Remote (REM )

modes can be selected?

9. How do you select the Remot e operating modes ?

How Did You Do?


Exercise B

In this exercise, you will practice transferring a project file to a Logix5000 controller.

Directions: For help performing steps in this exercise, see the associated job aid(s). 1. Change the keysw itch of the controller in slot 1 to the Remote position. E 2007 Rockwell Automation, Inc. All rights reserved.

Rev. February 2007 COMe56r


4--11

2. Start RSLogix 5000 software. 3. Open the COM_1756r_B1.acd project file. 4. Download the project to the controller in slot 1 of the workstati on and go online.

Tip "

Download the project with the EtherNet/IP network if available. 5. Verify that you are online in Remote Program mode. 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 back to Remote Pro gram. 9. Go offline. 10. Close the project.

How Did You Do?

Rev. February 2007



4--12


Answers

Exercise A 1. To transfer a new project from your computer to a controller you must download the project. NO TAG The computer must be online to monitor a project as it is running in a controller. 3. To transfer a file from the controller to computer in order to monitor a project running in a controller you must upload the project. 4. Both RSLogix 5000 and RSLinx Clas sic software are used to upload, download, and go online with a controller. RSLinx Classic is automatically called by RSLogix 5000 software when a communications option is selected. 5. Making mistakes online can cause unintended machi ne motion or loss of process control, injuring personnel and damaging equipment. 6. 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 cha nges. • Verify that you are online to the correct controller.

7. The table should be comple ted in the following manner: Description

R un

Remote

P ro g ra m

R un

P r o g ra m

The mode in which code is executing, I/O is not controlled, limited editing operations are available, and output modules are commanded to their Program mode state (on, off, or hold).

n

The mode(s) in which project edits can be made safely The mode(s) in which the controller actively controls the process/machine The mode that is identical to program mode

Test

n n

n n n

8. Run (RUN), Progr am (PROG), and Remote (REM) modes can be selected using the controller keyswitch. 9. With the controller keyswitch in the REM position, you can use the Online toolbar to select the Remote operating modes.




4--13

Exercise B 4. If you are using EtherNe t or EtherNet/IP to downl oad the project, your selection in the RSWho window will appear similar to the following graphic:

5. If you are online in the Remote Progra m mode, you should observe the following conditions: • “Remote Program” is displayed in the Online (mode) drop-down list • The icon in the Path toolbar is animated.

Rev. February 2007


4--14




Lesson

5

Configuring Local 1756-I/O Modules What You Will Learn Explain that in this lesson, students will configure simple digital input and output modules.

After completing this lesson, you should be able to perform the following tasks: • Add a local 1756- I/O module to an I/O c onfiguration • Identify a local I/O tag

Why These Skills Are Important Configuring I/O modules lets the controller send data to and receive data from the process/mac hine. Without properly configured I/O modules, the controller cannot communicate with the process/machine.

Before You Begin

1756-I/O Module Components

Point out the I/O modules in the 1756-I/O modules consist of two main components, the module body workstation. Explain that digital and and the RTB (removable terminal block): analog modules handle different forms of data. Module Side View Module Front View Status ControlBus Indicators Connector RTB

Top Guide

Locking Tab

Connector Pins Slots for Keying

Bottom Guide

Rev. February 2007

E 2007 Rockwell Automation, Inc. All rights reserved. IOCsb56r

5--2

Configuring Local 1756-I/O Modules

• Removable Terminal Block (RTB): A field wiring connector for I/O modules. Field wiring is connected to an RTB rather than directly to a module terminal block. • Interface Module (IFM): A field wiring arm that uses prewired/factory-wired cable to connect to an I/O module. • ControlBus Connector: The backplane connect or interface for the ControlLogix system that connects the module to the ControlBus backplane. • Connector Pins: Pins that create input/output, power and grounding connections to the module through an RTB or IFM. • Locking Tab: Anchors the RTB or IFM cable on the module, maintaining wiring connections. • Slots for Keying: Mechanically keys the RTB to prevent inadvertently making the wrong wire connections to the module. • Status Indicators: Display the status of communications , module health, and input/output devices. Use these indicators to help troubleshooting errors or system faults. • Top and Bottom Guides: Provide assistance in seating the RTB or IFM cable into the module.

RIUP (Removal and Insertion Under Power) RIUP: A ControlLogix feature that allows 1756 modules to be Encourage students ask what the module is doing in thetoactive process before removing it. Note that modules can easily be removed by pressing the top and bottom locking clips at the same time and sliding the module forward.

removed and inserted into a chassis while the backplane power is applied. When a module is inserted or removed while backplane power is applied, an electrical arc may occur. An electrical arc can cause personal injury or property damage by causing the following situations: • Sending a false signal to field devices caus ing unintended machine motion or loss of process control • Causing an explosion in a hazardous environ ment Repeated electrical arcing causes excessive wear to contacts on the module and its mating connectors. Take adequate safety precautions when inserting or removing a module under power.

Taking safety precautions, remove a module from the chassis.

Tip "


Modules can easily be removed by pressing the top and bottom locking clips at the same time and sliding the module forward.

Rev. February 2007 IOCsb56r


5 -- 3

LED Status Information Give an example of the status of a properly functioning module vs. an improperly functioning one.

I/O Status

LED indicators are located on the front of all I/O modules to show if all connections and communications are functioning properly:

Fuse Status

Fault Status

Module Status

Diagnostic Module

Electronically Fused

• I/O Status: The yellow status indicator shows the ON/OFF state of the field device. • Module Status: This green status indicator shows the module’s communication status. • Fault Status: This display, found on some modules, indicate s the presence or absence of various field-side faults. • Fuse Status: This display, found on electronically fused modules, indicates the state of the module’s fuse.

Digital and Analog I/O Modules Review the differences between input and output devices.

1756-I/O modules proces s two types of data: • Digital: Information represented by a discrete value (i.e., 1 or 0). • Analog: Numeric values that represent measurable quantities, such as temperature, weight, and pressure.

Digital 1756-I/O Modules

Digital 1756-I/O modules communicate with discrete (on/off) devices:

Pushbuttons Limit Switch Photo-Electric Sensor Motor

Rev. February 2007


5--4


Explain that digital I/O can also be referred to as “discrete” I/O.

Digital 1756-I/O modules provide on/off detection and control for items that utilize digital data. They have the following properties: • RIUP (Removal and Insertion Under Power) • 8-, 16-, and 32-point varieties • Electronic keying

Point out the digital and analog I/O modules in the chassis.

? Can anyone name additional analog devices?

• Isolated, non-isolated, and diagnostic var ieties:

-- Module-level fault reportin g and field-side diagno stics • Electronic fusing Analog 1756-I/O Modules Analog 1756-I/O modules communicate with the following types of devices:

Gauges/Meters Flow Meters

Thermometer

Analog 1756-I/O modules convert analog signals to digital values for inputs and convert digital values to analog signals for outputs. They have the following properties: • RIUP • Scaling to engin eering units calculated in the mo dule • 32-bit floating or 16- bit input and 13-16 bit output integ er data format depending on the module • Alarming • Rolling time stamp of data • Diagnostic choices




Local and Remote I/O Modules

Give examples of situations when it would be appropriate to use local I/O rather than remote I/O and vice versa:

S If the controller is located within a few feet of the process/machine and the wiring configuration between the I/O system and process/machine is simple, or if high c ommunication speed is required, then local I/O should be used. S If the controller is located very far from the

5 -- 5

Tip "

process/machine and if the wiring configuration between the I/O system and the process/machine is complicated, then remote I/O should be used.

Local and remote I/O modules can be configured in a Logix5000 t system based on the needs of the application. Local I/O Modules

Local I/O modules communicate with a controller across a backplane, thus limiting their distance from the controller. ControlLogix r systems do not support I/O modules across a parallel link (i.e., extended local I/O).

Remote I/O Modules

Mention that a remote ControlLogix chassis housing I/O modules is the most common option for remote I/O modules. If available, pass around a sample module for the students to see.

Remote I/O modules are not located in the same chassis as the controller that configures them. This allows I/O to be located in a closer proximity to the process:

Controller Local ControlLogix Chassis Communications Module

Process/Machine Communications Module Remote ControlLogix Chassis Control-Level Network

Example: 1756-ENBT Tip modules must be included in both chassis to create an EtherNet/IP network connection.

Rev. February 2007

"

Both the local and remote chassis must have communications modules to create a connection with the desired network


5--6


Read the names of one digital and one analog module from the workstation.

1756-I/O Module Identification

? Describe the module with the catalog

To identify a local device tag, the module type must be identified first by referring to the part number on one of the following items:

number 1756--OB16D.

• RSLogix t 5000 software I/O configuration

Answer: This module is a 16-point, DC output module with diagnostic features.

• Plant drawings • Hardware label (inside the module do or) • Factory sticker on the side of the m odule • RSWho network interface in RSLinx r software

I/O module identification becomes an important issue during the configuration process, when there are many available modules to choose from. RSLogix 5000 Software I/O Configuration

The part number identifies severa l characteristics of the device: I or O for Input or Output A for AC, B for DC, F for Fast Response Analog Number of Points or Channels Suffix (Diagnostic, Electronic Fusing, Individually Isolated, Voltage only, Current Only, etc.) OB16D

Module Slot Number

Tip "

Points refer to the number of physical locations at which wires can be connected to an I/O module.

I/O Configuration I/O modules are not the only type of module that can be configured in the I/O Configuration folder. Module such as bridges and controllers can also be configured there.

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

Configured Local 1756-I/O Modules Be sure to mention that this is a very basic overview of module configuration. For more details, students should attend an advanced course in the curriculum. Note that the Communications Format is one parameter that cannot be changed online.

Tip "


Every I/O module that sends process/machine data to a controller must be configured by a controller. Modules can be added online or offline, but they only can be deleted offline. Most configuration parameters can be changed online.



5 -- 7

When you add a new I/O module to a project, you are first prompted to enter general module properties in the New Module dialog box:

Once data has been entered in the New Module dialog box, you can then continue module configuration from the Module Properties dialog box. Parameters for configuring a digital 1756-I/O module are entered on the following tabs in the Module Properties dialog box: • General • Connection • Configuration

General Tab The following graphic shows the General tab parameters:

Name

Slot Number

Communications Format (Ownership) Electronic KeyingLevel and Revision

Rev. February 2007


5--8


Electronic Keying Explain that the compatible module keying option is the most common configuration choice.

To avoid installation or replacement errors, keying prevents controller from communicating with the wrong module: • Exact Match: All I/O module information must match (i.e., module type, major revision, and minor revision). • Compatible Keying: All I/O module information except minor revision must match. • Disable Keying: Minimum information must match (i.e., module type only) .

Communications Format (Ownership)

The communication s format parameter defines how an I/O module communicates with a controller. The following options are available: • Full Diagnostics: I/O connection where the module is owned by the controller, receiving configuration data from it:

-- The I/O module retur ns diagnostic dat a (e.g., Fuse Blow n, No Load) along with a timestamp of when the diagnostic data changes state. • Listen-Only Connection: I/O connection where another controller owns/p rovides the configuration data for the I/O module. The I/O module does not write configuration data.

Connection Tab The following graphic shows the Connection tab parameters:

Requested Packet Interval (RPI) Inhibit Module Connection Option Major Fault Option




5 -- 9

Requested Packet Interval (RPI): Also referred to as the “multicasting rate,” this is the rate at which data is simultaneously transmitted to all nodes or modules:

The RPI time indicates that data will updated at least as fast as the set time. It can be updated faster than the set time.

• The RPI specifies the time that elaps es before the modu le multicasts the current data in the on-board memory • The RPI can vary from 200 microseconds (.2 ms) to 750 ms

Inhibit Module Connection Option: An option that allows configuration data for a module to be written but prevents the module from communicating with the owner controller. Major Fault Option: An option that causes a major fault on the controller if the connection to the module fails.

Configuration Tab The following graphic shows an example of the Configuration tab parameters: Diagnostic Features

I/O Points

? How are diagnostic modules identified in the part number? Answer: The part number has a “D” as the suffix, e.g., 1756-IB16D.

Depending on the module, 1756 digital and analog diagnostic I/O modules can have the following diagnostic features: Open Wire Detection: Senses removed or disconnected field wiring on an input module: • A leakage resistor must be place d across the contac ts of an input device. • The modules must detect minimum leaka ge current or a point-level fault is sent to the controller.

Field Power Loss Detection: When field power to a module is lost,

a point-level fault is sent to the controller. No Load Detection: Senses the absence of field wiring or a missing load from each output point in the off state only.

Rev. February 2007


5--10


Field-Side Output Verification: Indicates that the ladder logic changes are accurate ly represented on the power side of a switching device (i.e., the output is on when it is commanded to be on). Point-Level Electronic Fusing: Internal electronic fusing that prevents too much current from flowing through a module. This feature clears fuses when an instruction in RSLogix 5000 software resets the fuse or a power cycle resets the fuse.

Add that latching can help you see where a fault occurred even if the cause of the fault has already been cleared (e.g., if the fault occurred and cleared overnight). Note that diagnostic modules require the most configuration. The workstation modules are diagnostic. This will give students the most practice.

Diagnostic Latching: Sets and retains a faulted state (bit) upon detection of any diagnostic faults: • The fault data is m ulticast to all controller s. • The I/O module LED displays a fault. • A fault bit is latc hed and can be exam ined in the tags lis t.

Asynchronous Updates Asynchronous: Actions that occur independently of each other and lack a regular pattern .

Mention in step one that the data is multicast to the backplane then received by the controller. Chalk Talk: If students are from PLC or SLC background, you may want to draw the PLC/SLC scan diagram on the board for comparison. When reviewing the diagram, explain the following steps based on the experience of the class and the lessons already covered: Tip " 1. Each rung of ladder logic (code) is scanned.

In Logix5000 controllers, I/O values update asynchronously with the execution of code: 1. Input modules mult icast their data to the backpla ne at the RPI rate set in the modules. 2. The code is scanne d and the output tags are updated immedia tely

after the execution of each output instruction. 3. Values are sent to the output modules at the RPI rate and at the end of each task. The automatic output processing that occurs at the end of a task can be disabled in the properties of the task.

2. As higher numbered rungs are scanned the inputs may change and therefore, the outputs may change as reflected in the tag database image. 3. The RPI is the rate at which the user configures the output modules to update.




5--11

Because of the update process, input devices may change state within one program scan and at a different rate than the program scan: Photo-eye tag is set in database 100

Photo-eye tag is cleared in database 250 RPI Rate

Input module and the physical devices are updated

Photo-eye tag is set in database 400

End of Task

If enabled, input module and the physical devices are updated

Identifying an I/O Module Tag Module-Defined Data Type: A data type assigned to a tag that is automatically generated when a communications or I/O module is added to an RSLogix 5000 project.

I/O base tags use the following format:

Location:Slot:Type.Member.Submember.Bit I/O Point (Optional) Emphasize that each component of a base tag depends on the type of hardware used.

Member-Specific Data (Optional) “Data” (I/O Values), “Fault”, etc. “I” for Input, “O” for Output, “C” for Configuration

Mention that submembers and bits are optional.

Module Slot Number “Local” or Module Name for Remote

Tip " Rev. February 2007

Digital I/O tags do not include submember and bit information. E 2007 Rockwell Automation, Inc. All rights reserved. IOCsb56r

5--12


Example: Input Base Tag

An input device wired to point six on a module in slot two: Local:2:I.Data.6 Example: Output Base Tag

An output device wired to point three on a module in slot nine: Local:9:0.Data.3

Here’s How Create a new project in RSLogix5000 software. Configure digital I/O modules in your workstation.


To add a local 1756-I/O module to an I/O configuration. As your instructor demonstrates this procedure, follow along in the associated job aid(s).



5--13

Exercise: Configuring Local 1756-I/O Modules Exercise A

In this exercise, you will demonstrate your understandin g of local 1756-I/O modules.

Directions: For help performing steps in this exercise, see the associated job aid(s). 1. What are the differe nces between local and remote I/O?

2. Why are devices w ired to an RTB rather than directly to the I/O module?

3. Examine the digital input modu le in your workstation. What status indications are given by the module?

4. Which I/O compone nt connects the module to the rest of the chassis?

5. Which configura tion feature prevent s a connection from the controller to the wrong module?

Rev. February 2007

E 2007 Rockwell Automation, Inc. All rights reserved. IOCe56r

5--14


6. Describe the conversions that an analog I/O module perfor ms:

7. How does the asynchron ous relationship between I/O module updates and code execution affect output?

8. Explain the Compatib le Module electro nic keying option:

9. Choose the I/O module charac teristics (input vs. output and digital vs. analog) that correspond to each of the following devices: Device

Input

Output

Digital

Analog

LED Thermometer Motor Contactor Pressure Gauge Pushbutton Start/Stop switch Light Sensor

How Did You Do?



Rev. February 2007 IOCe56r


Exercise B

5--15

In this exercise, you will practice configuring local 1756-I/O modules.

Directions: For help performing steps in this exercise, see the associated job aid(s). 1. Open the IOC_1756r_B1.acd project file. 2. Add the following loca l 1756-I/O modules in your wor kstation to

the I/O configuration of the Controller Organize r: Module Type

Default Slot

Notes • Ensure that the Comm. Format option is set to Full

Digital Output Module

Diagnostics-Output Data. 0

• Ensure that the Electronic Keying is set to Compatible Keying. • Make sure that diagnostics (including latching) are enabled for

points 0-5 only. • Keep other options at their default settings.

Digital Input 2 Module

Change only the module name and slot number settings.

Make sure that the configured slot numbers match the actual module slot numbers.

3. Download the project to the controller in slot 1 and go online. 4. Place check mark s in the available boxes after verifying the following conditions:

-

The OK light on the output module (slot 0) is steady green. The OK light on the input module (slot 2) is steady green. The I/O light on the controller is steady green. The I/O OK light on the online toolbar is steady green. A warning icon (yellow triangle) does not appear on the I/O configuration folder or the modules in slot 0 and 2 in the Controller Organizer.

5. If applicable, correct any faul ted modules.

Tip "

If there are FLT (fault) LEDs illuminated on the face of the output module, verify that the diagnostic selections on the Configuration tab for the output module are cleared. 6. When all modules are configure d and running correctly , go offline and close the project.

Rev. February 2007


5--16


7. Identify the I/O tags fo r the following descr iptions: A. An input device wired to point two on a module in slot four:

B. An output device w ired to point six on a module in sl ot one:

C. An output device wired to point one on a module in slot six:

How Did You Do?





Rev. February 2007

5--17


5--18


Answers

Exercise A 1. The following answers are possible correct responses: • Local I/O module s are located in the same cha ssis as the controller. Remote I/O modules are located in a separate chassis. • Communications between local I/O modules a nd the controller is faster than between remote I/O modules and the controller. • Local I/O module s communicate with the controlle r across the ControlBust backplane. Remote I/O modules communicate with the controller over a control network (i.e., ControlNet t) 2. When devices are wired to an RTB ra ther than directl y to an I/O module, alterations to the wiring scheme can be made without removing the entire module. Keying slots prevent the wrong RTB from being inserted in the wrong module. Also, the RTB allows for easier faster module replacem ent in that rewiring is unnecessary.

3. The OK light on the input mod ule (slot 2) shoul d be steady green. 4. The ControlBus co nnector connects the I/O module to the rest of the chassis, allowing for communications with the local controller. 5. Electronic keying compares ke ying informatio n in the

controller to keying information in the I/O module. This ensures that data is being sent and received to and from the correct module. 6. Analog modules convert analog signa ls to digital values for inputs and convert digital values to analog signals for outputs. These conversion s are performed because the controller can only deal with digital values. 7. The asynchronous relationship between code execution and I/O module updates means that output data is not being sent to the process/machine as code is executing. The real output may not match up with output displayed by the code execution. 8. The Compatible Mod ule electronic keying option allows all I/O module information except minor revision to match.



5--19


9. The table should be comple ted as shown below : Device

Input

LED Thermometer

Output

Digital

√

√

√

√

√

Motor Contactor Pressure Gauge

Analog

√

√

√

Pushbutton

√

√

Start/Stop switch

√

√

Light Sensor

√

√

Exercise B 2. The following dialo g boxes should match your config ured I/O module for slot 0:

Rev. February 2007


5--20


The following dialog boxes should match your configured I/O module for slot 2:




5--21

7. The correct tags for the descripti ons are listed: A. An input device wired to point two on a module in slot four: Local:4:I.Data.2 B. An output device w ired to point six on a module in s lot one: Local:1:O.Data.6 C. An output device wired to point one on a module in slot six: Local:6:O.Data.1

Rev. February 2007


5--22




Lesson Optional: A lesson on Identifying Numbering Systems and Converting Numeric Values is available. This lesson is not a requirement for the course.

What You Will Learn

6

Creating Tags and Monitoring Data in an RSLogix 5000 Project After completing this lesson, you should be able to create tags and monitor data in an RSLogix 5000 project by performing the following tasks: • Create tags in the Edit Tags list • Define an alias tag • Monitor and edit data in a Logix5000 t controller

Why These Skills Are Important These skills are important for the following reasons: Mention that factors such as the order in which data is entered can have an effect on the overall project file size.

• Being able to cre ate tags and monitor data in RSLogi x 5000 software is critical to developing a project that efficiently stores values in memory. • Having a properly organized proje ct and project tags will help reduce downtime during maintenance and troubleshooting activities.

Before You Begin

Tags Memory: A group of circuit elements in a controller where programs and data are stored.

The following are common memory sizes: • Bit: The smallest unit of data represented by the digits 0 and 1 • Byte: A string of 8 bits operated on as one unit. • Word: A unit of memory in a controller composed of 16 individual bits (or two bytes) that are treated as one unit.

Tag: An area of controller memory where data from devices, calculations, faults, etc. is stored. Each area is given a unique name:

“Drive_Speed” Data Controller Memory “Sensor” Data “Start” Data

Rev. February 2007

E 2007 Rockwell Automation, Inc. All rights reserved. TAGsb56r

6--2


Tip "

Traditional controllers have data files where groups of the same types of data are stored together .

Note that a PLC-5 processor has a pre-created timer file, where all timers are stored together.

There are no pre-created data files in a Logix5000 controller. Programmers must define controller memory by creating tags.

Programmers can perform the following tasks using tags: •

Organize data to mirror the process/machine • Document, through tag names and descr iptions, the appli cation as a project is developed

Data Types Add that the data type maps out the data just as it does in a PLC-5, SLC 500, or other processor.

Data Type: The definition of how many bits, bytes, or words of data a tag will use. The data type is based on the source of the information. Pre-Defined Data Types: Commonly used memory sizes that are already defined in the software. Atomic Data Type: A simple data type made of one piece of data:

Indicate that BOOL, INT DINT, and REAL data typesSINT, are called atomic data types.

Data Type

Definition

BOOL

Adiscrete single bit where 1 = as onaand 0 = off the state of a device such pushbu tton(e.g., or sensor)

SINT INT

Note that the DINT data type is the main data type. More details will be presented later in the lesson.

A short integer (8 bits) between --1 28 and +127 An integer or word (16 bits) between --32,768 and +32,767 (e.g., PLC-5r data)

DINT

A double integer (32 bits), used to store a base integer number in the range of --2,147,483,648 to +2,147,483,647 (e.g., serial number)

REAL

A 32-bit floating point value (e.g., an analog value such as a potentiometer value)

A DINT (32 bits) is the main data type used in Logix5000 systems. It is the main data type because it is the minimum memory allocation for any tag.


Rev. February 2007 TAGsb56r

6 -- 3


Using these definitions , tags for the given devices require the following data types: “Drive_Speed” Data DINT, or 32 Bits

Controller Memory

“Start” Data BOOL, or 1 Bit

Relate this to a timer relay where there is on/off data as well as a preset value.

“Sensor” Data BOOL, or 1 Bit

Structure: A more complex data type that is made up of several pieces of data. For example, a TIMER data type is made up of a combination of DINTs and BOOLs.

The following table lists commonly used structures: DataType

Tip "

Give an example, such as the TOTALIZER data type, which is used with the TOTALIZER function block. The data type contains a member for each parameter of the function block.

Definition

COUNTER

Increasing or decreasing total

TIMER

Increasing time total (milliseconds)

There are other less common, pre-defined data types that are used to store specific data for function block instructions or motion instructions. Module Defined Data Types: Data types used for hardware data, such as I/O tags.

Alias Tags Alias Tag: An additional name for a tag (or other alias tag): Tell students that if a base tag is used as an address, any corresponding alias tags will not be displayed.

Tip "

Rev. February 2007

• The tags refer to the same area of memory . • The tags, therefore, reflect the same value s and changes.

An alias tag can be used to identify an automatically generated I/O tag with a complex name. For example, Motor can be an alias tag for Local:2:O.Data.15.


6--4


Scope Scope: The definition of where a controller can access a tag or set of tags.

A tag must be designated as one of the following scopes: Note that while the open accessibility of controller-scoped tags is a benefit, program-scoped tags can be easily reused, resulting in less tags for a project (easier to maintain and troubleshoot).

• Controller-Scoped Tag: A tag that can be used by all tasks, programs, and routines within a project and is accessible to other devices.

Mention that controller-scoped tags are also known as global tags.

routines within a specific program of a project. Therefore, the tag name may be reused in different programs .

• Program-Scoped Tag: A tag that can be referenced only by the

Within a project, tags are located in different collections depending upon their scope: Point out in the graphic that the controller-scoped tags are located under the controller project name folder. The tags that can only be reference by routines within a program (program-scoped) are located within that program’s folder. Example: The MainLadder routine cannot access the program-scoped tags under the ProcessSimulation program.

Tags Icon

Controller-Scoped Tags Collection

Program-Scoped Tags Collection Program-Scoped Tags Collection

Tip "


Each Tags collection has a Monitor Tags tab and an Edit Tags tab.



6 -- 5

Monitor Tags Tab Point out the various unlabeled elements of the spreadsheet, including the rows, cells, columns, etc.

The Monitor Tags tab is a direct view of a controller’s memory. It allows users to perform the following tasks:

Mention that operand descriptions will appear with the tag in logic if configured to do so.

• Assign values to specific tags

• Monitor tag values in an active co ntroller (online) • Set operand (tag) descriptions • Define tag style

Right-Click to Hide/Show/Sort Columns

Scope of Current Blue Collection Arrow Filter Display Style Tag and Members Data Type

Operand (Tag) Descriptions

Value in Controller Expand to See Structure Members or Bits within the Tag

Monitoring View

Stress that finding tags is a key step in monitoring. The way in which tags are filtered can help limit the number of tags displayed. If used improperly, it can also hide required tags.

Tags and Members

Tags of the same data type are not automatically displayed together in the Monitor Tags tab: • Tags can be displayed alphabetically (default mode). • Tags can be sorted and filter ed (e.g., show DIN T tags only) • Tags that are structure s (TIMER, etc.) can be expanded to display members.

Display Style State that data from a BCD thumbwheel could be viewed in the hexadecimal style.

The Style parameter controls how data is displayed for certain tags. Example: DINT Display Style

The default style for a tag of the DINT data type is decimal. This can be changed to binary, octal, decimal, or hexadecimal.

Tip "

Rev. February 2007

Style is for display only; it does not affect how data is stored in the controller.


6--6


The Show drop-down menu is available for changing the Tags window display. It lets the user filter tags out of the window viewing area.

Tip "

Individual columns can be sorted in the window viewing area. Edit Tags Tab

Both Tags windows contain many of the same lists. Options such as style and descriptions can be changed from the Monitor and Edit tags windows.

The Edit Tags list lets users perform the following tasks: • Create and delete tags • Create tag aliases • Define tag data types

In the graphic, point out the Tag Name, Scope, Data Type (Type), and Description fields. Remind students that these are tag parameters. Point out the Value column and the blue arrow.

• Define tag style • Set operand (tag) descriptions

The following parameters can be modified in the Edit Tags tab:

Tag Name

What this is an Alias Tag For

Display Style Data Type

Operand (Tag) Descriptions

White = Editable Field Editing View

• Tag Names: A name a user supplies to reference a tag instance. • Data Type: A definition of the size and layout of memory that will be allocated when a tag of the data type is created. • Style: The format in which number system values for data type members are displayed within RSLogix 5000 software. • Descriptions: A string of characters that defines the purpose or function of a tag.

Tags that contain an error are marked with an “X” in the first column.




6 -- 7

When online, only the tag name, style, and description can be changed.

Stress the difference between editing the tag (e.g., tag name) and changing the tag data, such as the preset. In this ladder logic example, point out that values can be monitored and certain values, such as timer presets, can be

Monitoring and Editing Tag Values through a Routine Tag values can be monitored and sometimes edited online through instructions in routines:

edited. Blue Arrow: Change will Immediately Take Effect in the Controller

Here’s How Use CCP146_1756r_DEM1.acd to demonstrate the procedures.

To create tags and monitor data in an RSLogix 5000 project by performing the following tasks: • Create tags in the Edit Tags list • Define an alias tag • Monitor and edit data in a Logix5000 controller


Rev. February 2007


6--8




Exercise: Creating Tags and Monitoring Data in an RSLogix 5000 Project

6 -- 9

Exercise: Creating Tags and Monitoring Data in an RSLogix 5000 Project Exercise A

In this exercise, you will demonstrate your understanding of tags and data in an RSLogix 5000 system.

Directions: 1. Label the follow ing common memory siz es: Description

UnitofMemory

A unit of memory in a controller composed of 16 individual bits or two bytes that are treated as one unit. The smallest unit of data represented by the digits 0 and 1. A string of 8 bits operated on as one unit.

2. Define the term “tag”:

3. Define the term “data type”:

4. What is a data type f or a tag based on?

5. A programmer needs an instru ction in her project to execute an action for 500 ms. What kind of data type would the tag for this instruction require?

Rev. February 2007

E 2007 Rockwell Automation, Inc. All rights reserved. TAGe56r

6--10


6. AirTemperature is a tag that receives its data from a physical device. Based on the type of data (REAL), this tag is connected to which type of device?

-

Discrete device (digital module) Analog device

7. Start is a tag that receives its data from a physical device. Base d on the type of data (BOOL), this tag is connected to which type of device?

-

Discrete device (digital module)

-

Analog device 8. What is the main data type used in Logix5000 syste ms and why?

9. Define the term “alias tag”:

10. A tag that can be access ed by every program and routine is of which scope?

11. If you opened a tag collection, whic h tab would you choose to modify tag values in an active controller (online)?

12. If you opened a tag collection, whic h tab would you choose to create and delete tags?


Rev. February 2007 TAGe56r


6--11

13. Review the follow ing statements reg arding the display of tags in a tags collection. Check all of the statements that are true:

-

Tags of the same data type are not automatically displayed together.

-

Tags can be displayed alphabetically (default mode).

-

Tags that are structures (TIMER, etc.) can be expanded to display members.

Tags can be sorted and filtered (e.g., show DINT tags only).

How Did You Do?


Exercise B

In this exercise, you will practice creating tags in an RSLogix 5000 project.

Directions: For help performing steps in this exercise, see the associated job aid(s). 1. Open the TAG_1756r_B1.acd project file. 2. Create the follow ing tags in the Controller Tags database: Device/TagName

Type

Description

Conveyor_Moving

BOOL

Indicates conveyor movement

Conveyor_Start

BOOL

Starts the conveyor

Conveyor_Start_Time

TIMER

Keeps the conveyor moving for a set amount of time

Conveyor_Stop

BOOL

Stops conveyor process and resets the timers

Conveyor_Stop_Time

TIMER

Keeps the conveyor stopped for a set amount of time

Process

BOOL

Indicates that the process is taking place

Restart

BOOL

Restartstheprocess

3. Sort the tags so that all tags of the same data type ar e together. 4. Filter the tags to show only the tags of the BOO L data type. 5. Filter the tags to Show All T ags. 6. Resort the tags to display the tags by name in alphabetical order. 7. Save the project.

How Did You Do? Rev. February 2007



6--12


Exercise C

In this exercise, you will practice creating tags and monitoring data in an RSLogix 5000 project.

Directions: For help performing steps in this exercise, see the associated job aid(s). 1. Open the TAG_1756r_C1.acdproject file. 2. Define the followi ng controller-scoped tags as alias tags for the

local I/O tags: Device/TagName

Conveyor_Moving

LocalI/OTag

Local:0:O.Data.5

Conveyor_Start

Local:2:I.Data.0

Conveyor_Stop

Local:2:I.Data.1

Process

Local:0:O.Data.2

3. Download the project to the controller in slot 1. 4. Place the contro ller in the Remote Run mode. 5. Monitor the tag informa tion in the Monitor tags tab. 6. Expand the Conveyor _Start_Time tag to see all data related to the timer. 7. If you are using the standar d workstation, re fer to the following workstation diagram to test your project: Conveyor_Stop

Conveyor_Start

Process

Conveyor_Moving

8. On your workstation, pres s Conveyor_Start (button DI0). 9. What happens to to the Conveyor_Mo ving output (light DO5) and the Process output (light D02)?

10. What is the value of the Conveyor_Mo ving tag and the Process

tag?




6--13

11. What happens to the Conveyor_Sta rt_Time timer data?

12. On your workstation , press Conveyor_S top (button DI1). 13. What is the value of the C onveyor_Moving tag?

14. Close the project.

How Did You Do?

Rev. February 2007



6--14


Answers

Exercise A 1. The common memory size s are labelled in the following table: Description

UnitofMemory

A unit of memory in a controller composed of 16 individual bits or two bytes that are treated as one unit.

Word

The smallest unit of data represented by the digits 0 and 1.

Bit

A string of 8 bits operated on as one unit.

Byte

2. A tag is an area of controller mem ory where data from devices , calculations, faults, etc. is stored. Each area is given a unique name. 3. A data type is the definition of how many bits, bytes , or words of data a tag will use. 4. The data type is based on the source of the inform ation. 5. The programmer would select a TIMER data type. 6. Based on the type of data (REAL), the AirT emperature tag is connected to an analog device. 7. Based on the type of data (BOO L), the Start tag is connecte d to a digital/discrete device. 8. A DINT (32 bits) is the main data type use d in Logix5000 systems. It is the main data type because it is the minimum memory allocation for any tag. 9. An alias tag is an additional nam e for a tag (or another alias tag). An alias tag can be used to identify an automatically generated I/O tag with a complex name. For example, Motor can be an alias tag for Local:2:O.D ata.15. 10. A tag that can be access ed by every program and routine is a controller-scoped tag. 11. To modify tag values in an active controller (online) you must select the Monitor tab. 12. To create and delete tags yo u must select the Edit tab. 13. All of the statemen ts regarding the disp lay of tags in a tags collection are true:


n

Tags of the same data type are not automatically displayed together.

n n

Tags can be displayed alphabetically (default mode).

n

Tags that are structures (TIMER, etc.) can be expanded to display members.

Tags can be sorted and filtered (e.g., show DINT tags only).



6--15

Exercise B 2. Your tag database should appear similar to the following example: Controller Scope

Filter

Sort By Name

Exercise C 2. The following alia s tags tags were created:

9. The Conveyor_Moving light (DO5) alternat es with the Process light (DO2). 10. The values of Conveyor_M oving and Process altern ate between on (1) and off (0). 11. The Conveyor_Start_Timer timer tag begins collecting timer data each time Conveyor_Moving is on (1). 13. Conveyor_Stop stops the conveyor . Therefore, the value of Conveyor_Moving is also 0. Rev. February 2007


6--16




Lesson

7

Monitoring Arrays and Tags of User-Defined Data Types in an RSLogix 5000 Project What You Will Learn Review the definition of the term tag.

After completing this lesson, you should be able to troubleshoot an RSLogix 5000 project by performing the following tasks: • Monitor array tags through the Tags window • Monitor tags of user- defined data types through the T ags window

Why These Skills Are Important Often, well-des igned applications take advantage of more complex tags. These tags may combine multiple elements of the same data type into an array or may consist of new, user-defined data types. Understanding how to interpret and monitor these complex tags is essential to troubleshooting an application.

Before You Begin Note that an array that is a member of user-defined data type can only have one dimension.

Key Terms Array: A numerically indexed sequence of elements of the same data type. An array tag occupies a contiguous section of memory in the controller with each element in sequence. Arrays can have one, two, or three dimensions . Element: A single position within an array.

Relate this to PLC-5 data, where N7:0 to N7:9 is a one-dimensional array of integer data types. Note that an array of Part[40] will have elements of Part[0] to Part[39]. Stress that it is easier for a programmer to create a single-dimensional array of 100 DINTS than it is to create 100 individual tags.

Example: Array

A controller needs to store a piece of data for six different parts. This data can be stored in an array of 6 INTs: Array of 6 INTs

Group of 6 INTs (Numbered 0 to 5)

One Element

Point out that you can create an alias tag for each element of an array. For example, Cold_Timer might be an alias for TIMER [34].

Rev. February 2007

E 2007 Rockwell Automation, Inc. All rights reserved. ADTsb56r

7--2


Array Addressing Note that the number or expression in the brackets is the subscript. Point out the square brackets that enclose the element number.

An instruction might examine or write to one element of an array: Part_Data[3] Single Element of a 1 Dimensional Array

ArrayName

As an example, state that if

If an array total is 100, then you can address

Position1andfault the array an array of-Position2=48 only 40, a major will is occur.

elements 0-99. A major fault is generated if code attempts to read from or write to an array element location that exceeds its corresponding dimension, e.g., if an array = Part[100] and an instruction attempts to write data in Part[150].

Note that if executable code attempts to read beyond an array limit, it will read the next tag in memory and process the data accordingly.

Certain data types can support one-, two-, or three-dimensional arrays: Part_Data[2,5,3]

ArrayName Add that an array might include data stored by shift, day, and week. Or, x and y coordinates (for retrieving a part in storage).

Dimension 3 Dimension 2 Dimension 1

Example: Three Dimensional Arrays

Three dimensiona l arrays might store the following data: Part[2,3,0]

Storage[5,2,773] Part Number Shift Number Day

Tip "


Color Size Weight

Array dimensions are separated by commas.

Rev. February 2007 ADTsb56r

7 -- 3


Advanced Array Addressing Point out that a period indicates the next sublevel of an address. A tag without a period is the whole address.

The following table contains more advanced array formats and examples: If you monitor a tag in this format . . .

Example

Itisa ...

ArrayName[Element]

Part[5]

Standard single dimensional array element

ArrayName[Tag]

Station[Position]

Changing

ArrayName[Expression] ArrayName[Element].Bit

Station[Position+5] Part[5].15

element Bit in the element

ArrayName[Epression].[Tag] ArrayName[Expression].[Expression]

Part[IndexAND7].[MyIndex] Part[IndexAND7].[MyIndex+31]

Changing bit in the element

User-Defined Data Types Structure: A data type that combines other data types. E.g., a TIMER data type is made up of DINTs and BOOLs. Review: An element is one part of an array, while a member is one part of a data type.

User-Defined Data Type: A structure created by a programmer to group related data in an application. Member: One data type within the structure. Example: User-Defined Data Type

Chalk Talk:the Before showing slide, have students help the younext make a list of the members that might go into the user-defined data type for the tank example. Have the students select the data type of each member.

There are several identical tanks in an application. Each tank has data that needs to be stored:

Temperature Steam Valve State Time Over Temperature Level

Rev. February 2007


7--4


Provide other examples, including examples of recipe parameters and storage data types.

To store this data, a programmer creates a user-defined data type. This data type is then available for new tags: Data Type Name Tag Name

Members Tank Data Type

Structure within Structure

User-Defined Data Type Addressing Note that this is similar to how you address TIMER members in other projects (T4.EN or T4.TT). State that the delimiter is a period. Point out that the last example contains a structure (Load_Info) that is embedded in the user-defined data type.

Just as TIMER members are addressed (Total_Timer.EN or Total_Timer.TT), you can address members of a user-defined: Tag.Member

Examples: User-Defined Data Type Addressing

Specific data can be addressed in a tag of a user-defined data type: Tanks.Level Input_Load.Height Input_Location.Load_Info.Weight

Arrays and tags of user-defined data types can be mixed, providing extreme programming flexibility. Note that in this scenario, the user-defined data type is created first, and then the array of tags is created. Tank [0,0]

Example: Arrays and User-Defined Data Types

If there are 25 tanks (5 rows of 5), a programmer can make an array of tags that uses a user-defined data type: Array = [5,5]

One Specific Element = Tank[1,3]




Note that prior to version 12, RSLogix 5000 software optimized array indexing (indirect offset, such as Table[tag]) for single-dimensional array using pre-defined data types. This optimization includes single-dimensional array of user-defined data types.

? Identify other tags, such as the level

Example: Addressing

To observe the temperature value for the tank in position [1,3], the following tag would be addressed in the ladder logic: Tank[1,3].Temperature

for the tank in position 1,4.

To observe the preset of the timer for the tank in position [1,3], the following tag would be addressed in the ladder logic:

Answer: Tank[1,4].Level

Tank[1,3].Time_Over_Temp.PRE

Here’s How

7 -- 5

To monitor arrays and user-def ined data types by performing the following actions: • Monitor array tags through the Tags window

These procedures can be found in the Procedures Guide under Monitoring and Editing Tag Values through the Tags Window which is a subprocedure of Monitoring and Editing Data in a Logix5000 Controller.

• Monitor tags of user -defined data type through the T ags window


Open the CCP153_1756R_DEM3.acd file. When demonstrating the listed procedures, point out the following Items:

S In the Controller-scoped tags collection, review the available arrays and tags of the User-defined data types. S Review ladder logic created with these tags.

Rev. February 2007


7--6




Exercise: Monitoring Arrays and Tags of User-Defined Data Types in an RSLogix 5000 Project

7 -- 7

Exercise: Monitoring Arrays and Tags of User-Defined Data Types in an RSLogix 5000 Project Exercise A

In this exercise, you will practice monitoring arrays and tags of user-defined data types.

Context: As a maintenance technician for your plant’s Logix5000 HVAC application, you must have a window into the process that allows you to monitor all data, including most arrays and application-specific data stored in tags of user-defined data types. For help performing steps in this exercise, see the associated job aid(s).

Directions: 1. Open the ADT_1756R_A1.acd project file. 2. Download the project to the controller in slot 1 and change the controller operating mode to Remote Run. 3. Open the controller -scoped tags collection and monitor the

Zone_Preset array through the RSLogix 5000 Tags window. 4. How are the 4 elements numbered? Zone_Preset[

]

Zone_Preset[

]

Zone_Preset[

]

Zone_Preset[

]

5. What is the data type of the 4 elements, Zone_ Preset?

6. Open the MainRou tine in the MainProgra m. 7. On rung 26, what is the tag address of the sour ce parameter for the MOV instruction?

Rev. February 2007

E 2007 Rockwell Automation, Inc. All rights reserved. ADTe56r

7--8


8. Check each of the followi ng facts that you have now observ ed about this simple array:

-

An array is a sequence of tags of the same data type.

-

Individual array elements can be addressed in executable code.

Individual array elements are numbered beginning with 0. Individual array elements can be monitored in the RSLogix 5000 Tags window.

9. Open the controller -scopedthe tagsRSLogix colle ction andTags monitor the OffDelayZone tag through 5000 window. 10. How many elements are in the array?

11. How are the elements numbered?

OffDelayZone[ ] OffDelayZone[ ] OffDelayZone[ ] OffDelayZone[ ] OffDelayZone[ ] 12. What is the data typ e for each element?

Tip "

Recall that a timer is a structure, or more complex data type, that is made up of multiple members, including BOOLs and DINTs . 13. Expand element 0 in the array and view its me mbers. 14. Expand elements 1 and 2 in the array and view their me mbers. 15. Are the members of each eleme nt the same (e.g., .PRE, .ACC, etc.)?

16. On rung 12, what is the tag address of the TO F instruction that resembles one of the elements from Step 11.?


Rev. February 2007 ADTe56r


7 -- 9

17. Display rung 15 and examine it. 18. The TOF instruction on the main rung is using which eleme nt of the array?

19. If an instructio n addresses a member of a single elem ent in the array, such as the .DN bit of OffDelayZone[3], what would the tag address in the ladder logic be?

20. If an instruction addres ses a different member of a single element in the array, such as the .ACC (DINT) membe r of OffDelayZone[3], what would the tag address in the ladder logic be?

21. Display rung 27 and examine the MOV instruc tion (source tag). Does the tag match your answer?

22. Check each of the follow ing facts that you have now obser ved about more complex arrays:

Tip "

-

An array is a sequence of tags of the same data type.

-

Individual array elements can be addressed in executable code.

-

Each array element can be expanded to view its separate members.

-

Members of individual elements can be addressed in executable code (e.g., Part[5].DN).

Individual array elements are numbered beginning with 0. Individual array elements can be monitored in the RSLogix 5000 Tags window.

You will now examine a tag of a user-defined data type. 23. In the User-Defined data types folder , open and examine the format for the Clock data type. 24. What are the individua l parts of the data type called (elem ents or members)?

Rev. February 2007


7--10


25. List the members and their data types:

26. Are all of these data type s the same?

27. Monitor the ElapsedT ime tag through the RSLogix 5000 Tags window.

Tip "

ElapsedTime is a controller-scoped tag. 28. What is the data type?

29. Expand the tag. 30. Are the members the same as the clock data type tha t you examined (see Step 25.)?

31. If an instruction addres ses the Minutes memb er of the ElapsedTime tag in the ladder logic, what would the tag be?

32. Monitor the CTU tag on rung 23. Does the tag ma tch your answer?

33. If an instruction addres ses the .DN bit of the Seconds member of the ElapsedTime tag, what would the tag in the ladder logic be?

34. Monitor the XIC ( --] [-- ) instruction and tag on rung 23. Does the tag match your answer?




7--11

35. Check each of the follow ing facts that you have now obser ved about user-defined data types:

How Did You Do?

Rev. February 2007

-

A user-defined data type is a group of tags of different data types.

-

Individual members can be monitored in the RSLogix 5000 Tags window.

-

Individual members can be addressed in executable code. Each tag can be expanded to view its separate members.



7--12


Answers

Exercise A 4. The elements are numbered beginn ing with 0:

Zone_Preset[0] Zone_Preset[1] Zone_Preset[2] Zone_Preset[3] 5. All tags in an array are of the same data type -- in this case, DINT. 7. The tag address of the source parame ter of the MOV instruction is Zone_Preset[2]. 8. As you observed in the exercise, all of the following fac ts about arrays are true:

n An array is a sequence of tags of the same data type. n Individual array elements are numbered beginning w ith 0. n Individual array elements can be monitored in the RSLogix 5000 Tags window. n Individual array elements can be addressed in executable code. 10. OffDelayZone is an arra y of 5 elements. 11. The elements are numbered beginn ing with 0:

OffDelayZone[0] OffDelayZone[1] OffDelayZone[2] OffDelayZone[3] OffDelayZone[4] 12. All tags in an array are of the same data type -- in this case, TIMER. 15. The members of each eleme nt are exactly the same (.PRE, .ACC, etc.) 16. The TOF instruction on rung 12 that resembles one of the elements from Step 11. is OffDelayZone[2]. 18. The element specified in the ladder logic is 3 (OffDelayZone[3]). 19. The tag specified in the ladder log ic would be OffDelayZone[3].DN. 20. The tag specified in the ladder log ic would be OffDelayZone[3].ACC. E 2007 Rockwell Automation, Inc. All rights reserved.



7--13

21. If you answered number 20. with OffDelayZone[3].ACC, then the source tag of the MOV instruction on rung 27 should match your answer. 22. As you observed in the exercise, all of the following fac ts about more complex arrays are true:

n An array is a sequence of tags of the same data type. n Individual array elements are numbered beginning w ith 0. n Individual array elements can be monitored in the RSLogix 5000 Tags window. n Individual array elements can be addressed in executable code. n Each array element can be e xpanded to view it s separate members. n Members of individual el ements can be addressed in executable code (e.g., Part[5].DN). 24. The individual part s of a data type are called member s. 25. The members and their data types are :

Seconds

TIMER

Minutes

COUNTER

Hours

COUNTER

26. No. A user-defined data type is a structure that groups member s of different data types. 28. The data type is clock. 30. Yes. The members Seconds, Minutes, and Hours are specified by the clock user-defined data type, which is a template or map for the data. 31. The tag would be ElapsedTime.Minutes. 32. If you answered number 31. with ElapsedTime.Minutes, then the CTU tag on rung 23 should match your answer . 33. The tag would be ElapsedTime.Seconds.DN. 34. If you answered number 33. with ElapsedTime.Seconds.DN, then the XIC ( --] [--) instruction and tag on rung 23 should match your answer. 35. As you observed in the exercise, all of the following fac ts about user-defined data types are true:

n A user-defined data type is a group of tags of different data types. n Individual members can be monitored in the RSLogix 5000 Tags window n Individual members can be addressed in executable code. n Each tag can be exp anded to view its s eparate members. Rev. February 2007


7--14




Lesson

8

Selecting Basic Ladder Logic Instructions for an RSLogix 5000 Routine What You Will Learn Explain that in this lesson, students will be inserting basic instructions into rungs

After completing this lesson, you should be able to select basic ladder logic instructions that meet the given project specificatio ns for RSLogix 5000 ladder logic routines.

of ladder logic.

Why These Skills Are Important Explain that results will be incorrect when the incorrect instructions or related parameters are entered into ladder logic routines.

Before You Begin Mention that the most commonly used bit instructions are OTE and XIC. Explain that all the instructions listed are bit instructions, except for TON, which is a Timer instruction.

Selecting the correct basic ladder logic instructions is an essential skill for creating the code that will evaluate inputs and control outputs in a control system.

Basic Instructions Instructions are commands that evaluate data or control data during the program scan. The following list contains basic categor ies of ladder logic instructions: • Conditional Bit Input Instructions • One Shot Instructions • Conditional Bit Output Instructions • Retentive Bit Output Instructions

If students ask about add-on instructions, mention that the topic is covered in detail as part of the RSLogix 5000 Level 3: Project Development course.

• Timer Instructions

Conditional Bit Input Instructions

A conditional bit input instruction changes its true/false state to reflect the value of the bit to which it corresponds. The following table outlines two bit input instructions and their functions:

Remind students that bit instructions examine the state of a bit/BOOL (1/on or 0/off).

If you want a bit input instruction that . . .

Clarify that true does not equal 1 and

Is true when the bit it is examining

falsebe does equal 0. An instruction can truenot if the bit status is 1 or 0 depending upon the input instruction used.

has a value of 1 (on) Is true when the bit it is examining has a value of 0 (off)

Then select . . . N am e

Mnemonic

Examine if Closed

S ym b ol

XIC

Examine If Open XIO

Highlight the fact that bit input instructions have brackets in their symbols. Rev. February 2007

E 2007 Rockwell Automation, Inc. All rights reserved. BITsb56r

8--2

Selecting Basic Ladder Logic Instructions for an RSLogix 5000 Routine

The state of the instruction has nothing to do with the physical device/button type. The instruction simply examines the tag value for a 1 or 0.

Conditional Bit Output Instruction

A conditional bit output instruction changes the value of the bit it corresponds to when the instruction changes state. The following table outlines the output energize bit instruction and its functions: Highlight the fact that the entire rung does not have to be true. Only the conditions leading up to (left of) the OTE need to be true to set the bit.

If you want a bit output instruction that . . .


Sets the bit it operates on to 1 when the instruction is true/enabled and resets the bit it operates on to 0 when the instruction is false or after a power cycle

M nemonic

Output Energize

Sy m bol

OTE

Example: Conditional Input and Output Instructions Remind students that rungs must always end with output instructions

The following rung of ladder logic contains an XIC and an OTE instruction:

XIC Checks the Tag for a value of 1

Tip "

OTE

If the Start_Conveyor tag contains a 1, then the Conveyor tag is set (1). The XIO instruction activates the OTE instruction if it finds the bit value is 0:

XIO Checks the Tag for a value of 0

Tip "


OTE

If the Switch tag contains a 0, then the Conveyor tag is set (1).

Rev. February 2007 BITsb56r


8 -- 3

One Shot Instruction

A one shot instruction is an input instruction that enables the rest of the rung: If you want a bit output instruction that . . .

Then select . . .

Enables the remainder of a ladder logic rung for only one program scan when its status changes from false to true (enabled)

Example: When an operator presses a pushbutton, that input will be closed for several program scans. To limit the activity to one program scan, even if the button is still pressed, use an ONS instruction.

Remind students that since an Tip ONS is an input instruction, its status only reflects the status of the bit and does not change it.

"

One Shot

ONS

Example: ONS Instruction

In the following graphic, the bit is activated for exactly one program scan:

A unique tag and bit must be dedicated to each ONS instruction. Retentive Bit Output Instructions

Like the conditional bit outputs, retentive bit output instructions change the value of the tags to which they correspond. Retentive bit output instructions also maintain the state of the output after it becomes true, even if the conditions change to false.

Rev. February 2007


8--4


The following table outlines the functions of the two retentive bit output instructions: Highlight the fact that the entire rung does not have to be true. Only the conditions leading up to (left of) the instruction need to be true. Example: A retentive bit output instruction might be used to latch a cooling pump so it restarts after a power failure.

If you want a bit output instruction that . . .


Sets or latches a data bit when the instruction goes true/is enabled, and keeps it set even if the instruction goes false/is disabled or a power cycle occurs

M nemonic

Sy m bol

Output Latch

OTL

Output Unlatch

OTU

Clears or unlatches the bit it operates on when the instruction goes true/is enabled, and keeps it cleared even if the instruction goes false/is disabled or a power cycle occurs

Example: OTL and OTU Instructions

OTL and OTU instructions are typically used in pairs:

OTL

OTU

Tip "

The OTL instruction will maintain its value even if power is removed.

Tip " Note that OTU instructions can be used by themselves in Fault r outines. However, in standard, non-fault routine code, OTU instructions should not be used to force a bit off (0). Such bits should be controlled by the state of the rung.

Tip "


Seal-in logic is often used instead of the OTL and OTU instructions for applications in which it is undesirable to have latched bits following a power loss. Timer Instructions

Timer instructions count in time units. Operations then can be controlled based on the status or value of the timer. All timer instructions act on tags of the timer data type.



8 -- 5

TON (Timer On Delay) Think of structure data types, such as the TON instruction, as being made up of several bit data types.

The TON instruction is a non-retentive timer that accumulates time when the instruction is enabled:

When it is activated, the TON instruction counts up to a preset value. It has the following parameters: The timer displayed in the example graphic counts up to 5 seconds.

• Preset: The value (in milliseconds) that the timer times up to. • Accum: The amount of time that the timer has accumulated.

If the TON timer is deactivated while timing, the Accum value automatically goes back to zero. • Timer Status Bits: .EN, .DN, and .TT are timer status bits. Their function is to tell the controller the status of the timer instruction:

Timer Instruction Status Bit

This example references the timer timing component of timer instruction Conveyor_Timer.

Rev. February 2007

.EN (enable)

Description Specifies whether or not a timer instruction is enabled. When .EN is 1 (set), the instruction is enabled. When .EN is 0 (cleared), the instruction is disabled.

.TT (timer timing)

Specifies whether or not the timer instruction is timing. When .TT is 1 (set), the instruction is timing. When .TT is 0 (cleared), the instruction is not timing.

.DN (done)

Specifies whether or not the accumulated value of the timer equals the preset value of the timer. When Accum = Preset, .DN is 1 (set). When Accum < Preset, .DN is 0 (cleared).

Timer status bits are referenced by entering the timer name followed by the status bit: Conveyor_Timer.TT


8--6


Work through the meaning of these two rungs with the students. Be sure to explain the “seal-in” logic used on the first rung.

Example: TON Instruction

The following rungs control the activation of an output for a set amount of time: Preset Time

Accumulated Time

Output Activated



Exercise: Selecting Basic Ladder Logic Instructions for an RSLogix 5000 Routine

8 -- 7

Exercise: Selecting Basic Ladder Logic Instructions for an RSLogix 5000 Routine Exercise A

In this exercise, you will practice selecting basic ladder logic instructions for an RSLogix 5000 routine. 1. An instruction is needed that will mainta in the true/set statu s of a machine’s indicator light after the light’s initial activation. Which instruction(s) could be used?

2. An instruction is needed to deactivate the indic ator light listed in the question above. Which instruction(s) could be used?

3. An instruction is needed that will work as a stop swi tch in a seal-in logic circuit. Which instruction( s) should be used?

4. Draw two rungs of lad der logic in which an input located on the

second rung examines the status of an output (Emergency_Light) on the first rung to see if it is set (1):

Tip "

Rev. February 2007

On the first rung, any user-specified input can be used to enable the Emergency_Light output. Also, the second rung can have any user-specified output.

E 2007 Rockwell Automation, Inc. All rights reserved. BITe56r

8--8


5. An instruction is needed to activate a proces s that will occur for one program scan when the instruction goes true. Which instruction should be used?

6. An instruction is needed that, once activa ted, will cause a process to take place for 3500 ms. Which instruction should be used?

7. Draw a rung of ladder logic tha t uses seal-in logic to activ ate a timer (Process_Time). The ladder logic should contain a start and stop button (normally-closed) and the timer should have a preset value of 4000 ms:

8. Draw ladder logic that conta ins two timers called Drill_ Timer (preset at 3000 ms) and Push_Timer (preset at 2000 ms). A pushbutton called Start will activate Drill_Timer. Once Drill_Timer is through timing, Push_Timer will be activated.

Tip "

How Did You Do?


Seal-in logic should be used.


Rev. February 2007 BITe56r


Rev. February 2007

8 -- 9


8--10


Answers

Exercise A 1. An OTL instruction will keep a bit set to one (or true, in this case) even if a condition goes false. This instruction will keep the machine’s indicator light on even after a power cycle occurs. 2. An OTU instruction is paired with an OTL instruc tion to deactivate, or unlatch, it. The indicator light can be turned off with an OTU instruction. 3. An XIC (examine if closed) ins truction should be selecte d if the button used is wired normally-closed. 4. The input instructi on in the second rung uses the same alia s as the output instruction in the first. Because the input instruction references the output point, it becomes true every time the output is set:

5. An ONS (one-shot) instruction will activa te a process that needs to occur for one program scan when the instruction goes true. 6. A timer instruction will exam ine and control operations base d on time. For the process to occur for 3500 ms, it must be set up to reference the Timer.TT component. 7. The following graphic show s seal-in logic activating a TON timer. The Process_Time.TT tag keeps the timer activated until it is through timing:

Normally-Closed Stop Button




8--11

8. The ladder logic shows two timer s activated by two seal-in logic circuits. In this example, the Drill_Timer instruction’s .DN component activates the Push_Timer instruction:

Rev. February 2007


8--12




Lesson

9

Entering Ladder Logic Components in an RSLogix 5000 Routine What You Will Learn Explain that in this lesson, students will be inserting basic instructions into rungs of ladder logic.

After completing this lesson, you should be able to enter ladder logic components in an RSLogix 5000 routine by performing the following tasks: • Enter and edit ladder logic components • Assign tags to instructions • Verify a project or a routine

Why These Skills Are Important These skills are important for the following reasons: Explain that results will be incorrect when the incorrect instructions or related parameters are entered into ladder logic routines.

• Entering instructions into RS Logix 5000 ladder logi c routines is important for creating and maintaining simple projects that evaluate inputs and control outputs. • Assigning the proper tags to instruct ions and verifying a projec t or a routine will assist in ensuring that the ladder logic project functions properly according to the identified specifications .

Before You Begin

Entering and Editing Ladder Logic Components

Point out that the two of the more common methods of entering ladder logic will be discussed here. A demonstration will be presented later in the Here’s How section. Other more advanced methods such as ASCII editing will not be reviewed in this course.

Tip "

Rev. February 2007

RSLogix 5000 software offers the ability to enter and edit ladder logic using any combination of the following basic methods: • Windowsr-based methods (dragging) • Insert key • Right-click menu

Other more advanced methods of entering ladder logic, such as ASCII editing and neutral text, are available.

E 2007 Rockwell Automation, Inc. All rights reserved. LADsb56r

9--2


To use the visual, point out the selected OTE instruction in the Favorites tab. Indicate that it has been dragged to rung 2. Point out the valid placement locations.

Windows-Based Methods (Dragging)

Ladder logic elements can be dragged from the RSLogix 5000 Language Element toolbar to a valid placement location (target): Selected Tab

Language Element Toolbar

Valid Placement Location

Remind students that the Language Elements toolbar can be moved, hidden, and customized. Note that there are procedures for the tasks in the procedures guide.

When dragging ladder logic elements from this toolbar, keep in mind the following tips: • Target squares indicate where an instruction can be placed. • A green target circle indic ates where a ladder logic elem ent will be inserted when the mouse button is released. • An empty or completed rung can be s elected and dragged to another valid placement location.

Mention that RSLogix 5000 software has a [CTRL] + drag feature that allows you to copy an entire rung to any valid location (whereas dragging will only move the rung). Note that many of these Windows-based features are available in the right-click menu of a selected item.

• The software supports other common Windows-based features including: -- Cut, copy, and paste -- Delete -- Undo and redo

Insert Key

Ladder logic can be entered using the [Insert] key on a keyboard.


Rev. February 2007 LADsb56r


9 -- 3

The placement of the ladder logic depends on the current editing mode, as indicated in the bottom right of the main window:

Current Editing Mode

The following modes are available: • APP (Append): A mode that places a new element to the right of the current instruction. • INS (Insert): A mode that places the new element to the left of the current instruction. Notethatthetreeisnavigatedinamanner similar to the Controller Organizer.

The three-letter mnemonic of the element can then be typed or selected from the correct folder of the component tree:

In the graphic, point out the main options, including the grouping option. Mnemonic Text Box

Selection Tree

Grouping Option

Assigning a Tag to an Instruction An operand is the tag upon which a ladder logic instruction will operate.

Rev. February 2007


9--4


Created tags can be entered as operands using the following methods: • Created tag names can be typed:

-- As each letter is type d, the software displays the clos est tag

In the graphic, point out the main options. If you are using the software, change the scope, then select a program tag.

match. • Created tags can be selected from a drop- down list in the operand text box:

Note that to have the next closest match displayed, the Look Ahead option must be enabled in the Application Options.

Tag Drop-Down List

Drag to Expand Column Width Tag Scope

Resize Option In the graphic, point out the main options. If you are using the software, expand different tags such as timers, and I/O tags. Show the available members.

A member of a structure or a bit can be selected when the structure is expanded:

Note that for an I/O point you would select a point from the grid in the Data member. Expanded Local:0:I.Data Bit Already Used in Project

If a tag is not already created, it can be created from the operand text box in an instruction: In the graphic, point out themain operand and the create option. Add that if a tag is created from the rightclick menu, spaces (underscores) cannot be entered. New Tag Right-Click Option




9 -- 5

Verifying Projects and Routines Mention that projects and routines cannot run until data is verified and errors are corrected.

Before running a project in RSLogix 5000 software, all ladder logic must be verified. Verification checks ladder logic routines for the following types of errors: • Improper instruction placement • Improper or incomplete tags • Tags with data types that are not valid for the inst ruction • Empty rungs

Projects with errors will not download to the controller.

Verification can be performed on single routines or on the whole project by using the following buttons: Verify Open Routine

Tip " Explain that this option is available

Verify Project

The auto rung verification option is available for users who want errors to be displayed in the Results window as rungs are entered.

through the Tools --> Options dialog box.

Here’s How

To enter ladder logic components in an RSLogix 5000 routine by performing the following tasks: • Enter and edit ladder logic components

Open the CCP146_1756r_DEM1.acd file. Create a new ladder logic routine to enter ladder logic. While demonstrating the procedures, point out the following elements:

S Language Element toolbar

• Assign tags to instructions • Verify a project or a routine


S Verification buttons

Rev. February 2007


9--6




Exercise: Entering Ladder Logic Components in an RSLogix 5000 Routine

9 -- 7

Exercise: Entering Ladder Logic Components in an RSLogix 5000 Routine Exercise A

In this exercise, you will practice entering ladder logic components in an RSLogix 5000 routine. For help performing steps in this exercise, see the associated job aid(s).

Directions: 1. Open the LAD_1756r_A1.acd project file. 2. Open the Conveyor routine.

Use the following ladder logic to perform Steps 3. through 5.:

3. Interpret the ladder logic to understan d its meaning. 4. Enter the instruction s and branches using the Windows -based dragging method. 5. Assign tags to the instructions by selec ting the tags from the tag database (Controller-scoped).

Tip "

Rev. February 2007

Be sure to define the Preset value for the timer.

E 2007 Rockwell Automation, Inc. All rights reserved. LADe56r

9--8


Use the following ladder logic to perform Steps 6. through 8.:

6. Interpret the ladder logic to understan d its meaning. 7. Enter the instruc tions and branches on rungs 1, and 2 using the Windows-based dragging method.

Tip "

You could also copy the Conveyor_Stop XIO combination on rung 0 and paste it on rung 2. 8. Assign tags to the instr uctions by selec ting the tags from the tag database (Controller-scoped).

"

Be sure to define the Preset value for the timer.

Tip

Use the following ladder logic to perform Steps 9. through 11. for the last section of ladder logic:

9. Interpret the ladder logic to understa nd its meeting. 10. Enter the instructions on rungs 3 an d 4 using the [Insert] key

method. 11. Assign tags to the instr uctions created in Steps 10.

Tip "

The Process tag does not exist. Create this tag after assigning it. 12. Verify the routine and correct any errors.


Rev. February 2007 LADe56r


9 -- 9

13. Download the project to the controller in slot 1 and then place the controller in the Run mode. 14. Open the Watch tab in the Output window to monitor the tags and ladder logic at the same time. 15. Enable the Conveyo r_Start tag by typing a one as the tag value in the Watch tab. 16. Describe what happens in the ladde r logic:

17. Enable the Conveyor_Stop tag by typin g a one as the tag value in the Watch tab. 18. Describe what happens in the ladde r logic:

How Did You Do?

Rev. February 2007


E 2007 Rockwell Automation, Inc. All rights reserved. LADe56r

9--10


Answers

Exercise A 16. If the ladder logic is enter ed correctly, the Conveyor_Start_Time timer will accumulate until it reaches 5000 ms (5 seconds). 18. If the ladder logic is entered correctl y, the system will reset. In other words, the TON instruction will reset because the accumulated (Accum) value will return to zero.


Rev. February 2007 LADe56r

Lesson

10

Modifying Timer and Counter Instructions in an RSLogix 5000 Project What You Will Learn

After completing this lesson, you should be able to modify timer and counter instructions.

Why These Skills Are Important Having the skills necessary to know and apply all of the components associated with timer and counter instructions will give you the ability to modify time-base d events and control counting applications more effectively.

Before You Begin

Timer and Counter Instruction Usage

Examples: A timer instruction can start a motor after a 10-second-delay, open a valve for 15 seconds, or keep track of how long a gear has been turning.

Timer instructions are used when any of the following actions need to occur: • After a timed dela y, trigger an outcome to take place • Cause an event to trans pire for a specif ied length of time • Time the duration of an event

Example: A counter can keep track of how many cars enter and leave a parking garage or how many times a gate rises or falls.

Tip "

Counters are used for the following applications: • Count the number of parts entering or leaving • Count how many times a certain incident occu rs

In a RSLogix 5000 project, timers and counters are used as output instructions.

TIMER Data Type Ensure students understand that the TIMER structure stores status bits and the preset and accumulated values for a timer instruction.

Rev. February 2007

Data associated with a timer instruction is stored in members of a TIMER structure. The members each have their own tag and hold preset, accumulated, and status bit data.

E 2007 Rockwell Automation, Inc. All rights reserved. MTCsb56r

10 -- 2


A TIMER structure within the Monitor Tags window of RSLogix 5000 software: Clarify that a TIMER structure tag name can be anything. The example structure is named “Cycle_Timer” for simplicity. Note that the preset and accumulated tags are DINT data types that can hold values greater than 1, while the .EN, .TT, and .DN are BOOL data types, which can be either 1 (on) or 0 (off).

Preset Tag Accumulated Tag Enable Tag Timer Timing Tag Done Tag

• Preset Value (.PRE) : The number of units or time base to be timed. The preset value has a range of 0 through +2,147,483,647. • Accumulated Value (.ACC) : The total time the timer has counted in millisecond units. • Timer Status Bits (.EN , .DN, and .TT): Function to tell the controller the status of the timer instruction: Timer Instruction Status Bit

Description

.EN (enable)

Specifies whether or not a timer instruction is enabled: • When .EN is 1 (set), the instruction is enabled. • When .EN is 0 (cleared), the instruction is disabled.

.TT (timer timing)

Specifies whether or not the timer instruction is timing: • When .TT is 1 (set), the instruction is timing. •

.DN (done)

When .TT is 0 (cleared), the instruction is not timing. Specifies whether or not the accumulated value of the timer equals the preset value of the timer: • The .DN bit changes state when accumulated = preset.

Add that instructions are detailed in the online Help menu and in the Documentation Reference Guide.

Timer Instruction Components

Remind students that a structure stores a group of data in parts or members that have their own tag and data type.

• Timer: The structure where information from the timer is stored.

If students are familiar with PLCr/SLCt systems, point out that in these sytems the time base is either 1 or .01 seconds, as opposed to the fixed .001 seconds in Logix5000 systems.


Timer instructions have the following components: • Time Base : The unit of time used by a timer to register events.

In Logix5000 t systems, the time base is always 1 millisecond (.001 seconds). For example, in a 2-second timer, enter 2000 for the preset value.

Rev. February 2007 MTCsb56r

10 -- 3


Reference the Documentation Reference Guide and identify some of the other information students can gain on timer instructions.

Timer Instructions Timer instructions control operations based on time: To...

Example: A TON instruction turns on a motor 10 seconds after start is enabled for safety reasons. Example: A TOF instruction keeps a fan running for one minute after stopping a motor. Note that an RTO is similar to a TON except after timing it retains the accumulated value until it is reset.

Time for a specific interval after timer is enabled Time for a specific interval after timer is disabled Accumulate time Reset a timer

Tip "

ForInstance...

Begin timing when the rung goes true and reset accumulated time when rung logic goes false Begin timing when the rung goes false and reset accumulated time when rung logic goes true Begin timing when the rung goes true and hold the accumulated time when rung logic goes false Reset a TON or RTO (do not use reset for a TOF)

Then use this instruction . . .

TON timer on delay TOF timer off delay RTO retentive timer on delay RES

For more information on timer instructions and their functionality, see the Documentation Reference Guide. TON (Timer On Delay) Instruction

Note that when the .EN and .DN bits are set (1), they are highlighted on the rung in the ladder logic routine. This is true with all types of timer and counter instructions.

A TON instruction is used for a timer that needs to accumulate time when it is true and reset when false:

• Notice in the previous graphic, when limit_switch_1 is enabled (set), light_2 is enabled (on) for 2000 milliseconds ( timer_1 is timing). • When accumulated time reaches 2000 milisec onds, light_2 is disabled (off) and light_3 is enabled (on). • Light_3 remains on until the TON instruction is disabled. • If limit_switch_1 is disabled (cleared) while timer_1 is timing,

light_2 is disabled (off).

Rev. February 2007


10 -- 4


A TON instruction works in the following manner: Work through the table showing how bits change as rung continuity changes. Clarify that the TON begins timing when the instruction transitions from false to true (the instruction is enabled). Point out that with all timer instructions, when accumulated time reaches and is equal to the preset, the timer is said to be timed out.

And the status bits are in the following states . . .

If the accumulated value is . . .

.EN

.TT

0

Then the timer is . . .

.DN

=0

0

1

1

0 0

Rese(tFalse) Timing(True)

=PRE

1

0

1

Timedou(tTrue)

TOF (Timer Off Delay) Instruction

Mention that an overhead projector has a timed off element. When the light bulb is turned off, a cooling fan continues to run for a specified amount of time, which is representative of a TOF.

A TOF instruction is used for a timer that needs to time when it is false and reset when true:

Mention to students that if the preset value was increased it could better represent an overhead projector. For example, when the light bulb is disabled (turned off) a cooling fan continues to run for a specified length of time (i.e., 10 seconds).

• Notice in the previous graphic, when limit_switch_2 is enabled and then disabled (cleare d), light_2 and light_3 are enabled (on) for 2000 milliseconds ( timer_2 is timing and the done (.DN) bit is enabled). • When timer_2.ACC reaches 2000, light_2 and light_3 are disabled (turn off).

A TOF instruction works in the following manner:

Work through the table showing how bits change as rung continuity changes. Clarify that the TOF begins timing when the rung-condition-in transitions from true to false (the instruction is disabled).



If the accumulated value s...

.EN

.TT

0


.DN

=0

1

0

1

1 1

Rese(tFalse) Timing(True)

=PRE

0

0

0

Timedou(tTrue)



10 -- 5

RTO (Retentive Timer On Delay) Instruction

? What is a retentive instruction? Answer: An instruction that retains data until it is reset, even after a power failure.

An RTO instruction is a timer that accumulates time when it is true and does not reset when it goes false; it has the ability to start and stop without resetting (losing) its accumulated value:

• Notice in the previous graphic, when limit_switch_1 is enabled (set), light_1 is enabled (on) for 2500 milliseconds ( timer_3 is timing). • When timer_3.ACC reaches 2500, light_1 is disabled (off) and light_2 is enabled (on). • Light_2 remains enabled (on) until timer_3 is reset. • When limit_switch_2 is enabled (set), the RES instruction resets timer_3 (clears status bits and accumulated value). • If limit_switch_2 is disabled (cleared) while timer_3 is timing, light_1 remains enabled (on).

Tip "

An RES (reset) instruction is needed to reset the RTO instruction’s accumulated value and bits. An RTO instruction works in the following manner:

Work through the table showing how bits change as rung continuity changes. Example: An RTO instruction can be used to signal when maintenance of a system or part is required after a predetermined amount of time.

Rev. February 2007


If the accumulated value is . . .

.EN

.TT

0


.DN

=0

0

1

1

0 0

Rese(tFalse)

=PRE

1

0

1

Timedou(tTrue)

=PRE

0

0

1

Timedou(tFalse)

Timing(True)


10 -- 6


COUNTER Data Type Emphasize and ensure students understand that the COUNTER structure stores status bits and the preset and accumulated values for a counter instruction.

Data associated with a counter instruction is stored in members of a COUNTER structure. The members each have their own tag and hold preset, accumulated , and status bit data. A COUNTER structure within the Monitor Tags window of RSLogix 5000 software:

Clarify that like any structure, a COUNTER structure tag name can be whatever itthe determines. example, is user “Parts_Counter .” In this

Preset Tag Accumulated Tag Count Up Tag Count Down Tag Done Tag Overflow Tag Underflow Tag

• Preset Value (.PRE) : The value to be counted. The maximum value for counting up is +2,147,483,647. The maximum value for counting down is --2,147,483,648. • Accumulated Value (.ACC) : The number of elapsed counts. If accumulated = 50 that means 50 events have occurred. • Counter Status Bits (.CU , .CD , .DN, .OV, and .UN): Function

to tell the controller the status of the counter instruction:

Clarify that both of the counter instructions count when they are enabled. Compare this against the timer instructions, in which the TON times when enabled and the TOF times when disabled.

Clarify that the .DN counter bit performs the exact same function as the .DN timer bit.

Counter Status Bit

Description

.CU

Specifies whether or not a counter instruction that is designed to count up is enabled: • When .CU is 1 (set), the count up instruction is enabled. • When .CU is 0 (cleared), it is disabled.

.CD

Specifies whether or not a counter instruction that is designed to count down is enabled: • When .CD is 1 (set), the count down instruction is enabled. • When .CD is 0 (cleared), it is disabled.

.DN

Specifies whether or not the accumulated value is greater than or equal to the preset value: • When accumulated≥ preset, .DN is 1 (set). • When accumulated < preset, .DN is 0 (cleared).

.OV

.UN


Specifies whether or not the counter instruction has counted above the upper limit of +2,147,483,647 (overflow): • When .OV is 1 (set), the upper limit has been exceeded. • When .OV is 0 (cleared), it has not been exceeded. Specifies whether or not the counter instruction has counted below the lower limit of --2,147,483,648 (underflow): • When .UN is 1 (set), the lower limit has been exceeded. • When .UN is 0 (cleared), it has not been exceeded.


10 -- 7


With counter instructions , the accumulated value continues incrementing/decrementing even after the .DN bit is set (i.e., the accumulated value can be greater than the preset value).

Tip "

To clear the accumulated value of counters, use an RES (reset) instruction that references the counter tag. Counter Instruction Component

Tell students that a counter can keep track of how many bottles are filled on a conveyor line by counting up and down from the same total.

The COUNTER data type is a block of data that can be used to count up, count down, and add or subtract from one total count.

Reference the Documentation Reference Guide and identify some of the other information students can gain on counter instructions.

Counter Instructions

The Counter structure is where information from the counter is stored.

Counter instructi ons control operations based on the number of events:

Reinforce that counter instructions deal with number of events, while timer instructions deal with time.

ForInstance...

Then use this instruction . . .

Count up

Increase a count when an event occurs

CTU count up counter

Count down

Decrease a count when an event occurs

CTD count down counter

To...

Count up and count down Resetacounter

Tip "

Add and subtract from one total count as necessary ResetaCTUorCTD

CTU and CTD combined with same tag RES

For more information on counter instructions and their functionality , see the Documentation Reference Guide. CTU (Count Up) Instruction

A CTU instruction is used to count up by one every time the rung is true and the instruction is enabled:

Rev. February 2007


10 -- 8


• Notice, in the pr evious graphic, after Limit_Switch_1 goes from disabled to enabled 10 times, the .DN bit is enabled (set) and Red_Light_1 is enabled (on). • If Limit_Switch_1 continues to go from disabled to enabled, Switch_1_Count continues to increment its count and the .DN bit remains enabled (set). • When Limit_Switch_2 is enabled, the RES instruction resets Switch_1_Count (clears the status bits and the accumulated value) and Red_Light_1 is disabled (off).

CTD (Count Down) Instruction Example: A CTD instruction can be used to keep track of available empty bottles for a bottling machine. The instruction would count down as each empty bottle was used.

A CTD instruction is used to count down by one every time the rung is true and the instruction is enabled. It is usually used in conjunction with a CTU, but can be used separately:

The CTU and CTD add or subtract from the same total count.

• In the previous graphi c, the rungs of ladder logic repre sent a conveyor bringing parts into a buffer zone. • Each time a part enters, limit_switch_1 is enabled and part_count increments by 1. • Each time a part leaves, limit_switch_2 is enabled and part_count decrements by 1. • If there are 100 parts in the buff er zone ( part_count.DN is set), conveyor_A is enabled (on) and stops the conveyor from bringing in any more parts until the buffer has room.

RES (Reset) Instruction

An RES instruction is an output instruction used to reset timer and counter instruction s. An RES instruction will typically referenc e either a TON, RTO, CTU, or CTD instruction by its tag.




10 -- 9

When an RES instruction is true, the accumulated value and the bits of either a timer or counter instruction of the referenced tag data type are cleared to 0 (reset). The following graphic shows an example of an RES instruction referencing a counter instructio n:

Never use an RES instruction to reset a TOF instruction because the RES clears the status bits as well as the accumulated value.

Here’s How To demonstrate: 1. Go online to the controller with MTC_1756R_DEM1.acd file.

To modify timer and counter instructions. As your instructor demonstrates these procedures using the following examples, follow along in the associated job aids(s).

2. Review the TON, TOF, and RTO instructions. Emphasize the highlighting of the .EN and .DN bits when enabled. 3. Go online to the controller with MTC_1756R_DEM2.acd file. 4. Review the CTU and CTD instructions, as well as the RES instruction. Emphasize the highlighting of the .EN and .DN bits when enabled. If you need an example of the exercise answer, use the file named MTC_1756R_DEM3.acd.

Rev. February 2007


10 -- 10


Example In the demonstration, show how the timer resets when the rung goes false. Expand the tag TON_Demo in the Monitor Tags window during the demonstration so the students can see the correlation between the tags and the ladder logic. Point out that while the timer is enabled and timing, the two yellow pushbuttons Yellow_Light_DO1 and Yellow_Light_DO4 are illuminated.

TON Instruction The following graphic shows an example of a TON instruction. In this example, note the following conditions : • Red_Light_DO2 will become enabled (turn on) five seconds after Pushbutton_DI1 becomes enabled. • When Pushbutton_DI1 becomes true (enabled), the TON instruction will be enabled and start timing. It continues timing until the accumulated value reaches the preset value of 5 seconds (5000 ms). The branch using the TON_Demo.TT bit is used to

seal-in around the momentary pushbutton to keep the rung true. • If rung 0 becomes fals e (0/open) after the tim er starts timing, the timer will stop timing, reset, and the accumulated value will return to 0. • When accumulated = preset, the instr uction is timed out and the .DN bit is enabled. • TON_Demo.DN references the .DN bit and becomes true when the .DN bit is enabled.




Example

10--11

TOF Instruction The following graphic shows an example of a TOF instruction. In this example, note the following conditions :

Display the TOF_Routine in the Timers_Program. Demonstrate how the instruction resets as soon as the rung goes true (the opposite of TON). When online, point out that .EN and .DN bits are enabled simultaneously when the switch is enabled. When the switch is disabled, .TT and .DN are enabled simultaneously, for the specified length of the off delay.

• When Switch_ DI14 becomes enabled (false to true) Red_Light_DO11 will become enabled (on). • When Switch_ DI14 becomes false (0/open), the TOF instruction will be enabled and start timing. It continues timing until the accumulated value reaches the preset value of 7 seconds (7000 ms). • Red_Light_DO11 will become disabled (turn off) seven seconds after Switch_DI14 becomes disabled (true-to-false). • If Switch_ DI14 becomes true (1/closed) after the timer starts timing, the timer will stop timing, will reset the .TT bit to 0 and the .DN bit to 1, and the accumulated value will return to 0. • When accumulated = preset, the inst ruction is timed out and the .DN bit is disabled. • TOF_Demo.DN references the .DN bit and becomes false when the .DN bit is disabled.

Rev. February 2007


10 -- 12


Example Display the RTO_Routine. Demonstrate how when Switch_15 is disabled while timing and when the instruction times out, the RTO retains the accumulated value. Expand the tag RTO_Demo in the Monitor Tags window during the demonstration so students can see the correlation between the tags and the ladder logic.


RTO and RES Instructions The following graphic shows an example of an RTO and an RES instruction. In this example, note the following conditions : • Red_Light_DO5 will become enabled (turn on) six seconds after Switch_15 and Pushbutton_DI2 become enabled. • The RTO instruction functions the same as the TON instruction except that if Switch_15 is disabled (0/open) after the timer starts timing, the timer will stop timing but will not reset. The accumulated will retain its value. • The RTO instruction’s accumulated value and bits are not cleared until Pushbutton_DI0 is enabled and the RES instruction resets RTO_Demo.



Example

10 -- 13

CTU Instruction

Display the CTU_Routine in the Counters_Program.

The following graphic shows an example of a CTU instruction. In this example, note the following conditions :

Expand the CTU_Demo tag in the Monitor Tags window during the demonstration so the students can see the correlation between the tags and the ladder logic.

• When Count_Up_Pushbutton_DI4 is enabled (1/closed), the CTU instruction will count up by one. This pushbutton must go false-to-true three times for accumulated to = preset.

Point out the importance of using an RES instruction on a CTU instruction, or the willremain continue counting and the counter .DN bit will set.

Rev. February 2007

• When accumulated = preset, the .D N bit is enabled and Red_light_DO8 becomes enabled (true). • Once the .DN bit is set, it stay s set until the counter is rese t. • If Count_Up_Pushbutton_DI4 is enabled, the accumulated value will continue to increase past three until the counter is reset.


10 -- 14


Example

CTD Instruction

Display the CTD_Routine in the Counters_Program.

The following graphic shows an example of a CTD instruction. In this example, note the following conditions :

Point out that accumulated must be less than/go beyond --4 for the .DN bit to be cleared.

• The .DN bit is set before the ins truction is enable d because accumulated ≥ preset.

Mention that the CTD instruction is typically used with a CTU instruction that references the same counter tag value.

• When Pushbutton_DI0 is enabled (1/closed ), the CTD instruction will count down by one. Pushbutton_DI0 must go false-to-true four times for accumulated to = preset and five times for accumulated < preset and disable the .DN bit.

Point out the importance using an or RES instruction on a CTDofinstruction, the counter will continue counting and the .DN bit will remain disabled.

• When accumulated < preset, the .DN bit is dis abled and Green_light_DO9 becomes disabled (false).




Example Explain that the reset button must be enabled to reset the counters. Also, explain that the counters can be reset at any time, for instance, before or after accumulated is equal to, less than, or more than the preset value.

Rev. February 2007

10 -- 15

RES Instruction The following example shows a programmed RES instruction referencing the CTU and CTD counter instructio ns. In this example, note that when Reset_Counter_1_DI6 transitions from false-to-true, counters CTU and CTD are reset:


10 -- 16




Exercise: Modifying Timer and Counter Instructions in an RSLogix 5000 Project

10 -- 17

Exercise: Modifying Timer and Counter Instructions in an RSLogix 5000 Project Exercise A

In this exercise, you will practice modifying the appropriate timer and counter instructions to meet given functional specifications.

Context: You are responsible for portions of the Logix5000 ladder logic projects in the steel mill process. Your supervisor has assigned you the task of troubleshooting the Logix5000 Conveyor System program. Your supervisor has informed you of the following key points concerning this program: • A pushbutton on the works tation will indicate fe edback that coke is being loaded or not loaded. • It takes 8 seconds for the oper ator to load the coke on to each conveyor system. • A ladder logic instr uction will keep trac k of the time and retain the time until it is reset, even if the loading process is interrupted. • A pushbutton on the workst ation will reset the conve yor count

once every 24 hour period. • Once the conveyor system has bee n enabled by an operator for five cycles it should trigger an automatic preven tive maintenance alarm. For help performing steps in this exercise, see the associated job aid(s).

Directions: 1. Open the MTC_1756r_A1.acd project file. 2. Determine the tag name, base tag, and the workstation device for the digital inputs used in the program North_Conveyor: Workstation Device

Rev. February 2007

Tag Name

Base Tag (input)

E 2007 Rockwell Automation, Inc. All rights reserved. MTCe56r

10 -- 18


3. Determine the tag name, base tag and the workstation device for the digital outputs used in the program North_Conveyor: Workstation Device

Tag Name

Base Tag (output)

4. Determine the tag name, base tag and the workstation device for the digital inputs used in the program South_Conveyor: Workstation Device

Tag Name

Base Tag (input)

5. Determine the tag name, base tag and the workstation device for the digital outputs used in the program South_Conveyor: Workstation Device

Tag Name

Base Tag (output)

6. In the North Conveyor progr am, what is the prese t value of the

counter on rung 1? 7. How many times w ill the operator need to enable the coun ter in the North Conveyor program before the North_Conveyor output will be enabled?

8. In the North Conveyor progr am, modify the prese t value of the counter on rung 1 so that each time the operator enables the rung the North_Conveyor output will be enabled. 9. In the North Conveyor progr am, what did you change the prese t value of the counter on rung 1 to?

10. In the South Conveyor progra m, what is the preset value of the counter on rung 1?


Rev. February 2007 MTCe56r


10 -- 19

11. In the South Conveyor progra m, modify the preset valu e of the counter on rung 1 so that each time the operator enables the rung the South_Conveyor output will be enabled. 12. In the South Conveyor progra m, what did you change the preset value of the counter on rung 1 to?

13. Download the project to the controller in slot 1 and go online. 14. In the North Conveyor progr am, what condition or condit ions

cause rung 3 to be true?

15. In the North Conveyor prog ram, what happen s when rung 3 is true?

16. In the North Conveyor prog ram, what type of timer is used ?

17. In the South Conveyor progra m, what type of timer is used?

18. What type of timer is used to retain the acc umulated value if ther e is a power loss or the rung is disabled for some reason?

19. Go offline and modify the timer , if needed, in both programs, to the type that will retain its accumulated value if there is a power loss, etc. 20. In what program did you modify the timer type and wha t type did you change it to?

21. In the North and South Conveyor prog rams, modify the preset value for the timers to time for 8 seconds. 22. In the North Conveyor prog ram, what will caus e rung 3 to become false, and what will happen when it becomes false?

23. In the North Conveyor prog ram, which bit will enable the cou nter on rung 5?

Rev. February 2007


10 -- 20


24. In the North Conveyor progr am, modify the prese t value of the counter on rung 5 to the correct value.

Tip "

Use the project documentation (the rung comments) to determine what should occur on the rung. 25. In the South Conveyor progra m, modify the preset value of the counter on rung 5 to the correct value. 26. Download the project and verify that both program s contain an RTO timer. 27. Start the project and verif y the following inputs and outputs in the North_Conveyor program on the workstation and in the project: A. Enable the pushbutto n input DI1 and verify that the counter counts up and the North_Conveyor output (DO0) is enabled. B. Enable the pushbutto n input DI2 for 8 seconds while the RTO timer times which simulates coke loading onto the conveyor. C. Verify that the North_Coke_Loading_Timer.DN bit is enabled after 8 seconds and that the preventive maintenance counter incremen ts by 1. 28. Verify the following inputs and outputs in the South_Conveyor program on the workstation and in the project: A. Enable the pushbutto n input DI8 and verify that the counter counts up and the South_Conveyor output (DO5) is enabled. B. Enable the pushbutto n input DI10 for 8 seconds while the RTO timer times which indicates that coke loading onto the conveyor. 29. In the North Conveyor progr am, what is the purpose of rung 0?

30. In the North Conveyor progr am,what is the purpos e of rung 1?

31. In the South Conveyor program ,what is the purpose of rung 4?

32. In the North Conveyor program, descr ibe what will happen when the inputs and outputs on rung 5 are enabled?

33. Go offline. E 2007 Rockwell Automation, Inc. All rights reserved.



10 -- 21

34. Save the project.

How Did You Do?

Rev. February 2007



10 -- 22


Answers

Exercise A 2. The following table lis ts the the tag name, base tag and the workstation device for the digital inputs used in the program North_Conveyor: Workstation Device

Tag Name

Base Tag (input)

DI0

North_PushButton_Reset_Counter

Local:2:I.Data.0

DI1

North_Start_PushButton

Local:2:I.Data.1

DI2

North_Coke_Loading_PushButton

Local:2:I.Data.2

DI3 DI4

North_PushButton_Reset_Timer North_Stop_PushButton

Local:2:I.Data.3 Local:2:I.Data.4

DI5

North_PushButton_Reset_PM_Counter

Local:2:I.Data.5

3. The following table lis ts the the tag name, base tag and the workstation device for the digital outputs used in the program North_Conveyor: Workstation Device

Tag Name

Base Tag (output)

DO0

North_Conveyor

Local:0:O.Data.0

DO1

North_PM_Alarm

Local:0:O.Data.1

4. The following table lis ts the the tag name, base tag and the workstation device for the digital inputs used in the program South_Conveyor: Workstation Device

Tag Name

Base Tag (input)

DI6

South_Stop_PushButton

DI7

South_PushButton_Reset_Counter

Local:2:I.Data.6 Local:2:I.Data.7

DI8

South_Start_PushButton

Local:2:I.Data.8

DI9

South_PushButton_Reset_Timer

Local:2:I.Data.9

DI10

South_Coke_Loading_PushButton

Local:2:I.Data.10

DI11

South_PushButton_Reset_PM_Counter

Local:2:I.Data.11

5. The following table lis ts the the tag name, base tag and the workstation device for the digital outputs used in the program South_Conveyor: Workstation Device

Tag Name

Base Tag (output)

DO5

South_Conveyor

Local:0:O.Data.5

DO6

South_PM_Alarm

Local:0:O.Data.6

6. The preset value is 10.




10 -- 23

7. The operator will have to enable the counter by pressi ng the North_Start_Pushbutton (DI1) on the workstation 10 times before the done bit (.DN) will enable the North_Conveyor output (DO0). 9. The preset value could have be en changed to 0 or 1. 10. The preset value is 8. 12. The preset value could have be en changed to 0 or 1. 14. Rung 1 must be enabled in order for the North_C onveyor output (DO0) to enable rung 3. Also, the North_Coke_Loading_PushButton must be enabled. These 2 conditions will then cause the North_Coke_Loadin g_Timer to be enabled. 15. The North_Coke_Loading_Timer will time. 16. The North Conveyor program contains an RTO timer. 17. The South Conveyor programs contains a TON timer. 18. An RTO timer is the type of timer used if the accumulated value needs to be retained if an interruption occurs during the timing process. 20. In the South_Convey or program. It should have bee n changed to an RTO timer. 22. If the North_Sto p_PushButton (DI4) is enabled, the North_Conveyor output (DO0) will become disabled . Also, if the North_Coke_Loa ding PushButton is disabled the rung becomes false and the timer stops timing. 23. The North_Coke_Loading_Timer.DN bit. 29. This rung contains the RES ins truction for the counter on rung 1. 30. This rung will enable the Nor th_Conveyor output (D O0) and count how many times the rung transitions from false to true. 31. This rung contains the RES ins truction for the counter on rung 5. 32. Each time the North_Coke_Loading_Timer.DN bit is enabled the North_Conveyor_ PM_Counter will count. Once the counter has reached the preset value (5) the North_Conveyor_PM_Counter.DN bit will enable the North_PM_Alarm output (DO1).

Rev. February 2007


10 -- 24




Lesson

11

Modifying Program Control Instructions in an RSLogix 5000 Project What You Will Learn

After completing this lesson, you should be able to modify program control instructions.

Why These Skills Are Important Knowing when and how to change the flow of logic will help you more effectively and efficiently modify ladder logic according to your project.

Before You Begin

Program Control Instructions

Mention that in RSLogix 5000 software the Help drop-down menu could be used as an online user manual. Tell students they will be able to find a substantial amount of information on ladder logic instructions, among other useful information.

Program control instructions are used to change the flow of logic. The following table outlines the use of program control instructio ns: Use this instruction . . .

If you want to . . .

N am e

Jump over a section of logic that does JumptoLabel not always need to be executed or repeat a section of logic until certain Label conditions are met Disable all the rungs in a section of Master Control Reset logic

Rev. February 2007

JSR SBR RET JMP LBL MCR

Disable user tasks

User Interrupt Disable

UID

Enable user tasks

User Interrupt Enable

UIE

Mark a temporary end that halts routine execution

Tip "

Mnemonic

Jum to a se arate routine,, ass data Jump to Subroutine to the routine,, execute the routine,,Subroutine and return results Return from Subroutine

TemporaryEnd

TND

Disable a rung

Always False Instruction

AFI

Insert a placeholder in the ladder logic

No Operation

NOP

For more information on program control instructions and their functionality, see the Documentation Reference Guide.

E 2007 Rockwell Automation, Inc. All rights reserved. MPCsb56r

11--2

Modifying Program Control Instructions in an RSLogix 5000 Project

Subroutine Usage Tell students another r eason for using subroutines is to break up the logic of large or complex programming tasks into multiple routines or s ubroutines.

The following tasks are examples of what could be programmed in subroutines: • Loading a specific recipe when needed • Performing a calculation at spe cified intervals

Tell students these tasks are also examples of parameters that may be passed from the JSR to the SBR.

• Cleaning a vat after a specified number of cycles • Packing and sealing a carton • Painting a part a specific color • Initializing a system • Measuring a part at a speci fic point

If students ask, mention that Tip " add-on instructions became available in version 16. Also, mention that add-on instructions are covered in more detail as part of the RSLogix 5000 Level 3: Project Development standard course.

As a possible alternative to subroutines, users can create add-on instructions that combine commonlyused logic into a single, user-defined instruction. Add-on instructions can be reused throughout a project or as part of multiple projects. JSR (Jump to Subroutine) Instruction

When enabled, the JSR instruction jumps to a separate routine. The JSR instruction initiates the execution of the specified routine, which is referred to as a subroutine: • The subroutine executes one time. • After the subroutine executes, logic executio n returns to the srcinal routine.

The JSR instruction is an output instruction:

Output Instruction

SBR (Subroutine) Instruction Tell students that if you use an SBR instruction, it must be the first instruction on the first rung of the subroutine. Also, you cannot place an SBR instruction in a main routine. An example of parameters that may be passed is one that specifies oil flow rate through an oil lance to either increase or decrease production in a blast furnace.

An SBR instruction is used to receive passed parameters from a JSR instruction. The parameter values are then copied into specified tags in the subroutine where the SBR instruction is located. RSLogix 5000 software does not require an SBR instruction unless input parameters are passed from a JSR instruction.

The SBR instruction identifies the tags that store the incoming parameters. E 2007 Rockwell Automation, Inc. All rights reserved.

Rev. February 2007 MPCsb56r


Tip "

11--3

For others to better identify the routine as a subroutine, you can program an optional SBR instruction without input parameters. The SBR instruction (used in this example only as an identifier) is an input instruction:

Input Instruction

RET (Return from Subroutine) Instruction Specify that if the RET instruction is not enabled the controller continues executing the current subroutine and does not affect logic execution.

An example of when parameters might be returned is at a waste water plant with numerous pipes. For instance, the rate of flow in most or all of the pipes is changed by various valves. You want to verify the valves are working correctly, so that you can monitor the flow rate. For instance, the rate of flow for the various pumps this subroutine checks could be passed back to the calling routine.

An RET is an instruction within a subroutine that returns parameters to a JSR instruction. When enabled, an RET instruction passes its parameters to the specified return tags in the JSR, if any, and resumes execution at the rung following the associated JSR instruction. RSLogix 5000 software does not require an RET instruction unless return parameters are to be passed back to the JSR instruction.

An RET instruction is used only when returning parameters to the JSR instruction or when terminating the subroutine before the “end” is reached. An RET instruction ends the subroutine, and if needed, returns parameters to the JSR instruction. An RET instruction is an output instruction:

Output Instruction

Tip " Mention that as with nesting branches, nesting subroutines allows the placement of one occurrence inside another.

Rev. February 2007

A subroutine can have more than one RET instruction. Nesting subroutines allows access to one subroutine from inside another subroutine . There are no restrictions, except controller memory, on the number of nested subroutine s permitted or the number of parameters passed or returned.


11--4


The following graphic shows the concept of nesting subroutines: Level 1 Level 2 Level 3 Subroutine action_1 Subroutine action_2 Subroutine action_3 Main Routine action_1

JSR

Point out that the JMP and LBL instructions do not create additional routines and that they will increase the length of the main ladder logic by keeping sections of rungs inside the main ladder routine, rather than throughout different routines.

SBR

SBR action_2

SBR action_3

JSR

JSR

RET

RET

RET

JMP (Jump to Label) and LBL (Label) Instructions

When enabled, the JMP instruction skips to the referenced LBL instruction and the controller continues executing from that instruction. When disabled, the JMP instruction does not affect ladder logic execution. The JMP instruction can use the same JMP tag in more than one location in the ladder logic.

The JMP instruction is an output instruction:

Output Instruction

Tell students that it is possible to make multiple jumps that can point to the same label. For instance, your ladder logic can jump to a label from various points in the logic.

An LBL instruction is the target of the JMP instruction that uses the same reference. Each label name must be unique within a routine. The LBL instruction is an input instruction:

Input Instruction




11--5

Jumped logic is not scanned. Place critical logic outside the jumped zone.

MCR (Master Control Reset) Instruction Remind students that the OTE, TON, and TOF instructions are non-retentive instructions.

MCR instruction s, used in pairs, create a program zone that disables all non-retentive instruct ions rungs between the MCR pair: • When an MCR zone is e nabled, the rungs in the MCR zone ar e scanned for normal true or false conditions . • When disabled, the controller stil l scans rungs withi n an MCR zone, but scan time is reduced because non-retentive outputs in the zone are disabled. • The rung-condition-in is false for all the instr uctions inside of the disabled MCR zone.

An MCR instruction is an output instruction: Output Instruction

Output Instruction

Inform students that if an MCR zone continues to the end of the routine, it is not necessary to program an MCR instruction to end the zone. However, a good programming practice would be to accomplish this task. For instance, an MCR instruction would prevent ladder logic added to the bottom of the routine from being inadvertently placed inside the MCR zone.

Rev. February 2007

MCR Instruction Usage

When you program an MCR zone, note the following information: • End the zone with an unc onditional MCR in struction. • Do not nest one MCR z one within anoth er. • Do not jump into an MCR zon e. If the zone is fa lse, jumping into the zone activates the zone from that point to the end of the zone.


11--6


Do not overlap or nest MCR zones. Each MCR zone must be separate and complete. If they overlap or nest, unpredictable machine operation could occur with possible damage to equipment or injury to personnel. Place critical operatio ns outside the MCR zone. If instructions such as timers start in an MCR zone, instruction execution stops when the zone is disabled and the timer is cleared.

UID (User Interrupt Disable) and UIE (User Interrupt Enable) Instructions

An UID instruction and UIE instruction work together to prevent a small number of critical rungs from being interrupted by other tasks: • An UID instructio n prevents high-prior ity tasks from interrupti ng the current task but does not disable execution of a fault routine or the Controller Fault Handler. • An UIE instruction enables other tas ks to interrupt the curre nt task.

UID and UIE instructions are output instructions: Output Instruction

Output Instruction




11--7

UID and UIE Usage

The following list outlines how to prevent a series of rungs from being interrupted: • Limiting the number of rungs that you do not want interrupted

-- Disabling user interrupt s for a prolonged period of time can produce communication loss • Entering a rung and a U ID instruction above the firs t rung not to be interrupted • Entering a rung an d a UIE instruction after the las t rung in the

series not to be interrupted • Nesting pairs of UID/UIE instructions, if required TND (Temporary End) Instruction Tell students a TND instruction is a good tool to use if they need to debug or troubleshoot ladder logic.

A TND instruction acts as a boundary to the controller program scan. When a controller scans a TND instruction, the controller moves to the end of the current routine. A TND instruction acts as the end of the routine. When enabled, a TND instruction lets the controller execute ladder logic only up to a TND instruction: • If a TND instruction is in a subroutine, the program sc an returns to the calling routine. • If a TND instruction is in a main routine, the program sca n returns to the next program within the current task.

A TND instruction is an output instruction:

Output Instruction

Tip "

Use the TND instruction when debugging or troubleshooting to execute ladder logic up to that instruction. For example, progressively moving the TND instruction after debugging each section could make start-up time easier. AFI (Always False Instruction)

Point out that an AFI instruction is typically used to temporarily disable a rung while debugging a program.

Rev. February 2007

When enabled, an AFI instruction disables all the instructions on the rung. It sets its rung-condition-out to false and is typically used for debugging or troubleshooting logic.


11--8


An AFI instruction is an input instruction:

Input Instruction

NOP (No Operation Instruction) Mention that the NOP instruction can be used to bypass instructions to enable the output. For example, an NOP instruction, when placed on a branch, will bypass instructions and enable the output.

Here’s How

An NOP instruction functions as a placeholder anywhere on a rung. When enabled or disabled the NOP instruction performs no operation. An NOP instruction is useful for bypassing instructions to enable the output:

To modify program control instructions.

To demonstrate: 1. Go online to the controller with MPC_1756R_DEM1.acd file. 2. Review the JSR, SBR, RET, JMP, LBL, MCR, UID, UIE,TND, AFI and NOP instructions.

As your instructor demonstrates these procedures using the following examples, follow along in the associated job aids(s).

If you need an example of the exercise answer, use the file named MPC_1756R_DEM2.acd.

Example

JSR, SBR, and RET Instructions When subroutines are programmed, the program scan will leave the main program, scan the subroutine, then return to finish the main ladder program.

Each input parameter in SBR and RET instructions must use the same data type as the corresponding parameters as in the JSR instruction.




Be sure to show students how to remove instruction parameters in case parameters are not needed.

11--9

The following graphic shows an example of a JSR instruction, SBR instruction, and RET instruction. In this example, note the following conditions: • When enabled, the JSR instruction passes BoxHeight, BoxWidth, and BoxLength to Box_Volume_1. • The SBR instruction receives Height, Width, and Length from the JSR instruction and copies those values. The program scan continues to execute in this routine. • When scanned, the RET instr uction sends Volume to the JSR instruction. The JSR instruction receives Volume and copies the value to Box_Volume. The program scan continues executing with the next instruction following the JSR instruction.

JSR Instruction Guidelines

To program a jump to a subroutine, consider these guidelines: Point out that for each JSR created, the subroutine is automatically created in the Controller Organizer. For example, once the JSR is placed on a rung and the new tag is created for the routine name, then the subroutine will appear under the main routine as a subroutine.

Rev. February 2007

• Program a JSR instruction in the main routine or a ny other routine. • Do not use a RET inst ruction in the main rou tine, if you use a JSR instruction that calls the main routine, a major fault occurs. • Apply JSR instructions to get the program to jump to the othe r routines from the main routine, when there is more than one routine in a program.


11--10


Example

JMP and LBL Instructions

Tell students the JMP instruction skips to the referenced LBL instruction with the same name and the program scan continues executing from there. Also mention, that jumping forward to a label saves program scan time by omitting a logic segment until it’s needed. Jumping backward lets the controller repeat iterations of logic. So, these instructions are used to either ignore logic or repeat logic as required.

The following graphic shows an example of a JMP instruction and a LBL instruction. In this example, note the following conditions: • When the JMP instruc tion is enabled, exec ution jumps over successive rungs of logic until it reaches the rung that contains the LBL instruction with label_20. • The JMP instruction and the LBL instruction both have the sam e name: label_20. • The LBL instruction is the firs t instruction on the ru ng.

[Other Rungs of Ladder Logic]

[First Instruction on Rung]

Jumping backwards too often could cause a fault because the task’s watchdog timer could time out and the controller will also fault




Example Emphasize the criticality of correctly programming ladder logic within MCR zones to avoid programming errors.

11--11

MCR Instruction The following graphic shows an example of an MCR instruction. In this example, note the following conditions : • When the first MCR instruction is enabled ( Switch_13 enables the rung), the rungs in the MCR zone are scanned for normal true or false conditions. • When the MCR zone is disable d, the controller sti ll scans rungs within the MCR zone, but scan time is reduced because non-retentive outputs in the zone are disabled. The

rung-condition-in is false for all the instructions inside of the disabled MCR zone.

The MCR instruction is not a substitute for a hard-wired master control relay that provides emergency-stop capability. Install a hard-wired master control relay to provide emergency I/O power shutdown. Rev. February 2007


11--12


Example Tell students that UID and UIE instructions are used primarily in projects that contain multiple periodic tasks.

UID and UIE Instructions The following graphic shows an example of a UID instruction and a UIE instruction. In this example, note the following conditions: • First, the UID on the rung will pre vent any logic from interrupting the next two rungs until the UIE is scanned. • Next, each time Limit_Switch_D15 is enabled the counter increments by one. • Then, the Product_Counter_1.DNbit is enabled once the accumulated value equals the preset value and the output RaiseExitBarrier_Output_2 is enabled. • Lastly, after the UIE is scanned, any remaining rungs potentia lly could be interrupted by higher-priority tasks.

Example Emphasize that the next 3 instructions, TND, AFI, and NOP are intended more for troubleshooting or debugging ladder logic, rather than normal programming.


TND Instruction The following graphic shows an example of a TND instruction. In this example, the controller will stop scanning at the TND and move to the end of the routine:



Example Point out that the AFI instruction will only affect the rung where it is contained. It will not affect the timer or the bits on the previous or subsequent rungs.

Example Tell students the NOP instruction is useful when “testing” an output to ensure it is operational. It may also be used to troubleshoot individual instructions on a branch.

Rev. February 2007

11-- 13

AFI Instruction The following graphic shows an example of an AFI instruction. In this example, the AFI instruction will make the rung false and the output will not be enabled:

NOP Instruction The following graphic shows an example of a NOP instruction. In this example, note the following conditions : • The NOP instruction is used as a place holder for futu re editing. • The Amber_Light_7 tag will be on all the time regardless of the .DN bit.


11--14




Exercise: Modifying Program Control Instructions in an RSLogix 5000 Project

11-- 15

Exercise: Modifying Program Control Instructions in an RSLogix 5000 Project Exercise A

In this exercise, you will practice modifying the appropriate program control instruction s to meet given project specific ations.

Context: You are responsible for portions of the Logix5000 ladder logic projects in the steel mill process. Your supervisor has requested that you modify the skip cars to dump the required raw material for making iron through the top of the furnace. The following list shows the raw materials neede d for the iron making process and the order in which they are loaded in the blast furnace: 1. Coke 2. Pellets

Your supervisor has informed you of the following key points concerning this program: • A selector switch should initia lize the proces s

Tip "

The project should contain 2 subroutines that will be called out by the main routine and be enabled by the selector switch: N am e

Description

Raw_Material_Coke

Coke is processed coal

Raw_Material_Pellets

Pellets are iron ore

• An output should ind icate when the s ubroutines have been enabled.

Tip "

The output indicator should be a green light on the workstation. • A pushbutton should start the pr ocess.

Tip "

The pushbutton represents operator intervention. The pushbutton will need to be enabled after each process. • A retentive timer should time each raw m aterial loaded into a skip

Tip "

Rev. February 2007

car for 10 seconds. The timer will represent the loading of one skip car on the ground, while the other skip car is dumping the previously loaded material at the top of the furnace. E 2007 Rockwell Automation, Inc. All rights reserved. MPCe56r

11--16


• An output should indicate w hen the raw materia l is being loaded.

Tip "

The output indicator should be an amber light on the workstation for each raw material. • An output should indicate wh en the raw materia l is done loading.

Tip "

The output indicator should be a red light on the workstation for each raw material. • A timer for each skip car should allow for 10 sec onds of travelling time.

Tip "

The timer will represent one skip car travelling to the furnace top to dump material and the other skip car travelling to the ground to be loaded with more material.

Tip "

The 2 retentive timers should have RES instructions in the project that will reset the RTO timers after each process. You are now ready to modify the two skip cars to perform the task of loading each raw material. When modifying instructions on a rung, keep these key points in mind: • A ladder logic rung can have input and output ins tructions interlaced, but the last instruction must be an output. • The state of an outp ut can also be a condit ional input. • A rung may contain no inputs, but at minimum i t must contain

one output.


Rev. February 2007 MPCe56r

11-- 17


Skip Car

Coke Loaded on the Conveyor

Raw Material Loaded in the Blast Furnace

Raw Material Coke and Pellets Loaded in the Scale Car

Blast Furnace

Conveyor Taking Coke to Stockhouse

Iron Trough

Scale Readout Molten Iron

Hot Metal Car

For help performing steps in this exercise, see the associated job aid(s).

Directions: 1. Open the MPC_1756r_A1.acd file. 2. Open the MainRou tine and verify the routine. 3. Did you receive any erro rs or warnings?

4. How many JSR ins tructions are in the MainRoutine and what are the user-created names of these instructions?

5. What is the tag nam e and base tag of the out put that will be enabled when the 2 JSRs are enabled?

6. Open the subroutine Raw _Material_Coke and verify the routine. Rev. February 2007

E 2007 Rockwell Automation, Inc. All rights reserved. MPCe56r

11--18


7. Did you receive any error s or warnings?

8. Open the subroutine Raw_Ma terial_Pellets and verify the routine. 9. Did you receive any error s or warnings?

10. Modify the project by using the docume ntation from the MainRoutine. 11. Verify the project. 12. Download the project to the controller in slot 1 and go online. 13. Place the controller in Run mode . 14. Start the project and verif y the following inputs and outputs in the program on the workstation and in the project: A. Enable the selector switch input on rung 0 of the MainRoutine in order to enable the 2 JSRs. B. Verify that a green output light is enabled on the workstation and in the project on rung 0. C. Enable the start pushb utton in the subroutine Raw_Material_Coke. D. Verify that the RTO timer times for 10 seconds as the raw

material coke is loaded into a skip car. E. Verify that as the timer is timing an amber output light is enabled on the workstation and in the project. F. Verify that when the timer is done tim ing a red output light is enabled on the workstation and in the project. G. Verify that once the red output light is enabled on the workstation a timer for each skip car is enabled for 10 seconds which allows for travelling time up to and down from the furnace. H. Verify that once the timer used for the skip car travelling is done it enables an RTO timer in the subroutine Raw_Material_Pellets. I. Verify that the RTO timer times for 10 seconds as the raw material pellets is loaded into a skip car. J. Verify that as the timer is timin g an amber output light is enabled on the workstation and in the project. K. Verify that when the timer is done timing a red output light is enabled on the workstation and in the project. E 2007 Rockwell Automation, Inc. All rights reserved.



11-- 19

L. Verify that once the red output light is enabled on the workstation a timer for each skip car is enabled for 10 seconds which allows for travelling time up to and down from the furnace. M. Verify that once the timer used for the skip car travelling is done it enables the two RES (reset) instructions for the two RTO timers in the project. 15. Repeat step 14. as many times as necess ary to verify your project. 16. Go offline and save the pro ject.

How Did You Do?

Rev. February 2007



11--20


Answers

Exercise A 3. No, there are no error s or warnings. 4. There are two JSR instructions named Raw_Ma terial_Coke and Raw_Material_Pellets in the MainRoutine. 5. The output tag name that will be enabled whe n the 2 JSRs are enabled is JSRs_Initia lized assigned to the base tag Local:0:O.Data.3. 7. Yes, you should receive an error in the subroutine

Raw_Material_Coke that states Rung 0: Empty rung. 9. Yes, you should receive an error in the subroutine Raw_Material_Pellets that states Rung 0: Empty rung. 14. Refer to the Project Exam ple on the next page for one possible way to modify ladder logic to jump to subroutines with operator control after each process.




11-- 21

Project Example The following graphic shows the MainRoutine. This is one possible way to modify ladder logic to jump to subroutines with operator control after each process:

The following graphic shows one possible way to modify ladder logic in the Raw_Materia l_Coke subroutine with operator control after each process:

Rev. February 2007


11--22


The following graphic shows one possible way to modify ladder logic in the Raw_Materia l_Pellets subrouti ne for this exercise:



Lesson

12

Monitoring GSV/SSV Instructions in an RSLogix 5000 Project What You Will Learn

Poll students to see how many of them are familiar with PLC-5 or SLC 500 status files. Note that these instructions are commonly used for motion control information.

After completing this lesson, you should be able to monitor controller system data using GSV/SSV instruc tions in an RSLogix 5000 project.

Why These Skills Are Important Having the skills to correctly monitor controller status values is important for the following reasons: • Unlike with other con trollers, the GSV/SSV ins tructions are the only tools for accessing controller status values. • Basing machine logic on incorrect ly retrieved contr oller status values can cause dangerous situations.

Before You Begin Poll students to see how many of them are familiar with PLC-5 or SLC 500 status files.

Monitoring Controller System Data Unlike other controllers, a Logix5000 t controller does not constantly monitor controller system data and update status files. A Logix5000 controller stores controller system data in structures

Add that by removing status files, the controller can performthe more efficiently because it does not have to update status files when it is not required.

called objects.

Point out that these instructions are not available in function block diagram or sequential function chart languages.

• GSV (Get System Value) Instruction: An instruction used to monitor specific controller system data.

Mention that by default, the GSV and SSV instructions are part of the Input/Output tab on the RSLogix 5000 Instruction toolbar.

Rev. February 2007

Objects are monitored and changed using specific ladder logic and structured text instructions:

• SSV (Set System Value) Instruction: An instruction used to set specific controller system data.

Use the GSV/SSV instructions carefully. Changes to objects storing controller system data or based on controller system data can cause unintended controller operati on that may injure personnel and damage equipment.

E 2007 Rockwell Automation, Inc. All rights reserved. GS1sb56r

12 -- 2


To clarify, state that the object class is the general category, the instance name is the specific occurrence, and the attribute is the specific piece of data.

GSV/SSV Parameters

Note that the source and destination are similar to the source and destination in a MOV instruction.

• Instance

GSV/SSV instructions operate on the values for these parameters: • Class • Attribute • Source (SSV) or destination (GSV)

Class

The class is the category or type of object that is accessed:

Category

The following classes of objects can be monitored or set: For this class . . .

Add that these parameters are also detailed in the procedures guide.

Note that because the DF1 serial port is in the controller, it is part of the controller data.


The instruction will retrieve or set information about the . . .

AXIS

Axis of a servo module

CONTROLLER

Percentage of CPU time assigned to communications

CONTROLLERDEVICE

Controller hardware

CST

Coordinated system time of a chassis

DF1

DF1 driver of the controller’s serial port

FAULTLOG

Fault history of the controller

MESSAGE

Attributes of a message instruction

MODULE

Status, faults, and mode of a module

MOTIONGROUP

Status of a group of axes

PROGRAM

Fault or scan times of a program

ROUTINE

Instance of a routine

SERIALPORT

Configuration of the serial port

TASK

Properties or scan times of a task

WALLCLOCKTIME

Wall clock of a controller

Rev. February 2007 GS1sb56r


12 -- 3

Instance Note that this is one reason that naming I/O modules with a descriptive name (using purpose or location, for example) is beneficial.

If more than one project component relates to the class selected by a programmer, an instance will also be displayed:

Specific Instance Name

Specific Component

? How would the “This” option help

If “THIS” is displayed, then the information relates to the current task, program, or routine.

programmers work more efficiently? Answer: It makes copying the programming language to other programs extremely easy.

Attribute Note that not all attributes are able to be retrieved and set.

The attribute is the particular property or value that is retrieved or set:

Property to Monitor

Source or Destination Add that the layouts of the required source or destination data types are detailed in the documentation reference guide and in the online Help system.

A source contains values that will be set by an SSV instruction. A destination stores the values that are retrieved by a GSV instruction:

Storage Tag for Value

Rev. February 2007

E 2007 Rockwell Automation, Inc. All rights reserved. GS1sb56r

12 -- 4


Take some time to explain how the data requires a tag with a user-defined structure.

The data type of the source or destination tag is created by a programmer to match the size and layout of the data.

Example: GSV Instruction

GSV instruction s can be used to retrieve information about program scan time:

Tag

User-Defined Data Type

In the example instructions, point out the object class and the object name and then the attribute name.

This example shows how system data is gathered about a program: • The specified program being monito red is “THIS” (the cu rrent program). • The time.first GSV ins truction retrieves the value of the last sc an • The second GSV ins truction retrieves the value of the maximum scan time. • Both instructions place the data into diff erent members of a tag.




Use the graphic to relate the parts of a fault routine:

GSV instructions can also be used to retrieve a fault code and then store it in a tag.

1. The fault routine is created in the program and assigned.

Each program can have its own fault routine:

2. The GSV instruction is used to retrieve the fault code and store it in the tag. 3. The tag is a DINT array that mirrors the organization of the data in the object. 4. The DINT elements are described in the Help system under GSV/SSV object.

12 -- 5

• The controller exec utes the program’s fault routine when an instruction-related fault occurs. • If a fault is cleared, the routi ne continues exe cuting at the instruction immediately after the one that caused the fault: -- The controller does not enter F ault mode. A fault routine normally contains logic to identify a fault and

sometimes clear it:

Fault Routine Icon Fault Routine Code

If necessary, explain that the first element of the array must be selected by the programmer. The programmer knows that the fault information requires an array of 11 DINTS by checking GSV/SSV Objects in the Help system. Elements 0 to 1: 64-Bit Timestamp Element 2: Fault Type (Lower 16 Bits) and Code (Upper 16 Bits) Elements 3 to 10: Fault-Dependent Information

Programmers may store GSV data in simple tags or tags of user-defined data types.

Status Flags Stress that most controller values are accessed using GSV and SSV instructions.

Controller status and arithmetic status flags can also be examined for specific data.

Note that flags are not base tags. Programmers will never create alias tags for them.

Controller Status Flags

Limited controller status can be examined using the following controller status flags:

Rev. February 2007

This status flag . . .

Is set after the . . .

First scan

S:FS

First normal scan of the routines in the current program

Minor fault

S:MINOR

Generation of an instruction-execution minor fault by program execution E 2007 Rockwell Automation, Inc. All rights reserved. GS1sb56r

12 -- 6


Arithmetic Status Flags Add that for on-the-job reference, the status flags are listed in the documentation reference guide.

Arithmetic status flags can be used to view the results of an arithmetic operation: This status flag . . .

S:V

Value being stored cannot fit into the destination because it is either greater than the maximum value or less than the minimum value for the destination

Zero

S:Z

Instruction’s destination value is zero [0]

Negative

S:N

Instruction’s destination value is negative

Carry

S:C

Instruction generated a carry

Overflow

Here’s How

Download CCP153_1756R_DEM6.acd to the controller in slot 1. Open the routines. Demonstrate how the GSV instruction operates and then show students how to go to the tag files to see the data and how it’s mapped.


Is set when the . . .

To monitor controller system data using GSV/SSV instruc tions in an RSLogix 5000 project. As your instructor demonstrates this procedure, follow along in the associated job aid(s).


Exercise: Monitoring GSV/SSV Instructions in an RSLogix 5000 Project

12 -- 7

Exercise: Monitoring GSV/SSV Instructions in an RSLogix 5000 Project Exercise A

In this exercise, you will practice monitoring controller system data using GSV/SSV instructions.

Context: As a maintenance technician for a compressor assembly line, you are responsible for monitoring the line and returning the line to normal operation when there is a problem. You are monitoring a compressor assembly line that has been running for several weeks. For help performing steps in this exercise, see the associated job aid(s).

Directions: 1. Verify that selector switch DI12 is set to the left. 2. Open the GS1_1756R_A1.acd project file. 3. Download the file to the controller in slot 1 and change the controller operating mode to Remote Run. 4. Open the MainRoutine in the Station_1_Pr ess program. 5. Examine rung three. 6. What class or type of data is this GSV in struction retrieving?

7. Which instance of this data is being monitored?

8. Of all possible pieces of progra m-related data, which one is being monitored?

9. In which tag is this piece of data being stor ed?

10. Access the Contents section of the online Help system and searc h for GSV/SSV objects. Rev. February 2007

E 2007 Rockwell Automation, Inc. All rights reserved. GS1e56r

12 -- 8


11. Link to the informa tion on the Program obj ect. 12. What type of data is the attribute Las tScanTime?

13. According to the description, in what time unit is the LastScanTime given?

14. In the program-sc oped tags collection, acc ess the tag that you identified in Step 9. 15. What is the approxima te value of the last scan time?

16. Examine rung four. 17. What class or type of data is this GSV ins truction retrieving?

18. Which instance of this data is being monitored?

19. Of all possible pieces of progra m-related data, which one is being monitored?

20. Where is this piece of data bein g stored?

21. In the program-sc oped tags, access the tag that you identified in Step 20. and examine its structure. 22. Continue monitori ng this tag. To simulate parts on a conveyor passing the photo-eye, flip switch 12 (DI12) from left to right three times. 23. What is the value of Fault_Da ta.Type?


Rev. February 2007 GS1e56r


12 -- 9

24. What is the value of F ault_Data.Code?

25. In the Contents sec tion of the online Help syste m, search for minor fault types and codes. 26. According to the type and code, describe the fault that is occurring?

27. To simulate another part on a conveyor, flip switch 12 (DI12) from left to right. Has the minor fault stopped the process (e.g., are the workstation pilot lights off)?

28. What is the approxim ate value of the last scan time now ?

29. Compare the value of the last scan time to the value identifie d for Step 15. (approximately 200 microseconds). 30. Based on your answ er, why would you want to clear a minor

fault?

31. Verify that the selector switch DI12 is set to the left. 32. Go offline.

How Did You Do?

Rev. February 2007


E 2007 Rockwell Automation, Inc. All rights reserved. GS1e56r

12 -- 10


Answers

Exercise A 6. The object being monitor ed is “Program.” 7. The specific instance being monito red is “This,” or the open program. 8. The specific progr am-related data being monitored is LastScanTime. 9. This data is being stored in the Program_Last_S can_Time tag. 12. The data is a DINT value. 13. The LastScanTime is the last executio n time recorded for the program. Time is in microseconds. 15. Running in a ControlLogix 5563 controll er, the program takes approximately 50 to 80 microseconds to scan. 17. The class or type of data the GSV ins truction is retri eving is “Program.” 18. The specific instance being monito red is “This,” or the open program. 19. The specific progr am-related data being monitored is MinorFaultRecord. 20. This data is being store d in one member of the Fault_Data tag. 23. The value of Fault_Da ta.Type is 4. 24. The value of Fault _Data.Code is 4. 26. An arithmetic overf low has occurred in an instruction. The error can be fixed by examining arithmetic operations (order) or adjusting values. 27. No. A minor fault does not aff ect the control of the applicat ion or process. 28. The scan time has doubled. 30. Scan time and execution are affe cted by minor faults.


Rev. February 2007 GS1e56r

Lesson

13

Forcing I/O and Toggling Bits in RSLogix 5000 Software What You Will Learn

After completing this lesson, you should be able to troubleshoot 1756 I/O module problems by performing the following tasks: • Force digital and analog I/O values • Toggle bits

Why These Skills Are Important

? Has anyone forced I/O or toggled bits before?

Before You Begin

? How often do you use forcing at your company? For what situations?

Forcing I/O values and toggling bits allows a troubleshooter to effectively verify inputs and outputs and manipulate executable programming language. When forcing mistakes are made, unintended machine motion or loss of process control can occur, thereby injuring personnel and damaging equipment.

Force Functions Forcing: A software function that allows a user to enable or disable an input or output independent of the executable programming language.

Forcing an I/O value can be used for any of the following troubleshooting situations: • Checking field wiring • Checking the functionality of fi eld output device s • Testing a portion of executa ble programming language • Simulating inputs that have not been wired • Temporarily correcting mis-wired field devices

Force-On Function: Allows a user to enable an input module data point, regardless of the state of the input circuit, or an output circuit, regardless of the state of the output module data point. Force-Off Function: Allows a user to disable an input module data point, regardless of the state of the input circuit, or an output circuit, regardless of the state of the output module data point. Analog Force Function: Allows a user to set an analog I/O value regardless of the state of the input or output module’s channel data value.

Rev. February 2007

E 2007 Rockwell Automation, Inc. All rights reserved. FORsb56r

13 -- 2


Point out that forces can be installed, enabled, or disabled while monitoring the file offline or in any processor mode while monitoring the file online.

Rules for Forcing

Follow these rules when forcing any I/O values: • Always check for forced value s in the program before ena bling forces. • Apply forces only to real inputs a nd outputs.

Explain that if force protection exists, forces cannot be enabled. For example, if the data value is of type REAL, then individual bit forcing is not supported.

Understand the following points when using forcing functions: • Enabling or disabli ng forces acts on all insta lled forces. • Uploading the pr ogram uploads the forces.

forces are enabled, all forc ed values will take ef fect • If immediately. • Forces are saved and download ed with a project.

Tip "

When a controller is running a project, forcing has priority over ladder logic, function blocks, structured text, and sequential function charts. Safety Precautions

? Does your company have a policy regarding forcing?

? Does forcing an input affect any logic

All force functions can result in sudden machine movement. Consider these factors before forcing I/O values: • Potential danger to personnel • Machine response to forced I/O

that examines that bit?

• Possible effects on other portions of the machine/pr ocess

Answer: Yes.

• Company policy conc erning forcing I/O (e.g., is authoriza tion required?)

Use EXTREME CAUTION when using forcing. All force functions can result in sudden machine movement, possibly injuring personnel or damaging equipment. If forces are established, enabling forces will enable all forces without prompting. If forces are enabled, any additional forces will take effect immediately. Before proceeding, verify the status of forces, verify that you are online to the correct processor, notify personnel of the proposed changes, and take adequate safety precautions.


Rev. February 2007 FORsb56r

13 -- 3


? How can you determine if forces

State of Forces

exist in a project? Answer: Examine the Online toolbar or the ladder logic.

The state of forces in the controller is displayed in the RSLogix 5000 Online toolbar:

In the graphic, explain that the state of Forces forces is displayed Drop-Down in the O nline toolbar, List but individual forced I/O are found in the ladder logic.

I/O Forces Indicator

Also mention that the I/O Forces Indicatorbutton. is displayed by clicking the Forces

Search for Forces

Interpretation of the state of forces is shown in the following table: If the Forces drop-down list displays . . .

And the icon displayed is . . .

Gray

And the background color is . . .

None

No Forces Purple

Solidyellow

Red

Flashingyellow

Forces Red

Solidyellow

Then the following conditions exist . . .

No forces exist or are enabled (active). Even if forces are created they will not be automatically active. All I/O forces are enabled. se ex reme cau on. ny ex s ng forces are active and any added forces will take effect immediately. Forces have been created but are not enabled (active). If forces are enabled, the existing forces will take effect immediately. " Determine if the force is required. If it is not required, remove the force.

Point out that all enabled forces are shown in red.

Forces can also be installed and displayed through editors, such as the Ladder editor:

Emphasize that the input is forced on and the output is forced off. In the MOV instruction, point out that the analog input value is forced to a different value.

Forces Displayed in Red

Rev. February 2007


13 -- 4


Point out that the tag can reside in the Program Tags or Controller Tags collection.

A forced input or output is also installed and/or displayed in the tags collection:

Forced Value

A forced value is retained until the force is disabled or removed.

Point out that DriveLogix controllers do not have the Force LED.

Depending on the controller, the state of forces may also be displayed on a Force LED: ControlLogix Force LED

CompactLogix Force LED

FORCE

FlexLogix Force LED

The LED status can be interpreted using the following table:


If the LED status is . . .

Then the state of forces is . . .

Off

Noforcesareinstalled.

Amber

Forces are enabled.

Flashing Amber

Forces are installed but not enabled.



13 -- 5

Toggling Bits Point out that after an internal bit is toggled, it is acted on by the project’s programming language, just like any other part of the project.

Toggling an internal bit changes the binary value of that bit. For example, if a bit with a value of 0 is toggled, it will have a new value of 1.

Emphasize that forcing is for physical device tags, where as toggling is for internal bits.

A tag of BOOL data type can be toggled directly from the instruction in the Ladder editor:

Point out that bits can be toggled from either the Program Tags or Controller Tags collection.

A tag can also be toggled from a tags collection:

Toggle a Bit by Changing Its Value

Emphasize that both internal bits and I/O points can be toggled.

Tip "

Rev. February 2007

When a controller is running a project, the ladder logic has priority over toggling a bit.


13 -- 6


Here’s How

To troubleshoot 1756 I/O module problems by performing the following actions: • Force digital and analog I/O values

Demonstrate the following actions:

• Toggle bits

1. Go online to the CCP153_1756R_DEM13.acd project.


2. From the ladder logic, force inputs and outputs on and off and toggle bits. 3. Show that fo rced inputs affect the tag values and ladder logic. 4. From the tags collection, force inputs and outputs on and off and toggle bits. 5 Disable forces. 6. Remove forces one at a time and all at once. Cover these points:

n Online toolbar indicates force status n Enabled forces enable all forces n Additional forces take immediate effect when forces are enabled




13 -- 7

Exercise: Forcing I/O and Toggling Bits in RSLogix 5000 Software Exercise A

In this exercise, you will practice forcing I/O values and toggling bits using RSLogix 5000 software. For help performing steps in this exercise, see the associated job aid(s).

Directions: 1. List the situatio ns that might determin e when forcing is used:

2. List the factors to cons ider before usin g forcing:

3. Open the FOR_1756R_A1.acd project file. 4. Download the project file to the controller in slot 1 and change the operating mode to Remote Run. 5. Record the current state of force s in the controller:

6. Disable all forces. 7. Force the tag I_pushbutton_0 on. Rev. February 2007

E 2007 Rockwell Automation, Inc. All rights reserved. FORe56r

13 -- 8


8. Enable all forces. 9. What happens to the outputs? Why does this hap pen?

10. Force the tag O_Red light_11 off. 11. Did the tag get forc ed off?

12. Remove the force on the tag O_Redlight_1 1. 13. What is the condition of the tag O_Redlight _11 on the workstation now?

14. Enable the tag O_Redli ght_8 without using a force. 15. How did you enable the tag?

16. Disable the tag O_Redlight_8. 17. Enable the tag I_selector _12, enabling the tag O_Greenlight _3. 18. Force the tag I_sel ector_12 off.


Rev. February 2007 FORe56r


13 -- 9

19. What happens to the tag O_Greenlight_3?

20. Force the analog input value to 8.5 V . 21. Toggle the tag Internal_Bit_1. 22. What is the value of t he Channel 0 analo g meter?

23. Disable all forces. Noti ce that all of the forces rem ain in the program; however, they are no longer enabled. 24. What happens to the digital and analo g I/O values?

25. Go offline.

How Did You Do?

Rev. February 2007


E 2007 Rockwell Automation, Inc. All rights reserved. FORe56r

13 -- 10


Answers

Exercise A 1. Situations when forcing might be used include : • • • • •

Checking the field wiring Checking functionality of fie ld output devices Testing a portion of the program logic Simulating inputs that have not bee n wired Correcting mis-wired field devices temporarily

2. Factors to conside r before using forcing include: • • • •

Potential danger to personnel Machine response to forced I/O Possible effects on other portions of the machine/pro cess Company policy concerning for cing I/O (e.g., do you have authorization?)

5. The current state of forces in the controlle r is enabled, with no forces present. 9. When the forces are en abled, the output tag O_Redli ght_11 is enabled. This happens because forcing the input tag I_pushbutton_0 on transitions the rung from false-to-true, enabling the output condition. 11. Yes. The output for tag O_Redlight_11 on the workstation should be disabled. However, the output tag O_Redlight_1 1 in the software project remains enabled, but the force indicator

OFF determines the state of the bit. 13. Since the force wa s removed from the outpu t bit tag O_Redlight_11, the input tag I_pushbutton_0, on the same rung, determines the condition of the output. The input tag I_pushbutton_0 has been forced on, therefore enabling the output condition. 15. To enable the output tag O_Redligh t_8 without using a force, the input tag Internal_Bit_0 must be toggled. Since this input tag does not have an external bit address it will remain toggled until manually toggled again. 19. When I_selector_12 is forced off, the rung transitions from true-to-false and the output tag O_Greenlight_3 is disabled. 22. The Channel 0 analog meter is the sa me value as the analog input value of 8.5 volts. 24. When the forces ar e disabled, the digital and anal og values return to the state of the analog input devices.


Rev. February 2007 FORe56r

Lesson

14

Troubleshooting Logix5000 Controller Problems What You Will Learn

After completing this lesson, you should be able to troubleshoot Logix5000 controller problems by performing the following tasks: • Identify fault types • Resolve a non-recoverable major fault • Find and clear a r ecoverable major or mino r fault

Why These Skills Are Important Review the following fundamental concepts with the students: 1. The general purposes of a controller in an overall control system 2. For ControlLogix modules - RIUP (Removal and Insertion Under power), including safety warnings

Before You Begin

All troubleshooting in a Logix5000 system begins with the state of the controller: • Knowing how to identify a fault wi ll help you isolate it. • Knowing how to proper ly address each type of fault will help you return a system to proper order with minimal downtime.

Controller LEDs

Note that LEDs are often referred to as indicator lights or status lights. Point out that when power is first applied, LEDs flash on and off while the controller initializes. 2.

1.

Changes to the controller status indicators anytime after startup may indicate a change or a problem. When a failure in a system occurs, view the LEDs in this order: Alternate Viewing Options

Hardware 3.

3.

Rev. February 2007

Software

1.

1.

2.

E 2007 Rockwell Automation, Inc. All rights reserved. LEDsb56r

14 -- 2

Troubleshooting Logix5000 Controller Problems

Remind students that there is a separate lesson for power supply problems.

If all LEDs are off, the problem may be with the power supply.

Note that for other controller LEDs, students can refer to specific documentation for the controller -- this is usually found in the installation instruction manuals.

Mention that a non-recoverable fault is often called a hardware fault.

For a detailed explanatio n of ControlLogix controller LED states and colors, refer to the troubleshooting guide .

Identifying Fault Types The controller detects three main categories of faults: • Non-recoverable major fault • Recoverable major fault • Minor fault

Non-Recoverable Major Fault Non-Recoverable Major Fault: A fault within the controller that is severe enough to shut it down. Hardware failure causes such a fault.

With a non-recoverabl e major fault, the following changes take place in the system: Note that students should have a basic understanding of digital I/O configuration from the fundamentals course or equivalent experience. More in-depth information is available in the Troubleshooting Discrete I/O Modules lesson.

• Outputs change to the Fault Mode s tate set in the I/O configuration:

-- On -- Off -- Hold • The controller OK LED turns solid red. • The word “Faulte d” is displayed in the Online toolba r.

Solid Red


Rev. February 2007 LEDsb56r


14 -- 3

Recoverable Major Fault Note that the major fault types and codes and the minor fault types and codes can be found in the Help system and the appendices of the procedures guide.

Recoverable Major Fault: A fault that is severe enough to shut down the controller if the condition is not cleared.

A recoverable major fault can be of two categories: • Instruction execution • Other errors:

-- Power loss -- Loss of critical I/O -- Array subscript errors Recoverable Major Fault Processing: Level 1

When a recoverable major fault first occurs, the following changes take place in the system: • A major fault bit is set in the contro ller. • Any user-programmed fault routines are executed:

-- Program-level fault routine -- Controller-fault handler Fault Routine Tell students that the fault routine is created in the program and assigned. Additionally, a GSV instruction can be used to retrieve the fault code and store it in a tag.

Each program can have its own fault routine: • The controller exec utes the program’s fault routine when an instruction-related fault occurs. • If a fault is cleared, the rout ine continues exe cuting at the instruction immediately after the one that caused the fault:

-- The controller does not enter F ault mode. A fault routine normally contains logic to identify a fault and sometimes clear it: Fault Routine Icon

Remind students that non-instruction level faults include I/O faults, task watchdog faults, etc. Add that for non-instruction faults, no program fault routines are called.

Controller Fault Handler

Each project contains a Controller Fault Handler folder. A programmer may add one optional program to it. A controller fault handler executes in the following situations: • When a recoverable major fault is not relate d to an instruction

How do you access another routine ? from the main routine?

• When a program fault routine doe s not exist or coul d not clear an instruction-related fault

Answer: Program a JSR instruction to call the specified routine (subroutine) from the main routine. Rev. February 2007


14 -- 4


Note that the programming language works in the same manner as the programming in a fault routine.

At minimum, a main routine must be created and assigned:

Program Main Routine Subroutine

Recoverable Major Fault Processing: Level 2

If the controller fault handler does not exist or cannot clear the recoverable major fault, the controller enters Fault mode and shuts down: • Outputs change to the configured output state for Pr ogram mode. • The controller OK LED flashes red. • The word “Faulted” is displayed in the Online to olbar:

Flashing Red




14 -- 5

Multiple Recoverable Major Faults Remind students that the fault information is displayed on the Major Faults tab of the Controller Properties dialog box.

With multitasking capabilities, a controller can handle as many as 32 simultaneous recoverable major faults. If multiple recoverable major faults are reported, the following actions take place: • The controller processes the faults in the order that they occur . • If any of the faults are not cleare d by the controller fault handle r, the controller goes into Fault mode:

fault that w as not cleared and up to two additional fa ults -- The are logged.

-- This information can be view ed via the Major Fa ults tab in the controller properties. • If over 32 major faults occ ur at the same time, the control ler goes into Fault mode:

-- The first three ma jor faults are logge d into the controller fault log. Remind students that a watchdog fault occurs if the sum of the execution times for all programs in a task is greater than the watchdog value.

• If a watchdog fault occ urs a second time in the same logic s can, the controller enters Fault mode, whether or not the controller fault handler clears the fault.

Familiarize the students with this section of the guide. Point out some common faults. Mention that these error codes and descriptions will also be displayed in

Common Major Faults

the software when you select “Goto Fault”.

• Required I/O connection has failed

The Major Fault Types and Codes appendix in the Troubleshooting Guide identifies some common faults and their corrective actions: • Array subscript is too big • A timer has a negativ e preset or accumu lated value • Task watchdog timer has expired • Others

Minor Fault Minor Fault: A fault that is not severe enough to shut down the controller: • Low battery • Serial port problems

Rev. February 2007


14 -- 6


With a minor fault, the following changes take place in the system: • The program scan and normal I/O control conti nues. • The controller OK LED remains solid green. • A minor fault bit is set.

Normal Operating State

Solid Green

A minor fault may only be detected if programming language is written to monitor it or if you monitor the Minor Faults tab in the Controller properties.

A minor fault does not affect application operation. However, clearing a minor fault may improve scan time.

State that this is an overview of the process. The full procedure will be demonstrated in the Here’s How section.

Resolving a Non-Recoverable Major Fault Resolving a non-recoverable major fault requires cycling power to the faulted controller. Observe and comply with all applicable safety precautions in the Safety Precautions appendix.

Identify what devices or processes other controllers, communications modules, and I/O modules in the chassis are controlling before you cycle power to the entire chassis. E 2007 Rockwell Automation, Inc. All rights reserved.


14 -- 7


State that this is an overview of the process. The full procedure will be demonstrated in the Here’s How section.

Finding and Clearing a Recoverable Major or Minor Fault To properly address a recoverable major or minor fault, you must perform the following steps in this order: 1. Identify the caus e of fault using the softwar e. 2. Fix or remove the actual cau se of the fault (e.g., corr ect the programming, adjust the watchdog timer value, etc.)

Note that you must manually remove (sometime physically) the cause of the fault.

3. Clear the fault indic ation in the softwar e.

You can jump directly to step 3 and clear the fault; however, if an error that caused a recoverable major fault is not corrected, the controller will fault again.

Faults can be identified and cleared using the Controller Properties dialog box: Major Faults Tab Minor Fault Tab

Identify the Fault

Clear the Faults

Rev. February 2007


14 -- 8


A recoverable major fault can also be cleared using the keyswitch: ControlLogix Controller Keyswitch

CompactLogix Controller Keyswitch FlexLogix

Controller Keyswitch

Clearing the fault using the keyswitch will not correct the cause of the fault (hardware problem , etc.). Therefore, the controller may fault again as soon as it is placed in Run or Remote Run mode.

Tip " Here’s How

This procedure does not clear the major fault log in the software. The fault log is displayed on the Major Faults tab of the Controller Properties dialog box. To troubleshoot Logix 5000 controller problems by performing the following actions: • Identify a fault type

Download CCP153_1756R_DEM7.acd to the controller in slot 1. Beginning with tab two of the troubleshooting guide, identify and clear the major fault. Be sure to refer to the software procedure for clearing the fault in the appendix. Emphasize that you must identify the cause of the fault and remove it before clearing it. Do not save the changes to the project.

• Resolve a non-recoverable major fault • Find and clear a re coverable major or minor f ault


Download the project a second time and clear the fault using the keyswitch. Emphasize that this does not remove the cause of the fault.



Exercise: Troubleshooting Logix5000 Controller Problems

14 -- 9

Exercise: Troubleshooting Logix5000 Controller Problems Exercise A

In this exercise, you will practice troubleshoo ting Logix5000 controller problems.

Context: You are responsible for monitoring an application and returning the system to normal operation when there is a problem. You are monitoring a compressor assembly line that has been running for several weeks. For help performing steps in this exercise, see the associated job aid(s).

Directions: 1. Open the LED_1756R_A1.acd project file. 2. Download the file to the controller in slot 1 and change the controller operating mode to Remote Run. 3. After a few seconds, what is the color and sta te of the controller OK LED?

4. Identify and record the type of fa ult:

Tip "

For help, refer to the Troubleshooting Guide. 5. To simulate another part on a conveyor, flip switch 12 (DI12) from left to right. (Do not correct the fault). 6. Did the fault stop the proces s (e.g., are the work station pilot lights disabled)?

Rev. February 2007

E 2007 Rockwell Automation, Inc. All rights reserved. LEDe56r

14 -- 10


7. Why are the outputs set this way?

8. What is the cause of the fault?

9. You discussed the cause of this fault with the project programmer. The corrective action decided is to increase the task watchdog timer value to 500. 10. Clear the fault.

Tip "

For help, refer to the Troubleshooting Guide. 11. After the fault is cle ared, verify that the contr oller OK LED is solid green. 12. Verify that the selector sw itch DI12 is set to the left. 13. Go offline.

How Did You Do?


Exercise B

In this exercise, you will practice troubleshoot ing Logix5000 controller problems. For help performing steps in this exercise, see the associated job aid(s).

Directions: 1. Open the LED_1756R_B1.acd project file. 2. Download the project file to the controller in slot 1 and change the controller operating mode to Remote Run. 3. Verify that the controller OK LED is solid green. 4. To simulate parts mo ving down the conveyor and pass ing a photo-eye, press pushbutton 0 (DI0) 3 times. 5. What is the color and state of the controll er OK LED?


Rev. February 2007 LEDe56r


14--11

6. Identify and record the type of fa ult:

Tip "

For help, refer to the Troubleshooting Guide. 7. To what mode are outputs set (Fault or Program)?

8. What is the cause of the fault?

9. You have discussed the cause of this fault with the project programmer. Correct the cause of the fault by changing the Record tag properties. Make the tag an array of 400. 10. Clear the fault.

Tip "

For help, refer to the Troubleshooting Guide. 11. After the fault is cleared, verif y that the controller OK LED is solid green.

How Did You Do?

Rev. February 2007



14 -- 12


Exercise C

In this exercise, you will practice troubleshoot ing Logix5000 controller problems. To successfully complete this exercise, you may need to refer to the Troubleshooting Guide.

Directions: The following changes have taken place in the system: • Outputs have changed. They are all off. • The controller OK LED is solid red. • The controller battery has been removed. • The word “Faulte d” is displayed in the Online toolba r.

Solid Red

1. Identify and record the type of fau lt:

Tip "

For help, refer to the Troubleshooting Guide. 2. To what mode are the outputs set (Fault or Program)?

3. There are two ControlLog ix controllers in the chassis . Both are controlling diffe rent parts of the process. How would you cycle power to the faulted controller only?




14 -- 13

4. After you replace the controller in the chas sis and turn the power back on, you notice that the I/O light is off. What might be the problem if the I/O light is off?

Tip "

For help, refer to the Troubleshooting Guide. 5. What step would you take next?

6. If the controller “OK ” light had remained solid red, after taking the action in Step 5., what action would you take next?

How Did You Do?

Rev. February 2007



14 -- 14


Answers

Exercise A 3. The controller O K LED is flashing red. 4. The fault is a recoverable major fault (T ype 06, watchdog fault), as indicated by the flashing OK LED. 6. Yes, the pilot lights are all off. 7. The outputs are set to the Program Mode -- in this case “Off.” Program Mode may also be “on” or “hold” depending on safety factors and the type of equipment . 8. The cause of the fault (rec overable major fault) is from the expiration of the task watchdog. The software indicates that the Assembly task contains the expired watchdog. According to the error type and code (Type 06, Code 01), and using the online Help, you can find Major Fault Types and Codes that list corrective actions for each.

Tip "

If you are using the troubleshooting guide, a recoverable major fault (red flashing light) should take you from tab 2 to tab B7. On this tab, a procedure directs you to select “Go to Faults” and identify the error (Type 06, Code 01). Using online Help or the Appendix, the error code indicates a watchdog timer fault and recommends correc tive actions.

Exercise B 5. The controller O K LED is flashing red. 6. The fault is a recoverable major fault (T ype 04, program fault) as indicated by the flashing OK LED. 7. The outputs are set to the Program Mode -- in this case “Off.” Program Mode may also be “on” or “hold” depending on safety factors and the type of equipment . 8. The fault was caused beca use the array subscr ipt is too large (e.g., ladder logic attempted to write a value to an array element that is greater than the total number of elements), or the CONTROL data type POS or LEN is invalid. An invalid array subscript was specified. The software indicates that the Assembly task contains the program fault. According to the error type and code (Type 04, Code 20), and using the online Help, you can find Major Fault Types and Codes that list corrective actions for each.

Tip "


If you are using the troubleshooting guide, a recoverable major fault (red flashing light) should take you from tab 2 to tab B7. On this tab, a procedure directs you to select “Go to Faults” and identify the error (Type 04, Code 20). Using online Help or the Appendix, the error code indicates a program fault and recommends corrective actions. Rev. February 2007 LEDe56r


14 -- 15

Exercise C 1. This is a non-recovera ble major fault, also called a hardwar e fault. 2. The outputs are set to the Fault Mode -- in this case “Off.” Fault Mode may also be “On” or “Hold” depending on safety factors and the type of equipment. 3. With ControlLogix RIUP capabilities , observing all safety precautions, you can remove the faulted controller under power. 4. There are three possible reasons the I/O light might be off: • No modules are in the I/O confi guration. • Communications is not configured. • Project is not in the controller. 5. The next step is to configure devi ces or communications or download the project. 6. If the problem pers ists, the next step is to repair or rep lace the controller.

Rev. February 2007


14 -- 16




Appendix

A

I/O Wiring Diagrams

Slot 0 - 1756-OB16D Digita l Output Mod ule WORKSTATION DEVICE RED

K C A L B

RED

+DC-0 +DC-0

2

+DC-0

6

+DC-0 +DC-0 +DC-0 +DC-0

8

4

10 12

LABEL DO0

OUT-0

G

3

OUT-1

A

5

OUT-1

R

7

OUT-3

G

DO3

9

OUT-4

A

DO4

11

OUT-5

R

1

DO1 DO2

14

DO5

GND-0 +DC-1 +DC-1 +DC-1 +DC-1 +DC-1 +DC-1

16

28

DO2 = Local:0:O.Data.2

+DC-1 GND-1 GND-1 Not Used

30 32

DO3 = Local:0:O.Data.3 DO4 = Local:0:O.Data.4

18 20 22


24


26

34


36

K C A L B

A

- GREEN PILOT LIGHT - AMBER PILOT LIGHT

R

- RED PILOT LIGHT

G

Angle

24VDC

RAU

1/2

Euclid, Ohio

Frac. 1/64 .xx

Engineer Date 05/01/99

.010

C .xxx .xxxx

Rev. February 2007

.005 .0005

B A

Changed Wire Changed Wire Added lights Date

2/10/02 1/15/02 2/12/01

Approved By:

1756- OB16D SLOT 0 Digital Output Wiring Diagram

E 2007 Rockwell Automation, Inc. All rights reserved. WD3a56r

A--2

I/O Wiring Diagrams

Slot 2 - 1756-IB16D Digital Input Modu le LABEL

WORKSTATION DEVICE

BLACK

BLACK

BLACK

K C A L B

GND-0 GND-0 GND-0

2

1

4

3

6

5

IN-0 IN-1 IN-2

GND-0 GND-1 GND-1 GND-1

8

7

IN-3

10

9

12

11

IN-4 IN-5

14

13

IN-6

GND-1 GND-2

16

15

18

17

GND-2 GND-2 GND-2 GND-3 GND-3 GND-3

20

19

22

21

IN-7 IN-8 IN-9 IN-10

24

23

26

25

GND-3 GND-3 NOT USED

28

27

30

29

32

31

34

33

36

35

DI0 DI1 DI2

+ 24 DC

DI3 DI4 DI5 DI6 DI7 DI8 DI9 DI10 DI11 DI12

IN-11 IN-12 IN-13 IN-14 IN-15 NOT USED

DI13 DI14 DI15

NOT USED

DI0 = Local:2:I.Data.0
















- NORMALLY OPEN PUSHBUTTON - SELECTOR SWITCH Angle

RAU

1/2

Euclid, Ohio

Frac. 1/64 Engineer .xx .xxx .xxxx


.010 .005 .0005

C B A

Changed Wire Changed Wire

2/10/02 1/15/02

1756- IB16D SLOT 2

Added lights

2/12/01 Date

Digital Input Wiring Diagram

Rev. February 2007 WD3a56r

I/O Wiring Diagrams

A -- 3

Slot 4 - 1756-OB16D Output Module

RED

+DC-0 +DC-0

K C A L B

RED

2 4

+DC-0

6

+DC-0 +DC-0 +DC-0 +DC-0

8

LABEL

WORKSTATION DEVICE

10 12 14

13

GND-0 +DC-1 +DC-1 +DC-1 +DC-1 +DC-1 +DC-1 +DC-1

16

15

18

17

20

19

22 24

GND-1 GND-1 NOT USED

32

OUT-6 OUT-7

DO6 DO7 DO8

G A

21

OUT-8 OUT-9 OUT-10

A

23

OUT-11

R

R

DO9 DO10

G

DO11

26 28 30


34


36


K C A L B


G

24VDC

A R Angle

- GREEN PILOT LIGHT - AMBER PILOT LIGHT - RED PILOT LIGHT RAU

1/2

Euclid, Ohio

Frac. 1/64 .xx

Engineer Date 05/01/99

.010

C .xxx .xxxx

Rev. February 2007

.005 .0005

B A

Changed Wire Changed Wire Added lights

2/10/02 1/15/02 2/12/01 Date

Approved By:

1756- OB16D SLOT 4 Digital Onput Wiring Diagram


A--4

I/O Wiring Diagrams

Slot 7 - 1756-OF6VI Analog Output WORKSTATION DEVICE

WORKSTATION DEVICE OUT-1

2

1

OUT-0

NOT USED

4

3

NOT USED

RTN-1

6

5

RTN-0

OUT-3

8

7

OUT-2

NOT USED

10

9

NOT USED

RTN-3

12

11

RTN-2

NOT USED

14

13

NOT USED

OUT-5

16

15

OUT-4

NOT USED

18

17

NOT USED

RTN-5

20

19

RTN-4

AO1 (Channel 1)

AO0 Return

AO0 (Channel 0)

AO1 Return

AO0 = Local:7:O.Ch0Data AO1 = Local:7:O.Ch1Data

Angle

RAU

1/2

Euclid, Ohio

Frac. 1/64 Engineer .xx

C .xxx .xxxx


.005 .0005

Approved By:

Date 05/01/99

.010

B A Rev.

Changed Wire Changed Wire

2/10/02 1/15/02

1756- OF6VI Slot 7

Ad de d lig ht s

2/12 /01 Date

Analog Output Wiring Diagram


I/O Wiring Diagrams

A -- 5

Slot 8 - 1756-IF6VI Analog Input WORKSTATION DEVICE

AI1 (Channel 1)

WORKSTATION DEVICE IN-1/V

2

1

IN-0/V

IN-1/I

4

3

IN-0/I

RET-1

6

5

RET-0

IN-3/V

8

7

IN-2/V

IN-3/I

10

9

IN-2/I

RET-3

12

11

RET-2

NOT USED

14

13

NOT USED

IN-5/V

16

15

IN-4/V

IN-5/I

18

17

IN-4/I

RET-5

20

19

RET-4

AI0 (Channel 0)

AI0 Return

AI1 Return

AI0 = Local:8:I.Ch0Data AI1 = Local:8:I.Ch1Data

Angle

COMPRESSOR ASSEMBLY, CO.

1/2

Euclid, Ohio

Frac. 1/64 .xx .xxx .xxxx

Rev. February 2007

Engineer

Approved By:

.010 .005 .0005

C B A Rev.

Changed Wire Changed Wire Added lights

2/10/02 1/15/02 2/12/01 Date

1756- IF6VI Slot 8 Analog Iutput Wiring Diagram


A--6

I/O Wiring Diagrams



Appendix

B

ControlLogix Workstation I/O Device Assignments The following standard ControlLogix workstation inputs and outputs are used in this course (Local I/O tags are listed on the next page):

9 I3 O D D

) 2 to l S o t d e ir W ll (A h ig R o t ft e L n u R s t u p In

) 4 to l S n i 1 1 6 ( s t u p t u O ) 0 t lo S in 5 0 ( s t u tp u O

t u p In

g lo a n A 0 0 h C

t u p t u O r e t e M

re t e M

I7 D

2 I D

6 O D

6 I D

I1 D

3 O D

I5 D

0 I D

Rev. February 2007

g lo a n A 0 0 h C

0 O D

I4 D

0 1 O D

7 O D

4 O D

1 O D

g o l a n A 1 0 h C

t u p n I re t e M

g lo a n A 1 0 h C

t u p t u O r e t e M

1 1 O D

5 1 I D

0 1 I D

8 O D

4 I1 D

I9 D

5 O D

3 1 I D

2 O D

2 I1

1 I1 D

8 I D

D

E 2007 Rockwell Automation, Inc. All rights reserved. WI3a56r

B--2

ControlLogix Workstation I/O Device Assignments

Local I/O Tags

The devices used in the workstation have the following I/O base tags: Module

Digital Input wired to Slot 2

Workstation Device

DI7 DI8

Local:2:I.Data.0 Local:2:I.Data.1 Local:2:I.Data.2 Local:2:I.Data.3 Local:2:I.Data.4 Local:2:I.Data.5

DI6

Local:2:I.Data.6 Local:2:I.Data.7 Local:2:I.Data.8 Local:2:I.Data.9 Local:2:I.Data.10 Local:2:I.Data.11 Local:2:I.Data.12 Local:2:I.Data.13 Local:2:I.Data.14

DI9 DI10 DI11 DI12 DI13 DI14 DI15 D00 D01 Digital Output wired to Slot 0

Digital Output wired to Slot 4


I/O Base Tag

DI0 DI1 DI2 DI3 DI4 DI5

D02 D03

Local:2:I.Data.15 Local:0.O.Data.0 Local:0.O.Data.1 Local:0.O.Data.2 Local:0.O.Data.3

D04 D05 D06

Local:0.O.Data.4 Local:0.O.Data.5 Local:4:O.Data.6

D07

D010

Local:4:O.Data.7 Local:4:O.Data.8 Local:4:O.Data.9 Local:4:O.Data.10

D011

Local:4:O.Data.11

D08 D09

Rev. February 2007 WI3a56r

Appendix

C

Node Assignments If you are in an environment with multiple workstations on a ControlNet or EtherNet/IP network, ask your network specialist to supply the following information : EtherNet or EtherNet/IP Network Workstation Number

1756-ENET IP Address

ControlN et Network 1756-CNB or 1756-CN2 Node Address*

1784-PCICS Card Node Address

1784-PCC Card Node Address

1784-KTCX15 Interface Card

1

2

3

4

5

6

7

8

9

10

Rev. February 2007

E 2007 Rockwell Automation, Inc. All rights reserved. NO3a56r

C--2

Node Assignments


Rev. February 2007 NO3a56r

The following are trademarks of Rockwell Automation, Inc.: 1336FORCE 1336PLUS ControlBus DataHighwayPlus DriveTools Flex Logix5000 PanelBuilder PLC-5 PowerFlex RSLinx RSView SCANPort SoftLogix

1336IMPACT CompactLogix ControlLogix DH+ FactoryTalk FlexLogix Logix5550 PanelView PHOTOSWITCH RediSTATION RSLogix RSNetWorx SLC Ultra

ControlNet is a trademark of ControlNet International Ltd. DeviceNet is a trademark of the Open DeviceNet Vendor Association, Inc. (ODVA). The following are registered trademarks of Microsoft Corporation: MS-DOS Windows

PowerPoint WindowsNT

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

Catalog Number TT--13664 April 2007

E 2007 Rockwell Automation, Inc. All rights reserved. Printed in USA

CONTROLLOGIX

Recommend Documents