ProcessLogix R500.
Important User Information Because of the variety of uses for the products described in this publication, those responsible for the application and use of these products must satisfy themselves that all necessary steps have been taken to assure that each application and use meets all performance and safety requirements, including any applicable laws, regulations, codes and standards.
Table of Contents Preface Our Assumptions About Users . . . . . . . . . . . . . . . . . . . . . . . . . Starting Conditions and Assumptions . . . . . . . . . . . . . . . . Minimum Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . Contents of Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ProcessLogix Online User Documentation/Knowledge Builder . . . . . . . . . . . . . . . ProcessLogix R500.1 Installation and Upgrade Guide . . .
ii Table of Contents Starting the Windows XP Professional Installation . . . . . . . . . . Starting the Windows XP Installation from the CD-ROM . . . . Completing the Windows XP Professional Installation. . . . . . . Upgrading Windows 2000 Professional to XP Professional . . . . . . Windows 2000 Service Pack 2 Installation . . . . . . . . . . . . . . . . . . . . Checking for Windows 2000 Service Pack 2 . . . . . . . . . . . . . . . Installing Windows 2000 Service Pack 2 . . . . . . . . . . . . . . . . . .
Table of Contents iii Determining the Current RSLinx Version . . . . . . . . . . . . . . . . . Installing the Activation File . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring RSLinx Drivers for ControlNet Supervisory Network Updating the 1784-PCIC Firmware . . . . . . . . . . . . . . . . . . . . . . Starting Network Tools Application . . . . . . . . . . . . . . . . . . Updating the 1784-PCIC Firmware . . . . . . . . . . . . . . . . . . .
iv Table of Contents Saving R400.0 Data to a Remote PC. . . . . . . . . . . . . . . . . . . . . . . . . Networking an R400.0 Server to a Remote PC . . . . . . . . . . . . . Transferring Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing ProcessLogix R400.0 Software . . . . . . . . . . . . . . . . . . . . Removal of Selected ProcessLogix R400.0 Components . . . . . Remove ProcessLogix Server Components . . . . . . . . . . . . . . . . Remove Remaining ProcessLogix R400.
Table of Contents v Upgrade R400.0 Windows NT 4.0 Client to R500.1 Windows 2000 XP Client (Clean Install). . . . . . . . . . . . . . . . . 5-8 Upgrade R320.0 Windows NT 4.0 Client to R500.1 Windows 2000 XP Client (Clean Install). . . . . . . . . . . . . . . . . 5-9 Saving Important Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10 Networking an R320.0 Client to a Remote PC. . . . . . . . . . . . . . . . . 5-11 Networking an R400.0 Client to a Remote PC. . . . . . . . . . . .
vi Table of Contents Configuring the Time Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9 Confirming Data Link is Available . . . . . . . . . . . . . . . . . . . . . . . . 6-9 Configuring Stations in Quick Builder (on SERVERA) . . . . . . . . . 6-11 Setting Up Station on SERVERA . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12 Setting Up Station on SERVERB . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15 Setting up the Redundant ERDB . . . . . . . . . . . . . . . .
Table of Contents vii Chapter 8 Supplementary Procedures Stopping ProcessLogix Applications and Services . . . . . . . . . . . . . . . 8-1 Installing Knowledge Builder on a Non-ProcessLogix System . . . . . 8-2 Installing Knowledge Builder on Windows 2000. . . . . . . . . . . . . 8-2 Installing Knowledge Builder on Windows XP . . . . . . . . . . . . . . 8-3 Removing Knowledge Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3 Installing Knowledge Builder . . . . . . . . . . . . . . . . . .
viii Table of Contents Adding 1757-PLX52 Controller Redundancy to R500.1 Non-Redundant 1757-PLX52 Controller Configurations . . . . . Deleting a Non-Redundant 1757-PLX52 and Unassigning its Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing and connecting Redundant Chassis Pair (RCP) Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating Firmware Revision Levels . . . . . . . . . . . . . . . . . . . . . . Creating a Redundant 1757-PLX52 . . . . . .
Table of Contents ix Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2 Client Platform Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4 Application Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4 User Interface Capacity and Performance . . . . . . . . . . . . . . . . . 11-6 Control Builder Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . 11-7 Server Redundancy . . . . . . . . . . . . . . . .
x Table of Contents Publication 1757-IN500A-EN-P - September 2002
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.
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. Refer to Minimum Hardware Requirements on page P-2 for information about ProcessLogix Server hardware. • ProcessLogix Client Stations require a Windows 2000 Professional, XP Professional or 2000 Server operating system. See Table 11.
Preface Contents of Release 3 The following software and documentation components are included in the ProcessLogix R500.1 Software/documentation kit (1757-SWKIT5000). Table P.1 ProcessLogix R500.1 Release Components Release Components Pub/Part Number ProcessLogix R500.1 Base Software CD • SQL Server 2000 957678-70 ProcessLogix R500.1 Application Software CD • ProcessLogix Engineering Tools • ProcessLogix Server Software • RSLinx 2.31 957678-71 ProcessLogix R500.
Preface 4 ProcessLogix R500.1 Software Change Notice is incorporated into this Installation and Upgrade Guide in the following chapters: Table P.2 Installation and Upgrade Guide SCN Chapter Descriptions Chapter Removing the Default Startup Screens Description 9 New Functions and Features 10 Major ProcessLogix Software Components 11 Performance and Capacity Specifications Throughout this document there will be times when you need to remove the default startup screens.
Preface Rockwell Automation Technical Support 5 Rockwell Automation offers support services worldwide, with over 75 sales/support offices, 512 authorized distributors, and 260 authorized systems integrators located throughout the United States alone, plus Rockwell Automation representatives in every major country in the world.
Preface 6 Conventions Terms and Type Representations The following table summarizes the terms and type representation conventions used in this Guide. Table P.3 : Terms and Type Representations Publication 1757-IN500A-EN-P - September 2002 Term/Type Representation Meaning Example click, click on, click [button name] 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.
Preface 7 Acronyms and Abbreviations Table P.
Preface 8 Notes: Publication 1757-IN500A-EN-P - September 2002
Chapter 1 ProcessLogix R500.1 Installation Introduction Operating System Support The following table shows the supported operating systems for ProcessLogix. Table 1.A ProcessLogix Component Configuration Table ProcessLogix R500.1 Windows 2000 Server Server ✔ Client ✔(1) (1) Windows XP Professional Professional ✔ ✔ Windows 2000 Server is not recommended as a Client for ProcessLogix R500.1 due to the default standard hardware and operating system requirements. Windows NT 4.
1-2 ProcessLogix R500.1 Installation Introduction ProcessLogix Server Supported Installations IMPORTANT If you purchased a new ProcessLogix R500.1 Server from Rockwell Automation, the operating system and ProcessLogix software have already been installed. Do not reinstall the software. Refer to the ProcessLogix R500.1 Server Installation Instructions, publication 1757-IN950 shipped with your hardware. It is strongly recommended that you name your Server properly prior to installing ProcessLogix R500.
ProcessLogix R500.1 Installation Introduction ProcessLogix Client Supported Installations 1-3 The ProcessLogix R500.1 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 R500.1 Client Install Options Step 1: Select an R500.
1-4 ProcessLogix R500.
Chapter 2 Operating System Installation Procedures IMPORTANT These installation scenarios use a “clean” PC installation method in which all data on the system will be erased. This is an irrecoverable action. All data must be first backed up or transferred to another system before proceeding. • ProcessLogix R500.1 Servers require the Windows 2000 Server operating system. • ProcessLogix R500.1 Client Stations may use Windows 2000 Professional, Windows XP Professional or Windows 2000 Server.
2-2 Operating System Installation Procedures Installing Windows 2000 Server on a New System You must install Windows 2000 Server on your Server before you can install or run the ProcessLogix R500.1 software. The current required Operating System components are: • Windows 2000 Server with Windows 2000 Service Pack 2 and Windows 2000 Security Rollup • Internet Explorer 6 with the Internet Explorer 6.
Operating System Installation Procedures 2-3 If you received your PC from the manufacturer with Windows 2000 Server pre-installed, skip to Internet Explorer 6.0 Security Update Installation on page 2-34. TIP Consult the PC Manufacturer for any specialized instructions/procedures related to the installation of the Microsoft Windows 2000 Server operating system. This procedure lists only the generic installation procedure.
2-4 Operating System Installation Procedures 4. At the DOS prompt, enter the CD-ROM drive letter: >D:< and press . 5. Enter this command: >cd bootdisk< and press . 6. Enter this command: >makeboot< and press . 7. Enter floppy disk drive letter: >A<. 8. Follow the on-screen prompts for inserting, labeling, and creating the four floppy disks. IMPORTANT Server Boot floppies and Professional Boot floppies are different. 9. Be sure to label your floppy disks. 10.
Operating System Installation Procedures 2-5 5. Press on the Welcome to Setup screen. IMPORTANT If your installation requires additional Manufacturer’s Drivers, press the F6 key during the boot process and follow the on-screen instructions for adding the necessary drivers. 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 of the PC. 2.
2-6 Operating System Installation Procedures 3. If necessary, press to continue installing a fresh copy of Windows 2000. IMPORTANT TIP If existing partitions are found, delete all of them first before proceeding. Use the on-screen instructions to perform this task. Certain PCs will limit the size of the partition that you can create. Windows 2000 supports a boot partition size up to 32 Gigabytes on a NTFS formatted drive. Use the entire hard disk if possible.
Operating System Installation Procedures 2-7 10. Enter your Windows 2000 Server Product Key and click Next. 11. Choose your Server’s Licensing Mode: Rockwell Automation recommends that you choose 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.
2-8 Operating System Installation Procedures IMPORTANT PC Naming Rules The base name cannot contain more than 13 alphanumeric characters and must contain no spaces. The full computer name cannot contain more than 14 alphanumeric characters. The following naming conventions are required for given ProcessLogix system architectures. For non-redundant Server, be sure the name does not end in the letter “A” or “B”. The default name is PLX1.
Operating System Installation Procedures 2-9 a. If necessary, adjust the Date and Time settings. a. Set the appropriate Time Zone for your location. b. Uncheck the Automatically adjust clock for daylight saving changes option. c. Click Next. ATTENTION ! Failure to uncheck the Automatic adjustment for Daylight Savings Time will cause Redundant Systems to loose “Sync” when the time is automatically adjusted.
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.
Operating System Installation Procedures 2-11 c. Click Next. TIP All systems which are configured for this Process Control System should utilize the same Workgroup Name for easier operations. At this point in the installation, setup will finish installing Windows 2000. This will take some time depending on your hardware configuration. 21. At the Completing the Setup Wizard window, remove the Windows 2000 Server CD and click Finish. The PC will reboot.
2-12 Operating System Installation Procedures Starting the Windows 2000 Professional Installation This procedure assumes: • All network cards are installed in the PC and they are set to the correct IRQs. • All supporting ProcessLogix system hardware is installed and connected to the PC. • The PC meets specified hardware and software requirements. Navigate in Knowledge Builder to Server and Client Installation Guide⇒Before Installing ProcessLogix⇒Hardware and Software Requirements for more information.
Operating System Installation Procedures 2-13 You will need: • 4 blank 3.5” 1.44 Mb (High Density) Floppy Disks • 1.44 MB Floppy Drive • CD-ROM Drive • DOS or Windows based Operating System with access to CD-ROM and floppy devices. 1. Insert the Windows 2000 Professional CD into the CD-ROM drive. 2. Click Start ⇒ Run. 3. Enter this command: >cmd< and click OK to open the DOS window. 4. At the DOS prompt, enter: >D:< and press . 5. Enter this command: >cd bootdisk< and press . 6.
2-14 Operating System Installation Procedures Starting the Windows 2000 Professional Installation from the Boot Floppies 1. With the PCs’ power off, insert the diskette titled Windows 2000 Setup Boot Disk into the floppy disk drive. 2. Turn on the PC. 3. Insert the Microsoft Windows 2000 Professional CD into the CD-ROM drive. 4. Follow the on-screen prompts to remove and insert the Windows 2000 Professional Setup Disks 2, 3, and 4 when instructed to do so. 5.
Operating System Installation Procedures 2-15 Completing the Windows 2000 Professional Installation 1. Press on Welcome to Setup Screen. 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 will stop and prompt you for additional Manufacturer’s Drivers. Follow the on-screen instructions for adding the necessary drivers. 3.
2-16 Operating System Installation Procedures 9. Enter the appropriate Name and Organization name and click Next. 10. Enter your Windows 2000 Professional Product Key and click Next. 11. 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. For a ProcessLogix Client, be sure the name does not end in the letter “A” or “B”.
Operating System Installation Procedures 2-17 14. At the Networking Components window, select Internet Protocol (TCP/IP) and click Properties. 15. In the Networking Components Window, a. Click the Use the following IP address option. b. Enter the appropriate IP address information. The following Private Networking IP Address scheme can be utilized for the system to operate: Table 2.B Private Networking IP Address scheme PC Type Suggested Private Networking IP Address Client NIC 1: 192.168.0.
2-18 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.
Operating System Installation Procedures TIP 2-19 All systems which are configured for this Process Control System should utilize the same Workgroup Name for easier operations. At this point in the installation, setup will finish installing Windows 2000. This will take some time depending on your hardware configuration. 19. At the Completing the Setup Wizard window, remove the Windows 2000 Professional CD and click Finish. The PC will reboot.
2-20 Operating System Installation Procedures See Table 11.B: Client Platform Requirements based on System Configurations on 11-4 to review the ProcessLogix Client platform requirements. • All manufacturers related driver diskettes are available to complete the installation. IMPORTANT For ProcessLogix Client software to operate correctly, Windows XP MUST be installed to C:\winnt.
Operating System Installation Procedures 2-21 8. Press any key to boot from the CD-ROM. IMPORTANT If your installation requires additional Manufacturer’s Drivers, press during the boot process and follow the on-screen instructions for adding the necessary drivers. Completing the Windows XP Professional Installation 1. Press on the Welcome to Setup Screen.
2-22 Operating System Installation Procedures 7. Format the partition using the NTFS file system. Setup will format the partition. This takes a few minutes to complete. The computer will automatically reboot. Be sure to remove floppy disk from the floppy disk drive. 8. Verify the information on the Regional and Language options windows and click Next. 9. Enter the appropriate Name and Organization and click Next. 10. Enter your Windows XP Professional Product Key and click Next. 11.
Operating System Installation Procedures 2-23 d. Click Next. ATTENTION ! TIP Failure to uncheck the Automatic adjustment for Daylight Savings Time will cause Redundant Systems to loose “Sync” when the time is automatically adjusted. Choosing not to automatically adjust the time allows you to decide when to make the adjustment (at a time that is not critical to your process). If setup has not found a suitable Network Device, you will be prompted for installing one.
2-24 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.
Operating System Installation Procedures TIP 2-25 All systems which are configured for this Process Control System should use the same Workgroup Name for easier operations. At this point in the installation, setup will finish installing Windows XP. This will take some time depending on your hardware configuration. The PC will automatically reboot. 19. If you see a Display settings prompt, click OK. 20. At the Welcome to Microsoft Windows screen, click Next. 21.
2-26 Operating System Installation Procedures 31. Logon to the system as Administrator. 32. Click Start, right click the My Computer icon and select Manage. 33. Click the + sign to expand Local Users and Groups. 34. Click the Users folder. 35. Right click the >xptemp< user account and select Delete. 36. Click Yes to confirm. 37. Close the Computer Management window. 38. Continue with Internet Explorer 6.0 Security Update Installation on page 2-34.
Operating System Installation Procedures 2-27 This may take 30-60 minutes to complete. After reboot, the installation will cycle through the following: • • • Preparing Installation Installing Windows Finalizing Installation When completed, the system will automatically reboot. 9. At the Welcome to Microsoft Windows screen, click Next. IMPORTANT Microsoft Windows XP Professional must be registered with the Microsoft Corporation, but registration is not required at this time.
2-28 Operating System Installation Procedures Windows 2000 Service Pack 2 Installation Checking for Windows 2000 Service Pack 2 Before performing this installation, check the Microsoft Windows 2000 CDs to see if they have Service Pack 2 integrated. (This depends on when the software was purchased.) If Service Pack 2 has already been installed, you can skip to Windows 2000 Security Rollup Installation on page 2-30.
Operating System Installation Procedures 2-29 Installing Windows 2000 Service Pack 2 1. Logon to the system as Administrator. TIP If this is the first time start since the Windows 2000 operating system install, it will be necessary to remove the default startup screens. Refer to Removing the Default Startup Screens on page P-4. 2. Insert the ProcessLogix R500.1 Supplemental Software CD into the CD-ROM drive. 3. Click Start ⇒ Run. 4.
2-30 Operating System Installation Procedures Windows 2000 Security Rollup Installation Checking for the Windows 2000 Security Rollup All systems are required to install the Windows 2000 Security Rollup. You can check the version currently installed by doing the following: 1. Logon to the system as Administrator. TIP If this is the first time start since the Windows 2000 operating system install, it will be necessary to remove the default startup screens.
Operating System Installation Procedures 2-31 5. Click OK. 6. At the Welcome window, click Next. 7. Click the I agree option and click Next. 8. Click Finish. The system will automatically restart.
2-32 Operating System Installation Procedures Internet Explorer 6.0 Installation Checking the Internet Explorer Version All systems are required to use Internet Explorer 6.0. If you are using Windows XP Professional, IE6 is already installed. Skip to Internet Explorer 6.0 Security Update Installation on page 2-34. To check the version of Internet Explorer that is installed, do the following: 1. Logon to the system as Administrator.
Operating System Installation Procedures 2-33 Installing Internet Explorer 6.0 All systems are required to use Internet Explorer 6.0. Follow these steps to install Internet Explorer 6.0: 1. Logon to the system as Administrator. TIP If this is the first time start since the Windows 2000 operating system install, it will be necessary to remove the default startup screens. Refer to Removing the Default Startup Screens on page P-4. 2. Insert the ProcessLogix R500.
2-34 Operating System Installation Procedures Internet Explorer 6.0 Security Update Installation Checking for the Internet Explorer 6.0 Security Update All systems are required to install the Internet Explorer Security Update. The task must be performed after Internet Explorer 6.0 has been installed. Perform the follow tasks to see if your system has the package already installed: 1. Logon to the system as Administrator.
Operating System Installation Procedures 2-35 Installing Security Update for Internet Explorer 6.0 All systems are required to install the Internet Explorer 6.0 Security Update. The task must be performed after Internet Explorer 6.0 has been installed. Perform the following tasks to install the Internet Explorer 6.0 Security Update: 1. Logon to the system as Administrator.
2-36 Operating System Installation Procedures Updating Windows Installer IMPORTANT If using Windows XP Professional, do not perform this update as it is not necessary. Windows XP Professional has the most recent update for the Windows Installer. 1. Logon to the system as Administrator. TIP If this is the first time start since the Windows 2000 operating system install, it will be necessary to remove the default startup screens. Refer to Removing the Default Startup Screens on page P-4. 2.
Operating System Installation Procedures Additional Operating System Customization Procedures 2-37 All procedures in this section assume that you are logged onto the system with Administrator access. 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 (High Color, 16 bit). Utilizing any other setting will produce anomalies in some displays.
2-38 Operating System Installation Procedures Setting Up Additional Drivers Using the Microsoft Windows 2000 or XP Operating System CDs to perform an installation contains only a finite set of drivers for the most common hardware items at the time of its release. Rockwell Automation considers this set to be the “base” set of drivers. Manufacturers will update their drivers over time to fix anomalies or provide additional features that were not available at the time of their release on the CD.
Operating System Installation Procedures 2-39 Table 2.D Required System Settings for ProcessLogix R500.1 software Creating an Emergency Repair Disk Function Required Setting Value Dynamic Host Configuration Protocol (DHCP) IP Addressing ProcessLogix System requires that all specified IP address are fixed and known. We recommend that you do not use DHCP, but if your organization requires it, use only reserved addressing.
2-40 Operating System Installation Procedures Windows XP Use the following procedure to create a recovery disk for your Windows XP installation. 1. Insert a blank diskette into the PC's floppy drive. 2. Click Start ⇒ Programs ⇒ Accessories ⇒ System Tools ⇒ Backup. 3. If the Backup or Restore Wizard appears, click Advanced Mode. 4. Click Automated System Recovery Wizard. 5. Click Next. 6. Enter a backup media or file name and click Next. 7. Click Finish. 8.
Operating System Installation Procedures 2-41 You must create a Process User account to be used to perform the ProcessLogix R500.1 Software installation. Follow the steps below to create and logon with the ps_user and erserver accounts. Creating the ProcessLogix User Accounts IMPORTANT All R500.1 Systems are required to use the ps_user account. This is a change from R320.0, where most systems used the plx_user account.
2-42 Operating System Installation Procedures 10. Click Close. 11. Double Click the ps_user account. 12. Click the Member of tab. 13. Click Add. 14. In Windows 2000, Under Name, click on Administrators and click Add. In Windows XP, type Administrators in the object name field. 15. Click OK. 16. Click Apply. 17. Close the user properties window. 18. On ProcessLogix Servers, repeat steps 11 through 14 for the erserver account. 19. Close the Computer Management window.
Chapter 3 ProcessLogix Server Installation Procedures Installing ProcessLogix Software on a Clean PC Rockwell Automation delivers 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. The following table lists the items that you MUST complete before attempting to install the ProcessLogix software.
3-2 ProcessLogix Server Installation Procedures IMPORTANT PC Naming Requirements Before installing ProcessLogix R500.1, you must verify that your computer name follows the PC naming requirements. Refer to PC Naming Rules on page 2-8. It is strongly recommended that you name your Server properly prior to installing ProcessLogix R500.1 software. To change the Server name prior to installing ProcessLogix R500.1, follow the procedures in Changing the Computer Name on a ProcessLogix Client on page 8-23.
ProcessLogix Server Installation Procedures 3-3 • Client/Server (Display Builder, Station, Server, etc.) IMPORTANT If you plan to use Microsoft Excel Data Exchange, Microsoft Excel must be installed before installing ProcessLogix. Prior to the ProcessLogix installation, it is mandatory that the Excel macro security level is set to Medium. To change the security level for macro virus protection in Excel: 1. On the Tools menu, click Macro, then click Security. 2.
3-4 ProcessLogix Server Installation Procedures Installing ProcessLogix Product 1. Insert the ProcessLogix R500.1 Base Software CD into the CD-ROM drive. 2. Click Start ⇒ Run. 3. Enter this path or Browse to: >D:(or your CD-ROM drive letter)\SETUP.EXE< 4. Click OK to launch the software setup application. 5. Click the ProcessLogix Server option and click Next. IMPORTANT You must have either a PCIC or Ethernet card installed in your ProcessLogix Server to install R500.1. 6.
ProcessLogix Server Installation Procedures 3-5 2. When the following dialog appears, click OK to reboot the PC. You will see a system shutdown warning. 3. The system will shutdown and re-start. Normally, no actions are necessary on your part. Do not press any keys, buttons, etc. during shutdown and restart. However, if the system displays the logon window for more than about ten (10) seconds, logon as ps_user. TIP Upon restarting the system, you may receive: • a message that a service failed to start.
3-6 ProcessLogix Server Installation Procedures Installing Knowledge Builder 1. Insert the ProcessLogix R500.1 Knowledge Builder CD into the CD-ROM drive and click Yes. ATTENTION ! Clicking No will abort the entire ProcessLogix installation. 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.
ProcessLogix Server Installation Procedures 3-7 9. At the Server selection window: • If installing Full, click Next to accept the default directory for Knowledge Builder. • If installing Client, click Browse and select the appropriate Server location. For example, the location of the Full version of KB might be E:\Docs where E:\ is a mapped drive to C:\ProgramFiles\Honeywell\PST_Server\Knowledge Builder on PLX1A. 10. At the Start Copy window, click Next. 11.
3-8 ProcessLogix Server Installation Procedures Installing Engineering Tools 1. At the Ready to Install window, click Install. TIP Command windows will appear during Engineering Tools installation. These windows will close automatically. 2. At the Installation Complete window, click Finish. 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.
ProcessLogix Server Installation Procedures 3-9 Installing the ProcessLogix Server 1. At the Welcome to ProcessLogix Server Setup window, click Next. 2. At the Choose Setup Type window, click ProcessLogix Server 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 Next. TIP You must install Microsoft Excel prior to installing Microsoft Excel Data Exchange. 4.
3-10 ProcessLogix Server Installation Procedures 9. Skip to Step 11 if the Specify Microsoft Excel Directory window doesn’t appear. Otherwise, click Next to accept the default directory for Microsoft Excel. IMPORTANT We recommend that you answer No to the question: Do you want Microsoft Excel Data Exchange to be allowed to write to a ProcessLogix Server database? If you answer Yes, the write option is enabled and it is possible for anyone with access to the machine to write to the Server database. 10.
ProcessLogix Server Installation Procedures 3-11 18. At the Choose point mode acronyms window, click the Default acronyms option and click Next. 19. At the Choose Fast History Rate window, choose a Fast History collection rate and click Next. 5 seconds is the default rate. TIP To change the Fast History Collection Rate after installation is complete, click Start ⇒ Programs ⇒ ProcessLogix Server ⇒ Setup. 20. Review the software installation details summarized in the Confirmation window.
3-12 ProcessLogix Server Installation Procedures 26. Wait until after the command windows have closed and file copying is complete, then click the No, I will restart my computer later option and click Finish. ATTENTION ! If you are installing ProcessLogix software on a redundant Server pair: 1. Do not restart SERVERA. 2. Return to the beginning of Installing ProcessLogix Software on a Clean PC on page 3-1 and repeat for SERVERB. 3.
ProcessLogix Server Installation Procedures Moving the RSLinx Activation File 3-13 About the Activation File Use the following procedure 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.
3-14 ProcessLogix Server Installation Procedures • If the title is RSLinx Lite go to Step 3. • If the title is RSLinx OEM you already have the OEM version installed and you do not have to install the activation file. – For ControlNet Supervisory Networks, skip to Configuring RSLinx Drivers for ControlNet Supervisory Network on page 3-15. – For Ethernet Supervisory Networks, skip to Configuring RSLinx Drivers for Ethernet Supervisory Network on page 3-19. 3. Close RSLinx.
ProcessLogix Server Installation Procedures 3-15 9. Restart the PC. TIP IMPORTANT If you need to reformat the hard drive, you must first move the evrsi.sys file back to this Master Disk using this same general procedure; otherwise, the file will be corrupted. Refer to Removing the RSLinx Software Activation File on page 4-9. If you are installing ProcessLogix software on a redundant Server pair, return to the beginning of Moving the RSLinx Activation File on page 3-13 and repeat for SERVERB.
3-16 ProcessLogix Server Installation Procedures 3. Click the 1784-PCIC(S) for ControlNet devices selection in the Available Drivers list box and click Add New to call up the Add New RSLinx Driver dialog box. 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.
ProcessLogix Server Installation Procedures 3-17 10. Restart the PC. IMPORTANT Whenever the 1784-PCIC driver has been updated or the Network Address is changed, the 1784-PCIC driver must be stopped and restarted to complete the change. You must power down the PC.
3-18 ProcessLogix Server Installation Procedures 9. Click Yes to acknowledge the Warning prompt. 10. Navigate to the directory: C:\Honeywell\TPS50\System\Firmware\1784-PCIC\3_6_38 11. Click the 2MnBtPcic3x.nvs file so it appears in the File name entry field. 12. Click Open to start the firmware load and click Yes to confirm. 13. Wait for the load to complete. The Status field in the lower portion of the Network Tools window tracks the load progress. 14.
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-15. 1. Verify the settings of the Ethernet Network Interface card to be used to communicate with the controller.
3-20 ProcessLogix Server Installation Procedures Completing the ProcessLogix R500.1 Install on a Redundant Server Pair Refer to Completing the ProcessLogix R500.1 Setup on a Redundant Server Pair on page 6-1. Upgrading Hardware Component Firmware Completing the ProcessLogix R500.1 Install 1. Refer to Loading 1757-PLX52, TC-MUX021, or 1757-FIM Boot and on a Non-Redundant Server Personality Images on page 7-9 to upgrade the 1757-PLX52 boot and personality images to the current release level. 2.
ProcessLogix Server Installation Procedures 3-21 7. Enter the New Password, Confirm the New Password and click OK. The message Password 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.
3-22 ProcessLogix Server Installation Procedures An Emergency Repair Diskette window appears. 4. Insert a blank diskette into the PC's floppy drive. 5. Check the Also back up the registry to the repair directory checkbox and click OK. 6. When finished, click OK. 7. Repeat Steps 1 through 5 with another blank formatted diskette. 8. Click Job ⇒ Exit. 9. Store the two diskettes in different places to protect against damage to the diskettes.
Chapter 4 ProcessLogix Server Upgrade Procedures ProcessLogix Server Upgrade Scenarios Upgrade R320.0 Server to R500.1 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 R500.1 Server requires that you purchase a new PC and complete a clean R500.1 Server installation on Windows 2000 Server.
4-2 ProcessLogix Server Upgrade Procedures Upgrade R400.0 Server to R500.1 This section describes the steps necessary to upgrade the ProcessLogix R400.0 Server software to R500.0. There are two upgrade options. IMPORTANT Due to the nature of this upgrade, it is recommended that you follow Option 2 (Clean install) when upgrading from R400.0 to R500.1. Upgrading R400.0 Server to R500.1: Option 1 a. b. c. d. Backup your data. Uninstall your current ProcessLogix software. Install ProcessLogix R500.1.
ProcessLogix Server Upgrade Procedures 4-3 Table 4.C Upgrading R400.0 Server to R500.1 Option 2 Checklist ✔ Preparing for a ProcessLogix R320.0 to R500.1 Server Upgrade Step Page 3. Installing ProcessLogix Software on a Clean PC 3-1 4. Finalizing R400.0 to R500.1 Upgrade 4-27 5. Restoring ProcessLogix Data 4-28 ATTENTION ! Item All procedures in this section should be performed with the system(s) Off-Process.
4-4 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 with Contents of your Control Modules. 2. Update to Project, which will save the Monitor image to the Project image. This procedure captures the latest configuration changes.
ProcessLogix Server Upgrade Procedures 4-5 b. Enter >mngr1< as the default Password. c. Enter >localhost< in the Server Name field. 4. Click OK. 5. Click File ⇒ Export. 6. Click Browse to set the Directory Path to C:\Data\ExportDB. 7. Click Select All. a. Depending on the size of your database, this may take several minutes. It is recommended that you do not export the examples. New examples are provided with R500.1. b. To deselect an item, hold Ctrl and click each item. c.
4-6 ProcessLogix Server Upgrade Procedures Saving Important R320.0 Server Data Each of the following items should be considered on an R320.0 Server before proceeding. Table 4.D Upgrading an R320.0 Server Considerations Item Pre-upgrade Requirement Post-upgrade Folders and Files The following folders and their sub-folders may contain Copy backed up folders and files from the backup files you will require after upgrading. (For example.
ProcessLogix Server Upgrade Procedures 4-7 Table 4.D Upgrading an R320.0 Server Considerations Item Pre-upgrade Requirement Post-upgrade Station setup file Document any changes that were made to the default Station setup file. The new default setup file is configured to as “static Station 1”. If this is not correct, you must make the appropriate changes via Station’s Setup menu.
4-8 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. Refer to Stopping ProcessLogix Applications and Services on page 8-1. If you have redundant servers, you must complete this procedure on the SERVERB node first. Then complete the entire procedure again for the SERVERA node.
ProcessLogix Server Upgrade Procedures 4-9 Removing the RSLinx Software Activation File It is possible to transfer your RSLinx Activation codes from the old system to the new system. To move the activation file from your R320.0 Server, 1. Locate the RSLinx Master Disk and insert it into the floppy drive. 2. Click Start ⇒ Run. 3. Enter this path or the evmove.exe file on the diskette. >A:(or your floppy drive letter)\EVMOVE.EXE< 4. Click OK to launch the move executive. 5.
4-10 ProcessLogix Server Upgrade Procedures Copying R320.0 Data to the R500.1 Server Networking the R320.0 and R500.1 Servers Use the following procedure to map a drive to the new R500.1 Server. 1. Logon to the R320.0 Server as plx_user. 2. Click Start ⇒ Run. 3. Enter this command: >cmd< and click OK to open the DOS window. 4. If you have a non-redundant server, enter this command: >NET USE T: \\PLX1\C$ /user:ps_user< (where PLX1 is the R500.1 Server name) and press . 5.
ProcessLogix Server Upgrade Procedures 4-11 b. On SERVERA, enter this command: >NET USE T: \\PLX1A\C$ /user:ps_user< (where PLX1A is the name of the R500.1 Primary Server) and press . c. Open Windows Explorer on each R320.0 Server and confirm that the T: drive exists. Transferring R320.0 Data to the R500.1 Server 1. On the R320.0 Server(s), click Start ⇒ Run. 2. Enter this command: >cmd< and click OK to open the DOS window. 3. If you have a non-redundant server: a.
4-12 ProcessLogix Server Upgrade Procedures a. On SERVERA, enter this command: >xcopy C:\Data\*.* T:\R320PrimaryData\ /E< and press . b. If necessary, enter >D< to specify that R320PrimaryData is a directory. c. Wait until the C:\ prompt appears and close the DOS window. d. On SERVERB, enter this command: >xcopy C:\Data\*.* T:\R320BackupData\ /E< and press . e. If necessary, enter >D< to specify that R320BackupData is a directory. f.
ProcessLogix Server Upgrade Procedures Transferring the 1784-PCIC Card to the R500.1 System 4-13 The following procedure describes how to transfer the 1784-PCIC card from your R320.0 system to an R500.1 system. 1. If you R500.1 system already contains an 1784-PCIC card, skip to Restoring ProcessLogix Data on page 4-28. 2. Shut down and turn the power off to both the R320.0 and R500.1 Server(s). ATTENTION ! You must turn the power off to both systems before attempting to transfer hardware.
4-14 ProcessLogix Server Upgrade Procedures >D:(or your CD-ROM drive letter) \RSLinx\RSLinx\PlugNPlay\Win2K\1784-PCIC(S)\abpcic.inf< 16. Click OK. 17. Click Next to install the driver. 18. If a Digital Signature Not Found window appears, click Yes. 19. If necessary, click Yes to overwrite the VirtualBackplane.sys file. 20. If necessary, click Yes to overwrite the ABPCICSW.sys file. 21. Click Finish. Preparing for a ProcessLogix R400.0 to R500.
ProcessLogix Server Upgrade Procedures 4-15 Disabling ERDB Replication This procedure is only required for a Redundant Server Pair. Perform these steps on SERVERB only. If you have a non-redundant server, skip to Exporting the Database Using Control Builder on page 4-15. 1. Logon to the SERVERB as ps_user. 2. Click Start ⇒ Programs ⇒ ProcessLogix Engineering Tools ⇒ DB Admin. 3. Click the + sign to expand DbAdmin. 4. In the Login dialog box make these entries: a. Enter >mngr< as the default User Name. b.
4-16 ProcessLogix Server Upgrade Procedures 6. Click Browse to set the Directory to export the data to C:\Data\ExportDB. 7. Click Select All. a. Depending on the size of your database, this may take several minutes. It is recommended that you do not export the examples. New examples are provided with R500.1. b. To deselect an item, hold Ctrl and click each item. c. Deselect the following Point Names: example_cascade example_motor example_pid example_scm pidloop 4. Click Export.
ProcessLogix Server Upgrade Procedures 4-17 5. Enter this command: xcopy C:\Honeywell\TPS50\System\ER\FFdevices\*.* C:\Data\FFdevices /E and press . 6. If prompted, enter >A< to specify all files and folders. 7. Enter this command: xcopy C:\Honeywell\TPS50\System\ER\Release\*.* C:\Data\FFdevices /E and press . 8. If prompted, enter >A< to specify all files and folders.
4-18 ProcessLogix Server Upgrade Procedures Saving Important R400.0 Server Data Each of the following items should be considered on an R400.0 Server before proceeding. IMPORTANT Redundant ProcessLogix Systems All steps need to be performed on both the Primary (SERVERA) and Backup (SERVERB) ProcessLogix Servers. Table 4.E Upgrading an R400.
ProcessLogix Server Upgrade Procedures 4-19 Table 4.E Upgrading an R400.0 Server Considerations Item Pre-upgrade Requirement Post-upgrade Station configuration file C:\Winnt\station.ini Document any changes that were made to the station.ini file. • The IconPopToTopOnAlarm option has been removed, and is no longer recognized by Station. Its replacement is FlashWindowOnAlarm, which enables Station to flash its title bar and taskbar icon when an alarm is generated. This behavior is disabled by default.
4-20 ProcessLogix Server Upgrade Procedures Table 4.E Upgrading an R400.0 Server Considerations Item Pre-upgrade Requirement Post-upgrade Hardware definition files If you want to use existing hardware definition (hdwbld) files to build printers, you must change the CYRILLIC keyword to LANGUAGE=CYRILLIC. Alarms and messages Resolve any alarms before starting the upgrade. Alarms and messages currently in the system cannot be copied across for the upgrade.
ProcessLogix Server Upgrade Procedures 4-21 5. If necessary, enter >D< to specify that backup is a directory. 6. Wait until the C:\ prompt appears and close the DOS window. IMPORTANT REDUNDANT PROCESSLOGIX SYSTEMS You must now disconnect all Ethernet network cables on the node you are currently upgrading (SERVERA or SERVERB) before proceeding to the next step. The network cables should be reconnected only after both Servers have been upgraded.
4-22 ProcessLogix Server Upgrade Procedures Saving R400.0 Data to a Remote PC Networking an R400.0 Server to a Remote PC Use the following procedure to map a drive to a remote PC. 1. Logon to the R400.0 Server as ps_user. 2. Click Start ⇒ Run. 3. Enter this command: >cmd< and click OK to open the DOS window. 4. Enter this command: >NET USE T: \\STN01\C$ /user:ps_user< (where STN01 is the remote PC name and ps_user is the user currently logged on to STN01.) and press . 5.
ProcessLogix Server Upgrade Procedures 4-23 a. On SERVERA, enter this command: xcopy C:\Data\*.* T:\R400PrimaryData /E and press . b. On SERVERB, enter this command: xcopy C:\Data\*.* T:\R400BackupData /E and press . Removing ProcessLogix R400.
4-24 ProcessLogix Server Upgrade Procedures a. Click on the appropriate program in the list of installed programs. b. Click Add/Remove, Change/Remove or Remove. c. Click Yes to confirm removal. d. Repeat the steps for each component in the following order. IMPORTANT Be sure to remove the components in the order they are listed below. Table 4.F Removal of Selected ProcessLogix R400.0 Components ✔ Order Component 1. ProcessLogix Update 2.
ProcessLogix Server Upgrade Procedures 4-25 Remove Remaining ProcessLogix R400.0 Components 1. If necessary, logon to the system as ps_user. 2. Click Start ⇒ Settings ⇒ Control Panel. 3. Double-click Add/Remove Programs. 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. 4. To remove a program: a. Click on the appropriate program in the list of installed programs. b.
4-26 ProcessLogix Server Upgrade Procedures Verifying and Finalizing Component Removal IMPORTANT When you remove a program, its name may not automatically disappear from the Add/Remove Programs window. Do not remove the program again, continue with the next program on the list. 1. Close the Add/Remove Programs window. 2. Double-click Add/Remove Programs in the Control Panel window. 3. If any of the following programs are still present in the Add/Remove programs list, select and remove them.
ProcessLogix Server Upgrade Procedures 4-27 11. Empty the Recycle Bin. 12. Restart the PC. Installing ProcessLogix R500.1 Software The following table lists the items you MUST complete to install the ProcessLogix software. ✔ Finalizing R400.0 to R500.1 Upgrade Step Item Page 1. Windows 2000 Service Pack 2 Installation 2-28 2. Windows 2000 Security Rollup Installation 2-30 3. Internet Explorer 6.0 Installation 2-32 4. Internet Explorer 6.0 Security Update Installation 2-34 5.
4-28 ProcessLogix Server Upgrade Procedures a. On SERVERA, enter this command: xcopy T:\R400PrimaryData\*.* C:\R400PrimaryData /E and press . b. On SERVERB, enter this command: xcopy T:\R400BackupData\*.* C:\R400BackupData /E and press . Restoring ProcessLogix Data Each of the following items should be considered before proceeding. Table 4.
ProcessLogix Server Upgrade Procedures 4-29 Table 4.H Restoring ProcessLogix Data Considerations Item Post-upgrade Custom applications Custom applications must be re-compiled and re-linked using an appropriate development environment. Navigate in Knowledge Builder to Application Development Guide ⇒About the Development Environment⇒Compiling, Linking, and Editing for more information.
4-30 ProcessLogix Server Upgrade Procedures The message Password accepted should appear in the message zone. If it does not, repeat steps 7 and 8. 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. 9.
ProcessLogix Server Upgrade Procedures 4-31 6. Click File ⇒ Build Device Template ⇒ From Current Device. Do not use the From Existing .DEF files option. 7. Click OK to confirm file addition. 8. Repeat Steps 3-7 for each device stored in the FFDevices backup directory. Importing the Database Using Control Builder 1. Click Start ⇒ Programs ⇒ ProcessLogix Engineering Tools ⇒ Control Builder. 2. In the Login dialog box, make these entries: a. b. c. d. Enter >mngr< as the default User Name.
4-32 ProcessLogix Server Upgrade Procedures c. Deselect the following Point Names: All CEEs All CPMs (only if importing from R320.0) example_cascade example_motor example_pid example_scm pidloop 6. Click Import. Depending on the size of your database, this may take several minutes to several hours. 7. When completed, close the Import Window (if it did not automatically close). 8. Close Control Builder.
ProcessLogix Server Upgrade Procedures 4-33 5. Enter this command: >xcopy C:\(backup data folder name)\server\backup\*.* C:\Honeywell\server\backup\ /E< For example: >xcopy C:\R320Data\server\backup\*.* C:\Honeywell\server\backup\ /E< and press . 6. If necessary, enter >D< to specify that backup is a directory. 7. Enter this command: >cd Honeywell\Server< and press . 8. Enter this command: >copy backup\points data /y< and press . 9.
4-34 ProcessLogix Server Upgrade Procedures Restoring Server Redundancy If you have a redundant Server pair, you will need to restore redundancy between the two Servers to complete the upgrade procedure. Complete the steps to restore redundancy in Chapter 6, ProcessLogix Server Upgrade Procedures. Upgrading Hardware Component Firmware 1.
ProcessLogix Server Upgrade Procedures 4-35 Checking Control Builder Operation and Logging On Use the following general procedure to log on and check Control Builder operation on a ProcessLogix Server. Changing the default Operator's password In previous releases of ProcessLogix it was not necessary to change the default mngr operator's password to use it. As a security precaution it is now necessary to change the password before you can log in as the mngr operator.
4-36 ProcessLogix Server Upgrade Procedures Reloading Controllers 1. In the Project tab, confirm that the components of your configured control strategy are listed in the Root directory. 2. Download each CPM and SRM to its given Controller. 3. Download the database (contents of each CPM’s CEE) to the Controller. 4. In the Monitoring tab, activate the CEE and all of its components in a given Controller. 5. Close Control Builder.
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.
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.
ProcessLogix Client Installation and Upgrade Procedures Operating System Support 5-3 Windows 2000 Professional The supported installations to Windows 2000 Professional are: • Clean • Upgrade from R400.0 on Windows 2000 Professional • Upgrade from R400.0 on Windows NT 4.0 Workstation (requires clean install) • Upgrade from R320.0 on Windows NT 4.
5-4 ProcessLogix Client Installation and Upgrade Procedures Windows 2000 Professional Clean Install: Windows 2000 Professional Client Installation The following table lists the items that you MUST complete to install the Scenarios ProcessLogix Client Software on a clean PC. Table 5.
ProcessLogix Client Installation and Upgrade Procedures 5-5 Upgrade R400.0 Windows NT 4.0 Client to R500.1 Windows 2000 Professional Client (Clean Install) The following table lists the items that you must complete to upgrade an R400.0 Windows NT 4.0 Client to an R500.1 Windows 2000 Professional Client. IMPORTANT Due to significant changes in the ProcessLogix software, operating system, and performance requirements, migration from a ProcessLogix R400.0 Windows NT 4.0 Client to a ProcessLogix R500.
5-6 ProcessLogix Client Installation and Upgrade Procedures Upgrade R320.0 Windows NT 4.0 Client to R500.1 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 R500.1 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 R500.
ProcessLogix Client Installation and Upgrade Procedures Windows XP Professional Client Installation Scenarios 5-7 Clean Install: Windows XP Professional The following table lists the items that you must complete to install the ProcessLogix R500.1 Client Software on a clean PC. Table 5.E Clean Install: Windows XP Professional ✔ Step Task to Complete: Refer to: 1 Clean System Windows XP Professional Installation 2-19 2 Internet Explorer 6.
5-8 ProcessLogix Client Installation and Upgrade Procedures Upgrade R400.0 Windows NT 4.0 Client to R500.1 Windows 2000 XP Client (Clean Install) The following table lists the items that you must complete to upgrade an R400.0 Windows NT 4.0 Client to an R500.1 Windows 2000 Professional Client. IMPORTANT Due to significant changes in the ProcessLogix software, operating system, and performance requirements, migration from a ProcessLogix R400.0 Windows NT 4.0 Client to a ProcessLogix R500.
ProcessLogix Client Installation and Upgrade Procedures 5-9 Upgrade R320.0 Windows NT 4.0 Client to R500.1 Windows 2000 XP 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 R500.1 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 R500.
5-10 ProcessLogix Client Installation and Upgrade Procedures Each of the following items should be considered on an R320.0 or R400.0 Client before proceeding. Saving Important Data Table 5.I Pre-upgrade Considerations Item Pre-upgrade Post-upgrade Custom Displays Save any custom displays that were created. Typically these displays are located in C:\Honeywell\Client\abstract. Copy all custom displays to C:\Data\abstract.
ProcessLogix Client Installation and Upgrade Procedures 5-11 Networking an R320.0 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. Use the following procedure to map a drive on an R320.0 Client to a remote machine. 1. Logon to the R320.0 Client as plx_user. 2. Click Start ⇒ Run. 3. Enter this command: >cmd< and click OK to open the DOS window. 4.
5-12 ProcessLogix Client Installation and Upgrade Procedures Networking an R400.0 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. Use the following procedure to map a drive on an R400.0 Client to a remote machine. 1. Logon to the R400.0 Client as ps_user. 2. Click Start ⇒ Run. 3. Enter this command: >cmd< and click OK to open the DOS window. 4.
ProcessLogix Client Installation and Upgrade Procedures Removal of Selected R400.0 Components 5-13 Upgrading an R400.0 Windows 2000 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 Start ⇒ Settings ⇒ Control Panel. 3. Double-click Add/Remove Programs.
5-14 ProcessLogix Client Installation and Upgrade Procedures Table 5.J Removal of Selected R400.0 Components ✔ Order 9. Installing ProcessLogix R500.1 Client Software Component Quick Builder 10. VBScript Documentation 11. Control Component Library (Engineering Workstation Only) 12. Shape Library 400.0 13. PsAxCtl Document EXE (Engineering Workstation Only) 14. Display Builder 320.2 15. PSC Engineering Tools (Engineering Workstation Only) 16. Knowledge Builder 17.
ProcessLogix Client Installation and Upgrade Procedures 5-15 4. Click Start ⇒ Run. 5. Enter this path or Browse the setup.exe file on the CD. >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 Next. 8. At the Product Selection Completed window, click Continue. The ProcessLogix R500.1 Base Software CD ejects. Installing Knowledge Builder 1. Insert the ProcessLogix R500.
5-16 ProcessLogix Client Installation and Upgrade Procedures 3. Click the desired install type and click Next. KB Full Installs all KB components. Required on all ProcessLogix Servers and Clients. KB Client Installs the Client side components on a system. This install requires that you have already completed a KB Full install on a networked PC.
ProcessLogix Client Installation and Upgrade Procedures 5-17 Installing Engineering Tools This procedure is required for an Engineering Workstation only. If you are Installing an Operating Workstation, skip to Installing the ProcessLogix Client Software on page 5-17. 1. At the Ready to Install window, click Install. TIP Command windows will appear during Engineering Tools install. These windows will close automatically. 2. At the Installation Complete window, click Finish.
5-18 ProcessLogix Client Installation and Upgrade Procedures 2. At the Choose Setup Type window, click ProcessLogix Client Software setup (laptop icon). 3. At the Choose ProcessLogix Client Software window, check the appropriate checkboxes for your application. Click the box to check or uncheck it, or click Select All. • Station • HMIWeb Display Builder • Display Builder • Quick Builder • Microsoft Excel Data Exchange Uncheck this selection if Microsoft Excel is not currently installed on this PC.
ProcessLogix Client Installation and Upgrade Procedures 5-19 9. Click Next to accept ProcessLogix Client Software as the default Program Folder for the Client software. 10. Review the software installation details summarized in the Confirmation window. • If you need to make changes, click Back to access any previous entries. • If the details are okay, click Next to begin the Client software setup. This may take 10 to 15 minutes to complete. 11.
5-20 ProcessLogix Client Installation and Upgrade Procedures Finalizing ProcessLogix Client Installation Transferring R320.0 Data to the R500.1 Client 1. Logon to the R500.1 Client as ps_user. 2. Open Windows Explorer and confirm that the T: drive exists. • If the T: drive exists, skip to Transfer R320.0 Data on page 5-20. • If the T: drive does not exist, continue with Remap the T: Drive on page 5-20. Remap the T: Drive 3. Click Start ⇒ Run. 4.
ProcessLogix Client Installation and Upgrade Procedures 5-21 8. Enter this command: xcopy T:\R320Data\*.* C:\R320Data /E and press . 9. If necessary, enter >D< to specify that R320Data is a directory. 10. Delete the backup files from the remote PC. Transferring R400.0 Data to the R500.1 Client 1. Logon to the R500.1 Client as ps_user. 2. Open Windows Explorer and confirm that the T: drive exists. • If the T: drive exists, skip to Transfer R400.0 Data on page 5-22.
5-22 ProcessLogix Client Installation and Upgrade Procedures Transfer R400.0 Data 6. Click Start ⇒ Run. 7. Enter this command: >cmd< and click OK to open the DOS window. 8. Enter this command: xcopy T:\R400Data\*.* C:\R400Data /E and press . 9. If necessary, enter >D< to specify that R400Data is a directory. 10. Delete the backup files from the remote PC.
ProcessLogix Client Installation and Upgrade Procedures 5-23 Restoring ProcessLogix Data The following items should be considered before you begin operating your ProcessLogix Client. Table 5.K Post-upgrade Considerations Item Post-upgrade Custom Displays If necessary, use Windows Explorer to create the C:\Honeywell\client\abstract. Copy backed up displays from the backup directory to C:\Honeywell\client\abstract. Custom displays may require modification for use in an R500.1 system.
5-24 ProcessLogix Client Installation and Upgrade Procedures Setting Up a Station With a Non-redundant Server TIP You must define the appropriate Station items in Quick Builder on the Server in order for the Client Station to connect. Navigate in Knowledge Builder to Server and Client Configuration Guide⇒Understanding and Configuring Points⇒History Collection and Archiving⇒History Archiving for more information.
ProcessLogix Client Installation and Upgrade Procedures 5-25 6. On the Connection tab, make these entries: a. Enter the name or IP address of the non-redundant Server (PLX1) in the Server field. PLX1 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 Advanced. d. Enter >2< as the Static Station Number or enter the appropriate update rates and startup display number for Rotary.
5-26 ProcessLogix Client Installation and Upgrade Procedures • C:\honeywell\client\dspbld IMPORTANT Display Search Path Optimization You can improve Station’s performance by unchecking the Search subdirectories for shapes option in the Connection Properties dialog box, and then explicitly defining each subdirectory that contains displays. 8. Click Save. 9. Click Yes to save changes. 10. Click Connect. 11. Click Cancel at the Unable to connect prompt, if applicable. 12. Click Station ⇒ Exit. 13.
ProcessLogix Client Installation and Upgrade Procedures 5-27 Setting Up a Station With a Redundant Server Pair TIP You must define the appropriate Station items in Quick Builder on the Server in order for the Client Station to connect. Navigate in Knowledge Builder to Server and Client Configuration Guide⇒Understanding and Configuring Points⇒History Collection and Archiving⇒History Archiving for more information.
5-28 ProcessLogix Client Installation and Upgrade Procedures b. Select the appropriate Station type option, Static Station or Rotary Station. c. Click Advanced. d. Enter >3< as the Static Station Number or enter appropriate update rates and startup display number for Rotary. e. Check the Auxiliary setup file checkbox. f. Click Browse and navigate to C:\Honeywell\Client\Station\default.stn and click Open. IMPORTANT You must indicate the full path to the .stn file. 8. On the Displays tab: a.
ProcessLogix Client Installation and Upgrade Procedures 5-29 • C:\honeywell\client\dspbld IMPORTANT Display Search Path Optimization You can improve Station’s performance by unchecking the Search subdirectories for shapes option in the Connection Properties dialog box, and then explicitly defining each subdirectory that contains displays. 9. Click Save. 10. Click Yes to save the new connection. 11. Enter >defaultb.stn< in the File name field and click Save. 12. Highlight defaultb and click Connect. 13.
5-30 ProcessLogix Client Installation and Upgrade Procedures b. c. d. e. f. PLX1A is the default Server name assigned by the factory. It is used for example purposes only. Select the appropriate Station type option, Static Station or Rotary Station. Click Advanced. Enter >3< as the Static Station Number or enter appropriate update rates and startup display number for Rotary. Check the Auxiliary setup file checkbox. Click Browse and navigate to C:\Honeywell\Client\Station\defaultb.stn and click Open.
ProcessLogix Client Installation and Upgrade Procedures 5-31 • C:\honeywell\client\dspbld IMPORTANT Display Search Path Optimization You can improve Station’s performance by unchecking the Search subdirectories for shapes option in the Connection Properties dialog box, and then explicitly defining each subdirectory that contains displays. 18. Click Save. 19. Click Yes to save changes. 20. Highlight Default and click Connect. 21. Click Cancel at the Unable to connect prompt, if applicable. 22.
5-32 ProcessLogix Client Installation and Upgrade Procedures 23. Click Station ⇒ Exit. 24. Click Yes to exit Station. Creating an Emergency Repair Disk Refer to Creating an Emergency Repair Disk on page 2-39. Checking Control Builder Operation and Logging On This procedure is required for an Engineering Workstation only. Use the following general procedure to log on and check Control Builder operation on a ProcessLogix Engineering Workstation.
Chapter 6 Additional Redundant Server Procedures Adding Redundancy to R500.1 Non-Redundant Server Systems If your Servers are already named A and B (SERVERA and SERVERB), skip to Completing the ProcessLogix R500.1 Setup on a Redundant Server Pair on page 6-1. If you are adding Server redundancy to a non-redundant system, designate an existing R500.1 non-redundant Server as the SERVERA (Primary) node. Designate the other Server as SERVERB (Secondary) node.
6-2 Additional Redundant Server Procedures Changing Hosts File Entries Use the following procedure 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.
Additional Redundant Server Procedures 6-3 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.
6-4 Additional Redundant Server Procedures 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 Start ⇒ Settings ⇒ Control Panel. 2. Double-click the Network and Dial-up Connections icon. 3. Right-click the Local Area Connection icon and select Properties. 4. Select TCP/IP Protocol and click Properties. 5. Enter the TCP/IP address and appropriate Subset mask.
Additional Redundant Server Procedures 6-5 1. Click Start ⇒ Programs ⇒ ProcessLogix Server ⇒ Start-Stop ProcessLogix Server 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 Advanced ⇒ Full Mode. A checkmark will now appear in front of the Full Mode selection to show that it is active. a. With the Full Mode version of the dialog box active, click the Database Only option. b.
6-6 Additional Redundant Server Procedures Setting up Primary Server (SERVERA) ATTENTION ! Failure to convert the existing Server to the SERVERA redundant node will result in loss of configuration data. This will require reconfiguring the system. Use the following procedures to set up the Primary SERVERA. Making Redundant Hardware File Entries 1. On SERVERB, click Start ⇒ Programs ⇒ ProcessLogix Server ⇒ Start-Stop ProcessLogix Server to call up the ProcessLogix Server dialog box.
Additional Redundant Server Procedures 6-7 c. Close the ProcessLogix Server dialog box. 3. Are you using a dual network (LAN) data link with your redundant Servers? • If the answer is Yes, go to Step 4. • If the answer is No, go to Step 10. 4. Use Windows Explorer to locate the redun.hdw file in this directory path: C:\Honeywell\server\user 5. Double-click the redun.hdw file to open it in Notepad. 6. Modify the file to include the following entries for dual data links.
6-8 Additional Redundant Server Procedures 12. At DOS prompt, enter: >cd \Honeywell\server\user< and press . 13. Enter this command: >hdwbld redun.hdw< and press . The hdwbld utility reads the text file [redun.hdw] and adds the hardware definitions to the Server database. If you are using a dual LAN, be certain that you change the default redun.hdw file as noted in Step 4 to Step 9. 14. Check that no hardware build errors are listed.
Additional Redundant Server Procedures 6-9 a. With the Full Mode version of the dialog box active, click the System Running option. b. Click Yes to confirm the action and wait for the Server to change its state. c. Close the ProcessLogix Server dialog box. Setting Up Secondary Server (SERVERB) Use the following procedures to set up the Secondary SERVERB. Making Redundant Hardware File Entries Refer to Making Redundant Hardware File Entries on page 6-6 and repeat the procedures on SERVERB.
6-10 Additional Redundant Server Procedures 3. At the DOS prompt, key in this command: >dual_status< and press . 4. The unsynchronized SERVERA data should be similar to this: 5. Verify that the data link is available. 6. On SERVERB, click Start ⇒ Run. 7. Enter this command in the Open entry field: >cmd< and click OK to open the DOS window. 8. At the DOS prompt, key in this command: >dual_status< and press . 9. The unsynchronized SERVERB data should be similar to this: 10.
Additional Redundant Server Procedures Configuring Stations in Quick Builder (on SERVERA) 6-11 1. Click Start ⇒ Programs ⇒ ProcessLogix Server ⇒ Quick Builder. 2. Click the New Project option and click OK. 3. In the Save in drop down list, select the C:\Honeywell\client\qckbld 4. Enter >Stations.qdb< in the File name field and click Save. 5. Wait for the Enable Components dialog box to appear. a.
6-12 Additional Redundant Server Procedures 15. Click OK to initiate the download. 16. Click OK to acknowledge the successful download prompt and close the dialog box. 17. Click File ⇒ Exit to close Quick Builder. Setting Up Station on SERVERA 1. On SERVERA, click Start ⇒ Programs ⇒ ProcessLogix Server ⇒ Station. 2. Click Cancel at the Unable to connect prompt, if applicable. 3. Click Station ⇒ Connect to call up the Station Connect dialog box. 4. Click New Connection. 5.
Additional Redundant Server Procedures 6-13 6. On the Displays tab: a. Check the Search subdirectories for shapes checkbox. b. Click Add and then Browse and add the following directories.
6-14 Additional Redundant Server Procedures • C:\honeywell\client\dspbld IMPORTANT Display Search Path Optimization You can improve Station’s performance by unchecking the Search subdirectories for shapes option in the Connection Properties dialog box, and then explicitly defining each subdirectory that contains displays. 7. Click Save. 8. Click Yes to save the new connection. 9. Enter >defaultb.stn< in the File name field and click Save. 10. Select defaultb and click Connect. 11.
Additional Redundant Server Procedures b. c. d. e. 6-15 Select the Station type as Static Station. Enter >1< as the Static Station Number and click Advanced. Check the Auxiliary setup file checkbox. Click Browse and navigate to: C:\Honeywell\Client\Station\defaultb.stn and click Open. IMPORTANT You must indicate the full path to the .stn file. 15. Click Save. 16. Click Yes to save changes. 17. Highlight Default and click Connect. 18. Click Cancel at the Unable to connect prompt, if applicable. 19.
6-16 Additional Redundant Server Procedures c. Enter >2< as the Static Station Number and click Advanced. d. Check the Auxiliary setup file checkbox. e. Click Browse and navigate to: C:\Honeywell\Client\Station\default.stn and click Open. IMPORTANT You must indicate the full path to the .stn file. 6. On the Displays tab: a. Check the Search subdirectories for shapes checkbox. b. Click Add and then Browse and add the following directories.
Additional Redundant Server Procedures 6-17 • C:\honeywell\client\dspbld IMPORTANT Display Search Path Optimization You can improve Station’s performance by unchecking the Search subdirectories for shapes option in the Connection Properties dialog box, and then explicitly defining each subdirectory that contains displays. 7. Click Save. 8. Click Yes to save the new connection. 9. Enter >defaultb.stn< in the File name field and click Save. 10. Select defaultb and click Connect. 11.
6-18 Additional Redundant Server Procedures b. c. d. e. Select the Station type as Static Station. Enter >2< as the Static Station Number and click Advanced. Check the Auxiliary setup file checkbox. Click Browse and navigate to: C:\Honeywell\Client\Station\defaultb.stn and click Open. IMPORTANT You must indicate the full path to the .stn file. 15. Click Save. 16. Click Yes to save changes. 17. Highlight Default and click Connect. 18. Click Cancel at the Unable to connect prompt, if applicable. 19.
Additional Redundant Server Procedures 6-19 The message Password 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.
6-20 Additional Redundant Server Procedures Restarting Redundant Servers ATTENTION ! The following procedure assumes that you have completed the previous procedures in this section for both the SERVERA (Primary) and SERVERB (Secondary) nodes. Use the following procedure to restart SERVERA and then SERVERB. 1. Restart SERVERA. 2. On SERVERA, right-click in the taskbar to open the popup menu and click Task Manager to call up the Windows Task Manager dialog box. 3. Click the Performance tab. 4.
Additional Redundant Server Procedures 6-21 Depending on your configuration, this may take some time to complete. 7. Wait for the synchronization to complete (“Synchronization Complete” prompt appears) and verify that the display shows simulated Green LED indications for the following states: Primary Server • Running Backup Server • Synchronized • Running Link Status • Link 0 (LNK00) - OK Active link • Link 1 (LNK01) - OK (Only applies if you are using a dual LAN) 8. Click Station ⇒ Exit. 9.
6-22 Additional Redundant Server Procedures 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 Start ⇒ Run. 7. Enter this command: >cmd< and click OK to open the DOS window. 8. At the DOS prompt, key in this command: >dual_status< and press . 9. The synchronized SERVERB data should be similar to this: 10. Verify that the link is active and the databases are synchronized.
Additional Redundant Server Procedures 6-23 Synchronizing Other Files The Primary SERVERA node automatically transfers ProcessLogix database information to the Secondary SERVERB node. 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.
6-24 Additional Redundant Server Procedures 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-24. Creating an Emergency Repair Disk After all installations and drivers are installed, you should now create your Emergency Repair Disk.
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 will appear after each restart. Install Hardware Device Drivers 1. Restart the PC. 2. Logon as ps_user. 3.
7-2 Firmware Maintenance Procedures 14. Click Next to install the driver. 15. If a Digital Signature Not Found window appears, click Yes. 16. If necessary, click Yes to overwrite the VirtualBackplane.sys file. 17. If necessary, click Yes to overwrite the ABPCICSW.sys file. 18. Click Finish. Verify the 1784-PCIC Driver Version 1. Right-click the My Computer icon and select Manage. 2. Select Device Manager. 3. If the A-B Virtual Backplane icon exists, expand A-B Virtual Backplane. 4.
Firmware Maintenance Procedures 1784-PCIC Firmware Installation 7-3 If your 1784-PCIC firmware has not been updated for ProcessLogix R500.1, this procedure must be followed to use the 1784-PCIC in R500.1. IMPORTANT You must have the 1784-PCIC configured in RSLinx. Refer to Configuring RSLinx Drivers for ControlNet Supervisory Network on page 3-15 to configure the 1784-PCIC drivers in RSLinx.
7-4 Firmware Maintenance Procedures 13. Wait for the load to complete. The Status field in the lower portion of the Network Tools window tracks the load progress. 14. Click OK to acknowledge the load completion with no errors. 15. Close NTools. Upgrading Hardware Component Firmware 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.
Firmware Maintenance Procedures 7-5 Firmware Revision Level Reference The following table lists the firmware revision levels for listed components that are current for R500.1 along with the directory locations for firmware upgrade files. ATTENTION ! This release of ProcessLogix supports only the firmware versions listed in Table 7.A. When installing new systems or repairing existing systems, you must ensure that all modules meet the firmware version requirements listed in Table 7.A.
7-6 Firmware Maintenance Procedures Table 7.A Hardware component firmware revision level reference for R500.1 Component Name Model Number Revision Level for R500.1 Directory File FLEX IO ControlNet Adapter 1794-ACN15/C (single media) 1794-ACNR15/C (redundant media) 3.5 \1794-ACN(R)15\3_5 99423302.nvs ControlNet PCI Interface card 1784-PCIC 3.6.38 \1784-PCIC\3.6.38 2MnBtPcic3x.nvs ControlNet to Fieldbus Linking Device 1757-CN2FF 1.4 \1788-CN2FF\1_4 99454401.
Firmware Maintenance Procedures 7-7 Table 7.A Hardware component firmware revision level reference for R500.1 Component Name Model Number Revision Level for R500.1 Directory File Digital I/O Modules 1756-IA16/A 2.4 IOM\Digital\1756-IA16\2_4 99213204.nvs 1756-IB16/A 2.4 IOM\Digital\1756-IB16\2_4 99212904.nvs 1756-IB32/A 2.6 IOM\Digital\1756-IB32\2_6 99207106.nvs 1756-IB16I/A (ASIC ver. 2.1) 1.7 IOM\Digital\1756-IB16I\1_7 99205106.nvs (ASIC ver. 2.2) 2.
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 on page 7-5.
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.
7-10 Firmware Maintenance Procedures Special Considerations Table 7.B Special Considerations when Loading 1757-PLX52, TC-MUX021, or 1757-FIM Boot and Personality Images Special Considerations Description Upgrading the 1757-PLX52 from R300.0 to R500.1 When upgrading the firmware from R300.0 to the R500.1 firmware, the CPM will not reset after the flash is completed. The module will display wait on the module LED for an extended period of time.
Firmware Maintenance Procedures 7-11 2. Click the 1757-PLX52, TC-MUX021, or 1757-FIM module in the graphic of the chassis configuration in the Detail pane. If required, select another CNB icon to find the chassis that contains a 1757-PLX52, TC-MUX021, or 1757-FIM module. 3. Click Firmware to initiate the firmware update. 4. Click Yes to acknowledge the Warning prompt. 5.
7-12 Firmware Maintenance Procedures 11. Wait for the load to complete and the 1757-PLX52, TC-MUX021, or 1757-FIM module to reboot to its ALIVE status as shown in the module LED display. The Status field in the lower portion of the Network Tools window tracks the load progress. 12. Click OK to acknowledge the load completion with no errors. 13. Confirm that the LED display on the 1757-PLX52 or TC-MUX021 module shows ALIVE. Loading Personality Image 1.
Firmware Maintenance Procedures 7-13 6. To load the personality image to a 1757-FIM, locate the Fimrex.nvs personality (rex) file. See Table 7.A on page 7-5. This example illustrates loading the personality image to a 1757-PLX52 for CEE-50ms. 7. When the correct file appears in the list box, select it so that it appears in the File Name entry field. 8. Click Open to start the firmware load and click Yes to confirm the action. 9.
7-14 Firmware Maintenance Procedures Updating Firmware in CNB, ENET, IOM, SRM, PIM or ControlNet Adapter ATTENTION ! Redundant Chassis Firmware Upgrade Precautions When updating modules in an RCP, you MUST turn OFF power to the Secondary Chassis in the RCP, so you can update the firmware in the modules in the powered controller chassis while it is in a Primary with no partner state. Failure to remove power from the Secondary Chassis may result in an unrecoverable loss of the RM.
Firmware Maintenance Procedures 7-15 6. Carefully follow the on-screen prompts to complete the update. ATTENTION ! Be certain that you select the correct .nvs update file before you acknowledge any Warning prompt and initiate a file download to a given module. See Table 7.A on page 7-5. Do not update more than one module of a given type at a time. If the on-screen prompt includes a selection for “Update all other identical types in this controller (only) now”, be certain this selection is not checked.
7-16 Firmware Maintenance Procedures 3. Enter this command: >ntools -c -pg< TIP If the RSLinx and PCIC driver services for system communications in ControlNet mode are not running, this command will start the services. 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.
Firmware Maintenance Procedures 7-17 Be certain to adjust the Number of Repeaters, Cable Length, and Fiber Optics settings to match your actual system configuration when they differ from the suggested default values listed below. TIP The values listed below differ for applications that include a Foundation Fieldbus Linking Device.
7-18 Firmware Maintenance Procedures Updating Firmware in ABRIO Follow this procedure for updating the firmware in the 1757-ABRIO module. 1. Logon the Server as ps_user. 2. Insert the ProcessLogix R500.1 Supplemental CD. 3. Click Start ⇒ Run. 4. Browse to: >CDROM Drive Letter<:\ABRIO Control Flash\setup.exe 5. Click OK. 6. At the Welcome to ControlFLASH Setup window, click Next. 7. Click Yes to accept the License Agreement. 8. Click Next to accept the default location. 9.
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 redundant servers, you must complete this procedure on the SERVERB node first. Then complete the entire procedure again for the SERVERA node. This section describes how to stop ProcessLogix services in the Windows 2000 system.
8-2 Supplementary Procedures g. h. i. j. k. ProcessLogix System Repository ProcessLogix ER Server RSLinx XLNet Daemon MSSQLServer (also stops SQLServerAgent) 2. Close the Computer Management window. 3. Right click the SQL Server Service Manager icon in the task bar and select Exit. This will close the application. Installing Knowledge Builder on a Non-ProcessLogix System Knowledge Builder is the software application used to display ProcessLogix documentation.
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 Security Update Installation 2-34 3. Installing Knowledge Builder 8-4 Removing Knowledge Builder Before installing ProcessLogix R500.
8-4 Supplementary Procedures Installing Knowledge Builder 1. Insert the ProcessLogix R500.1 Knowledge Builder CD into the CD-ROM drive. 2. Enter this path or Browse to: >D:(or your CD-ROM drive letter)\Knowledge_Builder\Setup.exe< 3. Click OK to launch the Knowledge Builder setup. 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.
Supplementary Procedures 8-5 11. At the Server selection window: • If installing Full, click Next to accept the default directory for Knowledge Builder. • If installing Client, click Browse and select the appropriate Server location. For example, the location of the Full version of KB might be E:\Docs, where E:\ is a mapped drive to C:\ProgramFiles\Honeywell\PST_Server\Knowledge Builder on PLX1A. 12. At the Start Copy window, click Next. 13.
8-6 Supplementary Procedures 1. Right-click the My Computer icon and select Manage. 2. Expand Services and Applications. 3. Select Services. 4. Scroll down to the service MSSQLSERVER and verify that it has started. If the MSSQLSERVER service did not start, start it. 5. Scroll down to the service SQLSERVERAGENT and verify that it has started. If the SQLSERVERAGENT service did not start, start it. 6. Close the Computer Management window.
Supplementary Procedures Manual System Backup/Restore Procedures 8-7 Backing Up a ProcessLogix R500.1 Server to Tape For information on backing up a ProcessLogix R500.1 Server to tape, contact Rockwell Automation Tech Support, refer to Rockwell Automation Technical Support on page -5. Restoring a ProcessLogix Server System From a Backup Tape For information on restoring the ProcessLogix R500.
8-8 Supplementary Procedures • 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.
Supplementary Procedures 8-9 1. Click Start ⇒ Run. a. For ControlNet Supervisory Networks, enter this command: >ntools -c -u -pg< TIP If RSLinx and the PCIC driver services for system communications in ControlNet mode are not running, this command will start the services. b. For Ethernet Supervisory Networks, enter this command: >ntools -e -u -pg< 2. Click OK to launch the Network Tools application. 3. Click OK to acknowledge the warning about monitoring through Control Builder. 4.
8-10 Supplementary Procedures 5. Do the following in the Options tab. a. Enter >2< in the field for Delay between scans (seconds). b. Select the Periodic (automatic) option. This means automatic scans are made periodically with the specified delay between scans. c. Check Enable Module Version/Revision Checking. This turns ON the automatic firmware version/revision detection function.
Supplementary Procedures 8-11 9. In the Local Chassis tab, adjust the number in the scroll box to match the number of slots in your local chassis. 10. If your system includes a remote chassis, go to Step 11. Otherwise, go to Step 15. 11. Click the Remote Chassis 1 tab. 12. Check the Check here if... installed checkbox. 13. 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.
8-12 Supplementary Procedures 14. Repeat Steps 12 and 13 for other remote chassis by selecting the next numbered tab, as required. 15. When settings are complete, click OK. Look for the graphic of the chassis for given CNB to appear in the Detail pane. The graphic will also show remote chassis, if applicable. 16. Repeat Step 8 to Step 15 for next CNB or Ethernet driver icon, as required. 17. Close NTools when finished.
Supplementary Procedures Installing and Running NetShield with ProcessLogix IMPORTANT 8-13 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.
8-14 Supplementary Procedures Installing NetShield and Configuring Directories for Scan Exclusion Use the following procedure 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 Account. 3.
Supplementary Procedures Changing the Computer Name on a ProcessLogix Server 8-15 All ProcessLogix Servers and Clients require unique computer names and IP addresses. If your ProcessLogix system includes multiple Servers and/or Clients, you will 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.
8-16 Supplementary Procedures 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 sub-directory at the root of C: ie C:\ExportDB. If the system is brand new (ie, no configuration applied yet.), then this procedure can be skipped.
Supplementary Procedures 8-17 Stopping ProcessLogix Applications and Services 1. Exit all running ProcessLogix applications, such as Control Builder, Station, and Network Tools (NTOOLS). 2. Right click the My Computer icon and select Manage. 3. Expand Services and Applications. 4. Select Services. TIP To stop a service: If the service is present, right-click on it and select Stop. If prompted, click Yes to also stop other services.
8-18 Supplementary Procedures Removing Selected ProcessLogix R500.1 Components 1. Logon to the system as ps_user. 2. Click Start ⇒ Settings ⇒ Control Panel. 3. Double-click Add/Remove Programs. IMPORTANT If at any time during software uninstall, a remove shared file prompt appears, click Yes to all or Remove. If necessary, click OK or Yes to confirm. 4. To remove a program: a. Click on the appropriate program in the list of installed programs. b. Click Add/Remove, Change/Remove or Remove. c.
Supplementary Procedures 8-19 Table 8.C Removal of Selected ProcessLogix R500.1 Components ✔ Order Component 10. Knowledge Builder (Click the Remove option.) 11. Microsoft SQL Server 2000 12. PLX System Installer If you receive errors, these are expected and will not effect the outcome of the installation, click OK to continue.) 13. Close the Add/Remove Programs window. Remove ProcessLogix R500.1 Server Components 1. Click Start ⇒ Programs ⇒ ProcessLogix Server ⇒ Setup. 2.
8-20 Supplementary Procedures 3. If any of the following programs are still present in the Add/Remove programs list, select and remove them. • • • • • • • • • • • • • • • ProcessLogix Update Process Detail Displays Control Component Library PSAxCtl Document EXE Psc Engineering Tools Knowledge Builder Microsoft SQL Server RSLinx ProcessLogix Server HMIWeb HMIWeb Station HMIWeb Station and Display Builder Display Builder Quick Builder VBScript Documentation 4. Select ProcessLogix - Remove this last. 5.
Supplementary Procedures 8-21 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. The following naming conventions are required for given ProcessLogix system architectures. For non-redundant Server, be sure the name does not end in the letter “A” or “B”. The default name is PLX1.
8-22 Supplementary Procedures Restoring the Data ATTENTION ! If you are using this procedure for renaming redundant servers, finish setting up redundancy. Refer to Completing the ProcessLogix R500.1 Setup on a Redundant Server Pair on page 6-1 before performing this step to restore the Engineering Repository Database. (ERDB) Follow the steps below to import the data back into the Engineering Repository Database. 1. Logon to the system as ps_user. 2.
Supplementary Procedures Changing the Computer Name on a ProcessLogix Client 8-23 All ProcessLogix Servers and Clients require unique computer names and IP addresses. If your ProcessLogix system includes multiple Servers and/or Clients, you will need to change computer names and addresses to assure their unique identities. IMPORTANT ATTENTION ! The computer name cannot contain more than 14 alphanumeric characters and must contain no spaces.
8-24 Supplementary Procedures Changing the Computer Name on a Windows XP Client 1. Logon as ps_user. 2. Click Start ⇒ Settings ⇒ Control Panel. 3. Double-click the System icon. 4. On the Computer Name tab, click Change. 5. Enter the desired computer name in the Computer name entry field. 6. Click OK to initiate the change. 7. At the You must restart prompt, click OK. 8. Click OK to Close the System Properties window. 9. Click Yes to restart the computer.
Supplementary Procedures Adding 1757-PLX52 Controller Redundancy to R500.1 Non-Redundant 1757-PLX52 Controller Configurations 8-25 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. Deleting a Non-Redundant 1757-PLX52 and Unassigning its Contents Use the following procedure to save your existing database and delete it from the existing non-redundant 1757-PLX52 Controller. 1. Start Control Builder. 2.
8-26 Supplementary Procedures 11. Click Operate ⇒ Inactivate ⇒ This CEE’s SCMs to inactivate all assigned SCMs, if applicable. 12. Click Yes in the dialog box to confirm the action. 13. Click Operate ⇒ Inactivate ⇒ This CEE and its IOMs and CMs to inactivate the CEE and all assigned IOMs and CMs. 14. Click Yes in the dialog box to confirm the action. Color of all icons changes to Blue. 15. Select the contents (CMs, SCMs, IOMs) of the CEE folder and click Edit ⇒ Delete. 16.
Supplementary Procedures 8-27 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).
8-28 Supplementary Procedures 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. Once the redundant CPM is created in the Project tab, re-assign the modules unassigned from the previous non-redundant CPM to the CEE associated with the new redundant CPM.
Chapter 9 New Functions and Features This release introduces enhancements to Rockwell Automation's ProcessLogix process control system.The enhancements include: Table 9.
9-2 New Functions and Features Engineering Tools Enhancements Server Enhancements Table 9.B Enhancements to Engineering Tools Enhancement Description History Configuration Historical data collection, Group display assignment, and Trend display assignment are now standard part of CB point configuration. Cross Reference and Wiring Improvement This feature improves the wiring algorithm and results in better wiring paths during control configuration.
New Functions and Features 9-3 Updated Station & HMIWeb Display Builder The following updates have been made to Station & HMIWeb Display Builder: • Improved menu/toolbar configuration • Support for IKB/OEP Operator keyboards • Define which monitor to start on, on multi-monitor systems. • Faceplates - does not depend on hard-coded references to data, instead, links to point when called up. “Pin” function allows pop-up to stay open even after underlying display is changed.
9-4 New Functions and Features Plant Data Model Enhancements This release of ProcessLogix has been enhanced to support 40 character Point ID's (standard points only, i.e. analog, status, accumulator). Point descriptor and area codes have been lengthened to support 132 and 40 characters respectively. Users using the ProcessLogix ODBC Driver for reports or applications should investigate the effect of this change on their reports or applications.
New Functions and Features 9-5 Updated Network API Support for Visual Basic The Network API for Visual Basic has changed from previous releases. Previously, to add Network API support to a Visual Basic project, a developer would need to add references to 3 .bas files. The mechanism has been modified, and Visual Basic applications that need to use the latest Network API will no longer need to include references to the .bas files. Instead they will need to include a reference to the Network API .
9-6 New Functions and Features 1756-DNB DeviceNet Interface Module The 1756-DNB: • provides a communication bridge between ControlNet and DeviceNet • utilizes the Rockwell 1756 form factor, which is native to ProcessLogix • can be located in either the ProcessLogix Controller Rack or I/O Rack • supports the three DeviceNet baud rates: 500 KBps, 250 KBps and 125KBps.
Chapter 10 Major ProcessLogix Software Components This chapter contains the detailed information about the major ProcessLogix R500.1 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.
10-2 Major ProcessLogix Software Components Table 10.A Major ProcessLogix Engineering Tools Software Revisions Component Version Network Tools PS500.1-01.1 Example Verification Mechanism 1. Execute NTools using Start ⇒ Programs ⇒ ProcessLogix Engineering Tools ⇒ NTools. 2. Click Help ⇒ About Network Tools. Fieldbus Library Manager PS500.1-01.1 1. Execute Fieldbus Library Manager using Start ⇒ Programs ⇒ ProcessLogix Engineering Tools ⇒ Fieldbus Library Manager. 2.
Major ProcessLogix Software Components 10-3 Major ProcessLogix Server Software Revisions Table 10.B Major ProcessLogix Server Software Revisions Component Version Example Verification Mechanism ProcessLogix Server R500.1 Build 500.1-15.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.379 1. Execute Station using Start ⇒ Programs ⇒ ProcessLogix Server ⇒ Station.
10-4 Major ProcessLogix Software Components Embedded Software Components Table 10.C Embedded Software Components Component Version Example Verification Mechanism Windows 2000 Service Pack 2 Service Pack 2 1. At command prompt enter WINVER. 2. The response should include “Service Pack 2” Windows 2000 Security Rollup Multiple 1. Click Start ⇒ Settings ⇒ Control Panel ⇒ Add/Remove Programs. 2. Listed will be Windows 2000 Security Rollup Package [See Q311401 for more information] Internet Explorer 6.
Major ProcessLogix Software Components 10-5 Table 10.C Embedded Software Components SQL Server 2000 2000.80.534.0 1. Run Windows Explorer. 2. Right-click on the file C:\Program Files\Microsoft SQL Server\MSSQL\Binn\sqlservr.exe. 3. Click Properties. 4. Click Version tab. MS-Access 3.0.0.2504 1. Run Windows Explorer. 2. Right-click on the file C:\Honeywell\TPS50\System\bin\mswng300.dll 3. Click Properties. 4. Click Version Tab. Adobe Acrobat Reader 4.05b.0127 1.
10-6 Major ProcessLogix Software Components External, Third Party Qualified Software Components IMPORTANT WARNING ! This section identifies third party Windows-based software applications that are supported on a ProcessLogix Station Client. Special care must be exercised when using any of these third party packages. 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.
Major ProcessLogix Software Components 10-7 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.
10-8 Major ProcessLogix Software Components Table 10.D External, Third Party Qualified Software Components Component Version MS Visual C++ 6.0 Service Pack 5 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. Limitations/Compatibilities: • Use on Client only MS Visual Basic 6.0 1. Run Windows Explorer. 2. Right click \winnt\system32\msvbvm50.dll and \winnt\system32\msvbvm60.
Chapter 11 Performance and Capacity Specifications ATTENTION ! This chapter contains the most current platform requirements from the performance and capacity specifications for R500.1. 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.
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.
Performance and Capacity Specifications 11-3 includes active monitoring from multiple Stations with or without multiple locations and random report generation. 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.
11-4 Performance and Capacity Specifications Client Platform Requirements Table 11.B Client Platform Requirements based on System Configurations System Configuration Minimum Typical Performance Processor 1 GHz Pentium III or larger 1.4 GHz Pentium III or larger 2.
Performance and Capacity Specifications 11-5 Table 11.C Application RAM Usage Application RAM Usage Windows 2000 Applications Explorer 8 MB Computer Management(1) 8 MB Event Viewer 5 MB Task Manager(1) 2.
11-6 Performance and Capacity Specifications (5) While using the NI FBUS Configurator, you can only monitor 1 Linking Device at one time. This application should only be run on the Backup Server (if redundant) as this will put an additional CPU load on the system approximately 35% higher than the normal running state. If run on a Non-Redundant Server, it is required that you have a more performance CPU configuration. This applies only to 1757-CN2FF access to Foundation Fieldbus devices.
Performance and Capacity Specifications 11-7 Table 11.D Operational Display Update Rates Typical Display Call Up Time with 100 Parameters on a Single Station/Server (Call up time is dependent on display complexity; this excludes the first initial call up.) < 2 sec Maximum Number of Stations Connected to one Server 20 Maximum Number of Concurrent Users Connected to one Server. Unlimited for Windows 2000 See Table 11.G Server communication NetBIOS session capacity Sever based system on page 11-9.
11-8 Performance and Capacity Specifications • Database Modification in Progress, Try Again Later • Point Build Error In extreme cases these errors may cause Control Builder to stop functioning. If this happens, you should restart the Control Builder and reload the server points to ensure that the changes take effect. Data should not be affected. Server Redundancy Table 11.
Performance and Capacity Specifications 11-9 Client/Server Communication Capacity Table 11.G Server communication NetBIOS session capacity Session type or activity Comment/example Time Sync Active once every configured Time Sync period. Shared Drives/ Displays Active continuously, if Station Client get displays from central Server. Shared printer Active continuously if linked to a network printer for Reports, etc.
11-10 Performance and Capacity Specifications (3) OPC Alarm & Event Support: The ProcessLogix Server includes the option to support reception of OPC Alarms & Events, in addition to native ProcessLogix notifications. When an OPC Alarm & Event Server has been configured to generate notifications to captured by the ProcessLogix Server Alarm System, the notification limits noted above are applicable to the combined set of events received from all event sources configured. Server Data Access Table 11.
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.
11-12 Performance and Capacity Specifications operator stations and high-level application nodes), controller-level stations, I/O level chassis, and directly networked devices. Figure 11.1 System Communications Architecture Operator and Applications Nodes Server Node External DCS Systems Controller Nodes ABRIO IO Nodes Device Nodes The server is the head of a “pyramid” of controllers. Each controller, in turn, is a head of a pyramid of IO chassis.
Performance and Capacity Specifications 11-13 Since ProcessLogix permits almost totally generalized intercommunications paths, the two devices can be under or on: 1. the same H1 link, 2. different links of the same 1757-FIM, 3. different 1757-FIMs in the same IO chassis, 4. different IO chassis of the same controller, 5.
11-14 Performance and Capacity Specifications Processing power and memory are finite. CNB modules, for example, are limited to 64 connections. The 1784-PCIC card is limited to 128 connections. Node Processing Load Limits Processing power of nodes of the network is finite. Usually the “highest” node in the topology processes the most.
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.
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.
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.
11-18 Performance and Capacity Specifications 1757-PLX52 Resources Table 11.
Performance and Capacity Specifications 11-19 Table 11.
11-20 Performance and Capacity Specifications Table 11.
Performance and Capacity Specifications I/O Performance and Capacity Specifications 11-21 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.
11-22 Performance and Capacity Specifications Table 11.
Performance and Capacity Specifications 11-23 Table 11.T Profibus Capacity/Topology Specifications PFB Module and PROFIBUS Block Specifications Note: The PROFIBUS interface module hardware component is the SST-PFB-CLX, and is referred to herein as the PFB Module. This device acts as the “master” on the PROFIBUS-DP network. Each PFB module is represented as a block in the CEE, which is referred to as the PROFIBUS Interface Module Block (PBIM).
11-24 Performance and Capacity Specifications 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.
Performance and Capacity Specifications 11-25 FIM Display-related Performance Limits The following table gives performance guidelines for the display of tabs on the FF Block Detail Display Form, which obtains its data through the FIM and H1 links: Table 11.
11-26 Performance and Capacity Specifications I/O Module Publication Periods Table 11.
Performance and Capacity Specifications 11-27 Migration Consideration In R500.1, 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 R500.1 than that in pre-R500.1 release.
11-28 Performance and Capacity Specifications Publication 1757-IN500A-EN-P - September 2002
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 R500.1 Installation and Upgrade Guide Cat. No. 1757-SWKIT5000 Pub. No. 1757-IN500A-EN-P Pub. Date September 2002 Part No. 957678-65 Please complete the sections below.
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.
Publication 1757-IN500A-EN-P - September 2002 2 PN 957678-65 Copyright © 2002 Rockwell Automation, Inc. All rights reserved. Printed in the U.S.A.
ProcessLogix R500.
