2
SYSTEM CONFIGURATION
2.4 System Configuration Cautions
2
- 19
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
• To communicate via a module mounted on the extension base unit by using MC
protocol, use QnA-compatible 2C/3C/4C frame, QnA-compatible 3E frame, or 4E
frame for the access.
• MELSOFT products connectable to a module mounted on the extension base
unit are GX Developer and PX Developer. However, there are restrictions on
applicable functions. For details, refer to the following manuals.
GX Developer Version 8 Operating Manual
PX Developer Version 1 Operating Manual (Programming Tool)
POINT
Only the control system can access modules on the extension base units.
If accessing the standby system while the system monitor function of GX
Developer is in execution, the extension base units and modules on them are not
displayed.
Using GX Developer with specifying "Control system" at [Target system] in the
[Transfer Setup] screen is preferable.
(2) Modules that can be mounted on a main base unit
The I/O modules used independently by the network module and System A or System
B CPU module can be mounted on the same main base unit as a redundant CPU is
mounted.
I/O modules and intelligent function modules used to control a redundant system must
be mounted on MELSECNET/H remote I/O station or extension base unit.
Remote I/O station, remote device station, and intelligent device station can be used
by mounting CC-Link master module on a main base unit or extension base unit.