Logix Fundamentals Labs

RcSI Workshop 2012
Fundamentals of Logix Labs
Learn how to use RSLogix to reduce

engineering time and cost
Publication Number -- Date Copyright © 2012 Rockwell Automation, Inc.

Table of Contents
TABLE OF CONTENTS___________________________________________________________ 3
INTEGRATED ARCHITECTURE – COMPACT MACHINE SOLUTIONS (90 MINUTES) ________________ 5
WHAT IS INTEGRATED ARCHITECTURE ?__________________________________________ 5
ABOUT THIS HANDS-ON LAB __________________________________________________ 6
BEFORE YOU BEGIN ________________________________________________________ 6
LAB MATERIALS ___________________________________________________________ 7
DOCUMENT CONVENTIONS ____________________________________________________ 7
LAB 1: CREATING A NEW PROJECT (20 MINUTES) _____________________________________ 8
ABOUT THIS LAB ___________________________________________________________ 8
LAUNCHING RSLOGIX™ 5000 PROGRAMMING SOFTWARE ____________________________ 8
CREATING A NEW CONTROLLER PROJECT ________________________________________ 9
ADDING LADDER LOGIC TO THE MAIN ROUTINE ___________________________________ 11
CREATING TAGS FOR THE LADDER CODE ________________________________________ 17
MONITORING/EDITING TAGS __________________________________________________ 23
LAB 2: CONFIGURING I/O (15 MINUTES) ____________________________________________ 26
ABOUT THIS LAB __________________________________________________________ 26
ADDING COMPACTLOGIX I/O _________________________________________________ 26
LAB 3: CONNECTING YOUR COMPUTER TO THE CONTROLLER (5 MINUTES)__________________ 41
ABOUT THIS LAB __________________________________________________________ 41
LAUNCHING RSLINX SOFTWARE ______________________________________________ 41
ADDING THE AB_ETHIP-1 (ETHERNET/IP) DRIVER ________________________________ 42
LAB 4: LOADING THE PROJECT FROM THE COMPUTER TO THE CONTROLLER (5 MINUTES) ______ 44
LAB 5: TESTING YOUR LOGIC PROGRAM (5 MINUTES) _________________________________ 46
ABOUT THIS LAB __________________________________________________________ 46
PUTTING THE CONTROLLER INTO RUN MODE AND TESTING THE PROGRAM _______________ 47
LAB 6: ADDING LOGIC AND TAGS ONLINE (10 MINUTES) _______________________________ 50
ABOUT THIS LAB __________________________________________________________ 50
ADDING A TIMER TO THE LOGIC _______________________________________________ 50
LAB 7: CREATING AND RUNNING A TREND (5 MINUTES) ________________________________ 58
ABOUT THIS LAB __________________________________________________________ 58
CREATING AND RUNNING A TREND _____________________________________________ 58
LAB 8: CREATING AND USING USER-DEFINED DATA TYPE (5 MINUTES) ____________________ 63
ABOUT THIS LAB __________________________________________________________ 63
CREATING NEW USER-DEFINED DATA TYPE _______________________________________ 63
LAB 9: ADDING POINT I/O. IMPORTING ADD-ON INSTRUCTION. (10 MINUTES) ________________ 66
ABOUT THIS LAB __________________________________________________________ 66
ADDING POINT I/O ON ETHERNET/IP USING RSLOGIX 5000 SOFTWARE _________________ 66
IMPORTING ADD-ON INSTRUCTION _____________________________________________ 74
LAB 10: DOWNLOADING THE RUNTIME FILE TO THE PANELVIEW PLUS. TESTING APPLICATION
(5 MINUTES) 77
Logix fundamentals_labs
April 5, 2012 Page 3 of 82
ABOUT THIS LAB __________________________________________________________ 77
TESTING THE APPLICATION ON THE DEMOBOX ____________________________________ 78
LAB 11: USING RSLOGIXTM 5000 HELP (5 MINUTES) __________________________________ 79
ABOUT THIS LAB __________________________________________________________ 79
INSTRUCTION HELP ________________________________________________________ 79
USING ONLINE REFERENCE MATERIALS _________________________________________ 80
3RD PARTY VENDOR SAMPLE PROJECTS _________________________________________ 81
QUICK START, LEARNING CENTER, RESOURCE CENTER _____________________________ 81
APPENDIX A – DESCRIPTION OF DOCUMENT CHANGES ______________________________ 82
Integrated Architecture – Compact machine
Solutions (90 minutes)
What is Integrated Architecture ?
Integrated Architecture is a concept that allows automation components to be used as stand-
alone control devices or combined together as an integrated system based on a common set of
enabling technologies.
Integrated Architecture brings together an outstanding range of pre-integrated components and
systems to help today's manufacturing enterprises across a wide range of industries. The
Integrated Architecture technologies are the core of a robust system:
LOGIX is the Control Platform based on the same control engine embedded in scale-
able controllers using a single programming environment
NETLINX is the Communication Platform based on the Open Networks integrated to
Control, Configure & Collect data
FACTORYTALK is the Visualization & Information Platform. This technology is a
unified, scalable and extensible HMI platform using a single development environment.
Furthermore it integrates control systems and connects the enterprise with the production
facility
Rockwell’s Integrated Architecture provides all the control you need in one package:
Distributed Control Functionality for:
o Global Access to data
o Deterministic control
o Distributed HMI
o Extensive library of process control algorithms (Function Blocks)
Programmable Controller Flexibility for:
o An optimized maintenance & troubleshooting with the source stored in controller,
tag based
o Integrated Drives and Motion control
o Standalone operation
o Scalable architecture
o Interfaces to many devices
About This Hands-On Lab
This Hand-On-Lab will introduce you to the Logix programming basis. In this lab you will learn
how to use RSLogix5000 programming software to create a user program. You'll write a ladder
logic program and see how symbolic tag name addresses makes your program more user
friendly. Then you will also download the configuration to a Logix controller and examine a
controller tag database.
Before You Begin
Before you begin this Hands-On Lab, please be sure to close any applications that are currently
running.
To complete this lab, a general familiarity of computers, programmable controllers, I/O and
automation software is recommended but not essential.
Lab Materials
For this Hands-On lab, we have provided you with the following materials that will allow you to
complete the labs in this workbook.
Hardware
Compactlogix L35E, Controllogix L6x
Computer or laptop equipped with:

 Windows 7
 RSLogix 5000 v20.00
 RSLinx Professional v2.59
 Factory Talk View Studio v6.1
