Rockwell Automation 1757-SWKIT5100 ProcessLogix R510.0 Installation and Upgrade Guide - Manual (Page 266)

Publication 1757-IN510A-EN-P - October 2003
11-26 Performance and Capacity Specifications
Migration Consideration
In R510.0, 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 R510.0 than that in pre-R510.0 release. Roughly speaking, the
increase in memory can be calculated as follows:
Additional Memory Needed = (Number of IOMs + Number of SCMs +
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 R510.0 to work.
ERDB is Master for Configuration Data in R510.0
As of R500.0, 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
Er r or 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.
Descr iption: 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.
Recover y: Power-cycle the mute or faulted primary controller.
Wor kar ound: Avoid operator induced redundant controller
switchovers with I/O that is configured but not physically present.