ProcessLogix R500.1 Selection Guide

Important User Information Because of the variety of uses for the products described in this publication, 

those responsible for the application and use of these products must satisfy 

themselves that all necessary steps have been taken to assure that each 

application and use meets all performance and safety requirements, including 

any applicable laws, regulations, codes and standards. In no event will 

Allen-Bradley be responsible or liable for indirect or consequential damage 

resulting from the use or application of these products.

Any illustrations, charts, sample programs, and layout examples shown in this 

publication are intended solely for purposes of example. Since there are many 

variables and requirements associated with any particular installation, 

Allen-Bradley does not assume responsibility or liability (to include intellectual 

property liability) for actual use based upon the examples shown in this 

publication.

Allen-Bradley publication SGI-1.1, Safety Guidelines for the Application, Installation 

and Maintenance of Solid-State Control (available from your local Allen-Bradley 

office), describes some important differences between solid-state equipment 

and electromechanical devices that should be taken into consideration when 

applying products such as those described in this publication.

Reproduction of the contents of this copyrighted publication, in whole or part, 

without written permission of Rockwell Automation, is prohibited.

Throughout this publication, notes may be used to make you aware of safety 

considerations. The following annotations and their accompanying statements 

help you to identify a potential hazard, avoid a potential hazard, and recognize 

the consequences of a potential hazard:

Allen-Bradley is a trademark of Rockwell Automation

ATTENTION

!

Identifies information about practices or circumstances 

that can lead to personal injury or death, property damage, 

or economic loss.

IMPORTANT Identifies information that is critical for successful 

application and understanding of the product.

Minimum Hardware 

Requirements

ProcessLogix R500.1 Server Software must be installed on a PC that is 

specifically qualified. Use of any other PC variations will render the standard 

warranty and support agreement null and void.

There are two methods of obtaining the qualified ProcessLogix Server:

1. Purchase the Server from Rockwell Automation.

2. Contact Rockwell Automation Technical Support for further 

information on ordering specifically qualified hardware.

Contents of the 

ProcessLogix R500.1 

Release

The following software and documentation components are included in the 

ProcessLogix R500.1 Software/documentation kit (1757-SWKIT5000).

Table P.1 ProcessLogix R500.1 Release Components

Release Components Pub/Part Number

ProcessLogix R500.1 Base Software CD

• SQL Server 2000

957678-70

ProcessLogix R500.1 Application Software CD

• ProcessLogix Engineering Tools

• ProcessLogix Server Software

• RSLinx 2.31

957678-71

ProcessLogix R500.1 Supplemental Software CD 957707-19

ProcessLogix Knowledge Builder CD 957678-69

ProcessLogix R500.1 Selection Guide 957689-94

Our Assumptions About 

Users When Installing 

ProcessLogix R500.1

Before configuring a ProcessLogix system you must:

• Be familiar with navigating and running applications in a Microsoft 

Windows 2000 environment.

• Have some experience in loading software applications on a personal 

computer (PC).

• Be familiar with ProcessLogix hardware components.

• Be familiar with ControlNet or ENET configuration.

• Be trained on ProcessLogix, including Control Builder and Server 

components.

• If applicable to your system, you must also have appropriate training on 

other Rockwell Automation products applicable to ControlLogix, 

RSNetworx, and DeviceNet.

Starting Conditions and Assumptions for Installing ProcessLogix 

R500.1

You have the following items on hand:

• ProcessLogix R500.1 Base Software CD containing software such as 

SQL.

• ProcessLogix R500.1 Application Software CD containing ProcessLogix 

applications software.

• ProcessLogix R500.1 Knowledge Builder CD containing the latest 

version of the online documentation.

• Microsoft Windows Operating System(s) CD(s).

• RSLinx OEM Master (Activation) Disk.

IMPORTANT If you have not received ProcessLogix R500.1 training, we 

recommend that you find someone who does have 

experience to assist you in loading the ProcessLogix 

software and making hardware and firmware changes in 

associated ProcessLogix hardware components.

Contact your local sales office for more information about 

training schedules and available trained personnel

You must be certain that your PC meets the hardware requirements for a 

ProcessLogix Server or ProcessLogix Client.

• ProcessLogix Servers require a Windows 2000 Server operating system. 

Refer to ProcessLogix Online User Documentation/Knowledge Builder 

on page P-3 for information about ProcessLogix Server hardware.

• ProcessLogix Client Stations require a Windows 2000 Professional, XP 

Professional or 2000 Server operating system. See Table 11.B: Client 

Platform Requirements based on System Configurations on page 11-4

in the ProcessLogix R500.1 Installation and Upgrade Guide to review 

the ProcessLogix Client platform requirements.

ProcessLogix Online User Documentation/Knowledge Builder

ProcessLogix online user documentation is included with your ProcessLogix 

system in browser format through Knowledge Builder. Most of the documents 

may also be ordered individually through Rockwell Automation in print 

format, visit us at: www.theautomationbookstore.com

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. Knowledge Builder’s internal links and search 

functions allow the user to access process relevant information and references.

References to Knowledge Builder throughout this document are illustrated as:

Navigate in Knowledge Builder to Ethernet Implementation 

Guide⇒Configuration⇒Setting Up Drivers and IP Addresses for more 

information.

ProcessLogix R500.1 Installation and Upgrade Guide

The ProcessLogix R500.1 Installation and Upgrade Guide is shipped with a 

ProcessLogix system and provides:

• procedures for upgrading an R320.0 or R400.0 system to R500.1

• procedures for updating the firmware to R500.1 levels

• procedures for installing the software on a clean PC

• procedures for tasks associated with migrating to redundant Server 

and/or redundant Controller architecture.

Rockwell Automation 

Technical Support

Rockwell Automation offers support services worldwide, with over 75 

sales/support offices, 512 authorized distributors, and 260 authorized systems 

integrators located throughout the United States alone, plus Rockwell 

Automation representatives in every major country in the world.

Local Product Support

Contact your local Rockwell Automation representative for:

• sales and order support

• product technical training

• warranty support

• support service agreements

Before you contact Rockwell Automation for technical assistance, we suggest 

you please review the troubleshooting information contained in this 

publication first.

If the problem persists, call your local Rockwell Automation representative or 

contact Rockwell Automation in one of the following ways:

Your Questions or Comments about This Manual 

If you find a problem or have a comment about this manual, please notify us 

of it on the enclosed How Are We Doing Form, at the back of this manual. 

This form is also available in Knowledge Builder.

If you have any suggestions about how we can make this manual more useful 

to you, please contact us at the following address:

Rockwell Automation, Inc. 

Automation Control and Information Group

Technical Communication

1 Allen-Bradley Drive

Mayfield Heights, OH 44124-6118

Phone United 

States/Canada

1.440.646.5800

Outside United 

States/Canada

You can access the phone number for your 

country via the Internet:

1. Go to http://www.ab.com

2. Click on Product Support

(http://support.automation.rockwell.com)

3. Under Support Centers, click on Contact 

Information

Internet ⇒ 1. Go to http://www.ab.com

2. Click on Product Support

(http://support.automation.rockwell.com)

Conventions Terms and Type Representations

The following table summarizes the terms and type representation 

conventions used in this Guide.

Table P.2 : Terms and Type Representations

Term/Type 

Representation

Meaning Example

click, click on, click 

[button name]

Click left mouse button once. 

(Assumes cursor is positioned on 

object or selection.)

Click Browse. 

double-click Click left mouse button twice in 

quick succession. (Assumes cursor 

is positioned on object or 

selection.)

Double-click the Station icon. 

drag Press and hold left mouse button 

while dragging cursor to new 

screen location and then release 

the button. (Assumes cursor is 

positioned on object or selection to 

be moved.)

Drag the PID function block 

onto the Control Drawing.

right-click Click right mouse button once. 

(Assumes cursor is positioned on 

object or selection.)

Right-click the AND function 

block. 

select click to highlight a menu item or 

list choice, or click on a button.

Select Configure 

Allen-Bradley drivers from the 

list box.

<F1> Keys to be pressed are shown in 

angle brackets.

Press <F1> to view the online 

Help. 

<Ctrl>+<C> Keys to be pressed together are 

shown with a plus sign. 

Press <Ctrl>+<C> to close the 

window. 

File ⇒ New Shows menu selection as menu 

name followed by menu selection.

Click File ⇒ New to start 

new drawing. 

>D:setup.exe< Data to be keyed in at prompt or in 

an entry field.

Enter this path location 

>D:setup.exe<.

This release introduces enhancements to Rockwell Automation's ProcessLogix 

process control system.The enhancements include:

Table 1.A New Features and Functions Overview

Enhancements Description

Engineering Tools Enhancements • History Configuration

• Cross Reference and Wiring Improvement

• Compare Parameters

• SCM Memory Enhancements

• Server Scripting

Server Enhancements

New Alarm/Event subsystem • Flexible filtering, sorting and layout

• Common presentation for Alarms, Events, Journal, etc.

Updated Station & HMIWeb Display Builder • Improved menu/toolbar configuration

• Support for IKB/OEP Operator keyboards

• Define which monitor to start on, on multi-monitor systems.

• Faceplates

• Chart object

• Hyperlink support

• Rotation of static text on HMIWeb displays

• Third-party HTML displays

• Simplified appearance of HMIWeb object model in script editor

• Multiple Static Stations

Plant Data Model Enhancements • Supports 40 character Point ID's

Updated OPC Support • OPC Alarm and Event Server

Windows 2000 Security • Optionally allows the use of Windows user accounts for ProcessLogix 

operators.

Updated System Displays • Supports screen resolutions of 1280x1024

Updated Application Development • Service Pack 5 for Microsoft Visual Studio v6.0 has been qualified for 

use with ProcessLogix.

• Includes Microsoft Visual C/C++ v6.0 and Microsoft Visual Basic v6.0.

Hardware Enhancements

Additional Module Support The following modules have been qualified for use with ProcessLogix:

• 1756-ENET/B

• 1756-ENB/T

• 1794-IF4I

• 1794-OF4I

• 1756-DNB

• 1757-ABRIO

Engineering Tools 

Enhancements

Server Enhancements New Alarm/Event subsystem

The new Alarm/Event subsystem in this release of ProcessLogix can manage 

notifications from ProcessLogix and third party OPC systems. The alarm 

management presentation includes common presentation components for 

Alarms, Messages, Journal, etc. based on HMIWeb technologies. These 

displays support flexible filtering, sorting and layout. This new subsystem 

utilizes Microsoft's SQL Server for the Event Store. Optional journalling of 

full user name is also supported.

Table 1.B Enhancements to Engineering Tools 

Enhancement Description

History Configuration Historical data collection, Group display assignment, and Trend 

display assignment are now standard part of CB point 

configuration.

Cross Reference and 

Wiring Improvement

This feature improves the wiring algorithm and results in better 

wiring paths during control configuration. The cross reference 

provides an optional wire label that clearly identifies wire paths 

as they cross page boundaries.

Compare Parameters This enhancement is provided as an option during download of a 

CM/SCM or selection of CMs/SCMs. It allows reading 

parameters from the controller and comparing them with the 

Monitoring or Project version. If this option is selected, a dynamic 

form shows all parameters that differ; each of them has a 

selection box indicating if the user wants to override the value or 

not. Those parameters selected to override are sent to the 

controller.

SCM Memory 

Enhancements

CEE memory is now optimized for the actual contents of SCM 

expressions instead of a maximum sized allocation, resulting in a 

memory savings of 30-35% for the average sized SCM 

configuration.

Server Scripting Server scripts can now be attached to CM's. Server Scripts allow 

VBScript to be executed based on events happening on 

ProcessLogix like a CM going into Alarm or parameter of a CM 

changing.

Updated Station & HMIWeb Display Builder

The following updates have been made to Station & HMIWeb Display Builder: 

• Improved menu/toolbar configuration

• Support for IKB/OEP Operator keyboards

• Define which monitor to start on, on multi-monitor systems.

• Faceplates - does not depend on hard-coded references to data, instead, 

links to point when called up. “Pin” function allows pop-up to stay open 

even after underlying display is changed. Includes pre-built faceplates 

for 1757-PLX52 and Standard points.

• Chart object

• Hyperlink support

• Rotation of static text on HMIWeb displays

• Alarm object

The following updates have been made to HMIWeb Display Builder:

• Ability to edit HTML pages created in third-party tools in HMIWeb 

Display Builder.

• Simplified appearance of HMIWeb object model in script editor

• The licensing for Stations has been changed so that up to four Station 

windows can be opened from the same machine and these four Station 

windows only count as one Station License. Works only with Stations 

that have a reserved (static) connection to the server, i.e. not for rotary 

Station connections or Web browsers.

TIP The 1757-PLX52 faceplates are provided in a zipped 

package per faceplate. To use these faceplates, double-click 

on the related package in the displays directory to extract 

the files from the package.

Plant Data Model Enhancements

This release of ProcessLogix has been enhanced to support 40 character Point 

ID's (standard points only, i.e. analog, status, accumulator). Point descriptor 

and area codes have been lengthened to support 132 and 40 characters 

respectively. Users using the ProcessLogix ODBC Driver for reports or 

applications should investigate the effect of this change on their reports or 

applications.

Integrated Windows 2000 Security for ProcessLogix Operators

Operator security has been enhanced to optionally allow the use of Windows 

user accounts for ProcessLogix operators. Integrated Windows 2000 security 

allows single sign on to Windows and the ProcessLogix Operator station. 

Traditional ProcessLogix operator accounts are supported for backwards 

compatibility. In ProcessLogix R500.1, the ODBC Driver does not support 

Integrated Security accounts, only traditional accounts.

Updated OPC Support

OPC Alarm and Event Server

The ProcessLogix OPC Alarm and Event Server allows an OPC alarm and 

event client to receive alarm and event information from ProcessLogix. It is 

compliant with the OPC Version 1.0 Foundation Alarm Event Specification.

Updated System Displays

The ProcessLogix System Displays have been enhanced to support screen 

resolutions of 1280x1024.

Updated Application Development

Service Pack 5 for Microsoft Visual Studio v6.0 has been qualified for use with 

ProcessLogix. This qualification includes Microsoft Visual C/C++ v6.0 and 

Microsoft Visual Basic v6.0.

Updated Network API Support for Visual Basic

The Network API for Visual Basic has changed from previous releases. 

Previously, to add Network API support to a Visual Basic project, a developer 

would need to add references to 3 .bas files.

The mechanism has been modified, and Visual Basic applications that need to 

use the latest Network API will no longer need to include references to the 

.bas files. Instead they will need to include a reference to the Network API .dll 

from the project references dialog.

To include a reference to the Network API .dll, do the following:

1. Select Project References from the menu.

2. Check the reference “Honeywell Network API Type Library and click 

OK.

To Browse for information about the available functions, press F2 to 

open the Object Browser.

3. Select HscNetapi from the drop down combo box.

This change does not affect C/C++ applications using the Network 

API.

Hardware Enhancements Ethernet Supervisory Network

In addition to the 1756-ENET/A, the 10 megabit 1756-ENET/B and the 

10/100 megabit 1756-ENBT/A have been qualified for use as the Supervisory 

Network between the 1757-PLX52 controllers and the R500.1 ProcessLogix 

Server.

At the date of this publication, the ENBT/A is available and is the preferred 

version of this module. The 1756-ENET/A is now obsolete and the 

1756-ENET/B is in the process of being obsoleted, however both the 

1756-ENET/A and 1756-ENET/B will continue to be supported but will not 

be available for purchase.

Flex I/O

The following modules are being introduced with ProcessLogix R500.1:

• 1794-IF4I

• 1794-OF4I

1756-DNB DeviceNet Interface Module

The 1756-DNB:

• provides a communication bridge between ControlNet and DeviceNet

• utilizes the Rockwell 1756 form factor, which is native to ProcessLogix

• can be located in either the ProcessLogix Controller Rack or I/O Rack

• supports the three DeviceNet baud rates: 500 KBps, 250 KBps and 

125KBps.

• is configured from a PC running the RSNetWorx for DeviceNet 

configuration tool connected to either DeviceNet through a 1770-KFD 

Interface Module or ControlNet through a CNB.

• input and output messages from/to the various DeviceNet devices are 

bundled at the ControlNet level into 2 assemblies (data objects) which 

are available for transport across ControlNet from/to the 1757-PLX52 

Controller:

• as configured with the DeviceNet network configuration, all input 

data messages (from DeviceNet input devices) are packed into a 496 

byte input assembly. Input data is bound from input devices to the 

1757-PLX52 Controller.

• as configured with the DeviceNet network configuration, all output 

data messages (to DeviceNet output devices) are packed into a 492 

byte output assembly. Output data is bound from the 1757-PLX52 

Controller to the output device.

1757-ABRIO

The 1757-ABRIO allows Rockwell Automation controllers (ProcessLogix or 

ControlLogix) to communicate with existing Allen-Bradley analog 1771-RIO. 

The module acts as an Remote I/O scanner.

Major ProcessLogix Software Components

This chapter contains the detailed information about the major ProcessLogix 

R500.1 software and related components.

Major ProcessLogix Engineering Tools Software Revisions

Table 2.A Major ProcessLogix Engineering Tools Software Revisions

Component Version Example Verification Mechanism

Control Builder PS500.1-RI.1 1. Execute Control Builder using Start ⇒ Programs 

⇒ ProcessLogix Engineering Tools ⇒ 

Control Builder.

2. Click Help ⇒ About.

DB Admin 500.1.1.1 1. Run Windows Explorer.

2. Right-click on the file

C:HoneywellTPS50SystemBinAdminfuncs.dll

3. Click Properties.

4. Click Version tab.

Import-Export Tool PS500.1-01.1 1. Execute Import-Export Tool using Start ⇒ 

Programs ⇒ ProcessLogix Engineering Tools 

⇒ Import/Export Tool.

2. Click Help ⇒ About.

Engineering Tools 

Database

V5.0 ERDB

Release PS500.1-1.1

1. Execute Import-Export Tool using Start ⇒ 

Programs ⇒ ProcessLogix Engineering Tools 

⇒ Import/Export Tool.

2. Click Help ⇒ About.

IO Tool 500.1-1 1. Execute IO Tool using Start ⇒ Programs ⇒ 

ProcessLogix Engineering Tools ⇒ IO Tool.

2. Click Help⇒About.

External, Third Party Qualified Software Components

IMPORTANT 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.

WARNING

!

The user assumes all responsibility for issues resulting from 

the installation and operation of any components that have 

not been tested as compatible by Rockwell Automation. In 

addition, it is the customer’s responsibility to ensure that 

the combinations of third party components have sufficient 

resources (e.g. memory, CPU performance, disk space, 

display space, etc.).

Table 2.D External, Third Party Qualified Software Components

Component Version Verify the component version by:

McAfee VirusScan 4.5.1

(SP1)

1. Start VirusScan Console using: Start ⇒ Programs ⇒

Network Associates ⇒VirusScan Console.

2. Click Help ⇒ About…

McAfee VirusScan 6.0 1. Start VirusScan Console using: Start ⇒ Programs ⇒

Network Associates ⇒ VirusScan Console.

2. Click Help ⇒ About…

McAfee NetShield 4.5 1. Start NetShield using Start ⇒ Programs ⇒ Network 

Associates ⇒NetShield Console.

2. Click Help ⇒ About…

National Instruments NI-FBUS 

Communications Manager

NI-FBUS Communications Manager

2.3.4 1. Start Fieldbus Interface Configuration using: Start ⇒

Programs ⇒National Instruments FBUS ⇒ 

Interface Config.

2. Click the System Menu.

3. Select About fbConfig_NT.

Limitations/Compatibilities:

• Model Number 1788-FFCT, for use with the CN2FF. Only this 

model number should be purchased and not the general release 

of the Configurator from NI.

Performance and Capacity Specifications

Server/Client Performance 

and Capacity

PC Platform Requirements 

The performance of the PC Platform varies greatly based on the operating 

system and Process Control configuration. All information should be 

considered before ordering or configuring a system. Customers who are 

upgrading should consider upgrades to match the specifications outlined in 

this document.

ProcessLogix R500.1 Server(s) require a server grade hardware platform and 

Server grade operating system (Windows 2000 Server).

Server grade hardware is intended to serve data to clients over a network and 

as such is typically provided with lower performing video cards and without 

sound cards. The Windows 2000 Server operating system provides lower 

foreground performance than a desktop oriented operating system like 

Windows 2000 Professional. In combination with the hardware and operating 

system specifications, Rockwell Automation's tuning of the operating system 

provides optimum performance for the SQL 2000 and ProcessLogix Server. 

ATTENTION

!

This chapter contains the most current platform 

requirements from the performance and capacity 

specifications for R500.1. The information in this 

document takes precedence over that of Knowledge 

Builder or any other ProcessLogix document.

IMPORTANT The ProcessLogix Server should not be used as an operator 

station. The use of client applications on the server is 

supported (ideal for engineering activities, etc.) but the 

performance is not appropriate to be used as an operator 

station. For ProcessLogix Clients, Rockwell Automation 

recommends the Windows 2000 Professional and 

Windows XP Professional operating systems.

Server Requirements

ProcessLogix Server Software must be installed on a PC that is specifically 

qualified. Use of any other PC variations will render the standard warranty and 

support agreement null and void.

There are two methods of obtaining the qualified ProcessLogix Server:

1. Purchase the Server from Rockwell Automation.

2. Contact Rockwell Automation Technical Support for further 

information on ordering specifically qualified hardware.

Platform System Configuration Definitions

The number of Physical Servers and Stations does not determine system 

configuration. If you are considering a large and complex process, this will 

affect the performance. For example, you may only require passive monitoring 

and occasional report generation, but the process is large and complex. 

Therefore you would be better off installing system requirements that better 

match the Performance system, rather than the Typical configuration. Use the 

information below to approximate your system size.

Minimum

This is the minimum hardware necessary to run the ProcessLogix 

components. It should only be used for small configurations that may consist 

of 1 non-redundant Server or a Redundant Server pair with 1 Station. The 

system typically only includes passive monitoring and occasional report 

generation.

Typical

Configurations will consist of 1 non-redundant Server with up to 12 Stations 

or a Redundant Server pair and up to 8 Stations. This type of system includes 1 

or 2 Stations actively monitoring and occasional report generation.

Performance

An advanced configuration will consist of 1 non-redundant Server or a 

Redundant Server pair, and (between) 13 to 20 Stations. This system typically 

includes active monitoring from multiple Stations with or without multiple 

locations and random report generation. 

Table 3.A Database Sizing Chart

Process Configuration System Suggestion

Controllers: None

Up to 3,000 SCADA points

Minimum

Up to 6 Controllers(1)

Systems with up to 600 CM/SCM/IOM/1757-FIM

Up to 10,000 SCADA points

(1) Hybrid Controllers configured in a redundant mode should be counted as 1 Hybrid Controller.

Typical

More than 6 Controllers(1)

Systems with more than 600 CM/SCM/IOM/1757-FIM

More than 10,000 SCADA points.

Performance

Client Platform Requirements

Application Usage

Server configuration memory allocations assume Server services only. Client 

memory usage already includes the ProcessLogix Client Applications. 

However, most applications can be run on either the Servers or Station Clients. 

On minimum to typical systems, these applications may be run on the Server 

Platforms. On performance systems, the Servers should be dedicated to 

running only the Server Services. On these systems, when possible, all 

applications should be run from the Client stations.

Using the Platform Requirements Tables 3.B and 3.C as a base for memory 

usage, add on the memory requirements for each of the applications from the 

Application RAM Usage. Table 3.C is intended to be used on a regular basis.(1

Table 3.B Client Platform Requirements based on System Configurations

System Configuration Minimum Typical Performance

Processor 1 GHz Pentium III or larger 1.4 GHz Pentium III or larger 2.0 GHz Pentium IV or larger

RAM

• Windows 2000 Professional 128 MB(2) 256 MB 256/512 MB 

• Windows 2000 Server(1) 256 MB(2) 384 MB 512 MB 

Networking 10 Mb Ethernet(3) 100 Mb Ethernet 100 Mb Ethernet

Video Resolution 1024 x 768

65K colors

1024 x 768

1280x1024

65K colors

1024 x 768

1280x1024

65K colors

Video Memory (VRAM) 16MB 32MB 32MB

Hard Drive 9.1 GB 10 GB 20 GB

Example Hardware Dell Optiplex GX200 Dell Optiplex GX200 or GX240 Dell Optiplex GX240

(1) This Operating System is not optimal for hosting client applications. It may not be possible to configure server grade hardware to meet the requirements listed.

(2) In these configurations, paging may occur on these systems. Based on the intended usage of the platform, this configuration is acceptable. For better performance, 

users should upgrade the systems with an additional 128 MB of RAM.

(3) We suggest that you upgrade to 100 Mb Ethernet Networking

Low memory and CPU resources can affect Server performance in 

the following ways:

• Low memory can impact CB and Station operations such as 

display call-up and screen refresh. Background applications 

such as RSLinx and CDA can also be impacted. On occasion, 

extremely low memory resources have caused foreground and 

background applications to fail. 

• Low memory causes virtual memory to be swapped often, 

which itself is a CPU intensive operation. Therefore, low 

memory directly affects the amount of available CPU resources.

• Low CPU resources can impact communication between 

Clients and Server. Although the communication subsystem 

guarantees data delivery, low CPU resources can create 

communication bottlenecks that adversely affect the freshness 

of data displayed. 

• Low CPU resources can impact CB operations such as: opening 

charts, loading, uploading and updating project.

Control Builder Considerations

Viewing the expanded Monitoring Tab Tree View of the same 1757-PLX52 

Controller loaded with more than 500 total CMs, SCMs and IOMs from more 

than one CB client simultaneously, will severely affect the performance of the 

1757-PLX52 Controller’s communication capability, both to the Server and 

Peer-to-Peer.

Using multiple CB clients to load to multiple controllers simultaneously 

actually increases the overall load time. Do not employ this technique as a way 

to save time in loading a controller with contents.

Database operations (load, delete, upload, update, etc.) initiated from a CB 

client will affect the performance of applications that run on the backup 

Server. Remote CB clients will also be affected by these operations. For 

instance, a CB client will experience reduced performance if another CB client 

is also connected to the same Server and has requested a large database 

operation.

Control Builder supports multi-user functionality, however, it should be noted 

that there are some operations that are restricted. Specifically, if a load is 

carried out at the same time as database modifications are in progress 

(including import, copy, delete), then these operations may fail, displaying 

related error messages. Examples of such errors include:

• Database Modification in Progress, Try Again Later

• Point Build Error

In extreme cases these errors may cause Control Builder to stop functioning. If 

this happens, you should restart the Control Builder and reload the server 

points to ensure that the changes take effect. Data should not be affected.

Client/Server Communication Capacity

Server Notifications

Table 3.G Server communication NetBIOS session capacity

Session type or activity Comment/example

Time Sync Active once every configured Time Sync period.

Shared Drives/ Displays Active continuously, if Station Client get displays from 

central Server.

Shared printer Active continuously if linked to a network printer for 

Reports, etc.

Server Redundancy Uses from 1-3 Server Sessions based upon User/Login 

Configuration settings. (Also requires Time-Sync)

ER Server Active during replication on Redundant Servers.

Multi-User CB Active during Point Build (uses shared drive)

Snap-Shot Save & Restore Active during this operation (uses shared drive)

Server Type Simultaneous NetBIOS sessions available

ProcessLogix Server on Windows 2000 Server Unlimited (See Microsoft license restrictions)

Table 3.H Server Notifications

Server Notifications Value

Maximum number of events (burst condition)(1) 1000 events 

Maximum number of events/second (sustained) 40/sec

Maximum number of alarms/second (sustained)(2) 20/sec

Maximum number of remote OPC A&E Servers subscribed to by the ProcessLogix Server(3)

Maximum number of remote OPC A&E Clients supported by the ProcessLogix OPC A&E 

Server

5

(1) Event Burst Handling

The ProcessLogix Server Alarm System will handle an event burst of up to 1000 events, with a minimum time between consecutive 

bursts. An “event burst” will be defined as a group of events greater than 40/sec, received from all connected Event Servers in a period 

of less than 3 seconds. The time period required between consecutive bursts, to allow for event processing, can be calculated using 

the following formula:

T = BS/(40-ER) Where:

T = # of seconds required between bursts

BS = Burst Size (number of events in the burst)

ER = Event Rate between bursts

Examples: 

1) 1000 Event burst and no events between bursts: T = 1000/40 = 25 seconds

2) 500 Event burst with 30 events/sec between: T = 500/10 = 50 seconds

(2) Up to two events are also generated for every alarm, including one event for entering the alarm condition and one for return to normal.

(3) OPC Alarm & Event Support: The ProcessLogix Server includes the option to support reception of OPC Alarms & Events, in addition to 

native ProcessLogix notifications. When an OPC Alarm & Event Server has been configured to generate notifications to captured by the 

ProcessLogix Server Alarm System, the notification limits noted above are applicable to the combined set of events received from all 

event sources configured.