Files
Pump_Management.L5X The file containing Add-On instruction used in the lab.
Fund_of_Logix.mer Compiled FTView file.
Document Conventions
Throughout this workbook, we have used the following conventions to help guide you through the
lab materials.
This style or symbol: Indicates:

Words shown in bold (e.g., IO Any item or button that you must :
Configuration or OK) - Click on, or a menu name from which you must choose an
option or command. This will be an actual name of an item
that you see on your screen or in an example.
- Type in the specified field. This is information that you must
supply based on your application (e.g., a variable).
The text that appears inside of this gray box is supplemental information
regarding the lab materials, but not information that is required reading in
order for you to complete the lab exercises. The text that follows this
symbol may provide you with helpful hints that can make it easier for you to
use this product. Most often, authors use this “Tip Text” style for important
information they want their students to see.
Note: If the mouse button is not specified in the text, you should click on the left mouse button.
Lab 1: Creating a New Project (20 Minutes)
About This Lab
In this lab, we will introduce you to the Logix product family. In this lab you will:
 Create a new project
 Write ladder logic
 Use symbolic tag names
 Use the tag monitor/editor
Launching RSLogix™ 5000 Programming Software

In this section of the lab, you will launch the RSLogix™ 5000 software, which will allow you to
program a processor.
1. Double-click on the RSLogix 5000 icon on the computer desktop to launch

RSLogix 5000 software.
2. Create a new RSLogix 5000 project by selecting File > New… from the toolbar menu.
Creating a New Controller Project
In this portion of the lab, you will create a project offline. You will download the project to the
CompactLogix controller in the second part of the lab.
3. Make the following changes and select OK. Verify your processor type (on the top of the
CompactLogix CPU), and select your processor in the following drop down box. i.e. 1769-
L32E or L35E.
FYI
New Controller
From the New Controller window you are defining the project.
Type: This is the type of Logix controller you will use. This could be a ControlLogix,
FlexLogix, CompactLogix, DriveLogix, or SoftLogix controller. Only one programming
software package is needed for all Logix Controllers.
Revision: Here you are selecting the firmware revision that the project will be created
with. Revision 19 is the latest one.
Name: The name of the controller and the project.
Chassis Type: Select the size of the chassis you will use. This is not applicable for the
rack-less controllers.
Slot: The slot number that you wish the controller to be installed in. This is not applicable
for all controller types. For example, CompactLogix is fixed at slot zero.
The Controller Organizer appears on the left side of the RSLogix™5000 window, with a folder
called Controller Fund_of_Logix. You have now created your first controller project. At this
time, there is no I/O, no tag database, and no logic associated with the controller.
FYI
The Controller Organizer is a graphical representation of the contents of your

controller project. This display consists of a tree of folders and files that contain
all of the information about the programs and data in the current controller
project. The default main folders in this tree are:
 Controller File Name
 Tasks
 Motion Groups
 Add-On Instructions
 Data Types
 Trends
 I/O Configuration
 In front of each folder, there is a square containing a + sign or a - sign. The
+ sign indicates that the folder is closed. Click on it to expand the tree display
and display the files in the folder. The - sign indicates that the folder is already
open and its content is visible.
Adding Ladder Logic to the Main Routine

In this section you will add code for a simple motor start/stop seal in circuit.
During the labs we will only utilize ladder logic programming, but Logix controllers also can be
programmed using Function Block, Sequential Function Charts, and Structured Text. You can
select which program language best fits your application.
You will continue to use the project already opened.

4. In the Controller Organizer expand the MainProgram folder by clicking on the +.
5. Once expanded, the MainProgram will appear as shown below:
6. Double-click on the MainRoutine icon.
This will open the routine editor. An empty rung will be added for you as shown below:
7. From the instruction toolbar, left click and hold on the Examine if Closed (XIC) instruction
8. Drag the XIC onto rung 0 until the green dot appears as shown above. Release the mouse
button at the location you wish to place your instruction.
Verify that your rung appears like the figure below:
9. From the instruction toolbar left click and hold on the Examine if Open (XIO) instruction
.
10. Drag the XIO onto rung 0 to the right of the XIC instruction as shown above. Again a green
dot will appear to the right of the XIC instruction indicating where your new instruction will be
inserted. Release the mouse button at the location you wish to place your instruction.
11. Verify your rung appears like the figure below:
FYI
If you place an instruction in the wrong location on a rung simply click and hold
on the instruction and drag it to the correct location.
12. From the instruction toolbar, left click and hold on the Output Energize (OTE)
instruction.
13. Drag the OTE onto rung 0 to the right of the XIO instruction as shown above. Again a green
dot will appear to the right of the XIO instruction indicating where the OTE instruction will be
inserted. Release the mouse button at the location you wish insert the instruction.
14. Verify your rung appears as shown below:
We will now add a branch around the XIC instruction.
15. Click on the XIC instruction to select it as shown below:
16. From the instruction toolbar click on the Branch instruction .

A branch will be inserted on the rung.
17. Left-click and hold on the blue highlighted part of the branch and drag your selected leg of
the branch to the left side of the XIC instruction. Place the branch over the green dot and
release the mouse button.
18. From the instruction toolbar, left click and hold on the XIC instruction.
19. Drag the XIC onto your newly created branch until the green dot appears.
The rung should now appear as shown below.
You have completed adding the rung.
20. Verify that the entire rung appears like the figure below.
21. Save the program by clicking File > Save As on the toolbar and enter the name
‘Fund_of_Logix.ACD’. Save your program in the directory named
Fundamentals_of_Logix: C:\Documents and Settings\All
Users\Documents\CMS_Files\Fundamentals_of_Logix
As you can see the free form editing in RSLogix 5000 can help speed
development. You no longer have to place an instruction and tie an
address to it before you add the next instruction.
Creating Tags for the Ladder Code
In this section of the lab you will create tags needed for the program. In traditional PLCs, a
physical memory address identifies each piece of data, for example N7:0. In Logix controllers,
there is no fixed numeric format. We use tags.
FYI
What is a tag and why is it better?

