Adding Local Hardware

Modules
 Important User Information
This documentation, whether, illustrative, printed, “online” or electronic (hereinafter “Documentation”) is intended for use only as
a learning aid when using Rockwell Automation approved demonstration hardware, software and firmware. The Documentation
should only be used as a learning tool by qualified professionals.

The variety of uses for the hardware, software and firmware (hereinafter “Products”) described in this Documentation, mandates
that those responsible for the application and use of those Products must satisfy themselves that all necessary steps have been
taken to ensure that each application and actual use meets all performance and safety requirements, including any applicable
laws, regulations, codes and standards in addition to any applicable technical documents.

In no event will Rockwell Automation, Inc., or any of its affiliate or subsidiary companies (hereinafter “Rockwell Automation”) be
responsible or liable for any indirect or consequential damages resulting from the use or application of the Products described in
this Documentation. Rockwell Automation does not assume responsibility or liability for damages of any kind based on the
alleged use of, or reliance on, this Documentation.

No patent liability is assumed by Rockwell Automation with respect to use of information, circuits, equipment, or software
described in the Documentation.

Except as specifically agreed in writing as part of a maintenance or support contract, equipment users are responsible for:
• properly using, calibrating, operating, monitoring and maintaining all Products consistent with all Rockwell Automation
or third-party provided instructions, warnings, recommendations and documentation;
• ensuring that only properly trained personnel use, operate and maintain the Products at all times;
• staying informed of all Product updates and alerts and implementing all updates and fixes; and
• all other factors affecting the Products that are outside of the direct control of Rockwell Automation.

Reproduction of the contents of the Documentation, in whole or in part, without written permission of Rockwell Automation is
prohibited.

Throughout this manual we use the following notes to make you aware of safety considerations:

Identifies information about practices or circumstances that can cause an explosion in a hazardous
environment, which may lead to personal injury or death, property damage, or economic loss.

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

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

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.
 Level 1: Logix - On Demand Adding Local Hardware Modules

Before You Begin

About this Lab

When we want our controller to read data from or write data to an I/O module, we simply add
and configure the module within the I/O Configuration of the Studio 5000 Logix Designer®
project. This is accomplished through the use of an Add-On Profile (AOP). AOPs are available
for most Rockwell Automation products, as well as many Encompass Partner products. No
additional software is required, and neither is the training for using separate software.
Furthermore, the methodology is consistent throughout the product line, from digital input
modules through Variable Frequency Drives (VFDs), making the process of integrating
hardware with a Logix 5000® controller extremely fast and easy. In this lab you will:
 Add local hardware modules
This lab takes approximately 20 minutes to complete.

Hardware
To complete this lab, you will require the following hardware:
 PC-based programming workstation with access to the RAcbi learning environment

Software
To complete this lab, you will require the following software:
 Studio 5000 Logix Designer version 32

Files
To complete this lab, you will require the following files:
 Machine_1_Lab10.ACD

Setup
To complete this lab, you will need to perform the following setup procedure:
1. Log on to your instance of the RAcbi learning environment.

© Rockwell Automation, Inc. All rights reserved. 1

 Adding Local Hardware Modules Level 1: Logix - On Demand

Add Local Hardware Modules

We want our controller to interact with digital inputs and outputs via the local, digital I/O modules
to which they are wired. Local modules are those modules which may communicate with the
controller strictly over the backplane network (i.e., they are located within the same chassis as
the controller). In this example, we need to add a local digital input module to which pushbuttons
and switches are wired. We also need to add a local digital output module to which indicators
are wired. In this section of the lab, you will add local hardware modules to the Controller
Organizer of a Logix Designer project.
1. If you have completed all labs up to this point in the Level 1: Logix - On Demand course,
then you may continue using your Machine_1.ACD file from previous labs:
a. Open the Studio 5000® environment.
b. Under Recent Projects, select your Machine_1 project:

1.b.

2. If you have NOT completed all labs up to this point in the Level 1: Logix - On Demand
course (e.g., you are just doing this individual lab as a refresher), then open the starting
file for this lab:

a. Use the shortcut on the desktop of your instance of the RAcbi learning
environment to open the LabFiles.
b. Open the Machine_1_Lab10.ACD file.

