1757 In510 - en P

ProcessLogix
R510.0 Installation
and Upgrade Guide
1757-SWKIT5100
Installation Instructions
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.ab.com/manuals/gi) 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 we use notes to make you aware of safety
considerations.
WARNING
!
ATTENTION
Identifies information about practices or circumstances

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

that can lead to personal injury or death, property
damage, or economic loss.
Attentions help you:
identify a hazard
avoid a hazard
recognize the consequence
IMPORTANT
Identifies information that is critical for successful

application and understanding of the product.
Table of Contents
Preface
Our Assumptions About Users . . . . . . . . . . . . . . . . .

Starting Conditions and Assumptions . . . . . . . . .
Minimum Hardware Requirements . . . . . . . . . . . . . .
Contents of Release. . . . . . . . . . . . . . . . . . . . . . . . .
ProcessLogix Online Help/Knowledge Builder . .
ProcessLogix R510.0 Installation and
Upgrade Guide . . . . . . . . . . . . . . . . . . . . . . . . .
Removing the Default Startup Screens . . . . . . . . . . .
Rockwell Automation Support . . . . . . . . . . . . . . . . .
New Product Satisfaction Return . . . . . . . . . . . . .
Your Questions or Comments about This Manual
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Terms and Type Representations . . . . . . . . . . . .
Checklists . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Acronyms and Abbreviations . . . . . . . . . . . . . . . . . .
.
.
.
.
.
Preface-1
Preface-1
Preface-2
Preface-2
Preface-3
.
.
.
.
.
.
.
.
.
Preface-3
Preface-4
Preface-4
Preface-4
Preface-4
Preface-5
Preface-5
Preface-5
Preface-6
.
.
.
.
.
.
.
.
Chapter 1
ProcessLogix R510.0 Installation
Introduction
Operating System Support . . . . . . . . . . . . . .

Operating System Options . . . . . . . . . . . . . .
ProcessLogix Server Supported Installations .
ProcessLogix Client Supported Installations .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1-1
1-1
1-2
1-4
Clean System Windows 2000 Server Installation . . . . . . . . .

Installing Windows 2000 Server on a New System . . . . .
Starting the Windows 2000 Server Installation
from the Boot Floppies . . . . . . . . . . . . . . . . . . . . . . . .
Starting the Windows 2000 Server Installation
from the CD-ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Completing the Windows 2000 Server Installation . . . . .
PC Naming Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Clean System Windows 2000 Professional Installation . . . . .
Installing Windows 2000 Professional on a New System
Creating Windows 2000 Professional Boot Floppies. . . .
Starting the Windows 2000 Professional Installation
from the Boot Floppies . . . . . . . . . . . . . . . . . . . . . . . .
Starting the Windows 2000 Professional Installation
from the CD-ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Completing the Windows 2000 Professional Installation.
Clean System Windows XP Professional Installation . . . . . .
Installing Windows XP Professional on a New System . .
Starting the Windows XP Installation from the CD-ROM
Completing the Windows XP Professional Installation . .
Upgrading Windows 2000 Professional to XP Professional .
Creating the ProcessLogix User Accounts . . . . . . . . . . . . . .
Creating the ps_user and erserver accounts. . . . . . . . . .
2-2
2-2
Chapter 2
Operating System Installation
Procedures
2-4
2-5
2-5
2-7
2-11
2-11
2-12
2-13
2-13
2-14
2-18
2-18
2-19
2-20
2-24
2-26
2-26
Publication 1757-IN510A-EN-P - October 2003
Table of Contents
ii
Modifying Windows XP. . . . . . . . . . . . . . . . . . . . . . . .

Windows 2000 Service Pack 4 Installation . . . . . . . . . .
Checking for Windows 2000 Service Pack 4 . . . . . .
Installing Windows 2000 Service Pack 4 . . . . . . . . .
Windows Security Hotfix Installation . . . . . . . . . . . . . .
Installing Windows 2000 Security Hotfix . . . . . . . . .
Installing Windows XP Security Hotfix . . . . . . . . . .
Internet Explorer 6.0 SP1 Installation . . . . . . . . . . . . . .
Checking the Internet Explorer Version. . . . . . . . . .
Installing Internet Explorer 6.0 SP1 . . . . . . . . . . . . .
Updating Windows Installer. . . . . . . . . . . . . . . . . . . . .
Updating ISScript . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Additional Operating System Customization Procedures
Adjusting the Video Settings . . . . . . . . . . . . . . . . .
Setting Up Additional Drivers . . . . . . . . . . . . . . . . .
Other Required System Settings . . . . . . . . . . . . . . .
Creating Emergency Repair Disks . . . . . . . . . . . . . . . .
Windows 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Windows XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2-28
2-29
2-29
2-30
2-31
2-31
2-32
2-33
2-33
2-35
2-36
2-37
2-38
2-38
2-39
2-39
2-40
2-40
2-40
ProcessLogix Software Installation on a Clean PC . . . . . . .

Installing ProcessLogix R510.0 Software . . . . . . . . . . . . . .
Installing ProcessLogix Product. . . . . . . . . . . . . . . . . .
Installing SQL Server . . . . . . . . . . . . . . . . . . . . . . . . .
Installing Knowledge Builder . . . . . . . . . . . . . . . . . . .
Installing RSLinx . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing Engineering Tools . . . . . . . . . . . . . . . . . . . .
Installing Active X Components . . . . . . . . . . . . . . . . .
Installing the ProcessLogix Server . . . . . . . . . . . . . . . .
Installing ProcessLogix Update . . . . . . . . . . . . . . . . . .
Moving the RSLinx Activation File . . . . . . . . . . . . . . . . . .
About the Activation File . . . . . . . . . . . . . . . . . . . . . .
Determining the Current RSLinx Version . . . . . . . . . . .
Installing the Activation File . . . . . . . . . . . . . . . . . . . .
Configuring RSLinx Drivers for ControlNet
Supervisory Network. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Updating the 1784-PCIC Firmware . . . . . . . . . . . . . . .
Configuring RSLinx Drivers for Ethernet
Supervisory Network. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Completing the ProcessLogix R510.0 Install on a
Non-Redundant Server . . . . . . . . . . . . . . . . . . . . . . . . . .
Upgrading Hardware Component Firmware . . . . . . . .
Checking Control Builder Operation and Logging On .
Backing Up a ProcessLogix Server Hard Drive to Tape
Creating an Emergency Repair Disk . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-1
3-2
3-4
3-4
3-6
3-7
3-8
3-8
3-9
3-12
3-14
3-14
3-14
3-15
Chapter 3
ProcessLogix Server Installation
Procedures
. 3-16
. 3-17
. 3-19
.
.
.
.
.
3-20
3-20
3-20
3-21
3-21
Table of Contents
iii
Chapter 4
ProcessLogix Server Upgrade
Procedures
ProcessLogix Server Upgrade Scenarios . . . . . . . . . . . . . . . 4-1

Upgrade R500.1 Server to R510.0 . . . . . . . . . . . . . . . . . 4-1
Upgrade R400.0 SP2 Server to R510.0 . . . . . . . . . . . . . . 4-3
Upgrade R320.0 Server to R510.0 . . . . . . . . . . . . . . . . . 4-5
Preparing for a ProcessLogix R400.0 SP2 or R500.1 to R510.0
Server Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Exporting the R400.0 SP2 or R500.1 Engineering
Repository Database . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Saving Fieldbus Device Definition Files. . . . . . . . . . . . . 4-8
Saving Important R400.0 SP2 or R500.1 Server Data . . . . 4-9
Exporting the R400.0 SP2 or R500.1 ProcessLogix
Server Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
Removing the RSLinx Software Activation File . . . . . . . . 4-12
Saving R400.0 SP2 or R500.1 Data to a Remote PC . . . . . . . 4-13
Networking an R400.0 SP2 or R500.1 Server to a
Remote PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
Transferring Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Disconnect Redundant Servers . . . . . . . . . . . . . . . . . . . 4-15
Removing ProcessLogix R500.1 Software . . . . . . . . . . . . . . 4-15
Removing Selected ProcessLogix R500.1 Components . . 4-15
Remove ProcessLogix Server Components . . . . . . . . . . 4-17
Verifying and Finalizing Component Removal . . . . . . . . 4-18
Removing ProcessLogix R400.0 SP2 Software . . . . . . . . . . . 4-19
Removing Selected ProcessLogix R400.0 SP2
Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
Removing ProcessLogix Server Components . . . . . . . . . 4-21
Preparing for a ProcessLogix R320.0 to R510.0
Server Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
Backing Up a ProcessLogix R320.0 Server to Tape. . . . . 4-23
Exporting the R320.0 Engineering Repository Database . 4-24
Saving Important R320.0 Server Data . . . . . . . . . . . . . . 4-26
Exporting the ProcessLogix Server Database . . . . . . . . . 4-28
Removing the RSLinx Software Activation File . . . . . . . . 4-28
Copying R320.0 Data to the R510.0 Server . . . . . . . . . . . . . 4-29
Networking the R320.0 and R510.0 Servers . . . . . . . . . . 4-29
Transferring R320.0 Data to the R510.0 Server . . . . . . . . 4-30
Transferring the 1784-PCIC Card to the R510.0 System . . . . 4-32
Copying R400.0 SP2 or R500.1 Data to the R510.0 Server . . 4-33
Reconnect Redundant Servers. . . . . . . . . . . . . . . . . . . . 4-33
Transferring R400.0 SP2 or R500.1 Data to the
R510.0 Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
Restoring ProcessLogix Data . . . . . . . . . . . . . . . . . . . . . . . 4-35
Restoring Server Redundancy . . . . . . . . . . . . . . . . . . . . 4-36
Importing the Engineering Database . . . . . . . . . . . . . . . 4-36
Table of Contents
iv
Restoring the ProcessLogix Server Points Database . . .

Upgrading Hardware Component Firmware . . . . . . . .
Reloading Controllers. . . . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
4-39
4-40
4-41
4-41
Chapter 5
ProcessLogix Client Installation
and Upgrade Procedures
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Operating System Support . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Windows 2000 Professional . . . . . . . . . . . . . . . . . . . . . 5-2
Windows XP Professional. . . . . . . . . . . . . . . . . . . . . . . 5-3
Windows 2000 Server. . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Windows 2000 Professional Client Installation Scenarios . . . 5-3
Clean Install: Windows 2000 Professional . . . . . . . . . . . 5-3
Upgrade R500.1 Windows 2000 Professional Client
to R510.0 Windows 2000 Professional Client . . . . . . . . . 5-4
Upgrade R400.0 SP2 Windows 2000 Professional Client
to R510.0 Windows 2000 Professional Client . . . . . . . . . 5-5
Upgrade R400.0 SP2 Windows NT 4.0 Client to R510.0
Windows 2000 Professional Client (Clean Install) . . . . . 5-6
Upgrade R320.0 Windows NT 4.0 Client to R510.0
Windows 2000 Professional Client (Clean Install) . . . . . 5-7
Windows XP Professional Client Installation Scenarios . . . . 5-8
Clean Install: Windows XP Professional . . . . . . . . . . . . 5-8
Upgrade R500.1 Windows XP Professional Client to
R510.0 Windows XP Professional Client . . . . . . . . . . . . 5-8
Upgrade R500.1 Windows 2000 Professional Client to
Upgrade R400.0 SP2 Windows 2000 Professional Client to
Upgrade R400.0 SP2 Windows NT 4.0 Client to R510.0
Windows XP Professional Client (Clean Install) . . . . . . . 5-11
Upgrade R320.0 Windows NT 4.0 Client to R510.0
Windows XP Professional Client (Clean Install) . . . . . . . 5-12
Saving Important Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
Networking an Existing Client to a Remote PC . . . . . . . . . . 5-14
Removing Selected R500.1 Components . . . . . . . . . . . . . . . 5-15
Removing Selected R400.0 SP2 Components. . . . . . . . . . . . 5-16
Installing ProcessLogix R510.0 Client Software . . . . . . . . . . 5-18
Installing Knowledge Builder . . . . . . . . . . . . . . . . . . . . 5-19
Installing Engineering Tools . . . . . . . . . . . . . . . . . . . . . 5-20
Installing the ProcessLogix Client Software . . . . . . . . . . 5-21
Installing ProcessLogix Update . . . . . . . . . . . . . . . . . . . 5-23
Transferring ProcessLogix Data . . . . . . . . . . . . . . . . . . . . . 5-25
Transferring Data to the R510.0 Client. . . . . . . . . . . . . . 5-25
Restoring ProcessLogix Data. . . . . . . . . . . . . . . . . . . . . 5-26
Finalizing ProcessLogix Client Installation . . . . . . . . . . . . . 5-26
Table of Contents
Changing Hosts File Entries . . . . . . . . . . . . . . . . . . .

Station Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating Emergency Repair Disks . . . . . . . . . . . . . . .
Checking Control Builder Operation and Logging On
.
.
.
.
.
.
.
.
5-26
5-29
5-34
5-34
Chapter 6
Additional Redundant Server
Procedures
Adding Redundancy to R510.0 Non-Redundant