A tag is a text-based name for an area of memory. By using a text-based system
you can use the name of the tag to document your ladder code and organize
your data to mirror your machinery. For example you could create a tag named
North_Tank_Pressure. This helps to speed code generation and debugging. All
tag names are stored in the controller.
We will create 3 tags for the program: Motor_Start, Motor_Stop, and Motor_Run.
22. First you will create the tag Motor_Start. Right click on the ? of the first XIC instruction and
select New Tag.
23. The New Tag window will appear.
FYI
Creating a Tag
When you create a tag there are several attributes for a tag. The main attributes
we are interested in for this lab are as follows:
Tag Type: Defines how the tag operates within the project
Base: Stores a value or values for use by logic within a project
Alias: A tag that represents another tag
Produced: Send data to another controller
Consumed: Receive data from another controller
Data Type: Defines the type of data that the tag stores. For example Boolean,
Integer, Real, String, etc.
Scope: Defines how the data is accessed in the project. Is it either controller
scoped, global data accessible throughout the controller or program scoped,
data accessible for a specific program.
External Access: Defines how an external application (non-RSLogix 5000), such
as an HMI, Historian, or OPC data server, can access a tag inside the controller:
Read/Write: External applications can read and modify the tag’s value
Read Only: External applications can read the tag value, but not modify it
None: External applications do not have access to the tag (neither read nor
write)
24. Enter the parameters as shown below.
25. Click on OK to accept and create the tag.

The rung will now look like the figure below.
Next you will create the tag Motor_Stop.
26. Right click on the ? of the XIO instruction and select New Tag.
The New Tag window will appear.
27. Enter the parameters as shown below:

29. Verify the rung appears like the figure below:
You will now create the tag Motor_Run.

30. Right click on the ? of the OTE instruction and select New Tag.
The New Tag window will appear.
31. Enter the parameters as shown below:
Your rung should now appear as shown below:
For the XIC instruction in the branch we do not have to create a tag. You will use the tag
Motor_Run.
33. Left click and hold the mouse button over the tag Motor_Run on the OTE instruction.
34. Drag the tag Motor_Run tag over to the XIC instruction until a green dot appears next to the
?.. Then release the mouse button.
Your rung should now appear as shown below.
Notice the ‘e’s next to rung zero disappeared. RSLogix 5000 software verifies each rung
automatically when you finish inserting elements in it. This makes programming easier.
35. Save the program by clicking on the Save icon on the toolbar.
The tag database of Logix versus a traditional PLC’s fixed memory

addresses help you create self-documenting code. This means you do not
have to use address descriptions or symbols to make code easy to read.
Monitoring/Editing Tags
In this section of the lab, we will review the Tag Monitor/Editor in RSLogix™ 5000. We will also
discuss the concept of Controller versus Program scoped tags.
36. From the Controller Organizer double-click on Controller Tags.
The tag Monitor/Editor window appears. You notice in the lower left corner of the window two
tabs labeled Monitor Tags and Edit Tags as shown below.
FYI
Monitor/Edit Tags Tabs

When the ‘Monitor Tags’ tab is selected the actual value(s) for the tags will be
shown. For example, if you were to view an input button the software would show
the button tag actively energized or de-energized.
When the ‘Edit Tags’ tab is selected, NEW tags may be created, and existing tag
properties may be modified.
If you are having difficulty creating or modifying tag parameters, verify that the
‘Edit Tags’ tab is selected.
You notice first that there are no tags present, but you remember just created 3 tags.
Notice a field in the upper left corner of the Tag Editor window labeled Scope. Earlier in the
lab we talked briefly about Controller and Program scoped tags. Currently the selection is
Fund_of_Logix.
When we created the tags earlier we created them in the Program Scope.
FYI
Data Scoping
When you create a tag, you define it either as a controller tag (global data) or a
program tag for a specific program (local data).
Data at the program scope is isolated from other programs. Routines cannot
access data that is at the program scope of another program. Thus you can re-
use the tag name of a program-scoped tag in multiple programs.
37. Click on the down arrow for the Scope selection box.
38. Select MainProgram.
The Tag Editor now has switched views to the program level and you see the tags you
created earlier.
Congratulations! You have Completed Lab 1.

Please move on to Lab 2.
Lab 2: Configuring I/O (15 Minutes)
About this Lab
We will now look at configuring I/O for our project. To communicate with I/O modules you must
add modules to the I/O Configuration folder.
For this lab we will add the following I/O modules.
 1769-IQ16F: 16 Point 24VDC input module in slot 1

 1769-OB16P: 16 Point 24VDC output module in slot 2
 1769-IF4XOF2: Analog I/O Combination module in slot 3
Adding CompactLogix I/O

In this section of the lab, you will:
 Add CompactLogix I/O to your application
 View the I/O tags that were automatically created
 Learn about tag aliasing
Adding CompactLogix I/O

1. From the Controller Organizer, right click on CompactBus Local and select New Module.
The Select Module window appears as shown below:
2. Scroll through the list Digital until you locate the 1769-IQ16F.
3. Select the 1769-IQ16F module.
4. Click OK.
The Module Properties Wizard will appear for the 1769-IQ16F.
FYI
Module Configuration Wizard

Whenever you add an I/O module to the system you will go through the Module
Configuration Wizard. The Wizard allows you to step through the entire
configuration needed for a module. You can access this information later by
double clicking on a module in the I/O Configuration folder or through the tag
monitor/editor.
In Logix there are no more dip switches or jumpers needed to configure I/O
modules. I/O modules are software configured. This saves time when setting up
a system. The configuration for all modules is part of the controller’s program
and is downloaded to the module from the controller; this allows for ease of
replacement if an I/O module fails.
5. Enter the Name and Slot as shown below.
FYI
Name
Note that the Name can be any unique IEC 1131-3 compliant alpha-numeric
name that the user wants. IEC1131-3 basically says that it must begin with an
alpha character, can only be a maximum of 40 characters long and cannot
contain certain characters like % or #.
6. Click on the Change button and make sure the Electronic Keying information is set to
Compatible Module as shown below, and then click OK.
FYI
Connection
Determines the data structure for the tags that are associated with the module.
Many I/O modules support different formats. Each format uses a different data
structure.
Electronic Keying
When you insert a module into a slot of a chassis, the controller compares the
information read from the newly inserted module with what the user configured
that particular slot to be in their project. The following data is read and
compared:
Vendor, Product Type, Catalog Number, Major Revision, Minor Revision.
The user may select one of the following module keying options during the initial
module configuration:
Exact Match – all of the parameters described above must match or the inserted
module will reject the connection.
Compatible Module – The following criteria must be met, or else the inserted
module will reject the connection: Module Types, Catalog Number, and Major
Revision must match and the Minor Revision of the physical module must be
equal to or greater than the one specified in the software
Disable Keying – No keying used at all.
7. Click on the Connection tab to view the Requested Packet Interval data.
FYI
Requested Packet Interval (RPI)

