![ALTUS Hadron Xtorm Скачать руководство пользователя страница 277](http://html1.mh-extra.com/html/altus/hadron-xtorm/hadron-xtorm_user-manual_2914394277.webp)
6. HX3040 Redundancy
276
Transition 3
– Starting to Non-Configured
The current CPU is turned off or rebooted (Reset Warm, Reset Cold or Reset Origin).
The current CPU is inserted in an incorrect position.
There are configuration logic errors in the project received from MasterTool Xtorm.
The other CPU is in Active state, and the firmware version of the current CPU is incompatible
with the firmware version of the CPU Active.
The CPU, which is in Active state, has a different project than the one from the current CPU.
Besides going to Non-Configured state, the CPU requests a configuration. Thus, after the
projects synchronization, the CPU automatically toggles from the Non-Configured to the
Initializing state.
Transition 4
– Starting to Inactive
There are some software exceptions in the current CPU (watchdog, access violation, illegal
instruction).
Some of the sync channels of the internal link redundancy (channel A or B) is in failure. The
current CPU knows that this failure was caused by internal hardware or software components
(internal failures of A or B channels).
The other CPU is in Active state. However, you cannot synchronize the redundant data or the list
of redundant forcing.
The redundancy internal link is not able to find out the other CPU’s state, even though it can
monitor some activity on the bus. Therefore, although the internal link Redundancy does not
work properly, the other CPU is controlling the process.
The RUN/STOP states of the application are different from the Active CPU. For some failure
reason, the CPU did not synchronized these application states to the other Active CPU.
Transition 5
– Starting to Active
The other CPU is in Non-Active state. Before making this transition, this condition must remain
true for some time. When CPUA and CPUB are energized simultaneously, the CPU that first
finishes the system startup takes over as Active.
The redundancy internal link is not able to find out the other CPU’s state. Additionally, the CPU
cannot monitor any activity on the bus. Therefore, this CPU is missing or it is out of run
(software exception). For security reasons, the stand-by CPU switches to Active. This condition
should be kept for some time before making this transition.
Transition 6 - Starting to Stand-by
The other CPU is in Active state and the synchronization services of redundant data are working
properly (event queue, redundant variables and list of forcing redundant variables).
Transition 7
– Inactive to Not-Configured
The current CPU is turned off or rebooted (Reset Warm, Reset Cold or Reset Origin).
There is a request for the STAND-BY command. Besides going to Non-Configured state, the
CPU requests a configuration. Typically, the user requests the STAND-BY control after
repairing flaws that previously led this CPU to an Inactive state.
Transition 8
– Active to Not-Configured
The current CPU is turned off or rebooted (Reset Warm, Reset Cold or Reset Origin).
Transition 9
– Active to Inactive
There are some software exceptions in the current CPU (watchdog, access violation, illegal
instruction).