User manual

Toolbox 32 User Manual 1.47d www.cse-semaphore.com/mykingfisher
Page
264
#Y2NDSTAT
Primary / Secondary master RTU Status. This is an integer value that can
be configured as follows:
0 = No primary/secondary. The RTU is not a primary or a secondary RTU. This
is the default setting after a cold start.
1 = Primary control. The RTU is the primary RTU and is in control. This means
the RTU will behave like a normally configured RTU and will initiate and
acknowledge messages. When the primary RTU is in this mode, the secondary
RTU should be in secondary listen mode (mode 4 or 12).
2 = Primary listen. This RTU is the primary RTU but it is in listen mode. This
means the RTU will only respond to messages from the PC and messages from
the secondary RTU. The primary RTU should start up in this mode to check if the
secondary is in control mode. If the primary starts up in control mode and the
secondary is also in control mode, both RTU's will acknowledge the same
messages - causing communication failures. When the secondary is in control
mode it should regularly test the primary to see if the primary is ready to resume
control. If the primary is ready, the secondary should go back to listen mode and
the primary should take over. While in this mode, the RTU will not relay Modbus
write commands to the
outstations (please see mode 10).
3 = Secondary control. The secondary RTU is in control mode and will respond
to messages for itself and to messages for the primary RTU. The secondary RTU
should enter this mode when the primary RTU fails. When in secondary control
mode, the RTU will accept all outputs to the Primary RTU's local registers and
write these to its own local registers.
4 = Secondary listen. The secondary RTU is in listen mode and will respond to
messages for itself only. If it receives a message for the primary RTU it will
process it (for example update its network registers) but it will not acknowledge
the message. The secondary listen RTU will allow messages (eg. from Toolbox)
to be relayed to the Primary RTU and to the outstation RTUs. While in this mode,
the RTU will not relay Modbus write commands to the outstations (see mode 12).
The secondary RTU should be in this mode when the primary RTU is in primary
control mode. Note: the secondary RTU will not update its event logs when it
hears event log messages for the primary RTU. Event logs must be updated in
the secondary RTU by using a TX Update Event Logs block in the primary RTU.
10 = Primary Listen with relay Modbus write commands. This has the same
function as the Primary Listen mode but will also allow Modbus outputs to be
relayed to the outstation RTUs.
12 = Secondary Listen with relay Modbus write commands. This has the
same function as the Secondary Listen mode but will also allow Modbus outputs
to be relayed to outstation RTUs.
Read/Write