The Requested Packet Interval (RPI) specifies the frequency at which data is
updated to and from the module. RPIs are configured in milliseconds. The
range is 1ms to 750ms for this particular module.
8. Take a quick look at the Connection menu and uncheck the “Major Fault on Controller if
Connection Fails checkbox”. By disabling this feature we prevent the controller to go in major
fault state if the module is disconnected from the chassis.
Major Fault on Controller if Connection

Fails checkbox
Check this box to configure the controller
so that failure of the connection to this
module causes a major fault on the
controller if the connection for the module
fails.
Note: This checkbox is automatically
checked for all 1769 I/O modules and the
CompactBus Virtual Backplane adapter.
9. Click OK to accept.
In the Controller Organizer, the I/O Configuration folder should appear as follows:
10. From the Controller Organizer, right click on CompactBus Local and select New Module.
11. Scroll through the list Digital until you locate the 1769-OB16P.
12. Select the 1769-OB16P module.
13. Click OK.

14. The Module Properties Wizard will appear for the 1769-OB16P. Enter the Name and Slot
as shown below.
15. Click on the Change button and make sure the Electronic Keying information is set to
Compatible Module as shown below, and then click OK.
16. Click on the Connection tab to view the Requested Packet Interval data.
17. Click OK to accept.
18. Add another module in Slot 3. Now take the 1769-IF4XOF2 in the Analog section
19. Go to the Input Configuration tab and enable Channel 1.
20. Go to the Output Configuration tab and enable Channel 1.
21. Click OK to close this properties window. Your IO configuration should look like this:
Viewing the I/O Tags Just Created

Now that we have configured CompactLogix I/O modules in the project, let’s take a look how that
information is presented in RSLogix™ 5000.
22. From the Controller Organizer double click on Controller Tags.
23. The tag editor window will appear.
Drag to the right to increase
the size of the Tag Name
field. This will allow you to
view the entire Tag Name.
FYI: I/O Address Format
You notice by looking in the upper left corner of the tag editor that you are in the Controller
Scope. All I/O module tags are created in the Controller Scope.
24. Switch to Monitor Tags by Clicking on the Monitor Tags Tab.
The above entries are tag structures for the modules you added. They contain more tags than
are actually displayed. Note the + sign next to the tag name, this indicates that you can expand
the tag structure to see more information.
25. Expand and explore the tags for the I/O modules by clicking the +.
What you will find under the Configuration tags, for each module, is all the data, you entered
and selected from the Module Configuration Wizard.
Assigning Alias Tags

In this section of the lab you will learn about Alias Tags.
FYI
Aliasing
An Alias tag lets you create one tag that represents another tag.
 Both tags share the same value
 When the value of one of the tags changes, the other tag reflects the change
Use Aliases in the following situations:
 Program logic in advance of wiring diagrams
 Assign a descriptive name to an I/O device
 Provide a simpler name for a complex tag
 Use a descriptive name for an element of an array
26. From the Controller Organizer double click on MainRoutine.
The ladder editor appears as shown below:
In the last part of the lab we added I/O modules to the project. Now lets Alias the tags in the
program to the I/O Modules.
 Motor_Start will be Aliased to input point 0 of the 1769-IQ16F in Slot 1.

 Motor_Stop will be Aliased to input point 1 of the 1769-IQ16F in Slot 1.
 Motor_Run will be Aliased to output point 0 of the 1769-OB16P in Slot 2.
27. Right click on the tag Motor_Start and select Edit “Motor_Start” Properties.
The Tags Properties window for Motor_Start will appear.
Currently the tag is defined as a Base tag.
28. Change the Type to Alias and notice that the Tag Properties window changes.
29. Click on the down arrow for Alias For.

The tag browser appears.
You need to select your address from controller scoped tags. (Note: this window is resizable).
30. Make sure the Controller button is pressed.
The view on the screen will change to view your Controller Scoped Tags
31. Expand Local:1:I and select Local:1:I.Data.
32. Click the down arrow for Local:1:I.Data next to its data type (INT).
This will open the table of data points for the 1769-IQ16F module.
33. Select 0 from the table as shown below:
When you select 0 from the tag browser the window will close and the Tag Properties dialog
will appear as follows:
Motor_Start will now be aliased to Local:1:I.Data.0. This is the 1769-IQ16F in Slot 1.
34. Click on OK to close and apply the changes to the tag Motor_Start.
Look carefully at the tag Motor_Start in the ladder code. Under the tag Motor_Start you see <
Local:1:I.Data.0>. This means that Motor_Start has been Aliased to Local:1:I.Data.0. This
means that the tags are equivalent to one another in code. It is easier to read Motor_Start than
Local:1:I.Data.0.
35. Using the previous steps, alias the remaining two tags as follows:
 Motor_Stop = Local:1:I.Data.1
 Motor_Run = Local:2:O.Data.0
When you are finished, the ladder code should appear as follows.
37. Minimize RSLogix™ 5000 software.

Lab 3: Connecting Your Computer to the
Controller (5 Minutes)
About This Lab
In this lab, we will introduce you to the online operations that you will complete with the
RSLogix™5000 software. In this lab, you will:
 Launch RSLinx communications software
 Configure your communications driver
Launching RSLinx Software

In this section of the lab, you will launch the RSLinx software, which will enable you to configure
the driver you will use to communicate with the Logix processor in the Demo Box.
1. Launch RSLinx software from START > All Programs > Rockwell Software > RSLinx >
RSLinx Classic.
2. Click the RSWho icon .

The Rockwell Software RSLinx Gateway - [RSWho - 1] screen appears.
If in your RSWho window you can already see an Ethernet/IP driver, and in right pane you
can see devices like on the picture below you may skip this lab. Ethernet IP/driver is already
configured for you.
FYI
RSWho
The RSWho screen is actually RSLinx's network browser interface, which allows
you to view all of your active network connections.
The left pane of this display is the Tree Control, which shows networks and
devices in a hierarchical view. When a network or device is collapsed, as
indicated by the + sign, you can click on the + sign or double click on the network
or device icon to expand the view and begin browsing. When a network or
device is expanded, as indicated by the - sign, you can click on the - sign or
double click on the network or device icon to collapse the view.
The right pane of the RSWho display is the List Control, which is a graphical
representation of all of the devices present on the network.
Adding the AB_ETHIP-1 (Ethernet/IP) Driver

