rsl in x enterprise grg

7/28/2019 Rsl in x Enterprise Grg

1/66

Getting Results Guide

Publication LNXENT-GR001B-EN-PJuly 2005Supersedes Publication LNXENT-GR001A-EN-P


2/66

ii

ContactingRockwell Software

Technical Support Telephone1-440-646-5800Technical Support Fax1-440-646-5801World Wide Webwww.rockwellsoftware.com

Copyright Notice Rockwell Software Inc. All rights reserved. Printed in USA.

This manual and any accompanying Rockwell Software products are copyrighted by RockwellSoftware Inc. Any reproduction and/or distribution without prior written consent from RockwellSoftware Inc. is strictly prohibited. Please refer to the license agreement for details.

Trademark Notice The Rockwell Software logo, ControlLogix, FactoryTalk, FactoryTalk Administration Console,FactoryTalk Diagnostics, FactoryTalk Live Data, FactoryTalk Directory, FactoryTalk AutomationPlatform, RSAssetSecurity, RSOPC Gateway, RSSql, RSBizWare, RSLinx, RSView, RSViewMachine Edition, and RSView Supervisory Edition are registered trademarks of RockwellAutomation.

ControlNet is a registered trademark of ControlNet International.

Ethernetis a registered trademark of Digital Equipment Corporation, Intel, and XeroxCorporation.

Microsoft, Windows, and Windows NT are registered trademarks of Microsoft Corporation.

Adobe and Acrobat are trademarks of Adobe Systems Incorporated.

All other trademarks and registered trademarks are the property of their respective holders and arehereby acknowledged.

Warranty This Rockwell Software product is warranted in accord with the product license. The productsperformance will be affected by system configuration, the application being performed, operatorcontrol, and other related factors.

This products implementation may vary among users.

This manual is as up-to-date as possible at the time of printing; however, the accompanyingsoftware may have changed since that time. Rockwell Software reserves the right to change anyinformation contained in this manual or the software at anytime without prior notice.

The instructions in this manual do not claim to cover all the details or variations in the equipment,procedure, or process described, nor to provide directions for meeting every possible contingencyduring installation, operation, or maintenance.


3/66

iii

1 Introduction 1

Purpose of this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Intended audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Document conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Where to find additional information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Training programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Knowledgebases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Consulting services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Contact us. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2 Welcome to RSLinx Enterprise 3

What is RSLinx Enterprise?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Features and benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Overview of basic concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

FactoryTalk Automation Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

FactoryTalk Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

FactoryTalk Live Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

FactoryTalk Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

FactoryTalk Administration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

RSAssetSecurity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

FactoryTalk Administration Console and RSView Studio. . . . . . . . . . . . . . . . . . . 5

Design-time environment vs. runtime environment . . . . . . . . . . . . . . . . . . . . . . . . 5

Local applications vs. Network applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

A sample application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Installation and configuration checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

3 Installing RSLinx Enterprise 9

Minimum System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Hardware requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Software compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Installing RSLinx Enterprise and/or RSOPC Gateway software. . . . . . . . . . . . . . . . . 10

Updating an existing installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Updating a system that already has a FactoryTalk Automation Platform productinstalled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Contents


4/66

RSLINX ENTERPRISE GETTING RESULTS GUIDE

iv

4 Starting RSLinx Enterprise and exploring the user interface 15

Starting FactoryTalk Administration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

FactoryTalk Administration Console user interface components . . . . . . . . . . . . . . . . 16

Menu bar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Explorer pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Application tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Communications tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Status bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Starting RSLinx Enterprise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

For new applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

For existing applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Exploring the RSLinx Enterprise Communication Setup editor . . . . . . . . . . . . . . . . . 23

Device Shortcuts area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Primary and Secondary tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Offline Tag File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

5 Creating a configuration 27

Setting up communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Adding a driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

If you are running on an Ethernet network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

If you are running on any network other than Ethernet . . . . . . . . . . . . . . . . . . . . 28

Adding a device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Automatically adding a device by browsing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Browsing the virtual backplane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Manually adding a device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Creating shortcuts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

6 Troubleshooting 33

What to check first if youre having problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Troubleshooting Tools for RSLinx Enterprise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

FactoryTalk Diagnostics event log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34RSLinx Enterprise Diagnostics Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Answers to common questions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Where is the online help for RSLinx Enterprise?. . . . . . . . . . . . . . . . . . . . . . . . . 35

Why dont I see RSLinx Enterprise on my Start menu? . . . . . . . . . . . . . . . . . . . 35

Why cant I browse for tags? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Why cant I edit my Machine Edition configuration? . . . . . . . . . . . . . . . . . . . . . 35

How do I know if I have a valid license? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Can I run RSLinx Enterprise and RSLinx Classic on the same computer? . . . . . 36How to contact technical support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36


5/66

CONTENTS

v

A About activations 37

Protecting your activation files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Activating RSLinx Enterprise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Running the activation utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Finding more information about activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Answers to some common questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

My activation files were damaged. What should I do? . . . . . . . . . . . . . . . . . . . . 40

I accidentally deleted the software directory on my hard drive. Do I need to call

Rockwell Software for replacement activation files?. . . . . . . . . . . . . . . . . . . . 40

Why cant I move activation to a new floppy disk on a Windows NT system? . 40

B Advanced topics 41

About the virtual backplane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Supported network routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Moving RSLinx Enterprise configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Moving your shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Moving shortcuts from one computer to another: same application. . . . . . . 43

Moving shortcuts on the same computer: different application . . . . . . . . . . 43

Moving shortcuts from one computer to another: different application . . . . 44

Moving shortcuts from one computer to another: different FactoryTalk

Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Moving your physical layout (drivers and devices) . . . . . . . . . . . . . . . . . . . . . . . 45

Moving from one computer to another . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

C Using RSLinx Enterprise with RSLinx Classic 47

D About RSOPC Gateway 49

About activations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Where to install RSOPC Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Remote OPC Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Glossary 53

Index 57


6/66


vi


7/66

1

1 1Placeholder

Introduction

Purpose of this document

The Getting Results with RSLinx Enterprise guide provides you with information on

installing, navigating, and using RSLinx Enterprise software within the FactoryTalk

Administration Console environment.

Intended audience

We assume that you are familiar with:

Microsoft Windows operating systems

Allen-Bradley programmable logic controllers (PLCs) Rockwell Softwares PLC programming tools

FactoryTalk Administration Console

Document conventions

The conventions used throughout this document for the user interface comply with those

recommended by Microsoft. If you are not familiar with the Microsoft Windows user

interface, we recommend that you read the documentation supplied with the operatingsystem you are using before attempting to use RSLinx Enterprise software.

Where to find additional information

For additional information about RSLinx Enterprise software, consult the following

resources:

Online helpThe online help includes all overview, procedural, screen, and reference information for

the product. The help contains these basic components:

Overview topics

Quick start topics

Step-by-step procedures

Dialog descriptions

The Getting Results Guide is included in a portable document format (PDF) on your RSLinx

Enterprise software installation CD. These files must be viewed using the Adobe Acrobat Reader

software, which is also included on the CD.


8/66


2

To view online help while working in the FactoryTalk Administration Consoleenvironment:

Select Contents from the Help menu on the FactoryTalk Administration Console

main window, then select the book, Work with RSLinx Enterprise, or

ClickHelp on any RSLinx dialog box or property page, or

Press F1.

Release Notes

The electronic Release Notes provide a list of the hardware and software that is necessary

to use the RSLinx Enterprise software effectively and a list of known anomalies,

anomalies fixed, and new features that are available in the current release of the software.

