![ALTUS Hadron Xtorm Скачать руководство пользователя страница 302](http://html1.mh-extra.com/html/altus/hadron-xtorm/hadron-xtorm_user-manual_2914394302.webp)
6. HX3040 Redundancy
301
For more information, the MasterTool IEC XE User Manual TM8500 (MU299048) should be
consulted.
Load of Changes in Online Mode
In the section Load of Changes in Offline and Online Mode, were described modifications that
require offline load and those that allow online load.
A charge must be made online by connecting the MasterTool to Active CPU NET 1 channel, using
your unique IP address (CPUA or CPUB IP). It is necessary to change the Redundancy State of the
Standby CPU to inactive before sending the online modification to the Active CPU, otherwise the
MasterTool will block the operation. After the sending of changes, the application is automatically
created in the non-volatile memory of the CPU, without the risk of losing the modifications in case of
the CPU be switched off or in the event of a power failure.
After finished online loading process, the CPU can exit inactive state, for example, by using the
command "Switch to Standby" in the display menu. This will cause the CPU transition to the non-
configured state. The CPU will remain in the non-configured state until the process of automatic
synchronization of projects finishes. After that, the CPU goes to the initializing state and then returns
to the Standby state or goes back to the inactive state if a failure occurs.
Offline Load of Changes with Interruption of Process Control
In this section, it is defined the procedure for performing an offline loading that interrupts the process
control. Such a situation is acceptable in certain types of cases and during process shutdown.
An offline load of this type must be made by connecting the MasterTool to Active CPU NET 1
channel, using the unique address of the CPU in the active state (CPUx IP address). Before starting
an offline loading on the Active CPU, the user must pass the Standby CPU to the Inactive State. If
this is not done, the MasterTool will not allow this change.
To run offline load, it is necessary that Standby CPU goes to the inactive state, preventing an
accidental program load.
At the time that offline load starts, the Active CPU goes to the non-Configured state.
When the offline load finishes, the user can restart program execution on the CPU where the
application has been loaded (switch to RUN mode). After a few seconds, this CPU returns to the
active state.
After this CPU returns to the active state, the user can take the other CPU of inactive state, for
example, by using the command "Switch to Standby" in display menu. This will cause the CPU
transition to the non-configured state. The CPU will remain in the non-configured state until the
process of automatic synchronization of projects finishes. After that, the CPU goes to the initializing
state and then returns to the Standby state.
Redundant RTUs Maintenance
MasterTool Warning Messages
When the MasterTool is making a connection or is already connected to a CPU with redundant
project, some special warning messages may occur as described in the next subsections.
Blocking Before Commands that can Stop the Active CPU
Some commands, such as the following, can stop a CPU:
Offline load after Online/Login
Debug/Stop
Debug/New Breakpoint
Online/Reset (hot, cold, origin)