Server Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Changing the Computer Name on a ProcessLogix Server 6-2
Completing the ProcessLogix R510.0 Setup on a Redundant
Server Pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Changing Hosts File Entries . . . . . . . . . . . . . . . . . . . . . 6-3
Changing TCP/IP address on a Secondary
Server (SERVERB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Changing the ProcessLogix License. . . . . . . . . . . . . . . . 6-5
Setting up Primary Server (SERVERA). . . . . . . . . . . . . . . . . 6-6
Making Redundant Hardware File Entries . . . . . . . . . . . 6-7
Configuring the Time Service . . . . . . . . . . . . . . . . . . . . 6-9
Restarting ProcessLogix Services . . . . . . . . . . . . . . . . . . 6-9
Setting Up Secondary Server (SERVERB) . . . . . . . . . . . . . . 6-9
Making Redundant Hardware File Entries . . . . . . . . . . . 6-9
Configuring the Time Service . . . . . . . . . . . . . . . . . . . . 6-10
Restarting ProcessLogix Services . . . . . . . . . . . . . . . . . . 6-10
Confirming Data Link is Available. . . . . . . . . . . . . . . . . 6-10
Configuring Stations in Quick Builder (on SERVERA) . . . . . 6-11
Setting Up Station on SERVERA . . . . . . . . . . . . . . . . . . . . . 6-12
Setting Up Station on SERVERB . . . . . . . . . . . . . . . . . . . . . 6-15
Setting up the Redundant ERDB . . . . . . . . . . . . . . . . . . . . 6-18
Restarting Redundant Servers. . . . . . . . . . . . . . . . . . . . . . . 6-19
Synchronizing Server Databases on Redundant Server . . . . 6-20
Confirming Databases are Synchronized . . . . . . . . . . . . 6-20
Synchronizing Other Files . . . . . . . . . . . . . . . . . . . . . . 6-22
Upgrading Hardware Component Firmware . . . . . . . . . . . . 6-22
Checking Control Builder Operation and Logging On . . 6-22
Backing Up a ProcessLogix Server Hard Drive to Tape . 6-23
Creating an Emergency Repair Disk . . . . . . . . . . . . . . . 6-23
Chapter 7
Firmware Maintenance
Procedures
1784-PCIC Driver Installation . . . . . . . . . . . .

Install Hardware Device Drivers . . . . . . .
Verify the 1784-PCIC Driver Version . . . .
1784-PCIC Firmware Installation . . . . . . . . .
Upgrading Hardware Component Firmware .
About Firmware Upgrades . . . . . . . . . . .
Firmware Revision Level Reference . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7-1
7-1
7-2
7-3
7-4
7-4
7-5
Table of Contents
vi
Important Usage Considerations . . . . . . . . . . . . . . . . . . 7-8

Loading 1757-PLX52, TC-MUX021, or 1757-FIM Boot and
Personality Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
Updating Firmware in CNB, ENET, IOM, SRM, PIM
or ControlNet Adapter . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
Redundant Chassis Firmware Upgrade Precautions . . . . 7-13
Setting CNB Module NUT Timing . . . . . . . . . . . . . . . . . 7-15
Updating Firmware in the 1757-ABRIO Module . . . . . . . 7-17
Chapter 8
Supplementary Procedures
Stopping ProcessLogix Applications and Services . . . . . . . . 8-1

Installing Knowledge Builder on a Non-ProcessLogix System 8-2
Installing Knowledge Builder on Windows 2000 . . . . . . 8-2
Installing Knowledge Builder on Windows XP . . . . . . . 8-3
Removing Knowledge Builder . . . . . . . . . . . . . . . . . . . 8-3
Installing Knowledge Builder . . . . . . . . . . . . . . . . . . . . 8-4
Launching ProcessLogix Knowledge Builder. . . . . . . . . . . . 8-6
SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
SQL Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
Cancelling a Software Component Installation . . . . . . . . . . 8-7
Manual System Backup/Restore Procedures . . . . . . . . . . . . 8-8
Backing Up a ProcessLogix R510.0 Server to Tape. . . . . 8-8
Restoring a ProcessLogix Server System from a
Backup Tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
Using Network Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
About Network Tools. . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
Usage guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
Online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
Making First Time Network Tools Settings. . . . . . . . . . . 8-10
Installing and Running NetShield with ProcessLogix . . . . . . 8-14
Background. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14
Removing Existing NetShield Installation. . . . . . . . . . . . 8-14
Installing NetShield and Configuring Directories for Scan
Exclusion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-15
Changing the Computer Name on a ProcessLogix Server . . 8-16
Exporting the Engineering Repository Database . . . . . . 8-17
Removing Selected ProcessLogix R510.0 Components . . 8-18
Removing ProcessLogix R510.0 Server Components. . . . 8-19
Changing the PC Name . . . . . . . . . . . . . . . . . . . . . . . . 8-21
PC Naming Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-21
Reinstalling ProcessLogix R510.0 Components. . . . . . . . 8-22
Restoring the Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22
Changing the Computer Name on a ProcessLogix Client . . . 8-23
Changing the Computer Name on a Windows
2000 Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23
Table of Contents
vii
Changing the Computer Name on a Windows XP Client 8-24

Configuring a ProcessLogix Client. . . . . . . . . . . . . . . . . 8-24
Adding 1757-PLX52 Controller Redundancy to R510.0
Non-Redundant 1757-PLX52 Controller Configurations . . . . 8-25
Deleting a Non-Redundant 1757-PLX52 and Unassigning
its Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-25
Installing and connecting Redundant Chassis Pair (RCP)
Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-27
Updating Firmware Revision Levels . . . . . . . . . . . . . . . 8-27
Creating a Redundant 1757-PLX52 . . . . . . . . . . . . . . . . 8-28
Chapter 9
New Functions and Features
Overview . . . . . . . . . . . . . . . . .
ProcessLogix DeviceNet Wizard.
1757-ABRIO Update . . . . . . . . .
New PLX Function Blocks . . . . .
RSView Connectivity . . . . . . . . .
Additional Module Support . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
9-1
9-1
9-2
9-2
9-3
9-3
Major ProcessLogix Engineering Tools Software

Revisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Major ProcessLogix Server Software Revisions . . . . . .
Embedded Software Components . . . . . . . . . . . . . . .
External, Third Party Qualified Software Components
Miscellaneous SCADA Component Revisions. . . . . . .
.
.
.
.
.
.
.
.
.
.
10-1
10-2
10-3
10-4
10-6
.
.
.
.
.
.
.
.
.
.
.
.
. 11-1
. 11-1
. 11-2
. 11-2
. 11-3
. 11-4
. 11-7
. 11-8
. 11-9
. 11-9
11-10
11-10
Chapter 10
Major ProcessLogix Software
Components
Chapter 11
Performance and Capacity
Specifications
Server/Client Performance and Capacity. . . . . . . .

PC Platform Requirements . . . . . . . . . . . . . . .
Server Requirements . . . . . . . . . . . . . . . . . . .
Platform System Configuration Definitions . . .
Client Platform Requirements . . . . . . . . . . . . .
Application Usage . . . . . . . . . . . . . . . . . . . . .
User Interface Capacity and Performance . . . .
Control Builder Considerations . . . . . . . . . . . .
Server Redundancy . . . . . . . . . . . . . . . . . . . .
Client/Server Communication Capacity . . . . . .
Server Notifications . . . . . . . . . . . . . . . . . . . .
Server Data Access. . . . . . . . . . . . . . . . . . . . .
Controller and Communications Capacity and
Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Control Network Capacity . . . . . . . . . . . . . . .
System Communications Load Philosophy and
Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. . . . . . 11-11
. . . . . . 11-11
. . . . . . 11-12
Table of Contents
viii
System Communications Limits. . . . . . . . . . . . . . . . .

Controller Communications . . . . . . . . . . . . . . . . . . .
Controller Notifications . . . . . . . . . . . . . . . . . . . . . .
Controller Redundancy. . . . . . . . . . . . . . . . . . . . . . .
1757-PLX52 Resources . . . . . . . . . . . . . . . . . . . . . . .
I/O Performance and Capacity Specifications . . . . . . . . .
PROFIBUS DP Capacity and Topology Specifications.
FIM Performance Limits . . . . . . . . . . . . . . . . . . . . . .
FIM Display-related Performance Limits . . . . . . . . . .
I/O Module Publication Periods . . . . . . . . . . . . . . . .
Special Considerations. . . . . . . . . . . . . . . . . . . . . . . . . .
Device Control May Generate Nuisance Alarms . . . . .
Migration Consideration . . . . . . . . . . . . . . . . . . . . . .
ERDB is Master for Configuration Data in R510.0. . . .
Possible Loss of Communication with CPM . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
11-13
11-15
11-17
11-17
11-18
11-20
11-22
11-23
11-24
11-25
11-25
11-25
11-26
11-26
11-26
Preface
Our Assumptions About

Users
Before configuring a ProcessLogix system you must:

Be familiar with navigating and running applications in a
Microsoft Windows 2000 environment.
Have some experience in loading software applications on a
personal computer (PC).
Be familiar with ProcessLogix hardware components.
Be familiar with ControlNet or ENET configuration.
Be trained on ProcessLogix, including Control Builder and
Server components.
If applicable to your system, you must also have appropriate
training on other Rockwell Automation products applicable to
ControlLogix, RSNetworx, and DeviceNet.
IMPORTANT
If you have not received ProcessLogix R510.0

training, we recommend that you find someone who
does have experience to assist you in loading the
ProcessLogix software and making hardware and
firmware changes in associated ProcessLogix
hardware components.
Contact your local sales office for more information
about training schedules and available trained
personnel.
Starting Conditions and Assumptions

You have the following ProcessLogix R510.0 Software Kit, including:
ProcessLogix R510.0 Base Software CD containing software
such as SQL.
ProcessLogix R510.0 Application Software CD containing
ProcessLogix applications software.
ProcessLogix R510.0 Supplemental Software CD containing
Windows Service Packs and additional software
ProcessLogix R510.0 Knowledge Builder CD containing the
latest version of the online documentation.
Microsoft Windows Operating System(s) CD(s).
RSLinx OEM Master (Activation) Disk.
Preface
You must be certain that your PC meets the hardware requirements

for a ProcessLogix Server or ProcessLogix Client.
ProcessLogix Servers require a Windows 2000 Server operating
system. See Minimum Hardware Requirements, below, for
information about ProcessLogix Server hardware.
ProcessLogix Client Stations require a Windows 2000
Professional, XP Professional or 2000 Server operating system.
See Table 11.B: Client Platform Requirements based on System
Configurations on page 11-3 to review the ProcessLogix Client
platform requirements.
Minimum Hardware
Requirements
ProcessLogix R510.0 Server Software must be installed on a PC that is

specifically qualified. Use of any other PC variations will render the
standard warranty and support agreement null and void.
There are two methods of obtaining the qualified ProcessLogix Server:
1 . Purchase the Server from Rockwell Automation.
2. Contact Rockwell Automation Technical Support for further
information on ordering specifically qualified hardware.
Contents of Release
The following software and documentation components are included

in the ProcessLogix R510.0 Software/Documentation Kit
(1757-SWKIT5000).
Table P.1 ProcessLogix R510.0 Release Components
Release Components
Pub/Part Number
ProcessLogix R510.0 Base Software CD

SQL Server 2000
957859-46
ProcessLogix R510.0 Application Software CD

ProcessLogix Engineering Tools
ProcessLogix Server Software
RSLinx 2.41
957824-82
ProcessLogix R510.0 Supplemental Software CD
957824-83
ProcessLogix Knowledge Builder CD
957824-84
ProcessLogix R510.0 Installation and Upgrade Guide
957824-79
Preface
ProcessLogix Online Help/Knowledge Builder

ProcessLogix online help documentation is included with your
ProcessLogix system in browser format through Knowledge Builder.
Many of the documents may also be ordered individually through
Rockwell Automation in print format, visit us at:
www.theautomationbookstore.com
Knowledge Builder provides task-based documentation within the
Server and Client stations and may be accessed while using any of
ProcessLogixs software programs. Knowledge Builders internal links
and search functions allow you to access process relevant information
and references.
References to Knowledge Builder throughout this document are
illustrated as:
Navigate in Knowledge Builder to Ethernet Implementation
Guide Configuration Setting Up Drivers and IP Addresses for
more information.

The ProcessLogix R510.0 Installation and Upgrade Guide is shipped
with a ProcessLogix system and provides:
procedures for upgrading an R320.0, R400.0 SP2, or R500.1
system to R510.0
procedures for updating the firmware to R510.0 levels
procedures for installing the software on a clean PC
procedures for tasks associated with migrating to redundant
Server and/or redundant Controller architecture.
ProcessLogix R510.0 Software Change Notice is incorporated into this
Installation and Upgrade Guide in the following chapters:
Table P.2 Installation and Upgrade Guide SCN Chapter Descriptions
Chapter
Description
10
Major ProcessLogix Software Components
11
Performance and Capacity Specifications
Preface
Removing the Default

Startup Screens
Throughout this document there are times when you need to remove
the default startup screens. Use the following Tip to complete the
task.
TIP
If this is the first startup since the operating system

install, you must remove the default startup screens.
Professional Systems
1. On the Getting Started with Windows 2000 window, uncheck the
Show this screen at startup checkbox.
2. Click Exit.
Server Systems
1. On the Windows 2000 Configure your Server window, select the I
will configure this Server later option and click Next.
2. Uncheck the Show this screen at startup checkbox and close
the window.
Rockwell Automation
Support
Rockwell Automation provides technical information on the web to assist you

in using our products. At http://support.rockwellautomation.com, 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://support.rockwellautomation.com.
New Product Satisfaction Return

Rockwell tests all of our 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:
United States
Contact your distributor. You must provide a Customer Support case

number to your distributor in order to complete the return process.
Outside United
States
Please contact your local Rockwell Automation representative for

return procedure.
Your Questions or Comments about This Manual

If you find a problem or have a comment about this manual, please
notify us of it on the enclosed How Are We Doing Form, at the back
of this manual. This form is also available in Knowledge Builder.
Preface
Conventions
Terms and Type Representations

The following table summarizes the terms and type representation
conventions used in this Guide.
Table P.3 : Terms and Type Representations

Term/Type
Representation
Meaning
Example
click
Click left mouse button once. (Assumes cursor is positioned

on object or selection.)
Click Browse.
double-click
Click left mouse button twice in quick succession. (Assumes

cursor is positioned on object or selection.)
Double-click the Station icon.
right-click
Click right mouse button once. (Assumes cursor is positioned Right-click the AND function block.
on object or selection.)
drag
Press and hold left mouse button while dragging cursor to

new screen location and then release the button. (Assumes
cursor is positioned on object or selection to be moved.)
Drag the PID function block onto the Control

Drawing.
select
Click to highlight a menu item or list choice.
Select Configure Allen-Bradley drivers from the

list box.
check/uncheck
Click to activate/deactivate a checkbox.
Check the Do not show this dialog again

checkbox.
File New
Shows nested menu selections as menu name followed by

menu selection.
Click File New to start new drawing.
expand
Click the + to the left of a given item /folder to show its

contents.
Expand Local Users and Groups.
<F1>
Keys to be pressed are shown in angle brackets.
Press <F1> to view the online Help.
<Ctrl>+<C>
Keys to be pressed together are shown with a plus sign.
Press <Ctrl>+<C> to close the window.
>D:\setup.exe<
Data to be typed at prompt or in an entry field.
Enter this path location >D:\setup.exe<.
Checklists
To use checklists, continue in each section until you are instructed to
return to the checklist that led you to the given task. Be sure to review
the entire procedure before executing the steps.
Preface
Acronyms and
Abbreviations
Table P.4 Acronyms and Abbreviations
AI Analog Input
LAN Local Area Network
AO Analog Output
LED Light Emitting Diode
CB Control Builder
MAC Media Access Control
CD Compact Disc
MB Megabytes
CDA Control Data Access
Mb Megabits
CD-ROM Compact Disc Read Only Memory
NUT Network Update Time
CEE Control Execution Environment
ODBC Open Database Communications
CM Control Module
OEM Original Equipment Manufacturer
1756-CNB or CNB ControlNet Bridge module
PC Personal Computer
CPM Control Processor Module
PCI Personal Computer Interconnect
CPU Central Processing Unit
1784-PCIC or PCIC PCI ControlNet Interface Module
DI Digital Input
1757-PLX52 ProcessLogix Hybrid Controller with

Optional Redundancy
DO Digital Output
1757-PIM or PIM Pulse Input Module
DOS Disk Operating System
PLC Programmable Logic Controller
ER Engineering Repository
PLX ProcessLogix
ERDB Engineering Repository Database
RAM Random Access Memory
FB Function Block
RCP Redundant Chassis Pair
FF FoundationTM Fieldbus
SCADA Supervisory Control and Data Access
FTA Field Termination Assembly
SCM Sequential Control Module
HTML HyperText Markup Language
SP Service Pack
I/O Input/Output
1757-SRM or SRM System Redundancy Module
IOM Input/Output Module
TC-MUX01 Serial Interface Module
IRQ Interrupt Request
TCP/IP Transmission Control Protocol/Internet Protocol
Chapter
ProcessLogix R510.0 Installation Introduction
Operating System Support
The following table shows the supported operating systems for

ProcessLogix.
Table 1.A ProcessLogix Component Configuration Table
ProcessLogix R510.0
Windows 2000
Server
Server
Client
(1)
(1)
Windows XP
Professional
Professional
Windows 2000 Server is not recommended as a Client for ProcessLogix R510.0 due to the
default standard hardware and operating system requirements.
Windows NT 4.0 Server and Workstation are not supported.
Operating System Options
The hardware platform and all devices contained within it designated

for running the ProcessLogix R510.0 Software should be evaluated for
compatibility with the Windows 2000 operating system.
Systems designated to run ProcessLogix R510.0 Server software should
be Server Class and certified to run the Windows 2000 Server
Operating System. Refer to Minimum Hardware Requirements on
page Preface-2.
Systems designated to run ProcessLogix R510.0 Client Software should
be Workstation/Desktop Class and certified to run the Windows 2000
Professional Operating System.
To check to see which certifications your computer and hardware
components have, consult the Microsoft Hardware Compatibility List
at:
http://www.microsoft.com/windows2000/server/howtobuy/upgrading/
compat/default.asp
Review the scenarios below for your current operating system

installation and upgrade options.
1-2
ProcessLogix Server
Supported Installations
IMPORTANT
If you purchased a new ProcessLogix R510.0 Server

from Rockwell Automation, the operating system and
ProcessLogix software have already been installed.
Do n ot r ein stall th e softw ar e. Refer to the
ProcessLogix R510.0 Server Installation Instructions,
publication 1757-IN950 shipped with your hardware.
It is strongly recommended that you name your
Server properly prior to installing ProcessLogix
R510.0 software.
To change the Server name prior to installing
ProcessLogix R510.0, follow the procedures in
Changing the Computer Name on a ProcessLogix
Client on page 8-23.
Once the ProcessLogix R500.0 software is installed,
changing the computer name requires a full uninstall
and reinstall of all the ProcessLogix R510.0 software.
Refer to Changing the Computer Name on a
ProcessLogix Server on page 8-16.
IMPORTANT
A 1784-PCIC or Ethernet card must already be

installed in the ProcessLogix Server(s).
1-3
ProcessLogix R510.0 Servers require the Windows 2000 Server

operating system. The following table lists the ProcessLogix Server
Install Options. This table also applies if you have a redundant Server
pair. During the installations, the procedures refer you to the
appropriate redundant Server sections.
Table 1.B ProcessLogix R510.0 Server Install Options
Type of Install:
Refer to:
Clean Install
The Clean Install is a clean machine installed with
ProcessLogix R510.0 Server software. That is, the
installation begins with formatting the hard disk and
installing Windows 2000 Server.
ProcessLogix Software Installation

on a Clean PC on page 3-1.
Upgrade from R500.1, Option 1

1. Backup your data.
2. Complete a clean install.
Option 1: Upgrading R500.1 Server

to R510.0 - Clean Install on page
4-1.
Upgrade from R500.1, Option 2

Option 2: Upgrading R500.1 Server
to R510.0 on page 4-2.
2. Uninstall your current ProcessLogix software.
3. Install ProcessLogix R510.0.
Upgrade from R400.0 SP2, Option 1
2. Complete a clean install.
Option 1: Upgrading R400.0 SP2

Server to R510.0 - Clean Install on
page 4-3.
Upgrade from R400.0 SP2, Option 2

Option 2: Upgrading R400.0 SP2
Server to R510.0 on page 4-4.
2. Uninstall your current ProcessLogix software.
3. Install ProcessLogix R510.0.
Upgrade from R320.0
ProcessLogix R510.0 requires that you replace your
R320.0 current installation with new hardware and
operating software for the Server.
Upgrade R320.0 Server to R510.0

on page 4-5.
1-4
ProcessLogix Client
Supported Installations
The ProcessLogix R510.0 Client requires Windows 2000 Professional

or XP Professional operating systems. The following table lists the
ProcessLogix Client Install options. First, select the operating system
you plan to use and then select an install type.
Table 1.C Selecting a ProcessLogix R510.0 Client Install Options

Step 1: Select an
R510.0 Operating
System
Windows 2000 Professional
Windows XP Professional
Windows 2000 Server
Step 2: Select a type

of install:
Refer to:
Refer to:
Refer to:
Clean Install
ProcessLogix Client Installation and

Upgrade Procedures on page 5-1.
Clean Install: Windows XP

Professional on page 5-8.
Windows 2000 Server on

page 5-3.
Windows 2000 Server is not
a recommended operating
system for Clients.
Upgrade from R500.1

Windows XP
Professional Client
N/A
Upgrade R500.1 Windows XP

Professional Client to R510.0
Windows XP Professional Client on
page 5-8.
N/A
Upgrade from R500.1

Windows 2000
Professional Client
Upgrade R500.1 Windows 2000

Windows 2000 Professional Client
on page 5-4.
Upgrade R500.1 Windows 2000

page 5-9.
N/A
Upgrade from R400.0

SP2 Windows 2000
Professional Client
Upgrade R400.0 SP2 Windows 2000

on page 5-5.
Upgrade R400.0 SP2 Windows 2000

page 5-9.
N/A
Upgrade from R400.0

SP2 Windows NT 4.0
Client
Upgrade R400.0 SP2 Windows NT

4.0 Client to R510.0 Windows 2000
Professional Client (Clean Install) on
page 5-6.
Upgrade R400.0 SP2 Windows NT

4.0 Client to R510.0 Windows XP
page 5-11.
N/A
Upgrade from R320.0

Windows NT 4.0 Client
Upgrade R320.0 Windows NT 4.0

Client to R510.0 Windows 2000
page 5-7.
Upgrade R320.0 Windows NT 4.0

Client to R510.0 Windows XP
page 5-12.
N/A
Chapter
Operating System Installation Procedures

IMPORTANT
These installation scenarios use a clean PC

installation method in which all data on the system is
erased. This is an irrecoverable action. All data must
be first backed up or transferred to another system
before proceeding.
ProcessLogix R510.0 Servers require the Windows
2000 Server operating system.
ProcessLogix R510.0 Client Stations may use
Windows 2000 Professional, Windows XP
Professional or Windows 2000 Server.(1)
Windows NT 4.0 Server and Workstation are not
supported.
(1)
Windows 2000 Server is not recommended as a Client for ProcessLogix R510.0 due to the standard hardware
and operating system requirements.
Table 2.A Installing Windows on a Clean PC
For...
See Page...
Clean System Windows 2000 Server Installation
2-2
Clean System Windows 2000 Professional Installation
2-11
Clean System Windows XP Professional Installation
2-18
2-2
Clean System Windows

2000 Server Installation
These instructions cover installation of Windows 2000 Server from

either CD-ROM or floppy disks.
IMPORTANT

publication 1757-IN950, shipped with your
hardware.
Several additional installation methods are available. Consult the

Microsoft Documentation set included with the Operating System for
the following installation methods:
Unattended Installation
Remote Installation Services
Over the Network Installation
SysPrep
Systems Management Server
Installing Windows 2000 Server on a New System

You must install Windows 2000 Server on your Server before you can
install or run the ProcessLogix R510.0 software. The current required
Operating System components are:
Windows 2000 Server with Windows 2000 Service Pack 4
Internet Explorer 6.0 SP1
The Windows 2000 Server software, Service Packs, and Internet
Explorer are licensed products of Microsoft Corporation. Copies of the
Service Packs and Internet Explorer are included on the ProcessLogix
CDs for your convenience.
2-3
This procedure assumes you have:

All network cards installed in the PC and set to the correct IRQs.
All supporting ProcessLogix System hardware installed and
connected to the PC.
A PC that meets specified hardware and software requirements
for R510.0.
Refer to Minimum Hardware Requirements in the Preface for
more information.
All manufacturers related driver diskettes available to complete
the installation.
TIP
Consult the PC Manufacturer for any specialized

instructions/procedures related to the installation of
the Microsoft Windows 2000 Server operating system.
This procedure lists only the generic installation
procedure. It does not contain any special
instructions for any manufacturer specific driver
installation requirements.
Creating Windows 2000 Server Boot Floppies

If your system does not support booting from a CD-ROM, follow these
instructions to create the required Boot Floppies. Otherwise, skip
to Starting the Windows 2000 Server Installation from the CD-ROM on
page 2-5.
IMPORTANT
If your installation requires additional Drivers to be

installed for access to the Hard Disk Controller, Disk
Device, or CD-ROM, it may be necessary to start the
installation via the Boot Floppies (even if your
system supports booting off of a CD-ROM).
You need:
4 blank 3.5 1.44 Mb (High Density) Floppy Disks
1.44 MB Floppy Drive
CD-ROM Drive
DOS or Windows based Operating System with access to
CD-ROM and floppy devices.
2-4
1 . Insert the Windows 2000 Server CD into the CD-ROM drive.

2. Click Star t Run .
3. Enter >cmd< and click OK to open the DOS window.
4. At the DOS prompt, enter the CD-ROM drive letter (e.g., >D:<)
and press <Enter>.
5. Enter >cd bootdisk< and press <Enter>.
6. Enter >makeboot< and press <Enter>.
7. Enter floppy disk drive letter (e.g., >A<).
8. Follow the on-screen prompts for inserting, labeling, and
creating the four floppy disks.
IMPORTANT
Server Boot floppies and Professional Boot floppies

are different.
9. Label your floppy disks.

1 0. When all the boot floppies have been made, shut down the PC.
Starting the Windows 2000 Server Installation from the Boot

Floppies
1 . With the PCs power off, insert the diskette titled Windows 2000
Setup Boot Disk into the floppy disk drive.
2. Turn on the PC.
3. Insert the Microsoft Windows 2000 Server CD into the CD-ROM
drive.
4. Follow the on-screen prompts to remove and insert the
Windows 2000 Server Setup Disks 2, 3, and 4 when instructed to
do so.
5. Press <Enter> at the Welcome to Setup window.
IMPORTANT
If your installation requires additional

Manufacturers Drivers, press <F6> during the boot
process and follow the on-screen instructions for
adding the necessary drivers.
2-5
6. Continue with Completing the Windows 2000 Server Installation

on page 2-5.
Starting the Windows 2000 Server Installation from the CD-ROM

1 . Turn on the PC.
2. Insert the Microsoft Windows 2000 Server CD into the CD-ROM
drive.
3. When prompted, enter into the computers BIOS setup program.
4. Verify that the Boot Priority has the CD-ROM device listed first.
(Before the floppy or hard disk devices.)
5. Exit the BIOS and save the setting.
6. If prompted, press any key to boot from the CD-ROM.
IMPORTANT

7. Press <Enter> at the Welcome to Setup window.
Completing the Windows 2000 Server Installation

1 . If requested, insert the Windows 2000 Server CD into the
CD-ROM drive and press <Enter>.
2. Press <F8> to agree to the Windows 2000 Licensing Agreement.
2-6
3. If necessary, press <ESC> to continue installing a fresh copy of

Windows 2000.
IMPORTANT
If existing partitions are found, you must delete all

of them first before proceeding.
To delete a partition:
1 . Select the partition.
2. Press <D>.
3. Press <Enter>.
4. Press <L>.
5. Repeat for all partitions.
TIP
Certain PCs limit the size of the partition that you

can create. Windows 2000 supports a boot partition
size up to 32 Gigabytes on a NTFS formatted drive.
Use the entire hard disk if possible. If your system
has a limitation, create the largest partition you can,
and leave the leftover space as unpartitioned. (You
can create and format the unpartitioned space
later.) The minimum partition size required for this
installation is 4 Gigabytes.
6. Press <Enter> to set up Windows 2000 on the Unpartitioned

space.
7. Press <Enter> to format the partition using the NTFS file system.
Setup formats the partition. This takes a few minutes to
complete.
The computer automatically restarts. Be sure there is not a
disk in the floppy disk drive.
8. At the Welcome to Setup window, click Nex t.
IMPORTANT
If there is a delay clicking Nex t, setup continues the

installation automatically.
9. Verify the information on the Regional Settings window and

click Nex t.
1 0. Enter the appropriate Name and Organization and click Nex t.
1 1 . Enter your Windows 2000 Server Product Key and click Nex t.
1 2. Select your Servers Licensing Mode and click Nex t.
2-7
Rockwell Automation recommends selecting the Per Seat

licensing option.
IMPORTANT
Microsoft requires that you attain the appropriate

number of Client Access Licenses required for your
system. For ProcessLogix Systems, the total number
of clients includes other ProcessLogix Servers
(Redundant Servers), and ProcessLogix Clients.
When you purchase a ProcessLogix Client License,
a Client Access License for Windows 2000 Server is
included.
1 3. At the Computer Name and Administrator Password window:

a. Enter the Computer Name.
IMPORTANT

R510.0 software.
IMPORTANT
PC Naming Rules
The base name cannot contain more than 13
alphanumeric characters and must contain no spaces.
The full computer name cannot contain more than
14 alphanumeric characters. The following naming
conventions are required for given ProcessLogix
system architectures.
For non-redundant Server, be sure the name does
not end in the letter A or B. The default name is
PLX1.
For redundant Servers, append a letter to the base
name to identify the PCs function in the system
architecture beginning with the letters A and B for
the primary and secondary Servers, respectively. For
example, use the name PLX1A for the primary Server
(SERVERA) and PLX1B for the secondary Server
(SERVERB). (14 Character total: Up to 13 Base plus
A or B)
For a ProcessLogix Client, be sure the name does not
end in the letter A or B. The suggested name is
STNxx, where xx is the Station Number (01-20).
2-8
b. Enter the Administrator password.

c. Confirm the password.
IMPORTANT
Be sure to document the Administrator Password. (It

is required later in the procedure.) The Administrator
Account and password gives a user full access to the
system. Care should be taken to who has access to
this information.
d. Click Nex t.
TIP
In the next section, you have the ability to add

many services and options during the Server
installation. These components are not required for
the base operation of the ProcessLogix R510.0
Software. If any of these components are needed
for a custom installation, they can be added later
after the installation.
1 4. At the Windows 2000 Components window:

a. Uncheck the box for the Internet Information Services (IIS).
Only the Accessories and Utilities, Indexing Service, and
Script Debugger remain checked.
b. Click Nex t .
1 5. At the Date and Time Settings window:
a. If necessary, adjust the Date and Time settings.
b. Set the appropriate Time Zone for your location.
c. Uncheck the Automatically adjust clock for daylight saving
changes option.
d. Click Nex t.
ATTENTION
Failure to uncheck the Automatic adjustment for

Daylight Savings Time causes Redundant Systems to
loose Sync when the time is automatically
adjusted. Choosing not to automatically adjust the
time allows you to decide when to make the
adjustment (at a time that is not critical to your
process).
If setup has not found a suitable Network Device, you are

prompted for installing one. Follow the instructions for adding a
manufacturer supplied driver or add the Microsoft Loop Back
adapter.
1 6. Select the Custom Settin gs option and click Nex t.
2-9
1 7. At the Networking Components window, select In ter n et

Pr otocol (TCP/IP) and click Pr oper ties.
1 8. In the Networking Components Window,
a. Select the Use th e follow in g IP addr ess option.
b. Enter the appropriate IP address information.
The following Private Networking IP Address scheme can be
utilized for the system to operate:
Table 2.B Private Networking IP Address scheme
Server Type
Suggested Private Networking IP Address
Non-Redundant Server or Primary NIC 1: 192.168.0.1

NIC 2: 192.168.1.1
Redundant Server
NIC 3: 192.168.2.1
Backup Redundant Server
NIC 1: 192.168.0.2
NIC 2: 192.168.1.2
NIC 3: 192.168.2.2
c. Enter the Subnet Mask >255.255.255.0<.

d. Enter a default gateway if necessary.
2-10
e. Click OK to return to the Networking Components window.

IMPORTANT
IP Addresses are critical to the communication of

the system. Rockwell Automation suggests, when
possible, to utilize a Private Network for the control
system, not connected to any other networks. This
isolates the control system from interference from
any business communication.
In some organizations it is important for these
addresses to be controlled by the IT organization.
Consult your companys practices and IT
organization for the appropriate IP address
information. It is necessary to use valid IP
information to integrate the ProcessLogix Control
system with the Business Network.
1 9. Click Nex t.
20. Repeat steps 17-19 for additional network cards.
21 . At the Workgroup or Computer Domain window:
a. Select the No, th is computer... option.
b. Enter an appropriate WorkGroup Name.
c. Click Nex t.
TIP
All systems which are configured for this Process

Control System should utilize the same Workgroup
Name for easier operations.
At this point in the installation, setup finishes installing Windows

2000. The amount of time this takes depends on your hardware
configuration.
22. At the Completing the Setup Wizard window, remove the
Windows 2000 Server CD and click Fin ish .
The PC restarts.
Clean System Windows 2000 Server Installation is complete.
Return to the checklist that led you to this task.
Clean System Windows

2000 Professional
Installation
2-11
Windows 2000 Professional is the preferred Client operating system

for ProcessLogix R510.0. The current required operating system
components are:
Windows 2000 Professional with Windows 2000 Service Pack 4
The Windows 2000 Professional software, Service Packs, and Internet
CDs for your convenience.
Installing Windows 2000 Professional on a New System

A PC that meets specified hardware and software requirements.
the installation.
TIP

the Microsoft Windows 2000 Professional operating
system.
2-12
Creating Windows 2000 Professional Boot Floppies

If your system does not support booting from a CD-ROM, follow these
instructions to create the required Boot Floppies. Otherwise, skip
to Starting the Windows 2000 Professional Installation from the
CD-ROM on page 2-13.
IMPORTANT
If your installation requires additional Drivers to be

installed for access to the Hard Disk Controller, Disk
Device, or CD-ROM, it may be necessary to start the
installation via the Boot Floppies (even if you system
supports booting off of a CD-ROM).
You need:
4 blank 3.5 1.44 Mb (High Density) Floppy Disks
1.44 MB Floppy Drive
CD-ROM Drive
DOS or Windows based Operating System with access to
CD-ROM and floppy devices.
1 . Insert the Windows 2000 Professional CD into the CD-ROM
drive.
4. At the DOS prompt, enter the CD-ROM drive letter (e.g., >D:<)
and press <Enter>.
5. Enter >cd bootdisk< and press <Enter>.
6. Enter >makeboot< and press <Enter>.
7. Enter the letter of your floppy disk drive (e.g., >A<).
8. Follow the on-screen prompts for inserting, labeling, and
creating the four floppy disks.
IMPORTANT
Server Boot floppies and Professional Boot floppies

are different.
9. Label your floppy disks.
2-13
1 0. When all the boot floppies have been made, shut down the PC.
Starting the Windows 2000 Professional Installation from the

Boot Floppies
1 . With the PCs power off, insert the diskette titled Windows 2000
Setup Boot Disk into the floppy disk drive.
2. Turn on the PC.
3. Insert the Microsoft Windows 2000 Professional CD into the
CD-ROM drive.
4. Follow the on-screen prompts to remove and insert the
Windows 2000 Professional Setup Disks 2, 3, and 4 when
instructed to do so.
5. Continue with Completing the Windows 2000 Professional
Installation on page 2-14.
Starting the Windows 2000 Professional Installation from the

CD-ROM
1 . Turn on the PC.
2. Insert the Microsoft Windows 2000 Professional CD into the
CD-ROM drive.
5. Exit the BIOS and save the setting.
6. Press any key to boot from the CD-ROM.
IMPORTANT

2-14
Completing the Windows 2000 Professional Installation

1 . At the Welcome to Setup window, press <Enter>.
2. If requested, insert the Windows 2000 Professional CD into the
CD-ROM drive and press <Enter>.
IMPORTANT
If Windows 2000 Setup did not find a suitable

installation device, it stops and prompts you for
additional Manufacturers Drivers. Follow the
on-screen instructions for adding the necessary
drivers.
3. Press <F8> to agree to the Windows 2000 Licensing Agreement.

Windows 2000.
IMPORTANT
TIP
If existing partitions are found, delete all of them

first before proceeding. Use the on-screen
instructions to complete this task.
can create. Windows 2000 supports a boot partition
and leave the leftover space as unpartitioned (you
can format the unpartitioned space later). The
minimum partition size required for this installation
is 4 Gigabytes.
5. Press <Enter> to set up Windows 2000 on the Unpartitioned

space.
6. Format the partition using the NTFS file system.
complete.
The computer automatically restarts. Be sure there is not a disk
in the floppy disk drive.
7. At the Welcome to Setup window, click Nex t.
If there is a delay clicking Nex t, setup continues the installation
automatically.
2-15
8. Verify the information on the Regional Settings window and

click Nex t.
9. Enter the appropriate Name and Organization name and click
Nex t.
1 0. Enter your Windows 2000 Professional Product Key and click
Nex t.
1 1 . At the Computer Name and Administrator Password window:
IMPORTANT
The computer name cannot contain more than 14


IMPORTANT
Be sure to document the Administrator password, it

is required later in the procedure. The Administrator
account and password gives a user full access to the
this information.
d. Click Nex t.
changes option.
d. Click Nex t.
ATTENTION

lose Sync when the time is automatically adjusted.
Choosing not to automatically adjust the time
allows you to decide when to make the adjustment
(at a time that is not critical to your process).
1 3. If setup has not found a suitable Network Device, you are

prompted to install one. Follow the instructions for adding a
manufacturer supplied driver or add the Microsoft Loop Back
adapter.
2-16
1 4. Select the Custom settin gs option and click Nex t.

1 6. In the Networking Components Window:
Table 2.C Private Networking IP Address scheme
PC Type
Client
NIC 1: 192.168.0.x
NIC 2: 192.168.1.x
where x is the Station number +2 (for Station number 2, x=4)
c. Enter the Subnet Mask of >255.255.255.0<.

d. Enter a default gateway, if necessary.
2-17

IMPORTANT

system, not connected to any other networks. This
isolates the control system from interference from
any business communication.
system with the business network.
1 7. Click Nex t.
1 8. Repeat steps 15-16 for additional network cards.
1 9. At the Workgroup or Computer Domain window:
a. Select the No, th is computer option.
b. Enter an appropriate Workgroup name.
c. Click Nex t.
TIP

Control System should utilize the same Workgroup
name for easier operations.
At this point in the installation, Setup finishes installing Windows

2000. This takes some time depending on your hardware
configuration.
20. At the Completing the Setup Wizard window, remove the
Windows 2000 Professional CD and click Fin ish .
The PC restarts.
21 . If a Network Identification wizard opens, click Can cel.
Clean System Windows 2000 Professional Installation is complete.
2-18
Clean System Windows XP

Professional Installation
Windows XP Professional is available as a Client operating system for

ProcessLogix R510.0. The Windows XP Professional software and
Internet Explorer are licensed products of Microsoft Corporation. A
copy of Internet Explorer is included on the ProcessLogix Knowledge
Builder CD for your convenience.
Installing Windows XP Professional on a New System

A PC that meets specified hardware and software requirements.
the installation.
IMPORTANT
For ProcessLogix Client software to operate correctly,

Windows XP MUST be installed to C:\winnt.
If you received your PC from the manufacturer with
Windows XP Professional pre-installed, you must
confirm that the install was to C:\winnt. If Windows
XP was installed to C:\winnt, skip to Internet
Explorer 6.0 SP1 Installation on page 2-33. If
Windows XP was not installed to C:\winnt, you must
complete a clean Windows XP install. Continue
with Starting the Windows XP Installation from the
CD-ROM on page 2-19.
TIP

the Microsoft Windows XP Professional operating
system.
2-19
Starting the Windows XP Installation from the CD-ROM

TIP
If you are performing a clean XP installation, steps

14 must be completed on a different PC.
1 . Insert the ProcessLogix R510.0 Supplemental Software CD into

the CD-ROM drive.
2. Insert a blank disk into the PCs floppy drive.
3. Using Windows Explorer, copy the WinXP Install\winnt.sif file
from the ProcessLogix R510.0 Supplemental CD to the blank
floppy.
4. Remove the floppy disk.
5. Insert the floppy disk into the PC where XP is to be installed.
6. Turn on the PC.
7. Insert the Microsoft Windows XP Professional CD into the
CD-ROM drive.
1 0. Exit the BIOS and save the setting.
1 1 . Press any key to boot from the CD-ROM.
IMPORTANT

2-20
Completing the Windows XP Professional Installation

1 . Press <Enter> at the Welcome to Setup Window.
IMPORTANT
If Windows XP Setup did not find a suitable

installation device, it stops and prompts you for
additional Manufacturers Drivers. Follow the
on-screen instructions for adding the necessary
drivers.
2. Press <F8> to agree to the Windows XP Licensing Agreement.

Windows XP.
IMPORTANT
If existing partitions are found, you must delete all

of them first before proceeding.
To delete a partition:
1 . Select the partition.
2. Press <D>.
3. Press <Enter>.
4. Press <L>.
5. Repeat for all partitions.
TIP

can create. Windows XP supports a boot partition
and leave the leftover space as unpartitioned. (You
can create and format the unpartitioned space
later.) The minimum partition size required for this
installation is 4 Gigabytes.
6. Press <Enter> to set up Windows XP on the Unpartitioned

space.
7. Press <Enter> to format the partition using the NTFS file system.
complete.
The computer automatically restarts. Be sure there is not a disk
in the floppy disk drive.
2-21
8. If necessary, select the I accept th is agr eemen t option and

click Nex t.
9. Verify the information on the Regional and Language Options
window and click Nex t.
1 0. Enter the appropriate Name and Organization and click Nex t.
1 1 . Enter your Windows XP Professional Product Key and click
Nex t.
1 2. At the Computer Name and Administrator Password window:
IMPORTANT


IMPORTANT
Be sure to document the Administrator Password. (It

is required later in the procedure.) The Administrator
Account and password gives a user full access to the
this information.
d. Click Nex t.
changes checkbox.
d. Click Nex t.
ATTENTION

loose Sync when the time is automatically
adjusted. Choosing not to automatically adjust the
time allows you to decide when to make the
adjustment (at a time that is not critical to your
process).
2-22
TIP
If setup has not found a suitable Network Device,

you are prompted for installing one. Follow the
instructions for adding a manufacturer supplied
driver or add the Microsoft Loop Back adapter.
1 4. Select the Custom settin gs option and click Nex t.

1 6. In the Internet Protocol (TCP/IP) Properties window:
Table 2.D Private Networking IP Address scheme
PC Type
Client
NIC 1: 192.168.0.x
NIC 2: 192.168.1.x
where x is the Station number +2 (for Station number 2, x=4)
c. Enter the Subnet Mask >255.255.255.0<.

d. Enter a default gateway if necessary.
IMPORTANT
2-23

system. (Not connected to any other networks.)
This isolates the control system from interference
from any business communication.
system with the Business Network.
1 7. Click Nex t.
1 8. Repeat steps 15-17 for additional network cards.
1 9. At the Workgroup or Computer Domain window:
a. Select the No, th is computer option.
b. Enter an appropriate workgroup Name.
c. Click Nex t.
TIP

Control System should use the same Workgroup
Name for easier operations.
Setup finishes installing Windows XP. This takes some time

depending on your hardware configuration. The PC
automatically restarts.
20. If a Display Settings prompt appears, click OK, then click OK at
the Monitor Settings prompt.
21 . At the Welcome to Microsoft Windows window, click Nex t.
22. At the How will this computer connect to the internet window,
click Skip.
IMPORTANT
Microsoft Windows XP Professional must be

registered with the Microsoft Corporation, but
registration is not required at this time. We
recommend that you skip this step by answering
No to the activation and registration wizard.
organization to determine proper license
acquisition.
2-24
23. To skip the Windows Registration, select the No, n ot at th is

time option and click Nex t.
24. At the Who will use this computer? window, enter >xptemp<
into the Your name field and click Nex t.
25. At the Thank You! window, remove the Windows XP
Professional CD and click Fin ish to start Windows XP.
26. Click Star t, right-click the My Computer icon and select
Man age.
27. Expand Local Users and Groups.
28. Click the User s folder.
29. Right-click >xptemp< and select Delete.
30. Click Yes to confirm.
31 . Close the Computer Management window.
Windows XP Professional installation is complete.
Upgrading Windows 2000

Professional to XP
Professional
1 . Insert the Windows XP Professional CD into the CD-ROM drive.

The Auto-Run capability should start the application
automatically. If it does not, do the following:
a. Click Star t Run .
b. Enter this path or Br ow se to:
>D:(or your CD-ROM drive letter)\setup.exe<
c. Click OK.
2. At the Welcome to Microsoft Windows XP window, click In stall
Win dow s XP.
3. At the Welcome to Windows Setup window, select Upgr ade
(Recommen ded) from the drop-down list and click Nex t.
4. Select the I accept th is agr eemen t option and click Nex t.
5. Enter your Windows XP Professional Product Key and click
Nex t.
2-25
6. Select the No, skip th is step an d con tin ue in stallin g

Win dow s option and click Nex t.
After automatically restarting, the installation cycles through the
following:
Preparing Installation
Installing Windows
Finalizing Installation
This may take 30-60 minutes to complete. When completed, the

system automatically restarts.
7. At the Welcome to Microsoft Windows window, click Nex t.
IMPORTANT
Microsoft Windows XP Professional must be

registered with the Microsoft Corporation, but
registration is not required at this time. We
recommend that you skip this step by answering
No to the activation and registration wizards.
organization to determine proper license
acquisition.
8. To skip the Windows Registration Wizard, select the No, n ot at

th is time option and click Nex t.
9. Click Fin ish to start Windows XP.
Upgrading Windows 2000 Professional to XP Professional is complete.
2-26
Creating the ProcessLogix

User Accounts
You must create a Process User account to be used to complete the

ProcessLogix R510.0 Software installation. Follow the steps below to
create the ps_user and erserver accounts.
If you have a redundant Server pair, you must complete this
procedure on both SERVERA and SERVERB.
IMPORTANT
All R510.0 Systems are required to use the ps_user

account. This is a change from R320.0, where most
systems used the plx_user account.
Unless otherwise noted, all subsequent software
installs should be performed with the ps_user
account logged on to the system.
TIP
If this is the first time starting up since the Windows

2000 operating system install, it is necessary to
remove the default startup screens. Refer
to Removing the Default Startup Screens on
page P-4.
Table 2.E User Account Details

Username
Full name
Description(2)
Password
Confirm Password
Member of
ps_user
Process User
ProcessLogix
System
Administrator
password(3)
password(3)
Administrators
Users
erserver(1)
erserver
Engineering
Repository Server
erserver(4)
erserver(4)
Administrators
Users
(1)
The erserver account is only necessary on ProcessLogix Servers.
(2)
This field may be left blank.
(3)
For security reasons, it is recommended that you create a more complex ps_user password after the ProcessLogix installation is complete.
(4)
The confirm password must be lowercase.
Creating the ps_user and erserver accounts

1 . If using Windows XP, click Star t.
1 . Right-click the My Computer icon and select Man age.
2. Expand Local Users and Groups.
3. Click the Users folder.
4. Click Action New User.
5. Enter the appropriate information for ps_user from table
Table 2.E on page 2-26.
2-27
6. Uncheck the User must ch an ge passw or d at n ex t logon

checkbox.
7. Check ONLY the Passw or d n ever ex pir es checkbox.
8. Click Cr eate.
9. On ProcessLogix Servers, repeat steps 5 through 8 for the
erserver account.
1 0. Click Close.
1 1 . Double-click the ps_user account.
1 2. On the Member of tab, click Add.
1 3. In Windows 2000, under Name, click on Administrators and
click Add. In Windows XP, type Administrators in the object
name field.
1 4. Click OK.
1 5. Click Apply.
1 6. Close the user properties window.
1 7. On ProcessLogix Servers, repeat steps 11 through 16 for the
erserver account.
1 8. Close the Computer Management window.
Creating the ProcessLogix User Accounts is complete.
2-28
Modifying Windows XP
If upgrading from an R500.1 Windows XP Client, skip to step 12.

1 . Logon to Windows XP Professional as ps_user or Process User.
2. Click Star t Con tr ol Pan el.
3. Click User Accoun ts.
4. Click Ch an ge th e w ay user s Log on or off.
5. Uncheck the Use th e Welcome scr een checkbox and click
Apply Option s.
6. Close all windows, restart the PC and logon as ps_user.
7. Right-click in the taskbar and select Pr oper ties.
8. On the Start Menu tab, select Classic Star t Men u and click OK.
9. Click Star t Settin gs Con tr ol Pan el.
1 0. Click Sw itch to Classic View .
1 1 . Close the Control Panel window.
1 2. Open Windows Explorer.
1 3. Right-click the CD-ROM drive and select Pr oper ties.
1 4. On the AutoPlay tab, in the drop-down list, select Pictur es.
1 5. Select Select an action to per for m and select Take n o action .
1 6. In the drop-down list, select Mix ed con ten t.
1 7. Select Select an action to per for m and select Take n o action .
1 8. Click OK and close Windows Explorer.
1 9. Click Star t Sh ut Dow n .
20. In the drop-down list, select Log off ps_user and click OK.
Modifying Windows XP is complete.
Windows 2000 Service

Pack 4 Installation
2-29
Checking for Windows 2000 Service Pack 4

Complete the following steps to determine whether the source CDs
included SP4. If you have a redundant Server pair, you must complete
this procedure on both SERVERA and SERVERB.
1 . Logon to the system.
TIP

page P-4.

3. Enter >winver< and press <Enter>.
4. In the About Windows window, look to see if the following line
appears: Version 5.0 (Build 2195: Service Pack 4).
If the line appears as shown, click OK and return to the
checklist that led you to this task.
If the line does not say Service Pack 4, click OK and continue
with Installing Windows 2000 Service Pack 4 on page 2-30.
2-30
Installing Windows 2000 Service Pack 4

1 . If necessary, logon to the system.
TIP

page P-4.
2. Insert the ProcessLogix R510.0 Supplemental Software CD into

the CD-ROM drive.
4. Enter this path or Br ow se to:
>D:(or your CD-ROM drive letter)\Win2k_SP4\W2KSP4_EN.EXE<
5. Click OK to launch the Service Pack 4 setup application.
6. At the Welcome window, click Nex t.
7. Select the I Agr ee option and click Nex t.
8. Select the Ar ch ive Files option and click Nex t.
9. At the Completing the Windows 2000 Service Pack 4 window,
click Fin ish .
The system automatically restarts.
1 0. Logon to the system.
1 1 . Click Star t Settin gs Con tr ol Pan el.
1 2. Double-click Automatic Updates.
1 3. Uncheck the Keep my computer up to date checkbox and
click OK.
1 4. Close the Control Panel window.
The Windows 2000 Service Pack 4 installation is complete.
Windows Security Hotfix

Installation
2-31
All systems are required to install the Windows Security Hotfix.
Installing Windows 2000 Security Hotfix

If your system has Windows XP, skip to Installing Windows XP
Security Hotfix on page 2-32.
TIP

page P-4.
2. If necessary, insert the ProcessLogix R510.0 Supplemental

Software CD into the CD-ROM drive.
>D:(or your CD-ROM drive letter)\Win2k_Security_Hotfix_824146\
Windows2000-KB824146-x86-ENU.exe<
5. Click OK to launch the setup application.
8. At the Completing the Windows 2000 KB824146 Setup Wizard
window, click Fin ish .
The Windows 2000 Security Hotfix installation is complete.
2-32
Installing Windows XP Security Hotfix

the CD-ROM drive.
>D:(or your CD-ROM drive letter)\WinXP_Security_Hotfix_824146\
WindowsXP-KB824146-x86-ENU.exe<
5. Click OK to launch the setup application.
8. At the Completing the Windows XP KB824146 Setup Wizard
window, click Fin ish .
The system should automatically restart. If it does not, restart the
PC manually.
The Windows XP Security Hotfix installation is complete.

Installation
2-33
Checking the Internet Explorer Version

All systems are required to use Internet Explorer 6.0 SP1. Complete
the following steps to determine the version of Internet Explorer that
is installed. If you have a redundant Server pair, you must complete
this procedure on both SERVERA and SERVERB.
TIP

page P-4.
2. Start Internet Explorer.

IMPORTANT
If this is the first time running Internet Explorer on

Windows 2000, the Internet Connection Wizard
opens.
An internet connection is not required for this
function or ProcessLogix software use. However,
components in the software are required.
Fill in the appropriate information if known,
otherwise follow the steps listed here:
a. Select the I want to setup my Internet connection
manually option and click Next.
b. Select the I connect through a local area network
(LAN) option and click Next.
c. Click Next at the local area network internet
configuration window.
d. Select the No option for setting up an Internet Mail
Account and click Next.
e. Click Finish.
f. If you do not have an Internet connection, you receive an
error attempting to download the page. Click Work
Offline.
2-34
IMPORTANT
If this is the first time running Internet Explorer on

Windows XP, you are prompted with the New
Connection Wizard.
An internet connection is not required for this
function or ProcessLogix software use. However,
components in the software are required.
Fill in the appropriate information if known,
otherwise follow the steps listed here:
a. Click Cancel on the Location Information Window.
b. Click Yes to confirm.
c. Click Cancel at the New Connection Wizard window.
d. Start Internet Explorer.
3. Click Help About In ter n et Ex plor er.

4. Check to see the Version information:
If the version is 6.0 and the service pack is SP1, click OK, close
Internet Explorer and return to the checklist that led you to this
task.
If the version is less than 6.0 or the service pack is not SP1, click
OK, close Internet Explorer and continue with Installing Internet
Explorer 6.0 SP1 on page 2-35.
2-35
Installing Internet Explorer 6.0 SP1

All systems are required to use Internet Explorer 6.0 SP1. Complete
the following steps to install Internet Explorer 6.0 SP1. If you have a
redundant Server pair, you must complete this procedure on both
SERVERA and SERVERB.
TIP

page P-4.
2. Insert the ProcessLogix R510.0 Knowledge Builder CD into the

CD-ROM drive.
>D:(or your CD-ROM drive letter)\IE6_SP1\IE6Setup.exe<
5. Click OK to launch the Internet Explorer setup application.
6. Select the I accept th e agr eemen t option and click Nex t.
7. At the Windows Update: Internet Explorer window, click Nex t.
8. Click Fin ish .
TIP
On subsequent logons to the computer, a task runs

to apply the update. You will see this one time for all
users of the computer.
Internet Explorer 6.0 SP1 Installation is complete.

2-36
Updating Windows
Installer
All Windows 2000 systems are required to install the Windows

Installer update. Complete the following steps to install the Windows
Installer update. If you have a redundant Server pair, you must
complete this procedure on both SERVERA and SERVERB.
IMPORTANT
If using Windows XP Professional, do not complete

this update as Windows XP Professional has the most
recent update for the Windows Installer.

TIP

page P-4.
2. Insert the ProcessLogix R510.0 Base CD in the CD-ROM drive.

>D:(or your CD-ROM drive letter)\Process Product\instmsiw.exe<
5. Click OK.
6. If a Specified service already exists error appears, Windows
Installer is already up to date, click OK and return to the
checklist that led you to this task. Otherwise, click OK at the
Windows Installer Setup completed successfully dialog box.
7. Click No (Do not restart the system at this time.).
8. Wait for installation operations to complete.
9. Close all applications.
1 0. Restart the PC.
Updating Windows Installer is complete.
Updating ISScript
2-37
All systems are required to install the ISScript update. Complete the
following steps to install the ISScript update. If you have a redundant
Server pair, you must complete this procedure on both SERVERA and
SERVERB.
2. If necessary, insert the ProcessLogix R510.0 Base CD in the
CD-ROM drive.
TIP
In the next step, if browsing, select All Files in the

Files of type drop-down list.

>D:(or your CD-ROM drive letter)\Process Product\ISScript8.msi<
5. Click OK.
6. At the ISScript InstallShield Wizard window, click Nex t.
7. Select the I accept th e ter ms option and click Nex t.
8. At the Ready to Install window, click In stall.
9. At the InstallShield Wizard Completed window, click Fin ish .
Updating ISScript is complete.
2-38
Additional Operating
System Customization
Procedures
All procedures in this section assume that you are logged onto the
system with Administrator access. If you have a redundant Server pair,
you must complete this procedure on both SERVERA and SERVERB.
Adjusting the Video Settings

The system applications and displays have been optimized to be
displayed at a resolution of 1024 by 768 or 1280 by 1024, with 65K
color (High Color, 16 bit). Utilizing any other setting produces
anomalies in some displays. Complete the following steps to set the
Video Settings:
1 . Right-click the desktop and select Pr oper ties.
2. On the Settings tab, click Advan ced in the lower-right side of
the window.
3. If you are using Windows 2000, confirm that on the General
Tab, the Display Font size is set to Small Fonts. If you are using
Windows XP, confirm the DPI setting is Normal size (96 DPI).
4. Click the Adapter tab.
5. Click List All Modes.
6. Select one of the settings entitled 1024 by 768, or 1280 by 1024,
High Color (16 bit).
You should select a refresh rate (listed in Hertz) at the maximum
the monitor can handle. For Example, 1024 by 768, High Color
(16 bit), 75 Hertz. Click OK after your selection.
7. Click Apply.
At this point the setting is applied.
8. Click OK.
9. Click Yes to keep your setting.
If nothing appears or you are unable to see the screen, the
previous mode is reset after 15 seconds. Repeat steps 59 to
reset the mode to a lower Hertz setting.
1 0. Click OK to close the Advanced adapter properties Window.
1 1 . Click OK to close the Display Properties window.
2-39
Setting Up Additional Drivers

The Microsoft Windows 2000 or XP Operating System CDs used to
complete an installation contain a finite set of drivers for the most
common hardware items at the time of release. Rockwell Automation
considers this set to be the base set of drivers. Manufacturers update
their drivers to fix anomalies or provide additional features.
Third Party Platforms

Rockwell Automation recommends that you check your PC Supplier
for driver/software updates pertaining to running the Windows 2000
or XP Operating System on the platform. It may be necessary to
upgrade or install additional drivers to utilize the hardware in your
system.
IMPORTANT
Hardware drivers affect the stability of the system

and should be evaluated for their impact before
implementing.
Other Required System Settings

The following table summarizes the various system settings required
for optimum ProcessLogix R510.0 software operation.
IMPORTANT
If you change any system settings, it may be

necessary to restart the PC for the system to apply
them.
Table 2.F Required System Settings for ProcessLogix R510.0 Software

Function
Required Setting Value
Dynamic Host Configuration

Protocol (DHCP) IP Addressing
ProcessLogix System requires that all specified IP address are fixed and known. We recommend that
you do not use DHCP, but if your organization requires it, use only reserved addressing.
View Options
Windows Explorer
1. Open Windows Explorer

2. Click Tools Folder Options.
3. On the View tab, select the Choose the Show hidden files and folders option.
4. Uncheck the Hide extensions for known file types checkbox.
5. Repeat for each user.
Virtual Memory
The default Virtual Memory settings are typically appropriate for ProcessLogix installation. After the
ProcessLogix installation is complete, navigate in Knowledge Builder to Server and Client Installation
Guide Preparing to Install Configuring Virtual Memory for more information.
2-40
Creating Emergency Repair

Disks
After all installations are completed and all drivers are installed, you
need to create your Emergency Repair Disks.
Windows 2000
Complete the following Steps to create emergency repair disks for
your Windows 2000 installation. If you have a redundant Server pair,
you must complete this procedure on both SERVERA and SERVERB.
1 . Insert a blank diskette into the PC's floppy drive.
2. Click Star t Pr ogr ams Accessor ies System Tools
Backup.
3. Click Emer gen cy Repair Disk.
An Emergency Repair Diskette window opens.
4. Check the Also back up th e r egistr y to th e r epair dir ector y
checkbox and click OK.
5. When finished, click OK.
6. Repeat Steps 15 with another blank formatted diskette.
7. Click Job Ex it.
8. Store the two diskettes in different places to protect against
damage to the diskettes.
Windows XP
Complete the following steps to create recovery disks for your
Windows XP installation.
Backup.
3. If the Backup or Restore Wizard opens, click Advan ced Mode.
4. Click Automated System Recover y Wizar d.
5. Click Nex t.
2-41
6. Enter a backup media or file name and click Nex t.

7. Click Fin ish .
8. Repeat Steps 17 with another blank formatted diskette.
9. Click Job Ex it.
1 0. Store the two diskettes in different places to protect against
Creating Emergency Repair Disks is complete.
2-42
Chapter
ProcessLogix Server Installation Procedures
ProcessLogix Software
Installation on a Clean PC
Rockwell Automation delivers the ProcessLogix Server with all the

required software pre-installed. The following instructions can be
used if the system has to be reinstalled or for new installations on a
PC that was not purchased from Rockwell Automation.
IMPORTANT

publication 1757-IN951 shipped with your hardware.
The following table lists the items that you MUST complete to install
the ProcessLogix software. If you are installing ProcessLogix software
on a redundant Server pair you must complete the items on SERVERA
then repeat the same items on SERVERB.
Table 3.A ProcessLogix Software Installation on a Clean PC
Step
Item
Page
1.
2-2
2.
Creating the ProcessLogix User Accounts
2-26
3.
Windows 2000 Service Pack 4 Installation
2-29
4.
Windows Security Hotfix Installation
2-31
5.
Internet Explorer 6.0 SP1 Installation
2-33
6.
Updating Windows Installer
2-36
7.
Updating ISScript
2-37
8.
2-38
9.
Creating Emergency Repair Disks
2-40
1 0.
1784-PCIC Driver Installation
7-1
11.
Installing ProcessLogix R510.0 Software
3-2
1 2.
Moving the RSLinx Activation File
3-14
3-2
Table 3.A ProcessLogix Software Installation on a Clean PC
Step
1 3.
1 4.
IMPORTANT
Item
Page
Configuring RSLinx Drivers for ControlNet Supervisory

Network
or
Configuring RSLinx Drivers for Ethernet Supervisory
Network
3-16
Completing the ProcessLogix R510.0 Setup on a

Redundant Server Pair
or
Non-Redundant Server
6-2
3-19
3-20
PC Namin g Requir emen ts

Before installing ProcessLogix R510.0, you must
verify that your computer name follows the PC
naming requirements. Refer to PC Naming Rules on
page 2-7.
R510.0 software.
To change the Server name prior to installing
ProcessLogix R510.0, follow the procedures in
Changing the Computer Name on a ProcessLogix
Client on page 8-23.
Installing ProcessLogix
R510.0 Software
Complete the following steps to install these ProcessLogix software

components in succession.
SQL Server
Knowledge Builder
RSLinx OEM 2.31 (Build 10)
Engineering Tools
Client/Server (Display Builder, Station, Server, etc.)
3-3
Special Considerations
Table 3.B Special Considerations when Installing ProcessLogix R510.0 Software
Special Consideration
Description
Redundant Servers Directory

Structures
If you have a redundant Server pair, you must install software on SERVERA first. Then complete the
software installation process again on SERVERB.
You must install the ProcessLogix Server on the same partition on both the Primary and Secondary
Servers and ensure that their directory structures match.
For example, if you install the ProcessLogix Server to C:\honeywell\server on the Primary Server then it
should be installed to the same location on the Secondary Server.
Synchronization problems have been encountered by customers installing the ProcessLogix Server to
C:\honeywell\server on the Primary Server and to D:\honeywell\server on the Secondary Server.
R500.1 References
If at any time, during installation of R510.0, you see a reference to R500.1, this is expected because
R510.0 is a point release of R500.1.
Using Microsoft Excel Data

Exchange
If you plan to use Microsoft Excel Data Exchange, Microsoft Excel must be installed before installing
ProcessLogix.
Prior to the ProcessLogix installation, it is mandatory that the Excel macro security level is set to
Medium. To change the security level for macro virus protection in Excel:
1. On the Tools menu, click Macro, then click Security.
2. On the Security Level tab, select Medium and click OK.
3. Close Excel.
McAfee NetShield
If your system has McAfee NetShield software you must disable virus scanning before installing
ProcessLogix components. After the ProcessLogix installation is complete, refer to Installing and
Running NetShield with ProcessLogix on page 8-13. Pay attention to instructions regarding the
configuring of virus-scan exclusion directories. You can re-enable NetShield after the ProcessLogix
installation is complete.
If the message Dr. Watson has been installed as default application debugger, appears during
software installation, click OK.
1 . Restart the PC.

ATTENTION
It is r equir ed that you restart the PC before the

ProcessLogix installation can begin. Do n ot
con tin ue w ith th e Pr ocessLogix in stallation
un til you h ave r estar ted your system.
2. Logon as ps_user.
IMPORTANT
The system must be logged on as ps_user to

complete the procedures listed below.
Refer to Creating the ProcessLogix User Accounts on
page 2-26 if you need to create the ps_user account.
3. Close any running applications.
3-4
Installing ProcessLogix Product

1 . Insert the ProcessLogix R510.0 Base Software CD into the
CD-ROM drive.
>D:(or your CD-ROM drive letter)\SETUP.EXE<
4. Click OK to launch the software setup application.
5. Select the Pr ocessLogix Ser ver option and click Nex t.
IMPORTANT
You must have either a PCIC or Ethernet card

installed in your ProcessLogix Server to install
R510.0.
6. At the Before installing window, click Yes.

7. At the Product Selection Completed window, click Con tin ue.
Installing SQL Server

IMPORTANT
If SQL Server version 7.0 is present on the machine,

the following appears:
If for any reason you do not want your SQL version
updated, click Abort.
Click OK to continue. Clicking Abort terminates the
entire ProcessLogix installation.
If at any time during the SQL install you see a
Windows File Protection window, click Can cel then
click Yes to keep the file versions.
1 . The SQL Setup Installation Application automatically starts.

Status messages indicate progress, but no user interaction is
required. This takes 47 minutes to complete.
3-5
2. When the following dialog opens, click OK to restart the PC.
A System Shutdown warning opens and closes. After the restart,

installation automatically continues.
Normally, no actions are necessary on your part. Do not press
any keys, buttons, etc. during shutdown and restart. However, if
the system displays the logon window for more than about ten
(10) seconds, logon as ps_user.
TIP
Upon restarting the system, you may receive:

a message that a service failed to start. If you
receive this message, click OK.
an notcli.exe Unable to Locate DLL prompt.
This is normal at this stage and can be ignored.
Click OK to close the prompt.
ProcessLogix installation resumes automatically. It is
possible for ProcessLogix installation to be delayed
for several minutes before resuming.
3. SQL Service Pack 2 installation automatically starts.

required. This takes 2 to 6 minutes to complete.
TIP
If a Q323875 window opens, click Yes to all to

overwrite old files.
When the SQL install is complete, the ProcessLogix R510.0 Base

Software CD ejects.
3-6
Installing Knowledge Builder

ATTENTION
Do not click No in the next step.

Clicking No aborts the entire ProcessLogix
installation.
1 . Insert the ProcessLogix R510.0 Knowledge Builder CD into the

CD-ROM drive and click Yes.
Installing Adobe Acrobat

Adobe Acrobat Reader 4.05 is required to view *.pdf files contained in
Knowledge Builder. Follow these steps to install Acrobat Reader 4.05.
If Adobe Acrobat is already installed, the install will automatically
continue with Installing Knowledge Builder Components, below.
2. At the Acrobat Reader 4.05 Setup window, click Nex t.
3. At the Choose Destination Location window, click Nex t.
4. Click OK.
Installing Knowledge Builder Components

5. At the Knowledge Builder Welcome window, click Nex t.
6. Click Yes to accept the license agreement.
7. Select the KB Full option and click Nex t.
For additional information on KB install types, refer to Installing
Knowledge Builder Components on page 8-5.
8. Click Select All and click Nex t.
9. At the Server selection window, click Nex t to accept the default
directory for Knowledge Builder.
3-7
1 0. At the Start Copy window, click Nex t.

1 1 . At the Installation completed window, click Fin ish .
The KB_update executes. No user interaction is required.
When the Knowledge Builder install is complete, the
ProcessLogix R510.0 Knowledge Builder CD ejects.
Installing RSLinx
ATTENTION

installation.
1 . Insert the ProcessLogix R510.0 Application Software CD into the

2. At the RSLinx Welcome window, click Nex t.
3. Select the I accept th e ter ms option and click Nex t.
4. Enter the User Name and Organization to whom the RSLinx
package is registered, and click Nex t.
5. At the Standard Setup window, click Nex t.
7. At the If you have a previous Backup message window, click
OK.
8. At the InstallShield Wizard Completed window, click Fin ish .
9. After reviewing, close the Release Notes window.
1 0. At the ProcessLogix Installation window, click OK to restart the
PC.
A System Shutdown warning opens and closes. After restart,
installation automatically continues.
Normally, no actions are necessary on your part. Do not press
any keys, buttons, etc. during shutdown and restart. However, if
the system displays the logon window for more than about ten
(10) seconds, logon as ps_user.
3-8
Installing Engineering Tools

1 . At the Ready to Install window, click In stall.
TIP
Command windows open during Engineering Tools

installation. These windows close automatically.
2. At the Installation Complete window, click Fin ish .
Installing Active X Components

1 . Click OK to acknowledge the change directory warning.
2. At the PsAxCtl Document EXE Setup Welcome window, click

OK.
3. Verify that the Directory is:
C:\Honeywell\TPS50\System\bin.
4. Click the PC icon install button.
5. At the Setup complete window, click OK.
3-9
Installing the ProcessLogix Server

1 . At the Welcome to ProcessLogix Server Setup window, click
Nex t.
2. At the Choose Setup Type window, click Pr ocessLogix Ser ver
setup (desktop PC icon).
3. At the Enter License window, enter the System number and
Authorization number which appear on your software license
certificate in their respective fields and click Nex t.
TIP
You must install Microsoft Excel prior to installing

Microsoft Excel Data Exchange.
4. At the Choose ProcessLogix Server Options window, select

Microsoft Excel Data Exchange and/or Network API and click
Nex t.
TIP
In steps 512 below, you MUST NOT change the

directory names from their defaults. If you do change
directory names, the ProcessLogix system may not
operate properly.
If you see a Directory Already Exists window, click
Yes.
5. Click Nex t to accept the default directory for the Server

Software.
6. Click Nex t to accept the default directory for the Client
Software.
7. Click Nex t to accept the default directory for the Display Search
Path.
8. Click Nex t to accept the default directory for the ProcessLogix
Software.
9. If the Specify Microsoft Excel Directory window opens, click
Nex t. Otherwise, skip to step 11.
IMPORTANT
Rockwell Automation recommends answering No to

the question:
Do you want Microsoft Excel Data Exchange to be
allowed to write to a ProcessLogix Server database?
Answering Yes enables the write option and it is
possible for anyone with access to the machine to
write to the Server database.
3-10
1 0. To disable the Microsoft Excel Data Exchange write option, click

No in response to the question:
Do you want Microsoft Excel Data Exchange to be allowed to
write to a ProcessLogix Server database?
1 1 . Click Nex t to accept the default directories for the History
Archive.
1 2. Click Nex t to accept the default directory for the Event Archive.
1 3. At the Enter Account Passwords window, complete all entries:
(passwords are case sensitive)
a. Enter >mngr123< as the manager account password and press
<Tab>.
b. Enter >mngr123< again to confirm password and press
<Tab>.
c. Enter >engr123< as the engineering account password and
press <Tab>.
d. Enter >engr123< again to confirm password and press <Tab>.
e. Enter >oper123< as the operator account password and press
<Tab>.
f. Enter >oper123< again to confirm password.
1 4. Click Nex t to complete the password entry.
1 5. At the Choose Report Paper Format, select the desired paper
format and click Nex t. Letter paper is the standard format.
1 6. If the Choose ProcessLogix Server Folder window opens, click
Nex t. Otherwise, continue with the next step.
1 7. If the Choose ProcessLogix Server Diagnostic Tools Folder
window opens, click Nex t. Otherwise, continue with the next
step.
1 8. At the Choose Point Mode Acronyms window, select the
Default acr on yms option and click Nex t.
1 9. At the Choose Fast History Rate window, select a Fast History
collection rate and click Nex t. 5 seconds is the default rate.
TIP
To change the Fast History Collection Rate after

installation is complete, click Star t Pr ogr ams
Pr ocessLogix Ser ver Setup.
20. Review the software installation details summarized in the

Confirmation window.
3-11
If you need to make changes, click Back to access any

previous entries.
If the details are okay, click Nex t to begin the Server setup.
This may take 10 to 15 minutes to complete.
If a Sentinel Pro Driver Setup Error window appears, click
OK.
21 . If necessary, click OK at the Failed to uninstall Quick Builder
setup error.
22. If the system includes Excel Data Exchange, click En able
Macr os when prompted. Otherwise, continue to the next step.
TIP
TIP
If a Read Only File Detected window opens, select

Don t display th is w in dow again and click Yes to
overwrite old files.
If a Microsoft Excel window opens, check the Do
n ot sh ow th is dialog again checkbox and click
OK.
ATTENTION
The CD must remain in the CD-ROM drive. You must

select No in Step 23.
23. At the Setup Complete window, select the No, I w ill r estar t my
computer later option and click Fin ish .
Wait until the command windows have closed and file copying
is complete. This may take a few minutes to complete.
24. At the ProcessLogix Setup Complete window, select the No, I
w ill r estar t my computer later option and click Fin ish .
3-12
Installing ProcessLogix Update

1 . Restart the PC.
3. Click Star t Pr ogr ams Pr ocessLogix Ser ver Star t-Stop
Pr ocessLogix Ser ver to call up the ProcessLogix Server dialog
box.
TIP
To display the Full Mode version of the ProcessLogix

Server dialog box, click the icon on the left of the
title bar and click Advan ced Full Mode.
A checkmark appears in front of the Full Mode
selection to show that it is active.
4. With the Full Mode version of the dialog box active, select the
Database Un loaded option.
5. Click Yes to confirm the action and wait for the Server to change
its state.
6. Close the ProcessLogix Server dialog box.
the CD-ROM drive.
>D:(or your CD-ROM drive letter)\SP1\Server-Client\setup.exe<
1 0. Click OK to launch the software setup application.
1 1 . At the Welcome window, click Nex t.
1 2. At the Destination Folder window, click Nex t.
1 3. At the Ready to Install window, click In stall.
required. This takes 10-15 minutes to complete.
1 4. At the InstallShield Wizard Completed window, click Fin ish .
1 5. Click Yes to restart the system.
3-13
1 6. Logon as ps_user.
1 7. Click Star t Run .
1 8. Enter this path or Br ow se to:
>D:(or your CD-ROM drive letter)\Update\setup.exe<
20. Click Nex t to install the ProcessLogix Update.
21 . At the ProcessLogix Update Complete window, click Fin ish .
22. If prompted to reboot, click No.
ATTENTION
Non -r edun dan t Ser ver

If you are installing ProcessLogix software on a
non-redundant Server:
1 . Restart the Server.
ATTENTION
Redun dan t Ser ver Pair

If you are installing ProcessLogix software on a
redundant Server pair:
1 . Do n ot restart SERVERA.
2. Return to the beginning of ProcessLogix Software
Installation on a Clean PC on page 3-1 and repeat
for SERVERB.
3. Once you have completed these procedures for
both SERVERA and SERVERB, restart SERVERB.
4. Logon to SERVERB as ps_user.
5. When SERVERB is running, restart SERVERA and
logon as ps_user.
3-14
Moving the RSLinx

Activation File
About the Activation File

IMPORTANT
Be sure to move the activation file on both

SERVERA and SERVERB.
Complete the following steps to move the activation file (evrsi.sys)

from the RSLinx software Master Disk to the hard drive where RSLinx
is to be operated. The PC cannot execute the full OEM version of the
RSLinx application if the activation file is not present on its hard drive.
ATTENTION
If you need to reformat the hard drive, you must first

move the activation file back to the RSLinx Master
Disk using the same general procedure as follows.
Otherwise, the file will be corrupted and you will n ot
be able to run RSLinx in the OEM mode.
Before you attempt to move the activation file, you
MUST exit all ProcessLogix applications and stop all
ProcessLogix services. Refer to Stopping ProcessLogix
Applications and Services on page 8-1.
Do n ot manually copy or move the evrsi.sys file.
Moving/copying the evrsi.sys file will disable the OEM
version of RSLinx.
Always use the EVMOVE.EXE program (refer to page
4-28) to move the evrsi.sys file. If the evrsi.sys file is
corrupted or manually moved, resulting in RSLinx
changing to Lite version, you can visit the Rockwell
web site (http://suppport.automation.rockwell.com/resetcodes/)
to recover the RSLinx activation.
Determining the Current RSLinx Version

1 . Click Star t Pr ogr ams Rockw ell Softw ar e RSLin x
RSLin x to start the RSLinx application.
2. If necessary, click the RSLinx Icon (
the RSLinx window.
) in the Taskbar to open
3-15
3. Verify the application title in the title bar.
If the title is RSLin x Lite, close RSLinx and continue with

Installing the Activation File, below.
If the title is RSLin x OEM you already have the OEM version
installed and you do not have to install the activation file.
Close RSLinx, and return to the checklist that led you to this
task.
Installing the Activation File

1 . Locate the RSLinx Master Disk and insert it into the floppy drive.
>A:(or your floppy drive letter)\EVMOVE.EXE<
4. Click OK to launch the move executive.
5. Verify that you are Moving Activations From Drive A:(or your
floppy drive letter) To Drive C:(or your hard drive letter).
6. Click OK to initiate the move.
7. Click Move to move the file to the hard drive.
8. Wait for a dialog box to indicate a successful move, and click
OK.
3-16
9. Remove the Master Disk and store it in a safe place.

1 1 . If you are installing ProcessLogix software on a redundant
Server pair, return to the beginning of Moving the RSLinx
Activation File on page 3-14 and repeat for SERVERB. Otherwise,
return to the checklist that led you to this task.
TIP
Configuring RSLinx Drivers

for ControlNet Supervisory
Network
If you need to move the activation file back to the

Master Disk, refer to Removing the RSLinx Software
Activation File on page 4-28.
Complete the following steps to configure the ControlNet PCIC drivers

for RSLinx.
IMPORTANT
If you are using Ethernet for your Supervisory

Network, skip to Configuring RSLinx Drivers for
Ethernet Supervisory Network on page 3-19.
1 . Click Star t Pr ogr ams Rockw ell Softw ar e RSLin x

RSLin x to call up the Rockwell Software RSLinx window.
2. Click Commun ication s Con figur e Dr iver s to call up the
Configure Drivers dialog box.
3. Select 1 784-PCIC(S) for Con tr olNet devices in the Available
Drivers drop-down list and click Add New to call up the Add
New RSLinx Driver dialog box.
3-17
4. Click OK to accept the default name AB_PCIC-1 for the driver.

IMPORTANT
The driver name MUST be AB_PCIC-1.
5. In the Configure 1784-PCIC window, enter the following:

a. Serial Number(hex): This value is read from the PCIC card
and does not change.
b. Network Address(dec): Change the default of 99 to:
Non-redundant Server
24
Redundant Server A
24
Redundant Server B
23
6. Click OK start the PCIC driver.
7. In the Configure Drivers dialog box, you should see AB_PCIC-1
listed in the Configured Drivers list with the status Running. If
the AB_PCIC-1 driver status is not Running, call Rockwell
Automation Technical Support. Refer to Rockwell Automation
Support in the Preface.
8. Click Close to close the Configure Drivers dialog box.
9. Close RSLinx.
IMPORTANT
Whenever the 1784-PCIC driver has been updated or

the Network Address is changed, the 1784-PCIC
driver must be stopped and restarted to complete the
change. You must power down the PC.
Updating the 1784-PCIC Firmware

Starting Network Tools Application
If this is the fir st time you have used Network Tools on this PC, refer
to Making First Time Network Tools Settings on page 8-10 and then
continue with the following steps.
1 . Click Star t Run .
2. Enter >ntools -c -u<.
3. Click OK to launch the Network Tools application.
3-18
4. Click OK to acknowledge the warning about monitoring

through Control Builder.
5. Click the resume button
to initiate network scan.

1 . Click the desired PCIC icon under the Desktop tree and wait for
the card details to appear in the Detail pane.
2. Verify the firmware revision shown in the Name field.
If the firmware is 3.7.39, return to the checklist that led you
to this task.
If the firmware is not 3.7.39, go to Step 3.
3. Click the firmware button
to initiate the firmware update.
4. Click Yes to acknowledge the Warning prompt.

5. Navigate to the directory:
C:\Honeywell\TPS50\System\Firmware\1784-PCIC\3_7_39
6. Select the 9941 7807.n vs file.
7. Click Open to start the firmware load and click Yes to confirm.
8. Wait for the load to complete. The Status field in the lower
portion of the Network Tools window tracks the load progress.
9. Click OK to acknowledge the load completes with no errors.
1 0. Close NTools.
1 1 . Restart the PC.
1 2. If you are installing ProcessLogix software on a redundant
Server pair, return to the beginning of Configuring RSLinx
Drivers for ControlNet Supervisory Network on page 3-16 and
repeat for SERVERB. Once all Servers have been updated,
Configuring RSLinx Drivers

for Ethernet Supervisory
Network
IMPORTANT
3-19
If you are using ControlNet for your Supervisory

Network, skip this section.
Refer to Configuring RSLinx Drivers for ControlNet
Supervisory Network on page 3-16.
1 . Verify the settings of the Ethernet Network Interface card to be

used to communicate with the controller.
Navigate in Knowledge Builder to:
Ethernet Implementation Guide Configuration Setting Up
Drivers and IP Addresses for more information.
2. Configure the IP Address for each controller.
Ethernet Implementation Guide Configuration Setting Up
Drivers and IP Addresses Configuring and setting IP address
for Ethernet module section for more information.
3. Configure RSLinx drivers.
A driver must be configured for each controller.
Ethernet Implementation Guide Configuration Setting up
Drivers and IP Addresses Configuring additional RSLinx
drivers for more information.
4. If you are installing ProcessLogix software on a redundant
Server pair, return to the beginning of Configuring RSLinx
Drivers for Ethernet Supervisory Network on page 3-19 and
repeat for SERVERB. Once all Servers have been updated,
3-20
Upgrading Hardware Component Firmware

Completing the
ProcessLogix R510.0 Install
to Loading 1757-PLX52, TC-MUX021, or 1757-FIM Boot
on a Non-Redundant Server 1 . Refer
and Personality Images on page 7-9 to upgr ade the 1757-PLX52
boot and personality images to the current release level.
2. After upgrading the 1757-PLX52, refer to Upgrading Hardware
Component Firmware on page 7-4 to check if other hardware
components require upgrades.
IMPORTANT
Stop! It is essential that you check the firmware

revision levels for ALL ProcessLogix hardware
components after a ProcessLogix software
installation.
Do n ot proceed until you have upgr aded the
firmware.

Complete the following general steps to log on and check Control
Builder operation on a ProcessLogix Server.
Changing the default Operator's password

In previous releases of ProcessLogix it was not necessary to change
the default mngr operator's password to use it. As a security
precaution it is now necessary to change the password before you can
log in as the mngr operator. To change the password, do the
following:
1 . Click Star t Pr ogr ams Pr ocessLogix Ser ver Station .
2. Click the Oper field in the lower right corner of the display.
3. Enter >mngr< in the Station logon prompt and click OK.
4. Click Con figur e Oper ator s Oper ator s.
5. Click the mngr Operator ID.
6. Click Ch an ge Passw or d.
7. Enter the New Password, Confirm the New Password, and click
OK.
3-21
The message Passw or d accepted should appear in the message

zone. If it does not repeat steps 6 and 7.
Only systems using operator-based security and Control Builder
are affected by this change. The mngr operator account is
different than the Windows mngr user account. Navigate in
Knowledge Builder to Administration and Startup Guide for
more information before changing the password of the
Windows mngr user account.
8. Close Station.
9. Click Star t Pr ogr am s Pr ocessLogix En gin eer in g Tools
Con tr ol Builder.
1 0. In the Login dialog box, make these entries:
a. Enter >mngr< as the User Name.
b. Enter the appropriate Password.
c. Enter the appropriate Server name in the Server Name field.
d. Select Classic Ser ver Secur ity in the Domain Name
drop-down list.
1 1 . Click OK.

Performing backups is an essential part of maintaining your system.
You should back up all the files under the data directory, as well as
any user files you create. Refer to Backing Up a ProcessLogix R510.0
Server to Tape on page 8-8.
Creating an Emergency Repair Disk

After all installations and drivers are installed, you should create an
Emergency Repair Disk.
Complete the following steps to create an emergency repair disk for
your Windows 2000 Server installation.
Backup.
3-22
3. Click Emer gen cy Repair Disk.

4. Insert a blank diskette into the PC's floppy drive.
7. Repeat Steps 1 through 5 with another blank formatted diskette.
8. Click Job Ex it.
Chapter
ProcessLogix Server Upgrade Procedures
The supported ProcessLogix server upgrade scenarios are:
ProcessLogix Server
Upgrade Scenarios
Upgrade
Upgrade
Upgrade
Upgrade
Upgrade
from
from
from
from
from
R500.1
R500.1
R400.0
R400.0
R320.0
- clean install
SP2 - clean install
SP2
- requires clean install on new hardware

This section describes the steps necessary to upgrade the
ProcessLogix R500.1 Server software to R510.0. There are two upgrade
options.
IMPORTANT
Due to the nature of this upgrade, it is strongly

recommended that you follow Option 1 when
upgrading from R500.1 Server to R510.0.
Option 1: Upgrading R500.1 Server to R510.0 - Clean Install

a. Backup your data.
b. Install a clean Windows 2000 Server operating system.
c. Install ProcessLogix R510.0.
d. Restore your data.
The following table lists the items in Option 1 that you MUST
complete to upgrade an R500.1 Server to an R510.0 Server.
Table 4.A Option 1: Upgrading R500.1 Server to R510.0 Checklist
Step
Item
Page
1.

Server Upgrade
4-6
2.
Saving R400.0 SP2 or R500.1 Data to a Remote PC
4-13
3.
2-2
4.
2-29
5.
2-31
6.
2-33
7.
2-36
4-2
Table 4.A Option 1: Upgrading R500.1 Server to R510.0 Checklist
Step
Item
Page
8.
Updating ISScript
2-37
9.
2-38
1 0.
2-40
11.
Copying R400.0 SP2 or R500.1 Data to the R510.0 Server
4-33
1 2.
Restoring ProcessLogix Data
4-35
Option 2: Upgrading R500.1 Server to R510.0

b. Uninstall your current ProcessLogix software.
c. Install ProcessLogix R510.0.
d. Restore your data.
complete to upgrade an R500.1 Server to an R510.0 Server.
Table 4.B Option 2: Upgrading R500.1 Server to R510.0 Checklist
Step
Page
1.

Server Upgrade
4-6
2.
4-13
3.
Removing ProcessLogix R500.1 Software
4-15
4.
2-29
5.
2-31
6.
2-33
7.
2-36
8.
Updating ISScript
2-37
9.
3-2
1 0.
3-14
11.
Configuring RSLinx Drivers for ControlNet Supervisory Network

or
Configuring RSLinx Drivers for Ethernet Supervisory Network
3-16

or
6-2
1 2.
Item
3-19
3-20
1 3.
4-33
1 4.
4-35
4-3
Upgrade R400.0 SP2 Server to R510.0

This section describes the steps necessary to upgrade the
ProcessLogix R400.0 SP2 Server software to R510.0. There are two
upgrade options.
IMPORTANT
Due to the nature of this upgrade, it is strongly

recommended that you follow Option 1 when
upgrading from R400.0 SP2 to R510.0.
Option 1: Upgrading R400.0 SP2 Server to R510.0 - Clean Install

b. Complete a clean install.
c. Restore your data.
complete to upgrade an R400.0 SP2 Server to an R510.0 Server.
Upon restarting the system, you may receive a
message that a service failed to start. If you receive
this message, click OK.
TIP
Table 4.C Option 1: Upgrading R400.0 SP2 Server to R510.0 Checklist
Step
Item
Page
1.

Server Upgrade
4-6
2.
4-13
3.
2-2
4.
2-29
5.
2-31
6.
2-33
7.
2-36
8.
Updating ISScript
2-37
9.
2-38
1 0.
2-40
11.
4-33
1 2.
4-35
4-4
Option 2: Upgrading R400.0 SP2 Server to R510.0

a.
b.
c.
d.
Backup your data.

Uninstall your current ProcessLogix software.
Install ProcessLogix R510.0.
Restore your data.
complete to upgrade an R400.0 SP2 Server to an R510.0 Server.
Table 4.D Option 2: Upgrading R400.0 SP2 Server to R510.0 Checklist
Step
Item
Page
1.

Server Upgrade
4-6
2.
4-13
3.
Removing ProcessLogix R400.0 SP2 Software
4-19
4.
2-29
5.
2-31
6.
2-33
7.
2-36
8.
Updating ISScript
2-37
9.
3-2
1 0.
3-14
11.
Configuring RSLinx Drivers for ControlNet Supervisory Network

or
Configuring RSLinx Drivers for Ethernet Supervisory Network
3-16
1 2.
4-33
1 3.
4-35
3-19
4-5

ProcessLogix R320.0 Server is certified to run only on Windows NT
4.0. Due to significant changes in the ProcessLogix platform, operating
system, and performance requirements, upgrading from a
ProcessLogix R320.0 Server to a ProcessLogix R510.0 Server requires
that you purchase a new PC and complete a clean R510.0 Server
installation on Windows 2000 Server.
The procedures in this section assume that:
the old ProcessLogix R320.0 Server(s) and new ProcessLogix
R510.0 Server(s) are different PC hardware.
the new R510.0 Server(s) is fully up and configured at this stage.
If you need to install ProcessLogix R510.0 on your Server(s),
refer to ProcessLogix Software Installation on a Clean PC on
page 3-1.
the R320.0 and R510.0 Servers are configured on the same
network and accessible to each other. This requires that each
server has a different computer name and a unique TCP/IP
address for each network card.
Before continuing, it is recommended that you verify your R320.0 and
R510.0 Servers are properly connected using a utility like ping.
Table 4.E Upgrading R320.0 Server to R510.0 Checklist
Step
Item
Page
1.
Preparing for a ProcessLogix R320.0 to R510.0 Server

Upgrade
4-23
2.
Copying R320.0 Data to the R510.0 Server
4-29
3.
Transferring the 1784-PCIC Card to the R510.0 System
4-32
4.
4-35
4-6
Preparing for a
ProcessLogix R400.0 SP2 or
R500.1 to R510.0 Server
Upgrade
ATTENTION
All procedures listed in this section should be

performed with the system(s) Off-Process. Be certain
that your process is off control before you begin any
upgrade procedure. This means the 1757-PLX52
should be in the Idle state.
Exporting the R400.0 SP2 or R500.1 Engineering Repository

Database
IMPORTANT
To save Fieldbus device values and CM block

parameter values, it is recommended to do the
following:
1 . Upload w ith Con ten ts of your Control Modules.
2. Update to Pr oject, which saves the Monitor
image to the Project image.
This procedure captures the latest configuration
changes. Otherwise, after re-loading the CMs
following the ProcessLogix upgrade, changed values
would be lost.
Use the following procedure to export the Engineering Repository

Database.
Disabling ERDB Replication

This procedure is only required for a redundant Server pair. Complete
these steps on SERVERB only. If you have a non-redundant server,
skip to Exporting the Database Using Control Builder on page 4-7.
1 . Logon to SERVERB as ps_user.
2. Click Star t Pr ogr ams Pr ocessLogix En gin eer in g Tools
DB Adm in .
3. Expand DbAdmin .
4. In the Login dialog box make these entries:
a. Enter >mngr< as the default User Name.
c. Enter >localhost< in the Server Name field.
4-7
d. If necessary, select Classic Ser ver Secur ity in the Domain

Name drop-down list.
5. Expand Pr ocessLogix Node.
6. Click Adm in Tasks.
7. Click Disable Replication .
8. Click OK at the Disabled Database Replication prompt.
9. Close DbAdmin .
Exporting the Database Using Control Builder

Complete these steps on a non-redundant Server or SERVERB.
1 . If necessary, logon to the system as ps_user.
2. Using Windows Explorer, create the folder C:\Data\ExportDB.
Con tr ol Builder.
4. In the Login dialog box, make these entries:
a.
b.
c.
d.
Enter >mngr< as the User Name.

Enter the appropriate Password.
Enter >localhost< in the Server Name field.
Select Classic Ser ver Secur ity in the Domain Name
drop-down list.
5. Click OK.
6. Click File Ex por t.
7. Click Br ow se to set the Directory to C:\Data\ExportDB.
8. Click Select All.
a. Depending on the size of your database, this step may take
several minutes. It is recommended that you do not export
the examples. New examples are provided with R510.0.
b. To deselect an item, hold Ctrl and click each item.
4-8
c. Deselect the following Point Names:

example_cascade
example_motor
example_pid
example_scm
pidloop
8. Click Ex por t.
Depending on the size of your database, this step may take
several minutes to several hours.
9. When completed, close the Export Window (if it did not
automatically close).
1 0. Close Control Builder.
Saving Fieldbus Device Definition Files

This procedure is required if migrating a system containing Fieldbus
devices. Complete these steps on a non-redundant Server or
SERVERB. If you do not have Fieldbus devices connected to your
ProcessLogix system, skip to Saving Important R400.0 SP2 or R500.1
Server Data on page 4-9.
2. Using Windows Explorer, create the folder C:\Data\FFdevices.
5. At the C:\ prompt, enter >xcopy C:\Honeywell\TPS50\
System\ER\FFdevices\*.* C:\Data\FFdevices /E<
and press <Enter>.

6. If prompted, enter >A< to specify all files and folders.
4-9
7. Enter >xcopy C:\Honeywell\TPS50\System\ER\Release\*.*

C:\Data\FFdevices /E<
and press <Enter>.

8. If prompted, enter >A< to specify all files and folders.
9. Close the DOS window.
Saving Important R400.0 SP2 or R500.1 Server Data

Each of the following items should be completed on an R400.0 SP2 or
R500.1 Server before proceeding.
IMPORTANT
Redun dan t Pr ocessLogix System s

All steps need to be performed on both the Primary
(SERVERA) and Backup (SERVERB) ProcessLogix
Servers.
If you have a redundant Server pair, you must
complete this procedure on SERVERB first. Then
complete the entire procedure again on SERVERA.
ATTENTION
Before saving ProcessLogix data, you MUST exit all

ProcessLogix applications and stop all ProcessLogix
services. You must complete the procedure in
Stopping ProcessLogix Applications and Services on
page 8-1 before continuing.
4-10
Table 4.F Saving Important R400.0 SP2 or R500.1 Server Data

Item
Pre-upgrade Requirement
Post-upgrade
Folders and Files
The following folders and their sub-folders may contain files

you will require after upgrading. (For example. History
Archives in the archive folder, Event Archives in the evtarch
folder, etc.)
1. Using Windows Explorer, create the folder C:\Data\Server.
2. Copy these folders and files from C:\Honeywell\Server to
C:\Data\Server.
Copy backed up folders and files from the backup

directory to C:\Honeywell\Server after the system
is upgraded.
\archive
\cl
\evtarch
\help
\i18n
\report
\user
Custom Displays
Save any custom displays that were created. Typically these

displays are located in C:\Honeywell\Client\abstract.
1. Using Windows Explorer, create the folder C:\Data\abstract.
2. Copy all custom displays to C:\Data\abstract.
Copy backed up displays from the backup directory

to C:\Honeywell\Client\abstract.
Custom displays may require modification for use
in an R510.0 system.
System Displays
Document any changes that were made to existing system

displays. This applies in particular to the System Startup
display, which is often customized.
You must reapply the changes to the new display

after the upgrade.
Station Menus
Document any changes that were made to existing menus.
You must reapply the changes to the new menus

after the upgrade.
System Acronyms
Document any changes that were made to existing set.
You must reapply the changes to the new set after

the upgrade.
Scan Periods
Document any specialized scan periods that were used.
You must reapply the periods after the upgrade.
Localization
Localization settings are lost during the upgrade.
You must reapply the settings after the upgrade.
Station
configuration file
C:\Winnt\station.ini
Document any changes that were made to the station.ini file.
Navigate in Knowledge Builder to Server and Client
Configuration Guide Configuring Stations and Printers
Station.ini.
You must reapply the changes to the new

station.ini file after the upgrade.
Station setup file
C:\Honeywell\client\station\default.stn
Document any changes that were made to the default Station
setup file, default.stn.
The new default setup file, default.stn, is

configured as Static Station 1. If this is not
correct, you must make the appropriate changes to
the Connection Properties.
Navigate in Knowledge Builder to Server and
Client Configuration Guide Configuring
Stations and Printers Setting Up Station for
more information.
History archive
search path
Document the history archive search path.

1. Click Start Programs ProcessLogix Server
ProcessLogix Server Control Panel.
2. In the Registry Key drop-down list, select ArchiveDirectory.
3. Document the String field.
After upgrading, you must specify the history

archive search path using the ProcessLogix Server
Control Panel.
Client Configuration Guide Understanding and
Configuring Points History Collection and
Archiving History Archiving for more
information.
4-11
Table 4.F Saving Important R400.0 SP2 or R500.1 Server Data

Item
Post-upgrade
Custom applications Backup any custom applications built for your existing system. Custom applications must be re-compiled and
re-linked using an appropriate development
environment.
Navigate in Knowledge Builder to Application
Development Guide About the Development
Environment Compiling, Linking, and Editing
for more information.
Quick Builder
projects
Backup any Quick Builder projects.
When opening an old project file with the new

version of Quick Builder, you are prompted to
migrate the project file to the new format.
File dumps
Do not use any file dumps of the pre-upgrade

database to restore the upgraded database.
Hardware definition
files
If you want to use existing hardware definition (hdwbld) files

to build printers, you must change any instance of the
CYRILLIC keyword to LANGUAGE=CYRILLIC.
Alarms and
messages
Resolve any alarms before starting the upgrade. Alarms and

messages currently in the system cannot be copied across for
the upgrade.
Handover notes
Handover notes are lost during the upgrade. Handover notes

in the system cannot be copied for the upgrade.
Exporting the R400.0 SP2 or R500.1 ProcessLogix Server Database

ATTENTION
Before exporting the ProcessLogix Server Database,

you MUST exit all ProcessLogix applications and
stop all ProcessLogix services. You must complete
the procedure in Stopping ProcessLogix Applications
and Services on page 8-1 before continuing.
If you have a redundant server pair, you must
If you have a redundant Server pair, complete these steps on

SERVERA only.
4-12
4. Enter >xcopy C:\Honeywell\server\data\*.* C:\

Data\server\backup /E<
and press <Enter>.

5. If necessary, enter >D< to specify that backup is a directory.
6. Wait until the C:\ prompt appears and close the DOS window.
Removing the RSLinx Software Activation File

It is possible to transfer your RSLinx Activation codes from the old
system to the new system. Complete these steps on each Server in
your system.
To move the activation file from your Server:
1 . Insert the RSLinx Master Disk into the floppy drive.
5. Verify that you are Moving Activations From Drive C:(or your hard
drive letter) to Drive A:(or your floppy drive letter).
7. Click Move to move the file to the floppy.
OK.
4-13
9. Close EvMove.
1 0. Remove the Master Disk and store it in a safe place.
Preparation for a ProcessLogix R400.0 SP2 or R500.1 to R510.0 Server
Upgrade is complete.
Saving R400.0 SP2 or R500.1 Networking an R400.0 SP2 or R500.1 Server to a Remote PC
Data to a Remote PC
Use the following procedure to map a drive to a remote PC. If you
have a redundant server pair, you must complete this procedure on
SERVERB first. Then complete the entire procedure again on
SERVERA.
1 . If necessary, logon to the R400.0 SP2 or R500.1 Server as
ps_user.
4. Enter >NET USE T: \\STN01\C$ /user:ps_user<
(where STN01 is the remote PC name and ps_user is the user

currently logged on to STN01) and press <Enter>.
5. If prompted, enter the appropriate password.
6. Open Windows Explorer and verify that the T: drive exists.
4-14
Transferring Data
1 . If you have a non-redundant server:
a. At the DOS prompt, enter >xcopy C:\Data\*.* T:\
UpgradeData /E< and press <Enter>.
b. If necessary, enter >D< to specify that UpgradeData is a

directory.
2. If you have a redundant Server pair:
a. At the DOS prompt, on SERVERA, enter >xcopy C:\Data\
*.* T:\UpgradePrimaryData /E< and press <Enter>.
b. If necessary, enter >D< to specify that UpgradePrimaryData is

a directory.
c. On SERVERB, enter >xcopy C:\Data\*.* T:\
UpgradeBackupData /E< and press <Enter>.
d. If necessary, enter >D< to specify that UpgradeBackupData is

a directory.
4-15
Disconnect Redundant Servers

If you have a redundant Server pair, complete these steps on both
SERVERA and SERVERB. If you have a non-redundant Server, return
to the checklist that led you to this task.
1 . Disconnect the Ethernet network cable(s).
2. Use the PING command to confirm that the Servers can no
longer communicate with each other by name or IP address.
The network cables should be reconnected only after both
Servers have been upgraded.
3. Close the DOS window.
Saving Data to a Remote PC is complete.
Removing ProcessLogix
R500.1 Software
This procedure completely removes ProcessLogix R500.1 SP2 software

from your system, including:
SQL
Knowledge Builder
RSLinx
Engineering Tools
Server and/or Station
ATTENTION
Before installing or uninstalling any software

component, you MUST exit all ProcessLogix
applications and stop all ProcessLogix services. You
must complete the procedure in Stopping
ProcessLogix Applications and Services on page 8-1
before continuing.
Removing Selected ProcessLogix R500.1 Components

4-16
3. Double-click Add/Remove Pr ogr ams.

4. To remove a program:
a. Click on the appropriate program in the list of installed
programs.
b. Click Add/Remove, Ch an ge/Remove or Remove.
c. Click Yes to confirm removal.
d. Repeat the steps for each installed component in the
following order.
IMPORTANT
Be sure to remove the components, if installed, in

the order they are listed below.
If at any time during software uninstall, a Remove
shared file prompt appears, click Yes to all or
Remove all.
If necessary, click OK or Yes to confirm.
If you see an Uninstall successfully completed
message, or a message stating some elements were
not removed, click OK.
If a delay occurs during uninstall, verify that there
are no hidden Remove Programs windows in the
taskbar.
When you remove a program, its name may not be
automatically removed from the Add/Remove
Programs window. Do not remove the program
again, continue with the next program on the list.
Table 4.G Removal of Selected ProcessLogix R500.1 Components
Order Component
1 . ProcessLogix Update
2. Process Detail Displays (If you receive a Windows Installer prompt, click
Cancel, then click OK. Continue with the next section.)
3. Control Component Library

4. PsAxCtl Document EXE (If you see Application Removal windows, click
OK.)
5. Psc Engineering Tools

6. RSLinx
7. KB Server - Knowledge Builder Tools 4
8. KB Server - ProcessLogix R500
9. KB Client
4-17
Table 4.G Removal of Selected ProcessLogix R500.1 Components
Order Component
1 0. Knowledge Builder (At the Maintenance Welcome window, click

Remove and click Next.)
1 1 . Microsoft SQL Server 2000

1 2. PLX System Installer
(If you receive PSRoot Key and Fatal errors, these are expected and will
not effect the outcome of the installation. Click OK to continue.)
5. Close the Add/Remove Programs window.
Remove ProcessLogix Server Components

1 . Click Star t Pr ogr ams Pr ocessLogix Ser ver Setup.
2. Select Pr ocessLogix and click Nex t.
3. Click Nex t at the Welcome window.
4. Check the Remove Pr ocessLogix Ser ver softw ar e checkbox
and click Nex t.
5. Click Select All and then click Nex t.
6. Click Yes to continue.
7. Click Nex t at the Confirmation window.
8. Click OK at all createsqlobject prompts.
4-18
Verifying and Finalizing Component Removal

IMPORTANT

Remove all.
1 . Double-click Add/Remove Pr ogr ams in the Control Panel

window.
2. If any of the following programs are still present in the
Add/Remove programs list, select and remove them in the
following order.
ProcessLogix Update
Process Detail Displays
Control Component Library
PSAxCtl Document EXE
Psc Engineering Tools
KB Server - Knowledge Builder Tools 4
KB Server - ProcessLogix 500
KB Client
Knowledge Builder
Microsoft SQL Server
RSLinx
HMIWeb
HMIWeb Station
HMIWeb Station and Display Builder
Display Builder 320.2
Quick Builder
VBScript Documentation
3. Select Pr ocessLogix - Remove th is last.

4. Click Ch an ge/Remove.
6. Click OK when completed.
4-19

8. Close the Control Panel window.
9. Using Windows Explorer, delete the folder C:\Honeywell.
1 0. Click Yes, as necessary, to confirm.
1 1 . Empty the Recycle Bin.
Removing ProcessLogix R500.1 Software is complete.
Removing ProcessLogix
R400.0 SP2 Software
This procedure completely removes ProcessLogix software from your

system, including:
SQL
Knowledge Builder
RSLinx
Engineering Tools
Server and/or Station
ATTENTION

before continuing.
Removing Selected ProcessLogix R400.0 SP2 Components

4-20
programs.
following order.
IMPORTANT

Remove all.
If a delay occurs during uninstall, check the task bar
and call up the Remove Programs window.
Table 4.H Removing Selected R400.0 SP2 Components
Order
Component
1.
ProcessLogix SP2 Update
2.
Engineering Tools R400 SP2 Option
3.
Engineering Tools R400 SP2
4.
ProcessLogix - R400 SP2
5.
ProcessLogix Update
6.
7.
PsAxCtl Document EXE (If you see Application Removal windows,

click OK)
8.
9.
RSLinx
1 0.
Knowledge Builder
11.
Microsoft SQL Server 7.0
1 2.
PLX System Installer
4-21
Removing ProcessLogix Server Components

2. If necessary, at the Select Product to Install window, select the
Pr ocessLogix option, and click Nex t.
and click Nex t.
8. If a Sentinel Pro Driver Setup error window opens, click OK.

1 . Close the Add/Remove Programs window.
2. Double-click Add/Remove Pr ogr ams in the Control Panel
window.
IMPORTANT

Remove all.

following order.
ProcessLogix SP2 Update
Engineering Tools R400 SP2 Option
4-22
Engineering Tools R400 SP2

ProcessLogix Update
RSLinx
Knowledge Builder
Microsoft SQL Server 7.0
Quick Builder
ProcessLogix Server R400.0

1 0. Using Windows Explorer, delete the folder C:\Honeywell.
1 1 . If necessary, click Yes to confirm file deletion.
1 2. Empty the Recycle Bin.
TIP
Upon restarting the system, you may receive a

message that a service failed to start. If you receive
this message, click OK.
Removing ProcessLogix R400.0 SP2 Software is complete.

Preparing for a
ProcessLogix R320.0 to
R510.0 Server Upgrade
ATTENTION
4-23
All procedures in this section should be performed

with the system(s) Off-Process. Be certain that your
process is off control before you begin any upgrade
procedure. This means the 1757-PLX52 should be in
the Idle state.
All work performed in this section occurs on the
existing ProcessLogix R320.0 Server(s).
If operating a redundant server pair, be sure that
unless otherwise indicated in the upgrade procedure
SERVERA is primary, SERVERB is backup, and the
servers are synchronized.
Backing Up a ProcessLogix R320.0 Server to Tape

A complete system backup should be performed before proceeding
with the procedures in this section. This should include the
Engineering Database, ProcessLogix Server Database, Windows
Registry, and all files on the system.
Refer to Backup up a ProcessLogix Server to Tape on page 1-6 of the
R320.0 Installation and Upgrade Guide to back up your current
ProcessLogix R320.0 Server data to tape.
4-24
Exporting the R320.0 Engineering Repository Database

IMPORTANT
You must export the Engineering Repository

Database at this time before proceeding.
To save the CM block parameter values to the
Monitor image, it is recommended to do the
following:
1 . Upload w ith Con ten ts of your Control Modules.
2. Update to Pr oject, which saves the Monitor
image to the Project image.
This procedure captures the latest configuration
changes. Otherwise, after re-loading the CMs
following the Processlogix upgrade, changed values
would be lost.
Stopping the ER Replicator Service

This procedure is required for a Redundant Server pair only. Complete
these steps on SERVERB only. If you have a non-redundant server,
skip to Exporting the Database Using Control Builder on page 4-24.
1 . Logon to SERVERB as plx_user.
3. Double-click Ser vices.
4. Select the Plan tScape ER Replicator service and click Stop.
6. Close the Services and Control Panel windows.
Exporting the Database Using Control Builder

Complete these steps on a non-redundant Server or SERVERB.
1 . Using Windows Explorer, create the folder C:\Data\ExportDB.
Con tr ol Builder.
4-25

b. Enter >mngr1< as the default Password.
c. Enter >localhost< in the Server Name field.
4. Click OK.
6. Click Br ow se to set the Directory Path to C:\Data\ExportDB.
several minutes. It is recommended that you do not export
b. To deselect an item, hold <Ctrl> and click each item.
example_cascade
example_motor
example_pid
example_scm
pidloop
8. Click Ex por t.
9. When completed, close the Export Window (if it did not
1 1 . Document all CPM/CEE names and addresses.
You will need to create new CPMs/CEEs in R510.0, that have the
same names as the R320.0 CPMs/CEEs, prior to importing your
control strategy.
4-26
Saving Important R320.0 Server Data

Each of the following items should be completed on an R320.0 Server
before proceeding.
IMPORTANT
Redun dan t Pr ocessLogix Systems

All steps need to be performed on both the Primary
(SERVERA) and Backup (SERVERB) ProcessLogix
Servers.
ATTENTION
Before saving ProcessLogix data, you MUST exit all

ProcessLogix applications and stop all ProcessLogix
services. You must complete the procedure on page
1-8 of the ProcessLogix R320.0 Installation and
Upgrade Guide, before continuing.
Table 4.I Saving Important R320.0 Server Data

Item
Post-upgrade
Folders and Files
The following folders and their sub-folders may contain files

you will require after upgrading. (For example. History
Archives in the archive folder, Event Archives in the evtarch
folder, etc.)
1. Using Windows Explorer, create the folder C:\Data\Server.
2. Copy these folders and files from C:\Honeywell\Server to
C:\Data\Server:
Copy backed up folders and files from the backup

directory to C:\Honeywell\Server after the system
is upgraded.
\archive
\cl
\evtarch
\help
\i18n
\report
\user
Custom Displays

Copy all custom displays to C:\Data\abstract.
Copy backed up displays from the backup directory

to C:\Honeywell\Client\abstract.
Custom displays may require modification for use
in an R510.0 system.
System Displays

displays. This applies in particular to the System Startup
You must reapply the changes to the new display

after the upgrade.
Station Menus
You must reapply the changes to the new menus

after the upgrade.
System Acronyms
Document any changes that were made to existing set.
You must reapply the changes to the new set after

the upgrade.
4-27
Table 4.I Saving Important R320.0 Server Data

Item
Post-upgrade
Scan Periods
Document any specialized scan periods that were used.
Localization
Station
configuration file
Station.ini for more information.
You must reapply the changes to the new

station.ini file after the upgrade.
Station setup file
C:\Honeywell\client\station\default.stn
The new default setup file, default.stn, is

configured as Static Station 1. If this is not
correct, you must make the appropriate changes to
the Connection Properties.
Client Configuration Guide Configuring
Stations and Printers Setting Up Station for
more information.
History archive
search path
Document the history archive search path.
After upgrading, you must specify the history

archive search path using the ProcessLogix Server
Control Panel.
Client Configuration Guide Understanding and
Configuring Points History Collection and
Archiving History Archiving for more
information.
Custom applications Backup any custom applications built for your existing system. Custom applications must be re-compiled and
re-linked using an appropriate development
environment.
Navigate in Knowledge Builder to Application
Development Guide About the Development
Environment Compiling, Linking, and Editing
for more information.
Quick Builder
projects
Backup any Quick Builder projects.
File dumps
When opening an old project file with the new

version of Quick Builder, you are prompted to
migrate the project file to the new format.
Do not use any file dumps of the pre-upgrade
database to restore the upgraded database.
Hardware definition
files
If you want to use existing hardware definition (hdwbld) files

to build printers, you must change any instance of the
CYRILLIC keyword to LANGUAGE=CYRILLIC.
Alarms and
messages
Resolve any alarms before starting the upgrade. Alarms and

messages currently in the system cannot be copied across for
the upgrade.
Handover notes
Handover notes are lost during the upgrade. Handover notes

in the system cannot be copied for the upgrade.
4-28
Exporting the ProcessLogix Server Database

ATTENTION
Before exporting the ProcessLogix Server Database,

the procedure on page 1-8 of the ProcessLogix
R320.0 Installation and Upgrade Guide, before
continuing.
If you have a Redundant Server pair, complete this procedure on

SERVERA only.
1 . Logon to the R320.0 system as plx_user.
4. At the DOS prompt, enter >hscserver /unload /y< and press
<Enter>.
5. Enter the following command:
>xcopy C:\Honeywell\server\data\*.* C:\Data\Server\backup /E<
and press <Enter>.

7. Wait until the C:\ prompt appears and close the DOS window.
Removing the RSLinx Software Activation File

It is possible to transfer your RSLinx Activation codes from the old
system to the new system. To move the activation file from your
R320.0 Server:
1 . Locate the RSLinx Master Disk and insert it into the floppy drive.
4-29

5. Verify that you are Moving Activations From Drive C:(or your hard
drive letter) to Drive A:(or your floppy drive letter).
7. Click Move to move the file to the floppy.
OK.
9. Close EvMove.
1 0. Remove the Master Disk and store it in a safe place.
Preparation for a ProcessLogix R320.0 to R510.0 Server Upgrade is
complete.
Copying R320.0 Data to the

R510.0 Server
Networking the R320.0 and R510.0 Servers

Use the following procedure to map a drive to the new R510.0 Server.
1 . Logon to the R320.0 Server as plx_user.
4-30
4. If you have a non-redundant server, enter

>NET USE T: \\PLX1\C$ /user:ps_user<
(where PLX1 is the R510.0 Server name) and press <Enter>.

5. Open Windows Explorer and verify that the T: drive exists.
6. If you have a redundant server pair,
a. On SERVERB, enter
>NET USE T: \\PLX1B\C$ /user:ps_user<
(where PLX1B is the name of the R510.0 Backup Server)

and press <Enter>.
b. On SERVERA, enter
>NET USE T: \\PLX1A\C$ /user:ps_user<
(where PLX1A is the name of the R510.0 Primary Server)

and press <Enter>.
c. Open Windows Explorer on each R320.0 Server and confirm
that the T: drive exists.
Transferring R320.0 Data to the R510.0 Server

1 . On the R320.0 Server(s), click Star t Run .
4-31
3. If you have a non-redundant server:

a. Enter >xcopy C:\Data\*.* T:\R320Data\ /E<
and press <Enter>.

b. If necessary, enter >D< to specify that R320Data is a directory.
c. Wait until the C:\ prompt appears and close the DOS
window.
4. If you have a redundant server pair:
a. On SERVERA, enter
>xcopy C:\Data\*.* T:\R320PrimaryData\ /E<
and press <Enter>.

b. If necessary, enter >D< to specify that R320PrimaryData is a
directory.
c. Wait until the C:\ prompt appears and close the DOS
window.
d. On SERVERB, enter
>xcopy C:\Data\*.* T:\R320BackupData\ /E<
and press <Enter>.

e. If necessary, enter >D< to specify that R320BackupData is a
directory.
f. Wait until the C:\ prompt appears and close the DOS
window.
Copying R320.0 Data to the R510.0 Server is complete.
4-32
Transferring the 1784-PCIC

Card to the R510.0 System
The following procedure describes how to transfer the 1784-PCIC card

from your R320.0 system to an R510.0 system.
1 . If your R510.0 system already contains an 1784-PCIC card, skip
to Restoring ProcessLogix Data on page 4-35.
2. Shut down and turn the power off to both the R320.0 and R510.0
Server(s).
ATTENTION
You must turn the power off to both systems before

attempting to transfer hardware. Failure to do so
could result in hardware damage.
3. Remove the 1784-PCIC card from the R320.0 Server and insert it
into the R510.0 Server. Refer to the 1784-PCIC Installation
Instructions, Publication 1784-IN003A.
4. Turn on the R510.0 Server.
5. Logon to the R510.0 Server as ps_user.
6. If the Found New Hardware Wizard opens, skip to step 11. If the
Found New Hardware Wizard does not open, continue with
Step 7.
7. Right-click the My Computer icon and select Man age.
8. Select Device Man ager.
9. Under Other Devices, right-click the PCI device and select
Pr oper ties.
1 0. On the Driver tab, click Update Dr iver.
1 1 . Click Nex t.
1 2. Select the Sear ch for a suitable dr iver option and click Nex t.
1 3. Check only the Specify a location checkbox and click Nex t.
1 4. Insert the ProcessLogix R510.0 Application Software CD into the
CD-ROM drive.
4-33
1 5. Enter this path location in the Copy manufacturers file from

field or Br ow se to:
>D:(or your CD-ROM drive letter)\RSLinx\RSLinx\
PlugNPlay\Win2K\1784-PCIC(S)\abpcic.inf<
1 6. Click OK.
1 7. Click Nex t to install the driver.
1 8. If a Digital Signature Not Found window opens, click Yes.
1 9. If necessary, click Yes to overwrite the VirtualBackplane.sys file.
20. If necessary, click Yes to overwrite the ABPCICSW.sys file.
21 . Click Fin ish .
Transfer of the 1784-PCIC Card to the R510.0 System is complete.
Copying R400.0 SP2 or

R500.1 Data to the R510.0
Server
Reconnect Redundant Servers

If you have a redundant Server pair, both SERVERA and SERVERB
should have been upgraded to ProcessLogix R510.0.
1 . Shutdown both servers.
2. Reconnect the Ethernet network cable(s).
3. Restart SERVERA.
4. On SERVERA, right-click in the taskbar to open the popup
menu and click Task Manager to call up the Windows Task
Manager dialog box.
5. Click the Performance tab.
6. Monitor the CPU Usage until the value displayed goes below the
90 to 100% threshold.
Wait until the RSLinx icon appears in the taskbar. This assures
proper startup time of ProcessLogix services on SERVERA
before restarting SERVERB.
7. Click File Ex it Task Man ager.
4-34
8. Restart SERVERB.
Transferring R400.0 SP2 or R500.1 Data to the R510.0 Server

3. If you have a non-redundant server:
a. Enter >xcopy T:\UpgradeData\*.* C:\UpgradeData /E< and
press <Enter>.

directory.
4. If you have a redundant Server pair,
a. On SERVERA, enter >xcopy T:\UpgradePrimaryData\*.* C:\
UpgradePrimaryData /E< and press <Enter>.

directory.
c. On SERVERB, enter >xcopy T:\UpgradeBackupData\*.*
C:\UpgradeBackupData /E< and press <Enter>.
d. If necessary, enter >D< to specify that UpgradeData is a

directory.
5. Close the DOS window(s).
Copying R400.0 SP2 or R500.1 Data to the R510.0 Server is complete.
Restoring ProcessLogix
Data
4-35
Each of the following items should be considered before proceeding.

Table 4.J Restoring ProcessLogix Data Considerations
Item
Post-upgrade
Folders and Files
Copy backed up folders and files from the backup Server

directory to c:\Honeywell\Server after the system is
upgraded.
Custom Displays may require modification for use in an
R510.0 system.
Custom Displays
Custom displays may require modification for use in an

R510.0 system. Copy backed up displays from the backup
abstract directory to C:\Honeywell\Client\abstract.
System Displays
You must reapply the changes to the new display after the
upgrade.
Station Menus
You must reapply the changes to the new menus after the
upgrade.
System Acronyms
You must reapply the changes to the new set after the
upgrade.
Scan Periods
Localization
Station configuration file
You must reapply the changes to the new station.ini file after
the upgrade.
Station setup file
The new default setup file, default.stn, is configured as

static Station 1. If this is not correct, you must make the
appropriate changes via Stations Setup menu.
Configuration Guide Configuring Stations and
Printers Setting Up Station for more information.
History archive search path After upgrading, you must specify the history archive search
path using the ProcessLogix Server Control Panel.
Configuration Guide Understanding and Configuring
Points History Collection and Archiving History
Archiving for more information.
Custom applications
Custom applications must be re-compiled and re-linked using

an appropriate development environment.
Navigate in Knowledge Builder to Application Development
Guide About the Development Environment
Compiling, Linking, and Editing for more information.
Quick Builder projects
When opening an old project file with the new version of

Quick Builder, you are prompted to migrate the project file to
the new format.
File dumps
Do not use any file dumps of the pre-upgrade database to

restore the upgraded database.
4-36
Restoring Server Redundancy

If you have a redundant Server pair, you need to restore redundancy
between the two Servers to complete the upgrade procedure.
Complete the steps to restore redundancy in Chapter 6, Additional
Redundant Server Procedures. See Table 6.A on page 6-1.
Importing the Engineering Database

Complete the steps below to import the Engineering Database. For a
redundant Server pair complete these steps on SERVERB only.
IMPORTANT
If you are upgrading a redundant Server pair, you

must finish setting up redundancy before continuing.
Changing the default Operator's password

In previous releases of ProcessLogix it was not necessary to change
the default mngr operator's password to use it. As a security
precaution it is now necessary to change the password before you can
log in as the mngr operator. Only systems using operator based
security and Control Builder are affected by this change. The mngr
operator account is different than the Windows mngr user account.
Navigate in Knowledge Builder to Administration and Startup Guide
for more information before changing the password of the Windows
mngr user account.
To change the password, do the following:
1 . Logon to R510.0 Server as ps_user.
2. Click Star t Pr ogr ams Pr ocessLogix Ser ver Station .
5. Click Con figur e Oper ator Oper ator s.
4-37
8. Enter the New Password, Confirm the New Password and click
OK.
zone. If it does not, repeat steps 7 and 8.
If migrating a system with Fieldbus devices, continue with Adding
Saved Device Templates Using Fieldbus Library Manager on page
4-37. Otherwise skip to Importing the Database Using Control Builder
on page 4-38.
Adding Saved Device Templates Using Fieldbus Library Manager

For a redundant Server pair, complete these steps on SERVERB only.
1 . Click Star t Pr ogr ams Pr ocessLogix En gin eer in g Tools
Fieldbus Libr ar y Man ager.
b. Enter the appropriate password.
c. Select Classic Ser ver Secur ity in the Domain Name
drop-down list.
3. Click File Open Device.
4. Browse to your FFDevices backup directory, select a device and
click OK.
For example: C:\UpgradeData\FFDevices
5. Click File Save.
6. If necessary, click Yes at the Resolve Load Destination window.
7. Click OK.
8. Click File Build Device Template Fr om Cur r en t
Device.
Do not use the From Existing .DEF files option.
9. Click OK to confirm file addition.
1 0. Repeat Steps 3-9 for each device stored in the FFDevices backup
directory.
1 1 . Close the Fieldbus Library Manager.
4-38
Importing the Database Using Control Builder

Con tr ol Builder.
a.
b.
c.
d.
Enter >mngr< as the default User Name.

Enter the appropriate Server name in the Server Name field.
drop-down list.
IMPORTANT
If importing from R320.0, you need to recreate your

CPMs prior to importing the control strategies. When
recreating the CPMs and CEEs, make sure that you
use the exact same names as were used in R320.0.
3. Click File Impor t.

4. Click Br ow se to set the import Directory Path to your Exportdb
backup directory.
For example: C:\R320Data\ExportDB or
C:\UpgradeBackupData\ExportDB.
IMPORTANT
Do not import any CEEs. Attempting to import CEEs

from a prior release will cause the import to fail.

several minutes. It is recommended that you do not import
b. To deselect an item, hold Ctrl and click each item.
All CEEs
All CPMs (only if importing from R320.0)
example_cascade
example_motor
example_pid
example_scm
pidloop
6. Click Impor t.
4-39
7. When completed, close the Import Window (if it did not

8. Close Control Builder.
Restoring the ProcessLogix Server Points Database

ATTENTION
Before restoring the ProcessLogix Server Database,

the procedure in Stopping ProcessLogix Applications
and Services on page 8-1 before continuing.
If you have redundant servers, you must complete
this procedure on SERVERB first. Then complete the
entire procedure again on SERVERA.
Complete the steps below to restore the Server database. For a

Redundant Server Pair, complete these steps on SERVERA only.
1 . Logon to the system as ps_user.
4. At the DOS prompt, enter >hscserver /unload /y< and press
<Enter>.
5. Enter >xcopy C:\(backup data folder name)\server\backup\
*.* C:\Honeywell\server\backup\ /E<
For example, >xcopy C:\UpgradeData\server\backup\...<
and press <Enter>.
7. If necessary, enter >A< to overwrite files.
8. Enter >cd Honeywell\Server< and press <Enter>.
9. Enter >copy backup\points data /y< and press <Enter>.
1 0. To start the ProcessLogix Database, enter
>hscserver /database /y< and press <Enter>.
4-40
1 1 . To import the data, enter >sysbld -restore C:\

Honeywell\server\backup\data -y< and press <Enter>.
several minutes.
1 2. To start the ProcessLogix Server enter >hscserver /start /y< and
press <Enter>.
1 3. Close the command prompt.

1 . Refer to 1784-PCIC Driver Installation on page 7-1 and
1784-PCIC Firmware Installation on page 7-3 to upgrade the
1784-PCIC to the supported driver and firmware revisions.
2. Refer to Loading 1757-PLX52, TC-MUX021, or 1757-FIM Boot
IMPORTANT
Stop! It is mandatory that you check the firmware

installation and/or a component addition or
replacement.
firmware. Then go to the next section, Backing Up a
ProcessLogix Server Hard Drive to Tape.
ATTENTION
!
If you also upgraded from a non-redundant

1757-PLX52 to a redundant 1757-PLX52, you must
delete the existing CPM and its associated CEE from
the Project tab, reconfigure a new 1757-PLX52 and its
associated CEE, and reassign the components before
you download the CPM to the Controller.
4-41
Reloading Controllers
1 . Click Star t Pr ogr am s Pr ocessLogix En gin eer in g Tools
Con tr ol Builder.
a.
b.
c.
d.
Enter >mngr< as the default User Name.

Enter the appropriate Server name in the Server Name field.
drop-down list.
3. Click OK.
4. In the Project tab, confirm that the components of your
configured control strategy are listed in the Root directory.
5. Download each CPM and SRM to its given Controller.
6. Download the database (contents of each CPMs CEE) to the
Controller.
7. In the Monitoring tab, activate the CEE and all of its components
in a given Controller.

any user files you create. Refer to Backing Up a ProcessLogix R510.0
Server to Tape on page 8-8.
4-42
Chapter
ProcessLogix Client Installation and Upgrade

Procedures
Introduction
Two levels of the ProcessLogix Client workstation software installation

are available:
Operator Workstation
Engineering Workstation
Operator Workstation allows remote connections to the ProcessLogix
Server.
Engineering Workstation has all the functionality of the Operator
Workstation but also includes the ProcessLogix Engineering Tools.
From the Engineering Workstation, an engineer using Control Builder
can remotely access and modify the 1757-PLX52 ERDB. All installation
scenarios apply to both Operator Workstations and Engineering
Workstations.
IMPORTANT
Original releases of the NT 4.0 Operating system

could not have boot partitions larger than 4 GB.
Later, fixes were applied for NT 4.0 to have a 7.8 GB
boot partition.
Windows 2000 operating systems can have a 32 GB
boot partition natively, and larger partitions with
certain hardware configurations.
ProcessLogix R510.0 Client Software requires that the
boot partition be at least 4 GB. If your existing
systems boot partition is less than 4 GB, you must
complete a clean machine installation to extend the
boot partition size after completing the data
preservation steps included in this section.
Systems with 4GB or greater boot partitions can
proceed with the installation procedure. However,
you may want to consider a clean install to extend
the boot partition size.
5-2
ProcessLogix Client Installation and Upgrade Procedures
ATTENTION
Client conversion is not dependent on the Server

conversion. This allows a customer with multiple
clients to pre-upgrade clients before upgrading the
ProcessLogix Server.
Since the procedures here do not affect the running
of the Server software, these procedures can be
performed with the system on-process. Caution
should be taken not to affect the Server in this
scenario.
If you are pre-converting clients before the Server is
converted to R510.0, these converted clients will
NOT be functional with the R320.0 or R400.0 SP2
System. R510.0 Client software is NOT backwards
compatible.
ATTENTION
!
Operating System Support
This procedure does NOT cover the existence of any

prior version of ProcessLogix Server Software on the
Client PC. To convert the systems which previously
had a version of R320.0 or R400.0 SP2 Server on
them to a R510.0 Client, you have to follow the
directions for a clean install.

The supported installations to Windows 2000 Professional are:
Clean
Upgrade from R500.1 on Windows 2000 Professional
Upgrade from R400.0 SP2 on Windows 2000 Professional
Upgrade from R400.0 SP2 on Windows NT 4.0 Workstation
(requires clean install)
Upgrade from R320.0 on Windows NT 4.0 Workstation (requires
clean install)
For these scenarios, the current required Operating System
components are Windows 2000 Professional with Windows 2000 SP 2
applied and Internet Explorer 6.0.
The Windows 2000 Professional software, Service Packs, and Internet
R510.0 Software CDs for your convenience.
5-3
The supported installations to Windows XP Professional are:
Clean
Upgrade from R500.1 on Windows XP Professional
Upgrade from R500.1 on Windows 2000 Professional
Upgrade from R400.0 SP2 on Windows 2000 Professional
Upgrade from R400.0 SP2 on Windows NT 4.0 Workstation
(requires clean install)
Upgrade from R320.0 on Windows NT 4.0 Workstation (requires
clean install)
Windows 2000 Server

Windows 2000 Server is not a recommended operating system for
Clients. Although the procedures for a Windows 2000 Client install can
be applied to both the Windows 2000 Professional and Windows 2000
Server Operating Systems, the preferred Client Operating System
between the two is Windows 2000 Professional. This version of the
operating system better fits the nature of the client/server architecture.
Windows 2000 Professional Clean Install: Windows 2000 Professional

Client Installation
Scenarios
the ProcessLogix Client Software on a clean PC.
Table 5.A Clean Install: Windows 2000 Professional
Step
Task to complete:
Refer to:
1.
2-11
2.
2-26
3.
2-29
4.
2-31
5.
2-33
6.
2-36
7.
Updating ISScript
2-37
8.
2-38
5-4
Table 5.A Clean Install: Windows 2000 Professional
Step
9.
Task to complete:
Refer to:
2-40
1 0.
Installing ProcessLogix R510.0 Client Software
5-18
11.
Finalizing ProcessLogix Client Installation
5-26
Upgrade R500.1 Windows 2000 Professional Client to R510.0

The following table lists the items that you MUST complete to
upgrade an R500.1 Windows 2000 Professional Client to an R510.0
Windows 2000 Professional Client.
Table 5.B Upgrade R500.1 Windows 2000 Professional Client to R510.0 Windows
2000 Professional Client
Step
Task to Complete:
Refer to:
1.
Saving Important Data
5-13
2.
Networking an Existing Client to a Remote PC
5-14
3.
Removing Selected R500.1 Components
5-15
4.
2-29
5.
2-31
6.
2-33
7.
2-36
8.
Updating ISScript
2-37
9.
5-18
1 0.
Transferring ProcessLogix Data
5-25
11.
5-26
5-5
Upgrade R400.0 SP2 Windows 2000 Professional Client to R510.0

upgrade an R400.0 SP2 Windows 2000 Professional Client to an R510.0
Windows 2000 Professional Client.
Table 5.C Upgrade R400.0 SP2 Windows 2000 Professional Client to R510.0
Order
Task to Complete:
Refer to:
1.
5-13
2.
5-14
3.
Removing Selected R400.0 SP2 Components
5-16
4.
2-29
5.
2-31
6.
2-33
7.
2-36
8.
Updating ISScript
2-37
9.
5-18
1 0.
5-25
11.
5-26
5-6
Upgrade R400.0 SP2 Windows NT 4.0 Client to R510.0 Windows

2000 Professional Client (Clean Install)
upgrade an R400.0 SP2 Windows NT 4.0 Client to an R510.0 Windows
2000 Professional Client.
IMPORTANT
Due to significant changes in the ProcessLogix

software, operating system, and performance
requirements, migration from a ProcessLogix R400.0
SP2 Windows NT 4.0 Client to a ProcessLogix R510.0
Client requires that you backup your R400.0 SP2 data
and then complete a clean ProcessLogix R510.0
Client installation. Refer to Table 11.B to confirm that
your PC meets the platform requirements for a
ProcessLogix R510.0 Client.
Table 5.D Upgrade R400.0 SP2 Windows NT 4.0 Client to R510.0 Windows 2000
Professional Client (Clean Install)
Step
Task to Complete:
Refer to:
1.
5-13
2.
5-14
3.
Clean System Windows 2000 Professional

Installation
2-11
4.
2-26
5.
2-29
6.
2-31
7.
2-33
8.
2-36
9.
Updating ISScript
2-37
1 0.
Additional Operating System Customization

Procedures
2-38
11.
2-40
1 2.
5-18
1 3.
5-25
1 4.
5-26
5-7
Upgrade R320.0 Windows NT 4.0 Client to R510.0 Windows 2000

upgrade an R320.0 Windows NT 4.0 Client to an R510.0 Windows
2000 Professional Client.
IMPORTANT

Client to a ProcessLogix R510.0 Client requires that
you backup your R320.0 data and then complete a
clean ProcessLogix R510.0 Client installation. Refer to
Table 11.B to confirm that your PC meets the
platform requirements for a ProcessLogix R510.0
Client.
Table 5.E Upgrade R320.0 Windows NT 4.0 Client to R510.0 Windows 2000
Step
Task to Complete:
Refer to:
1.
5-13
2.
5-14
3.
2-11
4.
2-26
5.
2-29
6.
2-31
7.
2-33
8.
2-36
9.
Updating ISScript
2-37
1 0.
2-38
11.
2-40
1 2.
5-18
1 3.
5-25
1 4.
5-26
5-8
Client Installation
Scenarios
Clean Install: Windows XP Professional

the ProcessLogix R510.0 Client Software on a clean PC.
Table 5.F Clean Install: Windows XP Professional
Step
Task to Complete:
Refer to:
1.
2-18
2.
2-26
3.
2-28
4.
2-31
5.
2-33
6.
Updating ISScript
2-37
7.
2-38
8.
2-40
9.
5-18
5-26
1 0.
Upgrade R500.1 Windows XP Professional Client to R510.0

Windows XP Professional Client
upgrade an R500.1 Windows XP Professional Client to an R510.0
Windows XP Professional Client.
Table 5.G Upgrade R500.1 Windows XP Professional Client to R510.0 Windows XP
Professional Client Checklist
Order
Task to Complete:
Refer to:
1.
5-13
2.
5-15
3.
2-28
4.
2-31
5.
2-33
6.
Updating ISScript
2-37
7.
5-18
8.
5-25
9.
5-26
5-9
Upgrade R500.1 Windows 2000 Professional Client to R510.0

upgrade an R500.1 Windows 2000 Professional Client to an R510.0
Table 5.H Upgrade R500.1 Windows 2000 Professional Client to R510.0 Windows XP
Professional Client Checklist
Order
Task to Complete:
Refer to:
1.
5-13
2.
5-14
3.
5-15
4.
Upgrading Windows 2000 Professional to XP

Professional
2-24
5.
2-28
6.
2-31
7.
2-33
8.
Updating ISScript
2-37
9.
5-18
1 0.
5-25
11.
5-26
Upgrade R400.0 SP2 Windows 2000 Professional Client to R510.0

upgrade an R400.0 SP2 Windows 2000 Professional Client to an R510.0
Table 5.I Upgrade R400.0 SP2 Windows 2000 Professional Client to R510.0 Windows
XP Professional Client Checklist
Order
Task to Complete:
Refer to:
1.
5-13
2.
5-14
3.
Removing Selected R400.0 SP2 Components
5-16
4.
Upgrading Windows 2000 Professional to XP

Professional
2-24
5.
2-28
5-10
Table 5.I Upgrade R400.0 SP2 Windows 2000 Professional Client to R510.0 Windows
XP Professional Client Checklist
Order
Task to Complete:
Refer to:
6.
2-31
7.
2-33
8.
Updating ISScript
2-37
9.
5-18
1 0.
5-25
11.
5-26
5-11
Upgrade R400.0 SP2 Windows NT 4.0 Client to R510.0 Windows XP

upgrade an R400.0 SP2 Windows NT 4.0 Client to an R510.0 Windows
XP Professional Client.
IMPORTANT

SP2 Windows NT 4.0 Client to a ProcessLogix R510.0
Client requires that you backup your R400.0 SP2 data
and then complete a clean ProcessLogix R510.0
Client installation. Refer to Table 11.B to confirm that
your PC meets the platform requirements for a
ProcessLogix R510.0 Client.
Table 5.J Upgrade R400.0 SP2 Windows NT 4.0 Client to R510.0 Windows
Professional XP Client (Clean Install) Checklist
Order
Task to Complete:
Refer to:
1.
5-13
2.
5-14
3.
2-18
4.
2-26
5.
2-28
6.
2-31
7.
2-33
8.
Updating ISScript
2-37
9.
2-38
1 0.
2-40
11.
5-18
1 2.
5-25
1 3.
5-26
5-12
Upgrade R320.0 Windows NT 4.0 Client to R510.0 Windows XP

upgrade an R320.0 Windows NT 4.0 Client to an R510.0 Windows XP
Professional Client.
IMPORTANT

Client to a ProcessLogix R510.0 Client requires that
you backup your R320.0 data and then complete a
clean ProcessLogix R510.0 Client installation. Refer to
Table 11.B to confirm that your PC meets the
platform requirements for a ProcessLogix R510.0
Client.
Table 5.K Upgrade R320.0 Windows NT 4.0 Client to R510.0 Windows XP

Professional Client (Clean Install) Checklist
Step
Task to Complete:
Refer to:
1.
5-13
2.
5-14
3.
2-18
4.
2-26
5.
2-28
6.
2-31
7.
2-33
8.
Updating ISScript
2-37
9.
2-38
1 0.
2-40
11.
5-18
1 2.
5-25
1 3.
5-26
5-13
Each of the following items should be completed on an R320.0,

R400.0 SP2, or R500.1 Client before proceeding. After you have
completed these items, return to the checklist that led you to this task.
Table 5.L Saving Important Data

Item
Pre-upgrade
Post-upgrade
Custom Displays

1. Using Windows Explorer, create the folder C:\Data\abstract.
2. Copy all custom displays to C:\Data\abstract.
Copy backed up displays from the backup directory to:

C:\Honeywell\client\abstract.
Custom displays may require modification for use in
an R510.0 system.
System Displays

displays.This applies in particular to the System Startup
You must reapply the documented changes to the

new system displays after the upgrade.
Station Menus
You must reapply the documented changes to the

new Station menus after the upgrade.
Localization
Station
configuration file
Station.ini for more information.
You must reapply the changes to the new station.ini

file after the upgrade.
Station setup file
C:\Honeywell\client\Station\default.stn
The new default setup file, default.stn, is configured

as Static Station 1. If this is not correct, you must
make the appropriate changes to the Connection
Properties.
Configuration Guide Configuring Stations and
Printers Setting Up Station for more information.
5-14
Networking an Existing
Client to a Remote PC
ATTENTION
All data saved on the existing Client PC should be

stored on a remote PC before upgrading the Client.
The remote PC can be any PC on the network, such
as another Client PC.
Complete the following steps to map a drive on an existing Client to a

remote machine.
1 . If necessary, logon to the Client.
currently logged on to STN01)
and press <Enter>.

6. Open Windows Explorer and confirm that the T: drive exists.
7. In the DOS window, enter >xcopy C:\Data\*.* T:\UpgradeData /E<
and press <Enter>.
8. If necessary, enter >D< to specify that UpgradeData is a

directory.
Networking an Existing Client to a Remote PC is complete.
Removing Selected R500.1

Components
5-15
Upgrading an R500.1 Windows 2000 or XP Professional Client requires

the removal of selected ProcessLogix components. Begin the removal
process by accessing the Add/Remove programs dialog box.
programs.
following order.
IMPORTANT

Remove all.
taskbar.
Table 5.M Removing Selected R500.1 Components
Order
Component
1.
ProcessLogix Update or ProcessLogix Operator Workstation Update
2.

(Engineering Workstation only)
3.
PsAxCtl Document EXE (Engineering Workstation only. If you see

Application Removal windows, click OK.)
4.
PSC Engineering Tools (Engineering Workstation only)
5.
Control Component Library (Engineering Workstation only)
6.
7.
KB Server - ProcessLogix R500
5-16
Table 5.M Removing Selected R500.1 Components
Order
Component
8.
KB Client
9.
Knowledge Builder (At the Maintenance Welcome window, click

Remove and click Next.)
1 0.

(If you receive PS Root Key and Fatal errors, these are expected and
will not effect the outcome of the installation. Click OK to continue.)
11.
System Displays 500.1
1 2.
Quick Builder
1 3.
ODBC Client 500.1
1 4.
OPC Server Connect 500.1
1 5.
Shape Library 500.1
1 6.
1 7.
Network API 500.1
1 8.
1 9.
Microsoft Excel Data Exchange (Click Enable Macros if prompted.)
20.
21 .
ProcessLogix - Remove this last

7. Restart the PC.
Removing Selected R500.1 Components is complete.
Removing Selected R400.0

SP2 Components
Upgrading an R400.0 SP2 Windows 2000 Professional requires the

removal of selected ProcessLogix components.
1 . If necessary, logon to the Client as ps_user.
5-17

programs.
following order.
IMPORTANT

Remove all.
taskbar.
Table 5.N Removing Selected R400.0 SP2 Components
Order
Component
1.
ProcessLogix SP2 Update or ProcessLogix SP2 Operator Workstation

Update
2.
Engineering Tools R400.0 SP2 Option

3.
Engineering Tools R400.0 SP2

4.
5.
ProcessLogix Update or ProcessLogix Operator Workstation Update
6.
OPC Server Connect 400.0
7.
TPS - HCI Runtime
8.
Server System Displays
9.
PlantScape Server ODBC Client 400.0
1 0.
Microsoft Excel Data Exchange 400.0
11.
1 2.
Network API 400.0
1 3.
Quick Builder
1 4.
5-18
Table 5.N Removing Selected R400.0 SP2 Components
Order
Component
1 5.

1 6.
Shape Library 400.0
1 7.
PsAxCtl Document EXE

1 8.
1 9.
PSC Engineering Tools

20.
Knowledge Builder
21 .
22.
ProcessLogix - Remove this last

7. Restart the PC.
Removing Selected R400.0 SP2 Components is complete.
Installing ProcessLogix
R510.0 Client Software
Complete the following steps to install the ProcessLogix R510.0 Client

software.
IMPORTANT
If you plan to use Microsoft Excel Data Exchange,

Microsoft Excel must be installed before installing
ProcessLogix.
Prior to the ProcessLogix installation, it is
man dator y that the Excel macro security level is set
to Medium . To change the security level for macro
virus protection in Excel:
1. On the Tools menu, click Macro, then click Security.
2. Click the Security Level tab, select Medium and click OK.
3. Close Excel.
IMPORTANT
Be sure to logon as ps_user. If you dont have a

ps_user user account, you must create one at this
time. Refer to Creating the ProcessLogix User
Accounts on page 2-26.
5-19

2. Close all running applications.
3. Insert the ProcessLogix R510.0 Base Software CD into the
CD-ROM drive.
>D:(or your CD-ROM drive letter)\SETUP.EXE<
7. Select the Engineering Workstation or Operator Workstation
option and click Nex t.
8. At the Product Selection Completed window, click Con tin ue.
The ProcessLogix R510.0 Base Software CD ejects.

ATTENTION

installation.


If Adobe Acrobat is already installed, the install automatically
continues with Installing Knowledge Builder Components, below.
1 . At the Acrobat Reader 4.05 Setup window, click Nex t.
3. Click OK.
5-20

1 . At the Knowledge Builder - Welcome window, click Nex t.
3. Select the KB Full option and click Nex t.
For additional information on KB install types, refer to Installing
Knowledge Builder Components on page 8-5.
4. Click Select All and click Nex t.
5. At the Server selection window, click Nex t to accept the default
directory for Knowledge Builder.
6. At the Start Copy window, click Nex t.
7. At the Installation Completed window, click Fin ish .
When the Knowledge Builder install is complete, the
ProcessLogix R510.0 Knowledge Builder CD ejects.
ATTENTION

installation.
8. Insert the ProcessLogix R510.0 Application Software CD into the

Installing Engineering Tools

This procedure is required for an Engineering Workstation only. If you
are installing an Operating Workstation, skip to Installing the
ProcessLogix Client Software on page 5-21.
1 . At the Ready to Install window, click In stall.
TIP
Command windows open during Engineering Tools

install. These windows close automatically.
5-21
2. At the Installation Complete window, click Fin ish .
Installing PsAxCtl Document EXE

This procedure is required for an Engineering Workstation only. If you
are installing an Operating Workstation, skip to Installing the
ProcessLogix Client Software on page 5-21.
1 . Click OK to acknowledge the change directory warning.
2. At the PsAxCtl Document EXE Setup Welcome window, click

OK.
3. Verify that the destination directory is
C:\Honeywell\TPS50\System\bin.
4. Click the large install button (PC icon).
5. At the Setup complete window, click OK.
Installing the ProcessLogix Client Software

1 . At the Welcome to ProcessLogix Server Setup window, click
Nex t.
2. At the Choose Setup Type window, click Pr ocessLogix Clien t
Softw ar e setup (laptop icon).
3. At the Choose ProcessLogix Client Software window, check the
appropriate checkboxes for your application. Click the box to
check or uncheck each component, or click Select All.
Station
HMIWeb Display Builder
Display Builder
Quick Builder
Microsoft Excel Data Exchange
Uncheck this selection if Microsoft Excel is not currently
installed on this PC.
5-22
Network API for Windows

ODBC Client
Standard Displays
System Shapes
OPC Server Connect
4. Click Nex t.
IMPORTANT
In Step 5 below, you MUST NOT change the

directory names from their defaults. If you do change
directory names, the ProcessLogix system may not
operate properly.
5. Click Nex t to accept the default directory for the Client

Software.
6. If the Directory Already Exists window opens, click Yes to
continue. Otherwise, continue with the next step.
7. If the Specify Microsoft Excel Directory window opens, click
Nex t. Otherwise, skip to step 9.
ATTENTION
Rockwell Automation recommends answering No to

the question:
Do you want Microsoft Excel Data Exchange to be
allowed to write to a ProcessLogix Server database?
Answering Yes enables the write option and it is
possible for anyone with access to the machine to
write to the Server database.
8. To disable the Microsoft Excel Data Exchange write option, click

No in response to the question:
Do you want Microsoft Excel Data Exchange to be allowed to
write to a ProcessLogix Server database?
9. Click Nex t to accept ProcessLogix Client Software as the default
Program Folder for the Client software.
1 0. Review the software installation details summarized in the
Confirmation window.
If you need to make changes, click Back to access any
previous entries.
If the details are okay, click Nex t to begin the Client
Software setup. This may take 10 to 15 minutes to complete.
5-23
1 1 . If the system includes Excel Data Exchange, click En able

Macr os. Otherwise, continue with the next step.
TIP
If a Microsoft Excel dialog box opens, check the Do

n ot sh ow th is dialog again checkbox and click
OK.
ATTENTION
In the next step, ignore the prompt to remove any

disks. The CD must remain in the CD-ROM drive.
You must select No in Step 12.
1 2. At the Setup Complete window, click the No, I w ill r estar t my

If you are installing an Engineering Workstation, wait until after
the command windows have closed and file copying is
complete. This may take a few minutes to complete.
1 3. At the ProcessLogix Setup Complete window, click the No, I
w ill r estar t my computer later option and click Fin ish .
Installing ProcessLogix Update

1 . Restart the PC.
the CD-ROM drive.
>D:(or your CD-ROM drive letter)\SP1\Server-Client\SETUP.EXE<
8. At the Destination Folder window, click Nex t.
5-24

required. This takes 5-10 minutes to complete. If a delay occurs
during install, verify that there are no hidden status messages
windows in the taskbar.
1 0. At the InstallShield Wizard Completed window, click Fin ish .
1 1 . Click Yes to restart the system.
1 2. Logon as ps_user.
1 3. If necessary, insert the ProcessLogix R510.0 Supplemental
Software CD into the CD-ROM drive.
1 5. Enter or Br ow se to the appropriate path:
Client Type
Pate
Engineering Workstation
>D:(or your CD-ROM drive letter)\Update\SETUP.EXE<
Operator Workstation
>D:(or your CD-ROM drive letter)\

OperUpdate\SETUP.EXE<

1 7. Click Nex t to install the ProcessLogix Update.
1 8. At the ProcessLogix Update Complete window, click Fin ish .
The ProcessLogix R510.0 Client Software installation is complete.
Transferring ProcessLogix
Data
5-25
Transferring Data to the R510.0 Client

1 . Logon to the R510.0 Client as ps_user.
2. Open Windows Explorer and confirm that the T: drive exists.
If the T: drive exists, close Windows Explorer and skip
to Transfer Data on page 5-25.
If the T: drive does not exist, close Windows Explorer and
continue with Remap the T: Drive on page 5-25.
Remap the T: Drive

4. Enter this command:
>cmd<
and click OK to open the DOS window.

currently logged on to STN01.)
and press <Enter>.
Transfer Data
9. Enter >xcopy T:\UpgradeData\*.* C:\UpgradeData /E<
and press <Enter>.
5-26
1 0. If necessary, enter >D< to specify that UpgradeData is a

directory.
1 1 . Delete the backup files from the remote PC.

The following items should be considered before you begin operating
your ProcessLogix Client.
Table 5.O Post-upgrade Considerations
Item
Post-upgrade
Custom Displays
If necessary, use Windows Explorer to create the

Copy backed up displays from the backup directory to
Custom displays may require modification for use in an
R510.0 system.
System Displays
You must reapply the documented changes to the new system

displays after the upgrade.
Station Menus
You must reapply the documented changes to the new Station

menus after the upgrade.
Localization
Station configuration file
You must reapply the changes to the new station.ini file after
the upgrade.
Station setup file
The new default setup file, default.stn, is configured as

static Station 1. If this is not correct, you must make the
appropriate changes via Stations Setup menu. See the
Configuration Guide for details.
Setting Up Station for more information.
Transferring ProcessLogix Data is complete.

Finalizing ProcessLogix
Client Installation
Changing Hosts File Entries

Complete the following steps to map computer names to respective
unique IP addresses.
1 . If necessary, logon as ps_user.
2. Use Notepad to view the Hosts file in the directory location:
5-27
C:\WINNT\SYSTEM32\DRIVERS\ETC.
ATTENTION
TIP
You must identify all Server computer names and

respective unique IP addresses in the Hosts file and
be sure they are resident on each ProcessLogix
Client.
Use the DOS command >IPCONFIG/ALL<, or access
TCP/IP Properties through the General tab in the
Local Area Connection Properties dialog box to
obtain IP addresses for all configured components.
The Hosts file includes a default IP address of

>127.0.0.1< for a localhost. Do not delete this default
entry from the Hosts file.
3. You must enter the desired computer names and respective

unique IP addresses on a separate line for each Server as shown
in the display above.
These names and addresses must be included in the Hosts file
and resident on each Server and Client.
5-28
Use the following format to make your separate line entries into
this file.
<IP Address> <Computer Name> <Computer Name0> <Comment>
<IP Address> <Computer Name1>
Where:
is:
IP Address
the assigned internet address with no leading zeros. For example, a

typical address could be >192.168.0.1<.
Computer Name
a base name of up to 13 characters, which must be the same for each

ProcessLogix Server in the system.
In a redundant Server system, you must append a letter to the
base name to identify the PCs function in the system architecture
with the letters a and b for the Primary and Secondary Servers,
respectively.
For example, if you have a redundant Server system and you assign a
base name of PLX1, the Computer Name for the Primary Server and
Secondary Engineering Repository Database (ERDB) would be
>PLX1A<, the Secondary Server and Primary ERDB would be
>PLX1B<.
Computer Name0 the computer name appended with a 0 to show its association with
the first Ethernet adapter card.
the second Ethernet adapter card (in a dual Local Area Network (LAN)
system).
For example, if you have a redundant Server system with a dual LAN
and a base computer name of >PLX1<, the Computer Names would be
>PLX1A0<, >PLX1B0<, and >PLX1A1<, >PLX1B1< for their respective
addresses. If you have a single LAN system, you only need to append
the Computer Name with a 0.
Comment
any additional descriptive data you want to include for a given

Computer Name.
You must begin each entry with the number symbol >#<.
An example of a Host file with additional Host name entries and
comments is shown above for reference.
4. Click File Ex it and click Yes to save the Hosts file.

5. Repeat steps 14 for each Client in your system.
5-29
Station Setup
Setting Up a Station With a Non-redundant Server
If you are setting up Station with a redundant Server pair, refer to Setting
Up a Station With a Redundant Server Pair on page 5-31.
TIP
You must define the appropriate Station items in

Quick Builder on the Server in order for the Client
Station to connect.
Configuration Guide Configuration Tutorial
Defining a Station for more information.
Complete the following steps to set up the ProcessLogix Client to

access data in a networked ProcessLogix non-redundant Server.
1 . On the Server, click Star t Pr ogr ams Pr ocessLogix
Ser ver Star t-Stop Pr ocessLogix Ser ver to call up the
ProcessLogix Server dialog box. Verify that the Server is running
and close the dialog box.
OR
5-30
2. On the Client, click Star t Pr ogr ams Pr ocessLogix Clien t

Softw ar e Station .
3. Click Can cel at the Unable to connect prompt, if applicable.
4. Click Station Con n ect to call up the Station Connect dialog
box.
5. Select Default and click Edit Con n ection .
6. On the Connection tab:
a. Enter the name or IP address of the non-redundant Server
(PLX1 ) in the Server field.
PLX1 is the factory default Server name. It is used for
example purposes only.
b. Select the appropriate station type, Static Station or Rotary
Station.
c. Click Advan ced.
d. Enter the appropriate Static Station Number or enter the
appropriate update rates and startup display number for
Rotary.
7. On the Displays tab, check the Sear ch subdir ector ies for
sh apes checkbox.
8. Edit the Search for displays in list so that it includes the
following directories on ly:
C:\honeywell\client\system\r500
C:\honeywell\client\abstract
C:\honeywell\client\dspbld
a. To delete a directory, select it and click Remove.
b. To add a directory, click Add, click
and click OK.
TIP
, select the directory,
Display Sear ch Path Optimization

You can improve Stations performance by
unchecking the Search subdirectories for shapes
checkbox in the Connection Properties dialog box,
and then explicitly defining each subdirectory that
contains displays.
9. Click Save.
1 0. Click Yes to save changes.
1 1 . Click Con n ect.
5-31
1 2. Click Can cel at the Unable to connect prompt, if applicable.

1 3. Click Station Ex it.
1 4. Click Yes to exit Station.
Setting Up a Station With a Redundant Server Pair

If you are setting up Station with a non-redundant Server, refer
to Setting Up a Station With a Non-redundant Server on page 5-29.
TIP
You must define the appropriate Station items in

Quick Builder on the Server in order for the Client
Station to connect.
Configuration Guide Configuration Tutorial
Defining a Station for more information.
Complete the following steps to set up the ProcessLogix Client to

access data in networked ProcessLogix redundant Server.
1 . On SERVERB, click Star t Pr ogr ams Pr ocessLogix
ProcessLogix Server dialog box. Verify that the Server is running
and close the dialog box.
OR
2. Repeat Step 1 on SERVERA to verify that the ProcessLogix

Server is also running on this node.
3. On the Client, click Star t Pr ogr ams Pr ocessLogix Clien t
Softw ar e Station .
box.
6. Click New Con n ection .
5-32
7. On the Connection tab, make these entries to have the Station

point to SERVERB (PLX1 B):
a. Enter the name or IP address of SERVERB (PLX1 B) in the
Server field.
PLX1 B is the default Server name assigned by the factory. It is
used for example purposes only.
b. Select the appropriate Station type option, Static Station or
Rotary Station.
c. Click Advan ced.
Rotary.
e. Check the Aux iliar y setup file checkbox.
f. Click Br ow se and navigate to
C:\Honeywell\Client\Station\default.stn and click Open .
IMPORTANT
You must indicate the full path to the .stn file.
sh apes checkbox.
and click OK.
TIP

contains displays.
1 0. Click Save.
1 1 . Click Yes to save the new connection.
1 2. Enter >defaultb.stn< in the File name field and click Save.
1 3. Select defaultb and click Con n ect.
5-33

1 5. Click Station Con n ect to call up the Station Connect dialog
box.
1 6. Select Default and click Edit Con n ection .
1 7. On the Connection tab, make these entries to have the Station
point to SERVERA (PLX1 A):
a. Enter the name or IP address of SERVERA (PLX1 A) specified
in the Hosts file in the Server field.
PLX1 A is the default Server name assigned by the factory. It
is used for example purposes only.
b. Select the appropriate Station type option, Static Station or
Rotary Station.
c. If necessary, click Advan ced.
Rotary.
e. Check the Aux iliar y setup file checkbox.
f. Click Br ow se and navigate to
C:\Honeywell\Client\Station\defaultb.stn and click Open .
IMPORTANT
1 8. On the Displays tab, check the Sear ch subdir ector ies for
sh apes checkbox.
1 9. Edit the Search for displays in list so that it includes the
and click OK.
TIP

contains displays.
5-34
20. Click Save.

21 . Click Yes to save changes.
22. Select Default and click Con n ect.
24. If you have redundant LANs, you must repeat Step 3 through
Step 23 to set up files for the second LAN using the name or IP
address of SERVERA and SERVERB specified in the Hosts file
for the second LAN.
Configuration Guide Configuring and Monitoring a
Redundant Server System Configuring Stations for Server
Redundancy Dual Network Configuration for more
information.
25. Click Station Ex it.
26. Click Yes to exit Station.

Refer to Creating Emergency Repair Disks on page 2-40.

This procedure is required for an Engineering Workstation only. Use
the following general procedure to log on and check Control Builder
operation on a ProcessLogix Engineering Workstation.
Con tr ol Builder.
drop-down list.
3. Click OK.
Chapter
Additional Redundant Server Procedures
The following table lists the tasks you MUST complete in order to
complete the Additional Redundant Server Procedures.
Table 6.A Additional Redundant Server Procedures
Order
Task to Complete:
Refer to:
1.
Adding Redundancy to R510.0 Non-Redundant

Server Systems
6-2
2.
Completing the ProcessLogix R510.0 Setup on a

Redundant Server Pair
6-2
3.
Setting up Primary Server (SERVERA)
6-6
4.
Setting Up Secondary Server (SERVERB)
6-9
5.
Configuring Stations in Quick Builder (on SERVERA)
6-11
6.
Setting Up Station on SERVERA
6-12
7.
Setting Up Station on SERVERB
6-15
8.
Setting up the Redundant ERDB
6-18
9.
Restarting Redundant Servers
6-19
1 0.
Synchronizing Server Databases on Redundant

Server
6-20
11.
6-22
6-2
Adding Redundancy to
R510.0 Non-Redundant
Server Systems
If your Servers are already named A and B (SERVERA and SERVERB),

skip to Completing the ProcessLogix R510.0 Setup on a Redundant
Server Pair on page 6-2.
If you are adding Server redundancy to a non-redundant system,
designate an existing R510.0 non-redundant Server as SERVERA
(Primary). Designate the other Server as SERVERB (Secondary).
ATTENTION
Be certain that your process is off control before you

begin any upgrade procedure. This means the
1757-PLX52 should be in the Idle state.
Perform the following procedures on Primary (SERVERA) and

Secondary (SERVERB) Servers.
Changing the Computer Name on a ProcessLogix Server

Refer to Changing the Computer Name on a ProcessLogix Server on
page 8-16.
Completing the
ProcessLogix R510.0 Setup
on a Redundant Server Pair
Use the following procedures to configure a redundant server pair

after ProcessLogix R510.0 software has been installed. If you need to
install ProcessLogix R510.0 software, refer to Table 1.B on page 1-3.
ATTENTION

6-3
Changing Hosts File Entries

Complete the following steps to map computer names to respective
unique IP addresses on both Servers.
1 . Use Notepad to view the Hosts file in the directory location:
C:\WINNT\SYSTEM32\DRIVERS\ETC.
ATTENTION
To support redundant Servers (Primary/Secondary),

you must identify all computer names and respective
unique IP addresses in the Hosts file and be sure
they are resident on each ProcessLogix Client.
Use the DOS command >IPCONFIG/ALL<, or access
TCP/IP Properties through the General tab in the
Local Area Connection Properties dialog box to
obtain IP addresses for all configured components.
2. You must enter the desired computer names and respective

unique IP addresses on a separate line for each Server as shown
in the display above.
These names and addresses must be included in the Hosts file
and resident on each Server and Client.
6-4
Use the following format to make your separate line entries into
this file:
<IP Address> <Computer Name> <Computer Name0> <Comment>
<IP Address> <Computer Name1>
Where:
is:
IP Address
the assigned internet address with no leading zeros. For example, a

typical address could be >192.168.0.1<.
Computer Name
a base name of up to 13 characters, which must be the same for each

ProcessLogix Server in the system.
In a redundant Server system, you must append a letter to the
base name to identify the PCs function in the system architecture
with the letters a and b for the Primary and Secondary Servers,
respectively.
For example, if you have a redundant Server system and you assign a
base name of PLX1, the Computer Name for the Primary Server and
Secondary Engineering Repository Database (ERDB) would be
>PLX1A<, the Secondary Server and Primary ERDB would be >PLX1B<.
the first Ethernet adapter card.
the second Ethernet adapter card (in a dual Local Area Network (LAN)
system).
For example, if you have a redundant Server system with a dual LAN
and a base computer name of >PLX1<, the Computer Names would be
>PLX1A0<, >PLX1B0<, and >PLX1A1<, >PLX1B1< for their respective
addresses. If you have a single LAN system, you only need to append
the Computer Name with a 0.
Comment
any additional descriptive data you want to include for a given

Computer Name.
You must begin each entry with the number symbol >#<.
An example of a Host file with additional Host name entries and
comments is shown above for reference.
The Hosts file includes a default IP address of >127.0.0.1< for a
localhost. Do not delete this default entry from the Hosts file.
3. Click File Ex it and click Yes to save the Hosts file.

4. Repeat Step 1 to Step 3 for each Server in your system.
5. Use the PING command to determine if both Servers can
communicate with each other by name and IP address.
6-5
Changing TCP/IP address on a Secondary Server (SERVERB)

If you need to change the TCP/IP address on SERVERB to agree with
Hosts file entries, do the following:
1 . Click Star t Settin gs Con tr ol Pan el.
2. Double-click Netw or k an d Dial-up Con n ection s.
3. Right-click the Local Area Connection icon and select
Pr oper ties.
4. Select TCP/IP Pr otocol and click Pr oper ties.
5. Enter the TCP/IP address and appropriate Subnet mask.
TIP
Networked PCs must have unique addresses. For

example, if the address for SERVERA is 192.168.0.1,
you could change the SERVERB address to
192.168.0.2.
Changing the ProcessLogix License

If the license for redundant Servers has been installed, skip to Setting
up Primary Server (SERVERA) on page 6-6.
Perform the following procedure on Primary (SERVERA) and
Secondary (SERVERB) Servers.
1 . Click Star t Pr ogr ams Pr ocessLogix Ser ver Star t-Stop
box.
TIP
To display the Full Mode version of the ProcessLogix

Server dialog box, click the icon on the left of the
title bar and click Advan ced Full Mode.
A checkmark appears in front of the Full Mode
selection to show that it is active.
2. With the Full Mode version of the dialog box active, click the
Database On ly option.
its state.
6-6

5. Click Star t Pr ogr ams Pr ocessLogix Ser ver Setup.
7. Check the Ch an ge softw ar e licen se checkbox and click Nex t.
8. Enter the new System and Authorization numbers and click
Nex t.
9. Click Nex t to confirm.
1 0. If the license includes a new database size, click Yes in the
Rebuild Database dialog box.
1 1 . When completed, uncheck the Start ProcessLogix Server
Setting up Primary Server

(SERVERA)
ATTENTION
Failure to convert the existing Server to SERVERA

results in loss of configuration data. This requires
reconfiguring the system.
Use the following procedures to set up the Primary SERVERA.
6-7
Making Redundant Hardware File Entries

ProcessLogix Server dialog box. Verify that the Server is running.
Close the dialog box.
OR
2. On SERVERA, click Star t Pr ogr ams Pr ocessLogix

ProcessLogix Server dialog box.
TIP
To display the Full Mode version of the

ProcessLogix Server dialog box, click the icon to the
left of ProcessLogix in the title bar and click
Advan ced Full Mode. A checkmark appears in
front of the Full Mode selection to show that it is
active.
3. In Full Mode, if the Database Only is not selected, select it.

Otherwise, skip to step 6.
its state.
6. If you are you using a dual network (LAN) data link with your
redundant Servers continue with step 7.
Otherwise, skip to step 13.
7. Use Windows Explorer to locate the redun.hdw file in this
directory path:
C:\Honeywell\server\user
8. Double-click the redun.hdw file to open it in Notepad.
6-8
9. If you have redundant LANs, modify the file to include the

following entries for dual data links.
>DEL LNK00<
>ADD LNK00 NETWORK_LINK<
>DEL LNK01<
>ADD LNK01 NETWORK_LINK<
The default file definition is for a single network (LAN) data link
IMPORTANT
For information about the required operator actions

for the setup of fast failover, navigate in Knowledge
Builder to Server and Client Configuration Guide
Configuring and Monitoring a Redundant Server
System Server Redundancy Fast Failover
Configuration topic for HOSTS file and redundant
hardware build details.
1 0. Click File Save to save your changes to the file.

1 1 . Close Notepad.
1 2. Close Windows Explorer.
1 4. Enter >cmd< and click OK to open the DOS window.
1 5. At DOS prompt, enter >cd \Honeywell\server\user< and press
<Enter>.
1 6. Enter >hdwbld redun.hdw< and press <Enter>.
The hdwbld utility reads the text file [redun.hdw] and adds the
hardware definitions to the Server database.
If you are using a dual LAN, be certain that you change the
default redun.hdw file as noted in Step 7 to Step 12.
1 7. Verify that no hardware build errors are listed. If errors are listed,
be sure the Server state is Database Only and retry.
1 8. Enter >exit< and press <Enter> to exit DOS.
6-9
Configuring the Time Service

1 . To set up the time service on SERVERA, complete the steps in
Knowledge Builder at ProcessLogix R500 Server and Client
Redundant Server System Synchronizing Date and Time on
the Servers.
2. Close Knowledge Builder.
Restarting ProcessLogix Services

1 . Click Star t Pr ogr ams Pr ocessLogix Ser ver Star t-Stop
box.
TIP
To display the Full Mode version of the

ProcessLogix Server dialog box, click the icon to the
left of ProcessLogix in the title bar and click
Advan ced Full Mode. A checkmark appears in
front of the Full Mode selection to show that it is
active.
2. With the Full Mode version of the dialog box active, click the
System Run n in g option.
its state.
Setting Up Secondary
Server (SERVERB)
Use the following procedures to set up the Secondary SERVERB.
Making Redundant Hardware File Entries

Refer to Making Redundant Hardware File Entries on page 6-7 and
repeat the procedures on SERVERB. Change the reference in Step 1
from SERVERB to SERVERA and in Step 2 from SERVERA to
SERVERB.
6-10
Configuring the Time Service

1 . To set up the time service on SERVERB, complete the steps in
Knowledge Builder at Server and Client Configuration Guide
Configuring and Monitoring Redundant Server System
Synchronizing Date and Time on the Servers.
2. Click Star t Pr ogr ams Pr ocessLogix Ser ver Star t-Stop
box.
Restarting ProcessLogix Services

1 . With the Full Mode version of the dialog box active, click the
System Running option.
its state.
Confirming Data Link is Available

1 . On SERVERA, click Star t Run .
3. At the DOS prompt, enter >dual_status< and press <Enter>.
4. The unsynchronized SERVERA data should be similar to this:
5. Verify that the data link is available.

6-11
6. On SERVERB, click Star t Run .

8. At the DOS prompt, enter >dual_status< and press <Enter>.
9. The unsynchronized SERVERB data should be similar to this:
1 0. Verify that the data link is available.
Configuring Stations in
Quick Builder (on
SERVERA)
1 . Click Star t Pr ogr ams Pr ocessLogix Ser ver Quick

Builder.
2. Select the New Pr oject option and click OK.
3. In the Save in drop-down list, select
C:\Hon eyw ell\clien t\qckbld.
4. Enter >Stations.qdb< in the File name field and click Save.
5. Wait for the Enable Components dialog box to open.
a. Under the System/License Details tab, click the down arrow
and select Pr ocessLogix - R500 from the Server drop-down
list.
b. Select the En able Compon en ts tab.
c. Click Un select All, then check Static Station and Ser ver.
d. Click OK.
e. A Quick Builder prompt stating that you have not selected
any devices appears. Click OK to continue.
6-12
f. Wait for Quick Builder to generate the file.

TIP
For information on how to add devices to the Quick

Builder project once the file is open, navigate in
Knowledge Builder to Quick Builder Guide
Working with Projects Enabling and Disabling
Components.
6. Click Edit Add Items to call up the Add Item(s) dialog box.
7. Select Station in the Add items drop-down list.
8. Select Static Station .
9. Increase the number in the Number of items to Add field to
equal the number of connected Stations. Each Server counts as a
Station.
1 0. Enter the desired Use name or Prefix for multiple Stations. (For
example, use STN as the prefix with a numeric variable and
starting with the number 0. If the number of Stations to be
added is three, three Stations named STN0, STN1, and STN2 are
added.)
1 1 . Click OK to add the items to the project.
1 2. Click Tools Dow n load to call up the dialog box.
1 3. Click the All Items Relevan t to Selected Ser ver option.
1 4. Verify that one Server and at least two Static Stations are listed in
the summary.
1 5. Click OK to initiate the download.
1 6. Click OK to acknowledge the successful download prompt and
close the dialog box.
1 7. Click File Ex it to close Quick Builder.
Setting Up Station on
SERVERA
1 . On SERVERA, click Star t Pr ogr am s Pr ocessLogix

Ser ver Station .
box.
6-13

a. In the Server field, enter or Br ow se to the Secondary Server
name, SERVERB.
b. Select the Station type as Static Station .
c. Enter >1< as the Static Station Number and click Advan ced.
d. Check the Aux iliar y setup file checkbox.
e. Click Br ow se and navigate to:
IMPORTANT
sh apes checkbox.
6-14

and click OK.
TIP

contains displays.
8. Click Save.
9. Click Yes to save the new connection.
1 1 . Select defaultb and click Con n ect.
box.
a. In the Server field, enter or Br ow se to the Primary Server
name SERVERA.
IMPORTANT
1 6. Click Save.
1 8. Select Default and click Con n ect.
6-15
for the second LAN.
information.
21 . Click Station Ex it.
Setting Up Station on
SERVERB

Ser ver Station .
box.
a. In the Server field, enter or Br ow se to the Secondary Server
name, SERVERB.
IMPORTANT
6-16
sh apes checkbox.
and click OK.
TIP

contains displays.
8. Click Save.
9. Click Yes to save the new connection.
1 1 . Select defaultb and click Con n ect.
6-17

box.
a. In the Server field, enter or Br ow se to the Primary Server
name, SERVERA.
c. Enter >2< as the Static Station Number and click Advanced.
IMPORTANT
1 6. Click Save.
1 8. Select Default and click Con n ect.
for the second LAN.
information.
21 . Click Station Ex it.
6-18
Setting up the Redundant

ERDB
Complete the following steps on SERVERB only:

1 . Open Station.
2. Click the Oper field in the lower right corner of the display
4. Click Con figur e Oper ator Oper ator s.
7. Enter the New Password, Confirm the New Password and click
OK.
zone. If it does not repeat steps 6 and 7.
Only systems using operator based security and Control Builder
are affected by this change. The mngr operator account is
different than the Windows mngr user account. Navigate in
Knowledge Builder to Administration and Startup Guide for
more information before changing the password of the
Windows mngr user account.
DB Adm in .
9. Click the
+ sign to expand DbAdmin.
1 0. In the Login dialog box, make these entries:

c. Enter SERVERB in the Server Name field.
drop-down list.
1 1 . Click OK.
1 2. Click the
+ sign to expand the ProcessLogix Node.
1 3. Click Admin Tasks.

1 4. Click Disable Replication .
6-19
1 5. Click OK at the Disabled Database Replication prompt.

If this is the first time setting up the redundant ERDB, replication
is not yet enabled and you will receive a Failed to Disable
message. This is expected, click OK.
1 6. Click Recover Secondary Database.
a. Click Yes to recover Secondary Database.
b. Click OK at the Successfully Recovered Secondary Database
prompt.
1 7. Click Enable Replication.
a. Click Yes to proceed.
b. Click OK at the Successfully Enabled Database Replication
prompt.
1 8. Close DBAdmin.
Restarting Redundant
Servers
ATTENTION
The following procedure assumes that you have

completed all previous procedures in this chapter.
Complete the following steps to restart SERVERA and then SERVERB.

1 . Restart SERVERA.
2. Logon to SERVERA as ps_user.
3. On SERVERA, right-click in the taskbar to open the popup
menu and click Task Man ager to call up the Windows Task
Manager dialog box.
4. On the Performance tab, monitor the CPU Usage until the value
displayed goes below the 90100% threshold.
Wait until the RSLinx icon appears in the taskbar. This assures
proper startup time of ProcessLogix services on SERVERA
before restarting SERVERB.
5. Click File Ex it Task Man ager.
6. Restart SERVERB.
6-20
7. Logon to SERVERB as ps_user.
Synchronizing Server
Databases on Redundant
Server
1 . On SERVERA, click Star t Pr ogr am s Pr ocessLogix

Ser ver Station .
2. Click View System Status Ser ver Redun dan cy.
The Primary Server and Backup Server should be running and at
least one link is OK. If this is not the case, review the prior
redundancy configuration steps before continuing.
4. Enter >mngr< in the Station Logon dialog box and click OK.
5. Click Syn ch r on ize.
6. When the Synchronize Databases (Y/N) prompt appears, enter
>Y< in the entry field above the display and press <Enter>.
Depending on your configuration, this may take some time to
complete.
7. Once the Synchronization Complete prompt appears, verify that
the display shows simulated Green LED indications for the
following states:
LED(s)
State(s)
Primary Server
Running
Backup Server
Synchronized
Running
Link Status
Link 0 (LNK00) - OK Active link

Link 1 (LNK01) - OK (Only applies if you are using a dual LAN)
8. Click Station Ex it.

Confirming Databases are Synchronized

1 . On SERVERA, click Star t Run .
6-21
3. At the DOS prompt, enter this command:

>dual_status<
and press <Enter>.
4. The synchronized SERVERA data should be similar to this:
5. Verify that the link is active and the databases are synchronized.
6. On SERVERB, click Star t Run .
8. At the DOS prompt, enter this command:
>dual_status<
and press <Enter>.
9. The synchronized SERVERB data should be similar to this:
1 0. Verify that the link is active and the databases are synchronized.
6-22
Synchronizing Other Files

The Primary SERVERA automatically transfers ProcessLogix Server
database information to the Secondary SERVERB. This transfer
includes any changes in configuration data, such as points and
displays.
Navigate in Knowledge Builder to Server and Client Configuration
Guide Configuring and Monitoring a Redundant Server System
Synchronizing Other Files for more information.
If you previously configured the flbkup.def file for an earlier release,
you MUST re-configure it for R510.0.
Upgrading Hardware
Component Firmware
1 . Refer to Loading 1757-PLX52, TC-MUX021, or 1757-FIM Boot

IMPORTANT
Stop! It is mandatory that you check the firmware

installation and/or a component addition or
replacement.
firmware. Then continue with the next section.

Complete the following general steps to log on and check Control
Builder operation on a ProcessLogix Engineering Workstation.
Con tr ol Builder.
b. Enter the appropriate password.
c. Enter the appropriate Server Name in the Server Name field.
drop-down list.
6-23
3. Click OK.

any user files you create. Refer to Backing Up a ProcessLogix Server
Hard Drive to Tape on page 6-23.
Creating an Emergency Repair Disk

After all installations and drivers are installed, you should now create
your Emergency Repair Disk. Use the following procedure to create
an emergency repair disk for your Windows 2000 Server installation.
1 . Insert a blank diskette into the floppy drive.
Backup.
3. Click Emergency Repair Disk.
6. Repeat Steps 1 through 5 with another blank formatted diskette.
7. Click Job Ex it.
6-24
Chapter
Firmware Maintenance Procedures
1784-PCIC Driver
Installation
If you are using ControlNet for your Supervisory Network, you must
have a 1784-PCIC card installed in each Server. Refer to the 1784-PCIC
Installation Instructions, Publication 1784-IN003. If you have not yet
configured your 1784-PCIC card device drivers, a Found New
Hardware Wizard opens after each restart.
Install Hardware Device Drivers

1 . Restart the PC.
3. If the Found New Hardware Wizard opens, skip to step 8. If the
Found New Hardware Wizard does not open, continue with the
next step.
5. Select Device Man ager.
6. Under Other Devices, right-click the PCI device and select
Pr oper ties.
7. On the Driver tab, click Update Dr iver.
8. Click Nex t.
9. Select the Sear ch for a suitable dr iver option and click Nex t.
1 0. Uncheck the Floppy disk drives and the CD-ROM drives
checkboxes.
1 1 . Check only the Specify a location checkbox and click Nex t.
1 2. Insert the ProcessLogix R510.0 Application Software CD into the
CD-ROM drive.
7-2
1 3. Enter this path location in the Copy manufacturers file from

field or Br ow se to:
>D:(or your CD-ROM drive letter)\RSLinx\RSLinx\PnP_Drivers\
Win2K\1784-PCIC(S)\abvbp2k.inf<
1 4. Click OK.
1 5. Click Nex t to install the driver.
1 6. If a Digital Signature Not Found window opens, click Yes.
1 7. If necessary, click Yes to overwrite the VirtualBackplane.sys file.
1 8. If necessary, click Yes to overwrite the ABPCICSW.sys file.
1 9. Click Fin ish .
20. Click Close.
Verify the 1784-PCIC Driver Version

1 . If necessary, right-click the My Computer icon and select
Man age.
2. If necessary, select Device Man ager.
3. If the A-B Virtual Backplane icon exists, expand A-B Virtual
Backplane.
4. Double-click A-B 1784-PCIC(S).
5. If AB 1784-PCIC(S) is not present, you need to install the
Hardware Device Drivers. Restart the PC and refer to Install
Hardware Device Drivers on page 7-1.
6. On the Driver Tab click Dr iver Details.
7. Select ABPCICW.sys.
The ABPCICSW.sys file version should be 3.6.18 WDM.
8. Select Vir tual Backplan e.sys.
The VirtualBackplane.sys file version should be 1.9.
9. Click OK to close the Driver File Details window.
1 0. Click OK to close the AB 1784-PCIC(S) Properties window.
7-3
1 1 . Close the Computer Management window.

1784-PCIC Driver Installation is complete.
1784-PCIC Firmware
Installation
If your 1784-PCIC firmware has not been updated for ProcessLogix

R510.0, this procedure must be followed to use the 1784-PCIC in
R510.0.
IMPORTANT
You must have the 1784-PCIC configured in RSLinx.

Refer to Configuring RSLinx Drivers for ControlNet
Supervisory Network on page 3-16 to configure the
1784-PCIC drivers in RSLinx.

continue with the following steps starting with at Step 6.
2. Enter >ntools -c -u<.

6. Click the desired PCIC icon under the Desktop tree and wait for
the card details to appear in the Detail pane.
7. Check the firmware revision shown in the Name field.
If the firmware is 3.7.39, you do not need to update the
firmware.
If the firmware is not 3.7.39 go to Step 8.
7-4
1 0. Navigate to the directory:

C:\Honeywell\TPS50\System\Firmware\1784-PCIC\3_7_39
1 1 . Select 9941 7807.n vs.
1 2. Click Open to start the firmware load and click Yes to confirm.
1 3. Wait for the load to complete. The Status field in the lower
portion of the Network Tools window tracks the load progress.
1 4. Click OK to acknowledge the load completion with no errors.
1 5. Close NTools.
Upgrading Hardware
Component Firmware
ATTENTION

About Firmware Upgrades

Each ProcessLogix software version release includes files for updating
the firmware version in system hardware components to levels
compatible with the given release. This means you must use the
ProcessLogix Engineering Tools utility called Network Tools
(NTOOLS) to check that the firmware versions for the hardware in
your network are compatible and to upgrade them as required before
initiating control operations.
If this is the first time you have used Network Tools on this PC, refer
to Making First Time Network Tools Settings on page 8-10.
After a ProcessLogix Server upgrade, you must always upgrade the
firmware in the Control Processor module (1757-PLX52) and the Serial
7-5
Interface module (TC-MUX021) to match the current ProcessLogix

software version before you can download a control strategy.
IMPORTANT
Firmware Revision Level

Reference
Firmware versions for these modules are not

qualified for backward compatibility. For example, if
you try to use a 1757-PLX52 with a firmware version
that is compatible with R510.0 with a Server running
software version R300.1, the control and operation of
the system is not guaranteed.
The following table lists the firmware revision levels for listed
components that are current for R510.0 along with the directory
locations for firmware upgrade files.
ATTENTION
This release of ProcessLogix supports only the

firmware versions listed in Table 7.A. When installing
new systems or repairing existing systems, you must
ensure that all modules meet the firmware version
requirements listed in Table 7.A.
Table 7.A Hardware component firmware revision level reference for R510.0
Component Name
Model Number
Revision Level
for R510.0
Directory
File
Process Controller
Module
1757-PLX52
(redundantcompliant)
AV 500.1-01.1
BV 500.1-01.1
C:\Honeywell\tps50\system\bin
Cee5.pcm
Cee50.pcm
Cpmboot.pcm
Serial Interface
Module (SIM)
TC-MUX021
AV 500.1-01.1
BV 500.1-01.1
C:\Honeywell\tps50\system\bin
Simboot.pcm
simrex.pcm
Use this base directory path to locate the firmware directories and files for the following modules:
C:\Honeywell\tps50\system\firmware
Redundancy
Module (RM)
1757-SRM
AV 3.29
BV 3.2
\1757-SRM\3_29
99450209.nvs
7-6
Component Name
Model Number
Revision Level
for R510.0
Directory
File
ControlNet Bridge
module (CNB)
1756-CNB/B
(single media)
1756-CNBR/B
(dual media)
2.27
CNB\1756-CNB(R)-B\2_27
99422005.nvs
1756-CNB/C
(single media)
1756-CNBR/C
(dual media)
4.24
CNB\1756-CNB(R)-C\4_24
99404317.nvs
1756-CNB/D
(single media)
1756-CNBR/D
(dual media)
5.38
CNB\1756-CNB(R)-D\5_38
99415527.nvs
FLEX Ex ControlNet
Adapter
1797-ACNR15
(redundant media)
4.2
\1797-ACN(R)15\4_2
99423302.nvs
FLEX IO ControlNet
Adapter
1794-ACN15/C
(single media)
1794-ACNR15/C
(redundant media)
3.5
\1794-ACN(R)15\3_5
99423302.nvs
ControlNet PCI
Interface card
1784-PCIC
3.7.39
\1784-PCIC\3_7_39
99417807.nvs
ControlNet to
Fieldbus Linking
Device
1788-CN2FF
1.4
\1788-CN2FF\1_4
99454401.nvs
FOUNDATION
Fieldbus Interface
Module
1757-FIM
AV 4.3
BV 4.3
\1757-FIM
FimBoot.nvs
Fimrex.nvs
PROFIBUS Interface
Module
SST-PFB-CLX
3.12
N/A
N/A
Ethernet TCPIP
Communication
Interface Cards
1756-ENET/A
1.18
\Ethernet\1756-ENET-A\1_18
99236106.nvs
1756-ENET/B
2.7
\Ethernet\1756-ENET-B\2_7
99440202.nvs
1757-ENBT/A
1.61
\Ethernet\1756-ENBT-A\1_61
99437005.nvs
ABRIO
Allen-Bradley
Remote I/O
Interface Module
1757-ABRIO
1.2
\1757-ABRIO\1_2_11
*Refer to Updating Firmware in the
1757-ABRIO Module on page 7-17
57ABRIO.nvs
DeviceNet Interface
Module
1756-DNB
4.002
\1756-DNB\4_002
99403613.nvs
Pulse Input Module
1757-PIM
AV 1.9
BV 1.1
\IOM\1757-PIM\1_9
pim.nvs
7-7
Component Name
Model Number
Revision Level
for R510.0
Directory
File
Analog I/O
Modules
1756-IF6I/A
1.9
\IOM\Analog\1756_analog\1_9
99207408.nvs
1756-IF16/A
1.5
\IOM\Analog\1756_IF16\1_5
99223504.nvs
1756-IR6I/A
1.9
99207408.nvs
1756-IT6I/A
1.9
99207408.nvs
1756-OF6CI/A
1.9
99207408.nvs
1756-OF6VI/A
1.9
99207408.nvs
1756-OF8/A
1.5
\IOM\Analog\1756_OF8\1_5
99223704.nvs
1756-IA16/A
2.4
IOM\Digital\1756-IA16\2_4
99213204.nvs
1756-IB16/A
2.4
IOM\Digital\1756-IB16\2_4
99212904.nvs
1756-IB32/A
2.6
IOM\Digital\1756-IB32\2_6
99207106.nvs
1756-IB16I/A(1)
(ASIC ver. 2.1)
1.7
IOM\Digital\1756-IB16I\1_7
99205106.nvs
(ASIC ver. 2.2)
2.1
IOM\Digital\1756-IB16I\2_1
99218601.nvs
1756-IA16I/A
(ASIC ver. 2.1)
1.7
IOM\Digital\1756-IA16I\1_7
99205306.nvs
(ASIC ver. 2.2)
2.1
IOM\Digital\1756-IA16I\2_1
99218401.nvs
1756-IM16I/A
(ASIC ver. 2.1)
1.7
IOM\Digital\1756-IM16I\1_7
99204006.nvs
(ASIC ver. 2.2)
2.1
IOM\Digital\1756-IM16I\2_1
99219801.nvs
1756-IA8D/A
2.5
\IOM\Digital\1756-IA8D\2_5
99218804.nvs
1756-IB16D/A
2.5
\IOM\Digital\1756-IB16D\2_5
99219004.nvs
1756-OA16/A
2.3
\IOM\Digital\1756-OA16\2_3
99216503.nvs
1756-OB32/A
2.4
\IOM\Digital\1756-OB32\2_4
99207203.nvs
1756-OB16I/A
(ASIC ver. 2.1)
1.7
\IOM\Digital\1756-OB16I\1_7
99205006.nvs
(ASIC ver. 2.2)
2.1
\IOM\Digital\1756-OB16I\2_1
99218701.nvs
1756-OA16I/A
(ASIC ver. 2.1)
1.7
\IOM\Digital\1756-OA16I\1_7
99205206.nvs
(ASIC ver. 2.2)
2.1
\IOM\Digital\1756-OA16I\2_1
99218501.nvs
1756-OA8D/A
2.4
\IOM\Digital\1756-OA8D\2_4
99218903.nvs
1756-OB16D/A
2.3
\IOM\Digital\1756-OB16D\2_3
99219102.nvs
Digital I/O Modules
(1)
Use extreme caution when flashing these modules. Flashing with the wrong version will render the module inoperable. If uncertain of the modules hardware version,
contact Technical Support.
7-8
Important Usage Considerations

Be certain that you keep the following considerations in mind when
you are doing a firmware update.
If you are updating a 1784-PCIC card, your PC will be blind to
all modules.
If you get a Warning: Use Extreme Care dialog box during the
course of an update, confirm that the correct .nvs file is selected.
See Table 7.A on page 7-5.
Be certain that you carefully read all the dialog boxes presented
during the course of a given firmware update.

continue with the following steps, starting at Step 5.
a. For ControlNet Supervisory Networks, enter >ntools -c -u<.
b. For Ethernet Supervisory Networks, enter >ntools -e -u<.
7-9
Loading 1757-PLX52, TC-MUX021, or 1757-FIM Boot and

Personality Images
Use the following procedures to update the ROM boot code and
personality images in an existing 1757-PLX52, TC-MUX021 or
1757-FIM module. You must repeat these procedures for all
1757-PLX52, TC-MUX021 and 1757-FIM modules in your system.
ATTENTION

Table 7.B Special Considerations when Loading 1757-PLX52, TC-MUX021, or 1757-FIM
Boot and Personality Images
Description
Upgrading the 1757-PLX52 from

R300.0 to R510.0
When upgrading the firmware from R300.0 to the R510.0 firmware, the CPM will not reset after
the flash is completed. The module will display wait on the module LED for an extended period of
time.
Please follow these steps when upgrading a 1757-PLX52 from CPM300-xx.x to PS500.1-01.1:
1. When you receive a new 1757-PLX52 and are ready to update its firmware, check the
firmware revision in NTools. If the boot code is not CPM300.3-xx.x you will not be affected
by this defect.
2. Flash the 1757-PLX52 with the new boot firmware. The 4-character LED display should
transition from:
ALIV to LOAD to wait
The wait text indicates that the CPM is writing the new boot image to flash. After the image is
written, the CPM will usually restart. If the CPM doesnt restart and continues to display wait for
10 minutes or more, then manually cycle power to the module. Wait at least 10 minutes to ensure
that the new boot image was written successfully.
Redundant Chassis Firmware

Upgrade Precautions
When updating 1757-PLX52 modules in a Redundant Chassis Pair (RCP), you must turn OFF power
to the Secondary Chassis in the RCP, so you can update the firmware in the 1757-PLX52 in the
powered controller chassis while it is in a Primary with no partner state.
Once the 1757-PLX52 module is updated in the powered chassis, turn OFF power to this chassis
and turn ON power to the other controller chassis to repeat the firmware update for the other
1757-PLX52 in the RCP. This avoids possible confusion caused by the logical change in Network
Addresses in response to a controller switchover.
FIMs and Fieldbus Devices Reload

after Upgrade
After updating firmware for all FIMs, all FF devices and all associated Control Modules must be
reloaded, even if the FF devices were allowed to continue independent operation during the
ProcessLogix upgrade. This is to permit the FIM to view and save interface information that it may
need for proper interface operation.
7-10
Loading Boot Image

TIP
The devices with non-compatible versions of

firmware display their firmware versions in red.
Devices with the correct version of firmware display
their firmware version in green. Unknown devices
are displayed in yellow.
1 . Start NTools.
2. Click the desired CNB or ENET icon under the desktop tree and
wait for the graphic of the chassis to appear in the detail pane.
3. Click the 1757-PLX52, TC-MUX021, or 1757-FIM module in the
graphic of the chassis configuration in the Detail pane. If
required, select another CNB icon to find the chassis that
contains a 1757-PLX52, TC-MUX021, or 1757-FIM module.

6. If the LED on the 1757-PLX52, TC-MUX021, or 1757-FIM module
is not in its Ready (RDY) state, click Yes to issue a Stop
(Shutdown) command to the module and wait for the module to
reboot to its RDY state as shown in the module LED display.
Otherwise, continue with step 7.
7-11
7. To load the boot image to a 1757-PLX52, TC-MUX021, or

1757-FIM, locate the appropriate boot file. See Table 7.C, below.
Table 7.C Boot Image Reference for R510.0
Model Number
Directory
File
1757-PLX52
C:\Honeywell\TPS50\system\bin
cpmboot.pcm
TC-MUX021
simboot.pcm
1757-FIM
C:\Honeywell\TSP50\system\Firmware\1757-FIM
Fimboot.pcm
This example illustrates loading boot image to a 1757-PLX52.
8. Select the appropriate file.

9. Click Open to start the firmware load and click Yes to confirm
the action.
1 0. Wait for the load to complete and the 1757-PLX52, TC-MUX021,
or 1757-FIM module to reboot to its ALIVE status as shown in
the module LED display. The Status field in the lower portion of
the Network Tools window tracks the load progress.
1 1 . Click OK to acknowledge the load completion with no errors.
7-12
Loading Application Image

1 . With the 1757-PLX52, TC-MUX021, or 1757-FIM module in its
ALIVE state, click the 1757-PLX52, TC-MUX021, or 1757-FIM
module in the Detail pane.

4. To load the application image to a 1757-PLX52, TC-MUX021, or
1757-FIM, locate the appropriate application file. See Table 7.D,
below.
Table 7.D Application Image Reference for R510.0
Model Number
Directory
File
1757-PLX52
CEE-50ms
cee50.pcm
1757-PLX52
CEE-5ms
cee5.pcm
TC-MUX021
simrex.pcm
1757-FIM
C:\Honeywell\TSP50\system\Firmware\1757-FIM Fimrex.pcm
This example illustrates loading the personality image to a

1757-PLX52 for CEE-50ms.
5. Select the appropriate file.
7-13
6. Click Open to start the firmware load and click Yes to confirm
the action.
7. Wait for the load to complete and the 1757-PLX52, TC-MUX021,
or 1757-FIM module to reboot to its NODB status as shown in
the module LED display. The Status field in the lower portion of
the Network Tools window tracks the load progress.
8. Click OK to acknowledge the load completion with no errors.
9. Repeat the procedures in the Sections entitled Loading boot
image and Loading personality image for other 1757-PLX52,
TC-MUX021, or 1757-FIM modules in your network, as required.
Be sure to update the partner 1757-PLX52 module in an RCP
system configuration.
1 0. Click Netw or k Tools Ex it to close the application. Continue
with other firmware upgrades as applicable in the next Section
or return to upgrade or installation procedures as applicable.
Updating Firmware in CNB, ENET, IOM, SRM, PIM

or ControlNet Adapter
ATTENTION
Redundant Chassis Firmware Upgrade

Precautions
When updating modules in an RCP, you MUST turn
OFF power to the Secondary Chassis in the RCP, so
you can update the firmware in the modules in the
powered controller chassis while it is in a Primary
with no partner state. Failure to remove power from
the Secondary Chassis may result in an
unrecoverable loss of the RM.
Once the modules are updated in the powered
chassis, turn OFF power to this chassis and turn ON
power to the other controller chassis to repeat the
firmware update for the other modules in the RCP.
This avoids possible confusion caused by the logical
change in Network Addresses in response to a
controller switchover.
Never cancel an RM firmware upgrade in process.
Interruption of an RM firmware upgrade during the
boot code load may result in an RM that will not
power up properly and that cannot be recovered by
power cycling the unit.
7-14
The procedure for updating the firmware in other modules is similar

to the one used for updating a 1784-PCIC card.
1 . Launch the NTOOLS utility (ntools -c -u or ntools -e -u).
refer to Starting Network Tools Application on page 7-8.
2. Click the desired CNB or ENET icon.
3. Select the module to be updated in the chassis graphic.
and click Yes to acknowledge
the warning.
5. Select the path to the correct .nvs file.
See Table 7.A on page 7-5.
6. Carefully follow the on-screen prompts to complete the update.
ATTENTION
Be certain that you select the correct .nvs update file

before you acknowledge any Warning prompt and
initiate a file download to a given module. See
Table 7.A on page 7-5.
Do n ot update more than one module of a given
type at a time. If the on-screen prompt includes a
selection for Update all other identical types in this
controller (only) now, be certain this selection is
n ot checked.
If you have added any new CNB modules to your network, adjust the
Network Update Time (NUT) in the new modules. Refer to Setting
CNB Module NUT Timing on page 7-15. Otherwise, return to upgrade
or installation procedures as applicable.
7-15
Setting CNB Module NUT Timing

Use the procedure in the following table to adjust the NUT (Network
Update Timing) timing of all the n ew CNB modules in your system.
ATTENTION
!
ATTENTION
You only need to adjust the NUT timing on n ew

CNB modules received from the factory. You can
skip this procedure if you have previously set the
NUT timing for all the CNB modules in your system.
The CNB modules must be on a ControlNet that is
plugged into a rack, cabled to the ControlNet, and
have unique MAC addresses in order to change their
ControlNet parameters (as listed in Step 10 on
page 7-16) The ControlNet parameters are updated
for all CNBs on the ControlNet at the same time.
If you are including a Foundation Fieldbus Linking
Device in your application, review the CNB
restrictions covered in the Linking Device
Implementation Guide in Knowledge Builder for
NUT timing data specific to Fieldbus applications.
1 . If this is the fir st time you have used Network Tools on this PC,
refer to Making First Time Network Tools Settings on page 8-10
and then complete the following steps, starting with Step 6.
3. Enter this command:
>ntools -c -pg<
TIP
If the RSLinx and PCIC driver services for system

communications in ControlNet mode are not
running, this command starts the services.
7-16

6. Click Resume
7. Click any CNB icon under the Desktop tree and wait for the
graphic of the chassis to appear in the Detail pane.
8. In the graphic of your chassis, click the CNB module with the
Network Address selected above.
TIP
This may be the only module that appears in the

chassis graphic at this time.
9. Click Change ControlNet

dialog box.
to call up the Keeper Values
1 0. Confirm that the values listed for the parameters under the
Changes Tab on the dialog box match the following settings and
enter new values, as required.
Be certain to adjust the Number of Repeaters, Cable Length, and
Fiber Optics settings to match your actual system configuration
when they differ from the suggested default values listed below.
TIP
The values listed below differ for applications that

include a Foundation Fieldbus Linking Device.
If you are including a Foundation Fieldbus Linking
Device in your application, review the CNB
restrictions covered in the Linking Device
Implementation Guide in Knowledge Builder for
NUT timing data specific to Fieldbus applications
NUT Time: 10000 uS (10 msec.)

Smax: 1
UMax: 24
Number of Repeaters: 0
Cable Length: 1000 (meters)
Cable Usage: A+B (for dual media cable configuration) or A
(for single media cable configuration)
Uncheck My System uses Fiber Optics.
7-17
1 1 . If you made no changes to dialog box values, click Can cel and
skip to Step 17. Otherwise, continue with the next step.
1 2. Click OK to enter new values.
1 3. Click Yes in response to confirmation messages.
1 4. Wait for the data transfer to be completed. Click OK to
acknowledge the completion of the update without errors
prompt.
1 5. Click OK to acknowledge any communication prompt messages
that appear.
1 6. Click the pause button
to halt the network scan.
1 7. If CNBs that reside on I/O networks are also to be updated, then

select one CNB from each I/O network for Step 8 and repeat
Step 9 through Step 15 for each I/O network.
1 8. Click Netw or k Tools Ex it to end the session.
1 9. Return to upgrade or installation procedures as applicable.
Updating Firmware in the 1757-ABRIO Module

Complete the following steps for updating the firmware in the
1757-ABRIO module.
1 . Logon to the Server as ps_user.
2. Insert the ProcessLogix R510.0 Supplemental CD.
>D:(or your CD-ROM drive letter)\ABRIO Control Flash\setup.exe<
5. Click OK.
6. At the Welcome to ControlFLASH Setup window, click Nex t.
7. Click Yes to accept the License Agreement.
8. Click Nex t to accept the default location.
9. Uncheck the Yes, I want to view the ControlFLASH readme file.
7-18
1 0. Check Yes, I w an t to laun ch Con tr olFLASH and click Fin ish .

1 1 . At the Welcome to ControlFLASH window, click Nex t.
1 2. Click 1757-ABRIO and click Nex t.
1 3. Expand RSLinx Tree window to the location of the 1757-ABRIO
module you wish to flash.
1 4. Select the module icon and click OK.
1 5. Confirm that the new revision for this update is 1.2 and click
Nex t.
1 6. At the Summary window, click Fin ish .
1 7. Click Yes to confirm the flash.
1 8. Click OK.
If this update is successful, the Update Status window displays
the following message in green: Update Complete. Please verify
this new firmware update before using the target device in its
intended application.
1 9. Click OK and then click Can cel at the Welcome to
ControlFLASH Setup window.
20. Click Yes to end the configuration session.
Chapter
Stopping ProcessLogix
Applications and Services
ATTENTION

applications and stop all ProcessLogix services.
This section describes how to stop ProcessLogix services in the

Windows 2000 system. Use the following procedure to exit all
ProcessLogix applications and stop all ProcessLogix services.
1 . Exit all running ProcessLogix applications, such as Control
Builder, Station, and Network Tools (NTOOLS).
3. Expand Ser vices an d Application s.
4. Select Ser vices.
TIP
To stop a ser vice:

If the service is present, right-click it and select Stop.
If prompted, click Yes to also stop other services. If a
service is already stopped, move on to the next one
in the list below.
5. Stop these Services in the following order:

a. ProcessLogix Server Daemon (also stops ProcessLogix Server
Operator Management and ProcessLogix Server System, if
applicable)
b. ProcessLogix Server Database
c. ProcessLogix Server Desktop
d. ProcessLogix Server Logger
e. Windows Management Instrumentation
f. ProcessLogix Control Data Access Server
g. ProcessLogix System Repository
h. ProcessLogix ER Server
i. RSLinx
j. XLNet Daemon
1
8-2
k. MSSQLServer (also stops SQLServerAgent)

6. Close the Computer Management window.
7. Right-click the SQL Server Service Manager icon
in the task
bar and select Ex it.

The application closes.
Stopping ProcessLogix Applications and Services is complete.
Installing Knowledge
Builder on a
Non-ProcessLogix System
Knowledge Builder is the software application used to display

ProcessLogix documentation. Knowledge Builder (KB) requires
several other software applications and Microsoft components to
function properly. These components are included on the Knowledge
Builder and Supplemental CDs.
Installing Knowledge Builder on Windows 2000

The following table lists the items that you must complete to install
Knowledge Builder on a Non-ProcessLogix Windows 2000 system.
Table 8.A Prerequisites to Installing Knowledge Builder on Windows 2000
Step
Item
Page
1.
Removing Knowledge Builder
8-3
2.
2-29
3.
2-33
4.
2-36
5.
8-4
8-3
Installing Knowledge Builder on Windows XP

The following table lists the items that you must complete to install
Knowledge Builder on a Non-ProcessLogix Windows XP system.
Table 8.B Prerequisites to Installing Knowledge Builder on Windows XP
Step
Item
Page
1.
8-3
2.
2-33
3.
8-4

Before installing ProcessLogix R510.0 Knowledge Builder, you must
remove any previous versions of Knowledge Builder.
Removing R320.0 or R400.0 SP2 Knowledge Builder

3. Select Kn ow ledge Builder in the list of installed programs and
click Add/Remove.
5. If necessary, at the Remove Shared File prompt, click Yes to All
and click Yes to confirm.
6. When completed, close the Add/Remove Pr ogr ams window.
8-4
Removing R500.1 Knowledge Builder

programs.
following order.
IMPORTANT

Remove all.
Table 8.C Removing R500.1 Knowledge Builder Components
Step
Item
1.
2.
KBServer - ProcessLogix R500
3.
KB Client
4.
Knowledge Builder (At the maintenance window, click Remove and

Next.

CD-ROM drive.
>D:(or your CD-ROM drive letter)\Knowledge_Builder\Setup.exe<
3. Click OK to launch the Knowledge Builder setup.
8-5

If Adobe Acrobat is already installed, the install will automatically
continue with refer to Installing Knowledge Builder Components,
below.
4. At the Acrobat Reader 4.05 Setup window, click Nex t.
6. Click OK.

7. At the Knowledge Builder - Welcome window, click Nex t.
9. Check the desired install type and click Nex t.
KB Full
Installs all KB components. Required on all

ProcessLogix Servers and Clients.
KB Clien t Installs the Client side components on a system. This

install requires that you have already completed a
KB Full install on a networked PC. During the KB
Client install you will need to change the install
location to the current location of the networked
Knowledge Builder files, and select the Docs folder.
KB CD
Installs the Client side components on your system.

You will be required to have the KB CD inserted
every time you run Knowledge Builder.
1 0. If installing Full, click Select All and click Nex t.

1 1 . At the Server selection window:
If installing Full, click Nex t to accept the default directory for
Knowledge Builder.
If installing Client, enter the Server name and location or
click Br ow se and select the appropriate Server location. For
example, the location of the Full version of KB might be
E:\Knowledge_Builder\Docs, where E:\ is a mapped drive to
C:\Program Files\Honeywell\PST_Server on PLX1A. (The
PST_Server folder on a KB FUll install is shared by default as
PSTServer.)
8-6
1 2. At the Start Copy window, click Nex t.

1 3. At the Installation Completed window, click Fin ish .
1 4. If installing Full, enter this path or Br ow se to:
>D:(or your CD-ROM drive letter)\Knowledge_Builder\KB_update.exe<
and click OK.
1 5. Remove the ProcessLogix R510.0 Knowledge Builder CD.
Launching ProcessLogix
Knowledge Builder
IMPORTANT
To view the online documentation called Knowledge

Builder, you need the Microsoft Internet Explorer 6.0
HTML browser installed on your PC.
You can call up Knowledge Builder through the Help menu in the
Control Builder application. Knowledge Builder can also be accessed
through the main Programs menu as follows:
1 . Click Star t Pr ogr ams Per for man ce Suppor t Tools
Kn ow ledge Builder to launch the application.
2. Once you launch Knowledge Builder, click Help
complete instructions.
for
SQL Server
8-7
SQL Server is automatically installed during the ProcessLogix R510.0

installation.
SQL Status
Follow these steps to check if SQL Server is running and to start it if
necessary.
1 . Right-click the My Computer icon and select Man age.
2. Expand Services and Applications.
3. Select Ser vices.
4. Scroll down to the service MSSQLSERVER and verify that it has
started.
If the MSSQLSERVER service did not start, start it.
5. Scroll down to the service SQLSERVERAGENT and verify that it
has started.
If the SQLSERVERAGENT service did not start, start it.
6. Close the Computer Management window.
Cancelling a Software
Component Installation
If a problem occurs during the installation routine, complete the

following steps to cancel the installation of a component.
1 . Press F3 to open the Exit Setup window.
2. Click Ex it Setup.
3. Try to install the given component or all components again.
If you are still experiencing problems, Refer to Rockwell
Automation Support in the Preface for information on how to
contact us.
8-8
Manual System
Backup/Restore
Procedures
Backing Up a ProcessLogix R510.0 Server to Tape

For information on backing up a ProcessLogix R510.0 Server to tape,
contact Rockwell Automation Tech Support, Refer to Rockwell
Automation Support in the Preface.
Restoring a ProcessLogix Server System from a Backup Tape

For information on restoring the ProcessLogix R510.0 Server system
previously backed up to tape, contact Rockwell Automation Tech
Support, Refer to Rockwell Automation Support in the Preface.
Using Network Tools
About Network Tools

The Network Tools utility lets you access valuable operating data on
your ProcessLogix hardware. It scans all the nodes on the Supervisory
Network segment connected to your ProcessLogix Server.
The utility features a common Windows interface with pulldown
menus, toolbar buttons, and a status bar. Its main window is divided
into a Tree pane, a List pane, and a Detail pane.
The Tree pane shows the nodes connected to your PC in an

hierarchical fashion.
8-9
The List pane provides information about the communication

status of the Supervisory Network.
The Detail pane provides a graphical representation of the
modules included in the chassis.
Each module graphic provides these details about the module:
base catalog number (without the 1756- prefix)

current state
CEE type for 1757-PLX52s (standard is 50ms and fast is 5ms)
current firmware version including application (AV) and boot
versions (BV), if applicable.
Usage guidelines
Observe the following usage guidelines to avoid a possible negative
impact on network performance under abnormal network conditions.
Do n ot use Network Tools while connecting nodes to the
network.
Do n ot use Network Tools when monitoring an analog I/O
module through Control Builder.
Do n ot use Network Tools to monitor an analog I/O ControlNet
network while the system is on-control.
Online help
You can get online help by clicking Help Help Topics and
displaying the desired topic.
8-10
Making First Time Network Tools Settings

Complete the following steps to make the initial settings for Network
Tools the first time you launch the utility on your PC.
IMPORTANT
While using Network Tools, you may see a Message

Meter dialog box. Comply with the request regarding
Control Builder, if applicable, and close the dialog
box.

a. For ControlNet Supervisory Networks, enter
>ntools -c -u -pg<.
TIP
If RSLinx and the PCIC driver services for system

communications in ControlNet mode are not
running, this command starts the services.
b. For Ethernet Supervisory Networks, enter >ntools -e -u -pg<.

4. With the Desktop icon selected, click Settin gs
the Settings dialog box.
to display
8-11
5. Do the following in the Options tab.

a. Enter >2< in the field for Delay betw een scan s (seconds).
b. Select the Per iodic (automatic) option.
This means automatic scans are made periodically with the
specified delay between scans.
c. Check En able Module Ver sion /Revision Ch eckin g.
This turns on the automatic firmware version/revision
detection function. This means Network Tools automatically
detects any incompatible firmware in a given module and
shows the modules firmware indication in Red instead of
Green on the modules graphic representation.
d. Check En able Con tr olNet Par ameter Ch eckin g.
This turns on the function for checking ControlNet parameter
settings.
6. Click OK to close the dialog box.

8. When network nodes appear under the Desktop tree icon, click
the first CNB or Ethernet driver icon to call up the settings dialog
box.
You only have to make these settings on the initial scan of the
system. However, you can access the settings at any time by
clicking the CNB or ENET icon and then clicking Settings
8-12
9. In the Local Chassis tab, adjust the number in the scroll box to
match the number of slots in your local chassis.
1 0. If your system includes a remote chassis, go to Step 11.

Otherwise, go to Step 15.
1 1 . Click the Remote Chassis 1 tab.
1 2. Check the Ch eck h er e if... in stalled checkbox.
1 3. Adjust the numbers in the appropriate scroll box to match the
following data about your remote chassis.
a. Number of slots in your remote chassis.
b. Network Address (MAC ID) of CNB in your remote chassis.
The assigned MAC ID is repeatedly shown in the LED display
on the CNB module in the format A#NN, where NN is the
Network Address. For example, a display of A#03 means the
CNB Network Address is 3.
c. Slot number where downlink CNB is installed in your local
chassis.
This is the CNB that is cable connected to the uplink CNB in
your remote chassis.
8-13
1 4. Repeat Steps 12 and 13 for other remote chassis by selecting the

next numbered tab, as required.
1 5. When settings are complete, click OK.
Look for the graphic of the chassis with the CNB to appear in
the Detail pane. The graphic also shows remote chassis, if
applicable.
1 6. Repeat Step 8 to Step 15 for next CNB or Ethernet driver icon, as
required.
1 7. Close NTools when finished.
8-14
Installing and Running

NetShield with
ProcessLogix
IMPORTANT
If you need to run the Network Associates NetShield

4.5 for NT and 2000 application on a ProcessLogix
Server, you must install and run the application as
described in this section.
Background
Problems with starting up and synchronizing Servers and crashing of
NetShield components can result from running the components
concurrently with the ProcessLogix software unless NetShield is
specifically installed and run as described in this section.
The problems noted above have occurred with version 4.5 of Network
Associates (formerly known as McAfee) NetShield, when running
automatically upon startup or during file access.
If the NetShield program is already installed on your ProcessLogix
Server, go to the next section to remove it. Otherwise, go to the
section entitled Installing NetShield and configuring directories for
scan exclusion.
Removing Existing NetShield Installation

If NetShield is currently installed on the ProcessLogix Server, complete
the following steps to remove it.
3. Select NetSh ield and click Remove.
4. Click Yes to confirm the action and follow the on-screen
instructions on the Uninstall Wizard to remove the NetShield
program.
5. Click Yes to restart the PC if prompted.
The PC must be restarted before continuing with the next
section.
8-15
Installing NetShield and Configuring Directories for Scan

Exclusion
Complete the following steps to install the NetShield program and
configure directories to be excluded from the virus scan.
1 . Follow the manufacturers instructions and on-screen prompts to
install the Network Associates software on your PC.
2. When the option to use System or Custom Account appears,
select System Accoun t.
3. After NetShield is installed, click Star t Pr ogr ams
Netw or k Associates NetSh ield Con sole.
4. In the Console, click Scan Pr oper ties to call up the
Properties dialog box.
5. Click the Detection tab.
6. Uncheck the outbound files checkbox.
7. Click the Ex clusion s tab.
8. Click Add to open the Add Exclusion Item dialog box.
>C:\Honeywell\server\data<
and click OK.
1 0. Click Add to open the Add Exclusion Item dialog box.
1 1 . Enter this path or Br ow se to:
>C:\Honeywell\TPS50\SYSTEM\ER <
and click OK.
1 2. Click OK to close the Properties dialog box.
1 3. Click Scan Ex it to close the Console.
8-16
Changing the Computer

Name on a ProcessLogix
Server
All ProcessLogix Servers and Clients require unique computer names

and IP addresses. If your ProcessLogix system includes multiple
Servers and/or Clients, you need to change computer names and
addresses to assure their unique identities.
If you need to change the computer name of a ProcessLogix Client,
refer to Changing the Computer Name on a ProcessLogix Client on
page 8-23.
ATTENTION
!
IMPORTANT
All procedures listed in this section should be

performed with the system(s) Off-Process!
A complete system backup should be performed
before proceeding with the procedures in this
section. This should include the Engineering
Database, ProcessLogix Server Database, Windows
Registry, and all files on the system.
If changing the name to make non-redundant Servers
a redundant Server pair, you must complete these
procedures on both Primary (SERVERA) and
Secondary (SERVERB).
When changing the name on a ProcessLogix
Server(s), you need to update the Hosts file on every
system in your configuration. All station
configuration files also need to be updated to reflect
the ProcessLogix Server(s) name change.
The following table lists the items that you must complete to rename a
ProcessLogix R510.0 Server.
Table 8.D Changing the Computer Name
Step
Item
Page
1.
Exporting the Engineering Repository Database
8-17
2.
Stopping ProcessLogix Applications and Services
8-1
3.
8-18
4.
Removing ProcessLogix R510.0 Server Components
8-19
5.
8-20
6.
Changing the PC Name
8-21
7.
3-2
8.
Restoring the Data
8-22
8-17
Exporting the Engineering Repository Database

IMPORTANT
Process systems must export their Engineering

Repository Database at this time before proceeding.
The data that is saved during this step can be stored
on the existing system, but can NOT be contained
within the C:\Honeywell path.
For example, create a directory at the root of C:
(e.g., C:\ExportDB).
If the system is clean (i.e., no configuration applied
yet), this procedure can be skipped.
Complete these steps on a non-redundant Server or on SERVERB.

1 . Logon to the Server as ps_user.
2. Using Windows Explorer, create the folder C:\ExportDB.
Con tr ol Builder.
drop-down list.
5. Click OK.
7. Click Br ow se to set the Directory to export the data to
C:\ExportDB.
several minutes.
9. Click Ex por t.
8-18

>C:\Honeywell\TPS50\System\Bin\
RA_PLX_uninstall_RSViewPE.exe<
and click OK.
3. Click OK at the RA_PLX Database Uninstall window.
ATTENTION

before continuing.

programs.
d. Repeat the steps for each component in the following order.
IMPORTANT
If at any time during software uninstall, a remove

Remove All.
IMPORTANT
8-19
Be sure to remove the components in the order they

are listed below.
Table 8.E Removal of Selected ProcessLogix R510.0 Components
Order
Component
1.
2.
ProcessLogix Update
3.
PsAxCtl Document EXE (If you see Application Removal windows,

click OK.)
4.
5.
RSLinx
6.
KB Server Knowledge Builder Tools 4
7.
KB Server ProcessLogix R500
8.
KB Client
9.
Knowledge Builder (Click the Remove option.)
1 0.
11.
Microsoft SQL Server 2000
1 2.

(If you receive errors, these are expected and will not effect the
outcome of the installation. Click OK to continue.)
1 3. Close the Add/Remove Programs window.
Removing ProcessLogix R510.0 Server Components

2. Select Pr ocessLogix and click Nex t.
and click Nex t.
8-20
8. If the system includes Excel Data Exchange, click En able

Macr os when prompted. Otherwise, continue with the next
step.
9. Click OK at all createsqlobject prompts.
1 0. At the Setup Complete window, click the No, I w ill r estar t my

IMPORTANT

1 . If necessary, click Star t Settin gs Con tr ol Pan el.

following order.
ProcessLogix Update
KB Server - ProcessLogix R500
KB Client
Knowledge Builder
Microsoft SQL Server
RSLinx
ProcessLogix Server
HMIWeb
HMIWeb Station
Display Builder
Quick Builder
8-21
ODBC Client
OPC Server Connect
Network API
Shape Library

Changing the PC Name

IMPORTANT
PC Naming Rules
The base name cannot contain more than 13
The full computer name cannot contain more than
14 alphanumeric characters. The following naming
conventions are required for given ProcessLogix
system architectures.
For non-redundant Server, be sure the name does
not end in the letter A or B. The default name is
PLX1.
For redundant Servers, append the letter A or B to
the base name to identify the PCs function in the
system architecture for the primary and secondary
Servers, respectively. For example, use the name
PLX1A for the primary Server (SERVERA) and PLX1B
for the secondary Server (SERVERB) (14 characters
total: up to 13 base plus A or B).
Complete the following steps to change the name of your PC.

1 . If necessary, click Star t Settin gs Con tr ol Pan el.
2. Double-click System.
3. On the Network Identification tab, click Pr oper ties.
4. Enter the desired computer name in the Computer name entry
field.
8-22
5. Click OK to initiate the change.

6. At the You must reboot prompt, click OK.
This will not restart the system.
7. Click OK to close the System Properties window.
8. Click Yes to restart the computer.
Reinstalling ProcessLogix R510.0 Components

Reinstall the ProcessLogix R510.0 components by completing the
procedures in Installing ProcessLogix R510.0 Software on page 3-2.
Restoring the Data

ATTENTION
If you are using this procedure for renaming

redundant servers, finish setting up redundancy.
Refer to Completing the ProcessLogix R510.0 Setup
on a Redundant Server Pair on page 6-2 before
performing this step to restore the Engineering
Repository Database (ERDB).
Follow the steps below to import the data back into the Engineering
Repository Database.
2. Select Star t Pr ogr ams Pr ocessLogix En gin eer in g Tools
Con tr ol Builder.
c. Enter the appropriate Server Name in the Server Name field.
drop-down list.
4. Click OK.
5. Click File Impor t.
8-23
6. Click Br ow se to set the import Directory to C:\ExportDB.

several minutes.
8. Click Impor t.
9. When completed, close the Import Window.
IMPORTANT
At this point, each controller must be reloaded on

the system.
Changing the Computer

Name on a ProcessLogix
Client
All ProcessLogix Servers and Clients require unique computer names

and IP addresses. If your ProcessLogix system includes multiple
Servers and/or Clients, you need to change computer names and
addresses to assure their unique identities.
IMPORTANT
ATTENTION

Do not complete this procedure on a ProcessLogix
Server. The SQL Server fails without taking special
precautions first.
If you need to change the ProcessLogix Server
Computer name, refer to Changing the Computer
Name on a ProcessLogix Server on page 8-16.
Changing the Computer Name on a Windows 2000 Client

1 . Logon as ps_user.
4. On the Network Identification tab, click Pr oper ties.
8-24

field.
7. At the You must reboot prompt, click OK.
8. Click OK to Close the System Properties window.
Changing the Computer Name on a Windows XP Client

1 . Logon as ps_user.
4. On the Computer Name tab, click Ch an ge.
field.
7. At the You must restart prompt, click OK.
8. Click OK to Close the System Properties window.
Configuring a ProcessLogix Client

Changing Hosts files entries
Refer to Changing Hosts File Entries on page 6-3 to be certain that the
Hosts file on a ProcessLogix Client lists applicable Server names and
IP addresses.
Setting Up a ProcessLogix Client with a Non-redundant Server

If a ProcessLogix Client is networked to a non-redundant Server, refer
to ProcessLogix Client Supported Installations on page 1-4. Use this
8-25
procedure to confirm that any client reference the correct

non-redundant server or computer name or IP address.
Setting up a ProcessLogix Client with Redundant Servers

If ProcessLogix Client is networked to redundant Servers, refer
to ProcessLogix Client Supported Installations on page 1-4.
Adding 1757-PLX52
Controller Redundancy to
R510.0 Non-Redundant
1757-PLX52 Controller
Configurations
ATTENTION

Deleting a Non-Redundant 1757-PLX52 and Unassigning its

Contents
Complete the following steps to save your existing database and
delete it from the existing non-redundant 1757-PLX52 Controller.
1 . Start Control Builder.
2. Close any open Control Module and/or Sequential Control
Module.
3. In Monitoring tab, expand the non-redundant CPM to display
the CEE folder icon.
4. Click the CEE folder icon.
5. Click Tools Upload w ith Con ten ts to upload the existing
controller database.
6. Click Con tin ue.
This may take considerable time to complete, depending on the
amount of CM/SCMs (and their number of FBs and/or number
of Steps/Transitions) currently assigned to this CEE.
7. Click the CEE folder icon.
8. Click Tools Update w ith Con ten ts (to Project) to save the
existing controller database.
8-26
9. Click Con tin ue.

This may take considerable time to complete, depending on the
amount of CM/SCMs (and their number of FBs and/or number
of Steps/Transitions) currently assigned to this CEE.
1 0. Click the CEE folder icon.
1 1 . Click Oper ate In activate Th is CEEs SCMs to inactivate
all assigned SCMs, if applicable.
1 2. Click Yes in the dialog box to confirm the action.
1 3. Click Oper ate In activate Th is CEE an d its IOMs and
CMs to inactivate the CEE and all assigned IOMs and CMs.
1 4. Click Yes in the dialog box to confirm the action.
Color of all icons changes to Blue.
1 5. Select the contents (CMs, SCMs, IOMs) of the CEE folder and
click Edit Delete.
1 6. Click Delete Selected object(s) to delete the selected objects.
1 7. Click the CPM icon , and click Edit Delete.
1 8. Click Delete Selected object(s) to delete the non-redundant
CPM.
1 9. In Project tab, click the CEE folder icon.
20. Click Tools Assign to call up the Controller Assignments
dialog box.
21 . Verify that the checkboxes for Show CMs and Show IOMs are
checked.
22. Select the CEE associated with the non-redundant CPM in the
Select a CEE list box.
23. Select all the modules listed in the Assigned Modules list box.
Document the modules you are unassigning.
24. Click Un assign .
25. Wait for modules to be unassigned and removed from the
Assigned Modules list box.
26. Click Close and return to the Project tab.
8-27
27. Click the CPM icon and click Edit Delete.

28. Click Delete Selected object(s) to delete the CPM and its
associated CEE.
Installing and connecting Redundant Chassis Pair (RCP)

Hardware
Refer to the following data in Knowledge Builder for general
information about Controller redundancy and how to install and
connect the 1757-PLX52, 1757-SRM Redundancy Module (SRM), and
1756-CNBR redundant ControlNet Bridge module (CNB).
Navigate in Knowledge Builder to Control Builder Components
Theory Controller Redundancy Functionality before
upgrading to a Redundant Chassis Pair for general information
about Controller redundancy and related terminology.
Navigate in Knowledge Builder to Control Hardware
Installation Guide Controller Module Installation and
Removal for information on installing the 1757-PLX52 module.
Installation Guide Redundancy Module Installation and
Removal for information on installing the 1757-SRM module.
Installation Guide ControlNet Communication Module
Installation and Removal for information on installing the
1756-CNB module.
Updating Firmware Revision Levels

Refer to Upgrading Hardware Component Firmware on page 7-4 to
check/upgrade 1757-PLX52, 1756-CNB, and 1757-SRM firmware.
IMPORTANT
Stop! It is essential that you check the firmware

installation.
firmware.
8-28
Creating a Redundant 1757-PLX52

1 . Create redundant CPMs
Navigate in Knowledge Builder to Control Building Guide
Hardware Module Creation Creating a Control Processor
Module for more information about configuring a redundant
1757-PLX52 in Control Builder.
2. Create redundancy modules.
Hardware Module Creation Creating Redundancy Modules
for more information about configuring 1757-SRMs in Control
Builder.
3. Once the redundant CPM is created in the Project tab, re-assign
the modules unassigned from the previous non-redundant CPM
to the CEE associated with the new redundant CPM.
Control Module Creation Assigning the CM and IOMs to the
CEE for more information.
4. Load the primary and secondary CPMs and RMs to the
Controllers.
Control Strategy Loading Loading Objects to the CPM for more
information.
This completes the upgrade to a Redundant Chassis Pair.
Chapter

Overview
This release introduces enhancements to Rockwell Automation's

ProcessLogix process control system.The enhancements include:
Table 9.A New Features and Functions Overview
Enhancement
Description
ProcessLogix DeviceNet Wizard
Integrated configuration tool for DeviceNet

networks
1757-ABRIO Updates
Updated configuration software

Updated firmware
New PLX Function Blocks
AB_Logic Library
RSView Connectivity
ProcessLogix Server interface to RSView SE

with Process Extensions.
Additional Module Support
ProcessLogix DeviceNet
Wizard
The following modules have been qualified for use

with ProcessLogix:
1794-IB8
1794-OC16
1794-IM8
1794-IB32
1794-OM8
1794-OB32
1794-IC16
1794-IRT8
The DNET Library is integrated into ProcessLogix R500.1 or greater.

The ProcessLogix DeviceNet Wizard uses RSNetworx for DeviceNet
report files to create templates for Device and IM blocks. These
templates can then be imported into Control Builder. For best results,
use an RSNetworx report file with a fully configured DeviceNet
network.
Navigate in Knowledge Builder to ProcessLogixR500 CCL Help
DeviceNet Interface DeviceNet Wizard for more information.
9-2
1757-ABRIO Update
The new features for the ABRIO include:

Supports scheduled connections to update digital data with a
ControlLogix processor.
Supports firmware updates using NTools or ControlFlash.
Supports direct DDE/OPC data access.
The 1757-ABRIO ships with a configuration utility, AbRioCfg. This
configuration program is an online configuration tool. Use it to:
query the RIO network to determine the location and size of the
racks present
add and configure supported block transfer modules
create tags for access by the control processor
map I/O data to those tags
download the configuration to the module, using RSLinx
monitor data and diagnostics on the module
upload a configuration from a module
print the configuration
New PLX Function Blocks
AB Logic instructions are contained in the ControlBuilder Library tab.

These instructions allow you to combine bits into bytes, words, or
dwords. You can also convert bytes, words, or dwords into bits. The
following is a brief description of the new instructions.
Table 9.B New CCL Instructions
Instructions
Action
Inputs
Outputs
8Bits2Byte
takes 8 bits of input and creates 1

byte of output
(Boolean) 8 bits
(INT8) 1 byte
Byte2Bits8
takes 1 byte of input and

translates it into 8 bits of output
(INT8) 1 byte
(Boolean) 8 bits
16Bits2Word
takes 16 bits of input and creates

1 word of output
(Boolean) 16 bits (INT16) 1 byte
Word2Bits16
takes 1 word of input and

(INT16) 1 word
(Boolean) 16 bits
32Bits2DWord takes 32 bits of input and creates

1 dword of output
(Boolean) 32 bits (INT32) 1 dword
DWord2Bits32 takes 1 dword of input and

(INT32) 1 dword
(Boolean) 32 bits

AB_LOGIC for more information.
9-3
RSView Connectivity
The ProcessLogix R510.0 Server contains enhancements which enable

connectivity to RSView SE with Process Extensions 3.10 and higher.
When connected via OPC, R510.0 populates the PE Navigation
application with ProcessLogix I/O modules and PID loops configured
in the ERDB. RSView PE standard faceplates can be used to view the
I/O modules and PID loops.
Additional Module Support
The following modules have been qualified for use with ProcessLogix:
1794-IB8
1794-IB32
1794-IC16
1794-IM8
1794-IRT8
1794-OB32
1794-OC16
1794-OM8

1794-FlexI/O for more information.
9-4
Chapter
10
This chapter contains the detailed information about the major

ProcessLogix R510.0 software and related components.
Major ProcessLogix Engineering Tools Software Revisions

Table 10.A Major ProcessLogix Engineering Tools Software Revisions
Component
Version
Example Verification Mechanism
Control Builder
PS500.1-RI.1
1. Execute Control Builder using Start Programs

ProcessLogix Engineering Tools Control
Builder.
2. Click Help About.
DB Admin
500.1.1.1
1. Run Windows Explorer.

2. Right-click on the file
C:\Honeywell\TPS50\System\Bin\Adminfuncs.dll
3. Click Properties.
4. Click Version tab.
Import-Export Tool
PS500.1-01.1
1. Execute Import-Export Tool using Start

Programs ProcessLogix Engineering Tools
Import/Export Tool.
Engineering Tools
Database
V5.0 ERDB
Release PS500.1-1.1
1. Execute Import-Export Tool using Start

Import/Export Tool.
IO Tool
500.1-1
1. Execute IO Tool using Start Programs

ProcessLogix Engineering Tools IO Tool.
Network Tools
PS500.1-01.1
1. Execute NTools using Start Programs

ProcessLogix Engineering Tools NTools.
2. Click Help About Network Tools.
Fieldbus Library Manager PS500.1-01.1
1. Execute Fieldbus Library Manager using Start

Fieldbus Library Manager.
2. Click Help About Fieldbus Library Manager.
Knowledge Builder
Database
1. Execute Knowledge Builder using Start

Programs Performance Support Tools
Knowledge Builder.
2. Click the Legal Notices link on the Welcome
window.
Release 510.0
October 2003
Copyright 2003
10-2
Major ProcessLogix Server Software Revisions

Table 10.B Major ProcessLogix Server Software Revisions
Component
Version
ProcessLogix Server
R500.1
Build 500.1-20.0
1. Execute ProcessLogix Server dialog box using Start

Programs ProcessLogix Server
Start-Stop ProcessLogix Server.
2. Click System Menu (Top Left Corner) About.
Station
2.0.310.430
1. Execute Station using Start Programs

ProcessLogix Server Station.
2. Click Help About Station.
HMIWeb Display
Builder
2.0.310.379
1. Execute HMIWeb Display Builder using Start

Programs ProcessLogix Server HMIWeb
Display Builder.
2. Click Help About HMIWeb Display Builder.
Display Builder
320.3
(Build 17)
1. Execute Display Builder using Start Program

ProcessLogix Server Display Builder.
2. Click Help About Display Builder.
Quick Builder
2.00
(Build 474)
1. Execute Quick Builder using Start Programs

ProcessLogix Server Quick Builder.
2. Click Cancel at Quick Builder window.
Microsoft Excel Data

Exchange
R500.0
1. Execute Excel using Start Programs

Microsoft Excel.
2. Click Tools Microsoft Excel Data Exchange
About Microsoft Excel Data Exchange.
10-3
Embedded Software Components

Table 10.C Embedded Software Components
Component
Version
Windows 2000 Service

Pack 4
Service Pack 4
1. At command prompt enter >WINVER<.

2. The response should include Service Pack 4
Windows 2000 Hotfix
KB824146
1. Click Start Settings Control Panel

Add/Remove Programs.
2. Listed will be Windows 2000 Hotfix - KB824146
Internet Explorer 6.0
6.0.2800.1106CO
1. Run Knowledge Builder or Internet Explorer.

2. Click Help About Internet Explorer.
Internet Explorer 6.0

SP1
Update Versions: SP1
1. Run Knowledge Builder or Internet Explorer.

2. Click Help About Internet Explorer.
MS Visual C++
Run-Time DLLs
6.1.9844.0
1.
2.
3.
4.
MS Visual Basic
Run-Time DLLs
6.0.96.90

C:\winnt\System32\msvbvm60.dll
Seagate Crystal
Reports 6.0
6.0.1.151
1.
2.
3.
4.
Run Windows Explorer.

Right-click on the file C:\winnt\system32\msvcrt.dll.
Click Properties.
Click Version tab.
Run Windows Explorer.

Right-click on the file C:\winnt\System32\crpe32.dll.
Click Properties.
Click Version tab.
Stingray Objective Grid 6.0.1.0

C:\Honeywell\TPS50\System\Bin\objgrid.dll.
RSLinx
2.41.00
(Build 10)
1. Execute RSLinx using Start Programs

Rockwell Software RSLinx RSLinx.
2. Click Help About RSLinx
SQL Server 2000
2000.80.534.0

2. Right-click on the file C:\Program Files\Microsoft SQL
Server\MSSQL\Binn\sqlservr.exe.
MS-Access
3.0.0.2504

C:\Honeywell\TPS50\System\bin\mswng300.dll
4. Click Version Tab.
Adobe Acrobat Reader
4.05b.0127
1. Execute Adobe Acrobat using Start Programs

Adobe Acrobat 4.0 Acrobat Reader 4.0.
2. Click Help About Acrobat Reader.
10-4
External, Third Party Qualified Software Components

IMPORTANT
This section identifies third party Windows-based

software applications that are supported with
ProcessLogix. Special care must be exercised when
using any of these third party packages.
WARNING
The user assumes all responsibility for issues

resulting from the installation and operation of any
components that have not been tested as compatible
by Rockwell Automation. In addition, it is the
customers responsibility to ensure that the
combinations of third party components have
sufficient resources (e.g. memory, CPU performance,
disk space, display space, etc.).
Table 10.D External, Third Party Qualified Software Components

Component
Version
Verify the component version by:
McAfee VirusScan
4.5.1
(SP1)
1. Start VirusScan Console using: Start Programs

Network Associates VirusScan Console.
2. Click Help About
McAfee VirusScan
6.0
1. Start VirusScan Console using: Start Programs

Network Associates VirusScan Console.
2. Click Help About
McAfee NetShield
4.5
1. Start NetShield using Start Programs Network

Associates NetShield Console.
2. Click Help About
National Instruments NI-FBUS

Communications Manager
NI-FBUS Communications Manager
2.3.4
1. Start Fieldbus Interface Configuration using: Start

Programs National Instruments FBUS Interface
Config.
2. Click the System Menu.
3. Select About fbConfig_NT.
Limitations/Compatibilities:
Model Number 1788-FFCT, for use with the CN2FF. Only this
model number should be purchased and not the general release
of the Configurator from NI.
10-5

Component
Version
MS Office 2000 Products

Access

Excludes Outlook
9.0.1381
Service Pack 1
1. Open Access.
2. Click Help About Access
Use on Client only
Excel
9.0.1381
Service Pack 1
PowerPoint
9.0.1381
Service Pack 1
1. Run MS Excel.
2. Click Help About MS Excel
1. Run PowerPoint.
2. Click Help About PowerPoint
Use on Client only
Word
9.0.1381
Service Pack 1
1. Run Word.
Use on Client only
MS Office XP Products
Access
Excludes Outlook
10.3109.3501
Service Pack 1
1. Open Access.
Use on Client only
Excel
10.3506.3501
Service Pack 1
PowerPoint
10.3506.3501
Service Pack 1
1. Run MS Excel.
2. Click Help About MS Excel
1. Run PowerPoint.
2. Click Help About PowerPoint
Use on Client only
Word
10.3416.3501
Service Pack 1
1. Run Word.
Use on Client only
10-6

Component
Version
MS Visual C++
6.0

2. Right click \winnt\system32\mscvrt.dll
(Microsoft Run Time Library).
4. Click the Version tab.
Service Pack 5
Use on Client only
MS Visual Basic
6.0

2. Right click \winnt\system32\msvbvm50.dll
and \winnt\system32\msvbvm60.dll
4. Click the Version tab.
Use on Client only
Carbon Copy 32
5.5
1. Run Carbon Copy 32 using:

Start\Programs\ProcessLogix Carbon Copy 32 \
Carbon Copy 32
2. Click Help About...
Carbon Copy 32 cannot be installed in conjunction with other
remote control software e.g. PC Anywhere.
Miscellaneous SCADA Component Revisions

Table 10.E Miscellaneous SCADA Component Revisions
Component
Version
Modicon Netlib
2.1
RSNetworx
ControlNet
4.11 (Build 47)
DeviceNet
4.12 (Build 01)

2. Right click \winnt\system32\netlib.dll
1. Double click RSNetworx icon.
2. Click Help About RSNetworx
RSLogix 5
6.0
1. Run RSLogix 5
2. Click Help About RSLogix.
RSLogix 5000
12.01.00
1. Run RSLogix 5000.

2. Click Help About RSLogix.
RSBizware Batch
Contact Rockwell Automation Technical

Support, refer to Rockwell Automation Support
in the Preface
Chapter
11
ATTENTION
This chapter contains the most current platform

requirements from the performance and capacity
specifications for R510.0. The information in this
document takes precedence over that of Knowledge
Builder or any other ProcessLogix document.
Server/Client Performance PC Platform Requirements

and Capacity
The performance of the PC Platform varies greatly based on the
operating system and Process Control configuration. All information
should be considered before ordering or configuring a system.
Customers who are upgrading should consider upgrades to match the
specifications outlined in this document.
ProcessLogix R510.0 Server(s) require a server grade hardware
platform and Server grade operating system (Windows 2000 Server).
Server grade hardware is intended to serve data to clients over a
network and as such is typically provided with lower performing
video cards and without sound cards. The Windows 2000 Server
operating system provides lower foreground performance than a
desktop oriented operating system like Windows 2000 Professional. In
combination with the hardware and operating system specifications,
Rockwell Automation's tuning of the operating system provides
optimum performance for the SQL 2000 and ProcessLogix Server.
IMPORTANT
The ProcessLogix Server should not be used as an

operator station. The use of client applications on
the server is supported (ideal for engineering
activities, etc.) but the performance is not
appropriate to be used as an operator station. For
ProcessLogix Clients, Rockwell Automation
recommends the Windows 2000 Professional and
Windows XP Professional operating systems.
11-2
Server Requirements
ProcessLogix Server Software must be installed on a PC that is
specifically qualified. Use of any other PC variations will render the
standard warranty and support agreement null and void.
There are two methods of obtaining the qualified ProcessLogix Server:
1 . Purchase the Server from Rockwell Automation.
2. Contact Rockwell Automation Technical Support for further
information on ordering specifically qualified hardware.
Platform System Configuration Definitions

The number of Physical Servers and Stations does not determine
system configuration. If you are considering a large and complex
process, this will affect the performance. For example, you may only
require passive monitoring and occasional report generation, but the
process is large and complex. Therefore you would be better off
installing system requirements that better match the Performance
system, rather than the Typical configuration. Use the information
below to approximate your system size.
Minimum
This is the minimum hardware necessary to run the ProcessLogix
components. It should only be used for small configurations that may
consist of 1 non-redundant Server or a Redundant Server pair with 1
Station. The system typically only includes passive monitoring and
occasional report generation.
Typical
Configurations will consist of 1 non-redundant Server with up to 12
Stations or a Redundant Server pair and up to 8 Stations. This type of
system includes 1 or 2 Stations actively monitoring and occasional
report generation.
Performance
An advanced configuration will consist of 1 non-redundant Server or a
Redundant Server pair, and (between) 13 to 20 Stations. This system
typically includes active monitoring from multiple Stations with or
without multiple locations and random report generation.
11-3
Table 11.A Database Sizing Chart

Process Configuration
System Suggestion
Controllers: None
Up to 3,000 SCADA points
Minimum
Up to 6 Controllers(1)
Systems with up to 600 CM/SCM/IOM/1757-FIM
Up to 10,000 SCADA points
Typical
More than 6 Controllers(1)

Systems with more than 600 CM/SCM/IOM/1757-FIM
More than 10,000 SCADA points.
Performance
(1) Hybrid Controllers configured in a redundant mode should be counted as 1 Hybrid Controller.
Client Platform Requirements

Table 11.B Client Platform Requirements based on System Configurations
System Configuration
Minimum
Typical
Performance
Processor
1 GHz Pentium III or larger
1.4 GHz Pentium III or larger
2.0 GHz Pentium IV or larger
128 MB(2)
256 MB
256/512 MB
Windows 2000 Server(1)
256 MB(2)
384 MB
512 MB
Networking
10 Mb Ethernet(3)
100 Mb Ethernet
100 Mb Ethernet
Video Resolution
1024 x 768
65K colors
1024 x 768
1280x1024
65K colors
1024 x 768
1280x1024
65K colors
Video Memory (VRAM)
16MB
32MB
32MB
Hard Drive
9.1 GB
10 GB
20 GB
Example Hardware
Dell Optiplex GX200
Dell Optiplex GX200 or GX240
Dell Optiplex GX240
RAM
(1)
This Operating System is not optimal for hosting client applications. It may not be possible to configure server grade hardware to meet the requirements listed.
(2)
In these configurations, paging may occur on these systems. Based on the intended usage of the platform, this configuration is acceptable. For better performance, users
should upgrade the systems with an additional 128 MB of RAM.
(3) We suggest that you upgrade to 100 Mb Ethernet Networking.
11-4
Application Usage
Server configuration memory allocations assume Server services only.
Client memory usage already includes the ProcessLogix Client
Applications. However, most applications can be run on either the
Servers or Station Clients. On minimum to typical systems, these
applications may be run on the Server Platforms. On performance
systems, the Servers should be dedicated to running only the Server
Services. On these systems, when possible, all applications should be
run from the Client stations.
Using the Platform Requirements Tables 11.B and 11.C as a base for
memory usage, add on the memory requirements for each of the
applications from the Application RAM Usage. Table 11.C is intended
to be used on a regular basis.(1)
Failure to add additional memory may result in
degradation of system performance.
TIP
Table 11.C Application RAM Usage

Application
RAM Usage
Windows 2000 Applications

Explorer
8 MB
Computer Management(1)
8 MB
Event Viewer
5 MB
Task Manager(1)
2.5 MB
Internet Explorer
8 MB
Backup
6 MB
ProcessLogix Applications
Station(2)
5 MB
Control Builder
20 MB
Fieldbus Library Manager
15MB
Network Tools
(3)
Quick Builder(3)
20 MB
DB Admin(3)
10 MB
Import Export Tool(3)
20 MB
Knowledge Builder
Adds 2 MB on top of Internet Explorer
Fieldbus: NIFB(4)
8 MB
Fieldbus: NI FBUS Configurator(5)
13 MB
Other Applications
3 MB
11-5
Table 11.C Application RAM Usage

Application
RSBizware Batch
RAM Usage
(6)
128 MB
Microsoft Excel
7 MB
Microsoft Excel with Data Exchange
10 MB
Microsoft Word
13 MB
Upgrading Options
Non-Redundant to Redundant ProcessLogix
Server
(1)
32 MB (7)
Application usage on Servers greatly effects the CPU resources. A CPU upgrade or platform upgrade should be
considered if your primary usage of the applications will be on the Servers. On Redundant Systems, primary
application usage should be on the Backup Server.
(2) The Station application affects the Client and Server Nodes. The memory should be added on both physical PCs
per application. For example, if the Server is going to support 5 Stations, then you would require an additional 25
MB (5 x 5).
(3) These applications are more for configuration and typically are not run all the time. They represent a one-time
memory allocation when running. When considering additional RAM requirements, you should only include those
applications in which you intend to run on a daily or constant basis.
(4) If NIFB is run on the Primary ProcessLogix Server or the Server is Non-Redundant, you are limited to only 8 Linking
Devices. This applies only to 1757-CN2FF access to Foundation Fieldbus devices. It does not apply to FIM access.
(5) While using the NI FBUS Configurator, you can only monitor 1 Linking Device at one time. This application should
only be run on the Backup Server (if redundant) as this will put an additional CPU load on the system
approximately 35% higher than the normal running state. If run on a Non-Redundant Server, it is required that you
have a more performance CPU configuration. This applies only to 1757-CN2FF access to Foundation Fieldbus
devices. It does not apply to FIM access.
(6) RSBatch includes multiple services and applications.
(7)
This upgrade requirement is per Server Node.
11-6
ATTENTION
Low memory and CPU resources can affect Server

performance in the following ways:
Low memory can impact CB and Station
operations such as display call-up and screen
refresh. Background applications such as RSLinx
and CDA can also be impacted. On occasion,
extremely low memory resources have caused
foreground and background applications to fail.
Low memory causes virtual memory to be
swapped often, which itself is a CPU intensive
operation. Therefore, low memory directly affects
the amount of available CPU resources.
Low CPU resources can impact communication
between Clients and Server. Although the
communication subsystem guarantees data
delivery, low CPU resources can create
communication bottlenecks that adversely affect
the freshness of data displayed.
Low CPU resources can impact CB operations
such as: opening charts, loading, uploading and
updating project.
11-7
User Interface Capacity and Performance

Table 11.D Operational Display Update Rates
Operation Display Update Rates
Maximum Continuous Display Update Rate
1 sec
Maximum Number of Parameters/Display
300
Typical Field Change to Display Update Time with 100 Parameters Per Display on a Single Station/Server
(Server configured for 1 sec update)
< 2 sec
Typical Display Call Up Time with 100 Parameters on a Single Station/Server

(Call up time is dependent on display complexity; this excludes the first initial call up.)
< 2 sec
Maximum Number of Stations Connected to one Server
20
Maximum Number of Concurrent Users Connected to one Server.
Unlimited for Windows 2000

Sever based system
See Table 11.G Server communication NetBIOS session capacity on page 11-9.
Table 11.E Multi-user CB/FLM Operational Limits
Multi-user CB/FLM Limits
Maximum CB Clients connected to single Server
Remote Access Service (RAS) support for Multi-User CB
Not Supported
Dial-up Networking support for Multi-User CB
Not Supported
Minimum continuously available Network Bandwidth required for each multi-user CB Client.
128KB
Maximum Fieldbus Library Manager Clients connected to a single server
11-8
Control Builder Considerations

Viewing the expanded Monitoring Tab Tree View of the same
1757-PLX52 Controller loaded with more than 500 total CMs, SCMs
and IOMs from more than one CB client simultaneously, will severely
affect the performance of the 1757-PLX52 Controllers communication
capability, both to the Server and Peer-to-Peer.
Using multiple CB clients to load to multiple controllers
simultaneously actually increases the overall load time. Do not
employ this technique as a way to save time in loading a controller
with contents.
Database operations (load, delete, upload, update, etc.) initiated from
a CB client will affect the performance of applications that run on the
backup Server. Remote CB clients will also be affected by these
operations. For instance, a CB client will experience reduced
performance if another CB client is also connected to the same Server
and has requested a large database operation.
Control Builder supports multi-user functionality, however, it should
be noted that there are some operations that are restricted.
Specifically, if a load is carried out at the same time as database
modifications are in progress (including import, copy, delete), then
these operations may fail, displaying related error messages. Examples
of such errors include:
Database Modification in Progress, Try Again Later
Point Build Error
In extreme cases these errors may cause Control Builder to stop
functioning. If this happens, you should restart the Control Builder
and reload the server points to ensure that the changes take effect.
Data should not be affected.
11-9
Server Redundancy
Table 11.F Server redundancy specifications
Server Redundancy
Server Switchover Time Default
30-40 sec
Server Switchover Time Fastest Configurable Time
10 sec
On Server switchover, the 1757-PLX52 performs an event recovery. This causes the
controller to report all current alarm conditions. The Server will report all current process
alarms and events.
Database synchronization is performed as a background activity and is

performed online without affecting the operation of the Servers. Time
to complete synchronization will depend on the system configuration
(e.g., database size, history, processor speed).
Client/Server Communication Capacity

Table 11.G Server communication NetBIOS session capacity
Session type or activity
Comment/example
Time Sync
Active once every configured Time Sync period.
Shared Drives/ Displays
Active continuously, if Station Client get displays from

central Server.
Shared printer
Active continuously if linked to a network printer for

Reports, etc.
Server Redundancy
Uses from 1-3 Server Sessions based upon User/Login

Configuration settings. (Also requires Time-Sync)
ER Server
Active during replication on Redundant Servers.
Multi-User CB
Active during Point Build (uses shared drive)
Snap-Shot Save & Restore
Active during this operation (uses shared drive)
Server Type
Simultaneous NetBIOS sessions available
ProcessLogix Server on Windows

2000 Server
Unlimited (See Microsoft license restrictions)
11-10
Server Notifications
Table 11.H Server Notifications
Server Notifications
Value
Maximum number of events (burst condition)(1)
1000 events
Maximum number of events/second (sustained)
40/sec
Maximum number of alarms/second (sustained)(2)
20/sec
Maximum number of remote OPC A&E Servers subscribed to by

the ProcessLogix Server(3)
Maximum number of remote OPC A&E Clients supported by the
ProcessLogix OPC A&E Server
(1)
Event Burst Handling

The ProcessLogix Server Alarm System will handle an event burst of up to 1000 events, with a minimum time
between consecutive bursts. An event burst will be defined as a group of events greater than 40/sec, received
from all connected Event Servers in a period of less than 3 seconds. The time period required between
consecutive bursts, to allow for event processing, can be calculated using the following formula: T = BS/(40-ER)
Where:
T = # of seconds required between bursts
BS = Burst Size (number of events in the burst)
ER = Event Rate between bursts
Examples:
1) 1000 Event burst and no events between bursts: T = 1000/40 = 25 seconds
2) 500 Event burst with 30 events/sec between: T = 500/10 = 50 seconds
(2) Up to two events are also generated for every alarm, including one event for entering the alarm condition and one
for return to normal.

(3) OPC Alarm & Event Support: The ProcessLogix Server includes the option to support reception of OPC Alarms &
Events, in addition to native ProcessLogix notifications. When an OPC Alarm & Event Server has been configured
to generate notifications to captured by the ProcessLogix Server Alarm System, the notification limits noted
above are applicable to the combined set of events received from all event sources configured.
Server Data Access
Table 11.I Server Data Access

Server Data Access
Definition: PPS = Average Parameters Per Second
Maximum CDA PPS from all Controllers (1757-PLX52 and FIMs)
4000 PPS
Maximum OPC PPS from all configured OPC Servers
1600 PPS
Maximum number of remote OPC Data Access Servers subscribed

to by the ProcessLogix Server
Maximum OPC PPS published to all OPC Clients
2000 PPS
Maximum number of remote OPC Data Access Clients supported

by the ProcessLogix Server
Controller and
Communications Capacity
and Performance
11-11
Control Network Capacity
Table 11.J Process Control Network Specifications

Supervisory Process Control Network
Network Media
Ethernet
ControlNet
Supervisory Networks per ProcessLogix Server

(1 PCIC card per Server)
Mixed Supervisory ControlNet & Ethernet on the same Server is not
supported.
1 non-redundant network
serviced by 1 redundant or
non-redundant Server
1 redundant or non-redundant
network serviced by 1 redundant
or non-redundant Server
Total ControlNet connections Limit(1)
N/A
127
Allowable Combinations of Controllers per Server
Up to 10 non-redundant only
Up to 10 redundant or
non-redundant in any
combination
Maximum Number of Nodes allowed including Controllers, Servers

and FIM-only chassis.
12
Only qualified for redundant
Servers +10 non-redundant
controllers
FIMs are not supported on a
Supervisory Ethernet system
in any configuration
24
Data Transmission Rate
10 Mbits/sec
5 Mbit/sec
Media Redundancy
Non-redundant only
Single cable or redundant media

operation supported.
Controller Definitions including PLCs

Multiple 1757-PLX52s per chassis are NOT supported. However, a
non-redundant 1757-PLX52 can reside in the same chassis as a
Logix 5550.
PLCs only count as controllers when SCADA connections are
defined against the PLC.
Non-Redundant:
1 1757-PLX52
1 Logix5550
1 PLC5/C or E
1 SLC (Ethernet only)
Redundant:
2 1757-PLX52s in a Chassis
Pair with 2 1757-SRMs
2 1756-5555s in a chassis pair
with 2 1757-SRMs
(1) The CPM and FIM use 1 PCIC connection from the Server regardless of whether they reside on a Supervisory or I/O ControlNet. PLCs should be limited to 2 connections if
configured as SCADA controllers via RSLinx.
11-12
System Communications Load Philosophy and Guidelines

The ProcessLogix System is designed with certain patterns of
communications in mind. Being aware of the intended traffic flows
will help the application engineers insure that the application realizes
the highest usage from the systems architectural capabilities.
The basic concept is shown in the following hierarchical diagram. It
shows four levels of networking: Plant Information, Supervisory, I/O,
and Device. It also includes four levels of networking nodes:
Application stations (like operator stations and high-level application
nodes), controller-level stations, I/O level chassis, and directly
networked devices.
Figure 11.1 System Communications Architecture
Operator and
Applications Nodes
Server Node
External
DCS
Systems
Controller
Nodes
ABRIO
IO Nodes
Device Nodes
The server is the head of a pyramid of controllers. Each controller, in

turn, is a head of a pyramid of IO chassis. Each IO chassis is in turn, a
head of a pyramid of field devices nodes.
11-13
System communication is most effective and efficient if minimum

networks and nodes are involved between communicating devices
within a pyramid. For example, if a transmitter and a valve form a
second control loop, and they are on the same H1 network, latency of
communications will be minimal and traffic in other nodes and
networks will be minimal.
There are tradeoffs, however. A better algorithm set in the
ProcessLogix controller, the need for sequencing logic, or mixture
with conventional or other bus I/O are examples where controller
interaction is required. Further, interlocks with equipment in other
areas of the plant under other ProcessLogix controllers is not
uncommon.
Since ProcessLogix permits almost totally generalized
intercommunications paths, the two devices can be under or on:
1 . the same H1 link,
2. different links of the same 1757-FIM,
3. different 1757-FIMs in the same IO chassis,
4. different IO chassis of the same controller,
5. different controllers of the same server
As the configuration moves from 1, co-residency on the same H1 link,
to 2 to 3 to 4 to 5, more nodes and more networks get involved,
increasing the load on each node and network and adding additional
delays to the signals. Therefore, the interacting equipment should be
co-located in the pyramid when the plant instrumentation and control
networks are laid out. The number of communication circuits between
points of differing controllers should be small (less than 25% of the
total number of circuits.)
System Communications Limits

Communications limits are derived from various capacities. Common
constraints are described below.
Node Address Range Limits

Arbitrarily high limits on a network reduce effective bandwidth and
effect recovery time.
11-14
The maximum number of nodes permitted on the Supervisory

ControlNet (UMAX) is 24. This permits 10 redundant controllers,
1 redundant Server pair, plus 2 spare nodes.
The maximum number of nodes permitted on the Supervisory
Ethernet is 12. This permits 10 non-redundant controllers and 1
redundant Server pair.
The maximum number of nodes permitted on the I/O
ControlNet (UMAX) is 20. With the exception of planning for the
future upgrade of non-redundant controllers to redundant
controllers, unused node addresses may be utilized by Stations,
1757-FIM-Only Chassis, or other appropriate nodes.
Connection Limits
Processing power and memory are finite. CNB modules, for example,
are limited to 64 connections. The 1784-PCIC card is limited to 128
connections.
Node Processing Load Limits

Processing power of nodes of the network is finite. Usually the
highest node in the topology processes the most. A downlink CNB
module in a Controller Chassis can process I/O from 24 unscheduled
or 64 scheduled IOMs, requiring multiple CNBs when communicating
with more than 24 unscheduled. The multiple CNBs can be
configured in parallel to a single I/O Net or to physically separate I/O
Nets.
Communications Load Limits

Bandwidth of the network is finite. Some of this bandwidth must be
used for housekeeping functions. Message overhead also consumes
bandwidth.
Limits expressed herein are largely derived from the above types of
constraints.
11-15
Controller Communications
With the addition of the 1757-FIM, which uses CDA for
communications, the terms 1757-PLX52 Controller and CPM refer
not only to the CPM, but also to the 1757-FIM, if not explicitly noted.
For example, the Maximum Total Parameter Access Response Rate to
the Server from all Controllers combined is the total response rate
from all 1757-PLX52s and 1757-FIMs in the system combined.
Each 1757-PLX52 Controller can be the initiator of up to 5
peer-to-peer connections to other 1757-PLX52 Controllers.
Each 1757-PLX52 Controller can be the target of up to 5
peer-to-peer connections from other 1757-PLX52 Controllers.
Table 11.K 1757-PLX52 Controller Communications Performance
1757-PLX52 Controller Communications Performance
PPS = Average Parameters per Second
Overall Communications Performance per ProcessLogix Server
50 ms CEE
5 ms CEE
Maximum Total Parameter Access Response Rate to the Server from all 1757-PLX52s and
1757-FIMs Controllers combined.
4000 PPS
4000 PPS
Overall Communications Performance per 1757-PLX52/1757-FIM
50 ms CEE
5 ms CEE
Maximum Total Parameter Access Response Rate
2000 PPS
2000 PPS
1757-PLX52 to 1757-PLX52 peer to peer Communications Performance per 1757-PLX52 on

Supervisory Control Network
50 ms CEE
5 ms CEE
Maximum Initiator Node Pull/Get Request Rate to all target nodes.
500 PPS
500 PPS
(Includes Display updates, Fast/Slow History, Excel I/ODBC Exchange, and CB Monitoring)
Includes all Server Data Requests and peer communications, including other 1757-PLX52s and 1757-FIMs.
(Based on the number of requests for peer data and the peer update rate.)
The 1757-FIM from 1757-PLX52 is Pull and is fixed at 200ms. The 1757-PLX52 from 1757-FIM is
Pull and published on receipt by the 1757-FIM from FFD.
11-16
Table 11.K 1757-PLX52 Controller Communications Performance

1757-PLX52 Controller Communications Performance
1757-PLX52 to 1757-PLX52 Communications Performance per 1757-PLX52
50 ms
5 ms
Maximum Initiator Node Pull/Get Request Rate to all target nodes on ControlNet.
50 @ 100 ms
100 @ 200 ms
250 @ 500 ms
500 @ 1 sec
5 @ 10 ms
10 @ 20 ms
25 @ 50 ms
50 @ 100 ms
100 @ 200 ms
250 @ 500 ms
500 @ 1 sec
Maximum Initiator Node Pull/Get Request Rate to all target nodes on Ethernet.(1)
250 @ 500 ms
500 @ 1 sec
250 @ 500 ms
500 @ 1 sec
Maximum Target Node response Rate to Pull/Get Requests from all initiator nodes.
500 PPS
500 PPS
Maximum Initiator Node Push/Store Request Rate to all target nodes. (2) (3)
50 PPS
50 PPS
Maximum target node response rate to push/store Requests from all initiator nodes.(3)
50 PPS
50 PPS
Number of remote 1757-PLX52s that a 1757-PLX52 can initiate a peer connection with.
Excludes Exchange peer to peer.
Number of remote 1757-PLX52s that a 1757-PLX52 can receive a peer connection from.
Excludes Exchange peer to peer.
1757-PLX52 to PLC Peer-to-Peer Communications Capacity per 1757-PLX52
50 ms CEE
5 ms CEE
Maximum number of Exchange REQUEST blocks per 1757-PLX52
32
32
Maximum number of Exchange RESPONSE blocks per 1757-PLX52
32
32
Maximum number of target devices for REQUEST blocks per 1757-PLX52.
Maximum number of remote initializing devices for RESPONSE block data per 1757-PLX52.
Maximum number of DHRIO modules per 1757-PLX52
2 (local chassis
only)
1 DHRIO Module only counts as 1 Target Device even when communicating with multiple
PLCs on either DH+ network
(1)
Because Ethernet is inherently a non-deterministic network, no guarantees can be made about the timely delivery of critical data packets. The support of TCP/IP Ethernet as
the Supervisory network in ProcessLogix does not preclude the customer to design and configure a mission critical control strategy based upon Ethernet.
Ethernet is not a deterministic network. Consider these factors before employing a mission critical control strategy: Ethernet is subject to collisions, deferred transmissions, and
other anomalies, which may delay the arrival of critical data packets
Internal testing has shown that under a full load condition, approximately 1 in 30,000 peer fetches arrive at a peer node at greater than twice the configured peer update rate.
(2) Currently the SCM Step and the PUSH block are the only block types that can initiate peer push/store requests for 1757-PLX52 to 1757-PLX52 peer communications.
(3)
For Ethernet Supervisory LAN systems, the maximum store rate is 500 msec.
11-17
Controller Notifications
Table 11.L Controller Notifications Performance
1757-PLX52 and 1757-FIM Controller Notifications Performance
Maximum number of events(1) (burst condition)
50 events
Maximum number of event/second(1) (sustained)
2/sec
(1) Event burst will be throttled to one burst per minute to allow the server to process the previous burst. The
sustained rate may continue between bursts.
Controller Redundancy
ATTENTION
The Ethernet Modules cannot be used with

Controller Redundancy
Table 11.M Controller Redundancy (50 ms CEE only) Specifications

Controller Redundancy (50 ms CEE only)
Redundancy compliant devices
CNB
1757-PLX52
1757-SRM
1757-BEM
Non-redundancy compliant devices (cannot be introduced in a

redundant controller chassis)
1756 IOM
TC-MUX021
1757-PIM
1757-FIM
SST-PFB-CLX
Controller models supported
1757-PLX52 only
Control Processing Switchover Interruption Time
500 ms
Redundancy Module Cable Medium
Fiber Optic Cable
Redundancy Module Cable Lengths
1, 3, 10, 100 meters
Redundancy Module Slot Width
2 slots
Initial Synchronization Timer (from Sync Start to Completion)
90 sec
Maximum Elapsed Time Between Commanded Switchover and 120 sec

Completion of Initial Synchronization
Maximum Elapsed Time Between Switchover Due to Power
Cycle of the Primary and Completion of Initial Synchronization
150 sec
11-18
1757-PLX52 Resources
Table 11.N 1757-PLX52 Configuration Options
1757-PLX52 Configuration Options
1757-PLX52 Module Slot Width
2 slots
Base Execution Periods Supported

(different personalities required)
50 ms, 5 ms(2)
50 ms CEE
5 ms CEE
Controller Redundancy Supported
Yes
No
Remote I/O Supported
Yes
No
I/O Module Execution Period
50 ms
5 ms
Configurable Values for CM/SCM Execution Periods
50, 100, 200, 500, 1000,

2000 ms
5, 10, 20, 50, 100, 200 ms
Configurable Values of Peer Update Rates (period).

Defines the period at which data is updated for all pull/get requests for peer
data required by all blocks within a CEE.(1)
100, 200, 500, 1000 ms
10, 20, 50, 100, 200, 500,

1000 ms
(1) Supervisory Ethernet LAN systems only guarantee a Pull/Get Request Rate of 500 msec or greater. Faster Pull/Get rates can be configured, however, data arrival at the
configured rate cannot be guaranteed for rates faster than 500 msec.
(2) Different firmware is required for the 50ms and 5ms CEEs.
Table 11.O 1757-PLX52 Processing Resources

1757-PLX52 Processing Resources
Definitions:
PU = Processing Unit. The PU represents a platform independent amount of processing resources (time) required to complete a predefined
amount of computational (control) work.
Maximum Cycle Loading: Over any cycle (0-39), the Average CPU Used (CPUCYCLEAVG) statistic is not to exceed the stated maximums.
Minimum Reserved CPU to be Maintained During Runtime (CPUFREEAVG)
20%
1757-PLX52 Configuration
PU Maximum
Maximum Cycle
Loading
50 ms CEE Non-Redundant Configuration
3600 PU/sec
60%
50 ms CEE Redundant Configuration
1600 PU/sec
60%
5 ms CEE (Non-Redundant only)
2400 PU/sec
40%
Table 11.P 1757-PLX52 Memory Resources and Block Configuration

1757-PLX52 Memory Resources and Block Configuration
Definition: MU = Memory Unit = 1 Kbyte = 1024 bytes
Maximum Available 1757-PLX52 Memory Resources
4000 MU
Maximum Total Number of CMs, SCMs and IOMs Configurable per 1757-PLX52
1000
Maximum Number of Component Blocks per CM
40
Maximum Total Number of Steps and Transitions

(in all handlers) per SCM
160
(80 Step/Transition pairs)
11-19
Table 11.Q Typical IOM/CM/SCM Processing and Memory Resource Requirements

Typical IOM/CM/SCM Processing and Memory Resource Requirements
Total Processing Resources (PU/sec)
Typical Module Types

(FB Content in Parenthesis)
Processing Resource Consumption (PU/module execution)

Execution Period (sec/module execution)
Processing Resource Consumption

(Per Module)
Memory
Resource
Usage
50/5 ms CEE Non-Redundant

(PU/Module Execution)
50 ms CEE Redundant
(PU/Module Execution)
50/5 ms CEE
(MU/Mod)
Typical I/O Module

(Average consumption of available IOMs)
0.3
0.19
0.6
Analog Digital Acquisition Module

(10 AI, 10 DataAcq FBs)
2.9
3.8
7.4
Small Analog Data Acquisition Module

(1 AI, 1 DataAcq FB)
0.47
0.43
1.0
Regulatory Control Module

(1 AI, 1 DataAcq, 1 PID, 1 AO, 6 Logic FBs)
2.8
2.8
3.9
Auxiliary Function Module

(10 Aux. FBs, such as AuxCalc, Totalizer)
4.2
5.1
13.1
Digital Data Acquisition Module

(10 DI, 10 Flag FBs)
1.2
1.2
3.1
Small Digital Data Acquisition Module

(1 DI, 1 Flag FBs)
0.22
0.14
0.6
Device Control Module

(2 DI, 2 DO, 1 DevCtl, 5 Logic FBs)
1.3
1.3
3.1
Logic Control Module

(20 Logic FBs)
1.0
1.0
3.5
Sequence Control Module A(1)
2.0
3.0
28.9
Sequence Control Module B(2)
2.0
3.0
35.7
Sequence Control Module with an alias table of size 45

rows by 100 columns(3)
2.0
3.0
128.5
Sequence Control Module with an alias table of size 500

rows by 9 columns(4)
2.0
3.0
124.5
These Block Libraries will consume the following extra memory when the first block is loaded to the 1757-PLX52 Controller:
EXCHANGE 70 MUs
1757-PIM 100 MUs
1797-FLEX EX + 1794- FLEX I/O 125 MUs

FBUSIF 90 MUs
(1)
1 each of Main, Hold, Stop and Abort Handlers, 10 Steps with 8 Outputs each, 10 Transitions with 5 Conditions each, 10 Recipe items, 5 History items. SCM has a total of 10
Steps and 10 Transitions among the 4 Handlers.
(2)
1 Main Handler, no other Handlers, 20 Steps with 4 Outputs each, 20 Transitions with 3 Conditions each, 10 Recipe items, 5 History items. SCM has a total of 20 Steps and
20 Transitions.
(3) 1 each of Main, Hold, Stop and Abort Handlers, 10 Steps with 8 Outputs each, 10 Transitions with 5 Conditions each interspersed in all handlers, 10 Recipe items, 5 History
items. SCM has a total of 10 Steps and 10 Transitions among the 4 Handlers.
(4)
1 each of Main, Hold, Stop and Abort Handlers, 10 Steps with 8 Outputs each, 10 Transitions with 5 Conditions each interspersed in all handlers, 10 Recipe items, 5 History
items. SCM has a total of 10 Steps and 10 Transitions among the 4 Handlers.
11-20
I/O Performance and

Capacity Specifications
Every I/O device presents a load on the 1757-PLX52 system

performance by utilizing I/O network bandwidth and 1757-PLX52
memory and CPU resources.
Many of these constraints are measured in I/O Units, which is a
generic loading definition used to normalize the load among the many
different I/O devices and families supported.
Refer to Table 11.R I/O Unit Load Constraints on page 11-20 for the
I/O unit load assigned to various devices and modules. By following
these configuration constraints, you can prevent the 1757-PLX52 from
being overloaded and increase the ability for the 1757-PLX52 to
operate correctly.
Table 11.R I/O Unit Load Constraints
I/O Device or Module
I/O Units
1 1756/1757 chassis mounted I/O Module
1 1794 FLEX I/O or 1797 FLEX EX rail mounted I/O Module 1

1 1757-SIM FTA
1 1788-CN2FF, Foundation Fieldbus Linking Device
1 1757-FIM, Fieldbus Interface Module
1 DHRIO Module
1 SST-PFB-CLX Profibus Module
2 (for 64 Unit/CPM Limit)

6 (for 24 Unit/CNB Limit)
1 1756-DNB, DeviceNet Interface Module
Table 11.S I/O Module Capacity

I/O Module and Fieldbus Capacity
50 ms CEE
5 ms CEE
Maximum Number of I/O Units per 1757-PLX52

Refer to Table 11.R I/O Unit Load Constraints on page 11-20 for I/O unit definitions.
64
12
(local 1757/1756 I/O only)
Maximum Number of Remote I/O Chassis + 1757-FIM-Only Chassis+Remote Mixed

Chassis + 1794/1797-ACNR15s (combined) per 1757-PLX52.
0
Maximum Number of I/O units per Downlink 1756-CNB

Refer to Table 11.R I/O Unit Load Constraints on page 11-20 for I/O unit definitions.
64 scheduled
0
24 unscheduled
Maximum number of Downlink 1756-CNBs per Controller Chassis
0
(local I/O only)
Maximum number of DHRIO modules per 1757-PLX52
2 (local chassis only)
Serial Interface Module (TC-MUX021) related only
50ms CEE
5ms CEE
Maximum Number of Serial Interface Modules per 1757-PLX52
Maximum Number of FTA assemblies per Serial Interface Module (TC-MUX021)
Each FTA connected counts as 4 I/O units in the 64 I/O units per 1757-PLX52 and
the 24 I/O units per 1756-CNB calculation above.
11-21
Table 11.S I/O Module Capacity

1788-CN2FF related only
50ms CEE
5ms CEE
Maximum number CN2FFs per 1757-PLX52
Not Supported
Maximum number CN2FFs per Non-Redundant Server
Not Supported
Maximum number CN2FFs per Redundant Server (NI-FBUS Service and NI Configurator
must be run on the Backup Server only)
48
Not Supported
Maximum number CN2FFs per NI Configurator Project
Not Supported
Maximum Number of H1 segments per CN2FF
Not Supported
Maximum number of Foundation Fieldbus Devices per H1 segment connected to a

CN2FF.
10
Not Supported
1757-FIM Related Only
50ms CEE
5ms CEE
Maximum number 1757-FIMs per 1757-PLX52
21
Not supported
Maximum number 1757-FIMs per Server (Redundant or Non-Redundant)
100
Not Supported
Maximum number of H1 segments per 1757-FIM
Not supported
Maximum number of FF Devices per H1 segment connected to a 1757-FIM.

(other constraints may be encountered before this constraint)
16
Not Supported
Configurable Values for FF function block Execution Periods. (Since 250 ms period is not
compatible with the CMs 200 ms period, it should only be used for control if the entire
loop is resident on a Fieldbus link.)
250, 500, 1000,

2000, 4000 ms
Not Supported
Profibus Interface-Related Only
50 ms CEE
5 ms CEE
Maximum number of PFB Modules per 1757-PLX52
10
Maximum number of PFB Modules per downlink CNB (based on update rate, 25ms
default)
4 @ 25 ms
2 @ 12.5 ms
Not Supported
Each Linking Device counts as 1 I/O unit in the 64 I/O units per 1757-PLX52
calculation above.
Each 1757-FIM counts as 3 I/O units in the 64 I/O units per 1757-PLX52
calculation above.
11-22
PROFIBUS DP Capacity and Topology Specifications

The following PROFIBUS specifications are independent of the
interface to ProcessLogix:
PROFIBUS DP supports a maximum of 126 station addresses,
including, masters, slaves and active repeaters.
The maximum number of entries in the PBIM configuration
table is 100.
Table 11.T Profibus Capacity/Topology Specifications

PFB Module and PROFIBUS Block Specifications
Note: The PROFIBUS interface module hardware component is the SST-PFB-CLX, and is referred to herein as the PFB Module. This device
acts as the master on the PROFIBUS-DP network. Each PFB module is represented as a block in the CEE, which is referred to as the
PROFIBUS Interface Module Block (PBIM).
PROFIBUS Communication Profiles Supported
DP (only)
PROFIBUS Baud Rates Supported
12 MBps, 6 MBps, 3 MBps, 1.5 MBps, 500 KBps, 187.5 KBps,

93.75 KBps, 19.2 KBps, 9.6 KBps,
Support for Multi-Master Configurations
Yes
Support for PROFIBUS Slave Diagnostics
No
Valid PROFIBUS Station address range
0 - 125
Maximum number of modules per PBIM block (identified by a unique

station/module number combination)
100
Maximum Input Data Size per PFB Module

(all slave stations)
496 bytes
(valid range = 4-499)
Maximum Output Data Size per PFB Module

(all slave stations)
492 bytes
(valid range = 4-495)
PROFIBUS Device Profiles Supported

(with custom function blocks)
PROFIDRIVE, Encoder
Devices supported with custom function blocks
Siemens Simatic
ET200M I/O, Siemens Simocode 3UF5 Motor Protection and
Control Unit
Data types supported by the Generic PROFIBUS Channel Blocks(1)
Single bit (Discrete),

8 bit signed/unsigned integer,
16 bit signed/unsigned integer,
32 bit signed integer
(1)
The generic function blocks are capable of communicating with various PROFIBUS devices. The data types required/supplied by the device are a consideration in the
determination of whether or not a specific device can be used with these blocks.
11-23
FIM Performance Limits

The FIM is a complex device interfacing the high-speed ProcessLogix
internal networks to the 31.25 Kbps FF H1 links. It uses an advanced
caching scheme to maintain quick response to reasonably fresh values
and maintains communications with the multiple FF devices as time
permits in the prioritized scheme of the Link Schedule based on FF
specification requirements. This table describes limits of performance
through the FIM.
The FIM cache (one for both links) holds 800 items. An item can be:
A simple parameter
A structured parameter
An arrayed parameter
Quality of service is based on priorities (highest to lowest).
Incoming H1 Subscriptions and outgoing H1 Publications, per
LAS
H1 Alerts
H1 Writes
New H1 reads (and re-written parameters)
H1 Re-reads to refresh the cache
Table 11.U 1757-FIM Performance Limits
FIM Performance Limits
Per FIM
Per Link
Per Device
Burst
Sustained
Burst
Sustained
Burst
Sustained
H1 Link Publication Rate (parameters/second, pps)
---
32(1)
---
16(1)
---
16(1)
Client-Server Store Rate(1) (pps) [excludes publications from

ProcessLogix function blocks]
40
10(5)
20
5(5)
1(5)
Max number of slow history points.(1)
---
40
---
20(6)
---
20(6)
Max number of read-activities per second. (1)

A read-activity includes any or all of a block view list parameters or
a single non-viewed parameter.
Includes all users such as slow history, SCM connections to
non-published parameters, Excel or OPC reads of non-published
parameters, etc.
10
10
Maximum number of parameters read per second. (1)(2)

Includes all users such as CM connections to non-output
parameters (e.g. tuning constants or limits),
SCM connections to non-published parameters, Excel or OPC reads
of non-published parameters, etc.
80
80
40
40
16
16
Maximum Alert Rate per second. (Alarm and Return-to-Normal

reports) (1)(3)
50
50
Maximum Number of Devices
32(4)
(1) Assumes
16
---
50% of link schedule is usable for client-server messaging.
(2) Assumes all parameters read are in view lists and the average number of parameters read and used per view is 8.
11-24
(3)
Bursts are up to one minute apart.
(4)
These numbers may be further limited by other restrictions noted in this document.
(5)
This assumes that the FF device supports AlterEventConditionMonitoring, the ability to suppress Update Events. Otherwise reduce by factor of 2.
(6)
All parameters must be in one view list per device or published.
FIM Display-related Performance Limits

The following table gives performance guidelines for the display of
tabs on the FF Block Detail Display Form, which obtains its data
through the FIM and H1 links:
Table 11.V FF Block Detail Display Form Performance (per tab, 40 parameters)
Performance
Distribution
Call-up rate, sec

100% Contained in
View Lists
Call-up rate, sec

0% Contained in
View Lists
Refresh rate, sec

100% Contained
in View Lists
Refresh rate, sec

0% Contained in
View Lists
80% (average)
10
10% (slow)
16
16
10% (worst)
20
10
20
Assumptions:
At least 50% of the link schedule must be available and usable
for client-server transactions.
No more than 40 non-viewed-contained parameters appear on a
display tab at once. (This is provided by FLM.)
No more than one new tab is called up for devices on the same
link within 10 seconds of each other.
No more than four tabs are being refreshed from device on the
same link simultaneously.
The 80%-10%-10% specification is intended to allow that, in
consideration of the many factors that influence link throughput,
over the long-term (say, 1000 call-ups), 80% or more will meet
or exceed the average number, 90% (additional 10%) or more
will meet or exceed the slow spec, and 100% (additional 10%) or
more will meet or exceed the worst spec.
11-25
I/O Module Publication Periods

Table 11.W I/O Module Publication Period Specifications
Input Module types
Publication Period
Typical Input Module

Includes 1757/1756, 1797-FLEX Ex and 1794-FLEX I/O input modules, and CN2FFs with exceptions
noted below
25 ms
High Density / Non-Isolated Analog Input Module (1756-IF16)
250 ms
RTD Module (1756-IR6I)
50 ms
Thermocouple Module (1756-IT6I)
50 ms
Serial Interface Module (TC-MUX021)
250 ms
Digital Input Module used by 5 ms CEE (local only)
1 ms
For CMs which contain associated input channels, it is recommended that the CM execution period should be set to at least double the
input module sampling period.
Output Module Type
Publication Period
Typical Output Module

1757/1756,1797-FLEX EX, and 1794-FLEX I/O Output Modules
50 ms
Input/Output Module Type
Publication Period
PFB Module (SST-PFB-CLX)

Note: Update rate is configurable on the PBIM block.
Default = 25 ms
Minimum =
12.5 ms (remote chassis)
5 ms (local chassis)
Maximum = 50 ms
The following paragraphs describe known problems and limitations

found in this release.
Device Control May Generate Nuisance Alarms

Er r or In dication : DevCtl generates a Command Disagree alarm that
returns to normal at the same time.
Descr iption : Problem occurs when a DevCtl block is commanded to
different states very quickly, i.e. as soon as the DevCtl PV feedback
reaches the first OP state commanded, then a different OP command
is provided. When this different state command after a previous
command happens along with a) the internal DevCtl Command
Disagree timer expiring, and b) PV changing to the previous
commanded state during the same execution cycle of the DevCtl, then
the nuisance alarm will be generated.
Recover y: Nuisance Command Disagree alarm can safely be ignored.
11-26
Migration Consideration
In R510.0, every ProcessLogix function block uses 4 bytes of memory
more than that it used in earlier versions of ProcessLogix. As a result,
the CPM memory usage of the same control strategy would be more
in R510.0 than that in pre-R510.0 release. Roughly speaking, the
increase in memory can be calculated as follows:
Additional Memory Needed = (Number of IOMs + Number of SCMs +
Number of CMs + Number of all CM and SCM contained blocks) * 4
bytes
Enough spare memory that would accommodate this increase must be
available in existing controllers for migration to R510.0 to work.
ERDB is Master for Configuration Data in R510.0