The Release Notes are available from the RSLinx Enterprise software installation CD.

Training programs

Rockwell Automation offers a wide range of training programs, from regularly scheduledclasses to custom-tailored classes conducted at your site.

If you would like more information about these training programs, visit the Rockwell

Software site on the Web or contact the Rockwell Software Training Coordinator. The

Web address and telephone numbers appear on page ii of this document.

Knowledgebases

The Rockwell Automation Customer Support Center offers extensive onlineknowledgebases of tech notes and frequently asked questions for support of non-urgent

issues. To access these knowledgebases, visit support.rockwellautomation.com and select

Knowledgebase under Self-Service Support.

Consulting services

Rockwell Automation provides expert consulting and turnkey implementation of the

RSLinx Enterprise software. Please contact your local representative for more

information.

Contact us

Please use the feedback form packaged with your software to report errors or to let us

know what information you would like to see added in future editions of this document.

You can also send an email message to [email protected] with any comments

about Rockwell Softwares products and services.


9/66

3

2 2Welcome

Welcome to RSLinx Enterprise

This chapter includes the following information:

What is RSLinx Enterprise?

Features and benefits

Overview of basic concepts

A sample application

Installation and configuration checklist

What is RSLinx Enterprise?

RSLinx Enterprise is a data server that links networks and devices to Microsoft

Windows 2000-, XP-, and CE-based applications.It provides communication services

between your applications and devices on the plant floor so that on your Windows

computer, you can see values from your plant floor devices such as sensor readings and

other programmable logic controller (PLC) data.

Features and benefits

RSLinx Enterprise provides the following features and benefits:

Allows access to operator interfaces and data logger information in programmable

controllers and devices.

Optimized for Logix communications and provides a focused set of available

communication drivers and routing options.

Supports Local applications (also called stand-alone applications) for smaller systems

and Network applications (also called distributed applications) for larger, widely

dispersed systems.

For Network applications, provides the option of specifying a secondary, or

redundant, server to take over if the primary server fails.

When used within the FT Administration Console environment, provides editingcapabilities outside of RSView Studio. You no longer have to install RSView Studio

onto every computer to edit RSLinx Enterprise configurations.

Provides a means to monitor diagnostic items associated with RSLinx Enterprise

workstations and shortcuts using RSLinx Enterprise Diagnostics Monitor. RSLinx

Diagnostics Monitor is installed automatically with RSLinx Enterprise.


10/66


4

Provides a means for system administrators to control access to resources (such asapplications and areas) or the ability to perform tasks (such as read and write) in the

automation system using RSAssetSecurityTM. RSAssetSecurity is installed as part of

the FactoryTalk Automation Platform.

Provides OPC connectivity for third party clients using RSOPC Gateway. See

Appendix D for more information about RSOPC Gateway.

Overview of basic concepts

It is important to understand some basic concepts about FactoryTalk and RSLinx

Enterprise before you begin working with RSLinx Enterprise within the FactoryTalk

Administration Console environment. For more detailed information about FactoryTalk,

refer to the FactoryTalk online help.

FactoryTalk Automation Platform

FactoryTalk Automation Platform (FTAP) is a manufacturing information platform that

integrates and connects plant-wide control systems with the production facility. It

provides common services (such as access to real-time data and diagnostics) and allows

plant resources to be shared throughout a production facility. It includes the following

components:

FACTORYTALK DIRECTORY

FactoryTalk Directory provides a common address book of factory resources. Changes

made to an automation system automatically update across all participants in a

FactoryTalk-enabled application.

FACTORYTALK LIVE DATA

FactoryTalk Live Data provides reliable, enterprise-wide access to real-time

manufacturing data by managing the connections between FactoryTalk-enabled products

and data servers.

FACTORYTALK DIAGNOSTICS

FactoryTalk Diagnostics provides the ability to log errors, warnings, and other status

messages generated throughout a FactoryTalk-enabled system to a central location.

FACTORYTALK ADMINISTRATION CONSOLE

FactoryTalk Administration Console is a standalone tool that enables you to configure and

manage FactoryTalk-enabled applications and is the user interface to RSLinx Enterprise.

RSLinx Enterprise is launched from within FactoryTalk Administration Console.


11/66

2 WELCOMETO RSLINX ENTERPRISE

5

2Placeholder

RSAssetSecurityRSAssetSecurity is intended to improve the security of your automation system by

limiting access to those with a legitimate need. RSAssetSecurity authenticates user

identities and authorizes user requests to access a FactoryTalk-enabled system. These

security services are fully integrated into the FactoryTalk Directory and are included as

part of the FactoryTalk Automation Platform that installs with many products.

Access to resources (such as applications, areas, or servers) and the ability to perform

tasks (such as read or write) are governed by the permissions set in RSAssetSecurity. As aresult, some components on a dialog may be grayed out, or entire dialogs or context menu

selections described in the online help may be inaccessible, if you do not have the

appropriate permission. For more information about using RSLinx Enterprise with

RSAssetSecurity, refer to the topic titled Considerations when using RSLinx Enterprise

with RSAssetSecurity in the RSLinx Enterprise online help.

If you prefer not to use security services, you can grant all users full access to your

automation system. For more information on configuring RSAssetSecurity, refer to the

topic titledAbout RSAssetSecurity in the RSLinx Enterprise online help. Links areprovided to the FactoryTalk online help.

FactoryTalk Administration Console and RSView Studio

You can edit RSLinx Enterprise configurations in either the FactoryTalk Administration

Console environment or the RSView Studio environment. However, depending upon your

application, one environment may be better suited to meet your development needs.

For example, to edit an RSView Machine Edition (ME) project, you need to be in RSViewStudio because of the specific needs of RSView ME.

For Network (distributed) applications, you can be in either the FactoryTalk

Administration Console or RSView Studio environments to edit RSLinx Enterprise

configurations. However, you cannot edit HMI server properties such as graphics, data

logs, etc., in the FactoryTalk Administration Console environment.

For Local applications, you can edit locally or remotely within FactoryTalk

Administration Console (which is installed by default) or edit locally or remotely withinRSView Studio. You no longer are required to install RSView Studio onto every computer

to edit RSLinx Enterprise.

Design-time environment vs. runtime environment

RSLinx Enterprise is comprised of design-time and runtime environments. The design-

time environment provides the user interface that enables you to set up devices, drivers,

and shortcuts that are ultimately used by the runtime environment (by applications such as

RSView Supervisory Edition, RSSql, and RSView Machine Edition). Based on this


12/66


6

configuration data, the runtime environment executes read/write requests it receivesduring runtime operation.

To begin defining a configuration, you must first add an RSLinx Enterprise server to the

FactoryTalk Directory. This can be done within the FactoryTalk Administration Console

or RSView Studio environments.

An RSLinx Enterprise configuration consists of:

A list of communication devices and their settings (node, baud rate, etc.).

Device drivers and their associated configuration settings.

A list of potential target devices with which it can communicate (that is, exchange

data).

Device shortcuts, which represent a specific path to a processor. This is similar to

DDE/OPC topics in RSLinx Classic.

Local applications vs. Network applicationsAn application is a set of data elements used to implement a control system. RSLinx

Enterprise supports two types of applications: Local and Network.

In Network applications, also called distributed applications, computers that are

distributed across the plant are used to share data and collaborate with each other to build

customer applications. A Network application organizes project elements from multiple

FactoryTalk-enabled products, potentially on different computers. All of the computers

participating in a particular application share a common FactoryTalk Directory located ona network computer.

In Local applications, all application components are located on the same computer as the

server. A Local application is accessible only from the local computer where it resides and

