6. Redundancy with NX3030 CPU
279
Above there’s an example in ST language, where the redundancy command can be executed through
two variables from different communication ports. On the same example, three different commands
were executed (StandBy, Inactive and Turn-on).
Where:
var_StandBy_ command_Ethernet_relation: Bool type variable attributed to an Ethernet
communication Coil which will execute the command to put the local Half-Cluster in Stand-By.
var_StandBy_command_Serial_relation: Bool type variable attributed to a Serial communication
Coil which will execute the command to put the local Half-Cluster in Stand-By.
DG_NX4010.tRedundancy.RedCmdLoc.bStandbyLocal: this command executes an action similar to
the button STAND-BY from the PX2612, in the local PLC.
var_Inactive_command_Ethernet_relation: Bool type variable attributed to an Ethernet
communication Coil which will execute the command to put the local Half-Cluster in Inactive.
var_Inactive_command_Serial_relation: Bool type variable attributed to a Serial communication Coil
which will execute the command to put the local Half-Cluster in Inactive.
DG_NX4010.tRedundancy.RedCmdLoc.bInactiveLocal: this command executes an action similar to
the button INACTIVE from the PX2612, in the local PLC.
var_TurnOn_command_Ethernet_relation: Bool type variable attributed to an Ethernet
communication Coil which will execute the command to reactivate the local Half-Cluster after
switched off by the PX2612 relay.
var_Turn_command_Serial_relation: Bool type variable attributed to a Serial communication Coil
which will execute the command to reactivate the local Half-Cluster after switched off by the
PX2612 relay.
DG_NX4010.tRedundancy.RedCmdLoc.bTurnOnLocal: this command executes an action similar to
the button STAND-BY from the PX2612, in the local PLC.
Diagnostics, Commands and User Data Structure
Each CPU has several data structure related to redundancy. The following structure is AT variables
mapped over %Q variables:
ï‚· RedDgnLoc: has diagnostics from the CPU (local) related to the redundancy, as the CPU
redundancy state, for instance;
 RedDgnRem: it’s a copy from the other CPU RedDgnLoc, received through NETA/NETB
synchronism channels. This way, this CPU (local) has access to the other CPU (remote)
diagnostics;
ï‚· RedCmdLoc: has commands which must be applied on this CPU (when called Local) or on the
other CPU (when called Remote). E.g. the StandbyLocal field from this data structure
corresponds to a command which must be executed in this CPU (local), while the
StandbyRemote field corresponds to a command which must be executed in the other CPU
(remote);
 RedCmdRem: it’s a copy from the other CPU RedCmdLoc, received through NETA/NETB
synchronism channels. This way, this CPU (local) can execute commands received from the
other CPU (remote);
ï‚· RedUsrLoc: has 128bytes of data filled freely by the user (e.g. communication diagnostics with a
SCADA system). These 128bytes of data can be interchanged with the other CPU (remote);
 RedUsrRem: it’s a copy from the other CPU RedUsrLoc, received through NETA/NETB;
On Maintenance section, the following sub-sections offer more details regarding these data
structures:
ï‚· Redundancy Diagnostics Structure
ï‚· Redundancy Commands
To Next Page
Loading...
General