Prior to adding hardware to the I/O Configuration of our project, we will need to know the
catalog numbers and firmware revisions for the hardware. The RSLinx® Classic application is
one place we may look to discover this information.

3. Open the RSLinx Classic application.

2 © Rockwell Automation, Inc. All rights reserved.

Level 1: Logix - On Demand Adding Local Hardware Modules

4. Expand one of your Ethernet drivers:

© Rockwell Automation, Inc. All rights reserved. 3

Adding Local Hardware Modules Level 1: Logix - On Demand

5. Locate and expand the 1756-L85E controller:

4 © Rockwell Automation, Inc. All rights reserved.

Level 1: Logix - On Demand Adding Local Hardware Modules

6. Expand the Backplane:

© Rockwell Automation, Inc. All rights reserved. 5

Adding Local Hardware Modules Level 1: Logix - On Demand

7. Open the Device Properties for the digital input module (1756-IB16IF/A) in slot 3:

6 © Rockwell Automation, Inc. All rights reserved.

 Level 1: Logix - On Demand Adding Local Hardware Modules

8. Make note of the firmware Revision (your module’s firmware revision may differ from
what is shown below):

9. Close the Device Properties.

10. Use the same method to make note of the firmware revision of the digital output module
(1756-OB16IBF/A) in slot 4.

Now that we know the catalog numbers and firmware revisions of our I/O modules, we can
return to our Logix Designer project and begin the process of adding and configuring the
modules.

© Rockwell Automation, Inc. All rights reserved. 7

Adding Local Hardware Modules Level 1: Logix - On Demand

11. Within your Logix Designer project:

a. Locate the I/O Configuration within the Controller Organizer.
b. Right-click the Backplane.
c. Select New Module…:

8 © Rockwell Automation, Inc. All rights reserved.

Level 1: Logix - On Demand Adding Local Hardware Modules

12. In the Select Module Type window:

a. Begin typing ‘1756-IB16IF’ (the catalog number of the input module in slot 3) into
the search box.
b. When the list has narrowed down sufficiently, select the 1756-IB16IF catalog
number from the list.
c. Verify that the Close on Create checkbox is checked.
d. Click the Create button:

12.a.

12.b.

12.c.
12.d.

© Rockwell Automation, Inc. All rights reserved. 9

Adding Local Hardware Modules Level 1: Logix - On Demand

13. In the New Module window, configure the General properties of the module:
a. In the Name box, type in ‘DigitalInputs’.
b. For the description, type ‘Digital input module for Machine 1’.
c. Select Slot number 3.
d. Click the Change button:

13.a.
13.a

13.b. 13.c.
13.a 13.a

13.d.
13.a

10 © Rockwell Automation, Inc. All rights reserved.

Level 1: Logix - On Demand Adding Local Hardware Modules

14. In the Module Definition window:

a. Configure the Series and Revision to match your noted revision obtained from
the RSLinx Classic application (your module’s revision may vary from what is
shown below).
This configuration tells the controller which firmware revision to expect in the
input module.
b. Choose Compatible Module for the Electronic Keying.
Now when the controller first opens a connection to the module, it will make sure
that the vendor and catalog number match this configuration, and it will also
make sure that the actual firmware in the input module meets or exceeds the
firmware revision configured above. If these tests fail, the controller will not
communicate with the module.
c. For the Connection, select Data.
By choosing one of the data options, we are specifying that this controller owns
the input module. This means that this controller will write the configuration to the
module. If we had instead chosen one of the Listen Only options, then this
controller would only monitor the data coming from the module and another
controller would have to own the module.
d. Select Data for the Input Data.
This choice provides just the basic input data. The Timestamp Data option is an
advanced option available with this particular module. For this simple example,
we will not employ the more advanced option.
e. Click the OK button:

14.a.
13.a
14.b.
13.a

14.c.
13.a
14.d.
13.a

14.e.
13.a

© Rockwell Automation, Inc. All rights reserved. 11

 Adding Local Hardware Modules Level 1: Logix - On Demand

15. Click the Yes button to apply the changes:

16. Select the Connection category:

Within the Connection category, we have the option of altering the Requested Packet Interval,
or RPI. The RPI is the period at which the input module will communicate with the controller.
Thus, the lower we adjust this value, the more frequently the module will update the controller
and the more demand it will place on the Backplane network. The higher we adjust this value,
the less frequently the module will update the controller and the less demand it will place on the
Backplane network.

12 © Rockwell Automation, Inc. All rights reserved.

 Level 1: Logix - On Demand Adding Local Hardware Modules

17. Maintain the default RPI and click the OK button to add the module to the I/O
Configuration:

Now that the input module is added, let’s also add the 1756-OB16IEF digital output module
located in slot four of our ControlLogix chassis. This module has 16 digital output points, the first
twelve of which are wired to indicators on our control panel.

18. Back in the I/O Configuration of the Controller Organizer, right-click the Backplane
and select New Module… :

© Rockwell Automation, Inc. All rights reserved. 13

Adding Local Hardware Modules Level 1: Logix - On Demand

19. In the Select Module Type window:

a. Begin typing ‘1756-OB16IEF’ (the catalog number of the output module in slot 4)
into the search box.
b. When the list has narrowed down sufficiently, select the 1756-OB16IEF catalog
number from the list.
c. Verify that the Close on Create checkbox is checked.
d. Click the Create button:

19.a.
13.a

19.b.
13.a

19.c. 19.d.
13.a 13.a

14 © Rockwell Automation, Inc. All rights reserved.

Level 1: Logix - On Demand Adding Local Hardware Modules

20. In the New Module window, configure the General properties of the module:
a. In the Name box, type in ‘DigitalOutputs’.
b. For the description, type ‘Digital output module for Machine 1’.
c. Select Slot number 4.
d. Click the Change button:

20.a.
13.a

20.b. 20.c.
13.a 13.a

20.d.
13.a

© Rockwell Automation, Inc. All rights reserved. 15

Adding Local Hardware Modules Level 1: Logix - On Demand

21. In the Module Definition window:

a. Configure the Series and Revision to match your noted revision obtained from
the RSLinx Classic application (your module’s revision may vary from what is
shown below).
b. Choose Compatible Module for the Electronic Keying.
c. For the Connection, select Data.
d. Select Data for the Output Data.
e. Click the OK button:

21.a.
14.a.
13.a
21.b.
13.a

21.c.
13.a
21.d.
13.a

21.e.
13.a

22. Click the Yes button to apply the changes:

16 © Rockwell Automation, Inc. All rights reserved.

 Level 1: Logix - On Demand Adding Local Hardware Modules

23. Select the Connection category:

As with the input module, we have control over the period for communications between the
controller and the output module (i.e., the RPI).

© Rockwell Automation, Inc. All rights reserved. 17

 Adding Local Hardware Modules Level 1: Logix - On Demand

24. Maintain the default RPI and click the OK button to add the module to the I/O
Configuration:

This completes the addition of local digital I/O modules to our project.

25. Verify that your I/O Configuration appears as follows:

26. Click Save to save your project.

18 © Rockwell Automation, Inc. All rights reserved.

 Level 1: Logix - On Demand Adding Local Hardware Modules

As mentioned previously, the compatible electronic keying used in this example means that the
catalog number of the physical module must match the configured catalog number, and the
combined major and minor revisions of the physical module’s firmware must equal or exceed
the configured revisions. This configuration is fairly common and sufficient for many
applications.
However, industries that require government inspection and certification (such as the
pharmaceutical industry) often require exact match electronic keying. In these industries, any
variance in the installed modules, including the minor revision, requires re-inspection /
certification.
Disabled keying is not recommended other than in very specific testing / lab environments that
are closely controlled and monitored. And even then, the configuration is generally only
temporary.
Now we have some of the local hardware added to our project so that, when we download to
the controller, the configuration data that we entered will be written to the two modules. The
common look and feel between the two module profiles is no accident. You will learn, as you
configure other types of hardware, both local and remote, that the profile configurations are as
similar in look as possible, and are likewise intuitive.
But this is not all that has happened in our project. The goal of the Integrated Architecture is to
simplify the configuration of a system and, to that end, a lot goes on in the background that the
programmer would otherwise have to take care of manually. One of these things is the
automatic creation of hardware data types and tags.

© Rockwell Automation, Inc. All rights reserved. 19