does not share its data or any of its project elements with other applications. Redundancy

is not supported in Local applications. Refer to the FactoryTalk online help for more

information about Local applications.

Network applications can be organized and subdivided into logical divisions called areas.

For example, separate areas may correspond with separate manufacturing lines in a

facility, separate plants in different geographical locations, or different manufacturing

processes. Areas cannot be created for Local applications.

Applications and areas are created using FactoryTalk Administration Console or RSView

Studio. Refer to the FactoryTalk Administration Console online help or RSView Studio

online help for more information.


13/66

2 WELCOMETO RSLINX ENTERPRISE

7

2Placeholder

A sample applicationThe following diagram shows an example of a Network application. All of the computers

in the example are using computer 1 as the FactoryTalk Directory server.

RSLinx Enterprise is installed on computers 2 and 3; however, they serve different

purposes. RSLinx Enterprise on computer 2 takes advantage of its design-time

environment by enabling you, using FactoryTalk Administration Console or RSView

Studio, to not only configure RSLinx Enterprise on this computer but to configure it on

remote computers, such as computer 3.

Computer 3 is set up to be the data server, which takes advantage of the RSLinx

Enterprise run-time environment. However, if modifications to the configuration are

necessary, you can log into computer 3, launch the FactoryTalk Administration Console,

and make the changes.

FTAP = FactoryTalk Automation Platform

IIS = Microsoft Internet Information Services


14/66


8

Installation and configuration checklistUse the following checklist to guide you through the installation and configuration

process.

Step Description Refer to:

1. Read and understand the RSLinx Enterprise Getting

Results Guide.

2. Plan your system. Plan a FactoryTalk system in

the FactoryTalk online help.

3. Verify your personal computer meets the minimum

hardware and software requirements.

Minimum System requirements

on page 9.

4. Install FactoryTalk Automation Platform and

RSLinx Enterprise software. Optionally, install RSOPC

Gateway software.

Installing RSLinx Enterprise

and/or RSOPC Gateway

software on page 10.

5. Configure RSAssetSecurity. Getting started with security in

the FactoryTalk online help.

6 Add an RSLinx Enterprise data server. Starting RSLinx Enterprise on

page 19.

7. Specify general RSLinx Enterprise data server

properties.

Starting RSLinx Enterprise on

page 19.

8. Optionally, set up redundancy (Network applications

only).

On the Redundancy tab: on

page 21.

9. Add drivers and devices. Adding a driver on page 28.

10. Create shortcuts that point to your target devices. To create a device shortcut: on

page 30.


15/66

9

3

3InstallingandStarting

Installing RSLinx Enterprise

The RSLinx Enterprise installation CD-ROM provides wizards to guide you through the

installation process. This process includes the installation of the FactoryTalk Automation

Platform.

This chapter contains the following information:

System requirements Installing RSLinx Enterprise software for the first time

Updating an existing installation

Minimum System requirements

To effectively use RSLinx Enterprise, your personal computer must meet the following

minimum hardware and software requirements:

Hardware requirements

To install RSLinx Enterprise software, you will need the following hardware:

an Intel Pentium II processor (300 MHz or faster recommended) with a minimum of

125 Megabytes (MB) of RAM (256 MB recommended with Windows XP), and a

minimum of 35 MB of hard disk space

a floppy drive for product activation

Software requirements

To run RSLinx Enterprise, you require Microsoft Internet Explorer 6.0 (or later), and one

of the following operating systems:

Microsoft Windows XP Professional with the latest Service pack

Microsoft Windows 2000 Professional, Service Pack 4 or later

Microsoft Windows Server 2003

Software compatibility

To run effectively, all Rockwell Software components must be of the same Coordinated

Product Release (CPR) version. To check the CPR version of each Rockwell Software

product, select Start > Setting > Control Panel > Add or Remove Programs. The CPR

version number is shown next to the product name (for example, RSLinx Enterprise (CPR

7)).


16/66


10

Installing RSLinx Enterprise and/or RSOPC Gateway softwareTo install RSLinx Enterprise and/or RSOPC Gateway software, use the follow procedure:

1. Insert the RSLinx Enterprise installation CD into the CD-ROM drive.

2. Select the desired installation option. Options 1 and 2 provide separate installations

for RSLinx Enterprise and RSOPC Gateway. If you need to install both of these

products, select Option 3. Option 4 installs the required files to connect to RSOPC

Gateway for servers that do not support enumeration. Refer to Appendix D in this

manual or to the help files within options 2 and 3 for more information about RSOPC

Gateway and RSOPC Gateway Remote OPC Client Setup.

If autorun is: Then:

enabled The Setup program starts automatically, and the RSLinx Enterprise and

RSOPC Gateway opening screen displays. Proceed to step 2.

disabled a.1. ClickStart, and then clickRun. The Run dialog box displays.

b. In the Open control, type x:\setup, wherex is the letter of the

drive containing the RSLinx Enterprise/RSOPC Gateway CD,

and clickOK. The RSLinx Enterprise and RSOPC Gateway

installation opening screen displays.

RSLinx Enterprise installation opening screen


17/66

3 INSTALLING RSLINX ENTERPRISE

11

3Placeholder

3. Follow the instructions in the order they are presented on the opening screen. View Release Notes: The Release Notes may contain more up-to-date information

than was available when this document was published. Read the Release Notes for

the product you are installing before continuing with the installation.

View Getting Results Guide: This selection provides the RSLinx Enterprise

Getting Results Guide in a searchable PDF file. Read and understand this guide

before working with RSLinx Enterprise.

View RSOPC Gateway Help: This selection displays the online help files forRSOPC Gateway. Read the help files before working with RSOPC Gateway.

Install FactoryTalk Automation Platform: Click this step to start the installation

wizard for FactoryTalk Automation Platform. FactoryTalk Automation Platform

CPR 7 must be installed on the computer before you install RSLinx Enterprise.

Included with this installation is FactoryTalk Administration Console, which is a

stand-alone tool that allows you to configure and manage FactoryTalk-enabled

applications, such as RSLinx Enterprise. For more information about FactoryTalkand FactoryTalk Administration Console, refer to the FactoryTalk online help.

Install RSLinx Enterprise and/or Install RSOPC Gateway: Click this step to

start the installation wizard for RSLinx Enterprise and/or RSOPC Gateway. Youwill be prompted to do the following for each installation:

Accept the license agreement

Enter your user name and organization

Enter your serial number

Select a setup type:

Standard Feature Set Installation to Default Location. This is the default

selection, which installs both the runtime and the design-time components

to C:\Program Files\Rockwell Software\.

Custom Location Selection and/or Custom Feature Selection. Select this

option if you want to install RSLinx Enterprise or RSOPC Gateway to a

directory other than the default.

Install Activation: Rockwell Software uses a software key to implement copy

protection for Windows-based software products. Every software product has a

Tip: If you have already installed another CPR 7 FactoryTalk Automation Platform

product, you already have Factory Talk Automation Platform, and possibly RSLinx

Enterprise, installed on your computer. Refer to Updating a system that already has a

FactoryTalk Automation Platform product installed on page 13 for more information.


18/66


12

unique key. The key is located in an activation file, which is on a Master diskthat was shipped with your software.

You can install the software on any number of computers; however, you are

only licensed to run the software on one computer at a time. After you install

the software, you will be prompted to install the activation, which moves the

unique key onto your disk drive.

If you choose to install activation, insert the Master disk into the 3.5-inch disk

drive. Follow the instructions that appear on the screen to activate the software.For more information about activation, refer to Appendix A.

If at a later date you want to move the activation to another computer, or just

