ProcessLogix R400.
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.
Rockwell Automation Support Before you contact Rockwell Automation for technical assistance, we suggest you please review the troubleshooting information contained in this publication first. If the problem persists, call your local Rockwell Automation representative or contact Rockwell Automation in one of the following ways: Phone Internet United States/Canada 1.440.646.5800 Outside United States/Canada You can access the phone number for your country via the Internet: 1. Go to http://www.ab.com 2.
Table of Contents Important User Information . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Rockwell Automation Support . . . . . . . . . . . . . . . . . . . . . . . . 3 Your Questions or Comments on this Manual . . . . . . . . . . 3 Preface Our Assumptions About Readers . . . . . . . . . . . . . . . . . . . Starting Conditions and Assumptions . . . . . . . . . . . . . Minimum Hardware Requirements . . . . . . . . . . . . . . . . . . Rockwell Automation Technical Support . . . . . . . . . . . . .
Table of Contents ii Chapter 2 Operating System Installation Procedures Publication 1757-IN040B-EN-P - March 2002 Clean System Windows 2000 Server Installation . . . . . . . . . Installing Windows 2000 Server on a New System . . . . . Starting the Windows 2000 Server Installation . . . . . . . . Starting the Installation from the Boot Floppies . . . . . . . Starting the Installation from the CD-ROM. . . . . . . . . . . Completing the Windows 2000 Server Installation . . . . .
Table of Contents iii Chapter 3 ProcessLogix Server Installation Procedures Installing ProcessLogix Software on a Clean PC . . . . . . . . Installing Server Software . . . . . . . . . . . . . . . . . . . . . . Installing SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . Installing Knowledge Builder . . . . . . . . . . . . . . . . . . . Installing RSLinx . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Engineering Tools . . . . . . . . . . . . . . . . . . . .
Table of Contents iv Chapter 5 ProcessLogix Client Installation and Upgrade Procedures Publication 1757-IN040B-EN-P - March 2002 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operating System Support . . . . . . . . . . . . . . . . . . . . . . . Windows 2000 Professional . . . . . . . . . . . . . . . . . . . Windows NT 4.0 Workstation . . . . . . . . . . . . . . . . . . Pre-work for systems with ProcessLogix R320.0 . . . . . . . Saving Important Data . . . . . . . . . .
Table of Contents v Chapter 6 Additional Redundant Server Procedures Adding Redundancy to R400.0 Non-Redundant Server Systems . . . . . . . . . . . . . . . . . 6-1 Changing the Computer Name on a ProcessLogix Server 6-1 Completing the ProcessLogix R400.0 Setup on a Redundant Server Pair . . . . . . . . . . . . . . . 6-1 Changing Hosts File Entries . . . . . . . . . . . . . . . . . . . . . 6-1 Changing TCP/IP address on a Secondary Server (SERVERB) Node . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents vi Chapter 8 Supplementary Procedures Publication 1757-IN040B-EN-P - March 2002 Stopping ProcessLogix Applications and Services . . . . . . . Stopping the ProcessLogix Server . . . . . . . . . . . . . . . . Shut Down SQL Server Services . . . . . . . . . . . . . . . . . Stop RSLinx Service . . . . . . . . . . . . . . . . . . . . . . . . . . Stopping NI-FBUS and Excel . . . . . . . . . . . . . . . . . . . Launching ProcessLogix Knowledge Builder. . . . . . . . . . . SQL Server . . . . .
Table of Contents Installing and connecting Redundant Chassis Pair (RCP) Hardware . . . . . . . . Updating Firmware Revision Levels . . . . . . Creating a Redundant 1757-PLX52 . . . . . . . Installing Knowledge Builder on a Non-ProcessLogix System . . . . . . . . . . . . Removing Knowledge Builder . . . . . . . . . . Installing Service Pack 2 for Windows 2000. Installing Internet Explorer 5.5 SP1 . . . . . . . Installing MDAC2.5 SP1 . . . . . . . . . . . . . . . Installing Knowledge Builder . . . . . . . .
Table of Contents viii Chapter 10 New Functions and Features Publication 1757-IN040B-EN-P - March 2002 Enhanced Foundation Fieldbus Support . . . . . . . . . . . . . Profibus DP Support . . . . . . . . . . . . . . . . . . . . . . . . . . . SST-PFBCLX PROFIBUS Interface Module . . . . . . . . . SST-PFBCLX Module Characteristics . . . . . . . . . . . . . Functional Exclusions. . . . . . . . . . . . . . . . . . . . . . . . Topology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents ix Chapter 11 Performance and Capacity Specifications PC Platform Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 11-1 Summary of R400.0 Enhancements to ProcessLogix System Capacity & Performance. . . . . . . . . . . . . . . . . . . . . . . . 11-2 Server Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2 Platform System Configuration Definitions . . . . . . . . . . 11-3 Station/Engineering Client Requirements. . . . . . . . . . . .
Table of Contents x Publication 1757-IN040B-EN-P - March 2002
Preface Our Assumptions About Readers Before configuring a ProcessLogix R400.0 systrem you MUST: • Be familar with navigating and running applications in a Microsoft Windows NT/2000 environment. • Have some experience in loading software applications on a personnal computer (PC). • Be familar with ProcessLogix hardware components. • Be familar with ControlNet configuration. • Be trained on ProcessLogix R400.0, including Control Builder and Server components.
Preface 2 • Windows 2000 Server CD (Microsoft CD, including boot diskettes). • RSLinx OEM Master (Activation) Disk. • The Factory CD containing default system drivers for backup purposes only. Please contact Rockwell Automation Technical Support before using this CD. This CD is only supplied with new ProcessLogix R400.0 servers. You must be certain that your PC meets the minimum hardware requirements for a ProcessLogix Server or ProcessLogix Client.
Preface Minimum Hardware Requirements 3 ProcessLogix R400.0 Server Software must be installed on a PC that is specifically qualified. Use of any other PC variations will render the standard warranty and support agreement null and void. Refer to Table P.1: Supported Hardware for ProcessLogix R400.0 on page P-3 to review the hardware requirements for a new R400.0 ProcessLogix Server. See Table 11.B on page 11-5 and Table 11.C on page 11-6.
Preface 4 Rockwell Automation Technical Support 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 Conventions 5 Terms and Type Representations The following table summarizes the terms and type representation conventions used in this Guide. 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. (Assumes cursor is positioned on object or selection.) Double-click the Station icon.
Preface 6 Contents of Release The following software and documentation components are included in the ProcessLogix R400.0 Software/documentation kit (1757-SWKIT4000). Release Components Catalog and part numbers ProcessLogix R400.0 CD 1 and CD 2 ProcessLogix Engineering Tools ProcessLogix Server Software RSLinx 2.3 1757-SWKIT4000 CD 1 957555-50 CD 2 95760375 ProcessLogix Knowledge Builder CD 1757-SWKIT4000 957555-41 ProcessLogix R400.0 Documentation Set Including: The ProcessLogix R400.
Preface 7 ProcessLogix R400.0 Installation and Upgrade Guide The ProcessLogix R400.0 Installation and Upgrade Guide is shipped with a ProcessLogix system and provides: • • • • procedures for upgrading an R320.0 system to R400.0 procedures for updating the firmware to R400.0 levels procedures for installing the software on a clean PC procedures for tasks associated with migrating to redundant Server and/or redundant Controller architecture.
Preface 8 Acronyms and Abbreviations AI — Analog Input LAN — Local Area Network AO — Analog Output LED — Light Emitting Diode CB — Control Builder MAC — Media Access Control CCL — Control Component Library MB — Megabytes CD — Compact Disc NTFS — Windows NT File System CDA — Control Data Access NUT — Network Update Time CD-ROM — Compact Disc Read Only Memory NTFS — Windows NT File System CEE — Control Execution Environment NUT — Network Update Time CM — Control Module ODBC — Open Database
Chapter 1 ProcessLogix R400.0 Installation Introduction Operating System Support ProcessLogix Component Configuration Table The following table shows the supported operating systems for ProcessLogix. Table 1.A ProcessLogix Component Configuration Table ProcessLogix NT 4.0 Windows 2000 Workstation Server Professional ✔ Server Client Operating System Options Server ✔ ✔ ✔ ✔ The hardware platform and all devices contained within it designated for running the ProcessLogix R400.
1-2 ProcessLogix R400.0 Installation Introduction IMPORTANT If you plan to use Microsoft Excel Data Exchange, Microsoft Excel 2000 must be installed before installing ProcessLogix. Clean Install The Clean Install is a clean machine installed with ProcessLogix R400.0 Server software. That is, the installation begins with formatting the hard disk and installing Windows 2000 Server. Refer to Installing ProcessLogix Software on a Clean PC on page 3-1. Upgrade from ProcessLogix R320.
ProcessLogix R400.0 Installation Introduction ProcessLogix Client Supported Installations 1-3 Clean Install If you have a new client system, refer to ProcessLogix Client Installation and Upgrade Procedures on page 5-1. A clean install is not required for upgrading R320.0 Client software to R400.0. If performing this option, backup all the data on the system, then follow the instructions in Saving Important Data on page 5-6. Upgrade: Currently Running Windows NT 4.
1-4 ProcessLogix R400.
Chapter 2 Operating System Installation Procedures ATTENTION ! These installation scenarios use a “clean” PC installation method in which all data on the system will be removed/erased. This is an irrecoverable action. All data must be first “backed up” or transferred to another system before proceeding. R400.0 ProcessLogix Servers require the Windows 2000 Server operating system. R400.0 ProcessLogix Client Stations may use Windows 2000 Professional, Windows 2000 Server, Windows NT 4.
2-2 Operating System Installation Procedures Copies of the Service Packs and Internet Explorer are included on the ProcessLogix software CD for your convenience.
Operating System Installation Procedures 2-3 Creating Boot Floppies If your system does not support booting from a CD-ROM, follow these instructions to create the required Boot Floppies. Otherwise, skip to Starting the Installation from the CD-ROM on page 2-4. IMPORTANT If your installation requires additional Drivers to be installed for access to the Hard Disk Controller, Disk Device, or CD-ROM, it may be necessary to start the installation via the Boot Floppies.
2-4 Operating System Installation Procedures 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. When all the boot floppies have been made, shut down the PC. Starting the 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.
Operating System Installation Procedures 2-5 6. Press any key to boot from the CD-ROM. ATTENTION ! 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. Completing the Windows 2000 Server Installation 1. Press Enter on Welcome to Setup Screen. 2. If requested, insert the Windows 2000 Server CD into the CD-ROM drive and press Enter.
2-6 Operating System Installation Procedures Setup will format the partition. This takes a few minutes to complete. ATTENTION ! Certain PCs will limit the size of the partition that you can create. Windows 2000 supports a boot partition size up to a 32 Gigabytes on a NTFS formatted drive. If your system has a limitation, create the largest partition you can, and leave the leftover space as unpartitioned. (You can create and format the unpartitioned space later.
Operating System Installation Procedures • 2-7 Enter the Computer Name. ATTENTION ! 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.
2-8 Operating System Installation Procedures • Only the Accessories and Utilities, Indexing Service and Script Debugger remain checked. • Click Next. 14. At • • • the Date and Time Settings window: If necessary, adjust the Date and Time settings. Set the appropriate Time Zone for your location. Uncheck the Automatically adjust clock for daylight saving changes option. • Click Next.
Operating System Installation Procedures 2-9 The following Private Networking IP Address scheme can be utilized for the system to operate: Non-Redundant or Primary Redundant Server: NIC 1: 192.168.0.1, NIC 2: 192.168.1.1, NIC 3: 192.168.2.1 Backup Redundant Server: NIC 1: 192.168.0.2, NIC 2: 192.168.1.2, NIC 3: 192.168.2.2 • Fill in the appropriate Subnet Mask. All configurations use a Subnet Mask of 255.255.255.0 and a blank Default Gatetway. • If necessary, fill in the appropriate Default gateway.
2-10 Operating System Installation Procedures Clean System Windows 2000 Professional Installation Windows 2000 Professional is the preferred Client operating system for ProcessLogix R400.0. The current required Operating System components are Windows 2000 Professional with Windows 2000 Service Pack 2 applied and Internet Explorer 5.5 Service Pack 1. The Windows 2000 Professional software, Service Packs, and Internet Explorer are licensed products of Microsoft Corporation.
Operating System Installation Procedures 2-11 If you received your PC from the manufacturer with Windows 2000 Professional pre-installed, skip to Installing Service Pack 2 for Windows 2000 on page 2-17. ATTENTION ! Consult the PC Manufacturer for any specialized instructions/procedures related to the installation of the Microsoft Windows 2000 Professional operating system. This procedure lists only the generic installation procedure.
2-12 Operating System Installation Procedures 4. At the DOS prompt, key in: >D:< and press Enter. 5. Key in this command: >cd bootdisk< and press Enter. 6. Key in this command: >makeboot< and press Enter. 7. Enter the letter of your floppy disk drive. >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. When all the boot floppies have been made, shut down the PC.
Operating System Installation Procedures 2-13 3. When prompted, enter into the computer’s BIOS setup program. 4. Verify that the Boot Priority has the CD-ROM device listed first. (Before the floppy or hard disk devices.) 5. Exit the BIOS and save the setting. 6. Press any key to boot from the CD-ROM. ATTENTION ! 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.
2-14 Operating System Installation Procedures Use the entire hard disk if possible, see note below. 6. Format the partition using the NTFS file system. Setup will format the partition. This takes a few minutes to complete. ATTENTION ! Certain PCs will limit the size of the partition that you can create. Windows 2000 supports a boot partition size up to a 32 Gigabytes on a NTFS formatted drive.
Operating System Installation Procedures • Confirm the password. IMPORTANT • 2-15 Be sure to document the Administrator Password. (It is required later in the procedure.) The Administrator Account and password gives a user full access to the system. Care should be taken to who has access to this information. Click Next. 13. At • • • the Date and Time Settings window: If necessary, adjust the Date and Time settings. Set the appropriate Time Zone for your location.
2-16 Operating System Installation Procedures Navigate in Knowledge Builder to ProcessLogix R400.0 Installation Guide⇒Network Planning Guide for more information. In some organizations, it is important that these addresses are controlled by the IT organization. Consult your company’s practices and IT organization for the appropriate IP address information. It will be necessary to use valid IP information to integrate the ProcessLogix Control system with the Business Network.
Operating System Installation Procedures 2-17 21. At this point in the installation, setup will finish installing Windows 2000. This will take some time depending on your hardware configuration. 22. At the Completing the Setup Wizard window, remove the Windows 2000 Professional CD and click Finish. 23. The PC will reboot. 24. Continue the installation with Installing Service Pack 2 for Windows 2000 on page 2-17.
2-18 Operating System Installation Procedures 4. Key in this command in the Open entry field: >winver< and press Enter. 5. In the About Windows window, look to see if the following text appears: Version 5.0 (Build 2195: Service Pack 2) If the line appears as shown, you can skip to Installing Internet Explorer 5.5 SP1 on page 2-19. If the line does not say Service Pack 2, click OK and continue with Installing Windows 2000 Service Pack 2 on page 2-18. Installing Windows 2000 Service Pack 2 1.
Operating System Installation Procedures 2-19 6. Click OK to launch the Service Pack 2 setup application. 7. At the Windows 2000 Service Pack Setup window, check the boxes: • Accept the License Agreement. • Backup files necessary to uninstall this Service Pack at a later time. 8. Click Install to initiate the Service Pack 2 update. 9. At the Setup Complete window, close any open applications and click Restart. 10. Continue the installation with Installing Internet Explorer 5.5 SP1 on page 2-19.
2-20 Operating System Installation Procedures IMPORTANT If this is the first time running Internet Explorer, you will be prompted with the Internet Connection Wizard. An internet connection is not required for this function or ProcessLogix software use. However, components in the software are required. 3. Double-click the Internet Explorer icon on the Desktop. a. Click the I want to setup my Internet connection manually… option, and click Next. b.
Operating System Installation Procedures 2-21 3. Use the Administrator user account and enter the appropriate password. TIP If this is the first time start since the operating system install, it will be necessary to remove the default startup Screens Professional Systems 1. On the Getting Started with Windows 2000 window, uncheck box Show this screen at startup checkbox. 2. Click Exit. Server Systems 1.
2-22 Operating System Installation Procedures Installing Adobe Acrobat Reader 4.05 Adobe Acrobat Reader 4.05 is required to view *.pdf files contained in Knowledge Builder. Follow these steps to install Acrobat Reader 4.05. 1. Insert the ProcessLogix R400.0 Knowledge Builder CD into the CD-ROM drive. 2. Click Start⇒Run. 3. Key in this path location in the Open entry field or use Browse to navigate to the Setup.exe file on the CD. >D:(or your CD-ROM drive letter)\Adobe\Setup.exe< 4. Click OK. 5.
Operating System Installation Procedures 2-23 Adjusting the Video Settings The system applications and displays have been optimized to be displayed at a resolution of 1024 by 768 with 65K (High Color, 16 bit). Utilizing any other setting than this will produce anomalies in some displays. Set the Video Settings by performing the following tasks: 1. Right mouse click on the desktop and select Properties. 2. Choose the Settings tab. 3. Click Advanced in the lower right hand side of the window. 4.
2-24 Operating System Installation Procedures Setting Up Additional Drivers Using the Microsoft Windows 2000 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-25 Table 2.A Required System Settings for ProcessLogix R400.0 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-26 Operating System Installation Procedures Creating the ProcessLogix User Accounts You must create a Process User account to be used to perform the ProcessLogix R400.0 Software installation. Follow the steps below to create and logon with the ps_user and erserver accounts on Windows 2000. IMPORTANT All R400.0 Systems are required to use the ps_user account. This is a change from R320.0, where most systems used the plx_user account.
Operating System Installation Procedures 2-27 9. On ProcessLogix Servers, repeat steps 5 through 8 for the erserver account. 10. Click Close. 11. Double Click the ps_user account. 12. Click the Member of Tab on the ps_user Properties window. 13. Click Add. 14. Under Name, click on Administrators and click Add. 15. Click OK. 16. Click Apply, then click Close. 17. On ProcessLogix Servers, repeat steps 11 through 14 for the erserver account. 18. Close the Computer Management window.
2-28 Operating System Installation Procedures Clean System Windows NT 4.0 Workstation Installation IMPORTANT If the Windows NT boot disks are not available to you, contact Rockwell Automation Technical Support for more information. Refer to Rockwell Automation Technical Support on page P-3. Overview Windows NT Workstation can be used for a ProcessLogix Client only. If Windows NT is already installed on your PC, skip to Installing Service Pack 6a for Windows NT 4.0 on page 2-35.
Operating System Installation Procedures 2-29 Starting the Windows NT Installation Use the following procedure to start the installation of the Windows NT 4.0 software. IMPORTANT If you are installing software from a network Server, contact your network administrator for information on starting the setup process. This procedure assumes that: • All network cards are installed in the PC and they are set to the correct IRQs.
2-30 Operating System Installation Procedures 7. Check the displayed list of partitions for Windows NT installation. 8. Follow the on-screen prompts to select or create a partition that uses the entire hard drive, if possible. IMPORTANT Setup cannot create a partition greater than 4 gigabytes. In this case, create one partition as 4 GB for ProcessLogix and leave the balance as unpartitioned. The balance may be partitioned later using NT Disk Administrator. 9.
Operating System Installation Procedures 2-31 6. Enter a lower case computer name for your PC. IMPORTANT Be certain that the caps lock is not enabled. The computer name must be typed in lower case. You will notice that when you type, the computer name displays in capital letters. ATTENTION 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”.
2-32 Operating System Installation Procedures • The subnet mask for your network. • The default gateway, if appropriate. • Whether or not you are going to enable Windows Internet Name Service (WINS) and Domain Name Service (DNS) lookups. 1. Select Wired to the network, when prompted, even if you do not have a network card. This will specify whether this PC will participate in a network. 2. Click Next. 3. Setup prompts you to identify the type of network card installed in your PC. a.
Operating System Installation Procedures 2-33 9. If the MS Loopback Adapter is being installed, accept the frame type of 802.3 in the MS Loopback Adapter Card Setup dialog box. 10. Click No in response to the prompt for whether there is a DHCP Server on the network, unless advised otherwise by your network administrator. 11. If you selected No in Step 10, enter the following TCP/IP settings in the appropriate Microsoft TCP/IP Properties tabbed pages.
2-34 Operating System Installation Procedures • For a Domain, it may be necessary to work with your network administrator to create the proper accounts and access before you can join the domain. Verify that you are following the recommended outline as set forth in the ProcessLogix Network Planning Guide. Contact Rockwell Automation Technical Support if necessary for assistance with Domain groups. • If you are configuring a stand-alone network, key in the workgroup with a name such as PLX_NTWRK.
Operating System Installation Procedures 2-35 Setting Up the Display Driver Use the following procedure to set up the display driver on the PC. 1. Setup automatically detects your PC’s video card. Click OK to confirm the detected card and click OK again to exit. It may be necessary to skip the application of your video card driver until after the Service Pack is applied. If this is the case, use the default VGA Driver and install the newer version after the Service Pack installation.
2-36 Operating System Installation Procedures TIP If you received your Client PC from the manufacturer with Windows NT preinstalled with 128-bit components, you may need to download the High Encryption Version of Service Pack 6a. This can be obtained from Microsoft’s web site: www.microsoft.com/ntserver/nts/downloads/recommended/SP6/allsp6.asp 1. Insert the ProcessLogix R400.0 Software CD 2 into the CD-ROM drive. 2. Click Start⇒Run. 3.
Operating System Installation Procedures 2-37 Setting Up Additional Drivers after the Service Pack Installation ATTENTION ! If your particular video card is not detected (only a VGA card is detected), you need to install drivers provided by the PC manufacturer. You can do this after Windows NT is installed through the Control Panel application. 1. Click Start⇒Settings⇒Control Panel. 2. Double-click the Display icon. 3. Click the Settings tab. 4. Click Display Type. 5.
2-38 Operating System Installation Procedures 8. Click Test and click OK to invoke a sample screen. • If the sample screen displays correctly, click Yes. • If it does not display correctly, click No. Change the Desktop Area, Color Palette, or Refresh Frequency and repeat this step to correct the problem. 9. Close the Display Properties window. Close the Control Panel. 10. Add any other required drivers at this time. For example, Tape Drive, Sound Card, etc.
Operating System Installation Procedures 2-39 Converting to NTFS after Installing Windows NT If the PC is currently using a FAT file system, use the following procedure to convert to the NTFS file system. The ProcessLogix Server software must run on a PC using the NTFS file system. 1. Click Start⇒Run. 2. Key in this command in the Open entry field: >cmd< and click OK to open the DOS window. 3.
2-40 Operating System Installation Procedures Checking Required System Settings The following table summarizes the various system operating settings required for optimum ProcessLogix software operation. You can access these settings through the common Control Panel, Administrative Tools, and Windows NT Explorer selections. Once Windows NT is installed, verify that the communications card (PCIC or Ethernet) was installed.
Operating System Installation Procedures Function Required Setting Value 2-41 Path to Setting Browser – Internet Explorer • Microsoft Internet Explorer 5.01 File version: 5.00.2919.6304 Logon Account • Verify that the installation account, such as ps_user is configured correctly. Start⇒Programs⇒Administrative Tools (Common)⇒User Manager (Double-click ps_user in the username field of the dialog box.
2-42 Operating System Installation Procedures Publication 1757-IN040B-EN-P - March 2002
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 Redundant Servers Directory Structures If you have redundant Servers, you must install software on the SERVERA node first. Then complete the software installation process again for the SERVERB node. You must install the ProcessLogix Server on the same partition on both the primary and backup servers and that their directory structures match.
ProcessLogix Server Installation Procedures 3-3 3. Insert the ProcessLogix R400.0 Software CD 1 into the CD-ROM drive. 4. Click Start⇒Run. 5. Key in this path location in the Open entry field or use Browse to navigate to the msxml3mm.exe file on the CD. >D:(or your CD-ROM drive letter)\XML3\msxml3mm.exe< 6. Click OK to launch the MSXML 3.0 setup application. 7. Click Yes to accept the license agreement. 8. Click Browse to navigate to C:\winnt\system32 and click OK. 9. Click OK to extract files. 10.
3-4 ProcessLogix Server Installation Procedures Installing Knowledge Builder 1. Insert the ProcessLogix R400.0 Knowledge Builder CD into the CD-ROM drive and click Yes. ATTENTION ! Clicking No will abort the entire installation. 2. At the Welcome window, click Next. 3. Click the I accept the terms option and click Next. 4. Click the ProcessLogix option and the desired install type and click Next.
ProcessLogix Server Installation Procedures 3-5 2. At the RSLinx Welcome window, click Next. 3. Click the I accept the terms option and click Next. 4. Enter the User Name and Organization whom the RSLinx package is registered, and click Next. 5. Click the Standard Feature Set option and click Next. 6. At the Ready to Install window, click Install. 7. At the InstallShield Wizard Completed window, click Finish. 8. After reviewing, close the Release Notes window. 9. Click OK to reboot the PC.
3-6 ProcessLogix Server Installation Procedures Installing PsAxCtl Document EXE 1. Click OK to acknowledge the change directory warning. 2. At the PsAxCtl Document EXE Setup Welcome window, click OK. 3. Verify that the destination directory is: C:\Honeywell\TPS50\System\Bin. 4. Click the PC icon install button. 5. At the Setup complete window, click OK. Installing the ProcessLogix Server 1. At the Welcome to ProcessLogix Server Setup window, click Next. 2.
ProcessLogix Server Installation Procedures 3-7 4. At the Choose ProcessLogix Server Options window, select Microsoft Excel Data Exchange and/or Network API. Click Next. TIP In Step 5 through Step 12 below, you MUST NOT change the directory names from their defaults. If you do change directory names, the ProcessLogix system may not operate properly. 5. Click Next to accept the default directory for the Server Software. 6. Click Next to accept the default directory for the Client Software. 7.
3-8 ProcessLogix Server Installation Procedures a. Key in >mngr123< as the manager account password and press . b. Key in >mngr123< again to confirm password and press . c. Key in >engr123< as the engineering account password and press . d. Key in >engr123< again to confirm password and press . e. Key in >oper123< as the operator account password and press . f. Key in >oper123< again to confirm password. g. Click Next to complete the password entry. 14.
ProcessLogix Server Installation Procedures 3-9 20. Skip this step if the system does not include Excel Data Exchange. Otherwise, click Enable Macros when requested. TIP If a Microsoft Excel dialog box appears, check the Do not show this dialog again checkbox and click OK. ATTENTION ! The CD must remain in the CD-ROM drive. You must select No in Step 21. 21. At the Setup Complete window, click the No, I will restart my computer later option and click Finish. IMPORTANT If the message “Dr.
3-10 ProcessLogix Server Installation Procedures 25. 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. Once you have completed these procedures for both SERVERA and SERVERB, restart SERVERB. 4. Logon to SERVERB as ps_user. 5.
ProcessLogix Server Installation Procedures 3-11 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. IMPORTANT ATTENTION ! Complete Step 1 and Step 2 in the following procedure to determine your current RSLinx version. If you need to reformat the hard drive, you must first move the activation file back to the RSLinx Master Disk using the same general procedure as follows.
3-12 ProcessLogix Server Installation Procedures – For ControlNet Supervisory Networks, skip to Configuring RSLinx Drivers for ControlNet Supervisory Network on page 3-13. – For Ethernet Supervisory Networks, skip to Configuring RSLinx Drivers for Ethernet Supervisory Network on page 3-18. 3. Close RSLinx. Installing the Activation File 1. Locate the RSLinx Master Disk and insert it into the floppy drive. 2. Click Start⇒Run. 3.
ProcessLogix Server Installation Procedures 3-13 9. Restart the PC. TIP 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-7. IMPORTANT If you are installing ProcessLogix software on a redundant Server pair, return to the beginning of Moving the RSLinx Activation File on page 3-10 and repeat for SERVERB.
3-14 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-15 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-16 ProcessLogix Server Installation Procedures – For Ethernet Supervisory Networks, skip to Completing the ProcessLogix R400.0 Install on a Non-Redundant Server on page 3-20. • If the Firmware is not 3.5.33 go to Step 8. 8. Click Firmware to initiate the firmware update. 9. Click Yes to acknowledge the Warning prompt. 10. Navigate to the directory: C:\Honeywell\TPS50\System\Firmware\1784-PCIC\3_5_33 11. Select the 1784pcic_3_5.nvs file so that it appears in the filename entry field. 12.
ProcessLogix Server Installation Procedures 3-17 Reconfiguring RSLinx Drivers for ControlNet Supervisory Network Use the following procedure to reconfigure the 1784-PCIC drivers for RSLinx. 1. Click Start⇒Programs⇒Rockwell Software⇒RSLinx⇒RSLinx to call up the Rockwell Software RSLinx window. 2. Click Communications⇒Configure Drivers to call up the Configure Drivers dialog box. 3.
3-18 ProcessLogix Server Installation Procedures 4. In the Configure Drivers dialog box, you should see AB_PCIC-1 listed in the Configured Drivers list with the status Running. If the AB_PCIC-1 driver status is not Running, call Rockwell Automation Technical Support. Refer to Rockwell Automation Technical Support in the Preface. 5. Click Close to close the Configure Drivers dialog box. 6. Close RSLinx. 7. Restart the PC.
ProcessLogix Server Installation Procedures 3-19 Navigate in Knowledge Builder to: Ethernet Implementation Guide⇒Configuration⇒Setting Up Drivers and IP Addresses for more information. 2. Configure the IP Address for each controller. Navigate in Knowledge Builder to: Ethernet Implementation Guide⇒Configuration⇒Setting Up Drivers and IP Addresses⇒Configuring and setting IP address for Ethernet module section for more information. 3. Configure RSLinx drivers.
3-20 ProcessLogix Server Installation Procedures Upgrading Hardware Component Firmware Completing the ProcessLogix R400.0 Install to Loading 1757-PLX52, TC-MUX021, or 1757-FIM Boot on a Non-Redundant Server 1. Refer and Personality Images on page 7-9 to upgrade the 1757-PLX52 boot and personality images to the current release level. 2. After upgrading the 1757-PLX52, refer to Upgrading Hardware Component Firmware on page 7-4 to check if other hardware components require upgrades.
ProcessLogix Server Installation Procedures 3-21 Creating an Emergency Repair Disk After all installations and drivers are installed, you should create an Emergency Repair Disk. Use the following procedure to create an emergency repair disk for your Windows 2000 Server installation. 1. Insert a blank diskette into the PC’s floppy drive. 2. Click Start⇒Programs⇒Accessories⇒System Tools⇒Backup. 3. Click Emergency Repair Disk. An Emergency Repair Diskette window appears. 4.
3-22 ProcessLogix Server Installation Procedures Publication 1757-IN040B-EN-P - March 2002
Chapter 4 ProcessLogix Server Upgrade Procedures Preparing for a ProcessLogix Software Upgrade Things to consider before upgrading IMPORTANT ProcessLogix systems are required to replace the system with new hardware and operating system for ProcessLogix R400.0 Server use. The procedures in this section assume that the old ProcessLogix R320.0 system(s) and new ProcessLogix R400.0 system(s) are different PC hardware. The new R400.0 system is required to be fully up and configured at this stage.
4-2 ProcessLogix Server Upgrade Procedures 4. Key in this command: >NET USE T: \\PLX1\C$ /user:ps_user< (where PLX1 is the R400.0 Server name) and press Enter. 5. Open Windows NT Explorer and confirm that the T: drive exists. For a Redundant Server Pair 1. Logon to the old R320.0 SERVERB as plx_user. Use the following procedure to map a drive to the new R400.0 Backup Server. 2. Click Start⇒Run. 3. Key in this command in the Open entry field: >cmd< and click OK to open the DOS window. 4.
ProcessLogix Server Upgrade Procedures 4-3 9. Key in this command: >NET USE T: \\PLX1A\C$ /user:ps_user< (where PLX1A is the name of the R400.0 Primary Server) and press Enter. 10. Open Windows NT Explorer and confirm that the T: drive exists. Upgrade Procedures for ProcessLogix R320.0 Servers ATTENTION ! All procedures listed in this section should be performed with the system(s) Off-Process. Be certain that your process is off control before you begin any upgrade procedure.
4-4 ProcessLogix Server Upgrade Procedures Exporting the Engineering Repository Database Stopping the ER Replicator Service Perform these steps on an R320.0 redundant Server pair. 1. On SERVERB, click Start⇒Settings⇒Control Panel. 2. Double-click the Services Icon. 3. Select the ProcessLogix ER Replicator service and click Stop 4. Click Yes to confirm. 5. Close the Services and Control Panel Windows. Exporting the Database Using Control Builder Perform these steps on a non-redundant Server or SERVERB. 1.
ProcessLogix Server Upgrade Procedures 4-5 Saving Important Data Each of the following items should be considered before proceeding. Table 4.A Item Options System Displays Document any changes that were made to existing system displays. You must reapply the changes to the new display after the upgrade. This applies in particular to the System Startup display, which is often customized. Station Menus Document any changes that were made to existing menus.
4-6 ProcessLogix Server Upgrade Procedures Table 4.A Item Options 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. Navigate in Knowledge Builder to Server and Client Configuration Guide⇒Configuring Stations and Printers⇒Using Station for Configuration for more information. Alarms and messages Alarms and messages currently in the system cannot be copied across for the upgrade.
ProcessLogix Server Upgrade Procedures 4-7 3. At the DOS prompt, key in the following command: >hscserver /unload /y< 4. Key in the following command: XCOPY C:\Honeywell\server\data\*.* T:\Honeywell\Server\data.upgrade /S /E 5. If necessary, enter >D< to specify that data.upgrade is a directory. 6. Wait until the C:\ prompt appears and close the DOS window. Removing the RSLinx Software Activation File It is possible to transfer your RSLinx Activation codes from the old system to the new system.
4-8 ProcessLogix Server Upgrade Procedures 7. Click Move to move the file to the hard drive. Wait for a dialog box to give a successful move indication, and click OK to exit. 8. Remove the Master Disk from your floppy drive and store it in a safe place Restoring the Data IMPORTANT All work performed in this section occurs on the new ProcessLogix R400.0 Systems. A redundant Server pair should have completed setting up database replication before importing the Engineering Repository.
ProcessLogix Server Upgrade Procedures 4-9 2. Logon to SERVERB as ps_user. IMPORTANT All R400.0 Systems are required to use the ps_user account. This is a change from R320.0, where most systems used the plx_user account. Synchronizing Server Databases on Redundant Servers The following can be performed on the Primary or Backup Server. 1. Click Start⇒Programs⇒ProcessLogix Server⇒Station. 2. Click View⇒System Status⇒Server Redundancy to call up the Server redundancy display. 3.
4-10 ProcessLogix Server Upgrade Procedures Importing the ProcessLogix Server Points Database ATTENTION ! For Redundant systems, these steps are performed on the SERVERA node, with the SERVERB node shut off. 1. Logon to the system as ps_user. 2. Click Start⇒Run. 3. Key in this command in the Open entry field: >cmd< and click OK to open the DOS window. 4. At the DOS prompt, key in the following command: >hscserver /stop /y< and press Enter. 5.
ProcessLogix Server Upgrade Procedures 4-11 and press Enter. Depending on the size of your database, this may take several minutes. 10. To start the ProcessLogix Server Key in the following command: >hscserver /start /y< and press Enter. Importing the Engineering Database Perform the steps below to import the Engineering Database. For a redundant Server pair, these steps are performed on SERVERB. 1. Logon to the system as ps_user. 2. Click Start⇒Programs⇒ProcessLogix Engineering Tools⇒Control Builder.
4-12 ProcessLogix Server Upgrade Procedures 10. In the Project tab, confirm that the components of your configured control strategy are listed in the Root directory. ATTENTION ! If you also upgraded from a non-redundant 1757-PLX52 to a redundant 1757-PLX52, you must delete the existing CPM and its associated CEE from the Project tab, reconfigure a new 1757-PLX52 and its associated CEE, and reassign the components before you download the CPM to the Controller. 11.
ProcessLogix Server Upgrade Procedures 4-13 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 R400.0 Server to Tape on page 8-7.
4-14 ProcessLogix Server Upgrade Procedures Publication 1757-IN040B-EN-P - March 2002
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 ! Original releases of the NT 4.0 Operating system could not address boot partitions larger than 4 GB. Later, fixes were applied for NT 4.0 to address up to a 7.8 GB boot partition. Windows 2000 operating systems can address up to a 32 GB boot partition natively, and larger partitions with certain hardware configurations. ProcessLogix R400.0 Client Software requires that the boot partition be at least 4 GB.
ProcessLogix Client Installation and Upgrade Procedures 5-3 Clean Install: Windows 2000 Professional The following table lists the item that you MUST complete before installing the ProcessLogix Client Software. ✔ Step Item Page 1. Clean System Windows 2000 Professional Installation 2-10 2. Installing Service Pack 2 for Windows 2000 2-17 3. Installing Internet Explorer 5.5 SP1 2-19 4. Installing Adobe Acrobat Reader 4.
5-4 ProcessLogix Client Installation and Upgrade Procedures For these scenarios, the current required Operating System components are Windows NT 4.0 Workstation with the following: • Service Pack 6a includes enhancements and fixes for the NT 4.0 operating system. • Internet Explorer 5.5 SP1 installs the underlying support needed for the HTML technology support. • XML 3.0 adds additional support used by some of the client applications. • MDAC 2.
ProcessLogix Client Installation and Upgrade Procedures 5-5 If you are installing ProcessLogix Client to a Clean PC, skip to Installing ProcessLogix R400.0 Client Software on page 5-18. Upgrading a ProcessLogix R320.0 Windows NT 4.0 Workstation Client to a ProcessLogix R400.0 Windows NT 4.0 Workstation Client The following table lists the items that you must complete to upgrade a R320.0 Windows NT 4.0 Client to a R400.0 Windows NT 4.0 Client ✔ Step Page 1. Saving Important Data 5-6 2.
5-6 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 5-7 Table 5.A Item Options Localization Localization settings are lost during the upgrade, reapply the settings after the upgrade. Station configuration file Winnt\station.ini If you have made changes in the station.ini file, you will need to reapply them to the new file after the upgrade. The IconPopToTopOnAlarm option has been removed, and is no longer recognized by Station.
5-8 ProcessLogix Client Installation and Upgrade Procedures 1. Click Start⇒Settings⇒Control Panel. 2. Double-click the Add/Remove Programs icon. 3. Click on Knowledge Builder in the list of installed programs and click Add/Remove. 4. Click Yes to confirm. 5. At the Remove Shared File prompt, click Yes to All. 6. Click Yes to confirm. 7. When completed, click OK. Removing PsAxCtl Document EXE This procedure is required for an R320.0 Engineering Workstation only. If you are upgrading an R320.
ProcessLogix Client Installation and Upgrade Procedures 5-9 5. At the Remove Shared File prompt, click Yes to All. 6. Click Yes to confirm. 7. When completed, click OK. Removing Quick Builder 1. Click Start⇒Settings⇒Control Panel. 2. Double-click the Add/Remove Programs icon. 3. Select Quick Builder and click Add/Remove. 4. At the Welcome window, click Next. 5. Select the Remove option and click Next. 6. Click Remove. 7. Click OK to acknowledge the couldn’t remove QB shortcuts warning. 8.
5-10 ProcessLogix Client Installation and Upgrade Procedures 3. Key in this path location in the Open entry field or use Browse to navigate to the R3xxCleanUp.exe file on the CD and click Open. >D:(or your CD-ROM drive letter)\tools\R3xxCleanUp.exe 4. Click OK. 5. At the Warning, click Continue. 6. Select the R3XX Client to R400 Client option and click Run. 7. The application determines whether or not your system requires Cleanup from prior Process Installations.
ProcessLogix Client Installation and Upgrade Procedures 5-11 b. Key in this path location in the open entry field or use Browse to navigate to the setup.exe file on the CD. >D:(or your CD-ROM drive letter)\setup.exe< c. Click OK. 2. Click Yes in response to the question: Would you like to upgrade to Windows 2000? 3. At the Welcome window, select the Upgrade to Windows 2000 option and click Next. 4. Select the I accept this agreement option and click Next. 5.
5-12 ProcessLogix Client Installation and Upgrade Procedures Installing Windows 2000 Service Pack 2 Refer to Installing Service Pack 2 for Windows 2000 on page 2-17. Installing Internet Explorer 5.5 SP1 Refer to Installing Internet Explorer 5.5 SP1 on page 2-19. Installing ProcessLogix R400.0 Client Software Refer to Installing ProcessLogix R400.0 Client Software on page 5-18. Updating the Windows NT 4.0 Workstation Operating System for R400.0 Software If you are upgrading Windows NT 4.
ProcessLogix Client Installation and Upgrade Procedures IMPORTANT 5-13 Be sure to logon as ps_user. If you don’t have a user ps_user account, you must create one at this time. Refer to Creating the ProcessLogix User Accounts on page 2-26. Checking for Windows NT 4.0 Service Pack 6a R320.0 systems should already have the service pack applied. To verify the current Service Pack level, perform the following steps: 1. Click Start⇒Run. 2. Key in winver in the Open entry field and press Enter. 3.
5-14 ProcessLogix Client Installation and Upgrade Procedures >D:(or your CD-ROM drive letter)\nt_sp6a\sp6i386.exe< 4. Click OK to launch the Service Pack 6a setup application. 5. If a third-party system utilities message appears, click OK. 6. At the Setup window, check the boxes: • Accept the License Agreement • Backup files necessary to uninstall the Service Pack at a later time. 7. Click Install to initiate the Service Pack 6a update. 8.
ProcessLogix Client Installation and Upgrade Procedures 5-15 Recording the NT System Path Value If you are running Windows NT, you MUST record the NT System Path before installing Windows Installer. 1. Click Start⇒Settings⇒Control Panel. 2. Double-click the System icon. 3. Click the Environment tab. 4. Select the Path from the System Variables list. 5. Record the Path Value. TIP Use Notepad to create a file C:\path.txt. Copy the path value into this file and save.
5-16 ProcessLogix Client Installation and Upgrade Procedures 2. Double-click the System icon. 3. Click the Environment tab. 4. Select the Path from the System Variables list. 5. If the Path Value does not match the recorded path value from before the uninstall, change the path value to the recorded value. 6. Click Set and then click OK. 7. Close the Control Panel. Installing Internet Explorer 5.5 SP1 Internet Explorer 5.5 SP1 is required for ALL ProcessLogix systems.
ProcessLogix Client Installation and Upgrade Procedures 5-17 Updating the ActiveX Support Files This installation will update support files for ActiveX components which will be installed via the ProcessLogix Client installation. Failure to perform this step will cause the client installation to fail. 1. Insert the ProcessLogix R400.0 Software CD 2 into the CD-ROM drive. 2. Click Start⇒Run. 3. Key in this path location in the Open entry field or use Browse to navigate to the setup.exe file on the CD.
5-18 ProcessLogix Client Installation and Upgrade Procedures Installing ProcessLogix R400.0 Client Software Follow the steps in the section for installing the ProcessLogix R400.0 Client software. IMPORTANT If you plan to use Microsoft Excel Data Exchange, you must install Microsoft Excel 2000 prior to starting this procedure. Use the following procedure to install these ProcessLogix client software components in succession.
ProcessLogix Client Installation and Upgrade Procedures 5-19 11. Click OK to launch the software setup application. 12. Select the Engineering Workstation or Operator Workstation option and click Next. 13. At the Product Selection Completed window, click Continue. 14. The ProcessLogix R400.0 Software CD 1 ejects. Installing Knowledge Builder 1. Insert the ProcessLogix R400.0 Knowledge Builder CD into the CD-ROM drive and click Yes. ATTENTION ! Clicking No will abort the entire installation. 2.
5-20 ProcessLogix Client Installation and Upgrade Procedures 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-20. 1. At the Ready to Install window, click Install. TIP Command windows will appear during Engineering Tools install. These windows will close automatically. 2. Click Finish.
ProcessLogix Client Installation and Upgrade Procedures 5-21 2. At the Choose Setup Type window, click ProcessLogix Client setup (laptop icon). 3. At the Choose ProcessLogix Client Software window, confirm that the checkboxes for the following Client software components are checked, as appropriate for your application. Click the box to check or uncheck it, or click Select All.
5-22 ProcessLogix Client Installation and Upgrade Procedures 8. Skip to Step 10 if the Specify Microsoft Excel Directory window doesn’t appear. Otherwise, click Next to accept the default directory for Microsoft Excel.
ProcessLogix Client Installation and Upgrade Procedures 5-23 14. At the ProcessLogix Update Complete window, click Finish. 15. Wait until after the command windows have closed and file copying is complete, then remove the CD. 16. At the ProcessLogix Setup Complete window, click the No, I will restart my computer later option and click Finish. 17. Restart the PC.
5-24 ProcessLogix Client Installation and Upgrade Procedures Setting Up a Station With a Non-redundant Server Use the following procedure to set up the ProcessLogix Client node to access data in a networked ProcessLogix non-redundant Server node. 1. On the non-redundant Server node, click Start⇒Programs⇒ProcessLogix Server⇒Start-Stop ProcessLogix Server to call up the ProcessLogix Server dialog box. Check that the Server is running and close the dialog box. OR 2.
ProcessLogix Client Installation and Upgrade Procedures 5-25 9. Click Connect. 10. Click Cancel at the Unable to connect prompt, if applicable. 11. Click Station⇒Exit. 12. Click Yes to exit Station. Setting Up a Station With a Redundant Server Pair Use the following procedure to set up the ProcessLogix Client node to access data in networked ProcessLogix redundant Server nodes. 1.
5-26 ProcessLogix Client Installation and Upgrade Procedures PLX1B 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. Key in >3< as the Static Station Number or key in appropriate update rates and 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.
ProcessLogix Client Installation and Upgrade Procedures 5-27 b. Select the appropriate Station type option, Static Station or Rotary Station. c. Click Advanced. d. Key in >3< as the Static Station Number or key in appropriate update rates and display number for Rotary. e. Check the Auxiliary setup file checkbox. f. 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. 16. Click Save. 17.
5-28 ProcessLogix Client Installation and Upgrade Procedures Checking Control Builder Operation and Logging On (Engineering Workstation Only) Use the following general procedure to log on and check Control Builder operation on a ProcessLogix Engineering Workstation. 1. Click Start⇒Programs⇒ProcessLogix Engineering Tools⇒Control Builder. 2. In the Login dialog box, make these entries: a. Key in >mngr< as the default User Name. b. Key in >mngr1< as the default Password. c.
ProcessLogix Client Installation and Upgrade Procedures 5-29 4. Using the example tables, substitute your Server names for the values: PLX1 Non-redundant ProcessLogix Server PLX1A Redundant Primary ProcessLogix Server (dedicated and integrated with Engineering Database.) PLX1B Redundant Secondary ProcessLogix Server (dedicated and integrated with Engineering Database.
5-30 ProcessLogix Client Installation and Upgrade Procedures SERVERB Publication 1757-IN040B-EN-P - March 2002
Chapter 6 Additional Redundant Server Procedures Adding Redundancy to R400.0 Non-Redundant Server Systems If your Servers are already named A and B (SERVERA and SERVERB), skip to Completing the ProcessLogix R400.0 Setup on a Redundant Server Pair on page 6-1. If you are adding Server redundancy to a non-redundant system, designate an existing R400.0 non-redundant Server as the SERVERA (Primary) node. Designate the other Server as SERVERB (Secondary) node.
6-2 Additional Redundant Server Procedures C:\WINNT\SYSTEM32\DRIVERS\ETC. ATTENTION ! To support redundant Servers (Primary/Secondary), you must identify all computer names and respective unique IP addresses in the Hosts file and be sure they are resident on each ProcessLogix Client. Use the DOS command >IPCONFIG/ALL<, or access TCP/IP Properties through the General tab in the Local Area Connection Properties dialog box to obtain IP addresses for all configured components. 2.
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 IMPORTANT For information about the required operator actions for the setup of fast failover, navigate in Knowledge Builder to Server and Client Configuration Guide⇒Configuring and Monitoring Redundant Server System⇒Server Redundancy Fast Failover Configuration topic for HOSTS file and redundant hardware build details. 3. Click File⇒Exit and click Yes to save the Hosts file. 4. Repeat Step 1 to Step 3 for each Server node in your system. 5.
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) node ATTENTION ! Failure to convert the existing non-redundant 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 node. Making Redundant Hardware File Entries 1.
Additional Redundant Server Procedures 6-7 b. Click Yes to confirm the action and wait for the Server to change its state. 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 9. 4. Use Windows NT 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-8 Additional Redundant Server Procedures 11. At DOS prompt, key in: >cd \Honeywell\server\user< and press . 12. Key in 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 5 to Step 8. 13. Check that no hardware build errors are listed.
Additional Redundant Server Procedures 6-9 4. Edit the timeserv.ini file to replace the line PrimarySource =. with the new name of the Primary Server. EXAMPLE If your Primary Server is PLX1A, the line would become: PrimarySource=\\plx1a. Both Servers’ time service points to SERVERA. The file should be identical on SERVERA and SERVERB. 5. Click File⇒Save to save changes. 6. Click File⇒Exit to close Notepad. 7. Click Start⇒Run. 8.
6-10 Additional Redundant Server Procedures 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) Node Use the following procedures to set up the Secondary SERVERB node. Making Redundant Hardware File Entries Refer to Making Redundant Hardware File Entries on page 6-6 and repeat the procedures on SERVERB.
Additional Redundant Server Procedures 6-11 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. Key in 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. Verify that the data link is available.
6-12 Additional Redundant Server Procedures 3. In the Save in drop down box, select the C:\Honeywell\client\qckbld 4. Key in >Stations.qdb< in the File name field and click Save. 5. Wait for the Enable Components dialog box to appear. a. Under the System/License Details tab, click the down arrow and select ProcessLogix - R400.0 from the Server drop-down list. b. Select the Enable Components tab. c. Click UnSelect All, then check Static Station and Server. d. Click OK. e.
Additional Redundant Server Procedures 6-13 Synchronizing Server Databases on Redundant Server 1. On SERVERA, click Start⇒Programs⇒ProcessLogix Server⇒Station. 2. Click View⇒System Status⇒Server Redundancy to call up the Server redundancy display. 3. Click the Oper field in the lower right corner of the display. 4. Key in >mngr< in the Station Logon dialog box and press . 5. Click Synchronize.
6-14 Additional Redundant Server Procedures 2. Key in this command in the Open entry field: >cmd< and click OK to open the DOS window. 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 link is active and the databases are synchronized. 6. On SERVERB, click Start⇒Run. 7. Key in this command in the Open entry field: >cmd< and click OK to open the DOS window. 8.
Additional Redundant Server Procedures 6-15 9. The unsynchronized SERVERB data should be similar to this: 10. Verify that the link is active and the databases are synchronized. Setting up the Redundant ERDB Complete the following procedure on SERVERB only: 1. Click Start⇒Programs⇒ProcessLogix Engineering Tools⇒DB Admin. 2. In the Login dialog box, make these entries: a. Key in >mngr< as the default User Name. b. Key in >mngr1< as the default Password. c. Key in SERVERB in the Server Name field. 3.
6-16 Additional Redundant Server Procedures Setting Up Station on SERVERB 1. On SERVERB, 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. On the Connection tab, make these entries to have the Station point to the SERVERB (PLX1B) node: a. In the Server field, key in or Browse to the Secondary Server name, SERVERB. b.
Additional Redundant Server Procedures g. • • • 6-17 Click Add and then Browse and add the following directories. C:\honeywell\client\system\r400 C:\honeywell\client\abstract C:\honeywell\client\dspbld 6. Click Save. 7. Click Yes to save the new connection. 8. Key in >defaultb.stn< in the File name field and click Save. 9. Highlight defaultb and click Connect. 10. Click Cancel at the Unable to connect prompt, if applicable. 11. Click Station⇒Connect to call up the Station Connect dialog box. 12.
6-18 Additional Redundant Server Procedures b. c. d. e. Select the Station type as Static Station. Key in >2< as the Static Station Number and click Advanced. Check the Auxiliary setup file checkbox. Browse and navigate to: C:\Honeywell\Client\Station\defaultb.stn and click Open. IMPORTANT You must indicate the full path to the .stn file. 14. Click Save. 15. Click Yes to save changes. 16. Highlight Default and click connect. 17. Click Cancel at the Unable to connect prompt, if applicable. 18.
Additional Redundant Server Procedures 6-19 4. Click New Connection. 5. On the Connection tab, make these entries to have the Station point to the SERVERB (PLX1B) node: a. In the Server field, key in or Browse to the Secondary Server name, SERVERB. b. Select the Station type as Static Station. c. Key in >1< as the Static Station Number and click Advanced. d. Check the Auxiliary setup file checkbox. IMPORTANT You must indicate the full path to the .stn file. e.
6-20 Additional Redundant Server Procedures 6. Click Save. 7. Click Yes to save the new connection. 8. Key in >defaultb.stn< in the File name field and click Save. 9. Highlight defaultb and click Connect. 10. Click Cancel at the Unable to connect prompt, if applicable. 11. Click Station⇒Connect to call up the Station Connect dialog box. 12. Highlight Default and click Edit Connection. 13. On the Connection tab, make these entries to have the Station point to the SERVERA (PLX1A) node: a.
Additional Redundant Server Procedures 6-21 e. Browse and navigate to: C:\Honeywell\Client\Station\defaultb.stn and click Open. IMPORTANT You must indicate the full path to the .stn file. 14. Click Save. 15. Click Yes to save changes. 16. Highlight Default and click Connect. 17. Click Cancel at the Unable to connect prompt, if applicable. 18.
6-22 Additional Redundant Server Procedures 1. Restart the SERVERA node. 2. On the SERVERA node, right-click in the taskbar to open the popup menu and click Task Manager to call up the Windows NT Task Manager dialog box. 3. Click the Performance tab in the dialog box. 4. Monitor the CPU Usage until the value displayed goes below the 90 to 100% threshold. Wait until the RSLinx icon appears in the taskbar.
Additional Redundant Server Procedures 6-23 2. After upgrading the 1757-PLX52, refer to Upgrading Hardware Component Firmware on page 7-4 to check if other hardware components require upgrades. IMPORTANT Stop! It is mandatory that you check the firmware revision levels for ALL ProcessLogix hardware components after a ProcessLogix software installation and/or a component addition or replacement. Do not proceed until you have upgraded the firmware. Then continue with the next section.
6-24 Additional Redundant Server Procedures Use the following procedure to create an emergency repair disk for your Windows 2000 Server installation. 1. Insert a blank diskette into the floppy drive. 2. Click Start⇒Programs⇒Accessories⇒System Tools⇒Backup. 3. Click Emergency Repair Disk. 4. Click Start Backup located in the right hand side of the window. An Emergency Repair Diskette window will appear. 5. Insert a blank diskette into the floppy drive. 6.
Chapter 7 Firmware Maintenance Procedures 1784-PCIC Driver and Firmware Installation ATTENTION ! If your 1784-PCIC firmware has not been updated for ProcessLogix R400.0, this procedure must be followed to use the 1784-PCIC in R400.0. With the Win2K Operating System, plug-n-play devices, like the PCIC card, are automatically detected and drivers installed, if found. The first time the system detects the PCIC driver, a Found New Hardware wizard displays and you have the option to install the driver.
7-2 Firmware Maintenance Procedures 10. If necessary, click Yes to overwrite the ABPCICSW.sys file. 11. 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. Double-click A-B 1784-PCIC(S). 5. If AB 1784-PCIC(S) is not present, you need to install the Hardware Device Drivers. Restart the PC and refer to Install Hardware Device Drivers on page 7-1. 6.
Firmware Maintenance Procedures 7-3 If this is the first time you have used Network Tools on this PC, refer to Making First Time Network Tools Settings on page 8-9 and then continue with this procedure beginning at Step 6. 1. Click Start⇒Run. 2. Key in this command in the Open entry field: >ntools -c -u< TIP If the RSLinx and PCIC driver services for system communications in ControlNet mode are not running, this command will start the services. 3. Click OK to launch the Network Tools application. 4.
7-4 Firmware Maintenance Procedures 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. About Firmware Upgrades Each ProcessLogix software version release includes files for updating the firmware version in system hardware components to levels compatible with the given release.
Firmware Maintenance Procedures 7-5 Firmware Revision Level Reference The following table lists the firmware revision levels for listed components that are current for R400.0 along with the directory locations for firmware upgrade files. ATTENTION ! This release of ProcessLogix supports only the firmware versions listed in Table 7.A. When installing new systems or repairing existing systems, you must ensure that all modules meet the firmware version requirements listed in Table 7.A. Table 7.
7-6 Firmware Maintenance Procedures Table 7.A Hardware component firmware revision level reference for R400.0 Component Name Model Number Revision Level for R400.0 Directory File ControlNet PCI Interface card 1784-PCIC 3.5 \1784-PCIC\3_5_33 1784pcic_3_5.nvs ControlNet to Fieldbus Linking Device 1757-CN2FF 1.2 \1757-CN2FF cn2ff.nvs FOUNDATION Fieldbus Interface Module 1757-FIM PS400.0-19.3 \1757-FIM FimBoot.nvs Fimrex.nvs PROFIBUS Interface Module SST-PFBCLX 2.
Firmware Maintenance Procedures 7-7 Table 7.A Hardware component firmware revision level reference for R400.0 Component Name Model Number Revision Level for R400.0 Directory File 1756-IA8D/A 2.5 \IOM\Digital\1756-IA8D\2_5 99218804.nvs 1756-IB16D/A 2.5 \IOM\Digital\1756-IB16D\2_5 99219004.nvs 1756-OA16/A 2.3 \IOM\Digital\1756-OA16\2_3 99216503.nvs 1756-OB32/A 2.4 \IOM\Digital\1756-OB32\2_4 99207203.nvs 1756-OB16I/A (ASIC ver. 2.1) 1.7 \IOM\Digital\1756-OB16I\1_7 99205006.
7-8 Firmware Maintenance Procedures a. For ControlNet Supervisory Networks, key in this command in the Open entry field: >ntools -c -u< TIP If the RSLinx and PCIC driver services for system communications in ControlNet mode are not running, this command will start the services. b. For Ethernet Supervisory Networks, key in this command in the open entry field: >ntools -e -u< 2. Click OK to launch the Network Tools application. 3. Click OK to acknowledge the warning about monitoring through Control Builder.
Firmware Maintenance Procedures 7-9 Loading 1757-PLX52, TC-MUX021, or 1757-FIM Boot and Personality Images 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. 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.
7-10 Firmware Maintenance Procedures 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.
Firmware Maintenance Procedures 7-11 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.
7-12 Firmware Maintenance Procedures 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.
Firmware Maintenance Procedures 7-13 Updating Firmware in CNB, ENET, IOM, SRM, PIM or ControlNet Adapter ATTENTION ! Whenever you are updating modules in an RCP, we recommend you turn OFF power to one of the controller 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.
7-14 Firmware Maintenance Procedures 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.
Firmware Maintenance Procedures 7-15 3. Key in this command in the Open entry field: >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.
7-16 Firmware Maintenance Procedures 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.
Chapter 8 Supplementary Procedures Stopping ProcessLogix Applications and Services ATTENTION ! IMPORTANT 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. Use the following procedure to exit all ProcessLogix applications and stop all ProcessLogix services. 1.
8-2 Supplementary Procedures Stopping the ProcessLogix Server 2. 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.
Supplementary Procedures 8-3 3. Press Stop. 4. Click Yes to confirm stopping the SQLServerAgent service. 5. Click Yes to stop all of the dependent services. 6. Select MSSQLServer from the Services drop down list. 7. Press Stop. 8. Click Yes to confirm Stopping the MSSQLServer service. 9. Close the SQL Server Service Manager. 10. Right click the SQL Server Service Manager icon again and select Exit from the menu. This will close the application. Stop RSLinx Service 1.
8-4 Supplementary Procedures b. Wait for the message RSLinx Service is not running to appear. Close the dialog box. Stopping NI-FBUS and Excel 1. Skip to Step 5 if NI-FBUS is not running. Otherwise, close the NI-FBUS configurator. 2. Wait until the FCS shutdown window disappears before proceeding. 3. Right-click the NI-FBUS 2.3 icon in the taskbar and select Open. 4. Close the NI-FBUS window and click Yes to confirm. 5.
Supplementary Procedures 8-5 1. Click Start Programs Performance Support Tools Knowledge Builder to launch the application. 2. Once you launch Knowledge Builder, click Help for complete instructions. SQL Server SQL Server is automatically installed during the ProcessLogix R400.0 installation. SQL Status Follow these steps to check if SQL Server is running and to start it if necessary. 1. Right-click the My Computer icon and select Manage. 2. Expand the Services and Applications directory. 3.
8-6 Supplementary Procedures Replacing and Repairing Removing ProcessLogix Software Components ATTENTION ! Before installing or uninstalling any software component, you MUST exit all ProcessLogix applications and stop all ProcessLogix services. Refer to Stopping ProcessLogix Applications and Services on page 8-1. Replacing ProcessLogix R400.0 subsystems is different from prior ProcessLogix releases, previous techniques do NOT work from ProcessLogix R400.0.
Supplementary Procedures 8-7 7. Restart the PC. ATTENTION ! Before installing or uninstalling any software component, you MUST exit all ProcessLogix applications and stop all ProcessLogix services. Refer to Stopping ProcessLogix Applications and Services on page 8-1. Replacing ProcessLogix R400.0 subsystems is different from prior ProcessLogix releases, previous techniques do NOT work from ProcessLogix R400.0. These procedures do NOT support ProcessLogix R400.0 upgrades.
8-8 Supplementary Procedures Using Network Tools About Network Tools The Network Tools utility lets you access valuable operating data on your ProcessLogix hardware. It scans all the nodes on the Supervisory Network segment connected to your ProcessLogix Server. The utility features a common Windows interface with pulldown menus, toolbar buttons, and status bar. Its main window is divided into a Tree pane, a List pane, and a Detail pane.
Supplementary Procedures 8-9 Usage guidelines Observe the following usage guidelines to avoid a possible negative impact on network performance under abnormal network conditions. • Do not use Network Tools while connecting nodes to the network. • Do not use Network Tools when monitoring an analog I/O module through Control Builder. • Do not use Network Tools to monitor an analog I/O ControlNet network while the system is “on-control”.
8-10 Supplementary Procedures b. For Ethernet Supervisory Networks, key in this command in the Open Entry field: >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. With the Desktop icon selected, click Settings Settings dialog box.
Supplementary Procedures 8-11 5. Do the following in the Options tab. a. Key in >2< in entry 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.
8-12 Supplementary Procedures 9. In the Local Chassis tab, adjust the number in the scroll box to match the number of slots in your local chassis. 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.
Supplementary Procedures 8-13 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. Return to applicable install or upgrade procedure.
8-14 Supplementary Procedures Installing and Running VirusScan with ProcessLogix IMPORTANT If you need to run the Network Associates VirusScan NT application on a ProcessLogix Server, you must install and run the application as described in this section.
Supplementary Procedures 8-15 Installing VirusScan NT and Configuring Directories for Scan Exclusion Use the following procedure to install the Network Associates VirusScan NT 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 VirusScan NT software on your PC. 2. When the option to use System or Custom Account appears, select Custom Account 3. Enter your password. 4.
8-16 Supplementary Procedures Changing the Computer Name on a ProcessLogix Server All ProcessLogix Servers and Clients require unique computer names and IP addresses. If your ProcessLogix system includes multiple Servers and/or Clients, you 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-27.
Supplementary Procedures 8-17 Saving Important Data ATTENTION ! 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.
8-18 Supplementary Procedures 10. Close Control Builder. Shut Down ProcessLogix Server 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.
Supplementary Procedures 8-19 3. Press Stop. 4. Click Yes to confirm stopping the SQLServerAgent service. 5. Click Yes to stop all of the dependent services. 6. Select MSSQLServer from the Services drop down list. 7. Press Stop. 8. Click Yes to confirm stopping the MSSQLServer service. 9. Close the SQL Server Service Manager. 10. Right click the SQL Server Service Manager icon again and select Exit from the menu. This will close the application. Removal of Selected Components 1.
8-20 Supplementary Procedures ProcessLogix Update 3. Select ProcessLogix Update. 4. Click Remove. 5. Click Yes to confirm. Control Component Library 6. Select Control Component Library. 7. Click Remove. 8. Click Yes to confirm. PsAxCtl Document EXE 9. Select PsAxCtl Document EXE. 10. Click Change/Remove. 11. Click Yes to confirm. 12. At the Shared Component window, click Remove All. 13. Click OK to confirm. 14. At the Program installation removed prompt, click OK. PSc Engineering Tools 15.
Supplementary Procedures 8-21 ProcessLogix – Remove this last 21. Select ProcessLogix - Remove this last. 22. Click Change/Remove. 23. Click Yes to confirm. 24. Click OK when completed. Microsoft SQL Server 7.0 25. Select Microsoft SQL Server 7.0. 26. Click Change/Remove. 27. Click Yes to confirm. 28. At the Removed Shared File prompt, click Yes To All. 29. Click Yes to confirm. 30. When completed, click OK. 31. Click OK on the recommendation to restart the system.
8-22 Supplementary Procedures Changing the PC Name ATTENTION ! 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.
Supplementary Procedures 8-23 8. Click Yes to restart the computer. ATTENTION ! After the system is rebooted, you will receive an notcli.exe – Unable to Locate DLL prompt. This is normal at this stage and can be ignored. Click OK to close the prompt. Reinstalling Components Use the following procedure to reinstall the prior removed software components: 1. Logon to the system as ps_user. 2. Insert the ProcessLogix R400.0 Software CD 1 into the CD-ROM drive. 3. Click Start⇒Run. 4.
8-24 Supplementary Procedures Skipping Knowledge Builder and RSLinx Installation 9. Insert the ProcessLogix R400.0 Knowledge Builder CD and click Yes. 10. At the Knowledge Builder InstallShield Wizard Welcome window, click Cancel. (It is already installed.) 11. Click Yes to confirm. 12. At the Installshield Wizard Completed window, click Finish. The Knowledge Builder CD will eject. 13. Remove the Knowledge Builder CD, insert the ProcessLogix Software CD 2 and click Yes. 14.
Supplementary Procedures 8-25 Installing PsAxCtl Document EXE 23. Click OK to acknowledge the change directory warning. 24. At the PsAxCtl Document EXE Setup Welcome window, click OK. 25. Verify that the destination directory is: C:\Honeywell\TPS50\System\Bin. 26. Click the PC icon install button. 27. At the Setup complete window, click OK. Skipping ProcessLogix Server Installation 28. At the Welcome to ProcessLogix Server Setup window, click Cancel. (It is already installed on the system.) 29.
8-26 Supplementary Procedures Restoring the Data ATTENTION ! If you are using this procedure for renaming and setting redundant servers, finish setting up redundancy 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. Select Start⇒Programs⇒ProcessLogix Engineering Tools⇒ Control Builder. 3. In the Login dialog box, make these entries: a.
Supplementary Procedures Changing the Computer Name on a ProcessLogix Client 8-27 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 Server, refer to Changing the Computer Name on a ProcessLogix Server on page 8-16.
8-28 Supplementary Procedures 2. Double-click the System icon. 3. On the Network Identification tab, click Properties. 4. Key in the desired computer name in the Computer name entry field. 5. Click OK to initiate the change. 6. At the You must reboot prompt, click OK. 7. Click OK to Close the System Properties window. 8. Click Yes to restart the computer.
Supplementary Procedures 8-29 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. Close any open Control Module and/or Sequential Control Module. 3. In Monitoring tab, click the plus sign in the tree root path to the non-redundant CPM being made redundant to display the CEE folder icon. 4. Click the CEE folder icon. 5.
8-30 Supplementary Procedures 14. Select the contents (CMs, SCMs, IOMs) of the CEE folder and click Edit⇒Delete. 15. Click Delete Selected object(s) to delete the selected objects. 16. Click the CPM icon, and click Edit⇒Delete. 17. Click Delete Selected object(s) to delete the non-redundant CPM. 18. In Project tab, click the CEE folder icon. 19. Click Tools⇒Assign to call up the Controller Assignments dialog box. Confirm that the check boxes for the selection Show CMs and Show IOMs are checked. 20.
Supplementary Procedures 8-31 • Navigate in Knowledge Builder to Control Builder Components Theory⇒Controller Redundancy Functionality before upgrading to a Redundant Chassis Pair for general information about Controller redundancy and related terminology. • Navigate in Knowledge Builder to Control Hardware Installation Guide ⇒Controller Module Installation and Removal for information on installing the 1757-PLX52 module.
8-32 Supplementary Procedures 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. Navigate in Knowledge Builder to Control Building Guide⇒Control Module Creation⇒Assigning the CM and IOMs to the CEE for more information. 4. Load the primary and secondary CPMs and RMs to the Controllers.
Supplementary Procedures 8-33 5. If necessary, at the Remove Shared File prompt, click Yes to All and click Yes to confirm. 6. When completed, close the Add/Remove Programs window. Installing Service Pack 2 for Windows 2000 If you are installing Knowledge Builder on Windows 2000, refer to Installing Service Pack 2 for Windows 2000 on page 2-17. Installing Internet Explorer 5.5 SP1 Refer to Installing Internet Explorer 5.5 SP1 on page 2-19. Installing MDAC2.
8-34 Supplementary Procedures 6. Click Next to begin the installation. 7. When completed, choose the Let setup restart the system now option and click Finish. Installing Knowledge Builder 1. Insert the ProcessLogix R400.0 Knowledge Builder CD into the CD-ROM drive. 2. Key in this path location in the Open entry field or use Browse to navigate to the Setup.exe file on the CD: >D:(or your CD-ROM drive letter)\Knowledge_Builder\Setup.exe< 3. Click OK to launch the Knowledge Builder setup. 4.
Chapter 9 PC Performance for ProcessLogix Systems This section describes how to customize the Microsoft Windows 2000 series of Operating Systems to gain the best performance for ProcessLogix R400.0. The following is background information to help you make the appropriate decisions related to your system’s control configuration. Operating Systems Microsoft currently produces 4 versions of the Windows 2000 Operating System.
9-2 PC Performance for ProcessLogix Systems ProcessLogix ProcessLogix R400.0 is a set of applications that cover two phases of the Control Life Cycle: Configuration and Operation. During the Configuration Phase, Stand-alone type applications are used to configure the Control Hardware and Software for the user’s particular Process. Hardware components are defined, strategies are implemented, limits calculated, etc.
PC Performance for ProcessLogix Systems 9-3 Process Control systems are made up of multiple layers: IO, Control and Supervisory. Ethernet Network Supervisory Network High Alarm Low Alarm Comm. Err. High Alarm Low Alarm Comm. Err.
9-4 PC Performance for ProcessLogix Systems Rockwell Automation works with Dell to build PCs to specifications to meet the needs of Process Control Systems. Although based on systems available to the General Public, these systems will typically include such items as Error Correcting Memory, internal hardware sensors, management applications, and other features that differentiate them from the typical household or business PC. Once built, these systems are then brought in for evaluation and testing.
PC Performance for ProcessLogix Systems 9-5 Redundant Engineering Repository When the Redundant Server option is chosen on ProcessLogix Systems, you automatically get redundant Engineering Repositories. This is a database of Control information and configuration items which are critical in operation on these type of systems.
9-6 PC Performance for ProcessLogix Systems 3. In the Performance Section, click Performance Options. Tuning this parameter changes the overall effect of the foreground Application response. For ProcessLogix Clients the selection should be Optimize performance for Applications. ProcessLogix Server is supported only on Windows 2000 Server.
PC Performance for ProcessLogix Systems 9-7 tuned for Background Services, foreground applications receive lower priority thereby allowing the background services more. IMPORTANT During the Configuration phase of the system, running applications on the Server will be effected by this parameter setting. Therefore, this setting can be set to Applications during the configuration phase and then changed to Background Services for the Operational Phase.
9-8 PC Performance for ProcessLogix Systems • On nodes dedicated to running only the Engineering Repository (SQL), this setting should always be Maximize data throughput for network applications. Disk Management Disk performance, or the capability of the system to access and store files on the hard disk, can greatly affect the overall performance of the system.
PC Performance for ProcessLogix Systems 9-9 2. Right-click the drive you wish to check and select Properties. 3. Select Tools. 4. Click Check Now in the Error-Checking section. 5. Check the Automatically fix files system errors checkbox and click Start. Unless a prior check revealed bad sectors, do not check the Scan for and attempt recovery of bad sectors. 6. Due to file system locking the drive (NTFS), the system cannot perform this option at this time.
9-10 PC Performance for ProcessLogix Systems After the system returns to the logon prompt, you should log in and check the disk report in the System’s Event Viewer. If the report contains messages that it found bad sectors, then the operation should be re-run and the option to Scan for and attempt recovery of bad sectors should be checked. Drives which continually report bad sectors should be scheduled for replacement. It usually indicates that the drive is experiencing hardware malfunctions.
PC Performance for ProcessLogix Systems 9-11 4. Click Defragment now in the Defragmentation Section. 5. Select the drive you wish to defragment and click Analyze. This assesses the fragmentation level of the drive. If the window (above example) displays a majority red area, it means the system is fragmented. If the window displays a majority blue area, then the system is mostly contiguous. 6. If needed, choose Defragment now to run the defragmentor.
9-12 PC Performance for ProcessLogix Systems Windows 2000, have the ability to take memory space occupied by data in physical RAM and swap it into a file. This frees up the physical RAM for other processes. If the process again requires the data that was swapped out, a page fault occurs and the page is swapped back from the file into physical RAM before operation continues. This type of management is called Paging and the associated swapfile is called the page file.
PC Performance for ProcessLogix Systems 9-13 Client/Station Memory Settings Based on the Operating System and application usage, this system should not be affected by paging operations as long as the memory is at the specified amount of 128 MB. If adjustments are needed, you should follow the default rules of the Operating System suggestion: Example for a 128 MB System Initial Size: 192 MB (or default Operating System suggestion.) Maximum Size: 384 MB (or default Operating System suggestion.
9-14 PC Performance for ProcessLogix Systems Adjusting Swapfile Size on Windows 2000 Steps to change the Swapfile/Pagefile on Windows 2000 (Professional and Server): 1. Right-click the My Computer icon on the Desktop. 2. Choose Properties. 3. On the System Properties Window that appears, choose the Advanced Tab. 4. In the Performance Section, Click Performance Options. 5. In the Virtual Memory Section, click Change.
PC Performance for ProcessLogix Systems 9-15 6. After verifying the correct drive is selected in Drive Section, add the appropriate values in the Paging file size for selected drive and click Set. 7. Changing these values will require the system to be rebooted for them to take effect. As you answer OK to subsequent screens, you will be asked to restart the system. Network Optimization Few steps in the Operating System itself can optimize the Network.
9-16 PC Performance for ProcessLogix Systems Microsoft Windows 2000 uses all network cards defined in a system for communication with other systems as long as the networks are common between the initiator and target. From the example above, you can see that all 3 Ethernet Networks are common between the 2 ProcessLogix Servers. Effective management for Server to Server communication is to direct all Server to Server traffic across networks 1 and 2; thereby reserving network 3 for Control traffic only.
PC Performance for ProcessLogix Systems 9-17 – Backup Plant Information Network (If you have redundant networks.) – Supervisory Control Network (If you are doing control over Ethernet.) IMPORTANT Your network names may not be the ones used in the example provided. (These are only assigned if the system had the Installation Services option.) In this case, you will have to determine which network card is handling which task in the system before making adjustments.
9-18 PC Performance for ProcessLogix Systems • Number of Stations – – – – The Display update rate. Shared vs. local displays Chart Visualization The number of Parameters viewed (across all Stations) and their Frequency of change. • Frequency of Report Generation. • Frequency of performed maintenance; ie defragmentation of the disk. • History Collection. • Event Archiving. • Server Synchronization with File Backup. • Size of the system. (Also the size of ERDB for Process Systems.
PC Performance for ProcessLogix Systems 9-19 the Server Performance utilizing the procedures outlined in Section and adjust accordingly. Physical location of the Components During the operational phase of the system, client response will be better when the application is not run on the Server itself. For ProcessLogix Systems, if the processor on the server is being overwhelmed, you may want to change the configuration and move the ERDB to its own dedicated node.
9-20 PC Performance for ProcessLogix Systems Publication 1757-IN040B-EN-P - March 2002
Chapter 10 New Functions and Features Enhanced Foundation Fieldbus Support The second phase of Rockwell Automation’s Foundation Fieldbus support, delivers an FF physical connection mechanism that is suitable for high availability applications. The product characteristics are extended from those identified for the Linking Device, which was introduced in release 310: • Achieves full heterogeneous accommodation of FOUNDATION™ Fieldbus devices with ProcessLogix.
10-2 New Functions and Features connection costs and is designed especially for communication between automation systems and distributed peripherals. The interface of PROFIBUS DP to ProcessLogix R400.0 involves the provision of a communication path from the PROFIBUS DP network to the controller through the use of a dedicated hardware interface card. SST-PFBCLX PROFIBUS Interface Module The integration of PROFIBUS into ProcessLogix R400.
New Functions and Features 10-3 Functional Exclusions The SST-PFBCLX does not currently support the acyclic services associated with the PROFIBUS DP-V1 extension. Topology The diagram below depicts an example of the intended ProcessLogix/PROFIBUS interface in a typical hardware topology: Figure 10.
10-4 New Functions and Features • Multiple SST-PFBCLX modules can be used either on separate PROFIBUS DP networks or on the same PROFIBUS network (a multi-master configuration). • The SST-PFBCLX is accompanied by a set of SW applications from SST, which are used to configure (and monitor) the PROFIBUS network through a dedicated serial configuration port. • As pictured, you can use a dedicated PC for configuration operations, or alternatively, a ProcessLogix Station node can be used for this purpose.
New Functions and Features 10-5 All PROFIBUS blocks are housed in the PBUSIF (PROFIBUS Interface) library of the ProcessLogix database, as visible on the Library tab of Control Builder (CB). The PFBUSIF library introduces the following blocks: • PBIM block, an IOM block representing the SST-PFBCLX module. • “Generic” blocks, specifically a generic Device/Module Block and associated generic input and output channel blocks. These blocks can be configured to create an interface to most PROFIBUS DP devices.
10-6 New Functions and Features Delta Time Control A new type of control appears on the Fieldbus device and block forms allowing the user to see time presented in a proper manner. Naming Convention Change Tag names are no longer limited to starting with alpha characters only. With this release, tag names can start with numeric or alpha characters. CEE Function Blocks Four New Parameters The CEE function block displays the information related to how many CPMs and FIMs it has opened connections to.
New Functions and Features PUSH Function Block 10-7 This function block has been added to the UTILITY function block library in ProcessLogix R400.0. The PUSH function block: • provides store/push capability, • supports all data types supported by the TypeConvert function block, and • fetches the input value and stores it if the output store enable flag is true or if it is the first time change of CM or CEE state (i.e.
10-8 New Functions and Features The major use of the PUSH FB is to push the value of different data types to the output destination. The function block fetches the input when it is scheduled to run and stores the output in the same execution cycle after the type conversion. If data type conversion is not necessary, then none will be done. The figure below shows a diagram of the PUSH function block.
New Functions and Features 10-9 Table 10.2 PUSH Block Parameter Descriptions Library/Function Parameter Name Description SDENUMTEXT Provides the self-defining enumeration text IN.BOOLEAN BOOLEAN Input Value IN.UINT16 Unsigned 16-bit Integer Value IN.UINT32 Unsigned 32-bit Integer Value IN.INT8 Signed 8-bit Integer Value IN.INT16 Signed 16-bit Integer Value IN.INT32 Signed 32-bit Integer Value IN.FLOAT32 32-bit floating point Input Value IN.FLOAT64 64-bit floating point Value IN.
10-10 New Functions and Features Execution Status The status of input fetching is reflected in the Overall Execution Status (EXECSTS) parameter. EXECSTS provides information on how successful the block is in fetching the input. EXECSTS can have the following values: • OK - Successful, i.e. when input fetching and the conversion is done without any error or clamping. • CLAMPWARNING - Function completed, but with some limitation (e.g. value clamped after data conversion).
New Functions and Features Engineering Tools 10-11 Displaying Infinity and Handling for Online Changes It is now possible to use the Fieldbus values of +INF and -INF as limits for alarms, etc. Block Assignment It is now possible to assign and unassign FF function blocks. If a block is copied, for example, it is now possible to assign the copied block to a device that contains a block of the same type.
10-12 New Functions and Features • %Cxx where xx is the percentage of CPU usage (range of 00 – 99). • KpOv indicates that the keeper is powering up or off line with valid keeper information that may or may not match the network keeper. • KpOi indicates that the keeper is powering up or off line with invalid keeper information. • KpAv indicates that the keeper is the active network keeper, with valid keeper information, whose keeper signature defines the network keeper signature.
New Functions and Features 10-13 Display Builder, denoted with a “.dsp” file extension. All existing customer displays will continue to be fully functional within the new version of Station. In order to seamlessly support these displays this new release of ProcessLogix is shipped with both versions of Display Builder, so that the choice of which file format to use is completely up to the user.
10-14 New Functions and Features • Graphical customization of toolbar and menus, including text buttons on the toolbar and toolbar icons in menus. Note: due to the change in format of the menu and toolbar configuration files, menu and toolbar configuration from previous releases of ProcessLogix must be reapplied using the new user interface. Note: This version of Station does not support Operator keyboards like the IKB and USKB. This is planned for the next major release of ProcessLogix.
New Functions and Features 10-15 • Support for popup windows It is important to note that each Internet Explorer connection uses a rotary station on the server it is connected to, limiting the number of concurrent connections possible according to the number of licensed connections. The browser environment, through its very nature, also has a number of limitations when compared to Station, such as the absence of a command zone.
10-16 New Functions and Features • Multiple level undo/redo • Additional dragging options like holding shift down while dragging constrains horizontal or vertical motion • Ability to node-edit a polyline • JavaScript support • In-place text editing of text elements, similar to Microsoft PowerPoint • Improved snap-to-grid for thick lines • Ability to insert third-party ActiveX controls into a display.
New Functions and Features 10-17 Updated Displays A Point Browser has been added to the ProcessLogix displays to simplify the entering of point names onto displays like the trend displays. The Point Browser allows you to browse the points from an area of the server you are connected to and enter it into the display by clicking an Apply button. Server Scripting Scripting support has been added to the server allowing scripts to be attached to various point, server, and report related events.
10-18 New Functions and Features Quick Builder has also been enhanced to allow the creation of custom parameters attached to analog, status and accumulator points. These parameters can either be constants, variables, database references or point/parameter references. Although not enforced it is recommended that only 100 user-defined parameters be created per point.
New Functions and Features 10-19 Updated Alarm Pager Support The Alarm Pager option has been updated to support the escalation of unacknowledged alarms to another pager if the alarm has been paged and still not acknowledged after a configurable amount of time. History Archiving Manager The History Archiving Manager is a new way to manage the archiving and removal of history archives. It has been designed to replace the History Archive report.
10-20 New Functions and Features User Defined Data Formats The following scan tasks now support the creation of user defined data formats. Data formats are used to specify the format that a field value is in when read from a controller. This field value is then converted into something suitable for the server to use. Examples of standard data formats are IEEEFP and U4096.
New Functions and Features 10-21 The following compilers are no longer supported: • Microsoft Visual C++ v5.0 • Microsoft Visual Basic v5.0 • Digital Visual Fortran v5.0 Diagnostic Improvements A Diagnostic Capture Tool has been added to the ProcessLogix Server to help capture information required to diagnose problems on the Server. This tool can also be used to view the Server’s log file and Communication traces.
10-22 New Functions and Features Station, HMIWeb Display Builder, Display Builder and Quick Builder have been qualified on Windows 2000 SP2 and Windows NT 4.0 SP 6a. Windows 95, Windows 98 and Windows ME are not supported. Windows 2000 support for multiple monitors has also been qualified. This support allows more than one video card to be used in a machine. Miscellaneous • Controls are now rejected rather than clamped to the high or low limit if they are outside these limits.
New Functions and Features 10-23 • Modbus Plus PCI-85 (416NHM30030) Interface Adapter Card has been qualified for use with this release of ProcessLogix. • Analog auxiliary parameters names can now be selected from parameter drop down lists. • Systech 8-port terminal server has been qualified. • The Point Attribute report has been enhanced to support 1757-PLX52 points for determining points in alarm inhibit or manual mode.
10-24 New Functions and Features Publication 1757-IN040B-EN-P - March 2002
Chapter 11 Performance and Capacity Specifications ATTENTION ! PC Platform Requirements This chapter contains the most current platform requirements from the performance and capacity specifications for R400.0. The information in this document takes precedence over that of Knowledge Builder or any other ProcessLogix document. The performance of the PC Platform varies greatly based on the system configuration. All information should be considered before ordering or configuring a system.
11-2 Performance and Capacity Specifications Summary of R400.0 Enhancements to ProcessLogix System Capacity & Performance The following R400.0 features could affect the system capacity and performance: • Fieldbus Interface Module Support – The R400.0 ProcessLogix System supports Foundation™ Fieldbus H1 links via the 1757-FIM, Fieldbus Interface Module. • 1757-FIMs may reside in a controller chassis or in an I/O chassis.
Performance and Capacity Specifications 11-3 Clients require a Windows NT operating system to support the multiple-user configuration nodes architecture that is possible with R400.0 ProcessLogix systems. Table P.1: Supported Hardware for ProcessLogix R400.
11-4 Performance and Capacity Specifications Typical Configurations will consist of 1 non-redundant Server or a Redundant Server pair and up to 12 Stations. This type of system includes 1 or 2 Stations actively monitoring and occasional report generation. Performance An advanced configuration will consist of 1 non-redundant Server or a Redundant Server pair, and 13 to 20 Stations.
Performance and Capacity Specifications 11-5 Table 11.A Database Sizing Chart Process Configuration Operating System System Suggestion Up to 6 Controllers† Process systems with up to 600 CM/SCM/IOM/1757-FIM Systems with up to 10,000 scada points Server Typical Server More than 6 Controllers(1) Process systems with more than 600 CM/SCM/IOM/1757-FIM Systems with more than 10,000 scada points. (1) Performance Hybrid Controllers configured in a redundant mode should be counted as 1 Hybrid Controller.
11-6 Performance and Capacity Specifications ProcessLogix Server Platform Requirements Table 11.C ProcessLogix Server Platform Requirements Feature: Requirement: Processor Dual 1 GHz Pentium III or Larger RAM (Win 2000 Server) 384 MB(2) Networking 100 Mb Ethernet Video Resolution(1) 1024 x 768 65K colors Hard Drive 18.2 GB Example Hardware Dell PowerEdge 1400 (1) The Video Memory required to support this resolution varies by Video Module type, PC Bus supported, and Manufacturers Spec.
Performance and Capacity Specifications 11-7 Table 11.D 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-8 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 your normal running state. If run on a Non-Redundant Server, it is required that you have a more performance CPU configuration. (6) RSBatch includes multiple services and applications.
Performance and Capacity Specifications 11-9 User Interface Capacity and Performance Table 11.
11-10 Performance and Capacity Specifications ATTENTION ! Viewing the expanded Monitoring Tab Tree View of the same 1757-PLX52 Controller loaded with more than 500 total CMs, SCMs and IOMs from more than one CB client simultaneously, will severely affect the performance of the 1757-PLX52 Controller’s communication capability, both to the Server and Peer-to-Peer. Using multiple CB clients to load to multiple controllers simultaneously actually increases the overall load time.
Performance and Capacity Specifications 11-11 Server Redundancy Table 11.H Server redundancy specifications Server Redundancy Server Switchover Time – Default 30-40 sec Server Switchover Time – Fastest Configurable Time 10 sec On Server switchover, the 1757-PLX52 performs an event recovery. This causes the controller to report all current alarm conditions. The Server will report all current process alarms and events.
11-12 Performance and Capacity Specifications Communications Capacity and Performance System Communications Load Philosophy and Guidelines The ProcessLogix System is designed with certain patterns of communications in mind. Being aware of the intended traffic flows will help the application engineers to insure that the application realizes the highest usage from the system’s architectural capabilities. The basic concept is shown in the following hierarchical diagram.
Performance and Capacity Specifications 11-13 Figure 11.1 System Communications Architecture Operator and Applications Nodes Server Node Controller Nodes IO Nodes Device Nodes The server is the head of a “pyramid” of controllers. Each controller, in turn, is a head of a pyramid of IO chassis. Each IO chassis is in turn, a head of a pyramid of field devices nodes.
11-14 Performance and Capacity Specifications Since ProcessLogix permits almost totally generalized intercommunications paths, the two devices can be under or on: • • • • • the same H1 link, different nets of the same 1757-FIM, different nets of the same IO chassis, different IO chassis of the same controller, different controllers of the same server As the configuration moves from 1, co-residency on the same H1 link, to 2 to 3 to 4 to 5 to 6, more nodes and more networks get involved, increasing the lo
Performance and Capacity Specifications 11-15 System Communications Limits Communications limits are derived from various capacities. Common constraints are: Node Address Range Limits Arbitrarily high limits on a network reduce effective bandwidth and effect recovery time. The maximum number of nodes permitted on the Supervisory ControlNet (UMAX) is 24. This permits 10 redundant controllers, 1 redundant pair of servers, plus 2 spare nodes.
11-16 Performance and Capacity Specifications Controller Communications Note that 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.
Performance and Capacity Specifications 11-17 Table 11.J 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.
11-18 Performance and Capacity Specifications Client/Server Communication Capacity Table 11.K 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.
Performance and Capacity Specifications 11-19 Controller Redundancy ATTENTION ! The Ethernet Module cannot be used with Controller Redundancy Table 11.
11-20 Performance and Capacity Specifications I/O Specifications Table 11.N I/O Module Capacity The following applies to the Phase 2 Fieldbus integration using the 1757-FIM with controlled support for Phase 1 Fieldbus interface using the CN2FF. I/O Module and Fieldbus Capacity 50 ms CEE 5 ms CEE Maximum Number of IOMs per 1757-PLX52 (1756/1757 + 1797 FLEX Ex + 1794-FLEX I/O + CN2FFs + 3*1757-FIMs 2*SST-PFBCLX’s+ 4*TC-MUX021 FTA’s + in any combination.
Performance and Capacity Specifications 11-21 Table 11.N I/O Module Capacity The following applies to the Phase 2 Fieldbus integration using the 1757-FIM with controlled support for Phase 1 Fieldbus interface using the CN2FF. Configurable Values for FF function block Execution Periods. (Since 250 ms period is not compatible with the CM’s 200 ms period, it should only be used for control if the entire loop is resident on a Fieldbus link.
11-22 Performance and Capacity Specifications • The maximum number of SST-PFBCLX modules that can be supported by a C200 controller is 10. The modules may be distributed in one or more downlink CNI’s. (TBD) • Multi-master configurations are supported. (TBD) • Regarding the existing limits of 64 IOM connections per CPM and 24 IOM’s per downlink CNI: – The PBIM block is counted as 2 IOM’s – The various PROFIBUS device/module blocks that are associated with a given PBIM are not counted in these limits.
Performance and Capacity Specifications 11-23 Table 11.
11-24 Performance and Capacity Specifications Table 11.P 1757-FIM Performance Limits FIM Performance Limits Per FIM Per Link Per Device Burst Sustained Burst Sustained Burst Sustained H1 Link Publication Rate (parameters/second, pps) ‡ Assumes ≥50% of link schedule is usable for client-server messaging. --- 32‡ --- 16‡ --- 16‡ Client-Server Store Rate‡ (pps) [excludes publications from ProcessLogix function blocks] ‡ Assumes ≥50% of link schedule is usable for client-server messaging.
Performance and Capacity Specifications 11-25 I/O Module Sample Periods Table 11.
11-26 Performance and Capacity Specifications Table 11.R I/O ControlNet Addressing MACID Rules and Descriptions 4 Should be used by or reserved for additional Remote 1757/1756 I/O chassis 1756-CNB or 1794/1797-ACNR15 or CN2FF.
Performance and Capacity Specifications 11-27 (1) 5 ms CEE not supported on BETA-PLX52 (2) Supervisory Ethernet LAN systems only guarantee a Pull/Get Request Rate of 500 msec or greater. Faster Pull/Get rates can be co nfigured, however, data arrival at the configured rate cannot be guaranteed for rates faster than 500 msec. Table 11.T 1757-PLX52 Processing Resources 1757-PLX52 Processing Resources Definitions: PU = Processing Unit.
11-28 Performance and Capacity Specifications Table 11.V Typical IOM/CM/SCM Processing and Memory Resource Requirements Typical IOM/CM/SCM Processing and Memory Resource Requirements Total Processing Resources (PU/sec) per module are computed as = Processing Resource Consumption (PU/module execution) / Execution Period (sec/module execution).
Chapter 12 Major ProcessLogix Software Components This chapter contains the detailed information about the major ProcessLogix software components. Major ProcessLogix FTW Software Revisions 1 Component Version Example Verification Mechanism Control Builder PS400.0-19.1 1. Execute Control Builder using Start⇒Programs⇒ProcessLogix Engineering Tools⇒Control Builder. 2. Click Help⇒About. Import/Export Tool R400.0-19.1 1.
12-2 Major ProcessLogix Software Components Major ProcessLogix Server Software Revisions Component Version ProcessLogix Server R400.0 (Build 24) 1. Execute ProcessLogix Server dialog box using Start⇒Programs⇒ProcessLogix Server⇒Start-Stop ProcessLogix Server. 2. Click System Menu (Top Left Corner) ⇒About. Station R1.0 (Build 1015) 1. Execute Station using Start⇒Programs⇒ProcessLogix Server⇒Station. 2. Click Help⇒About. HMIWeb Display Builder R1.0 (Build 1015) 1.
Major ProcessLogix Software Components 12-3 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” Internet Explorer 5.5 5050.4522.1800ICSP1 1. Run Knowledge Builder (or Internet Explorer directly). 2. Click Help⇒About Internet Explorer. MS Visual C++ Run-Time DLLs 6.1.8924.0 1. Run Windows Explorer. 2. Right click \winnt\system32\dllcache\MSVCRT.
12-4 Major ProcessLogix Software Components MS-Access 3.0.0.2504 1. Run Windows Explorer. 2. Right click \Honeywell\TPS50\System\bin\mswng300.dll 3. Click Properties. 4. Version Tab. InstallShield 5.50.134.0 1. Insert the ProcessLogix R400.0 Software CD 1 into the CD-ROM drive. 2. Run Windows Explorer. 3. In the CD root, right click _Setup.dll. 4. Click Properties. 5. Version Tab. Adobe Acrobat Reader 4.05b.0127 1. Run Adobe Acrobat. 2. Click Help⇒About.
Major ProcessLogix Software Components 12-5 External, Third Party Qualified Software Components ATTENTION 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.
12-6 Major ProcessLogix Software Components PowerPoint 9.0.1381 Service Pack 1 1. 2. 3. 4. Run NT Explorer. Right click \Microsoft Office\Office\powerpoint.exe Click Properties. Version Tab. Limitations/Compatibilities: • Use on client only, Station Word 9.0.1381 Service Pack 1 1. 2. 3. 4. Run NT Explorer. Right click \Microsoft Office\Office\winword.exe Click Properties. Version Tab. Limitations/Compatibilities: • Use on client only, Station MS Visual C++ 6.0 Service Pack 3 1. Run NT Explorer.
Major ProcessLogix Software Components 12-7 Miscellaneous SCADA Component Revisions Component Version Modicon Netlib 2.1 1. Run NT Explorer. 2. Right click \winnt\system32\netlib.dll RSNetworx 3.00.00 1. Double click RSNetworx icon. 2. Click Help \ About RSNetworx. 3. Verify version information. RSLogix 5 5.00.01 1. Double click RSLogix icon. 2. Click Help \ About RSLogix. 3. Verify version information. RSLogix 5000 8.02 1. Double click RSLogix icon. 2. Click Help \ About RSLogix. 3.
12-8 Major ProcessLogix Software Components Publication 1757-IN040B-EN-P - March 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 R400.0 Installation and Upgrade Guide Cat. No. 1757-SWKIT4000 Pub. No. 1757-IN040B-EN-P Pub. Date March 2002 Part No. 957678-48 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-IN040B-EN-P - March 2002 2 Supersedes Publication 1757-IN040A-EN-P October 2001 PN 957678-48 Copyright © 2002 Rockwell Automation. All rights reserved. Printed in the U.S.A.
ProcessLogix R400.
