4. Configuration
36
ATTENTION:
When the initial address or the retentive or persistent data memory size are changed in the user
application, the memory is totally reallocated, what makes the retentive and persistent variable area
be clean. So the user has to be careful so as not to lose the saved data in the memory.
ATTENTION:
In situations where the symbolic persistent memory area is modified, a message will be displayed by
MasterTool IEC XE programmer, to choose the behavior for this area after charging the modified
program. The choice of this behavior does not affect the persistent area of direct representation,
which is always clean.
ATTENTION:
The option Enable I/O update per task is not supported for fieldbus masters such as NX5001
module. This feature is applicable only for input and output modules present on the controller local
bus (main rack and expansion racks).
ATTENTION:
Even when an I/O point is used in other tasks, with the Enable I/O update per task marked, it will
continue to be updated in the MainTask as well; except when all the points of the module are used in
some other task, in this case they will not be updated on MainTask anymore.
Hot Swap
Nexto Series CPUs have the possibility of I/O modules change in the bus with no need for system
turn off and without information loss. This feature is known as hot swap.
CAUTION:
Nexto Series CPUs do not guarantee the persistent and retentive variables retentivity in case
the power supply or even the CPU is removed from the energized backplane rack.
On the hot swap, the related system behavior modifies itself following the configuration table defined
by the user which represents the options below, as described on Table 4-1:
ï‚· Disable, for declared modules only
ï‚· Disabled
ï‚· Enabled, with consistency in the start only for declared modules
ï‚· Enabled, with startup consistency
ï‚· Enabled, without consistency in the start
Therefore, the user can choose the behavior the system must assume in abnormal bus situations and
when the CPU is in Run Mode. Table 4-2 presents the possible abnormal bus situations.
Incompatible
configuration
- Some module connected to the bus is different from the model that is declared in
configuration.
- The module was removed from the bus.
- Some mal functioning module is not responding to CPU
- Some bus position is malfunctioning.
Table 4-2. Bus Abnormal Situations