remove it altogether, you will need to move the key back onto the Master disk.

For more information about moving software keys and software activation,

refer to Appendix A.

Note that activation is not required for Local applications (i.e., RSView

Machine Edition or RSView Supervisory Edition Stand-alone products).

For information about RSOPC Gateway activations, refer to Appendix D.

Review Release Notes: If you want to review the Release Notes, leave the

checkbox checked.

Check for Product Updates: Click this step to launch the Product Updates page,

which provides links to any late-breaking product updates and to the Rockwell

Automation Support Knowledgebase.

4. When you are finished installing the software, clickExit, remove the RSLinx

Enterprise installation CD from the CD-ROM drive, and remove the Master disk from

the disk drive. Store them in a safe place.


19/66

3 INSTALLING RSLINX ENTERPRISE

13

3Placeholder

Updating an existing installationThe RSLinx Enterprise Installation automatically removes and replaces previous versions

of RSLinx Enterprise with the most current version during the installation process.

However, you can also update an existing installation using the following procedure:

1. Select Start > Settings > Control Panel > Add or Remove Programs and remove

RSLinx Enterprise and FactoryTalk Automation Platform.

2. Reboot your PC.

3. Follow the procedures in Installing RSLinx Enterprise and/or RSOPC Gateway

software on page 10.

4. You will be prompted to install activation. If activation was previously installed, it is

not necessary to move the activation. Uncheck the checkbox. If activation was not

previously installed, insert the Master disk into the 3.5-inch disk drive and follow the

instructions that appear on the screen. For more information on activation, refer to

Appendix A in this manual.

5. When you are finished installing the software, clickExit, remove the RSLinx

Enterprise installation CD from the CD-ROM drive, and remove the Master disk from

the disk drive. Store them in a safe place.

Updating a system that already has a FactoryTalk AutomationPlatform product installed

If you are installing RSLinx Enterprise on a system on which other FactoryTalk

Automation Platform products are currently installed, you must first verify that all

products are of the same CPR number. You can do this using Add or Remove Programs:

Start > Settings > Control Panel > Add or Remove Programs

The CPR number is shown with the product. If any products are of a previous release, you

must uninstall the products (uninstalling FactoryTalk Automation Platform last), reboot,

and then use the installation CD to install the correct release version.

If the CPR versions are compatible, verify that FactoryTalk Administration Console isinstalled using the following procedure:

1. Select Start > Settings > Control Panel > Add or Remove Programs.

2. Select FactoryTalk Automation Platform from the Add or Remove Programs

screen.

3. Select Change to start the installation wizard.

4. Select Modify from the Program Maintenance screen.


20/66


14

5. Verify the installation status of FactoryTalk Administration Console. Check the box toinstall it, if it is not already checked.

6. Click Install.

7. Click Finish when the installation is complete.


21/66

15

4

4Exploringtheinterface

Starting RSLinx Enterprise and exploringthe user interface

This chapter includes the following information:

Starting FactoryTalk Administration Console

Basic FactoryTalk Administration Console user interface components

Starting RSLinx Enterprise RSLinx Enterprise user interface components

Exploring the Communication Setup dialog

Starting FactoryTalk Administration Console

RSLinx Enterprise is launched from within Factory Talk Administration Console. To start

FactoryTalk Administration Console, use the following procedure:

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

Administration.

NOTE: Depending on the security settings, you may be required to enter a User name and

Password to work with FactoryTalk Administration Console. Refer to the FactoryTalk online

help for more information.

Select the FactoryTalk Directory you want to use. Refer to chapter 2 for more

information about Network and Local applications.


22/66


16

FactoryTalk Administration Console user interface components

FactoryTalk Administration Console is made up of the following basic user interface

components:

Menu bar

The menu bar contains the menu items for the active window.

Toolbar

The toolbar contains buttons for commonly used menu items so you can quickly access

the items without opening the menus. When you point to a button on the toolbar, the name

of the button is displayed in a tooltip.

Explorer pane

The Explorer pane contains the Application tab and the Communications tab.

Workspace

Communications tab

Application tab

Toolbar

Menu bar

Explorer pane

Status bar

Application tree


23/66

4 STARTING RSLINX ENTERPRISEANDEXPLORINGTHEUSERINTERFACE

17

4Placeholder

APPLICATIONTAB

The Application tab displays your applications in tree format as you create them. The

application tree allows you to view and manage your applications. You use FactoryTalk

Administration Console to add references to data servers, such as RSLinx Enterprise,

within FactoryTalk applications.

For more information about creating applications in the FactoryTalk Administration

Console, refer to the FactoryTalk Administration Console online help.


24/66


18

COMMUNICATIONSTAB

The Communications tab provides a view from the computer you are currently using. It

allows you to browse for devices your computer can access on the network (similar to

RSWho in RSLinx Classic) and displays them in tree format. The tree is composed of

networks, chassis, devices, and services. The status bar on this tab indicates if the

computer is online or offline, and whether it is browsing or not browsing.

Workspace

The workspace is an empty pane when you start FactoryTalk Administration Console.

When you launch RSLinx Enterprise from the Explorer, the Communication Setup editor

displays in the workspace.

Status bar

The status bar provides different kinds of information depending on where the pointer is

and what FactoryTalk Administration Console is doing. It can provide information about

the active window or selected tool.


25/66


19

4Placeholder

Starting RSLinx EnterpriseHow you start RSLinx Enterprise depends on whether or not you have already created an

application. This following sections describe how to start RSLinx Enterprise for new and

existing applications. Refer to chapter 2 for more information about applications.

For new applications

For new applications, you must add RSLinx Enterprise to the FactoryTalk Directory

before you can launch it.Use the following procedure to add an application and launch RSLinx Enterprise:

1. In the Explorer pane, expand the application tree where you want to add a data server.

2. Right-click the application icon or the area name (for Network applications) where

you want to add the data server.

3. From the context menu, select New Data Server, and then select RSLinx Enterprise

Data Server...


26/66


20

The RSLinx Enterprise Server Properties dialog displays.

4. Both Local and Network applications require you to specify server properties on the

General tab of the RSLinx Enterprise Server Properties dialog. Type the name and a

description for the data server.

For Network applications, a Redundancy tab is available for setting up a secondary

server. The secondary, or redundant, server takes over for the primary server if

communications are interrupted.If you are going to set up a redundant server, click the Redundancy tab. Otherwise,

clickApply to save the server information, clickOKto close the dialog, and then

continue to step 5.

For Local applications, the computer hosting the RSLinx Enterprise server defaults to localhost

and cannot be changed. For Network applications, identify the computer where the RSLinx

Enterprise server resides in the Computer hosting the RSLinx Enterprise server box by either

clicking Browse or typing the computer name.


27/66


21

4Placeholder

(Step 4, continued, for redundancy only)

On the Redundancy tab:

a. Select the Provide redundancy using a second server check box.

b. Type the name of the computer that the secondary server will run on, or clickBrowse to locate and select a computer.

c. Select a switch back option.

d. Click Apply to save the secondary server information. Then clickOKto close the

dialog.

5. Expand RSLinx Enterprise in the application tree.


28/66


22

6. Double-click Communication Setup. The Communication Setup dialog displays in the

workspace and you can begin creating a configuration. Refer to chapter 5 for more

information.

For existing applications

For existing applications, use the following procedure to launch RSLinx Enterprise:

1. In the Explorer pane, expand the appropriate application in the application tree.

2. Expand RSLinx Enterprise.

3. Double-click Communication Setup. The Communication Setup dialog displays in the

workspace and you can begin creating a configuration. Refer to chapter 5 for this

procedure.

Double-click

Communication Setup to