In this section of the lab, you will add the Ethernet/IP driver that you will use to communicate with
your Logix processor.
1. From the Communications menu, choose Configure Drivers.
The Configure Drivers dialog appears.
2. From the Available Driver Types pull-down menu, choose EtherNet/IP Driver then click on
the Add New button.
In RSLinx you will notice two different Ethernet drivers listed: EtherNet/IP Driver
and Ethernet devices. In general, you should use the new EtherNet/IP driver... it
will automatically scan for and find any EtherNet/IP compatible devices on the
network. A few older Rockwell Ethernet products cannot be found using this
driver. The older Ethernet devices driver works with all Rockwell Ethernet
products, but it will only scan for IP address that you manually tell it to search for.
You can have both types of drivers and/or multiple instances of each type active
in RSLinx at the same time if needed.
3. Click on OK to accept the default name (AB_ETHIP-1).
4. Ensure that the Browse Local Subnet radio button is enabled, select Windows Default
option and then click OK.
5. Exit the Configure Driver Dialog by clicking on Close.

Lab 4: Loading the Project from the Computer to
the Controller (5 Minutes)
In this section of the lab you will download the project.

1. Maximize RSLogix™ 5000 and your Fund_of_Logix project.
2. From the Communications menu, choose Who Active.
The Who Active Screen appears.
3. Expand the view by clicking on the ‘+’s until your screen appears as shown below. Locate the
1769-L32E / 35E Ethernet port with the IP address as detailed in Table A.
4. Click on the CompactLogix Processor, 1769-L32E or 35E controller in slot 00.
5. Click Download.
You will be asked to verify the download.
6. When the following prompt appears, click Download once more.
7. The project will then begin to download to your controller.
If your controller was in the RUN mode prior to the download, you may be
prompted to return to the RUN mode. If asked select YES.
At this point you will be online with the controller and the status LEDs will mimic the LEDs on your
controller.
8. Check that the I/O LED is solid green. If the LED is solid green proceed to the next lab.

Lab 5: Testing Your Logic Program (5 Minutes)
About This Lab
In this lab you will verify the operation of your program. You should be able to start and stop the
‘Motor’.
FYI
I/O Mapping
These are the push buttons on the Demo Box. The push buttons are mapped as
follows:
Motor_Run
Motor_Start Motor_Stop
Putting the Controller into Run Mode and Testing the Program
1. If not already in Run mode, from the Controller Faceplate select Run Mode and click OK.
The controller will go into run mode. This can be verified by looking at the Run LED on the
controller. It should now illuminate green. It can also be verified through RSLogix™ 5000 by
viewing the controller faceplate.
You notice that this is a replica of your controller’s faceplate.

2. From the Controller Organizer expand the MainProgram by clicking on the “+”.
3. Double-click on the MainRoutine to bring up the ladder editor.
Note:
To make the following section of the lab clearer, we show screenshots with
aliased addresses being hidden. In your program you will actually see the alias
addresses you configured earlier in the lab exercise. Leave the aliases
unchanged.
You will now see the ladder logic. Notice the green power rails on both sides of the ladder.
This indicates you are online and the routine is executing.
You notice that the XIO instruction Motor_Stop is green. This means that this instruction is
in the ‘true’ or ‘on’ state. This is because the Motor_Stop Pushbutton is not pressed.
4. Press button Motor_Stop button on pushbutton panel.

This correlates to the XIO instruction for Motor_Stop. Notice it’s no longer green. This is
because the instruction is no longer evaluated as true.
5. Press button Motor_Start.

The XIC instruction will become true and turn green. Motor_Run will energize (turn green). And the pilot
light Motor_Run on your lab station will illuminate.
6. Verify that output Motor_Run stays illuminated when you release pushbutton
Motor_Start.
7. Press pushbutton Motor_Stop and verify that output Motor_Run turns off.
8. Save your program by clicking Save in the toolbar and close RSLogix™5000.
9. Click No when prompted about uploading tag values.

Lab 6: Adding Logic and Tags Online (10
Minutes)
About This Lab
In this lab you will perform online editing. You will:
 Add a timer to the logic and its execution will be based on the Motor running.
 Add ladder logic to reset the timer when the Motor is stopped.
 Read analog values from the potentiometer and display them on the numeric display. The
execution will be based on the Motor running.
Adding a Timer to the Logic

1. Right click in the blue area to the left of rung zero and select Start Pending Rung Edits.
The ladder editor will now look as follows:

The rung with the ‘i’s on the power rails, is the rung that you will perform the edits on.
2. Click the OTE instruction so it becomes highlighted.
3. From the Instruction Toolbar click on the Timer/Counter tab.
4. Click on the Timer On (TON) icon .

A timer is inserted into the code to the right of the OTE instruction.
In RSLogix™ 5000 you can string output instructions together. You do not have to create
branches.
5. When the Timer is selected insert the Move (MOV) instruction by clicking the MOV button on
the Instruction toolbar.
Your rung should now be like this:
6. In the Move instruction double click on the ? next to the Source and then click on the drop
down arrow. The drop down list appears as below:
7. Select the Local:3:I.Ch1Data (I for Input) as Source. For the Dest do the same, but select
Local:3:O.Ch1Data (O for Output).
With this instruction we move the value coming from the potentiometer (Local:3:I.Ch1Data)
to the output (Local:3:O.Ch1Data) that is displayed on the numeric display.
8. On the timer instruction right click in the blue area next to the word Timer and select New
Tag.
The New Tag window appears. You notice that the Data Type is already set to TIMER. This
is because you are creating a tag in a timer instruction.
9. In the Name field enter ‘Timer’ then click OK.
10. Verify that the tag has been created in the timer instruction as shown below:
11. Double-click on the 0, in the timer instruction, next to the word Preset.
12. Enter a value of 3600000.
In Logix the Timer Preset is a 32-bit DINT which means the maximum value for
your timers can be: 2,147,483,647
13. Press Enter. Your TON instruction should now appear as shown below.
Your Preset value is now 3600000 milliseconds what corresponds to one hour. Leave the
accumulated value set to zero. You are now ready to verify the edits you made.
14. Click on the Finalize All Edits icon .

15. When asked to finalize all edits click on Yes.
The ladder editor will now appear as follows:
We now want to add a rung that will reset the timer when the Motor_Stop (DI1) is pushed.
16. Right click on the (End) rung and select Add Rung.
A new rung will appear in the ladder editor.
17. From the Instruction Toolbar, click on the
RES icon .
This will place a Timer-Reset instruction on the rung.
18. From the timer instruction on rung zero, click and hold on the word Timer.
19. Drag the tag name Timer to the RES instruction, a green dot will appear next to the
instruction. Release the mouse button.
20. Right click on the XIO (Motor_Stop) instruction on rung zero and select Copy Instruction.
21. Right click to the left of rung 1 and select Paste.
22. Double-click on the pasted XIO instruction.
The instruction can now be edited.

