QCPU Users Manual (Hardware Design - Maintenance and Inspection)
QCPU Users Manual (Hardware Design - Maintenance and Inspection)
Programmable Controller
User's Manual
(Hardware Design,
Maintenance and Inspection)
QCPU
01072009
SH(NA)-080483 MITSUBISHI ELECTRIC INDUSTRIAL AUTOMATION
Version P
SAFETY PRECAUTIONS
(Read these precautions before using this product.)
Before using this product, please read this manual and the relevant manuals carefully and pay full
attention to safety to handle the product correctly.
In this manual, the safety precautions are classified into two levels: " DANGER" and " CAUTION".
Under some circumstances, failure to observe the precautions given under " CAUTION" may lead to
serious consequences.
Observe the precautions of both levels because they are important for personal and system safety.
Make sure that the end users read this manual and then keep the manual in a safe place for future
reference.
A-1
[Design Precautions]
DANGER
Configure safety circuits external to the programmable controller to ensure that the entire system
operates safely even when a fault occurs in the external power supply or the programmable
controller. Failure to do so may result in an accident due to an incorrect output or malfunction.
(1) Configure external safety circuits, such as an emergency stop circuit, protection circuit, and
protective interlock circuit for forward/reverse operation or upper/lower limit positioning.
(2) The programmable controller stops its operation upon detection of the following status, and the
output status of the system will be as shown below.
Status Q series module AnS/A series module
Overcurrent or overvoltage protection of
All outputs are turned off All outputs are turned off
the power supply module is activated.
The CPU module detects an error such as All outputs are held or
a watchdog timer error by the turned off according to the All outputs are turned off
self-diagnostic function. parameter setting.
All outputs may turn on when an error occurs in the part, such as I/O control part, where the CPU
module cannot detect any error. To ensure safety operation in such a case, provide a safety
mechanism or a fail-safe circuit external to the programmable controller. For a fail-safe circuit
example, refer to LOADING AND INSTALLATION in this manual.
(3) Outputs may remain on or off due to a failure of an output module relay or transistor. Configure
an external circuit for monitoring output signals that could cause a serious accident.
A-2
[Design Precautions]
DANGER
In an output module, when a load current exceeding the rated current or an overcurrent caused by a
load short-circuit flows for a long time, it may cause smoke and fire. To prevent this, configure an
external safety circuit, such as a fuse.
Configure a circuit so that the programmable controller is turned on first and then the external power
supply.
If the external power supply is turned on first, an accident may occur due to an incorrect output or
malfunction.
For the operating status of each station after a communication failure, refer to relevant manuals for
the network.
Incorrect output or malfunction due to a communication failure may result in an accident.
When changing data of the running programmable controller from a peripheral connected to the
CPU module or from a personal computer connected to an intelligent function module, configure an
interlock circuit in the sequence program to ensure that the entire system will always operate safely.
For program modification and operating status change, read relevant manuals carefully and ensure
the safety before operation.
Especially, in the case of a control from an external device to a remote programmable controller,
immediate action cannot be taken for a problem on the programmable controller due to a
communication failure.
To prevent this, configure an interlock circuit in the sequence program, and determine corrective
actions to be taken between the external device and CPU module in case of a communication
failure.
CAUTION
Do not install the control lines or communication cables together with the main circuit lines or power
cables.
Keep a distance of 100mm (3.94 inches) or more between them.
Failure to do so may result in malfunction due to noise.
When a device such as a lamp, heater, or solenoid valve is controlled through an output module, a
large current (approximately ten times greater than normal) may flow when the output is turned from
off to on.
Take measures such as replacing the module with one having a sufficient current rating.
A-3
[Installation Precautions]
CAUTION
Use the programmable controller in an environment that meets the general specifications in this
manual.
Failure to do so may result in electric shock, fire, malfunction, or damage to or deterioration of the
product.
To mount the module, while pressing the module mounting lever located in the lower part of the
module, fully insert the module fixing projection(s) into the hole(s) in the base unit and press the
module until it snaps into place.
Incorrect mounting may cause malfunction, failure or drop of the module.
When using the programmable controller in an environment of frequent vibrations, fix the module
with a screw.
Tighten the screw within the specified torque range.
Undertightening can cause drop of the screw, short circuit or malfunction.
Overtightening can damage the screw and/or module, resulting in drop, short circuit, or malfunction.
When using an extension cable, connect it to the extension cable connector of the base unit securely.
Check the connection for looseness.
Poor contact may cause incorrect input or output.
When using a memory card, fully insert it into the memory card slot.
Check that it is inserted completely.
Poor contact may cause malfunction.
Shut off the external power supply for the system in all phases before mounting or removing the
module. Failure to do so may result in damage to the product.
A module can be replaced online (while power is on) on any MELSECNET/H remote I/O station or in
the system where a CPU module supporting the online module change function is used.
Note that there are restrictions on the modules that can be replaced online, and each module has its
predetermined replacement procedure.
For details, refer to this manual and in the manual for the corresponding module.
When using a Motion CPU module and modules designed for motion control, check that the
combinations of these modules are correct before applying power.
The modules may be damaged if the combination is incorrect.
For details, refer to the user's manual for the Motion CPU module.
A-4
[Wiring Precautions]
DANGER
Shut off the external power supply for the system in all phases before wiring.
Failure to do so may result in electric shock or damage to the product.
After wiring, attach the included terminal cover to the module before turning it on for operation.
Failure to do so may result in electric shock.
DANGER
Ground the FG and LG terminals to the protective ground conductor dedicated to the programmable
controller.
Failure to do so may result in electric shock or malfunction.
Use applicable solderless terminals and tighten them within the specified torque range. If any spade
solderless terminal is used, it may be disconnected when the terminal screw comes loose, resulting
in failure.
Check the rated voltage and terminal layout before wiring to the module, and connect the cables
correctly.
Connecting a power supply with a different voltage rating or incorrect wiring may cause a fire or
failure.
Connectors for external connection must be crimped or pressed with the tool specified by the
manufacturer, or must be correctly soldered.
Incomplete connections could result in short circuit, fire, or malfunction.
Prevent foreign matter such as dust or wire chips from entering the module.
Such foreign matter can cause a fire, failure, or malfunction.
A-5
[Wiring Precautions]
DANGER
A protective film is attached to the top of the module to prevent foreign matter, such as wire chips,
from entering the module during wiring.
Do not remove the film during wiring.
Remove it for heat dissipation before system operation.
Shut off the external power supply for the system in all phases before cleaning the module or
retightening the terminal screws or module fixing screws.
Failure to do so may result in electric shock.
Undertightening the terminal screws can cause short circuit or malfunction.
Overtightening can damage the screw and/or module, resulting in drop, short circuit, or malfunction.
A-6
[Startup and Maintenance Precautions]
CAUTION
Before performing online operations (especially, program modification, forced output, and operation
status change) for the running CPU module from the peripheral connected, read relevant manuals
carefully and ensure the safety.
Improper operation may damage machines or cause accidents.
Use any radio communication device such as a cellular phone or PHS (Personal Handy-phone
System) more than 25cm (9.85 inches) away in all directions from the programmable controller.
Failure to do so may cause malfunction.
Shut off the external power supply for the system in all phases before mounting or removing the
module. Failure to do so may cause the module to fail or malfunction.
A module can be replaced online (while power is on) on any MELSECNET/H remote I/O station or in
the system where a CPU module supporting the online module change function is used.
Note that there are restrictions on the modules that can be replaced online, and each module has its
predetermined replacement procedure.
For details, refer to this manual and the manual for the corresponding module.
After the first use of the product, do not mount/remove the module to/from the base unit, and the
terminal block to/from the module more than 50 times (IEC 61131-2 compliant) respectively.
Exceeding the limit of 50 times may cause malfunction.
Before handling the module, touch a grounded metal object to discharge the static electricity from
the human body.
Failure to do so may cause the module to fail or malfunction.
A-7
[Disposal Precautions]
CAUTION
When disposing of this product, treat it as industrial waste.
When disposing of batteries, separate them from other wastes according to the local regulations.
(For details of the Battery Directive in EU countries, refer to Appendix 4.)
[Transportation Precautions]
CAUTION
When transporting lithium batteries, follow the transportation regulations.
(For details of the regulated models, refer to Appendix 3.)
A-8
REVISIONS
*The manual number is given on the bottom left of the back cover.
Print date Manual number Revision
Jun., 2004 SH(NA)-080483ENG-A First edition
Dec., 2004 SH(NA)-080483ENG-B Addition
Section 12.2.21
Partial correction
CONTENTS, Section 2.1.5, 5.2.1, 5.3, 9.1.2, 9.2.4, 10.3.1, 10.4, 10.5, 10.6.1,
11.1, 11.3.1, 11.3.2, 11.4, 11.5, 12.2.1, 12.3.1, 12.3, 12.6, 12.7, Appendix 2.1,
Appendix 2.2, Appendix 3.1
May, 2005 SH(NA)-080483ENG-C Addition
Section 12.2.22, 12.2.23, 12.2.24, Appendix 2.4, Appendix 2.5
Partial correction
GENERIC TERMS AND ABBREVIATIONS, Chapter 1, Section 2.1.1, 2.1.2,
2.1.5, 2.2, 4.1, 5.2.1, 5.2.2, 5.3, 6.1.4, 7.2.1, 7.2.2, 9.1.3, 10.2, 10.3.2, 10.6.2,
11.3.1, 11.3.2, 11.3.3, 11.3.4, 11.4, 11.5, 12.2.1, 12.2.2, 12.2.3, 12.2.5, 12.2.7,
12.3.2, 12.4.1, 12.4.2, 12.6, 12.7, Appendix 1.5, Appendix 2.2, Appendix 2.3,
Appendix 3
Aug., 2005 SH(NA)-080483ENG-D Partial correction
SAFETY PRECAUTIONS, GENERIC TERMS AND ABBREVIATIONS, Section
2.1.1, 4.1, 5.1, 5.2.1, 5.2.2, 5.3, 7.1.2, 10.6.2, 11.3.3, 12.2.2, 12.3.1, 12.4.2, 12.6,
12.7, Appendix 1.2
Apr., 2006 SH(NA)-080483ENG-E Model addition
QA65B,QA68B
Partial correction
GENERIC TERMS AND ABBREVIATIONS, Section 1.1, 2.1.1, 2.1.2, 5.1, 5.2.1,
5.2.3, 6.1.1, 6.1.2, 9.1.3, 9.1.5, 9.1.6, 10.3.1, 10.3.3, 12.3.2, Appendix 1.4,
Appendix 2.2, 2.4, Index
Aug., 2006 SH(NA)-080483ENG-F Partial correction
SAFETY PRECAUTIONS, Section 2.1.5, 6.1.1, 6.1.2, 9.1.5, 10.2, 10.3.1, 12.5.1,
12.5.2, Appendix 1.3, 1.4
Sep., 2006 SH(NA)-080483ENG-G Partial correction
GENERIC TERMS AND ABBREVIATIONS, Section 7.1.2, 9.1.6, 10.3.1, 11.3.3,
12.3.4, 12.3.6, 12.7
Oct., 2006 SH(NA)-080483ENG-H Addition
Section 12.3.11
Partial correction
SAFETY PRECAUTIONS, Section 1.1, 2.1.1, Chapter3, Section 4.1, 4.2.1, 5.1,
5.2.1, 5.2.2, 5.3, 6.1.1, 9.1.1, 9.1.2, 9.1.3, 9.1.5, 9.2.3, 9.2.5, 10.2, 10.3.1, 10.6.1,
10.6.2, 11.3.1, 11.4, 11.5, 12.2.19, 12.3.2, 12.3.3, 12.3.5, 12.3.10, 12.6, 12.7,
Appendix 1.2, Appendix 2.2
This manual confers no industrial property rights or any rights of any other kind, nor does it confer any patent licenses. Mit-
subishi Electric Corporation cannot be held responsible for any problems involving industrial property rights which may occur
as a result of using the contents noted in this manual.
C 2004 MITSUBISHI ELECTRIC CORPORATION
A-9
Print date Manual number Revision
Apr., 2007 SH(NA)-080483ENG-I Universal model QCPU model addition,
Revision involving High Performance model QCPU and Redundant CPU serial
No.09012
Model addition
Q02UCPU, Q03UDCPU, Q04UDHCPU, Q06UDHCPU, Q65WRB
Addition
Section 4.4, 12.2.25
Partial correction
SAFETY PRECAUTIONS, ABOUT MANUALS,
GENERIC TERMS AND ABBREVIATIONS, Chapter 1, Section 1.1, 2.1, 2.1.1,
2.1.2, 2.1.3, 2.1.4, 2.1.5, 2.2, 4.1, 4.2.2, 4.3.2, 5.1, 5.2.1, 5.2.3, 6.1.1, 6.1.2,
6.1.3, 6.1.4, 7.1.1, 7.1.2, 7.1.3, 7.1.5, 7.1.6, 7.1.7, 7.2.2, 9.1.3, 9.1.5, 10.3.1,
10.3.3, 10.4, 10.6.1, 10.6.2, 11.1, 11.2, 11.3.1, 11.3.2, 11.3.3, 11.3.4, 11.4, 11.5,
12.1, 12.2.1, 12.2.2, 12.2.3, 12.2.10, 12.2.15, 12.2.21, 12.2.22, 12.2.23, 12.3.1,
12.3.2, 12.3.3, 12.3.4, 12.3.5, 12.3.6, 12.3.7, 12.3.8, 12.3.9, 12.3.11, 12.4.1,
12.5.1, 12.5.2, 12.6, 12.7, Appendix 1.1, Appendix 1.3, Appendix 1.4,
Appendix 2.2, Appendix 3
Jan., 2008 SH(NA)-080483ENG-J Revision due to the support for Redundant CPU serial number 09102
Model addition
QA6ADP, Q64PN
Addition
Appendix 2.6
Partial correction
SAFETY PRECAUTION, GENERIC TERMS AND ABBREVIATIONS,
Section 1.1, 2.1.1, 2.1.2, 2.1.3, 2.1.5, 4.1, 4.2.1, 4.3.1, 4.4.1, Chapter 3,
Section 5.1, 5.2.1, 5.2.2, 5.3, 6.1.2, 6.1.3, 9.1.1, 9.1.2, 9.1.5, 9.1.6, 9.2.3, 10.1,
10.3.1, 10.3.3, 10.6.1, 10.6.2, 11.2, 11.3.1, 11.3.4, 12.2.13, 12.2.22, 12.3.3,
12.3.4, 12.3.5, 12.3.9, 12.4.1, 12.4.2, 12.5.1, 12.5.2, 12.6, 12.7, Appendix 1.2,
Appendix 2.5, Index
Mar., 2008 SH(NA)-080483ENG-K Model addition
Q13UDHCPU, Q26UDHCPU
Addition
Section 11.3.1
Partial correction
GENERIC TERMS AND ABBREVIATIONS, PRECAUTIONS FOR USE,
Chapter 1, Section 1.1, 2.1.2, 2.1.4, 2.1.5, 4.1, 4.4.1, 5.2.1, 5.3, 6.1.1, 6.1.3,
7.1.1, 7.1.6, 7.2.1, 10.3.1, 11.1, 11.2, 11.3.1, 11.3.2, 11.3.4, 12.3.1, 12.3.3,
12.3.4, 12.3.5, 12.3.6, 12.6, 12.7, Appendix 1.1, Appendix 2.2, Appendix 2.3,
Appendix 2.4, Appendix 2.5, Appendix 2.6
A - 10
Print date Manual number Revision
May, 2008 SH(NA)-080483ENG-L Revision due to the addition of Process CPU and Universal model QCPU.
Addition
Section 12.2.26, 12.2.27, 12.2.28, 12.2.29, 12.2.30, 12.2.31, 12.5.2
Model addition
Chapter 1, Section 1.1, 2.1.2, 2.1.3, 2.1.4, 2.1.5, 2.2, 4.1, 4.3.1, 4.4.1, 6.1.3,
7.1.2, 11.3.2, 12.2.1, 12.3.3, 12.3.4, 12.3.5, 12.3.6, 12.3.9, 12.6, 12.7,
Appendix1.1, Appendix 2, Appendix 2.4, Appendix 2.5, Appendix 2.6
Sep., 2008 SH(NA)-080483ENG-M Partial correction
SAFETY PRECAUTION, Section 1.1, 2.2, 7.1.6, 7.2.1, 9.1.3, 9.1.5, Appendix 2.6
Addition
Appendix 4
Dec., 2008 SH(NA)-080483ENG-N Universal model QCPU model additions
Revision and overall review for support to the Universal model QCPU serial
number "10101".
Model addition
Q00UJCPU, Q00UCPU, Q01UCPU, Q10UDHCPU, Q10UDEHCPU,
Q20UDHCPU, Q20UDEHCPU
Mar., 2009 SH(NA)-080483ENG-O Revision due to the support for Universal model QCPU serial number "11012".
Partial correction
SAFETY PRECAUTIONS, INTRODUCTION, GENERIC TERMS AND
ABBREVIATIONS, Section 1.1, 2.1.3, 2.1.4, 4.1.3, 4.1.5, 4.3.1, 4.3.2, 4.3.5,
4.4.1, 5.2.1, 5.2.3, 5.2.4, 5.3, 6.1.1, 6.1.2, 7.1.2, 7.1.6, CHAPTER 8, Section
9.1.2, 9.1.3, 9.1.5, 9.2, 9.2.4, 10.1, 10.3.1, 10.3.3, CHAPTER 11, Section 11.3.1,
11.3.2, 11.3.3, 12.1, 12.2.1 to 12.2.12, 12.2.14 to 12.2.36, 12.3.11, 12.5.1, 12.6,
12.7, 12.8, Appendix 2.6
Addition
12.2.37 to 12.2.39
Jul., 2009 SH(NA)-080483ENG-P Revision because of function support by the Universal model QCPU having a
serial number "11043" or later
Partial correction
GENERIC TERMS AND ABBREVIATIONS, Section 2.1.3, 2.1.6, 7.2.2, 11.3.1,
11.3.2, 11.3.3, 11.4, 11.5, 12.3.3, 12.3.4, 12.4, 12.7, 12.8, Appendix 2.6
A - 11
Memo
A - 12
INTRODUCTION
This manual provides hardware specifications, maintenance and inspection of the system, and troubleshooting of the CPU
modules, power supply modules, and base units required for operating the Q series programmable controllers.
1) Chapter 1 and 2 Describes outline of the CPU module and the system configuration to help users
understand features of the CPU module and fundamentals of system configuration.
2) Chapter 3 through 7 Describes the general specifications of operating environments for the CPU module,
power supply module, and base units and performance specifications of respective
modules.
3) Chapter 8 through 12 Describes overall maintenance such as installation of the CPU module, daily inspec-
tions, and troubleshooting.
Remark
This manual does not describe the functions of the CPU module.
For the functions, refer to the following.
Manuals for the CPU module used. (Function Explanation, Program Fundamentals)
A - 13
CONTENTS
SAFETY PRECAUTIONS...................................................................................................................... A - 1
REVISIONS ........................................................................................................................................... A - 9
INTRODUCTION ................................................................................................................................... A - 13
MANUALS ............................................................................................................................................. A - 19
MANUAL PAGE ORGANIZATION ......................................................................................................... A - 22
GENERIC TERMS AND ABBREVIATIONS .......................................................................................... A - 24
USAGE NOTE ....................................................................................................................................... A - 27
4.3 High Performance Model QCPU, Process CPU and Redundant CPU .................................. 4 - 34
4.3.1 Part names ........................................................................................................................ 4 - 34
4.3.2 Switch operation after writing program.............................................................................. 4 - 40
4.3.3 Reset operation ................................................................................................................. 4 - 41
4.3.4 Latch clear operation......................................................................................................... 4 - 41
4.3.5 Automatic writing to standard ROM................................................................................... 4 - 42
A - 14
4.4.1 Part names ........................................................................................................................ 4 - 43
4.4.2 Switch operation after writing a program........................................................................... 4 - 53
4.4.3 Reset operation ................................................................................................................. 4 - 54
4.4.4 Latch clear operation......................................................................................................... 4 - 55
A - 15
CHAPTER9 EMC AND LOW VOLTAGE DIRECTIVES 9-1 to 9-18
9.1 Requirements for Compliance with the EMC Directive .......................................................... 9 - 1
9.1.1 Standards relevant to the EMC Directive .......................................................................... 9 - 2
9.1.2 Installation instructions for EMC Directive......................................................................... 9 - 3
9.1.3 Cables ............................................................................................................................... 9 - 4
9.1.4 Power supply part of the power supply module, Q00JCPU, and Q00UJCPU................... 9 - 8
9.1.5 When using MELSEC-A series modules........................................................................... 9 - 8
9.1.6 Others ............................................................................................................................... 9 - 13
10.4 How to set the Base Number for the Extension Base Unit .................................................... 10 - 30
10.5 Connection and Disconnection of Extension Cable ............................................................... 10 - 36
10.6 Wiring..................................................................................................................................... 10 - 39
10.6.1 Wiring precautions ............................................................................................................ 10 - 39
10.6.2 Connecting to the power supply module ........................................................................... 10 - 44
A - 16
12.1 Troubleshooting Basics.......................................................................................................... 12 - 1
12.2 Troubleshooting ..................................................................................................................... 12 - 3
12.2.1 Troubleshooting flowchart ................................................................................................. 12 - 3
12.2.2 When the ERR. terminal (negative logic) has turned off (opened).................................... 12 - 5
12.2.3 When the LIFE OUT terminal (negative logic) has turned off (opened) ............................ 12 - 9
12.2.4 When the MODE LED does not turn on ............................................................................ 12 - 10
12.2.5 When the MODE LED is flickering .................................................................................... 12 - 11
12.2.6 When the POWER LED has turned off ............................................................................. 12 - 12
12.2.7 When the POWER LED is flickering in orange ................................................................. 12 - 14
12.2.8 When the POWER LED has turned on in red ................................................................... 12 - 15
12.2.9 When the LIFE LED has turned off ................................................................................... 12 - 16
12.2.10 When the LIFE LED has turned on in red ......................................................................... 12 - 17
12.2.11 When the LIFE LED is flickering in red ............................................................................. 12 - 17
12.2.12 When the RUN LED has turned off ................................................................................... 12 - 18
12.2.13 When the RUN LED is flickering ....................................................................................... 12 - 19
12.2.14 When the ERR. LED has turned on or is flickering ........................................................... 12 - 19
12.2.15 When the USER LED has turned on ................................................................................. 12 - 20
12.2.16 When the BAT. LED has turned on or is flickering............................................................. 12 - 20
12.2.17 When the BOOT LED is flickering ..................................................................................... 12 - 21
12.2.18 When the LEDs of the output module do not turn on ........................................................ 12 - 22
12.2.19 When output load of the output module does not turn on ................................................. 12 - 23
12.2.20 When unable to read a program ....................................................................................... 12 - 24
12.2.21 When unable to write a program ....................................................................................... 12 - 25
12.2.22 When program is rewritten unintentionally ........................................................................ 12 - 26
12.2.23 When unable to perform boot operation from the memory card ....................................... 12 - 27
12.2.24 When “UNIT VERIFY ERR.” has occurred........................................................................ 12 - 29
12.2.25 When “CONTROL BUS ERR.” has occurred .................................................................... 12 - 30
12.2.26 When the CPU module does not start............................................................................... 12 - 31
12.2.27 When “OPERATION ERROR” has occurred at execution of the S(P).SFCSCOMR and
S(P).SFCTCOMR instructions. ............................................................................. 12 - 32
12.2.28 When comments cannot be read at execution of the S(P).SFCSCOMR and S(P).SFCTCOMR
instructions ...................................................................................................... 12 - 33
12.2.29 When “PARAMETER ERROR” has occurred at power on or reset................................... 12 - 35
12.2.30 When the CPU cannot communicate with GX Developer ................................................. 12 - 39
12.2.31 When Ethernet communication is not available other than by direct connection to GX Developer
.................................................................................................................... 12 - 41
12.2.32 When Ethernet communication with the target device is not available ............................. 12 - 43
12.2.33 When Ethernet communication is not available by direct connection to GX Developer.... 12 - 48
12.2.34 When Ethernet communication with CPU module is slow or unstable.............................. 12 - 51
12.2.35 When an error has occurred during MC protocol communication ..................................... 12 - 54
12.2.36 When clock data cannot be set by SNTP.......................................................................... 12 - 57
12.2.37 When unable to receive data on the external device side by the Socket communication function
.................................................................................................................... 12 - 59
12.2.38 When unable to receive data by the Socket communication function ............................... 12 - 60
12.2.39 When open process of the Socket communication function does not complete ............... 12 - 61
A - 17
12.3.2 Reading an error code ...................................................................................................... 12 - 63
12.3.3 Error code list (1000 to 1999)............................................................................................ 12 - 64
12.3.4 Error code list (2000 to 2999)............................................................................................ 12 - 77
12.3.5 Error code list (3000 to 3999)............................................................................................ 12 - 95
12.3.6 Error code list (4000 to 4999)............................................................................................ 12 - 112
12.3.7 Error code list (5000 to 5999)............................................................................................ 12 - 127
12.3.8 Error code list (6000 to 6999)............................................................................................ 12 - 129
12.3.9 Error code list (7000 to 10000).......................................................................................... 12 - 139
12.3.10 Canceling of Errors ........................................................................................................... 12 - 144
12.3.11 Error codes returned to request source during communication with CPU module............ 12 - 146
A - 18
MANUALS
To understand the main specifications, functions, and usage of the CPU module, refer to the basic manuals.
Read other manuals as well when using a different type of CPU module and its functions.
Order each manual as needed, referring to the following lists.
The numbers in the "CPU module" and the respective modules are as follows.
Number CPU module
1) Basic model QCPU
2) High Performance model QCPU
3) Process CPU
4) Redundant CPU
5) Universal model QCPU
Programming manual
QCPU Programming Manual (Common
How to use sequence instructions, basic
Instructions)
instructions, and application instructions
< SH-080809ENG (13JW10) >
A - 19
Manual name CPU module
Description
< Manual number (model code) > 1) 2) 3) 4) 5)
System configuration, performance
QCPU (Q Mode)/QnACPU Programming
specifications, functions, programming,
Manual (SFC)
debugging, and error codes for SFC
< SH-080041 (13JF60) >
(MELSAP3) programs
QCPU (Q Mode) Programming Manual Programming methods, specifications,
(MELSAP-L) and functions for SFC (MELSAP-L)
< SH-080076 (13JF61) > programs
QCPU (Q Mode) Programming Manual
Programming methods using structured
(Structured Text)
languages
< SH-080366E (13JF68) >
QCPU (Q Mode) / QnACPU Programming
Manual (PID Control Instructions) Dedicated instructions for PID control
< SH-080040 (13JF59) >
QnPHCPU/QnPRHCPU Programming
Manual (Process Control Instructions) Dedicated instructions for process control
< SH-080316E (13JF67) >
A - 20
Other relevant manuals
A - 21
MANUAL PAGE ORGANIZATION
The detailed explanation of "Note . " is The section in this manual or The chapter of the current page can be
provided under the corresponding another relevant manual that can easily identified by this indication on the
"Note . " at the bottom of the page. be referred to is shown with . right side.
Icons
High
Basic model Universal model Description
Performance Process CPU Redundant CPU
QCPU QCPU
model QCPU
Icons indicate that
specifications
High
Basic performance Process Redundant Universal described on the
page contain
some precautions.
A - 22
In addition, this manual uses the following types of explanations.
In addition to description of the page, notes or functions that require special attention are described here.
Remark
The reference related to the page or useful information are described here.
A - 23
GENERIC TERMS AND ABBREVIATIONS
Unless otherwise specified, this manual uses the following generic terms and abbreviations.
* indicates a part of the model or version.
(Example): Q33B, Q35B, Q38B, Q312B Q3 B
Generic term/abbreviation Description
Series
Q series Abbreviation for Mitsubishi MELSEC-Q series programmable controller
Generic term for compact types of Mitsubishi MELSEC-A Series Programmable
AnS series
Controller
Generic term for large types of Mitsubishi MELSEC-A Series Programmable
A series
Controller
CPU module type
Generic term for the Basic model QCPU, High Performance model QCPU,
CPU module
Process CPU, Redundant CPU, Universal model QCPU
Basic model QCPU Generic term for the Q00JCPU, Q00CPU, and Q01CPU
High Performance model QCPU Generic term for the Q02CPU, Q02HCPU, Q06HCPU, Q12HCPU, Q25HCPU
Process CPU Generic term for the Q02PHCPU, Q06PHCPU, Q12PHCPU, Q25PHCPU
Redundant CPU Generic term for the Q12PRHCPU and Q25PRHCPU
Generic term for the Q00UJCPU, Q00UCPU, Q01UCPU, Q02UCPU,
Q03UDCPU, Q04UDHCPU, Q06UDHCPU, Q10UDHCPU, Q13UDHCPU,
Universal model QCPU
Q20UDHCPU, Q26UDHCPU, Q03UDECPU, Q04UDEHCPU, Q06UDEHCPU,
Q10UDEHCPU, Q13UDEHCPU, Q20UDEHCPU, and Q26UDEHCPU
Generic term for the Q03UDECPU, Q04UDEHCPU, Q06UDEHCPU,
Built-in Ethernet port QCPU
Q10UDEHCPU, Q13UDEHCPU, Q20UDEHCPU, and Q26UDEHCPU
Generic term for Mitsubishi motion controllers, Q172CPUN, Q173CPUN,
Motion CPU Q172HCPU, Q173HCPU, Q172CPUN-T, Q173CPUN-T, Q172HCPU-T,
Q173HCPU-T, Q172DCPU, and Q173DCPU
Generic term for MELSEC-Q series-compatible PC CPU module,
PC CPU module
PPC-CPU852(MS)-512, manufactured by CONTEC Co., Ltd.
Generic term for the Q06CCPU-V, Q06CCPU-V-B, and Q12DCCPU-V C
C Controller module
Controller modules
CPU module model
Generic term for the Q00UJCPU, Q00UCPU, Q01UCPU, Q02UCPU,
QnU(D)(H)CPU Q03UDCPU, Q04UDHCPU, Q06UDHCPU, Q10UDHCPU, Q13UDHCPU,
Q20UDHCPU, and Q26UDHCPU
Base unit type
Generic term for the main base unit, extension base unit, slim type main base
unit, redundant power main base unit, redundant power extension base unit,
Base unit
redundant power extension base unit, and multiple CPU high speed main base
unit
Main base unit Generic term for the Q3 B, Q3 SB, Q3 RB, and Q3 DB
Generic term for the Q5 B, Q6 B, Q6 RB, Q6 WRB, QA1S6 B, QA6 B,
Extension base unit
and QA6ADP+A5 B/A6 B
Slim type main base unit Another name for the Q3 SB
Redundant power main base unit Another name for the Q3 RB
Redundant power extension base
Another name for the Q6 RB
unit
Redundant type extension base unit Another name for the Q6 WRB
A - 24
Generic term/abbreviation Description
Redundant type extension base
Another name for the Q6 WRB
unit
Multiple CPU high speed main
Another name for the Q3 DB
base unit
Generic term for the redundant power main base unit, redundant power
Redundant base unit
extension base unit, and redundant type extension base unit
Base unit model
Q3 B Generic term for the Q33B, Q35B, Q38B, and Q312B main base units
Q3 SB Generic term for the Q32SB, Q33SB, and Q35SB slim type main base units
Q3 RB Another name for the Q38RB redundant power main base unit
Q3 DB Generic term for the Q38DB and Q312DB multiple CPU high speed main base units
Q5 B Generic term for the Q52B and Q55B extension base units
Q6 B Generic term for the Q63B, Q65B, Q68B, and Q612B extension base units
Q6 RB Another name for the Q68RB redundant power extension base unit
Q6 WRB Another name for Q65WRB extension base unit for redundant system
QA1S6 B Generic term for the QA1S65B and QA1S68B
QA6 B Generic term for the QA65B and QA68B extension base units
A5 B Generic term for the A52B, A55B, and A58B extension base units
A6 B Generic term for the A62B, A65B, and A68B extension base units
QA6ADP+A5 B/A6 B Abbreviation for a large type extension base unit where the QA6ADP is mounted
Power supply module
Generic term for the Q series power supply module, slim type power supply mod-
Power supply module
ule, and redundant power supply module
Generic term for the Q61P-A1, Q61P-A2, Q61P, Q61P-D, Q62P, Q63P, Q64P, and
Q series power supply module
Q64PN power supply modules
AnS series power supply module Generic term for the A1S61PN, A1S62PN, and A1S63 power supply modules
Generic term for the A61P, A61PN, A62P, A63P, A68P, A61PEU, and A62PEU
A series power supply module
power supply modules
Slim type power supply module Abbreviation for the Q61SP slim type power supply module
Redundant power supply module Generic term for the Q63RP and Q64RP redundant power supply modules
Life detection power supply
Abbreviation for the Q61P-D life detection power supply module]
module
Network
MELSECNET/H Abbreviation for the MELSECNET/H network system
Ethernet Abbreviation for the Ethernet network system
CC-Link Abbreviation for the Control & Communication Link
Memory card
Memory card Generic term for the SRAM card, Flash card, and ATA card
Generic term for the Q2MEM-1MBS, Q2MEM-2MBS, Q3MEM-4MBS, and
SRAM card
Q3MEM-8MBS SRAM cards
Flash card Generic term for the Q2MEM-2MBF and Q2MEM-4MBF Flash cards
Generic term for the Q2MEM-8MBA, Q2MEM-16MBA, and Q2MEM-32MBA ATA
ATA card
cards
A - 25
Generic term/abbreviation Description
Others
Product name for SW D5C-GPPW-E GPP function software package compatible
GX Developer
with the Q series
PX Developer Product name for SW D5C-FBDQ process control FBD software package
QA6ADP Abbreviation for the QA6ADP QA conversion adapter module
Generic term for the QC05B, QC06B, QC12B, QC30B, QC50B, and QC100B
Extension cable
extension cables
Generic term for the QC10TR and QC30TR tracking cables for the Redundant
Tracking cable
module
Generic term for the Q6BAT, Q7BAT, and Q8BAT CPU module batteries,
Battery
Q2MEM-BAT SRAM card battery, and Q3MEM-BAT SRAM card battery
Generic term for Mitsubishi Graphic Operation Terminal, GOT-A*** series, GOT-F***
GOT
series, and GOT1000 series
A - 26
USAGE NOTE
Memory must be formatted using GX Developer before first use of the CPU module.
For details of memory formatting, refer to the following.
Operating manual for GX Developer
Batteries
(1) When resuming operation with the CPU module which has been stored without battery:
The CPU module memory must be formatted using GX Developer. ( Section 11.4)
(2) When resuming operation with the CPU module in which installed battery life had expired during storage:
The CPU module memory must be formatted using GX Developer. ( Section 11.5)
A - 27
CHAPTER1 OVERVIEW
1.1 Features
1-1
CHAPTER1 OVERVIEW
1.1 Features
Q20UD(E)HCPU 200K steps
Q26UD(E)HCPU 260K steps
1-2
(3) High speed processing
High speed processing has been achieved.
LD instruction processing
CPU module type
speed
Q00JCPU 200ns
Basic model QCPU Q00CPU 160ns
Q01CPU 100ns
Q02CPU 79ns
High Performance model QCPU Q02HCPU, Q06HCPU, Q12HCPU,
Q25HCPU
Q02PHCPU, Q06PHCPU, Q12PHCPU, 34ns
Process CPU
Q25PHCPU
Redundant CPU Q12PRHCPU, Q25PRHCPU
Q00UJCPU 120ns
Q00UCPU 80ns
Q01UCPU 60ns
Q02UCPU 40ns
Universal model QCPU
Q03UD(E)CPU 20ns
Q04UD(E)HCPU, Q06UD(E)HCPU,
Q10UD(E)HCPU, Q13UD(E)HCPU, 9.5ns
Q20UD(E)HCPU, Q26UD(E)HCPU
The MELSEC Q series base unit high-speed system bus has achieved faster access to an intelligent function
module and link refresh with a network module.
1-3
CHAPTER1 OVERVIEW
Q25HCPU(USB) 12
4
Q25HCPU(RS-232) 30
Q2ASHCPU 86 5
A2USHCPU-S1 94
0 10 20 30 40 50 60 70 80 90 100 (Unit:s)
Figure 1.1 26K step program transfer time 6
(5) AnS/A series I/O modules and special function modules are available 7
The AnS/A series compatible extension base units (QA1S6 B, QA6 B and QA6ADP+A5 B/A6 B) allow the
High Performance model QCPU to use the AnS/A series I/O modules and special function modules.
8
(6) Saved space by downsizing
The installation space for the Q series has been reduced by approx. 60% compared with the AnS series.
1.1 Features
AnS series
98mm (3.86inch)
Q series
(depth:98mm(3.86inch))
5 Slot Main Base Unit 245mm(9.65inch)
Figure 1.2 Installation area comparison between Q series and AnS series
1-4
(7) Connection of up to 7 extension base units.
Up to seven extension base units can be connected to the Q series CPU module.
The overall extension cable length is 13.2m (43.31feet), which allows flexible layout of base units.
For the High Performance model QCPU, the number of usable file register points differs depending on the function version
and serial number.
For details, refer to Appendix 2.2.
Note1
Note1.1 Basic
The Basic model QCPU, Q00(J)CPU, and Q01UCPU do not support memory cards.
1-5
CHAPTER1 OVERVIEW
Forced on and off of external input and output is available using GX Developer even when the CPU module is
4
running or program is being processed.
Also, wiring test and operation test can be conducted without halting the CPU module by forcibly turning on or off
the I/O. 5
7
(12)Remote I/O network of MELSECNET/H Note1.2
A MELSECNET/H remote I/O system can be configured by installing a MELSECNET/H remote master station.
8
● The remote password can be set up when the Ethernet module, serial communication module, or modem interface
1.1 Features
module of function version B or later is used.
● The MELSECNET remote I/O network can be implemented when the MELSECNET/H network module of function
version B or later is used.
Note1
Note1.2 Basic
The Basic model QCPU does not support the following functions.
• Automatic writing into the standard ROM
• Forced on/off of the external I/O
• MELSECNET/H remote I/O network
Note1.3 Universal
The Universal model QCPU does not support the following function.
• Parameter setting of automatic write to standard ROM
1-6
(13)Supporting the multiple CPU system
Multiple CPU systems can be constructed in combination with CPU modules, motion CPU(s), and PC CPU
module(s).
For details of the multiple CPU system, refer to the following.
QCPU User's Manual (Multiple CPU System)
The Built-in Ethernet port QCPU module allows direct connections to Ethernet.
For details of the functions, refer to the following.
QnUCPU User's Manual (Communication via Built-in Ethernet Port)
Note1
Note1.4 Universal
1-7
CHAPTER2 SYSTEM CONFIGURATION
This section describes system configurations for a single CPU system with the Basic model QCPU, High Performance
3
model QCPU, Process CPU, or Universal module, and a system configuration when using GOT by bus connection.
For a multiple CPU system and redundant system (when using the Redundant CPU), refer to the following.
QCPU User's Manual (Multiple CPU System)
4
QnPRHCPU User's Manual (Redundant System)
2-1
2.1.1 Overall configuration
Memory card
Extension cable
Power supply module/I/O module/Intelligent function module/Special function module
2-2
CHAPTER2 SYSTEM CONFIGURATION
*1: The Q00JCPU does not require a power supply module and the main base unit since the module is an integrated combination of a power 8
supply module and the main base unit.
2-3
(2) High Performance model QCPU
Table2.2 Configuration with the High Performance model QCPU
*1: The A/AnS series extension base units are applicable only when the main base unit (Q33B, Q35B, Q38B, Q312B) is used.
2-4
CHAPTER2 SYSTEM CONFIGURATION
2-5
2.1.3 Precautions for system configuration
This section explains restrictions on configuring a system with the Q series CPU module.
*1: The number is the total of the CC-Link IE controller network module and MELSECNET/H network module.
*2: Applicable to the function version B or later.
*3: The number indicates interrupt modules with no interrupt pointer setting.
No limitation is placed when the interrupt pointer settings have been completed.
*4: For the applicable GOT models, refer to the following.
GOT-A900 Series User's Manual (GT Work2 Version2/GT Designer2 Version2 Compatible Connection System
Manual)
GOT1000 Series Connection Manual
2-6
CHAPTER2 SYSTEM CONFIGURATION
(b) When using the High Performance model QCPU or Process CPU 1
Table2.6 Applicable number of modules (units)
*1: Only the High Performance model QCPU whose serial number (first five digits) is "09012" or later and Process CPU whose
serial number (first five digits) is "10042" or later can be used.
*2: The following indicates the number of modules that can be controlled with the CC-Link network parameter set by GX
Developer.
• The CPU module whose serial number (first five digits) is "08031" or earlier: Up to four modules
• The CPU module whose serial number (first five digits) is "08032" or later: Up to eight modules
When setting parameters with CC-Link dedicated instructions, the number of modules to install is not limited.
For the CC-Link system master/local modules whose parameters can be set by the dedicated instructions, refer to the
following.
CC-Link System Master/Local Module User's Manual
*3: Applicable only when the High Performance model QCPU is used.
*4: For applicable GOT modules, refer to the following.
GOT-A900 Series User's Manual (GT Work2 Version2/GT Designer2 Version2 Version2 Compatible Connection
System Manual)
GOT1000 Series Connection Manual
2-7
(c) When using the Redundant CPU
For modules having a limit to the number of mountable modules, refer to the following.
QnPRHCPU User's Manual (Redundant System)
*1: Only the CC-Link IE controller network module whose serial number (first five digits) is "09042" or later can be used.
*2: The number is a total of the CC-Link IE controller network modules and MELSECNET/H network modules.
*3: The applicable number of mountable module for the Q00UJCPU, Q00UCPU, and Q01UCPU is one in total, for the
Q02UCPU is two modules.
*4: Applicable to the function version B or later.
*5: The following indicates the number of modules that can be controlled by the CC-Link network parameter set by GX
Developer.
• Q00UJCPU, Q00UCPU, Q01UCPU: Up to two modules
• Q02UCPU: Up to four modules
• Q03UD(E)CPU, Q04UD(E)HCPU, Q06UD(E)HCPU, Q10UD(E)HCPU
Q13UD(E)HCPU, Q20UD(E)HCPU, Q26UD(E)HCPU: Up to eight modules
When setting parameters with CC-Link dedicated instructions, the number of modules that can be installed is not limited.
For the CC-Link system master/local modules whose parameters can be set with the dedicated instructions, refer to the
following.
CC-Link System Master/Local Module User's Manual
*6: The number indicates interrupt modules that have no interrupt pointer setting.
No limitation is placed when the interrupt pointer settings have been completed.
*7: For the applicable GOT models, refer to the following.
GOT1000 Series Connection Manual
2-8
CHAPTER2 SYSTEM CONFIGURATION
(2) Modules with limitations when using a Built-in Ethernet port QCPU 1
When using a Built-in Ethernet port QCPU, limitations are placed on the module listed in the Table2.8.
CPU 0 1 2 3 4
Number of 16 16 0 16 16
slot points points points point points points
Occupies 1 slot.
Figure 2.2 Number of modules including empty slots
2-9
(4) Precautions for the number of modules to mount
Mount modules within the range of the number of available slots.
When the total number of slots for the main base unit and extension base units exceeds the number of available
slots (for example, six 12-slot base units are used), mount modules only on the available slots so that no error
occurs.
If a module is mounted on a invalid slot, "SP.UNIT LAY ERR." (error code: 2124) occurs.
Q612B
12 13 14 15 16 17 18 19 20 21 22 23 Extension 1
Q612B
24 25 26 27 28 29 30 31 32 33 34 35 Extension 2
Q612B
36 37 38 39 40 41 42 43 44 45 46 47 Extension 3
Q612B
48 49 50 51 52 53 54 55 56 57 58 59 Extension 4
Figure 2.3 Configuration example with the High Performance model QCPU
2 - 10
CHAPTER2 SYSTEM CONFIGURATION
Product Model
*1: Only multidrop link function can be used. The computer link function and printer function cannot be used.
3) The QnA/A series dedicated instructions for the following modules cannot be used.
Rewriting using the FROM or TO instruction is required.
Product Model
High speed counter module A1SD61, A1SD62, A1SD62D(-S1), A1SD62E
MELSECNET/MINI-S3 A1SJ71PT32-S3, A1SJ71T32-S3
Positioning module A1SD75P1-S3(P2-S3/P3-S3)
ID module A1SJ71ID1-R4, A1SJ71ID2-R4
4) System configurations and functions are partially restricted when writing the parameters set under the "High
speed interrupt fixed scan interval" setting.
For the restrictions, refer to the following.
User's manual for the CPU module used (Function Explanation, Program Fundamentals)
2 - 11
5) For restrictions on mounting the A series module on the QA6 B or QA6ADP+A5 B/A6 B, refer to the
following.
QA65B/QA68B Extension Base Unit User's Manual
QA6ADP QA Conversion Adapter Module User's Manual
6) For restrictions on using varying AnS/A series compatible extension base units, refer to Section 10.4.
2 - 12
CHAPTER2 SYSTEM CONFIGURATION
(3) Precautions
8
• When connecting a GOT on the bus, position the GOT in the base subsequent to base units. Do not position
the GOT between base units.
2 - 13
• When using the QA1S6 B as a extension base unit, install the GOT in the base subsequent to the
extension base units but assign the I/O number subsequent to Q6 B/Q5 B.
Extension
stage number I/O number
• When using the QA6 B,QA6ADP+A5 B/A6 B as a extension base unit, the GOT cannot be connected
to the bus.
• Before starting up the CPU module, initialize the GOT (Set up the extension base and slot number in the
GOT setup.) that is to be connected to the bus.
(Set up the extension base and slot number in the GOT setup.)
• Apply the power to the CPU module and GOT by either of the following way.
1) Simultaneously turn on the CPU module and GOT.
2) Turn on the CPU module first, and then the GOT.
• Only the GOT1000, GOT-A900, and GOT-F900 series can be used. (Basic operating systems and
communication driver that are compatible with the Q mode must be installed.)
The GOT800 series, A77GOT, and A64GOT cannot be used.
2 - 14
CHAPTER2 SYSTEM CONFIGURATION
00 to 0F
10 to 1F
20 to 2F
30 to 3F
40 to 4F
.... I/O number 3
Q series
power supply CPU module 4
module
Extension base unit ... The figure shows the configuration when 16-point modules are loaded to each slot.
5
Q68B (8 slots occupied)
5 6 7 8 9 10 11 12
6
C0 to CF
B0 to BF
A0 to AF
50 to 5F
60 to 6F
70 to 7F
80 to 8F
90 to 9F
8
100 to 10F
110 to 11F
E0 to EF
D0 to 0F
F0 to FF
No. of extension stages: 3 No. of extension stages: 3 No. of extension stages: 3 No. of extension stages: 3 No. of extension stages: 3 Set on
slots No.: 0 slots No.: 1 slots No.: 2 slots No.: 3 slots No.: 4 the GOT
side.
Stage extension image for GOT connection viewed from CPU module
18 19 20 21 22 23 24 25 26 27
120 to 12F
130 to 13F
140 to 14F
150 to 15F
160 to 16F
1) 2) 3) 4) 5)
Set to empty in "I/O assignment setting"
of PLC parameter
2 - 15
Note1
Table2.12 Restrictions on the system configuration and applicable base units, extension cables and power supply modules
Applicable extension base Model requiring a Q-series power supply module Q63B, Q65B, Q68B, Q612B
unit Model requiring a AnS series power supply
QA1S65B, QA1S68B
module Note2.2
Note1
Because the Q00JCPU and Q00UJCPU is the CPU module with a power supply module and main base unit
incorporated, the main base unit (Q3 B) and Q series power supply module are not required.
High
Note2.2 performance
2 - 16
CHAPTER2 SYSTEM CONFIGURATION
6
Personal Computer (GX Developer, GX Configurator) RS-232 cable
*1: For the versions of GX Developer and GX Configurator that can be used with the Basic model QCPU, refer to Section
2.1.6.
2 - 17
(2) When using High Performance model QCPU
High Performance model QCPU
Memory card 1
RS-232 cable
Personal Computer
4
(GX Developer, GX Configurator)
USB cable 2, 3
(Connector type B)
2 - 18
CHAPTER2 SYSTEM CONFIGURATION
3
Memory card 1
4
RS-232 cable
5
Personal Computer
(GX Developer, GX Configurator,
PX Developer) 3
USB cable 2
6
(Connector type B)
2 - 19
(4) When using the Universal model QCPU
(a) QnU(D)(H)CPU
Universal model QCPU
Memory card 1
RS-232 cable
Personal Computer
3
(GX Developer, GX Configurator)
USB cable 2
(Connector type miniB)
2 - 20
CHAPTER2 SYSTEM CONFIGURATION
Memory card 1
3
4
4
Ethenet cable
Personal Computer
5
3
(GX Developer, GX Configurator)
USB cable
(Connector type miniB)
2
6
adapter
2 - 21
2.1.6 Applicable softwares
The following table indicates software versions applicable to the system.
Software version
CPU module
GX Developer PX Developer
Basic model QCPU Version 7.00A or later
N/A
High Performance model QCPU Version 4.00A or later
Q02PHCPU
Version 8.68W or later Version 1.18U or later
Q06PHCPU
Process CPU
Q12PHCPU
Version 7.10L or later*1 Version 1.00A or later
Q25PHCPU
Q02UCPU
Q03UDCPU
Version 8.48A or later
Q04UDHCPU
Q06UDHCPU
Q13UDHCPU
Version 8.62Q or later
Q26UDHCPU
Q03UDECPU
Universal model Q04UDEHCPU
N/A
QCPU Q06UDEHCPU Version 8.68W or later
Q13UDEHCPU
Q26UDEHCPU
Q00UJCPU
Q00UCPU
Q01UCPU Version 8.76E or later
Q10UD(E)HCPU
Q20UD(E)HCPU
2 - 22
CHAPTER2 SYSTEM CONFIGURATION
(a) When Basic model QCPU, Hogh Performance model QCPU, and Process QCPU are 3
used
Table2.14 Applicable GX Configurator
4
Software version
CPU module
Product name Version
GX Configurator-AD Version 1.10L or later 5
GX Configurator-DA Version 1.10L or later
GX Configurator-SC Version 1.10L or later
GX Configurator-CT Version 1.10L or later 6
GX Configurator-TI Version 1.10L or later
GX Configurator-TC Version 1.10L or later
Basic modelQCPU
GX Configurator-FL Version 1.10L or later 7
GX Configurator-QP Version 2.10L or later
GX Configurator-PT Version 1.10L or later
GX Configurator-AS Version 1.13P or later 8
GX Configurator-MB Version 1.00A or later
GX Configurator-DN Version 1.10L or later
GX Configurator-AD SW0D5C-QADU 00A or later
2 - 23
(b) When Universal model QCPU is used
Table2.15 Applicable GX Configurator
*1: The software can be used by installing GX Developer Version 8.48A or later
*2: The software can be used by installing GX Developer Version 8.62Q or later
*3: The software can be used by installing GX Developer Version 8.68W or later
*4: The software can be used by installing GX Developer Version 8.78G or later
*5: The software can be used by connecting USB
2 - 24
CHAPTER2 SYSTEM CONFIGURATION
4
Serial number (first 5 digits)
function version
5
Relevant regulation standards
6
Figure 2.12 Plate rated
090911090910001-B
Serial number
2 - 25
Remark
Attaching a serial number label to the front of each Redundant CPU was started from March 2008.
However, some of the modules manufactured at the beginning of it may not have the label.
(3) Checking on the System monitor screen (Product information list screen)
To display the screen for checking the serial number and function version, select [Diagnostics] [System
monitor] and click the Product Inf. List button in GX Developer.
On the screen, the serial number and function version of intelligent function modules can also be checked.
Serial Function Product
number version number
2 - 26
CHAPTER3 GENERAL SPECIFICATIONS
Item Specification
Operating ambient
0 to 55
3
temperature
Storage ambient *3
-25 to 75
temperature
4
Operating ambient
5 to 95%RH *4, non-condensing
humidity
Storage ambient
humidity
5 to 95%RH *4, non-condensing 5
Frequency Acceleration Amplitude Sweep count
Under
intermittent
5 to 9Hz ----
3.5mm
(0.14 inches) 10 times each in 6
Compliant with X, Y, Z directions
Vibration resistance JIS B 3502 and vibration 9 to 150Hz 9.8m/s2 ----
IEC 61131-2
Under continuous 5 to 9Hz ----
1.75mm
(0.069 inches) ----
7
vibration
9 to 150Hz 4.9m/s2 ----
Shock resistance Compliant with JIS B 3502, IEC 61131-2 (147 m/s2, 3 times in each of 3 directions X, Y, Z) 8
Operating ambience No corrosive gases
*1: This indicates the section of the power supply to which the equipment is assumed to be connected between the public electrical power
distribution network and the machinery within premises. Category II applies to equipment for which electrical power is supplied from fixed
facilities.
The surge voltage withstand level for up to the rated voltage of 300 V is 2500 V.
*2: This index indicates the degree to which conductive material is generated in terms of the environment in which the equipment is used.
Pollution level 2 is when only non-conductive pollution occurs. A temporary conductivity caused by condensing must be expected
occasionally.
*3: The storage ambient temperature is -20 to 75 if the system includes the AnS/A series modules.
*4: The operating ambient humidity and storage ambient humidity are 10 to 90%RH if the system includes the AnS/A series modules.
*5: Do not use or store the programmable controller under pressure higher than the atmospheric pressure of altitude 0m.
Doing so can cause a malfunction.
When using the programmable controller under pressure, please contact your sales representative.
3-1
Memo
3-2
CHAPTER4 HARDWARE SPECIFICATIONS OF THE CPU MODULE
Program size *1, *2 8K steps (32K bytes) 14K steps (56K bytes)
Program memory
58K bytes 94K bytes
(drive 0)
Memory card (RAM)
----
(drive 1)
Memory card (ROM)
----
(drive 2)
Memory size*1
Standard RAM
0 128K bytes *3
(drive 3)
Standard ROM
58K bytes 94K bytes
(drive 4)
CPU shared memory
---- 1K bytes
*3 , *4
*1: The unit of the file size stored in the memory area varies depending on the CPU module. For details, refer to the following.
Qn(H)/QnPH/QnPRHCPU User's Manual (Function Explanation, Program Fundamentals)
*2: The maximum number of executable sequence steps is as shown below.(Program size) - (File header size (default: 34 steps))
For details, refer to the following.
Qn(H)/QnPH/QnPRHCPU User's Manual (Function Explanation, Program Fundamentals)
*3: The size has been increased for the function upgrade of the CPU module. ( Appendix 2)
*4: The CPU shared memory is not latched.
( QCPU User's Manual (Multiple CPU System)
The CPU shared memory is cleared by turning on the programmable controller or resetting the CPU module.
4-1
Table4.1 Performance specifications
4-2
CHAPTER4 HARDWARE SPECIFICATIONS OF THE CPU MODULE
1
Table4.1 Performance specifications
The cyclic interval of system interrupt pointers I28 to 31 can be set up by parameters.
Interrupt pointer [I]
(2 to 1000ms, 1ms unit)
Default values I28: 100ms, I29: 40ms, I30: 20ms, I31: 10ms
4
Special relay [SM] 1024 points (SM0 to 1023) (The number of device points is fixed.)
Special register [SD] 1024 points (SD0 to 1023) (The number of device points is fixed.)
5
Function input [FX] 16 points (FX0 to F) (The number of device points is fixed.)
Function output [FY] 16 points (FY0 to F) (The number of device points is fixed.)
Function register [FD] 5 points (FD0 to 4) (The number of device points is fixed.)
6
No. of device tracking words ----
Device for accessing the link device directly.
Exclusively used for CC-Link IE controller network and MELSECNET/H. 7
Link direct device
Specified form: J \X ,J \Y ,J \W ,J \B ,
J \SW ,J \SB
*7: The step relay is the device for the SFC function.
*8: The value includes those of the CPU module and base unit.
*9: The value includes those of the CPU module, base unit, and power supply module.
Remark
For the general specifications, refer to CHAPTER 3.
4-3
4.1.2 High Performance model QCPU
Table4.2 Performance specifications
CPU shared
8K bytes
memory *3 , *4
*1: The unit of the file size stored in the memory area varies depending on the CPU module. For details, refer to the following.
Qn(H)/QnPH/QnPRHCPU User's Manual (Function Explanation, Program Fundamentals)
*2: The maximum number of executable sequence steps is as shown below.(Program size) - (File header size (default: 34 steps))
For details, refer to the following.
Qn(H)/QnPH/QnPRHCPU User's Manual (Function Explanation, Program Fundamentals)
*3: The size has been increased for the function upgrade of the CPU module. ( Appendix 2)
*4: The CPU shared memory is not latched.
( QCPU User's Manual (Multiple CPU System)
The CPU shared memory is cleared by turning on the programmable controller or resetting the CPU module.
4-4
CHAPTER4 HARDWARE SPECIFICATIONS OF THE CPU MODULE
1
Table4.2 Performance specifications
Max. number
Memory Flash
288
3
card card
of files stored
(ROM) ATA card 512
Standard RAM 3 *6 4
Standard ROM 28 60 124 252
No. of times of writing data into the
standard ROM
Max. 100000 times
5
No. of I/O device points
8192 points (X/Y0 to 1FFF)
(No. of points usable on program.)
No. of I/O points 6
(No. of points accessible to the actual 4096 points (X/Y0 to FFF)
I/O module.)
Internal relay [M] 8192 points by default (M0-8191) (changeable)
7
Latch relay [L] 8192 points by default (L0 to 8191) (changeable)
Link relay [B] 8192 points by default (B0 to 1FFF) (changeable)
2048 points by default (T0 to 2047) (sharing of low- and high-speed timers) (changeable)
8
The low- and high-speed timers are specified by the instructions.
Timer [T] The measurement unit of the low- and high-speed timers is set up by parameters.
(Low-speed timer: 1 to 1000ms, 1ms unit, 100ms by default)
(High-speed timer: 0.1 to 100.0ms, 0.1ms unit, 10.0ms by default)
No. of device points*7
*5: The CPU module can execute up to 124 programs. The CPU module cannot execute 125 or more programs.
*6: Extended by the upgraded functions of CPU module ( Qn(H)/QnPH/QnPRHCPU User's Manual (Function Explanation, Program
Fundamentals))
*7: The number of points can be changed within the setting range. ( Qn(H)/QnPH/QnPRHCPU User's Manual (Function Explanation,
Program Fundamentals)
4-5
Table4.2 Performance specifications
*8: Read only when Flash card is used. ATA card is unusable.
*9: The step relay is the device for the SFC function.
4-6
CHAPTER4 HARDWARE SPECIFICATIONS OF THE CPU MODULE
1
Table4.2 Performance specifications
Special register [SD] 2048 points (SM0 to 2047) (The number of device points is fixed.)
Function input [FX] 16 points (FX0 to F) (The number of device points is fixed.)
3
Function output [FY] 16 points (FY0 to F) (The number of device points is fixed.)
Function register [FD] 5 points (FD0 to 4) (The number of device points is fixed.) 4
No. of device tracking words ----
Device for accessing the link device directly.
*10: For use of CC-Link IE controller network, check the versions of the CPU module and GX Developer.
( Appendix 2.2)
Remark
For the general specifications, refer to CHAPTER 3.
4-7
4.1.3 Process CPU
Table4.3 Performance specifications
Process CPU
Item
Q02PHCPU Q06PHCPU Q12PHCPU Q25PHCPU
Control method Stored program repeat operation
Refresh mode
I/O control mode
(Direct access I/O is available by specifying direct access I/O (DX , DY ).)
Sequence control Relay symbol language, logic symbolic language, MELSAP3 (SFC),
Program language MELSAP-L, function block and structured text (ST)
language Process control
FBD for process control (Programming by PX Developer.)
language
Processing LD X0 34ns
speed
(sequence MOV D0 D1 102ns
instruction)
Processing Tracking
speed execution time
----
(redundant (increased scan
function) time)
Constant scan
(Function for keeping regular scan 0.5 to 2000ms (Setting available in 0.5ms unit.) (Setting by parameters.)
time)
28K steps 60K steps 124K steps 252K steps
Program size *1, *2
(112 bytes) (240 bytes) (496 bytes) (1008 bytes)
Program memory
112K bytes 240K bytes 496K bytes 1008K bytes
(drive 0)
Memory card
(RAM) Size of the installed memory card (2M bytes max.)
(drive 1)
Memory card
Size of the installed memory card
(ROM)
(Flash card: 4M bytes max., ATA card: 32M bytes max.)
(drive 2)
Memory size*1
Standard RAM
128K bytes 256K bytes *3
(drive 3)
Standard ROM
112K bytes 240K bytes 496K bytes 1008K bytes
(drive 4)
CPU shared
8K bytes
memory *3
*1: The unit of the file size stored in the memory area varies depending on the CPU module. For details, refer to the following.
Qn(H)/QnPH/QnPRHCPU User's Manual (Function Explanation, Program Fundamentals)
*2: The maximum number of executable sequence steps is as shown below.(Program size) - (File header size (default: 34 steps))
For details, refer to the following.
Qn(H)/QnPH/QnPRHCPU User's Manual (Function Explanation, Program Fundamentals)
*3: The CPU shared memory is not latched.
( QCPU User's Manual (Multiple CPU System)
The CPU shared memory is cleared by turning on the programmable controller or resetting the CPU module.
4-8
CHAPTER4 HARDWARE SPECIFICATIONS OF THE CPU MODULE
4-9
Table4.3 Performance specifications
Process CPU
Item
Q02PHCPU Q06PHCPU Q12PHCPU Q25PHCPU
Standard Up to 65536 points can be used by block Up to 131072 points can be used by block
RAM switching in units of 32768 points (R0 to 32767). switching in units of 32768 points (R0 to 32767).
SRAM card
Up to 517120 points can be used by block switching in units of 32768 points (R0 to 32767).
(1M bytes)
SRAM card
[R] Up to 1041408 points can be used by block switching in units of 32768 points (R0 to 32767).
(2M bytes)
Flash card
Up to 1041408 points can be used by block switching in units of 32768 points (R0 to 32767).
(2M bytes)
Flash card
Up to 1042432 points can be used by block switching in units of 32768 points (R0 to 32767).
File (4M bytes)
register*7 Standard 65536 points (ZR0 to 65535), block switching 131072 points (ZR0 to 131071), block switching
RAM not required. not required.
SRAM card
No. of device points
4 - 10
CHAPTER4 HARDWARE SPECIFICATIONS OF THE CPU MODULE
1
Table4.3 Performance specifications
Process CPU
Item
Q02PHCPU Q06PHCPU Q12PHCPU Q25PHCPU 2
Special relay [SM] 2048 points (SM0 to 2047) (The number of device points is fixed.)
No. of device points
Special register [SD] 2048 points (SD0 to 2047) (The number of device points is fixed.)
Function input [FX] 16 points (FX0 to F) (The number of device points is fixed.)
3
Function output [FY] 16 points (FY0 to F) (The number of device points is fixed.)
Function register [FD] 5 points (FD0 to 4) (The number of device points is fixed.) 4
No. of device tracking words ----
5
Device for accessing the link device directly.
Link direct device Exclusively used for CC-Link IE controller network*9 and MELSECNET/H.
Specified form: J \X ,J \Y ,J \W ,J \B ,J \SW ,J \SB 6
Device for accessing the buffer memory of the intelligent function module directly.
Intelligent function module device
Specified form: U \G
L0 to 8191(default) 7
Latch range
(Latch range can be set up for B, F, V, T, ST, C, D, and W.) (Setting by parameters.)
RUN/PAUSE contact One contact can be set up in X0 to 1FFF for each of RUN and PAUSE. (Setting by parameters.)
Year, month, date, hour, minute, second, and day of the week 8
(Automatic leap year detection)
Clock function Accuracy: -3.18 to +5.25s(TYP.+2.12s)/d at 0
Accuracy: -3.93 to +5.25s(TYP.+1.90s)/d at 25
*9: For use of CC-Link IE controller network, check the versions of the CPU module and GX Developer. ( Appendix 2.2)
Remark
For the general specifications, refer to CHAPTER 3.
4 - 11
4.1.4 Redundant CPU
Table4.4 Performance specifications
Redundant CPU
Item
Q12PRHCPU Q25PRHCPU
Control method Stored program repeat operation
Refresh mode
I/O control mode
(Direct access I/O is available by specifying direct access I/O (DX , DY ).)
Sequence control Relay symbol language, logic symbolic language, MELSAP3 (SFC),
Program language MELSAP-L, function block and structured text (ST)
language Process control
FBD for process control (Programming by PX Developer.)
language
Processing LD X0 34ns
speed
(sequence MOV D0 D1 102ns
instruction)
Processing Tracking
Device memory 48k words: 10ms
speed execution time
Device memory 100k words: 15ms
(redundant (increased scan
( QnPRHCPU User's Manual (Redundant System))
function) time)
Constant scan
(Function for keeping regular scan 0.5 to 2000ms (Setting available in 0.5ms unit.) (Setting by parameters.)
time)
124K steps 252K steps
Program size *1, *2
(496 bytes) (1008 bytes)
Program memory
496K bytes 1008K bytes
(drive 0)
Memory card
(RAM) Size of the installed memory card (2M bytes max.)
(drive 1)
Memory card
Size of the installed memory card
(ROM)
(Flash card: 4M bytes max., ATA card: 32M bytes max.)
(drive 2)
Memory size*1
Standard RAM
Size of the installed memory card (2M bytes max.)
(drive 3)
Standard ROM
496K bytes 1008K bytes
(drive 4)
CPU shared
----
memory
*1: The unit of the file size stored in the memory area varies depending on the CPU module. For details, refer to the following.
Qn(H)/QnPH/QnPRHCPU User's Manual (Function Explanation, Program Fundamentals)
*2: The maximum number of executable sequence steps is as shown below.(Program size) - (File header size (default: 34 steps))
For details, refer to the following.
Qn(H)/QnPH/QnPRHCPU User's Manual (Function Explanation, Program Fundamentals)
4 - 12
CHAPTER4 HARDWARE SPECIFICATIONS OF THE CPU MODULE
1
Table4.4 Performance specifications
Redundant CPU
Item
Q12PRHCPU Q25PRHCPU 2
Program memory 124 *3
252
Memory card (RAM) 287(When the Q2MEM-2MBS is used)
Memory Flash 3
Max. number 288
card card
of files stored
(ROM) ATA card 512
Standard RAM 3 *4 4
Standard ROM 124 252
No. of times of writing data into the
standard ROM
Max. 100000 times
5
No. of I/O device points
8192 points (X/Y0 to 1FFF)
(No. of points usable on program.)
No. of I/O points 6
(No. of points accessible to the actual 4096 points (X/Y0 to FFF)
I/O module.)
Internal relay [M] 8192 points by default (M0 to 8191) (changeable) 7
Latch relay [L] 8192 points by default (L0 to 8191) (changeable)
Link relay [B] 8192 points by default (B0 to 1FFF) (changeable)
2048 points by default (T0 to 2047) (sharing of low- and high-speed timers) (changeable) 8
The low- and high-speed timers are specified by the instructions.
Timer [T] The measurement unit of the low- and high-speed timers is set up by parameters.
(Low-speed timer: 1 to 1000ms, 1ms unit, 100ms by default)
(High-speed timer: 0.1 to 100.0ms, 0.1ms unit, 10.0ms by default)
4 - 13
Table4.4 Performance specifications
Redundant CPU
Item
Q12PRHCPU Q25PRHCPU
Standard
Up to 131072 points can be used by block switching in units of 32768 points (R0 to 32767).
RAM
SRAM card
Up to 517120 points can be used by block switching in units of 32768 points (R0 to 32767).
(1M bytes)
SRAM card
[R] Up to 1041408 points can be used by block switching in units of 32768 points (R0 to 32767).
(2M bytes)
Flash card
Up to 1041408 points can be used by block switching in units of 32768 points (R0 to 32767).
(2M bytes)
Flash card
Up to 1042432 points can be used by block switching in units of 32768 points (R0 to 32767).
File (4M bytes)
register*6 Standard
131072 points (ZR0 to 131071), block switching not required.
RAM
SRAM card
No. of device points
4 - 14
CHAPTER4 HARDWARE SPECIFICATIONS OF THE CPU MODULE
1
Table4.4 Performance specifications
Redundant CPU
Item
Q12PRHCPU Q25PRHCPU 2
Special relay [SM] 2048 points (SM0 to 2047) (The number of device points is fixed.)
No. of device points
Special register [SD] 2048 points (SD0 to 2047) (The number of device points is fixed.)
Function input [FX] 16 points (FX0 to F) (The number of device points is fixed.)
3
Function output [FY] 16 points (FY0 to F) (The number of device points is fixed.)
Function register [FD] 5 points (FD0 to 4) (The number of device points is fixed.) 4
Max. 100k words
No. of device tracking words
( QnPRHCPU User's Manual (Redundant System))
5
Device for accessing the link device directly.
Link direct device Exclusively used for CC-Link IE controller network*8 and MELSECNET/H.
Specified form: J \X ,J \Y ,J \W ,J \B ,J \SW ,J \SB 6
Device for accessing the buffer memory of the intelligent function module directly.
Intelligent function module device
Specified form: U \G
L0 to 8191 (default) (Setting by parameters.) 7
Latch range
(Latch range can be set up for B, F, V, T, ST, C, D, and W.)
RUN/PAUSE contact One contact can be set up in X0 to 1FFF for each of RUN and PAUSE. (Setting by parameters.)
Year, month, date, hour, minute, second, and day of the week 8
(Automatic leap year detection)
Accuracy: -3.2 to +5.27s
(TYP.+2.07s)/d at 0
Clock function
Accuracy: -2.77 to +5.27s
*8: For use of CC-Link IE controller network, check the versions of the CPU module and GX Developer. ( Appendix 2.2)
Remark
For the general specifications, refer to CHAPTER 3.
4 - 15
4.1.5 Universal model QCPU
*1: The unit of the file size stored in the memory area varies depending on the CPU module. For details, refer to the following.
QnUCPU User's Manual (Function Explanation, Program Fundamentals)
*2: The maximum number of executable sequence steps is as shown below.(Program size) - (File header size (default: 34 steps))
For details, refer to the following.
QnUCPU User's Manual (Function Explanation, Program Fundamentals)
*3: The CPU shared memory is not latched.
( QCPU User's Manual (Multiple CPU System)
The CPU shared memory is cleared by turning on the programmable controller or resetting the CPU module.
4 - 16
CHAPTER4 HARDWARE SPECIFICATIONS OF THE CPU MODULE
1
Table4.5 Performance specifications
Universal model QCPU
Item
Q00UJCPU Q00UCPU Q01UCPU Q02UCPU
Q03UDCPU 2
Q03UDECPU
Program memory 32 64 124
The low- and high-speed retentive timers are specified by the instructions.
Retentive timer [ST]*6 The measurement unit of the low- and high-speed retentive timers is set up by parameters.
(Low-speed retentive timer: 1 to 1000ms, 1ms unit, 100ms by default)
(High-speed retentive timer: 0.1 to 100.0ms, 0.1ms unit, 10.0ms by default)
*6 • Normal counter, 1024 points by default (C0 to 1023) (changeable)
Counter [C]
4 - 17
Table4.5 Performance specifications
Step relay [S] *8 8192 points (S0 to 8191) (The number of device points is fixed.)*9
Index register /
max. 20 points (Z0 to 19)
Standard devise register [Z]
Index register [Z]
max. 10 points (Z0 to 18)
(32-bit modification specification ----
(Index register (Z) is used in double words.)
of ZR device)
*7: Read only when a Flash card is used. ATA card is unusable.
4 - 18
CHAPTER4 HARDWARE SPECIFICATIONS OF THE CPU MODULE
The constant cyclic interval of system interrupt pointers I28 interrupt pointers I28 to 31 can be set
Interrupt pointer [I] to 31 can be set up by parameters. up by parameters.
(0.5 to 1000ms, 0.5ms unit) (0.5 to 1000ms, 0.5ms unit)
Default values I28: 100ms, I29: 40ms, I30: 20ms, I31: 10ms Default values I28: 100ms, I29: 40ms, 5
I30: 20ms, I31: 10ms
Special relay [SM] 2048 points (SM0 to 2047) (The number of device points is fixed.)
Special register [SD] 2048 points (SM0 to 2047) (The number of device points is fixed.) 6
Function input [FX] 16 points (FX0 to F) (The number of device points is fixed.)
Function output [FY] 16 points (FY0 to F) (The number of device points is fixed.)
7
Function register [FD] 5 points (FD0 to 4) (The number of device points is fixed.)
No. of device tracking words ----
Device for accessing the link device directly. 8
Dedicated to CC-Link IE controller network and MELSECNET/H.
Link direct device
Specified form: J \X ,J \Y ,J \W ,J \B ,
J \SW ,J \SB
Device for accessing the buffer memory of the intelligent function module directly.
*8: The step relay is the device for the SFC function.
*9: The device points can be changed to 0 for the Universal model QCPU if the serial number (first five digits) is "10042".
*10: Applicable only to the Q03UDECPU.
*11: The number indicates the total number of TCP/IP and UDP/IP protocols.
4 - 19
Table4.5 Performance specifications
*12: The value includes those of the CPU module and base unit.
*13: The current consumption in the Q03UDECPU is 0.46A
*14: The value includes those of the CPU module, base unit, and power supply module.
*15: The values for the Q03UDECPU are as follows.
External dimensions (D): 115mm (4.53 inches)
Weight: 0.22kg
Remark
For the general specifications, refer to CHAPTER 3.
4 - 20
CHAPTER4 HARDWARE SPECIFICATIONS OF THE CPU MODULE
QCPU
standard 8K bytes
CPU memory
shared Multiple
memory CPU high
*3 speed 32K bytes
transmis-
sion area
*1: The unit of the file size stored in the memory area varies depending on the CPU module. For details, refer to the following.
QnUCPU User's Manual (Function Explanation, Program Fundamentals)
*2: The maximum number of executable sequence steps is as shown below.(Program size) - (File header size (default: 34 steps))
For details, refer to the following.
QnUCPU User's Manual (Function Explanation, Program Fundamentals)
*3: The CPU shared memory is not latched.
( QCPU User's Manual (Multiple CPU System)
The CPU shared memory is cleared by turning on the programmable controller or resetting the CPU module.
4 - 21
Table4.6 Performance specifications
Universal model QCPU
Item Q04UDHCPU Q06UDHCPU Q10UDHCPU Q13UDHCPU Q20UDHCPU Q26UDHCPU
Q04UDEHCPU Q06UDEHCPU Q10UDEHCPU Q13UDEHCPU Q20UDEHCPU Q26UDEHCPU
The low- and high-speed retentive timers are specified by the instructions.
The measurement unit of the low- and high-speed retentive timers is set up by parameters.
Retentive timer [ST]
(Low-speed retentive timer: 1 to 1000ms, 1ms unit, 100ms by default)
(High-speed retentive timer: 0.1 to 100.0ms, 0.1ms unit, 10.0ms by default)
4 - 22
CHAPTER4 HARDWARE SPECIFICATIONS OF THE CPU MODULE
Standard
Up to 131072
points can be
Up to 393216
points can be
32768 points (R0 to 32767) Up
to 524288 points can be used
32768 points (R0 to 32767) Up
to 655360 points can be used
3
RAM used by block used by block by block switching in units of by block switching in units of
switching in switching in 32768 points 32768 points
units of 32768 units of 32768 4
points points
SRAM card 32768 points (R0 to 32767) Up to 517120 points can be used by block switching in units of 32768
[R]
(1M bytes) points
5
SRAM card 32768 points (R0 to 32767) Up to 1041408 points can be used by block switching in units of 32768
(2M bytes) points
SRAM card
(4M bytes)
32768 points (R0 to 32767) Up to 2087936 points can be used by block switching in units of 32768
points
6
SRAM card 32768 points (R0 to 32767) Up to 4184064 points can be used by block switching in units of 32768
(8M bytes) points
Flash card 32768 points (R0 to 32767) Up to 1041408 points can be used by block switching in units of 32768 7
(2M bytes) points
File reg-
Flash card 32768 points (R0 to 32767) Up to 2087936 points can be used by block switching in units of 32768
ister*8 (4M bytes) points 8
No. of device points
Step relay [S] *9 8192 points (S0 to 8191) (The number of device points is fixed.)*10
Index register /
max. 20 points (Z0 to 19)
Standard devise register [Z]
Index register [Z]
max. 10 points (Z0 to 18)
(32-bit modification specification
(Index register (Z) is used in double words.)
of ZR device)
4096 points (P0 to 4095), The use ranges of the local pointers and common pointers can be set up
Pointer [P]
by parameters.
*8: Read only when Flash card is used. ATA card is unusable.
*9: The step relay is the device for the SFC function.
*10: The device points can be changed if the serial number (first five digits) of the Universal model QCPU is "10042" or later.
4 - 23
Table4.6 Performance specifications
Default values I28: 100ms, I29: 40ms, I30: 20ms, I31: 10ms
Special relay [SM] 2048 points (SM0 to 2047) (The number of device points is fixed.)
Special register [SD] 2048 points (SM0 to 2047) (The number of device points is fixed.)
Function input [FX] 16 points (FX0 to F) (The number of device points is fixed.)
Function output [FY] 16 points (FY0 to F) (The number of device points is fixed.)
Function register [FD] 5 points (FD0 to 4) (The number of device points is fixed.)
No. of device tracking words ----
Device for accessing the link device directly.
Dedicated to CC-Link IE controller network and MELSECNET/H.
Link direct device
Specified form: J \X ,J \Y ,J \W ,J \B ,
J \SW ,J \SB
Device for accessing the buffer memory of the intelligent function module directly.
Intelligent function module device
Specified form: U \G
Data transmission
100/10Mbps
speed
Communication mode Full-duplex/Half-duplex
Specifi- Transmission method Base band
cations Max. distance
of Ether- between hub and 100m (328.08 feet)
net port node
built in Max. 10BASE-
the CPU Cascade connection: Up to four bases
number of T
module connect-
*11 100BASE
able Cascade connection: Up to two bases
-TX
nodes
Number of connec-
16 for a total of socket communication, MELSOFT connection, and MC protocol and 1 for FTP
tions *12
*11: Applicable only to the Built-in Ethernet port QCPU.
*12: The number indicates the total number of TCP/IP and UDP/IP protocols.
4 - 24
CHAPTER4 HARDWARE SPECIFICATIONS OF THE CPU MODULE
1
Table4.6 Performance specifications
4 - 25
4.2 Basic Model QCPU
(1) Q00JCPU
1) 4) 5) 6)
OUT
2)
7)
20)
Q00UJCPU
OUT
3) INPUT
100-240VAC 14) 13)
50/60Hz 105VA
OUTPUT
5VDC 3A
(FG)
(LG)
INPUT N
100-240VAC
100-240VAC
L
4 - 26
CHAPTER4 HARDWARE SPECIFICATIONS OF THE CPU MODULE
6) ERR. LED
•When the annunciator (F) is turned on by the SET/OUT instruction.
•When battery low occurs.
7
Off : Normal
Flash : When the error that stops operation is detected.
When reset operation is performed with the RUN/STOP/RESET switch. 8
Connector used for mounting an I/O or intelligent function module.
7) Module connector (To the connector of the spare space where no module is mounted, fit the accessory connector
cover or the blank cover module (QG60) to prevent dust from entering.)
8) DIN rail adaptor mounting holes Holes for mounting a DIN rail adaptor.
4 - 27
(2) Q00CPU, Q01CPU
1)
2)
3)
5)
6)
7)
8)
9)
4)
10)
11)
12)
Figure 4.5 Side face
4 - 28
CHAPTER4 HARDWARE SPECIFICATIONS OF THE CPU MODULE
4 - 29
*1: When a cable is connected to the RS-232 connector at all times, clamp the cable to prevent a poor connection, moving, and
disconnection by unintentional pulling.
The Q6HLD-R2 type RS-232 Connector Disconnection Prevention Holder is available as a clamp for RS-232 connector.
CPU module
Fixing screw
Figure 4.6 RS-232 cable fixing processing
4 - 30
CHAPTER4 HARDWARE SPECIFICATIONS OF THE CPU MODULE
The program modified online during boot operation is written to the program memory.
After making online program change, also write the program to the standard ROM of the boot source memory. If the program
is not written in the standard ROM, the old program will be executed at the next boot operation.
For details of the boot operation, refer to the following.
Qn(H)/QnPH/QnPRHCPU User's Manual (Function Explanation, Program Fundamentals)
4 - 31
4.2.3 Reset operation
For the Basic model QCPU, the RUN/STOP/RESET switch of the CPU module is used to switch between the RUN
status and STOP status and to perform RESET operation.
When using the RUN/STOP/RESET switch to reset the CPU module, moving the RUN/STOP/RESET switch to the
reset position will not reset it immediately.
Hold the RUN/STOP/RESET switch in the RESET position until reset processing is complete (the flashing ERR. LED turns
off).
If you release your hand from the RUN/STOP/RESET switch during reset processing (the ERR. LED is flashing), the switch
will return to the STOP position and reset processing cannot be completed.
Perform reset operation with the RUN/STOP/RESET switch as shown in Figure 4.7.
Start
RESET RUN
RUN/STOP/RESET
STOP switch
Flickers.
.......................Reset is completed.
The "ERR. LED" goes off .
Goes off.
.......................Reset is canceled.
Return the RUN/STOP/RESET
switch to the "STOP" position.
RESET RUN
RUN/STOP/RESET : Releasing your hand from the
STOP switch RUN/STOP/RESET switch returns it
to the STOP position.
4 - 32
CHAPTER4 HARDWARE SPECIFICATIONS OF THE CPU MODULE
1
Operate the RUN/STOP/RESET switch with your fingertips.
To prevent the switch from being damaged, do not use any tool such as screw driver.
2
● The valid/invalid for latch clear in the clear range of latch clear operation can be set for each device. The setting can be
5
mode in the device setting of the PLC parameter.
● For the remote latch clear operation by GX Developer, refer to the following.
Qn(H)/QnPH/QnPRHCPU User's Manual (Function Explanation, Program Fundamentals) 6
4 - 33
4.3 High Performance Model QCPU, Process CPU and Redundant
CPU
2)
9)
3)
4)
5)
1
2
6) 3 13)
4
7) 10) 5
14)
15)
11) *1
12)
8)
16)
17)
20)
19)
18)
4 - 34
CHAPTER4 HARDWARE SPECIFICATIONS OF THE CPU MODULE
21)
2
2)
9)
3) 22)
4) 23) 3
5)
24)
6) 13)
7) 10)
14)
4
15)
25)
5
11)
12) 6
8)
7
When opening the cover, put
your finger here.
Figure 4.11 Front face Figure 4.12 With front cover open 8
16)
17)
20)
19)
18)
4 - 35
Table4.9 Part Names
4 - 36
CHAPTER4 HARDWARE SPECIFICATIONS OF THE CPU MODULE
4 - 37
Table4.9 Part Names
For the memory copy from control system to standby system, refer to the following.
QnPRHCPU User's Manual (Redundant System)
Indicates the CPU module operates as control system or standby system.
On : Control system (The standby system is normal and system switching is available.)
22) CONTROL LED *4
Off : Standby system
Note that this LED turns on in the debug mode.
The LED of the CPU module on the system A side turns on.
On : System A
Flash : When the tracking cable is disconnected while the system runs normally as the system
23) SYSTEM A LED *4 A.
(It lasts until the system A side tracking cable is connected.)
Off : System B (The SYSTEM B LED turns on.)
Note that this LED turns on in the debug mode.
The LED of the CPU module on the system B side turns on.
On : System B
Flash : When the tracking cable is disconnected while the system runs normally as the system
24) SYSTEM B LED *4 B
(It lasts until the system B side tracking cable is connected.)
Off : System A (The SYSTEM A LED turns on)
Note that this LED turns off in the debug mode.
25) TRACKING connector *4 Connector for connecting system A or B with the tracking cable (QC TR).
4 - 38
CHAPTER4 HARDWARE SPECIFICATIONS OF THE CPU MODULE
*1: When a cable is connected to the RS-232 connector at all times, clamp the cable to prevent a poor connection, moving, and
disconnection by unintentional pulling. 1
The Q6HLD-R2 type RS-232 Connector Disconnection Prevention Holder is available as a clamp for RS-232 connector.
CPU module
2
RS-232 cable
3
Q6HLD-R2
Fixing screw
4
Figure 4.14 RS-232 cable fixing processing
*2: Because the DIP switches are located out of reach of fingertips, operate it with a tool such as screwdriver. Careful attention must be paid
to prevent the switch part from being damaged. 5
*3: Operate the RUN/STOP switch and RESET/L. CLR switch with your fingertips.
To prevent the switch from being damaged, do not use any tool such as screw driver.
*4: Applicable only to the Redundant CPU.
6
4 - 39
4.3.2 Switch operation after writing program
This section explains the switch operation after a program is written using GX Developer.
(b) To set to RUN status with device memory data not cleared (held)
1) Set the RUN/STOP switch to RUN.
2) The RUN LED flashes.
3) Set the RUN/STOP switch to STOP.
4) Set the RUN/STOP switch to RUN again.
5) The CPU module is placed in the RUN status (RUN LED: On).
● Before writing a program to the CPU module, perform the following operation.
• Set the system protect setting switch (DIP switch: SW1) of the CPU module to off (not protected).
• Cancel the registered password on GX Developer.
● When the CPU module is placed in the STOP status by the remote STOP operation of GX Developer, it can be put in
the RUN status by the remote RUN operation of GX Developer after program write. In that case, No operation is
needed for the RUN/STOP switch and RESET/L. CLR switch of the CPU module.
4 - 40
CHAPTER4 HARDWARE SPECIFICATIONS OF THE CPU MODULE
Be sure to return the RESET/L. CLR switch to the neutral position after resetting. When the system is left with the RESET/L.
CLR switch set to the RESET, the entire system is reset, not operated normally. 3
● The valid/invalid for latch clear in the clear range of latch clear operation can be set for each device. The setting can be 8
mode in the device setting of the PLC parameter.
● In addition to the way of using the RESET/L. CLR switch for latch clear, remote latch clear may be performed from GX
Developer.
For details of remote latch clear operation by GX Developer, refer to the following.
4 - 41
4.3.5 Automatic writing to standard ROM
The High Performance model QCPU, Process CPU and Redundant CPU allows data in the memory card to be written
into the standard ROM automatically.
For details, refer to the following.
Qn(H)/QnPH/QnPRHCPU User's Manual (Function Explanation, Program Fundamentals)
2) Store the set parameters and programs to be booted in the memory card.
4 - 42
CHAPTER4 HARDWARE SPECIFICATIONS OF THE CPU MODULE
4
2)
Q00UJCPU
OUT
(FG)
(LG)
INPUT N
100-240VAC
100-240VAC
L
16)
17)
15) 19) 18)
Figure 4.17 Side face Figure 4.18 With front cover open
4 - 43
Table4.10 Part Names
4 - 44
CHAPTER4 HARDWARE SPECIFICATIONS OF THE CPU MODULE
CPU module
5
6
RS-232 cable
Q6HLD-R2
7
Fixing screw
Figure 4.19 RS-232 cable fixing processing
8
*2: Operate the RUN/STOP/RESET switch with your fingertips.
To prevent the switch from being damaged, do not use any tool such as screw driver.
4 - 45
(2) Q00UCPU, Q01UCPU
1)
Q00UCPU
2)
3)
4)
5)
6)
10)
11)
12)
7)
Figure 4.20 Front face Figure 4.21 with front cover open
13)
14)
15)
8)
9)
4 - 46
CHAPTER4 HARDWARE SPECIFICATIONS OF THE CPU MODULE
4 - 47
Table4.11 Part Names
*1: When a cable is connected to the RS-232 connector at all times, clamp the cable to prevent a poor connection, moving, and
disconnection by unintentional pulling.
The Q6HLD-R2 type RS-232 Connector Disconnection Prevention Holder is available as a clamp for RS-232 connector.
CPU module
RS-232 cable
Q6HLD-R2
Fixing screw
Figure 4.23 RS-232 cable fixing processing
4 - 48
CHAPTER4 HARDWARE SPECIFICATIONS OF THE CPU MODULE
2)
9)
3) 3
4)
5)
6) 4
7) 10)
13)
5
11)
6
12)
8) 7
When opening the cover, put
your finger here.
Figure 4.24 Front face Figure 4.25 With front cover open 8
14)
15)
18)
17)
16)
4 - 49
(4) Q03UDECPU, Q04UDEHCPU, Q06UDEHCPU, Q10UDEHCPU, Q13UDEHCPU,
Q20UDEHCPU, Q26UDEHCPU
1)
2)
9)
3)
4)
5)
6)
7)
10)
13)
11)
20)
19)
21)
8)
When opening the cover, put
your finger here.
Figure 4.27 Front face Figure 4.28 With front cover open
14)
15)
18)
17)
16)
4 - 50
CHAPTER4 HARDWARE SPECIFICATIONS OF THE CPU MODULE
4 - 51
Table4.12 Part names
CPU module
RS-232 cable
Q6HLD-R2
Fixing screw
Figure 4.30 RS-232 cable fixing processing
4 - 52
CHAPTER4 HARDWARE SPECIFICATIONS OF THE CPU MODULE
2
(1) When writing program with CPU module set to "STOP" *1
(b) To set to RUN status with device memory data not cleared (held) 5
1) Set the RUN/STOP/RESET switch to the RUN position.
2) The RUN LED flashes.
3) Set the RUN/STOP/RESET switch to the STOP position.
6
4) Setthe RUN/STOP/RESET switch to the RUN position again.
5) The CPU module is placed in the RUN status (RUN LED: On). 7
(2) When a program is written while CPU module is running (online change)*2
No operation is needed for the RUN/STOP/RESET switch of the CPU module. At this time, the device memory
8
data are not cleared.
*1: When a program was written to the program memory during boot operation, also write the program to the boot source
memory.
When the CPU module is placed in the STOP status by the remote STOP operation of GX Developer, it can be set in the
RUN status by the remote RUN operation of GX Developer after program write.
In that case, no operation is needed for the RUN/STOP/RESET switch of the CPU module.
For details of GX Developer, refer to the following.
GX Developer Operating Manual
4 - 53
4.4.3 Reset operation
For the Universal model QCPU, the RUN/STOP/RESET switch of the CPU module is used to switch between the RUN
status and STOP status and to perform RESET operation.
When using the RUN/STOP/RESET switch to reset the CPU module, setting the RUN/STOP/RESET switch to the
reset position will not reset it immediately.
Hold the RUN/STOP/RESET switch in the RESET position until reset processing is complete (the flashing ERR. LED turns
off).
If you release your hand from the RUN/STOP/RESET switch during reset processing (the ERR. LED is flashing), the switch
will return to the STOP position and reset processing cannot be completed.
Perform reset operation with the RUN/STOP/RESET switch as shown in Figure 4.31.
Start
RESET RUN
RUN/STOP/RESET
STOP switch
MODE
RUN Flickers.
ERR.
USER
BAT.
BOOT
.......................Reset is completed.
The "ERR. LED" goes off .
MODE
RUN Goes off.
ERR.
USER
BAT.
BOOT
.......................Reset is canceled.
Return the RUN/STOP/RESET
switch to the "STOP" position.
RESET RUN
RUN/STOP/RESET : Releasing your hand from the
STOP switch RUN/STOP/RESET switch returns it
to the STOP position.
4 - 54
CHAPTER4 HARDWARE SPECIFICATIONS OF THE CPU MODULE
1
Operate the RUN/STOP/RESET switch with your fingertips.
To prevent the switch from being damaged, do not use any tool such as screw driver.
2
4.4.4 Latch clear operation
3
For the Universal model QCPU, latch clear is performed by the remote latch clear operation of GX Developer.
Latch clear cannot be executed by operating the switches of the CPU module.
4
● The valid/invalid for latch clear in the clear range of latch clear operation can be set for each device. The setting can be
made in the device setting of the PLC parameter. 5
● For the remote latch clear operation by GX Developer, refer to the following.
QnUCPU User's Manual (Functional Description, Program Fundamentals)
6
4 - 55
CHAPTER5 POWER SUPPLY MODULE
This chapter describes the specifications of the power supply modules applicable for the programmable controller
system (The Q Series power supply module, slim type power supply module, redundant power supply module and
AnS/A Series power supply module) and how to select the most suitable module.
5.1 Base Unit that Can Be Used in Combination with Power Supply
Module
This section describes the base unit that can be used in combination with the power supply module respectively.
For details of the CPU modules and base units, refer to the following.
CPU modules : CHAPTER 4
Base units : CHAPTER 6
Table5.1 Base unit that can be used in combination with power supply module
Base unit
Main base unit Extension base unit
Power
Q33B Q63B
supply Q32SB QA65B
Q35B Q38DB Q52B Q65B QA1S65B
module Q33SB Q38RB Q68RB Q65WRB QA68B
Q38B Q312DB Q55B Q68B QA1S68B
Q35SB *2
Q312B Q612B
Q61P-A1
Q61P-A2
Q61P
Q61P-D
Q62P
Q63P
Q64P
Q64PN
Q61SP
Q63RP *1
Q64RP
A1S61PN
A1S62PN
A1S63P
A61P
A61PN
A62P
A63P
A61PEU
A62PEU
5-1
CHAPTER5 POWER SUPPLY MODULE
5.2 Specifications
1
5.2.1 Power supply module specifications
2
Table5.2 shows the specifications of the power supply modules.
• By noise simulator of 1500Vp-p noise voltage, 1 s noise width and 25 to 60Hz noise frequency
Noise durability
• Noise voltage IEC 61000-4-4, 2KV
Operation indication LED indication (Normal: On (green), Error: Off)
Fuse Built-in (User-unchangeable)
5-2
Table5.2 Power supply module specifications
Performance Specifications
Item
Q61P-A1 Q61P-A2 Q61P Q62P
Application ERR. contact ( Section 5.3)
Rated switching
24VDC, 0.5A
voltage, current
Contact output section
Minimum
5VDC, 1mA
switching load
Response time OFF to ON: 10ms max. ON to OFF: 12ms max.
Mechanical : More than 20 million times
Life
Electrical : More than 100 thousand times at rated switching voltage, current
Surge
No
suppressor
Fuse No
Terminal screw size M3.5 7
5-3
CHAPTER5 POWER SUPPLY MODULE
5-4
Table5.3 Power supply module specifications
Performance Specifications
Item
Q63P
Application ERR. contact ( Section 5.3)
Rated switching
24VDC, 0.5A
voltage, current
Contact output section
Minimum
5VDC, 1mA
switching load
Response time OFF to ON: 10ms max. ON to OFF: 12ms max.
Mechanical : More than 20 million times
Life
Electrical : More than 100 thousand times at rated switching voltage, current
Surge
No
suppressor
Fuse No
Terminal screw size M3.5 7
Applicable wire size 0.75 to 2mm2
Applicable solderless
RAV1.25 - 3.5, RAV2 - 3.5
terminal
Applicable tightening
0.66 to 0.89N•m
torque
H 98mm (3.86 inches)
External
W 55.2mm (2.17 inches)
dimensions
D 90mm (3.55 inches)
Weight 0.33kg
5-5
CHAPTER5 POWER SUPPLY MODULE
• By noise simulator of 1500Vp-p noise voltage, 1 s noise width and 25 to 60Hz noise frequency
Noise durability
• Noise voltage IEC 61000-4-4, 2KV
Operation indication LED indication (Normal: On (green), Error: Off)
Fuse Built-in (User-unchangeable)
5-6
Table5.4 Power supply module specifications
Performance Specifications
Item
Q64P Q64PN
Application ERR. contact ( Section 5.3)
Rated switching
24VDC, 0.5A
voltage, current
Contact output section
Minimum
5VDC, 1mA
switching load
Response time OFF to ON: 10ms max. ON to OFF: 12ms max.
Mechanical : More than 20 million times
Life
Electrical : More than 100 thousand times at rated switching voltage, current
Surge
None
suppressor
Fuse None
Terminal screw size M3.5 screw
5-7
CHAPTER5 POWER SUPPLY MODULE
• By noise simulator of 1500Vp-p noise voltage, 1 s noise width and 25 to 60Hz noise frequency
Noise durability
• Noise voltage IEC 61000-4-4, 2KV
Operation indication LED indication (Normal: On (green), Error: Off)
Fuse Built-in (User-unchangeable)
Application ERR. contact ( Section 5.3)
Rated switching
24VDC, 0.5A
voltage, current
Contact output section
Minimum
5VDC, 1mA
switching load
Response time OFF to ON: 10ms max. ON to OFF: 12ms max.
Mechanical : More than 20 million times
Life
Electrical : More than 100 thousand times at rated switching voltage, current
Surge
None
suppressor
Fuse None
5-8
Table5.5 Power supply module specifications
Performance Specifications
Item
Q61SP
Terminal screw size M3.5 screw
5-9
CHAPTER5 POWER SUPPLY MODULE
Noise durability
By noise simulator of 500Vp-p
noise voltage, 1 s noise width and 25 to 60Hz
8
noise frequency
Operation indication LED indication*6 (Normal operation: On(green) Error:Off(red)
Fuse Built-in (User-unchangeable)
voltage, current
Minimum switching
5VDC, 1mA
load
Response time OFF to ON: 10ms max. ON to OFF: 12ms max.
Mechanical : More than 20 million times
Life
Electrical : More than 100 thousand times at rated switching voltage, current
Surge suppressor None
Fuse None
Terminal screw size M3.5 Screw
*6: Although the POWER LED momentarily turns on in red immediately after the power supply is turned on or off, the Q64RP is not faulty.
5 - 10
Table5.7 Power supply module specifications
Performance Specifications
Item
Q64RP
Mounting position Power supply module mounting slot
Applicable base unit Q3 RB, Q6 RB, Q6 WRB*8
+10%
100 to 120VAC/200 to 240VAC -15%
Input power supply
(85 to 132VAC/170 to 264VAC)
Input frequency 50/60Hz 5%
Input voltage distortion
Within 5% ( Section 5.2.4)
factor
Max. input apparent
160VA
power
Inrush current 20A within 8ms*5
Rated output 5VDC 8.5A
current 24VDC ----
Overcurrent 5VDC 9.35A or more
protection*1 24VDC ----
Overvoltage 5VDC 5.5 to 6.5V
protection*2 24VDC ----
Efficiency 65% or more
Allowable momentary
Within 20ms
power failure time*3
Dielectric withstand Between inputs/LG and outputs/FG
voltage 2830VAC rms/3 cycles (2000 m (6562 feet))
Input and LG batched, output and FG batched, batch input-LG, batch output-FG
Insulation resistance
10M or higher by 500VDC insulation resistance tester
• By noise simulator of 1500Vp-p noise voltage, 1 s noise width and 25 to 60Hz noise frequency
Noise durability
• Noise voltage IEC 61000-4-4, 2KV
Operation indication LED indication (Normal: ON (green), Error: ON (red)) *7
Fuse Built-in (User-unchangeable)
*7: Although the POWER LED momentarily turns on in red immediately after the power supply is turned on or off, the Q64RP is not faulty.
*8: When mounting the Q64RP to the Q65WRB, use the Q64RP whose first 6 digits of serial No. is "081103" or later.
The vibration condition described in the general specifications may not be met if the serial number (first six digits) of the Q64RP is
"081102" or earlier is mounted.
5 - 11
CHAPTER5 POWER SUPPLY MODULE
Minimum
5VDC, 1mA
3
switching load
Response time OFF to ON: 10ms max. ON to OFF: 12ms max.
Life
Mechanical : More than 20 million times 4
Electrical : More than 100 thousand times at rated switching voltage, current
Surge
None
suppressor
5
Fuse None
Terminal screw size M3.5 screw
5 - 12
Table5.8 Power supply module specifications
Performance Specifications
Item
Q61P-D
Mounting position Power supply module mounting slot
Applicable base unit Q3 B, Q3 DB, Q6 B
+10%
100 to 240VAC -15%
Input power supply*10
(85 to 264VAC)
Input frequency 50/60Hz 5%
Input voltage distortion
Within 5% ( Section 5.2.4)
factor
Max. input apparent
130VA
power
Max. input power ----
Inrush current 20A within 8ms*5
Rated output 5VDC 6A
current 24VDC ----
External output voltage ----
Overcurrent 5VDC 6.6A or more
protection*1 24VDC ----
Overvoltage 5VDC 5.5 to 6.5V
protection *2 24VDC ----
Efficiency 70% or more
Allowable momentary
Within 20ms
power failure period *3
Dielectric withstand Between input -LG batched and output-FG batched
voltage 2830VAC rms/3 cycles (2000m (6562 feet))
Input and LG batched, output and FG batched, batch input - LG, batch output - FG
Insulation resistance
10M or higher by 500VDC insulation resistance tester
• By noise simulator of 1500Vp-p noise voltage, 1 s noise width and 25 to 60Hz noise frequency
Noise durability
• Noise voltage IEC 61000-4-4, 2KV
Operation indication LED indication (POWER LED, LIFE LED)
Fuse Built-in (User-unchangeable)
Minimum
5VDC, 1mA
switching load
Response time OFF to ON: 10ms max. ON to OFF: 12ms max.
Mechanical : More than 20 million times
Life
Electrical : More than 100 thousand times at rated switching voltage, current
Surge suppres-
No
sor
Fuse No
*10: When using the Q61P-D in the system configured with a A/AnS series module, the power supply modules mounted on the main base
unit and extension base unit must be turned on and off simultaneously.
5 - 13
CHAPTER5 POWER SUPPLY MODULE
5 - 14
Table5.9 Power supply module specifications
Performance Specifications
Item
Q00JCPU (Power supply part) Q00UJCPU (Power supply part)
+10%
100 to 120VAC -15%
Input power supply
(85 to 264VAC)
Input frequency 50/60Hz 5%
Input voltage distortion
Within 5% ( Section 5.2.4)
factor
Max. input apparent
105VA
power
Inrush current 40A within 8ms*5
Rated output
5VDC 3A
current
Overcurrent
5VDC 3.3A or more
protection*1
Overvoltage
5VDC 5.5 to 6.5V
protection*2
Efficiency 65% or more
Allowable momentary
Within 20ms (100VAC or more)
power failure time*3
Dielectric withstand Between inputs/LG and outputs/FG
voltage 2830VAC rms/3 cycles (2000 m (6562 feet))
Input and LG batched, output and FG batched, batch input-LG, batch output-FG
Insulation resistance
10M or higher by 500VDC insulation resistance tester
• By noise simulator of 1500Vp-p noise voltage, 1 s noise width and 25 to 60Hz noise frequency
Noise durability
• Noise voltage IEC61000-4-4, 2KV
Operation indication LED indication (The POWER LED of the CPU part: Normal: On (green), Error: Off)
Fuse Built-in (User-unchangeable)
Contact output section None
Terminal screw size M3.5 7
5 - 15
CHAPTER5 POWER SUPPLY MODULE
• By noise simulator of 1500Vp-p noise voltage, 1 s noise width and 25 By noise simulator of 500Vp-p noise
Noise durability to 60Hz noise frequency voltage, 1 s noise width and 25 to
• Noise voltage IEC 61000-4-4, 2KV 60Hz noise frequency
Operation indication LED indication (Normal: On (green), Error: Off)
Fuse Built-in (User-unchangeable)
Contact output section None
Terminal screw size M3.5 screw
Applicable wire size 0.75 to 2mm2
Applicable solderless
RAV1.25 to 3.5, RAV2 to 3.5
terminal
Applicable tightening
0.66 to 0.89N•m
torque
H 130mm (5.12 inches)
External
W 55mm (2.17 inches)
dimensions
D 93.6mm (3.69 inches)
Weight 0.60kg 0.50kg
5 - 16
Table5.11 Power supply module specifications
Specifications
Item
A61P A61PN A62P A63P
Slot position Power supply module mounting slot
Applicable base unit QA6 B
+10%
100VAC to 120VAC-15%
(85VAC to 132VAC) 24VDC-35%
+30%
Input power supply
200VAC to 240VAC-15%
+10% (15.6VDC to 31.2VDC)
(170VAC to 264VAC)
Input frequency 50/60Hz 5% –
5 - 17
CHAPTER5 POWER SUPPLY MODULE
Dielectric withstand
Between 7
primary side 2830V AC rms/3 cycles (altitude 2000m (6562 feet))
voltage
and FG
Noise durability
By noise simulator of noise voltage IEC 801-4, 2KV, 1500Vp-p, 8
noise width 1 s, and noise frequency 25 to 60Hz
Power indicator LED indication of power supply
Terminal screw size M4 0.7 6
5 - 18
*1: Overcurrent protection
The overcurrent protection device shuts off the 5 V, 24 VDC circuit and stops the system if the current flowing in the
circuit exceeds the specified value.
The LED of the power supply module turns off or turns on in dim green when voltage is lowered. (As for the redundant
power supply module, the LED turns off or turns on in red.) If this device is activated, switch the input power supply off
and eliminate the cause such as insufficient current capacity or short. Then, a few minutes later, switch it on to restart
the system.
The initial start for the system takes place when the current value becomes normal.
5 - 19
CHAPTER5 POWER SUPPLY MODULE
3
+10%
100 to 120V AC-15%
(85 to 132V AC)
Input voltage
+10%
200 to 240V AC-15%
(170 to 264V AC)
4
Input frequency 50/60Hz 5%
Max. input apparent power
Inrush current
95VA
20A, within 8ms
5
Rated output +15VDC 1.2A
current -15VDC 0.7A
6
Overcurrent +15VDC 1.64A or more
protection*8 -15VDC 0.94A or more
Efficiency 65% or more
7
Power indicator Power LED display (Normal: On (green), error: Off)
Contact output
*8: The overcurrent protection shuts off the +15VDC circuit if a current higher than the specified value flows in the circuit and:
• Both +15VDC and -15VDC are switched off if overcurrent has occurred at +15V; or
• -15VDC is switched off but +15V remains output if overcurrent has occuerred at -15V; and
• The power supply module LED is switched off or dimly lit due to 15VDC voltage drop.
If this device is activated, turn off the input power supply and eliminate the cause such as insufficient current capacity or short before
restarting the system.
5 - 20
5.2.2 Selecting the power supply module
The power supply module is selected according to the total of current consumption of the base units, I/O modules,
intelligent function module, special function module, and peripheral devices supplied by its power supply module.
For the internal current consumption of 5 VDC of the base unit, refer to CHAPTER 6.
For the internal current consumption of 5 VDC of the I/O modules, intelligent function module, special function module,
and peripheral devices, refer to the Manuals of their respective modules.
For the devices obtained by a user, see the manual for the respective device.
Keep the current consumption of the base unit (Q3 B, Q3 DB, Q6 B) below the 5VDC rated output current of
the Q series power supply module.
• Select a power supply module of a proper 5VDC rated output current to be installed to the main base unit
so that it will cover the current used by Q5 B.
For example, if current consumption is 3.0A on the main base unit and 1.0A on Q5 B, any of the power
supply modules shown in Table5.15 must be mounted on the main base unit.
5 - 21
CHAPTER5 POWER SUPPLY MODULE
Keep the current consumption of the slim type main base unit (Q3 SB) not exceeding the 5VDC rated output
current of the slim type power supply module (Q61SP).
5 - 22
(3) When the base unit is Q3 RB or Q6 RB
Redundant power supply Redundant power supply base unit
module × 2 modules Q3 RB, Q6 RB
When a redundant power supply system is configured and one redundant power supply module has failed, the system is
operated using the other redundant power supply module only during replacement of the failed redundant power supply
module.
Therefore, keep the current consumption of the redundant power supply base unit (Q3 RB/Q6 RB/Q6 WRB) within the
5VDC rated output current (8.5A) for one redundant power supply module.
5 - 23
CHAPTER5 POWER SUPPLY MODULE
peripheral
Special function module devices
A1SD61,A1SD75P1-S3, etc. AD75TU
Figure 5.4 Modules and peripheral device that are powered
by power supply module
Select the power supply module also in consideration of the current consumption of the peripheral devices
connected to the special function module.
For example, when the AD75TU is connected to the AD75P1-S3, the current consumption of the AD75TU must
also be taken into account.
5 - 24
(5) When the base unit is QA6 B:
A series power supply
Base unit QA65B,
module A61P, A61PN, A62P,
QA68B
A63P
Peripheral
Special function module device
AD61,AD75P1-S3, etc. AD75TU
Figure 5.5 Modules and peripheral device that are powered
by power supply module
Select the power supply module also in consideration of the current consumption of the peripheral devices
connected to the special function module.
For example, when the AD75TU is connected to the AD75P1-S3, the current consumption of the AD75TU must
also be taken into account.
5 - 25
CHAPTER5 POWER SUPPLY MODULE
LED 4
LIFE OUT terminal Module
POWER LIFE
• Power supply module failure
• AC power is not input 5
Off Off Off
• Power failure (including momentary power
failure for 20ms or more)
On (green) On (green) • Normal operation 6
On • Normal operation (Remaining life approx.
On (green) On (orange)
50%)*1
Flash (orange) • Normal operation (Remaining life approx. 1 7
On (green) (On for 5 sec. and off for year)*1
1 sec.) Replacement of the module is recommended
Flash (orange) Off
• Normal operation (Remaining life approx. 6 8
On (green) (At intervals of half a *1
months)
sec.)
On (green) Off • Life expired
• Ambient temperature is out of range (Ambi-
*1: The remaining life of the module varies depending on the ambient temperature.
(If the ambient temperature rose by 10 , the remaining life of the module will be shortened by half.)
5 - 26
(a) Connecting the terminal to an external display device
Connecting the LIFE OUT terminal allows indication of the remaining life of the module to an external display,
device such as external LED, by turning it off when the life is one year or less.
When the external display device turned off, the remaining life can be checked by the LIFE LED of the Q61P-D
located in the control panel.
(b) Obtaining the output status into an input module and monitoring it by GOT
Obtaining the LIFE OUT terminal status into an input module allows monitoring of the module remaining life in
a sequence program.
The following indicates how to monitor the remaining life of the power supply module in the sequence program
by using GOT.
1) System configuration
GOT
Q61P-D
Figure 5.7 When obtaining into an input module
5 - 27
CHAPTER5 POWER SUPPLY MODULE
2) Conditions of a program
Table5.20 and Table5.21 indicate devices used in a program for monitoring the module life.
1
When the life detection function of the Q61P-D is faulty, the LIFE OUT terminal repeats on and off for three times when the
module is started.
Depending on the system, this behavior (ons and offs) of the LIFE OUT terminal may not be obtained to the input module
due to delay of the sequence program start after the Q61P-D has started.
In this program example, M11 turns on even though the life detection function is faulty when powered on since the remaining
life is regarded as one year.
5 - 28
3) Program example
5 - 29
CHAPTER5 POWER SUPPLY MODULE
5 - 30
5.3 Part Names and Settings
10) 10)
8) 4) 4)
(Q62P
6) 6)
only)
7) 7)
12) 9) 9)
Q61P-D (100 to 240VAC input, 5VDC 6A output) Q61SP (100 to 240VAC input, 5VDC2A output)
3)
11) 1) 11)
Q61SP
INPUT Q61SP
100-240VAC
10)
4)
4)
5)
6)
6)
7)
7)
15)
15)
MITSUBISHI
12)
12) 9)
5 - 31
CHAPTER5 POWER SUPPLY MODULE
3) LIFE LED
Module remaining life is approx. 6 months 6
Off: • Module life expired. (Turns on red for 1 second after power-on)
• Ambient temperature is out of range (Ambient temperature of the module is
exceeding the specification and also the life detection function is stopped.)
On (red) : Ambient temperature out of range (Ambient temperature of the module is
7
exceeding the specification)
Flash(red) : Function failure
• Turns on when the entire system operates normally. 8
• Turns off (opens) when the AC power is not supplied, a stop error (including reset)
occurs in the CPU module, or the fuse is blown.
4) ERR. terminal
• In a multiple CPU system, turns off when a stop error occurs in any of the CPU
modules.
*1: Flicker-OFF indicates that the output signal of the terminal turns off and on at intervals of one second for three times and then off
(opens).
*2: When using the Q61P-D in the system configured with an extension base unit, the POWER LED of the Q61P-D on the extension base
unit may turn on in dull red when the module is turned off. Note that this does not indicate an error.
5 - 32
Table5.22 Part Names
Table5.23 Precaution
● When the Q61P-A1, Q61P-A2, Q61P-D, Q61P, Q62P, Q63P, Q64P or Q64PN is mounted on the extension base unit, a
system error cannot be detected by the ERR. terminal. (The ERR. terminal is always off.)
● Cables for the ERR. contact and LIFE OUT contact must be up to 30m (98.43 feet) and installed in the control panel.
5 - 33
CHAPTER5 POWER SUPPLY MODULE
Q64RP
1
Q63RP
10) 1) 10) 2) 2
INPUT 9) 9) 3
24VDC
MAX 65W
OUTPUT 5VDC 8.5A
4
ERR.
L
3) 3)
24VDC 0.5A
(FG) 4) 4)
(LG) 5) 5)
+24V
INPUT 24VDC 6) 7) 5
24G
Q63RP
11) 11)
8) 8)
6
Figure 5.9 Power supply module
5 - 34
No. Name Application
9) Terminal cover Protective cover of the terminal block
Screw hole for securing a module to the base unit.
10) Module fixing screw hole
M3 12 screw (user-prepared) (Tightening torque : 0.36 to 0.48N•m)
11) Module mounting lever Used to mount a module on the base unit.
*1: Although the POWER LED turns on in red for a moment immediately after the power supply is turned on or off, redundant power supply
modules is not faulty.
5 - 35
CHAPTER5 POWER SUPPLY MODULE
1
A1S61PN A1S62PN A1S63P
9) 9) 9)
2
1) 1) 1)
3
8) 8) 8)
6
3) 4) 5) 7) 2) 3) 4) 5) 7) 3) 4) 6) 7)
● Do not wire to those terminals for which NC is stamped on the terminal block.
5 - 36
CHAPTER6 BASE UNIT AND EXTENSION CABLE
This chapter describes the specifications of the extension cables for the base units (the main base unit, slim type main
base unit, redundant power main base unit, extension base unit, redundant power extension base unit and redundant
type extension base unit) used in the programmable controller system and the specification standards of the extension
base unit.
6.1.1 Extension base units that can be combined with the main base unit
This section introduces extension base units that can be combined with the main base unit.
For details of the CPU module and power supply modules, refer to the following.
CPU module : CHAPTER 4
Power supply modules : CHAPTER 5
Table6.1 Extension base unit that can be combined with the main base unit
Slim type main base units do not have a connector for extension cable. Therefore, connection of extension base units and
GOT by bus is not available.
6-1
CHAPTER6 BASE UNIT AND EXTENSION CABLE
Type
Item
Q33B Q35B Q38B Q312B 4
Number of I/O modules
3 5 8 12
installed
Possibility of extension Extendable 5
Applicable module Q series modules
5 VDC internal current
0.11A 0.12A 0.13A
consumption 6
Mounting hole size M4 screw hole or 4.5 hole (for M4 screw)
H 98mm (3.86 inches)
External dimensions W 189mm (7.44 inches) 245mm (9.65 inches) 328mm (12.92 inches) 439mm (17.28 inches) 7
D 44.1mm (1.74 inches)
Weight 0.21kg 0.27kg 0.36kg 0.47kg
Attachment Mounting screw M4 14 4 pieces*1 (DIN rail mounting adapter is sold separately) 8
DIN rail mounting adapter
Q6DIN3 Q6DIN2 Q6DIN1
type
*1: The 5 base mounting screws are included with the Q38B and Q312B that have 5 base mounting holes.
Type
Item
Q32SB Q33SB Q35SB
Number of I/O modules
2 3 5
installed
Possibility of extension Not extendable
Applicable module Q series modules
5 VDC internal current
0.09A 0.10A
consumption
Mounting hole size M4 screw hole or 4.5 hole (for M4 screw)
H 98mm (3.86 inches)
External dimensions W 114mm (4.49 inches) 142mm (5.59 inches) 197.5mm (7.78 inches)
D 18.5mm (0.73 inches)
Weight 0.12kg 0.15kg 0.21kg
Attachment Mounting screw M4 12 4 pieces (DIN rail mounting adapter is sold separately)
DIN rail mounting adapter
Q6DIN3
type
6-2
(3) Redundant power main base unit
Table6.4 Redundant power main base unit specifications
Type
Item
Q38RB
Number of I/O modules
8
installed
Possibility of extension Extendable
Applicable module Q series modules
5 VDC internal current
0.12A
consumption
Mounting hole size M4 screw hole or 4.5 hole (for M4 screw)
H 98mm (3.86 inches)
External dimensions W 439mm (17.28 inches)
D 44.1mm (1.74 inches)
Weight 0.47kg
Attachment Mounting screw M4 14 5 pieces (DIN rail mounting adapter is sold separately)
DIN rail mounting adapter
Q6DIN1
type
Type
Item
Q38DB Q312DB
Number of I/O modules
8 12
installed
Possibility of extension Extendable
Applicable module Q series modules
5 VDC internal current
0.23A 0.24A
consumption
Mounting hole size M4 screw hole or 4.5 hole (for M4 screw)
H 98mm (3.86 inches)
External
W 328mm (12.92 inches) 439mm(17.30 inches)
dimensions
D 44.1mm (1.74 inches)
Weight 0.41kg 0.54kg
Attachment Mounting screw M4 14, 5 pieces (DIN rail mounting adapter is sold separately)
DIN rail mounting
Q6DIN1
adapter type
6-3
CHAPTER6 BASE UNIT AND EXTENSION CABLE
(5) Extension base unit (Type not requiring power supply module) 1
Table6.6 Extension base unit (Type not requiring power supply module) specifications
Type 2
Item
Q52B Q55B
Number of I/O modules
installed
2 5
3
Possibility of extension Extendable
Applicable module Q series modules
5 VDC internal current
0.08A 0.10A
4
consumption
Mounting hole size M4 screw hole or 4.5 hole (for M4 screw)
H 98mm (3.86 inches) 5
External
W 106mm (4.17 inches) 189mm (7.44 inches)
dimensions
D 44.1mm (1.74 inches)
Weight 0.14kg 0.23kg 6
Attachment Mounting screw M4 14, 4 pieces (DIN rail mounting adapter is sold separately)
DIN rail mounting
adapter type
Q6DIN3
7
Type
Item
Q63B Q65B Q68B Q612B QA1S65B QA1S68B QA65B QA68B
*2: The 5 base mounting screws are included with the Q68B and Q612B that have 5 base mounting holes.
6-4
(7) Redundant power extension base unit
Table6.8 Redundant power extension base unit specifications
Type
Item
Q68RB
Number of I/O modules
8
installed
Possibility of extension Extendable
Applicable module Q series modules
5 VDC internal current
0.12A
consumption
Mounting hole size M4 screw hole or 4.5 hole (for M4 screw)
H 98mm (3.86 inches)
External dimensions W 439mm (17.28 inches)
D 44.1mm (1.74 inches)
Weight 0.49kg
Attachment Mounting screw M4 14 , 5 pieces (DIN rail mounting adapter is sold separately)
DIN rail mounting adapter
Q6DIN1
type
Type
Item
Q65WRB
Number of I/O modules
5
installed
Possibility of extension Extendable
Applicable module Q series modules
5 VDC internal current
0.16A
consumption
Mounting hole size M4 screw hole or 4.5 hole (for M4 screw)
H 98mm (3.86 inches)
External dimensions W 439mm (17.28 inches)
D 44.1mm (1.74 inches)
Weight 0.52kg
Attachment Mounting screw M4 14 , 5 pieces (DIN rail mounting adapter is sold separately)
DIN rail mounting adapter
Q6DIN1
type
6-5
CHAPTER6 BASE UNIT AND EXTENSION CABLE
5) 4) 3
1) OUT
5V
SG
4
2) POWER
FG
CPU I/O0 I/O1 I/O2 I/O3 I/O4 IO5 I/O6 I/O7 I/O8 I/O9 I/O10 I/O11
3) 6)
6
Figure 6.1 Main base unit (Q33B, Q35B, Q38B, Q312B)
6-6
(2) Slim type main base unit (Q32SB, Q33SB, Q35SB)
3) 2)
SG
4) 1)
Figure 6.2 Slim type main base unit (Q32SB, Q33SB, Q35SB)
6-7
CHAPTER6 BASE UNIT AND EXTENSION CABLE
5) 4) 2
1) OUT
5V
SG
5V
SG
3
2) CPU I/O0 I/O1 I/O2 I/O3 I/O4 I/O5 I/O6 I/O7
FG FG
3) 6)
6-8
(4) Multiple CPU high speed main base unit (Q38DB, Q312DB)
5) 4)
1) OUT
5V
SG
a1 b1
POWER CPU I/O0 I/O1 I/O2 I/O3 I/O4 I/O5 I/O6 I/O7 I/O8 I/O9 I/O10 I/O11
2) FG
3) 6)
Figure 6.4 Multiple CPU high speed main base unit (Q38DB, Q312DB)
6-9
CHAPTER6 BASE UNIT AND EXTENSION CABLE
Q52B,Q55B 2
5)
6)
IN OUT
3)
3
2)
I/O0 I/O1 I/O2 I/O3 I/O4
1)
4
7) 4)
Q63B,Q65B,Q68B,Q612B
5)
5
6)
IN OUT
3)
2)
5V
SG
6
POWER I/O0 I/O1 I/O2 I/O3 I/O4 I/O5 I/O6 I/O7 I/O8 I/O9 I/O10 I/O11
1)
7
4) 7)
QA1S65B,QA1S68B
5) 8
6)
3) IN OUT
5V
2)
1)
4)
QA65B, QA68B
3) 8) 5) 4)
6)
1)
QA68B
2)
8) 5)
6 - 10
Table6.14 Part names
6 - 11
CHAPTER6 BASE UNIT AND EXTENSION CABLE
6) 5)
2
IN OUT
3)
5V 5V
2) SG SG
3
I/O0 I/O1 I/O2 I/O3 I/O4 I/O5 I/O6 I/O7
FG FG
1)
4
4) 7)
2) Base cover
Protective cover of extension cable connector.
Before connecting an extension cable, the part under OUT on the base cover must be
7
removed with a tool such as a flat blade screwdriver.
Connector for setting the number of bases of redundant power extension base units.
3) Base No. setting connector
( Section 6.1.4)
8
Connector for installing a redundant power supply module, I/O module and intelligent function
module.
4) Module connector
To the connectors unused, attach the supplied connector cover or the blank cover module
6 - 12
(7) Redundant extension base unit (Q65WRB)
5) 2) 4)
5V 5V
SG SG
1)
3) 6)
6 - 13
CHAPTER6 BASE UNIT AND EXTENSION CABLE
7
Figure 6.8 Connector
6 - 14
*1: If these base numbers are set, "BASE LAY ERROR" (error code: 2010) occurs.
*2: The extension base unit can be connected only when the serial number (first five digits) of the Redundant CPU is "09012"
or later and the redundant system is configured.
The extension base unit cannot be connected when the serial number (first five digits) of the Redundant CPU module is
"09011" or earlier.
*3: Connect the Q6 WRB to the first extension base. Since the Q6 WRB is fixed to the first extension base, base number
setting is not required.
*4: The Q6 WRB cannot be connected to the second extension base or later bases. Use the Q6 RB for the second
extension base or later bases.
● For the base number setting connector, set the number matched with the extension base number.
Do not set the same base number at two or more positions or do not fail to set a number. A miss-input or miss-output
may occur.
● In case of using the QA6ADP+A5 B/A6 B, set the same base number to both the base number setting connector of
the A5 B/A6 B and that of the QA6ADP.
6 - 15
CHAPTER6 BASE UNIT AND EXTENSION CABLE
4
(1) When only the Q5 B is connected to the extension base unit
Extension
I7 stage 7
6 - 16
Table6.19 Symbol
Symbol Description
V1 Voltage drop at the extension cable between the main base unit and extension base unit (Q5 B)
Voltage drop at the extension cable between the extension base unit (Q5 B) (extension base n-1) and extension base unit
Vn
(Q5 B) (extension base n)
R1 Extension cable resistance between the main base unit and extension base unit (Q5 B)
Extension cable resistance between the extension base unit (Q5 B) (extension base n-1) and extension base unit (Q5 B)
Rn
(extension base n)
l1 to l7 5VDC current consumption among extension base 1 to 7 *1
*1: Sum total of current consumed by Q5 B and currents consumed by the I/O, intelligent function modules loaded on the Q5 B.
The symbols including "I" (I1 to I7) vary with the modules loaded on the Q5 B. For details of the symbol, refer to the User's manuals of
the module used.
Table6.20 List for calculating voltage drops occurring at extension cables in system consisting of extensions 1 to 7
The voltage supplied to "IN" connector of the Q5 B in the final extension reaches 4.75 VDC or higher on the condition
that the sum total of voltage drop to "IN" connector of Q5 B (V) is 0.15V or lower.
6 - 17
CHAPTER6 BASE UNIT AND EXTENSION CABLE
(2) When the Q6 B is connected between the main base unit and the Q5 B 1
(a) Selection condition
4.75VDC or higher should be supplied to the "IN" connector of the Q5 B in the final extension. 2
(b) How to calculate voltage to "IN" connector
The 5VDC output voltage of the power supply module on the main base unit is set to at least 4.90VDC. 3
Therefore, the Q5 B can be used if the voltage drop is 0.15VDC or lower (4.9VDC -4.75VDC = 0.15VDC).
Table6.22 Symbol
5VDC current consumption when the extension base unit (Q5 B) is used as Extension n+1, n = 1 to 6, n: Extension number of
extension base unit (Q6 B) connected
In
(Sum total of current consumed by Q5 B and currents consumed by the I/O, intelligent function modules loaded on the
Q5 B.)
Extension cable resistance between the main base unit and the extension base unit (Q6 B) or the extension base unit
Rn
(Q6 B) and the extension base unit (Q6 B)
Rn+1 Extension cable resistance between the extension base unit (Q6 B) and extension base unit (Q5 B)
6 - 18
Table6.23 List for calculating voltage drops occurring at extension cables
when connecting Q6 B between main base unit and Q5 B
Position of extension base unit Voltage drop caused by extension cable from the main
Q6 B Q5 B base unit to the Q5 B IN connector (V)
Extension1 Extension 2 V=(R1+R2)I1
Extension 1, Extension 2 Extension 3 V=(R1+R2+R3)I2
Extension 1 to 3 Extension 4 V=(R1+R2+R3+R4)I3
Extension 1 to 4 Extension 5 V=(R1+R2+R3+R4+R5)I4
Extension 1 to 5 Extension 6 V=(R1+R2+R3+R4+R5+R6)I5
Extension 1 to 6 Extension 7 V=(R1+R2+R3+R4+R5+R6+R7)I6
The voltage supplied to the "IN" connector of the Q5 B reaches 4.75 VDC or later on the condition that the voltage
drop (V) at the extension cable between the main base unit and Q5 B is 0.15 VDC or lower.
GOT GOT
Extension
stage 3
Im
6 - 19
CHAPTER6 BASE UNIT AND EXTENSION CABLE
Table6.25 Symbol 1
Symbol Description
V Voltage drop at the extension cable between the main base unit and extension base unit (Q5 B)
5VDC current consumption when the extension base unit (Q5 B) is used as Extension n+1, n = 1 to 5, n: Extension number of
2
In the extension base unit (Q6 B) connected
(Sum total of current consumed by Q5 B and currents consumed by I/O, intelligent function modules loaded on the Q5 B)
5VDC current consumption of the GOT (current consumption per GOT is 255mA)
3
Im
• Im = 255 c (c: Number of GOTs connected (c: 1 to 5))
Rn
Extension cable resistance between the main base unit and extension base unit (Q6
and extension base unit (Q6 B)
B) or the extension base unit (Q6 B)
4
Rn+1 Extension cable resistance between the extension base unit (Q6 B) and extension base unit (Q5 B)
Table6.26 List of calculated voltage drop caused by the extension in bus connection of GOT
5
Position of extension base unit Number of bases
Voltage drop caused by extension cable from the
Q6 B Q5 B
for GOT bus
main base unit to the Q5 B IN connector (V) 6
connection
Extension 1 Extension 2 Extension 3 V=(R1+R2)(I1+Im)
Extension 1, Extension 2 Extension 3 Extension 4 V=(R1+R2+R3)(I2+Im)
7
Extension 1 to 3 Extension 4 Extension 5 V=(R1+R2+R3+R4)(I3+Im)
Extension 1 to 4 Extension 5 Extension 6 V=(R1+R2+R3+R4+R5)(I4+Im)
Extension 1 to 5 Extension 6 Extension 7 V=(R1+R2+R3+R4+R5+R6)(I5+Im)
8
The voltage supplied to the "IN" connector of the Q5 B reaches 4.75 VDC or later on the condition that the
voltage drop (V) at the extension cable between the main base unit and Q5 B is 0.15 VDC or lower.
6 - 20
6.2 Extension Cable
The extension cables are connected to transfer signals between a main base unit and an extension base unit or
between extension base units.
For specifications of the extension cables, refer to Section 6.2.1.
Type
Item
QC05B QC06B QC12B QC30B QC50B QC100B
Cable length 0.45m 0.6m 1.2m 3.0m 5.0m 10.0m
Conductor resistance value 0.044 0.051 0.082 0.172 0.273 0.530
Weight 0.15kg 0.16kg 0.22kg 0.40kg 0.60kg 1.11kg
When the extension cables are used in combination, overall distance of the combined cable must be 13.2 m (43.28 feet) or
less.
6 - 21
CHAPTER7 MEMORY CARD AND BATTERY
Q02CPU
Q03UD(E)CPU 8
Q02PHCPU Q04UD(E)HCPU
Q00JCPU Q02HCPU Q00UJCPU
Memory card *1 Q06PHCPU Q12PRHCPU Q06UD(E)HCPU
Q00CPU Q06HCPU Q00UCPU
Q12PHCPU Q25PRHCPU Q10UD(E)HCPU
Q01CPU Q12HCPU Q01UCPU
Q25PHCPU Q13UD(E)HCPU
Q2MEM-2MBS
SRAM card
Q3MEM-4MBS
Q3MEM-8MBS
Q2MEM-2MBF
Flash card
Q2MEM-4MBF
Q2MEM-8MBA
Q2MEM-32MBA
Note1
The Basic model QCPU, Q00U(J)CPU, Q01UCPU do not support memory cards.
7-1
7.1.2 Memory card specifications
The specifications of the memory card which can be used on the CPU module are compliant with those of the PCMCIA
small PC card.
Type
Item
Q2MEM-1MBS Q2MEM-2MBS Q3MEM-4MBS Q3MEM-8MBS
Memory size after format 1011.5K bytes 2034K bytes 4078K bytes 8172K bytes
Storable number of files 255 287 319
Number of insertions and removals 5000 times
H 45mm (1.77 inches) 74mm (2.91 inches)
External dimensions W 42.8mm (1.69 inches)
D 3.3mm (0.13 inches) 8.1mm (0.32 inches)
Weight 15g 30g 31g
Type
Item
Q2MEM-2MBF Q2MEM-4MBF
Memory size 2035K bytes 4079K bytes
Storable number of files 288
Number of insertions and removals 5000 times
Number of writings 100000 times
H 45mm (1.77 inches)
External dimensions W 42.8mm (1.69 inches)
D 3.3mm (0.13 inches)
Weight 15g
Type
Item
Q2MEM-8MBA Q2MEM-16MBA Q2MEM-32MBA
Memory size after format 7982K bytes*1 15982K bytes*1 31854K bytes
Storable number of files 512
Number of insertions and removals 5000 times
Number of writings 1000000 times
H 45mm (1.77 inches)
External dimensions W 42.8mm (1.69 inches)
D 3.3mm (0.13 inches)
Weight 15g
*1: The size of ATA cards after formating will be as follows when the manufacuturer control number of the card is E or earlier.
Manufacturer control number E: Q2MEM-8MBA: 7948K bytes, Q2MEM-16MBA: 15948K bytes
Manufacturer control number D or earlier: Q2MEM-8MBA: 7940k bytes, Q2MEM-16MBA: 15932K bytes
For the manufacturer control number, refer to "POINT" in this section.
*2: Up to 511 files can be stored in the Universal model QCPU.
7-2
CHAPTER7 MEMORY CARD AND BATTERY
1
When the ATA card is used, the value stored in the special register SD603 differs depending on the manufacturer control
number and CPU module type.
When the CPU module is the Universal model QCPU, the ATA card size is stored in SD603 in units of K bytes.
When the module is not the Universal model QCPU, 8000, 16000, or 32000 is stored in SD603 and the value depends on
2
the manufacturer control number and CPU module type
Table7.5 When the value stored in SD603 depending on manufacturer control number of the Q2MEM-8MBA
3
Value stored in special register SD603
Other than the Universal model QCPU
Manufacturer control No. and type of
ATA card type
Serial No. (first 5 Serial No. (first 5 Universal model 4
digits) is 09011 or digits) is 09012 or QCPU
earlier later
Q2MEM-8MBA 8000 8000 5
" " and
Q2MEM-16MBA 16000 16000
" D " or earlier
Q2MEM-32MBA 32000 32000
Q2MEM-8MBA 16000 8000 6
ATA card size
" E " Q2MEM-16MBA 16000 16000
(K bytes)
Q2MEM-32MBA 32000 32000
Q2MEM-8MBA 32000 16000 7
" F " or later Q2MEM-16MBA 32000 32000
Q2MEM-32MBA 32000 32000
8
The manufacturer control number (the third digit from the left) of the ATA card is described in the label on the back of the ATA
card. (Refer to Figure 7.1)
When character string including the manufacturer control number is 4digits, the third digit from the left is the manufacturer
control number, and when it is 3 digits, the manufacturer control number is "B".
7-3
7.1.3 Part names of the memory card
The part names of the memory card are described below.
1)
1)
3)
3)
4)
Write protect ON
"LOCK" Write protect ON
"RELEASE"
"LOCK"
2) "RELEASE" 4)
2)
7-4
CHAPTER7 MEMORY CARD AND BATTERY
4
Do not format an ATA card other than by GX Developer.
(If formatted using format function of Microsoft® Windows® Operating System, the ATA card may not be usable in a CPU
module.)
5
7
Note that the SRAM card memory is not backed up by the CPU module battery only.
Also, the program memory, standard RAM, and latch devices of the CPU module are not backed up by the battery installed
on the SRAM card.
8
7-5
7.1.5 Installing and removing a memory card
CPU module
main unit
Push
Memory card
7-6
CHAPTER7 MEMORY CARD AND BATTERY
MEMORY card
EJECT button
5
CPU module
main unit
Memory card
8
CPU module
main unit
7-7
(b) To remove the memory card
When removing a memory card from the CPU module main body, remove a memory card protective cover and
press the EJECT button to pull out the memory card.
Remove a cover,
pressing fixing claws
Remove the memory card of top/bottom
CPU module
main unit
Memory card
EJECT button
Push
CPU module
Press the EJECT button to eject main unit
a memory card.
Completed
When both "SM604" and "SM605" are off, remove the memory card according to the following procedure.
1) Turn on the special relay "SM609" using the sequence program or by the device test of GX Developer.
2) By monitoring GX Developer, check that the special relay "SM600" is turned off.
3) Remove the memory card.
SM600 (Memory card can be used) : The system is turned on when
memory card is ready to be used.
SM604 (memory card is being used) : The system is turned on when the
CPU module is using the memory
card.
SM605 (memory card removal prohibited) : Turned on by the user to disable a
removal of the memory card.
7-8
CHAPTER7 MEMORY CARD AND BATTERY
1
The following precautions must be observed when inserting or removing the memory card while the power is on.
● Note that the data in the memory card may be damaged if the above mentioned procedures are not performed
correctly. 2
Also, if the CPU module operation for an error is set to "Stop" in the Parameters, the CPU module stops its operation
upon the occurrence of “ICM.OPE.ERROR”.
● When the memory card is installed, the scanning time is increased by several 10ms max. 1 scan is only added, when
the CPU module executes mount processing.
3
● Poor insertion of the memory card may result in “ICM.OPE.ERROR”.
● Using the tweezers below is effective when the memory card cannot be removed smoothly.
4
Table7.7 Tweezers for replacing memory card
8
Figure 7.7 Memory card replacement using plastic tweezers
7-9
7.1.6 Specifications of the memory card battery
This section describes the specifications of the battery used for the memory card (SRAM card).
Type
Item
Q2MEM-BAT Q3MEM-BAT
Classification Graphite fluoride lithium primary battery Manganese dioxide lithium primary battery
Initial voltage 3.0V 3.0V
Nominal current 48mAh 550mAh
Battery life when stored Actually 5 years (room temperature)
Battery life when used Section 11.3.4.
Lithium content 0.014g 0.150g
Power failure backup for SRAM card Power failure backup for SRAM card
Application
(for Q2MEM-1MBS/Q2MEM-2MBS) (for Q3MEM-4MBS/Q3MEM-8MBS)
Remark
• For the life of the memory card battery, refer to Section 11.3.4.
• For the battery irective in EU member states, refer to Appendix 4.
7 - 10
CHAPTER7 MEMORY CARD AND BATTERY
4
RELEASE position
Battery holder
7
Insert the battery holder with which the
battery is installed firmly, into the SRAM ......
card.
8
Insert or remove the battery in the horizontal direction along the battery holder fixing guide.
Failure to do so may damage the latches of the battery holder.
Battery holder
Figure 7.9 Battery setting direction
7 - 11
(2) For Q3MEM-4MBS and Q3MEM-8MBS
Battery holder
LOCK
position
Completed
Polarity
Voltage
7 - 12
CHAPTER7 MEMORY CARD AND BATTERY
Note1
Note7.2 Basic
The Q7BAT and Q8BAT is not applicable to the Basic model QCPU.
7 - 13
7.2.2 Battery installation
Connector
Completed
(b) High Performance model QCPU, Process CPU, Redundant CPU and Universal model
QCPU
CPU module
Completed
7 - 14
CHAPTER7 MEMORY CARD AND BATTERY
Battery holder
7
Completed
8
Firmly push the connector all the way.
7 - 15
(3) Q8BAT-SET battery installation procedure
When changing the battery of the CPU module from the Q6BAT to the Q8BAT, install the battery and connect its
connector in the following procedure.
Connector of
battery
Q6BAT
Disconnect the connector connecting
the Q6BAT to the CPU module.
Connector
of cable
CPU module
(To next page)
7 - 16
CHAPTER7 MEMORY CARD AND BATTERY
Q8BAT
Mount the CPU module onto the main
base unit, so that the Q8BAT
2
connection cable connected to the
CPU module will not interfere with the
other devices.
3
Fix the Q8BAT onto the control panel.
(Screws or DIN rail is applicable.) 4
R (bending radius)
10mm (0.39 inch)
Attach the connector of Q8BAT
connection cable to the Q8BAT while
or more
5
confirming the orientation of the
connector.
6
Completed Q8BAT Q8BAT
connection cable
7
• Clamp the Q8BAT connection cable.
Failure to do so may damage the Q8BAT connection cover, connector, or the cable due to unintentional swinging
and shifting or accidental pulling of the cable. 8
• Provide 10mm (0.39 inches) or more of the bending radius for the Q8BAT connection cable.
If the bending radius is less than 10mm (0.39 inches), malfunction may occur due to characteristic deterioration
and wire breakage.
• For details of the module mounting position, refer to the following.
A Sticker
7 - 17
CHAPTER8 CPU MODULE START-UP PROCEDURES
This chapter provide the start-up procedure for the Q Series CPU module on the assumption that programs and
parameters have been created separately.
For the start-up procedures for a redundant system configured with a Redundant CPU, refer to the following.
QnPRHCPU User's Manual (Redundant System)
Start
8-1
CHAPTER8 CPU MODULE START-UP PROCEDURES
4
System reboot ••• CHAPTER 4
Turn off and on the system power supply, or reset the CPU module.
5
Error check ••• CHAPTER 4
Confirm that the ERR.LED of the CPU module is off.
If the ERR.LED is on or flashing, identify the error cause by the system monitor
of GX Developer or diagnostics* to eliminate the error cause.
6
If the error is related to the parameters or programs, correct them.
For details of the wiring, connection, and initial settings of intelligent function modules, special function modules, and net-
work modules, refer to relevant manuals for the network.
8-2
Memo
8-3
CHAPTER9 EMC AND LOW VOLTAGE DIRECTIVES
5
9.1 Requirements for Compliance with the EMC Directive
6
The EMC Directive specifies that products placed on the market must be so constructed that they do not cause
excessive electromagnetic interference (emissions) and are not unduly affected by electromagnetic interference
(immunity)". 7
Section 9.1.1 through Section 9.1.6 summarize the precautions on compliance with the EMC Directive of the
machinery constructed with the MELSEC-Q series programmable controllers.
These precautions are based on the requirements and the standards of the regulation, however, it does not guarantee 8
that the entire machinery constructed according to the descriptions will comply with above-mentioned directive. The
method and judgement for complying with the EMC Directive must be determined by the person who construct the
entire machinery.
9-1
9.1.1 Standards relevant to the EMC Directive
The standards relevant to the EMC Directive are listed in Table9.1.
9-2
CHAPTER9 EMC AND LOW VOLTAGE DIRECTIVES
9-3
9.1.3 Cables
The cables extracted from the control panel contain a high frequency noise component. On the outside of the control
panel, therefore, they serve as antennas to emit noise. To prevent noise emission, use shielded cables for the cables
which are connected to the I/O modules and intelligent function modules and may be extracted to the outside of the
control panel.
The use of a shielded cable also increases noise resistance.
The signal lines (including common line) of the programmable controller, which are connected to I/O modules,
intelligent function modules and/or extension cables, have noise durability in the condition of grounding their shields by
using the shielded cables. If a shielded cable is not used or not grounded correctly, the noise resistance will not meet
the specified requirements.
Screw
Paint mask
Shield cable
Figure 9.1 Part to be exposed Figure 9.2 Shield grounding (Correct example)
Note) The method of grounding with a vinyl-coated wire soldered onto the shielded section of the shielded
cable as in shown Figure 9.3 is not recommended. Doing so will raise the high-frequency impedance,
resulting in loss of the shielding effect.
Shield cable
Wire
Solderless terminal, crimp contact
Figure 9.3 Shield grounding (Incorrect example)
9-4
CHAPTER9 EMC AND LOW VOLTAGE DIRECTIVES
3
Shield Ground here
Figure 9.4 Double-shielded coaxial cable grounding
(3) Built-in Ethernet port QCPU module, Ethernet module, FL-net module, Web
5
server module, MES interface module
Precautions for using AUI cables, twisted pair cables and coaxial cables are described below.
• Always ground the AUI cables*1 connected to the 10BASE5 connectors. Because the AUI cable is a 6
shielded type, strip part of the jacket as shown in Figure 9.5 and ground the exposed shield section to the
ground as much as possible.
7
AUI cable
Shield 8
Figure 9.5 AUI cable grounding
Refer to (1) for the grounding of the shield.
*1: Make sure to install a ferrite core for the cable.
As a ferrite core, ZCAT2032 manufactured by TDK is recommended.
9.1.3 Cables
9.1 Requirements for Compliance with the EMC Directive
• Always use shielded twisted pair cables for connection to 10BASE-T and 100BASE-TX connectors.
• For the shielded twisted pair cable, remove a part of the jacket as shown in Figure 9.6 and ground the
exposed shield section to the ground as much as possible.
• Always use double-shielded coaxial cables as the coaxial cables*2 connected to the 10BASE2 connectors.
Ground the double-shielded coaxial cable by connecting its outer shield to the ground.
9-5
(4) Positioning module, channel-isolated pulse input module
Use shielded cables for the external wiring, and ground the shields of the external wiring cables to the control box
with the AD75CK cable clamp (Mitsubishi).
(Ground the shields 20 to 30cm away from the module.)
20 to 30cm
AD75CK (7.87 to 11.81 inch)
The AD75CK allows up to four cables to be grounded if the outside diameter of the shielded cable is about 7mm.
20 to 30cm
AD75CK (7.87 to 11.81 inch)
The AD75CK allows up to four cables to be grounded if the outside diameter of the shielded cable is about 7mm.
The required number of AD75CKs is indicated in Table9.2. (When cables of 7mm outside diameter are used for
all wiring.)
9-6
CHAPTER9 EMC AND LOW VOLTAGE DIRECTIVES
7
Inside control panel
8
QnPRHCPU
20 to 30cm
AD75CK (7.87 to 11.81 inch)
9.1.3 Cables
9.1 Requirements for Compliance with the EMC Directive
Figure 9.10 AD75CK cable clamp mounting position
9-7
9.1.4 Power supply part of the power supply module, Q00JCPU, and
Q00UJCPU
Always ground the LG and FG terminals after short-circuiting them.
The following describes the case where the MELSEC-A series module is used, using the QA1S6 B, QA6 B, and
QA6ADP+A5 B/A6 B as the extension base unit.
(1) Cable
Screw
Paint mask
Shield cable
Figure 9.11 Part to be exposed Figure 9.12 Shield grounding (Correct example)
Note) The method of grounding with a vinyl-coated wire soldered onto the shielded section of the shielded
cable as in shown Figure 9.13 is not recommended. Doing so will raise the high-frequency impedance,
resulting in loss of shielding effect.
Shield cable
Wire
Solderless terminal, crimp contact
Figure 9.13 Shield grounding (Incorrect example)
9-8
CHAPTER9 EMC AND LOW VOLTAGE DIRECTIVES
A1
SD
75 Cable clamp
Drive unit
6
Figure 9.14 When wiring with a 2 m (6.56 feet) or less cable
7
2) When wiring with cable that exceeds 2 m (6.56 feet), but is 10 m (32.79 feet) or less
• Ground the shield of the external device connection cable with a cable clamp. (Ground the shield at the
closest location to the A1SD75/AD75 external wiring connector.) 8
• Wire external device connection cables to drive modules and external devices by the shortest distance.
• Install a ferrite core.
Connector for external device connection
Power supply module
A1
Cable clamp
Drive unit
Figure 9.15 When wiring with cable that exceeds 2 m (6.56 feet), but is 10 m (32.79 feet) or less
9-9
3) Ferrite core and cable clamp types
• Cable clamp
Type : AD75CK (Mitsubishi)
• Ferrite core
Type : ZCAT3035-1330 (TDK ferrite core)
Required Qty
Cable length Prepared part
1 axis 2 axes 3 axes
Within 2 m (6.56 feet) AD75CK 1 1 1
AD75
20 to 30cm
AD75CK (7.87 to 11.81 inch)
9 - 10
CHAPTER9 EMC AND LOW VOLTAGE DIRECTIVES
6
DA DA DA
Terminal resistor (White) Terminal resistor
DB DB DB
(Yellow)
DG DG DG
SLD CC-Link SLD CC-Link SLD
FG dedicated FG dedicated FG 7
cable cable
Figure 9.18 Connection between CC-Link module/CC-Link station and FG line inside the control panel.
(Simplified figure)
8
• Use the external power supply that is CE compliant. Ground FG terminals.
• Power line connecting to the external power supply terminal (compliant with I/O power port of CE
standard) must be 30m (98.43 feet) or less. Power line connecting to module power supply terminal
(compliant with I/O power port of CE standard) must be 10m (32.81 feet) or less.
• The signal line connecting to the analog input of the following modules must be 30m or less.
AJ65BT-64RD3
AJ65BT-64RD4
AJ65BT-68TD
9 - 11
(2) Power supply module
The precautions required for each power supply module are described in Table9.5. Always observe the items
noted as precautions.
Model Precautions
A1S61P
A1S62P
Not usable
A61P
A62P
A1S63P *1
Use the CE marked 24VDC panel power equipment.
A163P
A1S61PEU
A1S62PEU
A1S61PN
A1S62PN
Always ground the LG and FG terminals after short-circuiting them.
A61PN
A61PEU
A62PEU
A68P
*1: If sufficient filter circuitry is built into the 24VDC external power supply module, the noise generated by A1S63P will be
absorbed by that filter circuit, so a line filter may not be required.
Filtering circuitry of version F or later of A1S63P is improved so that a external line filter is not required.
9 - 12
CHAPTER9 EMC AND LOW VOLTAGE DIRECTIVES
9.1.6 Others
9
(1) Ferrite core
A ferrite core has the effect of reducing radiated noise in the 30MHz to 100MHz band.
It is not required to fit ferrite cores to cables, but it is recommended to fit ferrite cores if shield cables pulled out of
2
the enclosure do not provide sufficient shielding effects.
Note that the ferrite cores must be fitted to the cables in the position immediately before they are pulled out of the
enclosure. If the fitting position is improper, the ferrite will not produce any effect.
3
The precautions required when installing a noise filter are described below. 6
• Do not bundle the wires on the input side and output side of the noise filter. When bundled, the output side
noise will be induced into the input side wires from which the noise was filtered.
7
Input side Input side
(power supply side) (power supply side)
Induction
9.1.6 Others
9.1 Requirements for Compliance with the EMC Directive
Filter Filter
The noise will be included when the Separate and lay the input
input and output wires are bundled. and output wires.
Figure 9.19 Precautions on noise filter
• Ground the noise filter grounding terminal to the control cabinet with the shortest wire possible (approx. 10
cm (3.94 inches)).
Remark
9 - 13
(3) Isolation transformer
An isolation transformer has an effect on reducing conducted noise (especially, lightning surge).
Lightning surge may cause a malfunction of the programmable controller.
As a measure against lightning surge, connect an isolation transformer as shown in Figure 9.20.
The use of an isolation transformer reduces an impact of lightning.
Programmable Isolation
Main controller power transformer
power supply supply
100VAC Programmable
200VAC controller
Relay
terminal block T1
I/O power supply
I/O equipment
Motor equipment
Inside a control panel
9 - 14
CHAPTER9 EMC AND LOW VOLTAGE DIRECTIVES
4
9.2.1 Standard applied for MELSEC-Q series programmable controller
The standard applied for MELSEC-Q series programmable controller is EN61131-2 safety of devices used in
measurement rooms, control rooms, or laboratories.
5
The MELSEC-Q series programmable controller which operate at the rated voltage of 50VAC/75VDC or above are
also developed to conform to the above standard. 6
The modules which operate at the rated voltage of less than 50VAC/75VDC are out of the Low Voltage Directive
application range.
For products with the CE mark, refer to the "Standard Compliance" menu of the MELFANSweb homepage. 7
9.2.2 MELSEC-Q series programmable controller selection
8
(1) Power supply module
There are dangerous voltages (voltages higher than 42.4V peak) inside the power supply modules of the 100/
200VAC rated I/O voltages. Therefore, the CE marked models are enhanced in insulation internally between the
9 - 15
9.2.3 Power supply
The insulation specification of the power supply module was designed assuming installation category II. Be sure to use
the installation category II power supply to the programmable controller.
The installation category indicates the durability level against surge voltage generated by a thunderbolt. Category I has
the lowest durability; category IV has the highest durability.
Category II indicates a power supply whose voltage has been reduced by two or more levels of isolating transformers
from the public power distribution.
9 - 16
CHAPTER9 EMC AND LOW VOLTAGE DIRECTIVES
Pollution level 1 : An environment where the air is dry and conductive dust does not exist. 3
Pollution level 2 : An environment where conductive dust
does not usually exist, but occasional temporary conductivity occurs due to the
accumulated dust. Generally, this is the level for inside the control box equivalent to IP54 in 4
a control room or on the floor of a typical factory.
Pollution level 3 : An environment where conductive dust exits and conductivity may be generated due to the
accumulated dust. 5
An environment for a typical factory floor.
Pollution level 4 : Continuous conductivity may occur due to rain, snow, etc. An outdoor environment.
As shown above, the programmable controller can realize the pollution level 2 when stored in a control panel 6
equivalent to IP54.
9 - 17
9.2.5 Grounding
There are the following two different ground terminals.
Use either ground terminal in an grounding status.
Protective grounding : Maintains the safety of the programmable controller and improves the noise resistance.
Table9.7 Intensive Insulation Withstand Voltage (Installation Category II, source : IEC 664)
9 - 18
CHAPTER10 LOADING AND INSTALLATION
8
(a) Overcurrent or overvoltage protection of the All outputs are All outputs are
power supply module is activated. turned off. turned off.
(b) The CPU module detects an error such as a All outputs are held or All outputs are
watchdog timer error by the self-diagnostic turned off according to
the parameter setting. turned off.
function.
All outputs may turn on when an error occurs in the part, such as I/O
10 - 1
When changing data of the running programmable controller from a
peripheral connected to the CPU module or from a personal computer
DANGER
connected to an intelligent function module, configure an interlock circuit
in the sequence program to ensure that the entire system will always
operate safely.
For program modification and operating status change, read relevant
manuals carefully and ensure the safety before operation.
Especially, in the case of a control from an external device to a remote
programmable controller, immediate action cannot be taken for a
problem on the programmable controller due to a communication failure.
To prevent this, configure an interlock circuit in the sequence program,
and determine corrective actions to be taken between the external
device and CPU module in case of a communication failure.
Do not install the control lines or communication cables together with the
main circuit lines or power cables.
CAUTION
Keep a distance of 100mm (3.94 inches) or more between them.
Failure to do so may result in malfunction due to noise.
When a device such as a lamp, heater, or solenoid valve is controlled
through an output module, a large current (approximately ten times
greater than normal) may flow when the output is turned from off to on.
Take measures such as replacing the module with one having a
sufficient current rating.
When the programmable controller is powered on and off, normal control output may not be done momentarily due to
a delay or a start-up time difference between the programmable controller power supply and the external power supply
(DC in particular) for the control target.
For example, if the external power supply for the controlled object is switched on in a DC output module and then the
programmable controller power supply is switched on, the DC output module may provide false output instantaneously
at power-on of the programmable controller. Therefore, it is necessary to make up a circuit that can switch on the
programmable controller power supply first.
Also, malfunction may occour if an external power supply or the programmable controller is faulty.
To prevent any malfunction which may affect the whole system and in a fail-safe viewpoint, provide a external circuit to
the areas which can result in machine breakdown and accidents (e.g. emergency stop, protective and interlock
circuits) must be constructed outside the programmable controller.
The following page gives examples of system designing in the above viewpoint.
10 - 2
CHAPTER10 LOADING AND INSTALLATION
(1) System design circuit example (when not using ERR. terminal of power supply 9
module, or using Q00JCPU)
FOR AC
Power supply
FOR AC/DC 10
Power supply
Transformer Transformer
Transformer
Input switched when
power supply
Fuse Fuse 3
Fuse
established. CPU module
CPU module
RUN/STOP circuit SM52 DC power
SM52
Ym interlocked with RA1
SM403
Ym
(-) (+) 4
(run monitor relay)
SM403 Yn Fuse
Yn XM Set time for DC power
TM
5
supply to be
Program established.
TM
MC1 NO M10
START SW RA1 NO
MC M10
MC STOP SW
Program
Input module START SW RA1
MC
6
MC STOP SW
Output module
Low battery alarm RA2
Ym
L
(Lamp or buzzer) RA2
XM
Voltage relay is
recommended 7
ON when run by
Yn SM403
RA1
8
Low battery alarm
Output module
Output module MC (Lamp or buzzer)
Power to output Ym
equipment switched ON when run by SM403
L
MC OFF when the STOP
signal is given. Yn
In the case of an RA1
emergency stop or a
MC2
10 - 3
(2) System design circuit example (when using ERR. terminal of power supply
module)
Power supply
FOR AC/DC
Transformer Transformer
Fuse Fuse
Input switched
when power supply
established. CPU module
SM52 DC power
Ym
RUN/STOP circuit (-) (+)
SM403
interlocked with RA1 Yn Fuse
(run monitor relay)
XM Set time for DC power
TM supply to be established.
TM
NO MC1 NO M10
M10
Program
START SW
RA1 RA3
MC
MC STOP SW
RA2
RA2 Voltage relay is
XM recommended
Output module
Ym Low battery alarm
L (Lamp or buzzer)
Yn
RA1
Output module
MC MC
Interlock circuits as
necessary. Output by ERR contact OFF
Provide external Power OFF of equipment
interlock circuits for
conflicting operations, In the case of an
such as forward rotation MC2 emergency stop or a
and reverse rotation, and MC1 stop caused by a limit
for parts that could switch.
damage the machine or MC1
cause accidents if no MC2
interlock were used.
For AC/DC
10 - 4
CHAPTER10 LOADING AND INSTALLATION
Output
Input
Input
Input
Input
6
Extension cable
7
No. of slots 16 points 16 points 16 points 16 points 16 points
8
Output
Output
Output
Empty
*1: The output module for fail-safe purpose must be mounted in the last slot of the system. (Y80 to Y8F in the above system.)
10 - 5
On delay time
Y80 Y8F L
24V
0.5s 0.5s
0V
DC24V
10 - 6
CHAPTER10 LOADING AND INSTALLATION
5
(1) Power consumption of power supply module
The power conversion efficiency of the power supply module is approx. 70 %, while 30 % of the output power is
consumed as heat. As a result, 3/7 of the output power is the power consumption. 6
Therefore the calculation formula is as follows.
3
W PW = ×{(I5V×5) + (I15V×15) + (I24V×24)} (W)
7 7
I5V: Current consumption of logic 5 VDC circuit of each module
I15V: Current consumption of 15VDC external power supply part of intelligent function
module 8
I24V: Average current consumption of 24VDC power supply for internal consumption of the
output module
(2) Total power consumption for 5VDC logic circuits of all modules
(including CPU module)
The power consumption of the 5 VDC output circuit section of the power supply module is the power consumption
of each module*1 (including the current consumption of the base unit).
W5V = I5V 5 (W)
*1: For the power consumption of the motion CPU and PC CPU module, refer to the instruction manuals of the
corresponding modules.
10 - 7
(3) A total of 24 VDC average power consumption of the output module
(power consumption for simultaneous ON points)
The average power of the external 24 VDC power is the total power consumption of each module.
W24V = I24V 24 Simultaneous ON rate (W)
(4) Average power consumption due to voltage drop in the output section of the
output module
(Power consumption for simultaneous ON points)
(5) Average power consumption of the input section of the input module
(Power consumption for simultaneous ON points)
(6) Power consumption of the external power supply section of the intelligent
function module
The total of the power consumption values calculated for each block becomes the power consumption of the overall
sequencer system.
W = WPW+W5V+W24V+WOUT+WIN+WS (W)
From this overall power consumption (W), calculate the heating value and a rise in ambient temperature inside the
panel.
The outline of the calculation formula for a rise in ambient temperature inside the panel is shown below.
W
T= C
UA
W : Power consumption of overall sequencer system (value obtained above)
A : Surface area inside the panel
U : When the ambient temperature inside the panel is uniformed by a fan......6
When air inside the panel is not circulated..................................................4
If the temperature inside the panel has exceeded the specified range, it is recommended to install a heat exchanger to the
panel to lower the temperature.
If a normal ventilating fan is used, dust will be sucked into the programmable controller together with the external air, and it
may affect the performance of the programmable controller.
10 - 8
CHAPTER10 LOADING AND INSTALLATION
Q35B
QX40 Q62DA
4
QY40P QJ71LP21-25
Figure 10.5 System configuration
5
(b) 5VDC/24VDC current consumption of each module
Table10.1 5VDC/24VDC current consumption
(f) Average power consumption due to voltage drop in the output section of the output
module
WOUT = 0.1 0.2 16 1 = 0.32(W)
(g) Average power consumption of the input section of the input module
WIN = 0.004 24 32 1 = 3.07(W)
(h) Power consumption of the external power supply section of the intelligent function
module
WS = 0.12 24=2.88(W)
The value of the heat generated in a redundant system configuration (when the Redundant CPU is used) is the sum of the
two values for the control and standby systems, each of which is calculated by the same method as that for the single
system.
10 - 9
10.3 Module Installation
10 - 10
CHAPTER10 LOADING AND INSTALLATION
In case of using the QA1S6 B, when installing the base unit to DIN rail in an environment of frequent vibration, use a 4
vibration-proofing bracket (A1S-PLT-D). Mounting the vibration-proofing bracket (A1S-PLT-D) enhances the resistance to
vibration.
Depending on the environment to install the base unit, it is also recommended to secure the base unit directly to the control
panel. 5
This section gives instructions for handling the CPU, I/O, intelligent function and power supply modules, base units and 6
so on.
• Module enclosure, terminal block connectors and pin connectors are made of resin; do not drop them or
subject them to strong impact. 7
• Do not remove module's printed circuit boards from the enclosure in order to avoid changes in operation.
• Tighten the module fixing screws and terminal block screws within the tightening torque range specified
shown in Table10.2. 8
Table10.2 Tightening torque range
• Be sure to install a power supply module in the power supply installation slot of Q3 B, Q3 SB, Q3 RB,
Q3 DB, Q6 B, Q6 RB, Q6 WRB, QA1S6 B or QA6 B.
Even if the power supply module is not installed, when the I/O modules and intelligent function module
installed on the base units are of light load type, the modules may be operated.
In this case, because a voltage becomes unstable, we cannot guarantee the operation.
• When using an extension cable or a tracking cable, keep it away from the main circuit cable (high voltage
and large current).
Keep a distance of 100mm (3.94 inches) or more from the main circuit.
• The following are precautions on use in combination with a module whose depth is 130mm or more (Q66DA-
G).
1) A module that is less than 130mm in depth cannot be mounted between modules that are 130mm or more
in depth.
2) A module that is less than 130mm in depth cannot be mounted on the right side of a module that is 130mm
or more in depth.
3) If a module that is 130mm or more in depth is mounted in slot 0 with the Q64P(N) used as power supply,
operations such as installing or removing a CPU memory card may be difficult.
Although there is no problem with the operation behavior, if it is inconvenient, mount a module that is less
than 130mm in depth in slot 0 or leave the slot empty.
10 - 11
Install a main base unit, Q00JCPU, and Q00UJCPU (by screwing) in the following procedure.
4) Fit the two base unit top mounting screws into the enclosure.
Panel
Figure 10.6 Installing a main base unit,Q00JCPU, and Q00UJCPU
5) Place the right-hand side notch of the base unit onto the right-hand side screw.
Panel
Figure 10.7 Installing a main base unit, Q00JCPU, and Q00UJCPU
6) Place the left-hand side pear-shaped hole onto the left-hand side screw.
Panel
Figure 10.8 Install a main base unit, Q00JCPU, and Q00UJCPU
7) Fit the mounting screws into the holes at the bottom of the base unit, and then
retighten the all mounting screws.
• Install the main base unit, Q00JCPU, and Q00UJCPU on the panel while no module is mounted in the right-end
slot on the base.
When removing the base from the panel, remove the module mounted on the right-end slot first and then the base
unit.
• The mounting screws that provided with the slim type main base unit differ from those provided with other types of
the base unit.
For mounting screws for the slim type main base unit, order "cross recessed head bind screw M4 x 12 (black)."
10 - 12
CHAPTER10 LOADING AND INSTALLATION
Insert the adaptor (large) into the grooves of Push the bottom of the adaptor (large) far enough
the base unit from below. until it "clicks".
Figure 10.9 Adaptor installation method
10 - 13
(c) Applicable DIN rail types (IEC 60715)
TH35-7.5Fe
TH35-7.5Al
TH35-15Fe
35mm
(1.38 inch)
P P P
<For Q38B, Q312B, Q68B, Q612B, Q38RB, Q68RB, Q65WRB, Q38DB or Q312DB type>
Screw the DIN rail in three places using the mounting screws and square washers included with the DIN rail
mounting adaptors (hereafter referred to as the adaptors) in ‘Position A’ (bottom of base unit).
B *3 A *2 B *3
35mm
Stopper
P P P P
Stopper
P=200mm (7.88 inch) or less
Figure 10.11 Distance between DIN rail mounting screws
10 - 14
CHAPTER10 LOADING AND INSTALLATION
<For Q00JCPU, Q00UJCPU, Q33B, Q35B, Q65B, Q52B, Q55B, Q63B, Q32SB, Q33SB or Q35SB type>
Screw the DIN rail in two places using the mounting screws and square washers included with the adaptors in 9
‘Position A’ (bottom of base unit).
B *3 A *2 B *3
Mounting screws
(included with adaptors)
Mounting screws (obtained by user) 10
DIN rail Square washers necessary *1 No square washers
35mm
3
Stopper
Stopper
P P P 4
P=200mm (7.88 inch) or less
Figure 10.12 Distance between DIN rail mounting screws
5
*1: The following shows where to position the square washers.
6
Square washer DIN rail Mounting screws DIN rail
7
square washer Mounting side
(e.g. Control panel)
Mounting screws 8
(M5 10) Side view A Side view A
Figure 10.13 Square washer
*2: Screw the DIN rail to a control panel using the mounting screws and square washers included with the adaptors in
‘Position A’ (bottom of base unit).
● Use only one washer for each mounting screw. Use only the square washers supplied with the adaptors.
If two or more washers are used together for one mounting screw, the screw may interfere with the base unit.
● Make sure to align the square washer sides with the DIN rail.
10 - 15
(e) Stopper mounting
When using the DIN rail in the environment with frequent vibration, use stoppers included with the DIN rail
mounting adaptor shown in (a).
Hook
2) Hitch the lower hook of the stopper
to the bottom of the DIN rail. Install
the stopper with the arrowhead side 3) Hitch hook to top of
facing up. DIN rail
5)
5) Tighten the screw of the stopper DIN rail
with a screwdriver.
(Tightening torque 1.00 to 1.35N m) (Left side)
4) Stopper
5)
DIN rail
(Right side)
Make sure that the left and right
stoppers are fixed securely to the
DIN rail. Stopper Stopper
Complete
10 - 16
CHAPTER10 LOADING AND INSTALLATION
In addition, when three or more modules with 130mm or more in depth (such as Q66DA-G etc.) are mounted,
or when the base unit is used in the environment with extremely frequent vibration, use the Q6DIN1A Q-type 9
base DIN rail mounting adaptor (vibration-proofing bracket kit) where the large mounting bracket is included.
The large mounting bracket enables to enhance the resistance to vibration. Depending on the environment, it is
recommended to mount the base unit directly on the control panel. 10
1) Q6DIN1A applicable models
Q00JCPU, Q00UJCPU, Q33B, Q35B, Q38B, Q312B, Q32SB, Q33SB, Q35SB, Q38RB, Q38DB, Q312DB,
Q52B, Q55B, Q63B, Q65B, Q68B, Q612B, Q68RB, Q65WRB
3
Table10.4 Q-type base DIN rail mounting adaptor (Vibration-proofing bracket kit) included parts
6
When stoppers are used, the dimension of stoppers need to be considered in the unit installation dimensions. Refer to a
CPU user's manual for the base unit dimensions (W). 7
Base unit
Stopper Stopper
(1.93) (1.93)
49
35(1.38)
98(3.86)
49
Unit: mm (inch)
Figure 10.16 Base unit external dimensions (Front face)
10 - 17
(f) Dimensions when DIN rail is attached (Side view).
Board side
DIN rail depth (D)
TH35-7.5Fe, TH35-7.5Al:7.5 (0.30) D 7.5 Base unit Power supply module
TH35-15Fe:15 (0.59) (0.30)
5
(0.20)
(49 (1.93))
DIN rail: TH35-7.5Fe,
TH35-7.5Al,
TH35-15Fe
98 (3.86)
35 (1.38)
(49 (1.93))
(0.12)
3
Example) Q64PN Power supply module = 115 (4.53)
Unit: mm (inch)
Figure 10.17 External dimensions (Side face)
10 - 18
CHAPTER10 LOADING AND INSTALLATION
6
Panel Door
4 30mm(1.18 inch)
20mm
(0.79 inch) 7
or more
or more
3
4, 5
8
5mm (0.20 inch) or more 2, 6 5mm (0.20 inch) or more 6
*1: For wiring duct with 50mm (1.97 inches) or less height.
10 - 19
(b) In case of slim type main base unit
Indicates the panel top, wiring duct or any
part position.
Panel Door
20mm
(0.79 inch)
4 30mm (1.18 inch)
or more
or more
3
4, 5
*1: For wiring duct with 50mm (1.97 inches) or less height.
40mm (1.58 inches) or more for other cases.
*2: The cable of the power supply module of the slim type main base unit protrudes out of the left end of the module. Install
the module while reserving 17mm (0.67 inches) or more wiring space.
If the cable sheath is susceptible to damage caused by a structural object or part on the left side of the module, take a
protective measure with spiral tube or a similar insulator.
*3: 80mm (3.15 inches) or more for the connector type. 80mm (3.15 inches) or more for installing the Q8BAT cable when
using the Q8BAT.
*4: 45mm (1.77 inches) or more when the Q7BAT is mounted.
*5: 30mm (1.18 inches) or more from the top and bottom of the Q8BAT when the Q8BAT is mounted.
*6: 5mm (0.20 inches) or more from the right and left of the Q8BAT when the Q8BAT is mounted.
Figure 10.19 Module mounting position
Horizontal installation
Vertical mounting
Figure 10.21 Orientation in which modules cannot be mounted
10 - 20
CHAPTER10 LOADING AND INSTALLATION
7
At least
50mm (1.97 inch)
At least At least 8
100mm 50mm (1.97 inch)
(3.94 inch)
10 - 21
10.3.3 Installation and removal of module
This section explains how to install and remove a power supply, CPU, I/O, intelligent function or another module to and
from the base unit.
(1) Installation and removal of the module from Q3 B, Q3 SB, Q3 RB, Q3 DB,
Q5 B, Q6 B, Q6 RB and Q6 WRB
module Module
fixing hook mounting lever
( 2)
Using the module fixing hole Module fixing
as a supporting point, push projection
the module in the derection
Module connector
of arrow until it clicks.
Base unit
Module fixing hole
Module fixing
projection ( 1) Module
Module
Make sure that the module mounting lever
is inserted in the base unit
securely.
Module protection
Completed
10 - 22
CHAPTER10 LOADING AND INSTALLATION
*1: If the module has two module fixing projections, insert the two module fixing projections on the right and left into the
module fixing holes so that they are not misaligned. 9
Module hook
Base unit hook
10
Q6 RP
3
4
Center top
5
Push
6
Figure 10.24 Mounting the Q6 RP
*2: If the module has two module fixing projections on its top, push the center top of the module so that the two module fixing
hooks on the right and left are securely engaged with the base unit hooks.
7
● When mounting the module, always insert the module fixing projection into the module fixing hole of the base unit.
At that time, securely insert the module fixing projection so that it does not come off from the module fixing hole.
8
Failure to do so may damage the module connector and module.
● When using the programmable controller in an environment of frequent vibration or impact, secure the CPU module to
the base unit using screws.
Module fixing screw : M3 X 12 (user-prepared)
10 - 23
(b) Removal from Q3 B, Q3 SB, Q3 RB, Q3 DB, Q5 B, Q6 B, Q6 RB, and
Q6 WRB
Support the module with both
hands and securely press the
module fixing hook(*1) with your
finger.
Push
Lifting
Unit/Module
While lifting the module, take off
the module fixing projection (*2) Base unit
from the module fixing hole.
Module fixing hole
Completed
*1: If the module has two module fixing hooks on its top, push the two modules fixing projections on the right and left of the
module top simultaneously with your fingers until they stop.
Push simultaneously
When removing the module which is secured by module fixing screw, remove the module fixing screw first and then module
fixing projection off the module fixing hole of the base unit.
Failure to do so may damage the module fixing projection.
10 - 24
CHAPTER10 LOADING AND INSTALLATION
Module
3
connector
8
Completed
Make sure to mount the module with the module fixing projection inserted into the module fixing hole, using the module fixing
screws.
Failure to do so may damage the module connector and module.
10 - 25
(b) Removal from QA1S6 B
Remove the module
mounting screw, and
using the bottom of the Base unit
module as a support,
pull the top of the
module toward you.
Module connector
Unit/Module
Completed
When removing the module which is secured by module fixing screw, remove the module fixing screw first and then module
fixing projection off the module fixing hole of the base unit.
Failure to do so may damage the module fixing projection.
10 - 26
CHAPTER10 LOADING AND INSTALLATION
10 - 27
For use in an environment with particularly frequent vibrations and/or shock, secure the module to
the base with screws. The applicable screw size is M4(0.16) 0.7(0.03) 12mm (0.47 inches).
Refer to the figure on the right.
To mount a module, Insert the module fixing projection(s) into the fixing
hole(s) in the base unit and press the module until it snaps into place.
CAUTION
Incorrect mounting may cause malfunction, failure, or a drop of the
module.
When using in an environment of frequent vibrations, secure the module
with a screw.
Tighten the screw within the specified torque range.
Undertightning can cause drop of the screw, circuit or malfunction.
Overtightning can damage the screw and/or module, resulting in drop,
short circuit, or malfunction.
10 - 28
CHAPTER10 LOADING AND INSTALLATION
10
Disengage the hook from the module fixing hole (A) and then remove the module fixing projection from the module fixing
hole (B). Attempting to remove the module forcibly may damage the hook or module fixing projection.
10 - 29
10.4 How to set the Base Number for the Extension Base Unit
When using two or more extension base units, the base number must be set with their base number setting
connectors.*1
(The number of extension bases is set to 1 by factory default.)
*1: Since the Q6 WRB is fixed to the extension 1, extension base No. setting is not required.
1) The base number setting connector of the extension base unit is located under the IN side base cover.
(Setting of the extension number setting connector ( Section 6.1.4))
First, loosen the upper and lower screws in the IN side base cover and remove the base cover from the
extension base unit.
Fixing screw
2) Insert the connector pin in the required base number location of the connector (PIN1) existing between the
IN and OUT sides of the extension cable connector.
Connector pin
10 - 30
CHAPTER10 LOADING AND INSTALLATION
3) Install the base cover to the extension base unit and tighten the base cover screw.
(Tightening torque: 0.36 to 0.48N•m) 9
Fixing screw
Base cover
Base cover
Flat blade screwdriver 4
Figure 10.31 Base cover removal procedure
5
Set the numbers for extension base units in the order of connecting, starting from the one connected to the main base unit.
10.4 How to set the Base Number for the Extension Base Unit
10 - 31
(2) Precautions for setting the extension base numbers
Power supply
CPU module
module
Extension base unit
Q68B
12 13 14 15 16 17 18 19 Extension 1
Q68B
0 0 0 0 0 0 0 0 Extension 2
Skipped
stage number
Q68B
20 21 22 23 24 25 26 27 Extension 3
Figure 10.32 The number of slots when a extension base number is skipped
10 - 32
CHAPTER10 LOADING AND INSTALLATION
Power supply
module
CPU module 4
Extension base unit
Q68B 5
Extension 1
6
The same extension stage
7
Q68B number cannot be set!
Extension 1
10.4 How to set the Base Number for the Extension Base Unit
Figure 10.33 When the same extension number is set
10 - 33
(c) When connector pins are connectd in more than 2 positions, or no pin is used
The extension base unit cannot be used when connector pins for base number setting are inserted in more
than two positions and when not using any connector pin.
Power supply
CPU module
module
Extension base unit
Q68B
Extension 1
Connector pins must not be
inserted in 2 or more positions!
Q68B
Extension 2
Connector pin must be inserted!
Figure 10.34 Connector pins are used in 2 positions, and not using any connector pin
10 - 34
CHAPTER10 LOADING AND INSTALLATION
(d) Extension base positioning for AnS/A series-compatible extension base units 9
(QA1S6 B, QA6 B, and QA6ADP+A5 B/A6 B)
When using AnS/A series-compatible extension base units in combination, connect Q5 B/Q6 B closest to
the main base unit, and then QA1S6 B, QA6 B, and then QA6ADP+A5 B/A6 B.
10
Note that the QA1S6 B and QA6ADP+A5 B/A6 B cannot be used in combination.
5
Power supply
module CPU module
QA1S68
8
20 21 22 23 24 25 26 27
Extension 2 Extension base unit for
mounting module corresponding
to the AnS series (QA1S6 B is
connected to the main base unit,
10.4 How to set the Base Number for the Extension Base Unit
the end of the Q5 B/Q6 B or
QA1S6 B)
QA68B
28 29 30 31 32 33 34 35
Extension 3
Extension base unit for mounting
module corresponding to the A
series 2 (QA6 B is connected to
the main base unit, the end of
the Q5 B/Q6 B/QA1S6 B or
QA6 B)
Figure 10.35 Extension base positioning for the AnS/A series-compatible extension base units
*1: When using the QA6ADP+A5 B/A6 B, connect it below the QA6 B.
10 - 35
10.5 Connection and Disconnection of Extension Cable
Connector
Ferrite core
Extension cable
Holding the ferrite core may cause the cable disconnection in the connector.
Also, if the ferrite core position is shifted, the characteristic will change. When handling the cable, do not to shift
the ferrite core position.
10 - 36
CHAPTER10 LOADING AND INSTALLATION
10
When connecting an extension base unit to the main base unit with an extension cable, plug the OUT side connector of the
main base unit and the IN side connector of the extension base unit with an extension cable. The system will not operate
properly if the extension cable is connected in the form of IN to IN, OUT to OUT or IN to OUT.
When connecting two or more extension base units, plug the OUT side connector of the first extension base unit and the IN
side connector of the second extension base unit with an extension cable.
3
• To connect an extension cable to the main base unit, remove the portion under the OUT characters on the
4
base cover with a tool such as a flat blade screwdriver (5.5 75, 6 100).
This also applies to a case where an extension cable is connected to the OUT side connector of the
extension base unit.
5
When connecting an extension cable to the Q00JCPU and Q00UJCPU, remove the base cover manually.
To remove the base cover, insert the tip of a screwdriver into a clearance below the base cover and pry it up.
Be careful not to damage the connector when inserting the screw driver since a connector is located inside
6
the base cover.
Main base unit Extension base unit
Base cover
Cut at 3 places
of thin wall
OUT side of
base cover
Cut at 3 places
of thin wall
7
10 - 37
• To connect the extension cable to the next extension base unit, remove the sticker put under the IN
characters on the base cover.
Extension base unit
IN side of
base cover
Seal
• When plugging the extension cable to any base unit, hold the connector part of the extension cable.
Connector
Extension cable
• After fitting the extension cable, always tighten the extension cable connector fixing screws.
(Tightening torque: 0.20N•m)
Fixing screw
10 - 38
CHAPTER10 LOADING AND INSTALLATION
10.6 Wiring
9
Shut off the external power supply for the system in all phases before 3
wiring.
DANGER
Failure to do so may result in electric shock or damage to the product.
After wiring, attach the included terminal cover to the module before 4
turning it on for operation.
Failure to do so may result in electric shock.
5
Ground the FG and LG terminals to the protective ground conductor
dedicated to the programmable controller.
CAUTION
Failure to do so may result in electric shock or malfunction. 6
Check the rated voltage and terminal layout before wiring to the module,
and connect the cables correctly.
Connecting a power supply with a different voltage rating or incorrect 7
wiring may cause a fire or failure.
Connectors for external connection must be crimped or pressed with the
tool specified by the manufacturer, or must be correctly soldered. 8
Incomplete connections could result in short circuit, fire, or malfunction.
Tighten the terminal screws within the specified torque range.
Undertightning can cause short circuit, fire, or malfunction.
10 - 39
This section describes the precautions for wiring power supply lines.
Programmable Isolation
Main controller power transformer
power supply supply
100VAC Programmable
200VAC controller
Relay
terminal block T1
I/O power supply
I/O equipment
Motor equipment
Inside a control panel
• Do not connect the 24VDC outputs of two or more power supply modules in parallel to supply power to one
I/O module. Parallel connection will damage the power supply modules.
Power supply module I/O module Power supply module I/O module
DC24V
10 - 40
CHAPTER10 LOADING AND INSTALLATION
• Momentary power failure may be detected or the CPU module may be reset due to serge caused by
lightening. 9
As measures against serge caused by lightening, connect a surge absorber for lightening as shown in
Figure 10.43.
Using the surge absorber for lightening can reduce the influence of lightening. 10
Programmable
controller 3
AC
I/O devices
4
E1 E1 E2
5
E1 Surge absorber for lightening
7
● Separate the ground of the surge absorber for lightening (E1) from that of the programmable controller (E2).
● Select a surge absorber for lightening whose power supply voltage does no exceed the maximum allowable circuit
voltage even at the time of maximum power supply voltage elevation.
8
10 - 41
(2) Wiring of I/O equipment
• Insulation-sleeved crimping terminals cannot be used with the terminal block.
It is recommended to cover the wire connections of the crimping terminals with mark or insulation tubes.
• The wires used for connection to the terminal block must be 0.3 to 0.75mm2 in core and 2.8mm (0.11 inches)
max. in outside diameter.
• Run the input and output lines away from each other.
• When the lines cannot be run away from the main circuit and power lines, use a batch-shielded cable and
ground it on the programmable controller side.
In some cases, ground it in the opposite side.
Programmable
controller
Shield cable
Input
RA
Output Shield jacket
DC
Figure 10.44 Wiring of I/O equipment
10 - 42
CHAPTER10 LOADING AND INSTALLATION
(3) Grounding 9
For grounding, perform the following:
• Use a dedicated grounding wire as far as possible. (Grounding resistance of 100
• When a dedicated grounding cannot be provided, use (2) Common grounding shown below.
or less.)
10
Programmable
controller
Another
equipment
Programmable
controller
Another
equipment
Programmable
controller
Another
equipment
3
Grounding Grounding
4
(1) Independent grounding Best (2) Common grounding Good (3) Joint grounding Not allowed
10 - 43
10.6.2 Connecting to the power supply module
The following figure shows the wiring example of lines such as power lines and grounding lines to the main base unit
and extension base units.
Fuse
ERR 1
AC
DC FG
24VDC
LG
INPUT
100-120VAC
Connect to 24VDC
terminals of I/O module
that requires 24VDC
internally. Extension base unit
(Q68B)
Extension cable Q61P-A1 I/O module
ERR 1
FG
100VAC LG
INPUT
100-120VAC
Ground wire
Grounding
● Use the thickest possible (max. 2 mm2 (14 AWG)) wires for the 100/200VAC and 24VDC power cables. Twist these
wires starting at the connection terminals. Use a solderless terminal for wiring a terminal block. To prevent short-circuit
due to loosening screws, use the solderless terminals with insulation sleeves of 0.8 mm (0.03 inches) or less.
Note that up to two solderless terminals can be connected per terminal block.
Solderless terminals Terminal block
with insulation sleeves
10 - 44
CHAPTER10 LOADING AND INSTALLATION
AC
10
Redundant power main base unit
(Q38RB)
Q64RP Q64RP CPU module
3
4
2, 3 2, 3
ERR ERR
100V/200VAC FG FG
LG LG
AC INPUT INPUT
100/ 100/
200VAC 200VAC
5
Redundant power extension base unit
6
(Q68RB)
Q64RP Q64RP I/O module
Extension cable
ERR
2, 3
ERR
2, 3 7
FG FG
LG LG
INPUT INPUT
Ground wire
100/
200VAC
100/
200VAC 8
Grounding
100V/200VAC
100V/200VAC
AC
10 - 45
● Use the thickest possible (max. 2 mm2 (14 AWG)) wires for the 100/200VAC and 24VDC power cables. Twist these
wires starting at the connection terminals. Use a solderless terminal for wiring a terminal block. To prevent short-circuit
due to loosening screws, use the solderless terminals with insulation sleeves of 0.8 mm (0.03 inches) or less.
Note that up to two solderless terminals can be connected per terminal block.
Solderless terminals Terminal block
with insulation sleeves
● Supply power to two redundant power supply modules individually (redundant power supply system).
● When two redundant power supply modules (Q64RP) are placed together and operated as a redundant power supply
system, it is recommended to use one of them as an AC power input and connect the other to an uninterruptible power
supply to the other.
● When the LG and FG terminals are connected, ground the wires.
If not, the programmable controller may become susceptible to noise.
Since the LG terminal has a half of the input voltage, touching this termial may result in electric shock.
10 - 46
CHAPTER11 MAINTENANCE AND INSPECTION
2
Do not touch the terminals while power is on.
Doing so will cause electric shock.
DANGER
Correctly connect the battery connector. 11
Do not charge, disassemble, heat, short-circuit, solder, or throw
the battery into the fire.
Doing so will cause the battery to produce heat, explode, or ignite, 4
resulting in injury and fire.
Shut off the external power supply for the system in all phases
before cleaning the module or retightening the terminal screws or 5
module fixing screws.
Failure to do so may result in electric shock.
Undertightening the terminal screws can cause short circuit or 6
malfunction.
Overtightening can damage the screw and/or module, resulting in
drop, short circuit, or malfunction. 7
11 - 1
Before performing online operations (especially, program
modification, forced output, and operation status change) for the
CAUTION
running CPU module from the peripheral connected, read relevant
manuals carefully and ensure the safety.
Do not disassemble of modify the modules.
Doing so may cause failure, malfunction, injury or a fire.
Use any radio communication device such as a cellular phone or
PHS (Personal Handy-phone System) more than 25cm (9.85
inches) away in all directions from the programmable controller.
Failure to do so may cause malfunction.
Shut off the external power supply for the system in all phases
before mounting or removing the module. Failure to do so may
cause the module to fail or malfunction.
A module can be replaced online (while power is on) on any
MELSECNET/H remote I/O station or in the system where a CPU
module supporting the online module change function is used.
Note that there are restrictions on the modules that can be
replaced online, and each module has its predetermined
replacement procedure.
( Section 12.4.1).
After the first use of the product, do not mount/remove the module
to/from the base unit, and the terminal block to/from the module
more than 50 times (IEC 61131-2 compliant) respectively.
Exceeding the limit of 50 times may cause malfunction.
Do not drop or apply shock to the battery to be installed in the
module.
Doing so may damage the battery, causing the battery fluid to leak
inside the battery.
If the battery is dropped or any shock is applied to it, dispose of it
without using.
Before handling the module, touch a grounded metal object to
discharge the static electricity from the human body.
Failure to do so may cause the module to fail or malfunction.
In order to use the programmable controller in normal and optimal condition at all times, this section describes
items that must be maintained or inspected daily or at regular intervals.
11 - 2
CHAPTER11 MAINTENANCE AND INSPECTION
2
Table11.1 Daily inspection
*1: For the Q00JCPU and Q00UJCPU, check the POWER LED on the CPU module side.
*2: When the Life detection power supply module is used, check the LIFE LED.
*3: The Basic model QCPU does not have the MODE LED.
*4: The Basic model QCPU does not have the BAT. LED.
11 - 3
11.2 Periodic Inspection
The items that must be inspected one or two times every 6 months to 1 year are listed below.
When the equipment has been relocated or modified, or wiring layout has been changed, perform this inspection.
Periodic Inspection
Looseness, rattling
looseness and rattling. securely. supply module is loose, fix it
3
with screws.
Adhesion of dirt and Dirt and foreign matter must
Check visually. Remove and clean.
foreign matter not be present.
Looseness of terminal Try to further tighten screws
Screws must not be loose. Retighten the terminal screws.
screws with a screwdriver.
Connection
*1: When AnS/A Series module is included in the system, the judgement criteria will be from 10 to 90 % RH.
11 - 4
CHAPTER11 MAINTENANCE AND INSPECTION
11
SM51 turns on when the battery voltage drops below the specified value, and remains on even after the voltage is recovered
to the normal value.
SM52 turns on when the battery voltage drops below the specified value, and turns off when the voltage is recovered to the
4
normal value.
After SM51 and/or SM52 turns on, replace the battery quickly.
5
SM51 and SM52 turn on when the battery voltage of the CPU module or SRAM card is lowered.
To identify the specific battery of the memory of which voltage is lowered, check the contents of the special resisters
SD51 and SD52.
6
b15 to b4 b3 b2 b1 b0
SD51, SD52 Fixed at 0
Battery error for CPU module When the battery
Battery alarm for SRAM card voltage is low, the 7
Battery error for SRAM card value is "1."
The cases for memory retention by the CPU module battery and the SRAM card battery are described below.
● The SRAM card battery cannot retain the CPU module memory.
Table11.3 Cases for memory retention by the CPU module battery and the SRAM card battery.
Installed
Connected
Not installed
Off
Installed
Not connected
Not installed
11 - 5
11.3.1 Display of battery consumption and reduction measures of the
consumption
When the standard RAM is set as a storage location for module error log data, battery consumption will be as
shown in Table11.5.
Table11.5 Battery consumption when module error log data are stored to the standard RAM
Battery consumption
(c) Size of file
Q10UD(E)H/
register file in
Q00U/01U/02U/ Q13UD(E)H/
standard RAM
Q03UD(E)/ Q6UD(E)HCPU Q20UD(E)H/
(SR)
Q04UD(E)HCPU Q26UD(E)HC
<Unit: word>
PU
0K SR 128K 2 3 3
*1: Applicable to the Q02UCPU, Q03UDCPU, Q04UDHCPU, and Q06UDHCPU if the serial numbers (first five digits) are
"10012" or later.
The current consumption level can be checked by referring to SD118 where the battery consumption value is stored.
*2: For details of the battery life-prolonging function, refer to the following.
( QnUCPU User's Manual (Function Explanation, Program Fundamentals)
*3: For details of the module error log function, refer to the following.
( QnUCPU User’s Manual (Function Explanation, Program Fundamentals)
Note1
Basic High
Note11.1 Redundant performance Process
The battery consumption value is displayed only for the Universal model QCPU.
11 - 6
CHAPTER11 MAINTENANCE AND INSPECTION
11 - 7
11.3.2 Battery lives of CPU modules
Battery life
After SM52 turned
CPU module Power-on time Actual service
Guaranteed value on. (Backup power
model ratio*1 value (Reference
*2 time after an
value)*3
alarm*4)
26,000 hours 43,800 hours 710 hours
0%
2.96 years 5.00 years 30 days
37,142 hours 43,800 hours 710 hours
30%
4.23 years 5.00 years 30 days
43,800 hours 43,800 hours 710 hours
Q00JCPU 50%
5.00 years 5.00 years 30 days
43,800 hours 43,800 hours 710 hours
70%
5.00 years 5.00 years 30 days
43,800 hours 43,800 hours 710 hours
100%
5.00 years 5.00 years 30 days
26,000 hours 43,800 hours 710 hours
0%
2.96 years 5.00 years 30 days
37,142 hours 43,800 hours 710 hours
30%
4.23 years 5.00 years 30 days
43,800 hours 43,800 hours 710 hours
Q00CPU 50%
5.00 years 5.00 years 30 days
43,800 hours 43,800 hours 710 hours
70%
5.00 years 5.00 years 30 days
43,800 hours 43,800 hours 710 hours
100%
5.00 years 5.00 years 30 days
5,600 hours 25,175 hours 420 hours
0%
0.63 years 2.87 years 18 days
8,000 hours 35,964 hours 420 hours
30%
0.91 years 4.10 years 18 days
11,200 hours 43,800 hours 420 hours
Q01CPU 50%
1.27 years 5.00 years 18 days
18,666 hours 43,800 hours 420 hours
70%
2.13 years 5.00 years 18 days
43,800 hours 43,800 hours 420 hours
100%
5.00 years 5.00 years 18 days
*1: The power-on time ratio indicates the ratio of programmable controller power-on time to one day (24 hours).
(When the total power-on time is 12 hours and the total power-off time is 12 hours, the power-on time ratio is 50%.)
*2: The guaranteed value represents a battery life at 70 , which is calculated based on the characteristic values of
manufacturere-supplied memories (SRAM) and on the assumption of storage within the ambient temperature range of -25
to 75 (operating ambient temperature of 0 to 55 ).
*3: The actual service value (reference value) represents a battery life that is calculated based on the values measured at
storage ambient temperature of 40 . This value is intended for reference only, as it varies with characteristics of the
memory.
*4: In the following status, the backup time after power off is 3 minutes.
•The battery connector is disconnected.
•The lead wire of the battery is broken.
11 - 8
CHAPTER11 MAINTENANCE AND INSPECTION
1
● Do not use the battery exceeding the guaranteed value of the battery life.
● When the battery may be used exceeding the guaranteed value of the battery life, take the following measures.
• Perform ROM operation to protect a program even if the battery dies at the programmable controller power-off. 2
• Back up programs and data after SM52 turned on (within the backup power time after an alarm).
● When the battery (Q6BAT) is not connected to the CPU module, its service life is five years.
● When the battery-low special relay SM52 turns on, immediately change the battery. 11
Even if an alarm has not yet occurred, it is recommended to replace the battery periodically according to the operating
condition.
● The battery (Q7BAT and Q8BAT) is not available for the Basic model QCPU. 4
11 - 9
(2) Battery (Q6BAT, Q7BAT and Q8BAT) lives of High Performance model QCPU,
Process CPU, and Redundant CPU
Table11.7 Battery life
Battery life*5
Q6BAT Q7BAT
After SM52 After SM52
CPU module Power-on Actual Actual
turned on. turned on.
model time ratio*1 service service
Guaranteed (Backup Guaranteed (Backup
value value
value*2 power time value*2 power time
(Reference (Reference
after an after an
value)*3 value)*3
alarm*4) alarm*4)
30,000 hours 43,800 hours 120 hours 43,800 hours 43,800 hours 240 hours
0%
3.42 years 5.00 years 5 days 5.00 years 5.00 years 10 days
42,857 hours 43,800hours 120 hours 43,800 hours 43,800 hours 240 hours
30%
4.89 years 5.00 years 5 days 5.00 years 5.00 years 10 days
43,800 hours 43,800 hours 120 hours 43,800 hours 43,800hours 240 hours
Q02CPU 50%
5.00 years 5.00 years 5 days 5.00 years 5.00 years 10 days
43,800 hours 43,800 hours 120 hours 43,800 hours 43,800 hours 240 hours
70%
5.00 years 5.00 years 5 days 5.00 years 5.00 years 10 days
43,800 hours 43,800 hours 120 hours 43,800 hours 43,800 hours 240 hours
100%
5.00 years 5.00 years 5 days 5.00 years 5.00 years 10 days
2,341 hours 18,364 hours 120 hours 5,000 hours 43,800 hours 240 hours
0%
0.26 years 2.09 years 5 days 0.57 years 5.00 years 10 days
3,344 hours 26,234 hours 120 hours 7,142 hours 43,800 hours 240 hours
30%
0.38 years 2.99 years 5 days 0.81 years 5.00 years 10 days
Q02HCPU 4,682 hours 36,728 hours 120 hours 10,000 hours 43,800 hours 240 hours
50%
Q06HCPU 0.53 years 4.19 years 5 days 1.14 years 5.00 years 10 days
7,803 hours 43,800 hours 120 hours 16,666 hours 43,800 hours 240 hours
70%
0.89 years 5.00 years 5 days 1.90 years 5.00 years 10 days
43,800 hours 43,800 hours 120 hours 43,800 hours 43,800 hours 240 hours
100%
5.00 years 5.00 years 5 days 5.00 years 5.00 years 10 days
1,897 hours 14,229 hours 96hours 4,051 hours 38,727 hours 192 hours
0%
0.21 years 1.62 years 4 days 0.46 years 4.42 years 8 days
2,710 hours 20,327 hours 96hours 5,787 hours 43,800 hours 192 hours
30%
0.30 years 2.32 years 4 days 0.66 years 5.00 years 8 days
Q02PHCPU 3,794 hours 28,458 hours 96 hours 8,102 hours 43,800 hours 192 hours
50%
Q06PHCPU 0.43 years 3.25 years 4 days 0.92 years 5.00 years 8 days
6,323 hours 43,800 hours 96 hours 13,503 hours 43,800 hours 192 hours
70%
0.72 years 5.00 years 4 days 1.54 years 5.00 years 8 days
43,800 hours 43,800 hours 9 hours 43,800 hours 43,800 hours 192 hours
100%
5.00 years 5.00 years 4 days 5.00 years 5.00 years 8 days
1,260 hours 7,755 hours 48 hours 2,900 hours 21,107 hours 96 hours
0%
0.14 years 0.88 years 2 days 0.33 years 2.40 years 4 days
Q12HCPU 1,800 hours 11,079 hours 48 hours 4,142 hours 30,153 hours 96 hours
30%
Q25HCPU 0.20 years 1.26 years 2 days 0.47 years 3.44 years 4 days
Q12PHCPU 2,520 hours 15,510 hours 48 hours 5,800 hours 42,214 hours 96 hours
50%
Q25PHCPU 0.28 years 1.77 years 2 days 0.66 years 4.81 years 4 days
Q12PRHCPU 4,200 hours 25,850 hours 48 hours 9,666 hours 43,800 hours 96 hours
Q25PRHCPU 70%
0.47 years 2.95 years 2 days 1.10 years 5.00 years 4 days
43,800 hours 43,800 hours 48 hours 43,800 hours 43,800 hours 96 hours
100%
5.00 years 5.00 years 2 days 5.00 years 5.00 years 4 days
11 - 10
CHAPTER11 MAINTENANCE AND INSPECTION
Battery life*5
1
Q8BAT
CPU module *1
model
Power-on time ratio
Actual service value
After SM52 turned on. 2
Guaranteed value *2 (Backup power time
(Reference value)*3
after an alarm*4)
0%
43,800 hours 43,800 hours 240 hours 11
5.00 years 5.00 years 10 days
43,800 hours 43,800 hours 240 hours
30%
5.00 years
43,800 hours
5.00 years
43,800 hours
10 days
240 hours
4
Q02CPU 50%
5.00 years 5.00 years 10 days
43,800 hours 43,800 hours 240 hours
70%
5.00 years 5.00 years 10 days 5
43,800 hours 43,800 hours 240 hours
100%
5.00 years 5.00 years 10 days
0%
20,498 hours 43,800 hours 240 hours 6
2.34 years 5.00 years 10 days
29,959 hours 43,800 hours 240 hours
30%
3.42 years 5.00 years 10 days 7
Q02HCPU 41,785 hours 43,800 hours 240 hours
50%
Q06HCPU 4.77 years 5.00 years 10 days
70%
43,800 hours 43,800 hours 240 hours 8
5.00 years 5.00 years 10 days
43,800 hours 43,800 hours 240 hours
100%
5.00 years 5.00 years 10 days
16,609 hours 43,800 hours 192 hours
11 - 11
*1: The power-on time ratio indicates the ratio of programmable controller power-on time to one day (24 hours).
(When the total power-on time is 12 hours and the total power-off time is 12 hours, the power-on time ratio is 50%.)
*2: The guaranteed value represents a battery life at 70 , which is calculated based on the characteristic values of manufacturer-supplied
memories (SRAM) and on the assumption of storage ambient temperature range of -25 to 75 (operating ambient temperature of 0 to
55 ).
*3: The actual service value (reference value) represents a battery life that is calculated based on the values measured at storage ambient
temperature of 40 . This value is intended for reference only, as it varies with characteristics of the memory.
*4: In the following status, the backup time after power off is 3 minutes.
• The battery connector is disconnected.
• The lead wire of the battery is broken.
*5: For the High Performance model QCPU, these values are applicable when the serial number (first five digits) of the CPU module is
"05011" or later.
For the battery life of the CPU module with a serial number (first five digits) is "05010" or earlier, refer to Appendix 2.3.
● Do not use the battery exceeding the guaranteed value of the battery life.
● When the battery may be used exceeding the guaranteed value of the battery life, take the following measures.
• Perform ROM operation to protect a program even if the battery dies at the programmable controller power-off.
• Back up programs and data after SM52 turned on (within the backup power time after an alarm).
● When the battery (Q6BAT, Q7BAT and Q8BAT) is not connected to the CPU module, its service life is five years.
● When the battery-low special relay SM52 turns on, immediately change the battery.
Even if an alarm has not yet occurred, it is recommended to replace the battery periodically according to the operating
condition.
11 - 12
CHAPTER11 MAINTENANCE AND INSPECTION
(3) Battery (Q6BAT, Q7BAT and Q8BAT) lives of the Universal model QCPU 1
Table11.8 Battery life
Battery life 2
Q6BAT
CPU module Battery Power-on After SM52 turned
model consumption*1 time ratio*2 Actual service value on. 11
Guaranteed value*3 (Backup power time
(Reference Value)*4
after an alarm*5)
0%
30,100 hours 43,800 hours 600 hours 4
3.44 years 5.00 years 25 days
43,000 hours 43,800 hours 600 hours
30%
4.91 years 5.00 years 25 days
5
43,800 hours 43,800 hours 600 hours
1 50%
5.00 years 5.00 years 25 days
70%
43,800 hours
5.00 years
43,800 hours
5.00 years
600 hours
25 days
6
Q00U(J)CPU 43,800 hours 43,800 hours 600 hours
100%
Q01UCPU 5.00 years 5.00 years 25 days
Q02UCPU 25,300 hours 43,800 hours 600 hours
7
0%
Q03UD(E)CPU 2.89 years 5.00 years 25 days
36,100 hours 43,800 hours 600 hours
30%
4.12 years 5.00 years 25 days 8
43,800 hours 43,800 hours 600 hours
2 50%
5.00 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
70%
11 - 13
Table11.8 Battery life
Battery life
Q6BAT
CPU module Battery Power-on After SM52 turned
model consumption*1 time ratio*2 Actual service value on.
Guaranteed value*3 (Backup power time
(Reference Value)*4
after an alarm*5)
25,300 hours 43,800 hours 600 hours
0%
2.89 years 5.00 years 25 days
36,100 hours 43,800 hours 600 hours
30%
4.12 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
1 50%
5.00 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
70%
5.00 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
100%
5.00 years 5.00 years 25 days
4,200 hours 32,100 hours 384 hours
0%
0.48 years 3.66 years 16 days
6,000 hours 43,800 hours 384 hours
30%
0.68 years 5.00 years 16 days
8,400 hours 43,800 hours 384 hours
Q06UD(E)HCPU 2 50%
0.96 years 5.00 years 16 days
14,000 hours 43,800 hours 384 hours
70%
1.60 years 5.00 years 16 days
43,800 hours 43,800 hours 384 hours
100%
5.00 years 5.00 years 16 days
2,300 hours 19,200 hours 192 hours
0%
0.26 years 2.19 years 8 days
3,200 hours 27,400 hours 192 hours
30%
0.37 years 3.13 years 8 days
4,600 hours 38,400 hours 192 hours
3 50%
0.53 years 4.38 years 8 days
7,600 hours 43,800 hours 192 hours
70%
0.87years 5.00 years 8 days
43,800 hours 43,800 hours 192 hours
100%
5.00 years 5.00 years 8 days
11 - 14
CHAPTER11 MAINTENANCE AND INSPECTION
1
Table11.8 Battery life
Battery life
Q6BAT 2
CPU module Battery Power-on After SM52 turned
model consumption*1 time ratio*2 Actual service value on.
Guaranteed value*3
(Reference Value)*4 (Backup power time
11
after an alarm*5)
22,600 hours 43,800 hours 600 hours
0%
2.58 years
32,200 hours
5.00 years
43,800 hours
25 days
600 hours
4
30%
3.68 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
1 50%
5.00 years 5.00 years 25 days 5
43,800 hours 43,800 hours 600 hours
70%
5.00 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours 6
100%
5.00 years 5.00 years 25 days
4,100 hours 26,200 hours 384 hours
0%
0.47 years 2.99 years 16 days 7
5,800 hours 37,400 hours 384 hours
30%
0.66 years 4.27 years 16 days
2 50%
8,200 hours 43,800 hours 384 hours 8
0.94 years 5.00 years 16 days
13,600 hours 43,800 hours 384 hours
70%
1.55 years 5.00 years 16 days
Q10UD(E)HCPU 43,800 hours 43,800 hours 384 hours
11 - 15
Table11.8 Battery life
Battery life
Q7BAT
CPU module Battery Power-on After SM52 turned
model consumption*1 time ratio*2 Actual service value on.
Guaranteed value*3 (Backup power time
(Reference Value)*4
after an alarm*5)
43,800 hours 43,800 hours 600 hours
0%
5.00 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
30%
5.00 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
1 50%
5.00 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
70%
5.00 years 5.00 years 25 days
Q00U(J)CPU 43,800 hours 43,800 hours 600 hours
100%
Q01UCPU 5.00 years 5.00 years 25 days
Q02UCPU 43,800 hours 43,800 hours 600 hours
0%
Q03UD(E)CPU 5.00 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
30%
5.00 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
2 50%
5.00 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
70%
5.00 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
100%
5.00 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
0%
5.00 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
30%
5.00 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
1 50%
5.00 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
70%
5.00 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
100%
5.00 years 5.00 years 25 days
Q04UD(E)HCPU
11,700 hours 43,800 hours 600 hours
0%
1.34 years 5.00 years 25 days
16,700 hours 43,800 hours 600 hours
30%
1.91 years 5.00 years 25 days
23,400 hours 43,800 hours 600 hours
2 50%
2.67 years 5.00 years 25 days
39,000 hours 43,800 hours 600 hours
70%
4.45 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
100%
5.00 years 5.00 years 25 days
11 - 16
CHAPTER11 MAINTENANCE AND INSPECTION
1
Table11.8 Battery life
Battery life
Q7BAT 2
CPU module Battery Power-on After SM52 turned
model consumption*1 time ratio*2 Actual service value on.
Guaranteed value*3
(Reference Value)*4 (Backup power time
11
after an alarm*5)
43,800 hours 43,800 hours 600 hours
0%
5.00 years
43,800 hours
5.00 years
43,800 hours
25 days
600 hours
4
30%
5.00 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
1 50%
5.00 years 5.00 years 25 days 5
43,800 hours 43,800 hours 600 hours
70%
5.00 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours 6
100%
5.00 years 5.00 years 25 days
11,400 hours 43,800 hours 600 hours
0%
1.30 years 5.00 years 25 days 7
16,200 hours 43,800 hours 600 hours
30%
1.85 years 5.00 years 25 days
Q06UD(E)HCPU 2 50%
22,800 hours 43,800 hours 600 hours 8
2.60 years 5.00 years 25 days
38,000 hours 43,800 hours 600 hours
70%
4.34 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
11 - 17
Table11.8 Battery life
Battery life
Q7BAT
CPU module Battery Power-on After SM52 turned
model consumption*1 time ratio*2 Actual service value on.
Guaranteed value*3 (Backup power time
(Reference Value)*4
after an alarm*5)
43,800 hours 43,800 hours 600 hours
0%
5.00 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
30%
5.00 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
1 50%
5.00 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
70%
5.00 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
100%
5.00 years 5.00 years 25 days
11,100 hours 43,800 hours 600 hours
0%
1.27 years 5.00 years 25 days
15,800 hours 43,800 hours 600 hours
30%
1.80 years 5.00 years 25 days
22,200 hours 43,800 hours 600 hours
2 50%
2.53 years 5.00 years 25 days
37,000 hours 43,800 hours 600 hours
70%
4.22 years 5.00 years 25 days
Q10UD(E)HCPU 43,800 hours 43,800 hours 600 hours
100%
Q13UD(E)HCPU 5.00 years 5.00 years 25 days
Q20UD(E)HCPU 5,000 hours 43,800 hours 600 hours
0%
Q26UD(E)HCPU 0.57 years 5.00 years 25 days
7,100 hours 43,800 hours 600 hours
30%
0.81 years 5.00 years 25 days
10,000 hours 43,800 hours 600 hours
3 50%
1.14 years 5.00 years 25 days
16,600 hours 43,800 hours 600 hours
70%
1.89 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
100%
5.00 years 5.00 years 25 days
3,700 hours 36,100 hours 432 hours
0%
0.42 years 4.12 years 18 days
5,200 hours 43,800 hours 432 hours
30%
0.59 years 5.00 years 18 days
7,400 hours 43,800 hours 432 hours
4 50%
0.84 years 5.00 years 18 days
12,300 hours 43,800 hours 432 hours
70%
1.40 years 5.00 years 18 days
43,800 hours 43,800 hours 432 hours
100%
5.00 years 5.00 years 18 days
11 - 18
CHAPTER11 MAINTENANCE AND INSPECTION
1
Table11.8 Battery life
Battery life
Q8BAT 2
CPU module Battery Power-on After SM52 turned
model consumption*1 time ratio*2 Actual service value on.
Guaranteed value*3
(Reference Value)*4 (Backup power time
11
after an alarm*5)
43,800 hours 43,800 hours 600 hours
0%
5.00 years
43,800 hours
5.00 years
43,800 hours
25 days
600 hours
4
30%
5.00 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
1 50%
5.00 years 5.00 years 25 days 5
43,800 hours 43,800 hours 600 hours
70%
5.00 years 5.00 years 25 days
Q00U(J)CPU 43,800 hours 43,800 hours 600 hours 6
100%
Q01UCPU 5.00 years 5.00 years 25 days
Q02UCPU 43,800 hours 43,800 hours 600 hours
0%
Q03UD(E)CPU 5.00 years 5.00 years 25 days 7
43,800 hours 43,800 hours 600 hours
30%
5.00 years 5.00 years 25 days
2 50%
43,800 hours 43,800 hours 600 hours 8
5.00 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
70%
5.00 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
11 - 19
Table11.8 Battery life
Battery life
Q8BAT
CPU module Battery Power-on After SM52 turned
model consumption*1 time ratio*2 Actual service value on.
Guaranteed value*3 (Backup power time
(Reference Value)*4
after an alarm*5)
43,800 hours 43,800 hours 600 hours
0%
5.00 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
30%
5.00 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
1 50%
5.00 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
70%
5.00 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
100%
5.00 years 5.00 years 25 days
37,900 hours 43,800 hours 600 hours
0%
4.33 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
30%
5.00 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
Q06UD(E)HCPU 2 50%
5.00 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
70%
5.00 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
100%
5.00 years 5.00 years 25 days
20,500 hours 43,800 hours 600 hours
0%
2.34 years 5.00 years 25 days
29,200 hours 43,800 hours 600 hours
30%
3.33 years 5.00 years 25 days
41,000 hours 43,800 hours 600 hours
3 50%
4.68 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
70%
5.00 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
100%
5.00 years 5.00 years 25 days
11 - 20
CHAPTER11 MAINTENANCE AND INSPECTION
1
Table11.8 Battery life
Battery life
Q8BAT 2
CPU module Battery Power-on After SM52 turned
model consumption*1 time ratio*2 Actual service value on.
Guaranteed value*3
(Reference Value)*4 (Backup power time
11
after an alarm*5)
43,800 hours 43,800 hours 600 hours
0%
5.00 years
43,800 hours
5.00 years
43,800 hours
25 days
600 hours
4
30%
5.00 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
1 50%
5.00 years 5.00 years 25 days 5
43,800 hours 43,800 hours 600 hours
70%
5.00 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours 6
100%
5.00 years 5.00 years 25days
37,000 hours 43,800 hours 600 hours
0%
4.22 years 5.00 years 25 days 7
43,800 hours 43,800 hours 600 hours
30%
5.00 years 5.00 years 25 days
2 50%
43,800 hours 43,800 hours 600 hours 8
5.00 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
70%
5.00 years 5.00 years 25 days
Q10UD(E)HCPU 43,800 hours 43,800 hours 600 hours
11 - 21
*1: For the battery consumption Section 11.3.1.
*2: The power-on time ratio indicates the ratio of programmable controller power-on time to one day (24 hours).
(When the total power-on time is 12 hours and the total power-off time is 12 hours, the power-on time ratio is 50%.)
*3: The guaranteed value represents a battery life at 70 , which is calculated based on the characteristic values of manufacturer-supplied
memories (SRAM) and on the assumption of storage ambient temperature range of -25 to 75 (operating ambient temperature of 0 to
55 ).
*4: The actual service value (reference value) represents a battery life that is calculated based on the values measured at storage ambient
temperature of 40 . This value is intended for reference only, as it varies with characteristics of the memory.
*5: In the following status, the backup time after power off is 3 minutes.
• The battery connector is disconnected.
• The lead wire of the battery is broken.
● Do not use the battery exceeding the guaranteed value of the battery life.
● When the battery may be used exceeding the guaranteed value of the battery life, take the following measures.
• Perform ROM operation to protect a program even if the battery dies at the programmable controller power-off.
• Back up programs and data After SM52 turned on (within the backup power time after an alarm).
● When the battery (Q6BAT, Q7BAT and Q8BAT) is not connected to the CPU module, its service life is five years.
● When the battery-low special relay SM52 turned on, immediately change the battery.
Even if an alarm has not yet occurred, it is recommended to replace the battery periodically according to the operating
condition.
11 - 22
CHAPTER11 MAINTENANCE AND INSPECTION
Backup time
3 minutes 5
Replacing battery
6
CPU module
Backup the program and the
data.
Connector
Close the CPU module front cover. battery side
Monitor
OFF
SM51 to check
ON/OFF.
ON
Monitor
Bit 0 is OFF.
SD52 to check if bit 0 is
ON.
Bit 0 is ON.
11 - 23
(2) Replacement procedure of the Q6BAT battery for the High Performance model
QCPU, Process CPU, Redundant CPU and Universal model QCPU
Backup time
3 minutes
Replacing battery
Connector
Remove the old battery from its battery side
holder. Battery Q6BAT
Monitor
OFF
SM51 to verify
on/off.
ON
Bit 0 is on.
11 - 24
CHAPTER11 MAINTENANCE AND INSPECTION
Backup time 2
3 minutes
Replacing battery
11
Backup the program and the data.
Q7BAT to be
replaced by Disengage the catch on one side of
Confirm
the type of the old
Q7BAT. the battery holder to disassemble the
holder into two, and remove the
Latch
8
battery. Q7BAT.
Battery holder
Q6BAT to be
replaced by Q7BAT. Insert the new Q7BAT into the holder
in the correct direction, and
Connector
Set the battery holder to the
CPU module.
Connector
stopper
Install the CPU module into the
base unit.
Battery holder
Monitor
OFF
SM51 to verify
on/off.
ON
Bit 0 is on.
11 - 25
(4) Replacement procedure of the Q8BAT battery
Table11.12 Backup time
Backup time
3 minutes
Replacing battery
2)
Q6BAT/Q7BAT to
be replaced by Remove the Q8BAT connection
Q8BAT. cable from the Q8BAT.
Remove the cover/battery holder at Connector Install the new Q8BAT to the control
the bottom of the CPU module. of CPU module
panel.*2 (Fixing with a mounting
Connector screw or fixing with the DIN rail is
of battery
Disconnect the battery connector, and Q6BAT
pull out the Q6BAT/Q7BAT. *1
1)
Connect the Q8BAT connection cable
to the connector of the CPU module.
CPU module
Connector
of cable
Q8BAT
connection
(To next page) cable
Connector
of CPU module
CPU module
Q8BAT
connection
cover
*1: Remove the battery connector with holding the connector part so that the battery cable may not be damaged.
11 - 26
CHAPTER11 MAINTENANCE AND INSPECTION
1)
Monitor OFF
SM51 to verify
on/off.
8
Q8BAT Q8BAT
connection cable
ON
Monitor
Bit 0 is OFF.
Bit 0 is on.
2)
*2: For the module mounting position, refer to the following .
Section 10.3.2
*3: Clamp the Q8BAT connection cable. If not being clamped, the Q8BAT connection cover, connector, and cable, may be
damaged by a loose cable connection, shifting, or pulling due to carelessness, etc.
*4: Secure 10mm or more as the minimum cable bend radius.
If it is less than 10mm, malfunction may occur due to characteristic deterioration, open cable or the like.
11 - 27
● After replacing a battery, write the date for next battery replacement on the sticker on the back side of the front cover.
Write the proper date by checking the battery life. ( Section 11.3.2)
11 - 28
CHAPTER11 MAINTENANCE AND INSPECTION
11 - 29
Battery life *3
*1: The power-on time ratio indicates the ratio of programmable controller power-on time to one day (24 hours).
(When the total power-on and power-off times are 12 hours for each, the power-on time ratio is 50%).
*2: The manufacturing control number (the third digit from the leftmost) is written on the label on the back of the SRAM card
(as shown in Figure 11.7).
Manufacturer
control number
● Do not use the battery exceeding the guaranteed value of the battery life.
● When the battery may be used exceeding the guaranteed value of the battery life, take the following measures.
• Perform ROM operation to protect a program even if the battery dies at the programmable controller power-off.
• Back up programs and data after SM52 turned on (within the backup time after an alarm).
● Note that the SRAM card battery is consumed even while the programmable controller is powered ON with the CPU
module battery connected.
● When the special relay showing battery low, SM52 turned on, immediately change the battery.
Even if an alarm has not yet occurred, it is recommended to replace the battery periodically according to the conditions
of use.
● The SRAM card is not available for the Basic model QCPU.
11 - 30
CHAPTER11 MAINTENANCE AND INSPECTION
11
Backup the program and the
data.
5
Release main unit
direction
With a flat-blade screwdriver, etc.,
remove the battery holder locking Battery holder
fixing switch
switch from the LOCK position.
Battery holder CPU module
6
main unit
7
Used battery
CPU module
main unit
Deeply insert the SRAM card
into the battery holder.
ON
Monitor
Bit 1 and bit 2 are OFF.
SD52 to check if bit 1 and bit
2 are ON.
11 - 31
(2) Replacing Q3MEM-4MBS and Q3MEM-8MBS
Release
direction
Battery holder
fixing switch
Remove the old battery from its
holder.
CPU module
main unit Facing "+ (positive)"
Insert a new battery into the up, install the battery
holder in the correct direction.
Battery holder
fixing switch
Set a battery holder fixing switch
to the LOCK position
Monitor OFF
SM52 to verify on/off.
ON
Monitor Bit 1 and bit 2 are OFF.
SD52 to check if bit 1 and bit
2 are ON.
11 - 32
CHAPTER11 MAINTENANCE AND INSPECTION
1
Be careful about the following to replace the SRAM card battery.
● To back up the data, replace the SRAM card battery with the programmable controller power supply on and the SRAM
card installed. 2
● Start replacement after backing up the CPU module data using GX Developer.
● Since replacement is made with the programmable controller power supply ON, take extreme care not to get an electric
shock. 11
● When dismounting or mounting the battery holder on the SRAM card, take care so that the battery does not come out
of the battery holder.
● When replacing the battery with the programmable controller power supply off, always back up the data before starting 4
replacement.
[Battery replacement procedure]
1) Back up the SRAM card data using GX Developer.
2) Replace the battery. 5
3) Write the backed up data from GX Developer to the memory card.
Insert or remove the battery in the horizontal direction along the battery holder fixing guide.
Failure to do so may damage the latches of the battery holder. 6
Battery holder latches
Battery holder
Figure 11.10 Battery setting direction
11 - 33
11.4 When Programmable Controller Has Been Stored Without Bat-
tery
When resuming operation of the programmable controller after having been stored without battery installed, the data in
the CPU module and the memory card may be corrupted.
Before restarting operation, format the CPU module memory and SRAM card using GX Developer.
After formatting the memories, write backed up data to each memory.
To format a program memory during boot operation, select the "Clear program memory" checkbox in the Boot file tab
of the PLC parameter dialog box.
Remark
For the Universal model QCPU, when the latch data backup function (to standard ROM) is used, data will not be disap-
peared even if storing data without a battery, since latch data such as device data of the CPU module or error history can
be backed up without using a battery.
The relationships between battery and battery-backed memorie are shown in Table11.15.
Battery
Memory Battery Built in Memory
Battery of QCPU Module*1
Card
Program memory *2
SRAM card
*3
Memory card Flash card ---- (Battery backup not needed)
ATA card ---- (Battery backup not needed)
Before restarting the operation, format the battery-backed memories shown in Table11.15 using GX Developer.
● Before storing the programmable controller, back up all the data stored in the memories.
● When the programmable controller is powered on or the CPU module is reset, the CPU module initializes all of the fol-
lowing data if an error is detected.
• Program memory data
• Standard RAM data
• Error history
• Latch data (latch relay (L), devices in latch setting range set in the parameter, special relay SM900 to SM999, spe-
cial register SD900 to SD900)
• Sampling trace data
11 - 34
CHAPTER11 MAINTENANCE AND INSPECTION
When using the programmable controller after the guaranteed battery life had expired during storing, the data in the 2
CPU module and the memory card may had been corrupted.
Before restarting operation, format the CPU module memory and SRAM card using GX Developer.
After formatting the memories, write backed up data to each memory. 11
To format a program memory during boot operation, select the "Clear program memory" checkbox in the Boot file tab
of the PLC parameter dialog box.
4
Remark
For the Universal model QCPU, when the latch data backup function (to standard ROM) is used, data will not be disap-
peared even if a battery life ends, since latch data such as device data of the CPU module or error history can be backed 5
up without using a battery.
6
The relationships between battery and battery-backed memorie are shown in Table11.16.
Battery
7
Memory Battery Built in Memory
Battery of QCPU Module*1
Card
*2
8
Program memory
11.5 When Battery Has Gone Flat During Storage of Programmable Controller
SRAM card
*3
Memory card Flash card ---- (Battery backup not needed)
ATA card ---- (Battery backup not needed)
Before restarting the operation, format the battery-backed up memories shown in Table11.16 using GX Developer.
● Before storing the programmable controller, back up all the data stored in the memories.
● When the programmable controller is powered on or the CPU module is reset, the CPU module initializes all of the fol-
lowing data if an error is detected.
• Program memory data
• Standard RAM data
• Error history
• Latch data (latch relay (L), devices in latch setting range set in the parameter, special relay SM900 to SM999, spe-
cial register SD900 to SD900)
• Sampling trace data
11 - 35
CHAPTER12 TROUBLESHOOTING
This chapter describes errors that may occur during system operation, how to locate the errors, and measures against
the errors.
For a redundant system (when the Redundant CPU is used), refer to the following. QnPRHCPU User's Manual
(Redundant System)
In order to increase the reliability of the system, resuming the system operation promptly after correcting a problem is
one of the important factors as well as using reliable device.
To promptly start up the system, the trouble cause must be located and eliminated correctly.
The basic three points to be followed in the troubleshooting are as follows.
After checking 1) through 7), connect GX Developer and monitor the operating status and programs of the
programmable controller.
2) Reset the trouble with the RESET/L.CLR switch. Note12.1 ( CHAPTER 4)*1
Note1
For the Basic model QCPU or Universal model QCPU use the "RUN/STOP/RESET switch" for the operation.
12 - 1
CHAPTER12 TROUBLESHOOTING
12
12 - 2
12.2 Troubleshooting
This section describes how to identify errors, details of errors, and measures to eliminate the errors.
Error description
LIFE OUT terminal of the Life detection power Section 12.2.3 When the LIFE OUT terminal (negative logic) has
supply module has turned off. turned off
MODE LED does not turn on. Note12.2 Section 12.2.4 When the MODE LED does not turn on
MODE LED is flickering. Section 12.2.5 When the MODE LED is flickering
POWER LED has turned off. Section 12.2.6 When the POWER LED has turned off
POWER LED of the Life detection power Section 12.2.7 When the POWER LED is flickering in orange
supply module is flickering in orange.
POWER LED of the redundant power supply Section 12.2.8 When the POWER LED has turned on in red
module has turned on in red.
LIFE LED of the Life detection power supply Section 12.2.9 When the LIFE LED has turned off
module has turned off.
LIFE LED of the Life detection power supply Section 12.2.10 When the LIFE LED has turned on in red
module has turned on in red.
LIFE LED of the Life detection power supply Section 12.2.11 When the LIFE LED is flickering in red
module is flickering in red.
RUN LED has turned off. Section 12.2.12 When the RUN LED has turned off
RUN LED is flickering. Section 12.2.13 When the RUN LED is flickering
ERR. LED has turned on or is flickering. Section 12.2.14 When the ERR. LED has turned on or is flickering
USER LED has turned on. Note12.2 Section 12.2.15 When the USER LED has turned on
BOOT LED is flickering. Note12.2 Section 12.2.17 When the BOOT LED is flickering
LEDs of the output module do not turn on. Section 12.2.18 When the LEDs of the output module do not turn on
I/O modules do not operate normally. Section 12.2.19 When output load of the output module does not
turn on
Note1
Note12.2 Basic
The Basic model QCPU does not have the following LEDs.
MODE LED
USER LED
BAT. LED
BOOT LED
12 - 3
CHAPTER12 TROUBLESHOOTING
CONTROL BUS ERR. has occurred. Section 12.2.25 When "CONTROL BUS ERR." has occurred
3
CPU module does not start. Section 12.2.26 When the CPU module does not start
12
OPERATION ERROR has occurred at When "OPERATION ERROR" has occurred at
execution of the S(P).SFCSCOMR and Section 12.2.27 execution of the S(P).SFCSCOMR and
S(P).SFCTCOMR instructions. S(P).SFCTCOMR instructions
Comments cannot be read at the execution of When comments cannot be read at execution of
the S(P).SFCSCOMR and S(P).SFCTCOMR
instructions.
Section 12.2.28 the S(P).SFCSCOMR and S(P).SFCTCOMR
instructions 5
PARAMETER ERROR has occurred at power Section 12.2.29 When "PARAMETER ERROR" has occurred at
on or reset. power on or reset
6
CPU module cannot communicate with Section 12.2.30
When the CPU module cannot communicate with
GX Developer. GX Developer
Ethernet communication with a CPU module is Section 12.2.34 When Ethernet communication with a CPU module
Error has occurred during MC protocol Section 12.2.35 When an error has occurred during MC protocol
communication. communication
Clock data cannot be set by SNTP. Section 12.2.36 When clock data cannot be set by SNTP
Note1
Note12.3 Basic
The Basic model QCPU cannot use the memory card.
12 - 4
12.2.2 When the ERR. terminal (negative logic) has turned off (opened)
Refer to the following flowchart when the ERR. terminal has turned off (opened) at power-on or during operation of the
programmable controller.Note1
Flickering (CPU
module is in stop
How is the "ERR." error) Check error details and take action
LED of the CPU according to the details.
module?
Not flickering
Is power supplied? NO
Is the power supply Supply power of proper voltage.
voltage proper?
YES
Off
Remove the corresponding power
supply module, and mount it to the
normal base unit.
(Do not mount any modules other
than the power supply module.)
How is the "POWER" LED On (red) The corresponding power supply module is
of the power supply faulty
module? (Replace it with a normal power supply
module).
Turned on green ( Section 12.4.2
12.4.2)
Mount the corresponding power
supply module to the original system
again, and remove all modules other
than the power supply module from
the base unit.
Note1
Note12.4 Basic
The Basic model QCPU does not have the "MODE" LED. In the flowchart, proceed to "Off".
12 - 5
CHAPTER12 TROUBLESHOOTING
On (green) 3
Check the sum of internal current
consumptions of the modules that
comprise the system.
12
Does the total
current exceed the rated Reexamine the system configuration to make the
5
Yes
current consumption of one power total current less than the rated current consumption
supply module? of one power supply module.
Hardware fault
No
6
Execute operation checks in due order,
starting with the minimum system.
For the module that does not operate,
please contact your local nearest
Mitsubishi or representative, explaining
7
a detailed description of the problem.
If a CPU module stop error occurs during use of two redundant power supply modules, the error is output from the ERR.
12.2.2 When the ERR. terminal (negative logic) has turned off (opened)
12.2 Troubleshooting
terminals of the two redundant power supply modules.
Refer to the following for details of the ERR. terminal.
Section 5.2.1 Power supply module specification list
Section 10.6.2 Wring of power supply module
12 - 6
Errors that can be detected by the ERR. terminal
The following shows the errors that can be detected by the ERR. terminal of the power supply module in a
singular power supply system/redundant power supply system.
<Singular power supply system> .....................................................One Q series power supply module is used.
Table12.1 Errors that can be detected by the ERR. terminal of a power supply module
CPU module
Basic model QCPU*,
Base unit
High Performance model QCPU, Process CPU, Redundant CPU
Universal model QCPU
Main base unit (Q3 B)
AC power not input, power supply module fuse blown and CPU module stop error (including reset)
Multiple CPU high speed main base
can be detected.
unit (Q3 DB)
Extension base unit (Q6 B) Errors cannot be detected (always off). (Cannot be added)
<Singular power supply system> .....................................................One slim type power supply module is used.
Table12.2 Errors that can be detected by the ERR. terminal of a power supply module
CPU module
Basic model QCPU*,
Base unit Process CPU,
High Performance model QCPU,
Redundant CPU
Universal model QCPU
Slim type main base unit AC power not input, power supply module fuse blown and
(Cannot be combined)
(Q3 SB) CPU module stop error (including reset) can be detected.
<Redundant power supply system>...................................................... Two redundant power supply modules are
used.
Table12.3 Errors that can be detected by the ERR. terminal of a power supply module
CPU module
Basic model QCPU*,
Base unit
High Performance model QCPU, Process CPU, Redundant CPU
Universal model QCPU
Redundant power main base unit AC power not input, redundant power supply module fuse blown, CPU module stop error (including
(Q3 RB) reset), and redundant power supply module failure can be detected.
12 - 7
CHAPTER12 TROUBLESHOOTING
1
Remark
In the redundant power supply system, the failure of the redundant power supply module can also be detected by using 2
GX Developer (Version 8.18U or later). Note12.5, Note12.6
12.2.2 When the ERR. terminal (negative logic) has turned off (opened)
12.2 Troubleshooting
Note1
Note12.5 Basic
Failure of redundant power supply cannot be detected by the Basic model QCPU.
High
Note12.6 performance Process
When using the High Performance QCPU or the Process CPU, check the versions of CPU module and GX Developer.
( Appendix 2)
12 - 8
12.2.3 When the LIFE OUT terminal (negative logic) has turned off (opened)
Refer to the following flowchart when the LIFE OUT terminal of the Life detection power supply module has turned off
(opened) at power-on or during operation of the programmable controller.
YES
NO
Section 12.2.6 Section 12.2.7
Flowchart for when the POWER LED Flowchart for when the POWER LED is
turned off flickering in orange
YES
YES
Figure 12.3 When the LIFE OUT terminal has turned off
12 - 9
CHAPTER12 TROUBLESHOOTING
Is the extension
cable connected
properly? (Isn't IN connected to
NO
Connect the extension cable properly.
8
IN or OUT connected to
OUT?)
YES NO YES
Can "MODE" LED turn on?
YES
Can "MODE" LED turn on? Hardware fault of power supply module.
NO
A hardware fault may have occurred in
any of the following modules.
1) CPU module Completed
2) Main base unit, extension base unit
3) Extension cable
4) I/O Module (If one is installed)
5) Intelligent function module
(If one is installed)
6) Network module (If one is installed)
Perform operations in due order, starting
with the minimum system where the power
supply module and CPU module are
mounted on the main base unit.
If the module will not work, please consalt
your local nearest Mitsubishi or
representative, explaining a detailed
description of the problem.
12 - 10
12.2.5 When the MODE LED is flickering
Refer to the following flowchart when the MODE LED of the CPU module flickers at programmable controller power-
on, at operation start or during operation.
Have the
forced ON/OFF YES
Cancel forced ON/OFF.
settings made?
NO
NO Can "MODE" LED YES
turn on?
Neutral position
12 - 11
CHAPTER12 TROUBLESHOOTING
NO
To (A) on the next page
12
NO
Is the power being supplied? Supply power
5
YES Off On (green)
How is the POWER LED?
6
On (red)*
Section 12.2.8
Flowchart for when the POWER LED turns on (red)
7
Is the power voltage NO
Adjust the voltage within the specification
within the specification?
YES
8
Off On (green)
How is the POWER LED?
On (red)*
YES On (green)
Off
How is the POWER LED?
On (green)
12 - 12
From (A) on the previous page
YES
Is the POWER LED off? Replace the faulty module.
NO
YES
Is the POWER LED on in green? Completed
NO
YES
Hardware fault
Check the operation starting from the
smallest system.
For the inoperable module, please
consult your local Mitsubishi service
center or representative, explaining
a detailed description of the problem.
12 - 13
CHAPTER12 TROUBLESHOOTING
NO 5
NO
Is the POWER LED on
in green?
6
YES
7
NO
Is the POWER LED off?
YES
Section 12.2.6
The corresponding Life detection 8
power supply module is faulty.
Flowchart for when the POWER LED (Replace with a normal Life detection
Completed turned off power supply module.)
12 - 14
12.2.8 When the POWER LED has turned on in red
Refer to the following flowchart when the POWER LED of the redundant power supply module has turned on in red at
power-on or during operation of the programmable controller.
The "POWER" LED has
turned on (red).
On (green)
Return the corresponding
redundant power supply module to
the original system, and remove all
modules other than the redundant
power supply module from the
redundant base unit.
No
Hardware fault
check operations checks in the
order starting with the minimum
system.
If the module will not work, please
consalt your local nearest
Mitsubishi or representative,
explaining a detailed description of
the problem.
12 - 15
CHAPTER12 TROUBLESHOOTING
NO
5
The power supply module life expired.
Replace the power supply module.
Is the LIFE LED on
in green or orange or flickering
YES
6
in orange?
NO
7
Completed
YES
8
Is the LIFE LED on
in red or flickering in red?
NO
Turned on in red
Figure 12.9 When the LIFE LED of the Life detection module has turned off
12 - 16
12.2.10 When the LIFE LED has turned on in red
Refer to the following flowchart when the LIFE LED of the Life detection power supply module has turned on in red at
power-on or during operation of the programmable controller.
NO
Stop the operation of the module for
Adjust the operating ambient
heat dissipation.
temperature within the 0 to 55 .
YES
YES
12 - 17
CHAPTER12 TROUBLESHOOTING
(When off)
3
Off or Section 12.2.5
Section 12.2.6 "Flowchart for
How is the when the "POWER" LED has
On (red)
"POWER" LED of the power
12
turned off."
supply module? (When on (red))
Section 12.2.6
Section 12.2.8 Flowchart for
Turned on green when the "POWER" LED has
turned on (red)
NO
Can "RUN" LED turn on?
YES
Completed
Note1
Note12.7 Basic
For the Basic model QCPU, use the RUN/STOP/RESET switch for operation.
12 - 18
12.2.13 When the RUN LED is flickering
If the RUN LED flickering, follow the procedure below.
Note1
When the programs or parameters are written into the CPU module during the STOP status and then the RUN/STOP
switch Note12.8 is set from STOP to RUN, the RUN LED of the CPU module flickers.
Although this status does not mean the CPU module error, the CPU module stops the operation. To set the CPU
module to the RUN status, reset the CPU module using the RESET/L.CLR switch Note12.8 or set the RUN/STOP
Can
NO
"ERR." LED
turn off?
YES
Completed
Note1
Note12.8 Basic
For the Basic model QCPU, use the RUN/STOP/RESET switch for operation.
12 - 19
CHAPTER12 TROUBLESHOOTING
The USER LED turns on when an error is detected by the CHK instruction or the annunciator (F) turns on. 2
If the USER LED is on, monitor the special relays SM62 and SM80 in the monitor mode of GX Developer.
6
When the RESET/L. CLR switch is tilted to L.CLR several times for latch clear operation, the USER LED flickers to indicate
that the latch clear processing is in process.
When the RESET/L. CLR switch is further tilted to L.CLR while the USER LED flickering, the USER LED turns off and
7
terminates the latch clear processing.
8
12.2.16 When the BAT. LED has turned on or is flickering
When the BAT. LED has turned on or is flickering, follow the procedure described below.
Note1
Note12.9 Universal
For the Universal model QCPU, use the RUN/STOP/RESET switch for operation.
12 - 20
12.2.17 When the BOOT LED is flickering
Refer to the following flowchart when the BOOT LED of the CPU module flickers at programmable controller power-on,
at operation start, or during operation.
12 - 21
CHAPTER12 TROUBLESHOOTING
5
Is the LED on when the NO
output module is monitored Reexamine the program.
on GX Developer? 6
YES
8
Does the output NO
Change the output number.
number match?
YES
Figure 12.15 When the LEDs of the output module do not turn on
Note1
Note12.10 Basic
The Basic model QCPU does not have the MODE LED. In the flowchart, proceed to "YES".
12 - 22
12.2.19 When output load of the output module does not turn on
Refer to the following flowchart when the output load of the output module does not turn on during programmable
controller operation.
YES
0V
YES On
Supply
voltage
What is the voltage value
among the various 0V Set the GX Developer in the
output COM terminals of the monitor mode and check that the
output module? input signal is OFF.
(Monitor signal off)
The rated voltage
is supplied.
For the trouble in which input signal to the input module does not turn off, troubleshoot referring to Section 12.5, Examples of
I/O Modules Troubleshooting.
12 - 23
CHAPTER12 TROUBLESHOOTING
YES NO
Can a program be read?
YES 12
5
Is the connection cable NO Connect the connection cable
connected properly? properly.
6
YES
NO YES
Can a program be read?
7
Can a program YES
be read by replacing the
connection cable? 8
NO
RS-232 YES
NO YES
Can a program be read?
NO
12 - 24
12.2.21 When unable to write a program
Refer to the following flowchart when a program cannot be written in the CPU module.Note1
Is the DIP
ON Turn the DIP switch Note12.11
switch Note12.11 SW1
SW1 (system protect) to OFF.
set to OFF?
OFF
NO Can a program YES
be written?
NO
NO Can a program YES
be written?
Memory card
Note12.12 Perform the following.
Confirm whether the write-
Is the memory program protect switch is off or not.
memory? Confirm if it is formatted.
Confirm the writing destination
Program memory specification.
Perform the following.
Organize file.
Confirm memory space.
Confirm the writing destination Can a program YES
specification. be written?
NO
Can a program YES
be written?
NO
NO
Note1
The Basic model QCPU and Universal model QCPU do not have the DIP switches.
In the flowchart, proceed to "OFF".
Note12.12 Basic
The Basic model QCPU does not support the memory card.
12 - 25
CHAPTER12 TROUBLESHOOTING
8
Power on the programmable
controller/perform reset operation.
NO
Completed Hardware fault
Please consult your local nearest
Mitsubishi or representative,
explaining a detailed description of
the problem.
12 - 26
12.2.23 When unable to perform boot operation from the memory card
Refer to the following flowchart when the boot operation of the CPU module cannot be performed using the memory
card.Note1
NO
NO Can boot operation YES
be performed?
Note12.13
Set the DIP switch 2 and 3 to the
Is the parameter- NO drive in which the parameter file is
valid drive specified by the stored.
DIP switches?
YES
Is a file set NO
with parameter boot Set a file to boot file setup.
file setup?
YES
NO Can boot operation YES
be performed?
Note1
The Basic model QCPU and Universal model QCPU do not have the DIP switches.
In the flowchart, proceed to "YES".
12 - 27
CHAPTER12 TROUBLESHOOTING
YES
NO YES
12
Can boot operation
be performed?
5
Is boot NO
operation file stored in the Write a file to the memory card.
memory card?
6
YES
NO Can boot operation YES
be performed? 7
Please consult your local nearest
Mitsubishi or representative,
8
explaining a detailed description of
the problem. Completed
Figure 12.20 When boot operation cannot be performed from the memory card
12.2.23 When unable to perform boot operation from the memory card
12.2 Troubleshooting
12 - 28
12.2.24 When “UNIT VERIFY ERR.” has occurred
Refer to the following flowchart when “UNIT VERIFY ERR.” has occurred at programmable controller power-on or
during operation.
Has
the module on
the corresponding slot been YES
Reset the CPU module.
removed/mounted during
operation?
NO
Has the "ERR." YES
LED turned off?
Is the module NO
of the applicable slot Mounted the module properly.
mounted properly? NO
NO YES
Has the "ERR."
LED turned off?
YES
NO Has the "ERR." YES
LED turned off?
Error detection
Error detection
Error detection
Hardware fault
Mitsubishi
Please consult your local nearest
service center
Mitsubishi or representative,
or representative,
explaining a detailed description of Completed
the problem.
12 - 29
CHAPTER12 TROUBLESHOOTING
Is the module of
the applicable slot mounted NO Mount the module and extension
5
properly? Is the extension cable of the cable properly.
applicable base unit connected
properly?
6
YES NO Is the "ERR." LED YES
turned off?
NO
Error detection
Error detection
Error detection
Hardware fault
Please consult your local Mitsubishi
nearest
service center
Mitsubishi or representative,
or representative,
explaining a detailed description of Complete
the problem.
12 - 30
12.2.26 When the CPU module does not start
Refer to the following flowchart when the CPU module does not start upon power-on.Note1
YES
YES NO YES
Does the CPU module start?
Connect peripheral deivce.
Is communication YES
with peripheral device
succeeded?
YES NO YES
Does the CPU module start?
Is the RESET-L.
CLR switch of the CPU module RESET position
in the RESET position? Cancel the RESET position.
Note12.15
NO
The following pleces of hardware may be faulty.
1) CPU module
2) Main base unit, extension base unit
3) Extension cable
4) I/O Module (If one is installed) End
5) Interlligent function module (If one is installed)
6) Network module (If one is installed)
Perform operations in due order, starting with the minimum system
where the power supply module and CPU module are mounted on the
main base unit.
If the module will not work, please consalt your local nearest Mitsubishi
or representative, explaining a detailed discription of the problem.
Note1
Note12.14 Basic
For the Basic model QCPU, it applied to the CPU module (power supply section) is.
Note12.15 Basic
For the Basic model QCPU, check if the RUN/STOP/RESET switch of CPU module is in the RESET position.
12 - 31
CHAPTER12 TROUBLESHOOTING
Refer to the following flowchart when “OPERATION ERROR” (error code: 4100) has occurred at execution of the
S(P).SFCSCOMR and S(P).SFCTCOMR instructions.
2
3
The OPERATION ERROR has
occurred at the execution of
SP.SFCSCOMR and
SP.SFCTCOMR instructions.
12
Check the program file name and step
No. where error occurred on the PLC
diagnostic screen of GX Developer.
5
Check that the values of the following
instruction devices are within the
range.
6
n1 (Block No.)
n2 (No. of reading comment)
n3 (No. of reading comment pe scan)
7
12.2.27 When “OPERATION ERROR” has occurred at execution of the S(P).SFCSCOMR and
12.2 Troubleshooting
YES
Correct the values specified with n1,
n2 and n3 of the instruction device
within the range.
S(P).SFCTCOMR instructions.
Set the comment file stored in the
memory other than ATA card *1 as
"Comment file used in a command".
12 - 32
12.2.28 When comments cannot be read at execution of the S(P).SFCSCOMR
and S(P).SFCTCOMR instructions
Refer to the following flowchart when any comment of active step or transfer condition associating with active step
cannot be read at execution of the S(P).SFCSCOMR and S(P).SFCTCOMR instructions
YES
Should the
comment file setting be
NO (Setting with the QCDSET instruction)
performed with the "Comment
file used in a command"
setting of the PLC
parameter?
YES
(Setting with the PLC parameter)
Execute the QCDSET instruction to
Switch the power from OFF to ON perform the comment file setting.
or reset, after writing the PLC
parameter to the CPU module.
Can the
NO comment of active step or the
comment of transfer condition
associating with active
step be read?
YES
12 - 33
CHAPTER12 TROUBLESHOOTING
Is the "Comment
file used in a command" 2
setting of the "PLC file setting" of YES
the PLC parameter the "Use
the same file name as
the program"? 3
Does a
comment file which
YES has the same name as the
NO
SFC program file exist in
the target memory?
12
NO
5
Create a comment file which has the same
name as the SFC program file and store it
in the target memory.
6
Switch the power from OFF to ON or
reset, after writing the PLC parameter.
7
Can the
comment of active step or
8
NO the comment of transfer
condition associating
Check the activated SFC block with the with active step
"All block batch monitor" of GX be read?
12.2.28 When comments cannot be read at execution of the S(P).SFCSCOMR and S(P).SFCTCOMR
12.2 Troubleshooting
Developer.
YES
instructions
Is the block Completed
specified with the
SP.SFCSCOMR and NO
SP.SFCTCOMR instructions
activated?
YES
Check the active step in the block Correct the block specified with the
specified with the SP.SFCSCOMR and instruction or review the executing
SP.SFCTCOMR instructions on "Active condition of instruction. (The comment of
step monitor" of GX Developer. the active step or the comment of transfer
condition associating with the active step
cannot be read, since the block specified
Does with the instruction is not activated.)
an activated step
exist in the block specified NO
with the SP.SFCSCOMR
and SP.SFCTCOMR
instructions?
YES
Review the executing condition of
Confirm that the comment of the activated
instruction. (The comment of the active
step or the comment of transfer condition
step or the comment of transfer condition
associating with the activated step can be
associating with the active step cannot
read.
be read, since no activated step exists in
the block specified with the instruction.)
12 - 34
12.2.29 When “PARAMETER ERROR” has occurred at power on or reset.
Refer to the following flowchart when “PARAMETER ERROR” occurs at power ON/reset.
Is the error
detected as the result of the YES
parameter check on GX
Developer?
Correct the item where the error has
NO occurred. Perform the parameter
check on GX Developer again and
confirm that no error is detected.
Is a device set
for each CPU transmission YES
range individually with
the multiple CPU
refresh setting?
Is a device
for each refresh of
NO the transmission range for the NO
host CPU set as " "
(Blank)?
Is the product
YES information of the CPU
module "070320000000000"
or later?
Switch the power from OFF to ON or
reset, after writing the PLC parameter
to the CPU module again. NO
Confirm that the same error does not Uncheck "Set starting device for each
occur. PLC" or change to a CPU module of
which product information is
"070320000000000" or later. (If the
product information is not
"070320000000000" or later, the
function for setting a device of each
transmission range individually cannot
be used.)
12 - 35
CHAPTER12 TROUBLESHOOTING
2
code: 3040) has occurred.
NO
5
Is the PARAMETER ERROR (error
code: 3040) detected again?
Completed
6
YES
12 - 36
(3) When PARAMETER ERROR (error code: 3041) has occurred.
The PARAMETER ERROR (error
code: 3041) has occurred.
NO
Is the PARAMETER ERROR (error
code: 3041) detected again?
Completed
YES
YES
12 - 37
CHAPTER12 TROUBLESHOOTING
YES
Is the "PARAM" set for
booting to the program 12
memory with the "Boot
file setting" of the PLC
parameter?
5
NO
YES
YES
Since the CPU module may be Select a parameter-valid drive with
faulty, please contact your local the "target memory" on the PLC
Mitsubishi representative, explaining writing screen of GX Developer.
a detailed description of the problem.
12 - 38
12.2.30 When the CPU cannot communicate with GX Developer
Refer to the following flowchart when communication with peripheral device is disabled when connecting the CPU
module with GX Developer.
The CPU cannot communicate
with the GX Developer.
NO
Replace the
CPU module with Replace the replaced CPU module
another one and check to see YES
if communication can be made
with the original CPU module and
between the replaced CPU check to see if the CPU module
module and GX starts up normally.
Developer.
Is the connection USB Is the USB driver NO Install the USB driver into
type RS-232? installed in the personal the personal computer.
computer?
RS-232 YES
NO Can the CPU YES
communicate with the GX
Developer?
NO
12 - 39
CHAPTER12 TROUBLESHOOTING
2
How is the "POWER" LED NO (When on (red))
of the power supply module? Section 12.2.8 Flowchart for when
the "POWER" LED turns on (red).
YES
12
YES NO Can the CPU communicate YES
with the GX Developer?
5
Is the extension
cable connected properly? NO
(Isn't IN connected to
IN or OUT connected
Connect the extension cable properly.
6
to OUT?)
NO
A hardware fault may have occurred in any of the following modules.
1) CPU module
2) Main base unit, extension base unit
3) Extension cable Completed
4) I/O Module (If one is installed)
5) Interlligent function module (If one is installed)
6) Network module (If one is installed)
Perform operations in due order, starting with the minimum system
where the power supply module and CPU module are mounted on the
main base unit.
If the module will not work, please consalt your local nearest Mitsubishi
or representative, explaining a detailed discription of the problem.
12 - 40
12.2.31 When Ethernet communication is not available other than by direct
connection to GX Developer
Refer to the following flowchart when Ethernet communication is not available other than by connecting GX Developer
directly.
YES
Is the Find CPU function used
for IP address setting? *1
YES
NO Is duplicate IP address Set unique IP addresses.
warning displayed?
NO
NO Is Ethernet YES
communication available
with GX Developer?
YES
NO Is Ethernet YES
communication available
with GX Developer?
YES
Accessing a QnA/A series
CPU on another station?
NO
NO Is Ethernet YES
communication available
with GX Developer?
Section 12.2.32
12 - 41
CHAPTER12 TROUBLESHOOTING
*1: If the target CPU is not found by the Find CPU function, check the following.
Route: 1
• Check that access to the target CPU does not pass through any router.
• Check the parameters.
• Check that the Find CPU function is not rejected by a parameter setting of the target CPU.
Computer-side settings:
• Check if an IP address is set.
2
• Check if use of the Ethernet port is enabled.
• Check if the firewall setting is disabled.
When enabled, check if communication with Built-in Ethernet QCPU is excluded in the setting.
• Check if communication with Built-in Ethernet QCPU is disabled by security software. 3
CPU-side settings:
• Is the load for service processing too high in the target CPU? (If so, increase the service
process time in Service process setting of PLC parameters.)
*2: Check the following: 12
PC side I/F Ethernet board setting
• Correct protocol specification (TCP/UDP)?
PC side I/F Detailed setting of PLC module
• Isn't direct CPU connection selected?
• Correct IP address specification?
5
*3: Check if all of the following conditions are met:
• The Built-in Ethernet QCPU connected to GX Developer is in a multiple CPU configuration.
• The control CPU of the MELSECNET/H network module on the route is any other than Built-in
Ethernet QCPU. 6
• The product information of the MELSECNET/H network module on the route is:
(100320000000000-D or earlier)
12.2.31 When Ethernet communication is not available other than by direct connection to GX
12.2 Troubleshooting
Developer
12 - 42
12.2.32 When Ethernet communication with the target device is not available
Refer to the following flowchart when Ethernet communication with the target device is not available.
YES Is Ethernet
NO communication available YES
with the target device?
YES Is Ethernet
NO communication available YES
with the target device?
NO
Check wiring of cables and hub
and connect them correctly. *1
Is Ethernet
NO YES
communication available
with the target device?
Off or
How is the "POWER" on (red) (When off)
LED of the power supply module? Section 12.2.6 When the "POWER" LED turns off
(When on (red))
Section 12.2.8 When the "POWER" LED turns on (red)
On (green)
*1: Supplemental remarks on switching hubs
Reconnecting a personal computer or CPU to a
To diagnose the built-in
switching hub or replacing the switching hub with
Ethernet port, power on the
another may take time for the hub to read MAC
CPU module again or reset it.
addresses.
Retry it after a little while, or power on the hub again.
Completed
12 - 43
CHAPTER12 TROUBLESHOOTING
Section 12.2.14 12
Flowchart for when the "ERR." LED is on/flickering
5
Is the Ethernet
port setting in "PLC parameter" for the Built-in NO
Enter correct parameters.
Ethernet port QCPU correct?*3
6
YES Is Ethernet
NO YES
communication available with
7
the target device?
Is forced deactivation
YES Disable the forced
set in "Status of each connection"
of "Ethernet diagnosis"? deactivation.
8
NO Is Ethernet
NO YES
communication available with
the target device?
12.2.32 When Ethernet communication with the target device is not available
12.2 Troubleshooting
Any error in
"Status of each connection" or YES Take actions according to
"Error log" of "Ethernet the error code.
diagnosis"?
NO Is Ethernet
NO YES
communication available with
the target device?
Completed
12 - 44
(From the previous page)
NO Is Ethernet
NO YES
communication available with
the target device?
YES
TCP/IP?
NO
YES
NO Is Ethernet YES
communication available with
the target device?
In the detailed
Perform the following.
host station setting of Set a time out value or number
YES
"Transfer Setup", increase the time out of retries again.
value or the number of retries. Consult your network administrator
Is communication now and check the network status.
available?
NO
Is Ethernet
NO YES
communication available with
the target device?
Completed
12 - 45
CHAPTER12 TROUBLESHOOTING
Is a response returned in
PING test?
YES
2
Does transmission NO
NO pass through a router?
5
YES
12.2.32 When Ethernet communication with the target device is not available
12.2 Troubleshooting
Are the router IP address and NO Set the router IP address and subnet
subnet mask set on the target mask correctly.
device side?
NO Is Ethernet YES
YES
communication available with
1) the target device?
NO
Any error in the router? Remove the error in the router.
YES
NO Is Ethernet YES
communication available with
the target device?
YES
Is Ethernet
NO YES
communication available with
the target device?
Completed
(To the next page) *4: Check the following.
Are the routing settings for the Built-in Ethernet port QCPU and target devices correct?
Isn't communication with the Built-in Ethernet QCPU disabled by any security or
security software?
12 - 46
(From previous page)
YES
Is Ethernet
NO YES
communication available with
the target device?
Error detection
Hardware fault
Please consult your local nearest
Mitsubishi or representative,
explaining a detailed description of
Completed
the problem.
12 - 47
CHAPTER12 TROUBLESHOOTING
Refer to the following flowchart when Ethernet communication is not available by direct connection to GX Developer.
2
Ethernet communication is not available
by direct connection to GX Developer.
3
Is one cable used for NO Connect the CPU to GX
Developer directly with one cable.
connection?
12
YES
Is Ethernet
NO
communication with GX Developer
YES
5
available?
Any cable
disconnection or poor contact?
NO
Connect the cable correctly.
6
YES
NO Is Ethernet YES
7
communication with GX Developer
available?
8
Is the computer's IP address set NO Ask your network administrator for the
correctly? *1 computer's IP address, and set it correctly.
YES
Is Ethernet
NO YES
communication with GX Developer
available?
12 - 48
(From the previous page)
How is Off
the "SD/RD" LED of the CPUmodule?
Flashing YES
Are cables connected properly? *2
NO
NO Is Ethernet YES
communication with GX Developer
available?
(When off)
How is Off or on (red) Section 12.2.6 When the "POWER" LED turns off
the "POWER" LED of the power
(When on (red))
supply module?
Section 12.2.8 When the "POWER" LED turns on (red)
On (green)
How is On or flashing
the "ERR." LED of the CPU module?
Hardware fault
Please consult your local nearest
Off YES Mitsubishi or representative,
"LAN CTRL. DOWN"?
explaining a detailed description
of the problem.
NO
Change to USB connection to read
CPU setting parameters.
Section 12.2.14
Flowchart for when the "ERR." LED is on/flickering
Is direct
MELSOFT connection NO Deselect "Disable direct
disabled in "Built-in Ethernet port" connection to MELSOFT".
of "PLC parameter"?
YES
Is Ethernet
NO YES
communication with GX Developer
available?
12 - 49
CHAPTER12 TROUBLESHOOTING
1
(From the previous page)
In "Status of
each connection" of
NO
2
"Ethernet diagnosis", is the directly Disable the forced deactivation.
connected connection set in
forced deactivation
status?
Is Ethernet
3
YES NO YES
communication available
with GX Developer?
12
Any error in "Status of NO
each connection" or "Error log" of Take actions according to the error code.
"Ethernet diagnosis"? 5
Is Ethernet
YES NO
communication available
with GX Developer?
YES
6
7
In the detailed
host station setting of Perform the following.
"Transfer Setup", increase the value YES Adjust the communication timeout or the
of Time out or Retry times. number of retries again.
Check the status of the cables, connected
8
Is communication now
available? devices, and Built-in Ethernet port QCPU
NO
Error detection
Is direct connection
available for the connected YES Connect a hub to the line and
device? (Check the Ethernet interface communicate with others through
specifications.) the hub.
NO
NO Is Ethernet YES
communication available
with GX Developer?
Hardware fault
Please consult your local nearest
Mitsubishi or representative,
explaining a detailed description of
the problem.
Completed
12 - 50
12.2.34 When Ethernet communication with CPU module is slow or unstable
Refer to the following flowchart when Ethernet communication with a CPU module is slow or unstable.
YES
Does a duplicate IP
address exist? *1 Set unique IP addresses.
NO
NO Is Ethernet YES
communication stabilized?
Is UDP in
MELSOFT connection YES Use UDP in MELSOFT connection for the specified
or MC protocol used for more the number
number of modules or less.
of modules set by the
parameter?
NO
NO Is Ethernet YES
communication stabilized?
NO
YES
Retry or increase the number of Use retries. *2
retries. Improved?
NO
YES
Replace the hub, router or cables. Replace the faulty one with another.
Stabilized?
NO
Is the hub
capable of flow control
(IEEE802.3x PAUSE)? NO Consult your network administrator and correct the hub.
Is the flow control enabled? Use a hub that is capable of flow control.
(Consult your network administrator.) Enable the flow control.
12 - 51
CHAPTER12 TROUBLESHOOTING
3
NO NO Is Ethernet YES
communication stabilized?
12
Consult your network administrator and check the
Is communication of a network condition.
YES Take actions against noise to reduce communication
device other than the Built-in Ethernet port
5
QCPU unstable? (Consult your network errors. *3
administrator.) Check the traffic, and if a high traffic is a cause of the
problem, take actions for it.
NO
NO Is Ethernet
communication stabilized?
YES
6
Have many
unnecessary broadcast data YES
been received? (See Connection
status in Ethernet 7
diagnosis.)
Unnecessary broadcast data have been highly loaded.
NO Increase service time for the Built-in Ethernet port QCPU.
Consult your network administrator, and check the network condition.
Identify a broadcasting device, and restrict the broadcast data volume.
8
(Devices such as computers or routers may broadcast data.)
Use filtering of broadcast data with a router to prevent the Built-in Ethernet port
QCPU from receiving them.
Separate the network where frequent broadcast occur from the network
NO Is Ethernet YES
communication stabilized?
NO Is Ethernet YES
communication stabilized?
YES
Is any interrupt program used? Reduce the frequency and process time of the interrupt
program.
NO
NO Is Ethernet YES
communication stabilized?
12 - 52
*3 : A communication error may occur due to high-frequency noise emitted from a device other than programmable
controllers. The following measures can be taken to protect network systems from high-frequency noise.
Wiring
• Do not install twisted pair cables together with the main circuit or power cables.
• Put twisted pair cables in a duct.
• Replace UTP cables with STP cables.
Communication method
• Use TCP/IP to exchange data with the target device.
• Increase the number of communication retries, if necessary.
• 10Mbps communication
• In the case of using 100Mbps, replace the hub with a 10Mbps hub and perform data
communication at a transmission speed of 10Mbps.
12 - 53
CHAPTER12 TROUBLESHOOTING
Communication error 2
YES
NO YES
12
Was the error resolved?
NO 6
(To the next page)
YES
NO YES
8
Was the error resolved?
Is the IP address NO
Correct the IP address and send the command again.
YES
NO YES
Was the error resolved?
Are command
Correct the command format referring to the following
format specifications such as NO
manual.
command type, device,
MELSEC Communication Protocol Reference Manual
or address correct?
YES
NO YES
Was the error resolved?
Hardware fault
Please consult your local nearest Mitsubishi or
representative, explaining a detailed description of the
problem.
Completed
12 - 54
(From the previous page)
Is the same
protocol (TCP/IP) used for NO Use the same protocol (TCP/IP) for communication with
communication with the target the target device.
device?
YES
NO YES
Was the error resolved?
Is the IP address NO
specified in the command correct? Correct the IP address and send the command again.
YES
NO YES
Was the error resolved?
YES
NO YES
Was the error resolved?
Is the Communication NO
data code setting (binary/ASCII) Send a command matched with Communication data
matched with the sent code setting.
command?
YES
NO YES
Was the error resolved?
NO
Is the sub-header
Send a sub-header of a normal value.
value correct?
YES
NO YES
Was the error resolved?
NO
Were data of the request Send data of the request data length.
data length sent?
YES
NO YES
Was the error resolved?
Completed
12 - 55
CHAPTER12 TROUBLESHOOTING
YES
NO YES 3
Was the error resolved?
NO
Was the error resolved?
YES 6
Section 12.2.32
Completed
12 - 56
12.2.36 When clock data cannot be set by SNTP
Refer to the following flowchart when clock data cannot be set by SNTP.
NO YES
YES Is the time setting available?
YES
Is the multiple CPU function used?
NO
NO
Has time been set on CPU
No.1 in the multiple CPU system? Set time on CPU No.1.
YES
NO YES
Is the time setting available?
YES
NO YES
Is the time setting available?
12 - 57
CHAPTER12 TROUBLESHOOTING
YES NO YES
Is the time setting available?
3
Is the SNTP server NO
specified for Q series running
properly?
Repair the SNTP server.
12
NO YES
YES Is the time setting available?
5
Section 12.2.32 Completed
When Ethernet communication with the target device is not available 6
12 - 58
12.2.37 When unable to receive data on the external device side by the Socket
communication function
NO Section 12.2.39
The connection opened?*1 When open process of the Socket
communication function does not complete
YES
NO
Any error
shown in the Status of YES *1 Refer to the corresponding bit of SD1282 (Open completion signal).
each connection screen or the Error Take corrective actions
*2 Check the following:
log screen on the Ethernet according to the error code.
diagnosis screen? Is the IP address correct?
Is the subnet mask pattern correct?
Is the default router IP address correct?
NO Connection No.
Are the connection method and open method correct?
Are the port No. of own station and IP address/port No. of the
The SOCSND Take corrective actions target device correct?
YES
instruction completed according to the error code Are the protocols and functions to be used all configured in the
in error (Error completion stored in the completion status Open settings?
device turned on)? area of the SOCSND instruction. *3 Two or more receive instructions may be executed to read the data
sent by one send instruction since TCP does not have architecture for
specifying data boundaries.
NO
For this reason, the received data size must be checked when
receiving, and receive the remaining data if exists.
The parameters For more details, refer to the following.
NO
and setting data for Correct the parameters and QnUCPU User's Manual (Communication via Built-in
SOCOPEN correct?*2 setting data for SOCOPEN. Ethernet Port)
YES
YES
NO
Set the send data length?*3 Set the data length.
YES
NO
Any faulty part Correct the faulty part in
in the target device? the target device.
YES
Section 12.2.32
12 - 59
CHAPTER12 TROUBLESHOOTING
12
YES
*3 Two or more receive instructions may be executed to read the data
sent by one send instruction since TCP does not have architecture for
Any error specifying data boundaries.
shown in the Status YES For this reason, the received data size must be checked when
of each connection screen or Take corrective actions
the Error log screen on the according to the error code. receiving, and receive the remaining data if exists.
5
Ethernet diagnosis For more details, refer to the following.
screen? QnUCPU User's Manual (Communication via Built-in
Ethernet Port)
NO
*4 It is recommended to include the checking method, such as the data
length and data type code, in the message data so that the data
6
The SOCRCV Take corrective actions according
instruction completed in YES information such as the number of bytes and data size can be
to the error code stored in
error (Error completion the completion status area of checked on the receive side.
device turned on)? the SOCRCV instruction.
NO
7
The receive completion NO
signal of the connection on?
8
YES The parameters NO Correct the parameters
and setting data for SOCOPEN and setting data for
correct?*2 SOCOPEN.
The SOCRCV(S) Correct the execution
NO
instruction being executed? conditions of the SOCRCV(S)
YES
Any faulty part NO Correct the faulty part
in the target device? in the target device.
YES
Section 12.2.32
When Ethernet communication with
the target device is not available
Provided
the processing for When the data length is determined, use the fixed-length receive
receiving remaining data when NO
the actual data is less than the mode.
response data length of the If the actual data volume is less than the expected data length,
receive message? take actions for receiving the remaining data .
If the actual data volume is exceeding the expected data length,
process the data as the next message or as unnecessary data.
YES
*3, *4
Section 12.2.32
When Ethernet communication with
the target device is not available
*5 The start-up contact may not be turned on only with the Reception status signal (SD1286) depending
Complete on the scan time since the signal turns on if the next data are received immediately after executing
the SP.SOCRCV instruction.
In this case, provide a normal close contact of the completion device of the SP.SOCRCV instruction
in the start-up condition of the instruction.
12 - 60
12.2.39 When open process of the Socket communication function does not
complete
When open process of
the Socket communication
function does not complete
NO
UDP/IP
TCP/IP? Correct the parameters.*1
YES TCP/IP
Any error
shown in the Status
NO of each connection screen YES Take corrective
Parameters are
Correct the parameters. or the Error log screen on actions according to
correctly set?*2
the Ethernet diagnosis the error code.
screen?
YES NO
Take corrective actions
Connect from the target The SOCOPEN according to the error
The target device NO YES
device to the specified instruction completed code stored in the
is connected to the in error (Error completion
port. completion status area
specified port?*3 device turned
on)? of the SOCOPEN
*3 When in Fullpassive, check that instruction.
YES the IP address and port No. of NO
the target device match with
the set data.
The parameters NO Correct the parameters
and setting data for and setting data for
SOCOPEN SOCOPEN.
correct?*1
YES
YES
YES
12 - 61
CHAPTER12 TROUBLESHOOTING
The CPU module uses the self diagnostics function to display error information (on the LED) and
stores the information into the special relay SM and special register SD, when an error occurs in
the following situations:
• When the Progammable Controller is powered ON.
• When the CPU module is switched from STOP to RUN.
• While the CPU module is running.
If an error occurs when a communication request is issued from the peripheral device, intelligent
function module or network system to the CPU module, the CPU module returns the error code 12
(4000H to 4FFFH) to the request source.
The following describes the description of errors which occur in the CPU module and the
corrective actions for the errors.
12 - 62
12.3.1 Error codes
Errors are detected by the self diagnostic function of the CPU module or detected during
communication with the CPU module.
The relation between the error detection pattern, error detection location and error code is shown
in Table 12.1.
Table12.1Reference destination
Error detection
Error detection pattern Error code Reference
location
Detection by the self
diagnostics function of CPU CPU module 1000 to 10000*1*2 Section 12.3.3 to 12.3.9
module
• QCPU User's Manual (Hardware design,
CPU module 4000H to 4FFFH
Maintenance and Inspection)
Serial communication
7000H to 7FFFH Serial Communication User's Manual, etc.
module, etc.
CC-Link System Master/Local Module User's
CC-Link module B000H to BFFFH
Manual
Ethernet module C000H to CFFFH Ethernet Interface Module User's Manual
Detection at communication
CC-Link IE controller CC-Link IE Controller Network Reference
with CPU module E000H to EFFFH
network Manual
• MELSECNET/H mode
Q Corresponding MELSECNET/H Network
MELSECNET/H System Reference Manual
F000H to FFFFH
network module • MELSECNET/10 mode
For QnA/Q4AR MELSECNET/10 Network
System Reference Manual
*1: CPU module error codes are classified into minor, moderate, major errors as shown below.
• Minor error: Errors that may allow the CPU module to continue the operation, e.g., battery error.
(Error code: 1300 to 10000)
• Moderate error: Errors that may cause the CPU module to stop the operation, e.g., WDT error.
(Error code: 1300 to 10000)
• Major error: Errors that may cause the CPU module to stop the operation, e.g., RAM error.
(Error code: 1000 to 1299)
Determine the error level, i.e. whether the operation can be continued or stopped, by referring to
"Operating Statuses of CPU" described in Section 12.3.3 to 12.3.9 "Error Code List"
*2: When detected an error code without being noted in the reference table, please contact your local
Mitsubishi representive.
When an error occurs, reading an error code, error message or the like can be executed with GX
Developer.
For the details of the operation method, refer to the operating manual for GX Developer.
12 - 63
CHAPTER12 TROUBLESHOOTING
The following shows the error messages from the error code 1000 to 1999, the contents and
causes of the errors, and the corrective actions for the errors.
12 - 64
Error LED Status Corresponding
Error Contents and Cause Corrective Action
Code CPU Status CPU
1006 [MAIN CPU DOWN] QCPU
1007 Runaway or failure of CPU module or failure of
main CPU
• Take noise reduction measures.
• Malfunctioning due to noise or other reason
• Reset the CPU module and RUN it again.If the
• Hardware fault Qn(H)
same error is displayed again, this suggests a
■Collateral information QnPH
1008 CPU module hardware fault.(Contact your local
• Common Information:– QnPRH
Mitsubishi representative.)
• Individual Information:–
■Diagnostic Timing
• Always
[MAIN CPU DOWN]
• A failure is detected on the power supply module,
CPU module, main base unit, extension base
unit or extension cable.
Reset the CPU module and RUN it again.If the
• When using the redundant base unit, the redun- Q00J/Q00/Q01*4
same error is detected again, it is considered that
dant power supply module failure in both sys-
the power supply module, CPU module, main base Qn(H)*6
1009 tems and/or the redundant base unit failure are QnPH
unit, extension base unit or extension cable is
detected. QnPRH
faulty.
■Collateral information QnU
(Contact your local Mitsubishi representative.)
• Common Information:–
• Individual Information:–
■Diagnostic Timing
• Always
[END NOT EXECUTE]
Entire program was executed without the execution
of an END instruction. RUN:
• When the END instruction is executed it is read Off
• Take noise reduction measures.
as another instruction code, e.g. due to noise. ERR.:
• Reset the CPU module and RUN it again. If the
• The END instruction has been changed to Flicker
1010 same error is displayed again, this suggests a QCPU
another instruction code somehow.
CPU module hardware fault. (Contact your local
■Collateral information CPU Status:
Mitsubishi representative.)
• Common Information:– Stop
• Individual Information:–
■Diagnostic Timing
• When an END instruction executed
[SFCP. END ERROR]
The SFC program cannot be normally terminated
due to noise or other reason.
• The SFC program cannot be normally terminated
• Take noise reduction measures.
due to noise or any similar cause.
• Reset the CPU module and RUN it again. If the Q00J/Q00/Q01*4
• The SFC program cannot be normally terminated
1020 same error is displayed again, this suggests a QnPH
for any other reason.
CPU module hardware fault. (Contact your local QnU
■Collateral information
Mitsubishi representative.)
• Common Information:–
• Individual Information:–
■Diagnostic Timing
• When SFC program is executed
[MAIN CPU DOWN]
Runaway or error of the CPU module was
detected. • Take measures against noise.
• Malfunction due to noise etc. • Reset the CPU module and run it again. If the
• Hardware failure same error is displayed again, the CPU module
1035 QnU
■Collateral information has hardware failure.(Contact your local Mitsub-
• Common Information:– ishi representative, explaining a detailed descrip-
• Individual Information:– tion of the problem.)
■Diagnostic Timing
• Always
12 - 65
CHAPTER12 TROUBLESHOOTING
1102
CPU module are faulty.
■Collateral information
• Reset the CPU module and RUN it again. If the
same error is displayed again,this suggests a
Stop
12
• Common Information:–
CPU module hardware fault.(Contact your local
• Individual Information:–
Mitsubishi representative.)
■Diagnostic Timing
• At power ON/ At reset/ When an END instruction
executed
12 - 66
Error LED Status Corresponding
Error Contents and Cause Corrective Action
Code CPU Status CPU
[RAM ERROR]
The device memory in the CPU module is faulty.
■Collateral information
• Common Information:– QCPU
• Individual Information:–
■Diagnostic Timing • Take noise reduction measures.
• At power ON/ At reset • When indexing is performed, check the value of
[RAM ERROR] index register to see if it is within the device
• The device memory in the CPU module is faulty. range.
1103
• The device out of range is accessed due to • Reset the CPU module and RUN it again. If the
indexing, and the device for system is overwrit- same error is displayed again,this suggests a
ten. CPU module hardware fault.(Contact your local Qn(H)*8
■Collateral information Mitsubishi representative.) QnPH*8
• Common Information:– QnPRH*9
• Individual Information:–
■Diagnostic Timing
• At power ON/ At reset/ When an END instruction
executed
[RAM ERROR]
The address RAM in the CPU module is faulty. • Take noise reduction measures.
■Collateral information • Reset the CPU module and RUN it again.If the
1104 • Common Information:– same error is displayed again, this suggests a QCPU
RUN:
• Individual Information:– CPU module hardware fault. (Contact your local
Off
■Diagnostic Timing Mitsubishi representative.)
• At power ON/ At reset ERR.:
Flicker
[RAM ERROR]
The CPU memory in the CPU module is faulty.
■Collateral information CPU Status:
Stop Q00J/Q00/Q01
• Common Information:–
QnU
• Individual Information:–
■Diagnostic Timing • Take noise reduction measures.
• At power ON/ At reset • Reset the CPU module and RUN it again.If the
1105 [RAM ERROR] same error is displayed again, this suggests a
The CPU shared memory in the CPU module is CPU module hardware fault. (Contact your local
faulty. Mitsubishi representative.) Qn(H)*4
■Collateral information QnPH
• Common Information:– QnPRH
• Individual Information:– QnU
■Diagnostic Timing
• At power ON/ At reset
• Check the battery to see if it is dead or not. If
[RAM ERROR]
dead, replace the battery.
The battery is dead.
• Take noise reduction measures.
The program memory in the CPU module is faulty.
• Format the program memory, write all files to the
■Collateral information Qn(H)
• Common Information:– PLC, then reset the CPU module, and RUN it
1106 QnPH*7
• Individual Information:– again.
QnPRH
■Diagnostic Timing If the same error is displayed again, the possible
cause is a CPU module hardware fault. (Contact
• STOP RUN/When an END instruction exe-
your local Mitsubishi representative, explaining a
cuted
detailed description of the problem.)
12 - 67
CHAPTER12 TROUBLESHOOTING
12 - 68
Error LED Status Corresponding
Error Contents and Cause Corrective Action
Code CPU Status CPU
[TRK. CIR. ERROR]
A tracking hardware fault was detected during run-
ning. • Start after checking that the tracking cable is con-
• The tracking cable was disconnected and rein- nected.
serted without the standby system being pow- If the same error is displayed again, the cause is
ered off or reset. the hardware fault of the tracking cable or CPU
• The tracking cable is not secured by the connec- module. (Please contact your local Mitsubishi
1116 tor fixing screws. representative, explaining a detailed description QnPRH
• The error occurred at a startup since the redun- of the problem.) RUN:
dant system startup procedure was not followed. • Confirm the redundant system startup procedure, Off
■Collateral information and execute a startup again. For details, refer to ERR.:
• Common Information:– the QnPRHCPU User's Manual (Redundant Sys- Flicker
• Individual Information:– tem).
■Diagnostic Timing CPU Status:
• During running Stop
[RAM ERROR]
The memory of the CPU module in the Multiple • Take noise reduction measures.
CPU high speed transmission area is faulty. • Reset the CPU module and RUN it again.
■Collateral information If the same error is displayed again, the CPU
1150 QnU*10
• Common Information:– module has hardware failure. Contact your local
• Individual Information:– Mitsubishi representative, explaining a detailed
■Diagnostic Timing description of the problem.
• At power ON/ At reset
[RAM ERROR] • Take noise reduction measures.
The program memory in the CPU module is over- • Format the program memory, write all files to the
written. PLC, then reset the CPU module, and RUN it
■Collateral information again.
1160
• Common Information:– If the same error is displayed again, the CPU
• Individual Information:– module has hardware failure. Contact your local
■Diagnostic Timing Mitsubishi representative, explaining a detailed
• At program execution description of the problem.
[RAM ERROR]
The data of the device memory built in the CPU
• Take noise reduction measures.
module is overwritten.
If the same error is displayed again, the CPU
■Collateral information
1161 module has hardware failure. Contact your local
• Common Information:– QnU
Mitsubishi representative, explaining a detailed RUN:
• Individual Information:–
description of the problem. Off
■Diagnostic Timing
• At program execution ERR.:
[RAM ERROR] Flicker
The error of the data held by the battery in the CPU • Take noise reduction measures.
module is detected. (It occurs when the automatic • Change the CPU main body or SRAM card bat- CPU Status:
format is not set.) tery. Stop
1162 ■Collateral information If the same error is displayed again, the CPU
• Common Information:– module has hardware failure. Contact your local
• Individual Information:– Mitsubishi representative, explaining a detailed
■Diagnostic Timing description of the problem.
• At power ON/ At reset
[RAM ERROR]
The destruction of the data stored in the standard
• Take noise reduction measures.
RAM is detected.
If the same error is displayed again, the CPU
■Collateral information
1164 module has hardware failure. Contact your local QnU*11
• Common Information:–
Mitsubishi representative, explaining a detailed
• Individual Information:–
description of the problem.
■Diagnostic Timing
• When instruction executed
*10 The Universal model QCPU except the Q00UJCPU, Q00UCPU, Q01UCPU, and Q02UCPU.
*11 The Q10UD(E)HCPU, Q13UD(E)HCPU, Q20UD(E)HCPU, .Q26UD(E)HCPU only.
12 - 69
CHAPTER12 TROUBLESHOOTING
12 - 70
Error LED Status Corresponding
Error Contents and Cause Corrective Action
Code CPU Status CPU
• Check FUSE. LED of the output modules and
[FUSE BREAK OFF] replace the module whose LED is lit.
There is an output module with a blown fuse.
(The module with a blown fuse can also be iden-
■Collateral information
tified using GX Developer.
• Common Information:Module No.(Slot No.) Qn(H)
Check the special registers SD1300 to SD1331
[For Remote I/O QnPH
to see if the bit corresponding to the module is
network]Network No./ QnPRH
"1".) RUN:
Station No. QnU
• When a GOT is bus-connected to the main base Off/On
• Individual Information:–
unit or extension base unit, check the connection ERR.:
■Diagnostic Timing
status of the extension cable and the earth status Flicker/On
• Always
1300 of the GOT.
[FUSE BREAK OFF] CPU Status:
There is an output module with a blown fuse. Stop/
■Collateral information Check ERR. LED of the output modules and
Continue*1
• Common Information:Module No.(Slot No.) replace the module whose LED is lit.
[For Remote I/O (The module with a blown fuse can also be identi-
Q00J/Q00/Q01
network]Network No./ fied using GX Developer. Check the special regis-
Station No. ters SD130 to SD137 to see if the bit corresponding
• Individual Information:– to the module is "1".)
■Diagnostic Timing
• Always
[I/O INT. ERROR]
An interruption has occurred although there is no
interrupt module. Any of the mounted modules is experiencing a
■Collateral information hardware fault. Therefore, check the mounted mod-
1310 QCPU
• Common Information:– ules and change the faulty module. (Contact your
• Individual Information:– local Mitsubishi representative.)
■Diagnostic Timing
• During interrupt
[I/O INT. ERROR]
An interrupt request from other than the interrupt
RUN:
module was detected.
Off
■Collateral information Take action so that an interrupt will not be issued Q00J/Q00/Q01*4
• Common Information:– from other than the interrupt module. ERR.:
QnU
• Individual Information:– Flicker
■Diagnostic Timing
• During interrupt CPU Status:
Stop
• Correct the interrupt pointer setting in the PLC
1311 [I/O INT. ERROR]
system setting of the PLC parameter dialog box.
An interrupt request from the module where inter-
• Take measures so that an interrupt is not issued
rupt pointer setting has not been made in the PLC
from the module where the interrupt pointer set-
parameter dialog box was detected. Q00J/Q00/Q01 *5
ting in the PLC system setting of the PLC param-
■Collateral information QnPRH
eter dialog box has not been made. Correct the
• Common Information:– QnU
interrupt setting of the network parameter. Cor-
• Individual Information:–
rect the interrupt setting of the intelligent function
■Diagnostic Timing
module buffer memory. Correct the basic pro-
• During interrupt
gram of the QD51.
1320 [LAN CTRL.DOWN] RUN:
The H/W self-diagnostics detected a LAN controller
Off
failure.
ERR.:
■Collateral information This suggests a CPU module hardware fault. (Con-
Flicker QnU*13
1321 • Common Information:– tact your local Mitsubishi representative.)
• Individual Information:–
CPU Status:
■Diagnostic Timing
Stop
• At power ON/ At reset
*1 CPU operation can be set in the parameters at error occurrence. (LED indication varies.)
*4 Function version is B or later.
*5 Function version is A.
*13 This applies to the Built-in Ethernet port QCPU.
12 - 71
CHAPTER12 TROUBLESHOOTING
*2 In the QCPU, either error stop or continue can be selected for each intelligent function module by the parameters.
12 - 72
Error LED Status Corresponding
Error Contents and Cause Corrective Action
Code CPU Status CPU
[CONTROL-BUS. ERR.]
The FROM/TO instruction is not executable, due to
a control bus error with the intelligent function mod-
ule/special function module. Reset the CPU module and RUN it again. If the
(On error occurring, the program error location is same error is displayed again, the intelligent func-
1412 stored in the individual information.) tion module/special function module, CPU module QCPU
■Collateral information or base unit is faulty. (Contact your local Mitsubishi
• Common Information:Module No. (Slot No.) representative.)
• Individual Information:Program error location
■Diagnostic Timing
• During execution of FROM/TO instruction set
[CONTROL-BUS. ERR.] • Remove the CPU module incompatible with the
In a multiple CPU system, a CPU module incom- multiple CPU system from the main base unit, or
patible with the multiple CPU system is mounted. replace the CPU module incompatible with the
Q00J/Q00/Q01*4
■Collateral information multiple CPU system with a CPU module com-
• Common Information:– patible with the multiple CPU system. Qn(H)*4
• Individual Information:– • The intelligent function module, CPU module or QnPH
■Diagnostic Timing base unit is faulty. (Contact your local Mitsubishi
• Always representative.)
RUN:
1413 [CONTROL-BUS. ERR.] Off
An error is detected on the system bus.
ERR.:
• Self-diagnosis error of the system bus.
Reset the CPU module and RUN it again. If the Flicker
• Self-diagnosis error of the CPU module
same error is displayed again, the intelligent func-
■Collateral information QCPU
tion module, CPU module or base unit is faulty. CPU Status:
• Common Information:–
(Contact your local Mitsubishi representative.) Stop
• Individual Information:–
■Diagnostic Timing
• Always
[CONTROL-BUS. ERR.] • Remove the CPU module incompatible with the
• Fault of a loaded module was detected. multiple CPU system from the main base unit, or
• In a multiple CPU system, a CPU module incom- replace the CPU module with a CPU module
Q00J/Q00/Q01*4
patible with the multiple CPU system is mounted. compatible with the multiple CPU system.
• Reset the CPU module and RUN it again. If the Qn(H)*4
■Collateral information
• Common Information:Module No. (Slot No.) same error is displayed again, the intelligent QnPH
• Individual Information:– function module, CPU module or base unit is QnU
■Diagnostic Timing faulty. (Contact your local Mitsubishi representa-
1414
• Always tive.)
[CONTROL-BUS. ERR.]
An error is detected on the system bus. Q00J/Q00/Q01*4
Reset the CPU module and RUN it again. If the
■Collateral information Qn(H)
same error is displayed again, the intelligent func-
• Common Information:Module No. (Slot No.) QnPH
tion module, CPU module or base unit is faulty.
• Individual Information:– QnPRH
(Contact your local Mitsubishi representative.)
■Diagnostic Timing QnU
• Always
12 - 73
CHAPTER12 TROUBLESHOOTING
12 - 74
Error LED Status Corresponding
Error Contents and Cause Corrective Action
Code CPU Status CPU
[MULTI-C.BUS ERR.] • Take noise reduction measures.
The communication error with other CPU is • Check the main base unit mounting status of the
detected in the Multiple CPU high speed bus. CPU module.
■Collateral information • Reset the CPU module and RUN it again. If the
1431
• Common Information:Module No. (CPU No.) same error is displayed again, the CPU module
• Individual Information:– has hardware failure. (Contact your local Mitsub-
■Diagnostic Timing ishi representative, explaining a detailed descrip-
• At power ON/ At reset tion of the problem.)
[MULTI-C.BUS ERR.]
The communication time out with other CPU is
Reset the CPU module and RUN it again. If the
detected in the Multiple CPU high speed bus.
same error is displayed again, the CPU module has
■Collateral information
1432 hardware failure. (Contact your local Mitsubishi rep-
• Common Information:Module No. (CPU No.)
resentative, explaining a detailed description of the
• Individual Information:–
problem.)
■Diagnostic Timing
• At power ON/ At reset
1433 [MULTI-C.BUS ERR.] • Take noise reduction measures.
1434 The communication error with other CPU is • Check the main base unit mounting status of the
detected in the Multiple CPU high speed bus. CPU module.
■Collateral information • Reset the CPU module and RUN it again. If the
RUN:
• Common Information:Module No. (CPU No.) same error is displayed again, the CPU module
1435 Off
• Individual Information:– has hardware failure. (Contact your local Mitsub-
ERR.:
■Diagnostic Timing ishi representative, explaining a detailed descrip-
• Always tion of the problem.)
Flicker QnU*10
*10 The Universal model QCPU except the Q00UJCPU, Q00UCPU, Q01UCPU, and Q02UCPU.
12 - 75
CHAPTER12 TROUBLESHOOTING
12 - 76
12.3.4 Error code list (2000 to 2999)
The following shows the error messages from the error code 2000 to 2999, the contents and
causes of the errors, and the corrective actions for the errors.
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[UNIT VERIFY ERR.]
In a multiple CPU system, a CPU module incom-
patible with the multiple CPU system is mounted.
■Collateral information
Replace the CPU module incompatible with the
• Common Information:Module No. (Slot No.) Qn(H)*3
multiple CPU system with a CPU module compati-
[For Remote I/O network] QnPH
ble with the multiple CPU system.
Network No./Station No.
• Individual Information:–
■Diagnostic Timing
• When an END instruction executed
[UNIT VERIFY ERR.]
The I/O module status is different from the I/O mod-
ule information at power ON.
Read the error common information at the GX
• I/O module (or intelligent function module) is not RUN:
Developer, and check and/or change the module
installed properly or installed on the base unit. Off/On
that corresponds to the numerical value (module
■Collateral information ERR.:
number) there. Q00J/Q00/Q01
• Common Information:Module No. (Slot No.) Flicker/On
2000 Alternatively, monitor special registers SD150 to
[For Remote I/O network]
SD157 using GX Developer, and check and replace
Network No./Station No. CPU Status:
the module where the bit of its data is "1".
• Individual Information:– Stop/
■Diagnostic Timing Continue*1
• When an END instruction executed
[UNIT VERIFY ERR.] • Read the common information of the error using
I/O module information power ON is changed. the peripheral device, and check and/or change
• I/O module (or intelligent function module/special the module that corresponds to the numerical
function module) not installed properly or value (module number) there.
installed on the base unit. • Alternatively, monitor the special registers Qn(H)
■Collateral information SD1400 to SD1431 at a peripheral device, and QnPH
• Common Information:Module No. (Slot No.) change the fuse at the output module whose bit QnPRH
[For Remote I/O network] has a value of "1". QnU
Network No./Station No. • When a GOT is bus-connected to the main base
• Individual Information:– unit or extension base unit, check the connection
■Diagnostic Timing status of the extension cable and the grounding
• When an END instruction executed status of the GOT.
[UNIT VERIFY ERR.] RUN:
During operation, a module was mounted on the
Off/On
slot where the empty setting of the CPU module
ERR.:
was made. During operation, do not mount a module on the
Flicker/On Q00J/Q00/Q01*3
2001 ■Collateral information slot where the empty setting of the CPU module
QnU
• Common Information:Module No. (CPU No.) was made.
CPU Status:
• Individual Information:–
Stop/
■Diagnostic Timing
• When an END instruction executed Continue*2
*1 CPU operation can be set in the parameters at error occurrence. (LED indication varies.)
*2 Either error stop or continue can be selected for each module by the parameters.
*3 The function version is B or later.
12 - 77
CHAPTER12 TROUBLESHOOTING
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[BASE LAY ERROR]
The QA1S6 B, QA6 B, or
QA6ADP+A5 B/A6 B was used as the base unit. Q00J/Q00/Q01*3
Do not use the QA1S6 B, QA6 B, or QnPH
2011 ■Collateral information
• Common Information:Base No. QA6ADP+A5 B/A6 B as the base unit. QnPRH
• Individual Information:– QnU
■Diagnostic Timing
• At power ON/At reset
[BASE LAY ERROR]
The GOT is bus-connected to the main base unit of
the redundant system.
The following errors are detected in the CPU 12
redundant system compatible with the extension
base unit.
• The base unit other than the Q6 WRB is con- • Remove a bus connection cable for GOT con-
nected to the extension stage No.1. nection connected to the main base unit.
• The base unit is connected to any one of the • Use the Q6 WRB (fixed to the extension stage
extension stages No.2 to No.7, although the No.1)
Q6 WRB does not exist in the extension stage • Use the CPU module compatible with the exten-
No.1 . sion base unit for the other system.
2012 • The other system CPU module is incompatible • Do not use the Q5 B, QA1S6 B, QA6 B or
with the extension base unit. QA6ADP+A5 B/A6 B for the base unit.
• The Q5 B, QA1S6 B, QA6 B or • Use the main base unit which has the same num-
QA6ADP+A5 B/A6 B is connected. ber of slots.
• The number of slots of the main base unit for • Hardware failure of the Q6 WRB. (Contact your QnPRH*6
RUN:
both systems is different. local Mitsubishi representative, explaining a
Off
Information of the Q6 WRB cannot be read cor- detailed description of the problem.)
ERR.:
rectly. Flicker
■Collateral information
• Common Information:Base No.
CPU Status:
• Individual Information:–
Stop
■Diagnostic Timing
• At power ON/At reset
12 - 78
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[SP. UNIT LAY ERR.]
The slot to which the QI60 is mounted is set to
other than Inteli (intelligent function module) or
Interrupt (interrupt module) in the I/O assignment of
Qn(H)*3
PLC parameter. Make setting again to match the PLC parameter I/O
QnPH
■Collateral information assignment with the actual loading status.
QnPRH
• Common Information:Module No. (Slot No.)
• Individual Information:–
■Diagnostic Timing
• At power ON/At reset
[SP. UNIT LAY ERR.]
• In the I/O assignment setting of PLC parameter,
Inteli (intelligent function module) was allocated
to an I/O module or vice versa.
• In the I/O assignment setting of PLC parameter,
a module other than CPU (or nothing) was allo-
cated to the location of a CPU module or vice
versa. • Make the PLC parameter’s I/O assignment set-
• In the I/O assignment setting of the PLC parame- ting again so it is consistent with the actual status Qn(H)
ter, switch setting was made to the module that of the intelligent function module and the CPU QnPH
has no switch setting. module. QnPRH
• In the I/O assignment setting of the PLC parame- • Delete the switch setting in the I/O assignment QnU
ter dialog box, the number of points assigned to setting of the PLC parameter.
2100 the intelligent function module is less than the
number of points of the mounted module.
RUN:
■Collateral information
Off
• Common Information:Module No. (Slot No.)
ERR.:
• Individual Information:–
Flicker
■Diagnostic Timing
• At power ON/At reset
CPU Status:
[SP. UNIT LAY ERR.]
Stop
• In the parameter I/O allocation settings, an Inteli
(intelligent function module) was allocated to a
location reserved for an I/O module or vice versa.
• In the parameter I/O allocation settings, a module
other than CPU (or nothing) was allocated to a
location reserved for a CPU module or vice
versa. Reset the parameter I/O allocation setting to con-
• In the I/O assignment setting of the PLC parame- form to the actual status of the intelligent function Q00J/Q00/Q01
ter dialog box, the number of points assigned to module and the CPU module.
the intelligent function module is less than the
number of points of the mounted module.
■Collateral information
• Common Information:Module No. (Slot No.)
• Individual Information:–
■Diagnostic Timing
• At power ON/At reset
[SP. UNIT LAY ERR.]
13 or more A-series special function modules
(except for the A1SI61) that can initiate an interrupt
to the CPU module have been installed. Reduce the A series special function modules
2101 ■Collateral information (except the A1SI61) that can make an interrupt Qn(H)
• Common Information:Module No. (Slot No.) start to the CPU module to 12 or less.
• Individual Information:–
■Diagnostic Timing
• At power ON/At reset
12 - 79
CHAPTER12 TROUBLESHOOTING
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[SP. UNIT LAY ERR.]
Seven or more A1SD51S have been installed.
■Collateral information
2102 • Common Information:Module No. (Slot No.) Keep the number of A1SD51S to six or fewer. Qn(H)
• Individual Information:–
■Diagnostic Timing
• At power ON/At reset
[SP. UNIT LAY ERR.] • Reduce the number of QI60/A1SI61 modules
• Two or more QI60/A1SI61 modules are mounted
mounted in the single CPU system to one.
in a single CPU system.
• Change the number of QI60/A1SI61 modules set
• Two or more QI60/A1SI61 modules are set to the
to the same control CPU to only one in the multi-
same control CPU in a multiple CPU system.
• Two or more A1SI61 modules are loaded in a
ple CPU system.
• Reduce the number of A1SI61 modules to only
Qn(H)*3 12
multiple CPU system. QnPH
one in the multiple CPU system. When using an
■Collateral information
interrupt module with each QCPU in a multiple
• Common Information:Module No. (Slot No.)
CPU system, replace it with the QI60. (Use one
• Individual Information:–
A1SI61 module + max. three QI60 modules or
■Diagnostic Timing
only the QI60 modules.) RUN:
• At power ON/At reset
Off
[SP. UNIT LAY ERR.] ERR.:
Two or more QI60, A1SI61 interrupt modules have
Flicker
been mounted.
■Collateral information Qn(H)
Install only 1 QI60, A1SI61 module. CPU Status:
• Common Information:Module No. (Slot No.) QnPRH
Stop
2103 • Individual Information:–
■Diagnostic Timing
• At power ON/At reset
[SP. UNIT LAY ERR.]
Two or more QI60 modules are mounted.
■Collateral information
• Common Information:Module No. (Slot No.) Reduce the QI60 modules to one. Q00J/Q00/Q01*5
• Individual Information:–
■Diagnostic Timing
• At power ON/At reset
[SP. UNIT LAY ERR.]
12 - 80
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[SP.UNIT LAY ERR.]
• Two or more MELSECNET/H modules are
mounted.
• Reduce the number of MELSECNET/H modules
• Two or more CC-Link IE controller network mod-
ules are mounted. to one.
• Two or more Ethernet modules are mounted. • Reduce the number of CC-Link IE controller net- Q00UJ
■Collateral information work modules to one.
• Common Information:Module No.
• Reduce the number of Ethernet modules to one.
• Individual Information:–
■Diagnostic Timing
• At power ON/At reset
[SP.UNIT LAY ERR.]
• Five or more MELSECNET/H and CC-Link IE
controller network modules in total are mounted • Reduce the number of MELSECNET/H and CC-
in the entire system. Link IE controller network modules to four or less
• Two or more MELSECNET/H modules are
in total in the entire system.
mounted in the entire system.
• Two or more CC-Link IE controller network mod- • Reduce the number of MELSECNET/H modules
ules are mounted in the entire system. to one in the entire system. Q00U/Q01U
• Two or more Ethernet modules are mounted in • Reduce the number of CC-Link IE controller net-
the entire system.
work modules to one in the entire system.
■Collateral information
• Common Information:Module No. • Reduce the number of Ethernet modules to one
• Individual Information:– in the entire system.
■Diagnostic Timing
• At power ON/At reset
[SP.UNIT LAY ERR.]
• Three or more MELSECNET/H and CC-Link IE
controller network modules in total are mounted RUN:
in the entire system. • Reduce the MELSECNET/H and CC-Link IE con- Off
• Three or more Ethernet interface modules are troller network modules up to two or less in the ERR.:
2106 mounted in the entire system. entire system. Flicker Q02U
■Collateral information • Reduce the Ethernet interface modules up to two
• Common Information:Module No. or less in the entire system. CPU Status:
• Individual Information:– Stop
■Diagnostic Timing
• At power ON/At reset
[SP.UNIT LAY ERR.]
• Five or more MELSECNET/H and CC-Link IE
controller network modules in total are mounted
in the entire system. • Reduce the MELSECNET/H and CC-Link IE con-
• Five or more Ethernet interface modules are troller network modules up to four or less in the
mounted in the entire system. entire system. QnU*7
■Collateral information • Reduce the Ethernet interface modules up to four
• Common Information:Module No. or less in the entire system.
• Individual Information:–
■Diagnostic Timing
• At power ON/At reset
[SP.UNIT LAY ERR.]
• Three or more CC-Link IE controller network
modules are mounted in the entire system.
• Five or more MELSECNET/H and CC-Link IE • Reduce the CC-Link IE controller network mod-
controller network modules in total are mounted ules up to two or less in the entire system. Qn(H)*6
in the entire system. • Reduce the total number of the MELSECNET/H QnPH*9
■Collateral information and CC-Link IE controller network modules up to QnPRH*9
• Common Information:Module No. four or less in the entire system.
• Individual Information:–
■Diagnostic Timing
• At power ON/At reset
12 - 81
CHAPTER12 TROUBLESHOOTING
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[SP. UNIT LAY ERR.]
• Five or more MELSECNET/H modules have
been installed.
• Five or more Ethernet interface modules have • Reduce the number of MELSECNET/H modules
Qn(H)
been installed. to four or less.
QnPH
■Collateral information • Reduce the number of Ethernet modules to four
QnPRH
• Common Information:Module No. (Slot No.) or less.
• Individual Information:–
■Diagnostic Timing
• At power ON/At reset
[SP. UNIT LAY ERR.]
• Two or more MELSECNET/H modules were
installed. 12
• Two or more Ethernet modules were installed. • Reduce the MELSECNET/H modules to one or
2106 • Three or more CC-Link modules were installed. less.
Q00J/Q00/Q01
■Collateral information • Reduce the Ethernet modules to one or less.
• Common Information:Module No. (Slot No.) • Reduce the CC-Link modules to two or less.
• Individual Information:–
■Diagnostic Timing
• At power ON/At reset
[SP. UNIT LAY ERR.]
• The same network number or same station num-
RUN:
ber is duplicated in the MELSECNET/H network
Off Q00J/Q00/Q01
system.
ERR.: Qn(H)
■Collateral information • Check the network number and station number.
Flicker QnPH
• Common Information:Module No. (Slot No.)
QnPRH
• Individual Information:–
CPU Status:
■Diagnostic Timing
Stop
• At power ON/At reset
[SP. UNIT LAY ERR.]
The start X/Y set in the PLC parameter’s I/O
assignment settings is overlapped with the one for
Make the PLC parameter’s I/O assignment setting
another module.
again so it is consistent with the actual status of the
2107 ■Collateral information QCPU
intelligent function module/special function mod-
• Common Information:Module No. (Slot No.)
12 - 82
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[SP. UNIT ERROR]
• The location designated by the FROM/TO
instruction set is not the intelligent function mod-
ule/special function module.
• The module that does not include buffer memory
has been specified by the FROM/TO instruction.
• The intelligent function module/special function Q00J/Q00/Q01
module, Network module being accessed is Qn(H)*3
2110 faulty. QnPH
• Station not loaded was specified using the • Read the individual information of the error using QnPRH
instruction whose target was the CPU share the GX Developer, check the FROM/TO instruc- QnU
memory. tion that corresponds to that numerical value
■Collateral information (program error location), and correct when nec-
• Common Information:Module No. (Slot No.) essary.
• Individual Information:Program error location • The intelligent function module/special function
■Diagnostic Timing module that was accessed is experiencing a
• When instruction executed hardware fault. Therefore, change the faulty
[SP. UNIT ERROR] module. Alternatively, contact your local Mitsub-
• The location designated by a link direct device ishi representative.
(J \ ) is not a network module.
• The I/O module (intelligent function module/spe-
cial function module) was nearly removed, com-
RUN:
2111 pletely removed, or mounted during running.
Off/On
■Collateral information
ERR.:
• Common Information:Module No. (Slot No.)
Flicker/On
• Individual Information:Program error location
■Diagnostic Timing
CPU Status:
• When instruction executed
Stop/
[SP. UNIT ERROR]
• The module other than intelligent function mod- Continue*1
QCPU
ule/special function module is specified by the
intelligent function module/special function mod-
ule dedicated instruction.
Or, it is not the corresponding intelligent function
module/special function module.
2112 • There is no network No. specified by the network
dedicated instruction.
Or the relay target network does not exit. Read the individual information of the error using a
■Collateral information peripheral device, and check the special function
• Common Information:Module No. (Slot No.) module /special function module dedicated instruc-
• Individual Information:Program error location tion (network instruction) that corresponds to the
■Diagnostic Timing value (program error part) to make modification.
• When instruction executed/STOP RUN
[SP. UNIT ERROR]
The module other than network module is specified
bythe network dedicated instruction.
■Collateral information Qn(H)
2113 • Common Information:FFFFH (fixed) QnPH
• Individual Information:Program error location
■Diagnostic Timing
• When instruction executed/STOP RUN
*1 CPU operation can be set in the parameters at error occurrence. (LED indication varies.)
*3 The function version is B or later.
12 - 83
CHAPTER12 TROUBLESHOOTING
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[SP. UNIT ERROR]
An instruction, which on execution specifies other
stations, has been used for specifying the host
CPU. (An instruction that does not allow the host Q00J/Q00/Q01*3
CPU to be specified). Qn(H)*3
2114
■Collateral information QnPH
• Common Information:Module No. (Slot No.)
QnU
• Individual Information:Program error location
■Diagnostic Timing
• When instruction executed/ STOP RUN
[SP. UNIT ERROR]
An instruction, which on execution specifies the
host CPU, has been used for specifying other
12
CPUs. (An instruction that does not allow other sta-
Q00J/Q00/Q01*3
tions to be specified).
2115 Qn(H)*3
■Collateral information
• Common Information:Module No. (Slot No.) QnPH
• Individual Information:Program error location
■Diagnostic Timing Read the individual information of the error using
• When instruction executed/ STOP RUN the GX Developer, check the program correspond-
[SP. UNIT ERROR] ing that value (program error location), and make
• An instruction that does not allow the under the correction.
control of another CPU to be specified is being RUN:
used for a similar task. Off/On
• Instruction was executed for the A or QnA mod- ERR.:
2116 ule under control of another CPU. Flicker/On
■Collateral information
• Common Information:Module No. (Slot No.) CPU Status:
Q00J/Q00/
• Individual Information:Program error location Stop/Continue
■Diagnostic Timing Q01*3
• When instruction executed/ STOP RUN Qn(H)*3
QnPH
[SP. UNIT ERROR]
A CPU module that cannot be specified in the QnU
instruction dedicated to the multiple CPU system
12 - 84
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[SP. UNIT LAY ERR.]
The locations of the Q5 B/Q6 B, QA1S6 B/
QA6 B, and QA6ADP+A5 B/A6 B are
improper. Q00J/Q00/Q01*4
2120 Check the location of the base unit. Qn(H)
■Collateral information
• Common Information:– QnPH
• Individual Information:–
■Diagnostic Timing
• At power ON/At reset
[SP. UNIT LAY ERR.]
The CPU module is installed to other than the CPU
slot and slots 0 to 2.
■Collateral information Check the loading position of the CPU module and Qn(H)
2121
• Common Information:– reinstall it at the correct slot. QnPH
• Individual Information:–
■Diagnostic Timing
• At power ON/At reset
[SP. UNIT LAY ERR.]
The QA1S6 B/QA6 B and QA6ADP+A5 B/
A6 B are used for the main base unit. Qn(H)
2122 ■Collateral information Replace the main base unit with a usable one. QnPH
• Common Information:– QnPRH
• Individual Information:–
■Diagnostic Timing
• At power ON/At reset
RUN:
[SP. UNIT LAY ERR.] Off
• A module is mounted on the 65th slot or later ERR.:
slot. Flicker
• Remove the module mounted on the 65th slot or
• A module is mounted on the slot whose number
later slot.
is greater than the number of slots specified at
• Remove the module mounted on the slot whose CPU Status:
[Slots] in [Standard setting] of the base setting. Stop
number is greater than the number of slots spec- Qn(H)
• A module is mounted on the slot whose number
ified at [Slots] in [Standard setting] of the base QnPH
of I/O points exceeds 4096 points.
setting. QnPRH
• A module is mounted on the slot whose number
• Remove the module mounted on the slot whose QnU*7
of I/O points strides 4096 points.
number of I/O points exceeds 4096 points.
■Collateral information
• Replace the module with the one whose number
• Common Information:–
of occupied points does not exceed 4096 points.
• Individual Information:–
■Diagnostic Timing
• At power ON/At reset
2124 [SP. UNIT LAY ERR.]
• A module is mounted on after the 25th slot (on
after the 17th slot for the Q00UJ).
• Remove the module mounted on after the 25th
• A module is mounted on the slot whose number
is later than the one set in the "Base setting" on (on after the 17th slot for the Q00UJ).
the I/O assignment tab of PLC parameter in GX • Remove the module mounted on the slot whose
Developer. number is later than the one set in the "Base set-
• A module is mounted on the slot for which I/O ting" on the I/O assignment tab of PLC parameter
points greater than 1024 (greater than 256 for
in GX Developer. Q00UJ
the Q00UJ) is assigned.
• Remove the module mounted on the slot for Q00U/Q01U
• A module is mounted on the slot for which I/O
points is assigned from less than 1024 to greater which I/O points greater than 1024 (greater than
than 1024 (from less than 256 to greater than 256 for the Q00UJ) is assigned.
256 for the Q00UJ). • Replace the end module with the one whose
■Collateral information number of occupied points is within 1024 (within
• Common Information:–
256 for the Q00UJ).
• Individual Information:–
■Diagnostic Timing
• At power ON/At reset
12 - 85
CHAPTER12 TROUBLESHOOTING
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[SP. UNIT LAY ERR.]
• A module is mounted on the 37th slot or later
slot. • Remove the module mounted on the 37th slot or
• A module is mounted on the slot whose number later slot.
is greater than the number of slots specified at • Remove the module mounted on the slot whose
[Slots] in [Standard setting] of the base setting. number is greater than the number of slots spec-
• A module is mounted on the slot whose number ified at [Slots] in [Standard setting] of the base
of I/O points exceeds 2048 points. Q02U
setting.
• A module is mounted on the slot whose number
of I/O points strides 2048 points. • Remove the module mounted on the slot whose
■Collateral information number of I/O points exceeds 2048 points.
• Common Information:– • Replace the module with the one whose number
• Individual Information:– of occupied points does not exceed 2048 points.
■Diagnostic Timing
• At power ON/At reset
12
[SP. UNIT LAY ERR.]
• A module is mounted on the 25th slot or later
slot. (The 17th slot or later slot for the Q00J.) • Remove the module mounted on the 25th slot or
• A module is mounted on the slot whose number later slot. (The 17th slot or later slot for the
is greater than the number of slots specified at Q00J.)
[Slots] in [Standard setting] of the base setting. • Remove the module mounted on the slot whose
2124
• A module is mounted on the slot whose number number is greater than the number of slots spec-
of I/O points exceeds 1024 points. (256 points for ified at [Slots] in [Standard setting] of the base RUN:
the Q00J.) setting. Off Q00J/Q00/Q01
• A module is mounted on the slot whose number • Remove the module mounted on the slot whose ERR.:
of I/O points strides 1024 points. (256 points for number of I/O points exceeds 1024 points. (256 Flicker
the Q00J.) points for the Q00J.)
■Collateral information • Replace the module with the one whose number CPU Status:
• Common Information:– of occupied points does not exceed 1024 points. Stop
• Individual Information:– (256 points for the Q00J.)
■Diagnostic Timing
• At power ON/At reset
[SP. UNIT LAY ERR.]
5 or more extension base units were added. (3
bases for Q00J)
■Collateral information Remove 5 or more extension base units. (3 bases
Q00J/Q00/Q01*4
12 - 86
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[SP. UNIT LAY. ERR.]
CPU module locations in a multiple CPU system
are either of the following. • Mount modules on the available slots so that the
• There are empty slots between the QCPU and empty slots will be located on the right-hand side
QCPU/motion controller. of the CPU module.
• A module other than the High Performance • Remove the module mounted on the left-hand
model QCPU/Process CPU (including the motion side of the High Performance model QCPU/Pro- Qn(H)*3
2126
controller) is mounted on the left-hand side of the cess CPU, and mount the High Performance QnPH
High Performance model QCPU/Process CPU. model QCPU/Process CPU on the empty slot.
■Collateral information Mount the motion CPU on the right-hand side of
• Common Information:Module No. (Slot No.) the High Performance model QCPU/Process
• Individual Information:– CPU.
■Diagnostic Timing
• At power ON/ At reset
[SP.UNIT LAY ERR.]
The unusable module is mounted on the extension
base unit in the redundant system.
■Collateral information • Remove the unusable module from the extension
2128 QnPRH*6
• Common Information:Module No. base unit.
• Individual Information:– RUN:
■Diagnostic Timing Off
• At power-ON/ At reset ERR.:
[SP. UNIT VER. ERR.] Flicker
In a multiple CPU system, the control CPU of the
intelligent function module incompatible with the • Change the intelligent function module for the CPU Status:
multiple CPU system is set to other than CPU No.1. one compatible with the multiple CPU system Stop Q00J/Q00/Q01
■Collateral information (function version B).
2150 QnPH
• Common Information:Module No. (Slot No.) • Change the setting of the control CPU of the
QuU*10
• Individual Information:– intelligent function module incompatible with the
■Diagnostic Timing multiple CPU system to CPU No.1.
• At power ON/At reset/
At writing to progurammable controller
[SP. UNIT VER. ERR.]
Either of the following modules incompatible with
the redundant system has been mounted in a
redundant system.
• CC-Link IE controller network modules Use either of the following modules compatible with
• MELSECNET/H modules the redundant system.
2151 • Ethernet modules • CC-Link IE controller network modules QnPRH
■Collateral information • MELSECNET/H modules
• Common Information:Module No. (Slot No.) • Ethernet modules
• Individual Information:–
■Diagnostic Timing
• At power ON/At reset/
At writing to progurammable controller
12 - 87
CHAPTER12 TROUBLESHOOTING
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[MISSING PARA.]
There is no parameter file in the drive specified as
valid parameter drive by the DIP switches. • Check and correct the valid parameter drive set-
Qn(H)
■Collateral information tings made by the DIP switches.
• Common Information:Drive Name QnPH
• Set the parameter file to the drive specified as
• Individual Information:– QnPRH
valid parameter drive by the DIP switches.
■Diagnostic Timing
• At power ON/At reset/ STOP RUN
[MISSING PARA.]
There is no parameter file at the program memory.
■Collateral information
2200 • Common Information:Drive Name
• Individual Information:–
Set the parameter file to the program memory. Q00J/Q00/Q01 12
■Diagnostic Timing
• At power ON/At reset/ STOP RUN
[MISSING PARA.]
Parameter file does not exist in all drives where
parameters will be valid.
■Collateral information
• Common Information:Drive Name Set a parameter file in a drive to be valid. QuU
• Individual Information:–
■Diagnostic Timing
• At power ON/At reset/ STOP RUN RUN:
Off
[BOOT ERROR]
ERR.:
The contents of the boot file are incorrect. Q00J/Q00/Q01*3
Flicker
■Collateral information Qn(H)
2210 • Common Information:Drive name Check the boot setting. QnPH
• Individual Information:– CPU Status:
QnPRH
■Diagnostic Timing Stop
QnU
• At power ON/ At reset
[BOOT ERROR]
File formatting is failed at a boot.
• Reboot.
■Collateral information Qn(H)
• CPU module hardware fault. (Contact your local
2211 • Common Information:Drive name QnPRH
Mitsubishi representative, explaining a detailed
12 - 88
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[RESTORE ERROR]
• The device information backuped by the device
data backup function is incomplete. (Turning
power supply OFF or reset is suspected.)
Do not return the data when this error occurs. Also,
delete the incomplete device information at the time
2221 Reset the CPU module and run it again.
of this error occurrence.
■Collateral information
• Common Information:File name/ Drive name
• Individual Information:–
■Diagnostic Timing
• At power ON/ At reset
[RESTORE ERROR]
The model name of the restoration destination CPU
module is different from the one of the backup
source CPU module.
Execute a restore for the CPU module whose name
2225 ■Collateral information
is same as the backup source CPU module.
• Common Information:–
• Individual Information:– RUN:
■Diagnostic Timing Off
• At power ON/ At reset ERR.:
[RESTORE ERROR] Flicker QnU
• ·The backup data file is destroyed. (The content
of the file is different from the check code. CPU Status:
• Reading the backup data from the memory card Stop
is not successfully completed.
• Since the write protect switch of the SRAM card • Execute a restore of other backup data because
is set to on (write inhibited), the checked the backup data may be destructed.
2226
"Restore for the first time only" setting cannot be • Set the write protect switch of the SRAM card to
performed. off (write enabled).
■Collateral information
• Common Information:–
• Individual Information:–
■Diagnostic Timing
• At power ON/ At reset
[RESTORE ERROR]
Writing the backup data to the restoration destina-
tion drive is not successfully completed.
■Collateral information Execute a restore for the other CPU module too
2227
• Common Information:File name/Drive name because the CPU module may be damaged.
• Individual Information:–
■Diagnostic Timing
• At power ON/ At reset
[ICM. OPE. ERROR]
• A memory card was removed without switching RUN:
the memory card in/out switch OFF. Off/On
• The memory card in/out switch is turned ON • Remove memory card after placing the memory ERR.: Qn(H)
although a memory card is not actually installed. card in/out switch OFF. Flicker/On QnPH
2300
■Collateral information • Turn on the card insert switch after inserting a QnPRH
• Common Information:Drive name memory card. CPU Status: QnU*11
• Individual Information:– Stop/
■Diagnostic Timing Continue*1
• When memory card is inserted or removed
*1 CPU operation can be set in the parameters at error occurrence. (LED indication varies.)
*11 The Universal model QCPU except the Q00UJCPU, Q00UCPU, and Q01UCPU.
12 - 89
CHAPTER12 TROUBLESHOOTING
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[ICM. OPE. ERROR]
• The memory card has not been formatted.
• Memory card format status is incorrect.
• The QCPU file does not exist in the Flash card. Qn(H)
• Format memory card.
■Collateral information QnPH
• Reformat memory card.
• Common Information:Drive name QnPRH
• Write the QCPU file the Flash card
• Individual Information:– QnU*11
■Diagnostic Timing
• When memory card is inserted or removed/When
memory card is inserted
2301 [ICM. OPE. ERROR] RUN:
SRAM card failure is detected. (It occurs when
automatic format is not set.)
Off/On
ERR.:
12
Writing parameters was performed duruing setting Flicker/On
Format SRAM card after changing battery of SRAM
file registers.
card.
■Collateral information
CPU Status: QnU*11
Write a parameter, which set the file register at "Not
• Common Information:Drive name
available", in CPU, and then perform the ioperation. Stop/
• Individual Information:–
Continue*1
■Diagnostic Timing
• When memory card is inserted or removed/When
memory card is inserted
[ICM. OPE. ERROR]
A memory card that cannot be used with the CPU
module has been installed. Qn(H)
• Format memory card.
■Collateral information QnPH
2302 • Reformat memory card.
• Common Information:Drive name QnPRH
• Check memory card.
• Individual Information:– QnU*11
■Diagnostic Timing
• When memory card is inserted or removed
[FILE SET ERROR]
Automatic write to standard ROM was performed
on the CPU module that is incompatible with auto-
• Execute automatic write to standard ROM on the
matic write to standard ROM.
CPU module which is compatible with automatic
(Memory card where automatic write to standard
write to standard ROM.
ROM was selected in the boot file was fitted and
*1 CPU operation can be set in the parameters at error occurrence. (LED indication varies.)
*3 The function version is B or later.
*11 The Universal model QCPU except the Q00UJCPU, Q00UCPU, and Q01UCPU.
12 - 90
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[FILE SET ERROR]
Program memory capacity was exceeded by per-
forming boot operation or automatic write to stan-
dard ROM.
Qn(H)*3
■Collateral information
• Common Information:File name/ Drive name QnPH
QnPRH
• Individual Information:Parameter number
■Diagnostic Timing • Check and correct the parameters (boot setting).
• At power ON/At reset/ • Delete unnecessary files in the program memory.
At writing to progurammable controller • Choose "Clear program memory" for boot in the
[FILE SET ERROR] parameter so that boot is started after the pro-
Program memory capacity was exceeded by per- gram memory is cleared.
forming boot operation.
■Collateral information
• Common Information:File name/ Drive name QnU
• Individual Information:Parameter number
■Diagnostic Timing
• At power ON/At reset/
At writing to progurammable controller
[FILE SET ERROR] RUN:
The file specified by parameters cannot be made. • Read the individual information of the error using Off
■Collateral information the peripheral device, check to be sure that the ERR.:
2401 • Common Information:File name/ Drive name parameter drive name and file name correspond Flicker
QCPU
• Individual Information:Parameter number to the numerical values there (parameter num-
■Diagnostic Timing ber), and correct. CPU Status:
• At power ON/At reset/ At writing to proguramma- • Check the space remaining in the memory card. Stop
ble controller
[FILE SET ERROR]
• Although setting is made to use the device data
storage file, there is no empty capacity required
for creating the device data storage file in the
standard ROM.
• When the latch data backup function (to standard
ROM) is used, there is no empty capacity
required for storing backup data in standard
ROM. (The parameter number "FFFFH" is dis-
Secure the empty capacity of the standard ROM. QnU
played for the error individual information.)
• Standard RAM capacity is insufficient that error
history of the module cannot be stored.
■Collateral information
• Common Information:File name/ Drive name
• Individual Information:Parameter number
■Diagnostic Timing
• At power ON/At reset/ At writing to proguramma-
ble controller
[FILE OPE. ERROR]
• The specified program does not exist in the pro-
• Read the individual information of the error using
gram memory. RUN:
the peripheral device, check to be sure that the
This error may occur when the ECALL, EFCALL, Off/On
program corresponds to the numerical values
PSTOP, PSCAN, POFF or PLOW instruction is ERR.: Qn(H)
there (program location), and correct.
executed. Flicker/On QnPH
2410 Create a file created using parameters, and load
• The specified file does not exist. QnPRH
it to the CPU module.
■Collateral information CPU Status: QnU
• In case a specified file does not exist, write the
• Common Information:File name/ Drive name Stop/
file to a target memory and/or check the file spec-
• Individual Information:Program error location Continue*1
ified with the instruction again.
■Diagnostic Timing
• When instruction executed
*1 CPU operation can be set in the parameters at error occurrence. (LED indication varies.)
*3 The function version is B or later.
12 - 91
CHAPTER12 TROUBLESHOOTING
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[FILE OPE. ERROR]
• The file is the one which cannot be specified by
the sequence program (such as comment file).
• The specified program exists in the program
memory, but has not been registered in the pro-
Read the individual information of the error using Qn(H)
gram setting of the Parameter dialog box.
the peripheral device, check to be sure that the pro- QnPH
2411 This error may occur when the ECALL, EFCALL,
gram corresponds to the numerical values there QnPRH
PSTOP, PSCAN or POFF instruction is executed.
(program location), and correct. QnU
■Collateral information
• Common Information:File name/ Drive name
• Individual Information:Program error location RUN:
■Diagnostic Timing
• When instruction executed
Off/On
ERR.:
12
[FILE OPE. ERROR] Flicker/On
The SFC program file is one that cannot be desig-
nated by the sequence program. Read the individual information of the error using Qn(H)
CPU Status:
■Collateral information the peripheral device, check to be sure that the pro- QnPH
2412 Stop/
• Common Information:File name/ Drive name gram corresponds to the numerical values there QnPRH
Continue*1
• Individual Information:Program error location (program location), and correct. QnU
■Diagnostic Timing
• When instruction executed
[FILE OPE. ERROR]
No data has been written to the file designated by Read the individual information of the error using
the sequence program. the peripheral device, check to be sure that the pro-
Qn(H)
■Collateral information gram corresponds to the numerical values there
2413 QnPH
• Common Information:File name/ Drive name (program location), and correct.
QnPRH
• Individual Information:Program error location Check to ensure that the designated file has not
■Diagnostic Timing been write protected.
• When instruction executed
[CAN'T EXE. PRG.]
• There is a program file that uses a device that is • Read the common information of the error using
out of the range set in the PLC parameter device the peripheral device, check to be sure that the
setting. parameter device allocation setting and the pro-
• After the PLC parameter setting is changed, only gram file device allocation correspond to the
the parameter is written into the PLC. numerical values there (file name), and correct if QCPU
*1 CPU operation can be set in the parameters at error occurrence. (LED indication varies.)
12 - 92
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[CAN'T EXE. PRG.]
There are multiple program files although "none"
has been set at the PLC parameter program set-
Qn(H)
tings.
Edit the PLC parameter program setting to "yes". QnPH
■Collateral information
• Common Information:File name/ Drive name Alternatively, delete unneeded programs. QnPRH
• Individual Information:– QnU
■Diagnostic Timing
• At power ON/At reset/ STOP RUN
2501
[CAN'T EXE. PRG.]
• There are three or more program files.
• The program name differs from the program con-
tents. • Delete unnecessary program files.
■Collateral information • Match the program name with the program con- Q00J/Q00/Q01
• Common Information:File name/ Drive name tents.
• Individual Information:–
■Diagnostic Timing
• At power ON/At reset/ STOP RUN
[CAN'T EXE. PRG.]
The program file is incorrect.
Alternatively, the file contents are not those of a
sequence program. Check whether the program version
■Collateral information is .QPG, and check the file contents to be QCPU
• Common Information:File name/ Drive name
sure they are for a sequence program.
• Individual Information:–
■Diagnostic Timing
RUN:
2502 • At power ON/At reset/ STOP RUN Off
[CAN'T EXE. PRG.] ERR.:
The program file is not the one for the redundant Flicker
CPU. Create a program using GX Developer or PX
■Collateral information Developer for which the PLC type has been set to CPU Status:
• Common Information:File name/ Drive name QnPRH
the redundant CPU (Q12PRH/Q25PRH), and write Stop
• Individual Information:– it to the CPU module.
■Diagnostic Timing
• At power ON/At reset/ STOP RUN
[CAN'T EXE. PRG.]
There are no program files at all.
■Collateral information
2503 • Common Information:File name/ Drive name QCPU
• Individual Information:–
■Diagnostic Timing
• At power ON/At reset/ STOP RUN
• Check program configuration.
[CAN'T EXE. PRG.]
• Check parameters and program configuration.
Two or more SFC normal programs or control pro-
grams have been designated. Qn(H)
■Collateral information QnPH
• Common Information:File name/ Drive name QnPRH
• Individual Information:– QnU
■Diagnostic Timing
2504 • At power ON/At reset/ STOP RUN
[CAN'T EXE. PRG.]
There are two or more SFC programs.
■Collateral information
• Common Information:File name/ Drive name Reduce the SFC programs to one. Q00J/Q00/Q01*3
• Individual Information:–
■Diagnostic Timing
• At power ON/At reset/ STOP RUN
12 - 93
CHAPTER12 TROUBLESHOOTING
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
Check for illegal accesses. If any illegal access is
identified, take actions such as disabling communi-
[REMOTE PASS.FAIL] cation of the connection.
RUN:
The count of remote password mismatches If no illegal access is identified, clear the error and
ON
reached the upper limit. perform the following. (Clearing the error also
ERR.:
■Collateral information clears the count of remote password mismatches.)
2700 ON
• Common Information:– • Check if the remote password sent is correct.
• Individual Information:– • Check if the remote password has been locked.
CPU Status:
■Diagnostic Timing • Check if concurrent access was made from multi-
Continue
• Always ple devices to one connection by UDP.
QnU*8
• Check if the upper limit of the remote password
mismatch count is too low.
[SNTP OPE.ERROR]
Time setting failed when the programmable control- • Check if the time setting function is set up cor-
RUN:
Off/ON
12
ler was powered ON or reset. rectly.
ERR.:
■Collateral information • Check if the specified SNTP server is operating
2710 Flicker/ON
• Common Information:– normally, or if any failure has occurred on the
• Individual Information:– network connected to the specified SNTP server
CPU Status:
■Diagnostic Timing computer.
• When time setting function is executed Stop/Continue
12 - 94
12.3.5 Error code list (3000 to 3999)
The following shows the error messages from the error code 3000 to 3999, the contents and
causes of the errors, and the corrective actions for the errors.
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[PARAMETER ERROR]
In a multiple CPU system, the intelligent function
module under control of another CPU is specified in
the interrupt pointer setting of the PLC parameter. • Specify the head I/O number of the intelligent
Qn(H)*1
■Collateral information function module under control of the host CPU.
QnPH
• Common Information:File name/ Drive name • Delete the interrupt pointer setting of the parame-
• Individual Information:Parameter number ter. QnU*10
■Diagnostic Timing
• At power ON/At reset/STOP RUN/
At writing to progurammable controller
[PARAMETER ERROR]
The PLC parameter settings for timer time limit set-
ting, the RUN-PAUSE contact, the common pointer
number, general data processing, number of empty
slots, system interrupt settings, baud rate setting,
and service processing setting are outside the
range that can be used by the CPU module. QCPU
■Collateral information
• Common Information:File name/ Drive name
• Individual Information:Parameter number
■Diagnostic Timing
• At power ON/At reset/STOP RUN/
At writing to progurammable controller
[PARAMETER ERROR]
In a program memory check, the check capacity RUN:
has not been set within the range applicable for the Off
CPU module. ERR.:
3000 ■Collateral information Flicker QnPH
• Read the individual information of the error using
• Common Information:File name/ Drive name the peripheral device, check the parameter item QnPRH*5
• Individual Information:Parameter number CPU Status:
corresponding to the numerical value (parameter
■Diagnostic Timing Stop
No.), and correct it.
• At power ON/At reset/STOP RUN/ • Rewrite corrected parameters to the CPU mod-
At writing to progurammable controller ule, reload the CPU power supply and/or reset
[PARAMETER ERROR] the module.
The parameter settings in the error individual infor- • If the same error occurs, it is thought to be a
mation (special register SD16) are illegal. hardware error. (Contact your local Mitsubishi
■Collateral information representative.)
• Common Information:File name/ Drive name QCPU
• Individual Information:Parameter number
■Diagnostic Timing
• At power ON/At reset/STOP RUN/
At writing to progurammable controller
[PARAMETER ERROR]
The ATA card is set to the memory card slot when
the specified drive for the file register is set to
“memory card (ROM)” and [Use the following file]
or [Use the same file name as the program] (either
one is allowed) is set in the PLC file setting.
■Collateral information QnU*11
• Common Information:File name/ Drive name
• Individual Information:Parameter number
■Diagnostic Timing
• At power ON/At reset/STOP RUN/
At writing to progurammable controller
12 - 95
CHAPTER12 TROUBLESHOOTING
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
• Read the individual information of the error using
[PARAMETER ERROR] the peripheral device, check the parameter item
The parameter settings are corrupted. corresponding to the numerical value (parameter
■Collateral information No.), and correct it.
• Common Information:File name/ Drive name • Rewrite corrected parameters to the CPU mod-
3001 • Individual Information:Parameter number QCPU
ule, reload the CPU power supply and/or reset
■Diagnostic Timing the module.
• At power ON/At reset/STOP RUN/ • If the same error occurs, it is thought to be a
At writing to progurammable controller hardware error. (Contact your local Mitsubishi
representative.)
[PARAMETER ERROR]
When "Use the following file" is selected for the file
register in the PLC file setting of the PLC parameter
12
dialog box, the specified file does not exist although
the file register capacity has been set. Qn(H)
■Collateral information QnPH
• Common Information:File name/ Drive name QnPRH
• Individual Information:Parameter number
■Diagnostic Timing
• At power ON/At reset/STOP RUN/ RUN:
Off
At writing to progurammable controller
ERR.:
[PARAMETER ERROR]
Flicker
When [Use the following file] is set for the file regis- • Read the individual information of the error using
ter in the PLC file setting of the PLC parameter dia- the peripheral device, check the parameter item
CPU Status:
log box and the capacity of file register is not set, corresponding to the numerical value (parameter
Stop
the file register file does not exist in the specified No.), and correct it.
target memory. • Rewrite corrected parameters to the CPU mod-
3002
■Collateral information QnU*10
ule, reload the CPU power supply and/or reset
• Common Information:File name/ Drive name the module.
• Individual Information:Parameter number • If the same error occurs, it is thought to be a
■Diagnostic Timing hardware error. (Contact your local Mitsubishi
• At power ON/At reset/STOP RUN/ representative.)
At writing to progurammable controller
[PARAMETER ERROR]
12 - 96
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[PARAMETER ERROR]
The automatic refresh range of the multiple CPU
system exceeded the file register capacity.
Qn(H)*1
■Collateral information Change the file register file for the one refresh-
QnPH
• Common Information:File name/ Drive name enabled in the whole range.
• Individual Information:Parameter number QnU*10
■Diagnostic Timing
• When an END instruction executed
[PARAMETER ERROR]
3003 • Read the individual information of the error using
The number of devices set at the PLC parameter
the peripheral device, check the parameter item
device settings exceeds the possible CPU module
corresponding to the numerical value (parameter
range.
No.), and correct it.
■Collateral information
• Common Information:File name/ Drive name • If the error is still generated following the correc-
• Individual Information:Parameter number tion of the parameter settings, the possible cause
■Diagnostic Timing is the memory errorm of the CPU module's pro-
gram memory or the memory card. (Contact your
• At power-On/ At reset/ STOP RUN/
local Mitsubishi representative.)
At writing to progurammable controller
QCPU
[PARAMETER ERROR]
The parameter file is incorrect.
Alternatively, the contents of the file are not param-
eters.
Check whether the parameter file version
■Collateral information
3004 • Common Information:File name/ Drive name is .QPA, and check the file contents to be
• Individual Information:Parameter number sure they are parameters. RUN:
■Diagnostic Timing Off
• At power-On/ At reset/ STOP RUN/ ERR.:
Flicker
At writing to progurammable controller
• Read the individual information of the error using
CPU Status:
the peripheral device, check the parameter item
Stop
[PARAMETER ERROR] corresponding to the numerical value (parameter
The contents of the parameter are broken. No.), and correct it.
■Collateral information • Write the modified parameter items to the CPU Qn(H)*7
3005 • Common Information:File name/ Drive name module again, and power-on the Programmable QnPH*9
• Individual Information:Parameter number Controller or reset the CPU module. QnPRH*9
■Diagnostic Timing • When the same error occurs again, the hardware
• At power-ON/ At reset/ STOP RUN is faulty. Contact your local Mitsubishi represen-
tative, explaining a detailed description of the
problem.
[PARAMETER ERROR] • Delete the setting of the Q02CPU' s high speed
• The high speed interrupt is set in a Q02CPU. interrupt. To use high speed interrupts, change
• The high speed interrupt is set in a multiple CPU the CPU module to one of the Q02H/Q06H/
system. Q12H/Q25HCPU.
• The high speed interrupt is set when aQA1S6 B • To use a multiple CPU system, delete the setting
of the high-speed interrupt. To use high speed
or QA6 B is used.
interrupts, change the system to a single CPU
• No module is installed at the I/O address desig-
3006 system. Qn(H)*4
nated by the high speed interrupt.
• To use either the QA1S6 B or QA6 B, delete
■Collateral information
• Common Information:File name/ Drive name the setting of the high speed interrupt. To use
• Individual Information:Parameter number high speed interrupts, do not use the QA1S6 B/
■Diagnostic Timing QA6 B.
• At power-On/ At reset/ STOP RUN/ • Re-examine the I/O address designated by the
At writing to progurammable controller high speed interrupt setting.
12 - 97
CHAPTER12 TROUBLESHOOTING
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[PARAMETER ERROR]
The parameter file in the drive specified as valid
parameter drive by the DIP switches is inapplicable
for the CPU module.
Create parameters using GX Developer, and write
■Collateral information
3007 • Common Information:File name/ Drive name them to the drive specified as valid parameter drive QnPRH
• Individual Information:Parameter number by the DIP switches.
■Diagnostic Timing
• At power-On/ At reset/ STOP RUN/
At writing to progurammable controller
[PARAMETER ERROR]
In a multiple CPU system, the modules for AnS, A,
Q2AS and QnA have been set to multiple control
12
CPUs.
Re-set the parameter I/O assignment to control
■Collateral information
3009 • Common Information:File name/ Drive name them under one CPU module. (Change the param- Qn(H)*1
• Individual Information:Parameter number eters of all CPUs in the multiple CPU system.)
RUN:
■Diagnostic Timing Off
• At power-On/ At reset/ STOP RUN/ ERR.:
At writing to progurammable controller Flicker
[PARAMETER ERROR]
The parameter-set number of CPU modules differs CPU Status:
from the actual number in a multiple CPU system. Stop
■Collateral information Match the number of (CPU modules in multiple
• Common Information:File name/ Drive name Qn(H)*1
3010 CPU setting) - (CPUs set as empty in I/O assign-
• Individual Information:Parameter number QnPH
ment) with that of actually mounted CPU modules.
■Diagnostic Timing
• At power-On/ At reset/ STOP RUN/
At writing to progurammable controller
[PARAMETER ERROR]
Multiple CPU setting or control CPU setting differs
from that of the reference CPU settings in a multi-
ple CPU system.
Match the multiple CPU setting or control CPU set- Q00/Q01*1
■Collateral information
12 - 98
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[PARAMETER ERROR]
Multiple CPU auto refresh setting is any of the fol-
lowings in a multiple CPU system.
• When a bit device is specified as a refresh
Check the following in the multiple CPU auto
device, a number other than a multiple of 16 is
refresh setting and make correction.
specified for the refresh-starting device.
• When specifying the bit device, specify a multiple
• The device specified is other than the one that
may be specified.
of 16 for the refresh starting device. Qn(H)*1
• Specify the device that may be specified for the QnPH
• The number of send points is an odd number.
refresh device.
■Collateral information
• Common Information:File name/ Drive name • Set the number of send points to an even num-
• Individual Information:Parameter number ber.
■Diagnostic Timing
• At power-On/ At reset/ STOP RUN/
At writing to progurammable controller
[PARAMETER ERROR]
In a multiple CPU system, the multiple CPU auto
refresh setting is any of the following.
• The total number of transmission points is
greater than the maximum number of refresh Check the following in the multiple CPU auto
points. refresh setting and make correction.
■Collateral information Q00/Q01*1
• The total number of transmission points is within
3013 • Common Information:File name/ Drive name the maximum number of refresh points.
• Individual Information:Parameter number
■Diagnostic Timing
• At power-On/ At reset/ STOP RUN/
At writing to progurammable controller RUN:
[PARAMETER ERROR] Off
In a multiple CPU system, the multiple CPU auto ERR.:
refresh setting is any of the following. Flicker
• The device specified is other than the one that Check the following in the multiple CPU auto
may be specified. refresh setting and make correction. CPU Status:
• The number of send points is an odd number. • Specify the device that may be specified for the Stop
• The total number of send points is greater than refresh device.
the maximum number of refresh points. • Set the number of send points to an even num-
• The setting of the refresh range crosses over the ber.
boundary between the internal user device and QnU*10
• Set the total number of send points within the
the extended data register (D) or extended link range of the maximum number of refresh points.
register (W). • Set the refresh range so that it does not cross
■Collateral information over the boundary between the internal user
• Common Information:File name/ Drive name device and the extended data register (D) or
• Individual Information:Parameter number extended link register (W).
■Diagnostic Timing
• At power-On/ At reset/ STOP RUN/
At writing to progurammable controller
[PARAMETER ERROR]
• In a multiple CPU system, the online module
change parameter (multiple CPU system param-
eter) settings differ from those of the reference
CPU. • Match the online module change parameter with
• In a multiple CPU system, the online module
that of the reference CPU.
change setting is enabled although the CPU Qn(H)
• If the CPU module that does not support online
3014 module mounted does not support online module QnPH
chang parameter. module change is mounted, replace it with the
QnU*8
■Collateral information CPU module that supports online module
• Common Information:File name/ Drive name change.
• Individual Information:Parameter number
■Diagnostic Timing
• At power-On/ At reset/ STOP RUN/
At writing to progurammable controller
12 - 99
CHAPTER12 TROUBLESHOOTING
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[PARAMETER ERROR]
In a multiple CPU system configuration, the CPU
verified is different from the one set in the parame-
Read the individual information of the error using
ter setting.
the peripheral device, check the parameter item
■Collateral information
3015 • Common Information:File name/ Drive name corresponding to the numerical value (parameter
• Individual Information:Parameter number/CPU No. No./CPU No.) and parameter of target CPU, and
■Diagnostic Timing correct them.
12 - 100
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[LINK PARA. ERROR]
In a multiple CPU system, the CC-Link IE controller
network module controlled by another CPU is spec- • Delete the network parameter of the CC-Link IE
ified as the head I/O number of the CC-Link IE con- controller network module controlled by another
Qn(H)*7
troller network module. CPU.
■Collateral information • Change the setting to the head I/O number of the QnPH*9
• Common Information:File name/ Drive name CC-Link IE controller network module controlled QnU
• Individual Information:Parameter number by host CPU.
■Diagnostic Timing
• At power-ON/ At reset/ STOP RUN
[LINK PARA. ERROR]
The network parameter of the CC-Link IE controller
network operating as the normal station is overwrit-
ten to the control station.
Or, the network parameter of the CC-Link IE con-
troller network operating as the control station is
overwritten to the normal station.
Reset the CPU module.
(The network parameter is updated on the module
by resetting.)
■Collateral information
• Common Information:File name/ Drive name
• Individual Information:Parameter number
■Diagnostic Timing
• At power-ON/ At reset/ STOP RUN
RUN:
[LINK PARA. ERROR]
Off
• The number of modules actually mounted is dif-
ERR.:
ferent from that is set in Network parameter for
3100 Flicker
MELSECNET/H.
• The head I/O number of the actually mounted
CPU Status:
module is different from the one set in the net-
Stop
work parameter of the CC-Link IE controller net- Qn(H)*7
work. QnPH*9
• Data cannot be handled in the parameter exists. • Check the network parameter and actual mount- QnPRH*9
• The network type of CC-Link IE controller net- ing status, and if they differ, make them matched. QnU
work is overwritten during power-on. (When When network parameters are modified, write
changing the network type, switch RESET to them to the CPU module.
RUN.) • Check the setting of extension base unit stage
■Collateral information number.
• Common Information:File name/ Drive name • Check the connection status of extension base
• Individual Information:Parameter number unit and extension cable. When the GOT is bus-
■Diagnostic Timing connected to the main base unit or extension
• At power-ON/ At reset/ STOP RUN base unit, also check its connection status.
[LINK PARA. ERROR] If an error occurs even after performing the
• The CC-Link IE controller network module is above checks, the hardware may be faulty.
specified for the head I/O number of network (Contact your local Mitsubishi representative,
parameter in the MELSECNET/H. explaining a detailed description of the problem.)
• The MELSECNET/H module is specified for the
head I/O number of network parameter in the
CC-Link IE controller network.
■Collateral information
• Common Information:File name/ Drive name
• Individual Information:Parameter number
■Diagnostic Timing
• At power-ON/ At reset/ STOP RUN
12 - 101
CHAPTER12 TROUBLESHOOTING
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
• Check the network parameter and actual mount-
[LINK PARA. ERROR]
ing status, and if they differ, make them matched.
• Although the CC-Link IE controller network mod-
When network parameters are modified, write
ule is mounted, network parameter for the CC-
them to the CPU module.
Link IE controller network module is not set.
• Check the setting of extension base unit stage
• Although the CC-Link IE controller network and
number. Qn(H)*7
MELSECNET/H modules are mounted, network
parameter for the MELSECNET/H module is not
• Check the connection status of extension base QnPH*9
unit and extension cable. When the GOT is bus- QnPRH*9
set.
connected to the main base unit or extension QnU
■Collateral information
• Common Information:File name/ Drive name base unit, also check its connection status.
• Individual Information:Parameter number If an error occurs even after performing the
■Diagnostic Timing above checks, the hardware may be faulty.
(Contact your local Mitsubishi representative,
12
• At power-ON/ At reset/ STOP RUN
explaining a detailed description of the problem.)
[LINK PARA. ERROR]
In a multiple CPU system, the MELSECNET/H
under control of another CPU is specified as the
• Delete the MELSECNET/H network parameter of
head I/O number in the network setting parameter Q00/Q01*1
the MELSECNET/H under control of another
of the MELSECNET/H. Qn(H)*1
CPU.
■Collateral information QnPH
• Common Information:File name/ Drive name • Change the setting to the head I/O number of the
MELSECNET/H under control of the host CPU. QnU*10
• Individual Information:Parameter number
■Diagnostic Timing
• At power ON/At reset/STOP RUN
[LINK PARA. ERROR] RUN:
The network parameter of the MELSECNET/H Off
operating as the normal station is overwritten to the ERR.:
3100 control station. Flicker
Or, the network parameter of the MELSECNET/H
operating as the control station is overwritten to the Qn(H)*1
CPU Status:
normal station. (The network parameter is updated QnPH
Reset the CPU module. Stop
on the module by resetting.) QnPRH
■Collateral information QnU
• Common Information:File name/ Drive name
12 - 102
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[LINK PARA. ERROR]
The link refresh range exceeded the file register
capacity. Qn(H)*1
■Collateral information Change the file register file for the one that enables QnPH
• Common Information:File name/ Drive name entire range refresh. QnPRH
• Individual Information:Parameter number QnU*10
■Diagnostic Timing
• When an END instruction executed
[LINK PARA. ERROR]
• When the station number of the MELSECNET/H
module is 0, the PLC-to-PLC network parameter
has been set.
• When the station number of the MELSECNET/H
module is other than 0, the remote master
Correct the type or station number of the MELSEC- Qn(H)*1
NET/H module in the network parameter to meet QnPH
parameter setting has been made.
the used system. QnPRH
■Collateral information
• Common Information:File name/ Drive name
• Individual Information:Parameter number
■Diagnostic Timing
• At power ON/At reset/STOP RUN
[LINK PARA. ERROR]
The refresh parameter for the CC-Link IE controller
network is outside the range. Qn(H)*7
■Collateral information QnPH*9
• Common Information:File name/ Drive name RUN: QnPRH*9
• Individual Information:Parameter number • Check the network parameters and mounting Off QnU
■Diagnostic Timing status, and if they differ, match the network ERR.:
3101 • At power ON/At reset/STOP RUN parameters and mounting status. Flicker
[LINK PARA. ERROR] If any network parameter has been corrected,
• The network No. specified by a network parame- write it to the CPU module. CPU Status:
ter is different from that of the actually mounted • Confirm the setting of the number of extension Stop
network. stages of the extension base units.
• The head I/O No. specified by a network parame- • Check the connection status of the extension
ter is different from that of the actually mounted I/ base units and extension cables.
O unit. When the GOT is bus-connected to the main
• The network class specified by a network param- base unit and extension base units, also check
eter is different from that of the actually mounted their connection status.
QCPU
network. If the error occurs after the above checks, the
• The network refresh parameter of the MELSEC- cause is a hardware fault. (Contact your local Mit-
NET/H, MELSECNET/10 is out of the specified subishi representative, explaining a detailed
area. description of the problem.)
■Collateral information
• Common Information:File name/ Drive name
• Individual Information:Parameter number
■Diagnostic Timing
• At power ON/At reset/STOP RUN
[LINK PARA. ERROR]
A multi-remote I/O network was configured using a
module that does not support the MELSECNET/H
multi-remote I/O network.
Use a module that supports the MELSECNET/H
■Collateral information QnPH
• Common Information:File name/ Drive name multi-remote I/O network.
• Individual Information:Parameter number
■Diagnostic Timing
• At power ON/At reset/STOP RUN
12 - 103
CHAPTER12 TROUBLESHOOTING
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[LINK PARA. ERROR]
• The system A of the MELSECNET/H remote
master station has been set to other than Station
No. 0.
• Set the system A of the MELSECNET/H remote
• The system B of the MELSECNET/H remote
master station to Station No. 0.
master station has been set to Station No. 0. QnPRH
• Set the system B of the MELSECNET/H remote
■Collateral information
• Common Information:File name/ Drive name master station to any of Station No. 1 to 64.
• Individual Information:Parameter number
■Diagnostic Timing
• At power ON/At reset/STOP RUN
[LINK PARA. ERROR]
Since the number of points of the B/W device set in
12
[Device] of the PLC parameter is lower than the
number of B/W refresh device points shown in the
following table when parameters of the MELSEC-
NET/H are not set, the refresh between the CPU
module and the MELSECNET/H cannot be per-
formed..
RUN:
Refresh No. of refresh device No. of refresh device
device points of B device points of W device Off
8192 points 8192 points ERR.: Qn(H)*7
1 (8192 points×1 (8192 points×1 Set the refresh parameter of the MELSECNET/H in
3101 module) module) Flicker QnPH*7
accordance with the number of points of B/W
8192 points 8192 points
No. of 2 (4096 points×2 (4096 points×2 devices set in [Device] of the PLC parameter. QnPRH*7
mountable modules) modules) CPU Status: QnU
network 6144 points 6144 points Stop
modules 3 (2048 points×3 (2048 points×3
modules) modules)
8192 points 8192 points
4 (2048 points×4 (2048 points×4
modules) modules)
■Collateral information
• Common Information:File name/ Drive name
• Individual Information:Parameter number
■Diagnostic Timing
12 - 104
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[LINK PARA. ERROR]
A CC-Link IE controller network parameter error
was detected. Qn(H)*7
■Collateral information QnPH*9
• Common Information:File name/ Drive name
QnPRH*9
• Individual Information:Parameter number
QnU
■Diagnostic Timing
• At power ON/At reset/STOP RUN • Correct and write the network parameters.
[LINK PARA. ERROR] • If the error occurs after correction, it suggests a
• The network module detected a network parame- hardware fault. (Contact your local Mitsubishi
ter error. representative.)
• A MELSECNET/H network parameter error was
detected.
QCPU
■Collateral information
• Common Information:File name/ Drive name
• Individual Information:Parameter number
■Diagnostic Timing
• At power ON/At reset/STOP RUN
[LINK PARA. ERROR]
The station No. specified in pairing setting are not
correct.
• The stations are not numbered consecutively.
Refer to the troubleshooting of the network module,
• Pairing setting has not been made for the CPU
and if the error is due to incorrect pairing setting,
module at the normal station. QnPRH
reexamine the pairing setting of the network param-
■Collateral information
• Common Information:File name/ Drive name eter. RUN:
• Individual Information:Parameter number Off
■Diagnostic Timing ERR.:
3102 • At power ON/At reset/STOP RUN Flicker
12 - 105
CHAPTER12 TROUBLESHOOTING
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[LINK PARA. ERROR]
• LB/LW own station send range at LB/LW4000 or
later was set.
• LB/LW setting (2) was performed.
Examine the network range assignments for the
3102 ■Collateral information Q00J/Q00/Q01
• Common Information:File name/ Drive name network parameter in the control station.
• Individual Information:Parameter number
■Diagnostic Timing
• At power ON/At reset/STOP RUN
[LINK PARA. ERROR]
In a multiple CPU system, Ethernet interface mod-
ule under control of another station is specified to
the start I/O number of the Ethernet network
• Delete the Ethernet network parameter of Ether-
net interface module under control of another Q00/Q01*1
12
parameter. station. Qn(H)*1
■Collateral information • Change the setting to the start I/O number of QnPH
• Common Information:File name/ Drive name Ethernet interface module under control of the QnU*10
• Individual Information:Parameter number host station.
■Diagnostic Timing
• At power ON/At reset/STOP RUN
[LINK PARA. ERROR]
• Although the number of modules has been set to
one or greater number in the Ethernet module
count parameter setting, the number of actually
mounted module is zero.
• The start I/O No. of the Ethernet network param-
eter differs from the I/O No. of the actually QCPU
3103 mounted module. RUN:
■Collateral information Off
• Common Information:File name/ Drive name ERR.:
• Individual Information:Parameter number Flicker
■Diagnostic Timing • Correct and write the network parameters.
• At power ON/At reset/STOP RUN • If the error occurs after correction, it suggests a
CPU Status:
hardware fault. (Contact your local Mitsubishi
[LINK PARA. ERROR] Stop
representative.)
• Ethernet module whose network type is set to
12 - 106
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[LINK PARA. ERROR]
In a multiple CPU system, the CC-Link module
under control of another station is specified as the
head I/O number of the CC-Link network parame- • Delete the CC-Link network parameter of the Q00/Q01*1
ter. CC-Link module under control of another station. Qn(H)*1
■Collateral information • Change the setting to the start I/O number of the QnPH
• Common Information:File name/ Drive name CC-Link module under control of the host station. QnU*10
• Individual Information:Parameter number
■Diagnostic Timing
• At power ON/At reset/STOP RUN
[LINK PARA. ERROR]
• Though the number of CC-Link modules set in
the network parameters is one or more, the num-
ber of actually mounted modules is zero.
• The start I/O number in the common parameters
is different from that of the actually mounted
RUN:
module.
Off
• The station type of the CC-Link module count QCPU
ERR.:
setting parameters is different from that of the
3105 Flicker
actually mounted station.
■Collateral information
• Common Information:File name/ Drive name CPU Status:
• Individual Information:Parameter number Stop
• Correct and write the network parameters.
■Diagnostic Timing • If the error occurs after correction, it suggests a
• At power ON/At reset/STOP RUN hardware fault. (Contact your local Mitsubishi
[LINK PARA. ERROR] representative.)
• CC-Link module whose station type is set to
“master station (compatible with redundant func-
tion)” is mounted on the extension base unit in
the redundant system.
• CC-Link module whose station type is set to
“master station (extension base)” is mounted on QnPRH*7
the main base unit in the redundant system.
■Collateral information
• Common Information:File name/ Drive name
• Individual Information:Parameter number
■Diagnostic Timing
• At power ON/At reset/STOP RUN
12 - 107
CHAPTER12 TROUBLESHOOTING
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[LINK PARA. ERROR]
The CC-Link link refresh range exceeded the file
register capacity. Qn(H)*1
■Collateral information Change the file register file for the one refresh- QnPH
• Common Information:File name/ Drive name enabled in the whole range. QnPRH
• Individual Information:Parameter number QnU
■Diagnostic Timing
• When an END instruction executed
[LINK PARA. ERROR]
The network refresh parameter for CC-Link is out of
range.
■Collateral information
• Common Information:File name Check the parameter setting. QCPU 12
3106 • Individual Information:Parameter number
■Diagnostic Timing
• At power ON/At reset/STOP RUN
[LINK PARA. ERROR]
The setting of the network refresh range crosses
over the boundary between the internal user device
and the extended data register (D) or extended link Set the network refresh range so that it does not
register (W). cross over the boundary between the internal user
QnU
■Collateral information device and the extended data register (D) or
• Common Information:File name extended link register (W).
• Individual Information:Parameter number RUN:
■Diagnostic Timing Off
• At power ON/At reset/STOP RUN ERR.:
Flicker
[LINK PARA. ERROR]
• The CC-Link parameter setting is incorrect.
• The set mode is not allowed for the version of the CPU Status:
mounted CC-Link module. Stop
12 - 108
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[SFC PARA. ERROR]
The number of step relays specified in the device
setting of the PLC parameter dialog box is less than
that used in the program. Qn(H)
3202 ■Collateral information QnPH
• Common Information:File name QnPRH
• Individual Information:Parameter number
■Diagnostic Timing Read the common information of the error using
• STOP RUN the peripheral device, check error step correspond-
[SFC PARA. ERROR] ing to its numerical value (program error location),
The execution type of the SFC program specified in and correct the problem.
the program setting of the PLC parameter dialog
Qn(H)
box is other than scan execution.
QnPH
3203 ■Collateral information
• Common Information:File name QnPRH
• Individual Information:Parameter number QnU
■Diagnostic Timing
• At power-ON/ At reset/ STOP RUN*3
[SP. PARA ERROR]
The start I/O number in the intelligent function mod-
ule parameter set on GX Configurator differs from
the actual I/O number.
■Collateral information
3300 • Common Information:File name Check the parameter setting. QCPU
• Individual Information:Parameter number*2
■Diagnostic Timing
• At power-On/ At reset/ STOP RUN/
RUN:
At writing to progurammable controller Off
[SP. PARA ERROR] ERR.:
• The refresh setting of the intelligent function Flicker
module exceeded the file register capacity.
• The intelligent function module set in GX Config- CPU Status: Q00J/Q00/Q01
urator differs from the actually mounted module. • Change the file register file for the one which Stop Qn(H)*1
■Collateral information allows refresh in the whole range. QnPH
• Common Information:File name • Check the parameter setting. QnPRH
• Individual Information:Parameter number*2 QnU
■Diagnostic Timing
• At power-On/ At reset/ STOP RUN/
At writing to progurammable controller
[SP. PARA ERROR]
The intelligent function module's refresh parameter
setting is outside the available range.
■Collateral information
3301 • Common Information:File name Check the parameter setting. QCPU
• Individual Information:Parameter number*2
■Diagnostic Timing
• At power-On/ At reset/ STOP RUN/
At writing to progurammable controller
[SP. PARA ERROR]
The setting of the refresh parameter range crosses
over the boundary between the internal user device
and the extended data register (D) or extended link
register (W). Set the refresh parameter range so that it does not
■Collateral information cross over the boundary between the internal user
QnU
• Common Information:File name device and the extended data register (D) or
extended link register (W).
• Individual Information:Parameter number*2
■Diagnostic Timing
• At power-On/ At reset/ STOP RUN/
At writing to progurammable controller
12 - 109
CHAPTER12 TROUBLESHOOTING
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[SP. PARA ERROR]
The intelligent function module's refresh parameter
are abnormal.
■Collateral information
3302 • Common Information:File name Check the parameter setting. QCPU
• Individual Information:Parameter number*2
■Diagnostic Timing
• At power-On/ At reset/ STOP RUN/
At writing to progurammable controller
[SP. PARA ERROR]
In a multiple CPU system, the automatic refresh
setting or other parameter setting was made to the
intelligent function module under control of another
• Delete the automatic refresh setting or other
12
parameter setting of the intelligent function mod- Q00/Q01*1
station.
■Collateral information
ule under control of another CPU. Qn(H)*1
3303
• Common Information:File name/ Drive name • Change the setting to the automatic refresh set- QnPH
• Individual Information:Parameter number ting or other parameter setting of the intelligent QnU*10
■Diagnostic Timing function module under control of the host CPU.
12 - 110
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[REMOTE PASS. ERR.]
Position specified as the head I/O number of the
remote password file is incorrect due to one of the
following reasons:
• Module is not loaded.
• Other than a the intelligent function module (I/O
module)
• Intelligent function module other than serial com-
munication module, modem interface module or
Mount serial communication module, modem inter- Qn(H)*1
face module or Ethernet module of function version QnPH
Ethernet module
B or later in the position specified in the head I/O QnPRH
• Serial communication module or Ethernet mod-
No. of the remote password file. QnU
ule of function version A
The intelligent function module where remote pass-
word is available is not mounted.
■Collateral information
• Common Information:–
• Individual Information:–
■Diagnostic Timing
• At power ON/At reset/STOP RUN RUN:
[REMOTE PASS. ERR.] Off
Any of the following modules is not mounted on the ERR.:
3401 slot specified for the head I/O number of the remote Flicker
password. Mount any of the following modules in the position
• Serial communication module of function version specified for the head I/O number of the remote CPU Status:
B or later password. Stop
• Ethernet module of function version B or later • Serial communication module of function version
• Modem interface module of function version B or Q00J/Q00/Q01*1
B or later
later • Ethernet module of function version B or later
■Collateral information • Modem interface module of function version B or
• Common Information:– later
• Individual Information:–
■Diagnostic Timing
• At power ON/At reset/STOP RUN
[REMOTE PASS. ERR.]
Serial communication module, modem interface
module or Ethernet module of function version B or
later controlled by another CPU was specified in a
• Change it for the Ethernet module of function Qn(H)*1
multiple CPU system.
version B or later connected by the host CPU. QnPH
■Collateral information
• Common Information:– • Delete the remote password setting. QnU*10
• Individual Information:–
■Diagnostic Timing
• At power ON/At reset/STOP RUN
12 - 111
CHAPTER12 TROUBLESHOOTING
The following shows the error messages from the error code 4000 to 4999, the contents and
causes of the errors, and the corrective actions for the errors.
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[INSTRCT. CODE ERR]
• The program contains an instruction code that
cannot be decoded.
• An unusable instruction is included in the pro- 12
gram.
4000 ■Collateral information QCPU
• Common Information:Program error location
• Individual Information:–
■Diagnostic Timing
• At power ON/At reset/STOP RUN
When instruction executed
[INSTRCT. CODE ERR]
The program contains a dedicated instruction for
SFC although it is not an SFC program. Q00J/Q00/Q01*2
■Collateral information Qn(H)
4001 • Common Information:Program error location QnPH
• Individual Information:– QnPRH
■Diagnostic Timing QnU
• At power ON/At reset/STOP RUN
When instruction executed
[INSTRCT. CODE ERR]
• The name of dedicated instruction specified by
RUN:
the program is incorrect.
Off
• The dedicated instruction specified by the pro- Read the common information of the error using a
ERR.:
gram cannot be executed by the specified mod- peripheral device, check error step corresponding
Flicker
ule. to its numerical value (program error location), and
12 - 112
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[MISSING END INS.]
There is no END (FEND) instruction in the pro-
gram.
■Collateral information
4010 • Common Information:Program error location QCPU
• Individual Information:–
■Diagnostic Timing
• At power ON/At reset/STOP RUN
[CAN'T SET(P)]
The total number of internal file pointers used by
the program exceeds the number of internal file
Qn(H)
pointers set in the parameters.
QnPH
4020 ■Collateral information
• Common Information:Program error location QnPRH
• Individual Information:– RUN: QnU
■Diagnostic Timing Off
• At power ON/At reset/STOP RUN ERR.:
Flicker
[CAN'T SET(P)]
• The common pointer Nos. assigned to files over-
Read the common information of the error using a CPU Status:
lap.
peripheral device, check error step corresponding Stop
• The local pointer Nos. assigned to files overlap.
to its numerical value (program error location), and
4021 ■Collateral information
correct the problem.
• Common Information:Program error location
• Individual Information:–
■Diagnostic Timing
• At power ON/At reset/STOP RUN QCPU
[CAN'T SET(I)]
The allocation pointer Nos. assigned by files over-
lap.
■Collateral information
4030 • Common Information:Program error location
• Individual Information:–
■Diagnostic Timing
• At power ON/At reset/STOP RUN
[OPERATION ERROR]
The instruction cannot process the contained data.
■Collateral information
• Common Information:Program error location QCPU
• Individual Information:–
■Diagnostic Timing
• When instruction executed
[OPERATION ERROR] • Take measurements against noise. RUN:
Access error of ATA card occurs by Off/On
• Reset and restart the CPU module.
SP.FREAD/SP.FWRITE instructions. Qn(H)
When the same error is displayed again, the ERR.:
■Collateral information QnPH
ATA card has hardware failure. Flicker/On
4100 • Common Information:Program error location QnPRH
(Please consult your local Mitsubishi service cen-
• Individual Information:–
CPU Status: QnU*11
ter or representative, explaining a detailed
■Diagnostic Timing
description of the problem.) Stop/
• When instruction executed
Continue*1
[OPERATION ERROR]
The file being accessed by other functions with
• Stop the file accessed with other functions to
SP.FWRITE instruction was accessed.
execute SP.FWRITE instruction.
■Collateral information
• Stop the access with othrer functions and the QnU*11
• Common Information:Program error location
SP.FWRITE instructuion to execute at same
• Individual Information:–
time.
■Diagnostic Timing
• When instruction executed
*1 CPU operation can be set in the parameters at error occurrence. (LED indication varies.)
*11 The Universal model QCPU except the Q00UJCPU, Q00UCPU, and Q01UCPU.
12 - 113
CHAPTER12 TROUBLESHOOTING
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[OPERATION ERROR]
• The number of setting data dealt with the instruc-
tion exceeds the applicable range.
• The storage data and constant of the device
specified by the instruction exceeds the applica-
ble range.
• When writing to the host CPU shared memory,
the write prohibited area is specified for the write
destination address.
• The range of storage data of the device specified
QCPU
by the instruction is duplicated.
• The device specified by the instruction exceeds
the range of the number of device points.
12
• The interrupt pointer No. specified by the instruc-
tion exceeds the applicable range.
■Collateral information
• Common Information:Program error location RUN:
• Individual Information:– Off/On
■Diagnostic Timing ERR.:
Read the common information of the error using
• When instruction executed
the peripheral device, check error step correspond- Flicker/On
4101 [OPERATION ERROR]
ing to its numerical value (program error location),
• The storage data of file register specified by the
and correct the problem. CPU Status:
instruction exceeds the applicable range. Or, file
Stop/
register is not set.
Continue*1
■Collateral information QnU*10
• Common Information:Program error location
• Individual Information:–
■Diagnostic Timing
• When instruction executed
[OPERATION ERROR]
• The block data that crosses over the boundary
between the internal user device and the
extended data register (D) or extended link regis-
ter is specified (including 32-bit binary, real num-
ber (single precision, double precision), indirect
*1 CPU operation can be set in the parameters at error occurrence. (LED indication varies.)
*10 The Universal model QCPU except the Q00UJCPU.
12 - 114
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[OPERATION ERROR]
In a multiple CPU system, the link direct device
(J \ ) was specified for the network module • Delete from the program the link direct device
Q00/Q01*2
under control of another station. which specifies the network module under con-
Qn(H)*2
■Collateral information trol of another CPU.
QnPH
• Common Information:Program error location • Using the link direct device, specify the network
• Individual Information:– module under control of the host CPU. QnU*10
■Diagnostic Timing
• When instruction executed
[OPERATION ERROR]
• The network No. or station No. specified for the
dedicated instruction is wrong.
• The link direct device (J \ ) setting is incorrect.
• The module No./ network No./number of charac-
4102 ter strings exceeds the range that can be speci- QCPU
fied.
■Collateral information
• Common Information:Program error location
• Individual Information:–
■Diagnostic Timing
• When instruction executed
[OPERATION ERROR] Read the common information of the error using
• The specification of character string the peripheral device, check error step correspond- RUN:
(" ") specified by dedicated instruction cannot be ing to its numerical value (program error location), Off/On
used for the character string. and correct the problem. ERR.:
■Collateral information QnU
Flicker/On
• Common Information:Program error location
• Individual Information:–
CPU Status:
■Diagnostic Timing
• When instruction executed Stop/
*1 CPU operation can be set in the parameters at error occurrence. (LED indication varies.)
*2 The function version is B or later.
*5 The module whose first 5 digits of serial No. is "07032" or later.
*10 The Universal model QCPU except the Q00UJCPU.
12 - 115
CHAPTER12 TROUBLESHOOTING
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[OPERATION ERROR]
With high speed interrupt setting PR, PRC,
UDCNT1, UDCNT2, PLSY or PWM instruction is
Delete the high-speed interrupt setting.
executed.
When using high-speed interrupt, delete the PR,
4109 ■Collateral information Qn(H)*3
PRC, UDCNT1, UDCNT2, PLSY and PWM instruc-
• Common Information:Program error location
tions.
• Individual Information:–
■Diagnostic Timing
• When instruction executed
[OPERATION ERROR] RUN:
An attempt was made to perform write/read to/from Off/On
ERR.:
the CPU shared memory write/read disable area of
the host station CPU module with the instruction. Flicker/On 12
Q00/Q01*2
4111 ■Collateral information
CPU Status: QnU
• Common Information:Program error location
• Individual Information:– Stop/
Read the common information of the error using
■Diagnostic Timing Continue*1
GX Developer, and check and correct the error step
• When instruction executed
corresponding to that value (program error loca-
[OPERATION ERROR]
tion).
The CPU module that cannot be specified with the
multiple CPU dedicated instruction was specified.
■Collateral information Q00/Q01*2
4112
• Common Information:Program error location QnU*10
• Individual Information:–
■Diagnostic Timing
• When instruction executed
[OPERATION ERROR]
• When the SP.DEVST instruction is executed, the
number of writing to the standard ROM of the day • Check that the number of execution of the RUN:
exceeds the value specified by SD695. SP.DEVST instruction is proper. Off/On
• The value outside the specified range is set to • Execute the SP.DEVST instruction again the fol- ERR.:
4113 SD695. lowing day or later day. Or, arrange the value of Flicker/On QnU
■Collateral information SD695.
• Common Information:Program error location • Correct the value of SD695 so that it does not CPU Status:
• Individual Information:– exceed the range. Stop/Continue
*1 CPU operation can be set in the parameters at error occurrence. (LED indication varies.)
*2 The function version is B or later.
*3 The module whose first 5 digits of serial No. is "04012" or later.
*10 The Universal model QCPU except the Q00UJCPU.
12 - 116
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[OPERATION ERROR]
• The dedicated instruction was executed to the
module mounted on the extension base unit in
the redundant system. RUN:
• The instruction for accessing the intelligent func- • Delete the dedicated instruction for the module Off/On
tion module mounted on the extension base unit mounted on the extension base unit. ERR.:
4122 from the standby system at separate mode was • Delete the instruction for accessing the intelligent Flicker/On QnPRH*6
executed. function module mounted on the extension base
■Collateral information unit from the standby system. CPU Status:
• Common Information:Program error location Stop/Continue
• Individual Information:–
■Diagnostic Timing
• When instruction executed
[OPERATION ERROR]
Instructions to read SFC step comment (S(P).SFC- RUN:
SCOMR) and SFC transition condition comment Off/On
(S(P).SFCTCOMR) are executed for the comment ERR.:
Qn(H)*4
file in ATA card Target comment file is to be other than the com- Flicker/On
4130 QnPH*5
■Collateral information ment file in ATA card.
• Common Information:Program error location CPU Status: QnPRH
• Individual Information:– Stop/
■Diagnostic Timing Continue*1
• When END/other instruction executed
[OPERATION ERROR]
The SFC program is started up by the instruction RUN:
while the other SFC program has not yet been Off/On
completed. Check the SFC program specified by the instruc- ERR.:
4131 ■Collateral information tion. Or, check the executing status of the SFC pro- Flicker/On
• Common Information:Program error location gram.
• Individual Information:– CPU Status:
■Diagnostic Timing Stop/Continue
• When instruction executed
[OPERATION ERROR]
Operation where the input data is special value
("-0", unnormalized number, nonnumeric, ) is
Read the common information of the error using
performed. QnU
the peripheral device, check the error step corre- RUN:
4140 ■Collateral information
sponding to the numerical value (program error Off/On
• Common Information:Program error location
part), and correct it. ERR.:
• Individual Information:–
■Diagnostic Timing Flicker/On
• When instruction executed
[OPERATION ERROR] CPU Status:
Overflow occurs at operation. Stop/
Read the common information of the error using
■Collateral information Continue*1
the peripheral device, check the error step corre-
4141 • Common Information:Program error location
sponding to the numerical value (program error
• Individual Information:–
part), and correct it.
■Diagnostic Timing
• When instruction executed
[FOR NEXT ERROR]
No NEXT instruction was executed following the
RUN:
execution of a FOR instruction.
Off
Alternatively, there are fewer NEXT instructions Read the common information of the error using
ERR.:
than FOR instructions. the peripheral device, check error step correspond-
4200 Flicker QCPU
■Collateral information ing to its numerical value (program error location),
• Common Information:Program error location and correct the problem.
CPU Status:
• Individual Information:–
Stop
■Diagnostic Timing
• When instruction executed
*1 CPU operation can be set in the parameters at error occurrence. (LED indication varies.)
*4 The module whose first 5 digits of serial No. is "07012" or later.
*5 The module whose first 5 digits of serial No. is "07032" or later.
*6 The module whose first 5 digits of serial No. is "09012" or later.
12 - 117
CHAPTER12 TROUBLESHOOTING
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[FOR NEXT ERROR]
A NEXT instruction was executed although no FOR
instruction has been executed.
Alternatively, there are more NEXT instructions Read the common information of the error using
than FOR instructions. the peripheral device, check error step correspond-
4201
■Collateral information ing to its numerical value (program error location),
• Common Information:Program error location and correct the problem.
• Individual Information:–
■Diagnostic Timing
• When instruction executed
[FOR NEXT ERROR]
More than 16 nesting levels are programmed.
■Collateral information 12
4202 • Common Information:Program error location Keep nesting levels at 16 or under.
• Individual Information:–
■Diagnostic Timing
• When instruction executed
[FOR NEXT ERROR]
A BREAK instruction was executed although no
FOR instruction has been executed prior to that.
■Collateral information
4203
• Common Information:Program error location
• Individual Information:–
■Diagnostic Timing Read the common information of the error using
• When instruction executed the peripheral device, check error step correspond-
RUN:
[CAN'T EXECUTE(P)] ing to its numerical value (program error location),
Off
The CALL instruction is executed, but there is no and correct the problem.
ERR.:
subroutine at the specified pointer.
Flicker QCPU
■Collateral information
4210
• Common Information:Program error location
CPU Status:
• Individual Information:–
Stop
■Diagnostic Timing
• When instruction executed
[CAN'T EXECUTE(P)]
There was no RET instruction in the executed sub-
12 - 118
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[CAN'T EXECUTE(I)]
Though an interrupt input occurred, the corre-
sponding interrupt pointer does not exist.
■Collateral information
4220
• Common Information:Program error location
• Individual Information:–
■Diagnostic Timing
• When instruction executed
[CAN'T EXECUTE(I)]
An IRET instruction does not exist in the executed
interrupt program.
■Collateral information
4221 QCPU
• Common Information:Program error location
• Individual Information:–
■Diagnostic Timing
• When instruction executed Read the common information of the error using
[CAN'T EXECUTE(I)] the peripheral device, check error step correspond-
The IRET instruction exists before the FEND ing to its numerical value (program error location),
instruction of the main routine program. and correct the problem.
■Collateral information
• Common Information:Program error location
• Individual Information:–
■Diagnostic Timing
• When instruction executed
[CAN'T EXECUTE(I)]
4223
• The IRET instruction was executed in the fixed
scan execution type program. RUN:
• The STOP instruction was executed in the fixed Off
scan execution type program. ERR.:
QnU
■Collateral information Flicker
• Common Information:Program error location
• Individual Information:– CPU Status:
■Diagnostic Timing Stop
• When instruction executed
[CAN'T EXECUTE(I)]
The interrupt pointer for the module mounted on
the extension base unit is set in the redundant sys-
tem. Delete the setting of interrupt pointer for the module
4225 ■Collateral information mounted on the extension base unit, since it cannot QnPRH*6
• Common Information:– be used.
• Individual Information:–
■Diagnostic Timing
• At power-ON/At reset
[INST. FORMAT ERR.]
The number of CHK and CHKEND instructions is
not equal.
■Collateral information Qn(H)
4230
• Common Information:Program error location QnPH
• Individual Information:–
■Diagnostic Timing Read the common information of the error using
• When instruction executed the peripheral device, check error step correspond-
[INST. FORMAT ERR.] ing to its numerical value (program error location),
The number of IX and IXEND instructions is not and correct the problem.
equal.
■Collateral information
4231 QCPU
• Common Information:Program error location
• Individual Information:–
■Diagnostic Timing
• When instruction executed
12 - 119
CHAPTER12 TROUBLESHOOTING
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[INST. FORMAT ERR.]
The configuration of the check conditions for the
CHK instruction is incorrect.
Alternatively, a CHK instruction has been used in a
low speed execution type program. Qn(H)
4235
■Collateral information QnPH
• Common Information:Program error location
• Individual Information:–
■Diagnostic Timing
• When instruction executed
[MULTI-COM.ERROR]
• The multiple CPU high-speed transmission dedi-
cated instruction used in the program specifies 12
the wrong CPU module. Or, the setting in the
CPU module is incompatible with the multiple
CPU high-speed transmission dedicated instruc-
tion.
• The reserved CPU is specified.
• The uninstalled CPU is specified.
• The head I/O number of the target CPU/16 (n1)
is outside the range of 3EH to 3E3H.
4350 • The CPU module where the instruction cannot be
executed is specified.
• The instruction is executed in a single CPU sys- RUN:
tem. Off
• The host CPU is specified. Read the common information of the error using
ERR.:
• The instruction is executed without setting the the peripheral device, check error step correspond-
Flicker
"Use multiple CPU high speed communication". ing to its numerical value (program error location),
■Collateral information and correct the problem.
CPU Status:
• Common Information:Program error location
Stop
• Individual Information:–
■Diagnostic Timing
QnU*7
• When instruction executed
[MULTI-COM.ERROR]
*7 The Universal model QCPU except the Q00UJCPU, Q00UCPU, Q01UCPU, and Q02UCPU.
12 - 120
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[MULTI-COM.ERROR]
The device which cannot be used for the multiple
CPU high-speed transmission dedicated instruction
specified by the program is specified.
4353 ■Collateral information QnU*7
• Common Information:Program error location
• Individual Information:–
■Diagnostic Timing
• When instruction executed
[MULTI-COM.ERROR]
The character string which cannot be handled by
the multiple CPU high-speed transmission dedi-
cated instruction is specified. Read the common information of the error using
4354 ■Collateral information the peripheral device, check error step
• Common Information:Program error location corresponding to its numerical value (program error
• Individual Information:– location), and correct the problem.
■Diagnostic Timing
• When instruction executed
[MULTI-COM.ERROR] QnU*7
The number of read/write data (number of request/
receive data) for the multiple CPU high-speed
transmission dedicated instruction specified by the
program is not valid.
4355
■Collateral information
• Common Information:Program error location
• Individual Information:–
■Diagnostic Timing
• When instruction executed RUN:
[SFCP. CODE ERROR] Off
No SFCP or SFCPEND instruction in SFC pro- ERR.:
gram. Flicker
Qn(H)
■Collateral information
4400 • Common Information:Program error location QnPH
CPU Status:
• Individual Information:– QnPRH
Stop
■Diagnostic Timing
• STOP RUN
[CAN'T SET(BL)]
The block number designated by the SFC program
exceeds the range.
■Collateral information
4410 • Common Information:Program error location
• Individual Information:–
■Diagnostic Timing
• STOP RUN Write the program to the CPU module again using
[CAN'T SET(BL)] GX Developer.
Block number designations overlap in SFC pro-
gram. Q00J/Q00/Q01*2
■Collateral information Qn(H)
4411 • Common Information:Program error location QnPH
• Individual Information:– QnPRH
■Diagnostic Timing QnU
• STOP RUN
[CAN'T SET(S)]
A step number designated in an SFC program
exceeds the range.
■Collateral information
4420 • Common Information:Program error location
• Individual Information:–
■Diagnostic Timing
• STOP RUN
12 - 121
CHAPTER12 TROUBLESHOOTING
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[CAN'T SET(S)]
Total number of steps in all SFC programs exceed
the maximum.
■Collateral information
4421 • Common Information:Program error location
• Individual Information:–
Q00J/Q00/Q01*2
■Diagnostic Timing
Qn(H)
• STOP RUN Write the program to the CPU module again using
QnPH
GX Developer.
[CAN'T SET(S)] QnPRH
Step number designations overlap in SFC program. QnU
■Collateral information
4422 • Common Information:Program error location
• Individual Information:–
12
■Diagnostic Timing
• STOP RUN
[CAN'T SET(S)]
The total number of (maximum step No.+1) of each
block exceeds the total number of step relays.
Correct the total number of step relays so that it
■Collateral information
4423 • Common Information:Program error location does not exceed the total number of (maximum
• Individual Information:– step No.+1) of each block.
■Diagnostic Timing
• STOP RUN RUN:
Off
[SFC EXE. ERROR]
ERR.:
The SFC program cannot be executed.
Flicker
• The data of the block data setting is illegal.
• Write the program to the CPU module again
• The SFC data device of the block data setting is
using GX Developer. CPU Status:
beyond the device setting range set in the PLC
• After correcting the setting of the SFC data Stop
4430 parameter.
device, write it to the CPU module.
■Collateral information
• Common Information:File name/Drive name • After correcting the device setting range set in
• Individual Information:– the PLC parameter, write it to the CPU module.
■Diagnostic Timing Q00J/Q00/Q01*2
• STOP RUN QnU
12 - 122
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[SFCP. FORMAT ERR.]
The numbers of BLOCK and BEND instructions in
an SFC program are not equal.
■Collateral information
4500 • Common Information:Program error location
• Individual Information:–
■Diagnostic Timing
• STOP RUN Qn(H)
[SFCP. FORMAT ERR.] QnPH
The configuration of the STEP* to TRAN* to TSET QnPRH
to SEND instructions in the SFC program is incor-
rect.
4501 ■Collateral information Write the program to the CPU module again using
• Common Information:Program error location the peripheral device.
• Individual Information:–
■Diagnostic Timing
• STOP RUN
[SFCP. FORMAT ERR.]
The structure of the SFC program is illegal.
• STEPI* instruction does not exist in the block of
RUN:
the SFC program.
Off
4502 ■Collateral information
• Common Information:Program error location ERR.:
• Individual Information:– Flicker
■Diagnostic Timing
CPU Status:
• STOP RUN
Stop
[SFCP. FORMAT ERR.]
The structure of the SFC program is illegal.
• The step specified in the TSET instruction does
• Write the program to the CPU module again
not exist. Q00J/Q00/Q01*2
using GX Developer.
• In jump transition, the host step number was Qn(H)
• Read the common information of the error using
4503 specified as the destination step number. QnPH
GX Developer, and check and correct the error
■Collateral information QnPRH
• Common Information:Program error location step corresponding to that value (program error
QnU
• Individual Information:– location).
■Diagnostic Timing
• STOP RUN
[SFCP. FORMAT ERR.]
The structure of the SFC program is illegal.
• The step specified in the TAND instruction does
not exist.
Write the program to the CPU module again using
4504 ■Collateral information
• Common Information:Program error location GX Developer.
• Individual Information:–
■Diagnostic Timing
• STOP RUN
12 - 123
CHAPTER12 TROUBLESHOOTING
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[SFCP. FORMAT ERR.]
The structure of the SFC program is illegal.
• In the operation output of a step, the SET Sn/
BLmSn or RST Sn/BLmSn instruction was speci-
fied for the host step.
4505
■Collateral information
• Common Information:Program error location RUN:
• Individual Information:– Off
■Diagnostic Timing Read the common information of the error using
ERR.:
• STOP RUN GX Developer, and check and correct the error step Q00J/Q00/Q01*2
Flicker
corresponding to that value (program error loca- QnU
[SFCP. FORMAT ERR.]
tion).
The structure of the SFC program is illegal.
• In a reset step, the host step number was speci-
CPU Status:
Stop
12
fied as the destination step.
4506 ■Collateral information
• Common Information:Program error location
• Individual Information:–
■Diagnostic Timing
• STOP RUN
[SFCP. OPE. ERROR]
The SFC program contains data that cannot be pro-
cessed.
■Collateral information
4600
• Common Information:Program error location
• Individual Information:–
■Diagnostic Timing
• When instruction executed
[SFCP. OPE. ERROR] RUN:
Exceeds device range that can be designated by Off/On
the SFC program. Read common information of the error using the ERR.:
Qn(H)
■Collateral information peripheral device, check error step corresponding Flicker/On
4601 QnPH
• Common Information:Program error location to its numerical value (program error location), and
QnPRH
• Individual Information:– correct the problem. CPU Status:
■Diagnostic Timing Stop/
*1 CPU operation can be set in the parameters at error occurrence. (LED indication varies.)
*2 The function version is B or later.
12 - 124
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[SFCP. EXE. ERROR]
The active step information at presumptive start of
the SFC program is incorrect.
■Collateral information
4610 • Common Information:Program error location
• Individual Information:– RUN:
Read common information of the error using the
■Diagnostic Timing On
peripheral device, check error step corresponding
• STOP RUN ERR.:
to its numerical value (program error location), and
On
[SFCP. EXE. ERROR] correct the problem.
Key-switch was reset during RUN when presump- The program is automatically subjected to an initial
CPU Status:
tive start was designated for SFC program. start.
Continue Qn(H)
■Collateral information
4611 QnPH
• Common Information:Program error location
QnPRH
• Individual Information:–
■Diagnostic Timing
• STOP RUN
[BLOCK EXE. ERROR]
Startup was executed at a block in the SFC pro-
gram that was already started up. Read common information of the error using the
■Collateral information peripheral device, check error step corresponding
4620
• Common Information:Program error location to its numerical value (program error location), and
• Individual Information:– correct the problem.
■Diagnostic Timing
• When instruction executed
[BLOCK EXE. ERROR] RUN:
Startup was attempted at a block that does not exist
• Read the common information of the error using Off Q00J/Q00/Q01*2
in the SFC program.
GX Developer, and check and correct the error ERR.: Qn(H)
■Collateral information
4621 step corresponding to that value (program error Flicker QnPH
• Common Information:Program error location
location). QnPRH
• Individual Information:–
• Turn ON if the special relay SM321 is OFF. CPU Status: QnU
■Diagnostic Timing
Stop
• When instruction executed
[STEP EXE. ERROR]
Startup was executed at a block in the SFC pro-
gram that was already started up. Read common information of the error using the
Qn(H)
■Collateral information peripheral device, check error step corresponding
4630 QnPH
• Common Information:Program error location to its numerical value (program error location), and
QnPRH
• Individual Information:– correct the problem.
■Diagnostic Timing
• When instruction executed
12 - 125
CHAPTER12 TROUBLESHOOTING
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[STEP EXE. ERROR]
• Startup was attempted at the step that does not
exist in the SFC program.
Or, the step that does not exist in the SFC pro-
gram was specified for end.
• Forced transition was executed based on the
• Read the common information of the error using Q00J/Q00/Q01*2
transition condition that does not exit in the SFC
the peripheral device, and check and correct the Qn(H)
program.
4631 error step corresponding to that value (program QnPH
Or, the transition condition for forced transition
error location). QnPRH
that does not exit in the SFC program was can-
• Turn ON if the special relay SM321 is OFF. QnU
celed.
■Collateral information
• Common Information:Program error location
RUN:
12
• Individual Information:–
Off
■Diagnostic Timing
ERR.:
• When instruction executed
Flicker
[STEP EXE. ERROR]
There were too many simultaneous active steps in
CPU Status:
blocks that can be designated by the SFC program.
Stop
■Collateral information
4632
• Common Information:Program error location
• Individual Information:–
■Diagnostic Timing Read common information of the error using the Qn(H)
• When instruction executed peripheral device, check error step corresponding QnPH
[STEP EXE. ERROR] to its numerical value (program error location), and QnPRH
There were too many simultaneous active steps in correct the problem. QnU
all blocks that can be designated.
■Collateral information
4633
• Common Information:Program error location
• Individual Information:–
■Diagnostic Timing
• When instruction executed
12 - 126
12.3.7 Error code list (5000 to 5999)
The following shows the error messages from the error code 5000 to 5999, the contents and
causes of the errors, and the corrective actions for the errors.
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[WDT ERROR]
• The scan time of the initial execution type pro-
• Read the individual information of the error from
gram exceeded the initial execution monitoring
the peripheral device, check its value (time), and
time specified in the PLC RAS setting of the PLC
shorten the scan time. Qn(H)
parameter.
• Change the initial execution monitoring time or QnPH
■Collateral information
the WDT value in the PLC RAS setting of the QnPRH
• Common Information:Time (value set)
PLC parameter. QnU
• Individual Information:Time (value actually mea-
• Resolve the endless loop caused by jump transi-
sured)
tion.
■Diagnostic Timing
• Always
[WDT ERROR]
5000 • The power supply of the standby system is
• Since power-off of the standby system increases
turned OFF.
the control system scan time, reset the WDT
• The tracking cable is disconnected or connected
value, taking the increase of the control system
without turning off or resetting the standby sys-
scan time into consideration.
tem.
• When the tracking cable is disconnected during
• The tracking cable is not secured by the connec-
operation, securely connect it and restart the QnPRH
tor fixing screws.
CPU module. If the same error is displayed
■Collateral information
again, the tracking cable or CPU module has a
• Common Information:Time (value set)
hardware fault. (Contact your local Mitsubishi
• Individual Information:Time (value actually mea- RUN:
representative, explaining a detailed description
sured) Off
of the problem.)
■Diagnostic Timing ERR.:
• Always Flicker
[WDT ERROR]
• The scan time of the program exceeded the • Read the individual information of the error using CPU Status:
WDT value specified in the PLC RAS setting of the peripheral device, check its value (time), and Stop
the PLC parameter. shorten the scan time.
■Collateral information • Change the initial execution monitoring time or
QCPU
• Common Information:Time (value set) the WDT value in the PLC RAS setting of the
• Individual Information:Time (value actually mea- PLC parameter.
sured) • Resolve the endless loop caused by jump transi-
■Diagnostic Timing tion.
• Always
[WDT ERROR]
• The power supply of the standby system is
5001 • Since power-off of the standby system increases
turned OFF.
the control system scan time, reset the WDT
• The tracking cable is disconnected or connected
value, taking the increase of the control system
without turning off or resetting the standby sys-
scan time into consideration.
tem.
• When the tracking cable is disconnected during
• The tracking cable is not secured by the connec-
operation, securely connect it and restart the QnPRH
tor fixing screws.
CPU module. If the same error is displayed
■Collateral information
again, the tracking cable or CPU module has a
• Common Information:Time (value set)
hardware fault. (Contact your local Mitsubishi
• Individual Information:Time (value actually mea-
representative, explaining a detailed description
sured)
of the problem.)
■Diagnostic Timing
• Always
12 - 127
CHAPTER12 TROUBLESHOOTING
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[PRG. TIME OVER]
The program scan time exceeded the constant
scan setting time specified in the PLC RAS setting
of the PLC parameter. Qn(H)
■Collateral information QnPH
• Common Information:Time (value set) QnPRH
• Individual Information:Time (value actually mea- QnU
sured)
• Review the constant scan setting time.
■Diagnostic Timing
• Review the constant scan setting time and low
• Always
speed program execution time in the PLC param-
[PRG. TIME OVER]
eter so that the excess time of constant scan can
The low speed program execution time specified in
the PLC RAS setting of the PLC parameter
be fully secured. 12
exceeded the excess time of the constant scan.
Qn(H)
■Collateral information
5010 QnPH
• Common Information:Time (value set)
QnPRH
• Individual Information:Time (value actually mea-
sured) RUN:
■Diagnostic Timing On
• Always ERR.:
[PRG. TIME OVER] On
The program scan time exceeded the constant
scan setting time specified in the PLC RAS setting CPU Status:
of the PLC parameter. Continue
Review the constant scan setting time in the PLC
■Collateral information
parameter so that the excess time of constant scan Q00J/Q00/Q01
• Common Information:Time (value set)
can be fully secured.
• Individual Information:Time (value actually mea-
sured)
■Diagnostic Timing
• Always
[PRG. TIME OVER]
The scan time of the low speed execution type pro-
gram exceeded the low speed execution watch
time specified in the PLC RAS setting of the PLC Read the individual information of the error using
parameter dialog box. the peripheral device, check the numerical value
12 - 128
12.3.8 Error code list (6000 to 6999)
The following shows the error messages from the error code 6000 to 6999, the contents and
causes of the errors, and the corrective actions for the errors.
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[FILE DIFF.]
In a redundant system, the control system and
standby system do not have the same programs
and parameters.
12 - 129
CHAPTER12 TROUBLESHOOTING
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[OPE. MODE DIFF.]
The operational status of the control system and
standby system in the redundant system is not the RUN:
same. On
(This can be detected from the standby system of ERR.:
Synchronise the operation statuses of the control
6010 the redundant system.) On
system and standby system.
■Collateral information
• Common Information:– CPU Status:
• Individual Information:– Continue
■Diagnostic Timing
• Always
[OPE. MODE DIFF.]
At power ON/reset, the RUN/STOP switch settings 12
of the control system and standby system are not
the same in a redundant system.
(This can be detected from the control system or
Set the RUN/STOP switches of the control system
6020 standby system of the redundant system.)
and standby system to the same setting.
■Collateral information
• Common Information:–
• Individual Information:–
■Diagnostic Timing
• At power ON/At reset
[UNIT LAY. DIFF.]
• In a redundant system, the module configuration
QnPRH
differs between the control system and standby
system.
• The network module mode setting differs RUN:
• Match the module configurations of the control
between the two systems. Off
system and standby system.
(This can be detected from the control system or ERR.:
6030 • In the redundant setting of the network parame-
standby system of the redundant system.) Flicker
ter dialog box, match the mode setting of System
■Collateral information
B to that of System A.
• Common Information:Module No. CPU Status:
• Individual Information:– Stop
■Diagnostic Timing
• At power ON/At reset/At tracking cable
12 - 130
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[UNIT LAY. DIFF.]
A difference in the remote I/O configuration of the
MELSECNET/H multiplexed remote I/O network
between the control system and standby system of
a redundant system was detected.
(This can be detected from the control system or Check the network cables of the MELSECNET/H
6036
standby system of the redundant system.) multiplexed remote I/O network for disconnection.
■Collateral information
• Common Information:Module No.
• Individual Information:–
■Diagnostic Timing
• Always
RUN:
[CARD TYPE DIFF.] Off
In a redundant system, the memory card installa-
ERR.:
tion status (installed/not installed) differs between
Flicker
the control system and standby system.
Match the memory card installation statuses (set/
6040 ■Collateral information
not set) of the control system and standby system. CPU Status:
• Common Information:–
Stop
• Individual Information:–
■Diagnostic Timing
• At power ON/At reset
[CARD TYPE DIFF.]
In a redundant system, the memory card type dif-
fers between the control system and standby sys-
tem.
Match the memory card types of the control system
6041 ■Collateral information
and standby system.
• Common Information:– QnPRH
• Individual Information:–
■Diagnostic Timing
• At power ON/At reset
[CAN'T EXE. MODE]
The function inexecutable in the debug mode or
operation mode (backup/separate mode) was exe- RUN:
cuted. On
(This can be detected from the control system or ERR.:
Execute the function executable in the debug mode
6050 standby system of the redundant system.) On
or operation mode (backup/separate mode).
■Collateral information
• Common Information:– CPU Status:
• Individual Information:– Continue
■Diagnostic Timing
• Always
[CPU MODE DIFF.]
In a redundant system, the operation mode
(backup/separate) differs between the control sys-
RUN:
tem and standby system.
Off
(This can be detected from the standby system of
ERR.:
the redundant system.) Match the operation modes of the control system
6060 Flicker
■Collateral information and standby system.
• Common Information:–
CPU Status:
• Individual Information:–
Stop
■Diagnostic Timing
• At power ON/At reset/At tracking cable connec-
tion
12 - 131
CHAPTER12 TROUBLESHOOTING
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[CPU MODE DIFF.]
In a redundant system, the operation mode
(backup/separate) differs between the control sys-
tem and standby system.
(This can be detected from the standby system of
Match the operation modes of the control system
6061 the redundant system.)
and standby system.
■Collateral information
• Common Information:–
RUN:
• Individual Information:–
Off
■Diagnostic Timing
ERR.:
• When an END instruction executed
Flicker
[CPU MODE DIFF.]
Both System A and B are in the same system sta- 12
CPU Status:
tus (control system).
Stop
(This can be detected from the system B of the
redundant system.)
Power the CPU module (System B) which resulted
6062 ■Collateral information
in a stop error, OFF and then ON.
• Common Information:–
• Individual Information:–
■Diagnostic Timing
• At power ON/At reset/At tracking cable
connection
[TRK. TRANS. ERR.]
• An error (e.g. retry limit exceeded) occurred in
tracking data transmission.
(This error may be caused by tracking cable
QnPRH
removal or other system power-off (including
reset).)
• The error occurred at a startup since the redun-
6100
dant system startup procedure was not followed.
■Collateral information
• Common Information:Tracking transmission data
classification
• Individual Information:–
• Check the CPU module or tracking cable. If the RUN:
■Diagnostic Timing
12 - 132
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[TRK. TRANS. ERR.]
A data sum value error occurred in tracking (data
reception).
(This can be detected from the control system or
standby system of the redundant system.)
6102
■Collateral information
• Common Information:–
• Individual Information:–
■Diagnostic Timing
• Always
[TRK. TRANS. ERR.]
• A data error (other than sum value error)
occurred in tracking (data reception).
(This error may be caused by tracking cable
removal or other system power-off (including
reset).)
• The error occurred at a startup since the redun-
6103 dant system startup procedure was not followed. • Check the CPU module or tracking cable. If the
(This can be detected from the control system or error still occurs, this indicates the CPU module
standby system of the redundant system.) or tracking cable is faulty. (Contact your local Mit-
■Collateral information subishi representative, explaining a detailed
• Common Information:– description of the problem.)
• Individual Information:– • Confirm the redundant system startup procedure,
■Diagnostic Timing and execute a startup again.
• Always
[TRK. TRANS. ERR.] RUN:
• An error (e.g. retry limit exceeded) occurred in On
tracking (data transmission). ERR.:
(This error may be caused by tracking cable On QnPRH
removal or other system power-off (including
reset).) CPU Status:
• The error occurred at a startup since the redun- Continue
dant system startup procedure was not followed.
6105
(This can be detected from the control system or
standby system of the redundant system.)
■Collateral information
• Common Information:Tracking transmission data
classification
• Individual Information:–
■Diagnostic Timing
• Always
[TRK. TRANS. ERR.]
• A timeout error occurred in tracking (data trans-
mission).
(This error may be caused by tracking cable
removal or other system power-off (including
• Check the CPU module or tracking cable. If the
reset).)
error still occurs, this indicates the CPU module
• The error occurred at a startup since the redun-
or tracking cable is faulty. (Contact your local Mit-
dant system startup procedure was not followed.
6106 subishi representative, explaining a detailed
(This can be detected from the control system or
description of the problem.)
standby system of the redundant system.)
• Confirm the redundant system startup procedure,
■Collateral information
and execute a startup again.
• Common Information:Tracking transmission data
classification
• Individual Information:–
■Diagnostic Timing
• Always
12 - 133
CHAPTER12 TROUBLESHOOTING
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[TRK. TRANS. ERR.]
A data sum value error occurred in tracking (data
reception).
(This can be detected from the control system or
standby system of the redundant system.)
6107
■Collateral information
• Common Information:–
• Individual Information:–
■Diagnostic Timing
• Always • Check the CPU module or tracking cable. If the
[TRK. TRANS. ERR.] error still occurs, this indicates the CPU module
• A data error (other than sum value error)
occurred in tracking (data reception).
or tracking cable is faulty. (Contact your local Mit-
subishi representative, explaining a detailed 12
(This error may be caused by tracking cable description of the problem.)
removal or other system power-off (including • Confirm the redundant system startup procedure,
reset).) and execute a startup again.
• The error occurred at a startup since the redun-
6108 dant system startup procedure was not followed.
(This can be detected from the control system or
standby system of the redundant system.)
■Collateral information
• Common Information:–
• Individual Information:–
■Diagnostic Timing
• Always
[TRK. SIZE ERROR] RUN:
The tracking capacity exceeded the allowed range. On
(This can be detected from the control system or ERR.:
standby system of the redundant system.) On QnPRH
■Collateral information
6110 Reexamine the tracking capacity.
• Common Information:Tracking capacity excess CPU Status:
error factor Continue
• Individual Information:–
■Diagnostic Timing
• When an END instruction executed
12 - 134
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[TRK. CABLE ERR.]
• A start was made without the tracking cable
being connected.
• A start was made with the tracking cable faulty.
RUN:
• As the tracking hardware on the CPU module Make a start after connecting the tracking cable. If
Off
side was faulty, communication with the other the same error still occurs, this indicates the track-
ERR.:
system could not be made via the tracking cable. ing cable or CPU module side tracking transmis-
6120 Flicker
(This can be detected from the control system or sion hardware is faulty.
standby system of the redundant system.) (Contact your local Mitsubishi representative,
CPU Status:
■Collateral information explaining a detailed description of the problem.)
Stop
• Common Information:–
• Individual Information:–
■Diagnostic Timing
• At power ON/At reset
[TRK. DISCONNECT]
• The tracking cable was removed.
• If the tracking cable was removed, connect the
• The tracking cable became faulty while the CPU
tracking cable to the connectors of the CPU mod-
module is running. RUN:
ules of the two systems.
• The CPU module side tracking hardware On
• When the error is not resolved after connecting
became faulty. ERR.:
the tracking cable to the connectors of the CPU
6130 (This can be detected from the control system or On
modules of the two systems and resetting the
standby system of the redundant system.)
error, the tracking cable or CPU module side
■Collateral information CPU Status:
tracking hardware is faulty.
• Common Information:– Continue
(Contact your local Mitsubishi representative,
• Individual Information:–
explaining a detailed description of the problem.)
■Diagnostic Timing
• Always
[TRK.INIT. ERROR]
• The other system did not respond during initial QnPRH
communication at power ON/reset. • Power the corresponding CPU module OFF and
RUN:
• The error occurred at a startup since the redun- then ON again, or reset it and then unreset. If the
Off
dant system startup procedure was not followed. same error still occurs, this indicates the CPU
ERR.:
(This can be detected from the control system or module is faulty. (Contact your local Mitsubishi
6140 Flicker
standby system of the redundant system.) representative, explaining a detailed description
■Collateral information of the problem.)
CPU Status:
• Common Information:– • Confirm the redundant system startup procedure,
Stop
• Individual Information:– and execute a startup again.
■Diagnostic Timing
• At power ON/At reset
[CONTROL EXE.]
The standby system has been switched to the con-
trol system in a redundant system. (Detected by the
CPU that was switched from the standby system to
the control system)
Since this error code does not indicate the error
RUN:
information of the CPU module but indicates its sta-
On
tus, the error code and error information are not
ERR.:
stored into SD0 to 26, but are stored into the error
6200 – Off
log every system switching.
(Check the error information by reading the error
CPU Status:
log using GX Developer.)
No error
■Collateral information
• Common Information:Reason(s) for system
switching
• Individual Information:–
■Diagnostic Timing
• Always
12 - 135
CHAPTER12 TROUBLESHOOTING
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[STANDBY]
The control system has been switched to the
standby system in a redundant system. (Detected
by the CPU that was switched from the control sys-
tem to the standby system)
Since this error code does not indicate the error
RUN:
information of the CPU module but indicates its sta-
On
tus, the error code and error information are not
ERR.:
stored into SD0 to 26, but are stored into the error
6210 – Off
log every system switching.
(Check the error information by reading the error
CPU Status:
log using GX Developer.)
■Collateral information
No error 12
• Common Information:Reason(s) for system
switching
• Individual Information:–
■Diagnostic Timing
• Always
[CAN'T SWITCH]
System switching cannot be executed due to
standby system error/ tracking cable error/ online
module change in execution at separate mode.
RUN:
Causes for switching system at control system are
On
as follows:
• Check the status of the standby system and ERR.: QnPRH
• System switching by SP. CONTSW instruction
6220 resolve the error. On
• System switching request from network module
• Complete the online module change.
■Collateral information
CPU Status:
• Common Information:Reason(s) for system switching
No error
• Individual Information:Reason(s) for system switching
failure
■Diagnostic Timing
• At switching execution
[STANDBY SYS. DOWN]
Any of the following errors was detected in the
backup mode. • Check whether the standby system is on or not,
12 - 136
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
• The standby system exists but the control system
[CONTROL SYS. DOWN] does not exist.
Any of the following errors was detected in the • Check whether the system other than the
backup mode. standby system is on or not, and if it is not on,
• The control system has not started up in the power it on.
redundant system. • Check whether the system other than the
• The control system has developed a stop error in standby system has been reset or not, and if it is
RUN:
the redundant system. has been reset, unreset it.
Off
• The CPU module in the debug mode was con- • Check whether the system other than the
ERR.:
nected to the operating standby system. standby system has developed a stop error or
6310 Flicker
• The error occurred at a startup since the redun- not, and if has developed the error, remove the
dant system startup procedure was not followed. error factor, set the control system and standby
CPU Status:
(This can be detected from the standby system of system to the same operating status, and restart.
Stop
the redundant system.) • When the CPU module in the debug mode was
■Collateral information connected to the control system operating in the
• Common Information:– backup mode, make connection so that the con-
• Individual Information:– trol system and control system are combined cor-
QnPRH
■Diagnostic Timing rectly.
• Always • Confirm the redundant system startup procedure,
and execute a startup again.
6311 [CONTROL SYS. DOWN]
• As consistency check data has not transmitted
from the control system in a redundant system,
the other system cannot start as a standby sys-
RUN:
tem. • Replace the tracking cable. If the same error still
Off
• The error occurred at a startup since the redun- occurs, this indicates the CPU module is faulty.
ERR.:
dant system startup procedure was not followed. (Contact your local Mitsubishi representative,
Flicker
6312 (This can be detected from the standby system of explaining a detailed description of the problem.)
the redundant system.) • Confirm the redundant system startup procedure,
CPU Status:
■Collateral information and execute a startup again.
Stop
• Common Information:–
• Individual Information:–
■Diagnostic Timing
• At power ON/At reset
[CONTROL SYS. DOWN]
The control system detected the error of the system RUN:
configuration and informed it to the standby system Off
Restart the system after checking that the connec-
(host system) in the redundant system. ERR.:
tion between base unit and the system configura-
6313 ■Collateral information Flicker QnPRH*1
tion (type/number/parameter of module) are
• Common Information:–
correct.
• Individual Information:– CPU Status:
■Diagnostic Timing Stop
• At power ON/At reset
[PRG. MEM. CLEAR]
The memory copy from control system to standby
RUN:
system was executed, and the program memory
Off
was cleared.
After the memory copy from control system to ERR.:
■Collateral information
6400 standby system is completed, switch power OFF Flicker QnPRH
• Common Information:–
and then ON, or make a reset.
• Individual Information:–
CPU Status:
■Diagnostic Timing
Stop
• At execution of the memory copy from control
system to standby system
12 - 137
CHAPTER12 TROUBLESHOOTING
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[MEM.COPY EXE]
The memory copy from control system to standby
system was executed. RUN:
(This can be detected from the control system of On
the redundant system.) ERR.:
6410 ■Collateral information – On
• Common Information:–
• Individual Information:– CPU Status:
■Diagnostic Timing Continue
• At execution of the function of copying memory
from control system to standby system
[TRK. PARA. ERROR]
The file register file specified in the tracking setting 12
of the PLC parameter dialog box does not exist.
Read the individual information of the error using
■Collateral information QnPRH
6500 GX Developer, and check and correct the drive
• Common Information:File name/Drive name
name and file name. Create the specified file.
• Individual Information:Parameter number
RUN:
■Diagnostic Timing
Off
• At power ON/At reset
ERR.:
[TRK. PARA. ERROR]
Flicker
The file register range specified in the device detail
setting of the tracking setting of the PLC parameter
CPU Status:
dialog box exceeded the specified file register file
Read the individual information of the error using Stop
capacity.
6501 GX Developer, and increase the file register capac-
■Collateral information
ity.
• Common Information:File name/Drive name
• Individual Information:Parameter number
■Diagnostic Timing
• At power ON/At reset
12 - 138
12.3.9 Error code list (7000 to 10000)
The following shows the error messages from the error code 7000 to 10000, the contents and
causes of the errors, and the corrective actions for the errors.
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[MULTI CPU DOWN]
• In the operating mode of a multiple CPU system,
a CPU error occurred at the CPU where "All sta-
tion stop by stop error of CPU " was selected. • Read the individual information of the error using
• In a multiple CPU system, a CPU module incom- GX Developer, identify the error of the CPU mod-
patible with the multiple CPU system was Q00/Q01*1
ule, and remove the error.
mounted.
• CPU modules other than CPU No.1 were
• Remove the CPU module incompatible with the Qn(H)*1
removed from the base unit in operation, or multiple CPU system from the main base unit. QnPH
reset. • Check the mounting status of CPU modules QnU*6
■Collateral information other than CPU No.1 and whether the CPU mod-
• Common Information:Module No.(CPU No.) ules were reset.
• Individual Information:–
7000
■Diagnostic Timing
• Always
[MULTI CPU DOWN]
In a multiple CPU system, CPU other than CPU
No.1 cannot be started up due to stop error of the
CPU No.1 at power-on, which occurs to CPU No.2 Q00/Q01*1
Read the individual information of the error using
to No.4. Qn(H)*1
GX Developer, identify the error of the CPU mod-
■Collateral information QnPH
ule, and remove the error.
• Common Information:Module No.(CPU No.) QnU*6
• Individual Information:–
■Diagnostic Timing
• At power ON/At reset RUN:
[MULTI CPU DOWN] Off
• There is no response from the target CPU mod- • Reset the CPU module and RUN it again. If the ERR.:
ule in a multiple CPU system during initial com- same error is displayed again, this suggests the Flicker
munication.
hardware fault of any of the CPU modules. (Con-
• In a multiple CPU system, a CPU module incom-
tact your local Mitsubishi representative.) CPU Status: Q00/Q01*1
patible with the multiple CPU system was
• Remove the CPU module incompatible with the Stop Qn(H)*1
mounted.
■Collateral information multiple CPU system from the main base unit. QnPH
• Common Information:Module No.(CPU No.) Or, replace the CPU module incompatible with
• Individual Information:– the multiple CPU system with the compatible
■Diagnostic Timing one.
7002
• At power ON/At reset
[MULTI CPU DOWN]
• There is no response from the target CPU mod-
ule in a multiple CPU system during initial com-
• Reset the CPU module and RUN it again. If the
munication.
same error is displayed again, this suggests the
■Collateral information QnU*6
hardware fault of any of the CPU modules. (Con-
• Common Information:Module No.(CPU No.)
tact your local Mitsubishi representative.)
• Individual Information:–
■Diagnostic Timing
• At power ON/At reset
[MULTI CPU DOWN]
There is no response from the target CPU module
in a multiple CPU system at initial communication
Reset the CPU module and RUN it again. If the
stage. Q00/Q01*1
same error is displayed again, this suggests the
7003 ■Collateral information Qn(H)*1
hardware fault of any of the CPU modules. (Contact
• Common Information:Module No.(CPU No.) QnPH
your local Mitsubishi representative.)
• Individual Information:–
■Diagnostic Timing
• At power ON/At reset
12 - 139
CHAPTER12 TROUBLESHOOTING
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[MULTI CPU DOWN] • Check the system configuration to see if modules
RUN:
In a multiple CPU system, a data error occurred in are mounted in excess of the number of I/O
Off
communication between the CPU modules. points.
ERR.:
■Collateral information • When there are no problems in the system con- Q00/Q01*1
7004 Flicker
• Common Information:Module No.(CPU No.) figuration, this indicates the CPU module hard- QnU*6
• Individual Information:– ware is faulty. (Contact your local Mitsubishi
CPU Status:
■Diagnostic Timing representative, explaining a detailed description
Stop
• Always of the problem.)
[MULTI EXE. ERROR]
• In a multiple CPU system, a faulty CPU module
was mounted.
• In a multiple CPU system, a CPU module incom-
patible with the multiple CPU system was • Read the individual information of the error using
12
mounted. (The CPU module compatible with the RUN:
GX Developer, and replace the faulty CPU mod-
multiple CPU system was used to detect an Off
ule. Q00/Q01*1
error.) ERR.:
• In a multiple CPU system, any of the CPU No. 2
• Replace the CPU module with the one compati- Qn(H)*1
Flicker
to 4 was reset with power ON. (The CPU whose ble with the multiple CPU system. QnPH
reset state was cancelled was used to detect an • Do not reset any of the No. 2 to 4 CPU modules. QnU*6
CPU Status:
error.) • Reset CPU No. 1 and restart the multiple CPU
Stop
■Collateral information system.
• Common Information:Module No.(CPU No.)
• Individual Information:–
■Diagnostic Timing
• At power ON/At reset
[MULTI EXE. ERROR]
The PC CPU module-compatible software package RUN:
(PPC-DRV-01)*5 whose version is 1.06 or earlier is Off
used in a multiple CPU system. Change the version of the PC CPU module-com- ERR.:
■Collateral information patible software package (PPC-DRV-01)*5 to 1.07 Flicker Q00/Q01*1
• Common Information:Module No.(CPU No.) or later.
7010
• Individual Information:– CPU Status:
■Diagnostic Timing Stop
• At power ON/At reset
[MULTI EXE. ERROR]
12 - 140
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[MULTI EXE. ERROR]
Either of the following settings was made in a multi-
ple CPU system.
RUN:
• Multiple CPU automatic refresh setting was
Off
made for the inapplicable CPU module. • Correct the multiple CPU automatic refresh set-
ERR.:
• "I/O sharing when using multiple CPUs" setting ting. Q00/Q01*1
Flicker
was made for the inapplicable CPU module. • Correct the "I/O sharing when using multiple QnU*6
■Collateral information CPUs" setting.
CPU Status:
• Common Information:Module No.(CPU No.)
Stop
• Individual Information:–
■Diagnostic Timing
• At power ON/At reset
[MULTI EXE. ERROR]
The system configuration for using the Multiple
7011 CPU high speed transmission function is not met.
• The QnUCPU is not used for the CPU No.1.
• The Multiple CPU high speed main base unit
(Q3 DB) is not used. • Change the system configuration to meet the RUN:
• Points other than 0 is set to the send range for conditions for using the Multiple CPU high speed Off
the CPU module incompatible with the multiple transmission function. ERR.:
CPU high speed transmission function. • Set the send range of CPU, that does not corre- Flicker QnU*3
• Points other than 0 is set to the send range for spond to multiple CPU compatible area, at 0
the CPU module incompatible with the multiple point, when performing automatic refreshing in CPU Status:
CPU. multiple CPU compatible area. Stop
■Collateral information
• Common Information:Module No.(CPU No.)
• Individual Information:–
■Diagnostic Timing
• At power ON/At reset
[MULTI EXE. ERROR]
The Q172(H)CPU(N) or Q173(H)CPU(N) is RUN:
mounted to the CPU slot or slots 0 to 2. (The mod- • Check the QCPU and Motion CPU that can be Off
ule may break down.) used in a multiple CPU system, and change the ERR.:
7013 ■Collateral information system configuration. Flicker QnU
• Common Information:Module No.(CPU No.) • Remove the Motion CPU incompatible with the
• Individual Information:– multiple CPU system. CPU Status:
■Diagnostic Timing Stop
• At power ON/At reset
[MULTI CPU ERROR]
In the operating mode of a multiple CPU system, an
error occurred in the CPU where "system stop" was RUN:
not selected. On
Read the individual information of the error using Q00/Q01*1
(The CPU module where no error occurred was ERR.:
the peripheral device, check the error of the CPU Qn(H)*1
7020 used to detect an error.) On
module resulting in CPU module fault, and remove QnPH
■Collateral information
the error. QnU*6
• Common Information:Module No.(CPU No.) CPU Status:
• Individual Information:– Continue
■Diagnostic Timing
• Always
[CPU LAY. ERROR]
An assignment error occurred in the CPU-mount- • Set the same value to the number of CPU mod- RUN:
able slot (CPU slot, I/O slot 0, 1) in excess of the ules specified in the multiple CPU setting of the Off
number of CPU modules specified in the multiple PLC parameter dialog box and the number of ERR.:
CPU setting of the PLC parameter dialog box. Q00J/Q01/Q01*1
7030 mounted CPU modules (including CPU (empty)). Flicker
■Collateral information QnU
• Common Information:Module No.(CPU No.) • Make the type specified in the I/O assignment
• Individual Information:– setting of the PLC parameter dialog box consis- CPU Status:
■Diagnostic Timing tent with the CPU module configuration. Stop
• At power ON/At reset
12 - 141
CHAPTER12 TROUBLESHOOTING
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
[CPU LAY. ERROR] • Set the same value to the number of CPU mod-
RUN:
An assignment error occurred within the range of ules specified in the multiple CPU setting of the
Off
the number of CPUs specified in the multiple CPU PLC parameter dialog box and the number of
setting of the PLC parameter dialog box. ERR.:
mounted CPU modules (including CPU (empty)). Q00J/Q01/Q01*1
7031 ■Collateral information Flicker
• Common Information:Module No.(CPU No.) • Make the type specified in the I/O assignment QnU
• Individual Information:– setting of the PLC parameter dialog box consis-
CPU Status:
■Diagnostic Timing tent with the CPU module configuration.
• At power ON/At reset Stop
CPU Status:
Continue
12 - 142
Error
LED Status Corresponding
Code Error Contents and Cause Corrective Action
CPU Status CPU
(SD0)
RUN:
[<CHK>ERR ***-***]
On
Error detected by the CHK instruction.
Read the individual information of the error using ERR.:
■Collateral information Qn(H)
the peripheral device, and check the program cor- Off
9010 • Common Information:Program error location QnPH
responding to the numerical value (error number) USER LED On
• Individual Information:Failure No. QnPRH
there.
■Diagnostic Timing
CPU Status:
• When instruction executed
Continue
[BOOT OK]
Storage of data onto ROM was completed normally RUN:
in automatic write to standard ROM. Off
Use the DIP switches to set the valid parameter
(BOOT LED also flickers.) ERR.: Qn(H)*1
drive to the standard ROM. Then, switch power on
9020 ■Collateral information Flicker QnPH
again, and perform boot operation from the stan-
• Common Information:– QnPRH
dard ROM.
• Individual Information:– CPU Status:
■Diagnostic Timing Stop
• At power ON/At reset
[CONT. UNIT ERROR]
In the multiple CPU system, an error occurred in RUN:
the CPU module other than the Process CPU/High Off
Performance model QCPU. Check the details of the generated error by con- ERR.:
Qn(H)*1
10000 ■Collateral information necting to the corresponding CPU module using Flicker
QnPH
• Common Information:– GX Developer.
• Individual Information:– CPU Status:
■Diagnostic Timing Continue
• Always
12 - 143
CHAPTER12 TROUBLESHOOTING
Q series CPU module can perform the cancel operation for errors only when the errors allow
the CPU module to continue its operation.
To cancel the errors, follow the steps shown below.
(1) When the error is canceled with the error code to be canceled stored in the SD50, the lower one digit of the code is
neglected.
(Example)
12 - 144
Memo
12 - 145
CHAPTER12 TROUBLESHOOTING
12.3.11 Error codes returned to request source during communication with CPU
module
The Q series CPU module returns an error code to the request source if an error occurs at a
request of communication from GX Developer, intelligent function module or network system.
This error code is not an error that is detected by the CPU module self-diagnosis function, so it is not stored in the special
relay (SD0).
When the request source is a GX Developer, a message or an error code is displayed.
When the request source is an intelligent function module or network system, an error is returned to the process that was
requested.
12
The error contents of the error codes (4000H to 4FFFH) detected by the CPU module and the
messages displayed by the GX Developer are shown in .
12.3.11 Error codes returned to request source during communication with CPU module
12.3 Error Code List
Any operation for the CPU module is prohibited
• Set the system protect switch of the CPU module to
Common error by the system protect function provided against
OFF.
4004H the following events.
• Perform operation again after the CPU module has
• The system protect switch is ON.
completed starting.
• The CPU module is starting.
The volume of data handled according to the
4005H Check the command data of the MC protocol, etc.
specified request is too large.
• Check with the external device maker for the support
condition.
4006H Serial communication could not be initialized.
• Check the CPU module model name selected in the
peripheral device.
The CPU module is BUSY.
4008H After the free time has passed, reexecute the request.
(The buffer is not vacant).
Since the CPU module is running, the request
4010H Execute after setting the CPU module to STOP status.
CPU mode contents cannot be executed.
error Since the CPU module is not in a STOP status,
4013H Execute after setting the CPU module to STOP status.
the request contents cannot be executed.
12 - 146
Table12.2 Error code
Error code
Error item Error details Corrective action
(Hexadecimal)
• Check the specified drive memory status.
The specified drive memory does not exist or
4021H • After backing up the data in the CPU module, execute
there is an error.
programmable controller memory format.
The file with the specified file name or file No.
4022H Check the specified file name and file No.
does not exist.
The file name and file No. of the specified file do
4023H Delete the file and then recreate the file.
not match.
4024H The specified file cannot be handled by a user. Do not access the specified file.
Forcibly execute the request, or make the request again after
The specified file is processing the request from
4025H the processing from the other peripheral device is com-
the other peripheral device.
pleted.
The file password or drive keyword set to the tar- Make access after specifying the file password or drive key-
4026H
get drive (memory) must be specified. word set to the target drive (memory).
CPU file related
4027H The specified range exceeds the file range. Check the specified range and access within that range.
error
Forcefully execute the request forcibly.
4028H The same file already exists.
Or reexecute after changing the file name.
Revise the specified file contents.
4029H The specified file capacity cannot be obtained. Or reexecute after cleaning up and reorganizing the speci-
fied drive memory.
After backing up the data in the CPU module, execute pro-
402AH The specified file is abnormal.
grammable controller memory format.
Execute again after setting the CPU module to the STOP
The request contents cannot be executed in the status.
402BH
specified drive memory. Execute programmable controller memory arrangement to
increase the continuous free space of the drive (memory).
The requested operation cannot be executed cur-
402CH Execute again after a while.
rently.
4030H The specified device name cannot be handled. Check the specified device name.
• Check the specified device No.
4031H The specified device No. is outside the range. • Check the device assignment parameters of the CPU
module.
There is a mistake in the specified device qualifi-
cation.
The unusable device name • Check the specified device qualification method.
4032H
CPU device (TS,TC,SS,SC,CS,CC) must be specified in MC • Check the specified device name.
specified error protocol random reading, random writing (word),
monitor registeration and monitor command.
Writing cannot be done because the specified Do not write the data in the specified device, and do not turn
4033H
device is for system use. on or off.
Since the completion device for the target station CPU mod-
Cannot be executed since the completion device
ule cannot be turned ON by the SREAD instruction/SWRITE
4034H for the dedicated instruction cannot be turned
instruction, execute again after setting the operating status of
ON.
the target station CPU module to the RUN status.
12 - 147
CHAPTER12 TROUBLESHOOTING
12.3.11 Error codes returned to request source during communication with CPU module
12.3 Error Code List
The online debug function is being executed by • When the operation was suspended by the other
4060H
the other peripheral device. peripheral device, execute the function again after
executing it on the other peripheral device to normally
complete the operation.
• Execute communication after the registering the online
debug function (e.g.online program change/trace/con-
Online registra- Communication of the online debug function was
4061H ditional monitor).
tion error unsuccessful.
• Execute again after checking the communication route
such as the communication cable.
The registered number of locked files exceeded Execute again after file access by the other peripheral device
4063H
the maximum value. has ended.
• Check the set data of the online debug function (e.g.
The specified data of the online debug function is online program change/trace/conditional monitor).
4064H
incorrect. • Execute again after checking the communication route
such as the communication cable.
12 - 148
Table12.2 Error code
Error code
Error item Error details Corrective action
(Hexadecimal)
The device allocation information differs from the Check the device assignment parameters of the CPU mod-
4065H
parameter. ule or the device assignment of the request data.
The specified drive keyword/file password is • Correct the drive keyword of the specified drive.
4066H
wrong. • Correct the file password of the specified file.
• Check the system area capacity of the user setting
Online registra- specified for programmable controller memory format.
4067H Monitor communication was unsuccessful.
tion error • Execute again after checking the communication route
such as the communication cable.
Operation is disabled since the same operation is Execute the function again after the operation from the other
4068H
being executed from the other peripheral device. peripheral device has been ended.
The drive (memory) number that cannot be han-
406AH Check the specified drive and specify the correct drive.
dled (other than 0 to 4) was specified.
Execute Read from PLC to make the program of the periph-
Circuit inquiry The program not yet corrected and the one cor-
4070H eral device the same as that of the CPU module, and then
error rected by online program change are different.
execute online program change again.
4080H Request data error Check the request data specified in the MC protocol, etc.
4081H The sort subject cannot be detected. Check the data to be searched.
The specified command is executing and there- Execute the command again after the request from the other
4082H
fore cannot be executed. peripheral device is completed.
An attempt was made to perform operation for the
4083H Register the program to the parameters.
program not registered to the parameters.
4084H The specified pointer P, I did not exist. Check the pointer P, I in the specified data.
Pointer P, I cannot be specified because the pro- Specify pointer P, I after registering the program to be exe-
4085H
gram is not specified in the parameter. cuted in the parameter.
Other errors
4086H Pointer P, I has already been added. Check the pointer No. to be added and make correction.
4087H Trying to specify too many pointer P, I. Check the specified pointer P, I and make a correction.
• The specified step No. is not the start of the • Check and correct the specified step No.
instruction. • Read from PLC to make the program of the peripheral
4088H
• Program stored in the CPU is different from device the same as that of the CPU module, and write
the relevant program. to PLC during RUN again.
• Check the specified program file contents.
An attempt was made to insert/delete the END
4089H • Write the program after setting the CPU module to the
instruction by online program change.
STOP status.
12 - 149
CHAPTER12 TROUBLESHOOTING
408CH
An attempt was made to remote-start the pro-
gram, which uses the CHK instruction, as a low
• The program including the CHK instruction cannot be
executed at low speed. Execute again after checking
12
speed program. the program.
• Check whether the model of the used CPU module is
correct or not.
Other errors
• The sequence program where online program change
The instruction code that cannot be handled
408DH was attempted includes the instruction that cannot be
exists.
handled by the CPU module model name set in the
project. Reexamine the sequence program and delete
that instruction.
• Write the program after setting the CPU module to the
STOP status.
• The starting position of online program change is not
408EH The write step is illegal. specified with the correct program step No. Check
whether the used peripheral device supports the CPU
module model name and CPU module version set in
the project.
40A0H A block No. outside the range was specified. Check the setting contents and make a correction.
A number of blocks that exceeds the range was
40A1H Check the number of settings and make a correction.
12.3.11 Error codes returned to request source during communication with CPU module
12.3 Error Code List
specified.
A step No. that is outside the range was speci-
40A2H Check the setting contents and make a correction.
SFC device fied.
40A3H specification Step range limit exceeded Check the number of settings and make a correction.
error The specified sequence step No. is outside the
40A4H Check the setting contents and make a correction.
range.
40A5H The specified device is outside the range. Check the number of settings and make a correction.
The block specification pattern and step specifi-
40A6H Check the setting contents and make a correction.
cation pattern were wrong.
The drive (memory) specified in SFC file opera-
40B0H Check the setting contents and make a correction.
tion is wrong.
The SFC program specified in SFC file operation
40B1H Check the specified file name and make a correction.
does not exist.
The program specified in SFC file operation is not
40B2H Check the specified file name and make a correction.
an SFC program.
SFC file related
Using online program change of SFC, an attempt
error
was made to execute rewrite operation of the
"SFC dedicated instruction", such as the "STEP
Write the program after setting the CPU module to the STOP
40B3H start instruction or transition start instruction", that
status.
shows an SFC chart.
(SFC dedicated instruction cannot be written dur-
ing RUN.)
12 - 150
Table12.2 Error code
Error code
Error item Error details Corrective action
(Hexadecimal)
4100H CPU module hardware fault Change the CPU module.
Serial communication connection was executed
4101H Check the CPU module series.
for a different CPU module series.
An attempt was made to erase the Flash ROM Execute again after setting the CPU module to the STOP
4102H
during use of the file register. status.
The instruction written during RUN is wrong or Execute online program change again, or write the program
4103H
illegal. after setting the CPU module to the STOP status.
4105H CPU module internal memory hardware fault Change the CPU module.
The command cannot be executed since the CPU
Execute the operation again after the CPU module has
4106H module is performing system initialization pro-
started.
cessing.
Other errors An attempt was made to perform the operation of
Do not execute the function unsupported by the target CPU
4107H the function unavailable for the target CPU mod-
module.
ule model name.
Operation cannot be made normally by device Execute device monitor/test again. Before execution, check
4108H
monitor/test. that access is not made to the access prohibited area.
The specified operation cannot be executed since
Execute the request again after deregistering the monitoring
4109H the monitoring, set the condition for other appli-
condition on the same screen.
cation in same computer, is in execution.
The specified command cannot be executed
410AH Execute the request again after the online program change.
because of online prgram change.
The registration of monitoring condition was can- Execute the registration of monitoring condition again after
410BH
celed because of online program change. the online program change.
Since the CPU module is in a stop error status, it
4110H Execute the request again after resetting the CPU module.
cannot execute the request.
CPU mode
The requested operation cannot be performed
error Execute the request again after the other CPU modules have
4111H since the other CPU modules have not yet started
started.
in the multiple CPU system.
12 - 151
CHAPTER12 TROUBLESHOOTING
Error code
Error item Error details Corrective action
(Hexadecimal)
The specified drive (memory) or file does not Execute again after checking the specified drive (memory) or
4121H
exist. file.
The specified drive (memory) or file does not Execute again after checking the specified drive (memory) or
4122H
exist. file.
Execute programmable controller memory format to make
the drive (memory) normal.
4123H The specified drive (memory) is abnormal.
In the case of the Flash ROM, check the data to be written to
the Flash ROM, and write them to the Flash ROM.
Execute programmable controller memory format to make
the drive (memory) normal.
4124H The specified drive (memory) is abnormal.
In the case of the Flash ROM, check the data to be written to 12
the Flash ROM, and write them to the Flash ROM.
The specified drive (memory) or file is performing
4125H Execute again after a while.
processing.
The specified drive (memory) or file is performing
4126H Execute again after a while.
processing.
4127H File password mismatch Execute again after checking the file password.
4128H File password mismatch with copy destination Execute again after checking the file password.
Cannot be executed since the specified drive
4129H Execute again after changing the target drive (memory).
(memory) is ROM.
Cannot be executed since the specified drive
412AH Execute again after changing the target drive (memory).
(memory) is ROM.
Execute again after changing the write inhibit condition or
412BH The specified drive (memory) is write-inhibited.
drive (memory).
File-related
Execute again after changing the write inhibit condition or
412CH errors The specified drive (memory) is write-inhibited.
drive (memory).
File-related
The specified drive (memory) does not have Execute again after increasing the free space of the drive
412DH errors
enough free space. (memory).
The specified drive (memory) does not have Execute again after increasing the free space of the drive
412EH
12.3.11 Error codes returned to request source during communication with CPU module
12.3 Error Code List
enough free space. (memory).
The drive (memory) capacity differs between the
Execute again after checking the drive (memory) copy desti-
412FH drive (memory) copy destination and copy
nation and copy source.
source.
The drive (memory) type differs between the drive Execute again after checking the drive (memory) copy desti-
4130H
(memory) copy destination and copy source. nation and copy source.
The file name of the file copy destination is the
4131H Execute again after checking the file names.
same as that of the copy source.
4132H The specified number of files does not exist. Execute again after checking the specified data.
Execute again after increasing the free space of the drive
4133H The specified drive (memory) has no free space.
(memory).
The attribute specification data of the file is
4134H Execute again after checking the specified data.
wrong.
The date/time data of the peripheral device (per- Execute again after checking the clock setting of the periph-
4135H
sonal computer) is beyond the range. eral device (personal computer).
4136H The specified file already exists. Execute again after checking the specified file name.
Execute again after changing the condition of the specified
4137H The specified file is read-only.
file.
Simultaneously accessible files exceeded the
4138H Execute again after decreasing file operations.
maximum.
The specified file has exceeded the already exist-
4139H Execute again after checking the size of the specified file.
ing file range.
12 - 152
Table12.2 Error code
Error code
Error item Error details Corrective action
(Hexadecimal)
The specified file has exceeded the already
413AH Execute again after checking the size of the specified file.
existing file size.
The same file was accessed simultaneously from
413BH Execute again after a while.
different peripheral devices.
File-related
413CH The specified file is write-inhibited. Execute again after changing the file condition.
errors
Execute again after increasing the capacity of the specified
413DH File-related The specified file capacity cannot be secured.
drive (memory).
errors
Operation is disabled for the specified drive
413EH Execute again after changing the target drive (memory).
(memory).
The file is inhibited from write to the standard
413FH Execute again after changing the specified drive (memory).
RAM.
Operation was executed for the intelligent func-
Intelligent func- Execute the operation again from the control CPU of the tar-
414AH tion module of the non-control group in the multi-
tion module get module.
ple CPU system.
specification
The I/O address of the specified CPU module is Execute again after checking the I/O address of the specified
414CH error
wrong. CPU module.
An attempt was made to format the drive pro- Do not format the target drive (memory) as it cannot be for-
4150H
File-related tected by the system. matted.
errors An attempt was made to delete the file protected
4151H Do not delete the target file as it cannot be deleted.
by the system.
The registered number of forced inputs/outputs
4160H Deregister the unused forced inputs/outputs.
exceeded the maximum value.
Execute again after securing the area that enables multiple-
The multiple-block online change system file does
4165H block online change at the time of programmable controller
not exist.
memory format.
Since the file batch online change executed previously
Cannot be executed since file batch online remains abnormally terminated for some reason (example:
4166H change is being made by the same starting communication disturbance during execution), file batch
source. online change is disabled.
Forcibly perform new file batch online change.
Since the file batch online change executed previously from
the other communication route remains abnormally termi-
Cannot be executed since file batch online nated for some reason (example: communication distur-
4167H Online registra- change is being made from the other starting bance during execution), file batch online change is disabled.
tion error source. If file batch online change is not being executed by the other
peripheral device, forcibly perform new file batch online
change.
Deregister the device test with executing condition in CPU
The registered number of device test with execut-
4168H module, or decrease the number of registering device test
ing condition exceeds 32.
with executing condition at one time.
Deregister the device test with executing condition after
The device test with executing condition has
4169H checking the registered number of device test with executing
never been registered.
condition in CPU module.
Check whether the specified executing conditions (program,
The specified executing condition does not exist.
416AH step No. operation timing, device name) in deregistering are
(Device test with executing condition)
registered.
The specified program is SFC program. (Device Check the specifing program name in de/registering the
416BH
test with executing condition) device test with executing condition.
12 - 153
CHAPTER12 TROUBLESHOOTING
12.3.11 Error codes returned to request source during communication with CPU module
12.3 Error Code List
If the error is shown once again, the CPU module hardware
must be abnormal. Please contact with system service sta-
tions, agencies, or branch offices nearby and consult forl the
problems.
• Check the receiving module operation.
• Check the status of the lines, such as cables, hubs
Transmission to the receiving modules is unsuc-
4181H and routes,connected to receiving modules.
cessful.
• Some line packets may be engaged. Retry to commu-
nicate a little while later.
• Check the receiving module operation.
• Check the status of the lines such as a cable, a hub
Communication with receiving modules caused a
4182H and a route to receiving modules.
time-out error.
• Some line packets may be engaged. Retry to commu-
nicate a little while later.
• Check the receiving module operation.
Communication with receiving modules was inter-
4183H • Check the status of the lines such as cables, hubs and
rupted.
routes connected to receiving modules.
12 - 154
Table12.2 Error code
Error code
Error item Error details Corrective action
(Hexadecimal)
• Communication processing buffer has been
ran out since requests were consecutively
received in MC protocol. • For MC protocol, send a request after receiving a
• Communication processing buffer has been response to the previous request.
4184H ran out since received data read is not per- • For socket communication, enable received data read.
formed or cannot keep up with the volume. • For socket communication, decrease the number of
• Communication processing is not available data sent from the target device.
since the communication processing buffer
has been ran out.
• For MC protocol, keep the connection until a response
• The connection to the target device is dis- is sent.
connected before sending a response using • Keep the connection until a sequence of communica-
4185H MC protocol tion is completed.
• The connection to the target device is dis- • Other error such as 4184H may be the cause. If any
connected during communication other error has occurred, take corrective action of that
error.
System error (The argument data in OS is abnor-
4186H
mal.)
System error (The wait processing in OS is
4187H
abnormal.)
4188H System error (The data length in OS is abnormal.)
System error (The protocol information in OS is
4189H
abnormal.)
System error (The address data of communicat-
418AH
Ethernet ing module in OS is abnormal.)
I/F System error (The protocol information in OS is
418BH
Error abnormal.)
System error (The protocol specification process-
418CH
ing in OS is abnormal.)
• Check whether the power module and programmable
System error
418DH controller CPU are attached properly.
(The typed data in OS is abnormal.)
• Check whether the system use environment is within
System error (The expedited data processing in
418EH the range of the programmable controller CPU
OS is abnormal.)
genaral specifications.
418FH System error (The protocol information in OS is
• Check whether the power capacity is sufficient.
4190H abnormal.)
• Reset the CPU module.
System error (The address data of communicat-
4191H If the error is shown once again, the CPU module hardware
ing module in OS is abnormal.)
is abnormal. Please contact with system service, agency, or
System error (The host module address process-
4192H branch office nearby and tell the problems.
ing in OS is abnormal.)
4193H to System error (The transmission processing in OS
4196H is abnormal.)
4197H System error (The connection processing in OS is
4198H abnormal.)
System error (The connection termination pro-
4199H
cessing is abnormal.)
System error (The connection processing in OS is
419AH
abnormal.)
System error (The connection termination pro-
419BH
cessing is abnormal.)
419CH System error (The processing order in OS is
419DH abnormal.)
12 - 155
CHAPTER12 TROUBLESHOOTING
12.3.11 Error codes returned to request source during communication with CPU module
12.3 Error Code List
41A3H
station No. and the same destination port • Review port numbers of the Built-in Ethernet port
No. are already specified to one communi- QCPU and correct if duplicated.
cation target.
• For UDP/IP, the same Host station port No. • Specify a port number that is not duplicated with that of
is specified as MC protocol. MC protocol
41A4H
• For UDP/IP, the specified host station No. is • Review port numbers of the Built-in Ethernet port
duplicated. QCPU and target device and correct if duplicated.
The IP address setting of the target device for
41A5H Ethernet Correct the IP address. Specify A, B, or C for the class.
OPEN processing is invalid.
I/F
• Check the bihavior of the target device.
socket com-
• Check OPEN processing of the target device.
muinication
Connection was not established in OPEN pro- • Correct the port No. of the Built-in Ethernet port QCPU
41A6H error
cessing for TCP connection. and the IP address, port No., and open processing
method of the target device.
• Check whether the cables are securely connected.
• Correct the data length.
41A8H Data length is out of permissible range. • If the data is longer than the range, split the data and
send them.
• Review the IP address and Ethernet address of the tar-
get device.
• Check whether the target device has the ARP function.
If not, communicate with the one that has the ARP
41ABH Failed to send data due to resend timeout in TCP. function.
• Check the bihavior of the target device.
• The line may be congested with packets. Resend data
after a while.
• Check whether the cables are securely connected.
12 - 156
Table12.2 Error code
Error code
Error item Error details Corrective action
(Hexadecimal)
• Check the bihavior of the target device.
41ACH The target device cannot be found.
• Check whether the cables are securely connected.
• Check whether the cables are securely connected.
• Check the line status by PING test from the target
Data cannot be send due to no connection or dis- device.
41ADH
connection of the cable. • Check the status of Built-in Ethernet port QCPU by self
diagnostic test (Built-in Ethernet port QCPU reset)
Ethernet • Send data again
I/F • Specify the connection No. within 1 to 16.
41B4H socket com- The connection number setting is invalid. • Check whether "Socket communication" is selected for
muinication "Open system" parameter.
error The specified connection has already completed
41B6H Perform CLOSE processing and then OPEN processing.
OPEN processing.
• The specified connection has not completed
41B7H • Reexecute after OPEN processing is completed.
OPEN processing.
• Contents of control data is not correct.
• Correct the contents of the control data.
• Open instruction was executed through
41B9H • Configure the open settings parameters or execute the
open settings parameter even though
OPEN instruction through control data.
parameters are not set for "Open settings".
The file information data may be corrupted.
The format information data of the specified drive
41C1H After backing up the data in the CPU module, execute pro-
(memory) is abnormal.
grammable controller memory format.
File open specification data for file access is
41C2H Execute again after checking the specification data.
wrong.
Simultaneously accessible files exceeded the
41C3H Execute again after decreasing file operations.
maximum.
Simultaneously accessible files exceeded the
41C4H Execute again after decreasing file operations.
maximum.
41C5H File-related The specified file does not exist. Execute again after checking the file.
errors The specified file or drive (memory) does not
41C7H Execute again after checking the file or drive (memory).
exist.
Execute again after checking the size of the specified file.
If the error recurs after re-execution, the file information data
The specified file has exceeded the already exist-
41C8H may be corrupted.
ing file range.
After backing up the data in the CPU module, execute pro-
grammable controller memory format.
Access to the file sector was unsuccessful.
After backing up the data in the CPU module, execute pro-
41C9H The format information data of the target drive
grammable controller memory format.
(memory) is abnormal.
12 - 157
CHAPTER12 TROUBLESHOOTING
12.3.11 Error codes returned to request source during communication with CPU module
12.3 Error Code List
The file information data may be corrupted.
The format information data of the specified drive
41D7H After backing up the data in the CPU module, execute pro-
(memory) is abnormal.
grammable controller memory format.
41D8H The specified file is being accessed. Execute again after a while.
Execute again after canceling the write protect of the speci-
41DFH The specified drive (memory) is write-protected.
fied drive (memory).
• Execute again after checking whether the memory
The specified drive (memory) is abnormal or does card has been installed.
41E0H
not exist. • After backing up the data, execute programmable con-
troller memory format.
• After backing up the data, execute write to PLC (Flash
ROM).
41E1H Access to the flash ROM was unsuccessful. • Execute again after checking whether the specified
drive is the Flash ROM card and whether the memory
card size is correct.
12 - 158
Table12.2 Error code
Error code
Error item Error details Corrective action
(Hexadecimal)
• Execute again after checking whether the memory
card has been installed.
41E4H Access to the memory card was unsuccessful. • Execute again after replacing the memory card.
• After backing up the data, execute programmable con-
troller memory format.
The file information data may be corrupted.
The format information data of the specified drive
41E7H After backing up the data in the CPU module, execute pro-
(memory) is abnormal.
grammable controller memory format.
The file information data may be corrupted.
The format information data of the specified drive
41E8H After backing up the data in the CPU module, execute pro-
(memory) is abnormal.
grammable controller memory format.
41E9H The specified file is being accessed. Execute again after some time.
41EBH The file name is specified in a wrong method. Execute again after checking the file name.
The file information data may have been corrupted.
The file system of the specified drive (memory) is
41ECH After backing up the data in the CPU module, execute pro-
logically corrupted.
grammable controller memory format.
The specified drive (memory) does not have con-
tinuous free space. Execute again after deleting unnecessary files or executing
41EDH
(The free space for file is sufficient but the contin- programmable controller memory arrangement.
uous free space is insufficient.)
File-related Creation of power failure backup for the specified Execute again after checking whether the memory card has
41EFH
errors drive (memory) was unsuccessful. been installed.
The power failure backup data of the specified Execute again after checking whether the memory card has
41F0H
drive (memory) are corrupted. been installed.
The power failure backup for the specified drive Execute again after checking whether the memory card has
41F1H
(memory) has a repair command. been installed.
Execute again after checking the specified drive (memory).
Operation cannot be performed since the speci-
41F2H When performing operation for the Flash ROM, use write to
fied drive (memory) is Flash ROM.
PLC (Flash ROM).
PLC write to the program memory or transfer to the backup
The identical data is being accessed by the other memory is in execution.
41F8H
peripheral devices. Access the data again after checking that the above-men-
tioned function has been completed.
Program was written beyond the area where the Execute again after reducing either the already written pro-
41FAH
program can be executed. gram or newly written program.
Operation is being performed for the file already Execute again after the currently performed operation is
41FBH
specified for the same peripheral device. completed.
An attempt was made to erase the drive (mem- The specified drive (memory) is being used and cannot be
41FCH
ory) being used. erased.
41FDH There are no data written to the Flash ROM. Write a file by executing write to PLC (Flash ROM).
41FEH The memory card has not been inserted. Insert or re-insert the memory card.
41FFH The memory card type differs. Check the memory card type.
12 - 159
CHAPTER12 TROUBLESHOOTING
12.3.11 Error codes returned to request source during communication with CPU module
12.3 Error Code List
The file information data may be corrupted.
The format information data of the specified drive
41D7H After backing up the data in the CPU module, execute pro-
(memory) is abnormal.
grammable controller memory format.
41D8H The specified file is being accessed. Execute again after a while.
Execute again after canceling the write protect of the speci-
41DFH The specified drive (memory) is write-protected.
fied drive (memory).
• Execute again after checking whether the memory
The specified drive (memory) is abnormal or does card has been installed.
41E0H
not exist. • After backing up the data, execute programmable con-
troller memory format.
• After backing up the data, execute write to PLC (Flash
ROM).
41E1H Access to the flash ROM was unsuccessful. • Execute again after checking whether the specified
drive is the Flash ROM card and whether the memory
card size is correct.
• Execute again after checking whether the memory
card has been installed.
41E4H Access to the memory card was unsuccessful. • Execute again after replacing the memory card.
• After backing up the data, execute programmable con-
troller memory format.
12 - 160
Table12.2 Error code
Error code
Error item Error details Corrective action
(Hexadecimal)
The file information data may be corrupted.
The format information data of the specified drive
41E7H After backing up the data in the CPU module, execute pro-
(memory) is abnormal.
grammable controller memory format.
The file information data may be corrupted.
The format information data of the specified drive
41E8H After backing up the data in the CPU module, execute pro-
(memory) is abnormal.
grammable controller memory format.
41E9H The specified file is being accessed. Execute again after some time.
41EBH The file name is specified in a wrong method. Execute again after checking the file name.
The file information data may have been corrupted.
The file system of the specified drive (memory) is
41ECH After backing up the data in the CPU module, execute pro-
logically corrupted.
grammable controller memory format.
The specified drive (memory) does not have con-
tinuous free space. Execute again after deleting unnecessary files or executing
41EDH
(The free space for file is sufficient but the contin- programmable controller memory arrangement.
uous free space is insufficient.)
Creation of power failure backup for the specified Execute again after checking whether the memory card has
41EFH
drive (memory) was unsuccessful. been installed.
The power failure backup data of the specified Execute again after checking whether the memory card has
41F0H File-related
drive (memory) are corrupted. been installed.
errors
The power failure backup for the specified drive Execute again after checking whether the memory card has
41F1H
(memory) has a repair command. been installed.
Execute again after checking the specified drive (memory).
Operation cannot be performed since the speci-
41F2H When performing operation for the Flash ROM, use write to
fied drive (memory) is Flash ROM.
PLC (Flash ROM).
PLC write to the program memory or transfer to the backup
The identical data is being accessed by the other memory is in execution.
41F8H
peripheral devices. Access the data again after checking that the above-men-
tioned function has been completed.
Program was written beyond the area where the Execute again after reducing either the already written pro-
41FAH
program can be executed. gram or newly written program.
Operation is being performed for the file already Execute again after the currently performed operation is
41FBH
specified for the same peripheral device. completed.
An attempt was made to erase the drive (mem- The specified drive (memory) is being used and cannot be
41FCH
ory) being used. erased.
41FDH There are no data written to the Flash ROM. Write a file by executing write to PLC (Flash ROM).
41FEH The memory card has not been inserted. Insert or re-insert the memory card.
41FFH The memory card type differs. Check the memory card type.
12 - 161
CHAPTER12 TROUBLESHOOTING
12.3.11 Error codes returned to request source during communication with CPU module
12.3 Error Code List
4214H
changed online. same as the one changed online.
When making a request, specify the head I/O number of the
4215H The specified module does not exist. module that will be changed online, or make a request again
after mounting the module.
4216H The specified module is faulty. Make a request again after changing the module.
4217H There is no response from the specified module. Continue the online module changing operation.
Do not make a request where an error occurred, or make a
The specified module is incompatible with online
4218H request again to the module compatible with online module
module change.
change.
The specified module is mounted on the exten- Do not make a request to any modules mounted on the
4219H sion base unit of the type that requires no power extension base unit of the type that requires no power supply
supply module. module and the main base unit.
Make a request to the CPU module that controls the speci-
421AH The specified module is not in a control group.
fied module.
An error occurred in the setting of the initial set- Resume processing after checking the contents of the intelli-
421BH
ting parameter of the intelligent function module. gent function module buffer memory.
Cannot be executed as the parameter file has
421CH Operation cannot be performed. Operation is interrupted.
been rewritten.
12 - 162
Table12.2 Error code
Error code
Error item Error details Corrective action
(Hexadecimal)
Connect GX Developer to the new control system and check
System switching occurs during the online mod-
421DH the status of the online module change. According to the sta-
ule change.
tus of online module change, take procedures for it.
The tracking cable may be faulty or the standby system may
The information of the online module change can- have an error.
not be sent to the standby system. When the sys- • Check the mounting status of the tracking cable or
Online module
421EH tem switching occurs during the online module replace the tracking cable.
change-related
change, the online module change may not be • Check the status of the standby system. When a stop
error
continued. error was detected by the standby system, perform
troubleshooting.
The module mounted on the extension base unit • Set the connection destination of a programming tool
cannot be replaced online when the connection to the present control system.
421FH
destination is set to the standby system in the • Perform the online module change to the module
separate mode. mounted on the extension base unit again.
Any of the following unsupported operations was
executed for the standby system.
• Operation mode change Execute the operation again after changing the transfer
4240H
• System switching setup to the control system.
• Memory copy from control system to
standby system
Communication cannot be made since the
standby system has been powered off or reset or Request communication after powering on the standby sys-
4241H
is in a user watchdog timer error or CPU module tem or setting its Reset switch to the neutral position.
hardware fault status.
Communication with the standby system cannot Cannot be executed since the tracking cable is disconnected
4242H be made since the tracking cable is faulty or dis- or faulty. Execute again after checking the tracking cable for
connected. disconnection or changing it for a normal one.
The command cannot be executed since the Execute again after removing the stop error of the standby
4243H
standby system is in stop error. system.
The command cannot be executed since the
Execute again after placing the standby system in the same
4244H operation status differs from that of the standby
operation status (RUN/STOP) as the control system.
Redundant sys- system.
tem-related Check that the other system CPU module has normally
4245H Other system CPU module status error
error started up and that the tracking cable is connected.
The command cannot be executed since opera-
tion mode (separate/backup) change or system Execute again after the operation mode change or system
4246H
(control/standby system) switching is being exe- switching being executed is completed.
cuted.
Execute again after memory copy from control system to
standby system is completed.
Check the following and take corrective action.
• Is SM1596 of the control system or standby system
ON?
(ON: Memory copy being executed)
Memory copy from control system to standby sys-
4247H Execute again after SM1596 has turned OFF since it is
tem is already being executed.
turned OFF by the system on completion of memory
copy.
• Is SM1597 of the control system ON?
(ON: Memory copy completed)
Execute again after turning OFF SM1597 of the control
system.
12 - 163
CHAPTER12 TROUBLESHOOTING
12.3.11 Error codes returned to request source during communication with CPU module
12.3 Error Code List
System switching was executed by the other con-
oper, system switching was executed first by the other condi-
424FH dition during execution of system switching by GX
tion. Check the system for any problem and execute the
Developer.
operation again as necessary.
Execute communication again after changing the tracking
cable.
Sum check error occurred in tracking communica- If the same error recurs after the tracking cable is changed,
4250H
tion. the cause is the hardware fault of the CPU module.
(Please contact your local nearest Mitsubishi or representa-
tive, explaining a detailed description of the problem.)
The command cannot be executed in the sepa-
4251H Execute again after changing to the backup mode.
rate mode.
By monitoring SD1690 (other system network module No.
System switching was not executed since an
that issued system switching request), identify the faulty
4252H error occurred in the redundant system compati-
redundant-compatible intelligent module of the standby sys-
ble network module of the standby system.
tem, then remove the module fault, and execute again.
12 - 164
Table12.2 Error code
Error code
Error item Error details Corrective action
(Hexadecimal)
Since a communication error or system switching occurred
during execution of online program change to the control
system CPU module, online program change redundant
tracking was suspended.
Since a communication error or system switching
Execute online program change again after confirming that
occurred during online program change to the
communication with the control system CPU module and
4253H control system CPU module, online program
standby system CPU module can be normally made.
change to the standby CPU module cannot be
When long time is taken for communication between GX
executed.
Developer and control system CPU module or standby sys-
tem CPU module, the error may be avoided by adjusting
SD1710 (standby system online program change start wait-
ing time).
The tracking cable may not be connected correctly, or the
tracking communication hardware of the CPU module may
The command cannot be executed since an error
be faulty. Check the connection status of the tracking cable.
4254H was detected in the tracking communication hard-
If the condition is not restored to normal after the cable con-
ware.
nection status is corrected, the possible cause is the hard-
ware fault of the CPU module.
Tracking communication is being prepared when it is con-
The command cannot be executed since tracking
4255H nected. Execute the operation again after a while (about 1
communication is being prepared.
second).
The tracking cable may not be connected correctly, or the
tracking communication hardware of the CPU module may
Redundant sys-
The command cannot be executed since a time- be faulty. Check the connection status of the tracking cable.
4256H tem-related
out error occurred in tracking communication. If the condition is not restored to normal after the cable con-
error
nection status is corrected, the possible cause is the hard-
ware fault of the CPU module.
The command cannot be executed since the host The command cannot be executed since the host system is
4257H system CPU module is in a watchdog timer error in a watchdog timer error or CPU module hardware fault sta-
or CPU module hardware fault status. tus. Execute again after checking the host system status.
Execute again after completing the operation mode change
Operation mode being changed (from backup by changing the status from STOP to RUN using the RUN/
4258H
mode to separate mode) STOP switch of the CPU module whose RUN LED is flicker-
ing or remote operation.
Operation mode change is being executed in the
Execute again in the same communication route as the one
4259H communication route different from the current
where the operation mode change was executed.
one from the other peripheral device.
Although the communication was made via the
intelligent function module mounted on the exten-
Change the combination of the connection destination speci-
425BH sion base unit, the combination of the connection
fication and the command to the supported combination.
destination specification (Redundant CPU specifi-
cation) and the command is unsupported.
System switching cannot be made since the mod-
Switch systems after the online module change has been
425CH ule mounted on the extension base unit is being
completed.
replaced online.
Operation mode cannot be changed since the
Change the operation mode after the online module change
425DH module mounted on the extension base unit is
has been completed.
being replaced online.
12 - 165
CHAPTER12 TROUBLESHOOTING
Link-related
• When System A/System B is not yet identi-
fied in a redundant system configuration,
tracking cable, start System A/System B normally, and
then restart communication.
12
error communication was made with the other
station via the network module.
The network of the No. set to the routing parame- Check and correct the routing parameters set to the related
4A01H
ters does not exist. stations.
• Check the network module/link module for an error or
offline status.
4A02H Access to the specified station cannot be made.
• Check to see if the network number/PC number setting
has no mistake.
4A03H A request for network test was issued. Check the request data of the MC protocol, etc.
• Take corrective action after checking the error that
occurred at the specified access destination or the
An error occurred in the access destination or
relay station to the accessed station.
4B00H relay station, or the specified transfer setup
• Check the transfer setup (request destination module
(request destination module I/O number) is illegal.
I/O number or programmable controller number) in the
request data of the MC protocol, etc.
The target is not the No. 1 CPU of the multiple Execute the request for the No. 1 CPU of the multiple CPU
4B01H
Target-related CPU system. system.
12.3.11 Error codes returned to request source during communication with CPU module
12.3 Error Code List
error Perform operation for the module that can execute the speci-
4B02H The request is not addressed to the CPU module.
fied function.
• The specified route is not supported by the
specified CPU module version.
4B03H Check whether the specified route is supported or not.
• The communication target CsPU is not
mounted.
The specified transfer setup (request destination In the target setup, an illegal value is set as the head I/O
4B04H
module I/O number) is not supported. number of the target module.
The specified device is unavailable for the motion
4C00H Check the request data contents.
CPU or outside the device range.
Multiple CPU- There are a total of 33 or more DDWR and DDRD Execute again after reducing the number of DDWR and
4C08H
related error requests. DDRD requests to be executed simultaneously.
The specification of the requested CPU module
4C09H Check the request data contents.
No. is illegal.
12 - 166
12.4 Module Change during System Operation
This section explains how to change the module online (with power on) without stopping the system.
An online module change Note12.15 is a function that allows the Q series module mounted on the main base unit or
extension base unit to be changed during system control executed by the Process CPU or Redundant CPU.Note1
Using an online module change, the module that failed during control can be replaced with the module of the same
model name.
● An online module change cannot add a module or change the current module for another module.
● When executing an online module change for the Process CPU in the multiple CPU system, it is necessary to specify
"Online module change enable for other CPU" in the multiple CPU setting of the PLC parameter dialog box.
Also, there are restrictions on the versions of the CPU modules that comprise the multiple CPU system. For details,
refer to the following.
QCPU User's Manual (Multiple CPU System)
● Perform an online module change after confirming that the system outside the programmable controller will not
malfunction.
● To prevent an electric shock, operating module malfunction, etc., provide a switch or similar individually cutting-off
means for the external power supply of the module to be changed online.
● It is recommended to verify that the operations of the unchanged modules will not be affected by executing an online
module change in an actual system beforehand to confirm the following
• The means and structure that will cut off the connection with the external device are correct.
• ON/OFF of switches, etc. has no influence.
● Do not mount/remove the module onto/from base unit or terminal block more than 50 times (IEC 61131-2 compliant),
after the first use of the product.
Failure to do so may cause the module to malfunction due to poor contact of connector.
Note1
High
Note12.15 Basic performance Universal
The Basic model QCPU, High Performance model QCPU and Universal model QCPU are not
compatible with an online module change.
12 - 167
CHAPTER12 TROUBLESHOOTING
Intelligent function
Digital-analog converter module 5
Temperature input module Supported by function version C.
module
Temperature control module
Pulse input module 6
*1: When using Redundant CPU and/or connecting a extension base unit, online module change cannot be performed to a
intelligent function module mounted on the main base unit.
7
The modules other than listed above cannot be changed online.
For whether the above intelligent function modules can be changed online or not and their changing
procedures, refer to the manual of the used intelligent function module. 8
(b) Versions of GX Developer that supports online module change
GX Developer is required to perform an online module change.
For GX Developer version, refer to the following
2) When the extension base unit of the type that requires no power supply module (Q5 SB) is used, an
online module change cannot be performed for the modules mounted on all base units connected.
3) When the redundant type extension base unit (Q6 WRB) is used, the online module change cannot be
performed to all modules connected to the main base unit.
12 - 168
(d) Control status of CPU module
1) An online module change can be executed when a stop error has not occurred.
Whether an online module change can be executed or not depending on the control status of the CPU
module is shown in Table12.4.
Control status RUN status*1 STOP status PAUSE status At stop error
Whether online module
change can be executed Can be executed Can be executed Can be executed Cannot be executed
or not
*1: Including the case where a continue error has occurred in the RUN status.
2) An online module change can be continued if the control status of the CPU module is changed to the STOP/
PAUSE status during the online module change.
In either of the following cases, however, the online module change cannot be continued.
•When the CPU module is reset
•When a stop error occurs
12 - 169
CHAPTER12 TROUBLESHOOTING
3
The following message appears (refer to Figure 12.24) if an online module change request is issued from another GX
Developer to the CPU module during online module change.
After confirming the message, select "Yes" or "No".
12
"Yes" selected
6
8
Online module Online module change
change continued execution canceled
"No" selected
GX Developer 2) GX Developer 1)
Figure 12.26 Online module change (When "No" is selected)
12 - 170
(3) Special relays and special register related to online module change
Information during online module change is stored into the special relays (SM235, SM236) and special register
(SD235).
•Whether the online module change of the corresponding CPU module is executed or not can
be checked by monitoring SM235, SM236 and SD235.
•SM235: Online module change flag (turns on during online module change)
•SM236: Flag that turns on only one scan after online module change (turns on only one scan
after completion of online module change)
•SD235: Module being changed online (stores the starting I/O number of the module being
changed online/10H)
Refer to Section 12.7 for details of SM235 and SM236 and to Section 12.8 for details of SD235.
Online module Online module
change start change completed
ON
SM235 OFF
ON
SM236 OFF
1 scan
12 - 171
CHAPTER12 TROUBLESHOOTING
3
• It is recommended to turn off the output (Y) from the output module/I/O combined module to be changed online
before it is changed.
• When making an online module change for the Redundant CPU, specify "No settings have been made (Default)",
"System A" or "System B" as the target system in the "transfer setup" by GX Developer.
Do not specify the "Control system" or "Standby system" as the target system.
12
If the "Control system" or "Standby system" is specified in the transfer setup, the following error dialog (refer to
Figure 12.28) appears at execution of an online module change.
When the following error dialog is displayed, change the target system to "No settings have been made (Default)",
"System A" or "System B", and then perform an online module change.
5
7
Figure 12.28 Error dialog box
• When executing online module change for the module mounted on the extension base unit in the Redundant
CPU, access cannot be made to a module mounted on the extension base unit from the standby system. Set 8
[Transfer setup] in GX Developer, checking that the trasnfer target Redundant CPU module is the control system.
12 - 172
1) Choose [Diagnostics] [Online module change] on GX Developer, and select the "Online module change"
mode.
2) Double-click the module to be changed online to display the online module change screen.
(Table12.5 shows the communication status with the target module for online module change when the
following screen (refer to Figure 12.30) is displayed.)
Executed/Not
Target module, item
executed
Input module refresh Executed
Output module refresh Executed
Input refresh Executed
I/O hybrid module
Output refresh Executed
Input refresh Executed
Output refresh Executed
FROM/TO instruction Executed
Instruction using intelligent
Executed
function module device
Intelligent dedicated instruction Executed
Intelligent function Intelligent automatic refresh Executed
module
12 - 173
CHAPTER12 TROUBLESHOOTING
Communication
Buffer memory batch monitor
error 7
Figure 12.31 Online module change screen
4) With a switch or other device, cut off the connection with the external device (module I/O signals).
8
5) Turn off the switch of the external power supply for module to shut off power supply.
6) Disconnect the terminal block or connector from the module.
12 - 174
12)After mounting the module, click the Execution button.
(Table12.7 shows the communication status with the target module for online module change when the
following screen (refer to Figure 12.32) is displayed.)
Executed/Not
Target module, item
executed
Not executed
Input module refresh
(Data held)
Output module refresh Not executed
Not executed
Input refresh
I/O hybrid module (Data held)
Output refresh Not executed
Input refresh Executed
Output refresh Executed
FROM/TO instruction No processing
Instruction using intelligent
No processing
function module device
Intelligent function Intelligent dedicated instruction No processing
module Intelligent automatic refresh No processing
When the initial settings of the intelligent function module have been made by GX Configulator, the set data are written to the
intelligent function module.
Executed/Not
Target module, item
executed
Input module refresh Executed
Output module refresh Executed
Input refresh Executed
I/O hybrid module
Output refresh Executed
Input refresh Executed
Output refresh Executed
FROM/TO instruction Executed
Intelligent function Instruction using intelligent
Executed
module function module device
Intelligent dedicated instruction Executed
Intelligent automatic refresh Executed
Figure 12.33 Online module change screen Buffer memory batch monitor Executed
12 - 175
CHAPTER12 TROUBLESHOOTING
12
8
Figure 12.34 System monitor
3) When selecting [Online module change] in a status of a module being replaced online, screen shown in
4) Continue the operation that has been executed before system switching occurrence.
12 - 176
• When connecting the new control system and clicking the Execution button, the message shown in Figure 12.31
may be shown. In this case, select [Yes] and continue operation for the online module change.
12 - 177
CHAPTER12 TROUBLESHOOTING
7
Make sure that the "POWER" LED is
turned on green.
8
Completed
12 - 178
• If either redundant power supply module fails, change it for a normal one earlier than usual (within 14 days as a
guideline).
If it does not fail, it is recommended to change the redundant power supply module for a new one after five years
have elapsed.
• Change the redundant power supply module with extreme care, referring to Section 10.3.3(1).
If the module fixing projection of the redundant power supply module comes off from the module fixing hole of the
redundant base unit, an error will occur due to connector damage.
• When the redundant power supply system is used, a "continue" error will occur due to a redundant power supply
module failure. Cancel the error after changing the faulty redundant power supply module for a normal one.
Note12.16, Note12.17
• When the redundant power supply system is used, the failure status of the redundant power supply module can
be checked by the system monitor of GX Developer (Version 8.18U or later) or the special relay SM1781/special
register SD1781. Note12.16, Note12.17Note1
For details of the system monitor, refer to the following.
GX Developer Operating Manual
Note1
Note12.16 Basic
Failure of redundant power supply cannot be detected by the Basic model QCPU.
High
Note12.17 performance Process
When using the High Performance QCPU or the Process CPU, confirm the versions of CPU module and GX
Developer. ( Appendix 2)
12 - 179
CHAPTER12 TROUBLESHOOTING
The following describes possible problems with input circuits and their corrective actions.
3
Table12.9 Input circuit problems and corrective actions
AC input
lower than the off voltage. 5
AC input
Example 1
Input signal is
Leakage Input
not turned off.
current module
• Same as Example 1.
• Leakage current due to line capacity of wiring cable.
(However, leakage current is not generated when the
(Line capacity C of twisted pair wire is approx. 100
power supply is located in the input equipment side
pF/m).
as shown below.)
Example 3
Power supply
Power supply
Input signal is
not turned off. Leakage current Input Resister Input
module module
12 - 180
Condition Cause Corrective Action
• Use only one power supply.
• Sneak path due to the use of two power supplies. • Connect a sneak path prevention diode. (Figure
DC input below)
Example 5
DC input
Input signal is
not turned off. E1 E2 Input
module
E1 E2 Input
module
E1 E2
Stepwise distortion as shown below appears to the Improve input signal waveform by using the on-
zero cross voltage of input signal (AC). line system etc.
Input signal is
Example 6
not turned on
(AC input Zero cross
module) voltage
24VDC
• In this case, the circuit does not satisfy the condition that the off current of the QX40 is 1.7mA or less.
Connect a resistance as follows.
QX40
2.33mA
IZ=1.7mA
IR=0.63mA R Input impedance
5.6k
24VDC
12 - 181
CHAPTER12 TROUBLESHOOTING
IZ 1.7
2
R< Z (Input impedance)= 5.6=15.11[k ]
IR 0.63
12 - 182
12.5.2 Output circuit troubleshooting
This section explains trouble examples and troubleshooting in the output circuit.
QY22
Output module D1 [1] Resistor
Load
Load
Excessive
Example 1
[2]
voltage is applied
to load when
• When the polarity of the power supply is [1], the
output turns off.
capacitor C is charged. When the polarity is [2], the
voltage charged in C plus the power supply voltage
is applied to across D1. The maximum value of the
voltage is approx. 2.2E.
(This usage does not pose problems to the output
components but may deteriorate the diode built in
the load, causing burnout, etc.)
• Leakage current due to the built-in surge • Connect a resistor at both ends of the load.
suppressor (If the wiring from the output module to the load is
long, be careful since there may be a leakage
QY22
current due to the line capacity.)
Example 2
Load
Control
circuit Load
Triac
12 - 183
CHAPTER12 TROUBLESHOOTING
1
Table12.10 Output circuit troubleshooting (Continued)
L
external power
Example 4
supply turns 8
on, the load is
turned on for a R1
0V
moment. SW
12/24VDC
SW C1
Constant
Source output
I Y0
L
R1
0V
SW
C1
COM
24V
*: Measures will not be effective to the
following module due to the characterictic
of external power supply circuit.
• QY81P
12 - 184
Table12.10 Output circuit troubleshooting (Continued)
Approx. 100 s
C1 R1=300 10-6 40
=12 10 s
-3
=12ms
12 - 185
CHAPTER12 TROUBLESHOOTING
12
electromotive
force
[2] Load
Y1 Load
OFF
Sink output
5
[1]
Shut off
[3]
COM Back
electromotive
force
0V Load
6
Output module, • Connect diode between (+) and (-) of
7
ombined module [3] the external power supply so that a
Back electromotive
Sink output + - sneak path circuit is porvided.
force
ON Y0 Load Connect the diode to C1 and R1 in
parallel when example 4 is performed
[2] simultaneously. 8
The load which Y1 Load Source output -
Back electromotive
+ [3]
OFF force
was turned off Y0 Load
[1] ON
Example 5
[2]
Y1 Load
OFF
[1]
Shut off
COM
D1
C1 R1
12/24VDC
Example 4
D1: Reverse current VR(VRM)···*1,
Forward current IF(IFM)···*2
* 1 Approx. 10 times the rated voltage of
the spec.
Ex.: 24VDC Approx.200V
*2 More than 2 times the Max. load
current (common) of the spec.
Ex: 2A/1 common More than 4A
12 - 186
12.6 Built-in Ethernet Port Diagnosis
Using the diagnostic function of GX Developer, the module status, parameter settings, communication status, and
error log of the Built-in Ethernet port QCPU can be checked.
The relevant screen can be activated by either of the following two methods.
• In GX Developer, select [Diagnostics] [PLC diagnostics] [Ethernet diagnosis]
On the following pages, details of the built-in Ethernet port diagnosis screens are described.
12 - 187
CHAPTER12 TROUBLESHOOTING
12
7
Figure 12.41 Ethernet diagnosis (Parameter status) screen
Before performing the Built-in Ethernet port, check that the “CPU” is selected in the Target module setting on the Ethernet
diagnosis screen.
12 - 188
(2) Error log
Item Description
Displays connection No. of the connection that has an error.
Connection No. UDP connections that function in MELSOFT connection are treated as one
connection, and the lowest connection No. is stored in the error log.
Protocol
Open system Displays the settings of PLC parameter.
Host station port No.
Displays a generated error code.*1
Error code In the case of MELSOFT connection, only the errors related to Ethernet com-
munication are stored in the Error log.
Displays the IP address of the other device when an error occurs in communi-
Destination IP address
cation with it.
Displays the port number of the other device when an error occurs in commu-
Destination port No.
nication with it.
Command code Displays command No. when an error occurs in MC protocol communication.
Year/Month/Day, Time Displays the date and time of error occurrence.
Clear history Clears the displayed error log.
Error and solution Displays details of the selected error code and corrective actions.
*1 "SNTP OPE. ERROR" (error code: 2710) is stored in the error log only when the time setting at power-ON or reset has
failed.
For results in the case of executing the time setting regularly or by special relay "SM1270" from the sequence program,
check the SNTP status screen or special register "SD1270".
Because the error log is battery backed up, the information is retained even if the power is turned off.
Note that the latch data backup function (to the standard ROM) cannot back up the error log to the standard ROM.
12 - 189
CHAPTER12 TROUBLESHOOTING
12
7
Figure 12.43 Ethernet diagnosis (Status of each connection) screen
*1: UDP connections that function in MELSOFT connection are treated as one connection. Therefore, for multiple connec-
tions, the same information is displayed.
*2: Not displayed when the protocol is UDP and direct connection to GX Developer is used.
*3: The same information is displayed when the protocol is TCP and when multiple MELSOFT connections exist.
12 - 190
(4) Connection status
Item Description
Full duplex/Half duplex Displays whether the line uses the full or half duplex system.
Connection status Displays whether a hub or target device is connected or not.
10BASE-T/100BASE-TX Displays whether the network is 10BASE-T or 100BASE-TX.
Maximum size of detection Displays the maximum size of discarded broadcast message data.
Amount of data per unit time (latest) Displays the total size of discarded broadcast message data per unit time.
Displays the maximum total size of discarded broadcast message data per unit
Amount of data per unit time (maximum)
time.
Clear line status Clears the number of receive buffer overflows and broadcast information.
12 - 191
CHAPTER12 TROUBLESHOOTING
12
7
Figure 12.45 Ethernet diagnosis (SNTP status) screen
12 - 192
(6) PING test
PING test is a test by which existence of the Built-in Ethernet port QCPU can be checked from GX Developer.
Performing a PING test for the Built-in Ethernet port QCPU can determine the following:
• Whether the line is connected to the target Built-in Ethernet port QCPU properly
• Whether the parameters for the Built-in Ethernet port QCPU are set correctly
12 - 193
CHAPTER12 TROUBLESHOOTING
7
If failed, check the following and run the PING test again.
• The Built-in Ethernet port QCPU installation to the base unit
• Connection to Ethernet
8
• Respective parameters written to the Built-in Ethernet port QCPU
• Built-in Ethernet port QCPU operating status (whether an error has occurred or not)
• Respective IP addresses set in GX Developer and PING test target stations
• Subnet addresses set in GX Developer and PING test target stations when transmissions do not pass through any
12 - 194
12.7 SPECIAL RELAY LIST
Special relays, SM, are internal relays whose applications are fixed in the Programmable
Controller.
For this reason, they cannot be used by sequence programs in the same way as the normal
internal relays.
However, they can be turned ON or OFF as needed in order to control the CPU module.
The heading descriptions in the following special relay lists are shown in 3.1.
Do not change the values of special relays set by the system with user program or device test operations.
Doing so may result in system downtime or communication fault.
12 - 195
CHAPTER12 TROUBLESHOOTING
Corres-
12 - 196
Table12.18 Special relay
Corres-
Set by ponding Corresponding
Number Name Meaning Explanation
(When Set) ACPU CPU
M9
• ON when operation error is generated
OFF : Normal
SM56 Operation error • Remains ON if the condition is restored to normal S (Error) M9011
ON : Operation error
thereafter.
• Turns ON if there is at least one output module
whose fuse has blown.
OFF : Normal
• Remains ON if the condition is restored to normal
SM60 Blown fuse detection ON : Module with blown S (Error) M9000
thereafter.
fuse
• Blown fuse status is checked even for remote I/O
station output modules. QCPU
• Turns ON if the I/O module differs from the status
registered at power on.
OFF : Normal • Remains ON if the condition is restored to normal
SM61 I/O module verify error S (Error) M9002
ON : Error thereafter.
• I/O module verification is also conducted for remote
I/O station modules.
OFF : Not detected S (Instruction
SM62 Annunciator detection • Goes ON if even one annunciator (F) goes ON. M9009
ON : Detected execution)
• Goes ON if error is detected by CHK instruction. Qn(H)
OFF : Not detected S (Instruction
SM80 CHK detection • Remains ON if the condition is restored to normal New QnPH
ON : Detected execution)
thereafter. QnPRH
Corresponds
SM90 M9108
to SD90
Corresponds
SM91 M9109
to SD91
Corresponds
SM92 M9110
to SD92
Corresponds
SM93 M9111
to SD93
• Goes ON when measurement of
Startup of monitoring OFF : Not started(monitoring Corresponds
SM94 step transition monitoring timer is M9112 Qn(H)
timer for step transition timer reset) to SD94
commenced. U QnPH
(Enabled only when ON : Started(monitoring Corresponds
SM95 • Resets step transition monitoring M9113 QnPRH
SFC program exists) timer started) to SD95 timer when it goes OFF.
Corresponds
SM96 M9114
to SD96
Corresponds
SM97 New
to SD97
Corresponds
SM98 New
to SD98
Corresponds
SM99 New
to SD99
OFF : Serial communication
• Stores the setting of whether the serial
Serial communication function is not used. S (Power-ON or
SM100 communication function is used or not in the serial
function using flag ON : Serial communication reset)
communication setting parameter
function is used.
OFF : GX Developer • Stores whether the device that is communicating via
Communication S (RS232
SM101 ON : MC protocol the RS-232 interface is GX Developer or MC protocol
protocol status flag communication)
communication device communication device
• Turns ON when an abnormal protocol was used to
make communication in the serial communication
OFF : Normal
SM110 Protocol error function. S (Error)
ON : Abnormal
• Remains ON if the condition is restored to normal
thereafter Q00/Q01
Q00UJ
• Turns ON when the mode used to make
New Q00U
communication was different from the setting in the
OFF : Normal Q01U
SM111 Communication status serial communication function. S (Error)
ON : Abnormal Q02U*7
• Remains ON if the condition is restored to normal
thereafter.
• Turns ON when the error codes stored in SM110,
SM112 Error information clear ON : Cleared SM111, SD110 and SD111 are cleared. (Activated U
when turned from OFF to ON)
OFF : Normal • Turns ON when an overrun error occurred in the
SM113 Overrun error S (Error)
ON : Abnormal serial communication error.
OFF : Normal • Turns ON when a parity error occurred in the serial
SM114 Parity error S (Error)
ON : Abnormal communication error.
OFF : Normal • Turns ON when a framing error occurred in the serial
SM115 Framing error S (Error)
ON : Abnormal communication error.
• Turns ON when the data is written to the program
cache memory.
Program memory OFF : Completed • Turns OFF when the program memory batch transfer
S (When status
SM165 batch transfer ON : Not being executed or is completed. New QnU* 6
changed)
execution status Not completed • Remains ON if the program memory batch transfer is
not executed after the data is written to the program
cache memory.
*6: The relevant modules are as follows:
• The Universal model QCPU whose serial number (first five digits) is "10012" or later.
• Q13UDHCPU, Q26UDHCPU
*7: The module whose first 5 digits of serial No. is "10102" or later.
12 - 197
CHAPTER12 TROUBLESHOOTING
Corres-
SM213
Clock data read
request
OFF : Ignored
ON : Read request
• When this relay is ON, clock data is read to SD210 to
SD213 as BCD values.
U M9028 6
Turned ON when access can be made to the CPU
OFF : CPU No.1 preparation
module No.1 from the other CPU module at power-on
CPU No.1 preparation uncompleted
SM220 or reset operation. SM220 is used as interlock for QnU
completed ON : CPU No.1 preparation
completed
accessing the CPU module No.1 when the multiple
CPU synchronous setting is asynchronous. 7
Turned ON when access can be made to the CPU
OFF : CPU No.2 preparation
module No.2 from the other CPU module at power-on
CPU No.2 preparation uncompleted
SM221 or reset operation. SM221 is used as interlock for
completed ON : CPU No.2 preparation
completed
accessing the CPU module No.2 when the multiple
CPU synchronous setting is asynchronous. S (When status
8
New QnU*8
Turned ON when access can be made to the CPU changed)
OFF : CPU No.3 preparation
module No.3 from the other CPU module at power-on
CPU No.3 preparation uncompleted
SM222 or reset operation. SM222 is used as interlock for
completed ON : CPU No.3 preparation
accessing the CPU module No.3 when the multiple
completed
CPU synchronous setting is asynchronous.
*5: The Universal model QCPU except the Q00UJCPU, Q00UCPU, Q01UCPU, and Q02UCPU.
*6: The relevant modules are as follows:
• The Universal model QCPU whose serial number (first five digits) is "10012" or later.
• Q13UDHCPU, Q26UDHCPU
*8: The Universal model QCPU except the Q00UJCPU.
12 - 198
Table12.19 Special relay
Corres-
Set by ponding Corresponding
Number Name Meaning Explanation
(When Set) ACPU CPU
M9
• Goes OFF when reset of the No. 1 CPU is canceled.
OFF : No. 1 CPU reset • Comes ON when the No. 1 CPU is resetting
SM240 No. 1 CPU reset flag cancel (including the case where the CPU module is
ON : No. 1 CPU resetting removed from the base).
The other CPUs are also put in reset status.
• Goes OFF when reset of the No. 2 CPU is canceled.
• Comes ON when the No. 2 CPU is resetting
OFF : No. 2 CPU reset Q00/Q01*1
(including the case where the CPU module is
SM241 No. 2 CPU reset flag cancel Qn(H)*1
removed from the base).
ON : No. 2 CPU resetting QnPH
The other CPUs result in "MULTI CPU DOWN" (error
code: 7000). QnU*8
12 - 199
CHAPTER12 TROUBLESHOOTING
SM257
module 1 information ON : Does not read
OFF : Writes
indicate whether to read from the link module.
• For refresh from CPU module to link (B, W, etc.),
U New
3
ON : Does not write designate whether to write to the link module.
• Goes ON for standby network
OFF : Operative network
SM260 (If no designation has been made concerning active S (Initial) New
ON : Standby network
MELSECNET/10,
MELSECNET/H OFF : Reads
or standby, active is assumed.)
• For refresh from link to CPU module (B, W, etc.)
12
SM261 U New
module 2 information ON : Does not read indicate whether to read from the link module.
OFF : Writes • For refresh from CPU module to link (B, W, etc.),
SM262 U New
ON : Does not write designate whether to write to the link module.
• Goes ON for standby network Qn(H)
OFF : Operative network
SM265 (If no designation has been made concerning active S (Initial) New QnPH
ON : Standby network
MELSECNET/10, or standby, active is assumed.) QnPRH
MELSECNET/H OFF : Reads • For refresh from link to CPU module (B, W, etc.)
SM266 U New
module 3 information ON : Does not read indicate whether to read from the link module.
SM267
OFF : Writes
ON : Does not write
• For refresh from CPU module to link (B, W, etc.),
designate whether to write to the link module.
U New
6
• Goes ON for standby network
OFF : Operative network
SM270 (If no designation has been made concerning active S (Initial) New
ON : Standby network
or standby, active is assumed.)
SM271
MELSECNET/10,
MELSECNET/H OFF : Reads • For refresh from link to CPU module (B, W, etc.)
U New
7
module 4 information ON : Does not read indicate whether to read from the link module.
OFF : Writes • For refresh from CPU module to link (B, W, etc.),
SM272 U New
ON : Does not write designate whether to write to the link module.
12 - 200
Table12.19 Special relay
Corres-
Set by ponding Corresponding
Number Name Meaning Explanation
(When Set) ACPU CPU
M9
• The SFC program starting mode in the SFC setting
of the PLC parameter dialog box is set as the initial
SFC program start OFF : Initial start M9102form
SM322 value. S (Initial)/U
status ON : Resume start at change
AT initial start: OFF
At continued start: ON
OFF : Continuous transition
Presence/absence of Set the presence/absence of continuous transition for
not effective
SM323 continuous transition the block where "Continuous transition bit" of the SFC U M9103
ON : Continuous transition
for entire block data device has not been set.
effective
• OFF during operation in the continuous transition S (Instruction
M9104 Q00J/Q00/Q01*1
OFF : When transition is mode or during continuous transition, and ON when execution)
Continuous transition Qn(H)
SM324 executed continuous transition is not executed.
prevention flag QnPH
ON : When no transition • Always ON during operation in the no continuous S (Status change) New
QnPRH
transition mode.
QnU
Select whether the coil outputs of the active steps are
held or not at the time of a block stop.
• As the initial value, the output mode at a block stop in
Output mode at block OFF : OFF
SM325 the parameter is OFF when the coil outputs are OFF, S (Initial)/U M9196
stop ON : Preserves
and ON when the coil outputs are held.
• All coil outputs go OFF when this relay is OFF.
• Coil outputs are preserved when this relay is ON.
Selects the device status when the stopped CPU is run
SFC device clear OFF : Clear device
SM326 after the sequence program or SFC program has been U New
mode ON : Preserves device
modified when the SFC program exists.
Qn(H)
OFF : Hold step output Select the device status at the time of switching from QnPH
Output during end step S (Initial)/U
SM327 turned OFF (cleared) STOP to program write to RUN.(All devices except the New QnPRH
execution QnU
ON : Hold step output held step relay)
U Q00J/Q00/Q01*1
Select whether clear processing will be performed or
not if active steps other than the ones being held exist
in the block when the end step is reached.?
OFF : Clear processing is • When this relay turns OFF, all active steps are
Clear processing
performed. forcibly terminated to terminate the block. Q00J/Q00/Q01*1
SM328 mode when end step U New
ON : Clear processing is not • When this relay is ON, the execution of the block is QnU
is reached
performed. continued as-is.
• If active steps other than the ones being held do not
exist when the end step is reached, the steps being
held are terminated to terminate the block.
Select whether the low speed execution type program
will be executed in the asynchronous mode or in the
synchronous mode.
• Asynchronous mode (this relay is turned OFF.)
Mode in which the operation of the low speed
Operation mode for
OFF : Asynchronous mode execution type program is performed continuously Qn(H)
SM330 low speed execution U New
ON : Synchronous mode within the excess time. QnPH
type program
• Synchronous mode (this relay is turned ON.)
Mode in which the operation of the low speed
execution type program is not performed
continuously and operation is performed from the
next scan if there is excess time.
• Indicates whether the normal SFC program is being
Normal SFC program OFF : Not executed executed or not.
SM331
execution status ON : Being executed • Used as an SFC control instruction execution
Qn(H)*3
interlock.
S (Status change) New QnPH*4
Program execution • Indicates whether the program execution
QnPRH
management SFC OFF : Not executed management SFC program is being executed or not.
SM332
program execution ON : Being executed • Used as an SFC control instruction execution
status interlock.
• The status of the intelligent function module access
ON indicates completion of instruction executed immediately before is stored. Qn(H)
SM390 Access execution flag intelligent function module (This data is overwritten when the intelligent function S (Status change) New QnPH
access module access instruction is executed again.) QnPRH
• Used by the user in a program as a completion bit.
GINT instruction Indicates execution status of the S(P).GINT instruction.
OFF : Not executed S (Instruction
SM391 execution completion • Turned OFF before the instruction is executed. New QnU
ON : Execution completed execution)
flag • Turned ON after the instruction is completed.
*1: This applies to the CPU of function version B or later.
*3: The module whose first 5 digits of serial No. is "04122" or later.
*4: The module whose first 5 digits of serial No. is "07032" or later.
12 - 201
CHAPTER12 TROUBLESHOOTING
Corres-
ON S (Every END
SM400 Always ON
OFF
• Normally is ON
processing)
M9036
QCPU
3
ON S (Every END
SM401 Always OFF • Normally is OFF M9037
OFF processing)
S (Every END
• After RUN, OFF for 1 scan only. New Q00J/Q00/Q01
processing)
12 - 202
Table12.20 Special relay
Corres-
Set by ponding Corresponding
Number Name Meaning Explanation
(When Set) ACPU CPU
M9
• This relay alternates between ON and OFF at
intervals of the time (unit: ms) specified in SD415.
• When Programmable Controller power supply is Qn(H)
n(ms) turned ON or a CPU module reset is performed, QnPH
SM415 2n (ms) clock n(ms) S (Status change) New
goes from OFF to start. QnPRH
(Note that the ON-OFF status changes when the QnU
designated time has elapsed during the execution of
the program.)
SM420 User timing clock No.0 • Relay repeats ON/OFF switching at fixed scan M9020
SM421 User timing clock No.1 intervals. M9021
• When Programmable Controller power supply is
SM422 User timing clock No.2 turned ON or a CPU module reset is performed, M9022
SM423 User timing clock No.3 goes from OFF to start. M9023
(For the redundant CPU, however, this relay is
S (Every END
always OFF after system switching.) QCPU
processing)
• The ON/OFF intervals are set with the DUTY
n2 scan n2 scan instruction
SM424 User timing clock No.4 M9024
DUTY n1 n2 SM420
n1 scan
n1: ON scan interval
n2: OFF scan interval
SM430 User timing clock No.5
SM431 User timing clock No.6
S (Every END Qn(H)
SM432 User timing clock No.7 • For use with SM420 to SM424 low speed programs New
processing) QnPH
SM433 User timing clock No.8
SM434 User timing clock No.9
Corres-
Set by ponding Corresponding
Number Name Meaning Explanation
(When Set) ACPU CPU
M9
OFF : Completed or not
Low speed program • Goes ON when low speed execution type program is S (Every END Qn(H)
SM510 executed New
execution flag executed. processing) QnPH
ON : Execution under way.
• When this relay goes from OFF to ON, the module Qn(H)
Reads module service OFF : Ignored
SM551 service interval designated by SD550 is read to U New QnPH
interval ON : Read
SD551 to SD552. QnPRH
Corres-
Set by ponding Corresponding
Number Name Meaning Explanation
(When Set) ACPU CPU
M9
• When this special relay is turned ON, I/O refresh is
performed after execution of the first program, and
the next program is then executed.
Program to program I/ OFF : Not refreshed
SM580 When a sequence program and an SFC program are U New Q00J/Q00/Q01*1
O refresh ON : Refreshed
to be executed, the sequence program is executed,
I/O refresh is performed, and the SFC program is
then executed.
12 - 203
CHAPTER12 TROUBLESHOOTING
SM601
Memory card protect
flag
OFF : No protect
ON : Protect
• Goes ON when memory card protect switch is ON S (Status change) New 3
OFF : No drive 1
SM602 Drive 1 flag • Turns ON when the mounted memory card is RAM S (Status change) New
ON : Drive 1 present
OFF : No drive 2
SM603 Drive 2 flag
OFF : No drive 3
Q00J/Q00/Q01
Qn(H) 7
SM622 Drive 3 flag • Always ON S (Initial) New QnPH
ON : Drive 3 present
QnPRH
QnU*2
*1: The Universal model QCPU except the Q00UJCPU, Q00UCPU, and Q01UCPU.
*2: The Universal model QCPU except the Q00UJCPU.
12 - 204
Table12.23 Special relay
Corres-
Set by ponding Corresponding
Number Name Meaning Explanation
(When Set) ACPU CPU
M9
Qn(H)
OFF : File register not used QnPH
SM650 Comment use • Goes ON when comment file is in use S (Status change) New
ON : File register in use QnPRH
QnU
OFF : Internal memory
Qn(H)
execution • Goes ON while boot operation is in process
S (Status change) New QnPH
ON : Boot operation in • Goes OFF if boot designation switch is OFF
QnPRH
progress
SM660 Boot operation
OFF : Program memory
execution Q00J/Q00/Q01
• Goes ON while boot operation is in process S (Status change) New
ON : Boot operation in QnU*1
progress
• Turned ON when latch data backup to the standard
Latch data backup to
OFF : Not completed ROM is completed.
SM671 standard ROM S (Status change) New QnU
ON : Completed • Time when the latch data backup to the standard
completion flag
ROM was performed is stored in SD672 or later.
• Goes ON when access is made to area outside the
Memory card file Qn(H)
OFF : Within access range range of file register of memory card(Set within END
SM672 register access range S/U New QnPH
ON : Outside access range processing.)
flag QnPRH
• Reset at user program
• Turned ON when data cannot be backuped to the
Error completion of
OFF : No Error standard ROM by the latch data backup normally.
SM675 latch data backup to S New
ON : Error • Turned OFF when data is backuped to the standard
standard ROM
ROM by the latch data backup normally.
• If latch data backup is performed when SM676 is
ON, restore the data every time turning ON from
Specification of OFF the power supply from the next power-on.
OFF : Not specified
SM676 restration repeated • Delete the backuped latch data, or restore the data U New
ON : Specified
execution every time turning ON from OFF the power supply
until the latch data backup operation will be executed
again.
OFF : Write error • Turns ON if a write error is detected at writing to
Program memory write
SM680 ON : Write not executed/ program memory (flash ROM). S (At write) New
error
normal Turns OFF by the write direction.
• Turns ON when writing to the program memory (flash
Program memory OFF : During writing
SM681 ROM) is in progress, and turns OFF when writing is S (At write) New QnU
writing flag ON : Write not executed
completed.
OFF : Overwrite count is
Program memory
100,000 or more • Turns ON when the overwrite count of program
SM682 overwrite count error S (At write) New
ON : Overwrite count is less memory (flash ROM) reaches 100,000.
flag
than 100,000
OFF : Write error • Turns ON when write error is detected at writing to
Standard ROM write
SM685 ON : Write not executed/ standard ROM (flash ROM). S (At write) New
error
normal • Turns OFF by the write direction.
• Turns ON when writing to the standard ROM (flash
Standard ROM writing OFF : During overwriting
SM686 ROM) is in progress, and turns OFF when writing is S (At write) New
flag ON : Overwrite not executed
completed.
OFF : Overwrite count is
Standard ROM • Turns ON when the overwrite count of standard
100,000 or more
SM687 overwrite count error ROM (flash ROM) reaches 100,000. S (At write) New
ON : Overwrite count is less
flag (It is necessary to change CPU module.)
than 100,000
OFF : Backup start
preparation not
Backup start Turns on when the backup start preparation is
SM691 completed S (Status change) New
preparation status flag completed.
ON : Backup start
preparation completed QnU*3
*1: The Universal model QCPU except the Q00UJCPU, Q00UCPU, and Q01UCPU.
*3: The modules whose serial number (first five digits) is "10102" or later are the relevant models. (Except the Q00UJCPU, Q00UCPU, and Q01UCPU)
12 - 205
CHAPTER12 TROUBLESHOOTING
3
Number of output • Used for the PR, PRC, BINDA, DBINDA, BINHA, QnPH
SM701 output characters and the U M9049
characters selection DBINHA, BCDDA, DBCDDA, or COMRD instruction QnPRH
output pattern
QnU
OFF : Search next • Designates method to be used by search instruction.
SM702 Search method U New
ON : 2-part search • Data must be arranged for 2-part search.
12
• The sort instruction is used to designate whether
OFF : Ascending order
SM703 Sort order data should be sorted in ascending order or in U New QCPU
ON : Descending order
descending order.
• Goes ON when all data conditions have been met for S (Instruction
New
OFF : Non-match found the BKCMP instruction. execution)
SM704 Block comparison
ON : All match • Goes ON when all data conditions have been met for S (Instruction
New
the DBKCMP instruction. execution)
Turns on when the data to be compared by the DT or
DT/TM instruction OFF : Improper data not QnU*2
TM instruction is not recognized as date data or time S (Instruction
SM709 improper data detected New
data, or the device (3 words) to be compared exceeds execution) or U
detection flag ON : Improper data detected
the specified device range.
CHK instruction OFF : Conditions priority • Remains as originally set when OFF. S (Instruction
Qn(H) 6
SM710 New QnPH
priority ranking flag ON : Pattern priority • CHK priorities updated when ON. execution)
QnPRH
OFF : During DI S (Instruction
SM715 EI flag • ON when EI instruction is being executed. New QCPU
ON : During EI execution)
Turns on when all data conditions are confirmed that 7
they are met by the DBKCMP instruction.
Block comparison
OFF : Mismatch found (Initial execution type program, scan execution type
SM716 (Except an interrupt
ON : No mismatch program, stand-by type program executed from initial
program)
execution type program or scan execution type
program) QnU*2 8
Turns on when all data conditions are confirmed that
S (Instruction
they are met by the DBKCMP instruction. New
Block comparison OFF : Mismatch found execution)
SM717 (Interrupt program, fixed scan execution type program,
(Interrupt program) ON : No mismatch
stand-by type program executed from interrupt program
or fixed scan execution type program)
Turns on when all data conditions are confirmed that
*1: The module whose first 5 digits of serial No. is "09042" or later.
*2: The relevant modules are as follows:
• The Universal model QCPU whose serial number (first five digits) is "10102" or later.
• Q00UJCPU, Q00UCPU, Q01UCPU
*3: The relevant modules are as follows:
• The Universal model QCPU whose serial number (first five digits) is "10102" or later.
• Q00UCPU, Q01UCPU
12 - 206
Table12.24 Special relay
Corres-
Set by ponding Corresponding
Number Name Meaning Explanation
(When Set) ACPU CPU
M9
OFF : Not executed by
• During OFF, XCALL instructions will not be executed
XCALL instruction execution condition
even if execution condition is risen.
SM734 execution condition risen U New Qn(H)*1
• During ON, XCALL instructions will be executed
designation ON : Executed by execution
when execution condition is risen.
condition risen
OFF : SFC comment readout
instruction is • Turns on the instructions, (S(P).SFCSCOMR) to Qn(H)*2
SFC comment readout
inactivated. read the SFC step comments and (S(P).
SM735 instruction in S (status change) New QnPH*3
ON : SFC comment readout SFCTCOMR) to read the SFC transition condition
execution flag QnPRH*3
instruction is comments.
activating.
OFF : Instruction not
MSG instruction S (Instruction Qn(H)
SM738 executed • Goes ON when MSG instruction is executed New
reception flag execution) QnPRH
ON : Instruction execution
Scaling instruction OFF : Search next Determines a search method when the scaling
SM750 U New QnU*8
search method setting ON : 2-part search instruction is executed.
PID bumpless Q00J/Q00/Q01*4
processing OFF : Matched • Specifies whether to match the set value (SV) with Qn(H)
SM774 U New
(for complete ON : Not matched the process value (PV) or not in the manual mode. QnPRH
derivative) QnU
• Select whether link refresh processing will be
OFF : Performs link refresh Q00J/Q00/Q01
performed or not when only communication with the
ON : Performs no link U New Qn(H)
CPU module is made at the execution of the COM
refresh QnPH
Selection of refresh instruction.
processing during
SM775 OFF : Performs refresh Q00J/Q00/Q01*4
COM/CCOM
instruction execution processes other than • Select whether to perform refresh processes other Qn(H)*5
an I/O refresh than an I/O refresh set by SD778 when the COM or U New QnPH*3
ON : Performs refresh set CCOM instruction is executed. QnPRH
by SD778 QnU
• Set whether the local device of the subroutine
Enable/disable local OFF : Local device disabled
SM776 program called at execution of the CALL instruction U New Qn(H)
device at CALL ON : Local device enabled
is valid or invalid. QnPH
Enable/disable local QnPRH
OFF : Local device disabled • Set whether the local device at execution of the
SM777 device in interrupt U New QnU*9
ON : Local device enabled interrupt program is valid or invalid.
program
Q00J/Q00/Q01*4
PID bumpless
OFF : Matched • Specifies whether to match the set value (SV) with Qn(H)*6
SM794 processing(for U New
ON : Not matched the process value (PV) or not in the manual mode. QnPRH
incomplete derivative)
QnU
*1: The module whose first 5 digits of serial No. is "06082" or later.
*2: The module whose first 5 digits of serial No. is "07012" or later.
*3: The module whose first 5 digits of serial No. is "07032" or later.
*4: This applies to the CPU module of function version B or later.
*5: The module whose first 5 digits of serial No. is "04012" or later.
*6: The module whose first 5 digits of serial No. is "05032" or later.
*8: The relevant modules are as follows:
• The Universal model QCPU whose serial number (first five digits) is "10102" or later.
• Q00UJCPU, Q00UCPU, Q01UCPU
*9: The Universal model QCPU except the Q00UJCPU.
12 - 207
CHAPTER12 TROUBLESHOOTING
*7: The Universal model QCPU except the Q00UJCPU, Q00UCPU, Q01UCPU, and Q02UCPU.
(9) Debug 7
Table12.25 Special relay
Corres-
12 - 208
(10) A to Q conversion correspondences
Special relays SM1000 to SM1255 are the relays which correspond to ACPU special relays
M9000 to M9255 after A to Q conversion.
(However, the Basic model QCPU and Redundant CPU do not support the A to Q
conversion.)
These special relays are all set by the system, and cannot be set by the user program.
To turn them ON/OFF by the user program, change the special relays in the program into
those of QCPU.
However, some of SM1084 and SM1200 to SM1255 (corresponding to M9084 and M9200 to
M9255 before conversion) can be turned ON/OFF by the user program, if they could be
turned ON/OFF by the user program before conversion.For details on the ACPU special
relays, see the user's manuals for the individual CPUs, and MELSECNET or MELSECNET/
B Data Link System Reference Manuals
Check "Use special relay/special register from SM/SD1000" for "A-PLC" on the PLC system tab of PLC parameter in GX
Developer when the converted special relays are used with the High Performance model QCPU, Process CPU, and
Universal model QCPU.
When not using the converted special relays, uncheck "Use special relay/special register from SM/SD1000" to save the time
taken for processing special relays.
Remark
The following are additional explanations about the Special Relay for Modification column.
When a special relay for modification is provided, the device number should be changed to the provided QCPU special
relay.
When is provided, the converted special relay can be used for the device number.
When is provided, the device number does not work with QCPU.
12 - 209
CHAPTER12 TROUBLESHOOTING
OFF : Normal
• Turns ON when the battery voltage drops to or below the
specified.
Qn(H)
QnPH
12
M9007 SM1007 – Battery low latch
ON : Battery low • Remains ON if the battery voltage returns to normal QnU*1
thereafter.
Self-diagnosis OFF : No error • Turned on when error is found as a result of self-
M9008 SM1008 SM1
error ON : Error diagnosis.
• Turned on when OUT F of SET F instruction is
Annunciator OFF : No F number detected
M9009 SM1009 SM62 executed.
detection ON : F number detected
• Switched off when SD1124 data is cleared to zero.
• Turned on when operation error occurs during execution
M9016 SM1016
Data memory clear OFF : lgnored
• Clears the data memory including the latch range (other
than special relays and special registers) in remote run Qn(H)
7
flag ON : Output claered
mode from computer, etc. when SM1016 is on. QnPH
• Clears the unlatched data memory (other than special
Data memory clear OFF : lgnored
M9017 SM1017 relays and special registers) in remote run mode from
flag ON : Output claered
computer, etc. when SM1017 is on. 8
• Relay which repeats on/off at intervals of predetermined
User timing clock
M9020 SM1020 – scan.
No.0
• When power is turned on or reset is per-formed, the clock
starts with off.
User timing clock Set the intervals of on/off by DUTY instruction.
M9021 SM1021 –
No.1
12 - 210
Table12.27 Special relay
ACPU Special Special
Corresponding
Special Relay after Relay for Name Meaning Details
CPU
Relay Conversion Modification
• Alternates between ON and OFF according to the
seconds specified at SD414. (Default: n = 30)
2n minute clock(1 ns • Not turned on or off per scan but turned on and off even
M9034 SM1034 –
minute clock)*2 ns during scan if corresponding time has elapsed.
• Starts with off when Programmable Controller power
supply is turned on or CPU module reset is performed.
ON
M9036 SM1036 – Always ON
OFF • Used as dummy contacts of initialization and application Qn(H)
instruction in sequence program. QnPH
ON • SM1038 and SM1037 are turned on and off without regard
M9037 SM1037 – Always OFF QnU*1
to position of key switch on CPU module front. SM1038
OFF
and SM1039 are under the same condition as RUN status
except when the key switch is at STOP position, and
ON for 1 scan only ON turned off and on. Switched off if the key switch is in STOP
M9038 SM1038 – 1 scan
after RUN OFF position. SM1038 is on for one scan only and SM1039 is
off for one scan only if the key switch is not in STOP
RUN flag(After position.
ON
M9039 SM1039 – RUN, OFF for 1 1 scan
scan only) OFF
OFF : PAUSE disabled Qn(H)
M9040 SM1040 SM206 PAUSE enable coil • When RUN key switch is at PAUSE position or pause
ON : PAUSE enabled QnPH
contact has turned on and if SM1040 is on, PAUSE mode
PAUSE status OFF : PAUSE not in effect is set and SM1041 is turned on.
M9041 SM1041 SM204
contact ON : PAUSE in effect
STOP status OFF : STOP not in effect • Switched on when the RUN key switch or RUN/STOP
M9042 SM1042 SM203 Qn(H)
contact ON : STOP in effect switch is in STOP position.
QnPH
OFF : Sampling trace in • Turned on upon completion of sampling trace performed QnU*1
Sampling trace progress the number of times preset by parameter after STRA
M9043 SM1043 SM805
completed ON : Sampling trace instruction is executed.
completed Reset when STRAR instruction is executed.
• Turning on/off SM1044 can execute STRA/STRAR
OFF ON Same as STRA instruction.
instruction (SM1044 is forcibly turned on/off by a peripheral device.)
execution When switched from OFF to ON: STRA instruction
M9044 SM1044 SM803 Sampling trace
ON OFF Same as STRAR When switched from ON to OFF: STRAR instruction
instruction The value stored in SD1044 is used as the condition for Qn(H)
execution the sampling trace. QnPH
At scanning, at time Time (10 ms unit)
• The SM1045 relay is turned on to reset the WDT when the
Watchdog timer OFF : Does not reset WDT ZCOM instruction and data communication request batch
M9045 SM1045
(WDT) reset ON : Resets WDT processing are executed (used when the scan time
exceeds 200 ms).
Qn(H)
OFF : Trace not in progress
M9046 SM1046 SM802 Sampling trace • Switched on during sampling trace. QnPH
ON : Trace in progress
QnU*1
OFF : Sampling trace • Sampling trace is not executed unless SM1047 is turned
Sampling trace
M9047 SM1047 SM801 suspended ON.
preparations
ON : Sampling trace started Sampling trace is suspended when SM1047 goes OFF.
• When SM1049 is OFF, characters up to NULL (00H) code
Switching the OFF : Output until NULL
are output.
M9049 SM1049 SM701 number of output code encountered
• When SM1049 is ON, ASCII codes of 16 characters are
characters ON : 16 characters output
output. Qn(H)
• Switched ON to disable the CHG instruction. QnPH
CHG instruction OFF : Enabled
M9051 SM1051 • Switched ON when program transfer is requested.
execution disable ON : Disable
Automatically switched OFF when transfer is complete.
• When SM1052 is ON, the SEG instruction is executed as
SEG instruction OFF : 7SEG segment display an I/O partial refresh instruction.
M9052 SM1052
switch ON : I/O partial refresh When SM1052 is OFF, the SEG instruction is executed as
a 7-SEG display instruction.
12 - 211
CHAPTER12 TROUBLESHOOTING
M9056 SM1056
Main side P, I set
OFF : Other than when P, I
set being requested 2
request ON : P, I set being • Provides P, I set request after transfer of the other
requested program (for example subprogram when main program is
OFF : Other than when P, I being run) is complete during run. Automatically switched
3
Sub side P, I set set being requested off when P, I setting is complete.
M9057 SM1057
request ON : P, I set being
requested
Main side P, I set Momentarily ON at P, I set
M9058 SM1058
completion completion • Turned ON once when the P, I set has been completed,
M9059 SM1059
Sub program P, I
set completion
Momentarily ON at P, I set
completion
and then turned OFF again.
12
OFF : Other than when P, I
Sub program 2 P, I set being requested
M9060 SM1060
set request ON : P, I set being • Provides P, I set request after transfer of the other
requested program (for example subprogram when main program is
OFF : Other than when P, I being run) is complete during run. Automatically switched
Sub program 3 P, I set being requested off when P, I setting is complete.
M9061 SM1061
set request ON : P, I set being
requested
M9070 SM1070
A8UPU/
A8PUJrequired
OFF : Read time not
shortened
• Turned ON to shorten the search time in the A8UPU/
A8PUJ.
6
search time*3 ON : Read time shortened (In this case, the scan time is extended by 10 %.) Qn(H)
It is set whether the error checks below are performed or not QnPH
7
when the END instruction is processed (to set the END
OFF : Error check executed instruction processing time).
M9084 SM1084 Error check
ON : No error check • Check for fuse blown.
• Check of battery
• Collation check of I/O module
8
• Turns ON when the detail factor of the operation error is
Operation error OFF : No error stored into SD1091.
M9091 SM1091
details flag ON : Error • Remains ON if the condition is restored to normal
thereafter.
OFF : SFC programs not
Presence/absence • Turned on if the SFC program is registered.
M9100 SM1100 SM320 used
of SFC program • Turned off if the SFC program is not registered.
ON : SFC programs used
12 - 212
Table12.27 Special relay
ACPU Special Special
Corresponding
Special Relay after Relay for Name Meaning Details
CPU
Relay Conversion Modification
OFF : Continuous transition
Presence/absence • Set whether continuous transition will be performed for the
not effective
M9103 SM1103 SM323 of continuous block where the "continuous transition bit" of the SFC
ON : Continuous transition
transition information device is not set.
effective
• OFF during operation in the continuous transition mode or
Continuous OFF : When transition is during continuous transition, and ON when continuous
M9104 SM1104 SM324 transition completed transition is not executed.
suspension flag ON : When no transition • Always ON during operation in the no continuous
transition mode.
Step transition
monitoring timer
M9108 SM1108 SM90
start (equivalent of
SD90)
Step transition
monitoring timer
M9109 SM1109 SM91
start (equivalent of
SD91)
Step transition
monitoring timer
M9110 SM1110 SM92
start (equivalent of
SD92)
Step transition • Turns ON when the measurement of the step transition
OFF : Monitoring timer reset
monitoring timer monitoring timer is started.
M9111 SM1111 SM93 ON : Monitoring timer reset
start (equivalent of Turning this relay OFF resets the step transition
start
SD93) monitoring timer.
Step transition
monitoring timer
M9112 SM1112 SM94
start (equivalent of
SD94) Qn(H)
Step transition QnPH
monitoring timer
M9113 SM1113 SM95
start (equivalent of
SD95)
Step transition
monitoring timer
M9114 SM1114 SM96
start (equivalent of
SD96)
• Selects the operation output when block stop is executed.
ON : Retains the ON/OFF status of the coil being used
by using operation output of the step being
Operation output OFF : Coil output OFF
M9196 SM1196 SM325 executed at block stop.
at block stop ON : Coil output ON
OFF : All coil outputs are turned off. (Operation output
by the SET instruction is retained regardless of
the ON/OFF status of SM1196.)
I/O numbers
SM SM
to be
1197 1198
displayed
M9197 SM1197
OFF OFF X/Y0 to 7F0 Switches I/O numbers in the fuse blow module storage
Switch between
X/Y800 to registers (SD1100 to SD1107) and I/O module verify error
blown fuse and I/O ON OFF
FF0 storage registers (SD1116 to SD1123) according to the
verify error display
X/Y1000 to combination of ON/OFF of the SM1197 and SM1198.
OFF ON
17F0
M9198 SM1198
X/Y1800 to
ON ON
1FF0
• Recovers the setting data stored in the CPU module at
Data recovery of
OFF : Data recovery disabled restart when sampling trace/status latch is executed.
M9199 SM1199 online sampling
ON : Data recovery enabled • SM1199 should be ON to execute again. (Unnecessary
trace/status latch
when writing the data again from peripheral devices.)
Corres-
Set by ponding Corresponding
Number Name Meaning Explanation
(When Set) ACPU CPU
M9
OFF : No time setting function Set this to ON when executing the time setting function
Time setting function
(SNTP client) execution (SNTP client).
SM1270 (SNTP client) U New
ON : Time setting function (Only when the time setting function is in "Use" with the
execution
(SNTP client) execution time setting parameter.) QnU*1
To clear the acumulated numeber (SD979 to 999) of
Remote password OFF : Normal
SM1273 mismatched remote passwords, the setting SM1273 is U New
mismatch count clear ON : Clear
executed.
12 - 213
CHAPTER12 TROUBLESHOOTING
Corres-
Corres-
Set by ponding Corresponding
Number Name Meaning Explanation
(When Set) ACPU CPU 6
M9
OFF : Redundant system
backup mode, stand-
• Turns on when the operating mode is redundant
SM1510 Operation mode alone system
ON : Redundant system
system separate.
S (Each END) New
7
separate mode
• Distinguishes between system A and system B.
System A identification • The flag status does not change even if the tracking cable is disconnected.
SM1511
flag
System A System B
When TRK. CABLE ERR.
(error code: 6210) occurs (Unknown) S (Initial) New
8
System B identification SM1511 ON OFF OFF
SM1512
flag QnPRH
SM1512 OFF ON OFF
Debug mode status OFF : Not in debug mode • Turns on when the redundant system operating
SM1513 S (Initial) New
flag ON : Debug mode mode is set to debug mode.
12 - 214
Table12.29 Special relay
Corres-
Set by ponding Corresponding
Number Name Meaning Explanation
(When Set) ACPU CPU
M9
• Turns on when the CPU module is started up by the
OFF : Power supply on
system switching (switching from the standby system
CPU module startup startup
SM1517 to the control system). Remains OFF when the S (Status change) New
status ON : Operation system
standby system is switched to the control system by
switch start up
a power-ON startup.
• Turns ON once switch between standby system to
Standby system to
ON control system, (ON for 1 scan only) occurs.
SM1518 control system 1 scan S (Each END) New
OFF • This status flag can only be used for scan execution
switching status flag
type programs.
• On the last operation Control System was System
Previous Control
ON B,if power supply is supplied, or reset is released on
SM1519 System Identification 1 scan S (Each END) New
OFF both SYSTEM together,After RUN, ON for 1 scan
Flag
only by System A side.
SM1520 SM1520 Block 1
SM1521 SM1521 Block 2
SM1522 SM1522 Block 3
SM1523 SM1523 Block 4
SM1524 SM1524 Block 5
SM1525 SM1525 Block 6
SM1526 SM1526 Block 7
SM1527 SM1527 Block 8
SM1528 SM1528 Block 9 • When data is transferred
QnPRH
SM1529 SM1529 Block 10 based on the tracking
SM1530 SM1530 Block 11 setting of the redundant
parameter dialog box, the
SM1531 SM1531 Block 12
target block is specified
SM1532 SM1532 Block 13 as trigger.
SM1533 SM1533 Block 14
Data tracking transfer OFF : No trigger • When "Auto Tracking
SM1534 SM1534 Block 15 S (initial)/U New
trigger specification ON : Trigger block No.1" is enabled in
SM1535 SM1535 Block 16 the tracking setting,
SM1536 SM1536 Block 17 SM1520 is turned ON by
the system at power ON/
SM1537 SM1537 Block 18
STOP to RUN. In other
SM1538 SM1538 Block 19 cases, SM1520 to
SM1539 SM1539 Block 20 SM1583 are turned ON
by the user.
SM1540 SM1540 Block 21
SM1541 SM1541 Block 22
SM1542 SM1542 Block 23
SM1543 SM1543 Block 24
SM1544 SM1544 Block 25
SM1545 SM1545 Block 26
SM1546 SM1546 Block 27
SM1547 SM1547 Block 28
SM1548 SM1548 Block 29
12 - 215
CHAPTER12 TROUBLESHOOTING
12 - 216
Table12.29 Special relay
Corres-
Set by ponding Corresponding
Number Name Meaning Explanation
(When Set) ACPU CPU
M9
Sets the operation for the case accessing buffer
memory of the intelligent function module mounted on
the extension base unit from the standby system CPU
in separate mode.
OFF : “OPERATION ERROR” (error code: 4112) will be
Setting to access
OFF : Error returned when accessing buffer memory of the
SM1593 extension base unit of QnPRH*2
ON : Ignored intelligent function module on the extension base
standby system CPU
unit from the standby system CPU.
ON : No processing is performed when accessing
buffer memory of intelligent function module on U
the extension base unit from the standby system New
CPU.
• When SM1595 is turned from OFF to ON, memory
copy from control system to standby system starts.
OFF : Start memory copy
Memory copy to other Note that when SM1595 is turned from OFF to ON,
SM1595 ON : No memory copy
system start flag memory copy does not start if the I/O No. of the copy
initiated
destination (standby system CPU module: 3D1H) is
not stored in SD1595.
OFF : Memory copy not • Turns on while memory is copied to other system.
Memory copy to other S (Starting to
SM1596 executed • Turns off when memory copy execution has
system status flag copy/finish)
ON : Memory copy executed completed. QnPRH
OFF : Memory copy not
Memory copy to other
completed • Turns on once the memory copying to the other
SM1597 system completion S (finish)/U
ON : Memory copy system has completed.
flag
completed
New
OFF : Copy standard ROM
Copy contents of • If set to on by user, the standard ROM data is not
data
SM1598 standard ROM during copied to the other system while memory copy is U
ON : Standard ROM data is
memory copy executing.
not copied
*2: The module whose first 5 digits of serial No. is “09012” or later.
12 - 217
CHAPTER12 TROUBLESHOOTING
6
tracking (3) In either of the following statuses, the system
switching disable status can also be canceled by
this relay.
•Multiple-block online program change redundant
tracking execution status New QnPRH
•File batch online program change redundant
(1)
tracking execution status
Set whether the tracking of the following data will
7
be executed or not during online program change
redundant tracking.
•Device memory
(Including SM/SD that will automatically execute
tracking)
8
Transfer tracking data OFF : No device tracking •PIDINIT information, S.PIDINIT information, SFC
SM1710 during online program ON : Transfer device information U
change enable flag memory (2) SM1710 can be also used to set whether tracking
will be executed or not while online change of
multiple program blocks or batch of files is being
12 - 218
Table12.31 Special relay
Corres-
Set by ponding Corresponding
Number Name Meaning Explanation
(When Set) ACPU CPU
M9
SM1712 SM1712 Block 1
SM1713 SM1713 Block 2
SM1714 SM1714 Block 3
SM1715 SM1715 Block 4
SM1716 SM1716 Block 5
SM1717 SM1717 Block 6
SM1718 SM1718 Block 7
SM1719 SM1719 Block 8
SM1720 SM1720 Block 9
SM1721 SM1721 Block 10
SM1722 SM1722 Block 11
SM1723 SM1723 Block 12
SM1724 SM1724 Block 13
SM1725 SM1725 Block 14
SM1726 SM1726 Block 15
SM1727 SM1727 Block 16
SM1728 SM1728 Block 17
SM1729 SM1729 Block 18
SM1730 SM1730 Block 19
SM1731 SM1731 Block 20
SM1732 SM1732 Block 21
SM1733 SM1733 Block 22
SM1734 SM1734 Block 23
Turns ON only during one
SM1735 Transfer trigger OFF : Transfer uncompleted SM1735 Block 24 scan when the transmission
S (status change) New QnPRH
SM1736 completion flag ON : Transfer completed SM1736 Block 25 of the corresponding block is
completed.
SM1737 SM1737 Block 26
SM1738 SM1738 Block 27
SM1739 SM1739 Block 28
SM1740 SM1740 Block 29
SM1741 SM1741 Block 30
SM1742 SM1742 Block 31
SM1743 SM1743 Block 32
SM1744 SM1744 Block 33
SM1745 SM1745 Block 34
SM1746 SM1746 Block 35
SM1747 SM1747 Block 36
SM1748 SM1748 Block 37
SM1749 SM1749 Block 38
SM1750 SM1750 Block 39
SM1751 SM1751 Block 40
SM1752 SM1752 Block 41
SM1753 SM1753 Block 42
SM1754 SM1754 Block 43
SM1755 SM1755 Block 44
SM1756 SM1756 Block 45
SM1757 SM1757 Block 46
SM1758 SM1758 Block 47
SM1759 SM1759 Block 48
12 - 219
CHAPTER12 TROUBLESHOOTING
*1: The "power supply 1" indicates the redundant power supply module mounted on the POWER 1 slot of the redundant base unit (Q38RB/Q68RB/Q65WRB).
The "power supply 2" indicates the redundant power supply module mounted on the POWER 2 slot of the redundant base unit (Q38RB/Q68RB/Q65WRB).
*2: The module whose first 5 digits of serial No. is "04012" or later.
However, for the multiple CPU system configuration, this applies to all CPU modules whose first 5 digits of serial No. are "07032" or later.
*3: The module whose first 5 digits of serial No. is "10042" or later.
12 - 220
12.8 SPECIAL REGISTER LIST
The special registers, SD, are internal registers with fixed applications in the Programmable
Controller.
For this reason, it is not possible to use these registers in sequence programs in the same way
that normal registers are used.
However, data can be written as needed in order to control the CPU modules.
Data stored in the special registers are stored as BIN values if no special designation has been
made to the contrary.
The heading descriptions in the following special register lists are shown in 4.1.
Do not change the values of special relays set by the system with user program or device test operations.
Doing so may result in system downtime or communication fault.
12 - 221
CHAPTER12 TROUBLESHOOTING
Corres-
• The minute and second that SD0 data was updated is stored as BCD 2-
digit code.
SD3 (Example) 35 min. 48 sec.
b15 to b8 b7 to b0
Minutes (0 to 59) Seconds (0 to 59) 3548H 6
Category codes which help indicate what type of information is being
stored in the common information areas (SD5 through SD15) and the
individual information areas (SD16 through SD26) are stored here.
The category code for judging the error information type is stored.
b15 to b8 b7 to b0
7
Individual information Common information
category codes category codes
12 - 222
Table12.34 Special register
Corres-
Set by ponding Corresponding
Number Name Meaning Explanation
(When Set) ACPU CPU
D9
• Common information corresponding to the error codes (SD0) is stored
here.
SD5 • The following ten types of information are stored here:
• The error common information type can be judged by the "common infor-
mation category code" in SD4. (The values of the "common information
category code" stored in SD4 correspond to following 1) to 8).)
1) Slot No.
SD6
Number Meaning
SD5 Slot No./CPU No./Base No. 1, 2, 3, 4
SD6 I/O No. 5
SD7
SD7 SD8
SD9
SD10
SD11 (Empty)
SD8 SD12
SD13
SD14
SD15
*1: For a multiple CPU system that consists of the Basic model QCPU, High
SD9
Performance model QCPU, Process CPU, Universal model QCPU, the
slot number or CPU number is stored depending on the error that
occurred.
Slot 0 in the multiple CPU system is the one on the slot on the right of the
SD10 rightmost CPU module.
(Refer to the corresponding error code for which number has been
stored.)
No. 1 CPU: 1, No. 2 CPU: 2, No. 3 CPU: 3, No. 4 CPU: 4
*2: If a fuse blown or I/O verify error occurred in the module loaded in the
SD11 MELSECNET/H remote I/O station, the network number is stored into the
upper 8 bits and the station number into the lower 8 bits.
Use the I/O No. to check the module where the fuse blown or I/O verify
error occurred.
*3: 255 is stored into SD5 of the Basic model QCPU when an instruction, etc.
SD12
has been executed for the module later than the one on the last slot
where a module can be mounted.
*4: Definitions of base No. and slot No.
<Base No.>
SD13 Value used to identify the base unit on which the CPU module has
Error common Error common been mounted. The following shows the definition of the base No. S (Error) New QCPU
information information
Base No. Definition
0 Indicates the main base unit mounted with the CPU
module.
SD14
1 to 7 Indicates the extension base unit. The stage
number setting made by the stage number setting
connector on the extension base unit is the base
No.
When stage number setting is extension 1:
Base No. = 1
when stage number setting is extension 7:
Base No. = 7
<Slot No.>
Value used to identify the slot of each base unit and the module
mounted on that slot.
•The I/O slot 0 (slot on the right side of the CPU slot) of the main base
unit is defined as the slot of "Slot No. = 0".
•The slot Nos. are consecutively assigned to the slots of the base
units in order of the main base unit and extension base units 1 to 7.
•When the number of base unit slots has been set in the I/O
assignment setting of the PLC parameter dialog box, the slot Nos.
are assigned for only the number of set slots.
*5: When 0FFFFH is stored into SD6 (I/O No.), the I/O No. cannot be
SD15
identified due to overlapping I/O No., etc. in the I/O assignment setting of
the PLC parameter dialog box. Therefore, identify the error location using
SD5.
2) File name/Drive name
Number Meaning (Example) File name =
SD5 Drive ABCDEFGH. IJK
b15 to b8 b7 to b0
SD6
42H(B) 41H(A)
SD7 File name 44H(D) 43H(C)
SD8 (ASCII code: 8 characters) 46H(F) 45H(E)
SD9
48H(H) 47H(G)
SD10 Extension 6 2EH(.)
49H(I) 2EH(.)
SD11 (ASCII code: 3 characters)
4BH(K) 4AH(J)
SD12
SD13
(Empty)
SD14
SD15
12 - 223
CHAPTER12 TROUBLESHOOTING
3
SD6
12
3) Time (value set)
Number Meaning
SD7 SD5 Time : 1 s units (0 to 999 s)
SD6 Time : 1ms units (0 to 65535ms)
SD7
SD8
SD9
SD10
6
SD8 SD11 (Empty)
SD12
SD13
SD14
SD15
7
4) Program error location
SD9
Number Meaning
SD5
SD6 File name
Error common Error common SD7 (ASCII code: 8 characters)
S (Error) New QCPU
SD10
information information SD8
SD9 Extension 6 2EH(.)
(ASCII code: 3 characters)
8
SD10
SD11 Pattern 7
SD12 Block No.
SD13 Step No./transition condition
SD14 Sequence step No. (L)
SD11 SD15 Sequence step No. (H)
SD14
SD15
12 - 224
Table12.34 Special register
Corres-
Set by ponding Corresponding
Number Name Meaning Explanation
(When Set) ACPU CPU
D9
Number Meaning
SD5
SD5 System switching condition 13
Control system switching
SD6
instruction argument
SD7
SD8
SD9
SD6 SD10
SD11 (Empty)
SD12
SD13
SD14
SD15
SD7
*13: Details of reason(s) for system switching
SD6 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
SD11 SD7 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
1 1
SD8 (SM1583) 0 0 0 0 0 0 0 0 0 0 0 0 0 0 (SM1568)
(Block64) (Block49)
SD9 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
SD12 SD15 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
*1: The module whose first 5 digits of serial No. is "07032" or later.
*2: The module whose first 5 digits of serial No. is "10042" or later.
12 - 225
CHAPTER12 TROUBLESHOOTING
12
SD6
SD7
Number Meaning 6
SD8 SD5 Data type 15
SD6
SD7
7
SD8
SD9
SD10 (Empty)
SD11
SD9
SD12
SD13
SD14
SD15 8
Error common Error common *15: Details of data classification
SD10 S (Error) New QnPRH
information information b15 b14 to b6 b5 b4 b3 b2 b1 b0 Each bit
0 0: Not sent
1: Being sent
SD13
SD14
SD15
12 - 226
Table12.34 Special register
Corres-
Set by ponding Corresponding
Number Name Meaning Explanation
(When Set) ACPU CPU
D9
• Individual information corresponding to error codes (SD0) is stored here.
• There are the following eight different types of information are stored.
• The error individual information type can be judged by the "individual
SD16 information category code" in SD4. (The values of the "individual infor-
mation category code" stored in SD4 correspond to following 1) to 8),
12), and 13).)
1) (Empty)
2) File name/Drive name
15 14 to 4 3 2 1 0 (Bit number)
0 0 to 0 0
*16: For details of the parameter No., refer to the User's Manual
(Function Explanation, Program Fundamentals) of the CPU
module used.
12 - 227
CHAPTER12 TROUBLESHOOTING
12 - 228
Table12.34 Special register
Corres-
Set by ponding Corresponding
Number Name Meaning Explanation
(When Set) ACPU CPU
D9
8) Reason(s) for system switching failure
Number Meaning
System switching prohibition
SD16 condition 14
SD17
SD18
SD19
SD20
SD21
(Empty)
SD22
SD23
SD24
SD25
SD26
Number Meaning
SD16 Parameter No.*16
SD17 CPU No. (1 to 4)
SD18
SD19
SD20
SD21
SD22 (Empty)
SD23
SD24
SD25
SD26
12 - 229
CHAPTER12 TROUBLESHOOTING
SD51
Battery low
latch
indicating where
battery voltage
alarm
error
1
S (Error) New 12
drop occurred
• In the alarm, data can be held within the time specified for battery low.
• The error indicates the complete discharge of the battery. QCPU
Bit pattern • Same configuration as SD51 above
indicating where • After the alarm is detected (ON), the alarm turns OFF by error detection
6
SD52 Battery low S (Error) New
battery voltage (ON). (For the Universal model QCPU only)
drop occurred • Turns to 0 (OFF) when the battery voltage returns to normal thereafter.
• Every time the input voltage falls to or below 85% (AC power)/65% (DC
Number of times power) of the rating during operation of the CPU module, the value is
AC/DC DOWN
SD53 for AC/DC DOWN incremented by 1 and stored in BIN code. S (Error) D9005
detection
detection • The counter repeats increment and decrement of the value ;
0 32767 -32768 0
7
Number of
Number of module • Value stored here is the lowest station I/O number of the module with
SD60 module with S (Error) D9000
with blown fuse the blown fuse.
blown fuse
SD61
I/O module
verify error
I/O module verify
error module
• The lowest I/O number of the module where the I/O module verification
S (Error) D9002
8
number took place.
number number
12 - 230
Table12.34 Special register
Corres-
Set by ponding Corresponding
Number Name Meaning Explanation
(When Set) ACPU CPU
D9
Annunciator Annunciator S (Instruction
SD62 • The first annunciator number (F number) to be detected is stored here. D9009
number number execution)
Number of Number of S (Instruction
SD63 • Stores the number of annunciators searched. D9124
annunciators annunciators execution)
SD64 When F goes ON due to OUT F or SET F instruction, the F numbers which D9125
go progressively ON from SD64 through SD79 are registered.
SD65 The F numbers turned OFF by RST F instruction are deleted from SD64 - D9126
SD79, and the F numbers stored after the deleted F numbers are shifted to
the preceding registers.
SD66 D9127
Execution of the LEDR instruction shifts the contents of SD64 to SD79 up
by one.
SD67 D9128
After 16 annunciators have been detected, detection of the 17th will not be
stored from SD64 through SD79.
SD68 D9129
SET SET SET RST SET SET SET SET SET SET SET
F50 F25 F99 F25 F15 F70 F65 F38 F110 F151 F210 LEDR
SD69 D9130
SD62 0 50 50 50 50 50 50 50 50 50 50 50 99 (Number
SD70 detected) D9131
QCPU
Table of SD63 0 1 2 3 2 3 4 5 6 7 8 9 8 (Number of
SD71 annunciators D9132
detected Annunciator detected) S (Instruction
annunciator detection number SD64 0 50 50 50 50 50 50 50 50 50 50 50 99 execution)
SD72 New
numbers SD65 0 0 25 25 99 99 99 99 99 99 99 99 15
SD66 0 0 0 99 0 15 15 15 15 15 15 15 70
SD73 New
SD67 0 0 0 0 0 0 70 70 70 70 70 70 65
SD68 0 0 0 0 0 0 0 65 65 65 65 65 38
SD74 New
SD69 0 0 0 0 0 0 0 0 38 38 38 38 110
SD70 0 0 0 0 0 0 0 0 0 110 110 110 151
SD75 SD71 0 0 0 0 0 0 0 0 0 0 151 151 210 New
(Number
SD72 0 0 0 0 0 0 0 0 0 0 0 210 0 detected)
SD76 SD73 0 0 0 0 0 0 0 0 0 0 0 0 0 New
SD74 0 0 0 0 0 0 0 0 0 0 0 0 0
SD77 SD75 0 0 0 0 0 0 0 0 0 0 0 0 0 New
SD76 0 0 0 0 0 0 0 0 0 0 0 0 0
SD78 SD77 0 0 0 0 0 0 0 0 0 0 0 0 0 New
SD78 0 0 0 0 0 0 0 0 0 0 0 0 0
SD79 SD79 0 0 0 0 0 0 0 0 0 0 0 0 0 New
S (Instruction
SD80 CHK number CHK number • Error codes detected by the CHK instruction are stored as BCD code. New
execution)
12 - 231
CHAPTER12 TROUBLESHOOTING
Stores the
D9
2
transmission
Transmission
speed specified in 96 : 9.6kbps, 192 : 19.2kbps, 384 : 38.4kbps, S (Power-ON or
SD100 speed storage New
the serial 576 : 57.6kbps, 1152 : 115.2kbps reset)
area
3
communication
setting.
b15 to b6 b5 b4 b3 to b0
Communication
Stores the
communication
setting specified in S (Power-ON or
Q00/Q01
Q00UJ
12
SD101 setting storage New Q00U
the serial reset) Q01U
area Sumcheck presence
communication
setting. Write during RUN setting 0: Absent Q02U*4
0: Disabled 1: Present
1: Enabled
* : Since the data is used by the system, it is undefined.
Stores the
transmission wait 0 : No waiting time
SD102
Transmission
wait time
storage area
time specifed in
the serial
10 to 150: Waiting time (unit: ms) S (Power-ON or
reset)
New 6
communication Defaults to 0.
setting.
Stores the preset Qn(H)
CH1 96 : 9600bps, 192 : 19.2kbps, 384 : 38.4kbps,
7
transmission QnPH
transmission 576 : 57.6kbps, 1152 : 115.2kbps
SD105 speed when GX S New QnPRH
speed setting *: Other than RS-232 connection holds the data at RS-232 connection.
Developer is
(RS-232)
used.
(When disconnected, the default value is 1152.) QnU*3
0:No factor
Battery life- b15 to b2 b1 b0 1:Foctor
Battery life- S (Status
SD119 prolonging New QnU
prolonging factor change)
factor b0: CPU switch setting
b1: Backup in execution by
latch data backup function
(to standard ROM)
*3: This applies to Universal model QCPUs except for the Built-in Ethernet port QCPU.
*4: The module whose first 5 digits of serial No. is "10102" or later.
12 - 232
Table12.34 Special register
Corres-
Set by ponding Corresponding
Number Name Meaning Explanation
(When Set) ACPU CPU
D9
SD130 • The numbers of output modules whose fuses have blown are input as a
bit pattern (in units of 16 points).
SD131 (If the module numbers are set by parameter, the parameter-set
numbers are stored.)
SD132 Bit pattern in units b15 b14 b13 b12 b11b10 b9 b8 b7 b6 b5 b4 b3 b2 b1 b0
of 16 points,
1 1
SD133 indicating the SD130 0 0 0 (YC0) 0 0 0 (Y80) 0 0 0 0 0 0 0 0
Fuse blown modules whose
1 1
SD134 module fuses have blown SD131 (Y1F0) 0 0 0 0 (Y1A0) 0 0 0 0 0 0 0 0 0 0
0: No blown fuse
SD135 1: Blown fuse 1 1
present SD137 0 0 0 0 (Y7B0) 0 0 0 0 0 0 0 (Y730) 0 0 0
• When I/O modules, of which data are different from those entered at S (Error) New Q00J/Q00/Q01
SD150
power-ON, have been detected, the I/O module numbers (in units of 16
SD151 points) are entered in bit pattern. (Preset I/O module numbers set in
parmeters when parameter setting has been performed.)
Bit pattern, in units
SD152
of 16 points, b15 b14 b13 b12 b11 b10 b9 b8 b7 b6 b5 b4 b3 b2 b1 b0
indicating the 1
SD153 SD150 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 (X Y)
modules with
I/O module 0
verify errors. 1
verify error SD151 0 0 0 0 0 0 ( X Y) 0 0 0 0 0 0 0 0 0
SD154 0: No I/O verify 190
errors
1: I/O verify error 1
SD155 SD157 0 ( X Y) 0 0 0 0 0 0 0 0 0 0 0 0 0 0
present 7E0
12 - 233
CHAPTER12 TROUBLESHOOTING
Corres-
b15 to b8 b7 to b4 b3 to b0
• The following bit patterns store the status of the LEDs on the CPU
module:
• 0 is off, 1 is on, and 2 is flicker.
b15 to b12b11 to b8 b7 to b4 b3 to b0
Q00J/Q00/Q01
S (Status Qn(H)
8) 7) 6) 5) 4) 3) 2) 1) New
change) QnPH
QnPRH
1): RUN 5): BOOT
2): ERR. 6): Empty Mode bit pattern
3): USER 7): Empty 0: OFF 1: Green
4): BAT. 8): MODE 2: Orange
Status of (The Basic model QCPU does not include 3) to 8).)
SD201 LED status
CPU-LED • The following bit patterns store the status of the LEDs on the CPU
module:
• 0 is off, 1 is on, and 2 is flicker.
b15 to b12b11 to b8 b7 to b4 b3 to b0
S (Status
8) 7) 6) 5) 4) 3) 2) 1) New QnU
change)
12 - 234
Table12.36 Special register
Corres-
Set by ponding Corresponding
Number Name Meaning Explanation
(When Set) ACPU CPU
D9
• Specify the LEDs to be turned off using this register, and turn SM202
from OFF to ON to turn off the specified LEDs.
USER and BOOT can be specified as the LEDs to be turned off.
• Specify the LEDs to be turned off in the following bit pattern.
(Turned off at 1, not be turned off at 0.)
b15 b8 b4 b0
Fixed Fixed Fixed Qn(H)
LED off Bit pattern of LED to 0 to 0 to 0 QnPH
SD202 U New
command that is turned off QnPRH
USER QnU
LED
BOOT
LED
2) 1)
• The LED display color of the LED status shown in SD201 1) to 8).
b15 b12 b11 b8 b7 b4 b3 b0
1)RUN LED
0: OFF
1: Green
2)ERROR LED
0: OFF
1: Red
3)USER LED
0: OFF
1: Red
LED display CPU-LED display S (status
SD204 4)BAT. LED New QnU
color color 0: OFF change)
1: Yellow
2: Green
5)BOOT LED
0: OFF
1: Green
6)Empty
7)Empty
8)MODE LED
0: OFF
1: Green
12 - 235
CHAPTER12 TROUBLESHOOTING
3
SD207 Priorities 1 to 4 D9038
• The Universal model QCPU sets execution/non-execution of LED
display of the error corresponding to the each priority ranking when the
error occurs.
• The setting areas for priorities are as follows:
b15 to b12 b11 to b8 b7 to b4 b3 to b0
SD207 Priority 4
SD208 Priority 8
Priority 3
Priority 7
Priority 2
Priority 6
Priority 1
Priority 5 D9039
12
SD208 Priorities 5 to 8 SD209 Priority 11 Priority 10 Priority 9 format
change Q00J/ Q00/Q01*9
(Priority 11 is valid when Redundant CPU is used.)
Qn(H)
LED display
U QnPH
priority ranking Default Value
SD207 = 4321H(0000H for Basic model QCPU) QnPRH
SD208 = 8765H(0700H for Basic model QCPU) QnU
(0765H for Redundant CPU)
SD209 = 00A9H(0000H for Basic model QCPU)
(0B09H for Redundant CPU)
• No display is made if "0" is set. 6
• In case of the Basic model QCPU, the ERR. LED turns ON when the
SD209 Priorities 9 to 11 annunciator turns ON, if "7" has been set to either of priorities 1 to 11. New
• In case of the Basic model QCPU, the ERR. LED does not turn ON
7
when the annumciator turns ON, if "7" has not been set to either of
priorities 1 to 11.
However, even if "0" has been set, information concerning CPU module
operation stop (including parameter settings) errors will be indicated by
the LEDs without conditions.
8
• The year (last two digits) and month are stored as BCD code as shown
below:
Year Month
Day Hour
• The minutes and seconds (after the hour) are stored as BCD code as
shown below:
Minute Second
12 - 236
Table12.36 Special register
Corres-
Set by ponding Corresponding
Number Name Meaning Explanation
(When Set) ACPU CPU
D9
• The year (first two digits) and the day of the week are stored as BCD
code as shown below.
b15 to b12 b11 to b8 b7 to b4 b3 to b0 Example:
1993, Friday
1905H
Clock data
SD213 Clock data (higher digits of Day of the week S (Request)/U D9028
year, day of week) 0 Sunday
Higher digits of year (19 or 20) 1 Monday
2 Tuesday
3 Wednesday
4 Thursday
5 Friday
6 Saturday
SD227 • The LED display device data at the time of CHK is not stored in the
Basic model QCPU and the Universal model QCPU.
The header I/O
Module to which number of the
online module module to which • 10H is added to the value of the header I/O number of which the online S (During online QnPH
SD235 New
change is being online module module change is being performed. module change) QnPRH
performed change is being
performed /10H
0: Automatic
SD240 Base mode mode • Stores the base mode. S (Initial) New
1: Detail mode
QCPU
0: Main base only
Extension stage
SD241 1 to 7: Extension • Stores the maximum number of the extension bases being installed. S (Initial) New
number
stage number
12 - 237
CHAPTER12 TROUBLESHOOTING
b4 b2 b1 b0
Fixed to 0 to
Base type
Installed Q base differentiation Main base unit
presence/ 0: Base not 1st extension base S (Initial) New Q00J/Q00/Q01
absence installed 2nd extension base
SD242 1: Q**B is installed
to
4th extension base 6
b7 b2 b1 b0
Fixed to 0 to
Main base unit
1st extension
7
Base type base
Fixed to 0
Installed Q base differentiation 2nd extension when the
presence/ 0: Base not base S (Initial) New QnU
absence installed
1: Q**B is installed
to
7th extension
base is not
installed. 8
base
• The bits from the third extension stage to the seventh extension stage
are fixed to "0" in the Q00UJCPU.
• The bits from the fifth extension stage to the seventh extension stage are
fixed to "0" in the Q00UCPU, Q01UCPU, and Q02UCPU.
SD244 Extension
7
Extension Extension Extension
6 5 4 Qn(H)
No. of base QnPH
No. of base slots S (Initial) New
slots • As shown above, each area stores the number of slots being installed. QnPRH
SD244 • The bits from the third extension stage to the seventh extension stage QnU
are fixed to "0" in the Q00UJCPU.
• The bits from the fifth extension stage to the seventh extension stage are
fixed to "0" in the Q00UCPU, Q01UCPU, and Q02UCPU.
12 - 238
Table12.36 Special register
Corres-
Set by ponding Corresponding
Number Name Meaning Explanation
(When Set) ACPU CPU
D9
Number of • Indicates the number of mounted MELSECNET/10 modules or
SD254
modules installed MELSECNET/H modules.
• Indicates I/O number of mounted MELSECNET/10 module or
SD255 I/O No.
MELSECNET/H module
Information from 1st module
*10: The Universal model QCPU except the Q00UJCPU, Q00UCPU, and Q01UCPU.
*11: The Universal model QCPU except the Q00UJCPU, Q00UCPU, Q01UCPU, and Q02UCPU.
12 - 239
CHAPTER12 TROUBLESHOOTING
1) When Xn0 of the mounted CC-Link module turns ON, the bit of the
D9
2
corresponding station turns to 1 (ON).
2) When either Xn1 or XnF of the mounted CC-Link module turns OFF, the
bit of the corresponding station turns to 1 (ON).
3) Turns to 1 (ON) when communication between the mounted CC-Link
module and CPU module cannot be made.
3
Information Information Information
of 3) of 2) of 1)
Error detection
b15 to b12 b11 to
Empty
b8 b7 to b4 b3 to b0
Qn(H)*14 12
SD281 CC-Link error S (Error) New QnPH*14
status 5st
module QnPRH*15
6nd
module
7rd
module
8th
module
The above module Nos. n are in order of the head I/O numbers.
(However, the one where parameter setting has not been made is not
6
counted.)
SD286 • The number of points assigned to M is stored with 32 bits.
Points assigned to
• Even if the points assigned to M are 32k points or less, the points are
7
SD287 M (for extension)
Device stored.
S (Initial) New QnU*16
SD288 assignment • The number of points assigned to B is stored with 32 bits.
Points assigned to
• Even if the points assigned to B are 32k points or less, the points are
SD289 B (for extension)
stored.
Number of points
SD290
assigned for X
• Stores the number of points currently set for X devices
8
Number of points
SD291 • Stores the number of points currently set for Y devices
assigned for Y
Number of points
SD292 Device • Stores the number of points currently set for M devices
assigned for M
assignment
Number of points
SD293 (Same as • Stores the number of points currently set for L devices S (Initial) New
*14: The module whose first 5 digits of serial No. is "08032" or later.
*15: The module whose first 5 digits of serial No. is "09012" or later.
*16: The module whose first 5 digits of serial No. is "10042" or later.
12 - 240
Table12.36 Special register
Corres-
Set by ponding Corresponding
Number Name Meaning Explanation
(When Set) ACPU CPU
D9
• Stores the number of points of index register (Z) to be modified in the
Device 16 bit modification
range of 16 bits.
SD305 assignment Number of points S (Initial) New QnU
(The assignment is set by the ZR device index modification setting
(Index register) assigned for Z
parameter.)
Device • Stores the number of ZR device points (except the number of points of
SD306
assignment Number of points extended data register (D) and extended link register (W)). The number
(Same as assigned for ZR of assignment points of ZR device is stored into this SD only when 1k
SD307 parameter (for extension) point or more is set to the extended data register (D) and extended link
contents) register (W).
Device Number of points
SD308 • Stores the total number of points of the extended data register (D) and
assignment assigned for D (for
(assignment data register in internal device memory area (stores the value in 32-bit S (Initial) New QnU*17
inside + for
SD309 including the binary).
extension)
number of
points set to the
SD310 Number of points
extended data • Stores the total number of points of the extended link register (W) and
assigned for W
register (D) and link register in internal device memory area (stores the value in 32-bit
(for inside + for
SD311 extended link binary).
extension)
register (W))
• Reserves the designated time for communication processing with GX
Developer or other units.
• The greater the value is designated, the shorter the response time for
Time reserved Q00J/Q00/Q01
Time reserved for communication with other devices (GX Developer, serial communication
for Qn(H)
SD315 communication units) becomes. U New
communication QnPH
processing • If the designated value is out of the range above, it is processed that no
processing QnPRH
setting is made.
• Setting range: 1 to 100 ms
• Note that the scan time becomes longer by the designated time.
No. of modules
SD340 • Indicates the number of mounted Ethernet module.
installed
SD341 I/O No. • Indicates I/O No. of mounted Ethernet module
Network
SD342 • Indicates network No. of mounted Ethernet module QCPU
No.
Information of 1st module
*10: The Universal model QCPU except the Q00UJCPU, Q00UCPU, and Q01UCPU.
*11: The Universal model QCPU except the Q00UJCPU, Q00UCPU, Q01UCPU, and Q02UCPU.
*17: The Universal model QCPU except the Q00UJCPU.
12 - 241
CHAPTER12 TROUBLESHOOTING
SD380
Ethernet
instruction
Instruction
reception status of
Instruction reception
status of channel 4 12
reception status 1st module Instruction reception
status of channel 5
Instruction reception
status of channel 6
Instruction reception S (Instruction
New QnPRH
status of channel 7 execution)
Instruction reception
status of channel 8
ON: Received (Channel is being used.)
OFF: Not received (Channel is not used.) 6
Instruction
SD381 reception status of • Configuration is identical to that for the first module.
2nd module
SD382
Ethernet
instruction
Instruction
reception status of • Configuration is identical to that for the first module.
7
reception 3rd module
status
Instruction
SD383 reception status of • Configuration is identical to that for the first module.
4th module 8
12 - 242
Table12.36 Special register
Corres-
Set by ponding Corresponding
Number Name Meaning Explanation
(When Set) ACPU CPU
D9
Number of • The number of CPU modules that comprise the multiple CPU system is Q00/Q01*9
SD393
multiple CPUs stored. (1 to 3, Empty also included) QnU
• The CPU module types of No. 1 CPU to 3 and whether the CPU
modules are mounted or not are stored.
S (Initial) New
CPU mounting
SD394 Q00/Q01*9
information
Q00/Q01*9
• In a multiple CPU system configuration, the CPU number of the host
Multiple CPU Qn(H)*9
SD395 CPU is stored. S (Initial) New
Multiple CPU number QnPH
CPU No. 1: 1, CPU No. 2: 2, CPU No. 3: 3, CPU No. 4: 4
system QnU
information
No. 1 CPU
SD396
operation status The operation information of each CPU No. is stored.
(The information on the number of multiple CPUs indicated in SD393 is
stored.)
No. 2 CPU
b15 b14 to b8 b7 to b4 b3 to b0 Q00/Q01*9
SD397 Vacancy Classification Operation status
operation status QnU*17
mounted S (END
0: Not mounted processing New
1: Mounted error)
No. 3 CPU
SD398 0: Normal 0: RUN
operation status
1: Minor fault 2: STOP
2: Medium fault 3: PAUSE
3: Major fault 4: Initial
FH: Reset FH: Reset
No. 4 CPU
SD399 QnU*11
operation statu
Corres-
Set by ponding Corresponding
Number Name Meaning Explanation
(When Set) ACPU CPU
D9
• Following programmable controller CPU module RUN, 1 is added each
1 second Number of counts S (Status
SD412 second D9022
counter in 1-second units change)
• Count repeats from 0 to 32767 to -32768 to 0 QCPU
2n second clock 2n second clock • Stores value n of 2n second clock (Default is 30)
SD414 U New
setting units • Setting can be made between 1 and 32767
2nms clock • Stores value n of 2nms clock (Default is 30)
SD415 2nms clock units U New
setting • Setting can be made between 1 and 32767 Qn(H)
• Incremented by 1 for each scan execution after the CPU module is set to QnPH
RUN. S (Every END QnPRH
New
(Not counted by the scan in an initial execution type program.) processing) QnU
Number of counts
SD420 Scan counter • Count repeats from 0 to 32767 to -32768 to 0
in each scan
• Incremented by 1 for each scan execution after the CPU module is set to
S (Every END
RUN. New Q00J/Q00/Q01
processing)
• Count repeats from 0 to 32767 to -32768 to 0
• Incremented by 1 for each scan execution after the CPU module is set to
Low speed scan Number of counts RUN. S (Every END Qn(H)
SD430 New
counter in each scan • Count repeats from 0 to 32767 to -32768 to 0 processing) QnPH
• Used only for low speed execution type programs
12 - 243
CHAPTER12 TROUBLESHOOTING
Corres-
SD500
Execution
program No.
Program No. in
execution
• Program number of program currently being executed is stored as BIN
value.
S (Status
change)
New
QnPH
QnPRH 3
QnU
Low speed
Low speed • Program number of low speed excution type program No. currently
execution type S (Every END Qn(H)
SD510 excution type being executed is stored as BIN value. New
program No.
program No. in
execution
• Enabled only when SM510 is ON.
processing) QnPH
12
• The current scan time is stored into SD520 and SD521. D9018
Current scan time S (Every END
SD520 (Measurement is made in 100 s units. (For the Universal model QCPU, format
(in 1 ms units) processing)
in 1 s units.)) change
SD520: Stores the ms place. (Storage range: 0 to 65535)
Current scan SD521: Stores the s place. (Storage range: 0 to 900 (For the
QCPU
time Universal model QCPU, storage range is 0 to 999))
Current scan time (Example) When the current scan time is 23.6ms, the following values are S (Every END
SD521 New
(in 100 s units) stored. processing)
SD520 = 23
SD521 = 600 6
Initial scan time • Stores the scan time of an initial execution type program into SD522 and
SD522
(in 1 ms units) SD523.
(Measurement is made in 100 s units. (For the Universal model QCPU,
S (First END
Initial scan time in 1 s units.)) New
SD523
Initial scan time
(in 100 s units)
SD522: Stores the ms place. (Storage range: 0 to 65535)
SD523: Stores the s place. (Storage range: 0 to 900 (For the Universal
processing)
7
model QCPU, storage range is 0 to 999))
Minimum scan • Stores the minimum value of the scan time except that of an initial D9017
S (Every END Qn(H)
SD524 time (in 1 ms execution type program into SD524 and SD525. (Measurement is made format
Minimum scan
time
units) in 100 s units. (For the Universal model QCPU, in 1 s units.))
SD524: Stores the ms place. (Storage range: 0 to 65535)
processing)
change QnPH
QnPRH
8
Minimum scan
SD525: Stores the s place. (Storage range: 0 to 900 (For the Universal S (Every END QnU
SD525 time (in 100 s New
model QCPU, storage range is 0 to 999)) processing)
units)
Maximum scan • Stores the maximum value of the scan time except that of an initial D9019
SD526 time (in 1 ms execution type program into SD526 and SD527. (Measurement is made format
units) change
Current scan time • Stores the current scan time of a low speed execution type program into
SD528 Current scan
(in 1 ms units) SD528 and SD529.
time for low S (Every END
(Measurement is made in 100 s units.) New
speed execution processing)
Current scan time SD528: Stores the ms place. (Storage range: 0 to 65535)
SD529 type programs
(in 100 s units) SD529: Stores the s place. (Storage range: 0 to 900)
Minimum scan
SD532 time (in 1 ms • Stores the minimum value of the scan time of a low speed execution
Minimum scan
units) type program into SD532 and SD533.
time for low S (Every END
(Measurement is made in 100 s units.) New Qn(H)
speed execution Minimum scan processing)
SD532: Stores the ms place. (Storage range: 0 to 65535) QnPH
SD533 type programs time (in 100 s SD533: Stores the s place. (Storage range: 0 to 900)
units)
Maximum scan
SD534 time (in 1 ms • Stores the maximum value of the scan time except that of the first scan
Maximum scan
units) of a low speed execution type program into SD534 and SD535.
time for low S (Every END
(Measurement is made in 100 s units.) New
speed execution Maximum scan processing)
SD534: Stores the ms place. (Storage range: 0 to 65535)
SD535 type programs time (in 100 s SD535: Stores the s place. (Storage range: 0 to 900)
units)
END processing • Stores the time from the end of a scan execution type program to the
SD540 time (in 1 ms start of the next scan into SD540 and SD541.
Qn(H)
units) (Measurement is made in 100 s units.(For the Universal model QCPU,
END processing S (Every END QnPH
in 1 s units.)) New
time END processing processing) QnPRH
SD540: Stores the ms place. (Storage range: 0 to 65535)
SD541 time (in 100 s QnU
SD541: Stores the s place. (Storage range: 0 to 900) (Storage range: 0
units) to 900 (For the Universal model QCPU, storage range is 0 to 999))
12 - 244
Table12.38 Special register
Corres-
Set by ponding Corresponding
Number Name Meaning Explanation
(When Set) ACPU CPU
D9
Minimum scan
SD524 time (in 1 ms • Stores the minimum value of the scan time into SD524 and SD525.
Minimum scan units) (Measurement is made in 100 s units.) S (Every END
time Minimum scan SD524: Stores the ms place. (Storage range: 0 to 65535) processing)
SD525 time (in 100 s SD525: Stores the s place. (Storage range: 0 to 900)
units)
New
Maximum scan
SD526 time (in 1 ms • Stores the maximum value of the scan time into SD526 and SD527.
Maximum scan units) (Measurement is made in 100 s units.) S (Every END
Q00J/Q00/Q01
time Maximum scan SD526: Stores the ms place. (Storage range: 0 to 65535) processing)
SD527 time (in 100 s SD527: Stores the s place. (Storage range: 0 to 900)
units)
END processing
SD540 time (in 1 ms • Stores the time from when the scan program ends until the next scan
units) starts into SD540 and SD541.
END processing S (Every END
(Measurement is made in 100 s units.) New
time END processing processing)
SD540: Stores the ms place. (Storage range: 0 to 65535)
SD541 time (in 100 s SD541: Stores the s place. (Storage range: 0 to 900)
units)
Constant scan • Stores the wait time for constant scan setting into SD542 and SD543.
SD542 wait time (in 1 ms (Measurement is made in 100 s units. (For the Universal model QCPU,
Constant scan units) in 1 s units.)) S (Every END
New QCPU
wait time Constant scan SD542: Stores the ms place. (Storage range: 0 to 65535) processing)
SD543 wait time (in 100 SD543: Stores the s place. (Storage range: 0 to 900 (For the Universal
s units) model QCPU, storage range is 0 to 999))
Cumulative
execution time for
low speed
SD544
execution type • Stores the cumulative execution time of a low speed execution type
Cumulative programs program into SD544 and SD545.
execution time (in 1 ms units) (Measurement is made in 100 s units.) S (Every END
for low speed New
Cumulative SD544: Stores the ms place. (Storage range: 0 to 65535) processing)
execution type
execution time for SD545: Stores the s place. (Storage range: 0 to 900)
programs
low speed • Cleared to 0 after the end of one low speed scan.
SD545
execution type
programs Qn(H)
(in 100 s units) QnPH
Execution time for
low speed
SD546 execution type • Stores the execution time of a low speed execution type program during
Execution time programs one scan into SD546 and SD547.
for low speed (in 1 ms units) (Measurement is made in 100 s units.) S (Every END
New
execution type Execution time for SD546: Stores the ms place. (Storage range: 0 to 65535) processing)
programs low speed SD547: Stores the s place. (Storage range: 0 to 900)
SD547 execution type • Stored every scan.
programs
(in 100 s units)
Scan execution
type program • Stores the execution time of a scan execution type program during one
SD548
execution time (in scan into SD548 and SD549.
Scan execution 1 ms units) Qn(H)
(Measurement is made in 100 s units.) S (Every END
type program New QnPH
Scan execution SD548: Stores the ms place. (Storage range: 0 to 65535) processing)
execution time QnPRH
type program SD549: Stores the s place. (Storage range: 0 to 900)
SD549 • Stored every scan.
execution time (in
100 s units)
Scan program • Stores the execution time of a scan program during one scan into
SD548 execution time SD548 and SD549.
(in 1 ms units) (Measurement is made in 100 s units. (For the Universal model QCPU,
Scan program in 1 s units.)) S (Every END Q00J/Q00/Q01
New
execution time Scan program SD548: Stores the ms place. (Storage range: 0 to 65535) processing) QnU
SD549 execution time SD549: Stores the s place. (Storage range: 0 to 900 (For the Universal
(in 100 s units) model QCPU, storage range is 0 to 999))
• Stored every scan.
Service interval
SD550 measurement Unit/module No. • Sets I/O number for module that measures service interval. U New
module
Module service Qn(H)
SD551 interval • Stores the service interval for the module specified in SD550 into SD551 QnPH
(in 1 ms units) and SD552 when SM551 is turned ON. QnPRH
Service interval
(Measurement is made in 100 s units.) S (Request) New
time Module service SD551: Stores the ms place. (Storage range: 0 to 65535)
SD552 interval SD552: Stores the s place. (Storage range: 0 to 900)
(in 100 s units)
12 - 245
CHAPTER12 TROUBLESHOOTING
3
b15 to b8 b7 to b4 b3 to b0
0
12
SD600 Memory card typs New
typs 0: Does not exist card removal) QnPRH
(1: SRAM) QnU
Drive 2 type
2: ATA card
3: Flash card
(The bits for the drive 1 (RAM) type and drive 2 (ROM) type are fixed to "0"
in the Q00UJCPU, Q00UCPU, and Q01UCPU.)
Drive 1
• Drive 1 capacity is stored in 1 k byte units. S (Initial and
SD602 (Memory card Drive 1 capacity New Qn(H)
• (Empty capacity after format is stored.) card removal)
RAM) capacity QnPH
6
Drive 2 QnPRH
S (Initial and
SD603 (Memory card Drive 2 capacity • Drive 2 capacity is stored in 1 k byte units.*1 New QnU*2
card removal)
ROM) capacity
• The use conditions for memory card are stored as bit patterns .
(In use when ON)
7
• The significance of these bit patterns is indicated below:
• The use conditions for memory card are stored as bit patterns .
*1: When the Q2MEM-8MBA is used, value stored in the special register SD603 differs depending on the combination of the serial number of the High
Performance model QCPU and the manufacture control number of the ATA card.
For details, refer to Section 7.1.2.
*2: The Universal model QCPU except the Q00UJCPU, Q00UCPU, and Q01UCPU.
12 - 246
Table12.39 Special register
Corres-
Set by ponding Corresponding
Number Name Meaning Explanation
(When Set) ACPU CPU
D9
• Indicates the drive 3/4 type.
b15 to b8 b7 to b4 b3 to b0
0
Drive 3
(Standrd Fixed to 1 Qn(H)
QnPH
RAM) S (Initial) New
QnPRH
Drive 4 QnU
(Standrd Fixed to 3
ROM)
SD620 Drive 3/4 typs Drive 3/4 typs
(The bits for the drive 3 (standard RAM) type is fixed to "0" in the
Q00UJCPU.)
• Indicates the drive 3/4 type.
b15 to b8 b7 to b4 b3 to b0
0
Drive 4 Fixed to
(Standrd ROM) "3 (FLASH ROM)"
Qn(H)
Drive 3 • Drive 3 capacity is stored in 1 k byte units. QnPH
S (Initial) New
SD622 (Standard RAM) Drive 3 capacity (Empty capacity after format is stored.) QnPRH
capacity QnU
• Drive 3 capacity is stored in 1k byte units. S (Initial) New Q00J/Q00/Q01
Qn(H)
Drive 4 • Drive 4 capacity is stored in 1 k byte units. QnPH
S (Initial) New
SD623 (Standard Drive 4 capacity (Empty capacity after format is stored.) QnPRH
ROM) capacity QnU
• Drive 4 capacity is stored in 1k byte units. S (Initial) New Q00J/Q00/Q01
• The conditions for usage for drive 3/4 are stored as bit patterns.
(In use when ON)
• The significance of these bit patterns is indicated below:
• The conditions for usage for drive 3/4 are stored as bit patterns.
SD624 (In use when ON)
• The significance of these bit patterns is indicated below:
12 - 247
CHAPTER12 TROUBLESHOOTING
SD642 b15 to b8 b7 to b0
SD643
SD641 2nd character 1st character
Qn(H)
3
SD642 4th character 3rd character
S (Status QnPH
SD643 6th character 5th character New
SD644 change) QnPRH
SD644 8th character 7th character QnU*3
SD645 SD645 1st character of
extension
2EH(.) 12
SD646 3rd character of 2nd character of
the extension the extension
File register file File register file
name name • Stores file register file name (MAIN.QDR) selected at parameters as
ASCII code.
b15 to b8 b7 to b0
SD641 2nd character (A) 1st character (M)
SD646
6
SD642 4th character (N) 3rd character (I)
SD643 6th character ( ) 5th character ( ) S (Initial) New Q00J/Q00/Q01
SD644 8th character ( ) 7th character ( )
1st character of
SD645 2EH(.)
the extension (Q)
SD646
3rd character of
the extension (R)
2nd character of
the extension (D)
7
Qn(H)
S (Status QnPH
SD647
File register
capacity
File register
capacity
• Stores the data capacity of the currently selected file register in 1 k word
units.
change)
New
QnPRH
QnU*3
8
S (Initial) Q00J/Q00/Q01
Q00J/Q00/Q01
Qn(H)
File register File register block S (Status
SD648 • Stores the currently selected file register block number. D9035 QnPH
Boot designation • Stores the drive number where the boot designation file (*.QBT) is being
SD660 S (Initial) New
file drive number stored.
SD661 • Stores the file name of the boot designation file (*.QBT).
SD662 b15 to b8 b7 to b0
SD661 2nd character 1st character Qn(H)
SD663
Boot operation SD662 4th character 3rd character QnPH
SD664 designation file File name of boot SD663 6th character 5th character QnPRH
S (Initial) New
designation file SD664 8th character 7th character QnU*4
SD665
1st character of
SD665 2EH(.)
the extension
SD666 3rd character of 2nd character of
SD666
the extension the extension
12 - 248
Table12.39 Special register
Corres-
Set by ponding Corresponding
Number Name Meaning Explanation
(When Set) ACPU CPU
D9
• Stores information of parameter storage destination drive which is
enabled.
0: Drive 0 (Program memory)
Parameter
Parameter enable 1: Drive 1 (SRAM card)
SD670 enable drive S (Initial) New
drive No. 2: Drive 2 (Flash card/ATA card)
information
4: Drive 4 (Standard ROM)
(Only drive 0 and drive 4 are valid in the Q00UJCPU, Q00UCPU, and
Q01UCPU.)
Indicates the status of the latch data backup function.
Year Month
• Stores the day and hour when backup is performed in 2-digit BCD code.
Day Hour
• Stores the minute and second when backup is performed in 2-digit BCD
code.
Minute Second
• Stores the first 2 digits of year and day of week when backup is
performed in BCD code.
b15 to b12 b11 to b8 b7 to b4 b3 to b0 Example:
1993, Friday
1905H
12 - 249
CHAPTER12 TROUBLESHOOTING
Corres-
Set by ponding Corresponding
Number Name Meaning Explanation
(When Set) ACPU CPU 1
D9
• Stores the last 2 digits of year and month when data is restored in 2-digit
BCD code.
SD676
Restore time
b15 to b12 b11 to b8 b7 to b4 b3 to b0 Example:
July, 1993
2
(Year and month)
9307H
Year Month
• Stores the day and time when data is restored in 2-digit BCD code. 3
b15 to b12 b11 to b8 b7 to b4 b3 to b0 Example:
Restore time (Day 31st, 10 a.m.
SD677
and time)
12
3110H
Day Hour
• Stores the minute and second when data is restored in 2-digit BCD
code.
Minute Second
• Stores the first 2 digits of year and day of week when data is restored in 6
BCD code.
b15 to b12 b11 to b8 b7 to b4 b3 to b0 Example:
1993, Friday
1905H 7
Restore time
SD679 (Year and day of Day of the week QnU
week) 0 Sunday
Higher digits of year (0 to 99)
8
1 Monday
2 Tuesday
3 Wednesday
4 Thursday
5 Friday
6 Saturday
12 - 250
Corres-
Set by ponding Corresponding
Number Name Meaning Explanation
(When Set) ACPU CPU
D9
Backup execution • Displays the execution status of data backup to the memory card in
Backup S (Status
SD691 status display percentage (0 to 100%). New
execution status change)
(Percentage) • "0" is set when the backup starts.
Stores the factor of an error that occurred in the restoration.
Each error factor is as follows:
Factor of error 800H: The CPU module model name is not matched.
Restoration error S (Error
SD692 occurred in the 801H: The file password is set only for the restoration destination data or is New
factor occurrence)
restoration not matched.
810H: The verified backup data file is not matched or the backup data read
failed.
Stores the current restoration execution status.
Each error factor is as follows: QnU*1
0 : Before restoration start
Restoration Current restoration 1 : Restoration in execution S (Status
SD693 New
status status 2 : Restoration completed change)
FF: Restoration error
Sets "0" (Before restoring), however, when the restoration is completed
only during the automatic restoration.
• Displays the execution status of restoration to the CPU module in
Restoration
percentage (0 to 100%).
Restoration execution status S (Status
SD694 • "0" is set before the restoration. New
execution status display change)
Sets "0" (Before restoring), however, when the restoration is completed
(Percentage)
only during the automatic restoration.
• Specifies the maximum number of executions of the writing to standard
ROM instruction (SP.DEVST) to write to the standard ROM per day.
Specification of Specification of • When the number of executions of the writing to standard ROM
writing to stan- writing to standard instruction exceeds the number of times set by SD695, “OPERATION
SD695 U New QnU
dard ROM ROM instruction ERROR” (error code: 4113) occurs.
instruction count count • The setting range for SD695 is 1 to 32767. If 0 or value outside the
range is set, “OPERATION ERROR” (error code: 4113) occurs at
execution of the writing to standard ROM instruction.
SD696 Available
Available memory Stores the available memory in memory card. (Stores the value in 32-bit
memory in
SD697 in memory card binary.)
memory card S (Backup in
New QnU*1
SD698 operation)
Backup data Backup data
Stores the backup data capacity. (Stores the value in 32-bit binary.)
SD699 capacity capacity
*1: The module whose first 5 digits of serial No. is "10102" or later. (Except the Q00UJCPU, Q00UCPU, and Q01UCPU)
12 - 251
CHAPTER12 TROUBLESHOOTING
Corres-
3
SD705
mask pattern being stored at SD705 (or at SD705 and SD706 if double Qn(H)
Mask pattern Mask pattern U New
words are being used) to operate on all data in the block with the QnPH
SD706 masked values. QnPRH
• Patterns masked by use of the IMASK instruction are stored in the
SD715
following manner:
SD716 IMASK
b15 b1 b0 12
S (During
instruction mask Mask pattern SD715 l15 to l1 l0 New
execution)
pattern
SD716 l31 to l17 l16
SD717 QCPU
SD717 l47 to l33 l32
SD718
Accumulator Accumulator • For use as replacement for accumulators used in A series programs. S/U New
SD719
SD755
SD754 34th character 33rd character
SD755 36th character 35th character
SD756
SD756 38th character 37th character
SD757
SD757 40th character 39th character
SD758
SD758 42nd character 41st character
SD759 SD759 44th character 43rd character
SD760 SD760 46th character 45th character
SD761 SD761 48th character 47th character
SD762 SD762 50th character 49th character
SD763 SD763 52nd character 51st character
SD764
SD764 54th character 53rd character
SD765 56th character 55th character
SD765
SD766 58th character 57th character
SD766
SD767 60th character 59th character
SD767
SD768 62nd character 61st character
SD768 SD769 64th character 63rd character
SD769
12 - 252
Table12.40 Special register
Corres-
Set by ponding Corresponding
Number Name Meaning Explanation
(When Set) ACPU CPU
D9
• Specify the limit of each PID loop as shown below.
• Selects whether or not the data is refreshed when the COM instruction is
executed.
• Designation of SD778 is made valid when SM775 turns ON.
b15 b14 to b5 b4 b3 b2 b1 b0
SD778 0/1 0 0/1 0/1 0/1 0/1 0/1
I/O refresh
CC-Link refresh
MELSECNET/H
refresh
Automatic refresh of
intelligent function Q00J/Q00/Q01*9
modules
U New Qn(H)*11
Automatic refresh of
CPU shared memory
(Fixed to "0" for
Redundant CPU)
Execution/non-
execution of
communication with
CPU module
Execution/non-
execution of
communication with
CPU module
12 - 253
CHAPTER12 TROUBLESHOOTING
SD781
to
Mask pattern of
IMASK Mask pattern
SD782 l79 to l65 l64
S (During
New
Qn(H)
QnPH
8
to execution) QnPRH
SD793 instruction
QnU
SD793 l255 to l241 l240
b15 b1 b0
SD781 l63 to l49 l48
SD781 Mask pattern of
SD782 l79 to l65 l64 S (During
to IMASK Mask pattern New Q00J/Q00/Q01
execution)
SD785 instruction
to to
12 - 254
Table12.40 Special register
Corres-
Set by ponding Corresponding
Number Name Meaning Explanation
(When Set) ACPU CPU
D9
Maximum
number of
• Specifies the maximum number of blocks used for the multiple CPU
blocks used for
high-speed transmission dedicated instruction (target CPU=CPU No.1).
the multiple
When the dedicated instruction of Multiple CPU transmission is
CPU high-
executed to the CPU No.1, and the number of empty blocks of the U (At 1 scan
SD796 speed New
dedicated instruction transmission area is less than the setting value of after RUN)
transmission
this register, SM796 is turned ON, which is used as the interlock signal
dedicated
for consecutive execution of the dedicated instruction of Multiple CPU
instruction
transmission.
setting (for CPU
No.1)
Maximum
number of
• Specifies the maximum number of blocks used for the multiple CPU
blocks used for
high-speed transmission dedicated instruction (target CPU=CPU No.2).
the multiple
When the dedicated instruction of Multiple CPU transmission is
CPU high-
executed to the CPU No.2, and the number of empty blocks of the U (At 1 scan
SD797 speed New
dedicated instruction transmission area is less than the setting value of after RUN)
transmission Maximum number
this register, SM797 is turned ON, which is used as the interlock signal
dedicated of blocks range for
for consecutive execution of the dedicated instruction of Multiple CPU
instruction dedicated
transmission.
setting (for CPU instructions
No.2) Range: 1 to 7
QnU*14*15
Maximum (Default: 2 Or
number of when setting other
• Specifies the maximum number of blocks used for the multiple CPU
blocks used for than 1 to 7, the
high-speed transmission dedicated instruction (target CPU=CPU No.3).
the multiple register operates
When the dedicated instruction of Multiple CPU transmission is
CPU high- as 7).
executed to the CPU No.3, and the number of empty blocks of the U (At 1 scan
SD798 speed New
dedicated instruction transmission area is less than the setting value of after RUN)
transmission
this register, SM798 is turned ON, which is used as the interlock signal
dedicated
for consecutive execution of the dedicated instruction of Multiple CPU
instruction
transmission.
setting (for CPU
No.3)
Maximum
number of
• Specifies the maximum number of blocks used for the multiple CPU
blocks used for
high-speed transmission dedicated instruction (target CPU=CPU No.4).
the multiple
When the dedicated instruction of Multiple CPU transmission is
CPU high-
executed to the CPU No.4, and the number of empty blocks of the U (At 1 scan
SD799 speed New
dedicated instruction transmission area is less than the setting value of after RUN)
transmission
this register, SM799 is turned ON, which is used as the interlock signal
dedicated
for consecutive execution of the dedicated instruction of Multiple CPU
instruction
transmission.
setting (for CPU
No.4)
*14: The Universal model QCPU except the Q00UJCPU, Q00UCPU, Q01UCPU, and Q02UCPU.
*15: The range is from 1 to 9 for the Q03UDCPU, Q04UDCPU, and Q06UDHCP whose first 5 digits of serial number is "10012" or earlier.
(Default: 2 Or when setting other than 1 to 9, the register operates as 9).
12 - 255
CHAPTER12 TROUBLESHOOTING
(7) Debug
Table12.41 Special register 1
Corres-
Set by ponding Corresponding
Number Name Meaning Explanation
2
(When Set) ACPU CPU
D9
Stores the status of the debug function usage as shown below.
0: Forced ON/OFF for external I/O
1: Executional conditioned device test
2 to 15:Absent (0 fix)
b15 to b2 b1 b0
3
Debug function Debug function S (Status
SD840 0 New QnU*1
usage usage change)
Forced ON/OFF for
external I/O
Executional conditioned
device test 12
(0: Not used, 1: Used)
*1: The module whose first 5 digits of serial No. is "10042" or later.
Set by
Corres-
ponding Corresponding
6
Number Name Meaning Explanation
(When Set) ACPU CPU
D9
Corres-
Set by ponding Corresponding
Number Name Meaning Explanation
(When Set) ACPU CPU
D9
Direct
SD979 MELSOFT
connection
SD980 to Connection
SD995 1 to 16 Count of unlock
Stores the count of unlock processing failures. S(Status
MELSOFT processing
Range: 0 to FFFEH (FFFFH when the limit is exceeded) change)
New QnU*1
SD998 connection failures
using TCP port
FTP
SD999 communi
cation port
12 - 256
(10) A to Q conversion
ACPU special registers D9000 to D9255 correspond to Q special registers SD1000 to
SD1255 after A to Q/QnA conversion.
(However, the Basic model QCPU and Redundant CPU do not support the A to Q
conversion.)
These special registers are all set by the system, and cannot be set by the user program.
To set data by the user program, correct the program for use of the QCPU special registers.
However, some of SD1200 to SD1255 (corresponding to D9200 to 9255 before conversion)
can be set by the user program if they could be set by the user program before conversion.
For details on the ACPU special registers, refer to the user's manual for the corresponding
CPU, and MELSECNET or MELSECNET/B Data Link System Reference Manuals.
Check "Use special relay/special register from SM/SD1000" for "A-PLC" on the PLC system tab of PLC parameter in GX
Developer when the converted special registers are used with the High Performance model QCPU, Process CPU, and
Universal model QCPU.
When not using the converted special registers, uncheck "Use special relay/special registers from SM/SD1000" to save the
time taken for processing special registers.
Remark
Supplemental explanation on "Special Register for Modification" column
For the device numbers for which a special register for modification is specified, modify it to the special register for
QCPU.
For the device numbers for which is specified, special register after conversion can be used.
12 - 257
CHAPTER12 TROUBLESHOOTING
ACPU
Special
Special
1
Register Corresponding
Special Register for Name Meaning Details
after CPU
Register Modification
Conversion
• When fuse blown modules are detected, the first I/O number of the
lowest number of the detected modules is stored in hexadecimal.
2
(Example: When fuses of Y50 to 6F output modules have blown,
"50" is stored in hexadecimal) Qn(H)
Number of module
D9000 SD1000 – Fuse blown To monitor the number by peripheral devices, perform monitor QnPH
with blown fuse
operation given in hexadecimal.
(Cleared when all contents of SD1100 to SD1107 are reset to 0.)
QnU*1 3
• Fuse blow check is executed also to the output modules of remote
I/O stations.
• Stores the module numbers corresponding to setting switch
numbers or base slot numbers when fuse blow occurred. 12
AJ02 I/O module Extension base unit
Setting Stored Base unit Stored
switch data slot No. data
0 0 0 4
1 1 1 5
Number of module Qn(H)
D9001 SD1001 – Fuse blown 2 2 2 6
with blown fuse QnPH
3 3 3 7
4
5
4
5
6
6 6
7 7
• For the remote I/O station, the value of (module I/O No./10H) + 1 is 7
stored.
• If I/O modules, of which data are different from data entered, are
detected when the power is turned on, the first I/O number of the
12 - 258
Table12.44 Special register
Special
ACPU Special
Register Corresponding
Special Register for Name Meaning Details
after CPU
Register Modification
Conversion
• When one of F0 to 2047 is turned on by OUT F or
SET F instruction, the F number, which has been detected earliest
F number at which Qn(H)
Annunciator among the F numbers which have turned on, is stored in BIN code.
D9009 SD1009 SD62 external failure has QnPH
detection • SD1009 can be cleared by RST F or LEDR instruction.
occurred QnU*1
If another F number has been detected, the clearing of SD1009
causes the next number to be stored in SD1009.
• When operation error has occurred during execution of application
Step number at which instruction, the step number, at which the error has occurred, is
D9010 SD1010 Error step operation error has stored in BIN code.
occurred. Thereafter, each time operation error occurs, the contents of
SD1010 are renewed.
• When operation error has occurred during execution of application
Step number at which instruction, the step number, at which the error has occurred, is
Qn(H)
D9011 SD1011 Error step operation error has stored in BIN code. Since the step number is stored into SD1011
QnPH
occurred. when SM1011 turns from OFF to ON, the data of SD1011 is not
updated unless SM1011 is cleared by a user program.
• The I/O control mode set is returned in any of the following
numbers:
I/O control I/O control mode
D9014 SD1014 0: Both input and output in direct mode
mode number
1: Input in refresh mode, output in direct mode
3: Both input and output in refresh mode
• The operation status of CPU as shown below are stored in
SD1015.
b15 to b12 b11 to b8 b7 to b4 b3 to b0
*1: When the CPU mdoule is in RUN mode and SM1040 is off, the
CPU module remains in RUN mode if changed to PAUSE mode.
12 - 259
CHAPTER12 TROUBLESHOOTING
12
(RAM)
5: Subprogram 1
(ROM)
Program • Indicates which sequence program is run presently. One value of 0 Qn(H)
D9016 SD1016 6: Subprogram 2
number to B is stored in BIN code. QnPH
(ROM)
7: Subprogram 3
(ROM)
8: Main program
(E2PROM)
9: Subprogram 1
(E2PROM)
A: Subprogram 2
(E2PROM)
6
B: Subprogram 3
(E2PROM)
Minute Second
12 - 260
Table12.44 Special register
Special
ACPU Special
Register Corresponding
Special Register for Name Meaning Details
after CPU
Register Modification
Conversion
• The day of the week is stored as BCD code as shown below.
b15 to b12 b11 to b8 b7 to b4 b3 to b0
Example:
Friday
H0005
Day of the week
Clock data
D9028 SD1028 – Clock data 0 Sunday Qn(H)
(day of week)
Always set "0" 1 Monday QnPH
2 Tuesday QnU*1
3 Wednesday
4 Thursday
5 Friday
6 Saturday
Extension file • Stores the block No. of the extension file register being used in
D9035 SD1035 SD648 Use block No.
register BCD code.
• Designate the device number for the extension file register for
direct read and write in 2 words at SD1036 and SD1037 in BIN
data.
D9036 SD1036 Use consecutive numbers beginning with R0 of block No. 1 to
designate device numbers.
Device number when Extension file register
Extension file
individual devices 0
registerfor to Block No.1
from extension file
designation of 16383 area
register are directly
device number
accessed 16384 Block No.2
to area
D9037 SD1037 SD1037,SD1036
Device No. (BIN data)
to
D9039 SD1039 SD208 Priorities 5 to 7 • For details, refer to the applicable CPUs User's Manual and the
ACPU Programming manual (Fundamentals).
Qn(H)
QnPH
• Turned on/off with a peripheral device.
When STRA or STRAR instruction is executed, the value stored in
For sampling Step or time during SD1044 is used as the sampling trace condition.
D9044 SD1044
trace sampling trace At scanning--------0
At time--------------Time (10 msec unit)
The value is stored into SD1044 in BIN code.
• Stores the block number of the expansion file register which is
used as the work area for the execution of a SFC program in a
Work area for Block number of
D9049 SD1049 binary value.
SFC extension file register
• Stores "0" if an empty area of 16K bytes or smaller, which cannot
be expansion file register No. 1, is used or if SM320 is OFF.
• Stores error code of errors occurred in the SFC program in BIN
code.
0 : No error
SFC program Error code generated 80: SFC program parameter error
D9050 SD1050
error number by SFC program 81: SFC code error
82: Number of steps of simultaneous execution exceeded
83: Block start error
84: SFC program operation error
• Stores the block number in which an error occurred in the SFC
Block number where
D9051 SD1051 Error block program in BIN code.
error occurred
In the case of error 83 the starting block number is stored.
• Stores the step number, where error code 84 occurred in an SFC
Step number where program, in BIN value.
D9052 SD1052 Error step
error occurred • Stores "0" when error code 80, 81 or 82 occurred.
• Stores the block stating step number when error code 83 occurs.
12 - 261
CHAPTER12 TROUBLESHOOTING
Status latch
• Stores the block number and the step number if status latch is
executed in a SFC program.
12
D9055 SD1055 SD812 execution step Status latch step
number Block No. Step No.
(BIN) (BIN)
Upper 8 bits Lower 8 bits
PLC Data check of serial • In the self-loopback test of the serial communication module, the
Qn(H)
D9072 SD1072 communication communication serial communication module writes/reads data automatically to
QnPH
check module make communication checks.
Register for
• Sets the time check time of the data link instructions (ZNRD,
ZNWR) for the MELSECNET/10.
6
D9085 SD1085 setting time 1 s to 65535 s • Setting range : 1 s to 65535 s (1 to 65535)
check value • Setting unit :1s
• Default value : 10 s (If 0 has been set, default 10 s is applied) Qn(H)
7
QnPH
Number of
Number of special
special • For details, refer to the manual of each microcomputer program
D9090 SD1090 functions modules
functions package.
over
modules over
Qn(H)
D9091 SD1091
Detailed error
code
Self-diagnosis
detailed error code
• Stores the detail code of cause of an instruction error. QnPH
QnU*1
8
Head I/O • Stores the first two digits of the head I/O number of the I/O module,
Head I/O number of I/
number of I/O which will be dismounted/mounted online (with power on), in BIN Qn(H)
D9094 SD1094 SD251 O module to be
module to be value. QnPH
replaced
replaced Example) Input module X2F0 H2F
12 - 262
Table12.44 Special register
Special
ACPU Special
Register Corresponding
Special Register for Name Meaning Details
after CPU
Register Modification
Conversion
• Output module numbers (in units of 16 points), of which fuses have
D9100 SD1100
blown, are entered in bit pattern. (Preset output module numbers
when parameter setting has been performed.)
D9101 SD1101
b15 b14b13b12b11b10 b9 b8 b7 b6 b5 b4 b3 b2 b1 b0
D9102 SD1102 1 1
SD1100 0 0 0 (YC0)
0 0 0 0 0 0 0 0 0 0 0
(Y80)
D9106 SD1106 • Fuse blow check is executed also to the output module of remote I/
O station.
(If normal status is restored, clear is not performed. Therefore, it is
D9107 SD1107
required to perform clear by user program.)
D9108 SD1108
• Set the value of the step transition monitoring timer and the
annunciator number (F number) that will be turned ON when the
D9109 SD1109 monitoring timer times out.
b15 to b8 b7 to b0
D9110 SD1110
Step transfer Timer setting valve
Qn(H)
D9111 SD1111 – monitoring timer and the F number at
F number setting Timer time limit setting QnPH
setting time out
(02 to 255) (1 to 255 s:(1 s units))
D9112 SD1112
• By turning ON any of SM1108 to SM1114, the monitoring timer
D9113 SD1113 starts. If the transition condition following a step which corresponds
to the timer is not established within set time, set annunciator (F) is
turned on.)
D9114 SD1114
• When I/O modules, of which data are different from those entered
D9116 SD1116
at power-ON, have been detected, the I/O module numbers (in
units of 16 points) are entered in bit pattern. (Preset I/O module
D9117 SD1117 numbers set in parmeters when parameter setting has been
performed.)
D9118 SD1118
b15 b14b13b12b11b10 b9 b8 b7 b6 b5 b4 b3 b2 b1 b0
1
SD1116 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 XY
D9119 SD1119 Bit pattern, in units of 0
I/O module 16 points, indicating 1
– SD1117 0 0 0 0 0 0 XY 0 0 0 0 0 0 0 0 0
verification error the modules with 190
D9120 SD1120
verification errors. 1
SD1123 0 0 0 0 XY
7B0
0 0 0 0 0 0 0 0 0 0 0 Qn(H)
QnPH
D9121 SD1121
Indicates an I/O module verify error. QnU*1
D9122 SD1122
• I/O module verify check is executed also to remote I/O station
modules.
D9123 SD1123 (If normal status is restored, clear is not performed. Therefore, it is
required to perform clear by user program.)
• When one of F0 to 255 (F0 to 2047 for AuA and AnU) is turned on
by SET F instruction 1 is added to the contents of SD63. When
Number of
Number of annuciator RST F or LEDR instruction is executed, 1 is subtracted from the
D9124 SD1124 SD63 annuciator
detections contents of SD63.
detections
• Quantity, which has been turned on by SET F instruction is stored
into SD63 in BIN code. The value of SD63 is maximum 16.
12 - 263
CHAPTER12 TROUBLESHOOTING
SD1126 0 0 25 25 99 99 99 99 99 99 99 99 15
SD1129 0 0 0 0 0 0 0 65 65 65 65 65 38
D9131 SD1131 SD70
SD1130 0 0 0 0 0 0 0 0 38 38 38 38 110 7
SD1131 0 0 0 0 0 0 0 0 0 110 110 110 151
12 - 264
(11) QCPU with built-in Ethernet port
Table12.45 Special register
Corres-
Set by ponding Corresponding
Number Name Meaning Explanation
(When Set) ACPU CPU
D9
Stores the operation result of the time setting function.
Operation Stores 0: Not executed
SD1270
result operationresult. 1: Success
FFFFH: Failure
Stores years (last two digits of the Christian Era) and monthes by two digits of
BCD code.
b15 to b12 b11 to b8 b7 to b4 b3 to b0 Example:
SD1271 July, 1993
9307H
Year Month
Stores dates and hours acquired with time setting function by two digits of
BCD code.
Day Hour
Time setting function
Stores minutes and seconds acquired with time setting function by two digits
of BCD code.
Stores time
Execution b15 to b12 b11 to b8 b7 to b4 b3 to b0 Example: S (status
SD1273 acquired with time
time 35 min., 48 sec. change)
setting function.
3548H
Minute Second
Stores years (first two digits of the Christian Era) and days acquierd with time
setting function.
Connection 15
Forced Specifies forced Connection 16
connection connection b15b14 b13 b12 to b4 b3 b2 b1 b0 U
SD1277 invalidation invalidation. SD1277 0 0 0
MELSOFT communication
port (UDP/IP)
MELSOFT communication
port (TCP/IP)
FTP communication port
Directconnection to
MELSOFT
0: Valid (default)
1: Invalid
This register is to be invalidated if a socket communication is used as an
open system.
12 - 265
CHAPTER12 TROUBLESHOOTING
Corres-
1
Set by ponding Corresponding
Number Name Meaning Explanation
(When Set) ACPU CPU
SD1282
b15b14 to b1 b0 3
Open completion Stores open S (Status
SD1282 Connection 1 New QnU*2
signal completion status change)
Connection 2
to
Connection 15
Connection 16 12
0 : Open processing is not completed.
1 : Open processing is completed.
Open request status of connections using socket communication functions is
stored.
All bits corresponding to connections using any communications other than
the socket communication are fixed to "0".
b15b14 to b1 b0
SD1284
SD1284
Open request
signal
Stores open
request status Connection 1
Connection 2
S (Status
change)
New QnU*2 6
to
Connection 15
Connection 16
0 : No open requests
1 : In open request
7
Reception status of connections using socket communication functions is
stored.
All bits corresponding to connections using any communications other than
the socket communication are fixed to "0".
b15b14 to b1 b0
8
SD1286
Connection 1
Connection 2
to
Connection 15
Reception status Stores reception S (Status
It may take several seconds for the QCPU to determine whether to connect or
disconnect a built-in Ethernet port.
*2: The built-in Ethernet port QCPU whose serial number (first five digits) is "11012" or later is targeted.
12 - 266
(12) Fuse blown module
Table12.47 Special register
Corres-
Set by ponding Corresponding
Number Name Meaning Explanation
(When Set) ACPU CPU
D9
SD1300 • The numbers of output modules whose fuses have blown are input as a D9100
SD1301 bit pattern (in units of 16 points). D9101
(If the module numbers are set by parameter, the parameter-set
SD1302 D9102
numbers are stored.)
SD1303 • Also detects blown fuse condition at remote station output modules D9103
SD1304 Bit pattern in units D9104
b15 b14 b13 b12 b11b10 b9 b8 b7 b6 b5 b4 b3 b2 b1 b0
SD1305 of 16 points, D9105
indicating the 1 1 Qn(H)
SD1306 SD1300 0 0 0 (YC0) 0 0 0 (Y80) 0 0 0 0 0 0 0 0 D9106
Fuse blown modules whose QnPH
SD1307 1 S (Error) D9107
module fuses have blown SD1301
1
0 0 0 0 0 0 0 0 0 0 0 0 0 0 QnPRH
SD1308 0 : No blown fuse
(Y1F0) (Y1A0)
New QnU
SD1309 1 : Blown fuse 1 1
to present SD1331 0 0 0 0 Y1F
B0
0 0 0 0 0 0 0 Y1F
30
0 0 0 New
SD1330
Indicates fuse blow.
SD1331 New
• Not cleared even if the blown fuse is replaced with a new one.
This flag is cleared by error resetting operation.
12 - 267
CHAPTER12 TROUBLESHOOTING
12 - 268
(16) For redundant systems (Other system CPU information *1)
SD1600 to SD1659 is only valid during the back up mode for redundant systems, and
refresh cannot be done when in the separate mode.
SD1651 to SD1699 are valid in either the backup mode or separate mode.
When a stand-alone system SD1600 to SD1699 are all 0.
Corres-
Set by ponding Corresponding
Number Name Meaning Explanation
(When Set) ACPU CPU
SD *2
• If an error is detected by the error check for redundant system, the
corresponding bit shown below turns ON. That bit turns OFF when the
error is cleared after that.
Each bit
b15 b2 b1 b0 0: OFF
SD1600 Fixed to 0 1: ON
• If any of b0, b1, b2 and b15 is ON, the other bits are all OFF.
• In the debug mode, b0, b1, b2 and b15 are all OFF.
Stores the reasons for system switching.
• Stores the reasons for system switching into SD1601 of both systems
when system switching occarred.
• Initialized to 0 at power OFF to ON/reset to unreset.
• The following shows values stored into this register.
System 0: Initial value (System switching has not occurred)
System switching S(when system QnPRH
SD1601 switching 1: Power-OFF, Reset, H/W failure, WDT error,(*)
results is switched)
results 2: CPU stop error (except WDT)
3: System switching request by network module
16: System switching dedicated instruction
17: System switching request from GX Developer
*: When the system is switched by the power OFF/reset of the control
system, "1" is not stored into SD1601 of the new standby system.
• Stores the parameters for system switching dedicated instruction
System SP.CONTSW.
System switching
switching (The parameters (SD1602) for SP.CONTSW are stored in both systems
dedicated S(when system
SD1602 dedicated A&B)
instruction is switched)
instruction • SD1602 is only valid when "16" is stored in SD1601.
parameter
parameter • This SD1602 is updated once system switch instruction SP.CONTSW is
activated.
Other system Diagnostic error • The error value sorted in BIN code.
SD1610 S(Every END) SD0
diagnostic error code • Stores SD0 of the other system CPU module
SD1611 Other system • Stores the date and time when diagnostics error occurred corresponding
SD1612 diagnostic error Diagnostic error to error code stored in SD1610. SD1 to
S(Every END)
occurrence occurrence time • Data format is the same as SD1 to SD3. SD3
SD1613 time • Also, stores the value to SD1 to SD3.
Other system • Stores the category code corresponding to the error comment
error Error information information/individual information code.
SD1614 S(Every END) SD4
information category code • Data format is the same as SD4.
category • Also, stores the value to SD4.
• Stores the common information corresponding to the error code stored
SD1615 Other system
Error common in this system CPU. SD5 to
to error common S(Every END)
information • Data composition is the same as SD5 to SD15. SD15
SD1625 information
• Also, stores the value to SD5 to SD15.
• Stores the individual information corresponding to the error code stored
SD1626 Other system
Error individual in this system CPU. SD16 to
to error individual S(Every END)
information • Data composition is the same as SD16 to SD26. SD26
SD1636 information
• Also, stores the value to SD16 to SD26.
*2: Shows the special register (SD ) for the host system CPU module.
12 - 269
CHAPTER12 TROUBLESHOOTING
0:No error
1:Continue error
2:Stop error
F:Communication with
other system
6
Other system Other system disabled ( )
SD1650 operating operating S(Every END)
information information 0:RUN : Communication
2:STOP
3:PAUSE
with other system
disabled, debug
7
F:Communication with mode
other system – QnPRH
disabled ( )
*2 : Shows the special register (SD ) for the host system CPU.
12 - 270
(17) For redundant systems (Trucking)
SD1700 to SD1779 is valid only for redundant systems.
These are all 0 for stand-alone systems.
Table12.52 Special register
Corres-
Set by ponding Corresponding
Number Name Meaning Explanation
(When Set) ACPU CPU
D9
• When the tracking error is detected, count is added by one.
Tracking error Tracking error
SD1700 • The counter repeats an increment and decrement of the value; 0 S(Error) QnPRH
detection count detection count
32767 - 32768 0
• Set in seconds the waiting time of the standby system CPU module from
when online program change to the control system CPU module is
completed by the online program change for redundancy function until
the online program change to the standby system CPU module starts.
• If no online program change request is issued to the standby system
CPU module within the preset time after completion of the online
program change to the control system CPU module, both system CPU
modules judge it as the failure of the online program change for
redundancy. In this case, both system CPU modules resume the
Waiting time for New
Waiting time for consistency check between system A & B suspended during the online
online program
online program program change. Also, the control system CPU module is set to accept a
SD1710 change U/ S (Initial) QnPRH
change (standby new request of online program change for redundancy.
(standby
system) • When both systems are powered on, 90 seconds are set to SD1710 as
system)
the default value.
• Set the value within the range 90 to 3600 seconds. When the setting is 0
to 89 seconds, it is regarded as 90 seconds for operation. If the setting is
outside the allowed range, it is regarded other than 0 to 3600 seconds
for operation.
• The waiting time for a start of online program change to the standby
system CPU module is checked according to the SD1710 setting during
online change of multiple blocks and online change of batch of files for
redundancy.
12 - 271
CHAPTER12 TROUBLESHOOTING
6
Main base unit
Extension base unit 1st stage
:
Extension base unit 7th stage
• When configuring multiple CPU, the status is stored to 1st CPU module.
• Stores the failure detection status of the redundant power supply module
in the following bit pattern. (The corresponding bit is cleared to 0 when
the input power to the faulty redundant power supply module is switched
7
OFF after detection of the redundant power supply module failure.)
• Stores 0 when the main base unit is not the redundant power main base
unit (Q38RB).
Failure detection
status of power
Failure detection
status of power 8
supply 2 1 supply 1 1 Each bit
0: Redundant power supply
b15 to b9 b8 b7 to b1 b0 module failure not
Power supply Power supply detected/No redundant power
SD1781 to to
SD1781 failure detection failure detection supply module S(Every END) New
1: Redundant power supply Qn(H)*2
status status
QnPH*2
module failure detected
(Detectable for redundant
• When configuring multiple CPU, the status is stored to 1st CPU module.
• Counts the number of times of momentary power failure of the power
Momentary supply 1/2.
power failure Momentary power • Monitors the status of the power supply 1/ 2 mounted on the redundant
detection failure detection power main base unit (Q38RB) and counts the number of times of
SD1782 S(Every END) New
counter for count for power momentary power failure.
power supply supply 1 Status of power supply 1/power supply 2 mounted on the redundant
1*1 extension base unit is not monitored.
• When the CPU module starts, the counter of the power supply 1/ 2 is
cleared to 0.
• If the input power to one of the redundant power supply modules is
turned OFF, the corresponding counter is cleared to 0.
The counter is incremented by 1 every time the momentary power failure of
Momentary the power supply 1/ 2 is detected.(The counter repeats increment and
power failure Momentary power decrement of the value; 0 32767 – 32768 0 (The system monitor
detection failure detection of GX Developer shows the counter within the range between 0 and 65535.
SD1783 S(Every END) New
counter for count for power • Stores 0 when the main base unit is not the redundant power main base
power supply supply 2 unit (Q38RB).
2*1 • When configuring multiple CPU, the status is stored to 1st CPU module.
• The counter repeats increment and decrement of the value, 0 32767
– 32768 0
(The system monitor of GX Developer shows the counter within the
range between 0 and 65535.
*1: The "power supply 1" in dicates the redundant power supply module mounted on the POWER 1 slot of the redundant base unit (Q38RB/68RB/Q65WRB).
The "power supply 2" indicates the redundant power supply module mounted on the POWER 2 slot of the redundant base unit (Q38RB/68RB/Q65WRB).
*2: The module whose first 5 digits of serial No. is "07032" or later.
However, for the multiple CPU system configuration, this applies to all CPU modules whose first 5 digits of serial No. are "07032" or later.
*3: The module whose first 5 digits of serial No. is "10042" or later.
12 - 272
APPENDICES
(1) Q00JCPU
4-mounting screws (M4 14)
80 0.3 (3.15 0.01)
98 (3.86)
(0.28)
98 (3.86)
7
Unit : mm (inches)
Figure App.1 Q00JCPU
(2) Q00UJCPU
4-mounting screws (M4 14)
80 0.3 (3.15 0.01)
98 (3.86)
(0.28)
(0.16)
98 (3.86)
4
Unit : mm (inches)
Figure App.2 Q00UJCPU
App - 1
APPENDICES
(3) Q00CPU,Q01CPU,Q02CPU,Q02HCPU,Q06HCPU,Q12HCPU,Q25HCPU, 1
Q02PHCPU, Q06PHCPU, Q12PHCPU,Q25PHCPU, Q00UCPU, Q01UCPU,
Q02UCPU, Q03UDCPU, Q04UDHCPU, Q06UDHCPU, Q10UDHCPU, 2
Q13UDHCPU, Q20UDHCPU, Q26UDHCPU
Q02HCPU
MODE
3
RUN
ERR.
USER
BAT.
App
BOOT
APPEN-
(3.86)
98
DIX
PULL
USB
6
7
RS-232
23 (0.92)
(0.16)
8
4
App - 2
(4) Q03UDECPU,Q04UDEHCPU,Q06UDEHCPU,Q10UDEHCPU,Q13UDEHCPU,Q20U
DEHCPU,Q26UDEHCPU
(3.86)
98
(0.16)
23 (0.92)
4
115 (4.53) 27.4
(1.08)
Unit : mm (inches)
Figure App.4 Q03UDECPU,Q04UDEHCPU,Q06UDEHCPU,Q10UDEHCPU,Q13UDEHCPU,Q20UDEHCPU, Q26UDEHCPU
(5) Q12PRHCPU,Q25PRHCPU
Q25PRHCPU
MODE BACKUP
RUN CONTROL
ERR. SYSTEM A
USER SYSTEM B
BAT.
BOOT
98 (3.86)
TRACKING
98 (3.86)
PULL
USB
RS-232
(0.16)
50.8
4
(2.03)
89.3 (3.52) 2 55.2
(0.08) (2.17)
Unit : mm (inches)
Figure App.5 Q12PRHCPU,Q25PRHCPU
App - 3
APPENDICES
2
MODE
RUN
ERR.
USER
BAT.
BOOT
98 (3.86)
PULL
USB App
RS-232
APPEN-
DIX
30 (1.18)
LITHIUM BATTERY
MODEL Q7BAT-SET 6
8
Q25PRHCPU
MODE BACKUP
RUN CONTROL
ERR. SYSTEM A
USER SYSTEM B
BAT.
TRACKING
98 (3.86)
PULL
USB
RS-232
30 (1.18)
2
(0.08)
LITHIUM BATTERY
MODEL Q7BAT-SET
App - 4
(7) When Q3MEM-4MBS or Q3MEM-8MBS is mounted on the CPU module
98 (3.86)
89.3 (3.52) 24.5 5
(5.95) (0.20)
118.8 (4.68) 27.4
(1.09)
Unit : mm (inches)
Figure App.7 When Q3MEM-4MBS, Q3MEM-8MBS is mounted on the CPU module
App - 5
APPENDICES
1
Appendix 1.2 Power Supply Module
(1) Q61P-A1,Q61P-A2,Q61P,Q61P-D,Q62P,Q63P 2
Q61P-A1
POWER
App
98 (3.86)
APPEN-
DIX
PULL
7
90 (3.54) 55.2
(2.17)
Unit : mm (inches) 8
Figure App.8 Q61P-A1,Q61P-A2,Q61P,Q61P-D,Q62P,Q63P
(2) Q64P
PULL
Unit : mm (incases)
Figure App.9 Q64P
App - 6
(3) Q64PN
98 (3.86)
115 (4.53) 55.2 (2.17)
Unit : mm (inches)
Figure App.10 Q64PN
(4) Q61SP
Q61SP
INPUT Q61SP
100-240VAC
98 (3.86)
MITSUBISHI
90 (3.54) 14 27.4
(0.55) (1.08)
Unit : mm (inches)
Figure App.11 Q61SP
App - 7
APPENDICES
(5) Q63RP 1
Q63RP
2
POWER
98 (3.86)
App
APPEN-
DIX
PULL
6
115 (4.53) 83 (3.27)
Unit : mm (inches) 7
Figure App.12 Q63RP
(6) Q64RP 8
Q64RP POWER
PULL
Unit : mm (inches)
Figure App.13 Q64RP
App - 8
(7) A1S61PN,A1S62PN,A1S63P
A1S61PN
POWER
INPUT OUTPUT
100-240VAC DC 5V 5A
105VA
50 / 60Hz
130 (5.12)
NP
App - 9
APPENDICES
5V
98 (3.86)
(3.15 0.01)
3
SG
80 0.3
POWER CPU I/O0 I/O1 I/O2
FG
App
(0.28)
7.5
7
(0.30) 44.1
(1.74) 15.5 169 0.3 (0.65 0.01) APPEN-
(0.61) 189 (7.44) DIX
Unit : mm (inches)
Figure App.15 Q33B 6
(2) Q35B
4-mounting screws (M4×14) 7
OUT
8
98 (3.86)
5V
(3.15 0.01)
SG
80 0.3
7.5
7
(0.30) 44.1
(1.74) 15.5 224.5 0.3 (8.84 0.01)
(0.61) 245 (9.65)
Unit : mm (inches)
Figure App.16 Q35B
App - 10
(3) Q38B
OUT
80 0.3(3.15 0.01)
5V
98(3.86)
SG
a1 b1
POWER CPU I/O0 I/O1 I/O2 I/O3 I/O4 I/O5 I/O6 I/O7
FG
(0.28)
5V
(3.15 0.01)
98 (3.86)
SG
80 0.3
7.5
7
(0.30) 44.1
(1.74) 15.5 308 0.3 (12.13 0.01)
(0.61)
328 (12.91)
Unit : mm (inches)
Figure App.18 Q38B (4 base mounting holes)
App - 11
APPENDICES
(4) Q312B 1
(a) Q312B with 5 base mounting holes
5-mounting screws 2
(M4 14)
OUT
3
5V
(3.15 0.01)
98(3.86)
SG
80 0.3
a1 b1
POWER CPU I/O0 I/O1 I/O2 I/O3 I/O4 I/O5 I/O6 I/O7 I/O8 I/O9 I/O10 I/O11
FG
App
(0.28)
7
OUT
4-mounting screws (M4×14)
7
(3.15 0.01)
98 (3.86)
8
80 0.3
(0.28)
(0.30) 44.1
(1.74) 15.5 419 0.3 (16.50 0.01)
(0.61) 439 (17.28)
Unit : mm (inches)
Figure App.20 Q312B (4 base mounting holes)
App - 12
(5) Q32SB
4-mounting screws (M4×12)
(3.15 0.01)
98 (3.86)
5V
80 0.3
SG
(0.28)
7.5
7
(0.30) 18.5 101 0.3 (3.98 0.01)
(0.73) 8.5 (0.33) 114 (4.49)
Unit : mm (inches)
Figure App.21 Q32SB
(6) Q33SB
4-mounting screws (M4×12)
(3.15 0.01)
98 (3.86)
5V
80 0.3
SG
7.5
7
Unit : mm (inches)
Figure App.22 Q33SB
App - 13
APPENDICES
(7) Q35SB 1
4-mounting screws (M4×12)
(3.15 0.01)
98 (3.86)
5V
80 0.3
SG
App
(0.28)
7.5
7
(0.30) 18.5
(0.73) 8.5 184.5 0.3 (7.26 0.01)
(0.33) 197.5 (7.78)
APPEN-
DIX
Unit : mm (inches)
Figure App.23 Q35SB
6
(8) Q38RB
5-mounting
screws 7
(M4×14)
OUT
5V 5V 8
(3.15 0.01)
98 (3.86)
SG SG
80 0.3
7.5
7
(0.30)
170 0.3 (6.69 0.01) 249 0.3 (9.80 0.01)
44.1 (1.74)
15.5 (0.61) 439 (17.28)
Unit : mm (inches)
Figure App.24 Q38RB
App - 14
(9) Q38DB
5-mounting
screws
(M4 14)
OUT
5V
98 (3.86)
0.3
SG
a1 b1
POWER CPU I/O0 I/O1 I/O2 I/O3 I/O4 I/O5 I/O6 I/O7
80
FG 38D
7.5
7
Unit : mm (inches)
Figure App.25 Q38DB
(10)Q312DB
5-mounting
screws
(M4 14)
OUT
0.01)
5V
98 (3.86)
0.3
SG
a1 b1
POWER CPU I/O0 I/O1 I/O2 I/O3 I/O4 I/O5 I/O6 I/O7 I/O8 I/O9 I/O10 I/O11
(3.15
FG
80
312D
(0.28)
7.5
7
Unit : mm (inches)
Figure App.26 Q312DB
App - 15
APPENDICES
(3.15 0.01)
98 (3.86)
3
80 0.3
I/O0 I/O1
App
(0.28)
7.5
7
(0.30)
44.1
(1.74) 15.5 83.5 0.3 APPEN-
(0.16) (3.29 0.01) DIX
106 (4.17)
Unit : mm (inches)
Figure App.27 Q52B 6
(2) Q55B
4-mounting screws (M4×14)
7
IN OUT
8
(3.15 0.01)
98 (3.86)
80 0.3
7.5
7
(0.30)
44.1
(1.74) 15.5 167 0.3 (6.57 0.01)
(0.61) 189 (7.44)
Unit : mm (inches)
Figure App.28 Q55B
(3) Q63B
4-mounting screws (M4×14)
IN OUT
5V
98 (3.86)
(3.15 0.01)
SG
80 0.3
7.5
7
(0.30)
44.1
(1.74) 15.5 167 0.3 (6.57 0.01)
(0.61) 189 (7.44)
Unit : mm (inches)
Figure App.29 Q63B
App - 16
(4) Q65B
4-mounting screws (M4×14)
IN OUT
5V
(3.15 0.01)
98 (3.86)
SG
80 0.3
POWER I/O0 I/O1 I/O2 I/O3 I/O4
FG
(0.28)
7.5
7
(0.30)
44.1
(1.74) 15.5 222.5 0.3 (8.76 0.01)
(0.61) 245 (9.65)
Unit : mm (inches)
Figure App.30 Q65B
(5) Q68B
IN OUT
5V
98(3.86)
(3.15 0.01)
SG
80 0.3
a1 b1
FG
(0.28)
Unit : mm (inches)
Figure App.31 Q68B (5 base mounting holes)
5V
(3.15 0.01)
98 (3.86)
SG
80 0.3
7.5
7
(0.30)
44.1
(1.74) 15.5 306 0.3 (12.05 0.01)
(0.61) 328 (12.91)
Unit : mm (inches)
Figure App.32 Q68B (4 base mounting holes)
App - 17
APPENDICES
(6) Q612B 1
(a) Q612B with 5 base mounting holes
5-mounting screws
2
(M4 14)
IN OUT
3
5V
(3.15 0.01)
98(3.86)
80 0.3
SG
a1 b1
App
POWER I/O0 I/O1 I/O2 I/O3 I/O4 I/O5 I/O6 I/O7 I/O8 I/O9 I/O10 I/O11
FG
(0.28)
7
7.5(0.30) 15.5 190 0.3 (7.48 0.01) 227 0.3 (8.94 0.01) APPEN-
44.1 (0.61) 439 (17.28) DIX
(1.74)
Unit : mm (inches)
Figure App.33 Q612B (5 base mounting holes) 6
(b) Q612B with 4 base mounting holes
4-mounting screws (M4×14) 7
IN OUT
5V
(3.15 0.01)
98 (3.86)
8
SG
80 0.3
POWER I/O0 I/O1 I/O2 I/O3 I/O4 I/O5 I/O6 I/O7 I/O8 I/O9
FG
7.5
7
(0.30)
44.1
(1.74) 15.5 417 0.3 (16.42 0.01)
(0.61)
439 (17.28)
Unit : mm (inches)
Figure App.34 Q612B (4 base mounting holes)
App - 18
(7) QA1S65B
4-mounting screws (M5×25)
130 (5.12)
5V
SG
FG
(0.39)
16.4
10
(0.65)
51.2
10 295 0.3 (11.61 0.01)
(2.02)
(0.39) 315 (12.40)
Unit : mm (inches)
Figure App.35 QA1S65B
(8) QA1S68B
4-mounting screws (M5×25)
110 0.3 (4.33 0.01)
IN OUT
130 (5.12)
5V
SG
FG
16.4
10
(0.65)
51.2
(2.02) 10 400 0.3 (15.75 0.01)
(0.39) 420 (16.54)
Unit : mm (inches)
Figure App.36 QA1S68B
App - 19
APPENDICES
(9) QA65B 1
2 6-M4 screw 4- 6 installation holes
Base cover (for module installation) (M5 mounting screw)
2
3
0.01)
250 (9.84)
0.3 (7.87
App
200
APPEN-
DIX
6
332 0.3 (13.07 0.01)
46.6
(1.83) 352 (13.87)
7
Hand hold
Unit : mm (inches)
Figure App.37 QA65B
8
(10) QA68B
2 9-M4 screw 4- 6 installation holes
Base cover (for module installation) (M5 mounting screw)
0.3 (7.87
200
Unit : mm (inches)
Figure App.38 QA68B
App - 20
(11) Q68RB
5-mounting
screws
(M4×14)
IN OUT
5V 5V
(3.15 0.01)
98 (3.86)
SG SG
80 0.3
7.5
7
(0.30)
44.1 (1.74) 15.5 170 0.3 (6.69 0.01) 247 0.3 (9.72 0.01)
(0.61) 439 (17.28)
Unit : mm (inches)
Figure App.39 Q68RB
(12) Q65WRB
5-mounting
screws
(M4×14)
5V 5V
(3.15 0.01)
98 (3.86)
80 0.3
SG SG
7.5
7
(0.30)
44.1 15.5 170 0.3 (6.69 0.01) 247 0.3 (9.72 0.01)
(1.74) (0.61) 439 (17.28)
Unit : mm (inches)
Figure App.40 Q65WRB
App - 21
APPENDICES
2
(1.65)
42.0
3
10 34.2 6.0
(1.35) (0.24)
(0.39)
App
Unit : mm (inches)
Figure App.41 QC05B,QC06B,QC12B,QC30B,QC50B,QC100B
APPEN-
DIX
7
A
B
(1.56)
B
39.7
12.4 33.5
8
(0.49) (1.32)
Unit : mm (inches)
Figure App.42 QC10TR,QC30TR
App - 22
Appendix 1.7 Q8BAT-SET
Q8BAT
Q8BAT
89.8(3.54)
98(3.86)
OUTPUT
3VDC
49(1.93)
5.8
(0.18)
(0.23) 47.1(1.85)
4.5
Unit : mm (inches)
Figure App.43 Q8BAT
QC10BAT
QC10BAT
30
55(2.17)
(1.18)
39(1.54) 1000(39.37)
Unit : mm (inches)
Figure App.44 QC10BAT
App - 23
APPENDICES
: Usable/compatible, : Unusable/incompatible
8
App - 24
(2) Function comparisons and supported GX Developer versions
TableApp.2 Function comparisons and supported GX Developer versions
App - 25
APPENDICES
: Usable/compatible, : Unusable/incompatible 7
*1: For details of the SRAM card battery life, refer to Section 11.3.4.
App - 26
First 5 digits of Supported GX
Function Function version
serial No. Developer
Compatibility with the multiple CPU system *5 “02122“ or later Version 7 or later
*3 “03051“ or later Version 7.10L or later
Installation of PC CPU module into the multiple CPU system
Error detection in the redundant power supply system *2 Version 8.23Z or later
App - 27
APPENDICES
Appendix 2.3 Precautions for Using the High Performance Model QCPU of
Older Versions 1
(1) Q6BAT/Q7BAT battery life when the serial number (first five digits) of the QCPU
2
is "05010" or earlier
TableApp.5 Q6BAT/Q7BAT Battery life
3
Battery life
Q6BAT Q7BAT
Actual After SM52 Actual After SM52 App
CPU module Power-on service turned on service turned on
Guaranteed Guaranteed
model time ratio value (Backup value (Backup
value value APPEN-
(Reference power time (Reference power time
(70 ) (70 ) DIX
value) after an value) after an
(40 ) alarm) (40 ) alarm)
0%
5,433 hours 43,800 hours 120 hours 13,000 hours 43,800 hours 240 hours 6
0.62 years 5.00 years 5 days 1.48 years 5.00 years 10 days
7,761 hours. 43,800 hours 120 hours 18,571 hours. 43,800 hours 240 hours
30%
0.88 years 5.00 years 5 days 2.11 years 5.00 years 10 days
7
10,866 hours 43,800 hours 120 hours 26,000 hours 43,800 hours 240 hours
Q02CPU 50%
1.24 years 5.00 years 5 days 2.96 years 5.00 years 10 days
18,110 hours 43,800 hours 120 hours 43,333 hours 43,800 hours 240 hours
70%
2.06 years 5.00 years 5 days 4.94 years 5.00 years 10 days
8
43,800 hours 43,800 hours 120 hours 43,800 hours 43,800 hours 240 hours
100%
5.00 years 5.00 years 5 days 5.00 years 5.00 years 10 days
2,341 hours 14,550 hours 120 hours 5,000 hours 38,881 hours 240 hours
0%
Appendix 2.3 Precautions for Using the High Performance Model QCPU of Older Versions
Appendix 2 Functions Added or Changed by Version Upgrade
0.26 years 1.66 years 5 days 0.57 years 4.43 years 10 days
3,344 hours 20,786 hours 120 hours 7,142 hours 43,800 hours 240 hours
30%
0.38 years 2.37 years 5 days 0.81 years 5.00 years 10 days
Q02HCPU 4,682 hours 29,100 hours 120 hours 10,000 hours 43,800 hours 240 hours
50%
Q06HCPU 0.53 years 3.32 years 5 days 1.14 years 5.00 years 10 days
7,803 hours 43,800 hours 120 hours 16,666 hours 43,800 hours 240 hours
70%
0.89 years 5.00 years 5 days 1.90 years 5.00 years 10 days
43,800 hours 43,800 hours 120 hours 43,800 hours 43,800 hours 240 hours
100%
5.00 years 5.00 years 5 days 5.00 years 5.00 years 10 days
1,260 hours 6,096 hours 48 hours 2,900 hours 16,711 hours 96 hours
0%
0.14 years 0.69 years 2 days 0.33 years 1.90 years 4 days
1,800 hours 8,709 hours 48 hours 4,142 hours 23,873 hours 96 hours
30%
0.20 years 0.99 years 2 days 0.47 years 2.72 years 4 days
Q12HCPU 2,520 hours 12,192 hours 48 hours 5,800 hours 33,422 hours 96 hours
50%
Q25HCPU 0.28 years 1.39 years 2 days 0.66 years 3.81 years 4 days
4,200 hours 20,320 hours 48 hours 9,666 hours 43,800 hours 96 hours
70%
0.47 years 2.31 years 2 days 1.10 years 5.00 years 4 days
43,800 hours 43,800 hours 48 hours 43,800 hours 43,800 hours 96 hours
100%
5.00 years 5.00 years 2 days 5.00 years 5.00 years 4 days
App - 28
TableApp.6 Q6BAT/Q7BAT Battery life
Battery life
Q6BAT
CPU module Power-on
After SM52 turned on
model time ratio Guaranteed value Actual service value
(Backup power time after
(70 ) (Reference value) (40 )
an alarm)
43,800 hours 43,800 hours 600 hours
0%
5.00 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
30%
5.00 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
Q02CPU 50%
5.00 years 5.00years 25 days
43,800 hours 43,800 hours 600 hours
70%
5.00 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
100%
5.00 years 5.00 years 25 days
20,498 hours 43,800 hours 600 hours
0%
2.34 years 5.00 years 25 days
29,959 hours 43,800 hours 600 hours
30%
3.42 years 5.00 years 25 days
Q02HCPU 41,785 hours 43,800 hours 600 hours
50%
Q06HCPU 4.77 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
70%
5.00 years 5.00 years 25 days
43,800 hours 43,800 hours 600 hours
100%
5.00 years 5.00 years 25 days
11,038 hours 43,800 hours 240 hours
0%
1.26 years 5.00 years 10 days
16,200 hours 43,800 hours 240 hours
30%
1.80 years 5.00 years 10 days
Q12HCPU 22,075 hours 43,800 hours 240 hours
50%
Q25HCPU 2.52 years 5.00 years 10 days
37,055 hours 43,800 hours 240 hours
70%
4.23 years 5.00 years 10 days
43,800 hours 43,800 hours 240 hours
100%
5.00 years 5.00 years 10 days
App - 29
APPENDICES
(2) SRAM card battery life when the serial number (first five digits) of the QCPU is 1
"04011" or earlier
TableApp.7 SRAM card Battery life 2
Battery life
Power-on After SM52 turned on
SRAM card
time ratio
Guaranteed value Actual service value
(Backup power time
3
(MIN) (Reference Value)
after an alarm)
690 hours 6,336 hours
Q2MEM-1MBS
0%
0.07 years 0.72 years
8 hours App
Q2MEM-2MBS 11,784 hours 13,872 hours
100% 8 hours
1.34 years 1.58 years
APPEN-
DIX
(3) Number of file register points according to the serial number (first five digits)
TableApp.8 File register points 6
CPU module model name Number of file register points
Q02CPU 32K points
Q02HCPU Serial number (first five digits) is "04011" or earlier 32K points
7
Q06HCPU Serial number (first five digits) is "04012" or later 64K points
Serial number (first five digits) is "02091" or earlier 32K points
Q12HCPU
Q25HCPU Serial number (first five digits) is "02092" or later 128K points
8
Appendix 2.3 Precautions for Using the High Performance Model QCPU of Older Versions
Appendix 2 Functions Added or Changed by Version Upgrade
App - 30
Appendix 2.4 Process CPU Upgrade
App - 31
APPENDICES
App - 32
Appendix 2.6 Universal Model QCPU Upgrade
App - 33
APPENDICES
App - 34
Appendix 3 Precautions for Battery Transportation
Classification for
Product name Model Product supply status
transportation
Battery Q8BAT Lithium battery (assembled battery)
Q2MEM-BAT
SRAM card battery Lithium coin battery
Q3MEM-BAT
App - 35
APPENDICES
This section describes the precautions for disposing of waste batteries in EU member states and exporting batteries 2
and/or devices with built-in batteries to EU member states.
The symbol shown in Figure App.45 is printed on the batteries and packaging of batteries and devices with built-in
APPEN-
batteries used for Mitsubishi programmable controllers. DIX
The symbol indicates that batteries need to be disposed of separately from other wastes.
App - 36
Appendix 4.2 Exportation precautions
The new EU Battery Directive (2006/66/EC) requires the follwoing when marketing or exporting batteries and/or
devices with built-in batteries to EU member states.
• To print the symbol on batteries, devices, or their packaging
• To explain the symbol in the manuals of the products
(1) Labelling
To market or export batteries and/or devices with built-in batteries, which have no symbol, to EU member states
on September 26, 2008 or later, print the symbol shown in Figure App.45 on the batteries, devices, or their pack-
aging.
The requirements apply to batteries and/or devices with built-in batteries manufactured before the enforcement date of the
new EU Battery Directive(2006/66/EC).
App - 37
INDEX
1
[0] to [9] [D]
Index - 1
[F] Link special register [SW] . . . . . . . . . . . . . . . . . . . 4-2
Link special relay [SB] . . . . . . . . . . . . . . . . . . . . . 4-2
Fail-safe Low Voltage directive . . . . . . . . . . . . . . . . . . . . . . 9-1
Circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
Measures . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
[M]
Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Ferrite core . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13 Main base unit . . . . . . . . . . . . . . . . . . . . . . . . . . A-24
File register. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 Max. number of files stored . . . . . . . . . . . . . . . . . 4-2
Flash card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1 MELSECNET/H . . . . . . . . . . . . . . . . . . . . . . . . . A-25
Function input [FX] . . . . . . . . . . . . . . . . . . . . . . . . 4-3 Memory capacity. . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Function output [FY] . . . . . . . . . . . . . . . . . . . . . . . 4-3 Memory Card
Function register [FD] . . . . . . . . . . . . . . . . . . . . . . 4-3 Battery Installation into the Memory Card . . . . 7-11
Function version . . . . . . . . . . . . . . . . . . . . . . . . . 2-25 Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
List of usable memory cards . . . . . . . . . . . . . . . 7-1
[G] Loading/unloading procedures . . . . . . . . . . . . . 7-6
Part names . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
GOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-26 Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
GX Developer . . . . . . . . . . . . . . . . . . . . . . . . . . . A-26 Specifications of the battery . . . . . . . . . . . . . . 7-10
Memory size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
[H] Module
Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-24
High Performance model QCPU . . . . . . . . . . . . A-24 Module change
During System Operation . . . . . . . . . . . . . . 12-167
[I] Redundant power supply module . . . . . . . . 12-178
Multiple CPU high speed main base unit . . . . . . A-25
I/O control mode . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Index register [Z]. . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Intelligent function module [N]
Intelligent function module device. . . . . . . . . . . 4-3 Network module . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Intelligent function module parameter . . . . . . . . 4-2 No. of device points . . . . . . . . . . . . . . . . . . . . . . . 4-2
Intensive insulation . . . . . . . . . . . . . . . . . . . . . . . 9-18 No. of device tracking words. . . . . . . . . . . . . . . . . 4-3
Internal current consumption . . . . . . . . . . . . . . . . 4-3 No. of I/O device points . . . . . . . . . . . . . . . . . . . . 4-2
Internal relay [M]. . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 No. of I/O points . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Interrupt pointer [I] . . . . . . . . . . . . . . . . . . . . . . . . 4-3 Noise filter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13
Isolation transformer . . . . . . . . . . . . . . . . . . . . . . 9-14
[O]
[L]
Online (with power on) . . . . . . . . . . . . . . . . . . 12-167
Latch clear operation . . . . . . . . . . . . . . . . . . . . . 4-33 Online module change . . . . . . . . . . . . . . . . . . 12-167
Latch range. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3 Operation mode change . . . . . . . . . . . . . . . . . . . 4-36
Latch relay [L] . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
LED
[P]
"BAT." LED turns on . . . . . . . . . . . . . . . . . . . 12-20
"BOOT" LED of the CPU module flickers . . . 12-21 Part name
"ERR." LED of the CPU module turns on or Base unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
flickers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-19 Memory card . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
"MODE" LED of the CPU module does not Part names
turn on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10 Basic model QCPU . . . . . . . . . . . . . . . . . . . . . 4-26
"MODE" LED of the CPU module flickers . . . 12-11 High Performance model QCPU, Process
"POWER" LED of the power supply module CPU and Redundant CPU . . . . . . . . . . . . . . . 4-34
turns off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-12 Power supply module . . . . . . . . . . . . . . . . . . . 5-31
"POWER" LED of the redundant power Periodic inspection . . . . . . . . . . . . . . . . . . . . . . . 11-4
supply module turns on red. . . . . . . . . . . . . . 12-15 Pointer [P] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
"RUN" LED flickers . . . . . . . . . . . . . . . . . . . . 12-19 Power supply module
"RUN" LED of the CPU module turns off . . . 12-18 Connecting to the power supply module . . . . 10-44
"USER" LED turns on . . . . . . . . . . . . . . . . . . 12-20 External dimensions . . . . . . . . . . . . . . . . . . . App-6
LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26 Names of Parts and Settings . . . . . . . . . . . . . 5-31
Link direct device . . . . . . . . . . . . . . . . . . . . . . . . . 4-3 Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Link register [W] . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 Precaution
Link relay [B]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Index - 2
Connection of GOT . . . . . . . . . . . . . . . . . . . . . 2-13 Separate mode . . . . . . . . . . . . . . . . . . . . . . . . . . 4-38
Precaution on installation. . . . . . . . . . . . . . . . 10-10 Serial number . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25
Precautions for battery transportation . . . . . App-35 Singlar power supply system . . . . . . . . . . . . . . . 10-44 1
Precautions for using coaxial cables . . . . . . . . . 9-5 Slim type main base unit . . . . . . . . . . . . . . . . . . .A-24
Precautions for using the high performance Slim type power supply module . . . . . . . . . . . . . .A-25
model QCPU . . . . . . . . . . . . . . . . . . . . . . . . App-28 Special register [SD] . . . . . . . . . . . . . . . . . . . . . . . 4-3 2
Precautions when connecting the Special relay [SM] . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
uninterruptive power supply . . . . . . . . . . . . . . . 5-30 Specifications
System configuration . . . . . . . . . . . . . . . . . . . . . 2-6 Battery specifications . . . . . . . . . . . . . . . . . . . . 7-13
Wiring precautions . . . . . . . . . . . . . . . . . . . . . 10-39 Extension cable specifications . . . . . . . . . . . . . 6-21 3
Process control language . . . . . . . . . . . . . . . . . . . 4-1 General specifications . . . . . . . . . . . . . . . . . . . . 3-1
Process CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-24 Hardware specifications of the CPU module . . . 4-1
Processing speed . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Main base unit specifications . . . . . . . . . . . . . . . 6-2 4
Program capacity. . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Memory card specifications . . . . . . . . . . . . . . . . 7-2
Program language . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Performance specifications . . . . . . . . . . . . . . . . 4-1
Program size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8 Power supply module specifications . . . . . . . . . 5-2
INDEX
Program transfer time . . . . . . . . . . . . . . . . . . . . . . 1-4 Specifications of the battery for memory card
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
[Q] SRAM card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Standard RAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 INDEX
Q series . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-24 Standard ROM. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Q series power supply module . . . . . . . . . . . . . . A-25 Standards
Q3oooB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-25 EMC Directive . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Q3oooDB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-25 Low Voltage Directive . . . . . . . . . . . . . . . . . . . . 9-1 7
Q3oooRB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-25 Standby system . . . . . . . . . . . . . . . . . . . . . . . . . . 4-38
Q3oooSB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-25 Step relay [S] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Q5oooB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-25
Q6BAT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
System
Control system . . . . . . . . . . . . . . . . . . . . . . . . . 4-38
8
Q6oooB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-25 Standby system . . . . . . . . . . . . . . . . . . . . . . . . 4-38
Q6oooRB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-25 System A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-38
Q6oooWRB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-25 System B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-38
Q7BAT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13 System A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-38
Q7BAT-SET. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15 System B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-38
Q8BAT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13 System configuration
Q8BAT-SET. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16 Applicable softwares . . . . . . . . . . . . . . . . . . . . 2-22
QA1S6oooB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-25 Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
QA6oooB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-25 Overall configuration . . . . . . . . . . . . . . . . . . . . . 2-2
QnUD(H)CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . A-24 Peripheral device configuration . . . . . . . . . . . . 2-17
Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
[R] Sequence control language . . . . . . . . . . . . . . . . 4-1
System switching . . . . . . . . . . . . . . . . . . . . . . . . . 4-38
Redundant base unit . . . . . . . . . . . . . . . . . . . . . . A-25
Redundant CPU . . . . . . . . . . . . . . . . . . . . . . . . . A-24 [T]
Redundant power extension base unit . . . . . . . . A-24
Redundant power main base unit . . . . . . . . . . . . A-24 Timer [T] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Redundant power supply module . . . . . . . . . . . . A-25 Timer function . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Redundant power supply system . . . . . . . . . . . 10-45 Tracking execution time. . . . . . . . . . . . . . . . . . . . . 4-1
Redundant system Troubleshooting
Backup mode . . . . . . . . . . . . . . . . . . . . . . . . . . 4-38 Troubleshooting Basics . . . . . . . . . . . . . . . . . . 12-1
Debug mode . . . . . . . . . . . . . . . . . . . . . . . . . . 4-38 Troubleshooting flowchart
Operation mode change . . . . . . . . . . . . . . . . . 4-36 Flowchart for when it is unable to perform
Separate mode . . . . . . . . . . . . . . . . . . . . . . . . 4-38 boot operation from memory card . . . . . . . . . 12-27
Reset operation . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32 Flowchart for when output load of output
Retentive timer [ST]. . . . . . . . . . . . . . . . . . . . . . . . 4-2 module does not turn on . . . . . . . . . . . . . . . . 12-23
RUN/PAUSE contact . . . . . . . . . . . . . . . . . . . . . . . 4-3 Flowchart for when output module LED is not
turned on . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-22
[S] Flowchart for when program is rewritten
unintentionally . . . . . . . . . . . . . . . . . . . . . . . . 12-26
Screw tightening torque range. . . . . . . . . . . . . . 10-11
Index - 3
Flowchart for when the "ERR." LED is
on/flickering. . . . . . . . . . . . . . . . . . . . . . . . . . 12-19
Flowchart for when the "MODE" LED is
flickering . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11
Flowchart for when the "MODE" LED is not
turned on. . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10
Flowchart for when the "POWER" LED is turned
off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-12
Flowchart for when the "RUN" LED is turned
off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-18
Flowchart for when the ERR terminal is turned
off (opened). . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5
Flowchart for when unable to read a program
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-24
Flowchart for when unable to write a program
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-25
Flowchart for when UNIT VERIFY ERR. occurs
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-29
When "CONTROL BUS ERR." has occurred
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-30
When the "BAT." LED is turned on . . . . . . . . 12-20
When the "RUN" LED is flickering. . . . . . . . . 12-19
When the "USER" LED is turned on . . . . . . . 12-20
[U]
[W]
Weight
Base unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
CPU module . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Extension cable. . . . . . . . . . . . . . . . . . . . . . . . 6-21
Memory card . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Power supply module . . . . . . . . . . . . . . . . 5-3,5-14
Wiring
Wiring of extension cables . . . . . . . . . . . . . . 10-36
Wiring of I/O equipment . . . . . . . . . . . . . . . . 10-42
Wiring of I/O module . . . . . . . . . . . . . . . . . . . 10-42
Wiring to power supply module . . . . . . . . . . . 10-44
Wiring of I/O module. . . . . . . . . . . . . . . . . . . . . 10-42
Index - 4
Warranty
Please confirm the following product warranty details before using this product.
1. Gratis Warranty Term and Gratis Warranty Range
If any faults or defects (hereinafter "Failure") found to be the responsibility of Mitsubishi occurs during use of the
product within the gratis warranty term, the product shall be repaired at no cost via the sales representative or
Mitsubishi Service Company.
However, if repairs are required onsite at domestic or overseas location, expenses to send an engineer will be
solely at the customer's discretion. Mitsubishi shall not be held responsible for any re-commissioning,
maintenance, or testing on-site that involves replacement of the failed module.
[Gratis Warranty Term]
The gratis warranty term of the product shall be for one year after the date of purchase or delivery to a designated
place.
Note that after manufacture and shipment from Mitsubishi, the maximum distribution period shall be six (6) months,
and the longest gratis warranty term after manufacturing shall be eighteen (18) months. The gratis warranty term of
repair parts shall not exceed the gratis warranty term before repairs.
[Gratis Warranty Range]
(1) The range shall be limited to normal use within the usage state, usage methods and usage environment, etc.,
which follow the conditions and precautions, etc., given in the instruction manual, user's manual and caution
labels on the product.
(2) Even within the gratis warranty term, repairs shall be charged for in the following cases.
1. Failure occurring from inappropriate storage or handling, carelessness or negligence by the user. Failure
caused by the user's hardware or software design.
2. Failure caused by unapproved modifications, etc., to the product by the user.
3. When the Mitsubishi product is assembled into a user's device, Failure that could have been avoided if
functions or structures, judged as necessary in the legal safety measures the user's device is subject to or
as necessary by industry standards, had been provided.
4. Failure that could have been avoided if consumable parts (battery, backlight, fuse, etc.) designated in the
instruction manual had been correctly serviced or replaced.
5. Failure caused by external irresistible forces such as fires or abnormal voltages, and Failure caused by force
majeure such as earthquakes, lightning, wind and water damage.
6. Failure caused by reasons unpredictable by scientific technology standards at time of shipment from
Mitsubishi.
7. Any other failure found not to be the responsibility of Mitsubishi or that admitted not to be so by the user.
2. Onerous repair term after discontinuation of production
(1) Mitsubishi shall accept onerous product repairs for seven (7) years after production of the product is
discontinued.
Discontinuation of production shall be notified with Mitsubishi Technical Bulletins, etc.
(2) Product supply (including repair parts) is not available after production is discontinued.
3. Overseas service
Overseas, repairs shall be accepted by Mitsubishi's local overseas FA Center. Note that the repair conditions at
each FA Center may differ.
4. Exclusion of loss in opportunity and secondary loss from warranty liability
Regardless of the gratis warranty term, Mitsubishi shall not be liable for compensation of damages caused by any
cause found not to be the responsibility of Mitsubishi, loss in opportunity, lost profits incurred to the user by Failures
of Mitsubishi products, special damages and secondary damages whether foreseeable or not , compensation for
accidents, and compensation for damages to products other than Mitsubishi products, replacement by the user,
maintenance of on-site equipment, start-up test run and other tasks.
5. Changes in product specifications
The specifications given in the catalogs, manuals or technical documents are subject to change without prior notice.
6. Product application
(1) In using the Mitsubishi MELSEC programmable controller, the usage conditions shall be that the application will
not lead to a major accident even if any problem or fault should occur in the programmable controller device,
and that backup and fail-safe functions are systematically provided outside of the device for any problem or
fault.
(2) The Mitsubishi programmable controller has been designed and manufactured for applications in general
industries, etc. Thus, applications in which the public could be affected such as in nuclear power plants and
other power plants operated by respective power companies, and applications in which a special quality
assurance system is required, such as for Railway companies or Public service purposes shall be excluded
from the programmable controller applications.
In addition, applications in which human life or property that could be greatly affected, such as in aircraft,
medical applications, incineration and fuel devices, manned transportation, equipment for recreation and
amusement, and safety devices, shall also be excluded from the programmable controller range of
applications.
However, in certain cases, some applications may be possible, providing the user consults their local
Mitsubishi representative outlining the special requirements of the project, and providing that all parties
concerned agree to the special circumstances, solely at the users discretion.
Microsoft, Windows, Windows NT, and Windows Vista are registered trademarks of Microsoft Corporation in the United
States and other countries.
Pentium is a trademark of Intel Corporation in the United States and other countries.
Ethernet is a trademark of Xerox Corporation.
All other company names and product names used in this manual are trademarks or registered trademarks of their respective
companies.
SH(NA)-080483ENG-P
MITSUBISHI ELECTRIC
MITSUBISHI
ELECTRIC Mitsubishi Electric Europe B.V. /// FA - European Business Group /// Gothaer Straße 8 /// D-40880 Ratingen /// Germany
FACTORY AUTOMATION Tel.: +49(0)2102-4860 /// Fax: +49(0)2102-4861120 /// [email protected] /// www.mitsubishi-automation.com