launch the Communication

Setup editor


29/66


23

4Placeholder

Exploring the RSLinx Enterprise Communication Setup editor

Use the Communication Setup editor to add drivers, add devices, set up driver and device

properties, and set up device shortcuts in your RSLinx Enterprise configurations.

The Communication Setup editor consists of the Device Shortcuts area, the Offline Tag

File area, and tabs on the right-hand side of the screen (Primary, Secondary) whose

function varies based on the application or product used. For Network applications, you

may see a Secondary tab in addition to the Primary tab on the right-hand side of the

screen. Refer to Primary and Secondary tabs later in this chapter for more information.

The Add, Remove, and Apply buttons

are used with the Device Shortcuts area

of the Communications Setup editor.

The OK, Cancel, and Help buttons apply

to the entire Communications Setup

editor.

Device Shortcuts area

Communications tree

Primary,

Secondary tabs



30/66


24

Device Shortcuts area

The Device Shortcuts area is used to name and apply device shortcuts. A device shortcut

represents a route to a specific device with which a client application will communicate. It

is a symbolic reference to a physical device, similar to a topic in RSLinx Classic. The

shortcut names are what you will see when your browse in RSView Studio.

See chapter 5 for more information on device shortcuts and how to create and apply them.

Primary and Secondary tabs

The Primary tab is used to configure the primary data server. This is the main data server

that will serve data. If you set up a secondary (redundant) server, which is the backup data

server that RSLinx Enterprise will be running on if the primary data server fails, you

configure it on the Secondary tab.

If you have set up only a primary server, only the Primary tab appears in the

Communication Setup dialog. If you have set up both a primary and a secondary data

server, both the Primary and the Secondary tabs appear in the Communication Setup

editor.

The Primary and Secondary tabs:

Display the communication configuration on this computer and the properties

associated with the primary or secondary RSLinx Enterprise data server to which it is

pointing.

Store drivers, devices, and shortcuts in a project-associated file as you add them to the

tabs.

Are online-enabled, which means they are capable of browsing attached networks and

automatically discovering devices when you click the node (whether it is a driver or a

device) or select Start Browsing from the context menu on that node. The status

indicators at the bottom of the tab indicate if it is in Online or Offline Mode, Browsing

or Not Browsing.

4 STARTING RSLINX ENTERPRISE AND EXPLORING THE USER INTERFACE


31/66


25

4Placeholder

Keep the following in mind about the secondary server:

The secondary (redundant) server cannot be hosted on the same computer as the

primary server.

Although they may use different communication paths, the shortcuts on both the

primary and secondary servers must point to the same physical data acquisition target

running the same program.

Offline Tag File

RSLinx Enterprise provides access to offline tags by enabling you to point to and browse

within a Logix 5000 program file (.acd). If a network is not connected to the controller,

developers can still work with offline tags. Developers can build an entire application

offline, without connecting to controllers, and then deploy the application to a runtime

system later.

Clicking Browse displays the Offline Processor File Selection dialog. This is used during

the offline tag browsing procedure.

NOTE: The .acd file must be located on the local PC, not in a networked location.

Refer to Offline tag browsing in the RSLinx Enterprise online help for more information.



32/66


26


33/66

27

5

5CreatingaConfiguration

Creating a configurationThis chapter includes the following information:

Setting up communications

Adding a driver

Adding a device

Creating shortcuts

To begin working with RSLinx Enterprise, you must add an RSLinx Enterprise data

server to the FactoryTalk Directory. This procedure is described in chapter 4. Once you

have added RSLinx Enterprise and configured its general properties, use the

Communication Setup editor to add drivers, set up driver and device properties, and set up

device shortcuts.

Setting up communications

To launch the Communication Setup editor, double-click Communication Setup from theExplorer under the RSLinx Enterprise data provider.

Double-clickCommunication Setup to

launch the Communication

Setup editor



34/66

28

Adding a driver

A driver is software that interacts with a network interface (such as the interface that

connects your computer to the Ethernet network)and manages the exchange of

communication packets over the network to which the interface is attached.Refer to the

RSLinx Enterprise online help for information about the drivers that are supported.

If you are running on an Ethernet network

To add a driver if you are running on an Ethernet network, right-click on the network

shown (EtherNet), and select Start Browsing to populate the driver with devices.

If you are running on any network other than Ethernet

To add a driver if you are running on any network other than Ethernet, right-click thedevice shown at this workstation, and select Add Driver.

Adding a device

You can add devices by browsing the network, or you can manually add devices.

Automatically adding a device by browsing

As described in the Design-time environment vs. runtime environment section inchapter 2, the list of potential data acquisition targets for RSLinx Enterprise can be

gathered during online browsing. During a browse cycle, RSLinx Enterprise scans the

network addresses, determines the present devices, and displays them in tree format. The

display shows the set of devices discovered during the most recent browse cycle. In this

way, RSLinx Enterprises browse cycle is like that of RSLinx Classic.

In RSLinx Enterprise, if a station is not found during a browse, it does not appear on the

display, regardless of whether or not that station was previously discovered. This isdifferent from RSLinx Classic, where a red X is used to highlight a station that was

discovered on a previous browse but is no longer present.

If you are running on an EtherNet network, right-click the network shown (EtherNet) to

start browsing. The driver is automatically populated with devices.

Some Ethernet devices may not support the browse protocol used by RSLinx Enterprise on

Ethernet. If the devices you expect to appear during the browse do not display, manually add the

devices to the workstation's Ethernet network by right-clicking on the network and selecting Add

Device.

5 CREATINGACONFIGURATION


35/66

29

5Placeholder

BROWSINGTHEVIRTUALBACKPLANE

When you select the virtual backplane on the user interface, RSLinx Enterprise may not

automatically discover devices that reside in it. This is most likely to happen if you have

added the device with a separate software package such as the SoftLogix Chassis Monitor

or RSLinx Classic.

If you think you have devices resident in your virtual backplane that are not showing up

on the RSLinx Enterprise user interface, you can right-click the virtual backplane and

select Start Browsing orShow All Devices to see those devices. Note that saved

configuration data is not lost if the devices do not appear.

Manually adding a device

You can manually add the devices to the workstation's network using the following

procedure:

1. Right-click the network or driver and select Add Device.

A list of Available Devices that applies only to the driver you selected displays.



36/66

30

2. Select the device you wish to add and clickOK. The device is added below the driver

or network on the communications tree. Unless your application requires a specific

device version, you should select the most recent revision of that device.

For information on device revisions in the device list, see the drivers, device, and

shortcuts section of Frequently Asked Questions in the online help. The online help also

provides information about how to add and configure drives and devices.

Creating shortcuts

In RSLinx Enterprise, a device shortcut represents a specific path to a processor (similar

to DDE and OPC topics in RSLinx Classic). In other words, they provide a mapping

between a user-defined name and a target device.

Device shortcuts are stored on a per-FactoryTalk-application basis versus being associated

with the RSLinx Enterprise server itself. Each application can have its own set of device

shortcuts for a particular server. Therefore, even if you are using the same computer to

create multiple applications, each application must have its own set of shortcuts defined.

The shortcuts are not copied over from one application to another.

To create a device shortcut:

1. From the Communication Setup dialog, clickAdd. A default shortcut named "NEW

SHORTCUT" is created in the Device Shortcut area.

If you wish to change the name of the shortcut, you can enter the new name at this

point.

5 CREATINGACONFIGURATION


37/66

31

5Placeholder

2. Navigate to the device on the communications tree you want the shortcut to point to,

and clickApply.

3. When you are finished adding shortcuts, clickOKto close the Communication Setup

dialog.

