4
PROCEDURE FOR STARTING UP A REDUNDANT
SYSTEM
4 - 3
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
* 1: Use "double-shielded coaxial cables" when configuring a coaxial bus system on a MELSECNET/
H remote I/O network.
Refer to the following manual for the double shielded coaxial cables.
Q Corresponding MELSECNET/H Network System Reference Manual (Remote I/O
network)
* 2: When the "SYSTEM A"/"SYSTEM B" LED is off and the "ERR." LED is flashing, they indicate that
the tracking cable is not connected or is faulty.
Connect or change the tracking cable.
* 3: When starting the redundant system, do not perform the following operations until the "BACKUP"
LED is ON (green).
Failure to do so may disable a normal start of the CPU module due to a stop error, "TRK. INIT.
ERROR (error code: 6140)" or "CONTROL SYS. DOWN (error code: 6310 to 6312)".
( Section 8.1.7, Section 8.1.8)
Power either system off and then on.
Reset either system CPU module and then set its RESET switch to the neutral position.
* 4: Diagnostics includes PLC diagnostics, Ethernet diagnostics, CC IE Control diagnostics,
MELSECNET diagnostics, and CC-Link/CC-Link/LT diagnostics.
For details, refer to each network manual.
* 5: If the RUN/STOP switch of standby CPU module is set to RUN and the operation status differs
between the control system and standby system, the "consistency check" causes "OPE.MODE
DIFF. (error code: 6010)" in the control system CPU module. ( Section 5.1.4)
Running Control System (System A) CPU module
...Refer to
Section 4.11
(1) Set the RUN/STOP switch of control system CPU module (the "CONTROL" LED is OFF) to
the RUN position, and confirm that the "RUN" LED of CPU module is ON.
(2) Confirm that the "ERR." LED of control system CPU module is OFF.
If the "ERR." LED is ON/flashing, check the error cause using the System Monitor or
diagnostics
*4
of GX Developer, and eliminate it.
If the error is caused by the parameter or programs, correct the parameters or programs of
system A and system B.
Restarting System A and System B
*3
...Refer to
Section 4.8
(1) Power off system A and system B, or simultaneously set the RESET/L.CLR switches of
CPU modules to the RESET position.
(2) Simultaneously power on system A and system B, or simultaneously set the RESET/L.CLR
switches of CPU modules to the reset switch neutral position.
Diagram 4.1 Procedure for starting Up in Backup Mode
Complete
To Next Page
Loading...