As of R500.0, the Engineering Repository Data Base is considered to
be the master for configuration data for Server's ProcessLogix
configuration data. This includes a ProcessLogix point's history, trend,
and group configuration data.
If a change is made to this Server data from Station, the customer
needs to upload each ProcessLogix point that had a configuration
change to the Engineering Repository using the Control Builder
Possible Loss of Communication with CPM

Er r or In dication : Unable to communicate with the CPM. From the
CPM front panel display, either the alphanumeric display's
illumination varies or the Health LED is solid red.
Descr iption : In a redundant controller system, the new primary CPM
infrequently may become mute or hard fault (i.e. Health LED is solid
red) under stress test conditions involving both (1) a non-trivial
number of repetitive switchovers and (2) I/O configured in the
controller that is not physically present.
Recover y: Power-cycle the mute or faulted primary controller.
Wor kar oun d: Avoid operator induced redundant controller
switchovers with I/O that is configured but not physically present.
How Are We Doing?

Your comments on our technical publications will help us serve you better in the future.
Thank you for taking the time to provide us feedback.
You can complete this form and mail it back to us, visit us online at www.ab.com/manuals, or
email us at RADocumentComments@ra.rockwell.com
Pub. Title/Type ProcessLogix R510.0 Installation and Upgrade Guide
Cat. No.
1757-SWKIT5100
Pub. No.
1757-IN510A-EN-P
Pub. Date October 2003
Part No.
957824-79
Please complete the sections below. Where applicable, rank the feature (1=needs improvement, 2=satisfactory, and 3=outstanding).
Overall Usefulness
Completeness
(all necessary information
is provided)
Technical Accuracy
(all provided information
is correct)
How can we make this publication more useful for you?
Can we add more information to help you?
Clarity
1
(all provided information is
easy to understand)
Other Comments
Your Name
procedure/step
illustration
feature
example
guideline
other
explanation
definition
Can we be more accurate?