The shortcuts are not saved until you click OK to close this dialog.



38/66

32


39/66

33

6

6Findinginformation

TroubleshootingThis chapter includes the following information:

What to check first if youre having problems

Troubleshooting tools for RSLinx Enterprise

Answers to common questions

How to contact technical support

What to check first if youre having problems

Does your PC meet the minimum hardware and software requirements? Refer to

chapter 3 for these requirements.

Is the software installed correctly? For optimum results, make sure any previous

versions of the software have been removed using the Add/Remove function on the

Windows Control Panel. Then reboot your PC and begin installing the product from the

RSLinx Enterprise installation CD. Reboot your PC after installing the software before

you begin using RSLinx Enterprise.

Is RSLinx Classic installed on your PC? Verify that it is not running as a service in the

background when you attempt to install RSLinx Enterprise.

Have you installed activation? RSLinx Enterprise software is copyright protected and

must be activated before you can begin using it. Refer to Appendix A for more

information about activation. Note that if you have configured a redundant server, this

must also be activated.

Was a current CPR version of FactoryTalk Automation Platform already installed

on your PC? Verify that FactoryTalk Administration Console was also installed using the

following procedure:

1. Select Start > Settings > Control Panel > Add or Remove Programs.

2. Select FactoryTalk Automation Platform from the Add or Remove Programs

screen.3. Select Change to start the installation wizard.

4. Select Modify from the Program Maintenance screen.

5. Verify the installation status of FactoryTalk Administration Console. Check the box to

install it, if it is not already checked.

6. Click Install.

7. Click Finish when the installation is complete.



40/66

34

Troubleshooting Tools for RSLinx Enterprise

RSLinx Enterprise provides a number of diagnostic tools that enable you to troubleshoot

problems if they occur:

FactoryTalk Diagnostics event log

RSLinx Enterprise Diagnostics Monitor

FactoryTalk Diagnostics event log

In a FactoryTalk-enabled automation system, Rockwell Software products monitorsystem activity and generate detailed diagnostic messages. Meanwhile, FactoryTalk

Diagnostics collects these activity, warning, error, and audit messages from all

participating products throughout a distributed system and routes them to Local Logs

(also called event logs) on each computer.

If you encounter a problem, you can review the events in the log that led up to the problem

to assist in determining the cause. Or you can monitor the log to identify potential

problems and take corrective action before a problem occurs.

Refer to the FactoryTalk online help for more information about FactoryTalk Diagnostics

and the event log.

RSLinx Enterprise Diagnostics Monitor

RSLinx Enterprise Diagnostics Monitor enables you to monitor the runtime values of

internal counters and strings, called predefined items, that are made available by network

Data Providers for diagnostic purposes. These items differ from regular data items in that

they access internal information contained in RSLinx Enterprise. Using RSLinxEnterprise Diagnostics Monitor, you can monitor the predefined items associated with

RSLinx Enterprise workstations and shortcuts.

To use RSLinx Enterprise Diagnostics Monitor:

RSLinx Enterprise must be installed and running on one or more host computers on

the network.

The diagnostics client must have access to a target workstation that has an application

with predefined items associated with it. A client must be accessing those predefinesin order for the predefines to be displayed on the Diagnostic Monitor.

To run RSLinx Enterprise Diagnostics Monitor, select Start > Programs > Rockwell

Software > RSLinx > Tools > RSLinx Enterprise Diagnostics Monitor.

6 TROUBLESHOOTING


41/66

35

6Placeholder

Answers to common questions

Where is the online help for RSLinx Enterprise?

From the FactoryTalk Administration Console, select Help > Contents > Work with

RSLinx Enterprise. If this file is not present, RSLinx Enterprise is not installed on your

PC. Refer to chapter 3 for the installation procedure.

Why dont I see RSLinx Enterprise on my Start menu?

RSLinx Enterprise uses the FactoryTalk Administration Console to edit all of theconfiguration data and does not require a standalone interface. RSView Studio can also

make changes to RSLinx Enterprise configurations, so Supervisory Edition and Machine

Edition users do not have to leave their main user interface.

Why cant I browse for tags?

Tag browsing (that is, browsing online for data items) is not supported in the FactoryTalk

Administration environment. To browse for tags and connect them to components in yoursystem, you must be in the RSView Studio environment or in the RSSql or BizWare tag

browsers.

Why cant I edit my Machine Edition configuration?

Editing HMI servers within applications, namely Supervisory Edition Distributed,

Supervisory Edition (SE) Station, and Machine Edition (ME), is not supported in the

FactoryTalk Administration Console environment. The FactoryTalk Administration

Console is intended to configure and manage your application. To edit SE or MEconfigurations, you must be in the RSView Studio environment.

How do I know if I have a valid license?

Check the FactoryTalk Diagnostics log. An information message is logged if the

activation file or the Master disk is not detected by the system when you launch RSLinx

Enterprise. Refer to the FactoryTalk online help for more information about diagnostic

messages. Also remember that SE Station (stand-alone) applications and RSView ME

applications do not require any type of RSLinx Enterprise activation. Applications that are

Networked such as RSView SE Distributed or RSSql/BizWare applications do require

an RSLinx Enterprise activation.



42/66

36

Can I run RSLinx Enterprise and RSLinx Classic on the same

computer?

RSLinx Enterprise and RSLinx Classic can run simultaneously on the same computer,

although there are some considerations that you must be aware of to avoid resource

conflicts between these two applications. Refer to Appendix C for more information.

How to contact technical support

Questions concerning installation and use of RSLinx Enterprise software are handled by

the Rockwell Automation Customer Support Center. The center is staffed Monday

through Friday, except on U.S. holidays, from 8 AM to 5 PM Eastern time zone for calls

originating within the U.S. and Canada.

To reach the Customer Support Center, call 440-646-5800 and follow the prompts. For

calls originating outside the U.S./Canada, locate the number in your country by visiting

support.rockwellautomation.com/contact information.

When you call, you should be at your computer and prepared to give the following

information:

the product serial number and version number, which can be found in the client

software by selecting Help > About FactoryTalk Administration Console...

the type of hardware you are using

the exact wording of any errors or messages that appeared on your screen

a description of what happened and what you were doing when the problem occurred

a description of how you attempted to solve the problem


43/66

37

A

AFrameMakerQuickTips

About activationsRockwell Softwares products are copy-protected. Only a computer with access to the

activation key can run the software. The key is located in an activation file, which is

originally located on the Master disk supplied with the RSLinx Enterprise product. The

activation file contains one activation key per product. Each key contains one or more

licenses depending on how many copies of the product you have purchased.

During the setup process, the setup program gives you the opportunity to move the

activation file from the Master disk to the root directory of the drive on which youre

installing the software.

When you launch RSLinx Enterprise, the software first checks your local hard drives, then

network hard drives, and finally local floppy drives for activation. If the system fails to

detect either the activation file or the Master disk, an error is logged to FactoryTalkDiagnostics. Refer to the FactoryTalk online help for more information about diagnostic

messages.

Protecting your activation files

To avoid damaging your activation files, do not perform the following operations with

activation files on the hard drive.

Restore from backup

Upgrade the operating system

Compress or uncompress the hard drive

Defragmentation utilities will not harm activation files.

Store your Master disk in a safe place. If your activation becomes damaged, the Master disk maybe the only means to run your software in an emergency.

Systems attached to extensive networks can take quite a while to search for activation files on all

available drives. You can use the CHECKDRIVES environment variable to specify and/or limit

the drives your software checks for activation files and to specify the order in which they are

checked. Refer to the activation utilities online help file by selecting Help > Copy Protection.

