Programming Manual

Logix5000 Controllers Security

Catalog Numbers 1756 ControlLogix, 1769 CompactLogix, 1789 SoftLogix, 1794 FlexLogix, PowerFlex 700S with DriveLogix
Important User Information
Solid-state equipment has operational characteristics differing from those of electromechanical equipment. Safety
Guidelines for the Application, Installation and Maintenance of Solid State Controls (publication SGI-1.1 available from
your local Rockwell Automation sales office or online at http://www.rockwellautomation.com/literature/) describes some
important differences between solid-state equipment and hard-wired electromechanical devices. Because of this difference,
and also because of the wide variety of uses for solid-state equipment, all persons responsible for applying this equipment
must satisfy themselves that each intended application of this equipment is acceptable.
In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from
the use or application of this equipment.
The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables and
requirements associated with any particular installation, Rockwell Automation, Inc. cannot assume responsibility or
liability for actual use based on the examples and diagrams.
No patent liability is assumed by Rockwell Automation, Inc. with respect to use of information, circuits, equipment, or
software described in this manual.
Reproduction of the contents of this manual, in whole or in part, without written permission of Rockwell Automation,
Inc., is prohibited.
Throughout this manual, when necessary, we use notes to make you aware of safety considerations.

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

ATTENTION: 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, and recognize the consequence.

SHOCK HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that dangerous voltage may be
present.

BURN HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that surfaces may reach
dangerous temperatures.

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

Allen-Bradley, Rockwell Automation, Rockwell Software, Studio 5000, CompactLogix, ControlLogix, DriveLogix, FactoryTalk, FactoryTalk Administration Console, FactoryTalk AssetCentre, FactoryTalk Batch, FactoryTalk
Directory, FactoryTalk Integrator, FactoryTalk Security, FactoryTalk Services Platform; FactoryTalk View ME, FactoryTalk View SE, Logix5000, RSLinx Classic, RSLogix 5000, SoftLogix5800, and TechConnect are
trademarks of Rockwell Automation, Inc.

Trademarks not belonging to Rockwell Automation are property of their respective companies.
 Summary of Changes

This manual contains new and updated information.

IMPORTANT RSLogix 5000 programming software is now known as Studio 5000TM Logix
Designer application, a component of the Studio 5000 Engineering and Design
Environment.

The following controllers are no longer supported in the Logix Designer

application, version 21.
Catalog Number Description
1756-L61 ControlLogix 5561 Controller
1756-L61S ControlLogix 5561S Controller
1756-L62 ControlLogix 5562 Controller
1756-L62S ControlLogix 5562S Controller
1756-L63 ControlLogix 5563 Controller
1756-L63S ControlLogix 5563S Controller
1756-L64 ControlLogix 5564 Controller
1756-L65 ControlLogix 5565 Controller
1768-L43 CompactLogix 5343 Controller
1768-L43S CompactLogix 5343S Controller
1768-L45 CompactLogix 5345 Controller
1768-L45S CompactLogix 5345S Controller
1769-L23E-QBF1 CompactLogix 5323E-QB1 Controller
1769-L23E-QBFC1 CompactLogix 5323E-QBFC1 Controller
1769-L23-QBFC1 CompactLogix 5323-QBFC1 Controller
1769-L31 CompactLogix 5331 Controller
1769-L32C CompactLogix 5332C Controller
1769-L32E CompactLogix 5332E Controller
1769-L35CR CompactLogix 5335CR Controller
1769-L35E CompactLogix 5335E Controller

Changes throughout this revision are marked by change bars, as shown in the
margin of this page.

This table contains the changes made to this revision.

Topic Page
Specifying a Source Key File 33
Securing a Logix Designer Application Project File 18, 19

Rockwell Automation Publication 1756-PM016F-EN-P - September 2012 3

Summary of Changes

Notes:

4 Rockwell Automation Publication 1756-PM016F-EN-P - September 2012

 Table of Contents

Preface Studio 5000 Engineering and Design Environment and

Logix Designer Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Purpose of This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Chapter 1
Security Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
FactoryTalk Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
FactoryTalk Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter 2
Configuring FactoryTalk Security Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
with Installing the Rockwell Software Security Emulator . . . . . . . . . . . . . . . . . 11
Enabling Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Logix Designer Application
Installing FactoryTalk Services Platform Software. . . . . . . . . . . . . . . . . . . 15
Securing a Logix Designer Application Project File . . . . . . . . . . . . . . . . . . 16
Applying Security to a Controller Resource. . . . . . . . . . . . . . . . . . . . . . . . . 21

Chapter 3
Migrating from a Security Server Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Database to a FactoryTalk Server Importing a Security Server Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Importing Status Text File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Organizer Import Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Resource Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Chapter 4
Configuring Source Protection in the Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Logix Designer Application Enabling Source Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Applying Source Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Specifying a Source Key File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Protecting Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Viewing Components Without a Key . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Source Key File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Verifying Source Protection on a Component . . . . . . . . . . . . . . . . . . . . . . 42
Specifying the Path to a Different sk.dat File . . . . . . . . . . . . . . . . . . . . 43
Use the Clear Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Using the Disable Ability to Configure Source Protection Button 45
Removing Access to a Protected Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Disabling Routine Source Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Rockwell Automation Publication 1756-PM016F-EN-P - September 2012 5

Table of Contents

Chapter 5
RSLogix 5000 Software CPU Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Security Tool Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Securing a ControlLogix Controller with Logix CPU Security Tool . . 50
Accessing a Secured Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Removing Security from a Controller with the CPU Security Tool 55
Removing a Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Index

6 Rockwell Automation Publication 1756-PM016F-EN-P - September 2012

 Preface

Studio 5000 Engineering and The Studio 5000™ Engineering and Design Environment combines engineering
and design elements into a common environment. The first element in the
Design Environment and Studio 5000 environment is the Logix Designer application. The Logix Designer
Logix Designer Application application is the rebranding of RSLogix™ 5000 software and will continue to be
the product to program Logix5000™ controllers for discrete, process, batch,
motion, safety, and drive-based solutions.

The Studio 5000 environment is the foundation for the future of

Rockwell Automation® engineering design tools and capabilities. It is the one
place for design engineers to develop all the elements of their control system.

Purpose of This Manual This manual explains how to configure security for Logix Designer application. It
also explains how to setup source protection for your logic and projects.

This manual is one of a set of related manuals that show common procedures for
programming and operating Logix5000 controllers. For a complete list of
common procedures manuals, see the Logix5000 Controllers Common Procedures
Programming Manual, publication1756-PM001.

The term Logix5000 controller refers to any controller that is based on the
Logix5000 operating system, such as the following:
• CompactLogix controllers
• ControlLogix controllers
• GuardLogix controller
• DriveLogix controllers
• SoftLogix5800 controllers

Rockwell Automation Publication 1756-PM016F-EN-P - September 2012 7

Preface

Additional Resources These documents contain additional information concerning related products
from Rockwell Automation.

Resource Description
Industrial Automation Wiring and Grounding Guidelines, Provides general guidelines for installing a Rockwell
publication 1770-4.1 Automation industrial system.
Product Certifications website, http://www.ab.com Provides declarations of conformity, certificates, and
other certification details.

You can view or download publications at http://www.rockwellautomation.com/

literature/. To order paper copies of technical documentation, contact your local
Allen-Bradley distributor or Rockwell Automation sales representative.

8 Rockwell Automation Publication 1756-PM016F-EN-P - September 2012

 Chapter 1

Security

Introduction This chapter discusses security related features available in the Logix Designer
application.

In version 20 or later of the application, security enhancements provide:

• Security Server Validation - When enabled, and a user attempts to access a
secured controller or project file, the application will make sure that the
user is authorized by a FactoryTalk Directory trusted by that controller or
project file. For more information, refer to “Securing a Logix Designer
Application Project File” on page 16.
• Change Detection - Two new Controller attributes were added:
ChangesToDetect and AuditValue. These attributes can be configured
programmatically or by using the Security tab found in the Controller
Properties dialog box. The audit value can be monitored from an HMI,
historian, remote controller, and from Logix Designer application. For
more information about Change Detection, see Logix5000 Controllers
Information and Status Programming Guide, publication1756-PM015.
• Restricted communications through trusted slots - When enabled,
ControlLogix controllers will only accept communications through
selected slots. For more information about trusted slots, refer to “Securing
a Logix Designer Application Project File” on page 16.

The Logix platform, version 18 or later, provides Data Access Control through
two new tag attributes: External Access and Constant. Together, these attributes
let you control access to tag data and help to safeguard tags by preventing
unwanted changes to their values. For more information about Data Access
Control, see the Logix5000 Controllers I/O and Tag Data Programming Guide,
publication1756-PM004.

FactoryTalk Security FactoryTalk Security integrates a common security model across all FactoryTalk
enabled products. FactoryTalk Services Platform (FTSP) includes the
FactoryTalk Administration Console that provides the interface for configuring
your system.

Rockwell Automation Publication 1756-PM016F-EN-P - September 2012 9

Chapter 1 Security

FactoryTalk Directories

The FactoryTalk Directory is an important aspect to implementing FactoryTalk

Security. In the FactoryTalk architecture, there are two separate Directory types,
Local and Network. A FactoryTalk Local directory is sometimes utilized when all
the Rockwell Automation Software products run on a single computer. The
Local FactoryTalk Directory is used for products such as FactoryTalk View
Machine Edition (ME) and FactoryTalk View Site Edition (SE) Station
(Standalone). The FactoryTalk Network Directory is used when multiple
Rockwell Automation Software products need to share information across
multiple computer systems. The FactoryTalk Network Directory allows these
systems to share a common FactoryTalk Directory for products, such as
FactoryTalk View SE, FactoryTalk Integrator, FactoryTalk Batch, and FactoryTalk
AssetCenter.

IMPORTANT In version 20 or later of the application, the FactoryTalk Local Directory is not
supported.

When securing controllers using version 20 or later of the application, only the
Network Directory is supported. If you are securing controllers using an earlier
version of the application, you can use either the FactoryTalk Local Directory or
the Network Directory. If you are trying to coordinate security across multiple
computers, you will need a Network Directory implementation of FactoryTalk
Security. If all of your products reside on a single computer, you can utilize the
Local Directory. If you have a choice, you might want to use the Network
Directory for forward compatibility with version 20 and later. The Network
Directory can be locally hosted on each machine just like the Local Directory.

For more information about FactoryTalk Security, see the FactoryTalk Security
System Configuration Guide, publication FTSEC-QS001.

10 Rockwell Automation Publication 1756-PM016F-EN-P - September 2012

 Chapter 2

Configuring FactoryTalk Security with

Logix Designer Application

Introduction FactoryTalk Services Platform (FTSP) software is installed during the installation
of the Logix Designer application.

Installing the Rockwell Software RSLogix 5000 software version 19 or earlier, uses the Rockwell Software Security
Emulator to communicate with FactoryTalk Security. Starting with version 20,
Security Emulator RSLogix 5000 obtains security information directly from FactoryTalk Services
Platform and does not require RSSecurity Emulator.

If you are using RSLogix 5000 version 19 or earlier, follow these instructions to
install the Rockwell Software Security Emulator.

1. From the Start menu select Programs>Rockwell Software>FactoryTalk

Tools>RSSecurity Emulator Install

2. Follow the installation prompts to complete the installation.

Rockwell Automation Publication 1756-PM016F-EN-P - September 2012 11

Chapter 2 Configuring FactoryTalk Security with Logix Designer Application

Enabling Security If the Security menu is dimmed, as shown in this picture, you need to enable
security for the application.

For version 20 or later of the application, if the security menu is dimmed, you
need to install FactoryTalk Services Platform. See “Installing FactoryTalk Services
Platform Software” on 15. If you are using version 20 or later, and the security
menu is enabled, skip to step 5.

If you are using RSLogix 5000 version 19 or earlier, you need to use SetSecKeys
to enable security. Follow the instructions below.

1. For RSLogix 5000 v19 or earlier, the SetSecKeys software is added to the
system during installation.

Navigate to: \Program Files\Rockwell Software\RSLogix

5000\ENU\vxx\Security and double-click SetSecKeys.exe. For this
example, we are using RSLogix 5000 v16.

12 Rockwell Automation Publication 1756-PM016F-EN-P - September 2012

 Configuring FactoryTalk Security with Logix Designer Application Chapter 2

2. If prompted to locate the project file, select the RS5000Keys.ini file and
click Open.

ATTENTION: For RSLogix 5000 version 19 or earlier, if you need to disable

FactoryTalk Security for RSLogix 5000, please contact Rockwell Automation
Technical Support.

3. In the Enable/Disable Security Keys dialog box, select the RSLogix 5000
check box and then click OK.

4. If the RSLogix 5000 Security: Enable dialog box appears, click OK.

Rockwell Automation Publication 1756-PM016F-EN-P - September 2012 13

Chapter 2 Configuring FactoryTalk Security with Logix Designer Application

5. Open the FactoryTalk Administration Console:

a. Click Start > All Programs > Rockwell Software > FactoryTalk
Administration Console.
b. Select the FactoryTalk Directory option and click OK.

IMPORTANT For version 20 or later of the application, security settings are obtained from
the FactoryTalk Network Directory. RSSecurity Emulator is not required and
the FactoryTalk Local Directory is not supported.

c. If prompted to log on to FactoryTalk, enter your FactoryTalk user name

and password, and then click OK.

TIP If you cannot log on to FactoryTalk, see “I cannot log on to the FactoryTalk
Directory” in FactoryTalk Help.

6. Open the RSLogix 5000 Feature Security Properties dialog box:

a. In the Explorer window, navigate to:
System > Policies > Product Policies > RSLogix 5000.
b. Right-click Feature Security and select Properties.
7. Secure the RSLogix 5000 controller:
a. In the Feature Security Properties dialog box, select Controller:Secure
and then click Browse.
b. In the Configure Securable Action dialog box, click Add to select the
user accounts or groups that you want to configure.
c. In the Select User and Computer dialog box, select the user accounts or
groups and click OK.
d. Follow the instructions to complete the configuration.

14 Rockwell Automation Publication 1756-PM016F-EN-P - September 2012

 Configuring FactoryTalk Security with Logix Designer Application Chapter 2

Installing FactoryTalk Services If you find that the Security feature is not enabled in the Logix Designer
application you will need to make sure FactoryTalk Services Platform (FTSP)
Platform Software software is installed properly.

Follow these instructions to install the FTSP software.

1. On the installation disk, browse to D:\System\FTSP and double-click

the Setup.exe file.
2. Follow the installation prompts to complete the installation.

During the installation, all existing local and network FactoryTalk

Directory files are automatically configured and backed up. For new
installations, the pre-configured FactoryTalk Directory files are backed up.
The backups let you restore the Factory Talk Directory files to a previous
software version.

After the installation is complete, refer back to “Enabling Security” on page 12

If you are having problems, refer to the FactoryTalk Security System Configuration
Guide, publication FTSEC-QS001.

Rockwell Automation Publication 1756-PM016F-EN-P - September 2012 15

Chapter 2 Configuring FactoryTalk Security with Logix Designer Application

Securing a Logix Designer Once you have configured the Logix Designer application to be security aware,
the next step is to enable security in a project file. Follow these steps to secure a
Application Project File project file.

1. Open Logix Designer.

a. Click Start > Rockwell Software>Studio 5000.
b. If prompted to Log On to FactoryTalk, enter your FactoryTalk user
name and password, and then click OK.

In the example below, the FactoryTalk Directory (FTD) was configured

with an account called FTADMIN.

2. Open the project file that you want to secure.

This example uses the DayOf Week project file, which is provided on the
installation CD.

16 Rockwell Automation Publication 1756-PM016F-EN-P - September 2012

 Configuring FactoryTalk Security with Logix Designer Application Chapter 2

3. On the Edit menu, click Controller Properties.

4. Click the General tab to find the controller name. Write down the name
that appears in the Name field. By default, this is the name of the ACD file
that will be used later on page 21when setting security in the FactoryTalk
Administration Console.

In this example, the name is DayOf Week.

Rockwell Automation Publication 1756-PM016F-EN-P - September 2012 17

Chapter 2 Configuring FactoryTalk Security with Logix Designer Application

5. To configure the security settings, click the Security tab or the Advanced
tab depending on the version of the application.
• Click the Security tab if it appears in the Controller Properties dialog
box.

a. In the Security Authority list, select FactoryTalk Security.

IMPORTANT When you select a security authority for a project, you can only access the
project and any controller that contains it when you have been granted access
in Factory Talk Security.

b. To associate the project with a specific authority, select the Use only the
selected Security Authority for Authentication and Authorization
check box.
To remove the association to the specified Security Authority for this
project, go online with the controller and then clear this check box.

When you associate a project with a specific Security Authority, you are
associating the project with a specific FactoryTalk Network Directory
that is identified by a security authority identifier. Projects that are
secured and bound to a specific Security Authority cannot be recovered
if the security authority identifier of the FactoryTalk Network
Directory used to secure the project no longer exists.

IMPORTANT Before you associate this project with a specific Security Authority, we
recommend that you back up the FactoryTalk Directory and save unsecured
versions of this project file in (.ACD) or (.L5X or .L5K) formats, and save them
in a secure location.
For details about backing up a FactoryTalk Directory see the FactoryTalk Help:
Start > Programs > Rockwell Software > FactoryTalk Tools >
FactoryTalk Help.

TIP The check box is available when you are using FactoryTalk Services Platform
2.50 or later and a version of the application that supports associating a
project with a specific Security Authority.

18 Rockwell Automation Publication 1756-PM016F-EN-P - September 2012

 Configuring FactoryTalk Security with Logix Designer Application Chapter 2

c. For information about the settings found on the Security tab such as,
Restrict Communications Except Through Selected Slots, Selected
Slots, or Change Detection, access the help from the Help menu.
• Click the Advanced tab, if the Security tab does not appear in the
Controller Properties dialog box.
a. In the Security list select FactoryTalk Security.

6. Click OK. If prompted to confirm whether to confirm the controller

settings, click Yes.

IMPORTANT When you select a security authority for a project, you can only access the
project and any controller that contains it when you have been granted access
in Factory Talk Security.

7. Save the project file.

Rockwell Automation Publication 1756-PM016F-EN-P - September 2012 19

Chapter 2 Configuring FactoryTalk Security with Logix Designer Application

8. To download the project file to the controller, on the Communications

menu, click Who Active.

9. In the Who Active window, locate and select the controller resource.

10. Click Download to continue.

11. When the download is complete, close the application.

If prompted, save changes.

20 Rockwell Automation Publication 1756-PM016F-EN-P - September 2012

 Configuring FactoryTalk Security with Logix Designer Application Chapter 2

Applying Security to a In the following steps, a single controller is configured for security. When
managing large numbers of users and controllers, Rockwell Automation
Controller Resource recommends that you group users with user groups, group permissions with
action groups, and use the Resource Grouping method to secure your resources to
simplify administration of permissions. For details see the FactoryTalk Help:
Start > Programs > Rockwell Software > FactoryTalk Tools > FactoryTalk
Help.

Follow these steps to apply security to a controller resource.

1. Open the FactoryTalk Administration Console, select

Start>Programs >Rockwell Software>FactoryTalk Administration
Console.
2. Select the FactoryTalk Directory option and click OK.

– For version 20 or later of the application, security settings are obtained

from the FactoryTalk Network Directory. RSSecurity Emulator is not
required and the FactoryTalk Local Directory is not supported.
– The default FactoryTalk Security configuration has Single Sign On
enabled, so the you will not be prompted to Log On to FactoryTalk.
Customers upgrading from revisions prior to 16.03 or customers that
have modified the default FactoryTalk Security configuration will be
prompted to Log On to FactoryTalk.
3. If prompted to Log On to FactoryTalk, enter your user name and
password.
In the example below, the FactoryTalk Directory (FTD) was configured
with an account called FTADMIN.

Rockwell Automation Publication 1756-PM016F-EN-P - September 2012 21

Chapter 2 Configuring FactoryTalk Security with Logix Designer Application

4. Navigate to the controller resource the secured project file was

downloaded to.
From the Explorer window, expand Networks and Devices and navigate to
the controller you want to configure.

5. Right-click on the controller resource and select Properties.

EXAMPLE If you want the security settings to be inherited by all controllers, right click on
Networks and Devices, then select Security. From the Security Settings
dialog, you can configure security settings that will be inherited by all secured
projects. Unique permissions can still be configured to a particular device, if
needed. For details see the FactoryTalk Help:
Start > Programs > Rockwell Software > FactoryTalk Tools >
FactoryTalk Help.

22 Rockwell Automation Publication 1756-PM016F-EN-P - September 2012

 Configuring FactoryTalk Security with Logix Designer Application Chapter 2

6. In the Logical Name list, select the Controller name. This name should
match the settings from the Controller Properties dialog box made during
the “Securing a Logix Designer Application Project File” section. The
controller name can also be manually typed in if the name does not appear
in the list.

IMPORTANT Security settings can be applied to a Logical Name. The Logical Name is the
same as the Name shown on the Controller Properties dialog. Security settings
for a Logical Name apply to the offline project, as well as when the project is
downloaded to the controller.
Security can be configured on a Logical Name associated to a particular
device, and Logic Names can also be associated to an Application or Area in
the FactoryTalk Explorer window. Security applied to an Application or Area is
inherited by any Logical Names associated with that Application or Area. In
the image in Step 5, Rootbeer Production and Samples Water are Applications,
and an Area would be located below an Application. You right click on an
Application or Area and use the Resource Editor to associate Logical Names to
that Application or Area.
Security can also be configured at the Networks and Devices level in the
Explorer window by right clicking and selecting Security. Security settings
configured at the Networks and Devices level are inherited by all devices
located under Networks and Devices. Security can be configured at the top-
most node in the Explorer window, and all Applications, Areas, and devices
will inherit these permissions.

TIP • The controller in the Network and Devices tree will also display the controller
name property next to the controller resource.
• If the name does not appear in the Network and Devices tree, open RSLinx Classic
and navigate to the controller resource with RSWho. Navigating to the resource in
RSLinx Classic will update the Controller path information in RSLinx Classic.
FactoryTalk Administration Console uses the controller path information from
RSLinx Classic to display Controllers. Once the path information is updated in
RSLinx Classic, open the FactoryTalk Administration Console and right-click on the
Network and Devices tree and select Refresh.

7. Click OK to continue.

Rockwell Automation Publication 1756-PM016F-EN-P - September 2012 23

Chapter 2 Configuring FactoryTalk Security with Logix Designer Application

8. Individual user or groups rights will still need to be configured to control

access to secured controllers.

To configure Security, right click on the Network, Networks and Devices,

Application, Area, or the particular device on which you wish to configure
security, then select Security from the menu.
9. From the Security Settings dialog, you can configure security permissions
for a particular user or user group and computer names.

This completes the FactoryTalk Security configuration for a controller resource.

For more FactoryTalk Security information, refer to the FactoryTalk Security
System Configuration Guide, publication FTSEC-QS001.

24 Rockwell Automation Publication 1756-PM016F-EN-P - September 2012

 Chapter 3

Migrating from a Security Server Database to a

FactoryTalk Server

Introduction To migrate to a FactoryTalk Security Server you must first export the security
server database and then import the database into FactoryTalk.

Importing a Security Server Follow these steps to import a security server database into FactoryTalk Security.
Database 1. From the Start menu, select Programs>Rockwell Software>FactoryTalk
Tools>Import RSSecurity Configuration

2. Select Import File.

3. Browse to the import file and Destination directory from the menu.

Rockwell Automation Publication 1756-PM016F-EN-P - September 2012 25

Chapter 3 Migrating from a Security Server Database to a FactoryTalk Server

4. Click Yes at the Warning message.

5. Type your user name and password and click OK.

The import status appears.

6. Select how you want action and resource groups to be imported into
FactoryTalk and click OK.

26 Rockwell Automation Publication 1756-PM016F-EN-P - September 2012

 Migrating from a Security Server Database to a FactoryTalk Server Chapter 3

7. Review the import issue resolution and click Continue.

8. Select a group to import.

9. Right-click the selected group, select Add Area, and browse to the
resource location.
10. Click OK.

Rockwell Automation Publication 1756-PM016F-EN-P - September 2012 27

Chapter 3 Migrating from a Security Server Database to a FactoryTalk Server

11. Click OK.

The import succeeded graphic appears.

12. Click OK.

28 Rockwell Automation Publication 1756-PM016F-EN-P - September 2012

 Migrating from a Security Server Database to a FactoryTalk Server Chapter 3

Importing Status Text File

This graphic shows an example of the Import Status text file that is created when
an import is completed.

Organizer Import Result

This graphic shows the results of the import process in the Organizer.

Rockwell Automation Publication 1756-PM016F-EN-P - September 2012 29

Chapter 3 Migrating from a Security Server Database to a FactoryTalk Server

Resource Editor

This graphic shows the results of the import in the Resource Editor.

30 Rockwell Automation Publication 1756-PM016F-EN-P - September 2012

 Chapter 4

Configuring Source Protection in the

Logix Designer Application

Introduction This chapter describes how to enable and apply source protection for your Logix
Designer components such as routines and Add-On Instructions.

Enabling Source Protection Do these steps to enable Logix Designer source protection.

1. On the Logix Designer installation CD, browse to

D:\ENU\Tools\Source Protection Tool and double-click on the
RS5KSrcPtc.exe.

A dialog box appears.

2. Click Yes.

Rockwell Automation Publication 1756-PM016F-EN-P - September 2012 31

Chapter 4 Configuring Source Protection in the Logix Designer Application

Applying Source Protection This procedure lets you apply source protection to a project file. When a source
key is applied to a component, that component is source-protected. Source keys
are user-generated, case-sensitive passwords that lock Logix Designer
components from being viewed or modified by third parties.

IMPORTANT Source Protection can be applied only on a project file that is offline.

Specifying a Source Key File

Do these steps to configure a file location.

1. Open an offline project file.

2. From the Tools menu, click Tools and choose Configure Source
Protection.
TIP This menu option is not available until you have run RS5KSrcPtc.exe on
your workstation.

Source Protection requires a Source Key File location to be specified on

your workstation. You are prompted to configure a file location.

3. Click Yes.

4. Click Browse to specify a Source Key File location.

32 Rockwell Automation Publication 1756-PM016F-EN-P - September 2012

 Configuring Source Protection in the Logix Designer Application Chapter 4

5. Navigate to the folder location to store the Key File.

The key file can be saved in any accessible folder. In this example,
C:\RSLogix 5000\Projects folder is specified as the Key File location.
6. Click OK to continue.

Once you return to the Source Protection Configuration dialog box, the
location you selected appears under Source Key Provider.

If a Key File is not found in the specified location, you will be prompted to
create a new Key File.
TIP To check for a specific location, click the Specify button on the Source
Protection Configuration dialog box. A window appears with the location,
if one exists on your workstation.

7. Click Yes to create a new key file.

Rockwell Automation Publication 1756-PM016F-EN-P - September 2012 33

Chapter 4 Configuring Source Protection in the Logix Designer Application

Protecting Components

The Source Protection Configuration dialog box lists all Program Routines,
Add-On Instructions, and Equipment Phase State Routines in the project file.
These components are protected by applying source keys to them. Source keys are
user-generated passwords used to lock components. Users that do not have the
source key for a component are not able to modify the component and may not
be able to view the component.

About Source Keys

In version 18 and earlier of RSLogix 5000 software, only IEC-61131 compliant

source keys are recognized. Each source key must begin with a lowercase character
a-z or underscore character ( _ ), and contain only characters lowercase a-z, 0-9,
and an underscore character ( _ ). Uppercase A-Z may be entered in
RSLogix 5000 software or in the source key file, but the uppercase characters will
be converted to lowercase. Source keys are limited to 40 characters in length.

In version 19 and later of the application, source keys are

case-sensitive and may contain any printable ASCII character, excluding the space
character. This includes uppercase A-Z, lowercase a-z, numbers 0-9, and symbols
such as "!@#$%. Source keys are limited to 40 characters in length.

Source Key Names

Version 19 and later of the application supports associating names with source
keys. Source key names are descriptive text that help identify source keys. Where
appropriate, Logix Designer application will display the source key name in place
of the source key itself. This provides an additional layer of security for the source
key.

34 Rockwell Automation Publication 1756-PM016F-EN-P - September 2012

 Configuring Source Protection in the Logix Designer Application Chapter 4

Descriptive names should be used to help identify the purpose of the source. For
instance, a source key used to secure components that field engineers require
access might be named, Field Engineer.

IMPORTANT If the same source keys will be used with version 18 and earlier and version 19 and
later of the application, begin each source key with a lowercase character a-z, or an
underscore character ( _ ), and use only characters lowercase a-z, 0-9 , or an
underscore character ( _ ) within the source keys.
If you use source key names in version 19 and later of the application, and your source
keys are IEC61131-3 compliant, your source keys will still work in version 18 and earlier.

Do these steps to apply a source key to one or more components.

1. Select one or more components that require protection and click Protect.

The Apply Source Key dialog box appears.

Readable text
option

For version 19 and later of the application, the entered source keys on the
Apply Source Key dialog box are masked by default, but you have an
option to display readable text. If you have version 18 and earlier of
RSLogix 5000 software, your source keys are in a readable, text-only
format.

Rockwell Automation Publication 1756-PM016F-EN-P - September 2012 35

Chapter 4 Configuring Source Protection in the Logix Designer Application

2. Complete the Apply Source Key dialog box to designate a new source key.

Element Description
Source Key to Apply to Selected Component(s) Type a new key. Source keys cannot exceed 40
characters.
The Confirm New Source Key and Source Key Name
boxes become active for version 19 and later of the
application.

To select an existing key, click the down arrow. When

the source key is selected, the Confirm New Source
Key and Source Key Names boxes become read-only.
The Confirm New Source Key box will be empty, and
the Source Key Name box will contain the name of
the selected source key, if one exists.
Show Source Key For version 19 and later of the application, click the
check box to display source keys in a readable format.
Confirm New Source Key Re-type exactly the characters you typed in the
Source Key to Apply to Selected Component(s) field.
This box is unavailable when an existing source key is
selected or when the source key is being displayed in
cleartext.
Source Key Name Type a name for the source key; do not exceed 40
characters. The box displays the name of a selected,
existing source key, if one is defined.
Allow viewing of component(s) You can set a protected routine to allow or deny
viewing of the routine from a system that does not
have the key required to access the routine.
Select the check box to allow viewing of a routine in
read-only mode. Protected routines that do not allow
viewing cannot be viewed by systems that do not
have the required key.

3. Click OK.
The Source Protection Configuration dialog box reappears.

For version 19 and later of the application, source keys may have names.
Where appropriate, the source key name is displayed instead of the source
key. This further protects the source key from being seen.

In the example, the name Field Engineer is displayed instead of a source key.

IMPORTANT Source key names cannot be added to existing source keys through the Logix
Designer application.
See page 40 to learn how to associate a name to an existing source key.

36 Rockwell Automation Publication 1756-PM016F-EN-P - September 2012

 Configuring Source Protection in the Logix Designer Application Chapter 4

For version 19 and later of the application, unnamed source keys are
obfuscated. Three black circles appear after the last character or any
character beyond the fifth character to provide security.

4. Close the Source Protection Configuration dialog box and save the
project file.

Viewing Components Without a Key

This procedure lets you flag source-protected components to be available in a

read-only format on a system that does not have the source keys.

1. Enter a source key on the Apply Source Key dialog box.

2. (optional) Name the source key.

3. Select the Allow viewing of components check box.
4. Click OK.

The Test_DOW routine in the example is source-protected and can be

viewed (as indicated by Yes) in a read-only format on workstations that
do not have the source key.

5. Click Close.
6. Save the project file and download it to the controller.

Rockwell Automation Publication 1756-PM016F-EN-P - September 2012 37

Chapter 4 Configuring Source Protection in the Logix Designer Application

When the project file is opened on a system that does not contain the keys
used to secure the routines and Add-On Instructions, the components will
be protected based on the setting in the Source Protection Configuration
dialog box.

Test_DOW was protected and set to viewable on the Source Protection

Configuration dialog box. You can open the routine as read-only on a
system that does not contain the key for the routine, but you will not be
able to modify the routine.

Routines or Add-On Instructions that are protected, but are not

configured as viewable, cannot be opened. The Dayof Week routine
cannot be opened on a system that does not have the key used to protect
the routine. In the example, the icon for the routine is dimmed, indicating
the routine cannot be opened.

Inactive icons are dimmed.

38 Rockwell Automation Publication 1756-PM016F-EN-P - September 2012

 Configuring Source Protection in the Logix Designer Application Chapter 4

The MyValveAOI cannot be viewed on a system that does not contain the
key used to protect the Add-On Instruction. This is because MyValveAOI
was protected, but not set to be viewable. The Add-On Instruction is
shown in the Controller Organizer, but the parameters and local tags for
the Add-On Instructions are not viewable on a system that does not
contain the required key used to protect it.

Local Tags and Logic are not viewable.

Parameters can be viewed but not
edited.

This example shows the Add-On Instruction MyValveAOI viewed from a

system that has the key used to secure the instruction.

Parameters, Local Tags, and

Logic are viewable and can
be edited.

TIP For source-protected export options, see the Logix5000 Controllers

Import/Export Reference Manual, publication 1756-RM084.
Source-protected content cannot be copied from version 19 of
RSLogix 5000 software and pasted into earlier software versions. The pasting function
will be disabled in previous software versions when source-protected content is placed
on the clipboard.

Rockwell Automation Publication 1756-PM016F-EN-P - September 2012 39

Chapter 4 Configuring Source Protection in the Logix Designer Application

Source Key File Source keys made available to the application through an sk.dat file are
unencrypted. We recommend that you back up and store the key in a secure
location. If necessary, the individual keys can be distributed or provided to the
necessary parties.

Text must be in first line.

IMPORTANT Source key files are created in an ANSI format in RSLogix 5000 software version 18 and
earlier. Software version 19, and later, creates UTF-8 formatted sk.dat files. ANSI sk.dat
files modified in software version 19, and later, are converted to UTF-8 sk.dat files.
Source keys must not appear on the first line of a UTF-8 formatted sk.dat file. The first
line of UTF-8 formatted sk.dat files is ignored by RSLogix 5000 software version 18 and
earlier. Versions 19 and later insert a header on the first line of the sk.dat file if one is
not already present.

Do these steps to assign a name to an existing source key.

1. Close the Logix Designer application.

2. Locate the sk.dat file on your workstation.
3. Open the file with a text editor, such as Notepad or WordPad.

4. Click the mouse at the end of an existing source key and press Enter.

Note that our example, P@ssWOrd, shows that source keys are case
sensitive and may use special characters like @#$%(){}[].
5. Click the space bar once and type a name for the source key.

40 Rockwell Automation Publication 1756-PM016F-EN-P - September 2012

 Configuring Source Protection in the Logix Designer Application Chapter 4

One or more character of white space is required to associate the name

with the source key.

One character space for

source key names

Source keys always begin in the first character of the text editor. A source
key name must be on the line immediately following the source key that it
is associated with, and at least one character of white space. Subsequent
lines after the source key that are preceded with white space are ignored by
the application, and can be used for comments.
6. Choose File>Save.
7. Open the Logix Designer application.
8. Choose Tools>Configure Source Protection.

Acme Field Engineer replaces P@ssWOrd in the Source Key column on the
Source Protection Configuration dialog box.

9. To use the named source key, select the component that you gave a name
and click Protect.

Rockwell Automation Publication 1756-PM016F-EN-P - September 2012 41

Chapter 4 Configuring Source Protection in the Logix Designer Application

The Apply Source Key dialog box displays.

10. Click the pull-down in the first entry box, and select the name you
associated with the source key.

The source key that is masked for privacy appears and the name is in the
Source Key Name box.

11. Click OK.

Verifying Source Protection on Make a decision on what method you want to use to see how a component looks
when it is source protected and when it is not.
a Component
When the Source Key is available, the component behaves the same as if it were
not source protected. To verify source protection, you remove the source keys.

Here are a few ways to verify that your content is protected.

IMPORTANT Disabling source protection using the RS5KSrcPT.exe tool does not remove the sk.dat
file.

• Specify the path to a different sk.dat file

• Use buttons on the Source Protection Configuration dialog box

42 Rockwell Automation Publication 1756-PM016F-EN-P - September 2012

 Configuring Source Protection in the Logix Designer Application Chapter 4

Specifying the Path to a Different sk.dat File

To use the specify path method, follow these steps.

1. On the Source Protection Configuration dialog box, click Specify.

2. On the Specify Source Key File Location dialog box, select a directory that
does not contain an sk.dat file. For example, C:\RSLogix 5000\Projects\
Empty.

3. When the message appears and asks if you want to create a new file, click
Yes.
4. When the message appears and asks if you want to create a new directory,
click Yes.

The software now points to an empty sk.dat file which mimics a user who does
not have a source key.

Rockwell Automation Publication 1756-PM016F-EN-P - September 2012 43

Chapter 4 Configuring Source Protection in the Logix Designer Application

Advantage

Keeping an empty source key file around makes it easy to quickly switch back and
forth between sk.dat files.

Disadvantage

Care must be taken that the correct sk.dat file is specified when creating new
source keys.

Use the Clear Button

IMPORTANT Back up your sk.dat file before using this button.

On the Source Protection Configuration dialog box, the Clear button clears the
location bar and gives you the option to delete your sk.dat file. See the steps under
“Removing Access to a Protected Routine" on page 46.

Advantage

You can clear the location without removing the sk.dat file.

Disadvantages

If you delete the sk.dat, it will be erased. You need to make a backup file.

The sk.dat file is still present on the system under its original name and could be
discovered.

44 Rockwell Automation Publication 1756-PM016F-EN-P - September 2012

 Configuring Source Protection in the Logix Designer Application Chapter 4

Using the Disable Ability to Configure Source Protection Button

IMPORTANT Back up your sk.dat file before using this button.

On the Source Protection Configuration dialog box, the Disable Ability to

Configure Source Protection button deletes your sk.dat file. See the steps under
"Disabling Routine Source Protection” on page 47.

Disadvantages

If you delete the sk.dat, it will be erased. You need to make a backup file.

It requires that you re-enable source protection for the Source Protection option
to be available under the Tools menu.

You can also rename or remove the sk.dat file to verify source protection, but you
must make a backup file before you do so.

Rockwell Automation Publication 1756-PM016F-EN-P - September 2012 45

Chapter 4 Configuring Source Protection in the Logix Designer Application

Removing Access to a Before you remove a source key file (sk.dat) from a workstation, write down the
source keys or make a copy of the file and store in a secure location.
Protected Routine
1. Open the project that is protected.
2. From the Tools menu, choose Security>Configure Source Protection.

3. Click Clear.

A dialog box asks if you want to delete the source key file (sk.dat).
4. Select Yes to remove, or No not to remove the source key file from the
workstation.

46 Rockwell Automation Publication 1756-PM016F-EN-P - September 2012

 Configuring Source Protection in the Logix Designer Application Chapter 4

Disabling Routine Before you disable a source key file (sk.dat) from a workstation, write down the
source keys or make a copy of the file and store in a secure location.
Source Protection
1. Open the project that is protected.
2. From the Tools menu, choose Security>Configure Source Protection.

3. Click the Disable Ability To Configure Protection button.

A dialog box prompts you to confirm the action.

4. Click Yes.

A dialog box asks if you want to delete the source key file (sk.dat).
5. Select Yes to remove the source key file from the computer or select No to
retain the source key file.

Rockwell Automation Publication 1756-PM016F-EN-P - September 2012 47

Chapter 4 Configuring Source Protection in the Logix Designer Application

Notes:

48 Rockwell Automation Publication 1756-PM016F-EN-P - September 2012

 Chapter 5

RSLogix 5000 Software CPU Security Tool

Introduction This chapter describes how to use the RSLogix 5000 CPU Security Tool to lock a
controller. When a controller is locked, no one can access until it is unlocked.

Installation The Logix CPU Security Tool is automatically installed when you install version
17 or later of the application. If you find that it is not installed, follow these
installation instructions. The installation file is on the installation CD under the
Tools folder.

Do these steps to install the Logix CPU Security Tool.

1. On the RSLogix 5000 installation CD, browse to

D:\ENU\Tools\LogixCPUSecurityTool and double-click the
RSLogix CPU Security Tool Installer.msi file.

2. Follow the installation prompts to complete the installation.

Rockwell Automation Publication 1756-PM016F-EN-P - September 2012 49

Chapter 5 RSLogix 5000 Software CPU Security Tool

Securing a ControlLogix You can secure a controller with the Logix CPU Security Tool. The tool is
installed under the Logix Desiger Tools menu.
Controller with Logix CPU
Security Tool

1. Start the Logix CPU Security Tool.

2. To specify a path to the controller, click the RSWho button.

Use the RSWho button to locate

the controller that you want to
secure.

50 Rockwell Automation Publication 1756-PM016F-EN-P - September 2012

 RSLogix 5000 Software CPU Security Tool Chapter 5

3. Select the controller that you want to secure and click OK.

The Logix CPU Security Tool displays the current status of the controller.

Notice that the controller you

selected is currently
unsecured and there is no
password set in the controller.

4. Click Change Password.

5. Enter a password in the new password field and confirm the password and
click OK.

Rockwell Automation Publication 1756-PM016F-EN-P - September 2012 51

Chapter 5 RSLogix 5000 Software CPU Security Tool

The Password Status for the controller now indicates a Password exists in
the controller, but the controller is not secured yet.

6. Click Secure Controller.

7. Enter the password for the controller and click Secure.
If the controller has Nonvolatile Memory
installed, this check box would save the
security state of the controller to Nonvolatile
Memory.
Refer to the Logix Designer Application Help
for additional information on how to Save to
Nonvolatile Memory.

The controller is now secured.

52 Rockwell Automation Publication 1756-PM016F-EN-P - September 2012

 RSLogix 5000 Software CPU Security Tool Chapter 5

Accessing a Secured Controller

When you try to access a controller that has been secured by the Logix CPU
Security Tool and you do not have a local copy of the project file on your
computer, you will be prompted to select the proper file.

To access a secured controller, do the following.

1. From the Communications menu, select Who Active.

2. Select the secured controller and click Go Online.

If you do not have a local copy of the project file on your computer, you
will be prompted to select a file.

Rockwell Automation Publication 1756-PM016F-EN-P - September 2012 53

Chapter 5 RSLogix 5000 Software CPU Security Tool

3. Click Select file to find the project file or to identify a location to save
the project file.
4. Identify a file and click Select.

5. Click Yes.

An unspecified communications dialog box appears.

6. Click OK to continue.

54 Rockwell Automation Publication 1756-PM016F-EN-P - September 2012

 RSLogix 5000 Software CPU Security Tool Chapter 5

If the project file already exists on your system, an error message is

displayed that indicates that the controller is secured and you cannot
go online.

Removing Security from a Controller with the CPU Security Tool

Do these steps to remove security from a controller.

1. Launch the Logix CPU Security Tool.

2. Use RSWho to specify the path to the controller.
3. Select the controller that you want to be unsecured and click OK.

Rockwell Automation Publication 1756-PM016F-EN-P - September 2012 55

Chapter 5 RSLogix 5000 Software CPU Security Tool

4. Select Unsecure Controller.

5. Enter the password for the controller and click Unsecure.

The controller is now unsecured, but the controller still recognizes

the password.
6. Select Exit.
7. Click Yes.

You can now go online with the controller.

56 Rockwell Automation Publication 1756-PM016F-EN-P - September 2012

 RSLogix 5000 Software CPU Security Tool Chapter 5

Removing a Password

Do these steps to remove a password.

1. Click Change Password.

2. Remove the '****' empty string and click OK.

The controller status is now UNSECURED.

Rockwell Automation Publication 1756-PM016F-EN-P - September 2012 57

Chapter 5 RSLogix 5000 Software CPU Security Tool

Notes:

58 Rockwell Automation Publication 1756-PM016F-EN-P - September 2012

 Index

A source protection 31
access
locked controller 53 L
Add-On Instructions
locking controller 49
source protection 32
Logix Designer application 7

C
O
controller
organizer
accessing locked files 53
locked 49 import result 29
organizer import 29
remove security 55
controller resource P
apply security 21 password
CPU Security Tool removal 57
install 49 project
protect 11, 25, 31, 49
secure files 16
D source protect files 32
delete protect
source key file 46 project 11, 25, 31, 49
directory
FactoryTalk 10 R
disable
source protection 47 remove
password 57
resource
E editor 30
emulator routine
install 11 source protection 32
enable security RSLogix 5000
RSLogix 5000 12 enable security 12
secure project file 16

F
S
FactoryTalk
secure
directory 10
security 9 RSLogix 5000 project 16
Service Platform software 15 security
file controller resource 21
sk.dat 40 FactoryTalk 9
source protection 32 import server database 25
technical support 13
sk.dat
I file 40
source key
import
delete file 46
security server database 25 source protection
install
disable routine 47
CPU Security Tool 49 install 31
emulator 11
FTSP software 15 Studio 5000 Engineering and Design Environment 7

Rockwell Automation Publication 1756-PM016F-EN-P - September 2012 59

Index

60 Rockwell Automation Publication 1756-PM016F-EN-P - September 2012

Rockwell Automation Support

Rockwell Automation provides technical information on the Web to assist you in using its products.
At http://www.rockwellautomation.com/support/, you can find technical manuals, a knowledge base of FAQs, technical and
application notes, sample code and links to software service packs, and a MySupport feature that you can customize to make the
best use of these tools.

For an additional level of technical phone support for installation, configuration, and troubleshooting, we offer TechConnect
support programs. For more information, contact your local distributor or Rockwell Automation representative,
or visit http://www.rockwellautomation.com/support/.

Installation Assistance

If you experience a problem within the first 24 hours of installation, review the information that is contained in this manual.
You can contact Customer Support for initial help in getting your product up and running.

United States or Canada 1.440.646.3434

Outside United States or Canada Use the Worldwide Locator at http://www.rockwellautomation.com/support/americas/phone_en.html, or contact your local Rockwell
Automation representative.

New Product Satisfaction Return

Rockwell Automation tests all of its products to ensure that they are fully operational when shipped from the manufacturing facility.
However, if your product is not functioning and needs to be returned, follow these procedures.

United States Contact your distributor. You must provide a Customer Support case number (call the phone number above to obtain one) to your
distributor to complete the return process.
Outside United States Please contact your local Rockwell Automation representative for the return procedure.

Documentation Feedback

Your comments will help us serve your documentation needs better. If you have any suggestions on how to improve this document,
complete this form, publication RA-DU002, available at http://www.rockwellautomation.com/literature/.

Rockwell Otomasyon Ticaret A.Ş., Kar Plaza İş Merkezi E Blok Kat:6 34752 İçerenköy, İstanbul, Tel: +90 (216) 5698400

Publication 1756-PM016E-EN-P - November 201162

Supersedes Publication 1756-PM016D-EN-P - September 2010 Copyright © 2011 Rockwell Automation, Inc. All rights reserved. Printed in the U.S.A.