ALTUS Nexto NX3004 User Manual

6. Redundancy with NX3030 CPU
294
 Transitions can only be triggered if the CPU is on and the MainTask is executing. Otherwise the
CPU is assumed to be in the Not-Configured state
 In several cases, transitions caused by the PX2612 panel buttons are mentioned. It must be
recalled there are alternatives for these buttons, which are internal commands from one CPU or
the other (via NETA / NETB). Such commands were mentioned preliminary in the Diagnostics,
Commands and User Data Structure section and are better described in the Redundancy
Commands section. In the following sub-sections, to simplify, these commands are not
mentioned, but one must remember they can cause the same transitions as the PX2612 button.
Transition 1 – Not-Configured to Starting
ATTENTION:
The conditions of this sub-section must not be analyzed in case the other CPU is in Active state and
the projects are different. This CPU must remain in the Not-Configured state while its project is
different from the other CPU project, if the other is in Active state. This note isn’t valid if the project
automatic synchronization is disabled (see Project Synchronization Disabling section), as in this case
differences between the CPUs projects are allowed.
 A configuration request is already existent at the beginning of the Not-Configured state. This
occurs in the moment the CPU is switched on, and also other situations, described in the next
sub-sections.
 The STAND-BY button was pressed during the Not-Configured state. This causes a manual
configuration request. The user typically presses STAND-BY after fail repairing which had
driven this CPU to the Not-Configured state.
Transition 2 – Starting to Not-Configured
 This CPU was turned off or restarted (warm reset, cold or origin) or its CPU went to Stop mode
 The identification register of this CPU is invalid (different than PLCA or PLCB)
 There are logic configuration errors in the project received from MasterTool IEC XE
 The other CPU is in the Active state and the firmware version in this CPU is incompatible with
firmware version in it
 The other CPU is in Active state and the project in this CPU is different from the project in it.
Besides going to the Not-Configured state, a configuration request is made. This way, after the
projects are synchronized, the CPU goes out automatically from the Not-Configured state to the
Starting state. This condition isn’t analyzed if the project automatic synchronization is disabled (
Project Synchronization Disabling section)
Transition 3 – Starting to Inactive
 NX4010 module not detected in the bus, or its microprocessor failure
 A synchronism channel (NETA or NETB) is in failure and this CPU knows this failure was
caused by hardware components or internal software (internal failures of NETA or NETB)
 The Other CPU is in Active state. However, it’s not possible to synchronize the redundant data or
the redundant forcing list
 The other CPU state cannot be discovered through NETA / NETB, but this CPU can monitor the
traffic in some configured PROFIBUS networks in vital fail mode. This way, it looks like the
other CPU is controlling the process, even though NETA / NETB aren’t working to confirm it
 On the redundancy without PX-2612 panel and without PROFIBUS network, in case other
PLC’s state can’t be known via NETA/NETB, but this PLC is receiving information that the
other cluster’s state is ACTIVE through Keep Alive packages received via NX3030’s NET1 or
NET2Link loss occurred to an Ethernet Interface configured as Vital Failure

ALTUS Nexto NX3004 Specifications

General

Brand	ALTUS
Model	Nexto NX3004
Category	Processor
Language	English