6
REDUNDANT SYSTEM NETWORKS
6.1 Communication with GX Developer and PX Developer
6.1.1 Communication Methods with GX Developer
6
- 2
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
Table6.1 GX Developer System Specification and Communication Paths
System
Specification
Communication Path
Not specified
(Default)
• Select this option to communicate with only the
CPU module connected to GX Developer.
Control
System
• Select this option to communicate with the control
system CPU module using GX Developer.
If system switching occurs, communication is done
with the new control system CPU module.
• If the CPU module connected to GX Developer is
the control system, communication is done with
that CPU module.
If the CPU module connected to GX Developer is
the standby system, communication is done with
the other system (the control system) via the
tracking cable.
Standby
System
• Select this option to communicate with the standby
system CPU module using GX Developer.
If system switching occurs, communication is done
with the new standby system CPU module.
• If the CPU module connected to GX Developer is
the standby system, communication is done with
that CPU module.
If the CPU module connected to GX Developer is
the control system, communication is done with the
other system (the standby system) via the tracking
cable.
System A
• Select this option to communicate with system A
CPU module using GX Developer.
If system switching occurs, communication
continues with the new system A CPU module.
• If the CPU module connected to GX Developer is
system A, communication is done with that CPU
module.
If the CPU module connected to GX Developer is
system B, communication is done with the other
system (system A) via the tracking cable.
System B
• Select this option to communicate with system B
CPU module using GX Developer.
If system switching occurs, communication
continues with the new system B CPU module.
• If the CPU module connected to GX Developer is
system B, communication is done with that CPU
module. If the CPU module connected to GX
Developer is system A, communication is done with
the other system (system B) via the tracking cable.
GX Developer
Communicate with the connected CPU module
Tracking cable
System A - Control System System B - Standby System
System not
specified (default)
GX Developer
GX Developer
Communicate with the control system CPU module
Communicate with the control system CPU module
Tracking cable
System A - Control System System B - Standby System
Control system
Tracking cable
System A - Control System System B - Standby System
Control system
GX Developer
GX Developer
Tracking cable
System A - Control System System B - Standby System
Tracking cable
System A - Control System System B - Standby System
Standby system
Standby system
Communicate with the standby system CPU module
Communicate with the standby system CPU module
GX Developer
GX Developer
Communicate with the System A's CPU module
Communicate with the System A's CPU module
Tracking cable
System A - Control System System B - Standby System
System A
Tracking cable
System A - Control System System B - Standby System
System A
Communicate with the System B's CPU module
Communicate with the System B's CPU module
GX Developer
GX Developer
Tracking cable
System A - Control System System B - Standby System
System B
Tracking cable
System A - Control System System B - Standby System
System B