Certain anti-virus software packages, such as Norton Anti-virus, can corrupt the activation files.

Configure your anti-virus software to avoid checking the files EVRSI.SYS and 386SWAP.PAR.



44/66

38

Before running any type of utility that may modify the structure or organization of the

hard drive, remove activation from the hard drive:

1. Use the Move Activation utility (EvMove) to move activation files from the hard

drive to an activation disk.

Run EVMOVE.EXE from your hard drive (located in C:\Program Files\Rockwell

Software\RSUtil if you accepted the default directory location during installation).

2. Perform the hard disk operation.

3. Move the activation files back to the hard drive.

Activating RSLinx Enterprise

Depending on your needs, you can activate RSLinx Enterprise from any of the following:

Hard drive.The activation key resides on your computers hard disk. Use this method ifyou will typically use RSLinx Enterprise on only one computer. This is the default method

if you activate RSLinx Enterprise during installation. To run RSLinx Enterprise on a

different computer, move the activation key back to the Master disk, and then to the harddrive of the new computer.

Diskette drive.The activation key resides on a floppy disk (activation disk). Use thismethod if you will typically use RSLinx Enterprise on more than one computer, for

example, if you want to run RSLinx Enterprise on a desktop computer at some times and a

portable computer at others.

Network drive.The activation keys reside on a network drive. Use this method if youhave purchased multiple licenses of the software and want several users to be able toactivate the software over a network. Refer to the online help for instructions on moving

activation to a network drive (refer to the Finding more information about activation

section in this chapter to access online help).

Do not use the Move Activation utility if Rockwell Software products are currently running. Ensure

all software programs are closed before initiating the EvMove utility.

You must use the move utility, EvMove, to move activation files. Attempts to copy, move or e-mail

an activation file by other means will damage the file.

A ABOUTACTIVATIONS


45/66

39

AFrameMakerQuickTips

Running the activation utilities

The utilities for moving and resetting activation are called EvMove and Reset

respectively. Reset is used when an activation file has been damaged. The

EVMOVE.EXE and RESET.EXE files are located on your hard drive (located in

C:\Program Files\Rockwell Software\RSUtil if you accepted the default directory location

during installation). To run these programs, select Start > Programs > Rockwell

Software > Utilities > Move Activation orReset Activation.

Finding more information about activationThe online help (COPYPROT.HLP) provides more extensive information on activation

including subjects such as:

KEYDISK.Set this environment variable to tell your computer to look for activation onfloppy drives

CHECKDRIVES.Specify which drives to search for activationnetwork activation.

Move activation to a network server to allow multiple users access tothe activation

moving activation.See detailed instructions for moving activationresetting activation.See detailed instructions for using the Reset utility to repair adamaged activation file

troubleshooting.Look up error messages, get problem-solving suggestionsYou can access online help: from the Help button on one of the EvMove or Reset dialog boxes.

from RSLinx Enterprise by selecting Help > Copy Protection from the main menu.

without running either RSLinx Enterprise or the activation utilities. From the

Windows Start menu, select Programs > Rockwell Software > Utilities > Activation

Help (if you accepted the default directory location during installation).



46/66

40

Answers to some common questions

Following are some common problems that people encounter with activation and their

solutions.

My activation files were damaged. What should I do?

If you have lost the activation because the activation file is damaged, you need to reset

activation. Follow the Reset Codes instructions on the Rockwell Software Technical

Support web page, or call the technical support telephone number. The web page and

telephone number are both listed on page ii of this guide.

If you cannot obtain a reset code immediately, follow these instructions to use the Master

disk to activate the software as a temporary solution.

To use the Master disk to activate software:

1. Set the KEYDISK environment variable to TRUE. (Please refer to the online help.)

2. Insert your Master disk in the floppy drive.

3. Run your software as usual. Your software will find the activation on the Master disk.

I accidentally deleted the software directory on my hard drive.

Do I need to call Rockwell Software for replacement activation

files?

No. Deleting the program files does not delete your activation. The activation files are not

stored in the program directory; they are located in the root directory. Your activation files

will not be lost unless you format the hard drive, tamper with hidden files in the root

directory, or perform certain other hard drive operations (refer to the Protecting your

activation files section in this appendix for more information).

To get the software running again, simply reinstall the software, but do not move the

activation when given the opportunity.

Why cant I move activation to a new floppy disk on a

Windows NT system?It has to do with a disk modification that NT does not allow. If you have access to a

machine with a different Windows operating system, you can create a disk that will work

under NT. Format a floppy and move any activation file to it under Windows XP, 2000,

Me, or 98. (You can move the activation back off the disk if you want to keep it where it

was.) Then take that disk to your Windows NT machine and move the activation to it.


47/66

41

B

BFrameMakerQuickTips

Advanced topicsThe following topics are presented in this section:

About the virtual backplane

Supported network routes

Moving RSLinx Enterprise configurations

About the virtual backplane

The virtual backplane is a driver service that provides connectivity between RSLinx

Enterprise and various device drivers and other applications within the RSLinx Enterprise

server. It allows the software modules and communications resources contained in the

server to be configured and visualized in a manner similar to the devices in a

ControlLogix system.

For example, both the PCICS and PKTCS device drivers plug into the virtual backplane.Packets received by one of these communications interface cards can be routed across the

virtual backplane to (or through) any other interface card whose driver plugs into the

virtual backplane, or to any application that plugs into the virtual backplane, such as the

SoftLogix5xxx controller.

This is very similar to having a 1756-CNB and a 1756-ENBT module plugged into a

ControlLogix chassis: packets received across the ENBT can be routed across the

backplane and out the CNB module, or to a controller sitting in the backplane.

Note that RSLinx Enterprise occupies a slot in the virtual backplane (as can RSLinx

Classic), which means that it is able to be both a source and a destination for packets sent

over the backplane.

This chassis-like model is carried over to the PanelView Plus (and VersaView CE)

platforms in a minimalistic fashion. For ControlNet support, those platforms implement

