ProcessLogix R320.
Important User Information Because of the variety of uses for the products described in this publication, those responsible for the application and use of this control equipment 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.
European Communities (EC) Directive Compliance If this product has the CE mark it is approved for installation within the European Union and EEA regions. It has been designed and tested to meet the following directives.
Table of Contents Important User Information . . . . . . . . . . . . . . . . . . European Communities (EC) Directive Compliance EMC Directive . . . . . . . . . . . . . . . . . . . . . . . . . Low Voltage Directive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Our Assumptions About Readers . . . . . . . . . . . . . . . . . . . Starting Conditions and Assumptions . . . . . . . . . . . . . Minimum Hardware Requirements . . . . . . . . . . . . . . . . . .
Table of Contents ii Migrating the ERDB. . . . . . . . . . . . . . . . . . . . Installing the ProcessLogix Server . . . . . . . . . Setting Up User Accounts . . . . . . . . . . . . . . . Moving the RSLinx Activation File . . . . . . . . . . . . About the Activation File . . . . . . . . . . . . . . . . Determining the Current RSLinx Version . . . . Installing the Activation File. . . . . . . . . . . . . . Configuring RSLinx Drivers for ControlNet Supervisory Network. . . . . . . . . . . . . . . . . . . .
Table of Contents Things to Check after the Upgrade. . . . . . . . . . . . . . . . Creating the Secondary ERDB . . . . . . . . . . . . . . . . . . . Synchronizing ERDB on Redundant Servers . . . . . . . . . Setting Up Station on SERVERB . . . . . . . . . . . . . . . . . . Setting Up Station on SERVERA . . . . . . . . . . . . . . . . . . Synchronizing Server Databases on Redundant Servers . Synchronizing Other Files . . . . . . . . . . . . . . . . . . . . . . Reconfiguring Other RSLinx Clients . . . . . . .
Table of Contents iv Chapter 2 Upgrading Hardware Component Firmware . . . . . . . . About firmware upgrades . . . . . . . . . . . . . . . . . . . Firmware revision level reference . . . . . . . . . . . . . Important Usage Considerations . . . . . . . . . . . . . . Updating the 1784-PCIC Card Firmware . . . . . . . . . Loading 1757-PLX52 and TC-MUX021 Boot and Personality Images . . . . . . . . . . . . . . . . Updating Firmware in CNB, ENET, IOM, SRM, PIM or ControlNet Adapter. . . . . . . . . . . . . . .
Table of Contents Configuring the ControlNet Supervisory Network . . . . . Updating the 1784-PCIC Network Address . . . . . . . . . . Configuring RSLinx Drivers for Ethernet Supervisory Network . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading Hardware Component Firmware. . . . . . . . . . . . Making Post ProcessLogix Software Installation Checks for a Non-redundant Server . . . . . . . . . . . . . . . . Checking Control Builder Operation and Logging On . .
Table of Contents vi Making Post ProcessLogix Software Installation Checks for a Redundant Server Pair . . . . . . . . . . . . . . . . Synchronizing ERDB on Redundant Servers . . . . . . . . . Synchronizing Server Databases on Redundant Servers . Synchronizing Other Files . . . . . . . . . . . . . . . . . . . . . . Checking Control Builder Operation and Logging On . . Enabling the ProcessLogix OPC Server . . . . . . . . . . . . . Backing Up a ProcessLogix Server to Tape. . . . . . . . . .
Table of Contents Creating a Redundant 1757-PLX52 . . . . . . . . . . . . . Setting Up User Accounts . . . . . . . . . . . . . . . . . . . . . . Creating the plx_user Account . . . . . . . . . . . . . . . . Setting up erserver and/or mngr user accounts . . . . Setting Up User Accounts to Logon as a Service . . . Setting up mngr Account on a ProcessLogix Server to Logon as a Batch Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii 5-26 5-27 5-27 5-28 5-28 . . .
Table of Contents viii Chapter 7 PC/NT Platform Requirements . . . . . . . . . . . Server Requirements . . . . . . . . . . . . . . . . Platform System Configuration Definitions User Interface Capacity and Performance . . . Control Network . . . . . . . . . . . . . . . . . . . . . Server Redundancy. . . . . . . . . . . . . . . . . . . . Server Notifications . . . . . . . . . . . . . . . . . . . Communications Capacity and Performance . Controller Communications . . . . . . . . . . .
Preface Our Assumptions About Readers We assume that you are familiar with navigating and running applications in a Microsoft Windows NT environment. You have some experience in loading software applications on a personal computer and are somewhat familiar with ProcessLogix hardware components as well as the Control Builder application.
Preface 2 Minimum Hardware Requirements ProcessLogix Server Software must be installed on a PC that is specifically qualified. Use of any other PC variations will render the standard warranty and support agreement null and void. IMPORTANT End users purchasing ProcessLogix 1757-PLXSYSKIT are not eligible for the standard 90 day technical support, unless the software is installed by personnel trained specifically for ProcessLogix installation.
Preface Rockwell Automation Technical Support 3 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 4 Conventions Terms and Type Representations The following table summarizes the terms and type representation conventions used in this Guide. Publication 1757-IN032B-EN-P - April 2001 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.
Preface Related Documents 5 The following is a list of the printed documents that ship with a ProcessLogix system. These documents complement the Knowledge Builder online user documentation and are listed in the suggested reading order. ProcessLogix R320.0 Installation and Upgrade Guide The ProcessLogix R320.0 Installation and Upgrade Guide provides: • procedures for upgrading a system to R320.0 • procedures for updating the firmware to R320.
Preface 6 ProcessLogix Online User Documentation/Knowledge Builder ProcessLogix online user documentation is included with your ProcessLogix system in browser format through the Knowledge Builder. The same documents may also be ordered individually through Rockwell Automation in print format. Knowledge Builder provides the user with task-based documentation within the Server and Client stations and may be accessed while using any of ProcessLogix’s software programs.
Preface 7 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
Preface 8 Publication 1757-IN032B-EN-P - April 2001
Chapter 1 System Software Upgrade Procedures Preparing for a ProcessLogix Software Upgrade ATTENTION ! This section assumes that you are currently running ProcessLogix software version R300.1 or 310.0 and Service Pack 5 for Windows NT 4.0. The tasks associated with upgrading from an earlier release are beyond the scope of this document. If you are migrating a system from R300.0 or earlier, you must upgrade to R300.1 or R310.0 before proceeding with the R320.0 upgrade.
1-2 System Software Upgrade Procedures The following table summarizes some upgrade related functions that you should consider before upgrading the existing system to R320.0. Consider this: Because: New license with R320.0 ProcessLogix software • Your existing R300.1 or 310.0 license will not work with R320.0. Localization • The localization of an existing system is lost during an upgrade. • Be certain that you have the R320.0 license numbers on hand before starting the software installation.
System Software Upgrade Procedures 1-3 Saving Current Controller Data (optional) IMPORTANT If you have redundant Servers, you only need to perform this procedure on the SERVERB node. While not required, we suggest that you use this procedure to update the ERDB with the most current Controller data before the upgrade. This procedure assumes that the Control Builder (CB) application is running and communicating with 1757-PLX52 Controllers in your ProcessLogix system. 1.
1-4 System Software Upgrade Procedures TIP We recommend that you make a backup copy of your erdb_a.mdb database after you save the current controller data. The default directory location for the erdb_a.mdb database is: C:\Honeywell\TPS50\System\ER. We recommend that you create a new folder in the C: directory for this purpose and then rename the database after it is copied to the folder. For example, you could name the folder erbackup and rename the file erdb_a_bu.
System Software Upgrade Procedures 1-5 3. Take this number and multiply it by 1.5 to find your free space requirements. If the result is less than 400 MB, make the result 400 MB. Click Cancel to close the Honeywell Properties dialog box. EXAMPLE In the following example, the C:\Honeywell tree size is 458 MB. Multiplying 458 MB by 1.5 results in 687 MB. This means you would need at least 687 MB of free disk space before beginning your upgrade. 4.
1-6 System Software Upgrade Procedures What should you do if you do not meet the recommended memory requirements: If you do not meet the minimum free disk space requirement, you can try one or more of the following actions to increase your free disk space: • Compact the ERDB (Use the DbAdmin utility: Start⇒Programs⇒ProcessLogix Engineering Tools⇒ DBADMIN⇒Tools⇒Compact Database.) • Remove old error logs in directory C:\ErrorHandling, • Remove old backups you have of the ERDB.
System Software Upgrade Procedures 1-7 4. Key in this command in the Open entry field: >cmd< and click OK to open the DOS window. 5. At the DOS prompt, key in this command: >fullbkup< and press >Enter< This initiates some file copying and then the backup dialog box appears. No further interaction is needed until the backup completes. This process may take considerable time to complete, depending on the Server.
1-8 System Software Upgrade 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.
System Software Upgrade Procedures 1-9 3. Click Start⇒Programs⇒ProcessLogix Server⇒Start-Stop ProcessLogix Server to call up the ProcessLogix Server dialog box. 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. TIP 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 Unloaded option. b.
1-10 System Software Upgrade Procedures b. Wait for the message RSLinx Service is not running to appear. Close the dialog box. 5. Skip to Step 9 if NI-FBUS is not running. Otherwise, close the NI-FBUS configurator. 6. Wait until the FCS shutdown window disappears before proceeding. 7. Right-click the NI-FBUS 2.3 icon in the taskbar and select Open. 8. Close the NI-FBUS window and click Yes to confirm. 9.
System Software Upgrade Procedures 1-11 Installing Service Pack 6a for Windows NT 4.0 IMPORTANT Your system should be running Service Pack 6a. If it is not running Service Pack 6a, follow this procedure to install it. For your convenience, we have included Service Pack 6a for Windows NT 4.0 on the ProcessLogix R320.0 software CD. This is also available as a free download from the Microsoft web site (www.microsoft.com/downloads/search.asp?). Use the following procedure to install Service Pack 6a.
1-12 System Software Upgrade Procedures Installing Internet Explorer 5.01 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 1-8. For your convenience, we have included Internet Explorer 5.01 on the ProcessLogix R320.0 software CD. Use the following procedure to install Internet Explorer 5.01 on a PC with Windows NT.
System Software Upgrade Procedures 1-13 Upgrading Data Access 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 1-8. For your convenience, we have included MDAC 2.1 on the ProcessLogix R320.0 software CD. Use the following procedure to install MDAC 2.1 on the PC. 1. Insert the ProcessLogix R320.
1-14 System Software Upgrade Procedures Uninstalling ProcessLogix Knowledge Builder Software If you have a previous version of Knowledge Builder on your PC, you must first record the system path and uninstall the installed version before attempting to install the latest version. Follow the steps below to record the system path and uninstall the Knowledge Builder software.
System Software Upgrade Procedures 1-15 5. Click Yes to confirm file deletion. 6. When prompted to remove shared files, click Yes to All and click Yes to continue. 7. When the uninstall completes, click OK. You can ignore details for any items that were not removed. 8. Close the Add/Remove window. 9. Close the Control Panel. Verifying the NT System Path Value 1. Click Start⇒Settings⇒Control Panel. 2. Double-click the System icon. 3. Click the Environment tab. 4.
1-16 System Software Upgrade Procedures Installing ProcessLogix Knowledge Builder Software Knowledge Builder is the software application used to display ProcessLogix online documentation. Knowledge Builder (KB) requires several other software applications and Microsoft components to function properly. These components include: Knowledge Builder requires this component: You MUST: Service Pack 6a for Windows NT • refer to Installing Service Pack 6a for Windows NT 4.0 on page 1-11 Internet Explorer 5.
System Software Upgrade Procedures 1-17 Accept the defaults for the program and the directory path location selections. The defaults are: • Next at the Welcome window • Yes to accept license agreement • Full Install and Next 6. At the Acrobat Reader 4.05 Setup window, click Next. 7. Accept the default directory location for Acrobat and click Next. 8. Click OK at the Thank you for choosing Acrobat Reader window. 9. Select No, I will restart my computer later and click OK. 10. Remove the CD. 11.
1-18 System Software Upgrade Procedures Removing the 9904/1784-KTCX15 Card and Installing the 1784-PCIC Card Use the following procedure as a general guide to remove the 9904/1784-KTCX15 drivers for RSLinx from an R300.1 or R310.0 ProcessLogix Server. If you already have a 1784-PCIC card installed, skip this section. ATTENTION ! IMPORTANT Before continuing, you MUST exit all ProcessLogix applications and stop all ProcessLogix services.
System Software Upgrade Procedures Upgrading ProcessLogix Software on a Non-redundant Server Only IMPORTANT 1-19 If you are upgrading a redundant Server pair, refer to Upgrading ProcessLogix Software on a Redundant Server Pair on page 1-45. 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.
1-20 System Software Upgrade Procedures The following table lists the items that you MUST complete before attempting to upgrade the ProcessLogix software on a non-redundant Server pair Step Item: Refer to page: 1 Preparing for a ProcessLogix Software Upgrade 1-1 2 Stopping ProcessLogix Applications and Services 1-8 3 Installing Service Pack 6a for Windows NT 4.0 1-11 4 Installing Internet Explorer 5.
System Software Upgrade Procedures 1-21 1. If the following pre-upgrade directories exist from a previous Server migration, delete them: • C:\Honeywell\ips.preupgrade • C:\Honeywell\server.preupgrade 2. Insert the ProcessLogix R320.0 software CD into the CD-ROM drive. 3. Click Start⇒Run. 4. 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< 5. Click OK to launch the software setup application. 6.
1-22 System Software Upgrade Procedures 4. Enter the name, company to whom the RSLinx package is registered, and the RSLinx OEM serial number (located on the RSLinx box and/or Master Disk). 5. Click Next. 6. At the Select Components window, be certain that all the components are checked, including any sublevel listings. Expand the items to display the sublevels and be certain that all the components are selected. 7. Click Next. 8. Click the Upgrade the existing version option and click Next. 9.
System Software Upgrade Procedures 1-23 d. Click the large install button (PC icon). e. At the Setup complete window, click OK. Installing CCL Deployment a. At the Welcome window, click Next. b. At the CCL Deployment Installation Complete window, click Finish. 2. At the Engineering Tools Setup Complete window, click Finish. Migrating the ERDB 1. Wait while the automatic ERDB migration from R300.1 or R310.0 to R320.0 is executed. The migration activity appears in a DOS window.
1-24 System Software Upgrade Procedures 4. Skip to Step 6 if the Specify Microsoft Excel Directory window does not appear. Otherwise, click Next to accept the default directory for Microsoft Excel. ATTENTION ! We recommend that you answer No to the question: Do you want Microsoft Excel Data Exchange to be allowed to write to a ProcessLogix Server database? If you answer Yes, the write option is enabled and it is possible for anyone with access to the machine to write to the Server database. 5.
System Software Upgrade Procedures 1-25 9. At the Setup Complete window, click the No, I will restart my computer later option and click Finish. IMPORTANT If the message “Dr. Watson has been installed as default application debugger,” appears during software installation, click OK. 10. The ProcessLogix Server Update is automatically installed. At the ProcessLogix Setup Complete window, click Finish. 11. Remove the CD.
1-26 System Software Upgrade Procedures Moving the RSLinx Activation File About the Activation File Use the following procedure to move the activation file (evrsi.sys) from the RSLinx software Master Disk to the hard drive where RSLinx is to be operated. The PC cannot execute the full OEM version of the RSLinx application if the activation file is not present on its hard drive. IMPORTANT ATTENTION ! Complete Step 1 and Step 2 in the following procedure to determine your current RSLinx version.
System Software Upgrade Procedures 1-27 2. Check the application title in the title bar. • If the title is RSLinx Lite, go to Step 3. • If the title is RSLinx OEM you already have the OEM version installed and you do not have to install the activation file. – For ControlNet Supervisory Networks, skip to Configuring RSLinx Drivers for ControlNet Supervisory Network on page 1-29. – For Ethernet Supervisory Networks, skip to Configuring RSLinx Drivers for Ethernet Supervisory Network on page 1-38. 3.
1-28 System Software Upgrade Procedures 5. Confirm that the floppy drive letter A:, for example, appears in the From Drive field and the hard drive letter C:, for example, appears in the To Drive field in the dialog box. 6. Click OK to initiate the move. 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.
System Software Upgrade Procedures Configuring RSLinx Drivers for ControlNet Supervisory Network 1-29 Use the following procedure to configure the ControlNet 1784-PCIC drivers for RSLinx. IMPORTANT If you are using Ethernet for your Supervisory Network, skip to Configuring RSLinx Drivers for Ethernet Supervisory Network on page 1-38. Installing the 1784-PCIC Driver 1. Click Start⇒Programs⇒Rockwell Software⇒RSLinx⇒RSLinx to call up the Rockwell Software RSLinx window. 2.
1-30 System Software Upgrade Procedures 7. In the Configure Drivers dialog box, you should see AB_PCIC-1 listed in the Configured Drivers list with the status Running. If the AB_PCIC-1 driver status is not Running, call Rockwell Automation Technical Support. Refer to Rockwell Automation Technical Support in the Preface. 8. Click Close to close the Configure Drivers dialog box. 9. Close RSLinx.
System Software Upgrade Procedures 1-31 3. Click the + (plus) sign next to AB_PCIC-1 to expand the ControlNet tree. 4. Confirm that the 1784-PCIC Workstation icon is listed with 3.3 Q28 firmware. If the revision is at 3.3 Q28, skip to Configuring the ControlNet Supervisory Network on page 1-35, if not go to Stop All ProcessLogix Applications and Services on page 1-31. If you do not have ControlNet devices connected to the 1784-PCIC, you can verify the firmware revision using the virtual backplane.
1-32 System Software Upgrade Procedures a. Select the Service and click Startup. b. In the Startup Type field, click the Manual option and click OK. The following Services should be changed to Manual Startup: • • • • • • • ProcessLogix ProcessLogix ProcessLogix ProcessLogix ProcessLogix ProcessLogix ProcessLogix ER Replicator (redundant SERVERB node only) ER Server System Repository Control Data Access Server Server Daemon Server Database Server System 5.
System Software Upgrade Procedures 1-33 14. Click Yes to confirm flash. The card will now execute the 3.3 firmware. 15. Click OK. When the update is completed, ControlFLASH will report that the 1784-PCIC card failed to report the new revision number. Since the 3.3 firmware requires a different driver than the 1.4 card, ControlFLASH does not reset the card when the update is completed. This allows the card to continue functioning as a 1.4 card. 16.
1-34 System Software Upgrade Procedures The following Services should be changed to Automatic Startup: • • • • • • • ProcessLogix ProcessLogix ProcessLogix ProcessLogix ProcessLogix ProcessLogix ProcessLogix ER Replicator (redundant SERVERB node only) ER Server System Repository Control Data Access Server Server Daemon Server Database Server System 26. Click Start⇒Shut Down and select the shutdown the computer option. 27. Power down the PC.
System Software Upgrade Procedures 1-35 4. 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. 5. Click OK to accept the default name AB_PCIC-1 for the driver. 6. In the Configure 1784-PCIC window, enter 20 for the Network Address and click OK. 7. In the Configure Drivers dialog box, you should see AB_PCIC-1 listed in the Configured Drivers list with the status Running.
1-36 System Software Upgrade Procedures 2. Key in this command in the Open entry field: >ntools -25 -c -nl -pit -pg -u< and click OK to launch Network Tools. 3. Click OK to acknowledge the warning about monitoring through Control Builder. 4. Click Resume to initiate network scan. 5. When network nodes appear under the Desktop tree icon, click the 01 CNB icon. 6. In the graphic pane, select the Supervisory Uplink CNB and click Change ControlNet Parameters . 7. Change UMax to 24 and click OK. 8.
System Software Upgrade Procedures 1-37 2. Click Communications⇒Configure Drivers to call up the Configure Drivers dialog box. 3. Select AB_PCIC-1 in the Configured Drivers list box and click Configure. 4. In the Configure 1784-PCIC window, enter 24 for the new Network Address for the 1784-PCIC and click OK. 5. Restart the PC.
1-38 System Software Upgrade Procedures Configuring RSLinx Drivers for Ethernet Supervisory Network IMPORTANT If you are using ControlNet for your Supervisory Network, skip this section. Refer to Configuring RSLinx Drivers for ControlNet Supervisory Network on page 1-29. 1. Verify the settings of the Ethernet Network Interface card to be used to communicate with the controller.
System Software Upgrade Procedures Upgrading Hardware Component Firmware 1-39 1. Refer to Loading 1757-PLX52 and TC-MUX021 Boot and Personality Images on page 2-10 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 2-1 to check if other hardware components require upgrades.
1-40 System Software Upgrade Procedures Reconfiguring Other RSLinx Clients Other applications which utilized the deleted 9904-KTCX15 driver must be reconfigured for the 1784-PCIC driver.
System Software Upgrade Procedures 1-41 5. Download each CPM and SRM to its given Controller. 6. Download the database (contents of each CPM’s CEE) to the Controller. 7. In the Monitoring tab, activate the CEE and all of its components in a given Controller. Initiating Redundant Controller Switchover For ProcessLogix system with redundant Controllers, use the following procedure to initiate a Backup (Secondary) Controller switchover to Primary Controller in a Redundant Chassis Pair (RCP).
1-42 System Software Upgrade Procedures The chassis information listed in the Primary and Secondary data boxes. 8. Click Initiate Switchover to initiate a Primary to Secondary Controller switchover. Click Yes to acknowledge the action. 9. Verify that the chassis information in the Primary and Secondary data boxes have switched positions. The names do not change. 10. Click Synchronize Secondary and click Yes to acknowledge the action. 11.
System Software Upgrade Procedures 1-43 7. At DOS prompt, key in: >cd\Honeywell\server\run< and press . 8. Key in this command: >hscopcserv.exe /r /s< and press . 9. Key in this command: >copy d:\server-client\hci\gopc.dll “c:\Program Files\Honeywell\TPS\hci”< and press . 10. At DOS prompt, key in: >cd\Program Files\Honeywell\TPS\hci< and press . 11. Key in this command: >regsvr32 gopc.dll< and press . 12. A gopc.dll registration succeeded message appears. Click OK. 13.
1-44 System Software Upgrade Procedures 3. Key in this command in the open entry field: >rdisk /s< and click OK. 4. Click Yes to create the Repair Disk. 5. Click OK to confirm the diskette is in the floppy drive. IMPORTANT All data on the floppy disk will be erased. 6. Click OK to exit. 7. Label the Emergency Repair Disk and place the diskette in a secure area.
System Software Upgrade Procedures Upgrading ProcessLogix Software on a Redundant Server Pair ATTENTION ! IMPORTANT 1-45 Due to the changes in the communications protocol between redundant servers in this release it is not possible to synchronize a server loaded with this version of ProcessLogix with a server loaded with an earlier version of ProcessLogix (including R300.0, R300.1 and R310.0). This means that redundant servers should be upgraded to this release at the same time.
1-46 System Software Upgrade Procedures • Server/Client (Display Builder, Station, and Server) • ProcessLogix Server Upgrade All files included with the migration wizard will be included as part of the installation package for the Engineering Tools media included in the Engineering Tools directory of the ProcessLogix CD. The files that comprise this utility will be installed into the default location C:\Honeywell\TPS50\System\ER\Migrate.
System Software Upgrade Procedures IMPORTANT 1-47 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. The Secondary or SERVERB node has the Primary or erdb_a database file. The Primary or SERVERA node has the Secondary or erdb_b database file. This procedure assumes that the ERDB and Servers have been synchronized.
1-48 System Software Upgrade Procedures 8. Click Yes to accept the license agreement. IMPORTANT You must have either a 1784-PCIC or Ethernet card installed in your ProcessLogix Server to install R320.0. 9. At the Before installing window, click Yes.
System Software Upgrade Procedures 1-49 Installing RSLinx 1. At the RSLinx Welcome window, click Next. 2. Click Yes to accept the license agreement. 3. At the Verify System Files window, click Next. TIP If a Read only File Detected message appears during software installation, check the Don’t display again checkbox and click Yes to acknowledge the message. 4. Enter the name, company to whom the RSLinx package is registered, and the RSLinx OEM serial number (located on the RSLinx box and/or Master Disk).
1-50 System Software Upgrade Procedures Installing Engineering Tools 1. Engineering Tools is automatically installed. This takes a few minutes to complete. Installing PsAxCtl Document EXE a. Click OK to acknowledge the change directory warning. b. At the PsAxCtl Document EXE Setup Welcome window, click OK. c. Verify that the destination directory is C:\Honeywell\TPS50\System\Bin. d. Click the large install button (PC icon). e. At the Setup complete window, click OK. Installing CCL Deployment a.
System Software Upgrade Procedures 1-51 Installing the ProcessLogix Server 1. At the Welcome to ProcessLogix Server Setup window, click Next. 2. Click Yes in the Question box to upgrade the ProcessLogix Server to R320.0. 3. Click Yes to replace the detected versions of Display Builder, Quick Builder, and Station. 4. Skip to Step 6 if the Specify Microsoft Excel Directory window does not appear. Otherwise, click Next to accept the default directory for Microsoft Excel.
1-52 System Software Upgrade Procedures 8. 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. TIP If a Read only File Detected message appears during software installation, check the Don’t display again checkbox and click Yes to acknowledge the message. 9.
System Software Upgrade Procedures 1-53 Moving the RSLinx Activation File 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. Otherwise, the file will be corrupted and you will not be able to run RSLinx in the OEM mode.
1-54 System Software Upgrade Procedures Configuring RSLinx Drivers for ControlNet Supervisory Network Use the following procedure to configure the ControlNet 1784-PCIC drivers for RSLinx. IMPORTANT If you are using Ethernet for your Supervisory Network, do not restart SERVERA. Return to the beginning of Upgrading ProcessLogix Software on a Redundant Server Pair on page 1-45 and repeat for SERVERB.
System Software Upgrade Procedures 1-55 – For SERVERA change the default of 99 to 20 – For SERVERB change the default of 99 to 19 6. Click OK to close the dialog box and start the 1784-PCIC driver. 7. In the Configure Drivers dialog box, you should see AB_PCIC-1 listed in the Configured Drivers list with the status running. If the AB_PCIC-1 driver status is not running, call Rockwell Automation Technical Support. Refer to Rockwell Automation Technical Support in the Preface. 8.
1-56 System Software Upgrade Procedures 4. 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. 5. Click OK to accept the default name AB_PCIC-1 for the driver. 6. In the Configure 1784-PCIC(S) window, enter the following: • Serial Number(hex): This value is read from the 1784-PCIC card and does not change.
System Software Upgrade Procedures 1-57 11. Restart the PC. IMPORTANT Be certain to update the 1784-PCIC firmware for both SERVERA and SERVERB. Once you have completed these procedures for both SERVERA and SERVERB, you can continue with the next section, Configuring the ControlNet Supervisory Network.
1-58 System Software Upgrade Procedures 9. Click Yes to confirm the action. 10. Click OK. 11. Close NTOOLS. Updating the 1784-PCIC Network Address ATTENTION ! Before continuing, you MUST exit all ProcessLogix applications and stop all ProcessLogix services on the SERVERB node. Refer to Stopping ProcessLogix Applications and Services on page 1-8. 1. On SERVERB, click Start⇒Programs⇒Rockwell Software⇒RSLinx⇒RSLinx to call up the Rockwell Software RSLinx window. 2.
System Software Upgrade Procedures 1-59 8. Select AB_PCIC-1 in the Configured Drivers list box and click Configure. 9. In the Configure 1784-PCIC window, enter 24 for the new Network Address for the 1784-PCIC and click OK. 10. Restart SERVERA.
1-60 System Software Upgrade Procedures Configuring RSLinx Drivers for Ethernet Supervisory Network IMPORTANT Do not restart SERVERA. Return to the beginning of Upgrading ProcessLogix Software on a Redundant Server Pair on page 1-45 and repeat for SERVERB. Once you have completed these procedures for both SERVERA and SERVERB, you can continue with this section. IMPORTANT If you are using ControlNet for your Supervisory Network, skip this section.
System Software Upgrade Procedures Upgrading Hardware Component Firmware 1-61 1. Refer to Loading 1757-PLX52 and TC-MUX021 Boot and Personality Images on page 2-10 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 2-1 to check if other hardware components require upgrades.
1-62 System Software Upgrade Procedures Making Post ProcessLogix Things to Check after the Upgrade Software Installation The following table summarizes some items that should be checked Checks for a Redundant before you begin operating your upgraded ProcessLogix system. Server Pair Check this. Because. Station Configuration File The original station.ini file is renamed old_station.ini and is replaced by a new station.ini in the C:\WINNT directory. Any changes made to the original file (old_station.
System Software Upgrade Procedures 1-63 5. When the replica creation has completed, click Yes to start the ER Replicator service. 6. Close DbAdmin. Synchronizing ERDB on Redundant Servers Use the following procedure to synchronize the ERDB after the redundant Servers are restarted as noted in the previous section. 1. On the SERVERB node, 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.
1-64 System Software Upgrade Procedures 11. Check that the synchronization status field indication changes to “SYNCING”. It may take a few seconds before the status field changes. 12. If the status field indication changes to “SYNCERR” with a red background, and/or an error message is displayed, please call Rockwell Automation Technical Support for help in determining the cause of the synchronization problem. 13.
System Software Upgrade Procedures 1-65 d. Key in >default.stn< in the Auxiliary Setup File field. 6. Click OK to close the TCP/IP dialog box. 7. Click Save to open the Save Setup dialog box. 8. Key in >defaultb.stn< in the File name field and click Save. 9. Click Yes to replace the existing file, if applicable. 10. Click Cancel at the Unable to connect prompt, if applicable. 11. Click Station⇒Setup to call up the Station Setup dialog box. 12.
1-66 System Software Upgrade Procedures d. Key in >defaultb.stn< in the Auxiliary Setup File field. 14. Click OK to close the TCP/IP dialog box. 15. Click Save to open the Save Setup dialog box. 16. Key in >default.stn< the File name field and click Save. 17. Click Yes to replace the existing file. 18. Click Cancel at the Unable to connect prompt, if applicable.
System Software Upgrade Procedures 1-67 19. If you have redundant LANs, you must repeat Step 3 through Step 18 to set up files for the second LAN using the name or IP address of the SERVERA and SERVERB nodes specified in the Hosts file for the second LAN. EXAMPLE For example, the Secondary Server (SERVERB) name would be PLX1B1 based on a Server name of PLX1B in Step 5 and the Primary (SERVERA) name would be PLX1A1 based on a Server name of PLX1A in Step 13.
1-68 System Software Upgrade Procedures d. Key in >default.stn< in the Auxiliary Setup File field. 6. Click OK to close the TCP/IP dialog box. 7. Click Save to open the Save Setup dialog box. 8. Key in >defaultb.stn< in the File name field and click Save. 9. Click Yes to replace the existing file, if applicable. 10. Click Cancel at the Unable to connect prompt, if applicable. 11. Click Station⇒Setup to call up the Station Setup dialog box. 12.
System Software Upgrade Procedures 1-69 c. Key in >1< as the Station number. d. Key in >defaultb.stn< in the Auxiliary Setup File field. 14. Click OK to close the TCP/IP dialog box. 15. Click Save to open the Save Setup dialog box. 16. Key in >default.stn< the File name field and click Save. 17. Click Yes to replace the existing file. 18. Click Cancel at the Unable to connect prompt, if applicable.
1-70 System Software Upgrade Procedures 19. If you have redundant LANs, you must repeat Step 3 through Step 18 to set up files for the second LAN using the name or IP address of the SERVERA and SERVERB nodes specified in the Hosts file for the second LAN. EXAMPLE For example, the Secondary Server (SERVERB) name would be PLX1B1 based on a Server name of PLX1B in Step 5 and the Primary (SERVERA) name would be PLX1A1 based on a Server name of PLX1A in Step 13.
System Software Upgrade Procedures 1-71 Synchronizing Server Databases on Redundant Servers 31. Click Start⇒Programs⇒ProcessLogix Server⇒Station. 32. Click View⇒System Status⇒Server Redundancy to call up the Server redundancy display. 33. Click the Oper field in the lower right corner of the display. 34. Key in >mngr< in the open Enter password field above the display and press . 35. Click Synchronize.
1-72 System Software Upgrade Procedures Synchronizing Other Files The Primary SERVERA node automatically transfers ProcessLogix database information to the Secondary SERVERB node. This transfer includes any changes in configuration data, such as points and displays. Navigate in Knowledge Builder to Server/Client Configuration Guide⇒ Configuring and Monitoring a Redundant Server System⇒Synchronizing Other Files for more information. If you previously configured the flbkup.
System Software Upgrade Procedures Installing ProcessLogix Client Software IMPORTANT 1-73 The ProcessLogix Server(s) must be upgraded before the ProcessLogix Client upgrade is performed. Two levels of the ProcessLogix Client software installation are available: • Operator Workstation • Engineering Workstation Operator Workstation allows remote connections to the ProcessLogix Server.
1-74 System Software Upgrade Procedures Installing Service Pack 6a for Windows NT 4.0 If you are installing Operator Workstation Software on a system with Windows NT, refer to Installing Service Pack 6a for Windows NT 4.0 on page 1-11. Installing Internet Explorer 5.01 Refer to Installing Internet Explorer 5.01 on page 1-12. Upgrading Data Access Components Refer to Upgrading Data Access Components on page 1-13.
System Software Upgrade Procedures 1-75 1. Be certain that the current logon account is plx_user. TIP If you are installing Operator Workstation Software on a system with Windows NT and you do not have a plx_user account, refer to Creating the plx_user Account on page 3-12. 2. Confirm that the PC’s date and time settings are correct. 3. Insert the ProcessLogix R320.0 software CD into the CD-ROM drive. 4. Click Start⇒Run. 5.
1-76 System Software Upgrade Procedures • Station • System Shapes • Microsoft Excel Data Exchange Uncheck this selection if Microsoft Excel is not currently installed on this PC. • • • • • Network API for Windows ODBC Client Standard Displays HCI Runtime toolkit (Windows NT only) OPC Server Connect (Windows NT only) 13. Click Next to confirm the settings. 14. Click Next to accept the default directory for the Client Software. 15. If you see a Directory Already Exists window, click Yes. 16.
System Software Upgrade Procedures 1-77 • If the details are okay, click Next to begin Client setup. This takes a few minutes to complete. TIP If a Read only File Detected message appears during software installation, check the Don’t display again checkbox and click Yes to acknowledge the message. 19. Skip this step if the system does not include Excel Data Exchange. Otherwise, click Enable Macros when requested.
1-78 System Software Upgrade Procedures Configuring an Engineering Workstation ATTENTION ! This procedure assumes that you are installing software on an Engineering Workstation that can be used as a configuration node in an R320.0 ProcessLogix system. This means that the Engineering Workstation must be running on a system with Windows NT 4.0 with Service Pack 6a installed. Refer to Configuring an Operator Workstation on page 1-73 to install the Operator version of ProcessLogix Client software.
System Software Upgrade Procedures 1-79 Refer to Installing ProcessLogix Knowledge Builder Software on page 1-16. Installing ProcessLogix Engineering Workstation Software 1. Be certain that the current logon account is plx_user. TIP If you do not have a plx_user account, refer to Creating the plx_user Account on page 3-12. 2. Confirm that the PC’s date and time settings are correct. 3. Insert the ProcessLogix R320.0 software CD into the CD-ROM drive. 4. Click Start⇒Run. 5.
1-80 System Software Upgrade Procedures Installing PsAxCtl Document EXE a. Click OK to acknowledge the change directory warning. b. At the PsAxCtl Document EXE Setup Welcome window, click OK. c. Verify that the destination directory is: C:\Honeywell\TPS50\System\Bin. d. Click the large install button (PC icon). e. At the Setup Complete window, click OK. Installing CCL Deployment a. At the Welcome window, click Next. b. At the CCL Deployment Installation Complete window, click Finish. 11.
System Software Upgrade Procedures 1-81 16. At the Choose ProcessLogix Client Software window, confirm that the checkboxes for the following Client software components are checked, as appropriate for your application. TIP The recommended selections are: • Display Builder • Quick Builder • Station • Standard Displays The remaining selections are options, based on your system configuration. Click the box to check or uncheck it, or click Select All.
1-82 System Software Upgrade Procedures 20. Skip to Step 23 if the Specify Microsoft Excel Directory window doesn’t appear. Otherwise, click Next to accept the default directory for Microsoft Excel. ATTENTION ! We recommend that you answer No to the question: Do you want Microsoft Excel Data Exchange to be allowed to write to a ProcessLogix Server database? If you answer Yes, the write option is enabled and it is possible for anyone with access to the machine to write to the Server database. 21.
System Software Upgrade Procedures 1-83 24. 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. 25. At the Setup Complete window, click the No, I will restart my computer later option and click Finish. 26. The ProcessLogix Engineering Workstation Update is automatically installed.
1-84 System Software Upgrade Procedures Setting Up a ProcessLogix Client 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.
System Software Upgrade Procedures 1-85 c. Key in >2< as the Station Number for Static or key in appropriate update rates and display number for Rotary. 7. Click OK to close the TCP/IP dialog box. 8. Click Save to open the Save Setup dialog box. 9. Key in >default.stn< in the File name field and click Save. 10. Click Yes to replace the existing file. 11. Click Cancel at the Unable to connect prompt, if applicable. 12. Click Station⇒Exit. 13. Click OK to exit Station.
1-86 System Software Upgrade Procedures Setting Up a ProcessLogix Client With Redundant Servers Use the following procedure to set up the ProcessLogix Client node to access data in networked ProcessLogix redundant Server nodes. 1. On the SERVERB 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.
System Software Upgrade Procedures 1-87 8. Click OK to close the TCP/IP dialog box. 9. Click Save to open the Save Setup dialog box. 10. Key in >defaultb.stn< in the File name field and click Save. 11. Click Yes to replace the existing file, if applicable. 12. Click Cancel at the Unable to connect prompt, if applicable. 13. Click Station⇒Setup to call up the Station Setup dialog box. 14. Click the down arrow button in the Server Connection field and select Network (TCP/IP). 15.
1-88 System Software Upgrade Procedures b. Select the appropriate option, Static or Rotary. c. Key in >3< as the Station Number for Static or key in appropriate update rates and display number for Rotary. d. Key in >defaultb.stn< in the Auxiliary Setup File field. 16. Click OK to close the TCP/IP dialog box. 17. Click Save to open the Save Setup dialog box. 18. Key in >default.stn< in the File name field and click Save. 19. Click Yes to replace the existing file. 20.
System Software Upgrade Procedures 1-89 21. If you have redundant LANs, you must repeat Step 3 through Step 20 to set up files for the second LAN using the name or IP address of the SERVERA and SERVERB nodes specified in the Hosts file for the second LAN. EXAMPLE For example, the Secondary Server (SERVERB) name would be PLX1B1 based on a Server name of PLX1B in Step 7 and the Primary (SERVERA) name would be PLX1A1 based on a Server name of PLX1A in Step 15.
1-90 System Software Upgrade Procedures Publication 1757-IN032B-EN-P - April 2001
Chapter 2 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.
2-2 Firmware Maintenance Procedures Firmware revision level reference The following table lists the firmware revision levels for listed components that are current for R320.0 along with the directory locations for firmware upgrade files. ATTENTION ! This release of ProcessLogix supports only the firmware versions listed in Table 2.A. When installing new systems or repairing existing systems, you must ensure that all modules meet the firmware version requirements listed in Table 2.A. Table 2.
Firmware Maintenance Procedures Component Name Catalog Number Revision Level for R320.0 Directory File Analog I/O Modules 1756-IF6I/A 1.9 Iom\Analog\1756_Analog\1_9 99207408.nvs 1756-IF16/A 1.5 Iom\Analog\1756-IFI6\1_5 99223504.nvs 1756-IT6I/A 1.9 Iom\Analog\1756_Analog\1_9 99207408.nvs 1756-IR6I/A 1.9 Iom\Analog\1756_Analog\1_9 99207408.nvs 1756-OF6CI/A 1.9 Iom\Analog\1756_Analog\1_9 99207408.nvs 1756-OF6VI/A 1.9 Iom\Analog\1756_Analog\1_9 99207408.nvs 1756-OF8/A 1.
2-4 Firmware Maintenance Procedures Component Name Catalog Number Revision Level for R320.0 Directory File FLEX I/O ControlNet Adapter 1794-ACNR15 or 1794-ACN15 3.5 1794-ACN(R)15\3_5 99423302.nvs Pulse Input Module 1757-PIM 1.9 Iom\1757-PIM\1_9 pim.nvs PCIC ControlNet Bridge 1784-PCIC 3.3 Q28 1784-PCIC\3_3 Use separate procedure. Refer to Updating the 1784-PCIC Card Firmware on page 2-5 Ethernet TCP/IP Communications Interface 1756-ENET 1.18 Enet\1756-ENET-A 99236106.
Firmware Maintenance Procedures 2-5 Updating the 1784-PCIC Card Firmware ATTENTION ! IMPORTANT In order to perform correctly, the 1784-PCIC card MUST have the PAL part number 99640604. If the 1784-PCIC card does not have this PAL, you must return your card for the update. Contact Rockwell Automation Technical Support for more information. Refer to Rockwell Automation Technical Support in the Preface.
2-6 Firmware Maintenance Procedures 2. Click Communications⇒Configure Drivers 3. Click the Virtual Backplane (SoftLogix 58XX) 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_VBP-1 for the driver. 5. Click Close to close the Configure Drivers dialog box. 6. Click the + (plus) sign next to AB_VBP-1 to expand the Virtual Backplane tree. 7. Confirm that the 1784-PCIC icon is listed with 3.3 Q28 firmware.
Firmware Maintenance Procedures 2-7 5. Click Start⇒Shut Down and select the shutdown the computer option. 6. Power down the PC. Continue with the updating of the 1784-PCIC card firmware. 1. Turn on the PC and logon as plx_user. 2. Click Start⇒Run. 3. Key in this command in the Open entry field: >C:\Honeywell\TPS50\System\Firmware\1784-PCIC\3_3\Setup.exe.< 4. Click OK. 5. At the Welcome to ControlFLASH Setup window, click Next. 6. Click Next to accept the default location. 7.
2-8 Firmware Maintenance Procedures 16. Click OK, and then click Cancel at the Welcome to ControlFLASH Setup window. 17. Click Yes to end the configuration session. 18. Click Start⇒Programs⇒Rockwell Software⇒RSLinx⇒RSLinx to call up the Rockwell Software RSLinx window. 19. Click Communications⇒Configure Drivers to call up the Configure Drivers dialog box. 20. Click AB_PCIC-1 selection in the Configured Drivers list and click Delete. 21. Click Close to close the Configure Drivers dialog box. 22.
Firmware Maintenance Procedures 2-9 28. Turn on the PC. IMPORTANT After flashing the 1784-PCIC card, you will need to reconfigure the RSLinx driver. For a non-redundant server, refer to Re-installing the 1784-PCIC Driver on page 1-34. For a redundant server pair, refer to Re-installing the 1784-PCIC Driver on page 1-55.
2-10 Firmware Maintenance Procedures Loading 1757-PLX52 and TC-MUX021 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 or TC-MUX021 module. You must repeat these procedures for all 1757-PLX52 and TC-MUX021 modules in your system.
Firmware Maintenance Procedures 2-11 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. 4. Click Resume to initiate network scan. 5.
2-12 Firmware Maintenance Procedures Loading Boot Image 1. Click the 1757-PLX52 or TC-MUX021 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 or TC-MUX021 module. 2. Click Firmware to initiate the firmware update. 3. Click Yes to acknowledge the Warning prompt. 4.
Firmware Maintenance Procedures 2-13 the module LED display. The Status field in the lower portion of the Network Tools window tracks the load progress. 10. Click OK to acknowledge the load completion with no errors. 11. Confirm that the LED display on the 1757-PLX52 or TC-MUX021 module shows ALIV. Loading Personality Image 1. With the 1757-PLX52 or TC-MUX021 module in its ALIVE state, click the 1757-PLX52 or TC-MUX021 module in the Detail pane. 2. Click Firmware to initiate the firmware update. 3.
2-14 Firmware Maintenance Procedures 6. When the correct file appears in the list box, select it so that it appears in the File Name entry field. 7. Click Open to start the firmware load and click Yes to confirm the action. 8. Wait for the load to complete and the 1757-PLX52 or TC-MUX021 module to reboot to its NODB status as shown in the module LED display. The Status field in the lower portion of the Network Tools window tracks the load progress. 9.
Firmware Maintenance Procedures 2-15 Updating Firmware in CNB, ENET, IOM, SRM, PIM or ControlNet Adapter ATTENTION ! IMPORTANT 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.
2-16 Firmware Maintenance Procedures If you have added any new CNB modules to your network, adjust the Network Update Time (NUT) in the new modules. Refer to Setting CNB Module NUT Timing on page 2-16. Otherwise, return to upgrade or installation procedures as applicable. Setting CNB Module NUT Timing Use the procedure in the following table to adjust the NUT (Network Update Timing) timing of all the new CNB modules in your system.
Firmware Maintenance Procedures 2-17 4. Click OK to launch the Network Tools application. 5. Click OK to acknowledge the warning about monitoring through Control Builder. 6. Click Resume to initiate network scan. 7. Click any CNB icon under the Desktop tree and wait for the graphic of the chassis to appear in the Detail pane. 8. In the graphic of your chassis, click the CNB module with the Network Address selected above. TIP This may be the only module that appears in the chassis graphic at this time.
2-18 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 3 Full PC Software Installation Procedures Installing Windows NT ATTENTION ! IMPORTANT We define a “clean” PC as one that has never had ProcessLogix Software installed on it or that has had the ProcessLogix software, including the database, completely removed from it. It is equivalent to a new out-of-the-box PC or one whose hard drive has been cleaned/erased. If the Windows NT boot disks are not available to you, contact Rockwell Automation Technical Support for more information.
3-2 Full PC Software Installation Procedures • • • • Completing installation Installing Service Pack 6a Configuring virtual memory Converting to NTFS (if required) after Windows NT has been installed • Setting COM ports Use the manufacturer’s instructions to supplement information in the remaining subsections, as required. Starting the Windows NT Installation Use the following procedure to start the installation of the Windows NT 4.0 software.
Full PC Software Installation Procedures 3-3 3. Allow the operating system to query your PC for its hardware functions and display a list of Mass Storage Devices. 4. If required, press to add drivers for additional storage devices such as hard drives or CD-ROM. Follow the on-screen prompts to add these drivers. 5. When prompted, insert the Windows NT 4.0 CD into the CD-ROM drive. 6. Review and accept the license agreement. 7. Check the displayed list of partitions for Windows NT installation. 8.
3-4 Full PC Software Installation Procedures Setting Up Windows NT Use the following procedure to continue with the Windows NT installation started in the previous procedure. 1. Wait for your PC to reboot and start the Setup Wizard. 2. When prompted, insert the Windows NT 4.0 CD into the CD-ROM drive. 3. Select Custom from the setup options list and click Next. The Custom setup lets you override default settings for the SCSI adapters, CD-ROM drives, video displays, virtual memory and others, as required.
Full PC Software Installation Procedures 3-5 For example, use the name PLX1C for the first ProcessLogix Client in a redundant Server system. 7. Record the computer name for future reference and click Next. 8. On the Administrator page, key in the password for the Administrator account twice. The default password for ProcessLogix systems is “password”. 9. Record the password for future reference and click Next. 10. Click No, do not create an Emergency Repair Disk and click Next.
3-6 Full PC Software Installation Procedures 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. Select Start Search if you want Windows NT to automatically detect the card installed in your PC. If the detected card is incorrect, or no card is detected, click Select from list and select the correct network card from this list.
Full PC Software Installation Procedures 3-7 11. If you selected No in Step 10, enter TCP/IP settings in the appropriate Microsoft TCP/IP Properties tabbed pages. See Table 3.A on page 3-8. Apply changes and click OK. TIP If you leave the default setting for WINS, you are prompted to leave this blank by answering Yes. 12. Click Next to continue. 13. Click Next again to start the network. 14. Key in a network group.
3-8 Full PC Software Installation Procedures Table 3.A TCP/IP network settings Tab Setting Description IP Address IP Address Provided by network administrator, if connecting to an existing network. Otherwise, choose something like 192.168.0.X, for the on-board network card, and 192.168.1.X for an additional card, where X is a unique number for each network card (and usually each host) in the network. This number can be between 1 and 255.
Full PC Software Installation Procedures 3-9 4. Close the Date/Time Properties dialog box. 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.
3-10 Full PC Software Installation Procedures 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.
Full PC Software Installation Procedures 3-11 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.
3-12 Full PC Software Installation Procedures 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.
Full PC Software Installation Procedures Checking Required System Settings 3-13 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.
3-14 Full PC Software Installation Procedures Function Required Setting Value 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 plx_user is configured correctly. Start⇒Programs⇒Administrative Tools (Common)⇒User Manager (Double-click plx_user in the username field of the dialog box.
Full PC Software Installation Procedures Installing ProcessLogix Knowledge Builder Software Installing the 1784-PCIC Card 3-15 Refer to Installing ProcessLogix Knowledge Builder Software on page 1-16. 1. Click Start⇒Shut Down and select the shutdown the computer option. 2. Power down the PC. 3. Install the 1784-PCIC card and attach the ControlNet cables. Refer to the installation instructions, Publication 1784-IN003A-EN-P for details.
3-16 Full PC Software Installation Procedures Installing ProcessLogix Software on a Clean PC The following table lists the items that you MUST complete before attempting to install the ProcessLogix software. If you are installing ProcessLogix software on a redundant Server pair you must complete the items on both SERVERA and SERVERB. Step Item: Refer to page: 1 Installing Windows NT 3-1 2 Checking Required System Settings 3-13 3 Installing Service Pack 6a for Windows NT 4.
Full PC Software Installation Procedures 3-17 Installing Server Software Use the following procedure to install these ProcessLogix software components on a clean PC in succession. • RSLinx OEM 2.2 • Engineering Tools • Client/Server (Display Builder, Station, and Server) 1. Logon to NT as plx_user (or your default user), using the account already set up. TIP Refer to Creating the plx_user Account on page 5-27 if you need to create the plx_user account. 2. Close all running applications. 3.
3-18 Full PC Software Installation Procedures Installing RSLinx 1. At the RSLinx Welcome window, click Next. 2. Click Yes to accept the license agreement. 3. At the Verify System Files window, click Next. 4. Enter the name, company to whom the RSLinx package is registered, and the RSLinx OEM serial number (located on the RSLinx box and/or Master Disk). 5. Click Next. 6. At the Select Components window, be certain that all the components are checked, including any sublevel listings.
Full PC Software Installation Procedures 3-19 Installing Engineering Tools 1. Engineering Tools is automatically installed. This takes a few minutes to complete. Installing PsAxCtl Document EXE a. Click OK to acknowledge the change directory warning. b. At the PsAxCtl Document EXE Setup Welcome window, click OK. c. Verify that the destination directory is C:\Honeywell\TPS50\System\Bin. d. Click the large install button (PC icon). e. At the Setup complete window, click OK. Installing CCL Deployment a.
3-20 Full PC Software Installation Procedures 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.
Full PC Software Installation Procedures 3-21 b. Key in >engr123< again to confirm password and press . c. Key in >oper123< as the operator account password and press . d. Key in >oper123< again to confirm password. IMPORTANT Passwords are case sensitive. Create passwords of at least six characters and include at least one non-alphabetic character. Record the passwords and keep the record in a safe and secure place.
3-22 Full PC Software Installation Procedures 18. 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. 19. At the Setup Complete window, click the No, I will restart my computer later option and click Finish. IMPORTANT If the message “Dr.
Full PC Software Installation Procedures 3-23 Setting up User Accounts 1. Configure the plx_user, mngr, and erserver accounts. Refer to Setting Up User Accounts on page 5-27. ATTENTION ! Do not restart the Server. If you are installing ProcessLogix software on a Redundant Server pair: • Do not restart SERVERA. • Return to the beginning of Installing ProcessLogix Software on a Clean PC on page 3-16 and repeat for SERVERB.
3-24 Full PC Software Installation Procedures ATTENTION ! If you need to reformat the hard drive, you must first move the activation file back to the RSLinx Master Disk using the same general procedure as follows. Otherwise, the file will be corrupted and you will not be able to run RSLinx in the OEM mode. Before you attempt to move the activation file, you MUST exit all ProcessLogix applications and stop all ProcessLogix services. Refer to Stop All ProcessLogix Applications and Services on page 3-27.
Full PC Software Installation Procedures 3-25 Installing the 1784-PCIC Driver 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. 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. 5.
3-26 Full PC Software Installation Procedures 9. Close RSLinx. IMPORTANT Whenever the PCIC Network Address is changed, the PCIC driver must be stopped and restarted to complete the change. 10. Restart the PC. Updating the 1784-PCIC Card Firmware ATTENTION ! IMPORTANT In order to perform correctly, the 1784-PCIC card MUST have the PAL part number 99640604. If the 1784-PCIC card does not have this PAL, you must return your card for the update.
Full PC Software Installation Procedures 3-27 If the revision is at 3.3 Q28, skip to Configuring the ControlNet Supervisory Network on page 3-31, if not go to Stop All ProcessLogix Applications and Services on page 3-27. If you do not have ControlNet devices connected to the 1784-PCIC, you can verify the firmware revision using the virtual backplane. Do the following: 1. Click Start⇒Programs⇒Rockwell Software⇒RSLinx⇒RSLinx to call up the Rockwell Software RSLinx window. 2.
3-28 Full PC Software Installation Procedures • • • • • • ProcessLogix ProcessLogix ProcessLogix ProcessLogix ProcessLogix ProcessLogix ER Server System Repository Control Data Access Server Server Daemon Server Database Server System 5. Click Start⇒Shut Down and select the shutdown the computer option. 6. Power down the PC. Continue with the updating of the 1784-PCIC card firmware. 1. Turn on the PC and logon as plx_user. 2. Click Start⇒Run. 3.
Full PC Software Installation Procedures 3-29 When the update is completed, ControlFLASH will report that the 1784-PCIC card failed to report the new revision number. Since the 3.3 firmware requires a different driver than the 1.4 card, ControlFLASH does not reset the card when the update is completed. This allows the card to continue functioning as a 1.4 card. 16. Click OK, and then click Cancel at the Welcome to ControlFLASH Setup window. 17. Click Yes to end the configuration session. 18.
3-30 Full PC Software Installation Procedures 26. Click Start⇒Shut Down and select the shutdown the computer option. 27. Power down the PC. IMPORTANT If you are configuring a redundant Server pair, configure both SERVERA and SERVERB. DO NOT RESTART the Servers. Return to Configuring the ControlNet Supervisory Network on page 4-10. Re-installing the 1784-PCIC Driver 1. Turn on the PC and logon as plx_user. 2.
Full PC Software Installation Procedures 3-31 7. In the Configure Drivers dialog box, you should see AB_PCIC-1 listed in the Configured Drivers list with the status Running. If the AB_PCIC-1 driver status is not Running, call Rockwell Automation Technical Support. Refer to Rockwell Automation Technical Support in the Preface. 8. Click Close to close the Configure Drivers dialog box. 9. Close RSLinx.
3-32 Full PC Software Installation Procedures 6. In the graphic pane, select the Supervisory Uplink CNB and click Change ControlNet Parameters . 7. Change UMax to 24 and click OK. 8. Click Yes to confirm the action. 9. Click OK. 10. Close NTOOLS. Updating the 1784-PCIC Network Address ATTENTION ! Before continuing, you MUST exit all ProcessLogix applications and stop all ProcessLogix services. Refer to Stopping ProcessLogix Applications and Services on page 1-8. 1.
Full PC Software Installation Procedures Configuring RSLinx Drivers for Ethernet Supervisory Network IMPORTANT 3-33 If you are using ControlNet for your Supervisory Network, skip this section. Refer to Configuring RSLinx Drivers for ControlNet Supervisory Network on page 3-24. 1. Verify the settings of the Ethernet Network Interface card to be used to communicate with the controller.
3-34 Full PC Software Installation Procedures Upgrading Hardware Component Firmware 1. Refer to Loading 1757-PLX52 and TC-MUX021 Boot and Personality Images on page 2-10 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 2-1 to check if other hardware components require upgrades.
Full PC Software Installation Procedures 3-35 Creating the Emergency Repair Disk Refer to Creating an Emergency Repair Disk on page 3-14.
3-36 Full PC Software Installation Procedures Verifying ProcessLogix Client Installation Setting Up a ProcessLogix Client with a Non-redundant Server Refer to Setting Up a ProcessLogix Client With a Non-redundant Server on page 1-84. Setting up a ProcessLogix Client with Redundant Servers Refer to Setting Up a ProcessLogix Client With Redundant Servers on page 1-86.
Chapter 4 Additional Redundant Server Procedures Completing ProcessLogix Install on a Redundant Server Pair and Adding Redundancy to R320.0 Non-Redundant Server Systems Use the following procedures to configure a redundant server pair after ProcessLogix R320.0 software has been installed. IMPORTANT Do not restart either Server at this time. Continue with the next section. If you are adding Server redundancy to a non-redundant system, designate an existing R320.
4-2 Additional Redundant Server Procedures 2. You must enter the desired computer names and respective unique IP addresses for both Primary and Secondary Servers on a separate line for each Server and Client as shown in the display above. These names and addresses must be included in the Hosts file and resident on each Server.
Additional Redundant Server Procedures 4-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.
4-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/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.
Additional Redundant Server Procedures 4-5 Changing the Computer Name If your computer names are already designated as A and B, skip to Updating the Registry on page 4-5. Use the following procedure to change the name of your computer. 1. Click Start⇒Settings⇒Control Panel. 2. Double-click the Network icon to display the Network dialog box. 3. In the Identification tab, click Change. 4. Key in the desired computer name in the Computer Name entry field. 5. Click OK to initiate the change. 6.
4-6 Additional Redundant Server Procedures 6. Confirm that the PC name is correct and click Next. The Current and New Settings should be identical. If the name is incorrect, click Back and repeat step 3. 7. At the Restarting Windows window, select No, I will restart my computer later, and click OK.
Additional Redundant Server Procedures 4-7 Installing PsAxCtl Document EXE TIP If an Application Removal window appears, click OK. a. Click OK to acknowledge the change directory warning. b. At the PsAxCtl Document EXE Setup Welcome window, click OK. c. Verify that the destination directory is C:\Honeywell\TPS50\System\Bin. d. Click the large install button (PC icon). e. At the Setup complete window, click OK. Installing CCL Deployment a. At the Welcome window, click Next. b.
4-8 Additional Redundant Server Procedures 11. Repeat this procedure for the SERVERA node of a redundant ProcessLogix Server and/or a ProcessLogix Client node. Moving the RSLinx Activation File 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.
Additional Redundant Server Procedures 4-9 Configuring RSLinx Drivers Installing the 1784-PCIC Driver for ControlNet Supervisory If you are using Ethernet for your Supervisory Network IMPORTANT Network, restart SERVERA and SERVERB Skip to Configuring RSLinx Drivers for Ethernet Supervisory Network on page 4-12. Install the 1784-PCIC driver for SERVERA first and then repeat the process for SERVERB. 1. Click Start⇒Programs⇒Rockwell Software⇒RSLinx⇒RSLinx to call up the Rockwell Software RSLinx window. 2.
4-10 Additional Redundant Server Procedures 7. In the Configure Drivers dialog box, you should see AB_PCIC-1 listed in the Configured Drivers list with the status running. If the AB_PCIC-1 driver status is not running, call Rockwell Automation Technical Support. Refer to Rockwell Automation Technical Support in the Preface. 8. Click Close to close the Configure Drivers dialog box. 9. Close RSLinx. Updating the 1784-PCIC Card Firmware Refer to Updating the 1784-PCIC Card Firmware on page 3-26.
Additional Redundant Server Procedures 4-11 6. When network nodes appear under the Desktop tree icon, click the 01 CNB icon. 7. In the graphic pane, select the Supervisory Uplink CNB and click Change ControlNet Parameters . 8. Change UMax to 24 and click OK. 9. Click Yes to confirm the action. 10. Click OK. 11. Close NTOOLS. Updating the 1784-PCIC Network Address ATTENTION ! Before continuing, you MUST exit all ProcessLogix applications and stop all ProcessLogix services on the SERVERB node.
4-12 Additional Redundant Server Procedures 6. On SERVERA, click Start⇒Programs⇒Rockwell Software⇒RSLinx⇒RSLinx to call up the Rockwell Software RSLinx window. 7. Click Communications⇒Configure Drivers to call up the Configure Drivers dialog box. 8. Click the AB_PCIC-1 in the Configured Drivers list box and click Configure. 9. In the Configure 1784-PCIC window, enter 24 for the new Network Address for the PCIC and click OK. 10. Restart SERVERA.
Additional Redundant Server Procedures 4-13 Restarting Redundant Servers ATTENTION ! The following procedure assumes that you have completed the previous procedures in this section for both the SERVERA (Primary) and SERVERB (Secondary) nodes. Use the following procedure to restart SERVERA and then SERVERB. 1. Restart 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.
4-14 Additional Redundant Server Procedures The replicate window appears: Created Secondary ERDB Successfully at: \\severname\Hybrid\System\ER\erdb_b.mdb TIP If the File Already Exists window appears, click OK to replace it with a new replica file. 5. When the replica creation has completed, click Yes to start the ER Replicator service. 6. Close DbAdmin. Making Redundant Hardware File Entries 1.
Additional Redundant Server Procedures 4-15 a. With the Full Mode version of the dialog box active, click the Database Only option. 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.
4-16 Additional Redundant Server Procedures 10. Key in this command in the Open entry field: >cmd< and click OK to open the DOS window. 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.
Additional Redundant Server Procedures 4-17 2. Key in this command in the Open entry field: >Notepad %SystemRoot%\timeserv.ini< TIP The %SystemRoot% is the path to the timeserv.ini file, such as C:\WINNT\timeserv.ini. 3. Click OK to open the Notepad application. 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. 5. Click File⇒Save to save changes. 6.
4-18 Additional Redundant Server Procedures 13. 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 to the left of ProcessLogix in 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.
Additional Redundant Server Procedures 4-19 10. Click OK to add the items to the project. 11. Click Tools⇒Download to call up the dialog box. 12. Click the All Items option. 13. Click OK to initiate the download. 14. Click OK to acknowledge the successful download prompt and close the dialog box. 15. Click File⇒Exit to close Quick Builder.
4-20 Additional Redundant Server Procedures c. Close the ProcessLogix Server dialog box. 2. Refer to Configuring Stations in QuickBuilder on page 4-18. Setting up Station on SERVERA Refer to Setting Up Station on SERVERA on page 1-67 to be sure any ProcessLogix Clients are pointing to the correct computer name or IP address. Upgrading Hardware Component Firmware 1.
Additional Redundant Server Procedures 4-21 Refer to Synchronizing Server Databases on Redundant Servers on page 1-71. Synchronizing Other Files Refer to Synchronizing Other Files on page 1-72. Checking Control Builder Operation and Logging On 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.
4-22 Additional Redundant Server Procedures Publication 1757-IN032B-EN-P - April 2001
Chapter 5 Supplementary Procedures Launching ProcessLogix Knowledge Builder IMPORTANT To view the online documentation called Knowledge Builder, you need the Microsoft Internet Explorer version 5.01 HTML browser installed on your PC. You can call up Knowledge Builder through the Help menu in the Control Builder application. Knowledge Builder can also be accessed through the main Programs menu as follows: 1.
5-2 Supplementary Procedures Use the appropriate procedure that follows to remove a given ProcessLogix software component. If you want to remove all the components, remove them in the order shown. Uninstalling ProcessLogix Knowledge Builder Software Refer to Uninstalling ProcessLogix Knowledge Builder Software on page 1-14.
Supplementary Procedures 5-3 9. At the Choose ProcessLogix Server Components window, click Select All and click Next. 10. At the Remove Database Question window, click Yes. 11. If the database needs to be unloaded, click Yes. 12. At the Confirmation window, click Next to initiate the uninstall. This takes a few minutes to complete. 13. At the Setup Complete window, click the Yes, I want to restart my computer now option. Click Finish. 14.
5-4 Supplementary Procedures ATTENTION ! Before uninstalling the ProcessLogix update from a Client PC, you MUST uninstall all Client applications. Refer to Removing ProcessLogix Client Software on page 5-3. 1. If you have not already done so, click Start⇒Programs⇒ProcessLogix Engineering Tools⇒Uninstall ProcessLogix Update. 2. At the Uninstall ProcessLogix window, enter 1. TIP Step 3 through Step 5 apply only to ProcessLogix Servers. If you are configuring a ProcessLogix Client, skip to Step 6. 3.
Supplementary Procedures 5-5 11. When prompted to remove shared files, click Yes to All and click Yes to continue. 12. When the uninstall completes, click OK. You can ignore details for any items that were not removed. 13. Repeat Step 6 through Step 12 for: • PsAxCtl Document EXE • PlantScape CCL Deployment 1.2 14. Close the Add/Remove window. Close the Control Panel. 15. Reboot the PC to complete the uninstall process. 16.
5-6 Supplementary Procedures Removing RSLinx 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 1-8. 1. Use the RSLinx Master Disk to remove the RSLinx activation key from your hard drive using the EVMOVE function. 2. Click Start⇒Programs⇒Rockwell Software⇒RSLINX⇒Uninstall RSLINX x.x. 3. Click Yes confirm the action. 4.
Supplementary Procedures Upgrading an Engineering Database to R320.0 5-7 This procedure would be intended for users that have already migrated their system to R320.0, but have an external database that is in R300.1 or R310.0 format that they want to put onto the system in place of the existing ERDB. EXAMPLE A database may have been generated by external engineering group. If this database is in R300.1 or R310.0 format it will have to be migrated first before being put into use. To upgrade an R300.
5-8 Supplementary Procedures 8. Key in this path location in the Open entry field, or use Browse to navigate to the setup.exe file in the Migrate folder. >C:\Honeywell\TPS50\System\ER\Migrate\SETUP.EXE< 9. Click OK to begin ERDB migration. After ERDB has been migrated, you will be notified of any fatal errors that occurred during the import migration. You will have the option to reattempt the import of those ERDB components or to continue with the migration process without those components.
Supplementary Procedures 5-9 2. Use Windows NT Explorer to locate the erdb_a.mdb file in this directory: C:\Honeywell\TPS50\System\ER\clean_database 3. Select erdb_a.mdb, right-click and select Copy. 4. Select the directory C:\Honeywell\TPS50\System\ER (the parent folder). 5. Right-click in the right pane and select Paste. 6. When the copy has completed, close Explorer. 7. Click Start⇒Programs⇒ProcessLogix Server⇒Start-Stop ProcessLogix Server to call up the ProcessLogix Server dialog box.
5-10 Supplementary Procedures 11. Select File⇒Import. 12. In the Import window, verify that the directory path is C:\Honeywell\TPS50\Ixport\. This directory should contain the set of files exported during the migration process. Each function block in the exported database should have a corresponding entry in the dialog’s object list. 13. Check the Import CEE assignments checkbox. 14. Click Select All. The Point Name field will now contain the names of the blocks to be imported. 15. Click Import.
Supplementary Procedures 5-11 2. Insert the R320.0 ProcessLogix system back up tape into the PC’s tape drive. 3. Click Start⇒Programs⇒Administrative Tools⇒Backup to launch the NT Backup program to restore the system from the tape. 4. In the Backup window, the Tapes window is minimized. Maximize the Tapes window. 5. Click the checkbox for the back up tape to be used for restoring the system to select it. 6. Click Restore to call up the Restore dialog box.
5-12 Supplementary Procedures • ODBC data source - Click Start⇒Settings⇒Control Panel⇒ODBC to verify that your ODBC data source (under the system DSN tab) is set to “erdb” and the Configure path points to the ERDB location (C:\Honeywell\TPS50\System\ER\erdb_a.mdb or erdb_b.mdb.) 13. Click Start⇒Settings⇒Control Panel⇒Services and verify that all ProcessLogix services have started correctly (RSLinx, ER Server, System Repository, Control Data Access).
Supplementary Procedures 5-13 • When prompted, start the ERDB Replication service, then close DbAdmin. • If the Server is a member of a redundant Server pair, Synchronize the Server databases. This completes the restore operation.
5-14 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 5-15 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”.
5-16 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 5-17 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.
5-18 Supplementary Procedures 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.. 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. Network Address (MAC ID) of CNB in your remote chassis.
Supplementary Procedures 5-19 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.
5-20 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 5-21 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 and enter your password. 3.
5-22 Supplementary Procedures Changing the Computer Name 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. Procedure for Configuring a Non-redundant Server Changing the Computer Name Use the following procedure to change the name of your computer. 1. Click Start⇒Settings⇒Control Panel. 2.
Supplementary Procedures 5-23 Procedure for Configuring a ProcessLogix Client Changing Hosts files entries Refer to Changing Hosts File Entries on page 4-1 to be certain that the Hosts file on a ProcessLogix Client lists applicable Server names and IP addresses. Changing the Computer Name Refer to Changing the Computer Name on page 5-22 to change the computer name for the ProcessLogix Client. Be certain that each ProcessLogix Client in the network has a unique computer name.
5-24 Supplementary Procedures 2. Close any open Control Module and/or Sequential Control Module. For a system with redundant ProcessLogix Servers, be certain that the databases are synchronized and you are using the SERVERB node. Refer to Synchronizing ERDB on Redundant Servers on page 1-63. 3. In Monitoring tab, click the plus sign in the tree root path to the non-redundant 1757-PLX52 being made redundant to display the CEE folder icon. 4. Click the CEE folder icon. 5.
Supplementary Procedures 5-25 15. Click Delete Selected object(s) to delete the selected objects. 16. Click the CPM icon, and click Edit⇒Delete. 17. Click the Delete Selected object(s) button to delete the non-redundant CPM. 18. In Project tab, 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. 19. Select the CEE associated with the non-redundant CPM in the Select a CEE list box. 20.
5-26 Supplementary Procedures • RefertoControlHardwareInstallationGuide⇒RedundancyModule Installation and Removal. • Refer to Control Hardware Installation Guide ⇒Communication Module Installation and Removal. Checking firmware revision levels Refer to Upgrading Hardware Component Firmware on page 2-1 to check/upgrade 1757-PLX52, 1756-CNB, and 1757-SRM firmware. Creating a Redundant 1757-PLX52 1.
Supplementary Procedures 5-27 Setting Up User Accounts The following table lists the details needed to set up user accounts on a system with Windows NT. Table 5.
5-28 Supplementary Procedures Setting up erserver and/or mngr user accounts IMPORTANT When setting up the eserver and mngr accounts, be certain that your current NT logon is through an administrator account, such as plx_user, but not Administrator and not an engr or mngr account. 1. Close all running applications. 2. Click Start⇒Programs⇒Administrative Tools (Common)⇒User Manager. 3. Select erserver or mngr users from the Username list.
Supplementary Procedures 5-29 3. Click Policies=>User Rights. 4. Check the Show Advanced User Rights checkbox. 5. Select Log on as a service in the Rights list. 6. If all the necessary users are in the Grant To list, go to Step 10. If any of the necessary users are not in the Grant To list, go to Step 7. 7. Click Add. 8. Verify your computer name is in the List Names From list and click Show Users. 9. Select each necessary user account in the Names list and click Add. 10.
5-30 Supplementary Procedures 7. Click Add. 8. Verify your computer name is in the List Names From list and click Show Users. 9. Select mngr in the Names list and click Add. 10. Click Ok to close the Add Users and Groups dialog box. 11. Click Ok to close the User Rights Policy dialog box. 12. Close User Manager.
Chapter 6 New Functions and Features ProcessLogix System Ethernet Supervisory Network A 10 megabit Ethernet module is being added to the system for use as the Supervisory Network between the ProcessLogix Server and 1757-PLX52 Controllers. This feature requires an Ethernet module (1756-ENET/A) to be placed in the Controller chassis.
6-2 New Functions and Features Controller & I/O Expanded ControlNet Interoperability This release includes enhanced communications to non-ProcessLogix ControlNet-based devices. Full peer-to-peer in both requestor and responder modes has been implemented for Rockwell’s ControlLogix, PLC5 and SLC500 PLC’s as well as Rockwell’s family of PanelView devices. 1794 FLEX I/O Several new 1794 FLEX I/O modules are being introduced with this release of ProcessLogix.
New Functions and Features 6-3 Common SCM’s Provides for one SCM to run against up to 100 equipment units. The parameters for these units will be contained in a spreadsheet configured in Control Builder. Binding to the specific equipment unit is at run time and can be changed by the SCM. A common SCM is not assigned at build time to a specific batch unit, but is assigned to a unit at run-time.
6-4 New Functions and Features and memory capacity, this card allows for Increased System Scalability mentioned above. ATTENTION ! Existing ProcessLogix systems must upgrade from the 9904-KTCX15 card to the new 1784-PCIC card when migrating to the R320.0 Release, even if additional controllers are not required. The 9904-KTCX15 card will no longer be offered as part of ProcessLogix new system orders for Release R320.0 and beyond.
New Functions and Features Control Builder 6-5 Chart Visualization Sequential Control Modules can be embedded in ProcessLogix Station Displays. This can be done without Control Builder running on the Station computer. Printing Enhancements These enhancements allow users to determine how pages are partitioned when printing Control Builder configurations. The default is one chart per printed page.
6-6 New Functions and Features Engineering Tools Network Diagnostic Manager The Network Diagnostic Manager (NDM) has been modified to run on both the primary and the backup server. On the primary server, NDM does everything that it did previously. On the backup server, NDM now monitors the health of RSLinx and the PCIC (without generating notifications).
New Functions and Features 6-7 Interrupt Usage Note ATTENTION ! Before Migration to R320.0, first verify your PC’s Interrupt usage. PCIC Control Net Cards require a PC Interrupt for use. You must have at least 1 free interrupt before installing the PCIC board; otherwise you will not be able to use the board. TIP The interrupt must fall between 8 and 15. Once defined, the board may share an interrupt with another device. There are only 15 Interrupts used on the PC architecture for devices.
6-8 New Functions and Features Table 6.B Interrupt Usage Table: 13 EtherLink board on some configurations or Stallion Board on some systems. 14 ATAPI, Primary IDE interface, used on some systems. 15 ATAPI, Secondary IDE interface, used on some systems. 1. Run the Windows NT Diagnostics program. Select Start⇒Programs⇒Administrative Tools (common) ⇒Windows NT Diagnostics. 2. Choose the Resources Tab, and click the IRQ button.
New Functions and Features 6-9 terms of screen update performance although Station performance can be maintained if the Server is running with enough CPU and RAM to support the configuration. Refer to Platform System Configuration Definitions on page 7-2 for details and recommendations for configuring large systems. FSC (Fail Safe Controller) Ethernet This feature duplicates the current functionality of the FSC interface using Ethernet connections. After you install ProcessLogix R320.
6-10 New Functions and Features New Quick Builder Quick Builder v1.13 has been included with this release of ProcessLogix. This version of Quick Builder includes an updated user interface that provides easier navigation, sorting and filtering of items. Items can now be sorted by any of their properties, and the filtering mechanism has been enhanced to allow a more natural entry of filter criteria as well as some predefined criteria (for example, show all status points). Figure 6.
New Functions and Features 6-11 Bristol Babcock OpenBSI Interface ProcessLogix has been enhanced in this release to include a Bristol Babcock OpenBSI interface. The interface allows communication with network connected RTU’s via TCP/IP. The Bristol Babcock OpenBSI Interface requires OpenBSI v3.2 software to be installed on the ProcessLogix Server. ProcessLogix requires updated versions of bsi32.dll and bslpdrv.exe to those delivered with OpenBSI v3.2.
6-12 New Functions and Features Modbus Plus SA85 Adapter Selectable for a Channel Previous releases of SCAN 3000 and ProcessLogix supported the following Modbus Plus architectures only. • Single channel communicating via a single SA85 (non-redundant media) or SA85-002 (redundant media) Adapter • Redundant channel communicating via two SA85 Adapters Throughput was limited to that supported by a single SA85 Adapter.
New Functions and Features 6-13 Figure 6.4 Detailed Adapter Configuration Quick Builder Configuration Modbus Plus channel configuration in Quick Builder has changed. The Adapter number can now be optionally specified in the Port Name field (instead of leaving this field blank). • Board0 corresponds to Adapter 0 (Device 0) • Board1 corresponds to Adapter 1 (Device 1) • Board2 corresponds to Adapter 2 (Device 2) • If Port Name is blank then Adapter 0 is assumed for a non-redundant channel.
6-14 New Functions and Features Figure 6.5 Quick Builder channel configuration to use Adapter 1 Support for Siemens S5 TF Driver v5.2 The Siemens TF Driver v5.2 has been qualified for use with this release of ProcessLogix. All ProcessLogix Siemens S5 Interface customers must upgrade to this version of the Siemens TF Driver before upgrading to this release of ProcessLogix.
New Functions and Features 6-15 Support for Redundant PLC-5 Controllers on ControlNet The Allen-Bradley Interface now supports redundant PLC-5 controllers connected via ControlNet as shown in the following diagram: Redundant PLC Pair Server RSLinx PCIC PLC-5 PLC-5 ControlNet Figure 6.6 PLC5 ControlNet Diagram Connection Setup Refer to the Allen-Bradley ControlNet PLC-5 Hot Backup System User Manual (Publication 1785-6.5.
6-16 New Functions and Features Allen-Bradley channel for Redundant Controller support. Select the Channel tab and add a Generic channel as shown in the following figure. Figure 6.
New Functions and Features rate 6-17 is the rate at which the PlantScape Allen-Bradley Interface will check for the primary status of the PLC Quick Builder is also used for defining and configuring the controllers. This is done using the same project that contains the channel definitions. Select the Controller Tab and add a Generic controller as shown in the following figure. Figure 6.
6-18 New Functions and Features In the Channel Name field select the channel defined earlier.
New Functions and Features 6-19 Alarm Pager support for UCP Protocols The Alarm Pager now supports UCP Protocols (commonly used in Europe). The protocols supported are: • UCP 01 • UCP 30 • UCP 51 Optional Failover of Redundant Servers On Process Controller Communications Subsystem Failure The ProcessLogix Server has been enhanced in this release to optionally failover redundant servers on Process Controller communications subsystem failure.
6-20 New Functions and Features The following will not cause a failover if the ProcessLogix servers are synchronized: • The CNet cable is disconnected. • A PLX52 controller is disconnected or fails. Station Object Model Extensions The Station Object Model has been enhanced in Station R320.2 to include new events OnConnect and OnDisconnect. These provide a way of receiving notification when Station connects (or disconnects) to a server.
New Functions and Features 6-21 New Features The following features have been added to the RSLinx 2.2, SP1 release: ControlLogix unsolicitied CIP Msg support 1784-PCIC driver ControlLogix predefined items Data monitor Bridge ControlLogix • You can send native tag information as part of an unsolicited message instruction. Data types supported include INT, SINT, DINT, and BOOL. • This driver is provided to support the 1784-PCIC ControlNet Communications card.
6-22 New Functions and Features • Further optimization of tag arrays is provided in this release to allow up to 243 SINTs or 121 DINTs in a single optimized packet as compared to 121 SINTs or 81 DINTs when using non-arrayed tags. • Also provided is further optimization of boolean tag arrays. An individual boolean tag is represented as a 32 bit word in the controller, however a boolean tag array is stored as a bit array. With this release, you can read a boolean array of up to 3872 items.
New Functions and Features Option to hide Linx Gateways 1784-PCC Auto-addressing DDE/OPC performance improvements New online help New PIC driver for Win9x 6-23 • Several customers have requested the ability to not show the Linx Gateway driver in RSWho because it creates confusion. With this release, a configuration option to disable this node from appearing in RSWho is provided. • This driver now includes an option for auto-addressing.
6-24 New Functions and Features Publication 1757-IN032B-EN-P - April 2001
Chapter 7 Performance and Capacity Specifications ATTENTION ! PC/NT Platform Requirements This chapter contains the most the current platform requirements from the performance and capacity specifications for R320.0. If any discrepancies are found between the information in this chapter and that of Knowledge Builder or any other ProcessLogix document, this document takes precedence. The performance of the NT Platform varies greatly based on the system configuration.
7-2 Performance and Capacity Specifications Please refer to the table below to review the hardware requirements for a new R320.0 ProcessLogix server or client system. ProcessLogix Clients require a Windows NT operating system to support the multiple-user configuration nodes architecture that is possible with R320.0 ProcessLogix systems. Table 7.
Performance and Capacity Specifications 7-3 Large System (Windows NT Server as the operating system) A large configuration may consist of a Redundant Server pair and up to 20 stations. These systems typically include active monitoring from multiple Stations with or without multiple locations and random report generation. Database Size in relation to System Configurations The number of physical Servers and Stations does not alone determine system configuration.
7-4 Performance and Capacity Specifications Table 7.C Minimum Platform Requirements Minimum Platform Requirements based on System Configurations Server Station System Configuration Small Medium Large Small Medium Large Processor 400 MHz Pentium II 550 MHz Pentium III 800 MHz Pentium III or Larger 200 MHz Pentium Pro 300 – 400 MHz Pentium II 550 MHz Pentium III or Larger • Win 95/98 -- -- -- 64 MB 64 MB 96 MB • Win NT 4.
Performance and Capacity Specifications 7-5 Table 7.E High Performance Platform Requirements High Performance Platform Requirements based on System Configurations Server Station System Configuration Small Medium Large Small Medium Large Processor 400 MHz Pentium II 550 MHz Pentium III 800 MHz Pentium III or Larger *Note 10 266 MHz Pentium II 300 – 400 MHz Pentium II 550 MHz Pentium III or Larger • Win 95/98 -- -- -- 64 MB 64 MB 96 MB • Win NT 4.
7-6 Performance and Capacity Specifications Table 7.F Application RAM Usage Application RAM Usage NT 4.
Performance and Capacity Specifications 4. 5. 6. 7. 8. 9. 10. 7-7 be on the Servers. On Redundant Systems, primary application usage should be on the Backup Server. These applications are more for configuration and typically are not run all the time. They represent a one-time memory allocation when running. When considering additional RAM requirements, you should only include those applications in which you intend to run on a daily or constant basis.
7-8 Performance and Capacity Specifications ATTENTION ! Users of large systems should consider upgrading to higher performing server based platforms than noted here. When making your selection, make sure it is Certified for NT Server or Windows 2000 Server use. Systems, which use NT Server, can benefit from some performance tweaks made to the operating system. These changes affect application usage on the Server node and thereby should only be made when system is dedicated for Server use.
Performance and Capacity Specifications 7-9 User Interface Capacity and Performance Table 7.G Operational display update rates Maximum Continuous Display Update Rate 1 sec Typical Field Change to Display Update Time with 100 Parameters < 2 sec Per Display on a Single Station/Server (Server configured for 1 sec update) Typical Display Call Up Time with 100 Parameters on a Single Station/Server (Call up time is dependent on display complexity; this excludes the first initial call up.
7-10 Performance and Capacity Specifications Control Network Table 7.I Process Control Network Specifications Supervisory Process Control Network Network Media Ethernet ControlNet Supervisory Networks per ProcessLogix Server - 1 1784-PCIC Card per NT Mixed Supervisory ControlNet & Ethernet on the same Server is not supported.
Performance and Capacity Specifications Communications Capacity and Performance 7-11 Controller Communications Table 7.L 1757-PLX52 Controller Communications Performance 1757-PLX52 Controller Communications Performance PPS = Average Parameters per Second Overall Communications Performance per ProcessLogix Server 50 ms CEE 5 ms CEE Maximum Total Parameter Access Response Rate to the Server from all Controllers combined.
7-12 Performance and Capacity Specifications Table 7.L 1757-PLX52 Controller Communications Performance Maximum Target Node Response Rate to Push/Store Requests from all initiator node: 50 PPS 50 PPS • For Ethernet Supervisory LAN systems, the maximum store rate is 500 msec. *Currently the SCM Step is the only block type that can initiate peer push/store requests for peer communications.
Performance and Capacity Specifications 7-13 Controller Notifications Table 7.O Controller Notifications Performance 1757-PLX52 Controller Notifications Performance (50 ms and 5 ms CEE) Maximum number of events (burst condition) 50 events Maximum number of event/second (sustained) 2/sec • Up to a minute between event bursts Controller Redundancy ATTENTION ! The Ethernet Module cannot be used with Controller Redundancy Table 7.
7-14 Performance and Capacity Specifications I/O Specifications Table 7.Q I/O Module Capacity 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 in any combination, exceptions noted below.
Performance and Capacity Specifications ATTENTION ! 7-15 Avoid operator-induced redundant controller switchovers with I/O that is configured but not physically present. In a redundant controller, the new primary 1757-PLX52 infrequently may become mute or hard fault under stress test conditions involving both {1} a non-trivial number of repetitive switchovers and {2} I/O configured in the controller that is not physically present.
7-16 Performance and Capacity Specifications I/O Network Configuration Rules Table 7.T I/O ControlNet Addressing I/O ControlNet Addressing MACID Rules and Descriptions 1 (ControlNet Keeper) 1) Must be configured on every physical I/O ControlNet segment. 2) Must be assigned to the Downlink 1756-CNB in the Controller chassis or to both Primary and Secondary Downlink CNBs in a Redundant Chassis Pair (RCP) for each physically separate I/O ControlNet segment.
Performance and Capacity Specifications 7-17 1757-PLX52 Resources Table 7.
7-18 Performance and Capacity Specifications Table 7.W 1757-PLX52 Memory Resources and Block Configuration 1757-PLX52 Memory Resources and Block Configuration Definition: MU = Memory Unit = 1 Kbyte = 1024 bytes Maximum Available 1757-PLX52 Memory Resources 4000 MU Maximum Total Number of CMs, SCMs and IOMs Configurable per 1757-PLX52 1000 Maximum Number of Component Blocks per CM 40 Maximum Total Number of Steps and Transitions (in all handlers) per SCM 160 (80 Step/Transition pairs) Table 7.
Performance and Capacity Specifications 7-19 Table 7.X Typical IOM/CM/SCM Processing and Memory Resource Requirements Sequence Control Module with an alias table of size 45 rows by 100 columns(2) 2.0 3.0 150 Sequence Control Module with an alias table of size 500 rows by 9 columns(3) 2.0 3.
7-20 Performance and Capacity Specifications Engineering Tools Resources Table 7.Y Engineering Repository Configuration Engineering Repository (ER) Database Configuration Recommended Maximum Size of ER Database (Compacted) Publication 1757-IN032B-EN-P - April 2001 1 Gbyte TIP Large database operations (load controller, delete controller, upload controller, update controller, etc.) on a 1757-PLX52 loaded with more than 500 total CMs, SCMs and IOMs will fragment the ER database.
Chapter 8 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 PS320.0-20.1 1. Execute Control Builder using Start⇒Programs⇒ProcessLogix Engineering Tools⇒Control Builder. 2. Click Help⇒About. DBADMIN PS320.0-20.1 1. Execute DBADMIN using Start⇒Programs⇒ProcessLogix Engineering Tools⇒DBADMIN. 2.
8-2 Major ProcessLogix Software Components Major ProcessLogix Server Software Revisions Component Version ProcessLogix Server R320.0 (Build 300.4-4.12) 1. Execute ProcessLogix Server dialog box using Start⇒Programs⇒ProcessLogix Server⇒Start-Stop ProcessLogix Server. 2. Click System Menu (Top Left Corner) ⇒About. Station R320.2 (Build 011) 1. Execute Station using Start⇒Programs⇒ProcessLogix Server⇒Station. 2. Click Help⇒About. Display Builder Release 320.2 (Build 11) for R300 Server 1.
Major ProcessLogix Software Components 8-3 Embedded Software Components Component Version Example Verification Mechanism Windows NT Service Pack 6A 6A 4.00.1381 1. At command prompt enter WINVER. 2. The response should include “Revised Service Pack 6a” Windows 95 Service Release 2 4.00.950B 1. Right click My Computer. 2. Click Properties. 3. General Tab. Limitations/Compatibilities: • Station, Display Builder, and QuickBuilder only Windows 98 1. Right click My Computer. 2. Click Properties. 3.
8-4 Major ProcessLogix Software Components Publication 1757-IN032B-EN-P - April 2001 1784-PCIC Device Driver 1.0.20 1. Run NT Explorer. 2. Right click \winnt\system32\drivers\ABPCIC.sys. 3. Click Properties. 4. Version Tab. 1784-PCIC(S) Device Driver 3.0.5 1. Run NT Explorer. 2. Right click \winnt\system32\drivers\ABPCICS.sys. 3. Click Properties. 4. Version Tab. MS-ODBC 3.510.4202.0 1. 2. 3. 4. Run NT Explorer. Right click \winnt\system32\odbc32.dll Click Properties. Version Tab.
Major ProcessLogix Software Components 8-5 External, Third Party Qualified Software Components ATTENTION ! WARNING ! This section identifies third party Windows-based software applications that are supported on a ProcessLogix Station Client. Special care must be exercised when using any of these third party packages. The user assumes all responsibility for issues resulting from the installation and operation of any components that have not been tested as compatible by Rockwell Automation.
8-6 Major ProcessLogix Software Components Photo Editor 3.0 1. Execute application. 2. Click Help⇒Αbout. Limitations/Compatibilities: • Use on client only, Station 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.
Major ProcessLogix Software Components 8-7 Miscellaneous SCADA Component Revisions Component Version Modicon Netlib 2.1 1. Run NT Explorer. 2. Right click \winnt\system32\netlib.dll RSLinx 2.2 OEM 2.20.01 Build 119 1. Double click RSLinx icon. 2. Click Help \ About RSLinx. 3. Verify version information. RSNetworx 2.25.12 1. Double click RSNetworx icon. 2. Click Help \ About RSNetworx. 3. Verify version information. RSLogix 5 4.10 1. Double click RSLogix icon. 2. Click Help \ About RSLogix. 3.
8-8 Major ProcessLogix Software Components Publication 1757-IN032B-EN-P - April 2001
Allen-Bradley Publication Problem Report If you find a problem with our documentation, please complete and return this form. Pub. Title/Type ProcessLogix R320.0 Installation and Upgrade Guide Cat. No. 1757-SWKIT3200 Check Problem(s) Type: Pub. No. 1757-IN032B-EN-P Pub. Date April 2001 Part No.
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.
Back Cover
Publication 1757-IN032B-EN-P - April 2001 2 Supersedes Publication 1757-IN032A-EN-P - November 2000 PN 957536-31 © 2001 Rockwell International Corporation. Printed in the U.S.A.
ProcessLogix R320.
