5
REDUNDANT SYSTEM FUNCTIONS
5.1 Basic Concept of Redundant System
5.1.3 Operation Mode
5
- 12
1
OV
ER
VIE
W
2
SYS
TEM
CONFIGURA
TI
ON
3
TR
AC
KI
N
G
C
ABL
E
4
P
R
OCE
DURE
FO
R
S
TAR
TING
UP
A
RE
DUN
DAN
T
S
Y
S
T
E
M
5
RE
DUNDA
NT S
Y
S
T
E
M
FUNCTIONS
6
RE
DUN
DAN
T
S
Y
S
T
E
M
NE
TW
O
R
K
S
7
PR
OG
R
A
MM
IN
G
CA
UTIO
N
S
8
TR
O
U
BLE
S
HOOTING
(c) Precautions
1) When the operation mode is changed with GX Developer while the redundant
system is running, the operation mode will automatically change to the
separate mode. (Refer to Section 5.4, for details on changing Operating
Mode.)
2) If either system is powered on again or either CPU module is unreset (RESET/
L.CLR switch is set to the neutral position) in the separate mode, system
switching will not occur.
• If the control system is powered on again or unreset (RESET/L.CLR
switch is set to the neutral position), it will start up as the control system,
again.
• If the standby system is powered on again or unreset (RESET/L.CLR
switch is set to the neutral position), it will start up as the standby system,
again.
System switching will not occur even when the control system is powered on
again or unreset (RESET/L.CLR switch is set to the neutral position).
However, system switching can be manually carried out.
Refer to Section 5.3, for details on system switching.
3) Do not turn OFF the power supply of the control system or perform reset
operation in the separate mode when the extension base unit is connected.
(If doing so, turn ON both systems simultaneously or cancel the reset.)
4) Internal device tracking can be done in the separate mode.
Internal devices are tracked even when the operation mode is changed from
the backup mode to separate mode.
To interrupt internal device tracking, turn the tracking trigger off.
(
POINT
1. When the system A and system B are powered on simultaneously or unreset
(RESET/L.CLR switch is set to the neutral position) simultaneously, the
operation mode will change to the backup mode.
2. Make sure the tracking cable is connected to the system A and system B
CPU modules before powering on the either system again in the separate
mode. Failure to do so may cause the "TRK. CABLE ERR (error code: 6120)"
stop error in the CPU module of that system.