Rockwell Automation 1757-SWKIT5100 User Manual
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
!
IMPORTANT
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
Identifies information that is critical for successful
application and understanding of the product.
Table of Contents
Preface
ProcessLogix R510.0 Installation
Introduction
Our Assumptions About Users . . . . . . . . . . . . . . . . . . Preface-1
Starting Conditions and Assumptions . . . . . . . . . . Preface-1
Minimum Hardware Requirements. . . . . . . . . . . . . . . Preface-2
Contents of Release. . . . . . . . . . . . . . . . . . . . . . . . . . Preface-2
ProcessLogix Online Help/Knowledge Builder . . . Preface-3
ProcessLogix R510.0 Installation and
Upgrade Guide . . . . . . . . . . . . . . . . . . . . . . . . . . Preface-3
Removing the Default Startup Screens . . . . . . . . . . . . Preface-4
Rockwell Automation Support . . . . . . . . . . . . . . . . . . Preface-4
New Product Satisfaction Return. . . . . . . . . . . . . . Preface-4
Your Questions or Comments about This Manual . Preface-4
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preface-5
Terms and Type Representations . . . . . . . . . . . . . Preface-5
Checklists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preface-5
Acronyms and Abbreviations . . . . . . . . . . . . . . . . . . . Preface-6
Chapter 1
Operating System Support . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Operating System Options. . . . . . . . . . . . . . . . . . . . . . . . . 1-1
ProcessLogix Server Supported Installations . . . . . . . . . . . . 1-2
ProcessLogix Client Supported Installations . . . . . . . . . . . . 1-4
Operating System Installation
Procedures
Chapter 2
Clean System Windows 2000 Server Installation . . . . . . . . . 2-2
Installing Windows 2000 Server on a New System . . . . . 2-2
Starting the Windows 2000 Server Installation
from the Boot Floppies . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Starting the Windows 2000 Server Installation
from the CD-ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Completing the Windows 2000 Server Installation . . . . . 2-5
PC Naming Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Clean System Windows 2000 Professional Installation . . . . . 2-11
Installing Windows 2000 Professional on a New System 2-11
Creating Windows 2000 Professional Boot Floppies. . . . 2-12
Starting the Windows 2000 Professional Installation
from the Boot Floppies . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Starting the Windows 2000 Professional Installation
from the CD-ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Completing the Windows 2000 Professional Installation. 2-14
Clean System Windows XP Professional Installation . . . . . . 2-18
Installing Windows XP Professional on a New System . . 2-18
Starting the Windows XP Installation from the CD-ROM 2-19
Completing the Windows XP Professional Installation . . 2-20
Upgrading Windows 2000 Professional to XP Professional . 2-24
Creating the ProcessLogix User Accounts . . . . . . . . . . . . . . 2-26
Creating the ps_user and erserver accounts. . . . . . . . . . 2-26
i Publication 1757-IN510A-EN-P - October 2003
Table of Contents ii
Modifying Windows XP. . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28
Windows 2000 Service Pack 4 Installation . . . . . . . . . . . . . 2-29
Checking for Windows 2000 Service Pack 4 . . . . . . . . . 2-29
Installing Windows 2000 Service Pack 4 . . . . . . . . . . . . 2-30
Windows Security Hotfix Installation . . . . . . . . . . . . . . . . . 2-31
Installing Windows 2000 Security Hotfix . . . . . . . . . . . . 2-31
Installing Windows XP Security Hotfix . . . . . . . . . . . . . 2-32
Internet Explorer 6.0 SP1 Installation . . . . . . . . . . . . . . . . . 2-33
Checking the Internet Explorer Version. . . . . . . . . . . . . 2-33
Installing Internet Explorer 6.0 SP1 . . . . . . . . . . . . . . . . 2-35
Updating Windows Installer. . . . . . . . . . . . . . . . . . . . . . . . 2-36
Updating ISScript . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37
Additional Operating System Customization Procedures . . . 2-38
Adjusting the Video Settings . . . . . . . . . . . . . . . . . . . . 2-38
Setting Up Additional Drivers . . . . . . . . . . . . . . . . . . . . 2-39
Other Required System Settings . . . . . . . . . . . . . . . . . . 2-39
Creating Emergency Repair Disks . . . . . . . . . . . . . . . . . . . 2-40
Windows 2000. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-40
Windows XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-40
ProcessLogix Server Installation
Procedures
Chapter 3
ProcessLogix Software Installation on a Clean PC . . . . . . . . 3-1
Installing ProcessLogix R510.0 Software . . . . . . . . . . . . . . . 3-2
Installing ProcessLogix Product. . . . . . . . . . . . . . . . . . . 3-4
Installing SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Installing Knowledge Builder . . . . . . . . . . . . . . . . . . . . 3-6
Installing RSLinx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Installing Engineering Tools . . . . . . . . . . . . . . . . . . . . . 3-8
Installing Active X Components . . . . . . . . . . . . . . . . . . 3-8
Installing the ProcessLogix Server . . . . . . . . . . . . . . . . . 3-9
Installing ProcessLogix Update . . . . . . . . . . . . . . . . . . . 3-12
Moving the RSLinx Activation File . . . . . . . . . . . . . . . . . . . 3-14
About the Activation File . . . . . . . . . . . . . . . . . . . . . . . 3-14
Determining the Current RSLinx Version . . . . . . . . . . . . 3-14
Installing the Activation File . . . . . . . . . . . . . . . . . . . . . 3-15
Configuring RSLinx Drivers for ControlNet
Supervisory Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Updating the 1784-PCIC Firmware . . . . . . . . . . . . . . . . 3-17
Configuring RSLinx Drivers for Ethernet
Supervisory Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
Completing the ProcessLogix R510.0 Install on a
Non-Redundant Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
Upgrading Hardware Component Firmware . . . . . . . . . 3-20
Checking Control Builder Operation and Logging On . . 3-20
Backing Up a ProcessLogix Server Hard Drive to Tape . 3-21
Creating an Emergency Repair Disk . . . . . . . . . . . . . . . 3-21
Publication 1757-IN510A-EN-P - October 2003
ProcessLogix Server Upgrade
Procedures
Table of Contents iii
Chapter 4
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
Verifying and Finalizing Component Removal . . . . . . . . 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
Publication 1757-IN510A-EN-P - October 2003
Table of Contents iv
ProcessLogix Client Installation
and Upgrade Procedures
Restoring the ProcessLogix Server Points Database . . . . 4-39
Upgrading Hardware Component Firmware . . . . . . . . . 4-40
Reloading Controllers. . . . . . . . . . . . . . . . . . . . . . . . . . 4-41
Backing Up a ProcessLogix Server Hard Drive to Tape . 4-41
Chapter 5
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
R510.0 Windows XP Professional Client . . . . . . . . . . . . 5-9
Upgrade R400.0 SP2 Windows 2000 Professional Client to
R510.0 Windows XP Professional Client . . . . . . . . . . . . 5-9
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
Publication 1757-IN510A-EN-P - October 2003
Additional Redundant Server
Procedures
Table of Contents v
Changing Hosts File Entries . . . . . . . . . . . . . . . . . . . . . 5-26
Station Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29
Creating Emergency Repair Disks . . . . . . . . . . . . . . . . . 5-34
Checking Control Builder Operation and Logging On . . 5-34
Chapter 6
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
Firmware Maintenance
Procedures
Chapter 7
1784-PCIC Driver Installation . . . . . . . . . . . . . . . . . . . . . . . 7-1
Install Hardware Device Drivers . . . . . . . . . . . . . . . . . . 7-1
Verify the 1784-PCIC Driver Version . . . . . . . . . . . . . . . 7-2
1784-PCIC Firmware Installation . . . . . . . . . . . . . . . . . . . . 7-3
Upgrading Hardware Component Firmware . . . . . . . . . . . . 7-4
About Firmware Upgrades . . . . . . . . . . . . . . . . . . . . . . 7-4
Firmware Revision Level Reference . . . . . . . . . . . . . . . . . . 7-5
Publication 1757-IN510A-EN-P - October 2003
Table of Contents vi
Supplementary Procedures
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
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
Verifying and Finalizing Component Removal . . . . . . . . 8-20
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
Publication 1757-IN510A-EN-P - October 2003
New Functions and Features
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
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
ProcessLogix DeviceNet Wizard. . . . . . . . . . . . . . . . . . . . . 9-1
1757-ABRIO Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
New PLX Function Blocks . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
RSView Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
Additional Module Support . . . . . . . . . . . . . . . . . . . . . . . . 9-3
Major ProcessLogix Software
Components
Performance and Capacity
Specifications
Chapter 10
Major ProcessLogix Engineering Tools Software
Revisions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1
Major ProcessLogix Server Software Revisions . . . . . . . . 10-2
Embedded Software Components . . . . . . . . . . . . . . . . . 10-3
External, Third Party Qualified Software Components . . 10-4
Miscellaneous SCADA Component Revisions. . . . . . . . . 10-6
Chapter 11
Server/Client Performance and Capacity. . . . . . . . . . . . . . . 11-1
PC Platform Requirements . . . . . . . . . . . . . . . . . . . . . . 11-1
Server Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2
Platform System Configuration Definitions . . . . . . . . . . 11-2
Client Platform Requirements . . . . . . . . . . . . . . . . . . . . 11-3
Application Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4
User Interface Capacity and Performance . . . . . . . . . . . 11-7
Control Builder Considerations . . . . . . . . . . . . . . . . . . . 11-8
Server Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-9
Client/Server Communication Capacity . . . . . . . . . . . . . 11-9
Server Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . 11-10
Server Data Access. . . . . . . . . . . . . . . . . . . . . . . . . . . 11-10
Controller and Communications Capacity and
Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-11
Control Network Capacity . . . . . . . . . . . . . . . . . . . . . 11-11
System Communications Load Philosophy and
Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-12
Publication 1757-IN510A-EN-P - October 2003
Table of Contents viii
System Communications Limits. . . . . . . . . . . . . . . . . . 11-13
Controller Communications . . . . . . . . . . . . . . . . . . . . 11-15
Controller Notifications . . . . . . . . . . . . . . . . . . . . . . . 11-17
Controller Redundancy. . . . . . . . . . . . . . . . . . . . . . . . 11-17
1757-PLX52 Resources . . . . . . . . . . . . . . . . . . . . . . . . 11-18
I/O Performance and Capacity Specifications . . . . . . . . . . 11-20
PROFIBUS DP Capacity and Topology Specifications. . 11-22
FIM Performance Limits . . . . . . . . . . . . . . . . . . . . . . . 11-23
FIM Display-related Performance Limits . . . . . . . . . . . 11-24
I/O Module Publication Periods . . . . . . . . . . . . . . . . . 11-25
Special Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . 11-25
Device Control May Generate Nuisance Alarms. . . . . . 11-25
Migration Consideration . . . . . . . . . . . . . . . . . . . . . . . 11-26
ERDB is Master for Configuration Data in R510.0. . . . . 11-26
Possible Loss of Communication with CPM . . . . . . . . . 11-26
Publication 1757-IN510A-EN-P - October 2003
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.
1 Publication 1757-IN510A-EN-P - October 2003
Preface 2
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
Contents of Release
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.
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
ProcessLogix R510.0 Application Software CD
• ProcessLogix Engineering Tools
• ProcessLogix Server Software
• RSLinx 2.41
ProcessLogix R510.0 Supplemental Software CD 957824-83
ProcessLogix Knowledge Builder CD 957824-84
957859-46
957824-82
Publication 1757-IN510A-EN-P - October 2003
ProcessLogix R510.0 Installation and Upgrade Guide 957824-79
Preface 3
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
ProcessLogix’s software programs. Knowledge Builder’s 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.
ProcessLogix R510.0 Installation and Upgrade Guide
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
9 New Functions and Features
10 Major ProcessLogix Software Components
11 Performance and Capacity Specifications
Publication 1757-IN510A-EN-P - October 2003
Preface 4
Removing the Default Startup Screens
Rockwell Automation Support
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 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.
Publication 1757-IN510A-EN-P - October 2003
Preface 5
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 /Typ e
Representation
click Click left mouse button once. (Assumes cursor is positioned
double-click Click left mouse button twice in quick succession. (Assumes
right-click Click right mouse button once. (Assumes cursor is positioned
drag Press and hold left mouse button while dragging cursor to
select Click to highlight a menu item or list choice. Select Configure Allen-Bradley drivers from the
check/uncheck Click to activate/deactivate a checkbox. Check the Do not show this dialog again
Meaning Example
Click Browse.
on object or selection.)
Double-click the Station icon.
cursor is positioned on object or selection.)
Right-click the AND function block.
on object or selection.)
Drag the PID function block onto the Control
new screen location and then release the button. (Assumes
cursor is positioned on object or selection to be moved.)
Drawing.
list box.
checkbox.
File ⇒ New
expand Click the + to the left of a given item /folder to show its
<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<.
Shows nested menu selections as menu name followed by
menu selection.
contents.
Click File ⇒ New to start new drawing.
Expand Local Users and Groups.
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.
Publication 1757-IN510A-EN-P - October 2003
Preface 6
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
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
SCADA — Supervisory Control and Data Access
Publication 1757-IN510A-EN-P - October 2003
Chapter
1
ProcessLogix R510.0 Installation Introduction
Operating System Support
Operating System Options
The following table shows the supported operating systems for
ProcessLogix.
Table 1.A ProcessLogix Component Configuration Table
ProcessLogix R510.0 Windows 2000 Windows XP
Professional
Server Professional
Server
Client
(1)
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.
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.
page Preface-2.
✔
(1)
✔
Refer to Minimum Hardware Requirements on
✔ ✔
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 Publication 1757-IN510A-EN-P - October 2003
1-2 ProcessLogix R510.0 Installation Introduction
ProcessLogix Server Supported Installations
IMPORTANT
IMPORTANT
If you purchased a new ProcessLogix R510.0 Server
from Rockwell Automation, the operating system and
ProcessLogix software have already been installed.
Do not r einstall the softw are. 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.
A 1784-PCIC or Ethernet card must already be
installed in the ProcessLogix Server(s).
Publication 1757-IN510A-EN-P - October 2003
ProcessLogix R510.0 Installation Introduction 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.
Upgrade from R500.1, Option 1
1. Backup your data.
2. Complete a clean install.
Upgrade from R500.1, Option 2
1. Backup your data.
2. Uninstall your current ProcessLogix software.
3. Install ProcessLogix R510.0.
Upgrade from R400.0 SP2, Option 1
1. Backup your data.
2. Complete a clean install.
Upgrade from R400.0 SP2, Option 2
1. Backup your data.
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.
ProcessLogix Software Installation
on a Clean PC on page 3-1.
Option 1: Upgrading R500.1 Server
to R510.0 - Clean Install on page
4-1.
Option 2: Upgrading R500.1 Server
to R510.0 on page 4-2.
Option 1: Upgrading R400.0 SP2
Server to R510.0 - Clean Install on
page 4-3.
Option 2: Upgrading R400.0 SP2
Server to R510.0 on page 4-4.
Upgrade R320.0 Server to R510.0
on page 4-5.
Publication 1757-IN510A-EN-P - October 2003
1-4 ProcessLogix R510.0 Installation Introduction
ProcessLogix Client
The ProcessLogix R510.0 Client requires Windows 2000 Professional
or XP Professional operating systems. The following table lists the
Supported Installations
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
Step 2: Select a type
of install:
Clean Install ProcessLogix Client Installation and
Upgrade from R500.1
Windows XP
Professional Client
Upgrade from R500.1
Windows 2000
Professional Client
Windows 2000 Professional Windows XP Professional Windows 2000 Server
Refer to: Refer to: Refer to:
Upgrade Procedures on page 5-1.
N/A Upgrade R500.1 Windows XP
Upgrade R500.1 Windows 2000
Professional Client to R510.0
Windows 2000 Professional Client
on page 5-4.
Clean Install: Windows XP
Professional on page 5-8.
Professional Client to R510.0
Windows XP Professional Client on
page 5-8.
Upgrade R500.1 Windows 2000
Professional Client to R510.0
Windows XP Professional Client on
page 5-9.
Windows 2000 Server on
page 5-3.
Windows 2000 Server is not
a recommended operating
system for Clients.
N/A
N/A
Upgrade from R400.0
SP2 Windows 2000
Professional Client
Upgrade from R400.0
SP2 Windows NT 4.0
Client
Upgrade from R320.0
Windows NT 4.0 Client
Upgrade R400.0 SP2 Windows 2000
Professional Client to R510.0
Windows 2000 Professional Client
on page 5-5.
Upgrade R400.0 SP2 Windows NT
4.0 Client to R510.0 Windows 2000
Professional Client (Clean Install) on
page 5-6.
Upgrade R320.0 Windows NT 4.0
Client to R510.0 Windows 2000
Professional Client (Clean Install) on
page 5-7.
Upgrade R400.0 SP2 Windows 2000
Professional Client to R510.0
Windows XP Professional Client on
page 5-9.
Upgrade R400.0 SP2 Windows NT
4.0 Client to R510.0 Windows XP
Professional Client (Clean Install) on
page 5-11.
Upgrade R320.0 Windows NT 4.0
Client to R510.0 Windows XP
Professional Client (Clean Install) on
page 5-12.
N/A
N/A
N/A
Publication 1757-IN510A-EN-P - October 2003
Chapter
2
Operating System Installation Procedures
IMPORTANT
(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
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.
• Windows NT 4.0 Server and Workstation are not
supported.
(1)
1 Publication 1757-IN510A-EN-P - October 2003
2-2 Operating System Installation Procedures
Clean System Windows 2000 Server Installation
These instructions cover installation of Windows 2000 Server from
either CD-ROM or floppy disks.
IMPORTANT
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
If you purchased a new ProcessLogix R510.0 Server
from Rockwell Automation, the operating system and
ProcessLogix software have already been installed.
Do not r einstall the softw are. Refer to the
ProcessLogix R510.0 Server Installation Instructions,
publication 1757-IN950, shipped with your
hardware.
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.
Publication 1757-IN510A-EN-P - October 2003
Operating System Installation Procedures 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,
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).
skip
You nee d:
• 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.
Publication 1757-IN510A-EN-P - October 2003
2-4 Operating System Installation Procedures
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
9. Label your floppy disks.
10. When all the boot floppies have been made, shut down the PC.
Server Boot floppies and Professional Boot floppies
are different.
Starting the Windows 2000 Server Installation from the Boot Floppies
1. With the PC’s 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.
Publication 1757-IN510A-EN-P - October 2003
5. Press <Enter> at the Welcome to Setup window.
IMPORTANT
If your installation requires additional
Manufacturer’s Drivers, press <F6> during the boot
process and follow the on-screen instructions for
adding the necessary drivers.
Operating System Installation Procedures 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 computer’s 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.
If your installation requires additional
Manufacturer’s Drivers, press <F6> during the boot
process and follow the on-screen instructions for
adding the necessary drivers.
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.
Publication 1757-IN510A-EN-P - October 2003
2-6 Operating System Installation Procedures
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 Ne x t .
IMPORTANT
If there is a delay clicking Ne x t , setup continues the
installation automatically.
9. Verify the information on the Regional Settings window and
click Ne x t .
10. Enter the appropriate Name and Organization and click Ne x t .
11. Enter your Windows 2000 Server Product Key and click Ne x t .
12. Select your Server’s Licensing Mode and click Ne x t .
Publication 1757-IN510A-EN-P - October 2003
Operating System Installation Procedures 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.
13. At the Computer Name and Administrator Password window:
a. Enter the Computer Name.
IMPORTANT
It is strongly recommended that you name your
Server properly prior to installing ProcessLogix
R510.0 software.
Once the ProcessLogix R510.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
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 PC’s 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).
Publication 1757-IN510A-EN-P - October 2003
2-8 Operating System Installation Procedures
b. Enter the Administrator password.
c. Confirm the password.
IMPORTANT
d. Click Ne x t .
TIP
14. 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 Ne x t .
15. 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 Ne x t .
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.
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.
Publication 1757-IN510A-EN-P - October 2003
ATTENTION
!
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.
16. Select the Custom Settin gs option and click Ne x t .
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).
Operating System Installation Procedures 2-9
17. At the Networking Components window, select Inte r n et
Protocol (TCP/IP) and click Pr op er ties.
18. In the Networking Components Window,
a. Select the Use the following IP address 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
Redundant Server
Backup Redundant Server NIC 1: 192.168.0.2
NIC 1: 192.168.0.1
NIC 2: 192.168.1.1
NIC 3: 192.168.2.1
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.
Publication 1757-IN510A-EN-P - October 2003
2-10 Operating System Installation Procedures
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 company’s 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.
19. Click Ne x t .
20. Repeat steps 17-19 for additional network cards.
21. At the Workgroup or Computer Domain window:
a. Select the No , t h i s c o m p u t e r ... option.
b. Enter an appropriate WorkGroup Name.
c. Click Ne x 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 is h .
The PC restarts.
Clean System Windows 2000 Server Installation is complete.
Return to the checklist that led you to this task.
Publication 1757-IN510A-EN-P - October 2003
Loading...