text
illustration
How can we make things clearer?
You can add additional comments on the back of this form.
Location/Phone
Your Title/Function
Would you like us to contact you regarding your comments?

___No, there is no need to contact me
___Yes, please call me
___Yes, please Email me at __________________________
___Yes, please contact me via ________________________
Return this form to:
Allen-Bradley Marketing Communications, 1 Allen-Bradley Dr., Mayfield Hts., OH 44124-9705

Phone: 440-646-3176 Fax: 440-646-3525 Email: RADocumentComments@ra.rockwell.com
Publication ICCG-5.21- January 2001
PN 955107-82
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEASE FOLD HERE
NO POSTAGE
NECESSARY
IF MAILED
IN THE
UNITED STATES
BUSINESS REPLY MAIL

FIRST-CLASS MAIL PERMIT NO. 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DR
MAYFIELD HEIGHTS OH 44124-9705
PLEASE REMOVE
Other Comments
Publication 1757-IN510A-EN-P - October 2003 2
PN 957824-79
Copyright 2003 Rockwell Automation, Inc. All rights reserved. Printed in the U.S.A.
Installation Instructions

1757 In510 - en P

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1757 In510 - en P

Uploaded by

Copyright:

Available Formats

ProcessLogix

Important User Information

Solid state equipment has operational characteristics differing from those of

