of your configuration (that is, function blocks) can be
allocated for recipes. As long as memory is available,
allocate as many recipes as needed.
The rule of thumb is
Max. number of recipes = Recipe memory allocation ÷
memory per recipe
Configuration memory allocation
The configuration memory comprises one allocation for the
function block configuration and one allocation for recipes.
In general,
Total configuration memory =
Configuration + Recipe allocation
Whatever memory has not been allocated to recipes is
available for your configuration. By changing the size of the
recipe pool allocation, you control the amount of memory
available for recipes and therefore configuration. Need a
small configuration but many recipes? Allocate more recipe
space. Need a large configuration but few recipes?
Allocate less recipe space
Where are usage/capacities presented?
File Properties in Designer displays statistics on
usage/availability of:
• configuration memory (recipes + function
block configuration),
• dynamic memory (function block configuration
only)
• fast scan time,
• Normal scan time,
• Normal CPU% used,
• Fast CPU% used,
• Each component of a configuration (variables,
constants, etc.).
Controller Data Storage
The controller may log process data values in the available
memory that is not used by the configuration. Up to 250
signal values may be logged in a rotating buffer using three
different sample rates with oldest data being replaced with
new data after the buffer is full.
Data is extracted from the controller using HC Historian data
harvesting software via Ethernet or Serial connection.