23. Type ‘XIC’ in place of XIO.
24. Press Enter when finished.
The rung should now appear as shown below.
You are now ready to accept the program edits you have made.
25. Click on the Finalize All Edits icon .

26. When the next dialog box appears, click Yes. This allows the software and controller to
assemble your edits.
The code should now appear as shown below.
27. Test this program :

 Press the Motor_Start pushbutton.
 Verify that Motor_Run illuminates (the light on the demo case should be lit), the Timer
instruction starts incrementing and when you turn the potentiometer the value on the
numeric display will change. The value on the display is the 0-100% range.
 Now, press the push button Motor_Stop.
 Verify that Motor_Run turns off (light goes out), the Timer resets and you can no longer
change the value of the numeric display.
In this lab you learned how easy it is to add instructions and tags while you
are online with the controller.

Lab 7: Creating and Running a Trend (5 Minutes)
About This Lab
In this lab you will use the built-in trending capabilities of RSLogix™ 5000.
In this Lab you will:
 Create a trend to watch the Timer instruction’s accumulated value.
This will be done online with the program from the previous Lab.
FYI
Trending
Basic Trending in RSLogix™ 5000 allows you to view data sampled over a time
period in a graphical display. Data is sampled at a periodic rate that is
configurable from 10 milliseconds to 30 minutes. RSLogix™ 5000 will allow you
to create a trend and save it as part of your project file.
Basic Trending has these constraints: you can trend data elements of type
BOOL, SINT, INT, DINT, and REAL, you are limited to sampling eight unique
data elements, and you will be limited to one active trend at a time.
Creating and Running a Trend

1. From the Controller Organizer, right click on Trends and select New Trend.
The New Trend window appears.

2. In the Name field enter ‘Timer_Trend’.
3. Click Next.
The New Trend Add/Configure Tags window appears.
4. We want to trend the timer accumulate value. When you added the timer the tag was created
in the Program Scope, so we must select the MainProgram tags as shown below:
Now only the tags for the MainProgram are shown.
5. Expand the Timer tag by clicking on the +.

6. Select Timer.ACC and then click the Add button.
This will add the tag Timer.ACC to the Tags To Trend list.
7. Click on Finish.
The Trend window will now appear.
8. Start the trend by clicking on Run.

9. Start the Timer in the program by pressing the Motor_Start pushbutton on your demo box.
10. Verify that you see the Trend begin capturing the data of the Timer.ACC as shown below:
11. When you are finished investigating the trend, click Stop and close the trend window.

Lab 8: Creating and using User-Defined Data
Type (5 Minutes)
About This Lab
Now we will add two pumps to our system. In this lab you will create User-Defined Data Type
called Pump. This structure will keep all available data describing a pump.
FYI
User-defined data types are custom structures which let you organize your data
to reflect your machine or process specifics.
Creating new user-defined data type
1. Go Offline with your project.
2. In the Controller Organizer from the Data Types folder, right click on User-Defined and select
New Data Type….
3. Type ‘Pump’ as the Name of the new data type. Insert three members of newly created
structure and click Apply.
 Name type STRING

 Status_ON_OFF type BOOL
 Reset type BOOL
 Total_Working_Time type DINT
Your screen should look like on the picture below:
Click OK.
4. Double-click on Program Tags in MainProgram, and select Edit Tags and then type in new
the new tags: Pump_1 and Pump_2, selecting them as the Data Type that we newly created
: Pump. Click the button and select the Pump type from the list.
Your Program Tags should look similar to the picture below:

5. Switch your view to Monitor Tags. Expand Pump_1 and Pump_2 tags tag by clicking on the
+.
6. Type ‘Pump 1’ in Pump_1.Name and ‘Pump 2’ in Pump_2.Name. Use button to open

String Browser and insert these names. They will show up afterwards on your graphics
screen.
Your Program Tags should look like on the picture below:

Lab 9: Adding Point I/O. Importing Add-On
instruction. (10 Minutes)
About This Lab
In this lab we add into RSLogix our Point I/O, which is used as our distributed I/O. This will enable
you to use two more pushbuttons for pump control. The controller will decide which pump to start
based on the lower total working time of the two. The program logic is already provided with an
Add-On Instruction. The code is written in Function Block Diagram, so you can see that different
parts of the same project may be written in different programming languages.
In this lab you will:

 Add Point I/O on Ethernet/IP
 Import the Add-On Instruction Pump_Management.
Adding Point I/O on Ethernet/IP using RSLogix 5000 Software

1. The next step will be to configure the distributed Point IO node connected via the Ethernet/IP
network. From the Controller Organizer, right click on I/O Configuration1769-L32E or 35E
Ethernet Port LocalENBEthernet and select New Module…
2. From the list, expand the Communications directory, select the 1734-AENT module and
click OK.
3. The following window appears. Add a name to the module and fill the IP address as detailed
in Table A: Click on the Change button
FYI
Chassis Size
Select the appropriate number of modules connected to the communication adapter.
Today we will use the AENT adapter and 5 Point IO modules. So the chassis size is 6.
However Point I/O can have a maximum of 64 modules with extra power supplies.
Connection
Before we continue let’s have a discussion on Connection formats. There are several
ways of gathering data on Ethernet/IP. Depending on the type of module selected and
other factors you can have different Connection options available.
Rack Optimization: A method of establishing a connection to an adapter type device
that allows all discrete inputs to send data via this connection and allows all discrete
outputs to be controlled via this connection. After a Rack Optimized connection is
configured to an adapter each module that you desire to communicate through this
connection must also be selected as a Rack Optimized connection under the adapter.
The Rack Optimized connection is an efficient way to gather all selected inputs and
control all selected outputs in a single connection. A Rack Optimized connection will
only transfer discrete input and output data. If a discrete card has additional data like
status or diagnostics an individual connection must be used to gather the additional
data.
None: A method of establishing a connection to an adapter type device that allows
connections to be made to individual modules using individual connections. After a
None connection is configured to an adapter each module that you desire to
communicate through this connection must also be configured under the adapter using
any type of individual module connection.
Input Data:
This connection types allows a Controller to receive incoming data from the device. If
the connection is to an I/O device that requires configuration data, the configuration
data will be sent one time, when the connection is first established. Be sure that if
multiple connections (Input Data, Output Data or Rack Optimized) to the same device
exist, that the configuration data in all Controllers must be identical. The incoming data
does not need to already exist on the network. You can get Input Data with or without
an existing Owner connection (Rack Optimized, Input Data or Output Data).
Listen Only-Input Data:
This connection type allows multiple Controllers to receive incoming data from the
same device. No configuration data is sent with this type of connection. An Owner
connection (Rack Optimized, Input Data or Output Data) must already exist to the
device to produce Listen Only-Input Data. The transfer of this data is valid only if the
Owner connection is active. If the Owner connection goes away the Listen Only-Input
Data will no longer be produced. No additional EtherNet traffic is generated with this
connection.
Output Data:
One and only controller can send output data to an output device. An Output Data
connection to a device is the only connection that determines the mode (Prog or Run)
of that particular device. If the connection is to an I/O device that requires configuration
data, the Output Data connection will send the configuration data, one time, when the
connection is first established.
4. Picking Rack Optimization provides an efficient way of mapping the digital cards as one
connection. Click OK to return and you will get the warning
5. Click Yes. Now your screen display looks like this:

6. Click OK. As you configured the Communication Format for Rack Optimization, you need
to assign an RPI (Requested Packet Interval) to the AENT Adapter. Click on the
Connection tab. In our setup all the digital inputs and outputs will have an RPI of 2.0ms.
Click OK.
FYI
Requested Packet Interval (RPI)

The RPI is the rate that the user requests the data be moved to or from the module.
The minimum and maximum RPI values are shown parenthetically to the right of the
box/spin control. The RPI is entered by the user.
We will now add the Point I/O modules in the Point I/O chassis.
7. Right click on the 1734-AENT PointIO 6 Slot Chassis and select New Module….
8. Select the 1734-IB8 from the Digital folder and select OK. The following window appears.
Add a name as shown bellow:
9. Inspect also the other tabs. Notice the RPI setting in the Connection tab is grayed out.
Select OK to close the Module Profile configuration window. You saw how easy it is to
configure the digital input module! Then we will do the same for the digital output module in
slot 2 of the Point I/O chassis.
10. Right click on the 1734-AENT PointIO 6 Slot Chassis and select New Module…. Select
the 1734-OB4E from the Digital directory and select OK. Add a name as follow:
11. Select the Fault/Program Action tab, and change the Fault Mode of Channel 0 & 1 to ON.
12. Inspect also the other tabs. Notice the RPI setting in the Connection tab is greyed out.
Select OK to close the Module Profile configuration window. Now, we will configure the
Analog Input and Output Point I/O modules. Right click on the 1734-AENT PointIO 6 Slot
Chassis and select New Module…. Select the 1734-IE2V from the Analog directory and
select OK. Add a name as follow:
40. Select OK to close the Module Profile configuration window. Right click on the 1734-AENT
PointIO 6 Slot Chassis and select New Module…. Select the 1734-8CFGDLX from the
Digital directory and select OK. Add a name as follows.
13. Select OK to close the Module Profile configuration window. Right click on the 1734-AENT
PointIO 6 Slot Chassis and select New Module…. Select the 1734-VHSC24 from the
Speciality directory and select OK. Add a name as follows, and check the RPI in the
Connection tab is at 80.0ms. Click OK to close the Module Profile.
14. Now we’ve finished configuring our Point/IO chassis in the IO Configuration of our controller!
Verify that your I/O Configuration appears as follows:
15. Save your work by clicking the save icon at the top left of the RSLogix 5000 window.
Importing Add-On instruction
FYI
Add-On Instructions allow you to encapsulate your most commonly used logic as
sets of reusable instructions, similar to the built-in instructions already in the
Logix controllers. This saves time by allowing you to easily re-use sets of your
commonly used instructions in your projects and also helps promote consistency
in your projects since commonly used algorithms will all work in the same
manner, regardless of who is implementing the project.
Your Add-On Instructions may be created using the standard Ladder Logic,
Function Block Diagram, and Structured Text. Once created, an Add-On
Instruction may then be used in any of the RSLogix 5000 editors without any
additional effort on your part.
16. In the Controller Organizer point to Add-On Instructions and right click the mouse button.
Select Import Add-On Instruction option.
17. Browse Fundamentals of Logix folder, select Pump_Management.L5X file and click
Import.
Click OK on the next pop-up screen.

18. The Add-On instruction is now visible in Controller Organizer tree and is available for use on
the Add-On instructions tab.
19. You can double click on Logic icon in order view the logic of the Add-On
instruction. Use arrows to view next sheet of Add-On instruction.
20. Go back to Main Program, click on . Click on Rung 1 and add new rung to
your code by clicking icon.

21. From the Add-On tab drag the Pump_Management instruction onto the newly created Rung
2.
22. Create a new tag for Add-On instruction called Pump_Management. Type
‘Pump_Management’. Make sure the Scope is Main Program and click OK.
23. For START input create new tag Point_IO_Start. Change the Type to Alias, change the
Alias For to Point I/O input: Distributed_Control_Panel:1:I.0. Click OK.
24. For STOP input create new tag Point_IO_Stop. Change the Type to Alias, change the Alias
For to Point I/O input: Distributed_Control_Panel:1:I.1. Click OK.
After this operation the rung should look like on the picture below:
25. For Pump_1_Selected output argument, select the tag Pump_1.Status_ON_OFF.

26. Similarly link Pump_2_Selected to Pump_2.Status_ON_OFF.
27. Link Pump_1_Reset input argument to Pump_1.Reset.
28. Link Pump_2_Reset to Pump_2.Reset.
29. Link Pump_1_Overall_Time to Pump_1.Totall_Working_Time.
30. Link Pump_2_Overall_Time to Pump_2.Totall_Working_Time.
After these operations the Pump_Management Add-On instruction should look like on the
picture below:
31. Save the code. Download the code to the controller and go to Run mode.

Lab 10: Downloading the runtime file to the
PanelView Plus. Testing application (5 Minutes)
About This Lab
As creating a Panelview application is beyond the scope of this hands-on lab, an application has
already been created for you using FactoryTalk View Studio. In this lab you will download
Fund_of_Logix.mer runtime file to the PanelView Plus and test the application. using the Add-
On Instruction from the previous lab.
1. Launch Transfer Utility tool located in Start → Programs → Rockwell Software → Factory
Talk View → Tools → ME Transfer Utility.
2. Browse and select the Fund_of_Logix.mer file located in Fundamentals_of_Logix folder.