two-slot virtual backplanes, where RSLinx Enterprise sits in one slot (slot #0) and the

2711P-RN15S ControlNet Scanner card sits in the other (slot #1).



48/66

42

Supported network routes

The preferred route for PCCC networks is for the RSLinx Enterprise engine to be

connected to the end device (for example, a PanelView Plus device connected directly to a

PLC-5, or an RSLinx Enterprise data server on a Windows computer connected directly to

a DH+/RIO module in a ControlLogix rack, as shown below.)

RSLinx Enterprise allows you to change the network type used when going across a routethat includes multiple CIP (Control and Information Protocol; e.g., Ethernet or

ControlNet) hops. An example of this would be a route from a Windows computer that

connects from Ethernet through a ControlLogix Gateway to ControlNet to a PLC-5, as

shown below.

RSLinx Enterprise does not support offlink routes. Offlink routes are network paths in

which the underlying network protocol changes. This mean if you originally start on a

PCCC route (for example, DH+/DH485, DH-RIO), you cannot switch to a CIP route such

as ControlNet or EtherNet. The reverse is also true: you cannot start on a CIP route (e.g.,

Ethernet to ControlLogix to DH+ to PLC-5) and then switch to a PCCC route.

B ADVANCEDTOPICS


49/66

43

BPlaceholder

Moving RSLinx Enterprise configurations

The following sections provide guidelines for moving your shortcuts from application to

application and for moving your list of selected hardware from computer to computer.

Before moving your files, shut down the RSLinx Enterprise service using the Windows

Service Control Panel.

Moving your shortcuts

You can reuse shortcuts developed in one application for RSLinx Enterprise for another

RSLinx application without having to re-enter the shortcuts using the followingprocedures. Note that these procedures move only the shortcuts and not the drivers

themselves.

MOVINGSHORTCUTSFROMONECOMPUTERTOANOTHER: SAME

APPLICATION

1. Right-click the RSLinx Enterprise server in the application tree and select Properties.

2. Change the computer name in the Computer hosting the RSLinx Enterprise server box

to the new location of the RSLinx Enterprise server.

3. A warning displays to alert you that this procedure changes the RSLinx Enterprise

server reference. You must reapply your shortcuts because the paths may not be set

correctly; only the shortcut name is preserved.Follow the instructions provided on the

dialog.

MOVINGSHORTCUTSONTHESAMECOMPUTER: DIFFERENTAPPLICATION

1. Identify the computer on which your FactoryTalk Directory Server is located.

2. On that FactoryTalk Directory Server computer, locate the shortcuts.xml file in:

C:\Documents and Settings\All Users\Application Data\Rockwell\RNAServer\

Global\RnaStore\your_application_name\any_area_or_sub_areas_you_have\

your_RSLinx_Enterprise_server_name

(This assumes you have not changed your documents and settings location and that

you installed Windows to the C:\ drive.)

Your_application_name is the name of your application, and within the application are

folders and sub folders for areas and sub areas, if used.

Any_area_or_sub_areas_you_have name will match a file directory of the same

names.

Your_RSLinx_Enterprise_server_name name will match the name of your RSLinx

Enterprise data server in the application (the default is RSLinx Enterprise).



50/66

44

3. Move the shortcuts.xml file to the path where your new application is; all your

shortcuts NAMES will be moved there.

For example:

C:\Documents and Settings\All Users\Application Data\Rockwell\RNAServer\

Global\RnaStore\your_NEW_application_name\any_area_or_sub_areas_you_have\

your_RSLinx_Enterprise_server_name

4. For each shortcut, you must reapply the path to the end device.

This method works for moving shortcuts between Local applications (remembering thatLocal applications always use the computer on which it runs as the "Local" FactoryTalk

Directory server) and for moving shortcuts between Local and Networked applications.

The path for local shortcuts is:

C:\Documents and Settings\All Users\Application Data\Rockwell\RNAServer\Local\

RnaStore\your_application_name_here\your_RSLinx_Enterprise_server_name.

MOVINGSHORTCUTSFROMONECOMPUTERTOANOTHER: DIFFERENT

APPLICATION

To move shortcuts between computers and between applications, follow the same path on

the FactoryTalk Directory server as described in the previous section. Keep in mind that

the FactoryTalk Directory server will have a directory for each application and for each

RSLinx Enterprise server.

MOVINGSHORTCUTSFROMONECOMPUTERTOANOTHER: DIFFERENT

FACTORYTALK DIRECTORY

To move shortcuts between computers, even with different FactoryTalk Directories,

follow the same path on the FactoryTalk Directory server as described in the previous

section. Keep in mind that the FactoryTalk Directory server will have a directory for each

application and for each RSLinx Enterprise server, and you will be able to move from

application to application.

Note that your shortcut names are copied, but not the associated paths; so you must

reapply each shortcut.

B ADVANCEDTOPICS


51/66

45

BPlaceholder

Moving your physical layout (drivers and devices)

If you are using the same RSLinx Enterprise software on the same computer for multiple

applications, adding device drivers to one application will make those same drivers

available to the other applications. There is no need to move hardware configurations

from one application to another.

MOVINGFROMONECOMPUTERTOANOTHER

1. Shut down the RSLinx Enterprise service using the Windows Service Control Panel

on both the source and the target computers.

2. Use Windows Explorer to locate the file an RSLinxNG.xml file in the directory

C:\Documents and Settings\All Users\Application Data\Rockwell\RSLinx Enterprise.

(This assumes you have not changed your documents and settings location and that

you installed Windows to the C:\ drive).

3. Copy the .xml file from the source computer to the target computer and restart the

RSLinx Enterprise service on the target computer. This will effectively copy all the

hardware information you need. Note that you may not have the same drivers or same

hardware on the second computer, so this may not always be a wise decision. Your

shortcuts are also on the computer you copied to, but each one will need to be applied

to the new hardware configuration.

The RSLinxNG.xml file is application- and directory-indifferent. This means you can

move the file between computers from directory to directory and need only to reapply

your shortcuts.



52/66

46


53/66

47

C

CFrameMakerQuickTips

Using RSLinx Enterprise with RSLinxClassic

RSLinx Enterprise and RSLinx Classic can run simultaneously on the same computer,

although there are some considerations that you must be aware of to avoid resource

conflicts between these two applications.

If your RSLinx Enterprise configuration consists of one of the following driver types and

you need RSLinx Classic to communicate using that same driver, then you must share the

driver within RSLinx Enterprise with RSLinx Classic:

Serial-DF1

1784-PKTX

To share one of these RSLinx Enterprise drivers with RSLinx Classic, execute the

following steps:

1. If you already have an RS232 DF1 driver configured in RSLinx Classic, select

Communications > Configure Drivers.

2. From the Configure Drivers dialog, select the DF1 driver from the Configured Drivers

list, and clickDelete. The driver no longer appears in the Configured Drivers list.

3. Select View > Options and clear the Accept UDP Messages on Ethernet Port

checkbox.

4. Exit and restart RSLinx Classic.

5. Launch either RSView Studio or the FactoryTalk Administration Console andnavigate to the Communications tab.

6. Select the Ethernet driver, right-click the mouse, and select Properties.

7. Select the Advanced tab, and then click the Listen on Ethernet/IP Encapsulation Port

checkbox. For more information on this checkbox, see the online help.

8. If you do not already have a Serial-DF1 driver in RSLinx Enterprise, then add a

Serial-DF1 driver.

Serial-DF1 is used in this example; however, the procedure is valid for the 1784-PKTX as well.

Keep in mind that clearing this checkbox in RSLinx Classic deactivates the Gateway Server in

RSLinx Classic. You are also disabling RSLinx Classic from receiving unsolicited packets across

Ethernet. Consider these facts when planning your side-by-side operation.



54/66

48

9. Start RSLinx Classic and select Communications > Configure Drivers.

10. Select Remote Devices via Linx Gateway in the Available Drivers list and clickAdd

New.

11. Name the driver, and clickOKto display the Configure Remote Devices via Linx

Gateway dialog.

12. Select your computer name in the Server Name selection list to display a list of drivers

to which you can connect.

13. Select the Serial DF1 driver you named from the Remote driver name list, and clickOK.

You now have connectivity for both RSLinx Enterprise and RSLinx Classic clients. When

using RSLogix, remember to select the remote driver (e.g., TCP-1) instead of the direct

serial DF1 (e.g., AB_DF1-1).

Please keep the following in mind:

The RSLinx Enterprise server only provides access to drivers for the RSLinx Classic

package running on the local computer.

Serial-DF1 (RS232 DF1 devices) and the 1784-PKTX/D drivers are the only drivertypes that can share access as described in this section.

The virtual backplane is a sharable component between RSLinx Classic and RSLinx

Enterprise. Since the PCICS plugs into the virtual backplane on the computer, it is

sharable as well.

If you complete all of these steps and your local workstation does not show up in step 11 (above),

then you need to restart the RSLinx Enterprise server so it can obtain sole ownership of the

resources that were allocated by RSLinx Classic prior to clearing of the Accept UDP Messageson Ethernet Port checkbox. The easiest way to restart RSLinx Enterprise server is to reboot the

host computer, although you can exit RSView Studio and use the Service Control Manager to

restart the RSLinx Enterprise service.


55/66