Identifies information about practices or circumstances

Identifies information about practices or circumstances

Identifies information that is critical for successful

Our Assumptions About Users . . . . . . . . . . . . . . . . .

Operating System Support . . . . . . . . . . . . . .

Clean System Windows 2000 Server Installation . . . . . . . . .

Publication 1757-IN510A-EN-P - October 2003

Modifying Windows XP. . . . . . . . . . . . . . . . . . . . . . . .

ProcessLogix Software Installation on a Clean PC . . . . . . .

Publication 1757-IN510A-EN-P - October 2003

ProcessLogix Server Upgrade Scenarios . . . . . . . . . . . . . . . 4-1

Restoring the ProcessLogix Server Points Database . . .

Publication 1757-IN510A-EN-P - October 2003

Changing Hosts File Entries . . . . . . . . . . . . . . . . . . .

Adding Redundancy to R510.0 Non-Redundant

1784-PCIC Driver Installation . . . . . . . . . . . .

Publication 1757-IN510A-EN-P - October 2003

Important Usage Considerations . . . . . . . . . . . . . . . . . . 7-8

Publication 1757-IN510A-EN-P - October 2003

Stopping ProcessLogix Applications and Services . . . . . . . . 8-1

Changing the Computer Name on a Windows XP Client 8-24