3. Check Run application at start-up and Replace communications options are marked.
4. Select PanelView Plus 600 at the IP address provided in Table A and click Download
button.
5. If the application already exists in the panel click Yes for overwriting.
6. Click Close on the panel in order to close information banner.
Testing the application on the Demobox
7. Make sure that CompactLogix controller is in RUN mode.
8. Press Point IO START button and observe on panel screen that Pump 1 is running, press
Point IO STOP button. Press Point IO START button again and observe that now Pump 2 is
running. The implemented Add-On instruction counts the total working time for both pumps
and selects the pump with lower total working time.

Lab 11: Using RSLogixTM 5000 Help (5 Minutes)
About This Lab
In this lab you will investigate the extensive online Help system in RSLogix™ 5000.
In this lab you will be viewing:
 Instruction help
 Module wiring diagrams
 On-line reference materials
rd
 3 party vendor sample projects
 The Quick Tour Tutorial
Instruction Help
1. From the Help pull down menu select Instruction Help.
The following window will appear.
2. Click on an instruction to locate its description, details about its parameters, and related
instructions along with examples on how to use the instruction.
Using Online reference materials
3. From the Help pull down menu select Online Books.
You will see the following literature available:
As part of the RSLogix™ 5000 software installion, there is an option to install the Online
reference materials. If these are installed they can be viewed here via RSLogix™ 5000 help.
4. Download different types of manuals available to you via this tool.
3rd Party Vendor Sample Projects
5. From the Help pull down menu select Vendor Sample Projects. The Adobe Acrobat viewer
rd
will open showing several 3 party modules allowing you to view and reuse sample programs
for RSLogix™ 5000.
6. When finished close Adobe Acrobat.
Quick Start, Learning Center, Resource Center

7. From the Help pull down menu select Quick Start.
If you ever require a refresher, the Quick Start is a great way to brush up on the basics of
Configuring RSLinx, Creating an RSLogix™ 5000 project and downloading to a controller.
CONGRATUALTIONS!!!
YOU HAVE COMPLETED

THE FUNDAMENTALS OF LOGIX LAB!
Appendix A – Description of Document Changes
HANDS-ON DOCS DESCRIPTION OF CHANGES PAGE
Fundamentals of Original document using RSLogix5000 v16 converted to CPR9.

Logix.doc
CMSW02ENv1.0.doc Above document with new numbering system
CMSW02ENv1.1.doc New Automation University front cover

Picture updated to Stratix 6000 switch. 6
Table A - IP Address table added, to allow lab to be used 6
networked or standalone. Reference to Table A added
Lab updated to RSLogix v17. Computer requirements changed.
8
Screenshots changed.
10
Added this Description of Changes table
Appendix
CE-DM092B-EN-P Named changed for DOCMAN
CE-DM092C-EN-P Upgraded for RSLogix v19

Changed Table A deleting ‘networked’ IP addressing 6
Author: M.Kaczorowski Point I/O slot 4 module changed 1734-8CFGDLX 8
Revisors: Added Lab 8 – Creating User Defined Data type 64
1. R.Mikołajczyk Added Lab 9 - Adding Point I/O. Importing Add-On instruction 67
2. D.Withenshaw Added Lab 10 - Downloading the runtime file to the PanelView 78
Plus
CE-DM092D-EN-P.doc Updated Table A & B with networked and standalone 6-7

18-03-2011 addressing.
Author: D.Withenshaw

Logix Fundamentals Labs

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Logix Fundamentals Labs

Uploaded by

Copyright:

Available Formats

RcSI Workshop 2012

Fundamentals of Logix Labs

Learn how to use RSLogix to reduce

Publication Number -- Date Copyright © 2012 Rockwell Automation, Inc.

Before You Begin

Computer or laptop equipped with:

This style or symbol: Indicates:

Launching RSLogix™ 5000 Programming Software

1. Double-click on the RSLogix 5000 icon on the computer desktop to launch

The Controller Organizer is a graphical representation of the contents of your

Adding Ladder Logic to the Main Routine

You will continue to use the project already opened.

5. Once expanded, the MainProgram will appear as shown below:

6. Double-click on the MainRoutine icon.

11. Verify your rung appears like the figure below:

14. Verify your rung appears as shown below:

15. Click on the XIC instruction to select it as shown below:

16. From the instruction toolbar click on the Branch instruction .

You have completed adding the rung.

What is a tag and why is it better?

25. Click on OK to accept and create the tag.

Next you will create the tag Motor_Stop.

28. Click on OK to accept and create the tag.

You will now create the tag Motor_Run.

Your rung should now appear as shown below:

The tag database of Logix versus a traditional PLC’s fixed memory

Monitor/Edit Tags Tabs

Congratulations! You have Completed Lab 1.

 1769-IQ16F: 16 Point 24VDC input module in slot 1

Adding CompactLogix I/O

Adding CompactLogix I/O

Module Configuration Wizard

5. Enter the Name and Slot as shown below.

Requested Packet Interval (RPI)

Major Fault on Controller if Connection

13. Click OK.

20. Go to the Output Configuration tab and enable Channel 1.

Viewing the I/O Tags Just Created

FYI: I/O Address Format

Assigning Alias Tags

The ladder editor appears as shown below:

 Motor_Start will be Aliased to input point 0 of the 1769-IQ16F in Slot 1.

29. Click on the down arrow for Alias For.

31. Expand Local:1:I and select Local:1:I.Data.

33. Select 0 from the table as shown below:

Congratulations! You have Completed Lab 2.

Launching RSLinx Software

2. Click the RSWho icon .

Adding the AB_ETHIP-1 (Ethernet/IP) Driver

3. Click on OK to accept the default name (AB_ETHIP-1).

5. Exit the Configure Driver Dialog by clicking on Close.

Congratulations! You have Completed Lab 3.

In this section of the lab you will download the project.

The Who Active Screen appears.

7. The project will then begin to download to your controller.

Congratulations! You have Completed Lab 4.

You notice that this is a replica of your controller’s faceplate.

3. Double-click on the MainRoutine to bring up the ladder editor.

4. Press button Motor_Stop button on pushbutton panel.

5. Press button Motor_Start.

Congratulations! You have Completed Lab 5.

You will continue to use the project already opened.

Adding a Timer to the Logic

The ladder editor will now look as follows: