Rockwell Automation 1757-SWKIT5000 ProcessLogix R500.1 Installation and Upgrade Guide - Manual (Page 267)

Publication 1757-IN500A-EN-P - September 2002
Performance and Capacity Specifications 11-27
Migration Consideration
In R500.1, every ProcessLogix function block uses 4 bytes of memory more
than that it used in earlier versions of ProcessLogix. As a result, the CPM
memory usage of the same control strategy would be more in R500.1 than that
in pre-R500.1 release. Roughly speaking, the increase in memory can be
calculated as follows:
Additional Memory Needed = (Number of IOM's + Number of SCM's +
Number of CMs + Number of all CM and SCM contained blocks) * 4 bytes
Enough spare memory that would accommodate this increase must be
available in existing controllers for migration to R500.1 to work.
ERDB is Master for Configuration Data in R500.1
As of R500.1, the Engineering Repository Data Base is considered to be the
master for configuration data for Server's ProcessLogix configuration data.
This includes a ProcessLogix point's history, trend, and group configuration
data.
If a change is made to this Server data from Station, the customer needs to
upload each ProcessLogix point that had a configuration change to the
Engineering Repository using the Control Builder
Possible Loss of Communication with CPM
Error Indication: Unable to communicate with the CPM. From the CPM
front panel display, either the alphanumeric display's illumination varies or the
Health LED is solid red.
Description: In a redundant controller system, the new primary CPM
infrequently may become mute or hard fault (i.e. Health LED is solid red)
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.
Recovery: Power-cycle the mute or faulted primary controller.
Workaround: Avoid operator induced redundant controller switchovers with
I/O that is configured but not physically present.