Mitsubishi Q12PRHCPU - Cautions on Access from GX Developer and PX Developer

6
REDUNDANT SYSTEM NETWORKS
6.1 Communication with GX Developer and PX Developer
6.1.3 Cautions on Access from GX Developer and PX Developer
6 - 4
1
OVERVIEW
2
SYSTEM CONFIGURATION
3
TRACKING CABLE
4
PROCEDURE FOR STARTING UP A REDUNDANT SYSTEM
5
REDUNDANT SYSTEM FUNCTIONS
6
REDUNDANT SYSTEM NETWORKS
7
PROGRAMMING CAUTIONS
8
TROUBLESHOOTING
6.1.3 Cautions on Access from GX Developer and PX Developer
This section describes cautions on access from GX Developer and PX Developer.
(1) Cautions when the System Connected to GX Developer/PX Developer
and the Specified System are Different
(a) Communicating with a CPU Module via a Tracking Cable
When the system for the CPU module to which GX Developer/PX Developer is
connected is different from the specified system, communication is done with the
CPU module of the other system (specified system) via the tracking cable.
( Table6.1)
(b) Accessing a Network Module via a Tracking Cable
Communication with a network module on the other system via a tracking cable is
not available for GX Developer and PX Developer.
To communicate with a network module on the other system (e.g, network
diagnosis of the other system), reconnect the GX Developer and PX Developer to
the CPU module on the other system.
Diagram 6.3 Communication with CPU Module via Tracking Cable
Diagram 6.4 Access to Network Module via Tracking Cable
GX Developer
CC-Link
Tracking cable
Specify standby
system.
GX Developer
CC-Link
Control system Standby system
Tracking cable
Specify CC-Link master
module in standby system.
CC-Link Master Module