Installation and Upgrade Guide

ManualsBrandsRockwell Automation ManualsEquipment1757-SWKIT5100 ProcessLogix R510.0

ProcessLogix

R510.0 Installation

and Upgrade Guide

1757-SWKIT5100

Installation Instructions

Summary of content (271 pages)

PAGE 1
ProcessLogix R510.
PAGE 2
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.
PAGE 3
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 . . . .
PAGE 4
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 . . . . . . . . . . . . . .
PAGE 5
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 6
Table of Contents iv Restoring the ProcessLogix Server Points Database . . . Upgrading Hardware Component Firmware . . . . . . . . Reloading Controllers. . . . . . . . . . . . . . . . . . . . . . . . . Backing Up a ProcessLogix Server Hard Drive to Tape . . . . 4-39 4-40 4-41 4-41 Chapter 5 ProcessLogix Client Installation and Upgrade Procedures Publication 1757-IN510A-EN-P - October 2003 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1 Operating System Support .
PAGE 7
Table of Contents Changing Hosts File Entries . . . . . . . . . . . . . . . . . . . Station Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Emergency Repair Disks . . . . . . . . . . . . . . . Checking Control Builder Operation and Logging On . . . . . . . . v 5-26 5-29 5-34 5-34 Chapter 6 Additional Redundant Server Procedures Adding Redundancy to R510.0 Non-Redundant Server Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 8
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 . . . . . . . . . . . . . . . . .
PAGE 9
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 . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 10
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 . . . . . . . . . . . .
PAGE 11
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.
PAGE 12
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.
PAGE 13
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.
PAGE 14
Preface 4 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.
PAGE 15
Preface Conventions 5 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.
PAGE 16
Preface 6 Acronyms and Abbreviations Table P.
PAGE 17
Chapter 1 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.
PAGE 18
1-2 ProcessLogix R510.0 Installation Introduction 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.
PAGE 19
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.
PAGE 20
1-4 ProcessLogix R510.0 Installation Introduction 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.
PAGE 21
Chapter 2 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.
PAGE 22
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 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.
PAGE 23
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.
PAGE 24
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 . 5. Enter >cd bootdisk< and press . 6. Enter >makeboot< and press . 7. Enter floppy disk drive letter (e.g., >A<). 8. Follow the on-screen prompts for inserting, labeling, and creating the four floppy disks.
PAGE 25
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.
PAGE 26
2-6 Operating System Installation Procedures 3. If necessary, press 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 . 3. Press . 4. Press . 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.
PAGE 27
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. 1 3.
PAGE 28
2-8 Operating System Installation Procedures 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.
PAGE 29
Operating System Installation Procedures 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.
PAGE 30
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.
PAGE 31
Operating System Installation Procedures 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 • Internet Explorer 6.0 SP1 The Windows 2000 Professional software, Service Packs, and Internet Explorer are licensed products of Microsoft Corporation.
PAGE 32
2-12 Operating System Installation Procedures 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.
PAGE 33
Operating System Installation Procedures 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 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 Professional CD into the CD-ROM drive. 4.
PAGE 34
2-14 Operating System Installation Procedures Completing the Windows 2000 Professional Installation 1 . At the Welcome to Setup window, press . 2. If requested, insert the Windows 2000 Professional CD into the CD-ROM drive and press . IMPORTANT If Windows 2000 Setup did not find a suitable installation device, it stops and prompts you for additional Manufacturer’s Drivers. Follow the on-screen instructions for adding the necessary drivers. 3.
PAGE 35
Operating System Installation Procedures 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: a. Enter the Computer Name. IMPORTANT The computer name cannot contain more than 14 alphanumeric characters and must contain no spaces.
PAGE 36
2-16 Operating System Installation Procedures 1 4. Select the Custom settin gs option and click Nex t. 1 5. At the Networking Components window, select In ter n et Pr otocol (TCP/IP) and click Pr oper ties. 1 6. 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.
PAGE 37
Operating System Installation Procedures 2-17 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.
PAGE 38
2-18 Operating System Installation Procedures 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.
PAGE 39
Operating System Installation Procedures 2-19 Starting the Windows XP Installation from the CD-ROM TIP If you are performing a clean XP installation, steps 1–4 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 PC’s 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.
PAGE 40
2-20 Operating System Installation Procedures Completing the Windows XP Professional Installation 1 . Press 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 Manufacturer’s Drivers. Follow the on-screen instructions for adding the necessary drivers. 2. Press to agree to the Windows XP Licensing Agreement. 3. If necessary, press to continue installing a fresh copy of Windows XP.
PAGE 41
Operating System Installation Procedures 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: a. Enter the Computer Name.
PAGE 42
2-22 Operating System Installation Procedures 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 5. At the Networking Components window, select In ter n et Pr otocol (TCP/IP) and click Pr oper ties. 1 6. In the Internet Protocol (TCP/IP) Properties window: a.
PAGE 43
Operating System Installation Procedures IMPORTANT 2-23 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.
PAGE 44
2-24 Operating System Installation Procedures 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.
PAGE 45
Operating System Installation Procedures 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.
PAGE 46
2-26 Operating System Installation Procedures 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.
PAGE 47
Operating System Installation Procedures 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.
PAGE 48
2-28 Operating System Installation Procedures Modifying Windows XP If upgrading from an R500.1 Windows XP Client, skip to step 12. If you have a redundant Server pair, you must complete this procedure on both SERVERA and SERVERB. 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.
PAGE 49
Operating System Installation Procedures 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 If this is the first time starting up since the Windows 2000 operating system install, it is necessary to remove the default startup screens.
PAGE 50
2-30 Operating System Installation Procedures Installing Windows 2000 Service Pack 4 If you have a redundant Server pair, you must complete this procedure on both SERVERA and SERVERB. 1 . If necessary, logon 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. 2. Insert the ProcessLogix R510.
PAGE 51
Operating System Installation Procedures 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. If you have a redundant Server pair, you must complete this procedure on both SERVERA and SERVERB. 1 . If necessary, logon to the system.
PAGE 52
2-32 Operating System Installation Procedures Installing Windows XP Security Hotfix 1 . If necessary, logon to the system. 2. Insert the ProcessLogix R510.0 Supplemental Software CD into the CD-ROM drive. 3. Click Star t ⇒ Run . 4. Enter this path or Br ow se to: >D:(or your CD-ROM drive letter)\WinXP_Security_Hotfix_824146\ WindowsXP-KB824146-x86-ENU.exe< 5. Click OK to launch the setup application. 6. At the Welcome window, click Nex t. 7. Select the I Agr ee option and click Nex t. 8.
PAGE 53
Operating System Installation Procedures Internet Explorer 6.0 SP1 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. 1 . If necessary, logon to the system.
PAGE 54
2-34 Operating System Installation Procedures 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.
PAGE 55
Operating System Installation Procedures 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. 1 . If necessary, logon 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.
PAGE 56
2-36 Operating System Installation Procedures 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. 1 .
PAGE 57
Operating System Installation Procedures 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. 1 . If necessary, logon to the system. 2. If necessary, insert the ProcessLogix R510.0 Base CD in the CD-ROM drive. 3. Click Star t ⇒ Run .
PAGE 58
2-38 Operating System Installation Procedures 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).
PAGE 59
Operating System Installation Procedures 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.
PAGE 60
2-40 Operating System Installation Procedures 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.
PAGE 61
Operating System Installation Procedures 2-41 6. Enter a backup media or file name and click Nex t. 7. Click Fin ish . 8. Repeat Steps 1–7 with another blank formatted diskette. 9. Click Job ⇒ Ex it. 1 0. Store the two diskettes in different places to protect against damage to the diskettes. Creating Emergency Repair Disks is complete. Return to the checklist that led you to this task.
PAGE 62
2-42 Operating System Installation Procedures Publication 1757-IN510A-EN-P - October 2003
PAGE 63
Chapter 3 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 If you purchased a new ProcessLogix R510.
PAGE 64
3-2 ProcessLogix Server Installation Procedures 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 Completing the ProcessLogix R510.0 Install on a Non-Redundant Server 6-2 3-19 3-20 PC Namin g Requir emen ts Before installing ProcessLogix R510.
PAGE 65
ProcessLogix Server Installation Procedures 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.
PAGE 66
3-4 ProcessLogix Server Installation Procedures Installing ProcessLogix Product 1 . Insert the ProcessLogix R510.0 Base Software CD into the CD-ROM drive. 2. Click Star t ⇒ Run . 3. Enter this path or Br ow se to: >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.
PAGE 67
ProcessLogix Server Installation Procedures 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.
PAGE 68
3-6 ProcessLogix Server Installation Procedures 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.
PAGE 69
ProcessLogix Server Installation Procedures 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 ! Do not click No in the next step. Clicking No aborts the entire ProcessLogix installation. 1 . Insert the ProcessLogix R510.
PAGE 70
3-8 ProcessLogix Server Installation Procedures 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.
PAGE 71
ProcessLogix Server Installation Procedures 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.
PAGE 72
3-10 ProcessLogix Server Installation Procedures 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.
PAGE 73
ProcessLogix Server Installation Procedures 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.
PAGE 74
3-12 ProcessLogix Server Installation Procedures Installing ProcessLogix Update 1 . Restart the PC. 2. Logon as ps_user. 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.
PAGE 75
ProcessLogix Server Installation Procedures 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< 1 9. Click OK to launch the software setup application. 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 .
PAGE 76
3-14 ProcessLogix Server Installation Procedures 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.
PAGE 77
ProcessLogix Server Installation Procedures 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. 2.
PAGE 78
3-16 ProcessLogix Server Installation Procedures 9. Remove the Master Disk and store it in a safe place. 1 0. Restart the PC. 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.
PAGE 79
ProcessLogix Server Installation Procedures 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.
PAGE 80
3-18 ProcessLogix Server Installation Procedures 4. Click OK to acknowledge the warning about monitoring through Control Builder. 5. Click the resume button to initiate network scan. Updating the 1784-PCIC Firmware 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.
PAGE 81
ProcessLogix Server Installation Procedures 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.
PAGE 82
3-20 ProcessLogix Server Installation Procedures 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.
PAGE 83
ProcessLogix Server Installation Procedures 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.
PAGE 84
3-22 ProcessLogix Server Installation Procedures 3. Click Emer gen cy Repair Disk. An Emergency Repair Diskette window opens. 4. Insert a blank diskette into the PC's floppy drive. 5. Check the Also back up th e r egistr y to th e r epair dir ector y checkbox and click OK. 6. When finished, click OK. 7. Repeat Steps 1 through 5 with another blank formatted diskette. 8. Click Job ⇒ Ex it. 9. Store the two diskettes in different places to protect against damage to the diskettes.
PAGE 85
Chapter 4 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 Upgrade R500.1 Server to R510.0 This section describes the steps necessary to upgrade the ProcessLogix R500.1 Server software to R510.0. There are two upgrade options.
PAGE 86
4-2 ProcessLogix Server Upgrade Procedures Table 4.A Option 1: Upgrading R500.1 Server to R510.0 Checklist ✔ Step Item Page 8. Updating ISScript 2-37 9. Additional Operating System Customization Procedures 2-38 1 0. Creating Emergency Repair Disks 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 a. Backup your data. b. Uninstall your current ProcessLogix software. c.
PAGE 87
ProcessLogix Server Upgrade Procedures 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 a. Backup your data. b. Complete a clean install. c. Restore your data.
PAGE 88
4-4 ProcessLogix Server Upgrade Procedures 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. The following table lists the items in Option 2 that you MUST 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 ✔ Publication 1757-IN510A-EN-P - October 2003 Step Item Page 1.
PAGE 89
ProcessLogix Server Upgrade Procedures 4-5 Upgrade R320.0 Server to R510.0 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.
PAGE 90
4-6 ProcessLogix Server Upgrade Procedures 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.
PAGE 91
ProcessLogix Server Upgrade Procedures 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. 3.
PAGE 92
4-8 ProcessLogix Server Upgrade Procedures 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.
PAGE 93
ProcessLogix Server Upgrade Procedures 4-9 7. Enter >xcopy C:\Honeywell\TPS50\System\ER\Release\*.* C:\Data\FFdevices /E< and press . 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.
PAGE 94
4-10 ProcessLogix Server Upgrade Procedures 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.
PAGE 95
ProcessLogix Server Upgrade Procedures 4-11 Table 4.F Saving Important R400.0 SP2 or R500.1 Server Data Item Pre-upgrade Requirement 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.
PAGE 96
4-12 ProcessLogix Server Upgrade Procedures 4. Enter >xcopy C:\Honeywell\server\data\*.* C:\ Data\server\backup /E< and press . 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 .
PAGE 97
ProcessLogix Server Upgrade Procedures 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. Return to the checklist that led you to this task. 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.
PAGE 98
4-14 ProcessLogix Server Upgrade Procedures Transferring Data 1 . If you have a non-redundant server: a. At the DOS prompt, enter >xcopy C:\Data\*.* T:\ UpgradeData /E< and press . 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 . b. If necessary, enter >D< to specify that UpgradePrimaryData is a directory. c.
PAGE 99
ProcessLogix Server Upgrade Procedures 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.
PAGE 100
4-16 ProcessLogix Server Upgrade Procedures 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.
PAGE 101
ProcessLogix Server Upgrade Procedures 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 .
PAGE 102
4-18 ProcessLogix Server Upgrade Procedures Verifying and Finalizing Component Removal IMPORTANT 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. 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. 1 . Double-click Add/Remove Pr ogr ams in the Control Panel window. 2.
PAGE 103
ProcessLogix Server Upgrade Procedures 4-19 7. Close the Add/Remove Programs window. 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. 1 2. Restart the PC. Removing ProcessLogix R500.1 Software is complete. Return to the checklist that led you to this task. Removing ProcessLogix R400.
PAGE 104
4-20 ProcessLogix Server Upgrade Procedures 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.
PAGE 105
ProcessLogix Server Upgrade Procedures 4-21 Removing ProcessLogix Server Components 1 . Click Star t ⇒ Pr ogr ams ⇒ Pr ocessLogix Ser ver ⇒ Setup. 2. If necessary, at the Select Product to Install window, select the Pr ocessLogix option, 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.
PAGE 106
4-22 ProcessLogix Server Upgrade Procedures • • • • • • • • • • • • • • • Engineering Tools R400 SP2 ProcessLogix - R400 SP2 ProcessLogix Update Control Component Library PSAxCtl Document EXE Psc Engineering Tools RSLinx Knowledge Builder Microsoft SQL Server 7.0 PLX System Installer HMIWeb Station and Display Builder Display Builder 320.2 Quick Builder ProcessLogix Server R400.0 VBScript Documentation 4. Select Pr ocessLogix - Remove th is last. 5. Click Ch an ge/Remove. 6. Click Yes to confirm. 7.
PAGE 107
ProcessLogix Server Upgrade Procedures 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).
PAGE 108
4-24 ProcessLogix Server Upgrade Procedures 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.
PAGE 109
ProcessLogix Server Upgrade Procedures 4-25 a. Enter >mngr< as the default User Name. b. Enter >mngr1< as the default Password. c. Enter >localhost< in the Server Name field. 4. Click OK. 5. Click File ⇒ Ex por t. 6. Click Br ow se to set the Directory Path to C:\Data\ExportDB. 7. 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.
PAGE 110
4-26 ProcessLogix Server Upgrade Procedures 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. If you have a redundant server pair, you must complete this procedure on SERVERB first. Then complete the entire procedure again on SERVERA.
PAGE 111
ProcessLogix Server Upgrade Procedures 4-27 Table 4.I Saving Important R320.0 Server Data Item Pre-upgrade Requirement Post-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.
PAGE 112
4-28 ProcessLogix Server Upgrade Procedures Exporting the 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 on page 1-8 of the ProcessLogix R320.0 Installation and Upgrade Guide, before continuing. If you have a redundant server pair, you must complete this procedure on SERVERB first. Then complete the entire procedure again on SERVERA.
PAGE 113
ProcessLogix Server Upgrade Procedures 4-29 3. Enter this path or Br ow se to: >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 C:(or your hard drive letter) to Drive A:(or your floppy drive letter). 6. Click OK to initiate the move. 7. Click Move to move the file to the floppy. 8. Wait for a dialog box to indicate a successful move, and click OK. 9. Close EvMove. 1 0.
PAGE 114
4-30 ProcessLogix Server Upgrade Procedures 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 . 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 . b.
PAGE 115
ProcessLogix Server Upgrade Procedures 4-31 3. If you have a non-redundant server: a. Enter >xcopy C:\Data\*.* T:\R320Data\ /E< and press . 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 . b. If necessary, enter >D< to specify that R320PrimaryData is a directory. c.
PAGE 116
4-32 ProcessLogix Server Upgrade Procedures 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.
PAGE 117
ProcessLogix Server Upgrade Procedures 4-33 1 5. Enter this path location in the Copy manufacturer’s 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 .
PAGE 118
4-34 ProcessLogix Server Upgrade Procedures 8. Restart SERVERB. Transferring R400.0 SP2 or R500.1 Data to the R510.0 Server 1 . Click Star t ⇒ Run . 2. Enter >cmd< and click OK to open the DOS window. 3. If you have a non-redundant server: a. Enter >xcopy T:\UpgradeData\*.* C:\UpgradeData /E< and press . b. If necessary, enter >D< to specify that UpgradeData is a directory. 4. If you have a redundant Server pair, a. On SERVERA, enter >xcopy T:\UpgradePrimaryData\*.
PAGE 119
ProcessLogix Server Upgrade Procedures 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.
PAGE 120
4-36 ProcessLogix Server Upgrade Procedures 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.
PAGE 121
ProcessLogix Server Upgrade Procedures 4-37 8. Enter the New Password, Confirm the New Password and click OK. The message Passw or d accepted should appear in the message 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.
PAGE 122
4-38 ProcessLogix Server Upgrade Procedures Importing the Database Using Control Builder 1 . Click Star t ⇒ Pr ogr ams ⇒ Pr ocessLogix En gin eer in g Tools ⇒ Con tr ol Builder. 2. In the Login dialog box, make these entries: a. b. c. d. Enter >mngr< as the default User Name. Enter the appropriate Password. Enter the appropriate Server name in the Server Name field. Select Classic Ser ver Secur ity in the Domain Name drop-down list. IMPORTANT If importing from R320.
PAGE 123
ProcessLogix Server Upgrade Procedures 4-39 7. When completed, close the Import Window (if it did not automatically close). 8. Close Control Builder. Restoring the ProcessLogix Server Points Database ATTENTION ! Before restoring 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.
PAGE 124
4-40 ProcessLogix Server Upgrade Procedures 1 1 . To import the data, enter >sysbld -restore C:\ Honeywell\server\backup\data -y< and press . Depending on the size of your database, this step may take several minutes. 1 2. To start the ProcessLogix Server enter >hscserver /start /y< and press . 1 3. Close the command prompt. Upgrading Hardware Component Firmware 1 .
PAGE 125
ProcessLogix Server Upgrade Procedures 4-41 Reloading Controllers 1 . Click Star t ⇒ Pr ogr am s ⇒ Pr ocessLogix En gin eer in g Tools ⇒ Con tr ol Builder. 2. In the Login dialog box, make these entries: a. b. c. d. Enter >mngr< as the default User Name. Enter the appropriate Password. Enter the appropriate Server name in the Server Name field. Select Classic Ser ver Secur ity in the Domain Name drop-down list. 3. Click OK. 4.
PAGE 126
4-42 ProcessLogix Server Upgrade Procedures Publication 1757-IN510A-EN-P - October 2003
PAGE 127
Chapter 5 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.
PAGE 128
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.
PAGE 129
ProcessLogix Client Installation and Upgrade Procedures 5-3 Windows XP Professional 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.
PAGE 130
5-4 ProcessLogix Client Installation and Upgrade Procedures Table 5.A Clean Install: Windows 2000 Professional ✔ Step 9. Task to complete: Refer to: Creating Emergency Repair Disks 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 Windows 2000 Professional Client The following table lists the items that you MUST complete to upgrade an R500.
PAGE 131
ProcessLogix Client Installation and Upgrade Procedures 5-5 Upgrade R400.0 SP2 Windows 2000 Professional Client to R510.0 Windows 2000 Professional Client The following table lists the items that you MUST complete to 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 Windows 2000 Professional Client ✔ Order Task to Complete: Refer to: 1. Saving Important Data 5-13 2.
PAGE 132
5-6 ProcessLogix Client Installation and Upgrade Procedures Upgrade R400.0 SP2 Windows NT 4.0 Client to R510.0 Windows 2000 Professional Client (Clean Install) The following table lists the items that you MUST complete to 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.
PAGE 133
ProcessLogix Client Installation and Upgrade Procedures 5-7 Upgrade R320.0 Windows NT 4.0 Client to R510.0 Windows 2000 Professional Client (Clean Install) The following table lists the items that you MUST complete to upgrade an R320.0 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 R320.0 Client to a ProcessLogix R510.
PAGE 134
5-8 ProcessLogix Client Installation and Upgrade Procedures Windows XP Professional Client Installation Scenarios Clean Install: Windows XP Professional The following table lists the items that you MUST complete to install 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. Clean System Windows XP Professional Installation 2-18 2. Creating the ProcessLogix User Accounts 2-26 3.
PAGE 135
ProcessLogix Client Installation and Upgrade Procedures 5-9 Upgrade R500.1 Windows 2000 Professional Client to R510.0 Windows XP Professional Client The following table lists the items that you MUST complete to upgrade an R500.1 Windows 2000 Professional Client to an R510.0 Windows XP Professional Client. 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. Saving Important Data 5-13 2.
PAGE 136
5-10 ProcessLogix Client Installation and Upgrade Procedures Table 5.I Upgrade R400.0 SP2 Windows 2000 Professional Client to R510.0 Windows XP Professional Client Checklist ✔ Publication 1757-IN510A-EN-P - October 2003 Order Task to Complete: Refer to: 6. Windows Security Hotfix Installation 2-31 7. Internet Explorer 6.0 SP1 Installation 2-33 8. Updating ISScript 2-37 9. Installing ProcessLogix R510.0 Client Software 5-18 1 0. Transferring ProcessLogix Data 5-25 11.
PAGE 137
ProcessLogix Client Installation and Upgrade Procedures 5-11 Upgrade R400.0 SP2 Windows NT 4.0 Client to R510.0 Windows XP Professional Client (Clean Install) The following table lists the items that you MUST complete to upgrade an R400.0 SP2 Windows NT 4.0 Client to an R510.0 Windows XP 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.
PAGE 138
5-12 ProcessLogix Client Installation and Upgrade Procedures Upgrade R320.0 Windows NT 4.0 Client to R510.0 Windows XP Professional Client (Clean Install) The following table lists the items that you MUST complete to upgrade an R320.0 Windows NT 4.0 Client to an R510.0 Windows XP Professional Client. IMPORTANT Due to significant changes in the ProcessLogix software, operating system, and performance requirements, migration from a ProcessLogix R320.0 Client to a ProcessLogix R510.
PAGE 139
ProcessLogix Client Installation and Upgrade Procedures Saving Important Data 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 Save any custom displays that were created. Typically these displays are located in C:\Honeywell\Client\abstract. 1.
PAGE 140
5-14 ProcessLogix Client Installation and Upgrade Procedures 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. 2. Click Star t ⇒ Run . 3. Enter >cmd< and click OK to open the DOS window. 4.
PAGE 141
ProcessLogix Client Installation and Upgrade Procedures 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. 1 . Logon to the system as ps_user. 2. Click Star t ⇒ Settin gs ⇒ Con tr ol Pan el. 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.
PAGE 142
5-16 ProcessLogix Client Installation and Upgrade Procedures 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. PLX System Installer (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.
PAGE 143
ProcessLogix Client Installation and Upgrade Procedures 5-17 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.
PAGE 144
5-18 ProcessLogix Client Installation and Upgrade Procedures Table 5.N Removing Selected R400.0 SP2 Components ✔ Order Component 1 5. Control Component Library (Engineering Workstation only) 1 6. Shape Library 400.0 1 7. PsAxCtl Document EXE (Engineering Workstation only) 1 8. Display Builder 320.2 1 9. PSC Engineering Tools (Engineering Workstation only) 20. Knowledge Builder 21 . PLX System Installer 22. ProcessLogix - Remove this last 5. Close the Add/Remove Programs window. 6.
PAGE 145
ProcessLogix Client Installation and Upgrade Procedures 5-19 1 . If necessary, logon to the system as ps_user. 2. Close all running applications. 3. Insert the ProcessLogix R510.0 Base Software CD into the CD-ROM drive. 4. Click Star t ⇒ Run . 5. Enter this path or Br ow se to: >D:(or your CD-ROM drive letter)\SETUP.EXE< 6. Click OK to launch the software setup application. 7. Select the Engineering Workstation or Operator Workstation option and click Nex t. 8.
PAGE 146
5-20 ProcessLogix Client Installation and Upgrade Procedures Installing Knowledge Builder Components 1 . At the Knowledge Builder - Welcome window, click Nex t. 2. Click Yes to accept the license agreement. 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.
PAGE 147
ProcessLogix Client Installation and Upgrade Procedures 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.
PAGE 148
5-22 ProcessLogix Client Installation and Upgrade Procedures • • • • • 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.
PAGE 149
ProcessLogix Client Installation and Upgrade Procedures 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.
PAGE 150
5-24 ProcessLogix Client Installation and Upgrade Procedures 9. At the Ready to Install window, click In stall. Status messages indicate progress, but no user interaction is 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.
PAGE 151
ProcessLogix Client Installation and Upgrade Procedures 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 3. Click Star t ⇒ Run . 4.
PAGE 152
5-26 ProcessLogix Client Installation and Upgrade Procedures 1 0. If necessary, enter >D< to specify that UpgradeData is a directory. 1 1 . Delete the backup files from the remote PC. Restoring ProcessLogix Data 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 C:\Honeywell\client\abstract.
PAGE 153
ProcessLogix Client Installation and Upgrade Procedures 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.
PAGE 154
5-28 ProcessLogix Client Installation and Upgrade Procedures Use the following format to make your separate line entries into this file. 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.
PAGE 155
ProcessLogix Client Installation and Upgrade Procedures 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.
PAGE 156
5-30 ProcessLogix Client Installation and Upgrade Procedures 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.
PAGE 157
ProcessLogix Client Installation and Upgrade Procedures 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.
PAGE 158
5-32 ProcessLogix Client Installation and Upgrade Procedures 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. d.
PAGE 159
ProcessLogix Client Installation and Upgrade Procedures 5-33 1 4. Click Can cel at the Unable to connect prompt, if applicable. 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.
PAGE 160
5-34 ProcessLogix Client Installation and Upgrade Procedures 20. Click Save. 21 . Click Yes to save changes. 22. Select Default and click Con n ect. 23. Click Can cel at the Unable to connect prompt, if applicable. 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.
PAGE 161
Chapter 6 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 ✔ 1 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.
PAGE 162
6-2 Additional Redundant Server Procedures 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).
PAGE 163
Additional Redundant Server Procedures 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.
PAGE 164
6-4 Additional Redundant Server Procedures Use the following format to make your separate line entries into this file: 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.
PAGE 165
Additional Redundant Server Procedures 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.
PAGE 166
6-6 Additional Redundant Server Procedures 4. Close the ProcessLogix Server dialog box. 5. Click Star t ⇒ Pr ogr ams ⇒ Pr ocessLogix Ser ver ⇒ Setup. 6. At the Welcome window, click Nex t. 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 .
PAGE 167
Additional Redundant Server Procedures 6-7 Making Redundant Hardware File Entries 1 . On SERVERB, 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. Close the dialog box. OR 2. On SERVERA, 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.
PAGE 168
6-8 Additional Redundant Server Procedures 9. If you have redundant LANs, modify the file to include the following entries for dual data links.
PAGE 169
Additional Redundant Server Procedures 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 Configuration Guide⇒ Configuring and Monitoring a Redundant Server System⇒ Synchronizing Date and Time on the Servers. 2. Close Knowledge Builder. Restarting ProcessLogix Services 1 .
PAGE 170
6-10 Additional Redundant Server Procedures 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 Pr ocessLogix Ser ver to call up the ProcessLogix Server dialog box. Restarting ProcessLogix Services 1 .
PAGE 171
Additional Redundant Server Procedures 6-11 6. On SERVERB, click Star t ⇒ Run . 7. Enter >cmd< and click OK to open the DOS window. 8. At the DOS prompt, enter >dual_status< and press . 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.
PAGE 172
6-12 Additional Redundant Server Procedures 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.
PAGE 173
Additional Redundant Server Procedures 6-13 5. On the Connection tab, make these entries to have the Station point to SERVERB (PLX1 B): 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: C:\Honeywell\Client\Station\default.stn and click Open .
PAGE 174
6-14 Additional Redundant Server Procedures b. To add a directory, click Add, click and click OK. TIP , select the directory, Display Sear ch Path Optimization You can improve Station’s performance by unchecking the Search subdirectories for shapes checkbox in the Connection Properties dialog box, and then explicitly defining each subdirectory that contains displays. 8. Click Save. 9. Click Yes to save the new connection. 1 0. Enter >defaultb.stn< in the File name field and click Save. 1 1 .
PAGE 175
Additional Redundant Server Procedures 6-15 20. If you have redundant LANs, you must repeat Step 1 through Step 19 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. Navigate in Knowledge Builder to Server and Client Configuration Guide⇒ Configuring and Monitoring a Redundant Server System⇒ Configuring Stations for Server Redundancy⇒ Dual Network Configuration for more information. 21 . Click Station ⇒ Ex it. 22.
PAGE 176
6-16 Additional Redundant Server Procedures 6. On the Displays tab, check the Sear ch subdir ector ies for sh apes checkbox. 7. 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.
PAGE 177
Additional Redundant Server Procedures 6-17 1 2. Click Can cel at the Unable to connect prompt, if applicable. 1 3. Click Station ⇒ Con n ect to call up the Station Connect dialog box. 1 4. Select Default and click Edit Con n ection . 1 5. On the Connection tab, make these entries to have the Station point to SERVERA (PLX1 A): a. In the Server field, enter or Br ow se to the Primary Server name, SERVERA. b. Select the Station type as Static Station . c.
PAGE 178
6-18 Additional Redundant Server Procedures 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 3. Enter >mngr< in the Station logon prompt and click OK. 4. Click Con figur e ⇒ Oper ator ⇒ 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. The message Passw or d accepted should appear in the message zone.
PAGE 179
Additional Redundant Server Procedures 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.
PAGE 180
6-20 Additional Redundant Server Procedures 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. 3. Click the Oper field in the lower right corner of the display. 4.
PAGE 181
Additional Redundant Server Procedures 6-21 3. At the DOS prompt, enter this command: >dual_status< and press . 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 . 7. Enter >cmd< and click OK to open the DOS window. 8. At the DOS prompt, enter this command: >dual_status< and press . 9. The synchronized SERVERB data should be similar to this: 1 0.
PAGE 182
6-22 Additional Redundant Server Procedures 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.
PAGE 183
Additional Redundant Server Procedures 6-23 3. Click OK. Backing Up a ProcessLogix Server Hard Drive to Tape 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 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.
PAGE 184
6-24 Additional Redundant Server Procedures Publication 1757-IN510A-EN-P - October 2003
PAGE 185
Chapter 7 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. 2. Logon as ps_user. 3.
PAGE 186
7-2 Firmware Maintenance Procedures 1 3. Enter this path location in the Copy manufacturer’s 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.
PAGE 187
Firmware Maintenance Procedures 7-3 1 1 . Close the Computer Management window. 1784-PCIC Driver Installation is complete. Return to the checklist that led you to this task. 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.
PAGE 188
7-4 Firmware Maintenance Procedures 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.
PAGE 189
Firmware Maintenance Procedures 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.
PAGE 190
7-6 Firmware Maintenance Procedures Table 7.A Hardware component firmware revision level reference for R510.0 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.
PAGE 191
Firmware Maintenance Procedures 7-7 Table 7.A Hardware component firmware revision level reference for R510.0 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 \IOM\Analog\1756_analog\1_9 99207408.nvs 1756-IT6I/A 1.9 \IOM\Analog\1756_analog\1_9 99207408.nvs 1756-OF6CI/A 1.9 \IOM\Analog\1756_analog\1_9 99207408.
PAGE 192
7-8 Firmware Maintenance Procedures 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.
PAGE 193
Firmware Maintenance Procedures 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 ! 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.
PAGE 194
7-10 Firmware Maintenance Procedures 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.
PAGE 195
Firmware Maintenance Procedures 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 C:\Honeywell\TPS50\system\bin 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.
PAGE 196
7-12 Firmware Maintenance Procedures 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. 2. Click the firmware button to initiate the firmware update. 3. Click Yes to acknowledge the Warning prompt. 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.
PAGE 197
Firmware Maintenance Procedures 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.
PAGE 198
7-14 Firmware Maintenance Procedures 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. 4. Click the firmware button and click Yes to acknowledge the warning. 5. Select the path to the correct .nvs file. See Table 7.
PAGE 199
Firmware Maintenance Procedures 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.
PAGE 200
7-16 Firmware Maintenance Procedures 4. Click OK to launch the Network Tools application. 5. Click OK to acknowledge the warning about monitoring through Control Builder. 6. Click Resume to initiate network scan. 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.
PAGE 201
Firmware Maintenance Procedures 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.
PAGE 202
7-18 Firmware Maintenance Procedures 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.
PAGE 203
Chapter 8 Supplementary Procedures Stopping ProcessLogix Applications and Services ATTENTION ! Before installing or uninstalling any software component, you MUST exit all ProcessLogix applications and stop all ProcessLogix services. If you have a redundant Server pair, you must complete this procedure on SERVERB first. Then complete the entire procedure again on SERVERA. This section describes how to stop ProcessLogix services in the Windows 2000 system.
PAGE 204
8-2 Supplementary Procedures 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. Return to the checklist that led you to this task. Installing Knowledge Builder on a Non-ProcessLogix System Knowledge Builder is the software application used to display ProcessLogix documentation.
PAGE 205
Supplementary Procedures 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. Removing Knowledge Builder 8-3 2. Internet Explorer 6.0 SP1 Installation 2-33 3. Installing Knowledge Builder 8-4 Removing Knowledge Builder Before installing ProcessLogix R510.
PAGE 206
8-4 Supplementary Procedures Removing R500.1 Knowledge Builder 1 . Click Star t ⇒ Settin gs ⇒ Con tr ol Pan el. 2. Double-click Add/Remove Pr ogr ams. 3. 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.
PAGE 207
Supplementary Procedures 8-5 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 refer to Installing Knowledge Builder Components, below. 4. At the Acrobat Reader 4.05 Setup window, click Nex t. 5. At the Choose Destination Location window, click Nex t. 6. Click OK. Installing Knowledge Builder Components 7.
PAGE 208
8-6 Supplementary Procedures 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. The KB_update executes. No user interaction is required. 1 5. Remove the ProcessLogix R510.0 Knowledge Builder CD. 1 6. Restart the PC.
PAGE 209
Supplementary Procedures 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.
PAGE 210
8-8 Supplementary Procedures 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.
PAGE 211
Supplementary Procedures 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.
PAGE 212
8-10 Supplementary Procedures 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. 1 . Click Star t ⇒ Run . a. For ControlNet Supervisory Networks, enter >ntools -c -u -pg<.
PAGE 213
Supplementary Procedures 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.
PAGE 214
8-12 Supplementary Procedures 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.
PAGE 215
Supplementary Procedures 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.
PAGE 216
8-14 Supplementary Procedures 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.
PAGE 217
Supplementary Procedures 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 manufacturer’s 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.
PAGE 218
8-16 Supplementary Procedures 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.
PAGE 219
Supplementary Procedures 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.
PAGE 220
8-18 Supplementary Procedures Removing Selected ProcessLogix R510.0 Components 1 . Click Star t ⇒ Run . 2. Enter this path or Br ow se to: >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 installing or uninstalling any software component, you MUST exit all ProcessLogix applications and stop all ProcessLogix services.
PAGE 221
Supplementary Procedures 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. Process Detail Displays 2. ProcessLogix Update 3. PsAxCtl Document EXE (If you see Application Removal windows, click OK.) 4. Psc Engineering Tools 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.
PAGE 222
8-20 Supplementary Procedures 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 computer later option and click Fin ish . Verifying and Finalizing Component Removal IMPORTANT When you remove a program, its name may not be automatically removed from the Add/Remove Programs window.
PAGE 223
Supplementary Procedures • • • • 8-21 ODBC Client OPC Server Connect Network API Shape Library 4. Select Pr ocessLogix - Remove th is last. 5. Click Ch an ge/Remove. 6. Click Yes to confirm. 7. Click OK when completed. 8. Close the Add/Remove Programs window. Changing the PC Name 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.
PAGE 224
8-22 Supplementary Procedures 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.
PAGE 225
Supplementary Procedures 8-23 6. Click Br ow se to set the import Directory to C:\ExportDB. 7. Click Select All. Depending on the size of your database, this step may take several minutes. 8. Click Impor t. Depending on the size of your database, this step may take several minutes to several hours. 9. When completed, close the Import Window. IMPORTANT At this point, each controller must be reloaded on the system. 1 0. Close Control Builder.
PAGE 226
8-24 Supplementary Procedures 5. Enter the desired computer name in the Computer name entry field. 6. Click OK to initiate the change. 7. At the You must reboot prompt, click OK. 8. Click OK to Close the System Properties window. 9. Click Yes to restart the computer. Changing the Computer Name on a Windows XP Client 1 . Logon as ps_user. 2. Click Star t ⇒ Settin gs ⇒ Con tr ol Pan el. 3. Double-click System. 4. On the Computer Name tab, click Ch an ge. 5.
PAGE 227
Supplementary Procedures 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.
PAGE 228
8-26 Supplementary Procedures 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 CEE’s SCMs to inactivate all assigned SCMs, if applicable. 1 2. Click Yes in the dialog box to confirm the action. 1 3.
PAGE 229
Supplementary Procedures 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. 29. Close Control Builder. 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).
PAGE 230
8-28 Supplementary Procedures 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. Navigate in Knowledge Builder to Control Building Guide⇒ Hardware Module Creation⇒ Creating Redundancy Modules for more information about configuring 1757-SRMs in Control Builder. 3.
PAGE 231
Chapter 9 New Functions and Features Overview This release introduces enhancements to Rockwell Automation's ProcessLogix process control system.The enhancements include: Table 9.
PAGE 232
9-2 New Functions and Features 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.
PAGE 233
New Functions and Features 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.
PAGE 234
9-4 New Functions and Features Publication 1757-IN510A-EN-P - October 2003
PAGE 235
Chapter 10 Major ProcessLogix Software Components 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 1 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.
PAGE 236
10-2 Major ProcessLogix Software Components 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.
PAGE 237
Major ProcessLogix Software Components 10-3 Embedded Software Components Table 10.C Embedded Software Components Component Version Example Verification Mechanism 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.
PAGE 238
10-4 Major ProcessLogix Software Components 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.
PAGE 239
Major ProcessLogix Software Components 10-5 Table 10.D External, Third Party Qualified Software Components Component Version MS Office 2000 Products Access Verify the component version by: Limitations/Compatibilities: • Excludes Outlook 9.0.1381 Service Pack 1 1. Open Access. 2. Click Help ⇒ About Access… Limitations/Compatibilities: • 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.
PAGE 240
10-6 Major ProcessLogix Software Components Table 10.D External, Third Party Qualified Software Components Component Version MS Visual C++ 6.0 Verify the component version by: 1. Run Windows Explorer. 2. Right click \winnt\system32\mscvrt.dll (Microsoft Run Time Library). 3. Click Properties. 4. Click the Version tab. Service Pack 5 Limitations/Compatibilities: • Use on Client only MS Visual Basic 6.0 1. Run Windows Explorer. 2. Right click \winnt\system32\msvbvm50.
PAGE 241
Chapter 11 Performance and Capacity Specifications 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.
PAGE 242
11-2 Performance and Capacity Specifications 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.
PAGE 243
Performance and Capacity Specifications 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.
PAGE 244
11-4 Performance and Capacity Specifications 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.
PAGE 245
Performance and Capacity Specifications 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.
PAGE 246
11-6 Performance and Capacity Specifications 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.
PAGE 247
Performance and Capacity Specifications 11-7 User Interface Capacity and Performance Table 11.
PAGE 248
11-8 Performance and Capacity Specifications 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 Controller’s 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.
PAGE 249
Performance and Capacity Specifications 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.
PAGE 250
11-10 Performance and Capacity Specifications Server Notifications Table 11.
PAGE 251
Performance and Capacity Specifications 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.
PAGE 252
11-12 Performance and Capacity Specifications 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 system’s architectural capabilities. The basic concept is shown in the following hierarchical diagram.
PAGE 253
Performance and Capacity Specifications 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.
PAGE 254
11-14 Performance and Capacity Specifications • 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.
PAGE 255
Performance and Capacity Specifications 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.
PAGE 256
11-16 Performance and Capacity Specifications 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.
PAGE 257
Performance and Capacity Specifications 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.
PAGE 258
11-18 Performance and Capacity Specifications 1757-PLX52 Resources Table 11.
PAGE 259
Performance and Capacity Specifications 11-19 Table 11.
PAGE 260
11-20 Performance and Capacity Specifications 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.
PAGE 261
Performance and Capacity Specifications 11-21 Table 11.
PAGE 262
11-22 Performance and Capacity Specifications 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.
PAGE 263
Performance and Capacity Specifications 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.
PAGE 264
11-24 Performance and Capacity Specifications (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.
PAGE 265
Performance and Capacity Specifications 11-25 I/O Module Publication Periods Table 11.
PAGE 266
11-26 Performance and Capacity Specifications 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.
PAGE 267
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.
PAGE 268
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.
PAGE 269
PAGE 271
ProcessLogix R510.