Major ProcessLogix Engineering Tools Software

Server/Client Performance and Capacity. . . . . . . .

Publication 1757-IN510A-EN-P - October 2003

System Communications Limits. . . . . . . . . . . . . . . . .

Publication 1757-IN510A-EN-P - October 2003

Our Assumptions About

Before configuring a ProcessLogix system you must:

If you have not received ProcessLogix R510.0

Starting Conditions and Assumptions

Publication 1757-IN510A-EN-P - October 2003

You must be certain that your PC meets the hardware requirements

ProcessLogix R510.0 Server Software must be installed on a PC that is

The following software and documentation components are included

Publication 1757-IN510A-EN-P - October 2003

ProcessLogix R510.0 Base Software CD

ProcessLogix R510.0 Application Software CD

ProcessLogix R510.0 Supplemental Software CD

ProcessLogix Knowledge Builder CD

ProcessLogix R510.0 Installation and Upgrade Guide

ProcessLogix Online Help/Knowledge Builder

ProcessLogix R510.0 Installation and Upgrade Guide

New Functions and Features

Major ProcessLogix Software Components

Performance and Capacity Specifications

Publication 1757-IN510A-EN-P - October 2003

Removing the Default

If this is the first startup since the operating system

Rockwell Automation provides technical information on the web to assist you

New Product Satisfaction Return

Contact your distributor. You must provide a Customer Support case

Please contact your local Rockwell Automation representative for

Your Questions or Comments about This Manual

Publication 1757-IN510A-EN-P - October 2003

Terms and Type Representations

Table P.3 : Terms and Type Representations

Click left mouse button once. (Assumes cursor is positioned

Click left mouse button twice in quick succession. (Assumes

Double-click the Station icon.