Mitsubishi Electronics Digital Home Theater Server Qnucpu Users Manual User's (Function Explanation, Program Fundamentals)

QnUCPU to the manual 5f0c62ae-3154-4750-b924-eaffe9077da0

2015-02-09

: Mitsubishi-Electronics Mitsubishi-Electronics-Mitsubishi-Digital-Electronics-Home-Theater-Server-Qnucpu-Users-Manual-556715 mitsubishi-electronics-mitsubishi-digital-electronics-home-theater-server-qnucpu-users-manual-556715 mitsubishi-electronics pdf

Open the PDF directly: View PDF .
Page Count: 630

Download
Open PDF In Browser	View PDF

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: "

WARNING" and "

CAUTION".

WARNING

Indicates that incorrect handling may cause hazardous conditions,
resulting in death or severe injury.

CAUTION

Indicates that incorrect handling may cause hazardous conditions,
resulting in minor or moderate injury or property damage.

Under some circumstances, failure to observe the precautions given under "

CAUTION" may lead to

serious consequences.
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]
WARNING
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

Output

Overcurrent or overvoltage protection of the power supply module
is activated.

All outputs are turned off.

The CPU module detects an error such as a watchdog timer error
by the self-diagnostic function.

All outputs are held or turned off according to
the 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 Chapter 10 LOADING AND INSTALLATION in the QCPU User's Manual
(Hardware Design, Maintenance and Inspection).
(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]
WARNING
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 the
QCPU User's Manual (Hardware Design, Maintenance and Inspection).
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 the relevant sections in the QCPU User's Manual (Hardware Design,
Maintenance and Inspection) and in the manual for the corresponding module.
Do not directly touch any conductive part of the module.
Doing so can cause malfunction or failure of the 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]
WARNING
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.

CAUTION
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.
Tighten the terminal screw within the specified torque range.
Undertightening can cause short circuit, fire, or malfunction.
Overtightening can damage the screw and/or module, resulting in drop, short circuit, 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]
WARNING
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.
Mitsubishi programmable controllers must be installed in control panels.
Connect the main power supply to the power supply module in the control panel through a relay
terminal block.
Wiring and replacement of a power supply module must be performed by maintenance personnel
who is familiar with protection against electric shock. (For wiring methods, refer to the QCPU User's
Manual (Hardware Design, Maintenance and Inspection)).

[Startup and Maintenance Precautions]
WARNING
Do not touch any terminal while power is on.
Doing so will cause electric shock.
Correctly connect the battery connector.
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, 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 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.
Do not disassemble or 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.
For details, refer to the relevant sections in the QCPU User's Manual (Hardware Design,
Maintenance and Inspection) and in 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.
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.

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 member states, refer to the QCPU User's Manual
(Hardware Design, Maintenance and Inspection).)

[Transportation Precautions]
CAUTION
When transporting lithium batteries, follow the transportation regulations.
(For details of the regulated models, refer to the QCPU User's Manual (Hardware Design,
Maintenance and Inspection).)

A-8

CONDITIONS OF USE FOR THE PRODUCT
(1) Mitsubishi programmable controller ("the PRODUCT") shall be used in conditions;
i) where any problem, fault or failure occurring in the PRODUCT, if any, shall not lead to any major
or serious accident; and
ii) where the backup and fail-safe function are systematically or automatically provided outside of
the PRODUCT for the case of any problem, fault or failure occurring in the PRODUCT.
(2) The PRODUCT has been designed and manufactured for the purpose of being used in general
industries.
MITSUBISHI SHALL HAVE NO RESPONSIBILITY OR LIABILITY (INCLUDING, BUT NOT
LIMITED TO ANY AND ALL RESPONSIBILITY OR LIABILITY BASED ON CONTRACT,
WARRANTY, TORT, PRODUCT LIABILITY) FOR ANY INJURY OR DEATH TO PERSONS OR
LOSS OR DAMAGE TO PROPERTY CAUSED BY the PRODUCT THAT ARE OPERATED OR
USED IN APPLICATION NOT INTENDED OR EXCLUDED BY INSTRUCTIONS, PRECAUTIONS,
OR WARNING CONTAINED IN MITSUBISHI'S USER, INSTRUCTION AND/OR SAFETY
MANUALS, TECHNICAL BULLETINS AND GUIDELINES FOR the PRODUCT.
("Prohibited Application")
Prohibited Applications include, but not limited to, the use of the PRODUCT in;
• Nuclear Power Plants and any other power plants operated by Power companies, and/or any
other cases in which the public could be affected if any problem or fault occurs in the PRODUCT.
• Railway companies or Public service purposes, and/or any other cases in which establishment of
a special quality assurance system is required by the Purchaser or End User.
• Aircraft or Aerospace, Medical applications, Train equipment, transport equipment such as
Elevator and Escalator, Incineration and Fuel devices, Vehicles, Manned transportation,
Equipment for Recreation and Amusement, and Safety devices, handling of Nuclear or
Hazardous Materials or Chemicals, Mining and Drilling, and/or other applications where there is a
significant risk of injury to the public or property.
Notwithstanding the above, restrictions Mitsubishi may in its sole discretion, authorize use of the
PRODUCT in one or more of the Prohibited Applications, provided that the usage of the PRODUCT
is limited only for the specific applications agreed to by Mitsubishi and provided further that no
special quality assurance or fail-safe, redundant or other safety features which exceed the general
specifications of the PRODUCTs are required. For details, please contact the Mitsubishi
representative in your region.

A-9

REVISIONS
*The manual number is given on the bottom left of the back cover.
Print date

Manual number

Revision

Dec., 2008

SH(NA)-080807ENG-A First edition

Mar., 2009

SH(NA)-080807ENG-B Revision because of function addition to Built-in Ethernet port QCPU (first five
digits of the serial number is "11012" or later)
Partial correction
SAFETY PRECAUTIONS, INTRODUCTION, MANUALS, MANUAL PAGE
ORGANIZATION, GENERIC TERMS AND ABBREVIATIONS, Section 1.3, 1.6,
2.2.2, 2.2.3, 2.3, 2.3.3, 2.3.4, 2.4, CHAPTER 3, Section 3.3, CHAPTER 4, Section 4.1.2, 4.2.2, 4.2.3, 5.1.1, 5.1.3, 5.1.6, 5.1.7, 5.1.8, 5.1.10, 6.1, 6.3, 6.4, 6.5,
6.6.1, 6.6.5, 6.11.1, 6.11.3, 6.11.4, 6.12.1, 6.13.3, 6.14, 6.15, 6.15.1, 6.15.2,
6.16, 6.17, 6.18, 6.20, 6.28, 6.30, 7.1.2, 8.2, 8.3, 9.2, 9.2.5, 9.2.11, 9.7.4, 9.11,
9.14.2, 11.5, Appendix 1, Appendix 2, Appendix 3.1, Appendix 3.3.2, Appendix 4
Addition
Appendix 3.4.2

Jul., 2009

SH(NA)-080807ENG-C Revision because of function addition to the Universal model QCPU (first five
digits of the serial number is "11043" or later)
Partial correction
Section 5.1.1, 5.1.5, 5.3.3, 6.1, 6.18, 6.21.2, 6.28, 8.1, 9.2.10, 9.6.1, 10.1.3, 12.2,
Appendix 1, Appendix 2, Appendix 3.1.2, Appendix 3.2
Addition
Section 6.31, 6.32

Nov., 2009

SH(NA)-080807ENG-D Partial correction
SAFETY PRECAUTIONS, Section 4.2.2, 9.6.1, 9.7.4, Appendix 3.1.1,
Appendix 3.1.2
Addition
CONDITIONS OF USE FOR THE PRODUCT

Japanese manual version SH-080802-D
This manual confers no industrial property rights or any rights of any other kind, nor does it confer any patent licenses. Mitsubishi 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

A - 10

2008 MITSUBISHI ELECTRIC CORPORATION

INTRODUCTION
This manual describes the memory maps, functions, programs, I/O number assignment, and devices of the Universal model
QCPU.
Before using this product, please read this manual and the relevant manuals carefully and develop familiarity with the
functions and performance of the Q series programmable controller to handle the product correctly.
Relevant CPU module
CPU module
Universal model QCPU

Model
Q00UJCPU, Q00UCPU, Q01UCPU, Q02UCPU, Q03UD(E)CPU,
Q04UD(E)HCPU, Q06UD(E)HCPU, Q10UD(E)HCPU,
Q13UD(E)HCPU, Q20UD(E)HCPU, Q26UD(E)HCPU

Remark
This manual does not describe the specifications of the power supply modules, base units, extension cables, memory
cards, and batteries.
For details, refer to the following.
QCPU User's Manual (Hardware Design, Maintenance and Inspection)
For multiple CPU systems, refer to the following.
QCPU User's Manual (Multiple CPU System)

A - 11

CONTENTS
CONTENTS

SAFETY PRECAUTIONS...................................................................................................................... A - 1
CONDITIONS OF USE FOR THE PRODUCT ...................................................................................... A - 9
REVISIONS ........................................................................................................................................... A - 10
INTRODUCTION ................................................................................................................................... A - 11
MANUALS ............................................................................................................................................. A - 18
MANUAL PAGE ORGANIZATION ......................................................................................................... A - 20
GENERIC TERMS AND ABBREVIATIONS .......................................................................................... A - 21

CHAPTER1 OVERVIEW
1.1

Processing Order in the CPU Module.................................................................................... 1 - 1

1.2

Storing and Executing Programs ........................................................................................... 1 - 2

1.3

Structured Programming ........................................................................................................ 1 - 3

1.4

Devices and Instructions Useful for Programming................................................................. 1 - 6

1.5

Features................................................................................................................................. 1 - 11

1.6

Checking Serial Number and Function Version ..................................................................... 1 - 13

CHAPTER2 SEQUENCE PROGRAMS
2.1
2.2

2.3

2.4

2-1 to 2-43

Sequence Program Overview ................................................................................................ 2 - 1
Sequence Program Configuration.......................................................................................... 2 - 3
2.2.1

Main routine program ........................................................................................................ 2 - 4

2.2.2

Subroutine program .......................................................................................................... 2 - 5

2.2.3

Interrupt program .............................................................................................................. 2 - 6

Settings When Program is Divided ........................................................................................ 2 - 13
2.3.1

Initial execution type program ........................................................................................... 2 - 17

2.3.2

Scan execution type program ........................................................................................... 2 - 20

2.3.3

Stand-by type program ...................................................................................................... 2 - 21

2.3.4

Fixed scan execution type program .................................................................................. 2 - 26

2.3.5

Changing the program execution type .............................................................................. 2 - 30

Data Used in Sequence Programs ........................................................................................ 2 - 32
2.4.1

BIN (Binary Code) ............................................................................................................. 2 - 35

2.4.2

HEX (Hexadecimal)........................................................................................................... 2 - 37

2.4.3

BCD (Binary-coded Decimal) ............................................................................................ 2 - 38

2.4.4

Real number (Floating-point data)..................................................................................... 2 - 39

2.4.5

Character string data......................................................................................................... 2 - 43

CHAPTER3 CPU MODULE OPERATION

A - 12

1-1 to 1-14

3-1 to 3-14

3.1

Initial Processing.................................................................................................................... 3 - 1

3.2

I/O Refresh (Refresh Processing with Input/Output Modules) ............................................... 3 - 2

3.3

Program Operation ................................................................................................................ 3 - 2

3.4

END Processing..................................................................................................................... 3 - 2

3.5

Operation Processing in the RUN,STOP, or PAUSE Status .................................................. 3 - 3

3.6

Operation Processing during Momentary Power Failure ....................................................... 3 - 5

3.7

Data Clear Processing ........................................................................................................... 3 - 6

3.8

I/O Processing and Response Delay ..................................................................................... 3 - 8
3.8.1

Refresh mode.................................................................................................................... 3 - 9

3.8.2

Direct mode ....................................................................................................................... 3 - 12

CHAPTER4 ASSIGNMENT OF BASE UNIT AND I/O NUMBER
4.1

4.2

Base Unit Assignment............................................................................................................ 4 - 1
4.1.1

Base mode ........................................................................................................................ 4 - 1

4.1.2

Base unit assignment setting ............................................................................................ 4 - 2

I/O Number Assignment......................................................................................................... 4 - 4
4.2.1

Concept of I/O number assignment .................................................................................. 4 - 5

4.2.2

Setting I/O numbers .......................................................................................................... 4 - 8

4.2.3

I/O number setting example .............................................................................................. 4 - 13

4.2.4

Checking I/O numbers ...................................................................................................... 4 - 17

CHAPTER5 MEMORIES AND FILES USED FOR CPU MODULE
5.1

4-1 to 4-17

5-1 to 5-38

Memories Used for CPU Module ........................................................................................... 5 - 1
5.1.1

Memory composition and storable data ............................................................................ 5 - 1

5.1.2

Program memory .............................................................................................................. 5 - 5

5.1.3

Program cache memory .................................................................................................... 5 - 8

5.1.4

Standard ROM .................................................................................................................. 5 - 11

5.1.5

Standard RAM ................................................................................................................... 5 - 12

5.1.6

Memory card ..................................................................................................................... 5 - 14

5.1.7

Writing to the Flash card by GX Developer ....................................................................... 5 - 18

5.1.8

Operating the program in the memory card (boot operation) ............................................ 5 - 23

5.1.9

Details of written files ........................................................................................................ 5 - 27

5.1.10

Specifying valid parameters (parameter-valid drive setting).............................................. 5 - 28

5.2

Program File Structure ........................................................................................................... 5 - 30

5.3

File Operations by GX Developer and Handling Precautions ................................................ 5 - 32
5.3.1

File operations................................................................................................................... 5 - 32

5.3.2

Precautions for handling files ............................................................................................ 5 - 33

5.3.3

File size ............................................................................................................................. 5 - 34

5.3.4

Units of file sizes ............................................................................................................... 5 - 36

CHAPTER6 FUNCTIONS

6-1 to 6-165

6.1

Function List........................................................................................................................... 6 - 1

6.2

Constant Scan ....................................................................................................................... 6 - 4

6.3

Latch Function ....................................................................................................................... 6 - 7

6.4

Output Mode at Operating Status Change (STOP to RUN)................................................... 6 - 10

6.5

Clock Function ....................................................................................................................... 6 - 13

6.6

Remote Operation.................................................................................................................. 6 - 18
6.6.1

Remote RUN/STOP .......................................................................................................... 6 - 18

6.6.2

Remote PAUSE................................................................................................................. 6 - 21

6.6.3

Remote RESET................................................................................................................. 6 - 23

A - 13

6.6.4

Remote latch clear ............................................................................................................ 6 - 25

6.6.5

Relationship between remote operation and RUN/STOP status of the CPU module ....... 6 - 26

6.7

Q Series-compatible Module Input Response Time Selection (I/O Response Time) ............ 6 - 27

6.8

Error Time Output Mode Setting ............................................................................................ 6 - 29

6.9

H/W Error Time PLC Operation Mode Setting ....................................................................... 6 - 30

6.10 Intelligent Function Module Switch Setting ............................................................................ 6 - 31
6.11 Monitor Function .................................................................................................................... 6 - 33
6.11.1

Monitor condition setting ................................................................................................... 6 - 34

6.11.2

Local device monitor/test .................................................................................................. 6 - 40

6.11.3

External input/output forced on/off .................................................................................... 6 - 43

6.11.4

Executional conditioned device test .................................................................................. 6 - 48

6.12 Writing Programs While CPU Module is in RUN Status......................................................... 6 - 58
6.12.1

Online change (ladder mode)............................................................................................ 6 - 58

6.12.2

Online change (files) ......................................................................................................... 6 - 61

6.12.3

Precautions for online change........................................................................................... 6 - 63

6.13 Execution Time Measurement ............................................................................................... 6 - 69
6.13.1

Program monitor list .......................................................................................................... 6 - 69

6.13.2

Interrupt program monitor list ............................................................................................ 6 - 72

6.13.3

Scan time measurement ................................................................................................... 6 - 73

6.14 Sampling Trace Function ....................................................................................................... 6 - 77
6.15 Debug Function from Multiple GX Developers....................................................................... 6 - 91
6.15.1

Simultaneous monitoring from multiple GX Developers function ...................................... 6 - 91

6.15.2

Online change function from multiple GX Developers ...................................................... 6 - 93

6.16 Watchdog Timer (WDT) ......................................................................................................... 6 - 95
6.17 Self-diagnostic Function......................................................................................................... 6 - 97
6.17.1

LEDs indicating errors ....................................................................................................... 6 - 104

6.17.2

Error clear ......................................................................................................................... 6 - 104

6.18 Error History........................................................................................................................... 6 - 105
6.19 System Protection.................................................................................................................. 6 - 106
6.19.1

Password registration........................................................................................................ 6 - 106

6.19.2

Remote password ............................................................................................................. 6 - 108

6.20 System Display of CPU Module with GX Developer.............................................................. 6 - 113
6.21 LED Indication........................................................................................................................ 6 - 116
6.21.1

Methods for turning off the LEDs....................................................................................... 6 - 116

6.21.2

LED indication priority ....................................................................................................... 6 - 117

6.22 Interrupt from Intelligent Function Module ............................................................................. 6 - 119
6.23 Serial Communication Function ............................................................................................. 6 - 120
6.24 Service Processing ................................................................................................................ 6 - 128
6.24.1

Service processing setting ................................................................................................ 6 - 128

6.25 Initial Device Value................................................................................................................. 6 - 135
6.26 Battery Life-prolonging Function ............................................................................................ 6 - 139
6.27 Memory Check Function ........................................................................................................ 6 - 140
6.28 Latch Data Backup to Standard ROM Function ..................................................................... 6 - 141
6.29 Writing/Reading Device Data to/from Standard ROM ............................................................ 6 - 146
6.30 CPU Module Change Function with Memory Card ................................................................ 6 - 147
6.30.1

A - 14

Backup function to memory card....................................................................................... 6 - 149

6.30.2

Backup data restoration function....................................................................................... 6 - 157

6.31 Module model name read ...................................................................................................... 6 - 161
6.32 Module error collection........................................................................................................... 6 - 162

CHAPTER7 COMMUNICATIONS WITH INTELLIGENT FUNCTION
MODULE
7.1

7-1 to 7-9

Communications between CPU Module and Intelligent Function Module ............................. 7 - 1
7.1.1

Initial setting and auto refresh setting by GX Configurator................................................ 7 - 2

7.1.2

Initial setting by initial device value ................................................................................... 7 - 5

7.1.3

Communications with the FROM and TO instructions ...................................................... 7 - 5

7.1.4

Communications using the intelligent function module device .......................................... 7 - 6

7.1.5

Communications using the intelligent function module dedicated instruction ................... 7 - 8

CHAPTER8 PARAMETERS

8-1 to 8-26

8.1

PLC Parameters .................................................................................................................... 8 - 2

8.2

Network Parameters .............................................................................................................. 8 - 21

8.3

Remote Password.................................................................................................................. 8 - 26

CHAPTER9 DEVICES
9.1
9.2

9.3

9.4
9.5

9-1 to 9-94

Device List ............................................................................................................................. 9 - 1
Internal User Device .............................................................................................................. 9 - 3
9.2.1

Input (X) ............................................................................................................................ 9 - 6

9.2.2

Output (Y).......................................................................................................................... 9 - 8

9.2.3

Internal relay (M) ............................................................................................................... 9 - 9

9.2.4

Latch relay (L) ................................................................................................................... 9 - 10

9.2.5

Annunciator (F) ................................................................................................................. 9 - 11

9.2.6

Edge relay (V) ................................................................................................................... 9 - 15

9.2.7

Link relay (B) ..................................................................................................................... 9 - 16

9.2.8

Link special relay (SB) ...................................................................................................... 9 - 18

9.2.9

Step relay (S) .................................................................................................................... 9 - 19

9.2.10

Timer (T)............................................................................................................................ 9 - 20

9.2.11

Counter (C) ....................................................................................................................... 9 - 27

9.2.12

Data register (D)................................................................................................................ 9 - 31

9.2.13

Link register (W) ................................................................................................................ 9 - 32

9.2.14

Link special register (SW) ................................................................................................. 9 - 34

Internal System Devices ........................................................................................................ 9 - 35
9.3.1

Function devices (FX, FY, FD) .......................................................................................... 9 - 35

9.3.2

Special relay (SM) ............................................................................................................. 9 - 38

9.3.3

Special register (SD) ......................................................................................................... 9 - 39

Link Direct Device (J\)............................................................................................................ 9 - 40
Module Access Devices......................................................................................................... 9 - 43
9.5.1

Intelligent function module device (U\G) ........................................................................... 9 - 43

9.5.2

Cyclic transmission area device (U3En\G)........................................................................ 9 - 45

A - 15

9.6

Index Register (Z)/Standard Device Resister (Z) ................................................................... 9 - 46
9.6.1

Index register (Z) ............................................................................................................... 9 - 46

9.6.2

Standard device register (Z) .............................................................................................. 9 - 48

9.6.3

Switching from the scan execution type program to the interrupt/fixed scan execution
type program .................................................................................................... 9 - 49

9.7

File Register (R)..................................................................................................................... 9 - 53
9.7.1

File register data storage location ..................................................................................... 9 - 54

9.7.2

File register size ................................................................................................................ 9 - 54

9.7.3

Differences in available accesses by storage memory ..................................................... 9 - 55

9.7.4

Registration procedure for the file register ........................................................................ 9 - 56

9.7.5

Specification methods of the file register........................................................................... 9 - 61

9.7.6

Precautions for using the file register ................................................................................ 9 - 62

9.8

Extended Data Register (D) and Extended Link Register (W) ............................................... 9 - 64

9.9

Nesting (N)............................................................................................................................ 9 - 70

9.10 Pointer (P).............................................................................................................................. 9 - 71
9.10.1

Local pointer..................................................................................................................... 9 - 72

9.10.2

Common pointer................................................................................................................ 9 - 74

9.11 Interrupt Pointer(I).................................................................................................................. 9 - 76
9.11.1

List of interrupt pointer numbers and interrupt factors ...................................................... 9 - 77

9.12 Other Devices ........................................................................................................................ 9 - 78
9.12.1

SFC block device (BL) ...................................................................................................... 9 - 78

9.12.2

Network No. specification device (J) ................................................................................. 9 - 78

9.12.3

I/O No. specification device (U)......................................................................................... 9 - 79

9.12.4

Macro instruction argument device (VD) ........................................................................... 9 - 80

9.13 Constants ............................................................................................................................... 9 - 81
9.13.1

Decimal constant (K) ......................................................................................................... 9 - 81

9.13.2

Hexadecimal constant (H) ................................................................................................. 9 - 81

9.13.3

Real number (E) ................................................................................................................ 9 - 82

9.13.4

Character string (" ").......................................................................................................... 9 - 83

9.14 Convenient Usage of Devices................................................................................................ 9 - 84
9.14.1

Global device .................................................................................................................... 9 - 84

9.14.2

Local device ...................................................................................................................... 9 - 85

CHAPTER10 CPU MODULE PROCESSING TIME

10-1 to 10-18

10.1 Scan Time .............................................................................................................................. 10 - 1
10.1.1

Scan time structure ........................................................................................................... 10 - 1

10.1.2

Time required for each processing included in scan time ................................................. 10 - 2

10.1.3

Factors that increase the scan time .................................................................................. 10 - 11

CHAPTER11 PROCEDURES FOR WRITING PROGRAM TO CPU
MODULE

11-1 to 11-10

11.1 Items to be Considered for Creating Programs ..................................................................... 11 - 1
11.2 Hardware Check .................................................................................................................... 11 - 3
11.3 Procedure for Writing One Program ...................................................................................... 11 - 5

A - 16

11.4 Procedure for Writing Multiple Programs ............................................................................... 11 - 7
11.5 Procedure for Boot Operation ................................................................................................ 11 - 10

CHAPTER12 SPECIAL RELAY LIST AND SPECIAL REGISTER LIST

12-1 to 12-78

12.1 SPECIAL RELAY LIST........................................................................................................... 12 - 1
12.2 SPECIAL REGISTER LIST.................................................................................................... 12 - 27

APPENDICES

App-1 to App-72

Appendix 1 List of Parameter Numbers ......................................................................................... App- 1
Appendix 2 Functions Added or Changed by Version Upgrade..................................................... App- 6
Appendix 3 Method of Replacing Basic Model QCPU or High Performance Model QCPU
with Universal Model QCPU ............................................................................... App- 8
Appendix 3.1 Replacement Precautions ........................................................................... App- 8
Appendix 3.1.1 Replacing Basic model QCPU with Universal model QCPU ....................... App- 8
Appendix 3.1.2 Replacing High Performance model QCPU with Universal model QCPU ...... App- 12
Appendix 3.2 Applicable devices and software .................................................................. App- 19
Appendix 3.3 Instructions .............................................................................................. App- 23
Appendix 3.3.1 Instructions not supported in the Universal model QCPU and replacing
methods .......................................................................................... App- 23
Appendix 3.3.2 Replacing programs using multiple CPU transmission dedicated
instructions ...................................................................................... App- 25
Appendix 3.3.3 Program replacement examples ........................................................... App- 26
Appendix 3.4 Functions................................................................................................. App- 40
Appendix 3.4.1 Floating-point operation instructions ...................................................... App- 40
Appendix 3.4.2 Error check processing for floating-point data comparison instructions ......... App- 48
Appendix 3.4.3 Range check processing for index-modified devices ................................. App- 52
Appendix 3.4.4 Device latch function .......................................................................... App- 55
Appendix 3.4.5 File usability setting ............................................................................ App- 57
Appendix 3.4.6 Parameter-valid drive and boot file setting .............................................. App- 60
Appendix 3.4.7 External input/output forced on/off function ............................................. App- 63
Appendix 3.5 Special Relay and Special Register ............................................................... App- 67
Appendix 3.5.1 Special relay list ................................................................................ App- 67
Appendix 3.5.2 Special register list ............................................................................. App- 70

Appendix 4 Device Point Assignment Sheet.................................................................................. App- 72

INDEX

Index-1 to Index-4

A - 17

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 list.

:Basic manual,
Manual name

< Manual number (model code) >

:Other CPU module manuals

Description

User's manual
Specifications of the hardware (CPU modules, power
supply modules, base units, extension cables, and
memory cards), system maintenance and inspection,
< SH-080483ENG (13JR73) >
troubleshooting, and error codes

QCPU User's Manual (Hardware Design,
Maintenance and Inspection)

QnUCPU User's Manual (Function
Explanation, Program Fundamentals)

Functions, methods, and devices for programming

< SH-080807ENG (13JZ27) >

Information on multiple CPU system configuration
(system configuration, I/O numbers, communication
QCPU User's Manual (Multiple CPU System)
between CPU modules, and communication with the
< SH-080485ENG (13JR75) >
input/output modules and intelligent function
modules)
QnUCPU User's Manual (Communication via
Built-in Ethernet Port)
< SH-080811ENG (13JZ29) >

Functions for the communication via built-in Ethernet
port of the CPU module

Programming manual
QCPU Programming Manual (Common
Instructions)
< SH-080809ENG (13JW10) >

How to use sequence instructions, basic instructions,
and application instructions

QCPU (Q Mode)/QnACPU Programming
Manual (SFC)

System configuration, performance specifications,
functions, programming, debugging, and error codes
< SH-080041 (13JF60) > for SFC (MELSAP3) programs

QCPU (Q Mode) Programming Manual
(MELSAP-L)
< SH-080076 (13JF61) >

QCPU (Q Mode) Programming Manual
(Structured Text)

Programming methods, specifications, and functions
for SFC (MELSAP-L) programs

Programming methods using structured languages

< SH-080366E (13JF68) >

QCPU (Q Mode) / QnACPU Programming
Manual (PID Control Instructions)
< SH-080040 (13JF59) >

A - 18

Dedicated instructions for PID control

Manual type

Other relevant manuals
Manual name
CC-Link IE Controller Network Reference
Manual

Description

Specifications, procedures and settings before system operation, parameter
setting, programming, and troubleshooting of the CC-Link IE controller
< SH-080668ENG (13JV16) > network module
Q Corresponding MELSECNET/H Network
Specifications, procedures and settings before system operation, parameter
System Reference Manual (PLC to PLC
setting, programming, and troubleshooting of a MELSECNET/H network
network)
system (PLC to PLC network)
< SH-080049 (13JF92) >

Q Corresponding MELSECNET/H Network
System Reference Manual (Remote I/O
network)
< SH-080124 (13JF96) >

Specifications, procedures and settings before system operation, parameter
setting, programming, and troubleshooting of a MELSECNET/H network
system (remote I/O network)

Q Corresponding Ethernet Interface Module
User's Manual (Basic)

Specifications, procedures for data communication with external devices,
line connection (open/close), fixed buffer communication, random access
< SH-080009 (13JL88) > buffer communication, and troubleshooting of the Ethernet module
E-mail function, programmable controller CPU status monitoring function,
Q Corresponding Ethernet Interface Module
communication via MELSECNET/H or MELSECNET/10, communication
User's Manual (Application)
using the data link instructions, and file transfer function (FTP server) of the
< SH-080010 (13JL89) >
Ethernet module
CC-Link System Master/Local Module User's
Manual
< SH-080394E (13JR64) >

System configuration, performance specifications, functions, handling,
wiring, and troubleshooting of the QJ61BT11N

Overview, system configuration, specifications, procedures before
operation, basic data communication method with external devices,
maintenance and inspection, and troubleshooting for using the serial
< SH-080006 (13JL86) >
communication module
Q Corresponding Serial Communication
Special functions (specifications, usage, and settings and data
Module User's Manual (Application)
communication method with external devices of the serial communication
Q Corresponding Serial Communication
Module User's Manual (Basic)

< SH-080007 (13JL87) > module

Q Corresponding MELSEC Communication
Protocol Reference Manual

Communication method using the MC protocol, which reads/writes data to/
from the CPU module via the serial communication module or Ethernet
< SH-080008 (13JF89) > module
GX Developer Version 8 Operating Manual
Operating methods of GX Developer, such as programming and printout
< SH-080373E (13JU41) >

A - 19

MANUAL PAGE ORGANIZATION

Note (icon)

Reference

Chapter

The detailed explanation of "Note . " is
provided under the corresponding
"Note . " at the bottom of the page.

The section in this manual or
another relevant manual that can
be referred to is shown with
.

The chapter of the current page can be
easily identified by this indication on the
right side.

Note (detailed explanation)

Section title

The detailed note corresponding to each icon
is described.

The section number and title of the current
page can be easily identified.

* cining page components, and differs from an actual page.
Icons

Description

Universal model QCPU
Universal

Icons indicate that specifications described on the page
contain some precautions.

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 - 20

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

CPU module type
CPU module

Generic term for the Universal model QCPU

Universal model QCPU

Generic term for the Q00UJCPU, Q00UCPU, Q01UCPU, Q02UCPU,
Q03UDCPU, Q04UDHCPU, Q06UDHCPU, Q10UDHCPU, Q13UDHCPU,
Q20UDHCPU, Q26UDHCPU, Q03UDECPU, Q04UDEHCPU, Q06UDEHCPU,
Q10UDEHCPU, Q13UDEHCPU, Q20UDEHCPU, and Q26UDEHCPU

Built-in Ethernet port QCPU

Generic term for the Q03UDECPU, Q04UDEHCPU, Q06UDEHCPU,
Q10UDEHCPU, Q13UDEHCPU, Q20UDEHCPU, and Q26UDEHCPU

Motion CPU

Generic term for Mitsubishi motion controllers, Q172CPUN, Q173CPUN,
Q172HCPU, Q173HCPU, Q172CPUN-T, Q173CPUN-T, Q172HCPU-T,
Q173HCPU-T, Q172DCPU, and Q173DCPU

PC CPU module

Generic term for MELSEC-Q series PC CPU module, PPC-CPU852(MS)-512,
manufactured by CONTEC Co., Ltd.

C Controller module

Generic term for the Q06CCPU-V-H01, Q06CCPU-V, Q06CCPU-V-B, and
Q12DCCPU-V C Controller modules

CPU module model
QnUD(H)CPU

Generic term for the Q03UDCPU, Q04UDHCPU, Q06UDHCPU, Q10UDHCPU,
Q13UDHCPU, Q20UDHCPU, and Q26UDHCPU

Base unit type
Base unit

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, and
multiple CPU high speed main base unit

Main base unit

Generic term for the Q3

B, Q3 SB, Q3

Extension base unit

Generic term for the Q5

B, Q6 B, and Q6 RB

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
unit

Another name for the Q6 RB

Multiple CPU high speed main base
unit

Another name for the Q3 DB

RB, and Q3

Base unit model
Q3

Generic term for the Q33B, Q35B, Q38B, and Q312B main base units

Generic term for the Q32SB, Q33SB, and Q35SB slim type main base units

Another name for the Q38RB main base unit for redundant power supply system

Generic term for the Q38DB and Q312DB multiple CPU high speed main base
units

Generic term for the Q52B and Q55B extension base units

Generic term for the Q63B, Q65B, Q68B, and Q612B extension base units

Another name for the Q68RB extension base unit for redundant power supply
system

A - 21

Generic term/abbreviation

Description

Power supply module
Power supply module

Generic term for the Q series power supply module, slim type power supply
module, and redundant power supply module

Q series power supply module

Generic term for the Q61P-A1, Q61P-A2, Q61P, Q61P-D, Q62P, Q63P, Q64P, and
Q64PN 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 power supply modules for redundant
power supply

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

SRAM card

Generic term for the Q2MEM-1MBS, Q2MEM-2MBS, Q3MEM-4MBS, and
Q3MEM-8MBS SRAM cards

Flash card

Generic term for the Q2MEM-2MBF and Q2MEM-4MBF Flash cards

ATA card

Generic term for the Q2MEM-8MBA, Q2MEM-16MBA, and Q2MEM-32MBA ATA
cards

Others
GX Developer

Product name for SW D5C-GPPW-E GPP function software package compatible
with the Q series

Extension cable

Generic term for the QC05B, QC06B, QC12B, QC30B, QC50B, and QC100B
extension cables

Battery

Generic term for the Q6BAT, Q7BAT, and Q8BAT CPU module batteries,
Q2MEM-BAT SRAM card battery, and Q3MEM-BAT SRAM card battery

GOT

Generic term for Mitsubishi Graphic Operation Terminal, GOT-A*** series, GOT-F***
series, and GOT1000 series

A - 22

CHAPTER1 OVERVIEW

The CPU module performs sequence control by executing programs.
This chapter describes the processing order in the CPU module, locations where the created programs are stored, and

devices and instructions useful for programming.

3
1.1 Processing Order in the CPU Module

The CPU module performs processing in the following order.

Scan time

Power-on or reset

Initial processing

Refresh processing with
input/output modules

Program operation processing

END processing

(1) Initial processing (

Section 3.1)

The CPU module performs preprocessing required for program operations.
The preprocessing is performed only once when the module is powered on or reset.

(2) Refresh processing with input and output modules (

Section 3.2)

The CPU module takes on/off data from the input module or intelligent function module and outputs on/off data to
the output module or intelligent function module.

(3) Program operation processing (

Section 3.3)

The CPU module sequentially executes the program stored in the module from the step 0 to the END or FEND
instruction.

(4) END processing (

Section 3.4)

The CPU module performs refresh processing with network modules or communicates with external devices.

1-1

1.1 Processing Order in the CPU Module

Figure 1.1 Processing order in the CPU module

1.2 Storing and Executing Programs
This section describes where to store and how to execute the programs in the CPU module.

(1) Programming
Programs are created with GX Developer.
For details of program configuration and execution conditions, refer to CHAPTER 2.

(2) Storing programs
Created programs and set parameters are stored in the following memories of the CPU module.
(

Section 5.1)
• Program memory
• Standard ROM (parameters only)
• Memory card

(3) Executing programs
The CPU module executes the programs stored in the program memory.
CPU module
Program memory

The CPU module executes
the programs stored here.

Parameter
Program
Device comment
Initial device value

Comments are stored
separately from the program.

Figure 1.2 Executing programs

To execute the programs stored in a memory card, the programs need to be booted to the program memory
(

Section 5.1.8) when the CPU module is powered off and then on or reset.
The CPU module executes the programs
booted from a memory card to here.

Program
memory

Boot

Parameter

Program

Device
comment

Initial device
value

CPU module

Memory card

Figure 1.3 Executing programs stored in a memory card

1-2

CHAPTER1 OVERVIEW

1.3 Structured Programming

The programs to be executed in the CPU module can be structured in the following two ways.

• In one program
• By dividing into multiple files

3
(1) Structuring in one program
Structured programming is available by creating one program as a collection of three program sections: main
routine program (
(

Section 2.2.1), subroutine program (

Section 2.2.2), and interrupt program

Section 2.2.3).

5
Main routine
program

CALL P1

FEND

P1
Subroutine
program 1

Y10

RET

8
P8
Subroutine
program 2

Y11

RET
1.3 Structured Programming

Y12

Interrupt program
IRET
END

Figure 1.4 Structuring in one program

1-3

(2) Structuring by dividing into multiple files
A program is stored in a file.
Changing the file name allows the CPU module to store multiple programs.
Multiple programs can be stored
by changing the file name.
File name: PARAM File name: ABC File name: ABC File name: DEF
Parameter

Program

Device
comment

Program

GX Developer
CPU module
Figure 1.5 Structuring by dividing into multiple files

Dividing into multiple files according to the processes or functions enables simultaneous programming by two or
more designers. Managing the files separately eases reuse and utilization to other programs.
Structured programming is efficient in this way because only the corresponding file needs to be modified or
debugged in case of change in the specifications.

(a) Dividing into multiple files according to the processes*1

Program memory/memory card

Processing contents
are divided according
to the processes.

Carrying in

Program A

Manufacturing

Program B

Assembly

Program C

Carrying out

Program D

Program A to D will
be executed in the
specified order. *2

Figure 1.6 Dividing into multiple files according to the processes
*1: The processing contents divided according to the processes can further be divided and managed according to the
functions.
*2: The execution order can be set in the Program tab of the PLC parameter dialog box. (

1-4

Section 2.3(2)).

CHAPTER1 OVERVIEW

(b) Dividing into multiple files according to the functions

1
2

Program memory/memory card

Processing contents
are divided according
to the functions.

Initial processing

Program A

Main processing

Program B

Communication
processing

Program C

Error processing

Program D

The execution order and
conditions for program
A to D can be set. *1

4
5
6
7

Figure 1.7 Dividing into multiple files according to the functions
*1: The execution order and conditions can be set in the Program tab of the PLC parameter dialog box. (

Section 2.3(2)).

1.3 Structured Programming

1-5

1.4 Devices and Instructions Useful for Programming
The CPU module is provided with devices and instructions useful for programming.
This section describes the outline of these devices and instructions.

(1) Various ways of device specification
(a) Using each bit of a word device as a contact or coil
By specifying a bit of a word device, the bit can be used as a contact or coil.
A bit-specified word device (turns on
(switches to 1) the 5th bit (b5) of D0.)

X0
SET

D0.5

A bit-specified word device (turns on/off depending
on the on/off (1/0) status of the 5th bit (b5) of D0.)
D0.5
SET

Y10
Figure 1.8 Specifying a bit of a word device

(b) Easy direct processing in units of one point
Use of the direct access input (DX

) and direct access output (DY

of one point) in the program. (

Section 3.8.2)

) enables easy direct processing (in units

Direct access input
M0 DX10
DY100

On/off data is output to the
output module when the
instruction is executed.
On/off data is input from
the input module when the
instruction is executed.
Figure 1.9 Direct processing in units of one point

(c) No input pulse conversion required by using a differential contact
Pulse conversion processing for inputs is no longer required with the use of a differential contacts (
).
Differential contact
X0

X1
Y100

PLS
M0

Y100

X1
Y100

On at the rising
edge of X0

Y100

Figure 1.10 Use of a differential contact

1-6

and

CHAPTER1 OVERVIEW

(d) Direct access to the buffer memory of the intelligent function module

The buffer memory of the intelligent function module can be used as a device area in a program.
(

Section 9.5.1)

X0
+P

U4\G12

Output module (16 points)

Q62AD (16 points)
Output module (16 points)

Q64AD (16 points)
Q64AD (16 points)

Input module (16 points)

CPU module

Power supply module

The CPU module can read the
data in the buffer memory
address 12 of the Q64AD.

*1:U4\G12
Specifying the buffer
memory address
Specifying the I/O number of
the intelligent function module

I/O number: X/Y40 to X/Y4F

Figure 1.11 Direct access to the buffer memory of the intelligent function module

(e) Direct access to the link devices
The link devices (LX, LY, LB, LW, SB, or SW) in network modules can be directly accessed without
the refresh setting. (

Section 9.4)

8
J5\W12

M0
+P J5\W12 D0

1.4 Devices and Instructions Useful for Programming

Specifying the
link register
Specifying the
network number

Power supply module
CPU module
QJ71LP21-25
Input module (16 points)
Input module (16 points)
Q68AD (16 points)
Q68AD (16 points)
Q62AD (16 points)
Output module (16 points)
Output module (16 points)

The CPU module can directly read the data in the
link register (LW12) of the number 5 network module.

Network number 5
Figure 1.12 Direct access to the link devices

1-7

(2) Structural description of programs
Use of the index register and edge relay enables easy structured programming including the pulse conversion
processing. (

Section 9.2.6)
X0
FOR

PLS M0

X10 X11
X0Z0 X1Z0 V0Z1
Y8Z2

PLS M10

M10
Y18

Multiple number (n) of
similar programs can
be executed by one
description.

X170 X171

PLS M170

M170
Y178

Figure 1.13 Structured programming including the pulse conversion processing

(3) Easy data processing
(a) Using real numbers and character string constants without conversion
Real numbers (floating-point data) and character string constants can be used without conversion for
programming.
Real number
data

X0
E+P

E1.23

Real number
data

E4.68

Character
string data

"CPU" D10

Character string data link instruction

R0
E3.45

E1.23

Real number addition instruction

$+P

Real number
data

D5 "0"

"Q"

D6 NULL
*1

"2"

R1
Character
string data
"CPU"

Character
string data
D10 "0"
D11 "C"

"Q"

"2"
D12 "U"
"P"
D13 NULL *1

Figure 1.14 Using real numbers and character string constants
*1: The NULL character represents "00H" (end of character strings).

(b) High-speed processing of bulk data
Extension of the data table operation instructions, such as the data table processing instruction, allows highspeed processing of bulk data.
X0
FINSP D0
Device
where the
data is
currently
stored

FIF0 table

Device Insertion
where position
the data
is to be
stored

Instruction for inserting data
to the table

R4
Figure 1.15 Data processing with the table processing instruction

1-8

FIF0 table

CHAPTER1 OVERVIEW

(4) Flexible management of subroutine programs
(a) Subroutine program sharing

The number of steps in a program can be reduced by sharing subroutine programs.
In addition, creating and managing programs become easier.
Subroutine programs can be created within the same program and called. Subroutine programs in other

programs can also be called by using the common pointer.

Program C
Program A

Common pointer

M0
0

Subroutine program
SM400 M0

Calling P1000
P1000

CALLP P1000

MOV K4X0
Always
on

M0
MOV K4X20 R0

Program B
RET
Calling P1000

M10
0

CALLP P1000

Figure 1.16 Subroutine program sharing

1.4 Devices and Instructions Useful for Programming

1-9

(b) Subroutine call instruction with argument passing
Subroutine program that is called more than one time can be created easily.

Main routine program
Argument specification
M0
CALLP P0
W0 K4X0 R0
Argument from FD2 *1
Argument to FD1
Argument to FD0
Subroutine program
specification
Argument specification
M10
CALLP P0

100

W10 K4X10 R10
Argument from FD2 *1
Argument to FD1
Argument to FD0
FEND

Subroutine program
Destination data
Source data
SM400 M0
P0
Always
on

MOV FD0

FD2

MOV FD1

FD2

RET

END
Figure 1.17 Calling subroutine program with argument passing
*1: For input and output conditions for an argument, refer to Section 9.3.1.

1 - 10

CHAPTER1 OVERVIEW

1.5 Features

This section describes the features specific to the Universal model QCPU.

(1) High-speed processing more than ever
The processing time required for the basic instructions, floating-point operations, and accesses to the file register
becomes shorter than the existing Q series CPU modules.
Use of a standard device register (Z)

achieves high-speed processing between register operations (transfer

instruction).

*1: An index register used between register operations is designated as a standard device register.(

Section 9.6.2)

(2) Large-capacity file register
The file register whose capacity is 640K points at maximum (4086K points at maximum when a memory card is
used)*2 can be set inside the CPU module.

*2: For the Q26UDHCPU and Q26UDEHCPU only

(3) Use of double-precision floating-point operation instructions
The double-precision floating-point operation instructions (64-bit instructions) are available as well as the existing
single-precision floating-point operation instructions. (

Section 2.4.4)

This enables more accurate analog control and positioning control.

(4) Using the file register area as the data register and link register
(W). (

Section 9.8)

Programming using the extended data register (D) or extended link register (W) whose capacity is 640K points at
maximum (4086K points at maximum when a memory card is used)*4 is available in addition to the internal user
device.
*3: Extended areas of the data register (D) and link register (W) are called the extended data register (D) and extended link
register (W), respectively.
*4: For the Q26UDHCPU and Q26UDEHCPU only

W0.0
MOV D0 W200
Internal user devices
are used.
SET W100.0
W10000.0 B80
MOV D30000 W10200

SET W10100.0

The extended data
register (D) and
extended link register
(W) are used.

GX Developer

Figure 1.18 Extended data register (D) and extended link register (W)

1 - 11

1.5 Features

The file register (ZR) area can be used as an pseudo extended area*3 of the data register (D) and link register

(5) 32-bit index modification
Since the index modification range is expanded to 32 bits, index modification for the entire file register areas is
possible. (

Section 9.6.1)

File register in the serial
number access method
ZR0
ZR1

ZR32767
ZR32768

Applicable range of index modification
for the Universal model QCPU

Applicable range
of existing index
modification

SM400
DMOV K1042431

MOV

ZR0Z0

Use the index register (Z) when indexing the
file register (ZR) in the serial number access
method by 32 bits.

ZR1042431

Figure 1.19 32-bit index modification

(6) Communication via the built-in Ethernet port of the CPU module
The Built-in Ethernet port QCPU can communicate with MELSOFT, GOT, and external devices using the built-in
Ethernet port of the module.
QnUCPU User's Manual (Communication via Built-in Ethernet Port)

(7) Communication with the personal computer and HMI by the serial
communication function (
Section 6.23)
The Q00UJCPU, Q00UCPU, Q01UCPU, and Q02UCPU can communicate using the MELSEC communication
protocol (hereafter, MC protocol) by connecting a RS-232 interface and personal computer or HMI.
RS-232 cable
Personal computer or HMI

Communication using the MC protocol
Figure 1.20 Communication with the personal computer or HMI

The CPU module functions are added at the update of serial number of CPU module or GX Developer version.
For functions added by the update, refer to Appendix 2.

1 - 12

CHAPTER1 OVERVIEW

1.6 Checking Serial Number and Function Version

The serial number and function version of the CPU module can be checked on the rating plate, on the front of the

module, and on the System monitor screen in GX Developer.

(1) Checking on the rating plate

The rating plate is located on the side of the CPU module.

4
Serial number (first five digits)
Function version

Relevant regulation
standards

Figure 1.21 Rating plate

7
(2) Checking on the front of the module
The serial number on the rating plate is printed on the front (at the bottom) of the module. This applies only to the
CPU module manufactured in mid-September, 2007 or later.

Q03UDCPU

1.6 Checking Serial Number and Function Version

MODE
RUN
ERR.
USER
BAT.
BOOT

PULL

USB

RS-232

Serial number
Figure 1.22 Front of the module

1 - 13

(3) Checking on the System monitor (Product Information List) screen
To open 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 same screen, the serial number and function version of intelligent function modules can also be checked.
Serial
number

Function
version

Product
number

Figure 1.23 System monitor (Product Information List) screen

[Serial number, function version, and product number]
• The serial number of the module is displayed in the "Serial No." column.
• The function version of the module is displayed in the "Ver." column.
• The serial number (product number) printed on the rating plate of the module is displayed in the "Product
No." column.
Note that "-" is displayed for the module that does not support the product number display.

The serial number displayed on the Product Information List screen of GX Developer may differ from that on the rating plate
and on the front of the module.
• The serial number on the rating plate and on the front of the module indicates the management information of the
product.
• The serial number displayed on the Product Information List screen indicates the functional information of the
product.
The functional information of the product will be updated when a function is added.

1 - 14

CHAPTER2 SEQUENCE PROGRAMS

2.1 Sequence Program Overview

(1) Definition

Sequence program is one of the programs that can be executed in the CPU module.
A sequence program consists of instructions, such as sequence instructions, basic instruction, and
application instruction.

4
Sequence instruction

K100
T0

T0
Y30

Basic instruction

X1
BIN

K4X10

D0
Application instruction

X41
FROM

D10

Figure 2.1 Sequence program

8
Remark
2.1 Sequence Program Overview

For the instructions used in sequence programs, refer to the following.
QCPU Programming Manual (Common Instructions)

2-1

(2) Programming method
There are two programming modes for sequence programs.
• Ladder mode
• List mode

(a) Ladder mode
Ladder mode is a mode based on the concept of sequential control by relay circuits.
A program in ladder mode is similar to a schematic for a set of relay circuits. Programming in units
of ladder blocks is available.
A ladder block, which starts from the left rail and ends at the right rail, is the minimum unit for
operating sequence programs.
N/O
contact

Left rail
0
Step number 2

N/C
contact

Right rail

X0
X1

Coil (output)
Y20

Y21
Y22

Ladder block

Y23
8

Y24

* X0 to X5: Input, Y20 to Y24: Output
Figure 2.2 Ladder mode

(b) List mode
List mode uses dedicated instructions for programming. The symbols, such as contacts and coils,
used in ladder mode are replaced with dedicated instructions.
The following instructions are used for normally open contacts, normally closed contacts, and coils.
• Normally open contact ••• LD, AND, OR
• Normally closed contact ••• LDI, ANI, ORI
• Coil ••• OUT

Remark
There are two other types of programs that can be executed in the CPU module: SFC programs and ST
programs.
For details, refer to the following.
QCPU (Q Mode)/QnACPU Programming Manual (SFC)
QCPU (Q Mode) Programming Manual (MELSAP-L)
QCPU (Q Mode) Programming Manual (Structured Text)

2-2

CHAPTER2 SEQUENCE PROGRAMS

(3) Sequence program operation
A sequence program is sequentially operated from the step 0 to the END or FEND instruction.
In ladder mode, a sequence program is operated from left to right and top to bottom in a ladder block.
[Ladder mode]
From left to right
1) 2) 7) 8) 9)
X0 X1 X5 X6 X7
0
3) 4)
X2 X3
From top
5)
to bottom
6)
X4

[List mode]

10)
Y10

11)
10

END

0 LD
1 AND
2 LD
3 AND
Program
4 ORB
operations are
5 OR
sequentially
6 AND
executed from
7 AND
the step 0 to the
8 AND
END instruction. 9 OUT
10 END

* Program operations are executed in the
order of 1) to 11).

X0
X1
X2
X3
X4
X5
X6
X7
Y10

0)
1)
2)
3)
4)
5)
6)
7)
8)
9)
10)
11)

3
4
5

Step number

Figure 2.3 Comparison between ladder mode and list mode

2.2 Sequence Program Configuration

Sequence programs are classified into the following three types.

• Main routine program
• Subroutine program
• Interrupt program

2.2 Sequence Program Configuration

File A

Main routine
program
FEND
P0

Subroutine
program
RET

Interrupt
program
IRET
END

Figure 2.4 Sequence program classification

2-3

2.2.1 Main routine program
(1) Definition
Main routine program is an entire program from the step 0 to the END or FEND instruction.

(2) Program operation
A main routine program executes its operations from the step 0 to the END or FEND instruction and
then performs END processing.
After the END processing, the program restarts its operations from the step 0.
Step 0
Indicates execution of
the program.
Main routine
program
The program operation
returns to the step 0.
END/FEND

END/FEND
END
processing

Figure 2.5 Main routine program

When multiple programs are executed, the main routine program operation after execution of the END or
FEND instruction varies depending on the preset execution conditions. (
Section 2.3.1)

Remark
For details of the END and FEND instructions, refer to the following.
QCPU Programming Manual (Common Instructions)

2-4

CHAPTER2 SEQUENCE PROGRAMS

2.2.2 Subroutine program

(1) Definition
Subroutine program is a program from a pointer (P ) to the RET instruction.
This program is executed only when it is called by a subroutine program call instruction (such as
CALL(P), FCALL(P)) from a main routine program.

2
3

(2) Application
• Programming a program which is executed two or more times in one scan as a subroutine

program can reduce the number of steps in the entire program.
• Programming a program which is executed only when a certain condition is satisfied as a
subroutine program can shorten the scan time.

(3) Programming of subroutine programs
Create subroutine programs between the FEND and END instructions in the main routine program.

Program A
Main routine
program

7
FEND

Y10
RET

Subroutine
program

Y11

2.2 Sequence Program Configuration
2.2.2 Subroutine program

RET

Y12
RET

END

pointer*1

Figure 2.6 Programming location of subroutine programs
*1: The pointer numbers do not need to be specified in asending order.

Subroutine programs can be managed as one separate program (stand-by type program).
(
Section 2.2.3)

Remark
Subroutine programs can be configured with the nesting.(

Section 9.9)

2-5

2.2.3 Interrupt program
(1) Definition
Interrupt program is a program from an interrupt pointer (I ) to the IRET instruction.
EI

Main routine
program
Indicates the end
of the main routine
program.

FEND
I0

Interrupt
program (I0)

IRET
I29
Interrupt
program (I29)

IRET
END
Interrupt pointer
Figure 2.7 Interrupt program

The interrupt pointer (I ) number varies depending on the interrupt factor. (

Section 9.11)

When an interrupt factor occurs, the interrupt program of the interrupt pointer number corresponding
to that factor is executed. (Interrupt programs are executed only when the corresponding interrupt
factor occurs.)
Occurrence of the
interrupt factor for I0
Main routine
program

Interrupt
program (I0)

Execution

Occurrence of the
interrupt factor for I29

Execution

Execution
IRET

Interrupt
program (I29)

Execution
IRET
Figure 2.8 Interrupt program execution timing

2-6

Time

CHAPTER2 SEQUENCE PROGRAMS

1
Only one interrupt program can be created with one interrupt pointer number.
EI

FEND

I0
IRET

Interrupt
program (I0)

IRET

Interrupt
program (I29)

I29

4
5

END

Remark
For details of the interrupt factors and interrupt pointers, refer to Section 9.11.

(2) Programming of interrupt programs
Create interrupt programs between the FEND and END instructions in the main routine program.

Program A

2.2 Sequence Program Configuration
2.2.3 Interrupt program

Main routine
program

FEN
I0

Y10
IRET

Interrupt
program

I32

Y11
IRET

I28

Y12
IRET
END
Interrupt pointer*1

Figure 2.9 Programming location of interrupt programs
*1: The pointer numbers do not need to be specified in ascending order.

Interrupt programs can be managed as one separate program (stand-by type program). (

Section 2.3.3)

2-7

(a) Before executing an interrupt program
Before executing the interrupt programs of the interrupt pointers I0 to I15, I28 to I31, I45, and I50 to
I255, enable interrupts with the EI instruction.

Remark
For details of the EI instruction, refer to the following.
QCPU Programming Manual (Common Instructions)

(b) Restrictions on programming
1) PLS and PLF instructions
The PLS and PLF instructions perform off processing in the next scan of which the instruction is
executed.
Therefore, the device which is turned on by the instruction remains on until the same instruction is
reexecuted.
X0

X0
PLS M0

END 0

IO IRET END 0

PLS M0

END 0 IO IRET END 0

ON
X0

OFF
ON

OFF
M0

Turns off by executing the
PLS M0 instruction.
Turns on by executing the PLS M0 instruction at the rise of X0.

Figure 2.10 Device turned on by the PLS instruction in the interrupt program

2) EI and DI instructions
During execution of an interrupt program, interrupts are disabled (DI) so that any other interrupt
processing will not be executed.
Do not execute the EI or DI instruction during interrupt program execution.

3) Timer (T) and counter (C)
Do not use the timer (T) and counter (C) in interrupt programs.
If more than one interrupts occur in one scan, the timer (T) and counter (C) in the interrupt
program cannot measure the time correctly.
The OUT C

instruction status causes the counter (C) measure the number of interrupts

incorrectly.

4) Instructions not available in interrupt programs
Refer to sections corresponding to each instruction in the following.
QCPU Programming Manual (Common Instructions)

2-8

CHAPTER2 SEQUENCE PROGRAMS

(3) Operation when an interrupt factor occurs
There are restrictions on interrupt programs depending on the interrupt factor occurrence timing.
(a) When an interrupt factor occurs before the interrupt program execution status is enabled

The CPU module stores the interrupt factor occurred.
As soon as the interrupt program execution status is enabled, the CPU module executes the

interrupt program corresponding to the stored interrupt factor.
Interrupt factor
occurrence

Interrupt
enabled (EI)

Main routine
program

Interrupt
program

Execution
Not executed because
the interrupt program
execution status is
disabled (DI).

Executed as soon as
the interrupt program
execution status
changes to enabled.

Figure 2.11 When an interrupt factor occurs before interrupts are enabled

When the same interrupt factor occurs more than one time before the interrupt program execution
status is enabled, the interrupt factors of I0 to I15, I28 to I31, I45, I50 to I255, and fixed scan

execution type programs are stored only once.
Note that all interrupt factors occurred are discarded if they are masked by the IMASK instruction.

Remark

(b) When an interrupt factor occurs in the STOP or PAUSE status
The CPU module executes the interrupt program as soon as the interrupt program execution status is enabled
after the CPU module status is changed to RUN.
Interrupt factor
occurrence

STOP/PAUSE
RUN
Interrupt
enabled (EI)

Main routine
program
Execution

Interrupt
program
Not executed because
the CPU module is in
the STOP status.

Executed as soon as the interrupt
program execution status changes
to enabled after the CPU module
status is changed from
STOP/PAUSE to RUN.

Figure 2.12 When an interrupt factor occurs in the STOP or PAUSE status

2-9

2.2 Sequence Program Configuration
2.2.3 Interrupt program

For details of the IMASK instruction, refer to the following.
QCPU Programming Manual (Common Instructions)

(c) When multiple interrupt factors occur simultaneously in the interrupt program execution
enabled status
The interrupt programs are executed in the order of interrupt pointers (I ) with high priority.
(

Section 9.11.1)

Other interrupt programs have to wait until processing of the interrupt program being executed is
completed.
Interrupt
enabled (EI)
Main routine
program

High

Interrupt
program (I50)

Simultaneous occurrence of
multiple interrupt factors
I50 I100
I150
Execution

Priority

IRET

Low

Interrupt
program (I100)

Execution
Wait to be
processed

IRET
Execution

Interrupt
program (I150)
Wait to be processed

IRET

Figure 2.13 When multiple interrupt factors occur simultaneously

(d) When the same interrupt factor as that of the interrupt program being executed occurs
When the same interrupt factor as that of the interrupt program being executed occurs more than
one time before completion of interrupt program processing, the interrupt factors of I0 to I15, I45,
and I50 to I255 are stored only once, and then the interrupt program corresponding to each stored
interrupt factor is executed after completion of current interrupt program execution.
The interrupt factors of I28 to I31 and fixed scan execution type programs are all stored, and then all
the interrupt programs corresponding to interrupt factors are executed after completion of current
interrupt program execution.

2 - 10

CHAPTER2 SEQUENCE PROGRAMS

(e) When an interrupt factor occurs during link refresh

The link refresh is suspended and an interrupt program is executed.
Even if the Block data assurance per station setting is enabled in the CC-Link IE controller network
or MELSECNET/H network, this setting does not work when a device set as a refresh target is used
in the interrupt program.
In the interrupt program, do not use any refresh target device.
10ms

10ms

2
3

10ms

4
Interrupt factor
Interrupt program
execution

Link refresh execution

6
Link refresh is suspended and
interrupt program is executed.

Figure 2.14 When an interrupt factor occurs during link refresh

Remark
For the Block data assurance per station setting, refer to the following.
Reference manual for each network module

When the constant scan function is used and an interrupt factor occurs during the waiting time in
END processing, an interrupt program corresponding to the interrupt factor is executed.
(g) When an interrupt factor occurs during access to another module
When an interrupt factor occurs during access to another module (during service processing or instruction
processing), the interrupt program becomes standby status until the service processing or the instruction in
execution is completed.
To shorten the wait time of the interrupt, reduce the amount of data that access to other modules.

2 - 11

2.2 Sequence Program Configuration
2.2.3 Interrupt program

(f) Interrupt during END processing

(4) Processing at program execution type change
When the program execution type is changed from the scan execution type to the interrupt, the CPU
module saves and restores the following data. (

Section 9.6.3)

• Data in the index register
• File register block number
Whether to save and restore the data above can be set in the PLC parameter dialog box.
If the data is not saved or restored, the overhead time of the corresponding interrupt program can be shortened.
(

Section 10.1.2)

(5) Restrictions
(a) When the same device is used
During execution of an instruction in a main routine program, an interrupt program may be
executed, suspending the processing of the instruction being executed.
If the same device is used for the main routine program and interrupt program, device data may
become inconsistent. In this case, take the following measures to prevent device data
inconsistency.
1) Moving device data to another device
Do not directly specify the device where the data is written by the interrupt program in the main
routine program. Use the data in another device by moving the data with the transfer instruction.
2) Disabling interrupts with the DI instruction
Disable interrupts with the DI instruction if instructions that may cause inconvenience for the main
routine program are used.
However, interrupts do not occur during access to the device of the corresponding argument of the
instruction. For this reason, data inconsistency will not occur in units of arguments.

2 - 12

CHAPTER2 SEQUENCE PROGRAMS

2.3 Settings When Program is Divided

When one sequence program is divided into multiple programs, execution conditions, such as executing a
program only once at start-up or executing a program at fixed intervals, can be set for each program.

(1) Control by multiple programs dividing one program

The CPU module can store multiple programs divided on the basis of each control unit.
This enables programming of one sequence program by two or more designers.
Control by one program

Program A
Control data A

Control data A

5
Control data B

Divide one program
into multiple
programs.

Program B
The programs divided on
the basis of each control
data are registered.

Control data B

6
7

Program C
Control data C

Control data C

Figure 2.15 Control by multiple programs

To execute multiple programs in the CPU module, names (file names) and execution conditions of the
programs must be set.
Set them in the Program tab of the PLC parameter dialog box.
(a)

(b)

(b) 4)

Programs are executed
according to the setting
order.

2 - 13

2.3 Settings When Program is Divided

(2) Settings required for execution of multiple programs

(a) Program name
Enter the name (file name) of the program to be executed in the CPU module.

(b) Execute type
Select an execution type of the program set under "Program name".
The CPU module executes programs whose execution type has been set here according to the
setting order.
1) Initial execution type ("Initial")
This program is executed only once when the CPU module is powered on or its status is switched
from STOP to RUN. (

Section 2.3.1)

2) Scan execution type ("Scan")
This program is executed once in every scan, starting in the next scan of which the initial
execution type program is executed and later. (

Section 2.3.2)

3) Stand-by type ("Wait")
This program is executed only when its execution is requested. (

Section 2.3.3)

4) Fixed scan execution type ("Fixed scan")
This program is executed at time intervals specified with fixed scan interval and unit.
(

Section 2.3.4)

• Fixed scan interval ("Fixed scan interval")
Enter the execution interval of fixed scan execution type program.
The setting range varies depending on the setting unit.
•When the unit is "ms" : 0.5 to 999.5ms (in increments of 0.5ms)
•When the unit is "s" : 1 to 60s (in increments of 1s)

• Unit ("In unit")
Select the unit ("ms" or "s") of the fixed scan interval.

2 - 14

CHAPTER2 SEQUENCE PROGRAMS

Note2.1Note1

For each program, determine whether to use the file specified for the local device in the PLC file tab
of the PLC parameter dialog box.

2
3
4
5

Figure 2.17 File usability setting

The default is set to "Use PLC file setting".
When "Not used" is selected, data in the local device is not saved or restored when the program
execution type is changed.

7
8

2.3 Settings When Program is Divided

Note1

Note2.1

Universal

The Q00UJCPU does not support the file usability setting.
When using the file usability setting for the Q02UCPU, Q03UDCPU, Q04UDHCPU, Q06UDHCPU, Q13UDHCPU, or
Q26UDHCPU, check the versions of the CPU module and GX Developer. (

Appendix 2)

2 - 15

(3) Program sequence in the CPU module
Figure 2.18 shows the program sequence after the CPU module is powered on or its operating status is changed
from STOP to RUN.
Powered off

on/STOP

RUN

Executed only once when
the CPU module is powered
on or its status is switched
from STOP to RUN.

Initial execution
type program

END processing

Scan execution
type program

Fixed scan
execution type
program

Stand-by
type program

Executed at specified
time intervals.

Executed only when its
execution is requested.

Program execution sequence
Program execution when any
subroutine program or interrupt
program is called
Figure 2.18 Program sequence

Use initial execution type program, stand-by type program, and fixed scan execution type program as required.

2 - 16

CHAPTER2 SEQUENCE PROGRAMS

2.3.1 Initial execution type program

(1) Definition
Initial execution type program is executed only once when the CPU module is powered on or its
operating status is changed from STOP to RUN.

This type of program can be used as a program that need not be executed from the next scan and

later once it is executed, like initial processing to an intelligent function module.
Control by one program
Processing performed
only once

When an initial execution type program is used
Program A

One program can
be divided into two
programs.

Program B
Processing performed
in every scan

Initial execution type
program

Scan execution type
program

Figure 2.19 When processing performed only once is separated as an initial execution type program

(2) Processing
(a) Execution order
After completion of all the initial execution type program execution, END processing is performed.

In the next scan and later, scan execution type programs are executed.

2.3 Settings When Program is Divided
2.3.1 Initial execution type program

Powered off on/
STOP RUN

Initial execution
type program A
Initial execution
type program B

1 scan

If there are multiple initial
execution type programs, the
CPU module executes them in
ascending order of the setting.

Initial execution
type program n

END processing

Scan execution type
program
Figure 2.20 Execution order of the initial execution type programs

2 - 17

(b) Initial scan time
Initial scan time is the execution time of initial execution type program.
When multiple programs are executed, the initial scan time will be the time required for completing
all the initial execution type program execution.
1) Initial scan time storage location
The CPU module measures the initial scan time and stores it into the special register (SD522 and
SD523).
The initial scan time can be checked by monitoring SD522 and SD523.
SD522

SD523
Stores the initial scan time of 1ms or less (unit: s).
Stores the initial scan time. (unit: ms).
Figure 2.21 Initial scan time storage location

Example If the stored values in SD522 and SD523 are 3 and 400 respectively, the initial scan
time is 3.4ms.

2) Accuracy and measurement of the initial scan time
Accuracy of the initial scan time stored in the special register is

0.1ms.

Even if the WDT instruction (instruction that resets the watchdog timer) is executed in the
sequence program, the measurement of the initial scan time continues.
3) Execution of an interrupt program or fixed scan execution type program
When an interrupt program or fixed scan execution type program is executed before completion of
the initial execution type program execution, the execution time of the executed program will be
added to the initial scan time.

(3) Precautions on programming
Initial execution type programs do not support the instructions that require several scans (instructions
with completion device).

Example SEND, RECV, and similar instructions

2 - 18

CHAPTER2 SEQUENCE PROGRAMS

(4) Initial execution monitoring time setting
Initial execution monitoring time is a timer for monitoring initial scan time.
Set a time value in the PLC RAS tab of the PLC parameter dialog box.

The setting range is 10 to 2000ms (in increments of 10ms).
No default value is set.

3
4
5
Figure 2.22 PLC RAS setting (Initial execution monitoring time)

(a) When the initial scan time exceeds the preset initial execution monitoring time

"WDT ERROR" occurs and the CPU module stops program operations.
Set a time value so that the initial execution monitoring time becomes longer than actual initial scan
time.

7
8

2 - 19

2.3 Settings When Program is Divided
2.3.1 Initial execution type program

An error of the measurement value is 10ms for the initial execution monitoring time setting.
If the initial execution monitoring time (t) parameter is set to 10ms, "WDT ERROR" occurs when actual initial
scan time is within the range of 10ms < t < 20ms.

2.3.2 Scan execution type program
(1) Definition
Scan execution type program is executed once in every scan, starting in the next scan of which the
initial execution type program is executed and later.
STOP
Power supply ON

RUN
RUN
1st scan

2nd scan

3rd scan

4th scan

END processing
Initial execution type program
0

END

Scan execution type program A
0

END

Scan execution type program B
0

END

Scan execution type program C
Scan time
Figure 2.23 Execution order of the scan execution type programs

(2) Processing
When multiple scan execution type programs are executed, the scan time will be the time required for
completing all the scan execution type program execution.
If an interrupt program or fixed scan execution type program is executed, execution time of the
executed program will be added to the scan time.

2 - 20

CHAPTER2 SEQUENCE PROGRAMS

2.3.3 Stand-by type program

(1) Definition
Stand-by type program is executed only when its execution is requested.

This type of program can be changed to any desired execution type by a sequence program
instruction.

(2) Application
(a) Program library
Stand-by type program is used as a program library, a collection of subroutine programs and/or

interrupt programs, and managed separately from a main routine program.
Multiple subroutine programs and/or interrupt programs can be created and managed in a single
stand-by type program.
Scan execution type program

Scan execution type program

Main routine
program
P100

Subroutine
program
Interrupt
program

5
6

Main routine
program

Stand-by type program
P100

Subroutine
program

Interrupt
program

(b) Program type change
Stand-by type program is used to create and store programs available in all systems. Only required
programs will be executed.
For example, a program preset as a stand-by ("Wait") type program in the PLC parameter dialog
box can be changed to a scan execution type program and executed in the sequence program.

2 - 21

2.3 Settings When Program is Divided
2.3.3 Stand-by type program

Figure 2.24 Program library using a stand-by type program

(3) Execution method
Execute stand-by type programs in either of the following methods.
• Create subroutine and/or interrupt programs in a stand-by type program and call them using a
pointer or when an interrupt occurs.
• Change a stand-by type program to any other execution type using instructions.

(a) Creating subroutine and/or interrupt programs in a single stand-by type program
When creating subroutine and/or interrupt programs in a single stand-by type program, start the
program from the step 0.
The FEND instruction used in creation of a subroutine or interrupt program is not required after a
main routine program.
Program A
Main routine
program

Program B (Stand-by type program)

P500

Y10
RET

P508

Y11
RET

P501

Y12
RET

END
Use common pointer.

Figure 2.25 Creating subroutine programs in a single stand-by type program

2 - 22

CHAPTER2 SEQUENCE PROGRAMS

1) Executing a subroutine program and interrupt program in a stand-by type program
After execution of the stand-by type program, the CPU module reexecutes the program that called a program

in the stand-by type program.
Figure 2.26 shows the operation when the subroutine and interrupt programs in the stand-by type program
are executed.
CALL P100
instruction execution
END processing

Interrupt factor
occurrence
END processing

END processing

Main routine program

Subroutine program within
a stand-by type program

P100

RET

5
I0

IRET

Figure 2.26 Operation when the subroutine and interrupt programs in the stand-by type program are executed

• Subroutine program:

●

6
7

For restrictions on programming of subroutine and interrupt programs, refer to the following.

• Interrupt program:

3
4

Interrupt program within a
stand-by type program

●

Section 2.2.2

Section 2.3.2

Use common pointers. (
Section 9.10.2)
If local pointers are used, subroutine programs in a stand-by type program cannot be executed from any other program.
2.3 Settings When Program is Divided
2.3.3 Stand-by type program

2 - 23

(b) Changing the program execution type using instructions
Use the PSCAN, PSTOP, or POFF instruction to change a program execution type.

1) Changing the execution type (in the case of scan execution type program)
• Set the programs "ABC" and "GHI" as scan execution type programs and the program "DEF" as a standby type program.
• When the condition is established (the internal relay (M0) in Figure 2.27 turns on), the program "DEF" is
changed to a scan execution type program and the program "ABC" to a stand-by type program.
[Before execution of the PSCAN and PSTOP instructions]
Scan execution type program: ABC
• The PSCAN instruction changes the program "DEF" to
MO

a scan execution type program.

PSCAN "DEF"

• The PSTOP instruction changes the program "ABC" to
a stand-by type program.

PSTOP "ABC"

Stand-by type program: DEF

Scan execution type program: GHI

PSCAN "GHI"

PSCAN "ABC"

PSTOP

PSTOP "GHI"

"DEF"

When M0 turns on

[After execution of the PSCAN and PSTOP instructions]
Stand-by type program: ABC

MO
PSCAN

"DEF"

PSTOP

"ABC"

Scan execution type program: DEF

Scan execution type program: GHI

PSCAN "GHI"

PSCAN "ABC"

PSTOP "DEF"

PSTOP

"GHI"

Figure 2.27 Example of changing the execution type (in the case of scan execution type program)

2 - 24

CHAPTER2 SEQUENCE PROGRAMS

2) Execution type change timing

The program execution type is changed in END processing.
Therefore, the execution type will not be changed in the middle of program execution.
If different types are set to the same program in the same scan, the program will be changed to the type
specified by the last instruction executed.
END processing
Program name

"GHI"

"ABC"

END processing
"GHI"
PSTOP "ABC"
execution
PSCAN "DEF"
execution

"GHI" *1

END processing
"DEF" *1

"GHI"

"DEF" is changed to a scan execution type
program and "ABC" is changed to a stand-by
type program.

Figure 2.28 Execution type change timing
*1: The programs "GHI" and "DEF" are executed in the order set in the Program tab of the PLC parameter dialog box.

5
6

(4) Precautions on programming
(a) Unavailable devices
Unavailable devices depend on the program type (subroutine program or interrupt program) or the execution

type changed by an instruction.

(b) Use of local devices

For execution of a subroutine program using a local device, refer to Section 9.14.2.

2.3 Settings When Program is Divided
2.3.3 Stand-by type program

2 - 25

2.3.4 Fixed scan execution type program
(1) Definition
Fixed scan execution type program is a program executed at specified time intervals.
This type of programs, unlike interrupt programs, can be interrupted in units of files without interrupt
pointers or the IRET instruction.
For the restrictions on programming, refer to Section 2.2.3(2)(b).
(The restrictions on programming are the same as those for interrupt programs.)
Fixed scan interval

END processing

Condition
established

Scan execution
type program

Fixed scan execution
type program
Figure 2.29 Execution of a fixed scan execution type program

To execute a fixed scan execution type program, execute the EI instruction in the initial execution type program
or scan execution type program to enable interrupts.

2 - 26

CHAPTER2 SEQUENCE PROGRAMS

(2) Processing
(a) When two or more fixed scan execution type programs exist

Each fixed scan execution type program is executed at specified time intervals.
If two or more fixed scan execution type programs reach the specified time at the same timing,
programs will be executed in ascending order of the numbers set in the Program tab of the PLC
parameter dialog box.

(b) When both fixed scan execution type program and interrupt program exist
When a fixed scan execution type program and an interrupt program (I28 to I31) reach the specified
time at the same timing, the interrupt program will be given priority.

3
4
5

(c) When the execution condition is established during link refresh
The link refresh is suspended and a fixed scan execution type program is executed.
Even if the Block data assurance per station setting is enabled in the CC-Link IE controller network or

MELSECNET/H network, this setting does not work when a device set as a refresh target is used in the fixed
scan execution type program.

In the fixed scan execution type program, do not use any refresh target device.
10ms

10ms

Interrupt factor

Link refresh execution
Link refresh is suspended and fixed scan
execution type program is executed.
Figure 2.30 When the execution condition is established during link refresh

Remark
For the Block data assurance per station setting, refer to the following.
Reference manual for each network module

2 - 27

2.3 Settings When Program is Divided
2.3.4 Fixed scan execution type program

Fixed scan execution type
program execution

(d) When the execution condition is established during END processing
When the execution condition is established during the waiting time of the constant scan execution
or the END instruction, a fixed scan execution type program is executed.
Constant scan
*2

Fixed scan interval

END processing

Condition
established

Scan execution
type program

Fixed scan execution
type program
*1: Waiting time
*2: If processing is not completed within the
waiting time, the scan time increases.
Figure 2.31 When the execution condition is established during the waiting time

(3) Processing at program execution type change
For how to save and restore data in the index register when the program execution type is changed, refer to
Section 2.2.3(4). (The method is the same as that for interrupt programs.)

2 - 28

CHAPTER2 SEQUENCE PROGRAMS

(4) Precautions
(a) Execution interval of a fixed scan execution type program
Execution interval of a fixed scan execution type program may increase from the preset interval

depending on the time set for disabling interrupts by the DI instruction (interrupt disabled time).
If the interrupt disabled time by the DI instruction becomes too long, use an interrupt program by
fixed scan interrupt (I28 to I31) instead of a fixed scan execution type program.

Highest common factor of fixed scan execution interval *1 < Interrupt disabled time ••• Condition 1)

3
4

*1: This is the highest common factor of execution interval set to multiple fixed scan execution type programs

When the condition 1) is satisfied, the actual execution interval of a fixed scan execution type

program may increase from the preset interval by the time shown in the expression below.

6
Interrupt disabled time

Fixed scan execution interval set to
the corresponding program

Highst common factor of scan
execution interval

The following shows an example of the increase in execution time of a fixed scan execution type
program.

Example

• Fixed scan execution interval ••• 10ms, 5ms, 1ms, 0.5ms
• Highest common factor of fixed scan execution interval ••• 0.5ms
2.3 Settings When Program is Divided
2.3.4 Fixed scan execution type program

• Interrupt disabled time (DI) ••• 5ms

(Interrupt enabled time (EI) ••• less than 0.5ms)
With the settings above, the condition 1) will be 0.5ms < 5ms.
n+1 scan

n scan
DI

DI
END

Program execution
operation

Interrupt enabled/
disabled status

Disabled

Enabled

Less than 0.5ms

Interrupt disabled time = 5ms

END

Disabled

Enabled

Disabled

Less than 0.5ms

Interrupt disabled time = 5ms

Figure 2.32 Program execution and interrupt enabled/disabled status

The execution time of a fixed scan execution type program whose execution interval is set to 10ms
increases 100ms (5

0.5

10 = 100) at the most.

2 - 29

2.3.5 Changing the program execution type
(1) Changing the execution type using instructions
(a) Instructions used to change the execution type
The execution type of sequence programs can be changed using instructions even during
execution.
Use the PSCAN, PSTOP, or POFF instruction to change the execution type.
Initial execution
type program

PSTOP, POFF
instruction

PSCAN
instruction

PSTOP, POFF
instruction

Scan execution
type program

PSCAN
instruction

Fixed scan execution
type program

Stand-by type
program
PSTOP, POFF
instruction

Figure 2.33 Pattern of execution type change

Table2.1 Timing of execution type change
Instruction

Execution type before
change

PSCAN

PSTOP

Scan execution type

Remains unchanged.

Changes to the stand-by
type.

Initial execution type

Changes to the scan
execution type.

Changes to the stand-by
type.

Stand-by type

Changes to the scan
execution type.

Remains unchanged.

Fixed scan execution
type

Changes to the scan
execution type.

Changes to the stand-by
type.

POFF

Turns off outputs in the next scan.
Changes to the stand-by type in two
scans later.
Turns off outputs in the next scan.
Changes to the stand-by type in two
scans later.
No processing
Turns off outputs in the next scan.
Changes to the stand-by type in two
scans later.

Once the fixed scan execution type program is changed to another execution type, the type cannot be returned
to the fixed scan execution type.

2 - 30

CHAPTER2 SEQUENCE PROGRAMS

(b) Execution type change example
In a control program, a stand-by type program matching the preset condition is changed to a scan
execution type program in the course of program execution.

1
2

An unused scan execution type program can also be changed to a stand-by type program.
Figure 2.34 shows the case where the execution type of the stand-by type programs "ABC", "DEF",

"GHI", and "JKL" are changed in the control program.

Control program
M0

The PSCAN instruction
changes the program "ABC" to
a scan execution type program.

PSCAN "ABC"
When M0 turns on, the
program "ABC" is
changed from a stand-by
type to a scan execution
type program.

The PSTOP instruction changes
the program "ABC" to a standby type program.

PSTOP "ABC"

PSCAN "DEF"

When M1 turns on, the
program "ABC" is
changed from a scan
execution type to a
stand-by type program.

PSTOP "DEF"

7
Stand-by
type
program
:ABC

Stand-by
type
program
:DEF

Stand-by
type
program
:GHI

Stand-by
type
program
:JKL

2.3 Settings When Program is Divided
2.3.5 Changing the program execution type

Figure 2.34 Execution type change example

(2) Changing the execution type from the Program monitor list screen
The execution type of programs can be changed on the screen opened by selecting [Online]
[Monitor]

[Program monitor list]. (

Section 6.13.1)

2 - 31

2.4 Data Used in Sequence Programs
The CPU module represents numeric and alphabetic data using two symbols (states): 0 (off) and 1 (on).
Data represented using these two symbols is called binary number (BIN).
The CPU module can also use hexadecimal (HEX) (each hexadecimal digit represents four binary bits), binary-coded
decimal (BCD), or real numbers.
Table2.2 shows the numeric representations of BIN, HEX, BCD, and DEC (decimal).
Table2.2 Numeric representations of BIN, HEX,BCD,and DEC
DEC (Decimal)

HEX (Hexadecimal)

1001

1010

0000

1011

0001

1100

0010

1101

0011

1110

0100

2 - 32

BIN (Binary)

BCD (Binary-coded decimal)
0

1111

0101

0000

0110

0001

0111

1111

100

0111

32766

7FFE

1111

1110

0111

1111

32767

7FFF

0111

1111

-32768

8000

1000

0000

1000

0000

-32767

8001

1000

0000

0001

1000

0000

0001

-2

FFFE

1111

1110

-1

FFFF

1111

CHAPTER2 SEQUENCE PROGRAMS

(1) Inputting numeric values externally to the CPU module
When setting a numeric value to the CPU module externally using a digital switch, BCD (binary-coded decimal)
can be used as DEC (decimal) by the method given in (b).

(a) Numeric values used inside the CPU module
The CPU module performs program operations in binary.
If the value set in binary-coded decimal is used without conversion, the CPU module performs program

operations regarding the set value as binary.
Therefore, the program operations are not performed correctly. (

(b) below)

(b) Using any numeric data regardless of the data type
To convert the data set in binary-coded decimal into binary, which can be used in the CPU module, use the BIN
instruction.

The BIN instruction allows the CPU module to use any external numeric data regardless of the data type.

CPU module
[Setting numeric data]
Digital switch
4
XF

2
to

1
X0

BINP K4X0 DO

Input data in BCD.
BIN data
BCD D5 K4Y30

Figure 2.35 Inputting data from a digital switch to the CPU module

2.4 Data Used in Sequence Programs

Remark
For details of the BIN instruction, refer to the following.
QCPU Programming Manual (Common Instructions)

2 - 33

(2) Outputting numeric values externally from the CPU module
When externally displaying numeric values operated in the CPU module, a digital indicator can be used.

(a) Outputting numeric values
The CPU module performs program operations in binary.
If the binary values used in the CPU module are output to a digital indicator, the indicator does not show the
values correctly.
To convert the data set in binary into binary-coded decimal, which can be used in the external indicator, use the
BCD instruction.
The BCD instruction allows the external indicator to display values in decimal.
CPU module
BINP K4X0 DO

[Setting numeric data]
Digital indicator

Y3F
BCD D5 K4Y30

Y30

Output data
in BCD.
BIN data

Figure 2.36 Display of operation results in the CPU module by a digital indicator

Remark
For details of the BCD instruction, refer to the following.
QCPU Programming Manual (Common Instructions)

2 - 34

CHAPTER2 SEQUENCE PROGRAMS

2.4.1 BIN (Binary Code)

(1) Definition
Binary is a numeral system that represents numeric values using two symbols, 0 (off) and 1 (on).
Decimal notation uses the symbols 0 through 9. When the symbols for the first digit are exhausted (a

digit reaches 9), the next-higher digit (to the left) is incremented, and counting starts over at 0.
In binary notation, only the symbols 0 and 1 are used. After a digit reaches 1, an increment resets it to
0 and the next digit (to the left) is incremented. (The numeric value becomes 10, which is equal to 2 in
decimal.)

3
4

Table2.3 shows the numeric representations in BIN and DEC.
Table2.3 Numeric representations in BIN and DEC
BIN (Binary)

0000

0001

0010

0011

0100

0101

0110

0111

1000

1001

1010

1011

5
Carry

Carry

7
8

Carry

2.4 Data Used in Sequence Programs
2.4.1 BIN (Binary Code)

DEC (Decimal)

2 - 35

(2) Numeric representation in BIN
(a) Bit configuration of BIN used in the CPU module
Each register (such as the data register, link register) in the CPU module consists of 16 bits.
(b) Numeric data available in the CPU module
Each register in the CPU module can store numeric values in the range of -32768 to 32767.
Figure 2.37 shows the numeric representations for registers.
Most significant bit (sign bit)
Bit name

b15 b14 b13 b12 b11 b10 b9 b8 b7 b6 b5 b4 b3 b2 b1 b0

2 15 2 14 2 13 2 12 2 11 2 10 29
Decimal value

27 26

-32768 16384 8192 4096 2048 1024 512 256 128

2 1 20
2

A value will be negative value when the most significant bit is "1".
Figure 2.37 Numeric representations for registers in the CPU module

A numeric value of 2n is assigned for each bit of registers.
Note that an unsigned binary number (0 to 65535) cannot be used in the most significant bit position since the
most significant bit is a sign bit.

• The most significant bit is "0"...Positive
• The most significant bit is "1"...Negative

2 - 36

CHAPTER2 SEQUENCE PROGRAMS

2.4.2 HEX (Hexadecimal)

(1) Definition
Hexadecimal (HEX) is a numeral system that represents four binary bits as one digit.

With four binary bits, sixteen different numeric values, 0 to 15, can be represented.
Hexadecimal notation uses 16 symbols to represent numeric values 0 to 15 in one digit, the symbols 0
to 9 to represent values zero to nine, and AH to FH to represent values ten to fifteen. After a digit
reaches FH, the next-higher digit (to the left) is incremented.
ï\2.4 shows the numeric representations in BIN, HEX, and DEC.

3
4

Table2.4 Numeric representations in BIN,HEX,and DEC

DEC (Decimal)

HEX (Hexadecimal)

BIN (Binary)

6
7

1001

1010

1011

1100

1101

1110

0000

1111

0001

1111

Carry

(2) Numeric representation in HEX
Each register (such as the data register, link register) in the CPU module consists of 16 bits.
In the 16-bit configuration register, 0 to FFFFH can be specified in hexadecimal.

2 - 37

2.4 Data Used in Sequence Programs
2.4.2 HEX (Hexadecimal)

2.4.3 BCD (Binary-coded Decimal)
(1) Definition
BCD is a numeral system that uses four binary bits to represent the decimal digits 0 through 9.
The difference from hexadecimal is that BCD does not use letters A to F.
Table2.5 shows the numeric representations in BIN, BCD, and DEC.

Table2.5 Numeric representations in BIN,BCD,and DEC
DEC (Decimal)

BIN (Binary)

BCD (Binary-coded Decimal)

0000

0001

0010

0011

0100

100

0101

101

0110

110

0111

111

1000

1001

1010

0000

1011

0001

1100

0010

Carry

(2) Numeric representation in BCD
Each register (such as the data register, link register) in the CPU module consists of 16 bits.
Therefore, the numeric values can be stored in each register are those in the range between 0 to 9999 in BCD.

2 - 38

CHAPTER2 SEQUENCE PROGRAMS

2.4.4 Real number (Floating-point data)

There are two types of real number data: single-precision floating-point data and double-precision
floating-point data.

(1) Single-precision floating-point data

(a) Internal representation
Internal representation of real numbers used in the CPU module is given below.
Real number data can be represented as follows, using two word devices.
[Sign] 1. [Mantissa]

2[Exponent]

The bit configuration and the meaning of each bit are described below.

b31

b30

b31
Sign

b23

b22

b16

b15

b30 to b23
Exponent (8 bits)

to
b22 to b0
Mantissa (23 bits)

Figure 2.38 Bit configuration of real number data

1) Sign
The most significant bit, b31, is the sign bit.
0: Positive
1: Negative

2.4 Data Used in Sequence Programs
2.4.4 Real number (Floating-point data)

2) Exponent
The 8 bits, b23 to b30, represent the excess n of 2n.
The following shows the excess n according to the binary values in b23 to b30.
b23 to b30
n

FFH

FEH

Not used 127

FDH

81H

80H

7FH

7EH

126

-1

02H

01H

00H

-125 -126 Not used

Figure 2.39 Relation between the exponent and excess n

3) Mantissa
Each of the 23 bits, b0 to b22, represents the "XXXXXX..." portion when the data is represented in binary,
"1.XXXXXX...".

2 - 39

(b) Calculation example
Calculation examples are shown below. (The "X" in (nnnnnn) x indicates the numeral system used.)
1) Storing "10"
(10)10

(1010)2

(1.010000.....

Sign:

Positive

23)2

Exponent:

82H

(10000010)2

Mantissa:

(010 00000 00000 00000 00000)2

In this case, the value will be encoded as 41200000H.

Sign
Exponent
Mantissa
0 1 0 0 0 0 0 1 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
4

2) Storing "0.75"
(0.75)10
Sign:

(0.11)2
Positive

2-1)2

(1.100.....
0
7EH

(01111110)2

Exponent:

-1

Mantissa:

(100 00000 00000 00000 00000)2

In this case, the value will be encoded as 3F400000H.

Sign
Exponent
Mantissa
0 0 1 1 1 1 1 1 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
3

Values after the decimal point (in binary) is calculated as follows.

Example

(0.1101)2
0.

The bit represents 2-1

The bit represents 2-2

The bit represents 2-3

The bit represents 2-4

(0.1101)2 = 2-1 + 2-2 + 2-4 = 0.5 + 0.25 + 0.0625 = (0.8125)10

2 - 40

CHAPTER2 SEQUENCE PROGRAMS

(2) Double-precision floating-point data
(a) Internal representation
Real number data used in the CPU module is internally represented as follows, using four word

devices.
[Sign] 1. [Mantissa]

2[Exponent]

The bit configuration and the meaning of each bit are described below.

b63

b62

b63
Sign

b52

b51

b16

b15

b52 to b62
Exponent (11 bits)

4
b0

b0 to b51
Mantissa (52 bits)

Figure 2.40 Bit configuration of real number data

1) Sign
The most significant bit, b63, is the sign bit.

0: Positive
1: Negative

2) Exponent
The 11 bits, b52 to b62, represent the excess n of

2n.

The following shows the excess n according to the binary values in b52 to b62.

7FFH

7FEH 7FDH

Not used 1023 1022

400H 3FFH 3FEH 3FDH 3FCH
2

-1

-2

02H

01H

00H

-1021 -1022 Not used

Figure 2.41 Relation between the exponent and excess n

3) Mantissa
Each of the 52 bits, b0 to b51, represents the "XXXXXX..." portion when the data is represented in binary,
"1.XXXXXX...".

2 - 41

2.4 Data Used in Sequence Programs
2.4.4 Real number (Floating-point data)

b52 to b62

(b) Calculation example
Calculation examples are shown below. (The "X" in (nnnnnn) x indicates the numeral system used.)

1) Storing "10"
(10)10

(1010)2

(1.010000.....

Sign:

Positive

0
401H

23)2

Exponent:

Mantissa:

(0100 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000)2

(100 0000 0001)2

In this case, the value will be encoded as 4014000000000000H.

Sign
Exponent
Mantissa
0 100000000010100000000000000000000000000000000000000000000000000
4

2) Storing "0.75"
(0.75)10
Sign:

(0.11)2
Positive

Exponent: -1

2-1)2

(1.100.....
0
3FDH

(011 1111 1101)2

Mantissa: (1000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000)2

In this case, the value will be encoded as 3FD8000000000000H.

Sign
Exponent
Mantissa
0 011111111011000000000000000000000000000000000000000000000000000
3

Values after the decimal point (in binary) is calculated as follows.

Example

(0.1101)2
0.

The bit represents 2-1

The bit represents 2-2

The bit represents 2-3

The bit represents 2-4

(0.1101)2 = 2-1 + 2-2 + 2-4 = 0.5 + 0.25 + 0.0625 = (0.8125)10

2 - 42

CHAPTER2 SEQUENCE PROGRAMS

2.4.5 Character string data

(1) Definition
The CPU module uses ASCII code data.

(2) ASCII code character strings

Table2.6 lists the ASCII code character strings.
"00H" (NULL code) in Table2.6 is used at the end of a character string as a terminator.

Table2.6 ASCII code character strings

b1 Low

Column
3

(SP)

(

)

;

[

{

(Comma)
,

]

}

NULL

(Minus)

(Period)

z
/

(Under
line)

6
7
8

2.4 Data Used in Sequence Programs
2.4.5 Character string data

2 - 43

CHAPTER3 CPU MODULE OPERATION
This chapter describes operation of the CPU module.

3.1 Initial Processing
The CPU module performs preprocessing required for sequence program operations.
The preprocessing is executed only once when any of the operations described in Table3.1 is performed to
the CPU module.
When initial processing is completed, the CPU module will be placed in the operation status set by the
RUN/STOP/RESET switch. (

Section 3.5)
Table3.1 Initial processing list
CPU module status

Initial processing item
Powered-on

Reset

Changed from STOP to RUN *1

The I/O module initialization
Boot from a memory card
PLC parameter check
Multiple CPU system parameter consistency check
Initialization of devices outside the latch range
(bit device: off, word device: 0)
Automatic I/O number assignment of mounted modules
CC-Link IE controller network and MELSECNET/H
information setting
Intelligent function module switch setting
CC-Link information setting
Ethernet information setting
Initial device value setting
Serial communication function setting
: Performed,

: Not performed

*1: The operation indicates that the status is changed back to RUN without resetting the module after any parameter or program was changed
in the STOP status.
(The RUN/STOP/RESET switch is set from STOP to RUN (the RUN LED will flash), then back to STOP and to RUN again.)
Note that the PLS

P instruction (instruction for pulse conversion) may not be executed properly with the above operation. This is

because the previous information may not be inherited depending on the program changes.

If any parameter or program is changed in the STOP status, reset the CPU module using the RUN/STOP/RESET switch.

RUN/STOP/RESET switch
RESET

RUN

STOP

3-1

CHAPTER3 CPU MODULE OPERATION

3.2 I/O Refresh (Refresh Processing with Input/Output Modules)

The CPU module performs the following before sequence program operations.

• On/off data input from the input module or intelligent function module to the CPU module
• On/off data output from the CPU module to the output module or intelligent function module
When the constant scan time is set, I/O refresh is performed after the constant scan waiting time has

elapsed. (I/O refresh is performed at each constant scan cycle.)

4
3.3 Program Operation

The CPU module sequentially executes the program stored in the module from the step 0 to the END or
FEND instruction.(

CHAPTER 2)

6
7

3.4 END Processing
The CPU module performs refresh processing with network modules and communication with external

devices.
END processing includes the following.
CHAPTER 10)

• Auto refresh with intelligent function module (

Section 7.1.1)

• Intelligent function module dedicated instruction processing (
• Device data latch processing (
• Service processing (

CHAPTER 10)

Section 6.3, CHAPTER 10)

Section 6.24, CHAPTER 10)

• Watchdog timer reset (

Section 6.16)

• Auto refresh between multiple CPU modules (

QCPU User's Manual (Multiple CPU System))

• Device data collection using the sampling trace function (only when trace point is set to every scan (after
END instruction execution)) (

Section 6.14)

• Self-diagnostics processing (

Section 6.17)

• Special relay/special register value setting (only for those that should be set during END processing)
(

CHAPTER 12)

When the constant scan function (
Section 6.2) is used, the results of processing performed in
END processing are held for the period between after END processing is completed and until the
next scan starts.

3-2

3.2 I/O Refresh (Refresh Processing with Input/Output Modules)

• Refresh with network modules (

3.5 Operation Processing in the RUN,STOP, or PAUSE Status
There are three types of operating status of the CPU module.
• RUN status
• STOP status
• PAUSE status
This section describes program operation processing in the CPU module based on its operating status.

(1) Operation processing in the RUN status
RUN status is a status where sequence program operations are repeatedly performed in a loop
between the step 0 and the END (FEND) instruction.

(a) Output status when entering the RUN status
The CPU module outputs either of the following according to the output mode parameter setting when its status
is changed to RUN. (

Section 6.4)

• Output (Y) status saved immediately before entering the STOP status
• Result of operations performed for one scan after entering the RUN status

(b) Processing time required before operations
The processing time required for the CPU module to start sequence program operations after its
operating status is changed from STOP to RUN varies depending on the system configuration and/
or parameter settings. (It takes one to three seconds normally.)

(2) Operation processing in the STOP status
STOP status is a status where sequence program operations are stopped by the RUN/STOP/RESET
switch or the remote STOP function (

Section 6.6.1).

The CPU module status will be changed to STOP when a stop error occurs.

(a) Output status when entering the STOP status
When entering the STOP status, the CPU module saves data in the output (Y) and turns off all
outputs.
The device memory other than that of the output (Y) will be held.

(3) Operation processing in the PAUSE status
PAUSE status is a status where sequence program operations are stopped by the remote PAUSE
function (

Section 6.6.2) after operations are performed for one scan, holding the output and

device memory status.

3-3

CHAPTER3 CPU MODULE OPERATION

(4) Operation processing in the CPU module when switch operation is performed
Table3.2 Operation processing when switch operation is performed

CPU module operation processing
RUN/STOP

Sequence program

status

operation

Device memory
External output

M,L,S,T,C,D

processing

RUN

STOP

the output (Y) status

executes the program

immediately before its

until the END

status is changed to

instruction and stops.

STOP and turns off all the

The CPU module saves

The CPU module saves
The CPU module

The CPU module holds the device
memory status immediately before its
status is changed to STOP.

the output (Y) status
immediately before its
status is changed to
STOP and turns off all the
outputs.

outputs.

The CPU module holds the device

STOP

RUN

The CPU module outputs

memory status immediately before its

The CPU module outputs

The CPU module

data according to the

status is changed to STOP.

data according to the

executes the program

output mode parameter

Note that the CPU module uses initial

output mode parameter

from the step 0.

setting.

device values if those values are

setting.

preset.

(

Section 6.4)

Local device data are cleared.

7
8

The CPU module performs the following in any of the RUN, STOP, or PAUSE status.
Refresh processing with I/O modules
Refresh processing with network modules
Auto refresh processing with intelligent function modules
Self-diagnostics processing
Service processing
Intelligent function module dedicated instruction processing (completion processing only)
Operation processing of Multiple CPU high speed transmission function

Even if the CPU module is in the STOP or PAUSE status, the following operations can be executed.
•
•
•
•

I/O monitor or test operation from GX Developer
Read/write data from/to external devices using the MC protocol
Communication with other stations using CC-Link IE controller network or MELSECNET/H
Communication with CC-Link remote stations

3-4

3.5 Operation Processing in the RUN,STOP, or PAUSE Status

•
•
•
•
•
•
•

3.6 Operation Processing during Momentary Power Failure
When the input voltage supplied to the power supply module drops below the specified range, the CPU
module detects a momentary power failure and performs the following operation.

(1) When a momentary power failure occurs for a period shorter than the allowable power
failure time
The CPU module registers error data and suspends the operation processing.
The CPU module, however, continues measurement in the timer device and holds the output status.

(a) When resume start is specified for the SFC program
Data in the system is saved.

(b) When power is recovered after a momentary power failure
The CPU module restarts its operation processing.

(c) Watchdog timer (WDT) measurement during a momentary power failure
Even if operation processing is suspended due to a momentary power failure, the CPU module
continues the measurement of the watchdog timer (WDT).
For example, when the WDT setting of PLC parameter is 200ms and the scan time is 190ms, if a
momentary power failure occurs for 15ms, "WDT ERROR" occurs.
Momentary power
failure occurrence

Power recovery

END 0

END

The CPU module suspends
its program operations.
Figure 3.1 Operation processing during a momentary power failure

(2) When a momentary power failure occurs for a period longer than the allowable power
failure tim
The CPU module starts its operations initially.
Operation processing will be the same as that when any of the following is performed.
• Programmable controller is powered on.
• The CPU module is reset by the RUN/STOP/RESET switch.
• The CPU module is reset by GX Developer (the remote reset operation).

3-5

●

In a redundant power supply system, the CPU module does not suspend its operations if a momentary
power failure occurs in either of the power supply modules. However, if a momentary power failure occurs
under the condition where the power is supplied to only one of the power supply modules, operations are
suspended.

●

Information of a momentary power failure occurred in a redundant power supply system will be stored in
SM1782 to SM1783 and SD1782 to SD1783.
On the other hand, information of a momentary power failure occurred in a single power supply system
CHAPTER 12)
will be stored in SM53 and SD53. (

CHAPTER3 CPU MODULE OPERATION

3.7 Data Clear Processing

This section describes how to clear data in the CPU module and the setting required for the latch data

clear.

(1) Clearing data in the CPU module
Data in the CPU module are cleared when the reset operation (by the RUN/STOP/RESET switch or

by powering the module off and then on) is performed.
However, data in (a) below cannot be cleared by the reset operation.

(a) Data that cannot be cleared by the reset operation
• Data in the program memory

• Data in the standard ROM
• Data in a memory card
• Data in latch-specified devices (

(2) in this section)

• Data in the file register
(b) Clearing data that cannot be cleared by the reset operation

1) Data in the program memory
Data can be cleared by:
• selecting the "Clear program memory" checkbox in the Boot file tab of the PLC parameter

dialog box, or
• selecting [Online]

[Delete PLC data] in GX Developer.

2) Data in the standard ROM
3.7 Data Clear Processing

Data can be cleared automatically when the data is written to the standard ROM.
3) Data in a memory card
Data can be cleared by selecting [Online]

[Delete PLC data] in GX Developer.

4) Data in latch-specified devices
Refer to (2) in this section.
5) Data in the file register
Data can be cleared by:
• resetting devices with the RST instruction,
• transferring K0 with the MOV or FMOV instruction, or

QCPU Programming Manual (Common Instructions)
• executing "Clear all file registers" from the screen opened by selecting [Online]

[Clear PLC

memory] in GX Developer.

3-6

(2) Latch specification of devices
Set a latch range for each latch-target device in the Device tab of the PLC parameter dialog box.
(

Section 6.3(5))

(a) Latch range setting
Two kinds of latch range can be set by GX Developer.

1) Latch clear operation enable range ("Latch (1) start/end")
Data in this latch range can be cleared with the remote latch clear operation.

2) Latch clear operation disable range ("Latch (2) start/end")
Data in this latch range cannot be cleared with the remote latch clear operation.
(b) Clearing device data set in the latch clear operation enable range
Clear data with the remote latch clear operation (

Section 6.6.4).

(c) Clearing device data set in latch clear operation disable range
Clear data by:
• resetting devices with the RST instruction,
• transferring K0 with the MOV or FMOV instruction, or

QCPU Programming Manual (Common Instructions)
• executing "Clear device’s whole memory (including latch)" from the screen opened by

selecting [Online]

[Clear PLC memory] in GX Developer.

Latching devices increases the scan time.
When latching a device, consider the increase in the scan time. (

Remark
For the operation of GX Developer, refer to the following.
GX Developer Version 8 Operating Manual

3-7

Section 10.1.2(9))

CHAPTER3 CPU MODULE OPERATION

3.8 I/O Processing and Response Delay

The CPU module performs I/O processing in the refresh mode.
Using the direct access input/output in a sequence program, however, allows the CPU module to perform
I/O processing in the direct mode at the time of each instruction execution.
This section describes these I/O processing modes of the CPU module and response delays.

(a) Refresh mode(

Section 3.8.1)

Refresh mode is a mode for the CPU module to access input/output modules and perform I/O
processing collectively before the start of sequence program operations.

(b) Direct mode(

Section 3.8.2)

4
5

Direct mode is a mode for the CPU module to access input/output modules and perform I/O
processing at the timing when each instruction is executed in a sequence program.
To access input/output modules in the direct mode, use the direct access input or direct access
output in a sequence program.

6
7

(1) Differences between refresh mode and direct mode
The direct mode directly accesses input/output modules at execution of an instruction. Therefore, data

input is faster than in refresh mode.
Processing time required for each instruction, however, is longer.
Table3.3 shows the availability of the refresh mode and the direct mode for each input and output.

Item
Input/output modules
Input/output of intelligent function modules
Remote input/output in CC-Link IE controller network, MELSECNET/H, or CC-Link

Refresh mode

direct mode

Available

Not available

3-8

3.8 I/O Processing and Response Delay

Table3.3 Availability of modes

3.8.1 Refresh mode
(1) Definition
Refresh mode is a mode for the CPU module to access input/output modules and perform I/O
processing collectively before the start of sequence program operations.
Input of on/off data by
input refresh
Device memory
Output of on/off data by
output refresh
0

On/off data

X10

On/off
data

CPU module

Input module or
output module

Figure 3.2 Refresh mode

(2) Input
On/off data of an input module are batch-input to the area for communication with the input module in
the CPU module before the start of sequence program operations.
The CPU module performs sequence program operations using the on/off data stored in the input (X)
device memory.

3-9

CHAPTER3 CPU MODULE OPERATION

(3) Output
The operation results of the sequence program is output to the output (Y) device memory in the CPU
module every time program operation is performed. Then, the CPU module batch-outputs the on/off
data in the output (Y) device memory to an output module before the start of sequence program

operations.

CPU module
Remote
input refresh
area *1

CPU (operation
processing area)
3)
X0

Input (X)
device
memory

GX Developer
input area *2

Network
module
Input
refresh
1)

Input
module

Output
refresh
2)

Output
module

4
5

Input module
access area
4)
Y22

Y20

Output (Y)
device
memory

6
7

Network
module

•Input refresh:
Before the start of sequence program operations, the CPU module batch-reads input data 1) from
an input module, performs a logical OR operation with data in the GX Developer input area or data
•Output refresh:
Before the start of sequence program operations, the CPU module batch-outputs data in the output
(Y) device memory 2) to the output module.
•When a contact instruction for input is executed:
The CPU module reads input data 3) from the input (X) device memory and executes a sequence
program.
•When a contact instruction for output is executed:
The CPU module reads output data 4) from the output (Y) device memory and executes a sequence
program.
•When the OUT instruction for output is executed:
The CPU module stores the operation result of the sequence program 5) in the output (Y) device
memory.
Figure 3.3 I/O data flow in refresh mode

3 - 10

3.8 I/O Processing and Response Delay
3.8.1 Refresh mode

in the remote input refresh area, and then stores the result in the input (X) device memory.

*1: The remote input refresh area indicates the area to be used when auto refresh is set to the input (X) in the

CC-Link IE controller network, MELSECNET/H, or CC-Link.
Data in the remote input refresh area will be refreshed automatically during END processing.
*2: Data in the GX Developer input area can be turned on/off by the following operation.

•Test operation by GX Developer
•Writing data from a network module
*3: Data in the output (Y) device memory can be turned on/off by the following operation.

•Test operation by GX Developer
•Refresh via CC-Link IE controller network or MELSECNET/H
•Writing data from an external device using the MC protocol
•Auto refresh via CC-Link

(4) Response delay
An output response which corresponds to the status change in the input module delays for two scans
(maximum) depending on the on timing of an external contact.
Examples

A program that turns on the output
Y5E when the input X5 turns on.

Y5E

END 0 56

END 0

: Input refresh
: Output refresh

ON
OFF

External contact

ON
OFF

X5
Devices in the
CPU module

ON
OFF

Y5E

ON
OFF

External load

Delay time
(Minimum 1 scan)
Figure 3.4 Y5E turns on the earliest

END 0 56

END 0

: Input refresh
: Output refresh

ON
OFF
External contact
ON
X5
Devices in the
CPU module

OFF
ON

Y5E

OFF
ON

External load

OFF
Delay time
(Maximum 2 scans)
Figure 3.5 Y5E turns on the latest

3 - 11

CHAPTER3 CPU MODULE OPERATION

3.8.2 Direct mode

(1) Definition
The direct mode is a mode for the CPU module to access input/output modules and performs I/O
processing at the timing when each instruction is executed in a sequence program.
Input of on/off data upon
instruction execution

2
3

Device memory
Output of on/off data upon
instruction execution
0

On/off data

DX10

On/off
data

5
6
7
CPU module

Input module or
output module

Figure 3.6 Direct mode

With this mode, the CPU module uses the direct access input (DX) and direct access output (DY) to
perform I/O processing.
3.8 I/O Processing and Response Delay
3.8.2 Direct mode

3 - 12

CPU module
Remote
input refresh
area *1

CPU (operation
processing area)

3)
DX0

Input (X)
device
memory
4)

Y20

DY25

2) GX
Developer
input area *2

Network
module
1)

Input
module

Output (Y)
device
memory

Output
module

•When a contact instruction for input is executed:
The CPU module performs a logical OR operation between input data from the input module 1) and
input data in the GX Developer input area 2) or data in the remote input refresh area.
Then, the module stores the result in the input (X) device memory and executes a sequence
program using the stored result as input data 3).
•When a contact instruction for output is executed:
The CPU module reads output data 4) from the output (Y) device memory and executes a sequence
program.
•When the OUT instruction for output is executed:
The CPU module outputs the operation result of the sequence program 5) to the output module and
also stores the result in the output (Y) device memory.
Figure 3.7 I/O data flow in direct mode

*1: The remote input refresh area indicates the area to be used when auto refresh is set to the input (X) in the

•Test operation by GX Developer
•Writing data from a network module
*3: Data in the output (Y) device memory can be turned on/off by the following operation.

•Test operation by GX Developer
•Refresh via CC-Link IE controller network or MELSECNET/H
•Writing data from an external device using the MC protocol
•Auto refresh via CC-Link

3 - 13

CHAPTER3 CPU MODULE OPERATION

(2) Response delay
An output response which corresponds to the status change in the input module delays for one scan
(maximum) depending on the on timing of an external contact.

Examples

DX5

A program that turns on the output
DY5E when the input DX5 turns on.

DY5E

ON
OFF

External contact

Devices in the
CPU module

DX5
(External
contact)

OFF

DY5E
(External
load)

OFF

6
Delay time

Figure 3.8 DY5E turns on the earliest

END 0

55 56

ON
External contact

DY5E
(External
load)

ON
OFF
3.8 I/O Processing and Response Delay
3.8.2 Direct mode

Devices in the
CPU module

DX5
(External
contact)

OFF

ON
OFF
Delay time
(Maximum 1 scan)

Figure 3.9 DY5E turns on the latest

3 - 14

CHAPTER4 ASSIGNMENT OF BASE UNIT AND I/O
NUMBER
This chapter describes the base unit and I/O number assignment required for the CPU module to
communicate data with I/O modules and/or intelligent function modules.

4.1 Base Unit Assignment
4.1.1 Base mode
Use this mode when assigning the number of available slots to the main base unit and extension base units.
The following two modes are available.
• Auto mode
• Detail mode

(1) Auto mode
Use this mode when assigning the number of slots equal to that on the base unit used.

(2) Detail mode
Use the detail mode when assigning the number of slots for each base unit.
Any number of slots can be assigned irrespective of the actual number of slots on the base unit to be used.

(a) Setting the number of slots greater than the actual one
Slots are occupied by the number of slots set.
The slots after actually used ones are regarded as empty slots.
For example, three slots will be the empty slots when a 5-slot base unit is used and the number of available
slots are set to eight.
Main base unit

Power supply
module
CPU module

Empty

CPU

Empty

Actual number of slots

Q35B

Slot number

Number of slots set

Figure 4.1 Setting the number of slots greater than the actual one

The number of points for the empty slots will be either value set on the PLC system tab, or on the I/O
assignment tab in the PLC parameter dialog box. (The default is 16 points.)

4-1

CHAPTER4 ASSIGNMENT OF BASE UNIT AND I/O NUMBER

(b) Setting the number of slots smaller than the actual one
Set the smaller number than the actual number of slots when slots with no module mounted need not be
recognized.
For example, four slots from the right end of the base unit will be the prohibited slots when using a 12-slot base

unit and setting the number of available slots to eight. (Mounting a module on a prohibited slot causes
"SP.UNIT LAY ERR.".)

Main base unit

Actual number of slots

Power supply
module
CPU module

Number of slots set

Prohibited

CPU

Prohibited

Q312B
Slot number

4
5
6

Mounting a module will result in an error.

Figure 4.2 Setting the number of slots smaller than the actual one

7
4.1.2 Base unit assignment setting

Set base units on the I/O assignment tab of the PLC parameter dialog box.

4.1 Base Unit Assignment
4.1.2 Base unit assignment setting

(1)
(4)

(2)

(3)

Figure 4.3 I/O assignment setting

(1) Auto/Detail
Select the mode for the base unit assignment either from auto mode or detail mode.

(2) Base model name, Power model name, and Extension cable
Enter the model names of mounted base units, power supply modules, and extension cables to be used within 16
characters for user reference or when printing out parameters.
CPU modules do not use the entered model names.

4-2

(3) Slots
When "Detail" is set, select the number of slots on the base unit to use from the following.
2 (2 slots), 3 (3 slots), 5 (5 slots), 8 (8 slots), 10 (10 slots), or 12 (12 slots)

(4) 8 Slot Default/12 Slot Default
When "Detail" is set, select either of these items for batch-setting the base units to the specified number of slots.

4-3

●

In auto mode, when any extension base number is skipped at the setting using the base number setting connector, an
empty extension base cannot be reserved.
To reserve empty extension bases for future extension, select detail mode.

●

In detail mode, set the number of slots to all base units used.
Failure to do so may result in incorrect I/O assignment setting.

CHAPTER4 ASSIGNMENT OF BASE UNIT AND I/O NUMBER

4.2 I/O Number Assignment

The I/O number indicates addresses used for sequence programs in the following cases.

• Input of on/off data to the CPU module
• Output of on/off data from the CPU module to the external device

(1) Input and output of on/off data
The input (X) is used to input on/off data to the CPU module, and the output (Y) is used to output on/
off data from the CPU module.

(2) I/O number representation
The I/O numbers are represented in hexadecimal.
0

When a 16-point I/O module is used, the I/O number for each slot will be 16 point-sequence number from
to

F as shown in Figure 4.4.

5
6

"X" and "Y" is prefixed to the I/O number of input modules and the I/O number of output modules, respectively.
For the case of input
module

For the case of
output module

X0 0 0 X0 1 0 X 0 2 0 Y0 3 0 Y0 4 0

Power supply

4.2 I/O Number Assignment

X0 0 F X0 1 F X0 2 F Y0 3 F Y0 4 F
16 input 16 input 16 input 16 output 16 output
points
points
points
points
points
CPU module
Figure 4.4 I/O numbers

4-4

4.2.1 Concept of I/O number assignment
The CPU module assigns I/O numbers at power on or reset, according to the I/O assignment setting.

(1) I/O number assignment
The Figure 4.5 shows an example of I/O number assignment to base units in the system where the CPU module
is mounted on the main base unit.

X20 to 3F

Slot number

50 to 8F

X10 to 1F

CPU

X40 to 4F

X00 to 0F

Q35B (5 slots occupied)

I/O number: assign the I/O points of each slot

Assignment order
Number of slot points 16 points 16 points 16 points 16 points 16 points

I/O number assignment order
Number of I/O points

YF0 to FF

Vacancy (100 to 10F)

D0 to EF

90 to AF

B0 to CF

Q65B (5 slots occupied)

Assignment order
Number of slot points 16 points 16 points 16 points 16 points 16 points

X120 to 12F

130 to 14F

150 to 16F

Y180 to 1BF

Y1A0 to 1AF

Y190 to 19F

170 to 18F

X110 to 11F

Q68B (8 slots occupied)

Assignment order
Number of slot points 16 points 16 points 16 points 16 points 16 points 16 points 16 points 16 points

X
Y

0 to
0 to
0 to

F : Inupt module
F :Output module
F :Intelligent function module

Figure 4.5 I/O number assignment example

(a) Assignment order
For the main base unit, the I/O numbers are assigned to the modules from left to right in a
sequential order, starting from 0H assigned to the module on the right of the CPU module.
For extension base units, the I/O numbers are continued from the last number of the I/O number of
the main base unit.

(b) I/O number of each slot
Each slot on the base unit occupies I/O numbers by the number of I/O points of the mounted
modules.

4-5

CHAPTER4 ASSIGNMENT OF BASE UNIT AND I/O NUMBER

(2) I/O assignment on a remote I/O stations
CPU module device input (X) and output (Y) can be assigned to I/O modules and intelligent function modules,
which allows to control the modules in the remote I/O system such as MELSECNET/H remote I/O network and
CC-Link.

Also, inputs (X) and outputs (Y) can be used for the refresh target (devices on the CPU module side) of the
MELSECNET/H module link I/O (LX and LY).

3
4

Y80 to 9F

X40 to 5F

CPU module

X60 to 7F

MELSECNET/H module
CC-Link module

Remote
station

6
7

580 to 59F

X560 to 57F

X540 to 55F

X520 to 53F

X500 to 51F

MELSECNET/H remote I/O network

X
Y

0 to
0 to
0 to

F : Inupt module
F : Output module
F : Intelligent function module

Figure 4.6 I/O number assignment on the remote station

When the input (X) and output (Y) of the CPU module are used for the I/O numbers in the remote
station, assign the I/O numbers later than those used for the I/O modules and intelligent function
modules on the CPU module side.

Example When X/Y0 to X/Y3FF (1024 points) are used for the I/O modules and intelligent function modules
on the CPU module side, X/Y400 and later can be used in the remote stations.

4-6

4.2 I/O Number Assignment
4.2.1 Concept of I/O number assignment

(a) I/O numbers available on remote I/O stations

(b) Precautions for using remote station I/O numbers
1) Setting for future extension
When the input (X) and output (Y) of the CPU module are used for the I/O numbers on the remote
station, consider future extension of I/O modules and/or intelligent function modules on the CPU
module side.
Input/output (X/Y)
X/Y0
I/O numbers used by I/O modules/intelligent function
modules

to
X/Y3FF
X/Y400
to

For future expansion

X/Y4FF
X/Y500

For MELSECNET/H
remote I/O station
Empty

For CC-Link remote
I/O station

I/O numbers that can be used by remote stations

X/Y1FFF
When X/Y0 to 3FF (1024 points) are used by I/O modules and/or intelligent function
modules and X/Y400 to 4FF (256 points) are secured for future extension
Figure 4.7 Remote station I/O number assignment

2) When MELSECNET/H and CC-Link are used
I/O numbers to the refresh target (CPU module side device) of MELSECNET/H and to the CC-Link
remote I/O system must be unique.

4-7

●

When network parameter setting has not been made in the CC-Link system, X/Y 1000 to 17FF (2048 points) are
assigned to the CC-Link system master/local modules of lower numbers.

●

There are no restrictions on the I/O number assignment order for the MELSECNET/H remote I/O networks, CC-Link, or
other networks.

●

Space can be provided between the I/O area for MELSECNET/H remote I/O station and the I/O area for CC-Link
remote station.

CHAPTER4 ASSIGNMENT OF BASE UNIT AND I/O NUMBER

4.2.2 Setting I/O numbers

Set the I/O number on the I/O assignment tab.

(1) Purpose of I/O number assignment
(a) Reserving points for future module changes
The number of points can be flexibly set so that the I/O number modification can be avoided when

changing the current module to another in the future.
For example, 32 points can be assigned for future use to the slot where an input module with 16
points is currently mounted.

(b) Preventing I/O numbers from changing

4
5

The change in the I/O numbers can be prevented when an I/O module or intelligent function
module, whose occupied I/O points are other than 16, is removed due to failure.

(c) Changing the I/O numbers to those used in the program
When the I/O numbers used in the actual system differ from those in the designed program, the I/O
numbers of each module on the base unit can be changed to the ones in the designed program.

If any of the I/O modules whose number of I/O points are other than 16 fails without I/O assignment setting, the I/O
numbers assigned following to the failed module may change, leading to a malfunction.For this reason, making the I/O
assignment setting is recommended.

●

I/O assignment setting allows the following settings as well.
• Input response time (I/O response time) (
• Error time output mode (

Section 6.7)

Section 6.8)

• CPU module operation during a hardware error of intelligent function modules (
• Switch setting of intelligent function modules and interrupt modules(

4.2 I/O Number Assignment
4.2.2 Setting I/O numbers

●

Section 6.9)

Section 6.10)

The I/O assignment is required for the input response time and switch settings.

4-8

(2) I/O assignment
The I/O assignment is set on the I/O assignment tab of the PLC parameter dialog box.
On the I/O assignment tab, the following items can be set for each slot on the base unit.
• "Type" (module type)
• "Points" (I/O points)
• "Start XY" (start I/O number)
For example, to change the I/O number of the specified slot, setting is allowed only to the number of points.
For other items that are not set, settings are completed based on the installation status of the base unit.
(a)

(b)

(c)

(d)

(e)

Figure 4.8 I/O assignment

(a) Slot
The slot number and location of the slot are displayed.
When the base unit is set in Auto mode, the base unit number is indicated in "*", and the slot number is counted
from slot 0 of the main base unit.

4-9

CHAPTER4 ASSIGNMENT OF BASE UNIT AND I/O NUMBER

(b) Type

Select the type of the mounted module from the followings:

• Empty (empty slot)

• Input (input module)
• Hi input (high-speed input module)

• Output (output module)

• I/O Mix (I/O combined module)
• Intelli. (intelligent function module)

• Interrupt (interrupt module)

If the type is not specified, the type of the actually mounted module is used.

CPU modules do not use entered model names. (Use the entered model names for user reference.)

(d) Points

When changing the number of I/O points for each slot, the selections are as follows.
0 points, 16 points, 32 points, 48 points, 64 points, 128 points, 256 points, 512 points, 1024 points

If the number of points is not selected, the points of the actually mounted module is used.
For empty slots, the points that are set on the PLC system tab of the PLC parameter dialog box is assigned.
(Default: 16 points)

When changing the I/O number for each slot, enter a new start I/O number.

If start XY is not specified for a slot, the I/O number continuing from the last number of the current
setting is assigned.

4 - 10

4.2 I/O Number Assignment
4.2.2 Setting I/O numbers

(e) Start XY

(3) Precautions
(a) Type setting
The type set to the I/O assignment tab must be the same as that of the mounted module.
Setting a different type may cause incorrect operation.
For the intelligent function module, the I/O points must also be the same in addition to the I/O assignment
setting.
Table4.1 shows the operations when the mounted module type differs from the one in the I/O

assignment tab.
Table4.1 Incorrect operation when the module type differs
Mounted module

I/O assignment setting

Input module, output module,

• Intelli.

I/O combined module

• Interrupt

Result

Error (SP.UNIT.LAY.ERR.)

• Input
Intelligent function module

• Hi. input

Error (SP.UNIT.LAY.ERR.)

• Output
• I/O combined
• Input
• Hi. input

Empty slot

• Output
• I/O combined

Empty slot

• Intelli.
• Interrupt
All modules

• Empty

Empty slot
Error does not occur but incorrect operation

Other combinations

may be caused.
Or, error (PARAMETER ERROR (error code:
3000)).

(b) I/O points of slots
The number of I/O points for each slot selected in the I/O assignment tab is set in priority to those of mounted
modules.

1) When the preset number of I/O points is less than those of mounted I/O modules
The available points for the mounted I/O module will be decreased.
For example,when the number of I/O points is set to 16 points in the I/O assignment setting of PLC

parameter to the slot where a 32-point input module is mounted, the second half 16 points of the
32-point input module becomes unavailable.
2) When the preset number of I/O points exceeds those of mounted I/O modules
The exceeded number of points will not be used in I/O modules.

3) Last I/O number
Set the last I/O number within the I/O point range.

Failure to do so causes an error ("SP. UNIT LAY ERR."). ("***" is displayed as an I/O address on
the System monitor screen of GX Developer.)

4 - 11

CHAPTER4 ASSIGNMENT OF BASE UNIT AND I/O NUMBER

automatically assigns the start XY if it is not set. For this reason, the start XY setting of each slot
may be duplicated with the one assigned by the CPU module in the case of 1) or 2) below.
1) Start XY values are not in the correct order.

2
3

2) Slots with and without the start XY setting (automatically assigned slot) are mixed
An example of start XY duplication is given in Figure 4.9 below.

4
5
6
7
8
Figure 4.9 I/O assignment setting with start XY duplication
4.2 I/O Number Assignment
4.2.2 Setting I/O numbers

1
Input module

32 points 32 points 32 points

X40 X20
to
to
X5F X3F

Slot number

Additional module

0
Input module

Automatically assigned slot

X40
to
X5F

Number of I/O points
I/O number

Start XYs are overlapped
Figure 4.10 Start XY set by above (Figure 4.9) I/O assignment

Do not set duplicated start XY for each slot.

Duplication of start XY will result in an error ("SP. UNIT LAY ERR.").

Setting "Empty" and "0" to Type and Points respectively even occupies one slot.
To set on and after the specific slot unoccupied, set the number of slots in Detail mode. (

Section 4.1.1)

4 - 12

4.2.3 I/O number setting example
I/O number setting examples are provided as follows.

(1) Changing the number of points of an empty slot from 16 to 32
Reserve 32 points for the currently empty slot (Slot 3) so that the I/O numbers of Slot No. 4 and later
do not change when a 32-point input module is mounted there in the future.

(a) System configuration and I/O number assignment before I/O assignment using GX
Developer

Output module

Input module

3
Empty

Input module

0
Input module

Q38B

32 points 32 points 32 points 16 points 32 points 32 points 32 points 32 points

X00 X20
to
to
X1F X3F

X40
to
X5F

60
to
6F

Y70 Y90 YB0 YD0
to
to
to
to
Y8F YAF YCF YEF

Slot number

Number of I/O points
I/O number

Intelligent function
module

15
Output module

Intelligent function
module

Output module

Empty

9
Intelligent function
module

Extension
1

8
Intelligent function
module

Q68B

32 points 32 points 32 points 32 points 16 points 32 points 32 points 32 points

F0
to
10F

110
to
12F

130 150
to
to
14F 16F

170
to
17F

Y18
to
Y19

Y1A Y1C
to
to
Y1B Y1D

Figure 4.11 I/O number assignment (Before changing points of the empty slot)

4 - 13

CHAPTER4 ASSIGNMENT OF BASE UNIT AND I/O NUMBER

(b) I/O assignment
Select "32 points" for the number of I/O points of Slot 3 in the I/O assignment setting of PLC
parameter in GX Developer.

1
2
3

Select 32 points. (When
the type is not selected,
the type of the mounted
module will be set.)

4
5
6
7
Figure 4.12 I/O assignment setting (When changing points of Slot 3)

8
(c) I/O number assignment after the I/O assignment using GX Developer

Input module

Empty

Output module

32
32
32
32
32
32
32
32
points points points points points points points points

X00 X20
to
to
X1F X3F

X40
to
X5F

60
to
7F

Y80 YA0 YC0 YE0
to
to
to
to
Y9F YBF YDF YFF

Slot number

Number of I/O
points
I/O number

Intelligent
function module

15
Output module

Intelligent
function module

Output module

Empty

9
Intelligent
function module

Extension
1

8
Intelligent
function module

Q68B

32
32
32
32
32
32
32
32
points points points points points points points points

100
to
11F

120
to
13F

140 160
to
to
15F 17F

180 Y190 Y1B0 Y1D0
to
to
to
to
18F Y1AF Y1CF Y1EF

Figure 4.13 I/O numbers after I/O assignment (After changing points of the empty slot)

4 - 14

4.2 I/O Number Assignment
4.2.3 I/O number setting example

The number of I/O points is changed
from 16 points to 32 points.

0
Input module

Q38B

(2) Changing the I/O number of an empty slot
Change the I/O number of the currently empty slot (Slot 3) to X200 through 21F so that the I/O
numbers of Slot 4 and later do not change when a 32-point input module is mounted there in the
future.

(a) System configuration and I/O number assignment before the I/O assignment using
GX Developer

Output module

Input module

Empty

Input module

0
Input module

Q38B

32
32
32
16
32
32
32
32
points points points points points points points points

X00 X20
to
to
X1F X3F

X40
to
X5F

60
to
6F

Y70 Y90 YB0 YD0
to
to
to
to
Y8F YAF YCF YEF

Slot number

Number of I/O
points
I/O number

15
Output module

Intelligent
function module

Output module

Empty

Intelligent
function module

Extension
1

Intelligent
function module

Q68B

32
16
32
32
32
32
32
32
points points points points points points points points

F0
to
10F

110
to
12F

130 150
to
to
14F 16F

170 Y180 Y1A0 Y1C0
to
to
to
to
17F Y19F Y1BF Y1DF

Figure 4.14 I/O number assignment (Before changing slot I/O numbers)

4 - 15

CHAPTER4 ASSIGNMENT OF BASE UNIT AND I/O NUMBER

(b) I/O assignment
Set "200" for the start XY of Slot 3 and "70" to Slot 4 in the I/O assignment setting of PLC parameter

in GX Developer.

2
3

Set "200" to start XY.
Set "70" to start XY.
(If not set, the I/O
number following the
slot 3 will be set.)

4
5
6
7

Figure 4.15 I/O assignment setting (When changing I/O numbers of Slot 3)

4.2 I/O Number Assignment
4.2.3 I/O number setting example

4 - 16

Output module

Input module

0
Input module

Q38B

32 points 32 points 32 points 32 points 32 points 32 points 32 points 32 points

X00 X20
to
to
X1F X3F

X40 X200 Y70 Y90 YB0 YD0
to
to
to
to
to
to
X5F X21F Y8F YAF YCF YEF

Output module

Empty

Intelligent function
module

9
Intelligent function
module

Extension
1

Intelligent function
module

Q68B

Slot number

Number of I/O points
I/O number
The I/O number is not
changed.

32 points 32 points 32 points 32 points 16 points 32 points 32 points 32 points

F0
to
10F

110
to
12F

130 150
to
to
14F 16F

170 Y180 Y1A0 Y1C0
to
to
to
to
17F Y19F Y1BF Y1DF

Figure 4.16 I/O number assignment (After changing slot I/O numbers)

4.2.4 Checking I/O numbers
Information of mounted modules and their I/O numbers can be checked on the System monitor screen of
GX Developer. (

4 - 17

Section 6.20)

CHAPTER5 MEMORIES AND FILES USED FOR CPU MODULE

CHAPTER5 MEMORIES AND FILES USED FOR CPU
MODULE

1
2

5.1 Memories Used for CPU Module
3

5.1.1 Memory composition and storable data
This section describes the memories used for the Universal model QCPU and data that can be stored in

the memories.

(1) Memory composition
Program memory (program cache memory)

RAM

Parameter

Program

Parameter

Program

Device comment

Initial device value

Device comment

Initial device value

File register

Standard ROM
Parameter

Program

Device comment

Initial device value

Programmable controller
user data

Local device

Sampling
trace file
Memory card*1

ROM
Program

File for data to be stored by the
latch data backup function

Device comment

Initial device value

File used for the SP.DEVST and
S.DEVLD instructions

File register

Standard RAM
File register
Sampling
trace file

Local device
Module error
log file

Figure 5.1 Memory composition of the Universal model QCPU
*1: The Q00UJCPU, Q00UCPU, and Q01UCPU cannot be used with a memory card.
*2: The Q00UJCPU does not have the standard RAM.

5-1

5.1 Memories Used for CPU Module
5.1.1 Memory composition and storable data

Parameter

CPU module

(a) Program memory (

Section 5.1.2)

This memory is for storing programs and parameters for CPU module operation.
The CPU module transfers a program from the program memory to the program cache memory for operation.
(

Section 5.1.3)

(b) Standard ROM (

Section 5.1.4)

This memory is for storing data such as parameters and programs.

Section 5.1.5)

This memory is for using file registers, local devices, and sampling trace files without a memory card.

(d) Memory card (

Section 5.1.6)

This memory is for expansion of built-in memory in the CPU module.
Three types of memory cards are available: SRAM card, Flash card, and ATA card.

5-2

CHAPTER5 MEMORIES AND FILES USED FOR CPU MODULE

(2) Data that can be stored in each memory
Table5.1 provides the data that can be stored in each memory.

Table5.1 Data that can be stored in each memory
Memory
card (RAM)

CPU module built-in memory

Item

Program
memory

Standard
RAM

Standard
ROM

SRAM card

Drive 0
*1

Drive 3
*1

Drive 4
*1

Drive 1
*1

Memory card (ROM)
ATA
card

Flash card

Intelligent function
module parameter*2

Device comment

Remarks

Drive 2
*1

Parameter

Program

File name and
extension

PARAM.QPA

1 data/drive

IPARAM.QPA

1 data/drive

***.QPG

***.QCD

***.QDI

***.QST

***.QDR

Initial device value
Device data

Local device

***.QDL

Sampling trace file

***.QTD

Error history data

***.QFD

Device data storage file

DEVSTORE.
QST

Module error collection file

IERRLOG.QIE

Backup data file

MEMBKUP0.
QBP

***.***

Programmable controller
user data

*10

User setting system area*11

1 data/CPU
module

: Required,

: Storable,

: Not storable

*1: A drive number is used to specify a memory to be written/read by the external device using a sequence program or MC protocol.
Since the memory name is used to specify the target memory by GX Developer, the drive number needs not to be considered.
*2: Store the intelligent function module parameters in the same drive with the parameters.
When they are stored in different drives, the intelligent function module parameters do not become valid.
*3: A program stored in the standard ROM cannot be executed.
Store the program to the program memory before execution.
*4: To execute a program stored in the memory card, make the setting in the Boot file tab of the PLC parameter dialog box.
*5: The device comments cannot be read by instructions in a sequence program.
*6: Reading from a sequence program requires several scans.
*7: Only each one of file register, one local device, and/or sampling trace file can be stored in the standard RAM.
*8: For the number of storable file register points, refer to Section 9.7.
*9: A sequence program allows reading only. No data can be written from the sequence program.
*10: Data can be written or read with the following instructions.
•SP.FREAD (batch-reads data from the specified file in the memory card.)

•SP.FWRITE (batch-writes data to the specified file in the memory card.)
*11: Set an area used by the system. (

Section 5.1.2(2)(b))

5-3

4
5
6
7
8

5.1 Memories Used for CPU Module
5.1.1 Memory composition and storable data

File register

*7*8

(3) Memory capacities and necessity of formatting
Table5.2 provides the memory capacities and necessity of formatting of each memory.

Format a memory requiring formatting by GX Developer beforehand.
Table5.2 Memory capacities and necessity of formatting
Q00UJCPU

Q00UCPU

Q01UCPU

Q02UCPU

Q03UDCPU,
Q03UDECPU

Q04UDHCPU,
Q04UDEHCPU

Formatting

Program memory

40K bytes
(10K steps)

60K bytes
(15K steps)

80K bytes
(20K steps)

120K bytes
(30K steps)

160K bytes
(40K steps)

Necessary

Standard ROM

256K bytes

512K bytes

1024K bytes

Unnecessary

Standard RAM

128K bytes

192K bytes

256K bytes

Necessary*1

Memory
card

SRAM
card

Q2MEM-1MBS: 1M byte
Q2MEM-2MBS: 2M bytes
Q3MEM-4MBS: 4M bytes
Q3MEM-8MBS: 8M bytes

Necessary
(Use GX
Developer.)

Flash
card

Q2MEM-2MBF: 2M bytes
Q2MEM-4MBF: 4M bytes

Unnecessary

ATA
card

Q2MEM-8MBA: 8M bytes
Q2MEM-16MBA: 16M bytes
Q2MEM-32MBA: 32M bytes

Necessary
(Use GX
Developer.)

Q06UDHCPU,
Q06UDEHCPU

Q10UDHCPU,
Q10UDEHCPU

Q13UDHCPU,
Q13UDEHCPU

Q20UDHCPU,
Q20UDEHCPU

Q26UDHCPU,
Q26UDEHCPU

Formatting

Program memory

240K bytes
(60K steps)

400K bytes
(100K steps)

520K bytes
(130K steps)

800K bytes
(200K steps)

1040K bytes
(260K steps)

Necessary

Standard ROM

1024K bytes

2048K bytes

4096K bytes

Unnecessary

Standard RAM

768K bytes

1024K bytes

1280K bytes

Necessary*1

Memory
card

SRAM
card

Q2MEM-1MBS: 1M byte
Q2MEM-2MBS: 2M bytes
Q3MEM-4MBS: 4M bytes
Q3MEM-8MBS: 8M bytes

Necessary
(Use GX
Developer.)

Flash
card

Q2MEM-2MBF: 2M bytes
Q2MEM-4MBF: 4M bytes

Unnecessary

ATA
card

Q2MEM-8MBA: 8M bytes
Q2MEM-16MBA: 16M bytes
Q2MEM-32MBA: 32M bytes

Necessary
(Use GX
Developer.)

*1: When the memory contents become indefinite in initial status or due to the end of battery life, the memory is automatically formatted after
the CPU module is powered off and then on or is reset.

5-4

●

When files are written to each memory, the unit of stored file size depends on the target CPU
module and memory area.(
Section 5.3.4)

●

In memory capacity calculation, 1 step is equal to 4 bytes.

CHAPTER5 MEMORIES AND FILES USED FOR CPU MODULE

5.1.2 Program memory

(1) Definition
This memory is for storing programs and parameters for CPU module operation.
The CPU module transfers a program from the program memory to the program cache memory for
operation. (

Section 5.1.3)

3
4

If the total size of data to be stored exceeds the program memory capacity:
• reduce the user setting system area, or
• transfer data other than programs to the standard ROM or memory card.

5
6

(2) Before using the program memory
Format the program memory by GX Developer.
(a) Formatting
Select [Online]

[Format PLC memory] in GX Developer.

Select "Program memory/Device memory" in “Target memory”.

5.1 Memories Used for CPU Module
5.1.2 Program memory

Figure 5.2 Formatting the program memory

(b) Creating a user setting system area
When formatting a program memory, set the capacity of user setting system area.

1) Do not create a user setting system area (the necessary system area only)
The user setting system area is not created during formatting.

2) Create a user setting system area
The user setting system area is created during formatting.
Table5.3 provides the type of user setting system area.
Table5.3 Type of user setting system area
System area

High speed monitor area from
other station.

Description
Setting this area increases the monitoring speed in the GX Developer connected to such as
a serial communication module.
When using RS-232 and USB together with GX Developer, this area is used to register
monitor data from GX Developer connected to such as a serial communication module.

5-5

When a user setting system area is created, the available area reduces by the number of steps created in the
area.

[Read from PLC] in GX Developer.

1) Select "Program memory/Device memory" in “Target memory” on the Read from PLC screen.
2) Click the Free space volume button.
3) The memory capacity appears in “Total free space volume”.
1) Select the target memory.

2) Click the
Free space volume button.

3) The memory capacity
value is shown.

Figure 5.3 Procedure for checking the memory capacity

5-6

CHAPTER5 MEMORIES AND FILES USED FOR CPU MODULE

(3) Writing to the program memory
Select [Online]

[Write to PLC] in GX Developer.

Select "Program memory/Device memory" in “Target memory” on the Write to PLC screen.

2
3
4
5
6
7

Figure 5.4 Write to PLC screen

5-7

5.1 Memories Used for CPU Module
5.1.2 Program memory

The file size has its minimum unit. (
Section 5.3.4)
The occupied memory capacity may be greater than the actual file size.
Note that as the number of files increases, the difference between the occupied memory capacity and the actual file size
increases.

5.1.3 Program cache memory
(1) Definition
This memory is for program operation.
The CPU module transfers a program from the program memory to the program cache memory for
operation.
The program is transferred during:
• initial processing after the CPU module is powered on, or
• initial processing after the CPU module is reset.
Figure 5.5 provides the flow of program operations.
Power-on/reset

Universal model QCPU
Initial Processing
(transfers data in the
program memory to the
program cache memory.)

1) Transfer

Program
memory
(Flash ROM)

Program
cache
memory
(SRAM)

I/O module refresh
processing

2) Operation
processing

Standard
RAM (SRAM)

Standard
ROM
(Flash ROM)

Multiple
CPU auto
refresh area

Operation processing
of the program

END processing

Figure 5.5 Flow of program operation

5-8

CHAPTER5 MEMORIES AND FILES USED FOR CPU MODULE

(2) Writing a program
When writing data from GX Developer, programs and parameters are written to the program cache memory in the
CPU module. After the completion of the writing, the data are transferred to the program memory.

Figure 5.6 provides the flow of writing a program.
Universal model QCPU
2) After data are written to the program
cache memory, the data are automatically
transferred to the program memory.

1) Data are written to the program
cache memory once.

Program
cache
memory
(SRAM)

Program
memory
(Flash ROM)

4
5

GX Developer

Standard
RAM
(SRAM)

Standard
ROM
(Flash ROM)

Multiple
CPU auto
refresh area

Figure 5.6 Flow of writing a program

(3) Transferring data to the program memory by GX Developer
Data can also be batch-transferred from the program cache memory to the program memory by selecting [Online]

[Program memory batch transfer] in GX Developer.
Figure 5.4 provides the transfer time required when data are batch-transferred to the program memory while the
5.1 Memories Used for CPU Module
5.1.3 Program cache memory

CPU module is in the RUN status.
Table5.4 Transfer time of program memory batch-transfer
CPU module
Q00UJCPU, Q00UCPU, Q01UCPU, Q02UCPU

Transfer time
Ts

320 + 4.8 (s)

260 + 4.7 (s)

Q10UDHCPU, Q10UDEHCPU

439 + 6.2 (s)

Q13UDHCPU, Q13UDEHCPU

600 + 8.0 (s)

Q20UDHCPU, Q20UDEHCPU

839 + 11.4 (s)

Q26UDHCPU, Q26UDEHCPU

1100 + 15.0 (s)

Q03UDCPU, Q04UDHCPU, Q06UDHCPU, Q03UDECPU,
Q04UDEHCPU, Q06UDEHCPU

Ts: scan time (s)

5-9

(4) Checking status during data transfer to the program memory
The status during data transfer to the program memory can be checked either in the progress screen
of GX Developer or by the special relay and special register.

(a) Checking the status in the progress screen
Figure 5.7 provides the progress screen of GX Developer.

Figure 5.7 Screen showing status of data transfer to the program memory

(b) Checking the status by the special relay and special register
The status can be checked by SM681 and SD681.

(5) Checking whether data are transferred to the program memory

Note5.1Note1

Whether data are transferred from the program cache memory to the program memory can be
checked by SM165.

Note1

Note5.1

Universal

When checking the transfer status to the program memory in the Q02UCPU, Q03UDCPU, Q04UDHCPU,
or Q06UDHCPU, check the versions of the CPU module and GX Developer. (

5 - 10

Appendix 2)

CHAPTER5 MEMORIES AND FILES USED FOR CPU MODULE

5.1.4 Standard ROM

(1) Definition
This memory is for storing data such as parameters and programs.

(2) Checking the memory capacity
Select [Online]

[Read from PLC] in GX Developer.

1) Select "Standard ROM" in “Target memory” on the Read from PLC screen.
2) Click the Free space volume button.

3) The memory capacity appears in “Total free space volume”.
1) Select the target memory.

5
6
7
8

5.1 Memories Used for CPU Module
5.1.4 Standard ROM

2) Click the
Free space volume button.

3) The memory capacity
value is shown.

Figure 5.8 Procedure for checking the memory capacity

(3) Writing to the standard ROM
Select [Online]

[Write to PLC] in GX Developer.

Select "Standard ROM" in “Target memory”.

5 - 11

5.1.5 Standard RAM

Note5.2

Note1

(1) Definition
This memory is for using file registers, local devices, and sampling trace files without a memory card.
Storing the file registers in the standard RAM allows fast access as data registers do.
The memory is also used for storing a module error collection file.

If the size of files to be stored exceeds the standard RAM capacity:
• store the files in the memory card, or
• reduce the number of points of the file register, local device, or sampling trace.
Note when file registers are stored in the memory card, the access speed will be slower than when they are
stored in the standard RAM.

(2) Before using the standard RAM
Format the standard RAM by GX Developer.
(a) Formatting
Select [Online]

[Format PLC memory] in GX Developer.

Select "Standard RAM" in “Target memory”.

Figure 5.9 Formatting the standard RAM

Note1

Note5.2

Universal

The Q00UJCPU does not have the standard RAM.

5 - 12

CHAPTER5 MEMORIES AND FILES USED FOR CPU MODULE

(b) Checking the memory capacity after formatting
Select [Online]

[Read from PLC] in GX Developer.

1) Select "Standard RAM" in “Target memory” on the Read from PLC screen.

2) Click the Free space volume button.
3) The memory capacity appears in “Total free space volume”.

1) Select the target memory.

4
5
6
7
2) Click the
Free space volume button.

3) The memory capacity
value is shown.

Figure 5.10 Procedure for checking the memory capacity

Select [Online]

5.1 Memories Used for CPU Module
5.1.5 Standard RAM

(3) Writing to the standard RAM
[Write to PLC] in GX Developer.

Select "Standard RAM" in “Target memory” on the Write to PLC screen.

Figure 5.11 Write to PLC screen

5 - 13

5.1.6 Memory card

Note5.3

Note1

(1) Definition
This memory is for expansion of a memory in the CPU module.
The following three types are available:
• SRAM card
• Flash card
• ATA card

(a) SRAM card
File registers in the SRAM card can be written or read by the sequence program.
The SRAM card is used when:
• the number of file register points is greater than the standard RAM capacity, or
• the sampling trace function is used. (
Section 6.14)
When storing file registers to the SRAM card, the file registers can be written or read by the sequence program
up to 4086K points.

(b) Flash card
Write data by GX Developer and read it by the sequence program. (Data can be read only by the sequence
program.)
Use the Flash card when data are not changed.
File registers can be stored up to 2039K points.

(c) ATA card
This card is used for programmable controller user data (general-purpose data).
With the file access instruction (such as the SP. FWRITE instruction) in the sequence program, access the
programmable controller user data in the ATA card in CSV format/binary format.

Note1

Note5.3

Universal

The Q00UJCPU, Q00UCPU, and Q01UCPU cannot be used with a memory card.

5 - 14

CHAPTER5 MEMORIES AND FILES USED FOR CPU MODULE

(2) Before using the SRAM card or ATA card
Format the SRAM card or ATA card by GX Developer.

(a) Formatting

Select [Online]
[Format PLC memory] in GX Developer.
• When formatting the SRAM card, select "Memory card (RAM)" in “Target memory”.
• When formatting the ATA card, select "Memory card (ROM)" in “Target memory”.

3
4
5
6
7

Figure 5.12 Formatting the SRAM card or ATA card

8
●

Use only GX Developer to format the ATA card.
If formatting the ATA card by such as the formatting function of Microsoft
be used with the CPU module.

Windows , the card may not

When formatting the SRAM card or ATA card, the memory card information area is automatically secured.
Therefore, the card capacity reduces by the area size.

Remark
Formatting is not required for the Flash card.

5 - 15

5.1 Memories Used for CPU Module
5.1.6 Memory card

●

(b) Checking the memory capacity after formatting
Select [Online]

[Read from PLC] in GX Developer.

1) Select "Memory card (RAM)" or "Memory card (ROM)" in “Target memory” on the Read from PLC screen.
2) Click the Free space volume button.
3) The memory capacity appears in “Total free space volume”.
1) Select the target memory.

2) Click the
Free space volume button.

3) The memory capacity
value is shown.

Figure 5.13 Procedure for checking the memory capacity

(3) Writing to the memory card
The following describes the operations before writing and the methods for writing.

(a) Writing to the SRAM card or the ATA card
Select [Online]
[Write to PLC] in GX Developer.
• When writing data to the SRAM card, select "Memory card (RAM)" in “Target memory” on the Write to PLC
screen.
• When writing data to the ATA card, select "Memory card (ROM)" in “Target memory” on the Write to PLC
screen.

Figure 5.14 Write to PLC screen

5 - 16

CHAPTER5 MEMORIES AND FILES USED FOR CPU MODULE

(b) Writing to the Flash card

The following two methods are available.
• Writing by "Write the program memory to ROM" (
• Writing by "Write to PLC (Flash ROM)” (

Section 5.1.7(1)(a))

Section 5.1.7(1)(b))

3
The file size has its minimum unit. (
Section 5.3.4)
The occupied memory capacity may be greater than the actual file size.
Note that as the number of files increases, the difference between the occupied memory capacity and the
actual file size increases.

4
5
6

(4) How to use the program stored in the memory card
Boot the program stored in the memory card to the program memory before its execution.(

Section 5.1.8)

7
8

5.1 Memories Used for CPU Module
5.1.6 Memory card

5 - 17

5.1.7 Writing to the Flash card by GX Developer
(1) Methods for writing data to the Flash card and applications
Figure 5.15 provides the methods for writing data to the Flash card.
Writing by "Write the program memory to ROM"

Program
memory

Writing by "Write to PLC
(Flash ROM)"

CPU module

GX Developer
Figure 5.15 Methods for writing data to the Flash card

(a) Writing by “Write the program memory to ROM”
Data in the program memory are batch-written to the Flash card.
To batch-write the data, select [Online]

[Write to PLC (Flash ROM)]

[Write the program memory to ROM]

in GX Developer.
Use this method when:
• debugging the program in the program memory and writing the debugged program to the Flash card
without change for boot operation (

Section 5.1.8), or

• storing the data in the program memory to the Flash card without battery backup.

(b) Writing by “Write to PLC (Flash ROM)”
Files specified by GX Developer are batch-written to the Flash card.
To batch-write the files, select [Online]

[Write to PLC (Flash ROM)]

[Write to PLC (Flash ROM)] in GX

Developer.
Use this method when:
• storing parameters, initial device values, or device comments whose size exceeds the program memory
capacity to the Flash card, or
• using file registers storied in the Flash card.

5 - 18

CHAPTER5 MEMORIES AND FILES USED FOR CPU MODULE

(2) Writing to the Flash card
The following describes the operations before writing and the methods for writing.

(a) Before writing
Check the following.

1) Preparing files to be written

Writing a file to the Flash card automatically deletes all files stored in the Flash card.
Also write all files same as the stored files together.

2) Boot operation
When storing parameters to the Flash card at boot operation, make the boot file setting described in Section

5.1.8.

5
(b) Writing procedure
The following describes a procedure for writing a file to the Flash card.

1) Procedure for [Write the program memory to ROM] in GX Developer
• Select [Online]

[Write to PLC (Flash ROM)]

[Write the program memory to ROM].

• The program memory data into ROM screen appears.

• Select the memory to be written in "Target" to write the program memory file to the Flash card.

●

When files are written by “Write the program memory to ROM”, the capacity of used target memory is equal to that of
used program memory.
To fully use the capacity of the target memory, write the files by “Write to PLC (Flash ROM)”.

●

When writing data that cannot be stored to the program memory (file register) to the Flash card, write it by “Write to
PLC (Flash ROM)”.

5 - 19

5.1 Memories Used for CPU Module
5.1.7 Writing to the Flash card by GX Developer

Figure 5.16 Copy program memory data into ROM screen

2) Procedure using [Write to PLC (Flash ROM)] in GX Developer
• Select [Online]

[Write to PLC (Flash ROM)]

[Write to PLC (Flash ROM)].

• The Write to PLC (Flash ROM) screen appears.

Figure 5.17 Write to PLC (Flash ROM) screen

• Select the target memory.
• Select a file to be written and write it to the Flash card.

(3) Adding or changing a file in the Flash card
Add or change the file by either of the following methods (stored files cannot be added or changed directly).

(a) When writing files using [Write the program memory to ROM] in GX Developer
• To read all files in the program memory, select [Online]

[Read from PLC].

• Add or change the read files.
• Write the added or changed files to the program memory.
• Select [Online]

[Write to PLC (Flash ROM)]

[Write the program memory to ROM] and write the files to

the Flash card.

(b) When writing files using [Write to PLC (Flash ROM)] in GX Developer
• To read all files in the Flash card, select [Online]

[Read from PLC].

• Add or change the read files.
• Select [Online]
Flash card.

5 - 20

[Write to PLC (Flash ROM)]

[Write to PLC (Flash ROM)] and write the files to the

CHAPTER5 MEMORIES AND FILES USED FOR CPU MODULE

(4) Precautions
(a) Setting the communication time check period in GX Developer
Since writing a file to the Flash card takes time, set "Check at communication time" in GX Developer to 60

seconds or longer.
If the set time is short, GX Developer may time out.

3
4
5

Figure 5.18 Check at communication time setting

(b) Writing a file from GX Developer in another station via CC-Link
Since writing a file to the Flash card takes time, make the CPU monitoring time setting (SW000A) of CC-Link to

60 seconds or longer.
(The default value of 90 seconds can be used.)

CPU module that writes
files to the Flash card

5.1 Memories Used for CPU Module
5.1.7 Writing to the Flash card by GX Developer

GX Developer in another station

Figure 5.19 Writing a file from GX Developer in another station(via CC-Link)

Remark
For settings of the communication time check period and CPU monitoring time, refer to the following.
GX Developer Version8 Operating Manual

5 - 21

(c) Time required for “Write to PLC (Flash ROM)”
Using "Write to PLC (Flash ROM)” writes data to the entire space in the Flash card.
Therefore, even if a program having the small number of steps is written to the Flash card, the processing
takes time.
(Writing using the Q2MEM-4MBF at a communication speed of 115.2Kbps with an RS-232 interface requires
14 minutes.)
When writing data to the Flash card, increase the transmission speed or use an USB.
Communication time takes time when “Write to PLC (Flash ROM)” is executed from another station.

(d) Online change (Only “Write to PLC (Flash ROM)” can be used.)
“Write to PLC (Flash ROM)” can be executed during the RUN status except the following cases.
Execute “Write to PLC (Flash ROM)” after setting the RUN/STOP/RESET switch to STOP when:
1) File registers stored in the Flash card are used in the sequence program, or
2) although "Not used" is set to the file registers by the PLC parameter dialog box, they are used in the
sequence program.
If “Write to PLC (Flash ROM)” is executed during the RUN status in either above situations of 1) or 2), an error
may occur, resulting the CPU module to stop.

(e) Writing/reading data during execution of “Write to PLC (Flash ROM)”
While “Write to PLC (Flash ROM)” is executed, data cannot be read from/written to other modules.
Therefore, time-out may occur in other modules.

(f) When “Write to PLC (Flash ROM)” is executed during the STOP status
Do not set the RUN/STOP/RESET switch to RUN during the writing.
The CPU module may not enter the RUN status normally during execution of "Write to PLC (Flash ROM)".
Set the RUN/STOP/RESET switch to RUN after the writing.

5 - 22

CHAPTER5 MEMORIES AND FILES USED FOR CPU MODULE

5.1.8 Operating the program in the memory card (boot operation)

This section describes methods for operating the program stored in the memory card.

(1) Operating the program in the memory card
To execute the boot operation, set the names of files to be booted in the Boot file tab of the PLC parameter dialog
box. (
(3) in this section, (4))
The program stored in the memory card, whose file name is specified in the Boot file tab, is booted with the
program memory after the CPU module is powered off and then on or is reset.

3
4

Program
memory

5
Boot
CPU module

6
7

Memory card
Figure 5.20 Boot operation

8
(2) Bootable files, transfer source, and transfer destination
Table Table5.5 provides the combinations of bootable file, transfer source, and transfer destination.

File name

Transfer source

Transfer destination
Program memory

Standard ROM

Parameter
Sequence program
Device comment

Memory card

Initial device value
Label program
: Bootable,

: Cannot be booted.

5 - 23

5.1 Memories Used for CPU Module
5.1.8 Operating the program in the memory card (boot operation)

Table5.5 Combinations of bootable file, transfer source, and transfer destination

(3) Procedure before boot operation
The following explains the procedures to store the files to be booted in the memory card and then start boot
operation.

(a) Creating a program
Create a program.
(b) Boot file setting
Set the names of files to be booted to the program memory in the Boot file tab of the PLC parameter
dialog box.

Figure 5.21 Boot file tab

(d) Writing to the memory card
Write the parameters and programs set in the Boot file tab to the memory card.

(e) Executing the program
Set the RUN/STOP/RESET switch to RESET.
The BOOT LED turns on after a boot from the specified memory is completed.

(f) Checking whether a boot is normally completed
The following status indicates normal completion of boot operation.
• The BOOT LED turns on.
• The special relay (SM660) turns on.
• The data written to the transfer source memory and the data in the program memory are found the same
by verification made by selecting [Online]
[Verify with PLC] in GX Developer.

5 - 24

CHAPTER5 MEMORIES AND FILES USED FOR CPU MODULE

(4) Operation for stopping boot operation
To stop boot operation and operate the CPU module by the parameters and program files written to the program
memory, perform the following operations.
1) Remove the memory card and write parameters without boot file setting to the program memory by

GX Developer.

2) Power on the programmable controller again or reset the CPU module.

(5) Boot operation precautions

(a) Storage location of parameters
• Store the parameters set in the Boot file tab of the PLC parameter dialog box to the memory card.
If the parameters set in the Boot file tab are stored in the program memory or standard ROM, the CPU
module ignores the parameter settings. (

Section 5.1.10)

• When both of the following status 1) and 2) occurs, the CPU module is not operated by the parameters in
the memory card, but by the parameters in the program memory.

1) There are parameters in the program memory.

2) The parameters in the memory card are not set in the Boot file tab.

(b) Online change in boot operation

1) Memory card (RAM)
When data are written to a program in the program memory in the RUN status (

Section 6.12), the

change can be updated to the program in the boot source memory card (RAM).

Even if a program in the program memory is written in the RUN status, the change is not updated to the
program in the boot source memory card (ROM).
Therefore, write the same file whose program was written to the program memory to the memory card (ROM)
by Write to PLC (Flash ROM). (

Section 5.1.7)

(c) Maximum number of settable boot files
Set the maximum number of settable boot files in the Boot file tab of the PLC parameter dialog box so that it
may be the same with the number of files storable to the program memory.
However, the number of boot files reduces by 1 when:
• a heading is set, or
• the parameters set in the Boot file tab of the PLC parameter dialog box and stored in the memory card is
booted.

5 - 25

5.1 Memories Used for CPU Module
5.1.8 Operating the program in the memory card (boot operation)

2) Memory card (ROM)

(d) Boot operation when the ATA card is used
When data are booted from the ATA card, the processing time of maximum 200ms may be required per 1K step
(4K bytes).

(e) When data in the program memory are changed after the CPU module is powered off and
then on or is reset
If the program memory data are changed after the sequence program is written to the program memory and the
CPU module is powered off and then on or is reset, a boot operation may be active.
While the BOOT LED on the front of the CPU module is on, the boot operation is active. Refer to (4) in this
section and stop the boot operation.

(f) Size after a boot from the memory card
The size unit of a file stored in each memory differs between the memory card and the program memory.
(

Section 5.3.4)

Therefore, note that files transferred from the memory card to the program memory differ in memory capacity
between before and after the transfer.

(g) Program written to the memory card
Set the programmable controller type (model name of the CPU module) for the program written to the memory
card (program set in the Boot file tab) and the model name of the CPU module to be booted to the same.

5 - 26

CHAPTER5 MEMORIES AND FILES USED FOR CPU MODULE

5.1.9 Details of written files

For each file written to the CPU module, its name, size, and created date and time set at the file creation are
appended.
The file is displayed on the Read from PLC screen, opened by selecting [Online]

[Read from PLC] in GX Developer,

as shown below.

3
4
5
6
7

Figure 5.22 Displaying the details of a file

(a) File name
1) File name structure and file specification
Each file name is composed of a name (up to 8 characters in one byte/4 characters in double bytes) and an

extension (3 characters).
Create a file name with upper-case characters only.

2) Characters that cannot be used for a file name
The following reserved words for Microsoft

Windows

cannot be used as a file name.

COM1 to COM9, PRN, LPT1 to LPT9, NULL, AUX, CLOCK$, CON

3) How to specify a file name in the sequence program
Since the sequence program is not case-sensitive, the file can be named by both upper-case and lower-case
characters.
*Both "ABC" and "abc" are treated as "ABC".
In double-byte characters, an upper-case character and lower-case character are distinguished. Name a file
by an upper-case character.
*"ABC" and "abc" are distinguished.

(b) Date and time
The date and time when a file was written to the CPU module is shown.
The date and time are appended according to the clock set on the GX Developer (personal computer) side.

(c) Size
The file size when the file was written from GX Developer to the CPU module is shown in units of bytes (To
display the latest data, select [Online]

[Read from PLC] and click the Refresh view button). At least 64

bytes (136 bytes for a program) are added to the file created by an user except a file register file.
(

Section 5.3.3)

5 - 27

5.1 Memories Used for CPU Module
5.1.9 Details of written files

An extension is automatically appended according to the type set when the file was created.

5.1.10 Specifying valid parameters (parameter-valid drive setting)
Drives (memories) storing valid parameters are automatically specified by the system.
The valid parameters are determined by the priority of the drives where parameters are stored.
Settings by an user is unnecessary.

(1) Priority of the parameter-valid drives
Table5.6 provides the priority of the drives where parameters are stored.
Write parameters to be validated to the higher priority drives.
Table5.6 Priority of the drives
Priority
High

Low

Parameter drive
1

Drive 0 (program memory)

Drive 1 (memory card RAM)

Drive 2 (memory card ROM)

Drive 3 (standard ROM)

Figure 5.23 provides the operation flowchart for the CPU module to select parameter drives.
Start

Are there the
parameters (boot file setting)
in the memory card?

No boot file setting

The boot file setting
is stored.
Boot data to the specified
transfer destination following the
boot file setting parameters in the
memory card (If the destination is
the program memory, the data
are also transferred to the
program cache memory).

Are there the
parameters in
the program
memory?

No
(No parameters in the program memory)

Yes (The parameters
are stored in the
program memory.)
Start the program by the
parameters in the program
memory.

Are there the
parameters in the
memory card?

No
(No parameters in the memory card)

Yes (The parameters
are stored in the
memory card.)
Start the program by the
parameters in the memory card.

Are there the
parameters in the
standard ROM?

No (No parameters in
the standard ROM)

Yes (The parameters
are stored in the
standard ROM.)
Start the programs by the
parameters in the standard ROM.

End

Figure 5.23 Flowchart to specify drives storing parameters

5 - 28

Error since parameters
are not stored

CHAPTER5 MEMORIES AND FILES USED FOR CPU MODULE

(2) When to determine valid parameters
The CPU module automatically searches for parameters in the following timing and operates by the settings of
the parameters stored in the drives when:
• the CPU module is powered off and then on, or

• it is reset.
When storing parameters by Write to PLC in GX Developer, the timing for validating the parameters depends on

the drive that stores the parameters.

(a) When parameters are stored to the drive different from the one that stores the parameters in

operation
The parameters are validated according to the priority set to the drive after the CPU module is powered off and
then on or is reset.

(b) When parameters are stored to the drive same as the one that stores the parameters in
operation
Only the setting made in the Device tab of the PLC parameter dialog box is validated after “Write to PLC” is

performed.
To validate all parameter settings, power off and then on or reset the CPU module.

7
8

5.1 Memories Used for CPU Module
5.1.10 Specifying valid parameters (parameter-valid drive setting)

5 - 29

5.2 Program File Structure
A program file consists of a file header, execution program, and reserved area for online change.
Program file structure
34 steps
(By default)

File header
Execution program

These areas are reserved in units
of file sizes. (
Section 5.3.4)

Reserved area for
online change

500 steps

Figure 5.24 Program file structure

(1) Details of each structure
The capacity of the programs stored in the CPU module program memory is the total of above three areas.

(a) File header
This area stores the name, size, and created date of files.
The file header size ranges from 25 to 35 steps (100 to 140 bytes) depending on the setting made in the Device
tab of the PLC parameter dialog box (34 steps is set by default).

(b) Execution program
This area stores the created program.

(c) Reserved area for online change
This area is used when the number of steps is increased after writing data in the RUN status from GX
Developer.
When such operation is performed, the remaining reserved area for online change is shown.

1) Default
500 steps (2000 bytes) is set by default.

2) Setting change
To change the number of steps, select [Online]

[Write to PLC]

<> tab in GX Developer.

This setting can be made when data are written in the RUN status. (

5 - 30

Section 6.12.1)

CHAPTER5 MEMORIES AND FILES USED FOR CPU MODULE

(2) Displaying the program capacity on the GX Developer screen
During programming by GX Developer, the program size (total of the file header size and the number of steps in
the created program) is displayed by the number of steps as shown in Figure 5.25.

The program size is displayed.

3
4
5

Figure 5.25 Displaying the program size

6
●

The program size displayed during programming by GX Developer is the total of the file header and
execution program, and the capacity of the reserved area for online change (500 steps) is not included.

Example The size of program having the execution program area of 491 steps is displayed on the GX
Developer screen as shown below (The file header is fixed to 34 steps).

8
File header

34 steps

Execution program

491 steps

Figure 5.26 File status displayed on the GX Developer screen

●

Since files are stored in units of file sizes in the program memory, the program size displayed during
programming by GX Developer may differ from the program file size in the CPU module.
(
Section 5.3.3)

5 - 31

5.2 Program File Structure

Display on the GX Developer screen:
34 steps + 491 steps = 525 steps

5.3 File Operations by GX Developer and Handling Precautions
5.3.1 File operations
Table5.7 shows the functions can be performed to files stored in the program memory, standard ROM, and memory
card by the online functions of GX Developer.
However, the executable operations depends on the password registration setting by GX Developer and CPU module
status (RUN/STOP).
Table5.7 File operations executable from GX Developer
Operability
File operation

Read from PLC

Operation detail

While write

While write/read

protection

password is set

to the file

While the CPU
module is in the
RUN status

Reads a file from the target memory.
Writes a file to the program memory or

Write to PLC

SRAM card.
Writes a file to the standard ROM.

Verify with PLC

Verifies the file in the target memory and
the file of GX Developer.

Write the program memory to

Batch-writes files stored in the program

ROM

memory to the Flash card.

Write to PLC (Flash ROM)

Batch-writes specified files from GX
Developer to the Flash card.

Format PLC memory

Formats a memory.

Arrange PLC memory

Rearranges files stored in a memory at
random.

Online change (ladder mode)

Writes data changed in the ladder mode to
the program memory.
: Executable,

5 - 32

: Executable when entered password matches,

: Cannot be executed

CHAPTER5 MEMORIES AND FILES USED FOR CPU MODULE

5.3.2 Precautions for handling files

(1) Power-off or reset at file operation
When the CPU module is powered off or reset at file operation, files in each memory are held (for a memory card,
when the CPU module where a memory card has been mounted before power-off is powered on).

2
3

When the programmable controller is powered off during an operation in which a file is moved, the data in operation are held
in the internal memory of the CPU module.
The held data are recovered at power-on.
To hold the internal memory data, battery backup is required.

4
5

(2) Concurrent writing from multiple GX Developers to one file
GX Developers other than the one writing data to a file cannot access the file until the writing ends.
Also, GX Developers other than the one accessing a file cannot write data to the file until the access ends.

Therefore, write data to one file from multiple GX Developers one by one.

(3) Concurrent access from multiple GX Developers to different files
Except the currently viewed GX Developer, maximum 10 GX Developers can access to different files in one CPU
module concurrently.

5.3 File Operations by GX Developer and Handling Precautions
5.3.2 Precautions for handling files

5 - 33

5.3.3 File size
The size of a file used for the CPU module depends on the file type.
When a file is written to the memory area, the unit of the stored file depends on the CPU module and memory area to
be written. (

Section 5.3.4)

When using the program memory, standard RAM, standard ROM, or memory card, calculate the rough size of each file
with reference to Table5.8.
Table5.8 Calculation of file size
Function
Drive heading

Rough file size (unit: Byte)
72
Default: 464 (can be increased by parameter setting.)*1
Reference
Boot setting

84 + (18

(number of files))*2

• With CC-Link IE controller network setting
• 72 + (total parameter sizes of each module) + (size of the routing setting) + (size of the data link transfer
setting)
• Parameter size of each module: Up to 10368 (when only LB/LW(1) is set, 1826 + 16

(number of

refresh transfer points))
• Routing setting size: 6 + 8

(number of routing settings)

• Size of data link transfer setting: 6 + 12
Parameter

• With the MELSECNET/H setting

(number of transfer settings) + 86

(number of modules)

Increase up to 6180/module

• With the Ethernet setting

Increase up to 922/module

• With the CC-Link setting

Increase up to the values in the following table (The values indicate an

increment of each module).
CC-Link setting

Mode setting
Ver.1 mode

Ver.2 mode

Ver.2 additional mode

1st module

550 bytes

572 bytes

624 bytes

2nd to 4th modules

536 bytes

558 bytes

610 bytes

5th module

550 bytes

566 bytes

618 bytes

6th to 8th modules

536 bytes

558 bytes

610 bytes

• With the remote password setting
Sequence program

148 + (4

92 + (number of target modules

10), increase up to 172/module

((number of steps) + (number of steps of reserved area for online change)))

74 + 8 + (total comment data size of each device)
Device comment

Comment data size per device = 10 + 10250

a + 40

• a: Quotient of ((number of device points)/256)
• b: remainder of ((number of device points/256))

Initial device value
User setting area
*6

File register

66 + 44

n+2

(total number of device points set to the initial device value) + 8

n: number of settings of the initial device value
Setting value at formatting (0 to 15K)
2

(number of file register points)
(To the next page)

5 - 34

CHAPTER5 MEMORIES AND FILES USED FOR CPU MODULE

Table5.8 Calculation of file size(continued)
Function

Rough file capacity (unit: Byte)
362 + (number of word device points + number of bit device points)
word device points

2 + (number of bit device points/16)

12 + (N1 + N2 + N3 + number of

executions)*4
• Apply the following values to N1 to N3 according to the items set in "Trace additional information" of the

Sampling trace file*6

Trace condition settings screen. (

Section 6.14(4)(b))

N1: When "Time" is set, apply "4".
N2: When "Step no." is set, apply "10".
N3: When "Program name" is set, apply "8".
Device data backup file
Module error collection

3
4

Setting value at formatting (2 to 1024K)
file*8

76 + (64
72 + 6

(value set for the number of storable errors))
(set device type) + 2

((total number of M and V points)/16 + (number of D points) + 18

number of T, ST, and C points)/16))

(total

(number of programs where local devices are used*5)

• M, V, D, T, ST, and C indicate the following set devices.
M: internal relay
V: edge relay
D: data register
T: timer
ST: retentive timer
C: counter

Local device*6

7
8

Z: index register*7

(
Appendix 2)
*8: When using the module error collection, check the versions of the CPU module and GX Works2.
Appendix 2)

Remark
For calculation example of memory capacity, refer to Section 5.3.4.

5 - 35

5.3 File Operations by GX Developer and Handling Precautions
5.3.3 File size

*1: The value is adjusted by the system so that the total bytes with the addition of the network parameter setting may be multiple of four.
*2: The value is adjusted by the system so that the bytes may be multiple of four.
*3: 148 is set by default (This value depends on the parameter setting).
*4: After the decimal point of a value found by the number of bit device points/16 is rounded up.
*5: For the Universal model QCPU, if the serial number (first five digits) is "10011" or earlier, apply the number of execution programs.
*6: The Q00UJCPU does not support this function.
*7: When using the index register as a local device for the Q03UDCPU, Q04UDHCPU, Q06UDHCPU, Q13UDHCPU, Q26UDHCPU, or
Built-in Ethernet port QCPU, check the versions of the CPU module and GX Developer.

(

the number of traces (total number of

5.3.4 Units of file sizes
(1) Definition
When a file is written to the memory area, the unit of the stored file depends on the CPU module and memory
area to be written. This unit is referred to as a file size unit.

(a) File size unit for each memory area
The following table shows the file size unit depending on the CPU module and memory area to be written.
Table5.9 File size unit for each CPU module and memory area
Memory area

CPU module model

Program memory, standard ROM, Flash card*1

Standard RAM

Program memory: 1 step/4 bytes

Q00UJCPU

Standard ROM: 64 steps/256 bytes
Program memory: 1 step/4 bytes

Q00UCPU, Q01UCPU

Standard ROM: 128 steps/512 bytes

Q02UCPU, Q03UDCPU,
Q04UDHCPU,Q06UDHCPU,

Program memory: 1 step/4 bytes

Q03UDECPU, Q04UDEHCPU,

Standard ROM, Flash card: 128 steps/512 bytes

Q06UDEHCPU

512 bytes

Program memory: 1 step/4 bytes

Q10UDHCPU,Q10UDEHCPU,Q13U

Standard ROM: 256 steps/1024 bytes

DHCPU,Q13UDEHCPU

Flash card: 128 steps/512 bytes
Program memory: 1 step/4 bytes

Q20UDHCPU,Q20UDEHCPU,Q26U

Standard ROM: 512 steps/2048 bytes

DHCPU,Q26UDEHCPU

Flash card: 128 steps/512 bytes

*1: The file size unit of the Flash card is applied when a file is written to the Flash card by [Online]
memory to ROM] in GX Developer. (

[Write the program

Section 5.1.7(1)(a))

(b) File size unit for each memory card
Table5.10 File size unit for each memory card
Type

SRAM card

Flash card*1

ATA card

Memory card model

File size unit
(cluster size)

Q2MEM-1MBS

512 bytes

Q2MEM-2MBS

1024 bytes

Q3MEM-4MBS

1024 bytes

Q3MEM-8MBS

4096 bytes

Q2MEM-2MBF

1024 bytes

Q2MEM-4MBF

1024 bytes

Q2MEM-8MBA

4096 bytes

Q2MEM-16MBA

4096 bytes

Q2MEM-32MBA

2048 bytes

*1: The file size unit of the Flash card is applied when:
•file is written to the Flash card by [Online]
[Write to PLC (Flash ROM)] in GX Developer.
(

Section 5.1.7(1)(b))

•file is written to the Flash card by GX Developer without accessing the CPU module

5 - 36

CHAPTER5 MEMORIES AND FILES USED FOR CPU MODULE

(2) Calculation example of memory capacity
The following shows an calculation example of memory capacity when the parameters and sequence program
are written to the program memory.

(a) Conditions
1) CPU module to be written: Q26UDHCPU

2) Writing file
Table5.11 File sizes

File size*1

File name
PARAM.QPA (parameter file)

464 bytes
525 steps/2100 bytes*2

MAIN.QPG (sequence program)

*1: For the file size, refer to (1)(a) in this section.
*2: This indicates the program size (file header + execution program) displayed on the GX Developer screen.
(

Section 5.2)

3) Reserved area for online change: 500 steps/2000 bytes

(b) Memory capacity calculation
The memory capacity is calculated in units of file sizes of the CPU module to be written.
The file size unit of the Q26UDHCPU in this example is 1 step/4 bytes.(

(1) in this section)

1) Calculation of parameter file size
Since the parameter file size is 464 bytes, 116 steps/464 bytes is occupied in the program memory.
5.3 File Operations by GX Developer and Handling Precautions
5.3.4 Units of file sizes

Parameter file
(464 bytes)

4 bytes
4 bytes
The parameter file
occupies 464 bytes
(116 steps).

This file is stored in
units of file sizes
(1 step/4 bytes).
4 bytes
Program memory
capacity

Figure 5.27 Occupation in units of the file size (parameter file)

5 - 37

2) Calculation of program size
The program size is found by the formula: sequence program size + reserved area for online change.
Since a program is stored in units of file sizes (1 step), only the amount equal to the program size is occupied.

3) Result
The calculation results of the memory capacities are as shown below.

Table5.12 Calculation results of memory capacities

File name

File size

Memory capacity

PARAM.QPA

464 bytes

116 steps (464 bytes)

Sequence program size
MAIN.QPG

Reserved area for online
change
Total
Total memory capacity

5 - 38

525 steps
500 steps

1025 steps (4100 bytes)

1025 steps
1141 steps (4564 bytes)

CHAPTER6 FUNCTIONS

This chapter describes the functions of the Universal model QCPU.

6.1 Function List

Table6.1 lists the functions of the Universal model QCPU.
Table6.1 Function list
Item

Constant scan
Latch function
Output status selection
when the status changed
from STOP to RUN
Clock function
Remote RUN/STOP

Description

Q00UJ
CPU

Q00UCPU,
Q01UCPU

Q02U
CPU

Executes a program in a set time interval

QnUD(H)
CPU

Built-in
Ethernet
port QCPU

Reference

Section 6.2

regardless of its scan time.
Holds the device data even at power OFF

4
5

Section 6.3

or reset.

Selects the output (Y) status (outputting
the same status prior to STOP or clearing

Section 6.4

the status) when the CPU module status

is switched from STOP to RUN.
Reads the internal clock data of the CPU

Section 6.5

module to use it for time management.
Runs or stops the program operations in

Section 6.6.1

the CPU module externally.

Stops the program operations in the CPU
Remote PAUSE

module externally, holding the status of

Section 6.6.2

outputs (Y).
Resets the CPU module externally when

Section 6.6.3

the CPU module is in a STOP status.
Clears the latch data in the CPU module

Remote latch clear

when the CPU module is in a STOP

Section 6.6.4

status.
Selects input response time values for
Input response time

the Q series-compatible input modules, I/

selection

O combined modules, high-speed input

Section 6.7

modules, and interrupt modules.
Sets whether to clear or retain the output
to the Q series compatible output
Error time output mode

modules, I/O combined modules,

setting

intelligent function modules, and interrupt

Section 6.8

modules at the time of a stop error of the
CPU module.
Sets whether to stop or continue
H/W error time PLC
operation mode setting

operations in the CPU module when a
hardware error has occurred in an

Section 6.9

intelligent function module or interrupt
module.
: Supported,

: Partly supported, : Not supported
(To the next page)

6-1

6.1 Function List

Remote RESET

Table6.1 Function list (Continued)
Item

Description

Q00UJ
CPU

Q00UCPU,
Q01UCPU

Q02U
CPU

QnUD(H)
CPU

Built-in
Ethernet
port QCPU

Reference

Makes settings for the intelligent
Intelligent function module
switch setting

function modules and interrupt

Section

modules. (Refer to manuals of

6.10

intelligent function modules and
interrupt modules for setting details.)
Reads the status of programs and

Monitor function

Section

devices in the CPU module by GX

6.11

Developer.
Specifies the monitoring timing of the
Monitor condition setting

CPU module with device condition or

step number.
Monitors and/or tests the local
Local device monitor/test

devices of the specified program by
GX Developer.

External input/output forced
on/off
Executional conditioned
device test
Online change

Forcibly turns on/off the external
input/output of the CPU module by

GX Developer.
Changes a device value within the
specified step of a sequence
program.
Writes programs when the CPU

6.11.4

Section
6.13.2

area specified by the steps in a

Continuously samples the specified

multiple GX Developers.

Section
6.13.3
Section

device data at a preset timing.
Enables simultaneous debugging by

6.14
Section
6.15

Monitors operational delays caused

Section

by hardware failure or program error

6.16

of the CPU module.

Error history

Section

interrupt programs.

GX Developers

Self-diagnostic function

6.11.3

Displays the number of executions of

Debug function from multiple

Watchdog timer

Section

6.13.1

program.
Sampling trace function

6.11.2

Section

status of the program being

Measures the execution time of the
Scan time measurement

Section

6.12

executed.
Interrupt program monitor list

6.11.1

Section

module is in the RUN status.
Displays the scan time and execution

Program monitor list

Section

Self-diagnoses the CPU module to

Section

see whether an error exists or not.

6.17

Stores the result of self-diagnostics

Section

to the memory as error history data.

6.18

Prevents the programs from being
System protection

modified from GX Developer, serial

Section

communication module, and

6.19

Ethernet module.
: Supported,

: Partly supported, : Not supported
(To the next page)

6-2

CHAPTER6 FUNCTIONS

Table6.1 Function list (Continued)
Item

Q00UJ
CPU

Description

Q00UCPU,
Q01UCPU

Q02U
CPU

QnUD(H)
CPU

Built-in
Ethernet
port QCPU

Prohibits writing/reading data to/from
Password registration

Reference

Section

each file in the CPU module using GX

6.19.1

Developer.

Prevents unauthorized access from
Remote password

external devices such serial

Section

communication module and Ethernet

6.19.2

module.
System display

Monitors the system configuration

Section

using GX Developer.

Section

CPU module with LEDs on the front

6.21

of the module.
Sets whether to indicate an error with
LED indication priority

Section
6.21.2

LED according to the priority of each
error.

Interrupt from intelligent
function module

Serial communication
function

Executes an interrupt program at the

Section

time of interrupt request from the

6.22

intelligent function module.
Connects the RS-232 interface of the CPU
module and the personnel computer or
HMI with RS-232 cable and communicates
in the MC protocol.

Section

6.23

Specifies the service processing
Service processing setting

Section

the intelligent function modules and

6.25

special function modules without
programs.
Prolongs a battery life by holding only
clock data in the battery.

Section
6.26

Checks whether data in the memories
Memory check function

Section

of the CPU module are not changed

6.27

due to excessive electric noise.
Latch data backup to
standard ROM function

Backs up latch data such as device

Section

data and error history without using a

6.28

battery.

Writing/reading device data

Writes/reads device data to/from

to/from standard ROM

standard ROM.

CPU module change function
with memory card

Backs up data in the CPU module to a
memory card and restores the backup data
to another CPU module.

Module model name read*1

Reads the model name of a module on a
base unit.

Section

Module error collection*1

Collects errors occurred in the connected
intelligent function modules in the CPU
module.

Section

Section
6.29
*1

Section
6.30

6.31

6.32
: Supported,

*1: Availability depends on the version of the CPU module. (

7
8

: Partly supported, : Not supported

Appendix 2)

6-3

6.1 Function List

devices and the buffer memories of

function

6.24.1

Registers data used in programs with

Battery life-prolonging

Section

count or time to be executed in END
processing.

Initial device value

6.20

Displays the operating status of the
LED indication

6.2 Constant Scan
(1) Definition
Scan time of the CPU module is not constant because the processing time varies depending on the
execution status of instructions used in a sequence program.
This function allows sequence programs to be executed repeatedly, maintaining its scan time
constant.

(2) Application
I/O refresh is performed before every sequence program execution.
This function is used to maintain I/O refresh intervals constant even if the execution time of each
sequence program differs.
Scan time without constant scan setting
Sequence program
END 0

END

END processing
END 0

5ms

END 0
5ms

6ms

Scan time with constant scan setting (7ms)
Sequence program
END 0

END

Waiting time
5ms

END processing
END
0

2ms

7ms

6ms

END

5ms

1ms

7ms

2ms

7ms

Scan time for multiple programs with constant scan setting (10ms)
Sequence program A
Sequence program B
Sequence program C
END processing

Waiting time
8ms
10ms

2ms

9ms
10ms

Figure 6.1 Constant scan operation

6-4

1ms

CHAPTER6 FUNCTIONS

(3) Constant scan time setting
Set a constant scan time value in the PLC RAS tab of the PLC parameter dialog box.
The setting range is 0.5 to 2000ms (in increments of 0.5ms).
When not executing the constant scan function, leave the constant scan time setting box blank.

2
3
4

Set a constant scan
time value here.

5
6
Figure 6.2 When the constant scan time is set to 10ms

(a) Condition
The constant scan time needs to satisfy the following relational expression.

(WDT setting time) > (Constant scan setting time) >
(Sequence program maximum scan time)

If the sequence program scan time is longer than the constant scan setting time, the CPU module
In this case, the constant scan setting will be ignored and the sequence program scan time will be
applied.
Constant scan setting (4ms)

Constant
scan
Sequence
program

END

3.5ms
4ms

END 0
0.5ms

END

3.5ms
5.3ms

4ms

END

4 ms

0.5ms
3.4ms

0.6ms

4ms

Scan where the constant scan setting is not applied
Figure 6.3 Operation when the scan time is longer than the constant scan setting time

If the sequence program scan time is longer than the WDT setting time, the CPU module detects
“WDT ERROR”.
In this case, the program execution will be stopped.

6-5

6.2 Constant Scan

detects “PRG. TIME OVER” (error code: 5010).

(4) Waiting time from when END processing is executed until next scan starts
Sequence program processing is stopped during the waiting time from when END processing of a
sequence program is executed until next scan starts.
(a) When an interrupt factor occurs during waiting time
Either of the following programs is executed.
• Interrupt program
• Fixed scan execution type program

(b) When a service processing parameter is set
The communication service processing with peripherals (such as GX Developer) and intelligent function
modules is enabled during the waiting time by setting a service processing parameter. (

Section 6.24.1)

(5) Constant scan accuracy
The constant scan accuracy is 0.01ms.
However, when any program indicated below is being executed, the constant scan time may increase.
(a) Interrupt program or fixed scan execution type program
Interrupts are disabled while an interrupt program or fixed scan execution type program is executed.
Even if the constant scan time runs out during execution of an interrupt program or fixed scan
execution type program, the constant scan cannot be finished.
In this case, the constant scan time may increase by the execution time of the program executed.

6-6

CHAPTER6 FUNCTIONS

6.3 Latch Function

(1) Definition

This function holds data in each device of the CPU module when:
• the CPU module is powered off and then on,
• the CPU module is reset, or

• power failure occurs exceeding the allowable momentary power failure time.
Data in each device of the CPU module is cleared and set back to its default (bit device: off, word

device: 0) without using the latch function.

(2) Application
This function is used to hold the data managed by sequential control and continue control operation

especially when the CPU module is powered off and then on.

(3) Program operation when the latch function is use
Program operation is the same, regardless of the latch status.

(4) Devices that can be latched
The following devices can be latched.(By default, only the latch relay is enabled for latch.)

• Latch relay (L)
• Link relay (B)
• Annunciator (F)

6.3 Latch Function

• Edge relay (V)
• Timer (T)
• Retentive timer (ST)
• Counter (C)
• Data register (D)
• Link register (W)

When the battery life-prolonging function (
latched.

Section 6.26) is set, the latch relay cannot be

6-7

(5) Latch range setting
Set a latch range in the Device tab of the PLC parameter dialog box.
There are two types of latch range settings: the latch clear operation enable range setting (Latch (1))
and the latch clear operation disable range setting (Latch (2)).

Figure 6.4 Latch range setting

The latch range of the file register (ZR), extended data register (D), and extended link register (W) can also be
set.
After selecting "Use the following file." and setting the capacity of the file register in the PLC file tab of the PLC
parameter dialog box, set a latch range of the file register (ZR), extended data register (D), and extended link
register (W). (For the extended data register (D) and extended link register (W), assign a part of the file register
area.)
If "Use the same file name as the program." is selected in the PLC file tab of the PLC parameter dialog box, a
latch range of the file register (ZR), extended data register (D), and extended link register (W) cannot be set.
(All data in the file register will be latched.)
The data outside the latch range will be cleared when the CPU module is powered off and then on or is reset.
The file register points set
in the PLC file tab is displayed.

Set a latch range.

Figure 6.5 Latch range setting

When the file register file to be used is switched with the QDRSET instruction, the latch range setting of the file
register will be invalid.
After switching, regardless of the latch range setting, whole range of the file register will be latched.

6-8

CHAPTER6 FUNCTIONS

(6) Device data latch method and influence on the scan time
Data latch processing is performed during END processing.
For this reason, the scan time increases.
Consider an influence on the scan time when latching devices. (

Section 10.1.2)

3
To shorten the scan time due to latch, minimize the number of latch points (latch (1) setting, latch (2) setting,
and latch relay (L)) as much as possible.
The number of latch points can be reduced by performing the following.
• Move data to be latched to the file register.
• Store device data that is less frequently updated in the standard ROM with the SP.DEVST instruction.
(The device data stored in the standard ROM can be read with the S(P).DEVLD instruction.)
QCPU Programming Manual (Common Instructions)

4
5
6

(7) Device data latch clear
Table6.2 shows the status of device data when the latch clear operation is performed.

Table6.2 Status when the latch clear operation is performed
Latch setting

Status of data

Device data without latch setting

Cleared

Device data in the "Latch (1)" range

Cleared

Device data in the "Latch (2)" range

Held

*1: For the clearing method, refer to Section 3.7.
6.3 Latch Function

Data in the file register (R or ZR) will not be cleared by the latch clear operation.
To clear data in the file register (R or ZR), perform data clear operation by a sequence program or GX Developer.
(

Section 9.7.3)

(8) Precautions
(a) When a local device or initial device value is specified
Device data cannot be latched even if the device has been latch-specified,
(b) Use of battery
Device data in the latch range are held with the battery installed to the CPU module.
• Even for the boot operation, the battery is required to latch device data.
• Note that if the battery connector is disconnected from the connector of the CPU module while
the power supply for the programmable controller is off, device data in the latch range will not
be held and will become undefined.

6-9

6.4 Output Mode at Operating Status Change (STOP to RUN)
(1) Definition
When the operating status is changed from RUN to STOP, the CPU module internally stores the
outputs (Y) in the RUN status and then turns off all the outputs (Y).
The status of the outputs (Y) when the operating status of the CPU module is changed back from
STOP to RUN can be selected from the following two options in the parameter setting in GX
Developer.
• Output the output (Y) status prior to STOP. (“Previous state”)
• Clear the output (Y) status. (“Recalculate (output is 1 scan later)”)

(2) Application
This function is used to determine the status of outputs (whether to resume the outputs from the
previous status or not) when the operating status is changed from STOP to RUN in the holding circuit.
Start Stop
button button

Figure 6.6 Holding circuit

• When outputting the output (Y) status prior to STOP
ON

RUN

STOP

RUN

X20 OFF
X21 OFF

ON
Y0 OFF
Figure 6.7 Timing chart when the parameter is set to "Previous state"

• When clearing the output (Y) status
RUN

STOP

RUN

ON
X20 OFF

X21 OFF
ON
Y0 OFF
Figure 6.8 Timing chart when the parameter is set to "Recalculate (output is 1 scan later)"

6 - 10

CHAPTER6 FUNCTIONS

(3) Operation when the operating status is changed from STOP to RUN

(a) Previous state (Default)
The CPU module outputs the output (Y) status immediately before changing to the STOP status and
then performs sequence program operations.

(b) Recalculate (output is 1 scan later)

All outputs are turned off.
The CPU module outputs the output (Y) status after sequence program operations are completed.
For the operation of the CPU module when the output (Y) status is forcibly turned on in the STOP
status, refer to (5) in this section.

Operating status change (STOP to RUN)

5
NO ("Recalculate (output is 1 scan later)" is set.)
Is "Previous state" set?

YES ("Previous state" is set.)
The output (Y) status immediately before
changed to the STOP status is output.

Sequence program operations
are performed.

Figure 6.9 Operation when the operating status is changed from STOP to RUN

Set the output mode when the operating status is changed from STOP to RUN in the PLC system tab
of the PLC parameter dialog box.

Set the output
mode here.

Figure 6.10 PLC system setting

6 - 11

6.4 Output Mode at Operating Status Change (STOP to RUN)

(4) Setting the output mode when the operating status is changed from STOP to RUN

(5) Precautions
Table6.3 shows the output status of the CPU module when the operating status is changed from STOP

to RUN after the outputs (Y) are forcibly turned on in the STOP status.
Table6.3 Output status when the operating status is changed from STOP to RUN after the output forced on operation is performed

Output mode ("Output mode at STOP to RUN") selected

Output status
The output status prior to STOP is output.

Previous state

Even if the outputs are forcibly turned on, the on status is not held if
the output status prior to STOP was off.

Recalculate (output is 1 scan later)

6 - 12

The on status is held and output.

CHAPTER6 FUNCTIONS

6.5 Clock Function

(1) Definition
This function reads the internal clock data of the CPU module by a sequence program and uses it for

time management.
The clock data is used for time management required for some functions in the system, such as storing date into
the error history.

Remark
The Built-in Ethernet port QCPU can set the time in the CPU module automatically by using the time setting function
(SNTP client).
QnUCPU User’s Manual (Communication via Built-in Ethernet Port)

3
4
5
6

(2) Clock operation at power off and momentary power failure
Clock operation continues by the internal battery of the CPU module even when the programmable
controller is powered off or power failure occurs exceeding the allowable momentary power failure
time.

(3) Clock data

7
8

Table6.4 shows the details of clock data, which is used internally in the CPU module.
Table6.4 Clock data details
Description

Year

Four digits (from 1980 to 2079)

Month

1 to 12

Day

1 to 31 (Automatic leap year detection)

Hour

0 to 23 (24 hours)

Minute

0 to 59

Second

0 to 59

Day of the week

Sunday

Monday

Tuesday

Wednesday

Thursday

Friday

Saturday

6.5 Clock Function

Data name

6 - 13

(4) Changing and reading clock data
(a) Changing clock data
Clock data can be changed either by GX Developer or a program.
1) Changing clock data by GX Developer
Select [Online]

[Set time] to open the Set time screen and change the clock data.

Figure 6.11 Set time screen

2) Changing clock data by a program
Use the DATEWR instruction (instruction for writing clock data) to change the clock data.
Figure 6.12 shows a program for writing the set clock data to D0 to D6.
Write request
X0
0

MOVP K1999

Year 1999

MOVP

Month 8

MOVP

K10

Day 10

MOVP

K11

Hour 11

MOVP

K35

Minute 35

MOVP

K24

Second 24

MOVP

Day of the week
Tuesday: 2

DATEWR

Figure 6.12 Program example for writing clock data

For details of the DATEWR instruction, refer to the following.
QCPU Programming Manual (Common Instructions)

6 - 14

●

When clock data is changed, the clock of 1/1000 second is reset to 0.

●

Year data settable by GX Developer is up to 2037.

CHAPTER6 FUNCTIONS

(b) Reading clock data
To read clock data to the data register, use either of the following instructions in the program.
• DATERD (instruction for reading clock data)

• S(P).DATERD (instruction for reading extended clock data)
Figure 6.13 shows a program for storing the clock data read with the DATERD instruction to D10 to

D16.
Read request
X1
DATERD

Figure 6.13 Program example for storing clock data

*1: Figure 6.14 shows the clock data stored in D10 to D16.

D10
D11
D12
D13
D14
D15
D16

2004
4
1
11
35
24
2

Year (four digits)

Month
Date
Hour
Minute
Second

3
4

Stores clock data to D10
to D16.*1

D10

(

(3) in this section)

Day of the week

Figure 6.14 Clock data stored

For details of the DATERD and S(P).DATERD instructions, refer to the following.
QCPU Programming Manual (Common Instructions)

6 - 15

6.5 Clock Function

Clock data can also be written or read by the special relay (SM210 to SM213) and special register (SD210 to SD213).
For details of the special relay and special register, refer to CHAPTER 12.

(5) Precautions
(a) Initial clock data setting
No clock data is set at the factory.
Clock data is required for some functions of the CPU module used in the system, such as error
history storage, or for intelligent function modules.
Before using the CPU module for the first time, set the time correctly.

(b) Clock data correction
If a part of the clock data is corrected, rewrite the entire clock data to the CPU module.

(c) Clock data setting range
When changing clock data, write data within the range given in (3) in this section.
If data outside of clock range is written to the CPU module, the clock function does not operate normally.
However, the CPU module does not detect an error if the clock data is out of the range.
Table6.5 Example of clock data
Write operation to the CPU module
February 30

Executed

32 of month 13

Not executed

CPU module operation
An error is not detected.
When the DATEWR instruction is executed, "OPERATION ERROR" (error
code: 4100) is detected.
When SM210 is turned on, SM211 turns on.

(d) Use for clock data of 1/1000 sec.
1) Function that clock data of 1/1000 sec. can be used
Only the following instructions can use the clock data of 1/1000 sec.
• S(P).DATERD
• S(P).DATE+
• S(P).DATEOther instructions cannot use the clock data of 1/1000 sec.
(Such as for reading data by SM/SD, storing the time of error occurrence as error history data, reading data
by GX Developer, or reading data by dedicated instructions of other modules.)

2) When clock data is changed
When clock data is changed by GX Developer or instructions (including dedicated instruction of other
modules), the clock of 1/1000 sec. is reset to 0.

6 - 16

CHAPTER6 FUNCTIONS

(6) Clock data accuracy
Accuracy of the clock data varies depending on the ambient temperature as shown below.

Table6.6 Clock data accuracy
Ambient temperature ( )

Accuracy (Day difference, S)

-2.96 to +3.74 (TYP.+1.42)

+ 25

-3.18 to +3.74 (TYP.+1.50)

+ 55

-13.20 to +2.12 (TYP.-3.54)

3
4

(7) Clock data comparison
To compare clock data in a sequence program, read the clock data with the DATERD instruction (instruction for
reading clock data).

Since the DATERD instruction reads the year data in four digits, the data can be compared by the comparison

instruction without any modifications.

7
8

6.5 Clock Function

6 - 17

6.6 Remote Operation
Remote operation allows to change the operating status of the CPU module externally (by GX Developer
or external devices using the MC protocol, with link dedicated instructions of the CC-Link IE controller
network module or MELSECNET/H module, or using remote contacts).
There are four types of remote operations:
• Remote RUN/STOP

Section 6.6.1

• Remote PAUSE

Section 6.6.2

• Remote RESET

Section 6.6.3

• Remote latch clear

Section 6.6.4

6.6.1 Remote RUN/STOP
(1) Definition
This operation changes the operating status of the CPU module externally to RUN or STOP, keeping
the RUN/STOP/RESET switch of the CPU module in the RUN position.

(2) Application
This operation is useful to run or stop the CPU module remotely when:
• the CPU module is inaccessible, or
• the CPU module is in a control panel.

(3) Program operation
The program operation will be as follows when the remote RUN/STOP operation is performed.
(a) Remote STOP
The CPU module executes a program until the END instruction and changes its operating status to
STOP.
(b) Remote RUN
The CPU module changes its operating status to RUN and executes a program from the step 0.
(The remote RUN operation must be performed to the CPU module whose operating status has
been changed to STOP by the remote STOP operation.)

6 - 18

CHAPTER6 FUNCTIONS

(4) Executing method

There are three methods for performing the remote RUN/STOP operation.
• Using a RUN contact

• By GX Developer or an external device using the MC protocol
• With link dedicated instructions of the CC-Link IE controller network module or MELSECNET/H
module

(a) Using a RUN contact
Set a RUN contact in the PLC system tab of the PLC parameter dialog box.

The settable device range is X0 to 1FFF.
The remote RUN/STOP operation can be performed by turning on/off the set RUN contact.

• When the RUN contact is turned off, the CPU module status changes to RUN.
• When the RUN contact is turned on, the CPU module status changes to STOP.

Step 0

END
ON

RUN contact

END
0

OFF
RUN
STOP

RUN/STOP status

STOP status
Figure 6.15 Remote RUN/STOP using a RUN contact
6.6 Remote Operation
6.6.1 Remote RUN/STOP

(b) By GX Developer or an external device using the MC protocol
Select [Online]

[Remote operation] in GX Developer.

To perform the remote RUN/STOP operation from an external device, use the MC protocol
command.
Q Corresponding MELSEC Communication Protocol Reference Manual
Step 0

END

Step 0

ON
Remote STOP
GX Developer command
or
External device Remote RUN
command
RUN/STOP status

OFF

END
0

OFF
RUN
STOP

STOP status
Figure 6.16 Remote RUN/STOP by GX Developer or an external device

6 - 19

(c) With link dedicated instructions of the CC-Link IE controller network module or
MELSECNET/H module
The remote RUN/STOP operation by link dedicated instructions of the CC-Link IE controller network
module or MELSECNET/H module can change the RUN/STOP status of the CPU module.
For details, refer to the following.
Reference manual of each network module

(5) Precautions
Pay attention to the following since the STOP status is given priority over the RUN status.
(a) Timing of changing to the STOP status
The operating status of the CPU module is changed to STOP when the remote STOP operation is
performed from any one of the following: RUN contact, GX Developer, or an external device using
the MC protocol.

(b) When changing the status back to RUN
To change the operating status back to RUN after the CPU module status was changed to STOP by the remote
STOP operation, perform the remote RUN operation in the same order for the remote STOP operation.

6 - 20

●

The definitions of the RUN/STOP status are described below.
• RUN status•••A status where sequence program operations are repeatedly performed in a loop between the step
0 and the END or FEND instruction.
• STOP status•••A status where sequence program operations are stopped. All outputs (Y) are turned off.

●

After being reset, the operating status of the CPU module becomes the one set with the RUN/STOP/RESET switch.

CHAPTER6 FUNCTIONS

6.6.2 Remote PAUSE

(1) Definition
This operation changes the operating status of the CPU module externally to PAUSE, keeping the
RUN/STOP/RESET switch of the CPU module in the RUN position.

PAUSE status is a status where sequence program operations in the CPU module are stopped,

holding the status (on or off) of all outputs (Y).

(2) Application
This operation is useful, especially during the process control, to hold the on status of outputs (Y) even

after the operating status of the CPU module is switched from RUN to STOP.

(3) Executing method
There are two methods for performing the remote PAUSE operation.
• Using a PAUSE contact

• By GX Developer or an external device using the MC protocol
(a) Using a PAUSE contact

Set a PAUSE contact in the PLC system tab of the PLC parameter dialog box.
The settable device range is X0 to 1FFF.
• The PAUSE contact (SM204) turns on during END processing of the scan where both the

PAUSE contact and PAUSE enable coil (SM206) turn on.

The CPU module executes one more scan until the END instruction after the scan where the PAUSE
contact turns on, and then changes its operating status to PAUSE. In the PAUSE status, the program
• When the PAUSE contact or SM206 is turned off, the PAUSE status will be canceled and the

CPU module will restart the sequence program operation from the step 0.
0
ON
PAUSE
contact
SM206

END
0

END

END
0

OFF
ON
OFF
ON

SM204

OFF
Turns on when the
PAUSE conditions
are established

RUN/PAUSE
status

RUN

PAUSE

RUN

PAUSE status
Figure 6.17 Remote PAUSE using a PAUSE contact

Setting of only a PAUSE contact is not allowed.
When setting a PAUSE contact, set a RUN contact as well.

6 - 21

6.6 Remote Operation
6.6.2 Remote PAUSE

operations are stopped.

(b) By GX Developer or an external device using the MC protocol
Select [Online]

[Remote operation] in GX Developer.

To perform the remote PAUSE operation from an external device, use the MC protocol command.
Q Corresponding MELSEC Communication Protocol Reference Manual
• The PAUSE contact (SM204) turns on during END processing of the scan where the remote

PAUSE command is executed.
The CPU module executes one more scan until the END instruction after the scan where the PAUSE
contact turns on, and then changes its operating status to PAUSE. In the PAUSE status, the program
operations are stopped.
• Upon execution of the remote RUN command, the CPU module will restart the sequence

program operations from the step 0.
END

0
END

0
ON
Remote PAUSE
command
Remote RUN
command

0
END

OFF
ON
OFF
ON
OFF

SM204

Turns on when the
PAUSE conditions
are established

RUN/PAUSE
status

RUN

PAUSE

RUN

PAUSE status
Figure 6.18 Remote PAUSE by GX Developer or an external device

(4) Precautions
(a) When forcibly keeping output status
To forcibly keep the output status (on or off) in the PAUSE status, provide an interlock with the
PAUSE contact (SM204).
M20

Y70

The on/off status of Y70 is determined by the
on/off status of M20 in the PAUSE status.

Y71

Y71 turns off in the PAUSE status.

Y72

Y72 turns on in the PAUSE status.

SM204

Figure 6.19 Program example for forcibly keeping output status in the PAUSE status

6 - 22

CHAPTER6 FUNCTIONS

6.6.3 Remote RESET

(1) Definition
This operation resets the CPU module externally when the CPU module is in the STOP status.
Even if the RUN/STOP/RESET switch is in the RUN position, this operation can be performed when

the module is stopped due to an error detected by the self-diagnostics function.

(2) Application
This operation is useful to reset the CPU module remotely when an error occurs in the CPU module
placed in an inaccessible location.

(3) Executing method
This operation can only be performed by GX Developer or an external device using the MC protocol.
• Select [Online]

4
5

[Remote operation] in GX Developer.

• To perform the remote RESET operation from an external device, use the MC protocol command.

Q Corresponding MELSEC Communication Protocol Reference Manual

7
Before performing the remote RESET operation, select the "Allow" checkbox for the remote RESET operation
in the PLC system tab of the PLC parameter dialog box, and then write the parameter setting to the CPU
module.
Without the preset parameter setting, the operation cannot be performed.

6.6 Remote Operation
6.6.3 Remote RESET

Select the checkbox
here to enable the
remote RESET
operation.

Figure 6.20 Parameter setting required for the remote RESET operation

6 - 23

(4) Precautions
(a) Remote RESET in the RUN status
When the CPU module is in the RUN status, the remote RESET operation cannot be performed.
To perform the operation, change the operating status of the CPU module to STOP by the remote
STOP or similar operation.
(b) Status after reset processing
After reset processing of the remote RESET operation is completed, the CPU module will be placed
in the operating status set by the RUN/STOP/RESET switch.
If the RUN/STOP/RESET switch is set to STOP, the CPU module will be in the STOP status. If the
switch is set to RUN, the CPU module will be in the RUN status.

●

If the remote RESET operation is performed to the CPU module which is stopped due to an error, note
that the CPU module will be placed in the operating status set by the RUN/STOP/RESET switch after
reset processing is completed.

●

If the CPU module cannot be reset by the remote RESET operation from GX Developer, check that the
"Allow" checkbox for the remote RESET operation in the PLC system tab of the PLC parameter dialog box
is selected.
If the checkbox is not selected, the CPU module cannot be reset even after the remote RESET processing
from GX Developer is completed.

(c) When an error occurs due to noise
Note that the CPU module may not be reset by the remote RESET operation from GX Developer.
In this case, reset the CPU module using the RUN/STOP/RESET switch or power off and then on
the CPU module.

6 - 24

CHAPTER6 FUNCTIONS

6.6.4 Remote latch clear

(1) Definition
This function resets the latched device data from GX Developer or an external device when the CPU
module is in the STOP status.

2
3

(2) Application
This function is useful in the following cases if used together with the remote RUN/STOP operation.
• When the CPU module is inaccessible

• To clear latched device data in the CPU module in a control panel externally

(3) Executing method
This operation can only be performed by GX Developer or an external device using the MC protocol.
• Select [Online]

[Remote operation] in GX Developer.

• To execute the remote latch clear operation from an external device, use the MC protocol

command.
Q Corresponding MELSEC Communication Protocol Reference Manual

To perform the remote latch clear operation, follow the following steps.
1) Change the operating status of the CPU module to STOP by the remote STOP operation.
2) Clear the latched device data in the CPU module by the remote latch clear operation.

3) After remote latch clear processing is completed, perform the remote RUN operation to return the operating
status to RUN.
6.6 Remote Operation
6.6.4 Remote latch clear

(4) Precautions
(a) Latch clear in the RUN status
The latch clear operation cannot be performed when the CPU module is in the RUN status.

(b) Latch clear enabled range
There are two kinds of latch range can be set in the Device tab of the PLC parameter dialog box: latch clear
operation enable and disable range.
Remote latch clear operation resets only the data set in the "Latch (1)" (latch clear operation enable range).
For the method for resetting the device data in the latch clear operation disable range, refer to Section
3.7(2)(c).

(c) Devices that are reset by the remote latch clear operation
Devices that are not latched are also reset when the remote latch clear operation is performed.

6 - 25

6.6.5 Relationship between remote operation and RUN/STOP status of the CPU
module
(1) Relationship between remote operation and RUN/STOP status of the CPU
module
Table6.7 shows the operating status of the CPU module according to the combination of remote operation and
RUN/STOP status.
Table6.7 Operating status of the CPU module
RUN/STOP status

Remote operation
RUN*1

STOP

PAUSE*2

RUN

STOP

PAUSE

STOP

RESET*3
Operation disabled
RESET*5

Latch clear
*4

Operation disabled*4
Latch clear

*1: When performing the operation using a RUN contact, "RUN-PAUSE contact" must be set in the PLC system tab of the PLC
parameter dialog box.
*2: When performing the operation using a PAUSE contact, "RUN-PAUSE contact" must be set in the PLC system tab of the
PLC parameter dialog box.
In addition, the PAUSE enable coil (SM206) must be turned on.
*3: The "Allow" checkbox for the remote RESET operation must be selected in the PLC system tab of the PLC parameter
dialog box.
*4: The remote RESET and remote latch clear operations are enabled if the CPU module status is changed to STOP by the
remote STOP operation.
*5: The STOP status includes a case where the CPU module is stopped due to an error.

(2) Remote operations from a single GX Developer
When remote operations are performed from a single GX Developer, the operating status of the CPU module will
be the status of the last remote operation performed.

(3) Remote operations from multiple GX Developers
Any remote operation from other GX Developers via other stations cannot be performed to the CPU module
where remote operations are being performed from GX Developer connected.
To perform any remote operations from another GX Developer, cancel the remote operation by performing the
remote RUN operation from the same GX Developer that is performing the current remote operation.
For example, even if the remote STOP or RUN operation is performed from another GX Developer to the CPU
module where the remote PAUSE operation has been performed by GX Developer connected, the CPU module
remains in the PAUSE status.
Once after the remote RUN operation is performed from the same GX Developer that is performing the remote
PAUSE operation, remote operations from another GX Developer will be enabled.

6 - 26

CHAPTER6 FUNCTIONS

6.7 Q Series-compatible Module Input Response Time Selection (I/O
Response Time)

1
2

(1) Definition
This function changes the input response time for each Q series-compatible module.
Table6.8 shows the modules available for input response time change and selectable time settings.

Table6.8 Modules available for input response time change
Module name

Type

Input module

“Input”

I/O combined module

“I/O Mix”

High-speed input module

“Hi Input”

Interrupt module

“Interrupt”

Settable time setting

1ms, 5ms, 10ms, 20ms, 70ms
(Default: 10ms)
0.1ms, 0.2ms, 0.4ms, 0.6ms, 1ms
(Default: 0.2ms)

The Q series-compatible modules in the table above take in external inputs within the set time here.

External input

OFF
ON

Q series-compatible module

OFF

Input response time
6.7 Q Series-compatible Module Input Response Time Selection (I/O Response Time)

Figure 6.21 Input response time

6 - 27

(2) Input response time setting
Set input response time values in the I/O assignment tab of the PLC parameter dialog box.
1) Make I/O assignment for the target module.
2) Click the Detailed setting button.
3) On the screen opened, select an input response time value (“I/O response time”).
2) Click the Detailed setting button.

1) Make I/O assignment.

3) Select the input response time.

Figure 6.22 Input response time setting

(3) Precautions
(a) When input response time is shortened
The shorter the input response time is, the more the CPU module is susceptible to noise.
Consider the operating environment when setting input response time values.

(b) Enabling the setting
The input response time setting will be enabled when:
• the CPU module is powered off and then on, or
• the CPU module is reset.

6 - 28

CHAPTER6 FUNCTIONS

6.8 Error Time Output Mode Setting

(1) Definition
This function determines the output mode (clear or hold) from the CPU module to the Q series-

compatible output modules, I/O combined modules, intelligent function modules, and/or interrupt
module when a stop error occurs in the CPU module.

(2) Error time output mode setting
Set the error time output mode in the I/O assignment tab of the PLC parameter dialog box.

1) Make I/O assignment for the target module.
2) Click the Detailed setting button.

3) On the screen opened, select "Clear" or "Hold". (Default: "Clear")

1) Make I/O assignment.

2) Click the Detailed setting button.

3) Select "Clear" or "Hold" for
the error time output mode.

7
8

6.8 Error Time Output Mode Setting

Figure 6.23 Error time output mode setting

(3) Precautions
The error time output setting will be enabled when:
• the CPU module is powered off and then on, or
• the CPU module is reset.

Failure to perform either of the operations above after changing the error time output mode setting will
result in "PARAMETER ERROR" (error code: 3000).

6 - 29

6.9 H/W Error Time PLC Operation Mode Setting
(1) Definition
This function determines the program operation mode (stop or continue) of the CPU module when a
hardware error occurs in an intelligent function module or interrupt module.

(2) H/W error time PLC operation mode setting
Set the H/W error time PLC operation mode in the I/O assignment tab of the PLC parameter dialog
box.
1) Make I/O assignment for the target module.
2) Click the Detailed setting button.

3) On the screen opened, select "Stop" or "Continue". (Default: "Stop")

1) Make I/O assignment.

2) Click the Detailed setting button.

3) Select "Stop" or "Continue" for
the H/W error time PLC operation mode.

Figure 6.24 H/W error time PLC operation setting

(3) Precautions
The H/W error time PLC operation setting will be enabled when:
• the CPU module is powered off and then on, or
• the CPU module is reset.

6 - 30

CHAPTER6 FUNCTIONS

6.10 Intelligent Function Module Switch Setting

(1) Definition
This function sets the switches of each Q series-compatible intelligent function module and interrupt

module in GX Developer.

(2) Writing the switch settings
The switch settings will be written from the CPU module to each intelligent function module and
interrupt module when:

• the CPU module is powered off and then on, or
• the CPU module is reset.

5
2) The settings are written when the CPU module
is powered off and then on or reset.

6
7
8

1) Write the
settings.

6.10 Intelligent Function Module Switch Setting

GX Developer

Figure 6.25 Writing the switch settings to each intelligent function module

6 - 31

(3) Switch settings
Set the switch details for each intelligent function module and interrupt module in the I/O assignment
tab of the PLC parameter dialog box.
1) Make I/O assignment for the target module.
2) Click the Switch setting button.
3) Set the switch details for each module.
1) Make I/O assignment.

2) Click the Switch setting button.

3) Set the switch details of each intelligent
function module and interrupt module.
Figure 6.26 Switch settings

(4) Precautions
(a) Switch setting details of each module
For the switch setting details of each intelligent function module or interrupt module, refer to the
manual for the intelligent function module or interrupt module used.

(b) Enabling the setting
The switch settings of each intelligent function module or interrupt module will be enabled when:
• the CPU module is powered off and then on, or
• the CPU module is reset.

6 - 32

CHAPTER6 FUNCTIONS

6.11 Monitor Function

(1) Definition
This function reads program and device data in the CPU module, and intelligent function module

status using GX Developer.

Table6.9 List of monitor functions and availability
Availability
Monitor function

Q00UJ

Q00UCPU,

CPU

Q01UCPU

Q02UCPU

QnUD(H)
CPU

Built-in

Reference

Ethernet

port QCPU

Ladder monitor

Device/buffer memory batch
monitor

GX Developer
Version 8

Entry data monitor

Operating Manual

Section 6.11.1

Device test
Entry ladder monitor
*1

External input/output forced on/off

Section 6.11.3

Executional conditioned device test

Section 6.11.4

Monitor condition setting
Local device monitor/test

Section 6.11.2

: Available,

: Not available

Appendix 2)

(2) Monitor request timing and displayed data
The CPU module processes monitor requests from GX Developer during END processing.
For this reason, the data in the CPU module at the time of END processing will be displayed in GX
Developer.

(3) Monitor with monitor condition settings
By setting the monitor condition in GX Developer during debugging, the program operation status in
the CPU module can be monitored under the specified condition.
Besides, the monitoring status under the specified condition can be held by setting the monitoring stop
condition.

(4) Local device monitor
If multiple programs are executed and local devices are used, data in local devices of each program
can also be monitored.

6 - 33

6.11 Monitor Function

*1: Availability depends on the version of the CPU module. (

: Available with restrictions,

6.11.1 Monitor condition setting

Note6.1

This function is used to monitor data in the CPU module under the specified condition.Note1

(1) Monitor condition setting for ladder monitor
Switch GX Developer into monitor mode.
Select [Online]

[Monitor]

[Monitor condition setup] to open the Monitor condition screen.

Set the condition as shown below to monitor data on the rising edge of Y70.

Select to use a device as
a monitor condition.
Select to use a step
number as a monitor
condition.

Monitoring starts
when the condition is
established.
(An operation status
when the condition
isestablished is
displayed.)

Figure 6.27 Monitor condition setting screen

(a) When only a step number is specified
Monitor data is collected when the status immediately before execution of the specified step
becomes the specified status.
The following status can be specified.
•
•
•
•
•

When the operation of the specified step changes from the non-execution status to the execution status: <-P->
When the operation of the specified step changes from the execution status to the non-execution status: <-F->
Always only when the operation of the specified step is in execution:
Always only when the operation of the specified step is in non-execution:
Always regardless of the status of the operation of the specified step:

Note1

Note6.1

Universal

The Q00UJCPU, Q00UCPU, and Q01UCPU do not support the monitor condition setting.
When setting monitor condition for the Q02UCPU, Q03UDCPU, Q04UDHCPU, Q06UDHCPU, Q13UDHCPU, or
Q26UDHCPU, check the versions of the CPU module and GX Developer. (

6 - 34

Appendix 2)

CHAPTER6 FUNCTIONS

1
●

If a step between the AND/OR blocks is specified as a monitor condition, monitor data is collected when the status
previous to execution of the specified step is specified by the LD instruction.
The monitor timing depends on the step specified as a monitor condition.
The following shows examples of monitoring when the step 2 is on (Step No. [2] = ).
• When the step 2 is connected by the AND instruction:
In Figure 6.28, the monitor execution condition is established when both X0 and X1 are on.

Ladder mode

List mode

Step 2
X0

X2
Y20

0
1
2
3

LD
AND
AND
OUT

XO
X1
X2
Y2

Figure 6.28 When the step 2 is connected by the AND instruction
• When the step 2 is connected in the middle of the AND/OR block:
In Figure 6.29, the monitor execution condition is established when X1 turns on. (The on/off status of X0 does not
affect the establishment of the monitor execution condition.)

Ladder mode

List mode

Step 2
0

X2
Y20

0
1
2
3
4
5

LD
LD
AND
OR
ANB
OUT

XO
X1
X2
X3

7
8

Y20

Figure 6.29 When the step 2 is connected in the middle of the AND/OR block

Ladder mode
0
2

X0
X1

List mode

Y10
Y11

0
1
2
3

LD
OUT
LD
OUT

XO
Y10
X1
Y11

Figure 6.30 When the start of a ladder block other than the step 0 is specified for the step number

●

Be sure to set the condition of the step set as step No.0 to "Always".

6 - 35

6.11 Monitor Function
6.11.1 Monitor condition setting

• If the start of a ladder block other than the step 0 is specified for the step number as a detailed condition, monitor
data is collected when the execution status of the instruction immediately before execution becomes the specified
status.
If (Step No. [2] = ) is specified in the following ladder, monitor data is collected when OUT Y10 turns on.

(b) When only a device is specified
Either word device or bit device can be specified.

1) When a word device is specified
Monitor data is collected when the current value of the specified word device becomes the specified value.
Enter the current value (in decimal or hexadecimal).

2) When a bit device is specified
Monitor data is collected when the execution status of the specified bit device becomes the specified status.
Select the execution condition (on the rising edge or falling edge).

(c) When a step number and device are specified
Monitor data is collected when the status previous to execution of the specified status or the status (current
value) of the specified bit device (word device) becomes the specified value.

When "Step No.[100]=<-P->, Word device [D1]=[K5]" is specified as an execution condition, a monitor execution condition is
established on the rising edge of the step 100 and also D1=5.

Step 100

Y20

INC D1
Figure 6.31 When the rising edge of the step 100 and D1=5 are specified
The monitor interval of GX Developer depends on the processing speed of GX Developer.
For the monitor execution conditions established at the interval shorter than the monitor interval of GX Developer, monitor is
executed only when the monitor execution condition is established at the monitor timing of GX Developer.

100

Step No.

100

M0
X0
D1=5
Monitor timing
(CPU module)
Figure 6.32 Monitor timing of GX Developer

6 - 36

100

CHAPTER6 FUNCTIONS

(2) Monitor stop condition setting
Set a monitor stop condition on the screen opened by selecting [Online]

[Monitor]

[Monitor stop condition

setup].

Set the condition as shown in Figure 6.33 to stop a monitor operation on the rising edged of Y71.

3
4
5
Figure 6.33 Monitor stop condition screen

(a) When a device is specified
Either word device or bit device can be specified.

1) When a word device is specified
A monitor operation is stopped when the current value of the specified word device becomes the specified

value.
Enter the current value (in decimal, hexadecimal, 16-bit integer, 32-bit integer, or real number).

2) When a bit device is specified
status.
Select the execution condition (on the rising edge or falling edge).

(b) When a step number is specified
A monitor operation is stopped when the execution status of the step specified as a monitor condition becomes
the specified status.
The following status can be specified.
• When the operation of the specified step changes from the non-execution status to the execution status:
<-P->
• When the operation of the specified step changes from the execution status to the non-execution status:
<-F->
• Always only when the operation of the specified step is in execution:
• Always only when the operation of the specified step is in non-execution:
• Always regardless of the status of the operation of the specified step:
If a step number is not specified, a monitor operation is stopped after END processing of the CPU module.

6 - 37

6.11 Monitor Function
6.11.1 Monitor condition setting

A monitor operation is stopped when the execution status of the specified bit device becomes the specified

(3) Precautions
(a) Files to be monitored
When monitor conditions are set, GX Developer monitors the file displayed on the screen.
Select [Online]

[Read from PLC] in GX Developer and read data from the CPU module so that the file name

in the CPU module to be monitored matches the file named displayed on the screen of GX Developer.

(b) No file register setting
If the file register is monitored when there is no file register used, "FFFFH" is displayed.

(d) Monitoring the buffer memory of an intelligent function module
When monitoring the buffer memory of an intelligent function module, the scan time increases for the same
reason for execution of the FROM/TO instructions.

(e) Monitoring by multiple users
When multiple users are performing monitoring at the same time, pay attention to the following.
• High speed monitor can be performed by increasing 1K step per monitor file of other stations in the system
area when formatting the program memory or setting a parameter in the Boot file tab of the PLC parameter
dialog box.
Up to 15 stations can be set as the station monitor file, but the program space will be reduced.
• If the monitor condition or monitor stop condition is set, only one user can perform monitoring.

(f) Setting a monitor stop condition
A monitor stop condition can be set only in the ladder monitor.

(g) Specifying the same device as a condition
When specifying the same device as a monitor condition or monitor stop condition, set the on/off status as well.

(h) Specifying a step number as a monitor condition
If an instruction in the specified step is not executed in such cases described below, the monitor condition will
not be established.
• The specified step is skipped with the CJ, SCJ, or JMP instruction.
• The specified step is the END instruction and never be executed because the FEND instruction also exists
in the program.

6 - 38

CHAPTER6 FUNCTIONS

(i) During monitor condition registration

Do not reset the CPU module while monitoring conditions are being registered.

(j) Monitor operation with monitor condition setting
When monitor operation with monitor condition setting is performed, other applications on the same personal
computer cannot execute any online function using the same route for the monitor operation. The following
applications must be noted.

• GX Developer
• Application using MX Component

• MX Sheet
If any online function is executed by other applications using the same route for the monitor operation, the

following situations may occur.
• No response is returned from the CPU module for the online function executed. (An online communication
function time-out occurs.)

• The CPU module detects an error (error code: 4109) for the online function executed.
• Even when the monitor condition is established in the CPU module, monitoring results cannot be updated
for the monitor operation with monitor condition setting.

7
8

6.11 Monitor Function
6.11.1 Monitor condition setting

6 - 39

6.11.2 Local device monitor/test

Note6.2

This operation is useful for debugging a program, monitoring local devices (

Section 9.14.2) in the program

monitored by GX Developer. Note1

(1) Monitoring a local device
Table6.10 shows the monitor operation when the CPU module executes three programs "A", "B", and "C" and D0
to D99 are set as a local device.
(Three programs are to be executed in the order of A B C (END processing)

A B....)

Table6.10 Data displayed when three programs are executed
Setting
When the device is not set as
a local device
When the device is set as a
local device

Monitor device
D0 (Local device)
D0 in the program "C" is monitored.
D0 in the displayed program is monitored.

Note1

Note6.2

Universal

The Q00UJCPU does not support the use of local devices.

6 - 40

D100 (Global device)
D100 after the program "C" is executed is
monitored.
D100 after the program "C" is executed is
monitored.

CHAPTER6 FUNCTIONS

When local devices are set to be monitored and the program "B" is displayed for monitoring, the local device(s)
used in the program "B" can be monitored.

CPU module

Program execution (A

3
X0
MOVP K2 DO
X1

Program: A
MOVP K3 D99

5
X10
MOVP K4 DO
X11

Program: B
MOVP K8 D99

7
8

X20
MOVP K3 DO
X21

Program: C
MOVP K6 D99
6.11 Monitor Function
6.11.2 Local device monitor/test

The local device data of the
program B is displayed.
(Example)
If D0 to D99 are set as a local device,
D0=4 is displayed when X10 is on and
D99=8 is displayed when X11 is on.

Local devices are set to be
monitored and the
program "B" is monitored.

GX Developer
Figure 6.34 Local device monitor example

6 - 41

(2) Monitoring procedure
The following shows the local device monitoring procedure.
Connect a personal computer to the CPU module.

Display a program in ladder mode.

Select [Online]
[Monitor] [Monitor mode].

Switching to the
monitor mode

Select [Local device monitor]
from the monitor window.

Setting of the local
device monitor

The local device of the
displayed program is
monitored.
Figure 6.35 Local device monitoring procedure

(3) Precautions
(a) Local devices that can be monitored/tested by a single GX Developer
A single GX Developer can monitor or test local devices in one program at a time.
Local devices in multiple programs cannot be monitored or tested simultaneously.

(b) Number of programs that can be monitored/tested
Local devices in 16 programs can be monitored or tested simultaneously from multiple GX Developers
connected to the RS-232 interface of the CPU module or the serial communication module.

(c) Monitoring local devices in a stand-by type program
When local devices in a stand-by type program are monitored, data in local devices are saved and restored.
For this reason, the scan time increases. (

Section 9.14.2)

(d) Monitoring local devices in a fixed scan execution type program
When local devices in a fixed scan execution type program are monitored, data in local devices cannot be
acquired and "0" is displayed.

6 - 42

CHAPTER6 FUNCTIONS

6.11.3 External input/output forced on/off

Note6.3

The external input/output can forcibly be turned on/off on the screen opened by selecting [Online]

[Debug]

[Forced input output registration/cancellation] in GX Developer.Note1

The information registered for forced on/off can be cancelled by an operation from GX Developer.

3
4
5
6
7
8
Figure 6.36 Forced input output registration/cancellation screen

There are three kinds of forced on/off operations: forced on ("Set forced ON"), forced off ("Set forced OFF"), and
forced on/off cancellation ("Cancel it").
Table6.11 shows the CPU module operation when a forced on/off operation is performed.
Table6.11 Input/output operation when a forced on/off operation is performed
Operation
Forced on/off
cancellation (no
operation)
Forced on
Forced off

Input (X) operation

Output (Y) operation

The CPU module performs sequence program operations

The CPU module outputs the results of sequence

using external inputs.

program operations externally.

The CPU module performs sequence program operations

The CPU module outputs "on" externally regardless of

using inputs forcibly turned on.

the results of sequence program operations.

The CPU module performs sequence program operations

The CPU module outputs "off" externally regardless of

using inputs forcibly turned off.

the results of sequence program operations.

Note1

Note6.3

Universal

When performing an external input/output forced on/off operation for the Q02UCPU, Q03UDCPU, Q04UDHCPU,
Q06UDHCPU, Q13UDHCPU, or Q26UDHCPU, check the versions of the CPU module and GX Developer. (
Appendix 2)

6 - 43

6.11 Monitor Function
6.11.3 External input/output forced on/off

(1) Input/output operation when a forced on/off operation is performed

Figure 6.37 shows the input/output operation when a forced on/off operation is performed.

Output forced on/off operation Y10 device forced off

Output refresh

Y10 output
(off)

External output
(Y10 off)

Input refresh

X0 input
(on)
Input forced on/off operation X0 device forced off

External input
(X0 on)

Program execution
MO
Y10
External input is
forcibly turned off.

Y11

Y10
M1
On the ladder block, Y10 appears to be on even
though a forced off operation is performed.

END

Figure 6.37 Input/output operation when a forced on/off operation is performed

(2) Specifications
(a) CPU module status where input/output can forcibly be turned on/off
Forced on/off can be registered regardless of the operating status (RUN/STOP) of the CPU module.
Note, however, that only input can be forcibly turned on/off during a stop error.
The CPU module outputs on/off data only to Y device.

(b) Registerable devices
Forced on/of can be registered as many as the number of I/O device points in the CPU module.

(c) Target input/output
The following input/output are targeted for a forced on/off operation.
• Input(X) and output (Y) of modules mounted on the base unit
• Input(X) and output (Y) of the CPU module to be refreshed from LX/LY of a CC-Link IE controller network
or MELSECNET/H module
• Input(X) and output (Y) of the CPU module to be refreshed from RX/RY of a CC-Link module
When forcibly turning on/off the devices outside the above refresh ranges (for example, empty slots), only
input/output in the CPU module device memory are turned on/off and the results are not output externally.

In multiple CPU systems, inputs and outputs of control modules can forcibly turned on/off.
Even when inputs and outputs of non-control modules are registered for forced on/off, the input/output devices in other CPU
modules and inputs and outputs of modules controlled by other CPU modules cannot be forcibly turned on/off. (The input/
output devices in the host CPU module can forcibly turned on/off.)

6 - 44

CHAPTER6 FUNCTIONS

(d) Cancelling on/off registration data

The registered forced ON/OFF data can be canceled by GX Developer.
Once the registered data is canceled, the status of the forced on/off registered devices will be as follows.

Table6.12 Status of devices after forced on/off registration data is canceled
Forced on/off registered device
Input from modules mounted on the base unit
Input of the CPU module to be refreshed from LX
of a CC-Link IE controller network or
Input

Sequence program operations

(on/off) performed

(on/off) not performed

Uses the on/off status input from modules.
Used the on/off status refreshed via CC-Link IE controller network or
MELSECNET/H.

MELSECNET/H module
Input of the CPU module to be refreshed from
RX of a CC-Link module

3
4

Uses the on/off status refreshed via CC-Link.

Input other than above (outside of the refresh

Uses the results of sequence

range)

program operations.

Holds the forced on/off status.

Output from modules mounted on the base unit
Output of the CPU module to be refreshed from

Output

LY of a CC-Link IE controller network or

Outputs the results of sequence

MELSECNET/H module

program operations.

Holds the registered on/off status.

Output of the CPU module to be refreshed from

RY of a CC-Link module
Output other than above (outside of the refresh
range)

Outputs the results of sequence
program operations. (The results

Holds the forced on/off status.

are not output externally.)

Forced on/off setting can be cleared by:
• powering off and then on the CPU module,
• resetting the CPU module by the remote RESET operation.

(e) External input/output forced on/off timing
Table6.13 shows the external input/output forced on/off timing.
Table6.13 Forced on/off timing
Refresh area

Input
• During END processing (input refresh)
• At execution of the COM instruction (input refresh)

Input and output of
modules mounted on the
base unit

• At execution of an instruction using direct access
input (DX) (LD, LDI, AND, ANI, OR, ORI, LDP, LDF,
ANDP, ANDF, ORP, ORF)
• At execution of the RFS or MTR instruction
• At execution of an instruction used for a system
interrupt (UDCNT1, UDCNT2, SPD)

Output
• During END processing (output refresh)
• At execution of the COM instruction (output
refresh)
• At execution of an instruction using direct access
input (DX) (OUT, SET, DELTA, RST, PLS, PLF,
FF, MC, SFT)
• At execution of the RFS or MTR instruction
• At execution of an instruction used for a system
interrupt (PLSY, PWM)

Input and output of the CPU
module to be refreshed from

• During END processing (refresh via CC-Link IE controller network or MELSECNET/H)

LX/LY of a CC-Link IE

• At execution of the COM instruction

controller network or

• At execution of the ZCOM instruction

MELSECNET/H module
Input and output of the CPU

• During END processing (auto refresh)

module to be refreshed from

• At execution of the COM instruction (auto refresh)

RX/RY of a CC-Link module

• At execution of the ZCOM instruction (auto refresh)

6 - 45

6.11 Monitor Function
6.11.3 External input/output forced on/off

• resetting the CPU module by the RUN/STOP/RESET switch, or

(f) Number of registerable devices
Forced on/off can be registered for 32 devices in total.

(g) When output Y contact is used in a sequence program
On/off operations in a sequence program are given priority.

(h) Checking forced on/off registration status
Forced on/off execution status can be checked by:
• reading the forced on/off registration status by GX Developer,
• flashing of the MODE LED (green), (The MODE LED flashes in green when at least one forced on/off is
registered.) or
• the on status of the 1st bit in SD840 (Debug function usage).

●

The MODE LED also flashes in green when the executional conditioned device test function is used.
To check the registration status using the MODE LED, check the status of the executional conditioned device test
function as well. (

●

Section 6.11.4)

When using SD840 to check the registration or cancellation status, remind that SD840 is used to check the status of
the executional conditioned device test function as well.

(i) Forcibly turning input or output on/off from multiple GX Developers
Forced on/off can be registered to a single CPU module from multiple GX Developers connected via network.
In this case, the last registration will be effective.
For this reason, the forced on/off status which is different from the status actually registered in the CPU module
may be displayed on the screen of GX Developer that registered forced on/off earlier.
When the forced on/off registration is performed from multiple GX Developers, click the "Update status" button
to update the registered data and execute the function.

6 - 46

CHAPTER6 FUNCTIONS

(3) Operating procedure
Operating procedure is described below.
• To register forced on/off for a device, select [Online]

[Debug]

[Forced input output registration/

cancellation] in GX Developer.
• On the screen opened, specify a device and click the "Set forced ON" or "Set forced OFF" button.

5
2)

6
7

6)
Figure 6.38 Forced input output registration/cancellation screen

No.
1)
2)

Item
Device
Registration status display
area

Description
Select the I/O number for which forced on/off is to be registered or cancelled.
Displays the forced on/off registration status.

Update status

Reads the forced on/off registration status from the CPU module.

Set forced ON/OFF

Registers forced on/off for a device specified.

Cancel it

Cancels forced on/off registered for the device specified.

Clear all

Cancels all forced on/off registration.

6 - 47

6.11 Monitor Function
6.11.3 External input/output forced on/off

Table6.14 Items on the Forced input output registration/cancellation screen

6.11.4 Executional conditioned device test

Note6.4

This function changes a device value within the specified step of a program.Note1
This enables debugging of the specified ladder block without modifying the program.*1
*1: The executional conditioned device test is not available for the SFC program.

(1) Operation of the executional conditioned device test
A device value will be changed based on the registration data once after the executional conditioned device test
setting is registered.
The changed device value becomes effective in the ladder blocks of the specified step number and later.
Program: MAIN
Registration data
Program name : MAIN
Step No.
: 10
: M0
Device
: ON
Setting value
: Before executing instruction

Execution timing

GX Developer

M0 is turned on.

Figure 6.39 Operation of the executional conditioned device test

Note that a device value is changed within the specified step regardless of an execution status of the instruction in
the specified step.

Ladder mode

List mode

Processing
Value in D0
Value in M0

Executional conditioned device test which
sets "35" in D0 in this step is registered.

LD M0

Changes the value in D0 to "35".

+ K10 D0

OFF

A device value is changed within the
specified step regardless of the value in M0.

Figure 6.40 Operation example of the executional conditioned device test

Note1

Note6.4

Universal

When using the executional conditioned device test in the Q02UCPU, Q03UDCPU, Q04UDHCPU, Q06UDHCPU,
Q13UDHCPU, or Q26UDHCPU, check the versions of the CPU module and GX Developer.(

6 - 48

Appendix 2)

CHAPTER6 FUNCTIONS

(2) Available devices and number of settable devices
Table6.15 Available devices and number of settable devices
Type

Number of settable

Available device
X, Y, M, L, B, F, SB, V, SM, T (contact), ST (contact), C (contact), J

Bit device

\B, J

devices
\X, J

\Y,

\SB, FX, FY, DX, and DY

T (current value), ST (current value), C (current value), D*1, SD, W*2, SW, R,
ZR, Z, U

, U3E

\SW

, and FD

Up to 32 (in total)

Digit-specified bit device:

Word device

X, Y, M, L, F, SM, V, B, SB, J

\X, J

\Y, J

\B, and J

\SB

Indirect specification (@D0): D, SD, W, SW, R, and ZR (devices specified with
@)
*1: The extended data register (D) is included.
*2: The extended link register (W) is included.

(3) How to check the execution status
The execution status of registered executional conditioned device test can be checked in three different ways:

• By the flash of the MODE LED in green
• By the on status of the first bit of SD840 (Debug function usage)

• By the display on the screen for checking the registration status in GX Developer
(

The MODE LED also flashes in green when the external input/output forced on/off function is used.
To check the execution status using the MODE LED, check the status of the external input/output forced on/off function
as well. (

●

Section 6.11.3)

When using SD840 to check the execution status, remind that SD840 is used to check the status of the external input/
output forced on/off function as well.

6 - 49

6.11 Monitor Function
6.11.4 Executional conditioned device test

●

(4)(d) in this section)

(4) Operating instructions
(a) Registering executional conditioned device test settings
Select the registration target step number on the program editing screen in GX Developer. Then, select
[Online]

[Debug]

[Executional conditioned device test]

[Register executional conditioned device test].

7)
1)
2)
4)

Figure 6.41 Screen for registering executional conditioned device test settings

Table6.16 Items on the screen for registering executional conditioned device test settings
No.

Setting range

Item

Program name

Step No.

For bit device

Name of a program registered in the CPU module
0 to (Step number for the END instruction)

Device

Execution timing

Setting value

- (Not specified)

DEC / HEX

- (Not specified)

For word device

Device listed in (2) in this section

Data type*1

Before executing instruction / After executing instruction

- (Not specified)

Setting range corresponding to each data type
DEC (decimal) / HEX (hexadecimal)
16 bit integer / 32 bit integer / Real number (single
precision) / Real number (Double precision)

*1: When a word device which is index-modified or indirectly-specified is set, only "16 bit integer" can be specified.

1) Multiple executional conditioned device test registrations for the same step
number
Multiple executional conditioned device test settings can be registered for one step number.
+

D0 D10

D20

Devices that executional conditioned device test settings
can be registered for the start step of the + instruction.

However, if multiple executional conditioned device test settings with same device name and same execution
timing are registered for the same step number, the registration data will be overwritten. (Even though the
same device is specified, if the execution timing differs, two settings can be registered for one step.)

6 - 50

CHAPTER6 FUNCTIONS

1
●

When setting a word device with a different data type, a device is regarded as the same device.

Example

When setting a device with a different modification method (such as a bit-specified word device, digit-specified bit
device, or index-modified device), a device is regarded as a different device.

When a word device is set in the order of "D100 (16 bit integer)" and then "D100 (Real number (single
precision))", "D100 (Real number (single precision))" is registered.

●

Example When a word device is set in the order of "D100.F" and then "D100Z0 (Real number (single precision)),
both devices are registered.

2) Step to be specified for executional conditioned device test registration
Any step number (0 to step number for the END instruction) in a sequence program can be specified.

4
5
6

Be sure to specify the start step of each instruction.

7
3) Execution timing
Timing of changing a device value can be specified. A device value can be changed either before or after an

instruction of the specified step is executed. Figure 6.42 shows the module operation based on the execution
timing.

6.11 Monitor Function
6.11.4 Executional conditioned device test

Ladder mode

List mode

Executional conditioned device test which
sets "20" in D0 in this step is registered.

Execution timing

Before executing
an instruction of
step 101

After executing
an instruction
of step 101

CPU module operation

Processing
Value in D0

LD M0

Changes the value in D0 to "20".

LD M0

+ K100 D0

120

Changes the value in D0 to "20".

110

Figure 6.42 CPU module operation based on execution timing

6 - 51

Note that there may be a case where a device value will not be changed depending on the execution timing even
though the specified step is executed.
The following instructions need to be noted when registering executional conditioned device test settings.
• Instructions that do not change device values*1
A device value will not be changed by executing the excutional conditioned device test when the execution
timing has been set to "After executing instruction", specifying the step for instructions that do not execute
the next step, such as branch instructions.
*1:

If the execution condition of an instruction is not satisfied, a device value will be changed based on the registration data.

Table6.17 lists the instructions that do not change device values.
Table6.17 Instructions that do not change device values
No.
1

Classification

Instruction

Stop

Jump

• When the execution condition for an instruction

SCJ

is satisfied

GOEND

Repeat (Loop)

A device value will not be changed even when

BREAK(P)
CALL(P)

FCALL(P)
ECALL(P)

Subroutine program call

the specified step is executed.
• When execution condition for an instruction is

Operation

STOP

EFCALL(P)

XCALL

not satisfied
A device value will be changed after the
specified step is executed.

End

FEND

Jump

JMP

A device value will not be changed even when the

Return from subroutine program

RET

specified step is executed.

Return from interrupt program

IRET

• FOR/NEXT instructions
When the executional conditioned device test setting is registered specifying the step for the FOR or NEXT
instruction, timing of device value change is different from the timing when steps for other instructions are
specified.
Table6.18 shows the device value change timing based on the execution timing.
Table6.18 Device value change timing when a step for the FOR or NEXT instruction is specified
Instruction of the specified step

Execution timing setting
Before executing instruction

After executing instruction
Executed once after the start of loop

FOR

Executed once before the start of loop

processing. (Executed before the operation

processing.

of the program between the FOR and NEXT
instructions.)

Executed every loop processing.
NEXT

(Executed after the operation of the

Executed once after the start of loop

program between the FOR and NEXT

processing.

instructions.)

• END instruction
When the executional conditioned device test setting is registered specifying the step for the END
instruction, the execution timing is restricted to "Before executing instruction" only. If "After executing
instruction" is set, the CPU module returns a registration error to GX Developer.

6 - 52

CHAPTER6 FUNCTIONS

4) Number of settings that can be registered simultaneously in one scan
Eight executional conditioned device test settings can be registered into the CPU module simultaneously in

one scan.
When nine or more executional conditioned device test settings are to be registered simultaneously by
GX Developer, they will be registered over multiple scans.

(b) Disabling executional conditioned device test settings
Select the disabling target step number on the program editing screen in GX Developer. Then, select [Online]
[Debug]

[Executional conditioned device test]

2
3

[Check/disable executional conditioned device test].

4
5
6
7
Figure 6.43 Screen for checking/disabling executional conditioned device test settings

Table6.19 Items on the screen for checking/disabling executional conditioned device test settings
Setting range
For bit device

Program name

For word device

Name of a program registered in the CPU module

Step No.

0 to (Step No. for the END instruction)

Device

Device listed in (2) in this section

Execution timing

Before executing instruction/After executing instruction

1) Number of settings that can be disabled simultaneously in one scan
Eight executional conditioned device test settings can be disabled simultaneously in one scan.
When nine or more executional conditioned device test settings are to be disabled simultaneously by GX
Developer, they will be disabled over multiple scans.

[Debug]

[Executional conditioned device test]

[Batch disable executional conditioned

device test] in GX Developer.

Figure 6.44 Screen for batch-disabling executional conditioned device test settings

6 - 53

6.11 Monitor Function
6.11.4 Executional conditioned device test

Item

(d) Checking executional conditioned device test settings
Select [Online]

[Debug]

[Executional conditioned device test]

[Check/disable executional conditioned

device test].

Figure 6.45 Screen for checking executional conditioned device test settings

Remark
1.

For the operating instruction of checking or disabling executional conditioned device test settings, refer to the
following.
GX Developer Version 8 Operating Manual

Usage of the executional conditioned device test can be checked in the special register (SD840).

(e) Cases where executional conditioned device test settings cannot be registered or
disabled
In the following cases, executional conditioned device test setting cannot be registered or disabled.
When multiple settings are to be registered, no setting can be registered if any of the settings applies to the
cases below.

1) Executional conditioned device test settings cannot be registered
• Specified program does not exist.
• Specified step does not exist.
• Specified device does not exist.
• The number of registered executional conditioned device test settings exceeds 32.

2) Executional conditioned device test settings cannot be disabled
• Specified program does not exist.
• Specified step does not exist.
• Specified device does not exist.
• No executional conditioned device test setting has been registered.

6 - 54

CHAPTER6 FUNCTIONS

(5) Precautions

(a) Operations from multiple GX Developers
Executional conditioned device test setting can be registered in the same CPU module from multiple GX
Developers connected via network.

Note, however, that if multiple executional conditioned device test settings are registered with the same device
name in the same step, the registration data will be overwritten.
When registering executional conditioned device data setting from multiple GX Developers update the data first

by clicking the Read file button, and then register the setting.

(b) Priority
If any of the following functions is set in the same step number that is specified by the executional conditioned

device test setting, the executional conditioned device test is given the priority to other functions.
• Monitor condition setting
• Sampling trace function (trace point)

• Sampling trace function (trigger point)
• Scan time measurement (start step)
• Scan time measurement (end step)

(c) Disabling executional conditioned device test settings
Executional conditioned device test setting can be disabled by any of the following operations, in addition to the
operation by GX Developer.

• Powering off and then on the CPU module
• Resetting the CPU module
• Writing program files to the program memory while the CPU module is in the STOP status
• Formatting the program memory while the CPU module is in the STOP status

(d) Writing data to the running CPU module
The CPU module operation will be as follows if the executional conditioned device test and the online change
function are executed simultaneously.

1) When the executional conditioned device test is executed during execution of the
online change function
The online change function completes normally. However, the executional conditioned device test cannot be
executed.
The following message box will appear. Execute the executional conditioned device test again after the online
change has completed.

Figure 6.46 Message box (when the executional conditioned device test is executed during execution of the online change
function)

6 - 55

6.11 Monitor Function
6.11.4 Executional conditioned device test

• Clearing the program memory while the CPU module is in the STOP status

2) When the online change function is executed during execution of the executional
conditioned device test
The Online change function completes normally. If any executional conditioned device test setting has been
registered in the program to be changed online, the corresponding setting will be disabled.
(

(5)(e) in this section)

(e) Online change of the CPU module with executional conditioned device test
registration
1) Online change (ladder mode)
If any executional conditioned device test setting has been registered in the ladder block to be changed
online, the CPU module disables the corresponding setting.
Example 1) Step numbers of registrations 1 to 3 are specified in the executional conditioned device test
settings. When the ladder block including the registration 2 is changed online, the registration 2 is
disabled during execution of the online change function.
Since the registrations 1 and 3 are not included in the change target program, they are not disabled.

Registration 1

Registration 2

Registration 3

The shaded area is the ladder block to be changed online.

Figure 6.47 Adding a ladder block online

Example 2) When multiple ladder blocks are to be changed online, ladder blocks between the change target
ladder blocks will be included in the change target.
For this reason, if the online change function is executed as shown in Figure 6.48, all registrations 1 to
3 are disabled.

Registration 1

Registration 2

Registration 3

The shaded area is the ladder block to be changed online.

Figure 6.48 Changing multiple ladder blocks online

6 - 56

CHAPTER6 FUNCTIONS

Example 3) When a ladder block is to be added online, the executional conditioned device test setting
included in the ladder block followed after the added ladder block will be disabled.

For this reason, if the online change function is executed as shown in Figure 6.49, the registration 2 is
disabled.

Registration 1

3
4

Registration 2

Registration 3
*

The shaded area is the ladder block to be changed online.

Figure 6.49 Adding a ladder block online

2) Online change (files)
All executional conditioned device test settings registered to the program in the online change target file are

disabled.

(f) Precautions for specifying an index-modified device
If an index-modified device name is specified to register the executional conditioned device test setting, the
CPU module does not check whether the specified device is within the setting range.

If the index-modified device is out of the device range or on the boundary of devices, a device value will not be
changed within the specified step.

If indirectly-specified device name is specified to register the executional conditioned device test setting, the
CPU module does not check whether the specified device is within the setting range.
If the indirectly-specified device is out of the device range or on the boundary of devices, a device value will not
be changed within the specified step.

(h) Precautions for specifying the file register
If the file register is specified to register the executional conditioned device test setting, the CPU module does
not check the file register file assignment and the file register number range.
A file register value will not be changed within the specified step in the following cases.
• The file register file is not assigned.
• The specified file register number is out of the file register range.

6 - 57

6.11 Monitor Function
6.11.4 Executional conditioned device test

(g) Precautions for specifying an indirectly-specified device

6.12 Writing Programs While CPU Module is in RUN Status
There are two ways of writing programs in the RUN status.
• Online change (ladder mode) :
• Online change (files) :

Section 6.12.1

Section 6.12.2

Data can also be written in the RUN status using a pointer. (

Section 6.15.2)

6.12.1 Online change (ladder mode)
(1) Definition
This function writes programs to the CPU module in the RUN status.
This function enables the program to be changed without stopping the program operation in the CPU
module.

X0 X2
Y30
X1

X3 X4
SET M10
X5

END

GX Developer

Change a program with GX Developer and
write it to the CPU module in the RUN status.
Figure 6.50 Outline of online change (ladder mode)

6 - 58

CHAPTER6 FUNCTIONS

This function also can write programs by GX Developer connected to another station on the network.

1
2
3
4

GX Developer
MELSECNET/H
PLC-to-PLC network

5
6
7
8

Change a program with GX Developer and
write it to the CPU module in the RUN status.
Figure 6.51 Outline of online change via network

6.12 Writing Programs While CPU Module is in RUN Status
6.12.1 Online change (ladder mode)

(2) Memory for online change
A program cache memory (program memory) is available.

(3) Number of steps that can be batch-written by online change
Up to 512 steps can be batch-written.

6 - 59

(4) Changing the reserved area for online change
A program file has an area designated as reserved area for online change to support the online
change that changes program file size.
The following provides precautions when changing the size of reserved area for online change.
(a) Size of a program file
The size of a program file is addition of created program size and reserved area for online change.

(b) When program file size is increased from the secured capacity
If the size secured for the program file (size including reserved area for online change) is exceeded after a
program is written in the RUN status, the reserved area for online change can be re-set before the writing if the
user memory area has space.

(c) Increase in the scan time
The scan time is increased when reserved area for online change is re-set when programs are written in the
RUN status.
For increase in the scan time, refer to Section 10.1.3.

(5) Operations prohibited when programs are written to the CPU module in the
RUN status, T/C setting value is changed, or data are transferred from a
program cache memory to a program memory
Refer to Section 6.12.3(2).

(6) Instructions that do not operate normally when programs are written to the
CPU module in the RUN status
Refer to Section 6.12.3(3).

6 - 60

CHAPTER6 FUNCTIONS

6.12.2 Online change (files)

(1) Definition
This function batch-writes files shown in Table 6.20 to the CPU module in the RUN status by online operation from
GX Developer.
Table6.20 Files that can be written to the CPU module in the RUN status
Memory card

CPU module built-in memory
File name
Program memory

(RAM)

Standard

RAM

ROM

SRAM card

Memory card (ROM)
Flash card

ATA card

2
3
4

Parameter
Intelligent function module

parameter
Program
*1

Device comment

Initial device value
*1

File register

Local device
Sampling trace file
Programmable controller user

data
: Can be written,

: Partially restricted,

: Cannot be written

6.12 Writing Programs While CPU Module is in RUN Status
6.12.2 Online change (files)

*1: The file can be written if not being accessed by a sequence program.

Program file
A
Writing of
program file A

GX Developer
Figure 6.52 Outline of online change (files)

6 - 61

(2) Availability
(a) For the Q00UJCPU,Q00UCPU,and Q01UCPU
The function cannot be performed in the following cases.
• A program memory does not have enough area for storing a program file to be written.
• A program memory stores the maximum number of files can be stored.

(b) For the Q02UCPU,QnUD(H)CPU, and Built-in Ethernet port QCPU
A file can be written to the CPU module in the RUN status regardless of space of a memory to be
written and the number of files to be stored.

(3) Increase in the scan time
The scan time increases when a program file is written to the CPU module in the RUN status.
For increase in the scan time, refer to Section 10.1.3.

(4) When a file is accessed by a sequence program instruction
An instruction in a program cannot access to the file being written to the CPU module in the RUN status. If
If doing so, the instruction will not be executed.

(5) Online change(files) from multiple locations
Do not simultaneously write files to one CPU module in the RUN status from multiple locations.
Doing so may delete program files.

(6) Online change (files) of SFC programs
SFC programs cannot be written in units of files to the CPU module in the RUN status.

(7) Operations prohibited when programs are written to the CPU module in the
RUN status, T/C setting value is changed, or data are transferred from a
program cache memory to a program memory
Refer to Section 6.12.3(2).

(8) Instructions that do not operate normally when files are written to the CPU
module in the RUN status
Refer to Section 6.12.3(3).

6 - 62

CHAPTER6 FUNCTIONS

6.12.3 Precautions for online change

The following shows precautions for online change.

(1) Online change during boot operation
When data are written to the CPU module in the RUN status during boot operation, the status of boot source

program is not changed.

(2) Operations prohibited when programs are written to the CPU module in the
RUN status, T/C setting value is changed, or data are transferred from a
program cache memory to a program memory
Do not perform the following operations.

4
5

(a) Power-off or reset
The following operations are not normally completed if they are performed during online change, TC setting
value change, or data transfer from the program cache memory to the program memory.

If performed, write the data to the CPU module again.
• Power-off

• Reset

(b) Operations from GX Developer
The following operations cannot be performed during online change, TC setting value change, or data transfer

from the program cache memory to the program memory. If performed, an error is displayed on GX Developer.
Perform the following operations after online change, TC setting value change, or data transfer from the
program cache memory to the program memory.
6.12 Writing Programs While CPU Module is in RUN Status
6.12.3 Precautions for online change

(Ladder mode, writing files during RUN, and function block)
TC setting value change
Data transfer to the program memory
• Online change (ladder mode), online change (files)
• TC setting value change
• Data transfer to the program memory
• Write to PLC (Flash ROM)

6 - 63

(3) Instructions do not operate normally during online change
When data are written to the CPU module in the RUN status, the following instructions do not operate normally.
• Fall instruction
• Rise instruction
• SCJ instruction

(a) Fall instruction
The fall instruction is executed when the instruction is in the data written to the CPU module in the RUN status,
even if the execution condition (on

off) is not met.

For preventing the fall instruction execution during online change, refer to POINT in this section.

Completion of
online change

XO
[ PLF MO ]

END

A END

END

1 scan
X0 status

OFF

ON
XO
OFF
OFF ON
MO
OFF

ON
XO
OFF
ON
ON
MO
OFF

ON
XO
OFF
OFF
ON
MO
OFF

The fall instruction is executed
even if the execution condition is off

off.

Figure 6.53 Operation of the fall instruction

The corresponding fall instructions are LDF, ANDF, ORF, MEF, PLF, FCALLP, and EFCALLP.

6 - 64

CHAPTER6 FUNCTIONS

(b) Rise instruction
The rise instruction is not executed when the instruction is in the data written to the CPU module in the RUN
status, even if the execution condition (off
Completion of
online change

on) is met.

XO
[ PLS MO ]

END 0

A END 0

END 0

1 scan

X0 status
ON

XO
OFF
OFF

OFF
ON
MO
OFF

XO
ON

ON
OFF

ON MO ON
OFF

ON
XO
ON

OFF

The rise instruction is not executed even
if the execution condition is off on.

ON
OFF

Figure 6.54 Operation of the rise instruction

The corresponding rise instructions are PLS and

(c) SCJ instruction
When the SCJ instruction is in the data written to the CPU module in the RUN status and the execution

Completion of
online change
END

X0 status
OFF

ON
XO

XO
[ SCJ PO ]

A END

END

1 scan

OFF

OFF
SCJ
instruction
ON
XO

Jumps to the specified pointer.
OFF

ON
SCJ
instruction
ON
XO

Jumps to the specified pointer.
OFF

OFF
SCJ
instruction

Jumps to the specified pointer
without waiting for one scan.

Figure 6.55 Operation of the SCJ instruction

6 - 65

6.12 Writing Programs While CPU Module is in RUN Status
6.12.3 Precautions for online change

condition is on at completion of the writing, a jump to the specified pointer is made without a wait of one scan.

To avoid execution of the fall instruction even when the execution condition (on
off) is not met after data are written to the
CPU module in the RUN status, select "Trailing edge instructions are not executed" in the Options screen in GX Developer.
The option is deselected by default.

Selecting this option avoids
execution of the fall instruction
whose execution condition is "off".

Figure 6.56 Options screen

Figure 6.57 shows operations of the fall instruction depending on the setting of "Trailing edge instructions are not executed"
in GX Developer.
Completion of
online change

Completion of
online change

XO
[ PLF MO ]

END 0

A END 0

[ PLF MO ]

A END 0

END 0

1 scan
X0 status

OFF

ON
XO
OFF
OFF ON
MO
OFF

ON
XO
OFF
OFF
ON
MO
OFF

A END 0

1 scan
The fall instruction is executed
even if the execution condition is off

(a) Operation when deselecting "Trailing
edge instructions are not executed"

X0 status

OFF

ON
XO
OFF
OFF ON
MO
OFF

ON
XO
OFF
OFF
ON
MO
OFF

off.

The fall instruction is not executed
when the timing of completion of
online change and execution
condition of on off are met.

(b) Operation when "Trailing edge instructions are not executed" is checked.

Figure 6.57 Operation comparison of the fall instruction

6 - 66

The rise instruction is not
executed even if the execution
condition is off off.

CHAPTER6 FUNCTIONS

(4) Writing to the program memory during online change and T/C setting value
change
Contents changed due to online change and TC setting value change are automatically transferred to the
program memory simultaneously when the data are written to the program cache memory.

1
2

The time required for writing data to the CPU module in the RUN status and changing T/C setting value is

increased due to automatic transfer of the program memory by the time shown in Table6.21.
Table6.21 Time increased due to automatic transfer of data to the program memory
CPU module
Q00UJCPU,Q00UCPU,Q01UCPU,Q02UCPU

Transfer time
Ts

320 + 4.8 (s)

260 + 4.7 (s)

Q10UDHCPU,Q10UDEHCPU

439 + 6.2 (s)

Q13UDHCPU,Q13UDEHCPU

600 + 8.0 (s)

Q20UDHCPU,Q20UDEHCPU

839 + 11.4 (s)

Q26UDHCPU,Q26UDEHCPU

1100 + 15.0 (s)

Q03UDCPU,Q04UDHCPU,Q06UDHCPU,Q03UDECPU,
Q04UDEHCPU,Q06UDEHCPU

4
5
6
Ts: Scan time (s)

Since the number of writes to the program memory (Flash ROM) is limited (up to 100,000 times), set the
automatic transfer to the program memory to be disabled when data are written to the CPU module in the RUN

7
8

status and changing T/C setting value frequently.

6.12 Writing Programs While CPU Module is in RUN Status
6.12.3 Precautions for online change

6 - 67

Automatic transfer to the program memory can be set to be disabled in the Options screen of GX Developer.

Data are not automatically
transferred to the program
memory by deselecting
here.

Figure 6.58 Online change/TC setting value change program memory transfer settings
When the automatic transfer is set to be disabled, the following message appears after online change.

Selecting "Yes" transfers data to the program memory.
Selecting "No" does not transfer data to the program memory.
When selecting "No", execute "Program memory batch transfer" by GX Developer.Note1
Program transfer status can be checked by the special relay (SM165).
Note6.5
When SM165 is on, the program memory batch transfer has not completed.
When SM165 is off, the program memory batch transfer has completed.

Note1

Note6.5

Universal

When checking the batch transfer status to the program memory with the Q02UCPU,Q03UDCPU,Q04UDHCPU, or
Q06UDHCPU, check the versions of the CPU module and GX Developer.(

6 - 68

Appendix 2)

CHAPTER6 FUNCTIONS

6.13 Execution Time Measurement

(1) Definition

This function displays the processing time of the program being executed.

(2) Applications and types
This function can be used to know the effect of processing time of each program on the total scan time when the

system is adjusted.
There are following three types.
• Program monitor list :

Section 6.13.1

• Interrupt program list monitor :
• Scan time measurement :

Section 6.13.2

Section 6.13.3

6.13.1 Program monitor list
(1) Definition

This function displays the processing time of the program being executed.
The scan time, number of execution times, and processing time by item can be displayed for each program.

(2) Execution
Selecting [Online]

[Monitor]

[Program monitor list] displays the Program monitor list screen.*1

Figure 6.59 shows an example of executing the program monitor list.
6.13 Execution Time Measurement
6.13.1 Program monitor list

(b)

(a)

(c)

Figure 6.59 Program monitor list screen
*1: During execution of a fixed scan execution type program, the scan time of the fixed scan execution type program is not
displayed.
"-" is displayed in the Scan time column.

6 - 69

(a) Total Scan Time
The monitoring time set in "WDT (Watchdog timer) setting" of the PLC RAS tab of the PLC parameter dialog
box and total scan time for each program type during execution by the CPU module are displayed.

1) Monitor time
The monitoring time of each program is displayed.
If the scan time exceeds this time, the CPU module detects ”WDT ERROR".

2) Sum of scan time
The total time of each item in "Scan execution part, detailed scan time" is displayed.
When constant scan time is set, the constant scan time is displayed.

(b) Scan execution part, detailed scan time
The details of the scan time are displayed.

1) Program
The total execution time of the scan execution type program is displayed.

2) END operation time
The END processing time is displayed.

3) Low speed program
Since a low-speed execution type program is not used "0.000" is displayed.

4) Constant waiting
The constant scan waiting time is displayed when the constant scan time is set.

(c) Execution status of each program
The execution status of a program selected at the program tab of the PLC parameter dialog box is displayed.

1) Program
The program name is displayed in the order set in the PLC parameter dialog box.

2) Execution
The program type set in the PLC parameter dialog box is displayed.

3) Scan time
The actual scan time (current value) is displayed.
When a program is in stop (standby) status, the scan time is displayed as 0.000 ms.

4) Execute count
The number of execution times of programs before monitoring is displayed, setting the measurement start as
"0". The number of execution times is displayed up to 65535 and returns to 0 when the 65536 is measured.
The execution times is held even when the program is stopped.

6 - 70

CHAPTER6 FUNCTIONS

Remark
When the POFF instruction is executed, a non-execution processing is performed for one scan.
The number of execution times displayed is the addition of the execution times of the non-execution processing.
For details of the POFF instruction, refer to the following.

QCPU Programming Manual (Common Instructions)

3
(3) Program start and stop

Program cannot be started and stopped from the Program list monitor screen.

(4) Precautions

The scan time of a fixed scan execution type program is not displayed during its execution.
"-" is displayed in the Scan time column.

6
7
8

6.13 Execution Time Measurement
6.13.1 Program monitor list

6 - 71

6.13.2 Interrupt program monitor list
(1) Definition
This function displays the number of executions of an interrupt program.
This function is used to check the execution status of the interrupt program.

(2) Execution
Selecting [Online]

[Monitor]

[Interrupt program monitor list] of GX Developer displays the Interrupt program

monitor list screen.
Figure Figure 6.60 shows an execution example of the interrupt program monitor list.

(b)

(a)

Figure 6.60 Interrupt program monitor list screen

(a) Execute count
The number of executions of an interrupt program is displayed.
This function starts counting after the CPU module is in the RUN status.
When the counting reaches 65536 times, it is reset to 0.

(b) Common comment
Device comments created to an interrupt pointer is displayed.

6 - 72

CHAPTER6 FUNCTIONS

6.13.3 Scan time measurement

Note6.6

Note1

(1) Definition

This function displays the processing time of set program section during ladder monitoring.
The time required for the subroutine and interrupt programs can be measured.

(2) Range specification of scan time measurement
There are following two types for specifying a scan time measurement range.
• Setting on the ladder monitor screen

• Setting on the scan time measurement screen

(3) When the subroutine program call instruction is in the measurement range
When the subroutine program call instruction (CALL) is in the range of scan time measurement, the scan time

includes the time required for processing a subroutine program.

Measurement range
Main
program

Subroutine
program

8
Measurement range

Figure 6.61 When subroutine program is in measurement range

The execution time of interrupt programs and fixed scan execution type programs are added.

Note1

Note6.6

Universal

When using the scan time measurement for the Q02UCPU, Q03UDCPU,Q04UDHCPU,Q06UDHCPU,Q13UDHCPU,
and Q26UDHCPU, check the versions of CPU module and GX Developer.(

Appendix 2)

6 - 73

6.13 Execution Time Measurement
6.13.3 Scan time measurement

(4) When interrupt programs/fixed scan execution type programs are executed in
the scan time measurement range

(5) Execution
Measure the scan time by the following procedure.
• Display the start of the ladder program where scan time is measured in GX Developer and set the monitor
mode.
• Select [Online]

[Monitor]

[Scan time measurement] to open the Scan time measurement screen.

• Enter the start and end steps and click the Start button.

Example When the start step is 52 and the end step is 105

Figure 6.62 Scan time measurement screen

Remark
When displaying the Scan time measurement screen after specifying the scan time measurement rage in the monitor
mode, the start and end steps are set in the specified range.
To specify the range, press the "Shift" key and click the mouse (The specified part is inverted).

Y20
50

M0
Y21

M1
Y22

104

106

END

Figure 6.63 Measurement range specification

6 - 74

CHAPTER6 FUNCTIONS

(6) Precautions
(a) Measurement range setting

Set the measurement range so that "Start step < End step" is satisfied.

(b) Minimum unit of measurement time

The minimum unit of measurement time is 0.01ms.
If the measurement time is less than 0.01ms, 0.000ms is displayed.

The execution time of one scan between the specified steps is displayed.

(d) When scan time cannot be measured

Scan time cannot be updated on the Scan time measurement screen in the following cases.
• When the branch instruction is specified the to end step

Example The JMP instruction is specified to the end step.
0

Start step: 3

End step: 6
5

JMP P0

6.13 Execution Time Measurement
6.13.3 Scan time measurement

• When only the start step is executed

Example The specified end step is not executed by the JMP instruction.
0

Start step: 3
3

The specified end step
is not executed due to
the JMP instruction.

JMP P0
End step: 9

END

6 - 75

• When the end step is executed before the start step

Example The start step is specified as the next step of the CALL instruction and the end step is
specified in a subroutine program executed by the CALL instruction.
0

CALL P0
Start step: 3

The start step is executed
after the end step due to the
CALL instruction.

FEND
End step: 8

RET

• When the start step is executed continuously

Example Only the start step is specified between the FOR and NEXT instructions.
3

FOR K2

Start step: 8

"The start step is executed
continuously since it is specified
between the FOR and NEXT
instructions."

6 - 76

NEXT
End step: 13

CHAPTER6 FUNCTIONS

6.14 Sampling Trace Function

Note6.7

(1) Definition
This function samples the data of the specified device at a preset timing and at a preset interval

(sampling cycle), and then stores the trace results in the sampling trace file.Note1

(2) Application
This function is useful to check the change of the device data used in the program during debugging at

a preset timing.
In addition, this function is used to read the device data at trigger condition establishment.

(3) Sampling trace file
This file stores the trace setting necessary for executing the function and trace results.

6
Sampling trace file can be stored only in the Standard RAM or SRAM card. (

Section 5.1.1)

7
8

6.14 Sampling Trace Function

Note1

Note6.7

Universal

The Q00UJCPU does not support the sampling trace function.

6 - 77

(4) Sampling trace operation
(a) Operation of the CPU module
When a sampling trace trigger is issued by GX Developer, the CPU module executes traces for the preset
number of times.
The number of traces will be a value of which the number of bytes for the sampling trace area divided by the
number of bytes of the specified device (N1 + N2 + N3 + word device points
2).
*1:
*2:

2 + (bit device points/16)

*1 *2

Round up the result of "bit device points/16" in the expression to the right of the decimal point.
Add the following values to N1 to N3 according to the items selected under the trace additional information of the trace
condition setting.
•N1: When "Time(sec)" is selected, add "4".

•N2: When "Step no." is selected, add "10".
•N3: When "Program name" is selected, add "8".
CPU module
GX Developer

Standard RAM/memory card
*3

Sampling trace area

Specified
device data
Device
area
File
register
area

Sampling trace area
1
2
3
4
5
6

1st trace data
2nd trace data
3rd trace data
4th trace data
5th trace data
6th trace data

1
2
3
4
5
6

n-1
n

(n-1)th trace data
n th trace data

n -1
n

Read out the
trace data to
a peripheral.

The specified
number of trace
data sets is
displayed.
Sampling trace

When data is stored for n th time,
the next data overwrites the 1st data.
Figure 6.64 Sampling trace operation

*3:

6 - 78

When the trigger is issued, the CPU module samples data for the preset number of times and latches the data in the
sampling trace area.

CHAPTER6 FUNCTIONS

(b) Operation of the special relay

1) When the sampling trace is executed normally
The execution status of the sampling trace can be checked in the special relay listed in Table6.22.

Table6.22 Execution status of the sampling trace
Number

Name

Description

SM800

Trace preparation

SM801

Trace start

Turns on when the sampling trace is started.

Trace execution in

Turns on during sampling trace execution.

progress

The relay is used to check the sampling trace execution status.

Trace trigger

A trigger turns on upon the status change of the relay (off

SM802
SM803

Turns on when the trace setting in GX Developer is written to the CPU module.
The relay is used to check the sampling trace enable status.

on).

Turns on when any of the following condition is established.
• A trigger is issued by GX Developer.
SM804

After trace trigger

• The TRACE instruction is executed.
• SM803 turns on.

• Detailed setting (Device and Step No.)
The relay is used to check the trigger condition establishment status.
SM805

Trace completed

Turns on when the sampling trace is completed.

SM826

Trace error

Turns on when an error occurs during sampling trace execution.

7
8

Figure 6.65 shows the operation flow chart of the special relay for sampling trace execution.
Trace start requested

Trigger condition
established

Trace completed
6.14 Sampling Trace Function

Number of traces after trigger

Total number of traces

SM80
(trace ready)

SM801
(trace start)

SM802
(Trace execution in progress)
SM803
(Trace trigger)

SM804
(After trace trigger)
SM805
(Trace completed)
Figure 6.65 Operation flow chart of the special relay (for sampling trace execution)

6 - 79

2) When the sampling trace is interrupted
If SM801 (Trace start) is turned off during sampling trace, execution of the sampling trace will be interrupted.
When the sampling trace is interrupted, the trace count is cleared.
The sampling trace restarts by turning on SM801.
Trigger
executed

SM801
off

Number of
traces
after trigger

SM801
on

The trace count is cleared.

Trigger
executed

Trace
completed

Number of
traces
after trigger

SM800
(Trace preparation)

SM801
(trace start)
SM802
(Trace execution in progress)

SM803
(Trace trigger)
SM804
(After trace trigger)
SM805
(Trace completed)
Figure 6.66 Operation flow chart of the special relay (for sampling trace interruption)
*1: SM801 also turns off when the sampling trace is interrupted by GX Developer.

6 - 80

CHAPTER6 FUNCTIONS

(5) Operating procedure
Select [Online]

[Trace]

[Sampling trace...] in GX Developer.

On the screen opened, select the method for operating the sampling trace.

• "Wizard setting/execution"
(

GX Developer Version 8 Operating Manual)

• "Individual setting/execution"
(

(5)(a) in this section)

(a) Setting "Trace data (setting + result) storage" and "Trace execution method"
On the screen opened, set the trace data storage location and trace execution method.

5
2)

6
1)

7
8

6.14 Sampling Trace Function

Figure 6.67 Sampling trace screen

1) Trace data (setting + result) storage
Select the memory for storing the trace data and the file for writing the trace conditions.
Select either "Standard RAM" or "Memory card (RAM)" for the target memory setting.
Trace results will be stored in the memory set here under the selected file name.

2) Trace execution method
Select either of the following trace execution method.
• "Execute trace after overwriting the current trace setting to the PLC":
The CPU module executes the sampling trace after the trace settings are overwritten to the existing
sampling trace file.
• "Execute trace for the settings written in PLC":
The CPU module executes the sampling trace with the trace settings in the sampling trace file selected
for "Trace data (setting + result) storage".

6 - 81

(b) Setting trace conditions
Set trace conditions on the screen opened by clicking the Trace condition setting button on the screen
shown in Figure 6.67.
On the Trace condition settings screen, set the following items.
• Number of traces ("No. of traces", "After trigger number of times")
• Trace point setting ("Trace point setup")
• Trigger point setting ("Trigger point setup")
• Additional information ("Trace additional informaton")
• Auto start setting ("Auto start trace")

Figure 6.68 Trace condition settings screen

1) No. of traces
There are two items need to be set: "No. of times" and "After trigger number of times".
• No. of times: Select the number of executions from the start to the end of sampling trace.
• After trigger number of times: Select the number of executions from the trigger point to the end of
sampling trace.
Trace started

Trigger point

Trace completed

Number of traces
after trigger
Total number of traces
Figure 6.69 Relationship between two setting items

Set the numbers for each items within the following setting range.
("After trigger number of times")

6 - 82

("No. of times")

(8192)

CHAPTER6 FUNCTIONS

2) Trace point setup

Select the timing for collecting trace data from the items listed in Table6.23.
Table6.23 Trace point setup item
Item

Description

Each scan

Collects trace data during END processing of each scan.

Interval

Collects trace data at specified time intervals.
Collects trace data in a cycle of 0.88m

specified time intervals.

Since data is collected at the timing of interrupt program (I45) execution, trace data can be collected only when
Each multiple CPU high

the following conditions are all satisfied.

speed communication

• The multiple CPU high-speed main base unit (Q3

DB) is used.

cycle*1

• The multiple CPU system where two or more CPU modules are used and the multiple CPU high speed
transmission function is set.

• Interrupt pointer (I45) exists in a program.
• Interrupts are enabled and interrupt mask of I45 is cancelled.
A trace point (device and/or step number) needs to be set.
The following devices can be set as a trace point.
• Bit device: X(DX), Y(DY), M, L, F, SM, V, B, SB, T(contact), ST(contact), C(contact), FX, FY, J

\X, J

\Y,

• Word device: T(current value), ST(current value), C(current value), D*1, SD, W*2, SW, R, Z, ZR, FD, U

\G,

Detail

\B, J

\W, J

\SB, BL

\SW, U3E

The following modifications are available for the above devices.

7
8

• Digit specification of bit device
• Bit specification of word device
• Indirect specification of word device
• Index modification

Section 6.11.1.
If a device is set as a trace point, the timing when the word device value is changed can be selected as a data
collection timing.
*1: The extended data register (D) is included.
*2: The extended link register (W) is included.

3) Trace additional information
Set the information added for each trace.
Select one or more items from the following. (If not necessary, do not select any item.)
• Time(sec.): Stores the time when the trace was executed.
• Step no.: Stores the step number where the trace was executed.
• Program name: Stores the program name where the trace was executed.

6 - 83

6.14 Sampling Trace Function

The setting method and trace data collection timing are same as those for the monitor condition setting in

4) Trigger point setup
Select the trigger point from the items listed in Table6.24.
Table6.24 Trigger point setup item
Item

Description

At the time of TRACE
instuction execution

The time of execution of the TRACE instruction is set as a trigger.

At the time of trigger
operation

The time when a trigger is issued by GX Developer is set as a trigger.

from GX Developer
A trace point (device and/or step number) needs to be set.
The following devices can be set as a trace point.
• Bit device: X(DX), Y(DY), M, L, F, SM, V, B, SB, T(contact), ST(contact), C(contact), FX, FY
• Word device: T(current value), ST(current value), C(current value), D*1, SD, W*2, SW, R, ZR
The following modification is available for the above devices.
• Bit specification of word device

Detail

Indirectly-specified devices cannot be set.
The setting method and trace data collection timing are same as those for the monitor condition setting in
Section 6.11.1.
If a device is set as a trace point, the timing when the word device value is changed can be selected as a data
collection timing.
*1: The extended data register (D) is included.
*2: The extended link register (W) is included.

5) Auto start trace

Note6.8Note1

When the checkbox is selected, the sampling trace will be started automatically when:
• the CPU module is powered off and then on after the trace settings are written, or
• the CPU module status is changed from STOP to RUN.

When the CPU module is powered off and then on, reset, or the CPU module status is changed from STOP to RUN to
rewritten the sampling trace settings, the settings cannot be rewritten to the CPU module regardless of the status of SM829
(Forced registration specification of trace setting) if the trigger condition has already been established.
In this case, the CPU module will be in the status where the sampling trace setting registration has been canceled. SM800
(Trace preparation) turns off.

Note1

Note6.8

Universal

When using the sampling trace auto start function for the Q02UCPU, Q03UDCPU, Q04UDHCPU, Q06UDHCPU,
Q13UDHCPU, or Q26UDHCPU, check the versions of the CPU module and GX Developer. (

6 - 84

Appendix 2)

CHAPTER6 FUNCTIONS

Set trace data on the screen opened by clicking the Trace data setting button on the screen shown in
Figure 6.67.

Table6.25 shows the devices can be set as trace data.

3
4
5
6
7
8

Figure 6.70 Trace data settings screen

Table6.25 Devices can be set as trace data
Description
The following bit devices can be set up to 50 points.
X, DX, Y, DY, M, L, F, SM, V, B, SB, T(contact), T(coil), ST(contact), ST(coil), C(contact),

Bit device

C(coil), J

\X, J

\Y, J

\B, J

\SB, BL

The following word devices can be set up to 50 points.
T (current value), ST (current value), C (current value), D*1, SD, W*2,SW, R, Z, ZR,
U

Word device

\G, J

\W, J

\SW, U3E

The following modifications are available for the above devices.
• Digit specification of bit device
• Bit specification of word device
• Index modification
Indirectly-specified devices cannot be set.

*1: The extended data register (D) is included.
*2: The extended link register (W) is included.

6 - 85

6.14 Sampling Trace Function

Item

(d) Writing the trace condition settings and trace data settings
Write the set trace conditions and trace data to the memory selected as a sampling trace file for "Trace data
(setting + result) storage".
Click the Write to PLC button on the screen shown in Figure 6.67 to write the settings.

When storing the sampling trace file into a memory card (SRAM card), more than one sampling trace files can be stored by
changing the file name.
For the standard RAM, only one sampling trace file can be stored.
When multiple sampling trace files are used, use the memory card (SRAM card).

(e) Executing the sampling trace
Click the Trace execution button on the screen shown in Figure 6.67 to open the Execute sampling trace
screen.
Select an item shown in Table6.26 and click the Execute button.

Displayed only when status
display is selected

Figure 6.71 Execute sampling trace screen

Table6.26 Trace point setting
Item
Start trace

Description
Starts the function, and starts counting the number of sampling trace executions.
Stops the function, and clears the total sampling trace execution count and the

Stop trace

execution count after trigger.
(To restart the function, select "Start trace" again.)
Executes a trigger, and starts counting the number of sampling trace executions after

Execute trigger

trigger.
The function will be ended when the trace execution count after trigger reaches the
preset count.

Registry trace (For start trace from Program)

6 - 86

Registers trace data when a program is executed.

CHAPTER6 FUNCTIONS

(f) Displaying trace results

Read trace results form the CPU module and display the data.
1) Click the Trace result PLC read button on the screen shown in Figure 6.71 to read trace results.

2) Click the Trace result button on the same screen to display the trace results read.
The trace results shows the on/off status of each bit device for every sampling cycle and the current value of
each word device.

3
4
5
6
7

Figure 6.72 Trace result screen

Data when the trigger
conditions are satisfied.

Data when trigger condition is met

Figure 6.73 Trace result

6 - 87

6.14 Sampling Trace Function

Specified devices are read when the condition selected in "Trigger point setup" (trigger condition) is established.
Therefore, when devices are sampled in every scan and the sampling is finished by trigger operation from a peripheral, the
data is sampled twice because timing of the sampling is the same with that of the establishment of trigger condition.

(6) Method for clearing trace execution status
The trace execution status can be cleared by latch clear using the remote latch clear operation.
(

Section 6.6.4)

To perform the sampling trace again after latch clear, select “Start trace” or “Registry trace”.

(7) Precautions
(a) Areas where sampling trace can be performed
The sampling trace can be performed from other stations on the network or serial communication module.
However, it cannot be performed from multiple devices simultaneously. It can be performed from one device to
the CPU module.

(b) Holding and clearing the trace setting
The trace setting (sampling trace file) registered with the CPU module is latched.
Even if the CPU module is powered off and then on or is reset, the sampling trace can be performed again with
the trace setting at registration.
However, the previous trace result cannot be read.
Also in the following cases, even when the trigger condition of the sampling trace is established, the latched
trace setting will be cleared since the condition is not recognized as the trigger condition (SM800 (Trace
preparation) turns off).
Register the trace setting again with GX Developer.
1) When selecting "Standard RAM" in "Target memory", configuring the setting that changes the local device
size in the standard RAM*1, writing parameters to the CPU module, and then performing any of the
following operations
• The CPU module is powered off and then on
• The CPU module is reset.
• The CPU module is set from STOP to RUN.
*1: The operation includes when a local device is created.

2) When selecting "Standard RAM" in "Target memory” and the sampling trace file is corrupt, either of the
following operations were performed.
• The CPU module is powered off and then on.
• The CPU module is reset.

To keep the trace result to the personal computer even after configuring the setting that changes the local device size,
perform the following operations.
• Click the Trace result
personal computer.

6 - 88

PLC read

• Click the

Trace result

• Click the

Create CSV file

button on the screen shown in Figure 6.71 to read the trace result to the

button on the screen shown in Figure 6.71 to display the trace result.
button on the screen shown in Figure 6.72 to save the trace result in CSV format.

CHAPTER6 FUNCTIONS

3) When selecting "Memory card (RAM)" in "Target memory" while the SRAM card where the sampling trace
file has been registered is not mounted, either of the following operations were performed.
• The CPU module is powered off and then on.

1
2

• The CPU module is reset.
4) When selecting "Memory card (RAM)" in "Target memory" and the sampling trace file is corrupt, either of the

following operations were performed.
• The CPU module is powered off and then on.
• The CPU module is reset.

When reading the trace result, read it while the CPU module is in the RUN status.

(d) Sampling trace registration while the trigger condition is established
Even if the trigger condition is established, the sampling trace setting can be registered by the following
procedure.
1) Turn on SM829 (Forced registration specification of trace setting).

6
7

2) Select “Individual setting/execution” in the screen shown in Figure 6.67.
3) Click the Trace execution button, select “Registry trace (For start trace from Program)”, and click the

Execute button.

When the sampling trace is registered by the procedures above (d) 1) to 3), start the sampling trace in status where the
trigger condition is not established.
If the trigger condition has been established when the sampling trace starts, the trigger may not be normally executed.

●

When selecting "Wizard setting/execution" in the Sampling trace screen shown in (d) 2), and starting the sampling
trace, the trigger may not be normally executed, although the sampling trace setting can be registered.

(e) When a file register is selected as a specified device by the detail setting of trace
conditions
When a file register is selected as a specified device by the detail setting of trace point setting and trigger point
setting, do not change the block numbers of file register file and file register after trace registration.
Trace data may not be normally sampled.

(f) Trace point setting
When setting the trace point setting per each time or per multiple CPU high speed transmission cycle, pay
attention to the sampling interval and sampling processing time for one sampling since the sampling trace is
performed as interrupt processing.
If the sampling processing time for one sampling is long, “WDT ERROR” may be detected.

6 - 89

6.14 Sampling Trace Function

●

(g) Performing sampling trace during execution of another sampling trace
The first sampling trace is performed normally. The second sampling trace cannot be performed.

(h) Executing online change
When sampling trace and online change are performed simultaneously, they operate as follows.

1) Performing sampling trace during online change
• The trace point or trigger point is specified by the step number:
The online change is completed normally but the sampling trace is not performed.
• The trace point and trigger point are specified by except the step number:
Both the online change and sampling trace can be performed.

2) Performing online change during execution of sampling trace
• The trace point or trigger point is specified by the step number:
The sampling trace is suspended but the online change is normally performed.
• The trace point and trigger point are specified by except the step number:
Both the online change and sampling trace can be performed.

6 - 90

CHAPTER6 FUNCTIONS

6.15 Debug Function from Multiple GX Developers

(1) Definition
This function allows debugs from multiple GX Developers connected to such as a CPU module or serial

communication module.
When files are divided according to the processes or functions, this function can be used when multiple

GX Developers debug different files.

(2) Description

Table6.27 shows combinations of the debug functions executable from multiple GX Developers.
Table6.27 Combinations of the debug functions

Function executed later
Function in execution

Monitor

Online change

Monitor

Online change

Execution time
measurement

Sampling trace

Scan measurement

Sampling trace
: Can be performed simultaneously,
*1: Since only one GX Developer can set the monitor conditions (

: Can be performed from one GX Developer.
Section 6.11.1), other GX Developers cannot set

them.
*2: The monitoring with monitor conditions and online change cannot be performed simultaneously.
*3: For how to perform Nonline change to a file from multiple GX Developers, refer to Section 6.15.2.

(1) Definition
This function allows simultaneous monitoring from multiple GX Developers connected to such as a CPU module
or serial communication module.
Monitor target

GX Developer
GX Developer
Figure 6.74 Simultaneous monitoring

Creating a user setting system area allows high-speed monitoring from multiple GX Developers (Setting a
monitoring file for the host station is unnecessary).

6 - 91

6.15 Debug Function from Multiple GX Developers
6.15.1 Simultaneous monitoring from multiple GX Developers function

6.15.1 Simultaneous monitoring from multiple GX Developers function

(2) Setting for simultaneous monitoring from multiple GX Developers
Create a user setting system area in the following procedure.
•
•
•
•

Select [Online]
[Format PLC memory] in GX Developer to open the screen shown in Figure 6.75.
Select "Program memory/Device memory" in "Target Memory".
Select "Create a user setting system area" in "Format Type".
Set the number of steps for the system area (in increments of: 1K step).

Figure 6.75 System area setting (when 1K step is set)

Table6.28 shows the maximum number of steps settable in the system area.
1K step is available for a monitoring file from another station.

Table6.28 Maximum size of steps settable in the system area

Maximum size of settable step

System area for monitoring from another station

Maximum 15K steps

Maximum 15

(3) Precautions
(a) Monitor condition setting
The monitor conditions can be set from one GX Developer.

(b) Necessity of system area setting
Although multiple GX Developers in other stations can simultaneously monitor a CPU module without the user
setting system area, the monitor speed will be slow.
Since the system area is set in the program memory, the area for storing programs reduces by the size of set
system area.

(c) The number of GX Developers for which high-speed monitoring can be set
The number of GX Developers that can simultaneously monitor a CPU module at high-speed is “the number of
user setting system areas (the number of K steps) + 1”.
For example, when user setting system area of 15K steps is created, maximum 16 GX Developers can
simultaneously monitor a CPU module at high-speed.

6 - 92

CHAPTER6 FUNCTIONS

6.15.2 Online change function from multiple GX Developers

(1) Definition
This function allows multiple GX Developers to perform online change to one file or different files.

• Online change to one file:
Select "Relative step No. by pointer".

• Online change to different files:
• The writing can be executed without selecting "Relative step No. by pointer".

4
5
6
Personal computer A
(GX Developer)

Personal computer B
(GX Developer)

Figure 6.76 Simultaneous online change from multiple GX Developers

(2) Operating procedure for performing online change to one file
Select [Tools]

[Options]

tab in GX Developer.

Set a pointer for online change beforehand.
6.15 Debug Function from Multiple GX Developers
6.15.2 Online change function from multiple GX Developers

6 - 93

(a) Setting “After conversion writing behavior” and “Step No. specification used in writing”
Set them as follows:
1) Select "Write during RUN (while PLC is running)" in "After conversion writing behavior".
2) Select “Absolute step No. (default)” or “Relative step No. by pointer” in “Step No. specification used in
writing”.

Figure 6.77 Options screen

(b) Performing online change
Display the ladder including the specified pointer and write the changed ladder during RUN.

(3) Precautions
Precautions for online change from multiple GX Developers are the same as those for usual Write during RUN
(

6 - 94

Section 6.12.3).

CHAPTER6 FUNCTIONS

6.16 Watchdog Timer (WDT)

(1) Definition
This function serves as an CPU module internal timer to detect errors of CPU module hardware and sequence
programs.

2
3

(2) Setting and resetting
(a) Setting
The watchdog timer setting can be changed in the PLC RAS setting of PLC parameter.
The default is set to 200ms.
The setting range is 10 to 2000ms (in increments of: 10ms).

4
5

(b) Reset
The CPU module resets the watchdog timer during END processing.
• The watchdog timer does not time up when the CPU module operates normally and the END/FEND
instruction is executed within the setting value of watchdog timer.
• The watchdog timer times up when the scan time of the sequence program is extended and the END/
FEND instruction could not be executed within the setting value of watchdog timer due to the hardware
failure of the CPU module or execution of an interrupt program/fixed scan execution type program.

(3) When the watchdog timer times up

6
7
8

“WDT ERROR” is detected and the following status occurs:
1) The CPU module turns off all outputs.
2) The RUN LED on the front of the CPU module turns off and the ERR. LED starts flashing.

6.16 Watchdog Timer (WDT)

3) SM1 turns on and the error codes 5000 and 5001 are stored in SD0.

(4) Precautions
(a) Watchdog timer error
An error is observed within the range of 0 to 10ms.
Set a watchdog timer while considering such an error.

6 - 95

(b) Resetting a watchdog timer when a program is repeatedly executed between the FOR and
NEXT instructions
The watchdog timer can be reset by executing the WDT instruction in the sequence program.
To avoid the time up of watchdog timer while a program is repeatedly executed between the FOR and NEXT
instructions, reset the watchdog timer by the WDT instruction.
FOR K1000

Program repeatedly executed
Repeated in
1,000 times

MO
WDT

WDT reset

NEXT
Resetting watchdog timer when the a program is executed between the FOR and NEXT instructions

Figure 6.78 Resetting a watchdog timer when the program is executed between the FOR and NEXT instructions

(c) Scan time when using the WDT instruction
The scan time value is not reset even if the watchdog timer is reset in the sequence program.
The scan time is measured up to the END instruction.
Internal processing time
END

Sequence program
Scan execution
0 type program A

Internal
processing time

Scan execution
type program B END

Scan execution
0 type program A

Next scan time

Scan time
WDT reset
(CPU module internal
processing)

WDT measurement time

WDT reset
(CPU module internal
processing)

Figure 6.79 Watchdog timer reset

●

A scan time is time required for the CPU module to operate the sequence program from step 0 and return
to the step 0 in the sequence program with the same file name.

●

The scan time depends on the execution status of the following:
• Instructions used in the program
• Interrupt program and fixed scan execution type program
To keep the same scan time in every scan, use the constant scan function. (

6 - 96

Section 6.2)

CHAPTER6 FUNCTIONS

6.17 Self-diagnostic Function

(1) Definition

This function allows the CPU module to diagnose itself to check for errors.
This function aims to preventive measures and prevention of malfunction of the CPU module.

(2) Self-diagnostic timing
When an error occurs at power-on or during the RUN or STOP status of the CPU module, the error is detected
and displayed by the self-diagnostic function, and the CPU module stops an operation.
Note that errors cannot be detected by the function depending on error status or an instruction executed.
When the operation is not stopped by the function, configure a safety circuit external to the programmable
controller so that the entire system operates safely.

3
4
5

(3) Checking errors
(a) LED status

When the CPU module detects an error, the ERR. LED turns on.

(b) Storage location of error information and error check
When the CPU module detects an error, the special relays (SM0, SM1) turn on and the error information (error
code) are stored in the special register (SD0).
When several errors are detected, the latest error code is stored in SD0.
Use the special relays and special register in a program as an interlock for the programmable controller and
mechanical system.

7
8

(4) Checking error history

6 - 97

6.17 Self-diagnostic Function

To check the latest error code, select [Diagnostics]
[PLC diagnostics]
"Error log” in GX Developer.
The error data history are backed up using a battery even after the programmable controller is powered off.

(5) CPU module operation at error detection
(a) Mode at error detection
When an error is detected by the self-diagnostic function, the CPU module enters either of the following modes.

1) Mode that stops CPU module operation
When an error is detected, the CPU module stops an operation and turns off all external outputs of the
module set to "Clear" in "Error time output mode" in “Detailed setting” of the I/O assignment tab of the PLC
parameter dialog box (Outputs (Y) in the device memory are held).
Note that the external outputs of the module set to "Hold" in "Error time output mode" are held (Outputs (Y) in
the device memory are held).

2) Mode that continues CPU module operation
When an error is detected, the CPU module operates programs other than the one (instruction) where an
error occurred.

(b) Errors whether to continue or stop an operation can be selected
Whether to continue or stop an operation can be selected in the following errors.

1) Errors whether to continue or stop an operation can be selected in the PLC RAS tab of the
PLC parameter dialog box
• Computation error (including SFC program)
• Expanded command error (setting for future extension)
•
•
•
•
•
•

Fuse blown
Module verify error
Intelligent module program execution error
File access error
Memory card operation error
External power supply OFF (setting for future extension)

For example, when “Module verify error” is set to "Continue", an operation is continued from the I/O number
before an error.
For details of errors, refer to “Self-diagnostics list”. (

(7) in this section)

2) Error whether to continue or stop an operation can be selected in “Detailed setting” in the
I/O assignment tab of the PLC parameter dialog box
• Intelligent function module error

6 - 98

CHAPTER6 FUNCTIONS

(6) Error check options
Whether to check the following errors or not can be selected in the PLC RAS tab of the PLC parameter dialog box
(All the options are selected (executed) by default).
1) Carry out battery check

2) Carry out fuse blown check

3) Verify module
4) Check device range at indexing.
5) Diagnose redundant power supply system.

Note6.9Note1

4
5
6
7
8

6.17 Self-diagnostic Function

Note1

Note6.9

Universal

When setting the diagnostic function of the redundant power supply system for the Q02UCPU,
Q03UDCPU, Q04UDHCPU, Q06UDHCPU, Q13UDHCPU, or Q26UDHCPU, check the versions of the
CPU module and GX Developer. (

Appendix 2)

6 - 99

(7) Self-diagnostics list
The following table shows the self-diagnostics performed by the CPU module.
To check the error messages in the "Error message" column of Table6.29, select [Diagnostics]

[PLC

diagnostics] of GX Developer.
Table6.29 Self-diagnostics list

Diagnostics

Error message

Diagnostic timing

CPU
module
status

LED status
RUN

ERR.

CPU error

MAIN CPU
DOWN

• Always

Stop

Off

Flashi
ng

END instruction
not executed

END NOT
EXECUTE

• Execution of the
END instruction

Stop

Off

Flashi
ng

SFC program
execution error

SFCP. END
ERROR

• Execution of a
SFC program

Stop

Off

Flashi
ng

RAM check

RAM ERROR

• Power-on/reset

Stop

Off

Flashi
ng

Operation circuit
check

OPE.CIRCUIT
ERR.

• Power-on/reset
• Execution of the
END instruction

Stop

Off

Flashi
ng

Fuse blown*1 *2

FUSE BREAK
OFF

• Always

Stop/
continue

Off/on

Flashi
ng/on

I/O interrupt error

I/O INT.
ERROR

• Occurrence of an
interrupt

Stop

Off

Flashi
ng

LAN CTRL.
DOWN

• Power-on/reset

Stop

Off

Flashi
ng

SP.UNIT
DOWN

• Power-on/reset
• Execution of the
FROM/TO
instructions
• Execution of the
intelligent
function module
dedicated
instruction
• Execution of the
END instruction

Stop/
continue

Off/on

Flashi
ng/on

Control bus error

CONTROLBUS ERR.

• Power-on
• Execution of
END processing
• Execution of the
FROM/TO
instructions
• Execution of the
intelligent
function module
dedicated
instruction
• Always

Stop

Off

Flashi
ng

Momentary power
failure

AC/DC DOWN

• Always

Continue

Off

Multiple CPU high
speed bus error

MULTI-C.BUS
ERR.

• Power-on/reset

Stop

Off

Flashi
ng

LAN controller

failure

Hardware
Intelligent function
failure
module error *1

Q00U
Q00UJ CPU,
Q01U
CPU
CPU

: Self-diagnostics is performed.

Q02U QnUD(H)
CPU
CPU

Built-in
Ethernet
port QCPU

: Self-diagnostics is not performed.
(To the next page)

6 - 100

CHAPTER6 FUNCTIONS

Table6.29 Self-diagnostics list (continued)

Diagnostics

Error message

CPU
module
status

RUN

ERR.

Voltage drop of
power supply for
redundant base
unit

SINGLE PS.
DOWN

• Always

Continue

Redundant
power supply
module failure

SINGLE PS.
ERROR

• Always

Continue

UNIT VERIFY
ERR.

• Execution of
the END
instruction

Base
assignment
error

BASE LAY
ERROR

• Power-on/reset

Intelligent
function module
assignment
error

SP.UNIT LAY
ERR.

Module
verification*1*2

Intelligent
program
execution

Off/on

Flashi
ng/on

Stop

Off

Flashi
ng

Stop

Off

Flashi
ng

Stop/
continue

• Power-on/reset
• Switching from
STOP to RUN

• Execution of
the FROM/TO
instructions

Stop/
continue

Off/on

Flashi
ng/on

Intelligent
function module
version error

SP.UNIT
VER.ERR

• Power-on/reset

Stop

Off

Flashi
ng

No parameter

MISSING
PARA.

• Switching from
STOP to RUN

Stop

Off

Flashi
ng

Boot error

BOOT ERROR

• Power-on/reset

Stop

Off

Flashi
ng

Backup error

RESTORE
ERROR

• Power-on/reset

Stop

Off

Flashi
ng

ICM.OPE.
ERROR

• Mounting/removal
of the memory
card

Stop/
continue

Off/on

Flashi
ng/on

Stop

Off

Flashi
ng

Stop/
continue

Off/on

Flashi
ng/on

Stop

Off

Flashi
ng

Stop

Off

Flashi
ng

Stop

Off

Flashi
ng

Memory card
operation error*1

• Power-on/reset

Q00UJ
CPU

Q00U
CPU,
Q01U
CPU

Q02U
CPU

QnUD(H)
CPU

Built-in
Ethernet
port
QCPU

3
4
5
6
7
8

• Power-on/reset
File setting error

File access
error*1
Instruction
execution
disabled

FILE SET
ERROR

• Writing to
programmable
controller

FILE OPE.
ERROR

• Execution of an
instruction

CANëT
EXE.PRG.

• Power-on/reset
• Switching from
STOP to RUN

• Power-on/reset

Parameter
error

Parameter
setting check

PARAMETER
ERROR

Link parameter
error

LINK
PARA.ERROR

• Switching from
STOP to RUN
• Writing to
programmable
controller

• Power-on/reset
• Switching from
STOP to RUN

: Self-diagnostics is performed.

6.17 Self-diagnostic Function

SP.UNIT
ERROR

error*1
Handling
error

Diagnostic timing

LED status

: Self-diagnostics is not performed.
(To the next page)

6 - 101

Table6.29 Self-diagnostics list (continued)

Diagnostics

LED status

CPU
module
status

RUN

ERR.

Error message

Diagnostic timing

SFC parameter error

SFC
PARA.ERROR

• Switching from
STOP to RUN
• Writing to
programmable
controller

Stop

Off

Flashi
ng

Intelligent function module
parameter error

SP.PARA.
ERROR

• Power-on/reset

Stop

Off

Flashi
ng

Password error

REMOTE
PASS.ERR

Stop

Off

Flashi
ng

Stop

Off

Flashi
ng

Stop

Off

Flashi
ng

Stop

Off

Flashi
ng

Stop

Off

Flashi
ng

Off/on

Flashi
ng/on

• Power-on/reset
• Switching from
STOP to RU

Q00UJ
CPU

Q00U
CPU,
Q01U
CPU

Q02U
CPU

QnUD(H)
CPU

Built-in
Ethernet
port
QCPU

• Power-on/reset
Instruction code check

No END instruction

INSTRUCT.
CODE ERR

MISSING END
INS.

• Switching from
STOP to RUN

• Execution of an
instruction
• Power-on/reset
• Switching from
STOP to RUN

• Power-on/reset
CANëT SET(P)
Pointer setting error

• Power-on/reset
CANëT SET(I)

• Switching from
STOP to RUN

OPERATION
ERROR

• Execution of an
instruction

FOR NEXT
ERROR

• Execution of an
instruction

Stop

Off

Flashi
ng

CANëT
EXECUTE(P)

• Execution of an
instruction

Stop

Off

Flashi
ng

CANëT
EXECUTE(I)

• Execution of an
instruction

Stop

Off

Flashi
ng

Instruction
execution
disabled

INST. FORMAT
ERR.

• Execution of an
instruction

Stop

Off

Flashi
ng

Dedicated
instruction of
multiple CPU high
speed bus error

MULTI
COM.ERROR

• Execution of an
instruction

Stop

Off

Flashi
ng

CANëT
SET(BL)

• Switching from
STOP to RUN

Stop

Off

Flashi
ng

SFC step
configuration
error

CANëT SET(S)

• Switching from
STOP to RUN

Stop

Off

Flashi
ng

SFC execution
error

SFC EXE.
ERROR

• Switching from
STOP to RUN

Stop

Off

Flashi
ng

Operation
error*1 *4
FOR to NEXT
instructions
structure error
CALL to RET
instructions
structure error
Interrupt
program error

Program
error

• Switching from
STOP to RUN

SFC block
configuration
error

Stop/
continue

: Self-diagnostics is performed.

: Self-diagnostics is not performed
(To the next page)

6 - 102

CHAPTER6 FUNCTIONS

Table6.29 Self-diagnostics list (continued)

Diagnostics

SFC syntax

Off

BLOCK
EXE.ERROR

• Execution of an
instruction

Stop

Off

Flashi
ng

STEP
EXE.ERROR

• Execution of an
instruction

Stop

Off

Flashi
ng

WDT ERROR

• Always

Stop

Off

Flashi
ng

PRG.TIME OVER

• Always

Continue

MULTI CPU
DOWN

• Always
• Power-on/reset

Stop

Off

Flashi
ng

Multiple CPU
systems
execution error

MULTI
EXE.ERROR

• Power-on/reset

Stop

Off

Flashi
ng

Multiple CPU
systems
consistency
error

CPU LAY.
ERROR

• Power-on/reset

Stop

Off

Flashi
ng

Another CPU
minor error

MULTI CPU
ERROR

• Always

Continue

Stop

Off

SFC block
execution error

Watchdog error
supervision
Program timeAnother CPU
major error

system
s error

ERR.

Stop

out

CPU

RUN

Flashi
ng

execution error

Multiple

CPU
module
status

• Switching from
STOP to RUN

SFC step

CPU
error

Diagnostic timing

SFCP. FORMAT
ERR.

error
Program
error

Error message

LED status
Q00UJ
CPU

Q00U
CPU,
Q01U
CPU

Q02U
CPU

QnUD(H)
CPU

Built-in
Ethernet
port
QCPU

2
3
4
5
6
7
8

• Power-on/reset

Annunciator check

INCORRECT
FILE

F****

• Switching from
STOP to RUN
• Writing to
programmable
controller

• Execution of an
instruction

Continue

Off

USER
LED
turns
on.

: Self-diagnostics is performed.

: Self-diagnostics is not performed

*1: The operating status can be changed to "Continue" with the parameter setting of GX Developer The default is set to "Stop".
*2: This option can be set "not checked" (set "checked" by default) with the parameter setting of GX Developer. Also, this option is not
checked while SM251 is on.
*3: This option can be set "not checked" (set "checked" by default) with the parameter setting of GX Developer.
*4: This error includes an operation error when device range check is made at index modification.
*5: The CPU module having the serial number (first five digits) is "10042" or later can be diagnosed.

6 - 103

6.17 Self-diagnostic Function

File diagnostic check

6.17.1 LEDs indicating errors
When an error occurs, the LEDs on the front of the CPU module turns on/flashes. (

Section 6.21)

6.17.2 Error clear
The CPU module can clear an error by a program if the error does not stop program operation.

(1) Procedures for error clear
Clear an error by the following procedures.
• Resolve the error cause.
• Store the code of the error to be cleared in the special register SD50.
• Turn off and then on the special relay SM50.
• The error is cleared.

(a) Procedures for error clear in case of multiple errors
When the latest error (error stored in the special register SD0) is cleared, error information stored in special
relays and special registers (SM0, SM1, SM5, SM16, SD0 to SD26) are cleared and therefore information on
errors that have not been cleared cannot be obtained from the special relays and spcial registers.
For errors that have not been cleared, obtain the past errors from the error history (

Section 6.18) and

clear the errors.

(2) Status after error clear
When the CPU module is recovered by clearing an error, the special relay, special register, and LEDs affected by
the error return to the status before the error.
If the same error occurs after clearing the error, it is logged in the error history again.

(3) Clear of annunciator
When multiple annunciators are detected, only the first detected "F"is cleared. (

●

Section 9.2.5)

When an error is cleared by storing the code of the error to be cleared in SD50, the last digit of the code number is
ignored.
When the error code 2410, 2411, or 2412 occurs, clearing the error by storing 2412 in SD50 also clears
the error codes 2410 and 2411.

Example

●

If the CPU module is not an error cause, the error cannot be resolved by using the special relay (SM50) and special
register (SD50).

Example Since "SP. UNIT DOWN" indicates an error occurred to the Q bus, the error cannot be resolved by using
the special relay (SM50) and special register (SD50).
To resolve the error cause, refer to the following.
QCPU User's Manual (Hardware Design, Maintenance and Inspecting)

6 - 104

CHAPTER6 FUNCTIONS

6.18 Error History

This function stores an error detected by the self-diagnostic function and the detection time as an error history in a

memory.
Select [Diagnostics]

[PLC diagnostics] of GX Developer to check the history.

3
The detection time is based on the clock in the CPU module. Make sure to set the correct time before the first use of the
CPU module. (

Section 6.5)

4
5

(1) Storage area
All stored logs are saved to the storage memory for error history of the CPU module.

Table6.30 Storage area for error history file
Storage area

Number of storable logs

System memory in CPU module*1

Up to 100*2

*1: The memory is managed inside the system.
*2: When the number of storable logs are exceeded, the latest error log is stored by deletion of the oldest error log.

(2) How to clear error history
To clear the storage memory for error history and error history file, select [Diagnostics]

button.

This method clears all data stored in the storage memory for error history of the CPU module and error history file
in a memory card.

6 - 105

6.18 Error History

GX Developer and click the Clear log

[PLC diagnostics] in

6.19 System Protection
The CPU module has protection functions (system protection) to prevent programs being modified by a third party
other than the designer with GX Developer or serial communication module.
Table6.31 System protection types
Protection target

In units of memory
cards*1

File that can be
protected
All files

Description

Method

Prohibits writing to a

Turn on the write protect

memory card.

switch of a memory card.

Valid
timing
Always

Reference

• Changes the attribute
for each file to either of
the following.
• Program
In units of files

• Device comment
• Initial device value

• Read/write (reading/
writing to programs)
prohibitation
• Write prohibitation

Make setting in the
Password registration
screen.

Always

Section
6.19.1

(operations regarding
writing such as writing
to programs and tests)
*1: The Q00UJCPU, Q00UCPU, and Q01UCPU do not support the system protection in units of memory cards since they
cannot use the memory card.

6.19.1 Password registration
This function prohibits reading and writing data such as a programs and device comments in the CPU module with
GX Developer.

(1) Valid password range
The password can be registered with program, device comment, and initial device values files in the specified
memory (program memory, standard ROM, and memory card).

(2) Operations that can be prohibited
The following two operations can be prohibited.
• Reading and writing a file
• Writing a file
When a password has been registered with a file, GX Developer cannot operate the file unless entered password
does not match with the registered password.

6 - 106

CHAPTER6 FUNCTIONS

(3) Setting method
Select [Online]

[Password setup] or click the Password setup button on the Write to PLC screen in

GX Developer.

3
(e)
(f)

(a)

4
5
6

(d)
(c)

(b)

7
Figure 6.80 Password registration/change screen

(a) Target memory
Select a memory storing a file where a password is to be registered.
6.19 System Protection
6.19.1 Password registration

(b) Data type
Displays the type of a file stored in the target memory.

(d) Registration
Displays "*" when a password has been set to the target file.

(e) Password
Enter current password or a password to be registered.
The Registration Condition column can be set after setting a password.

(f) Registration Condition
1) Write protect
Writing to a password-protected file is prohibited (reading is allowed).

2) Read/Write protect
Reading and writing to a password-protected file is prohibited.

3) Clear
The set password is cleared (entering the current password is necessary).

6 - 107

(4) Precautions
(a) Password management
A password registered with a file cannot be read from the file.
Forgetting the registered password disables the following operations.
• Program memory or memory card: Format PLC memory
• Standard ROM: Batch-writing
Make sure to record the registered password and store the recording paper.

(b) Operations that overwrite a file independent of the password registration setting
The following operations overwrite a file in the target drive (program memory, standard ROM) independent of
the password registration setting.
• Boot from a memory card
• Replacement of the CPU modules with a memory card (backup data restoration function)

6.19.2 Remote password
(1) Definition
This function prevents unauthorized remote access to the CPU module.
If a remote password has been set and the CPU module is remotely accessed, entering a remote password is
required.

(2) Settable modules and the number of settable modules
Table6.32 shows the modules for which the remote password can be set and the number of settable modules.
Table6.32 Settable modules and the number of settable modules
Settable module

Number of settable modules

Ethernet module
Serial communication module
Modem interface module
Built-in Ethernet port QCPU

8
1

●

The number of settable modules in the above table indicates the number of modules for which the remote password
can be set, not the number of mountable modules in the system using the CPU module.

●

For the number of mountable modules in the system, refer to the following.
QCPU Userís Manual (Hardware Design, Maintenance and Inspection)

●

For details of the remote password of each module, refer to the following.
Manual for each module

6 - 108

CHAPTER6 FUNCTIONS

(3) Flow from remote password setting to reflection of the password
Set a remote password (

(5) in this section) and then write it to the CPU module.

The remote password is transferred to the target module when the CPU module is powered off and then on or is
reset. (

(2) in this section)

2
3

GX Developer

4
Ethernet

5
Ethernet module

6
7

GX Developer

Checks the remote
password.

6.19 System Protection
6.19.2 Remote password

Transfers a remote
password to the
Ethernet module when
the CPU module is
powered off and then
on or is reset.

Sets,
changes, or
clears
the remote password and writes
the result to the CPU module.

Figure 6.81 Outline of a remote password

6 - 109

(4) Remote password lock/unlock
Unlock the remote password of a serial communication module via a modem or the Ethernet module via Ethernet.
When entered remote password matches with the registered password, the module can access the CPU module.

GX Developer

Unlocks (releases) the remote password
and accesses the CPU module.
When a line is closed, the remote password is
locked.

Ethernet

Ethernet module

Transfers a remote
password to the
Ethernet module when
the CPU module is
powered off and then
on or is reset.

Checks the remote
password.

GX Developer
Figure 6.82 Outline of locking/unlocking a remote password with an Ethernet module

6 - 110

CHAPTER6 FUNCTIONS

(5) Procedures for setting/changing/clearing a remote password
(a) Setting a remote password
• In the project data list of GX Developer, select [Parameter]

[Remote pass].

Remote password setting

For the
QnUDE(H)CPU
or QJ71E71,
configure setting
in "Detail".

4
5
6
7

Figure 6.83 Remote password settings screen

8
Table6.33 Setting items on the Remote password settings screen
Item

Enter a remote password.

Setting range/option
Four characters or less (alphanumeric
characters, special symbols)
• QnUDE(H)CPU

Password active

Model name

Select a model name.

Start X/Y

Set the start address of the module.

• QJ71E71
• QJ71C24/CMO

module settings
Detail

User connection No.

Select user connection No.

0000H to 0FE0H
Connection 1 to Connection 16

Auto open UDP port
FTP transmission port
(TCP/IP)
System

GX Developer transmission

Select a valid port of the remote

connection

port (TCP/IP)

password.

GX Developer transmission
port (UDP/IP)
HTTP port

• Connect GX Developer to the CPU module.
• Write a set remote password to the CPU module.
• In multiple CPU systems, write a remote password to the control CPU of the module to which the remote
password is to be set.

6 - 111

6.19 System Protection
6.19.2 Remote password

Password settings

Description

After setting a remote password, store the parameters to the valid drive (

Section 5.1.10).

(b) Changing a remote password
Change set password in the Remote password settings screen and write a new password to the CPU module.

(c) Clearing a remote password
• To delete set remote password, click the Clear button in the Remote password settings screen.
• Write a remote password with GX Developer.

6 - 112

CHAPTER6 FUNCTIONS

6.20 System Display of CPU Module with GX Developer

When the CPU module is connected to GX Developer, this function can check the following items of the modules on

the base unit in the System Monitor screen.
• Installed status
• Parameter status

• Module’s Detailed Information
• Product information

(1)

(3)

5
6
(4)

(2)

(5)
(6)
(7)
(8)
(9)

Figure 6.84 System Monitor screen

The control CPU, model name, and the number of points of the modules on the selected base unit can be
checked.
"Unmounting" is displayed in the field of a number of slot where a module is not mounted.
The model name of a module on a slot to which "Empty" is set in the I/O assignment tab of the PLC parameter
dialog box is not displayed.
When using a redundant base unit, mounted status of the power supply module is also displayed.
Note6.10Note1

(2) Parameter status
The I/O number, type, and the number of points of the module on each slot of the selected base unit can be
displayed.
If the Parameter status displays "0" for an empty slot or assignment error, it indicates that the I/O assignment
setting of the PLC parameter dialog box and the mounted status differs. Therefore, change the I/O assignment
setting so that it may match with the mounted status.
When using a redundant base unit, mounted status of the power supply module is also displayed.

Note6.10

Note1

Note6.10

Universal

Before monitoring the Q02UCPU, Q03UDCPU, Q04UDHCPU, Q06UDHCPU, Q13UDHCPU, or Q26UDHCPU, check
the versions of the CPU module and GX Developer.(

Appendix 2)

6 - 113

6.20 System Display of CPU Module with GX Developer

(1) Installed status

(3) Base
The status of the base unit and modules on the base unit can be checked.
When there is even one faulty module, the "Module" field color changes according to the status described at the
bottom of the screen.

(4) Mode
The mode cannot be selected since modules cannot be replaced online.

(5) Diagnostics
Click this button to check an error and status of the selected module.

(6) Module’s Detailed Information
Click this button to check the details of the selected module.
For details of the intelligent function module, refer to the manual for the intelligent function module used.

(7) Base Information
The "Overall Information" and "Base Information" can be checked.

(a) Overall Information
The number of base units and the number of modules on the base units can be checked.

(b) Base Information
The name, the number of slots, type, and the number of modules of the selected base unit can be checked.

(8) Product Inf. List
Individual information (Type, Series, Model name, Points, I/O No., Master PLC, Serial No., Ver., and Product No.)
of the mounted CPU module, I/O modules, and intelligent function module can be checked.
Serial
number

Function
version

Figure 6.85 Product Information List screen

6 - 114

Product
number

CHAPTER6 FUNCTIONS

(9) Detailed information of power supply module
This screen displays "ON/OFF status", "Error existence", and "Number of momentary power failures" of the power
supply module.
This screen can be displayed when using the power supply module supporting a redundant base unit and this
screen.

1
2
3
4

Figure 6.86 Detailed information of power supply module screen

5
Table6.34 Description of the Detailed information of power supply module screen
Item

Description

ON/OFF status

Displays the status of an input power supply to the redundant power supply module.

Error existence

Displays whether a failure (error) occurs in the redundant power supply module.
• When the redundant power supply module of redundant main base unit is selected

Number of momentary power
failures

Displays the number of momentary power failures of the redundant power supply

module on the redundant main base unit (display range: 0 to 65535).
• When the redundant power supply module of redundant extension base unit is selected
Displays "-" and the number of momentary power failures is not counted.

In multiple CPU systems, the Detailed information of power supply module screen can be displayed:
• when GX Developer is connected to CPU No. 1, or
• when serial numbers (first five digits) of all CPU modules are "07032" or later.

●

Double-clicking the area of power supply module in "Installed status" can also display the screen.

6.20 System Display of CPU Module with GX Developer

●

MasterPLC ->
Powe Powe
r su r su
pply pply

Q03UDCPU

Double-clicking this area displays the Detailed information
of power supply module screen.

Remark
For details of the System Monitor screen of GX Developer, refer to the following.
GX Developer Version 8 Operating Manual

6 - 115

6.21 LED Indication
Operating status of the CPU module can be checked by the LEDs on the front of the CPU module.
For details of LED indications, refer to the following.
QCPU Userís Manual (Hardware Design, Maintenance and Inspection)

Figure 6.87 LEDs on the front of the CPU module

6.21.1 Methods for turning off the LEDs
(1) Methods
The LEDs can be turned off by the following operations (except for reset operation).
Table6.35 Methods for turing off the LEDs
Relevant LED

Method for turning off the LED

ERR.

USER

BAT.

BOOT

Execute the LEDR instruction after resolving the error.
After resolving the error, clear the error by the special relay SM50 and special
register SD50*1 (operation continuation error only).
Turn off the LED by the special relay SM202 and special register SD202.*1
: Valid,

: Invalid

*1: Description of special relays and special registers
• SM50
• SD50

: Clears an error of the error code stored in SD50 when the CPU module is powered off and then on.
Stores an code of an error to be ccleared.
: For details of error codes, refer to the following.
QCPU Userís Manual (Hardware Design, Maintenance and Inspection)

• SM202

: Turns off the LED corresponding to each bit of SD202 when the CPU module is powered off and then on.

• SD202

: Set an LED to be turned off.
b15
SD20

1/0

BOOT LED

USER

LED
0: Not turn on.
1: Turns on.

Figure 6.88 Bit structure of the special register SD202

Configure setting to turn off each LED as follows:
• Turning off both the Boot LED and USER LED: SD202 = 110H
• Turning off only the BOOT LED: SD202 = 100H
• Turning off only the USER LED: SD202 = 10H

6 - 116

CHAPTER6 FUNCTIONS

(2) Methods for not turning on the ERR. LED, USER LED, and BAT. LED
There is a priority in indications of the ERR.LED, USER LED, and BAT.LED. (

Section 6.21.2)

When an cause number of an LED is deleted in the priority, the LED will not turn on even if an error with the cause
number occurs.

2
3

6.21.2 LED indication priority
This section describes a priority for error messages stored in the LED display data (SD220 to SD227) in case of an

error.

(1) Displayed error messages and their priorities
In case of multiple errors, the error messages are displayed with the following conditions.

• A stop error is always set to the LED display data (SD220 to SD227).
• An operation continuation error is displayed according to the priority cause number described in this section.
Whether to indicate an error according to its priority using LED can be selected. (Set the priority using
special registers, SD207 to SD209.)

• When errors having the same priority occur simultaneously, the error detected first is displayed.

The priority is determined with the special registers SD207 to SD209 as follows.
4 3
0bits
to
to
8 7
15 to 12 11 to
Priority 2
Priority 1
Priority 3
SD207 Priority 4

Default value of factor number
to
0bits
15
SD207
2
1
4
3
6.21 LED Indication
6.21.2 LED indication priority

Factor number setting area
SD208

Priority 8

Priority 7

Priority 6

Priority 5

SD208

Priority 9

SD209

Factor number setting area
Priority 10

SD209
Ignored

Factor number setting area
Figure 6.89 Special registers and bit structure ragarding a priority

6 - 117

(2) Priorities and cause numbers
The following table shows the description and priority of the cause numbers set to the special registers SD207 to
SD209.
Table6.36 List of cause numbers and priorities
Priority

Cause number

Displayed error message

(hexadecimal)

Remarks

• AC/DC DOWN

• Power-off

• UNIT VERIFY ERR.
2

• I/O module verification error

• FUSE BREAK OFF

• Fuse blown

• SP.UNIT ERROR

• Intelligent function module verification error

• SP.UNIT DOWN
3

• OPERATION ERROR

• Operation error

• SFCP OPE.ERROR

• SFC instruction operation error

• SFCP EXE.ERROR

• SFC program execution error

• ICM.OPE.ERROR*1

• Memory card operation error

• FILE OPE.ERROR

• File access error

• FLASH ROM ERROR

• Flash ROM access count over error

• PRG.TIME OVER

• Constant scan setting time-out error

• MULTI CPU

ERROR*2

• Another CPU error in multiple CPU systems

• Annunciator
• BATTERY ERROR
-

*1: The Q00UJCPU, Q00UCPU, and Q01UCPU cannot display the error message.
*2: The Q00UJCPU cannot display the error message.

●

To remain the LED off even in case of an error, set the cause number setting area (each 4 bits) of SD207 to SD209 that
stores the corresponding cause number to “0”.
To remain the ERR. LED off even when a fuse blown error is detected, set the cause number setting area
where the cause number “2" is stored to “0”.

Example

SD20
0

SD20
9

SD20
5

Figure 6.90 Cause numbers stored in SD207 to SD209
Because the cause number "2" is not set, the ERR.LED remains off even if a fuse blown is detected.
In this case, even if another error with the cause number "2" (I/O module verification error or intelligent function module
verification error) is detected, the ERR.LED remains off.

●

6 - 118

If “0” is set to the cause number setting area (setting that does not turn on the LED), SM0 (Diagnostic errors) and SM1
(Self-diagnostic error) turn on, and the error code is stored to SD0 (Diagnostic errors).

CHAPTER6 FUNCTIONS

6.22 Interrupt from Intelligent Function Module
The CPU module can execute an interrupt program (I

) by the interrupt request from the intelligent function module.

For example, the serial communication module can receive data by an interrupt program when the following data
communication functions are executed.

• Data reception during communication by nonprocedural protocol

• Data reception during communication by bidirectional protocol
Using an interrupt program enables a CPU module to receive data quickly.

External device to be communicated

5
Sends data.
Serial communication
module

Reception

Issues an
interrupt.

Main program

CPU module

Main program

Interrupt program
execution

FEND

SM400
I

BUFRCVS

(1) Setting an interrupt from the intelligent function module
To execute an interrupt program by an interrupt from the intelligent function module, select "Interrupt pointer
setting" in "Intelligent function module setting" of the PLC system tab in the PLC parameter dialog box.
Configure system setting at the intelligent function module is also required.
For execution of an interrupt program by an interrupt from the intelligent function module, refer to the following.
Manual for the intelligent function module used

Remark
For the numbers of interrupt pointers available for an interrupt from the intelligent function module, refer to Section 9.11.

6 - 119

6.22 Interrupt from Intelligent Function Module

Figure 6.91 Interrupt from a serial communication module

6.23 Serial Communication Function

Note6.11

Note1

(1) Definition
This function communicates in the MC protocol*1 by connecting the RS-232 interface of the CPU module,
personal computer, and HMI by RS-232 cable.
This section describes the specifications, functions, and various settings of the function.
*1: The MC protocol is an abbreviation for the MELSEC communication protocol.
The MELSEC communication protocol is a communication method to access from an external device to the CPU
module according to the communication procedure for the Q series programmable controller (such as a serial
communication module, Ethernet module).
For the MC protocol, refer to the following.
Q Corresponding MELSEC Communication Protocol Reference Manual

RS-232 cable
Personal computer or HMI

Communication in the MC protocol
Figure 6.92 Communication with personal computer or HMI

●

A personal computer or HMI can communicate with a CPU module by the serial communication function only when the
CPU module is connected to it.
The CC-Link IE controller network, MELSECNET/H, Ethernet, or CC-Link cannot be communicated with another
station.

●

The serial communication function is not used for connection of GX Developer or GX Configurator with the CPU
module.

Note1

Note6.11

Universal

When using the serial communication function for the Q02UCPU, check the versions of the CPU module and GX
Developer. (

Appendix 2)

When using the Q03UDCPU, Q04UDHCPU, Q06UDHCPU, Q10UDHCPU, Q13UDHCPU, Q20UDHCPU,
Q26UDHCPU, or Built-in Ethernet port QCPU, the serial communication function cannot be used.

6 - 120

CHAPTER6 FUNCTIONS

(2) Specifications
(a) Transmission specifications
Table6.37 shows the transmission specifications of RS-232 for the serial communication function of the CPU

module.
Check that the specifications of the personal computer and HMI match those of Table6.37 before using the
function.

Table6.37 Transmission specifications of the serial communication function
Item

Default

Communication method

Full-duplex communication

Synchronization method

Asynchronous method

Transmission speed

19.2kbps

Setting range

9.6kbps, 19.2kbps, 38.4kbps, 57.6kbps, 115.2kbps

• Start bit: 1
• Data bit: 8

Data format

• Parity bit: Odd

• Stop bit: 1
MC protocol format*2

• Format 4 (ASCII)

(automatic detection)

• Format 5 (binary)
• QnA-compatible 3C frame

Frame*2

Sum check

DTR/DSR control

Checked

Transmission wait time*1

Prohibited (deselected)

Overall cable distance

Checked/not checked
No waiting time, 10ms to 150ms (in increments of
10ms)
Permit (checked), prohibited (deselected)

15m

*1: Can be set in the PLC parameter dialog box.
*2: Table6.38 shows the relationship between the MC protocol formats and frames.

Table6.38 Relationship between the MC protocol formats and frames
Function
Communication in ASCII code
Communication in binary code

Format 4

Format 5

QnA-compatible 3C frame
QnA-compatible 4C frame
QnA-compatible 4C frame
: Available,

: Unavailable

6 - 121

6.23 Serial Communication Function

setting*1

No waiting time

• QnA-compatible 4C frame

Transmission control

RUN write

(b) RS-232 connector specifications
Table6.39 shows the specifications of the RS-232 connector for the CPU module.
Table6.39 RS-232 connector specifications
Appearance

5
6

Pin number

Signal

RD(RXD)

SD(TXD)

DSR(DR)

Data setting ready

DTR(ER)

Data terminal ready

1
2

Mini-DIN 6 pins
(female)

Signal name
Receive data
Send data
Signal ground
-

(c) RS-232 cable
• The following RS-232 cable can be used for connecting the CPU module to the personal computer or HMI.
• QC30R2 (cable length: 3m)
• FMBKAZ1-*** (manufactured by Kuremo Electric Co., Ltd.)
• Cable with a Mini-DIN connector on one side and without connector on the other side
• *** indicates a cable length, which can be lengthened up to 15m in units of 0.1m.
(CPU module side)

FMBKAZ1-***
21
4
6

Signal layout of the
3 FMBKAZ1-*** connector
5 on CPU module side

Effective length

Pin number

Signal

Wire core

Red

Black

Yellow

Brown

Green/
white

Figure 6.93 Effective length and signal layout of RS-232 cable

6 - 122

Metal shell
Shield

CHAPTER6 FUNCTIONS

(3) Functions
Table6.40 shows the MC protocol commands that can be executed by the serial communication function.

Table6.40 MC protocol commands supported by the serial communication function
Function

Command
In units of
bits

Batch read

In units of
words
In units of
*1

Batch write

bits
In units of
words

0401(00

1401(00

Processing
Reads bit devices in units of 1 point.
Reads bit devices in units of 16 points.
Reads word devices in units of 1 point.
Writes bit devices in units of 1 point.

Number of processing
points
ASCII: 3584 points

BIN: 7168 points
480 words (7680 points)

480 points
ASCII: 3584 points
BIN: 7168 points

Writes bit devices in units of 16 points.

480 words (7680 points)

Writes word devices in units of 1 point.

480 points

Reads bit devices in units of 16 points or 32 points
Random read

In units of
words

by specifying the device or device number at
0403(00

random.

96 points

Reads word devices in units of 1 point or 2 points by

Device

specifying the device or device number at random.

memory

In units of
bits

1402(00

Sets/resets bit devices in units of 1 point by
specifying the device or device number at random.

7
94 points

Sets/resets bit devices in units of 16 points or 32

Test*1
(random write)

In units of
words

points by specifying the device or device number at
1402(00

random.

Writes word devices in units of 1 point or 2 points by
specifying the device or device number at random.

Monitor

In units of

registration

words

0801(00

points or 32 points.
Registers word devices to be monitored in units of 1
point or 2 points.

Monitor

In units of
words

0802(00

Monitors devices registered for monitoring.

96 points
96 points
Number of monitor
registration points

*1: When writing data while the CPU module is in the RUN status, set "RUN write setting" to "Permit".
*2: Set the number of processing points within the range of the following calculation formula.
(number of word access points)
12 + (number of double word access points)
14
960
• One point of a bit device corresponds to 16 bits for word access or to 32 bits for double word access.
• One point of a word device corresponds to one word for word access or to two words for double word access.

6 - 123

6.23 Serial Communication Function

Registers bit devices to be monitored in units of 16

(4) Accessible devices
Table6.41 shows accessible devices by the serial communication function.

Table6.41 Accessible devices by the serial communication function
Category

Device
Function input

Internal
system device

Internal user

Function output

Hexadecimal

000000 to 00000F

Hexadecimal

000000 to 000004

Decimal

000000 to 002047

Decimal

Special register

000000 to 002047

Decimal

Input

000000 to 001FFF

Hexadecimal

Output

000000 to 001FFF

Hexadecimal

Internal relay

000000 to 008191

Decimal

Latch relay

000000 to 008191

Decimal

Annunciator

000000 to 002047

Decimal

Edge relay

000000 to 002047

Decimal

Link relay

000000 to 001FFF

Hexadecimal

Data register

000000 to 012287

Decimal

Link register

000000 to 001FFF

Hexadecimal

000000 to 002047

Decimal

000000 to 002047

Decimal

000000 to 001023

Decimal

000000 to 0007FF

Hexadecimal

Link special register

000000 to 0007FF

Hexadecimal

Step relay

000000 to 008191

Decimal

Direct input

000000 to 000FFF

Hexadecimal

Direct output

000000 to 000FFF

Hexadecimal

Timer

Contact

Coil

Current value

Contact

Coil

Current value

Contact

Coil

Current value

Link special relay

Extended link

000000 to 00000F

Counter

FX*2

timer

Extended data

(default value

Special relay

Retentive

File register*3

Device number range*1

Function register

device

Index register

Device code

Index register

000000 to 000019

Decimal

000000 to 032767

Decimal

000000 to 3FD7FF

Hexadecimal

Extended data register

000000 to 093183

Decimal

Extended link register

000000 to 016BFF

Hexadecimal

File register

: Reading/writing are enabled.

Write

Read

: Writing is prohibited.

*1: After changing the number of device points of the CPU module with GX Developer, use the devices within the new device number range.
Decimal and hexadecimal indicate whether a command specified for the MC protocol is decimal or hexadecimal.
*2: From 000005 to 00000F of FX and FY will be indefinite value.
*3: These registers are not supported by the Q00UJCPU.

6 - 124

CHAPTER6 FUNCTIONS

(5) Setting of transmission specifications
Set Transmission speed, Sum check, Transmission wait time, and Run write setting of the serial communication
function in the Serial tab of the PLC parameter dialog box.

• Select "Use serial communication" in communication with the personal computer or HMI.
• Set Transmission speed, Sum check, Transmission wait time, and Run write setting in the tab.

3
Click here to use the serial
communication function.

4
Set Transmission speed, Sum
check, Transmission wait time,
and Run write setting.

5
6
7
Figure 6.94 Serial tab

(6) Precautions
(a) Switching connection to GX Developer during communication with such as HMI
The CPU module can switch connection to GX Developer during communication with the personal computer or
However, the personal computer or HMI in communication by the serial communication function results in a
communication error.
For startup methods of the personal computer and HMI when they are reconnected to the CPU module, refer to
the manual for used device.

(b) Transmission speed set in the Transfer Setup screen
When "Use serial communication" is selected, the transmission speed set in the Transfer setup screen of GX
Developer is ignored.

The data set in the "Serial" tab is valid when:
• the CPU module is powered on, or
• the CPU module is reset.

6 - 125

6.23 Serial Communication Function

HMI with the serial communication function.

(c) Communication error
If any of the following status is met, responses are not returned and therefore communication cannot be made.
Review the transmission frame.
1) The serial communication function is set not to be used.
2) Communication is made at different transmission speed and data format.
3) A frame to be sent has no correct starting end or terminal.
• 3C frame format 4: ENQ/CR + LF
• 4C frame format 4: ENQ/CR + LF
• 4C frame format 5*1: DLE+STX/DLE + ETX
*1: When "Sumcheck enable" is set, the sumcheck code is included.

4) The frame identification number of a frame to be sent is incorrect.
5) The number of transmission bytes is under the header part size.

6 - 126

CHAPTER6 FUNCTIONS

(7) Error codes during communication with the serial communication function

Table6.42 shows the error codes, error description, and corrective actions sent from the CPU module to the
external device when an error occurs during communication with the serial communication function.

Table6.42 Error codes sent from the CPU module to external device
Error code
(hexadecimal)

Error item

4000H

Description

Corrective action

Refer to the QCPU Userís Manual (Hardware Design,
Maintenance and Inspection), and take corrective action.

7155H

Unregistered
monitor error

A monitor request was given before monitor
registration.

Give a monitor request after registering a device to be
monitored.

7157H

Request target
specification error

Other than the Q00UJCPU, Q00UCPU,
Q01UCPU, and Q02UCPU was selected as a
request module and route.

Check that the transmission message address is Q00UJCPU,
Q00UCPU, Q01UCPU, Q02UCPU, modify the setting and
communicate again.

7164H

Request data error

The requested data or device specification
method is wrong.

Check the sent message/requested data of the external
device, correct it, and restart communication.

7167H

Disabled during
RUN

A write command was specified while online
change is disabled.

Enable the online change and restart communication.

7E40H

Command error

A subcommand or a command that does not exist
is specified.

Check and correct the sent message of the external device
and restart communication.

7E41H

Data length error

The number of points specified for random write/
read exceeds the number of points enabled for
communication.

Check and correct the sent message of the external device
and restart communication.

7E42H

Data count error

The requested number of points exceeds the
range of the command.

Check and correct the sent message of the external device
and restart communication.

7E43H

Device error

The device specified does not exist.
The device specified cannot be specified by the
corresponding command.

Check and correct the sent message of the external device
and restart communication.

7E47H

Continuous
request error

The next request was received before the
response message was returned.

Do not give continuous requests from the external device.
Match the monitoring time of timer 1 with the time-out time of
the external device.

7F21H

Receive header
section error

7F22H

Command error

The command or device specified does not exist.

Check and correct the sent message of the external device
and restart communication.

7F23H

MC protocol
message error

The data (such as ETX, CR+LF) specified after
the character part does not exist or in error.

Check and correct the sent message of the external device
and restart communication.

7F24H

Sumcheck error

The calculated sumcheck does not match the
received sumcheck.

Review the sumcheck of external device.

7F67H

Overrun error

The next data was received before the CPU
module completed receive processing.

Reduce the communication speed and restart communication.
Check the CPU module for momentary power failure.
(For the CPU module, use the special register SD53 to check.)
When an momentary power failure occurs, remove its cause.

7F68H

Framing error

The stop bit setting does not match.

Match the setting of the CPU module with that of the external
device.

7F69H

Parity error

The parity bit setting does not match.

Match the setting of the CPU module with that of the external
device.

4FFFH

The command (frame) section specified is in error.
The ASCII code received cannot be converted
into binary.

Check and correct the sent message of the external device
and restart communication.

6 - 127

4
5
6
7
8

6.23 Serial Communication Function

Error detected by the CPU module
(error occurred by other than the serial
communication function)

6.24 Service Processing
6.24.1 Service processing setting
(1) Definition
This function allows to set the time and the number of times of service processing performed at END processing
by parameters.
This function also improves the response of communication with a peripheral and restrains the increase of scan
time due to service processing.
This achieves the configuration of service processing environment optimum for the system.

The service processing refers to communication service processing with a peripheral (such as GX Developer) and intelligent
function modules. Link refresh processing such as CC-Link IE controller network module, MELSECNET/H module, and CCLink Safety system master/local module are not included.

Using the COM instruction enables service processing during program execution of same performance with
service processing at END processing. Therefore, the high-speed service processing response can be performed
even if the scan time is long.

6 - 128

CHAPTER6 FUNCTIONS

(2) Parameter setting
Set the parameters in the PLC system tab of the PLC parameter dialog box.

2
3
4
5
6
7

Figure 6.95 Parameter setting screen

To perform the service processing, select any of the parameter items in Table6.43.
The setting value of deselected parameter cannot be entered (default: Execute the process as the scan time
proceeds. = 10%).

Table6.43 Parameter items
Description

Setting range

Remarks

Set the percentage of service processing

• Range: 1 to 99%

the scan time proceeds.

for one scan.

• Unit: 1%

Specify service process

Set the time of service processing for one

• Range: 0.2ms to 1000ms

time.

scan.

• Unit: 0.1ms

Specify service process

Set the number of service processing for

• Range: 1 to 10 times

Default when selected

execution counts.

one scan.

• Unit: 1 time

=1 time

Default when selected =10%
Default when selected =0.2ms

Even when the waiting time is
Execute it while waiting
for constant scan setting.

0.2ms or less, the service

Set whether to perform service
processing during waiting time for
constant scan setting.

processing time (0.2ms) will be
added to the scan time at service
processing execution.

6 - 129

6.24 Service Processing
6.24.1 Service processing setting

Item
Execute the process as

(3) Operations for service processing setting
Operations for each service processing setting is described below.

(a) Operation when "Execute the process as the scan time proceeds." is selected

2nd scan
(10ms)

END processing

Request 5

When the time required for processing
one request exceeds 10% of one scan
time, the service processing is suspended
and the request is processed at END
processing in the next scan.

1ms

Request 2-1

The service processing time depends on the
scan time (program execution time).

Program execution
3rd scan
(12ms)

GX Developer

Request 1

Program execution

END processing

Request 4

1ms

Request 3

Program execution

Request 2

Request 1

1st scan
(10ms)

1) Operation when 10% is set

1.2ms

END processing

Request 2-2

Request 3

Figure 6.96 Operation when 10% is set

If no request data for service processing exists, END processing speeds up by the request processing time. (The CPU
module does not wait for requests.)

2) Operation for constant scan setting
The calculation of the service processing time is a calculation of the percentage of the time excluding the
waiting time of the constant scan from the scan time, not a calculation of the percentage of the scan time.

Example Operation when 50% is set
0%

50%

100%

END processing
Program execution
Service processing

Waiting time

Service processing time
Scan time (constant scan setting)

Figure 6.97 Operation for constant scan setting

When setting the constant scan, selecting "Execute it while waiting for constant scan setting." can perform the service
processing efficiently. (

6 - 130

(3)(d) in this section)

CHAPTER6 FUNCTIONS

(b) Operation when "Specify service process execution counts." is selected

3rd scan

2nd scan

END processing

Request 5

Request 4

GX Developer

3
Regardless of request data size, one request
is processed at one END processing.

Request 2

Even if the program execution time are the same,
the scan time depends on service processing time.

Program execution

END processing

Request 1

Program execution

END processing

Request 3

Program execution

Request 2

Request 1

1st scan

1) Operation when 1 time is set

Request 3

Figure 6.98 Operation when 1 time is set

7
Request 4

Request 5

Request 3

Request 2

1st scan

Program execution

Request 1

2) Operation when 2 times is set

8
GX Developer

Request 1

END processing

Regardless of request data size,
two requests are processed at
one END processing.

6.24 Service Processing
6.24.1 Service processing setting

Request 2

2nd scan

Program execution

Request 3

END processing
Request 4

Figure 6.99 Operation when 2 times is set

●

When several devices are connected to one CPU module, each device requests service processing.
When the CPU module receives requests from several devices simultaneously, a single END processing can accept
several requests simultaneously if the service processing count is set to the number of connected devices. This
improves response performance. (Note that the scan time increases by the service processing time.)

●

If no request data exists when setting the service processing count, END processing speeds up by the request
processing time. (The CPU module does not wait for requests.)

6 - 131

3rd scan

2nd scan

Request 5

Request 4

Request 3

Program execution

Request 2

Request 1

1st scan

0.5ms

GX Developer

END processing Request 1
When the time required for processing one request
exceeds the service processing time (0.5ms) , the
service processing is suspended and the processing
is performed at END processing in the next scan.

Program execution

END processing

Request 1
Request 2

Program execution

The scan time increases equally.
END processing Request 2
Figure 6.100 Operation when 0.5ms is set

2) Operation when 1ms is set

Request 5

Request 4

Request 3

Request 2

1st scan

Program execution

Request 1

1ms

GX Developer

END processing Request 1

2nd scan

Request 2

Program execution

END processing Request 2

Several requests are processed until the time exceeds
the specified service processing time (1ms).
When the time exceeds the specified service
processing time, the service processing is suspended
and the request is processed continuously at END
processing of next scan.

Request 3

3rd scan

Program execution

Although multiple processing is performed at
one END processing, the scan time increases equally.

Request 3

END processing Request 4

Figure 6.101 Operation when 1ms is set

If no request data exists when setting the service processing time, END processing speeds up by the request processing
time. (The CPU module does not wait for requests.)

6 - 132

CHAPTER6 FUNCTIONS

(d) Operation when "Execute it while waiting for constant scan setting." is selected

Constant scan

Request 5

GX Developer

Request 1

Waiting time

Request 2

The service processing is performed
during waiting time.

Program execution
Constant scan

Request 3

END processing

Request 2

Request 1

Constant scan

Program execution

Request 4

5
END processing
Request 3

Waiting time

Request 4

Figure 6.102 Operation when "Execute it while waiting for constant scan setting." is selected

●

When setting the constant scan, selecting "Execute it while waiting for constant scan setting." can perform the service
processing efficiently.

• When "Execute it while waiting for constant scan setting." is selected
END processing

6.24 Service Processing
6.24.1 Service processing setting

Wait time
Program execution
Service processing
Service processing time
Scan time (constant scan setting)

• When "Execute the process as the scan time proceeds." is selected (50% is set.)
0%

50%

100%

END processing
Program execution
Service processing

Wait time

Service processing time
Scan time (constant scan setting)

●

Even when there is no waiting time, the service processing (0.2ms) is performed. Therefore, when the waiting time is
less than 0.2ms, the constant scan time may be exceeded.

6 - 133

(4) Precautions
The following describes precautions when the service processing setting is configured.
1) For the following functions, scan time will be increased longer than the specified time during service
processing even if the service processing time specification is set.
• Online change
• Change T/C setting
• Local device monitor
• Program memory backup
• Writing to/reading from a file register (The scan time will be increased when the write or read size is
large.)
• Writing to/reading from the buffer memory of the intelligent function module (The scan time will be
increased when the write or read size is large.)
• Access to a network module
a) Diagnostic functions (CC IE Control diagnostics, MELSECNET diagnostics, Ethernet diagnostics,
CC-Link/ CC-Link/LT diagnostics)
b) Monitor function (Module access device, Link direct device)
2) Note that the scan time will be increased much longer if the CPU module receives multiple requests
simultaneously while the service processing count specification is set many.
3) When setting the service processing time much shorter than the scan time, the response performance of
service processing is extremely reduced. Set the service processing time with considering the time-out
time of a peripheral.
4) An error of -20
time.

6 - 134

s to +30

s occurs between the actual processing time and the set service processing

CHAPTER6 FUNCTIONS

6.25 Initial Device Value

(1) Definition
This function registers data used in a program to the device or the buffer memory of the intelligent function

module without a program.

(2) Application
Using an initial device value can omit device data setting program by initial processing program.

4
5

Device memory

SM402
MOV

H100

MOV

H2020

Power-on/STOP/RESET
RUN

7
8

At power-off

on, reset, or STOP

RUN

6.25 Initial Device Value

Initial device value

Device memory

Figure 6.103 Data setting by initial program

6 - 135

(3) Timing when initial device values are written to the specified device
The CPU module writes data in the specified initial device value file to the specified device or the buffer memory
of the intelligent function module when the CPU module is powered off and then on, is reset, or is set to the STOP
status and then the RUN status.

Writing of initial
device value

Setting of
initial device
value range

GX Developer

Program memory
Initial
device
value file

(At power-off on, reset,
or STOP RUN)

Specified
device

Setting of
initial device
value range

Writing of initial device value
(at power off on, reset, or
STOP RUN)
Figure 6.104 Flow of writing initial device value

(4) Devices that can be used*1
The following shows devices that can be used for initial device value.
• Current timer value (T)
• Current retentive timer value
(ST)
• Current counter value (C)
• Data register

(D)*2

• Special register (SD)
• Link register

• Link special register (SW)
• File register (R)
• File register (ZR)
• Intelligent function module device (U \G )
• Link direct device (J \W , J \SW )

(W)*3

*1: For available ranges, refer to Section 9.1.
*2: The extended data register (D) is included.
*3: The extended link register (W) is included.

6 - 136

CHAPTER6 FUNCTIONS

(5) Procedures and settings for using initial device values
To use initial device values, create initial device value data with GX Developer beforehand, and store the data as
a initial device value file in the program memory, standard ROM, or memory card of the CPU module.
• Add an initial device value data to the project data list of GX Developer.

The Device initialization range setting screen appears. Set the initial device value range.

The number of settable points is up to 8000 points per range setting.
• Add device memory data in the project data list of GX Developer.
The device memory screen appears. Set the initial device value data within the initial device value range set

above.

5
6
7
8
Figure 6.105 Device initialization range setting screen and device memory screen

GX Developer Version 8 Operating Manual

6 - 137

6.25 Initial Device Value

When changing the setting on the Device initialization range setting screen, always execute "Device memory registration/
diversion".
For details of the "Device memory registration/diversion", refer to the following.

• Select the name of a file where the initial device value data are stored in the PLC file tab of the PLC
parameter dialog box.

Figure 6.106 PLC file tab

• Write the set initial device value and parameters to the CPU module.

(6) Precautions
(a) When initial device value and latch range are overlapped
In that case, initial device value takes priority. Therefore, the latch range data will be overwritten to the initial
device value data after the CPU module is powered off and then on.

(b) Area disabling the initial device value setting when the CPU module is set from
STOP to RUN
The initial device value are also reflected when the CPU module is set from STOP to RUN.
For an area where an initial device value is not to be set when the CPU module is set from STOP to RUN (data
that are set when the CPU module is powered off and then on and changed by a program), the initial device
value cannot be used.
Use an instruction such as the MOV instruction in the main routine program so that the initial device values will
be set to the specified devices.
Use the TO instruction to write data to the buffer memory of the intelligent function module.

(c) Devices that require module synchronization setting
When setting the following devices in the Device initialization range setting screen, set "Module
synchronization" in the PLC system tab of the PLC parameter dialog box.
If the setting is not configured, the initial device values may not be set to the target module properly.
• Intelligent function module device (U \G )
• Link direct device (J \W

, J \SW )

Remark
For details of the initial device value range setting, setting of the initial device value data, and writing of the initial device
values to the CPU module, refer to the following.
GX Developer Version 8 Operating Manual

6 - 138

CHAPTER6 FUNCTIONS

6.26 Battery Life-prolonging Function

(1) Definition
This function extends the life of battery installed in the CPU module by restricting data to be held by the battery to

clock data only.
This function initializes all data other than the clock data when the CPU module is powered off or is reset.

Table6.44 Initialization details
Data held by a battery

Description

Error history

The number of error history data is initialized to zero.

Latch device (L)

Cleared to zero.

Device in the latch range

Cleared to zero.

Standard RAM

Formatted (cleared to zero).

File register assigned to
the standard RAM

Set "Use the same file name as the program."
Set "Use the following file".

A file is deleted.
A file is deleted (A file is recreated at power-on or reset

(Data is cleared to zero.).)

(2) Setting

Set the function in the I/O assignment tab of the PLC parameter dialog box.
1) Configure the I/O assignment setting.

2) Click the Switch setting button.
3) Enter 0001H to the switch 3 of the slot where the CPU module is mounted (When entering the value to a slot
in another station, the value is ignored).
Enter 0000H.

6.26 Battery Life-prolonging Function

Figure 6.107 Switch setting screen

(3) Battery life
For the life of battery installed in the CPU module when the battery life-prolonging function is used, refer to the
following.
QCPU User's Manual (Hardware Design, Maintenance and Inspection)

6 - 139

6.27 Memory Check Function
This function checks whether data in the memories of the CPU module are not changed due to such as excessive
electric noise.
Since the CPU module automatically checks a memory, setting for enabling this function is unnecessary.
This function does not require processing time.

(1) Data to be checked
(a) Program
The program during execution is compared with the user program written to the program memory.
If they do not match, a stop error, “RAM ERROR” (error code: 1160) is detected.

(b) Parameter
The parameters are compared with the ones written to the parameter-valid drive.

(2) Execution timing
1) Program: At program execution
2) Parameter:
• When the CPU module is powered off and then on
• When the CPU module is reset
• When the CPU module is set from STOP to RUN after data are written to it
3) Device memory: When device data are read

6 - 140

CHAPTER6 FUNCTIONS

6.28 Latch Data Backup to Standard ROM Function

(1) Definition
This function holds (backs up) latch data, such as device data and error history, to the standard ROM without

using a battery when the system is stopped for a long period. This function helps to extend battery life.

3
Remark
When this function is performed, the battery life-prolonging function is enabled regardless of the parameter setting for the
battery life-prolonging function.
Also, the battery life-prolonging function is switched to be disabled after backup data are restored.
The setting status of the battery life-prolonging function can be checked by SD119 (battery life-prolonging factor).
For details of the battery life-prolonging function, refer to Section 6.26.

4
5
6

(2) Data to be backed up
Table6.45 shows data to be backed up.

Table6.45 Data to be backed up
Data to be backed up

Description

Remarks

• Internal user device (M, L, B, F, V, T, ST,
C, D, W)
• Index register (Z)/standard device
Device data

The data of the file register, extended data
register (D), and extended link register (W) are
backed up only when the file register in the

• File register (R, ZR)
• Extended data register (D)

standard RAM is used

• Extended link register (W)*1
Error history data immediately before the
latch data backup function to standard

ROM function is performed
Module error collection file

Information on errors occurred in the

The data are backed up independent of the

connected intelligent function modules

setting of the module error collection.

SFC program continuation start

Information to start the SFC program

information

continuously

Trace setting
(Sampling trace file)

Trace condition settings and Trace data
settings created by the sampling trace
function.

Data cannot be backed up in the following cases.
• Trace setting is made in a memory card.
• Trace setting is not registered with the CPU
module.

*1: The data are backed up only when the Universal model QCPU having the serial number (first five digits) is "10042" or later is used.

6 - 141

6.28 Latch Data Backup to Standard ROM Function

Error history

When backing up the data in the file register, extended data register (D), and extended link register (W), pay attention to the
following.
• The data are backed up only when the file register in the standard RAM is set to be used.
• Select "Transfer to Standard ROM at Latch data backup operation." on the PLC file tab of the PLC parameter
dialog box.

Selecting this option
starts backup.

Figure 6.108 PLC file tab

(3) File size for storing backup data
The system automatically creates storage file for backup data when the latch data backup function to standard
ROM is performed.
Table6.46 shows the size of storage file.
Table6.46 Sizes of files to be stored
Data to be backed up
Device data

Internal user device (M, L, B, F, V, T, ST, C, D, W)
Index register (Z)/standard device register (Z)

Error history
SFC program continuation start information

File size
• Serial number (first five digits) is "11042" or
earlier: 110890 bytes*1
(When the default device assignment is set)*2
• Serial number (first five digits) is "11043" or

Module error collection file (stored in system memory.)

later: 117310 bytes*5

Module error collection file (stored in standard RAM.)

(When the default device assignment is set)*2

File register (R, ZR)*3, extended data register (D)*3, extended link register (W)*3

64 + 2

ÉgTrace setting (sampling trace file)*4

16 + Sampling trace file size

Number of file register points

*1: The file size of the Q00UJCPU,Q00UCPU,Q01UCPU,and Q02UCPU is 87210 bytes.
*2: The size depends on the parameter setting.
*3: Storage files are created only when data in the file register, extended data register (D), and extended link register (W) are backed up.
*4: Storage files are created only when the trace registration has been made.
*5: The file size of the Q00UJCPU, Q00UCPU, and Q01UCPU is 89790 bytes and that of the Q02UCPU is 93630 bytes.

6 - 142

CHAPTER6 FUNCTIONS

(4) Execution method
(a) Execution by contacts

1) Setting method
Set "Latch data backup operation valid contact" in the PLC system tab of the PLC parameter dialog box
(Devices X, M, or B can be selected).

Specify a contact

Figure 6.109 Setting screen of latch data backup start contact to standard ROM

2) Execution method
Backup starts at the rise of a contact (off

on).

After backup, the BAT.LED of the CPU module flashes (green), indicating that the CPU module is in the
standby status ready to be powered off.

3) Precautions
a)Since data to be backed up is the data when a contact is on (END processing), the CPU module will not
become the RUN status until the CPU module is powered on again or is reset after this operation.

b) Since the status of latch data backup start contact to the standard ROM is checked at execution of the
END instruction, data are not backed up even if a contact is turned on

off

on, or off

off in

one scan.

c) In the following cases, data are not backed up unless the latch data backup start contact to the standard
ROM is turned off and then on again.

off and then on or is reset after backup by turning off and then on the contact.
• The latch data backup start contact to the standard ROM is set to M or B, and data are backed up by
turning off and then on the contact.

(b) Execution by remote operation
1) Execution method
Select [Online]

[Latch data backup operation] of GX Developer.

After backup, the BAT.LED of the CPU module flashes (green), indicating that the CPU module is in the
standby status ready to be powered off.

Figure 6.110 Remote operation execution screen

Data to be backed up is the data at the execution of remote operation.

6 - 143

6.28 Latch Data Backup to Standard ROM Function

• The latch data backup start contact to the standard ROM is set to X, and the CPU module is powered

(5) Restoring backup data
The backup data is automatically restored by the following operations.
• At power-off

on of the CPU module

• At reset
Whether to restore data once after backup or per above operation is set by SM676 (Specification of restore
repeated execution).
Table6.47 Status of SM676 and restoration operation
Status of SM676 at backup operation

Restoration operation
Data are restored once when the CPU module is powered off

SM676 is off.

and then on or is reset after backup.
Data are restored whenever the CPU module is powered off and
then on or is reset after backup.

SM676 is on.

Data are repeatedly restored until the backup data are deleted or
the latch data are backed up next time.

After backup data are restored, the BAT.LED on the CPU module turns on (green) for five seconds.

If the number of device points configured in the parameter setting and the number of device points at the time of backup are
different, "RESTORE ERROR" (error code: 2220) is detected when the backup data are restored, and data restoration is not
normally completed.
(Data will be restored again when the CPU module is powered off and then on or is reset in the next time.)
Perform any of the following operations to normally complete restoring data.
• Return the status of data when the parameters are backed up.
• Delete the backup data.
• Backup data again.

(6) Deleting backup data
Select [Online]

[Latch data backup operation] of GX Developer (Set the CPU module to STOP since data

cannot be deleted in the RUN status).
Also, information of special registers (SD671 to SD675) can be initialized (cleared to 0) by deleting the backup
data.

Figure 6.111 Screen for deleting backup data

6 - 144

CHAPTER6 FUNCTIONS

(7) Checking with special relays and special registers
The status of execution of latch data backup to the standard ROM or restoration operation can be checked by
SM671, SM676, SD671 to SD679.

(8) Precautions

The following provides precautions for backing up latch data.
1) Do not power off or reset the CPU module during backup of latch data. If performed, "RESTORE ERROR"
(error code: 2221) is detected, and backup data is not restored (The backup data are deleted).
2) Even if the backup data exists, the initial device value has a priority over the backup data when the initial

device value is set.
Therefore, the device where the initial device value setting is configured is overwritten by the device data
of the initial device value after reflecting the backup data.

3) Even if the latch device or latch range setting is used, backup data has a priority. Therefore, even when data
of latch device and latch range setting are changed after backup, it is overwritten by data backed up when
the CPU module is powered off and then on or is reset.

4) Devices where local device range setting is configured are not backed up. They are initialized (cleared to 0)
when the CPU module is powered off and then on or is reset.
5) When the number of writes to the standard ROM exceeds 100,000 times ("FLASH ROM ERROR" (error

code: 1610) is detected), data may not be normally backed up.
6) Backup data cannot be deleted unless the data are deleted or the storage location memory (standard ROM)
for the backup data is formatted.

7) The following operations cannot be performed during latch data backup. Perform them after the backup
operation.
6.28 Latch Data Backup to Standard ROM Function

If performed, an error is displayed on the GX Developer screen.
• Format PLC memory (standard ROM only)
• Latch data backup by remote operation
• Online change (ladder mode, files, function block)
• Write the program memory to ROM
• Write to PLC (Flash ROM)

6 - 145

6.29 Writing/Reading Device Data to/from Standard ROM
(1) Definition
This function writes device data to the standard ROM.
Writing the fixed values for operation and operation results to the standard ROM can prevent losing data due to
low battery. Also, timing of writing to the standard ROM can be set by an instruction.

(2) Execution method
Device data are written to the standard ROM by the SP.DEVST instruction.
The device data written to the standard ROM is read to the specified device by the S(P).DEVLD instruction.

(3) Devices that can be written to the standard ROM
Table6.48 shows the devices whose data can be written to the standard ROM.
Table6.48 Devices that can be written to the standard ROM and storage location
Device
*1

X,Y,M,L,B,F,V,T,ST,C,D ,W ,SM,SD,SB,SW,R,ZR

Storage location
Standard ROM(device data storage location)

*1: The extended data register (D) is included.
*2: The extended link register (W) is included.

(4) Setting method
The area for storing the device data is set in the standard ROM by the PLC file tab of the PLC parameter dialog
box.

Set a file size
(A file name is fixed to DEVSTORE).

Figure 6.112 Screen for setting a file for storing device data

Remark
For details of the instructions, refer to the following.
QCPU Programming Manual (Common Instructions)

6 - 146

CHAPTER6 FUNCTIONS

6.30 CPU Module Change Function with Memory Card

Note6.12

(1) Definition
This function backs up data in the CPU module to a memory card and restores the backup data to another CPU

module.Note1

Universal model QCPU
1) Backs up to a
memory card.

Program memory
Standard RAM

Standard ROM
Device data
Memory card for storing backup data

3) Restores backup
data.

System data

5
6
7
8

2) Changes the
CPU module.
GX Developer

6.30 CPU Module Change Function with Memory Card

Figure 6.113 CPU module change function with memory card

This function consists of the following two functions.
• Backup function to memory card:

Section 6.30.1

• Backup data restoration function:

Section 6.30.2

Note1

Note6.12

Universal

The Q00UJCPU, Q00UCPU, and Q01UCPU do not support the CPU module change function with memory card.
When using the function for the Q02UCPU, Q03UDCPU, Q04UDHCPU, Q06UDHCPU, Q13UDHCPU, Q26UDHCPU,
or Built-in Ethernet port QCPU, check the versions of the CPU module and GX Developer. (

Appendix 2)

6 - 147

(2) Backup data file
After data are backed up, a backup data file "MEMBKUP0.QBP" is created in a memory card.
Only one backup data file can be stored to a memory card.
When data are backed up to a memory card containing a backup data file again, the stored backup data file is
overwritten. When a memory card contains another file, a backup data file can be stored in the memory card
without deleting the stored file.*1 *2
*1: After restoration, if the parameters are stored in the memory card but not in the CPU module, the CPU module operates by
the parameter settings in the memory card.
*2: When data are backed up to the Flash card, only a backup data file can be stored.

The backup data file can be deleted by "Delete PLC data” of GX Developer.

(3) Backup data
(a) Backup data selection
Table6.49 shows data to be backed up.
Table6.49 Data to be backed up
Backup data (drive)

Description

Backup selection by the user

Program memory (drive 0)

All data in the program memory (drive 0)

Standard RAM (drive 3)

All data in the standard RAM (drive 3)

Standard ROM (drive 4)

All data in the standard ROM (drive 4)

Selectable

Internal user device

Device data*2

Not selectable

(M, L, B,F,V,T,ST,C,D,W)

(Data are automatically backed up by the

Data managed by the system (such as error

System data

system.)

history)

*1: Data in the program cache memory are backed up.
*2: Only the latch relay (L) and devices to which the latch range setting can be configured are backed up.

(b) Maximum backup data size
Table6.50 shows the maximum size of data that can be backed up.
Table6.50 Maximum size of data that can be backed up
Backup target data (drive)

Program memory (drive 0)

Q02UCPU

Q03UD/
Q03UDE
CPU

Q04UDH/
Q04UDEH
CPU

Q06UDH/
Q06UDEH
CPU

Q10UDH/
Q10UDEH
CPU

Q13UDH/
Q13UDEH
CPU

Q20UDH/
Q20UDEH
CPU

Q26UDH/
Q26UDEH
CPU

124

164

244

408

528

808

1048

130

194

258

770

1026

1282

Standard ROM (drive 4)

516

1032

2056

4104

Device data

128

System data

Total (maximum)

897

1542

1646

2238

3682

6386

6626

Standard RAM (drive 3)

(Unit: K byte)

The backup data size can be checked by the following methods.
• Execution screen of GX Developer (
• SD698 and SD699(

CHAPTER 12)*1

*1: Can check the data size after backup starts.

6 - 148

Section 6.30.1(1)(b))

CHAPTER6 FUNCTIONS

6.30.1 Backup function to memory card

This function can save data in the CPU module to a memory card.
If a memory card is used in running system, data can be backed up by replacing the current memory card with the one
for storing a backup data.

(1) Methods

2
3

(a) Method with contacts
1) Setting
To back up data with contacts, turn on the device set in the “PLC module change setting“ screen in the PLC

system tab of the PLC parameter dialog box.

5
6
7
8

6.30 CPU Module Change Function with Memory Card
6.30.1 Backup function to memory card

Figure 6.114 PLC module change setting screen
Table6.51 Setting items
Item
Backup start setup
contact*1
Backup start contact

Description

Setting range

At the rise of the selected device among the items
shown in the right column, backup is ready to start.
At the rise of the selected device among the items
shown in the right column, backup enters
execution status.

Available devices
• X (0 to 1FFF)
• B (0 to 1FFF)*3

Format memory card
before backup

Select whether to format a memory card before
backup.

Title setting*5

Set a title appended to backup data stored in a
memory card.

32 characters (16 in two-byte
characters)

Select data to be backed up stored in any of
*4

memories shown in right column.

• M (0 to 8191)*3
• Program memory (drive 0)
• Standard RAM (drive 3)
• Standard ROM (drive 4)
Formatted
Not formatted

Backup target data

Default

All drives are backed up.
Not formatted
Set the title of the current time.
(Example) If data are backed up at 12
p.m. on October 1, 2008,
"200810011200" is set.

*1: The CPU module enters the STOP status at the rise of the backup start setup contact, the backup start contact cannot be turned on in the
sequence program.
*2: The backup start setup contact and backup start contact cannot be set to the same device.
*3: This indicates the default number of points. The setting range when the internal user device is set to the maximum number of points (60K
points) is M(0 to 61439) and B(0 to 0EFFF).
*4: If data to be backed up is deselected in "Backup target data", only device data and system data are backed up.
*5: The title is used for identifying backup data.
Settings for the title of the backup data stored in a memory card can be checked on the Delete PLC data screen of GX Developer.

6 - 149

2) Operating procedure
Turn on in the order of the backup start setup contact and the backup start contact. Data are not backed up
when only the backup start contact is on.

Turn on the backup start setup contact.

Preparation for backup:
1) Set the CPU module to the STOP status.
2) Stop an operation that uses a memory
card so that the card can be removed.

1) Check that the preparation for backup
is completed by the following methods.
Check the LEDs.
Check the special relay and special register.
(a) SM691 is on.
(b) SD690 stores 2h.
2) Remove the mounted memory card.
3) Mount a memory card for storing backup data.
4) Turn on the backup start setup contact.

Back up data.

Check that the backup is completed by
the following methods.
Check the LEDs.
Check the special relay and special
register.
(a) SM691 is on.
(b) SD690 stores 4h.

Check the backup error*1.
Check the LEDs.
Check the special relay and special
register.
(a) SM691 is on.
(b) SD690 stores FFh.
(c) SD689 stores the error cause.

: Operation by the CPU module
: Operation by the user
Figure 6.115 Backup procedure using contacts
*1: Since the SM691 (Backup start preparation status flag) is on, data can be backed up again by turning off and then on the
backup start contact.

6 - 150

CHAPTER6 FUNCTIONS

3) Operation of contacts
Operations of the backup start setup contact, backup start contact, SM691 (Backup start preparation status

flag), and SD690 (Backup status) at backup are shown in Figure 6.116.
Backup start setup request from
GX Developer or the backup start
setup contact is turned on.

Before backup start

Backup start request from
GX Developer or the backup
start contact is turned on.

Backup start
Backup start prepared preparation completed Backup in execution

Backup completed

3
4

Backup start
setup contact
SM691
(Backup start
preparation status
flag)

ON
OFF

Backup start
contact

OFF

SD690
(Backup status)

7
0

Figure 6.116 Operation of contacts

If the backup start contact is turned on while the value in SD690 is 0H (Before backup start) or 1H (Backup
start prepared), data are not backed up.
turning off and then on the backup start contact again while the value in SD690 is 2H (Backup start
preparation completed) starts backup.

6 - 151

6.30 CPU Module Change Function with Memory Card
6.30.1 Backup function to memory card

If the backup start contact is on before the value in SD690 becomes 2H (Backup start preparation completed),

(b) Backup from GX Developer
Select [Online]

[PLC module change]

[Create backup data...].

Figure 6.117 Create backup data screen

For details of the operating procedure by the GX Developer wizard, refer to the following.
GX Developer Version 8 Operating Manual

Clicking the Confirm data size button on the screen shown in Figure 6.117 displays the size of backup data created at
backup.
Data size can be checked by GX Developer connected to the CPU module.
This function is available regardless of the operating status of the CPU module (RUN, STOP, PAUSE) or mounting status of
a memory card.

6 - 152

CHAPTER6 FUNCTIONS

(2) Operations of backup to a memory card
(a) Mounting/removal of a memory card
In a system using a memory card, the memory card can be changed/removed after preparation for backup has
been completed (Turning on SM609 (Memory card remove/insert enable flag) is unnecessary).

After preparation for backup has been completed, the CPU module turns off SM604 (Memory card in-use flag).

(b) Status of backup to a memory card
Table6.52 shows backup status.

Table6.52 Backup status
Status

Description

Value in SD690

Before backup start

Backup is not started.

Backup start prepared

A memory card can be mounted/removed.

Backup start preparation completed

Set data to be backed up.

Backup in execution

Backup is in execution.

Backup completed

Backup is normally completed.

Backup error

Backup failed due to an error.

FFH

5
6
7

Start

Before backup start

The backup start setup
contact is turned on.

Backup start prepared
Backup is ready to start.

Backup start preparation completed

The backup start contact
is turned on.

Backup start request
from GX Developer

Data are backed up again.

Backup in execution

Backup to the memory card is completed.

Backup failed.

Backup completed

Backup error

End
Figure 6.118 Flow of status change at backup

6 - 153

6.30 CPU Module Change Function with Memory Card
6.30.1 Backup function to memory card

Backup start setup
request from
GX Developer

(c) Operations of special relays and special register*1
Figure 6.119 shows the operations of the SM609 (Memory card remove/insert enable flag), SM691 (Backup
start preparation status flag), and SD690 (Backup status).
Backup start setup request from
GX Developer or the backup
start setup contact is turned on.

Backup start request from
GX Developer or the backup
start contact is turned on.

Backup start
Before backup start Backup start prepared preparation completed Backup in execution

SM609*2
(Memory card
remove/insert
enable flag)
SM691
(Backup start
preparation
status flag)
SD690
(Backup status)

Backup completed

ON
OFF
ON
OFF

Figure 6.119 Special relays and special register at backup
*1: For details of the special relays and special register used for backup, refer to CHAPTER 12.
*2: This special relay is turned on/off by the system.

(d) Operating status of the CPU module
After END processing where the backup start setup request is accepted, the CPU module changes the
operating status to STOP at backup. Therefore, data can be backed up regardless of the operating status.
After backup, power off and then on the CPU module or reset the CPU module.(If the CPU module is not
powered off and then on or is not reset but set the RESET/STOP/RUN switch to RUN, the CPU module
remains in the STOP status).
Backup start setup request from
GX Developer or the backup start
setup contact is turned on.

Before backup start

CPU operating
status

Backup start
Backup start prepared preparation completed Backup in execution

RUN/STOP*1
STOP*1
/PAUSE
Figure 6.120 Operating status of the CPU module at backup

*1: The status includes a stop error.

6 - 154

Backup start request from
GX Developer or the backup
start contact is turned on.

Backup completed

CHAPTER6 FUNCTIONS

(3) LEDs indicating backup status
The LEDs on the front of the CPU module indicate backup status.

Table6.53 LEDs indicating backup status
Value stored in

Backup status

SD690

Backup start preparation

completed

LED indication

MODE: Flash (green), BAT.: Flash (green)
The color changes at intervals of 800ms as follows.

Backup in execution

: Flashing (green)
: On (red)
: On (green)

4H
FFH

Backup completed

MODE: Flash (green), BAT.: Flash (green), BOOT: Flash (green)

Backup error

MODE: Flash (green),USER: MODE: Flash (red), BAT.: Flash (green)

7
8

(4) Error cause of backup
When backup is not normally completed, an diagnostic error is not detected. In that case, the error cause is

Table6.54 Error cause of restoration
Value stored
in SD689

Error
Error cause

response
number

100H

Restoration started while a memory card was not mounted.

200H

Size of data to be backed up exceeds the capacity of mounted memory card.

300H

Write protection has been set to the memory card.

400H

Writing to the memory card was not normally completed.

500H

Reading from a drive storing backup data was not normally completed (program memory read error).

503H

Reading from a drive storing backup data was not normally completed (standard RAM read error).

504H

Reading from a drive storing backup data was not normally completed (standard ROM read error).

510H

Reading from a drive storing backup data was not normally completed (system data read error).

600H*1

4335H*2

Backup preparation started while latch data were backed up to the standard ROM.

601H*1

410AH*2

Backup preparation started while data were written in the RUN status.

602H *1

4336H*2

Backup preparation started while a FTP client connected a FTP to the CPU module in FTP connection.

4082H*3,
4330H*4
4333H*2

Backup preparation or backup started while another backup was in execution.
Backup started while the CPU module was in "Before backup start" (SD690 = 0).

*1: Only when data are backed up with contacts
*2: Only when data are backed up from GX Developer
*3: Only when data area backed up from another boot source.
*4: Only when data area backed up from the same boot source.

6 - 155

6.30 CPU Module Change Function with Memory Card
6.30.1 Backup function to memory card

stored in SD689(Backup error factor) and the error response is returned to GX Developer.

(5) Functions that cannot be performed during backup
Table6.55 shows functions that cannot be performed during backup.
Table6.55 Functions that cannot be performed during backup
Category

Function

Drive operation

Online change

Category

Format PLC memory

Trace

Write the program memory to ROM

Remote operation

Program memory batch transfer

Function
Sampling trace registration
Remote latch clear
Write to PLC

Arrange PLC memory

Delete PLC data

Online change (ladder mode)

Write PLC user data

Online change (files)

File operation

Delete PLC user data

Online change (multiple blocks)

Password registration

Change TC setting

Latch data backup operation

Monitor

Monitor condition setup

Debug

Executional conditioned device test

FTP function

For all operations and commands

(6) Precautions
(a) Do not perform the following operations during backup.
• Mounting/removal of a memory card
• Power-off of the CPU module
• Reset

(b) Even if booting parameters backed up with contacts for the Universal model QCPU
having the serial number (first five digits) is "10101" or earlier, the system ignores
the parameters.
In this case, even if the backup start setup contact or backup start contact set by the
parameters is turned on, the operating status of the CPU module does not change (a
diagnostic error is not detected).
(c) After backup is ready to start, the following functions stop (do not resume the
operations even after the backup).
• Refresh of network modules
• Data link transfer
• Auto refresh of intelligent function modules
• Auto refresh of CPU shared memory

6 - 156

CHAPTER6 FUNCTIONS

6.30.2 Backup data restoration function

This function restores data backed up to a memory card to the CPU module.

(1) Methods
(a) Restoration from GX Developer
Select [Online]

[PLC module change]

[Restore...].

4
5
6
7

Figure 6.121 Restore screen

After selecting "Execute" on the screen above and powering off and then on the CPU module or reset the CPU
module, the restored data become valid.

(b) Automatic restoration
parameter dialog box. (

ON" in "PLC module change setting" in the PLC system tab of the PLC

Section 6.30.1(1)(a))

After data are backed up and the CPU module is powered off and then on or is reset, restoration automatically
starts.
Also, items shown in Table6.56 can be set by the option setting.
Table6.56 Option setting items
Option setting item
Restore for the first time only
*1 *2

Restore every time

The CPU module is powered off and then on or is reset
First time
Restored
Restored

After the first time
Not restored (The CPU module operates the memory card as
usual.)*3
Restored

*1: This setting is valid only when backup data are stored to the ATA card or SRAM card.
Note if the write protect switch of the SRAM card is set to be valid (write protection), the setting does not
become valid and the data are restored even after the first time ("RESTORE ERROR" (error code: 2226)
occurs).
*2: When using the FLASH card, restoration can be performed even after the first time.
*3: Restoration after the first time can be performed from GX Developer.

Data are restored at initial processing after the CPU module is powered off and then on or is reset.
After restoration, powering off and then on the CPU module or resetting the CPU module again is not required
to change the operating status to the one set with the RUN/STOP/RESET switch.
If a memory card needs to be changed after restoration, turn on SM609 (Memory card remove/insert enable
flag) and change the memory card after SM600 (Memory card usable flags) turns off.

6 - 157

6.30 CPU Module Change Function with Memory Card
6.30.2 Backup data restoration function

Select ”Auto restore at turn OFF

(2) Operation for restoring backup data
Figure 6.122 shows operation for restoration.
Automatic restoration

Restoration from GX Developer

Start

1: Before restoration start

1: Before restoration start
Mount a memory card storing the
backup data to the CPU module and
restore the data with GX Developer.

Restoration is
performed again.

Mount a memory card storing the backup data
to the CPU module and power off and then on
the CPU module or reset the CPU module.

Restoration is
performed again.

2: Restoration in execution

Restoration failed.

Restoration is completed.

4: Restoration error

3: Restoration completed

Restoration failed.

4: Restoration error

Restoration is completed.

3: Restoration completed

Restoration is suspended.

End

After restoration, the CPU module can continue operation.
Powering off and then on the CPU module or
resetting the CPU module is unnecessary.

After restoration, power off and then on the
CPU module or reset the CPU module.

Figure 6.122 Operation for restoration

A value indicating restoration status is stored in SD693 (Restoration status).
Table6.57 Status at restoration
Status

Description

Value stored in SD693

Before restoration start

Restoration is not performed.

Restoration in execution

Restoration is in execution.

Restoration completed

Restoration is normally completed.

Restoration error

Restoration failed due to an error.

FFH

(3) Operation of special relay and special register*1
Figure 6.123 shows the operation of SM692 (Restoration complete flag) at restoration.
Before
restoration start
SM692
(Restoration
complete flag)

Restoration in
execution

Restoration
completed

On
Off
Figure 6.123 Operation of the special relay

*1: For details of special relays and special registers for restoration, refer to CHAPTER 12.

6 - 158

CHAPTER6 FUNCTIONS

(4) LEDs indicating restoration status
The LEDs on the front of the CPU module indicate restoration status.

Table6.58 LEDs indicating restoration status
Value stored in

Restoration status

SD693
0H

LED indication

Before restoration start

MODE: On (green)
The color changes at intervals of 800ms as follows.

4
1H

Restoration in execution

: Flashing (orange)
: On (red)
: On (green)

• Restoration from GX Developer
2H

MODE: Flashing (orange), BAT.: Flashing (green), BOOT: Flashing (green)

Restoration completed

• Automatic restoration
MODE:On (green)

• Restoration from GX Developer
MODE:Flashing (orange), USER: Flashing (red),BAT.:Flashing (green)

Restoration error

FFH

• Automatic restoration
MODE:On (green), ERR: Flashing (red)

When restoration is not normally completed, an diagnostic error is not detected. In that case, the error cause is
stored in SD692 (Restoration error factor) and the error response is returned to GX Developer.
Table6.59 Error cause of restoration
Value stored

Error response

in SD692

number

800H

801H

810H

4335H*1

Restoration started while latch data were backed up to the standard ROM.

410AH*1

Restoration started while data were written in the RUN status.

4336H*1

Restoration started while a FTP client connected a FTP to the CPU module in FTP connection.

4330H*1

Restoration started while another restoration was in execution.

Error cause
The CPU module where data are restored is different model with the one where the backup source
data are stored.
• Backup data files do not match.
• Reading of backup data from a memory card was not normally completed.
Writing of backup data to the restoration destination drive was not normally completed.

41FEH

Restoration started while a memory card was not mounted.

*1: Only when data are restored from GX Developer

6 - 159

6.30 CPU Module Change Function with Memory Card
6.30.2 Backup data restoration function

(5) Error cause of restoration

When automatic restoration is not normally completed, “RESTORE ERROR” (error code: 2225 to 2227) is
detected.
Table6.60 Error when automatic restoration is not normally completed
Error code

Error message

Error cause
The CPU module where data are restored is different model with the one where the backup

2225

source data are stored.
• Backup data file is corrupt (The contents of backup data file do not match with the check

2226

RESTORE ERROR

code).
• Reading of backup data from a memory card was not normally completed.
• The write protect switch of the SRAM card is valid (write protection), and therefore "Restore
for the first time only" cannot be set to valid.

2227

Writing of backup data to the restoration destination drive was not normally completed.

Remark
For details of error codes, refer to the following.
QCPU User's Manual (Hardware Design, Maintenance and Inspection)

(6) Functions that cannot be performed during restoration
Functions that cannot be performed during restoration are the same as the ones that cannot be performed during
backup. (

Section 6.30.1(5))

(7) Precautions
(a) Do not perform the following operations during restoration.
• Mounting/removal of a memory card
• Power-off of the CPU module
• Reset

(b) Even if mounting a memory card storing backup data file to the Universal model
QCPU having the serial number (first five digits) is "10101" or earlier and powering
off and then on the CPU module or reset the CPU module, the system ignores the
backup data file and starts operation (a diagnostic error is not detected).
(c) Do not use a memory card where the boot file setting parameter is stored. If used,
data in the memory card are overwritten by the boot file setting even restoration is
performed.
(d) If restoration is started from GX Developer, the following functions stop (do not
resume the operations even after the restoration).
• Refresh of network modules
• Data link transfer
• Auto refresh of intelligent function modules
• Auto refresh of CPU shared memory

6 - 160

CHAPTER6 FUNCTIONS

6.31 Module model name read

Note1

Note6.13

(1) Definition

This function reads the model name of a module on a base unit.
The mounted module is identified in a ladder program and processing according to the module can be performed.
QD75MH2
QD75MH4

Processing 1 and 2 are performed.
Processing 1 and 3 are performed.

3
4

Processing common to
the QD75M modules

Module model name read
Processing 1
Device memory
Module model name read
instruction
Reads the module name of the specified module by the
instruction.
TYPERD

= D0 K0

Execution result of D0
the instruction
D1
Checks the execution
result of the
instruction.

Module model name
"QD75MH2"

SET MO

M0
$= D1

"QD75MH2"

Processing 2

$= D1

"QD75MH4"

Processing 3

Reads the character string.

Identifies the mounted module and performs
processing according to the module.

Figure 6.124 Operation of the module model name read
6.31 Module model name read

(2) Execution method
Use the TYPERD instruction.

Remark
For details of the instruction, refer to the following.
QCPU Programming Manual (Common Instructions)

Note1

Note6.13

Universal

When using the module model name read function, check the versions of the CPU module and GX Developer.
(

Appendix 2)

6 - 161

6.32 Module error collection

Note6.14

Note1

(1) Definition
This function collects errors occurred in the connected intelligent function modules in the CPU module.
By storing the errors in a memory that can hold data in the event of a power failure, the errors can be held even
after power-off or reset.
Error history (CPU module) and error log (intelligent function module)
are displayed in one screen.
Errors that occurred in the entire system (base units) can be
monitored in reverse chronological order.
CPU
Error C1 occurred!

Module A

Module B

19:29 Error A1 occurred!
19:36 Error A2 occurred!

19:34 Error B1 occurred!

Programming tool

Error history display
Time Module in error Error code
19:29
19:33
19:34
19:35

Module A
CPU
Module B
Module A

Error A1
Error C1
Error B1
Error A2

Error history
(CPU module)

Module error log
Time Module in error Error code

19:33 Error C1

19:29
19:34
19:36

ModuleA
ModuleB
ModuleA

Error A1
Error B1
Error A2

[Example of screen display]

Figure 6.125 Operation of module error collection

(2) Supported modules
The CPU module collects errors occurred in the connected intelligent function modules*1.
The CPU module does not collect the errors of intelligent function modules on other stations in the network.
*1: Indicates intelligent function modules that support this function. For supported module versions, refer to the manual for
each module.

(3) Timing when module errors are collected
Module errors are not collected during execution of a program such as the COM instruction but collected in END
processing.

Note1

Note6.14

Universal

When using the module error collection, check the versions of the CPU module and GX Works2. (
GX Developer cannot display module errors.

6 - 162

Appendix 2)

CHAPTER6 FUNCTIONS

(4) Storing module errors
The module errors can be stored either the system memory*1 or the standard RAM.

The errors are stored separately from error history (CPU module) data.
*1: The memory is managed inside the system.
Table6.61 Storage locations and the number of storable module errors
CPU module

System memory

Standard RAM

Q00UJCPU

40 (Fixed)

Q00UCPU, Q01UCPU

40 (Fixed)

1000

Q02UCPU, QnUD(H)CPU, Built-in Ethernet port QCPU

100 (Fixed)

1000

3
4
5

(5) Setting method
Select "Collect error histories of intelligent function modules" in "Module Error History Collection (Intelligent
Function Module)" in the PLC RAS tab of the PLC parameter dialog box.

6
7
8

6.32 Module error collection

Figure 6.126 PLC RAS

Table6.62 PLC RAS setting list
Item

Description

Corresponding
Memory

Select a storage location.

History No.

Set the number of collected errors only when the errors are
stored in the standard RAM.

Collection No.

Set the number of collected errors in one scan.*3

Setting range
• System Memory
• Standard RAM*1, *2
32 to 1000
• Stored in system memory: 1 to 100
• Stored in standard RAM: 1 to 128

Default
System Memory
40/100
1

*1: When a sampling trace file is stored to the standard RAM, powering off and then on or resetting the CPU module will delete the file.
*2: The battery consumption may be increased.
QCPU User's Manual (Hardware Design, Maintenance and Inspection)
*3: If collected module errors are frequently lost, set a greater value to "Collection No.". The recommended value is the number of intelligent
function modules that support this function.

Parameter settings are enabled to the CPU module when:
• the CPU module is powered off and then on or
• the CPU module is reset.

6 - 163

(6) Monitoring module errors
Collected module errors can be monitored in the Error History screen opened by selecting [Diagnostics]
[System Monitor]

[System Error History] of GX Works2.

Figure 6.127 Error History screen

Table6.63 Description of Error History List
Item
Error Code

Description

Remarks

Displays error code numbers.

Year/Month/Day/Time*2

Displays the year, month, day, hour, minute, and second when

The year can be displayed within the

an error occurred.

range of 1980 to 2079.

Model Name

Displays a module model name.

Start I/O

Displays the start I/O number of a module in error.

*1: For details of error codes, refer to the manual for the intelligent function module.
*2: If an error occurred during initial processing, its occurrence time may be stored as "0000/00/00 00:00:00" in the module
error collection file. In this case, the error is not displayed in correct order in Error History List.

●

The Error History screen can be displayed by selecting a module figure in the System Monitor screen and clicking the
Error History Detail button.
In this case, only the errors of the selected module is displayed.
GX Works2 Version1 Operating Manual (Common)

6 - 164

●

Errors are not displayed for modules that do not support the module error collection function.

●

Errors may not be displayed when they occur successively.

CHAPTER6 FUNCTIONS

(7) Clearing module error history
Clear module error history by clicking the Clear History in the Error History screen.
Note that error information on each intelligent function module displayed in the Module's Detailed Information
screen is not cleared.

2
3
4
5

Error information displayed
here is not cleared.

6
7

Figure 6.128 Module's Detailed Information screen

8
The module error history is cleared when the standard RAM is formatted.
Note that a module error collection file cannot be deleted since it is automatically created after the CPU module is powered
off and then on or is reset. To delete the file, clear the setting and then format the standard RAM.
6.32 Module error collection

(8) Precautions
(a) Using the CPU module change function with memory card
Backing up or restoring data will stop collecting module errors.

6 - 165

CHAPTER7 COMMUNICATIONS WITH INTELLIGENT
FUNCTION MODULE
(1) Intelligent function module
The intelligent function module allows the CPU module to process analog quantity and high speed pulses that
cannot be processed by the I/O modules.
For example, the analog-digital conversion module, one of the intelligent function modules, uses analog quantity
by converting it into a digital value.

(2) Communication with intelligent function module
The intelligent function module is equipped with a memory (buffer memory) to store the data taken in from or
output to external devices.
The CPU modules writes or reads data to or from the buffer memory of the intelligent function module.

7.1 Communications between CPU Module and Intelligent Function
Module
The following table shows the communication methods between the CPU module and intelligent function modules and
the communication timing.
Table7.1 Communication methods with intelligent function module and the communication timing
Communication timing
Communication methods with intelligent
function module

GX Configurator

Power off
on

CPU
module is
reset

STOP
RUN*2

Initial setting
Auto refresh setting

Initial device value

Instruction

END

execution

processing

Reference

Section 7.1.1

Section 7.1.2

FROM or TO instruction*1

Section 7.1.3

Intelligent function module device*1

Section 7.1.4

Intelligent function module dedicated instruction*1

Section 7.1.5

: Executed, -: Not executed
*1: Indicates the program that uses the intelligent function module device, FROM or TO instruction, or the intelligent function module
dedicated instruction.
*2: The RUN/STOP/RESET switch is set from STOP
RUN (RUN LED flashes)
STOP
RUN.

7-1

●

Data, such as initial settings used for communications with intelligent function module, are stored in the CPU module.
For the storage location, refer to Section 5.1.

●

Power off and then on or reset the CPU module to make the initial setting configured in GX Configurator taken effect.

CHAPTER7 COMMUNICATIONS WITH INTELLIGENT FUNCTION MODULE

7.1.1 Initial setting and auto refresh setting by GX Configurator

The initial setting and auto refresh setting can be made by adding in GX Configurator that is supported by the
intelligent function module to GX Developer.
After the initial and auto refresh settings, data can be read or written without creating a program for communications

with intelligent function modules.

(1) Starting GX Configurator
Select [Tools]

[Intelligent function module utility]

[Start] in GX Developer.

(2) Setting in GX Configurator
An example of initial setting and auto refresh setting for the A/D conversion module Q64AD is used in this section.

(a) Initial setting

The initial setting for the Q64AD offers the following four types.

• A/D conversion enable/disable setting
• Sampling process/averaging process setting
• Time/number of times specifying

• Average time/average number of times setting
Make the initial settings of the Q64AD in the Initial setting screen in GX Configurator as shown in Figure 7.1.

The initial setting data set in this screen are stored into the intelligent function module parameters of the CPU
module.

7-2

7.1 Communications between CPU Module and Intelligent Function Module
7.1.1 Initial setting and auto refresh setting by GX Configurator

Figure 7.1 Initial setting screen

(b) Auto refresh setting
The CPU module devices for storing the following data can be set in the Auto refresh setting screen.
• Digital output of the Q64AD
• Maximum and minimum values of the Q64AD
• Error codes
Make auto refresh settings of the Q64AD in the Auto refresh setting screen in GX Configurator as shown in
Figure 7.2.

Figure 7.2 Auto refresh setting screen

The auto refresh setting data set in this screen are stored into the intelligent function module parameters of the
CPU module.

7-3

CHAPTER7 COMMUNICATIONS WITH INTELLIGENT FUNCTION MODULE

(3) Limitation on the number of parameter settings
Limitations are placed on the number of parameters (initial setting and auto refresh setting) set in GX
Configurator.
When multiple intelligent function modules are mounted, make setting in GX Configurator so that the number of

parameter settings for all intelligent function modules may not exceed the limitation shown in Table7.2.

Table7.2 Maximum number of parameters set in GX Configurator
CPU module

Maximum number of parameter settings
Initial setting

Auto refresh setting

Q00UJCPU, Q00UCPU, Q01UCPU

512

256

Q02UCPU

2048

1024

4096

2048

Q03UDCPU, Q04UDHCPU, Q06UDHCPU,
Q10UDHCPU, Q13UDHCPU, Q20UDHCPU, Q26UDHCPU,
Q03UDECPU, Q04UDEHCPU, Q06UDEHCPU,

Q10UDEHCPU, Q13UDEHCPU, Q20UDEHCPU, Q26UDEHCPU

6
One line in the Auto refresh screen is counted as one parameter setting.

7
8

7.1 Communications between CPU Module and Intelligent Function Module
7.1.1 Initial setting and auto refresh setting by GX Configurator

This one line is counted as one
parameter setting.
Blanks are not counted.
Add the number of lines on
this screen to those of other
intelligent function modules.

Figure 7.3 Counting the number of parameter settings

Remark
For details of GX Configurator, refer to the manual for the intelligent function module used.

7-4

7.1.2 Initial setting by initial device value
(1) Initial device value
Using an initial device value (

Section 6.25) allows the initial setting of the intelligent function module without

a program.
The set initial device values are written from the CPU module to the intelligent function module when the CPU
module is powered off and then on, is reset, or set from STOP to RUN.

(2) Setting initial device values
Use GX Developer to set the following.
• Set the device data of the intelligent function module (

Section 9.5.1) used as the initial device value to

the device memory.
• In the initial device value setting, specify the device range of the intelligent function module used as the initial
device value.

7.1.3 Communications with the FROM and TO instructions
The FROM instruction stores data read from the buffer memory of the intelligent function module to the specified
device.
The TO instruction writes data stored in the specified device to the buffer memory of the intelligent function module.

Remark
• For details of the FROM and TO instructions, refer to the following.
QCPU Programming Manual (Common Instructions)
• For details of the buffer memory of the intelligent function module, refer to the following.
Manual for the intelligent function module used

7-5

CHAPTER7 COMMUNICATIONS WITH INTELLIGENT FUNCTION MODULE

7.1.4 Communications using the intelligent function module device

(1) Intelligent function module device
The intelligent function module device (

Section 9.5.1) represents the buffer memory of the intelligent

function module as one of the CPU module devices.
The data stored in the buffer memory of the intelligent function module can be treated by the sequence instruction
as well as the device memory.

A programming example is given below for the case where "100" is written to the buffer memory of an address 0
of the intelligent function module whose I/O number is X/Y20 to X/Y2F.

MOV K100 U2\G0
Buffer memory address
I/O number X/Y20

Figure 7.4 Use of the intelligent function module device

(2) Difference from the FROM and TO instructions

The intelligent function module device processes data read from the intelligent function module with one
instruction as the device can be treated as one of the CPU module devices.
A program example is given below for the case where data read from the intelligent function module are added
and then the result is stored in D2.
+ U2\G0 D0 D2

7
8

Figure 7.5 Application example of the intelligent function module device

This reduces the number of steps in whole program.
function module.

7-6

7.1 Communications between CPU Module and Intelligent Function Module
7.1.4 Communications using the intelligent function module device

The instruction processing time indicates the time required for instruction execution and accessing the intelligent

The intelligent function module device accesses the intelligent function module every time when an instruction is executed.
When writing or reading buffer memory data using multiple intelligent function module devices in a sequence program, write
or read the data with the FROM or TO instruction in one location of the program.

Figure 7.6 Writing using multiple intelligent function module devices

Stores data in the
data register.

Writes data once
at this point.

Figure 7.7 Writing using the TO instruction

7-7

CHAPTER7 COMMUNICATIONS WITH INTELLIGENT FUNCTION MODULE

7.1.5 Communications using the intelligent function module dedicated
instruction

(1) Intelligent function module dedicated instruction

This instruction enables easy programming for the use of functions of the intelligent function module.

(a) Example with the serial communication module dedicated instruction (OUTPUT
instruction)

The OUTPUT instruction allows communications with external device by nonprocedural protocol regardless of
the buffer memory address of the serial communication module.

[Transmission by the OUTPUT instruction]
CPU module
b15
S2 +0
+1
+2

Serial communication module
to

Set the used
channel in
control data.

Channel
1

Send

Channel
2

Send

6
7
8

(2) Processing of the intelligent function module dedicated instruction
Some of intelligent function module dedicated instructions can specify the completion device.
This completion device turns on for one scan when an instruction execution is completed.
When using multiple intelligent function module dedicated instructions to one intelligent function module, execute
the dedicated instructions one by one after the completion device turns on.

7-8

7.1 Communications between CPU Module and Intelligent Function Module
7.1.5 Communications using the intelligent function module dedicated instruction

Figure 7.8 Communications with external devices using the OUTPUT instruction

(3) Precautions
(a) When the CPU module is set from RUN to STOP before the completion device turns
on
When a intelligent function module dedicated instruction is executed and the CPU module is set from RUN to
STOP before the completion device turns on, the completion device will not turn on until the CPU module is set
to RUN and then finishes one scan.

(b) Available range
The intelligent function module dedicated instructions are not applicable to the intelligent function modules
mounted on remote I/O stations of MELSECNET/H.
The instructions are applicable to the intelligent function modules mounted on the base unit or extension base
units.

Remark
For intelligent function module dedicated instructions and completion devices, refer to the following.
Manual for the intelligent function module used

7-9

CHAPTER8 PARAMETERS

This chapter describes the parameters required to be set for configuring a programmable controller system.

(1) Parameter types
The following parameters are provided for CPU module setting.
• PLC parameters (

Section 8.1)

These parameters are set when a programmable controller is used.
• Network parameters (

Section 8.2)

These parameters are set when a programmable controller module is used in combination with any of CCLink IE controller network modules, MELSECNET/H modules, Ethernet modules, and CC-Link modules.
• Remote password (

Section 8.3)

Parameters are set when the remote password function is used for an Ethernet module, serial

communication module, modem interface module, or Built-in Ethernet port QCPU.

(2) Parameter setting method

Use GX Developer.
For the setting details, refer to the following.
GX Developer Version 8 Operating Manual

Grayed-out (unselectable) parameter settings in GX Developer are not available since the corresponding function is not
supported.

Remark
Each parameter number shown in the tables in this chapter is stored in the special register (SD16 to SD26) when an error
occurs in parameter setting.
Identify the parameter error location from the parameter number.
For the list of the special register (SD16 to SD26), refer to CHAPTER 12.
For the parameter updating procedure, refer to CHAPTER 11.

8-1

8.1 PLC Parameters
This section provides the list of PLC parameters and describes parameter details.

(1) PLC name
A label and a comment for the CPU module are set.
The settings will be displayed in the list for the find CPU function.

Note8.1Note1

Figure 8.1 PLC name

Table8.1 PLC name setting list
Parameter
No.

Description

Label

0000H

Set a label (name, application) for
the CPU module.

Up to 10 characters

Blank

Comment

0001H

Set a comment for the CPU
module label.

Up to 64 characters

Blank

Item

Setting range

Default

Reference

Note1

Note8.1

Universal

The Universal model QCPUs other than the Built-in Ethernet port QCPU do not support the find CPU function.

8-2

CHAPTER8 PARAMETERS

(2) PLC system
Parameters required for use of the CPU module are set.

2
3
4
5
6
7

Figure 8.2 PLC system

Table8.2 PLC system setting list
Item
Low speed

Description

Setting range

Default

Reference

1ms to 1000ms (in increments of 1ms)

100ms

Section 9.2.10

0.01ms to 100.0ms (in increments of
0.01ms)

10.0ms

Section 9.2.10

1000H

Set the time limit for the low
speed timer or high speed timer.

1001H

Set the contacts that control RUN/
PAUSE of the CPU module.
X0 to 1FFF
Setting of only the PAUSE contact
is not allowed.

Blank

Latch data backup
operation valid contact

1014H

Set the valid contact device No.
for backup of latch data to the
standard ROM.

X, M, B

Blank

Section 6.28

Remote reset

1002H

Select whether to allow the
remote reset from GX Developer.

Selected/deselected

Deselected

Section 6.6.3

Output mode at STOP to
RUN

1003H

Set the status of the outputs (Y)
when the operating status is
switched from STOP to RUN.

Previous state, Recalculate (output is 1
scan later)

Previous state

Section 6.4

Intelligent function module
setting (Interrupt pointer
setting)

100AH

Assign the interrupt pointers (I50
to I255) and set the start I/O
number and start SI number of
each intelligent function module.

Blank

Section 9.11

Module synchronization

100CH

Select whether to synchronize
CPU module startup with
intelligent function module
startup.

RUNPAUSE
contcts

High speed
RUN
PAUSE

• Start I/O No.
• Start SI No.
• I50 to 255

Selected/deselected

Section 6.6.1

Deselected

Section 6.6.2

(To the next page)

8-3

8.1 PLC Parameters

Timer limit
setting

Parameter
No.

Table8.2 PLC system setting list (continued)
Parameter
No.

Description

Common pointer No.

1005H

Set the start number of common pointers.

P0 to 4095

Blank

Section 9.10.2

Points occupied by
empty slot

1007H

Set the number of points for empty slots
on the main/extension base units.

0, 16, 32, 64, 128, 256, 512, or
1024 points

16 points

Section 3.2.2

Fixed scan
interval (n:
28 to 31)

1008H

Set each execution interval for the
interrupt pointers (I28 to I31).

0.5ms to 1000ms
(in increments of 0.5ms)

Interrupt program/Fixed
scan program setting

1008H

Enable or disable high speed execution
of interrupt programs or fixed scan
execution type programs.

Selected/deselected

Service processing
setting

1013H

Select any of the following options.
• Execute the process as the scan time
proceeds.
• Specify service process time.
• Specify service process execution
counts.
• Execute it while waiting for constant
scan time setting.

PLC module change
setting (PLC module
change setting)

1017H

Set items required when performing the
CPU module change with memory card
function.

Item

System
interrupt
settings

8-4

Setting range

Default

•
•
•
•

I28: 100.0ms
I29: 40.0ms
I30: 20.0ms
I31: 10.0ms

Reference

Section 9.11

Deselected

Section 2.2.3,
2.3.4

• 1 to 99% (in increments of
1%)
• 1 to 10 (in increments of 1
time)
• 0.2 to 1000ms (in increments
of 0.1ms)
• Blank

Execute the
process as the
scan time
proceeds.: 10%

Section 6.24.1

•
•
•
•

Blank

Section 6.30

Backup start setup contact
Backup start contact
Backup target data
Title setting

CHAPTER8 PARAMETERS

(3) PLC file
Parameters required for the files used in the CPU module are set.

2
3
4
5
6
7

Figure 8.3 PLC file

Table8.3 PLC file setting list
Parameter
No.

Description

Setting range

1100H

Set a file for the file register used in
the program.

• Not used
• Use the same file name as the
program.
• Use the following file.

1104H

Select whether to batch-transfer
the data in the file register at the
time of latch data backup to the
standard ROM.

1101H

Set a file for device comments
used in the program.

• Not used
• Use the same file name as the
program.
• Use the following file.

Not used

Initial Device value

1102H

Set a file for initial values of the
devices used for the CPU module.

• Not used
• Use the same file name as the
program.
• Use the following file.

Not used

Section 6.25

File for local device*1

1103H

Set a file for local devices used in
the program.

• Not used
• Use the following file.

Not used

Section 9.14.2

File use for SP.DEVST/S.DEVLD
instruction

1105H

Set a device data file used for
writing to or reading from the
standard ROM.

• Not used
• Use the following file.

Not used

Section 6.28

Item

Transfer to Standard ROM at
Latch data backup operation*1

Comment file used in a
command

Checked/unchecked

Reference

Not used

Section 9.7

Not selectable

Section 6.27

*1: Not available for the Q00UJCPU.

8-5

8.1 PLC Parameters

File register*1

Default

(4) PLC RAS (1)
Parameters required for performing the RAS functions are set.

Figure 8.4 PLC RAS (1)

Table8.4 PLC RAS (1) setting list
Item

WDT
(Watchdog
timer) setting

Parameter
No.

Description

Setting range

Default

Reference

Set a watchdog timer value for
the CPU module.

10ms to 2000ms
(in increments of
10ms)

200ms

Section 6.16

Set a watchdog timer value in
the case of using an initial
execution type program.

10ms to 2000ms
(in increments of
10ms)

Blank

Section 2.3.1

3002H

Set the operation mode of the
CPU module when an error is
detected.

Stop/Continue

Stop

Section 6.17

3001H

Enable or disable detection of
the specified error.

Selected/deselected

Deselected

Section 6.17

3003H

Set a constant scan time value.

0.5ms to 2000ms
(in increments of
0.5ms)

Blank

Section 6.2

WDT Setting
3000H
Initial execution monitoring
time
Computation error
Expanded command error*1
Fuse blown

Operating mode
when there is an
error

Module verify error
Intelligent module program
execution error
File access error
Memory card operation
error*3
External power supply OFF*1
Carry out battery check
Carry out fuse blown check
Verify module

Error check

Check device range at
indexing.
Diagnose redundant power
supply system.*2

Constant scanning

*1: These items are provided for future expansion.
*2: When selecting this item for the Q02UCPU, Q03UDCPU, Q04UDHCPU, Q06UDHCPU, Q13UDHCPU, or Q26UDHCPU, check the
versions of the CPU module and GX Developer. (
Appendix 2)
*3: Not available for the Q00UJCPU, Q00UCPU, and Q01UCPU.

8-6

CHAPTER8 PARAMETERS

(5) PLC RAS (2)

Note8.2

Note1

Parameters required for performing the RAS functions are set.

2
3
4
5
6
7

Figure 8.5 PLC RAS (2)

Table8.5 PLC RAS (2) setting list
Item

Description

Collect module error log
(intelligent function module)

Set whether to collect module
errors.

Corresponding memory

Select a storage location.

Log No.

Collection No.

300AH

Set the number of collected
errors only when the errors are
stored in the standard RAM.
Set the number of collected
errors in one scan.

Setting range
Selected/deselected
• System memory
• Standard RAM
32 to 1000
• Stored in system
memory: 1 to 100
• Stored in standard
RAM: 1 to 128

Default

Reference

Selected
System memory

40/100

Section 6.32

Note1

Note8.2

Universal

The setting screen differs between GX Works2 and GX Developer. For the setting of the module error log function,
refer to Section 6.32(5)

8-7

8.1 PLC Parameters

Module error log
(Intelligent
function module)

Parameter
No.

(6) Device
Number of points, latch range, and local device range are set for each device.

Figure 8.6 Device

Table8.6 Device setting list
Item

Parameter
No.

Description

Setting range

Default

Reference

• X: 8K
• Y: 8K
• M: 8K

Device points*1

Latch (1) start/end (Latch
clear

valid)*2

Latch (2) start/end (Latch
clear

invalid)*2

Local device start/end*6

•
•
•
•
•

L: 8K*2
B: 8K
F: 2K
SB: 2K
V: 2K

•
•
•
•
•
•
•

S: 8K*3
T: 2K
ST: 0K
C: 1K
D: 12K
W: 8K
SW: 2K

Set the number of device points
that is appropriate to the system.

X (8K), Y (8K), and S (8K)*3 are fixed.
Setting is available within the range of
29K words in total, including the above
fixed points (1.5K words).
• One device: Up to 32K points
• Total bit device points: Up to 64K
points

2001H

Set a latch range (start and end
device numbers), which can be
cleared by remote latch clear
operation.

Setting is available for only one range
for each of B, F, V, T, ST, C, D, and W
devices.

Blank

Section 3.4, 6.3

2002H

Set a latch range (start and end
device numbers), which cannot be
cleared by remote latch clear
operation.

Setting is available for only one range
for each of L, B, F, V, T, ST, C, D, and W
devices.

Blank

Section 3.4, 6.3

2003H

Set a range (start and end device
numbers), which is used for a
local device.

Blank

Section 9.14.2

2000H

Setting is available for only one range
for each of M, V, T, ST, C, D, and Z

Section 9.1

devices.*5

(To the next page)

8-8

CHAPTER8 PARAMETERS

Table8.6 Device setting list (continued)
Parameter
No.

Item

Device points

File register
extended

Latch (1) start/end
(Latch clear valid)

32 bit

Indexing*4

Setting range

Default

Reference

2000H

Set points for the file register
(ZR), extended data register
(D), and extended link register
(W).

Point assignment to the file
register (ZR), extended data
register (D), or extended link
register (W). Assign part of the
points of the file register to the
extended data register and
extended link register.

Blank

Section 9.1,
9.8

2004H

Set a latch range (start and
end device numbers), which
can be cleared by remote latch
clear operation.

Each latch range for the file
register (ZR), extended data
register (D), or extended link
register (W).

Blank

Section 3.4,
6.3

2005H

Set a latch range (start and
end device numbers), which
cannot be cleared by remote
latch clear operation.

Each latch range for the file
register (ZR), extended data
register (D), or extended link
register (W).

Blank

Section 3.4,
6.3

Use Z

QCPU
Programmin
g Manual
(Common
Instructions)

setting*6
Latch (2) start/end
(Latch clear invalid)

Description

2000H

Select Z or ZZ device for 32-bit
indexing.

Z0 to Z18 (when using Z device)

*1: When changing the device points, new setting must not exceed the refresh ranges of network modules or the auto refresh ranges of
intelligent function modules.
If a new device point setting exceeds the corresponding device range, the data may be written to another device or an error may occur.
*2: When a device latch range is set, the scan time increases.

Built-in Ethernet port QCPU, check the versions of the CPU module and GX Developer. (
*6: Not available for the Q00UJCPU.

Appendix 2)

8-9

3
4
5
6
7
8

8.1 PLC Parameters

When latching a device, consider the increase in the scan time. (
Section 10.1.2)
*3: The points for the step relay (S) can be changed to 0 if the serial number (first five digits) of the Universal model QCPU is "10042" or later.
*4: Available only when the serial number (first five digits) of the Universal model QCPU is "10042" or later.
*5: When using the index register as a local device for the Q03UDCPU, Q04UDHCPU, Q06UDHCPU, Q13UDHCPU, Q26UDHCPU, or

(7) Program
File names and execution types (execution conditions) are set for each program when two or more programs are
written to the CPU module.

Figure 8.7 Program

Table8.7 Program setting list
Item

Program setting

Parameter
No.

Description

7000H

When writing two or more programs to
the CPU module, set a file name and
execution type (execution condition) of
each program.
Also, set a fixed scan interval
(execution interval of the fixed scan
execution type program).

Setting range

• Program name
• Execute type (fixed scan
interval when the fixed scan
execution is selected)

Default

Blank

• File usability setting*1

*1: Available for local devices only.
When using the file usability setting, check the versions of the CPU module and GX Developer. (
The setting is not available for the Q00UJCPU.

8 - 10

Appendix 2)

Reference

Section 2.3

CHAPTER8 PARAMETERS

(8) Boot file
Parameters required for a boot from a memory card are set.

2
3
4
5
6
7

Figure 8.8 Boot file

Table8.8 Boot file setting list
Item

Boot option

Parameter
No.

7000H
Boot file setting

Setting range

Select whether to clear the
program memory at the time of
boot.

Selected/deselected

Set the type and data name of
the boot file, and transfer source
drive for boot operation.

Type, "Data name, and Transfer
from (the transfer target drive
(Transfer to) is automatically set
in the program memory.)

Default

Reference

Deselected
Section 5.1.8
Blank

8 - 11

8.1 PLC Parameters

Clear program
memory

Description

(9) SFC
The mode and conditions for starting an SFC program, and the output mode in the case of a block stop are set.

Figure 8.9 SFC

Table8.9 SFC setting list
Item

Parameter
No.

SFC program start mode

8002H

Start conditions

8003H

Output mode when the block
is stopped

8006H

8 - 12

Description

Setting range

Set the mode and conditions for
starring an SFC program, and also
set the output mode in case a
program block is stopped.

Refer to the QCPU (Q Mode)/
QnACPU Programming Manual
(SFC).

Default

Reference

Initial start
Autostart block 0
Turn OFF

CHAPTER8 PARAMETERS

(10)I/O assignment
The mounting status of each module in the system is set.

2
3
4
5
6
7
Figure 8.10 I/O assignment

Table8.10 I/O assignment setting list
Item

Parameter
No.

Base
setting

Setting range

Set the model name of the mounted
module. (Entered at user’s discretion.
Do not use the one for the CPU
module.)

Up to 16 characters

Points

Set the number of points assigned to
each slot.

0, 16, 32, 48, 64, 128, 256, 512, or
1024 points

Start XY

Set the start I/O number of each slot.

0H to FF0H

Base model
name

Set the model name of the main base
unit or extension base unit. (Entered at
user’s discretion. Do not use the one
for the CPU module.)

Up to 16 characters

Power model
name

Set the model name of the power
supply module on the main base unit
or extension base unit. (Entered at
user’s discretion. Do not use the one
for the CPU module.)

Up to 16 characters

Extension
cable

Set the extension cable name.
(Entered at user’s discretion. Do not
use the one for the CPU module.)

Up to 16 characters

Slots

Set the number of slots of the main
base unit or extension base unit.
This setting must be done for all base
units.

2, 3, 5, 8, 10, or 12

0401H

Reference

• CPU No.2 to No.4: No.n/Empty (Set
"CPU (Empty)" for the slot where no
CPU module is mounted.)
• Empty, Input, Hi input, Output,
Intelli., I/O mix, or Interrupt

Model name

0400H

Default

Blank

Section
4.2.2

Blank

Section
4.1.2

(To the next page)

8 - 13

8.1 PLC Parameters

Set the type of the mounted module.

Type

I/O
Assignme
nt

Description

Table8.10 I/O assignment setting list (continued)
Item

Setting range

Default

Reference

Set various switches of an
intelligent function module.

Refer to the manual for the
intelligent function module used.

Blank

Section 6.10

0403H

Set whether to clear or hold the
output in case of a stop error in
the control CPU.

Clear/Hold

Clear

Section 6.8

4004H

Set whether to stop or continue
the operarion of the control
CPU in case of a hardware
failure of the intelligent function
module.

Stop/Continue

Stop

Section 6.9

I/O response
time

0405H

Set a response time for the
input module, high-speed input
module, I/O combined module,
or interrupt module.

Control PLC

0406H

Set the control CPU for the input/
output modules and intelligent
function module.

Error time
output mode

8 - 14

Description

0407H

Switch setting

Detailed
setting

Parameter
No.

H/W error
time PLC
operarion
mode

• Input or I/O mix: 1ms, 5ms,
10ms, 20ms, or 70ms
• Hi input or Interrupt: 0.1ms,
0.2ms, 0.4ms, 0.6ms, or 1ms
No.1, No.2, No.3, or No.4

• Input or I/O mix:
10ms
• Hi input or Interrupt:
0.2ms
No.1

Section 6.7

QCPU User's
Manual (Multiple
CPU System)

CHAPTER8 PARAMETERS

(11) Serial

Note8.3Note1

The transmission speed, sum check, transmission wait time, and RUN write setting for using the serial
communication function of the CPU module are set.

2
3
4
5
6
7

Figure 8.11 Serial

8
Table8.11 Serial setting list
Parameter
No.

Item

Description

Setting range

Default

Select the item when using the
serial communication function.

Selected/deselected

Deselected

Transmission speed

Set a transmission speed for data
communication with the external
device.

9.6kbps, 19.2kbps, 38.4kbps,
57.6kbps, 115.2kbps

19.2kbps

Sum check

Set whether to add a sum check
code to a message sent or
received when using the serial
communication function,
according to the specifications of
the external device.

Selected/deselected

Selected

Transmission wait time

Set a period of waiting time on the
Basic model QCPU side in case
the CPU module cannot receive
data immediately after the
external device sends data.

No waiting time/10ms to
150ms (in increments of
10ms)

No waiting time

RUN write setting

Enable or disable writing of data
from the external device to the
running CPU module.

Selected/deselected

Deselected

100EH

8.1 PLC Parameters

Use serial communication

Reference

Section 6.23

Note1

Note8.3

Universal

When using the serial communication function for the Q02UCPU, check the versions of the CPU module and GX
Developer. (

Appendix 2)

The Q03UDCPU, Q04UDHCPU, Q06UDHCPU, Q10UDHCPU, Q13UDHCPU, Q20UDHCPU, Q26UDHCPU, and
Built-in Ethernet port QCPU do not support the serial communication function.

8 - 15

(12) Acknowledge XY assignment
The parameters set in the I/O assignment, Ethernet/CC IE/MELSECNET setting, and CC-Link setting can be
confirmed.

Figure 8.12 Acknowledge XY assignment

Table8.12 Acknowledge X/Y assignment list
Item

X/Y assignment

8 - 16

Parameter
No.

Description

Setting range

Default

Reference

The data set in the I/O assignment, Ethernet/CC IE/
MELSECNET setting, and CC-Link setting can be
checked.

CHAPTER8 PARAMETERS

(13) Multiple CPU settings

Note8.4Note1

Parameters required for configuring a multiple CPU system are set.

2
3
4
5
6
Figure 8.13 Multiple CPU settings

7
Table8.13 Multiple CPU setting list
Description

0E00H

Set the number of CPU modules used in a multiple
CPU system.

1 to 4

E00CH

Set a CPU number for which the multiple CPU
setting parameters are set. (Set the number of the
connected CPU module.)

PLC No.1 to No.4

Blank

Operating mode

0E01H

Select the multiple CPU system operation to be
performed in case a stop error occurs in any of
CPU No.2 to No.4.
When CPU No.1 results in a stop error, the multiple
CPU system stops. (Fixed)

Selected/
deselected

All items selected

Multiple CPU
synchronous

E00BH

Enable or disable synchronous startup of the CPU
modules on the multiple CPU system.

Mp.1 to No.4

All items selected

No. of PLC
Host CPU
number*1

startup setting

Setting range

Default

Reference

QCPU User's
Manual (Multiple
CPU System)

(To the next page)

Note1

Note8.4

Universal

The Q00UJCPU cannot be used in multiple CPU systems.

8 - 17

8.1 PLC Parameters

Parameter
No.

Item

Table8.13 Multiple CPU setting list (continued)
Item

Online module change*1

I/O sharing when
using Multiple CPUs

Multiple
CPU high
speed
transmiss
ion area
setting*1

Parameter
No.

Description

E006H

Enable or disable the online
module change in the multiple
CPU system. (When enabled,
the CPU module cannot read
the I/O data outside the
specified group.)

Selected/deselected

Deselected

Select whether to read the
input data of the input modules
or intelligent function modules
controlled by another CPU.

Selected/deselected

Deselected

Select whether to read the
output data of the output
modules controlled by another
CPU.

Selected/deselected

Deselected

Simple setting:
0 to 12K (in increments of 1K
points)
Advanced setting:
0 to 16K (in increments of
0.5K points)

3K points

Available devices*2:
X, Y, M, L, B, D, W, R, ZR,
SM, SD, SB, and SW

All CPUs
can read all
inputs
0E04H
All CPUs
can read all
outputs

CPU specific send
range

E008H

Set the size of the multiple
CPU high-speed transmission
area that is assigned to each
CPU module of the multiple
CPU system.

Auto
refresh
setting

E009H
E00AH

Set an area range for data
communication performed with
the auto refresh function in the
user area of the multiple CPU
high-speed transmission area.

Refresh
setting

Setting range

[Set starting devices for each
CPU]
Selected/deselected

Communication area setting
(refresh setting)

E002H
E003H

In the multiple CPU system,
data are transferred by auto
refresh among respective CPU
modules.
Set the devices to be written or
read and their points.

Deselected

[CPU specific send range]
0 to 2048 points (in
increments of 2 points) per
CPU
Up to 8K points (8192 points)
per system
[PLC side device]
B, M, Y, D, W, R, or ZR
Occupies the device of the
points set for the send range
and starting from the
specified device number.
• One point in the send
range equals 16 points in
B, M, or Y.
• One point in the send
range equals one point in
D, W, R, or ZR.

*1: Not available for the Q00UCPU, Q01UCPU, and Q02UCPU.
*2: SM, SD, SB, and SW are valid only when they are selected as send devices.

8 - 18

Default

Blank

Reference

QQCPU Userís
Manual (Multiple
CPU System)

CHAPTER8 PARAMETERS

(14) Built-in Ethernet port

Note8.5Note1

Parameters required for use of the built-in Ethernet port are set.

2
3
4
5
6
7
Figure 8.14 Built-in Ethernet port

Table8.14 Built-in Ethernet port setting list
Item

Parameter
No.

1016H

Communication
data code

• IP address:
Enter the IP address of the
QnUDE(H)CPU.
• Subnet mask pattern:
Enter the subnet mask pattern
when using a router.
• Default router IP address:
Enter the IP address of the
router.

Select the code for MC protocol
communication.

Setting range
• IP address:
0.0.0.1 to 223.255.255.254
(00000001H to 0DFFFFFFEH)
• Subnet mask pattern:
Blank or
192.0.0.0 to 255.255.255.252
(0C0000000H to 0FFFFFFFCH)
• Default router IP address:
Blank or
0.0.0.1 to 223.255.255.254
(00000001H to 0DFFFFFFEH)
Binary code/ASCII code

Default

• IP address:
192.168.3.39
• Subnet mask
pattern:
Blank
• Default router IP
address:
Blank

Reference

QnUCPU
Userís
Manual(Com
munication via
Built-in
Ethernet Port)

Binary code

(To the next page)

Note1

Note8.5

Universal

The Universal model QCPUs other than the Built-in Ethernet port QCPU are not equipped with any Ethernet port.

8 - 19

8.1 PLC Parameters

IP address

Description

Table8.14 Built-in Ethernet port setting list (continued)
Item

Parameter
No.

Description

Setting range

Open settings

Set data when using MC protocol or
socket communication.

Blank

FTP settings

Set data when using the file transfer
function (FTP).

Blank

Time settings

Set data when using the time
setting function.

Blank

Enable online
change (FTP, MC
protocol)

Enable or disable writing data in
devices or files to the running CPU
module when MC protocol or FTP is
used.

Selected/deselected

Deselected

Disable direct
connection to
MELSOFT

Enable or disable direct connection
to MELSOFT.
To enhance the security with the
remote password setting, check it to
disable it.

Selected/deselected

Deselected

Do not respond to
search for CPU
(Built-in Ethernet
port) on network

Checking this box disables
response to the find CPU function
of the MELSOFT connection.
To enhance the security, check it to
disable this.

Selected/deselected

Deselected

1016H

8 - 20

Default

Reference

QnUCPU
Userís Manual
(Communicati
on via Built-in
Ethernet Port)

CHAPTER8 PARAMETERS

8.2 Network Parameters

This section provides the list of network parameters and describes parameter details.

2
Symbols, M and N, used in the "Parameter No." column
M and N in "Parameter No." in this section denote the following:

• N: Indicates the module number.
• M: Indicates the network type.
Table8.15 For CC-Link IE controller network and MELSECNET/H (
M
1H

Network type

CC IE Control (Control station), MELSECNET/H mode (Control station), MELSECNET/H
Extended mode (Control station), MELSECNET/10 mode (Control station)

Extended mode (Normal station), MELSECNET/10 mode (Normal station)
MELSECNET/H (Remote master)

MELSECNET/H (Standby station)

MELSECNET/H mode multiplexed remote I/O network master station

CC IE Control (Normal station), MELSECNET/H mode (Normal station), MELSECNET/H

(1), (2) in this section)

MELSECNET/H mode multiplexed remote I/O network sub-master station
(when no parameter is set)

MELSECNET/H mode multiplexed remote I/O network sub-master station
(when parameters are set)

(4) in this section)

8.2 Network Parameters

Table8.16 For CC-Link setting (

Network type

Master station

Local station

Standby master station

8 - 21

(1) CC-Link IE controller network setting
Network parameters for the CC-Link IE controller network are set.

Figure 8.15 Setting the number of Ethernet/CC IE/MELSECNET cards (CC-Link IE controller network setting)

Table8.17 CC-Link IE controller network setting list
Item
Number of modules on CC-Link IE
controller network

Parameter No.

Description

Setting range

Default

Reference

A000H

Starting I/O No.
Network No.
Total stations

ANM0H

Station No.
Group No.

0AmnH

Mode

ANM0H

Refresh parameters

ANM1H

Common parameters

ANM2H

Station inherent parameters

ANM3H

Interlink transmission parameters

A002H

Routing parameters

5003H

8 - 22

Set network parameters for
the CC-Link IE controller
network.

Refer to the manual for the
CC-Link IE controller
network.

CHAPTER8 PARAMETERS

(2) MELSECNET/H setting
Network parameters for MELSECNET/H are set.

2
3
4
5
6
7

Figure 8.16 Setting the number of Ethernet/CC IE/MELSECNET cards (MELSECNET/H setting)

Table8.18 MELSECNET/H setting list
Item
Number of modules on MELSECNET/H

Parameter No.

Description

Setting range

Default

Reference

Refer to the manual for the Q
series-compatible
MELSECNET/H.

5000H

Starting I/O No.
5NM0H

Total stations
Group No.

05mnH

Mode

5NM0H

Refresh parameters

5NM1H

Common parameters

5NM2H

Station inherent parameters

5NM3H

Common parameters 2

5NMAH

Station inherent parameters 2
Interrupt settings
Valid module during other station access

Set MELSECNET/H
network parameters.

5NMBH
5001H

Interlink transmission parameters

5002H

Routing parameters

5003H

8 - 23

8.2 Network Parameters

Network No.

(3) Ethernet setting
Network parameters for Ethernet are set.

Figure 8.17 Setting the number of Ethernet/CC IE/MELSECNET cards (Ethernet setting)

Table8.19 Ethernet setting list
Item
Number of modules on Ethernet

Parameter No.

Description

Setting range

Default

Reference

Refer to the manual for the
Q series-compatible
Ethernet.

9000H

Starting I/ONo.
Network No.
Group No.

9N00H

Station No.
Operational settings
Initial settings

9N01H

Open settings

9N02H

Router relay parameter

9N03H

Station No.<->IP information

9N05H

FTP Parameters

9N06H

E-mail settings

9N07H

News setting

9N08H

Interrupt settings

9N09H

Valid module during other station access

5001H

Routing parameter

9N04H

8 - 24

Set Ethernet network
parameters.

CHAPTER8 PARAMETERS

(4) CC-Link setting
Parameters for CC-Link are set.

2
3
4
5
6
7
Figure 8.18 Setting the CC-Link list

Table8.20 CC-Link setting list
Item

Description

Setting range

Default

Reference

Refer to the manual for
CC-Link.

8.2 Network Parameters

Number of modules
Type

Parameter No.
C000H

Start I/O No.
Operational setting

CNM2H

All connect count
Remote input (RX)
Remote output (RY)
Remote register (RWr)
Remote register (RWw)
Ver.2 Remote input (RX)

CNM1H

Ver.2 Remote output (RY)
Ver.2 Remote register (RWr)

Set CC-Link
parameters.

Ver.2 Remote register (RWw)
Special relay (SB)
Special register (SW)
Retry count
Automatic reconnection station count
Standby master station No.
PLC down select

CNM2H

Scan mode setting
Delay information setting
Station information setting
Remote device station initial setting
Interrupt setting

8 - 25

8.3 Remote Password
This section provides the list of parameters for use of remote password and describes parameter details.

Figure 8.19 Remote password settings dialog box

A remote password is set for an Ethernet module, serial communication module, modem interface module,
or Built-in Ethernet port QCPU.

Table8.21 Remote password setting list
Item

Parameter No.

Password settings

Password
active
module
settings

Setting range
Four characters or less
(alphanumeric characters, special
symbols)

Default

Enter a remote password.

Model
name

Select a model name of the module
for which the remote password set
to the CPU module is checked.

Start XY

Set the start address of the module
for which the remote password is
checked.

Set details of the remote password
for the QJ71E71.

Select user connection No.

Connection 1 to Connection 16

Select a valid port of the remote
password for system connection.

Specify a valid port of the remote
password.
• Auto open UDP port
• FTP transmission port (TCP/IP)
• GX Developer transmission port
(TCP/IP)
• GX Developer transmission port
(UDP/IP), Dedicated instruction,
CC IE Control, MNET/10(H) relay
transmission port.
• HTTP port

Detail
User connection No.

System connection

8 - 26

Description

• QnUDE(H)CPU
• QJ71E71
• QJ71C24/CMO
0000H to 0FE0H

Reference

• QnUDE(H)CPU:
QnUCPU User's
Manual
(Communication
via Built-in
Ethernet Port)
• QJ71E71:
Ethernet module
manual
• QJ71C24:
Serial
communication
module manual
• QJ71CMO:
Modem interface
module manual

CHAPTER9 DEVICES

9
2

This chapter describes the devices that can be used in the CPU module.

9.1 Device List
Table 9.1 lists the names and data ranges of the devices that can be used in the CPU module.

Table9.1 Device list
Classification

Type

Bit
device

Internal user
device

Device name
Input

8192

X0 to X1FFF

Hexadecimal

Section 9.2.1

8192

Y0 to Y1FFF

Hexadecimal

Section 9.2.2

Internal relay

8192

M0 to M8191

Decimal

Section 9.2.3

Latch relay

8192

L0 to L8191

Decimal

Section 9.2.4

Annunciator

2048

F0 to F2047

Decimal

Section 9.2.5

Edge relay

2048

V0 to V2047

Decimal

Section 9.2.6

Step relay

8192

S0 to S511/block

Decimal

Link relay

8192

B0 to B1FFF

Hexadecimal

Link special relay

2048

SB0 to SB7FF

Hexadecimal

Timer*1

2048

T0 to T2047

Decimal

(ST0 to ST2047)

Decimal

Link direct
device

Bit
device

Module access
device

Word
device

C0 to C1023

Decimal

Section 9.2.11

D0 to D12287

Decimal

Section 9.2.12

Link register

8192

W0 to W1FFF

Hexadecimal

Section 9.2.13

Link special register

2048

SW0 to SW7FF

Hexadecimal

Section 9.2.14

Function input

FX0 to FXF

Hexadecimal

Section 9.3.1

Function output

FY0 to FYF

Hexadecimal

Section 9.3.1

2048

SM0 to SM2047

Decimal

Word
device

Cannot be changed

Section 9.3.2

FD0 to FD4

Decimal

Section 9.3.1

Special register

2048

SD0 to SD2047

Decimal

Section 9.3.2

Link input

8192

Jn\X0 to Jn\X1FFF

Hexadecimal

Link output

8192

Jn\Y0 to Jn\Y1FFF

Hexadecimal

Link relay

16384

Jn\B0 to Jn\B3FFF

Hexadecimal

512

Jn\SB0 to Jn\SB1FF

Hexadecimal

Link register
Link special register
Intelligent function
module device
Cyclic transmission

Index register or
standard device
register

6
7
8

Section 9.2.10

1024

area device *4
Index register
or standard
device register

Section 9.2.8

12288

Link special relay
Word
device

Section 9.2.7

within 29K words *3

Data register

Function register

Section 9.2.9
Can be changed

Counter *1

Special relay
Word
device

Reference

Cannot be changed

16384

Jn\W0 to Jn\W3FFF

Hexadecimal

512

Jn\SW0 to Jn\SW1FF

Hexadecimal

65536

Un\G0 to Un\G65535*2

Decimal

Cannot be changed

14336

U3En\G10000 to U3En\G24335

Decimal

Can be changed

Z0 to Z19

Decimal

Cannot be changed

Section 9.4

Section 9.5

Section 9.6

(To the next page)

9-1

9.1 Device List

Internal
system device

Bit
device

Parameter-set
range

Range

Output

Retentive timer*1
Word
device

Default
Points

Table9.1 Device list (continued)
Classification
File register *7
Extended data
register *7
Extended link
register *7
Nesting
Pointer

Type

Device name

Parameter-set range

Range

Word
device

File register

Word
device

Extended data register

Word
device

Extended link register

Nesting

Bit device

Pointer
Interrupt pointer
SFC block device
Network No. specification
device

Other

Default
Points

4096

N0 to N14
*8

256

*10

320

*10

P0 to P4095
I0 to I255

255

I/O No. specification
device

Macro instruction
argument device

U0 to UFF, U3E0 to
U3E3E3 *13

Cannot be changed
Cannot be changed

Real number constant

Decimal

Section 9.12.1
Cannot be changed

Hexadecimal

Section 9.12.3
Section 9.12.4
Section 9.13.1

H0 to HFFFFFFFF

Section 9.13.2

1.17549435

38 to E

3.40282347 + 38

Section 9.13.3

Double-precision floating-point data*5:
E

2.2250738585072014
E

Character string constant

Section 9.11
Section 9.12

Single-precision floating-point data:
Constant

Section 9.10

K-2147483648 to K2147483647

Hexadecimal constant

Section 9.9

Decimal

Hexadecimal

VD0 to VD

Section 9.8

Decimal

*12

J1 to J255

Decimal constant

0 to 4086K points
*6

Decimal

*11

BL0 to BL319

Section 9.7

Decimal
*9

Reference

308 to

Section 9.13.3

1.7976931348623157 + 308
"ABC", "123"

Section 9.13.4

*1: For the timer, retentive timer, and counter, a bit device is used for contacts and coils, and a word device is used for a present value.
*2: The number of points that can be actually used varies depending on the intelligent function module.
For the number of buffer memory points, refer to the manual for the intelligent function module used.
*3: Can be changed in the Device tab of the PLC parameter dialog box (except the input, output, and step relay). The points for the step relay
can be changed to 0 if the serial number (first five digits) of the Universal model QCPU is "10042" or later. (
Section 9.2)
*4: Available only in multiple CPU systems.
*5: Up to 15 digits can be entered in GX Developer.
*6: Indicates the total number of points for the file register, extended data register (D), and extended link register (W).
*7: Not available for the Q00UJCPU.
*8: "512 points" for the Q00UJCPU, Q00UCPU, and Q01UCPU.
*9: "P0 to P511" for the Q00UJCPU, Q00UCPU, and Q01UCPU.
*10: "128 points" for the Q00UJCPU, Q00UCPU, and Q01UCPU.
*11: "I0 to I127" for the Q00UJCPU, Q00UCPU, and Q01UCPU.
*12: "BL0 to BL127" for the Q00UJCPU, Q00UCPU, and Q01UCPU.
*13: "U0 to UF" for the Q00UJCPU, "U0 to U3F" or "U3E0 to U3E3E2" for the Q00UCPU and Q01UCPU, and "U0 to U7F" or "U3E0 to
U3E3E2" for the Q02UCPU.

9-2

CHAPTER9 DEVICES

9.2 Internal User Device

(1) Definition

Internal user devices can be used for various user applications.

(2) Points for internal user devices

The default values can be changed in the Device tab of the PLC parameter dialog box.
However, the points for the input (X), output (Y), and step relay (S)

Note9.1 cannot be changed.Note1

4
5
6

Default
Most of the default device
points can be changed.

7
8

Figure 9.1 Device tab of the PLC parameter dialog box

When changing device points, note the following.
• The maximum number of points for a bit device is 32K.
For an internal relay and link relay, the maximum number of points can be set up to 60K.

Note9.2

• Up to 29K words can be set for total internal user devices.
• One point set for the timer, retentive timer, or counter must be regarded as two points (one for coil and one
for contact).

Note1

Note9.1

Universal

The points for the step relay (S) can be changed to 0 if the serial number (first five digits) of the Universal model QCPU
is "10042" or later. (

Note9.2

Section 9.2.9)

Universal

This applies to the Universal model QCPU when the first five digits of the serial No. is "10042" or later.

9-3

9.2 Internal User Device

• Set each device in increments of 16 points.

●

When changing device points, the following refresh ranges must not exceed the corresponding
device ranges.
• Refresh range of network module
• Auto refresh range of intelligent function module
If device points are set exceeding the corresponding device range, data may be written to any other device or an error
may occur.

●

The total number of points for the internal relay, latch relay, annunciator, edge relay, link relay,
link special relay, step relay, timer, retentive timer, and counter must be set within the following
range.
• Serial number (first five digits) of the Universal model QCPU is "10041" or earlier: Up to 64K points
• Serial number (first five digits) of the Universal model QCPU is "10042" or later: Not limited (Up to 29
words for internal user devices)

(3) Memory size
Set the internal user devices so that the following condition is satisfied.

(Bit device size) + (Timer, retentive timer, and counter sizes) + (Word device size)

29K words

(a) Bit device
For bit devices, 16 points are calculated as one word.
(Bit device size) =

(X+Y+M+L+B+F+SB+V+S)
16

Words

(b) Timer (T), retentive timer (ST), and counter (C)
For the timer (T), retentive timer (ST), and counter (C), 16 points are calculated as 18 words.
(Timer, retentive timer, or counter size) =

(T+ST+C)
16

18 Words

(c) Word device
For the data register (D), link register (W), and link special register (SW), 16 points are calculated as
16 words.
(Word device size) =

(D+W+SW)
16

16 Words

If the points for the internal user devices have been changed, the following files created with the
previous parameters can no longer be used.
• Sequence program files
• SFC program files
• ST program files
In such a case, read the above program files out from the CPU module to GX Developer, and then write them back again to
the CPU module.

9-4

CHAPTER9 DEVICES

(4) Device point assignment example
Table9.2 shows a device point assignment example.
Table9.2 uses the same format as the device point assignment sheet shown in Appendix 4.

Table9.2 Device point assignment example
Device name

Symbol

Numeric
notation

Number of device point *2
Points

Restriction check
Size (words)*3

Range

Points (bits)*2

Hexadecimal

8K (8192)

X0000 to X1FFF

/16

512

8192

Output relay*1

Hexadecimal

8K (8192)

Y0000 to Y1FFF

/16

512

8192

Internal relay

Decimal

16K (16384)

M0 to M16383

/16

1024

16384

Latch relay

Decimal

4K (4096)

L0 to L4095

/16

256

4096

Link relay

Hexadecimal

4K (4096)

B0000 to B0FFF

/16

256

4096

Annunciator

Decimal

1K (1024)

F0 to F1023

/16

1024

Link special relay

Hexadecimal

2K (2048)

SB0000 to SB07FF

/16

128

2048

Edge relay

Decimal

1K (1024)

V0 to V1023

/16

1024

Step relay*1

Decimal

8K (8192)

S0 to S8191

/16

512

8192

Timer

Decimal

2K (2048)

T0 to T2047

18
16

2304

4096

Retentive timer

Decimal

2K (2048)

ST0 to ST2047

18
16

2304

4096

Counter

Decimal

1K (1024)

C0 to C1023

18
16

1152

2048

Data register

Decimal

14K (14336)

D0 to D14335

14336

Link register

Hexadecimal

4K (4096)

W0000 to W4095

4096

Link special register

Hexadecimal

2K (2048)

SW0000 to SW07FF

2048

Total

29568
(29696 or less)

63488
(65536 or less)

*1: The points are fixed for the system. (Cannot be changed)
The points for the step relay (S) can be changed to 0 if the Universal model QCPU whose serial number (first five digits) is "10042" or
later.
*2: Up to 32K points can be set for each device.
However, up to 60K points can be set for each device of the internal relay and link relay if the Universal model QCPU whose serial
number (first five digits) is "10042" or later,
*3: Enter the values multiplied (or divided) by the number shown in the Size (words) column.

9-5

4
5
6
7
8

9.2 Internal User Device

Input relay*1

9.2.1 Input (X)
(1) Definition
The input (X) is used to send commands or data to the CPU module from external devices such as push-

button switches, selector switches, limit switches, and digital switches.
Push-button switch

Selector switch

Input (X)
Sequence
operation

Digital switch
1

Figure 9.2 Commands from external devices to a CPU module

(2) Concept of input (X)
One input point is assumed to be a virtual relay Xn in the CPU module.
Programs use the normally open or closed contact of Xn.
Virtual relay
PB1

Programmable
controller

X0
LS2

X1
X1

PB16

XF
XF

Program

Input ladder (external device)

Figure 9.3 Concept of input (X)

(3) Allowable number of normally open or closed contacts
There are no restrictions on the number of normally open or closed contacts of Xn used in a program,
as long as the program capacity is not exceeded.

No restrictions on
the quantity used.

Y21
X0
Figure 9.4 Input (X) used in a program

9-6

Y20
Y21
Y23

CHAPTER9 DEVICES

9
●

When debugging a program, the input (X) can be set to on or off by the following:
• Device test in GX Developer
• OUT Xn instruction

2
OUTX1

ON/OFF command

X1
Figure 9.5 Input (X) on/off with the OUT Xn instruction

4
●

The input (X) can also be used for the following.
• Refresh target device (CPU module side) of RX in CC-Link
• Refresh target device (CPU module side) of CC-Link IE controller network or MELSECNET/H

5
6
7
8

9.2 Internal User Device
9.2.1 Input (X)

9-7

9.2.2 Output (Y)
(1) Definition
The output (Y) is used to output control results on programs to external devices such as signal lamps, digital
displays, electromagnetic switches (contactors), or solenoids.
Data can be output to the outside like using a normally open contact.
Signal lamp

Digital display

Output (Y)
Sequence
operation

Contactor

Figure 9.6 Output from a CPU module to external devices

(2) Allowable number of normally open or closed contacts
There are no restrictions on the number of normally open or closed contacts of Yn used in a program,
as long as the program capacity is not exceeded.
Programmable
logic cont

No restrictions on the quantity used.
Load

X0
Y20

M51

Y20
X1

Y20

X2
Y21

Y20

X3
Y22

Program

Out ladder (external device)

Figure 9.7 Output (Y) used in a program

(3) Using the output (Y) as the internal relay (M)
The output (Y) corresponding to the slots for input modules or empty slots can be utilized as the internal relay (M).
Input module

OUT Yn
Equivalent to
internal relay
Figure 9.8 Using as the internal relay

9-8

CHAPTER9 DEVICES

9.2.3 Internal relay (M)

(1) Definition
The internal relay (M) is a device for auxiliary relays used in the CPU module.

All of the internal relay are set to off in the following cases:
• When the CPU module is powered off and then on

• When the CPU module is reset
• When latch clear is executed (

Section 6.3)

(2) Latch (data retention during power failure)
The internal relay cannot be latched.

No restrictions on the quantity used.
M0 is set to on when X0 turns on from off.

X0
SET

M0
K20
TO

Y20

Internal relay (M0) can be set to on only for
use inside the CPU module, and not for
output to the outside.

8
The on/off information of M0 is output from the
output module to the external device.
9.2 Internal User Device
9.2.3 Internal relay (M)

X1 M0
M100
X2 M0
M2047
Figure 9.9 Internal relay (M) used in a program

(4) Method for external output
The output (Y) is used to output sequence program operation results to external devices.

Use the latch relay (L) when latch (data retention during power failure) is required.
(

Section 9.2.4)

9-9

9.2.4 Latch relay (L)
(1) Definition
The latch relay (L) is a device for auxiliary relays that can be latched inside the CPU module.

Latch relay data are retained by batteries in the CPU module during power failure.
Operation results (on/off information) immediately before the following will be also retained.
• Powering off and then on the CPU module
• Resetting the CPU module

(2) Latch relay clear
The latch relay is turned off by the latch clear operation. (

Section 3.7)

However, the latch relay set in "Latch (2) start/end" in the Device tab of the PLC parameter dialog box

cannot be turned off even by the remote latch clear function.

(3) Allowable number of normally open or closed contacts
There are no restrictions on the number of normally open or closed contacts used in a program, as
long as the program capacity is not exceeded.
No restrictions on the quantity used.
M0 is set to on when L0 turns on from off.
X0
SET

L0
K20
T0

Y20
X1

Latch relay (L0) can be set to on only for
use inside the CPU module, and not for
output to the outside.

The on/off information of L0 is output from the
output module to the external device.

L0
L100

L0
L2047
Figure 9.10 Latch relay

Scan time is prolonged when the latch relay (L) is used. Reducing the points of latch relay (L) can reduce the prolonging
scan time. (

Section 10.1.2)

(4) Method for external output
The output (Y) is used to output sequence program operation results to external devices.

9 - 10

●

If latch is not required, use the internal relay (M). (

●

The latch clear invalid area is set in the Device setting of PLC parameter. (

Section 9.2.3)
Section 6.3)

CHAPTER9 DEVICES

9.2.5 Annunciator (F)

(1) Definition
The annunciator (F) is an internal relay which can be effectively used in fault detection programs for user-created
system.

(2) Special relay and special register after annunciator ON
When the annunciator is turned on, the special relay (SM62) is set to on, and the numbers and

2
3

quantity of the annunciator numbers are stored in the special register (SD62 to SD79).
• Special relay

: SM62

• • • Turns on even if only one of the annunciator number areas
is turned on.

• Special register

: SD62

• • • Stores the number of the annunciator that was turned on
first.

SD63

• • • Stores the quantity of the annunciator number areas that are

on.
SD64 to • • • Stores annunciator numbers in the order of turning on.
SD79

(The same annunciator number is stored in SD62 and

SD64.)

The annunciator number stored in SD62 is also registered in the error history area.

(3) Applications of the annunciator
Using the annunciator in a fault detection program allows check for a system fault and identification of

the fault (annunciator number) by monitoring the special register (SD62 to SD79) when the special
relay (SM62) turns on.

to the outside.
[Fault detection program]
X0

X10
SET F5

SM62
BCDP SD62 K4Y20
Outputs No. of the
annunciator that turned on.

SM62

OFF

SD62
SD63
SD64
SD65

0
0
0

SD79

ON
5
1
5

0
0

Annunciator ON detection
Figure 9.11 Detecting and saving the annunciator ON

(4) Allowable number of normally open or closed contacts
There are no restrictions on the number of normally open or closed contacts used in a program, as
long as the program capacity is not exceeded.

9 - 11

9.2 Internal User Device
9.2.5 Annunciator (F)

Example In this program, when annunciator (F5) is turned on, the corresponding annunciator number is output

(5) Turning on the annunciator and processing
(a) Turning on the annunciator
The following instructions can be used.

1) SET F

instruction
instruction can be used to turn on the annunciator only on the leading edge (off to on)

The SET F

of an input condition.
Even if the input condition turns off, the annunciator is held on.
Using many annunciator numbers can shorten scan time more than using the OUT F

2) OUT F

instruction.

instruction

The OUT F

instruction can be also used to turn on or off the annunciator. However, since the

processing is performed for every scan, the scan time is longer than the case of using the SET F
instruction.
In addition, execution of the RST F , LEDR, or BKRST instruction is required after the annunciator is turned
off with the OUT F

instruction.

Therefore, use of the SET F

instruction is recommended.

If the annunciator is turned on with any instruction other than SET F and OUT F (for example, the MOV instruction), the
same operation as the internal relay (M) is performed.
The ON information is not stored in SM62, and annunciator numbers are not stored in SD62 and SD64 to SD79.

(b) Processing after annunciator on
1) Data stored in the special register (SD62 to SD79)
• Turned-on annunciator numbers are stored in SD64 to SD79 in order.
• The annunciator number in SD64 is stored in SD62.
• SD63 value is incremented by "1".
SET F50

SET F25 SET F1023

SD62

SD63

3
50

SD64

SD65

SD66

1023

SD67

SD79

Up to 16 annunciator
numbers can be stored.

Figure 9.12 Processing after annunciator ON

2) Processing on the CPU
The USER LED on the front side turns on (red).

3) On/off setting for the LED
Whether to turn on the USER.LED or not when the annunciator is turned on can be set in the LED indication
setting. (

9 - 12

Section 6.21.2).

CHAPTER9 DEVICES

(6) Turning off the annunciator and processing
(a) Turning off the annunciator

The following instructions can be used.

1) RST F

instruction

This is used to turn off the annunciator number that was turned on with the SET F

instruction.

2) LEDR instruction
This is used to turn off the annunciator number stored in SD62 and SD64.

3) BKRST instruction
This is used to turn off all of the annunciator numbers within the specified range.

4) OUT F

instruction

One annunciator number can be turned on or off with the same instruction.
However, even if an annunciator number is turned off with the OUT F

instruction, the off processing

described in (6)(b) in this section is not performed.
If the annunciator is turned off with the OUT F

instruction, execution of the RST F , LEDR, or BKRST

instruction is required.

• Turning off annunciator 5 (F5)

Fault detection program
(Annunciator ON program)
Display reset input
RST F5

Program that turns OFF
9.2 Internal User Device
9.2.5 Annunciator (F)

• Turning off all of the turned-on annunciator numbers
Fault detection program
(Annunciator ON program)
Display reset input
BKRSTP F0 K10

Program that turns
off F0 to F9.

Figure 9.13 Example of turning off the annunciator

Remark
For details of each instruction, refer to the following.
QCPU Programming Manual (Common Instructions)

9 - 13

(b) Processing after annunciator off
1) Data stored in the special register (SD62 to SD79) after execution of the LEDR instruction
• The annunciator number in SD64 is deleted, and the other annunciator numbers in the
register addressed SD65 and after are shifted accordingly.
• The annunciator number in SD64 is stored into SD62.
• SD63 value is decremented by "1".
• If the SD63 value is changed to "0", SM62 is turned off.
SET F50

SET F25 SET F1023

LEDR

SD62

SD63

SD64

SD65

1023

SD66

1023

SD67

SD79
0
0
0
0
0
Figure 9.14 Processing after annunciator OFF (when the LEDR instruction executed)

2) Data stored in the special register (SD62 to SD79) when the annunciator is turned off with
the RST F

or BKRST instruction

• The annunciator number specified with the RST or BKRST instruction is deleted, and the
other annunciator numbers in the register addressed SD65 and after are shifted accordingly.
• If the existing annunciator number in SD64 is turned off, a new annunciator number stored in SD64 will
be stored in SD62.
• SD63 value is decremented by "1".
• If the SD63 value is changed to "0", SM62 is turned off.
SET F50

SET F25 SET F1023 RST F25

SD62

SD63

SD64

SD65

1023

SD66

1023

SD67

SD79

Figure 9.15 Processing after annunciator OFF (when the REST F

instruction is executed)

3) LED indication
When all of the annunciator numbers in SD64 to SD79 turn off, the LED that was turned on by
turn-on of the annunciator will turn off. (

(5)(b) in this section)

If the LEDR instruction is executed while the annunciator is on and at the same time the operation continuation error that has
higher priority (
Section 6.21.1) than the annunciator has occurred, the LEDR instruction clears the higher priority
error. Because of this, the annunciator is not turned off by execution of the LEDR instruction.
To turn off the annunciator with the LEDR instruction, remove the error whose priority is higher than that of the annunciator.

9 - 14

CHAPTER9 DEVICES

9.2.6 Edge relay (V)

(1) Definition
The edge relay (V) is a device in which the on/off information from the beginning of the ladder block.
Contacts only can be used. (Coils cannot be used).
X0

X10

2
3

Stores on/off information of
X0, X1, and X10.

Figure 9.16 Edge relay

(2) Applications of the edge relay
The edge relay can be utilized to detect the leading edge (off to on) in programs configured using

index modification.

[Ladder example]
SM400
MOV KO Z1

Clears index register (Z1).

FOR K10

Specifies the number of repeats (10 times).

X0Z1*1 V0Z1*1

Turns on M0Z1 1 scan,
followed by rise of X0Z1.

M0Z1
SM400

Increments index
register (Z1). (+1)

INC Z1
NEXT

Returns to FOR instruction.

9.2 Internal User Device
9.2.6 Edge relay (V)

*1: The on/off information for X0Z1 is stored in the V0Z1 edge relay.
For example, the on/off information of X0 is stored in V0, and that of X1 is stored in V1.

[Timing chart]
ON
X0 OFF
ON
When Z1=0

V0 OFF
ON
M0 OFF
1 scan
ON
X1 OFF
ON

When Z1=1

V1 OFF

Turns on for 1 scan by rise of X1.

ON
M1 OFF
1 scan
Figure 9.17 Application example and timing chart of the edge relay

(3) Precautions
The edge relay of the same number cannot be set only once in a program.

9 - 15

9.2.7 Link relay (B)
(1) Definition
The link relay (B) is a relay on the CPU module side, and it is used for refreshing the link relay (LB) data of

another module such as a MELECNET/H network module to the CPU module or refreshing the CPU
module data to the link relay (LB) of the MELECNET/H network module.
CPU module

MELSECNET/H network module

Link relay

LB0
Link refresh
setting range

Link refresh

Figure 9.18 Link refresh

(2) Allowable number of normally open or closed contacts
There are no restrictions on the number of normally open or closed contacts used in a program, as
long as the program capacity is not exceeded.
No restrictions on the quantity used.
B0 is set to on when X0 turns on from off.
X0
SET B0
K20
T0

Y20
X1

Link relay (B0) can be set to on only for use inside
the CPU module, and not for output to the
outside.

The on/off information of B0 is output from the
output module to the external device.

B0
B100

B0
B1FFF
Figure 9.19 Link relay

9 - 16

CHAPTER9 DEVICES

(3) Using the link relay in the network system
Network parameters must be set.
The link relay range areas that is not set by network parameters (not used for a network system such as a
MELSECNET/H network) can be used as the internal relay or latch relay.

• Link relay range where no latch is performed••••••Internal relay
• Link relay range where latch is performed••••••••••Latch relay

• Although the points for the link relay in a CC-Link IE controller network module is 32768, the default for the link
relay in the CPU module is 8192 points.
• Although the points for the link relay in a MELSECNET/H network module is 16384, the default for the link relay in
the CPU module is 8192 points.
To use the link relay exceeding the above points, change the link relay points in the Device tab of the PLC parameter dialog
box.

4
5
6
7

Remark
For network parameters, refer to the following.
Reference manual for each network module

9.2 Internal User Device
9.2.7 Link relay (B)

9 - 17

9.2.8 Link special relay (SB)
(1) Definition
The Link special relay (SB) is a relay that indicates various communication status and detected errors of
intelligent function modules such as CC-Link IE controller modules or MELSECNET/H network modules.
Each of this device area is turned on or off according to a factor occurred during data link.
The communication status and errors on the network can be confirmed by monitoring the link special relay (SB).

(2) Number of link special relay points
The points for the link special relay in the CPU module is 2048. (SB0 to SB7FF).
However, the points can be changed in the Device tab of the PLC parameter dialog box. (

Section 9.1)

To an intelligent function module that has a link special relay, such as a CC-Link IE controller module or
MELSECNET/H network module, 512 points are assigned.
Assigning the link special relay as shown in Figure 9.20 allows refresh of the CC-Link link special relay (SB) to the
link special relay (SB) of the CPU module.
Link special relay
SB0
For 1st network module

512
points

For 2nd network module

512
points

For 3rd network module

512
points

For 4th network module

512
points

For 1st CC-Link module

512
points

SB1FF
SB200
SB3FF
SB400
SB5FF
SB600
SB7FF
SB800
SB9FF

2560
points

Figure 9.20 Points of the link special relay

Remark
For details of the link special relay, refer to the manual for an intelligent function module that has the link special relay.

9 - 18

CHAPTER9 DEVICES

9.2.9 Step relay (S)

This device is provided for SFC programs.

2
Because the step relay is a device exclusively used for SFC programs, it cannot be used as an internal relay in the sequence
program.
If used, an SFC error will occur, and the system may go down.

3
4

Remark

For use of the step relay, refer to the following.
QCPU (Q Mode)/QnACPU Programming Manual (SFC)

6
7
8

9.2 Internal User Device
9.2.9 Step relay (S)

9 - 19

9.2.10 Timer (T)
(1) Definition
Time counting starts when a coil is turned on, and it times out and the contact turns on when the
current value reaches the set value.
The timer is of an incremental type.

(2) Timer types
Timers are mainly classified into the following two types.
1) Timer of which value is set to 0 when the coil is turned off.
2) Retentive timer that holds the current value even if the coil is turned off.
Also, low-speed and high-speed timers are included in timer 1), and low-speed and high-speed retentive timers
are included in timer 2).
Timer

Timer

Low-speed timer
High-speed timer

Retentive
timer

Low-speed retentive timer
High-speed retentive timer

Figure 9.21 Timer types

(3) Specification of the timer
The same device is used for the low- and high-speed timers, and the type is determined according to the
instruction used.

Example For the OUT T0 instruction, the low-speed timer is specified, and for the OUTH T0 instruction, the
high-speed timer is specified.
The same device is used for the low- and high-speed retentive timers, and the type is determined according to the
instruction used.

Example For the OUT ST0 instruction, the low-speed retentive timer is specified, and for the OUTH ST0
instruction, the high-speed retentive timer is specified.

9 - 20

CHAPTER9 DEVICES

(4) Low-speed timer
(a) Definition

This type of timer measures time in increments of 1 to 1000ms.

The timer starts time measurement when its coil is turned on, and when it times out, the contact is
turned on. If the timer's coil is turned off, the current value is changed to "0" and the contact is
turned off.
[Ladder example]
X0

K10
T0

When X0 is turned on, coil of T0 is turned on, and the
contact turns on after 1s. (when unit of the timer is set
to 100ms)

[Timing chart]
ON
X0

OFF

T0 coil

OFF

6
1s
ON

T0 contact

OFF
Figure 9.22 Ladder example and timing chart of a low-speed timer

(b) time increment setting

The time increment is set in the PLC system tab of the PLC parameter dialog box.
The default is 100ms, and it can be changed in increments of 1ms.

(a) Definition
This type of timer measures time in increments of 0.01 to 100ms.

High-speed timer indication
H
K50
T200

When X0 is turned on, coil of T200 is turned on, and the
contact turns on after 0.5s. (when unit of the timer is set
to 10ms)

[Timing chart]
ON
X0

OFF

T200 coil

OFF

ON
0.5s
T200 contact

ON
OFF
Figure 9.23 Ladder example and timing chart of a high-speed timer

(b) Time increment setting
The time increment is set in the PLC system tab of the PLC parameter dialog box.
The default is 10.0ms, and it can be changed in increments of 0.01ms.

9 - 21

9.2 Internal User Device
9.2.10 Timer (T)

(5) High-speed timer

(6) Retentive timer
(a) Definition
This timer measures the period of time during which the coil is on.

The timer starts time measurement when its coil is turned on, and when it times out, the contact is
turned on. Even if the timer's coil is turned off, the current value and the on/off status of the contact
are retained.
When the coil is turned on again, the measurement restarts from the retained current value.

(b) Retentive timer clear
The current value and the contact off status can be cleared with the RST ST
[Ladder example]
X0

K200
ST0

instruction.

X0 ON time is measured for 20s when unit of
the timer is 100ms.
Retentive timer

X1
RST ST0

When X1 is turned on, ST0 contact is reset
and the current value is cleared.

[Timing chart]
ON
X0

OFF

ST0 coil

OFF

ON
15s
Current value
of ST0
Contact of
ST0

5s
150

151 to 200

Current value is held even
if the coil is turned off.

OFF
Contact remains on even if the coil is turned off.

Instruction execution

RST ST0
instruction
ON
X1

OFF
Figure 9.24 Ladder example and timing chart of a retentive timer

(c) Time increment setting
The time increment is set in the same manner as the corresponding low- or high-speed timer.
• Low-speed retentive timer: Low-speed timer
• High-speed retentive timer: High-speed timer

To use a retentive timer, set the points for it in the Device tab of the PLC parameter dialog box.

9 - 22

CHAPTER9 DEVICES

(7) Timer processing and accuracy
(a) Processing
When the OUT T

or OUT ST

instruction is executed, the on/off switching of the timer coil, current

value update, and on/off switching of the contact are performed.
In the END processing, the current timer value is not updated and the contact is not turned on/off.

[Ladder example]
K10
T0

[Processing at execution of OUT T0 instruction]
Sequence
program

END

OUT TO

END

Processing
Coil ON/OFF
Current value update
Contact ON/OFF

Figure 9.25 Processing at execution of the OUT T0 instruction

7
8

9.2 Internal User Device
9.2.10 Timer (T)

9 - 23

(b) Accuracy
The value obtained by the END instruction is added to the current value when the OUT T
ST

or OUT

instruction is executed.

The current value is not updated while the timer coil is off even if the OUT T

or OUT ST

instruction is

executed.
[Ladder example]
H
K8
TO

[Current value update timing]
OUT T0

OUT T0

END
processing

OUT T0

END
processing

Program
ON
External input

OFF

X0 of CPU module

OFF

Coil of T0

OFF

ON
Contact of T0

OFF
1

10ms counting

Count at execution of
the END instruction
Current value

0+2=2

2+3=5

5+2=7

7+3=10

Accuracy from when the coil of the timer turns on until
when the contact of the timer turns on
- (1 scan time + timer limit setting) to (1 scan time)
Timing when the coil of the timer turns on
Input reading timing
Figure 9.26 Timer accuracy (in the case of 10ms)

Accuracy of the timer response that is from reading input (X) to output the data is up to "2-scan time
+ timer limit setting".

9 - 24

CHAPTER9 DEVICES

(8) Precautions for using timers
(a) Use of the same timer
Do not use the OUT T

instruction that describes the same timer more than once within one scan.

If this occurs, the current timer value will be updated by each OUT T

instruction execution, resulting in

incorrect time measurement.

END

OUT
T

3
OUT
T

OUT
T
END

OUT
T

Sequence
program

Current value is updated.
1 scan

Figure 9.27 When the same timer is used

(b) When the timer is not executed in every scan
While a coil of a timer (for example. T1) is on, do not make the OUT T1 instruction jumped to any other
part with another instruction such as CJ.
If jump of the OUT T

instruction has occurred, the current timer value is not updated.

Also, if a timer exists in a subroutine program, execute a subroutine call including the OUT T1

instruction once in each scan while the coil of the timer (for example, T1) is on.

Failure to do so will not update the current timer value.

(c) Programs that cannot use timers
Timers cannot be used in interrupt programs and fixed scan execution programs.
(d) When the set value is 0
instruction is executed.

(e) When the set value is 1
When the timer limit setting value is greater than the scan time value, the count value of the timer
becomes 1 at execution of the END instruction in a scan where the count value reaches to the timer
limit setting value.
When the coil of the timer turns on in the scan next to the one where the count value becomes 1, the current
timer value becomes 1. In this case, the timer times up in the step and the contact turns on.
If the contact of the timer (setting value = 1) turns on in a short time, change the timer with small timer limit
setting value and set a greater value to the contact.
Scan time
END

K1
T0

X0
END

END

Timer counting
Timer limit setting value
Count at execution
of the END instruction

Current timer value

1
ON

OFF

Coil of T0

OFF

Contact of T0

OFF

ON
ON

Figure 9.28 Operation when the set value is 1

9 - 25

9.2 Internal User Device
9.2.10 Timer (T)

The contact turns on when the OUT T

(f) When the set value is changed after time-out
Even if the set value is changed to a larger value after time-out of the timer, the timer remains timedout and does not start the operation.
(g) When using multiple timers
When using multiple timers to update the respective current values at execution of each OUT T
pay attention to the ladder sequence.
For example, to create an on/off ladder using two timers, refer to examples shown in Figure 9.29.
[Correct ladder example]
Coil of T1 is turned on one scan after T0 is turned on.
T0

K10
T1

Measures for one second after T0 is turned on.

K10
T0

Measures for one second when T1 is off.

T0
M0

OUT T1
OUT T0

Alternates on and off every second.

OUT T1
OUT T0

END processing

OUT T1
OUT T0

END
processing

END processing

OUT T1
OUT T0

END processing

OUT T1
OUT T0

END
processing

END processing

ON
Coil of T0

OFF

OFF
ON

Contact
of T0
Current
value of T0

OFF
0

One second
Coil of T1

OFF

OFF
ON

OFF
Contact
of T1
Current
value of T1

OFF
0

One second

[Incorrect ladder example]
Coil of T1 is turned on within the same scan in which T0 was turned on.
T1

K10
T0

Measures for one second when T1 is off.

K10
T1

Measures for one second after T0 is turned on.

T0
M0

Alternates on and off every second.

OUT T0
OUT T1

END processing

OUT T0
OUT T1

END processing

OUT T0
OUT T1

END
processing

END processing

ON
Coil of T0

OFF

OFF
ON

Contact
of T0
Current
value of T0

OFF
0

One second
Coil of T1

OFF

OFF
ON

Contact
OFF
of T1
Current
value of T1

OFF
0

900ms
Because the current value is updated in the scan where
T0 is timed out, the count starts from 1 or larger value.

Figure 9.29 On/off ladder using two timers

9 - 26

instruction,

CHAPTER9 DEVICES

9.2.11 Counter (C)

(1) Definition
The counter (C) is a device that counts the number of rises for input conditions in sequence programs.
When the count value matches the set value, the counting stops and its contact is turned on.

The counter is of an incremental type.

(2) Counter types
Counters are mainly classified into the following two types.

• Counter that counts the number of rises for input conditions in sequence programs
• Interrupt counter that counts the number of interrupts occurred

(3) Counting
(a) When the OUT C

instruction is executed

The coil of the counter is turned on/off, the current value is updated (the count value + 1), and the contact is
turned on.

In the END processing, the current counter value is not updated and the contact is not turned on.
[Ladder example]
X0

K10
C0

[Processing at OUT C0 Instruction (X0: OFF to ON)]
Sequence
program

END

OUT C0

END

Figure 9.30 Execution and processing of the OUT C

instruction

(b) Current value update (count value + 1)
The current value is updated (count value + 1) at the leading edge (OFF

ON) of the OUT C

instruction.
The current value is not updated while the coil is off, or when it remains on or turns off from on by the OUT C
instruction.
[Ladder example]
X0

K10
C0

[Current value update timing]
END

Sequence
program

OUT C0

END

OUT C0

END

OUT C0

ON
X0

OFF

Coil C0

OFF

Current value
update

Figure 9.31 Current value update timing

9 - 27

9.2 Internal User Device
9.2.11 Counter (C)

Processing
Coil ON/OFF
Current value update
Contact ON

instruction is turned off.

To clear the current value and to turn off the contact of the counter, use the RST C
At the time of execution of the RST C

instruction.

instruction, the counter value is cleared, and the contact is also turned

off.
[Ladder example]
X0
RST C0
[Counter reset timing]
END

Sequence
program

RST C0

END

RST C0

END

RST C0

ON
X0

OFF
Execution

RST C0
OFF
instruction
Count value cleared,
the contact turned off
Figure 9.32 Resetting the counter

9 - 28

Count value cleared,
the contact turned off

CHAPTER9 DEVICES

1) Precautions for resetting the counter
Execution of the RST C

instruction also turns off the coil of C .

If the execution condition for the OUT C
instruction, turn on the coil of C

instruction is still ON after execution of the RST C

at execution of the OUT C

instruction and update the current

value (count value + 1).
[Ladder example]
M0

K10
C0

C0
RST C0
Figure 9.33 Counter resetting ladder example

In the above ladder example, when M0 turns on from off, the coil of C0 turns on, updating the
current value.
When C0 reaches the preset value finally, the contact of C0 turns on, and execution of the RST C0

instruction clears the current value of C0. At this time, the coil of C0 also turns off.
If M0 is still on in the next scan, the current value is updated since the coil of C0 turns on from off
at execution of the OUT C0 instruction. (The current value is changed to 1.)
END

Sequence
program

OUT C0 RST C0 END

7
8

ON
M0

OFF

9.2 Internal User Device
9.2.11 Counter (C)

Coil of C0 OFF

RST C0

OFF

Current value
update, turning on
the contact

Current value is
updated since the coil
of C0 turns on from off.

Turning off the
coil of C0

Count value cleared, the contact turned off
Figure 9.34 Current value update timing

To prevent the above, it is recommended to add a normally closed contact of the OUT C0
instruction execution to the condition for the RST C0 instruction execution so that the coil of C0
does not turn off while the execution condition (M0) of the OUT C0 instruction is on.
[Modified ladder example]
K10
C0

M0
RST C0

Figure 9.35 Counter resetting ladder example (recommended)

9 - 29

(d) Maximum counting speed
The counter can count only when the on/off time of the input condition is longer than the execution interval of
the corresponding OUT C

instruction.

The maximum counting speed is calculated by the following expression:
n
Maximum counting
=
speed (Cmax)
100

1
[times/s]
T

n: Duty (%) *1
T: Execution interval of the OUT C

instruction (sec)

*1: Duty (n) is the ON-OFF time ratio of count input signal, and is expressed as a percentage
value.

T2
T1+T2
T1
When T1 < T2, n =
T1+T2
When T1

T2, n =

100%
100%

ON
Count input signal OFF
Figure 9.36 Duty ratio

The maximum counting speed can be increased by placing multiple counters within one scan.
At this time, use the direct access input (DX

END

OUT
C

)(

OUT
C

Section 3.8.2) for the counter input signal.

OUT
C END

OUT
C

Sequence
program
Execution interval of the
OUT C instruction
Figure 9.37 Ladder example for increasing the maximum counting speed

(4) Precautions
(a) When counting processing is suspended
If an interrupt occurs during execution of the processing shown below, counting is suspended until the
execution of each processing is completed.
• Each instruction on the sequence program
• Interrupt program
• Fixed scan execution type program
Upon completion of the processing, the counting restarts.
However, if the same interrupt occurs again during each processing, these interrupts are counted as once.

9 - 30

CHAPTER9 DEVICES

9.2.12 Data register (D)

(1) Definition
The data register (D) is a memory in which numeric data (-32768 to 32767, or 0000H to FFFFH) can be
stored.

(2) Bit structure of the data register

2
3

(a) Bit structure and read/write unit
One point of the data register consists of 16 bits, and data can be read or written in units of 16 bits.
to

b15

Most significant bit represents a sign bit.
Figure 9.38 Bit structure of the data register

6
Data register data are handled as signed data.
In the case of the hexadecimal notation, 0000H to FFFFH can be stored. However, because the most significant bit
represents a sign bit, decimal values that can be specified are -32768 to 32767.

(b) When using a 32-bit instruction for the data register
For a 32-bit instruction, two consecutive points of the data register (Dn and Dn+1) are the target of the

7
8

processing.

The lower 16 bits correspond to the data register number (Dn) specified in the sequence program,

Example When D12 is specified in the DMOV instruction, D12 represents the lower 16 bits and D13
represents the higher 16 bits.

DMOV K500000 D12
Processing target: D12, D13
D13

D12

Upper 16 bits Lower 16 bits
Figure 9.39 Data transfer with a 32-bit instruction and storage location

Data of -2147483648 to 2147483647 or 0H to FFFFFFFFH can be stored in a two-point area of the data
register. (The most significant bit in a 32-bit structure is a sign bit.)

(3) Retention of stored data
The data stored in the data register are held until other different data are stored.
Note that the stored data are initialized when the CPU module is powered off or reset.

9 - 31

9.2 Internal User Device
9.2.12 Data register (D)

and the higher 16 bits correspond to the specified data register number + 1.

9.2.13 Link register (W)
(1) Definition
The link register (W) is a memory in the CPU module, which is refreshed with link register (LW) data of an
intelligent function module such as a MELSECNET/H network module.
CPU module

MELSECNET/H network module

Link register

LW0
Link refresh

Link refresh

Figure 9.40 Link refresh

In the link register, numeric data (-32768 to 32767, or 0000H to FFFFH) are stored.

(2) Bit structure of the link register
(a) Bit structure and read/write unit
One point of the link register consists of 16 bits, and data can be read or written in units of 16 bits.
to

b15

Wn
setting range
Figure 9.41 Bit structure of the link register

9 - 32

●

Link register data are handled as signed data.
In the case of the hexadecimal notation, 0000H to FFFFH can be stored. However, because the most significant bit
represents a sign bit, decimal values that can be specified are -32768 to 32767.

●

The area range in the link register, which is not used for a MELSECNET/H network module, can be used as a data
register.

CHAPTER9 DEVICES

(b) When using a 32-bit instruction for the link register
For a 32-bit instruction, two consecutive points of the data register (Wn and Wn+1) are the target of the

processing.
The lower 16 bits correspond to the link register number (Wn) specified in the sequence program, and the
higher 16 bits correspond to the specified link register number + 1.

Example When W12 is specified in the DMOV instruction, W12 represents the lower 16 bits and D13
represents the higher 16 bits.

DMOV K500000 W12

2
3
4

Processing target: W12, W13
W13

W12

Upper 16 bits Lower 16 bits
Figure 9.42 Data transfer with a 32-bit instruction and storage location

Data of -2147483648 to 2147483647 or 0H to FFFFFFFFH can be stored in a two-point area of the link register.

(The most significant bit in a 32-bit structure is a sign bit.)

(3) Retention of stored data
The data stored in the link register are held until other different data are stored.

Note that the stored data are initialized when the CPU module is powered off or reset.

To use the link register exceeding the above points, change the link register points in the Device tab of the PLC parameter
dialog box in GX Developer or use a file register.

(4) Using the link register in a network system
Network parameters must be set.
The area range that is not set by network parameters can be used as a data register.

Remark
For the network parameters, refer to the following.
Reference manual for each network module

9 - 33

9.2 Internal User Device
9.2.13 Link register (W)

• Although the number of points for the link register in a CC-Link IE controller network module is 131072 points, the
default value for the link register in the CPU module is 8192 points.
• Although the number of points for the link register of a MELSECNET/H network module is 16384 points, the
default value for the link register in the CPU module is 8192 points.

9.2.14 Link special register (SW)
(1) Definition
The link special register (SW) is used to store communication status data and error data of intelligent function
modules, such as CC-Link IE controller network modules and MELSECNET/H network modules.
Because the data link information is stored as numeric data, error locations and causes can be checked by
monitoring the link special register.

(2) Number of link special register points
The points for the link special register in the CPU module are 2048 (SW0 to SW7FF).
However, the number of points can be changed in the Device tab of the PLC parameter dialog box.
(

Section 9.1)

The points for an intelligent function module such as a CC-Link IE controller network module or a MELSECNET/H
network module are 512.
By assigning it as shown in Figure 9.43, data of the link special register (SW) in a CC-Link module can be also
refreshed to the link special register (SW) in the CPU module.
Link special register
SW0
For 1st network module

512
points

For 2nd network module

512
points

For 3rd network module

512
points

For 4th network module

512
points

For 1st CC-Link module

512
points

SW1FF
SW200
SW3FF
SW400
SW5FF
SW600
SW7FF
SW800
SW9FF

2560
points

Figure 9.43 Points of the link special register

Remark
For details of the link special register, refer to the manual for each intelligent function module that has the link special
register.

9 - 34

CHAPTER9 DEVICES

9.3 Internal System Devices

Internal system devices are provided for system operations.

The allocations and sizes of internal system devices are fixed, and cannot be changed by the user.

9.3.1 Function devices (FX, FY, FD)

(1) Definition
Function devices are used in subroutine programs with argument passing.
Data are read or written between such subroutine programs and calling programs, using function devices.

Example When FX0, FY1, and FD2 are used in a subroutine program, and if X0, M0, and D0 are specified with
a subroutine program call instruction, on/off data of X0 and FY1 are passed to FX0 and M0 respectively, and

4
5

D0 data are passed to FD2.

[Subroutine program]

[Calling program]

FX0

X0
CALL P0 X0 M0 D0

MOV FD2 R0

SET FY1
RET

Figure 9.44 Application example of function devices

(2) Applications of function devices
the same subroutine program can be used without considering other calling programs.

(3) Types of function devices
The following three types of function devices are available.
• Function input (FX)
• Function output (FY)
• Function register (FD)

(a) Function input (FX)
• The function input is used to pass on/off data to a subroutine program.
• Bit data specified by a subroutine call instruction with argument passing are fetched into a subroutine
program and they are used for operations.
• All bit devices for the CPU module can be used.

9 - 35

9.3 Internal System Devices
9.3.1 Function devices (FX, FY, FD)

Because a device in each calling program can be determined by using a function device for subroutine programs,

(b) Function output (FY)
• The function output is used for passing an operation result (on/off data) in a subroutine program to a
calling program.
• An operation result is stored in the device specified in the subroutine program with argument passing.
• All bit devices except for input devices of the CPU module (X and DX) can be used.

(c) Function register (FD)
• The function register is used for data writing or reading between a subroutine program and a calling
program.
• The CPU module auto-detects the input or output conditions of the function register.
Source data are input data of the subroutine program.
Destination data are output data from the subroutine program.
• The function register of one point can occupy up to four words.
Note that, however, the number of words used differs depending on the instruction in the subroutine
program.
1) A one-word instruction uses one word only.
CALLP P0 D0

MOV R0 FD0

P0
Data is stored in D0 (1 point).

Figure 9.45 When the function register of one point occupies one word

2) two-word instruction uses two words.
CALLP P0 D0

DMOV R0 FD0

Data are stored in D0 and D1 (2 points).
Figure 9.46 When the function register of one point occupies two words

3) At a destination using 32-bit multiplication or division, four words are used.
CALLP P0 D0

D* R0 R10 FD0

Data are stored in D0 to D3 (4 points).
Figure 9.47 When the function register of one point occupies four words

• Word devices of the CPU module can be used.

9 - 36

CHAPTER9 DEVICES

9
In subroutine programs with argument passing, do not use any devices that are used by the function register.
If this occurs, function register values will not be normally passed to the calling program.

CALLP P0 D0

D* R0 R10 FD0
MOV K0 D3

3
Since D0 to D3 are used for FD0,
D3 cannot be used in the
subroutine program.
Figure 9.48 Ladder example in which use of devices is not allowed in a subroutine program with argument passing

4
5

Remark

For use of function devices, refer to the following.
QCPU Programming Manual (Common Instructions)

7
8

9.3 Internal System Devices
9.3.1 Function devices (FX, FY, FD)

9 - 37

9.3.2 Special relay (SM)
(1) Definition
The special relay (SM) is an internal relay of which details are specified inside the programmable controller, and
the CPU module status data are stored in this special relay.

(2) Special relay classifications
Table9.3 shows special relay classifications.
Table9.3 Special relay classification list
Classification

Special relay

Diagnostics information

SM0 to SM199
SM100 to SM115 *1

Serial communication function
System information

SM200 to SM399

System clocks and counters

SM400 to SM499

Scan information, I/O refresh

SM500 to SM599

Drive information

SM600 to SM699

Instruction related

SM700 to SM799

Debugging

SM800 to SM899

Latch area

SM900 to SM999

QnA conversion compatibility

SM1000 to SM1299 *2 *3
SM1780 to SM1799*3

Redundant power supply module information

*1: Available only for the Q00UJCPU, Q00UCPU, Q01UCPU, and Q02UCPU. (
Section 6.23)
*2: Valid only when "Use special relay/special register from SM/SD1000" is selected in the PLC system tab of the PLC
parameter dialog box.
*3: Applicability differs depending on the CPU module version. (

Remark
For details of the special relay, refer to CHAPTER 12.

9 - 38

Appendix 2)

CHAPTER9 DEVICES

9.3.3 Special register (SD)

(1) Definition
The special register (SD) is an internal relay of which details are specified inside the programmable controller,
and the CPU module status data (such as error diagnostics or system information) are stored in this special

(2) Special register classifications
Table9.4 shows special register classifications.

Table9.4 Special register classification list
Classification

Special register

Diagnostics information

SD0 to SD199

System information

SD200 to SD399

System clocks and counters

SD400 to SD499

Scan information

SD500 to SD599

Drive information

SD600 to SD699

Instruction related

SD700 to SD799

Debugging

SD800 to SD899

Latch area

SD900 to SD929

Fuse blown module

SD1300 to SD1399

Check of I/O modules

SD1400 to SD1499

QnA conversion compatibility

SD100 to SD111*1

Serial communication function

6
7
8

SD1000 to SD1299 *2 *3
SD1780 to SD1799 *3

Redundant power supply module information

*3: Applicability differs depending on the CPU module version. (

Appendix 2)

Remark
For details of the special register, refer to CHAPTER 12.

9 - 39

9.3 Internal System Devices
9.3.3 Special register (SD)

9.4 Link Direct Device (J \ )
(1) Definition
The link direct device is a device for direct access to the link device in a CC-Link IE controller network module or
MELSECNET/H network module.
The CPU module can directly write data to or read data from the link device in a CC-Link IE controller network
module or MELSECNET/H network module using sequence programs regardless of link refresh.

(2) Specification method and application example
(a) Specification method
Specify a network number and a device number.
Specification method: J

\
Device No.
Input
Output

X0 to

Link relay

B0 to

Link register
Link special relay

W0 to
SB0 to

Link special register

SW0 to

Y0 to

Network number: 1 to 255
Figure 9.49 Specification method

(b) Application example
For link register 10 (W10) of network number 2, "J2\W10" must be used.

MOVP K100 J2\ W10

Network module of
network number 2
LW 0

LW10

Figure 9.50 Application example

For a bit device (X, Y, B, or SB), the digit must be specified.

Example J1\K1X0, J10\K4B0

9 - 40

CHAPTER9 DEVICES

(3) Specification range

A link device that is not set in the Network parameter dialog box can be specified.

(a) Writing
• The write range must be within the link device send range that is set by common parameters on Network

parameter setting dialog box, and it must be outside the refresh range set by network refresh parameters.
CPU module

Network module

LB 0

Link range

Refresh range

4
Send range

5
6

Write range

Figure 9.51 Write range of a link direct device

• Although writing can be done to a refresh range portion (specified by refresh parameters) within the link

device range, the link module's link device data will be overwritten when a refresh occurs.
When writing data by using a link direct device, write the same data to the relevant devices on the CPU
module side, which are set by refresh parameters.

[Refresh parameter settings]
1) Network number: 1
2) CPU module (W0 to W3F)

Network module (LW0 to LW3F)
9.4 Link Direct Device (J\)

[Sequence program]
MOV K100 W1

MOV W1 J1\W1

"100" is written to network module
LW1 when a refresh occurs.
"100" is written to network module
LW1 when the MOV instruction is
executed.

[Writing timing]
CPU module

MOV K100 W1
MOV W1 J1\W1

Network module
Writing at
instruction
execution
W0
W1

LW1

Writing at instruction
execution
Writing by a refresh

Figure 9.52 Writing to the link device set within the refresh range

• If data are written to another station's write range using a link direct device, the data will be overwritten
with other data that are received from the corresponding station.

9 - 41

(b) Reading
The link device ranges of network modules can be read.

Writing or reading data by using a link direct device is allowed for only one network module that is on the same network.
If two or more network modules are mounted on the same network, a network module with the lowest slot number is the
target of writing or reading by the link direct device.
For example, if network modules set as station numbers 1 and 2 are mounted on network number 1 as shown in Figure 9.53,
station number 2 is the target of the link direct device.

Station
No.1

Station
No.2

Network No.1

Writing/reading using link direct devices not allowed
Writing/reading using link direct devices allowed
Figure 9.53 When two or more network module are mounted on the same network

(4) Differences between link direct devices and link refresh
Table9.5 Differences between link direct devices and link refresh
Item

Link direct device

Link refresh

Link relay

\K4B0 or higher

B0 or higher

\W0 or higher

W0 or higher

\K4SB0 or higher

SB0 or higher

\SW0 or higher

SW0 or higher

Description on

Link register

programs

Link special relay

J
J

Link special register

Number of steps

2 steps

Range of network module access

0 to J

Guaranteed access data integrity

1 step
3FFF

Range specified by refresh parameters
Word (16-bit) units

Remark
For network parameters, common parameters, and network refresh parameters, refer to the following.
• Details:
Network manual for each network module
• Setting method:
GX Developer Version 8 Operating Manual

9 - 42

CHAPTER9 DEVICES

9.5 Module Access Devices

9.5.1 Intelligent function module device (U

)

(1) Definition
The intelligent function module device allows direct access from the CPU module to the buffer memories of the
intelligent function modules which are mounted on the main and extension base units.

(2) Specification method and application example

3
4

(a) Specification method
Specify the I/O number and buffer memory address of the intelligent function module.
Specification method: U

\G
Buffer memory address (setting range: 0 to 65535 in decimal)

Starting I/O number of intelligent function module
Setting : First 2 digits of starting I/O number expressed in 3 digits
For X/Y1F0

X/Y1F0

Specification: 1F
* Setting range: 00H to FFH
Figure 9.54 Specification method

(b) Application example
When the Q64AD analog-digital converter module is mounted in the position of I/O number 020 (X/Y020 to X/
Y02F), to store digital output values of CH.1 to CH.4 into D0 to D3 accordingly, specify the device as shown in

9.5 Module Access Devices
9.5.1 Intelligent function module device (U\G)

Figure 9.54.
Q64AD
BMOV U2\G11 D0 K4
11 CH.1 Digital output value
12 CH.2 Digital output value
13 CH.3 Digital output value
14 CH.4 Digital output value

Figure 9.55 Application example

If the intelligent function module device is used, device comments can be attached to the buffer memory.
GX Developer Version 8 Operating Manual

9 - 43

(3) Processing speed
The processing speed of the intelligent function module device is as follows:
• The processing speed of writing or reading using the intelligent function module device is slightly higher
compared with the case of using the FROM or TO instruction.

Example "MOV U2\G11 D0"
• When reading from the buffer memory of an intelligent function module and another processing with one
instruction, totalize the processing speed of the FROM or TO instruction and the other instruction.

Example "+ U2\G11 D0 D10"

Instead of using the intelligent function module device in the sequence program twice or more to write or read buffer memory
data, using the FROM or TO instruction once in one place can increase the processing speed.

Figure 9.56 Writing data using the intelligent function module device multiple times

Stores data in the
data register.

Writes data once
at this point.

Figure 9.57 Writing data using the TO instruction once in the program

Remark
1.

For buffer memory addresses and applications, refer to the manual for each intelligent function module/special
function module.

For the FROM and TO instructions, refer to the following.
QCPU Programming Manual (Common Instructions)

9 - 44

CHAPTER9 DEVICES

9.5.2 Cyclic transmission area device (U3En\G

)

(1) Definition
The cyclic transmission area device is used to access the CPU shared memory of each CPU module in a multiple
CPU system.

(2) Features

2
3

• The transfer speed is higher than the case of using the write (S.TO or TO) or read (FROM) instruction to the
CPU shared memory, resulting in reduced programing steps.

• Using the cyclic transmission area device allows bit manipulation.
• By setting device comments for the cyclic transmission area device, program readability is increased.
• Because information on the CPU shared memory can be directly specified as an argument of the instruction,
no interlock device is required.

(3) Specification method

5
6

Specify the I/O number of the CPU module and the CPU shared memory address.
Specification method:U3En\G

CPU shared memory (setting range: 0 to 4096, 10000 to 24335 in decimal)
Starting I/O number of the CPU module
Setting: First 3 digits of starting I/O number
CPU module mounting location:
* CPU slot (CPU No.1): 3E00H 3E0
* Slot 0 (CPU No.2): 3E10H 3E1
* Slot 1 (CPU No.3): 3E20H 3E2
* Slot 2 (CPU No.4): 3E30H 3E3

9.5 Module Access Devices
9.5.2 Cyclic transmission area device (U3En\G)

Figure 9.58 Specification method

Remark
For details of the cyclic transmission area device, refer to the following.
QCPU User's Manual (Multiple CPU System)

9 - 45

9.6 Index Register (Z)/Standard Device Resister (Z)
9.6.1 Index register (Z)
(1) Definition
The index register is used for indirect specification (index modification) in sequence programs.
Index modification uses one point of the index register.
X0
MOVP K5 Z0
SM400

BCD D0Z0 K4Y30
Specify the index register
by one point (16 bits).
Figure 9.59 Index register

The index register has 20 points (Z0 to Z19).

(2) Bit structure of the index register
(a) Bit structure and read/write unit
One point of the index register consists of 16 bits, and data can be read or written in units of 16 bits.
b15

Zn
Most significant bit represents a sign bit.
Figure 9.60 Bit structure of the index register

Index register data are handled as signed data.
In the case of the hexadecimal notation, 0000H to FFFFH can be stored. However, because the most significant bit
represents a sign bit, decimal values that can be specified are -32768 to 32767.

9 - 46

CHAPTER9 DEVICES

(b) When using the index register for a 32-bit instruction

The processing target is Zn and Zn+1.
The lower 16 bits correspond to the specified index register number (Zn), and the higher 16 bits correspond to

the specified index register number + 1.

Example When Z2 is specified in the DMOV instruction, Z2 represents the lower 16 bits and Z3 represents
the higher 16 bits. (The most significant bit in a 32-bit structure is a sign bit.)

DMOV D0 Z2

Processing target:
Z3

Upper 16 bits Lower 16 bits

Figure 9.61 Data transfer with a 32-bit instruction and storage location

(3) When using 32-bit index modification
For the file register (ZR), extended data register (D), extended link register (W) using the serial number access
method, 32-bit index modification using two points of the index register is available.

The following two kinds of methods can be used to specify the index register.
• Specify the range used for 32-bit index modification.
• Specify the 32-bit index modification using "ZZ".

Note9.3Note1

9.6 Index Register (Z)/Standard Device Resister (Z)
9.6.1 Index register (Z)

Remark
For details and precautions of index modification using the index register, refer to the following.
QCPU Programming Manual (Common Instructions)

Note1

Note9.3

Universal

When specifying the 32-bit index modification using "ZZ" for the Q02UCPU, Q03UDCPU, Q04UDHCPU,
Q06UDHCPU, Q13UDHCPU, or Q26UDHCPU, check the versions of the CPU module and GX Developer.
(

Appendix 2)

9 - 47

9.6.2 Standard device register (Z)
(1) Definition
By using the index register between register operations, operations can be executed at a higher speed.
The index register used in this case is called the standard device resister.

(2) Device number
Since the standard device register is the same device as the index register, pay attention not to use the same
device number when using the index modification.

Remark
For operation processing and processing time of the standard device register, refer to the following.
QCPU Programming Manual (Common Instructions)

9 - 48

CHAPTER9 DEVICES

9.6.3 Switching from the scan execution type program to the interrupt/fixed scan
execution type program
The CPU module performs the following when switching from the scan execution type program to the interrupt/
fixed scan execution type program.
• Saving and restoring the index register data

9
2
3

• Saving and restoring block numbers of the file register

(1) Setting for saving and restoration

Saving and restoration setting can be enabled in the PLC system tab of the PLC parameter dialog box.
To disable writing to the index register in the interrupt/fixed scan execution type program, select "High speed
execution" in the Interrupt program/Fixed scan program setting area.

If this setting is enabled, the program will switch faster than before.

6
7
8

9.6 Index Register (Z)/Standard Device Resister (Z)
9.6.3 Switching from the scan execution type program to the interrupt/fixed scan execution type
program

Figure 9.62 Interrupt/fixed scan program setting

9 - 49

(2) Processing of the index register
(a) When "High-speed execution" is not selected
1) When switching from the scan execution type program to the interrupt/fixed scan
execution type program
The CPU module saves index register values in the scan execution type program, and passes them to the
interrupt/fixed scan execution type program.

2) When switching from the interrupt/fixed scan execution type program to the scan
execution type program
The CPU module restores the saved index register values.

Execution program

Index register value

Scan execution
type program

Switching Interrupt/fixed scan Restored Scan execution

execution type
program
Passed

Z0=1

type program

Z0=3*1

Z0=1
Restored

Saved
Save area of index register
for scan execution
type program

Z0=0

Z0=1

Figure 9.63 Saving and restoring index register data (when "High speed execution" is not selected)
*1: The Z0 value is changed to 3 in the interrupt program.

To pass index register values from the interrupt/fixed scan execution type program to the scan execution type program, use
word devices.

9 - 50

CHAPTER9 DEVICES

(b) When "High-speed execution" is selected

1) When switching from the scan execution type program to the interrupt/fixed scan
execution type program

The CPU module does not save/restore any index register values.

2) When switching from the interrupt/fixed scan execution type program to the scan
execution type program

If data are written to the index register by the interrupt/fixed scan execution type program, the values of the
index register used in the scan execution type program will be corrupted.

Execution program

Scan execution
type program

Switching

Passed
Index register value

Interrupt/fixed scan
Restored Scan execution
execution type
type program
program

Z0=1

Z0=3 *1

Passed
Z0=3

Save area of index register
for scan execution
type program

Z0=0

Figure 9.64 Saving and restoring index register data (when "High speed execution" is selected)
*1: The Z0 value is changed to 3 in the interrupt program.

8
When writing data to the index register by the interrupt/fixed scan execution type program, use the ZPUSH or
ZPOP instruction to save and restore the data.
ZPUSH

SM400

ZPOP

D0
IRET

9.6 Index Register (Z)/Standard Device Resister (Z)
9.6.3 Switching from the scan execution type program to the interrupt/fixed scan execution type
program

SM400
I0

Data in Z0 to Z15 are
stored in the area
addressed from D0.

Data in the area
addressed from D0 are
stored in Z0 to Z15.

Figure 9.65 Writing data to the index register in the interrupt/fixed scan execution type program

9 - 51

(3) Processing of file register's block numbers
(a) When switching from the scan execution type program to the interrupt/fixed scan
execution type program
The CPU module saves the file register block numbers in the scan execution type program, and passes them
to the interrupt/fixed scan execution type program.

(b) When switching from the interrupt/fixed scan execution type program to the scan
execution type program
The CPU module restores the saved block numbers of the file register.

Execution program

Scan execution
type program

Switching

Passed

Block No. of
file register

Block 1

Save area

Block 0

Interrupt/fixed scan
execution type
program
[RSET K0]
Block1

Saved

Block 1

Restored

Block 1
0

Block 1

Restored

Block 1

Figure 9.66 Saving and restoring file register's block numbers

9 - 52

Scan execution
type program

Block 1

CHAPTER9 DEVICES

9.7 File Register (R)

Note9.4

(1) Definition

The file register (R) is a device provided for extending the data register.
The file register can be used at the same processing speed as the data register.Note1

3
MOV K100 R2

File register
R0
R1
100 is written to R2.

Figure 9.67 Writing to the file register

(2) Bit structure od the file register

(a) Bit structure and read/write unit
One point of the file register consists of 16 bits, and data can be read or written in units of 16 bits.
to

b15

Rn
Most significant bit represents a sign bit.

(b) When using a 32-bit instruction for the file register
The processing target is Rn and Rn+1.
The lower 16 bits correspond to the file register number (Rn) specified in the sequence program, and the
higher 16 bits correspond to the specified file register number + 1.
For example, when R2 is specified in the DMOV instruction, R2 represents the lower 16 bits and R3 represents
the higher 16 bits.

DMOV D0

R2
Processing target: R2, R3
R3

Upper 16 bits Lower 16 bits
Figure 9.69 Data transfer with a 32-bit instruction and storage location

Data of -2147483648 to 2147483647 or 0H to FFFFFFFFH can be stored in a two-point area of the file register.
(The most significant bit in a 32-bit structure is a sign bit.)

Note1

Note9.4

Universal

The Q00UJCPU does not have the file register.

9 - 53

9.7 File Register (R)

Figure 9.68 Bit structure of the file register

(3) Clearing the file register
The file register contents are backed up by the battery built in the CPU module, and they are held if the CPU
module is powered off or reset.
(Not initialized even if the latch is cleared.*1)
*1: The latch range of the file register can be set in the Device tab of the PLC parameter dialog box. (

Section 6.3)

To initialize the file register contents, perform the data clear operation in the sequence program or GX Developer.

(a) When clearing by the sequence program
FMOV K0 R0 K1000
Figure 9.70 Example of clearing the file register R0 to R999

(b) When clearing by GX Developer
Select [Online]

[Clear PLC memory] in GX Developer and clear the data by selecting "Clear all file registers".

9.7.1 File register data storage location
There are the following three kinds of memory media for storing file register data.
• Standard RAM
• SRAM card
• Flash card

9.7.2 File register size
(1) When using the standard RAM
The table below shows the maximum points of file register data that can be stored in the standard RAM.
Note that, however, if the standard RAM is used for an application other than file registers, available points are
decreased. (

Section 5.1.10)
Table9.6 File register size
CPU module

Q00UCPU, Q01UCPU, Q02UCPU

64K

Q03UDCPU, Q03UDECPU

96K

Q04UDHCPU, Q04UDEHCPU

128K

Q06UDHCPU, Q06UDEHCPU

384K

Q10UDHCPU, Q10UDEHCPU, Q13UDHCPU,
Q13UDEHCPU
Q20UDHCPU, Q20UDEHCPU, Q26UDHCPU,
Q26UDEHCPU

9 - 54

Points

512K
640K

CHAPTER9 DEVICES

(2) When using an SRAM card
Up to 4086K points can be stored in one file.
Since one block consists of 32K words, up to 128 blocks can be stored.

Note that the number of points or blocks that can be added depends on the size of the programs and device
comments stored in the memory card.

(3) When using a Flash card
Up to 2039K points can be stored in one file.

Since one block consists of 32K words, up to 64 blocks can be stored.
Note that the number of points or blocks that can be added depends on the memory card capacity and the size of

the programs and device comments stored in the memory card.

Remark

For the memory cards available for the CPU module, refer to Section 5.1.1.

9.7.3 Differences in available accesses by storage memory

Accesses available for the file register vary for each memory.
Table9.7 Differences in accesses available for the file register
Access

Standard RAM

SRAM card

Flash card
9.7 File Register (R)
9.7.3 Differences in available accesses by storage memory

Program writing
Program reading
Writing device memory to programmable controller
Reading device memory from programmable controller
Online test operation from GX Developer
Writing to programmable controller by GX Developer
Data

Writing to programmable controller by GX Developer (flash ROM)

modification

Batch write by a serial communication module
Device data writing from GOT1000 series
Random write command from GOT1000 series

9 - 55

9.7.4 Registration procedure for the file register
To use a file register, register the file of the file register to the CPU module in the following steps.
Setting a
file register

Start
"PLC file" tab of the PLC parameter dialog box

Select "Use the following file."
Select "Not used" or " Use the
same name as the program."
File register setting
New "Device memory" window

Writing the file register
[Online]

[Write to PLC]

Write the file register to the CPU module.

Write parameters to the CPU module.
Figure 9.71 Registration procedure for the file register

9 - 56

CHAPTER9 DEVICES

(1) Setting the file register
In the PLC file tab of the PLC parameter dialog box, specify the standard RAM or a memory card to use the file
register in the sequence program.

2
3

(a)
(b)

(c)

5
6
Figure 9.72 File register setting

(a) Not used

Select this in the following cases.
• When not using any file register
• When specifying a file register used in the sequence program (the QDRSET instruction is used for
specification.)

9.7 File Register (R)
9.7.4 Registration procedure for the file register

9 - 57

(b) Use the same file name as the program.
Select this when executing the file register with the same file name as the sequence program.

1) When the program is changed
The file name of the file register is automatically changed to the same name as the program.
This feature is useful if the file register is exclusively used for one program as a local device.

Example When each of file registers A to C has the same name with the corresponding one of the program
A to C, the operation is as described below.
• During execution of program A: Accessing file register A
• During execution of program B: Accessing file register B
• During execution of program C: Accessing file register C

Program A execution

Synchronized

Program B execution

Synchronized

Program C execution

Synchronized

File register A

File register B

File register C

Figure 9.73 When the program is changed

2) Point setting for file registers
Select [Online]

[Write to PLC] in GX Developer and set the number of file register points.

●

Only one file register can be created in the standard RAM.
To create more than one, use a SRAM or Flash card.

●

With some instructions, file registers set for respective programs cannot be specified.
For details, refer to the pages describing devices available for each instruction in the following manual.
QCPU Programming Manual (Common Instructions)

(c) Use the following file.
Select this when one file register is to be shared by all execution programs.
Specify "Corresponding memory", "File name", and "Capacity" and write these parameters to the CPU module
to create a file for the file register.
If the capacity is not specified, note the following.
• When the specified file register file is stored in the specified drive, the file is used. (The capacity is the
same as that of the stored file register file.)
• If the file register file with the specified file name is not found on the specified drive, "PARAMETER
ERROR" (error code: 3002) will occur.
• For use of an ATA card, "Memory card (ROM) cannot be selected for "Corresponding memory".
(File register data cannot be stored in ATA cards.)
Selecting "Memory card (ROM)"for "Corresponding memory" and writing the settings to the CPU module
will result in "PARAMETER ERROR" (error code: 3002).

9 - 58

CHAPTER9 DEVICES

(2) File register setting
In a new device memory window, set data for the specified file register.

2
3
4
5

Figure 9.74 Device memory window

(a) Devices
Setting Rn (R0 in the case shown above)and clicking the Display button will display the file register list.

(b) Data setting

7
8

Enter data that are set for the file register.
This step is not needed when you specify only the capacity of file register.

When either of the following is selected in the PLC file tab of the PLC parameter dialog box, the file register file
must be registered to the CPU module.
• Not used. (when specifying a file register used in the sequence program) (
• Use the same name with the program. (

(1)(a) in this section)

(1)(b) in this section)

File register files can be registered to the CPU module by selecting [Online]

[Write to PLC] in GX Developer.

Figure 9.75 File register file registration

9 - 59

9.7 File Register (R)
9.7.4 Registration procedure for the file register

(3) Registering the file register file to the CPU module

(a) Target memory
Select the Standard RAM, Memory card (RAM), or Memory card (ROM) from this list box.
When using the same file name as that of the program, register the file register to the memory specified in the
PLC File tab of the PLC parameter dialog box.

(b) Selecting a file register file
By selecting a memory for the file register, file names of the set file registers are displayed. Select a file register
file.

(c) Setting the size and file name
Set the size of the file register and a file name of the file register file to be written to the CPU module (PLC-side
file name).

1) File register size of the CPU module
The file register size can be set in increments of one point.
Note that each file size is ensured in units of 256 points.
Even if a file register is not specified from ZR0, the created file will have an assignment from ZR0 to the last
number.
For example, if the write range of a file register is specified to be ZR1000 to ZR1791, the created file register
file will have an assignment from ZR0 to ZR1791.
However, because the data in ZR0 to ZR999 are unreliable, specify the file register from ZR0.
The size of the file register is checked in the units of 1K points. Therefore, the file register size must be
specified from R0 in the units of 1K points.

(d) Writing to the CPU module
The file register file of the specified points is registered to the specified memory of the CPU module.

9 - 60

CHAPTER9 DEVICES

9.7.5 Specification methods of the file register

(1) Block switching method
The file register points used are divided and specified in units of 32K points (R0 to R32767).
If multiple blocks are used, the desired block is specified with the block number in the RSET instruction.

Each block has a specification range of R0 to R32767.

3
RSET K1

MOV

R0 specification
for block 1

Block 0

R0
R32767

RSET K2

MOV

R0 specification
for block 2

5
Block 1

R32767

R0
Block 2

Figure 9.76 Block switching method

(2) Serial number access method

A file register whose size is exceeding 32K points can be specified using consecutive device numbers.
Multiple blocks of a file register can be used as a continuous file register.
This kind of device is expressed as "ZR".

9.7 File Register (R)
9.7.5 Specification methods of the file register

MOV

ZR32768
ZRO
(Block 0)

MOV

ZR32767
ZR32768

ZR65536

(Block 1)
ZR65535
ZR65536
(Block 2)

Figure 9.77 Serial number access method

The block numbers and ZR device points that can be specified vary depending on the following.
• Storage location of the file register (
• File register size (

Section 9.7.1)

Section 9.7.2)

9 - 61

9.7.6 Precautions for using the file register
(1) No registration or use of an invalid file register number
(a) When the file of the file register has not been registered
Writing to or reading from the file register will result in "OPERATION ERROR" (error code: 4101).

(b) When writing to or reading from the file register exceeding the registered size
(points)
"OPERATION ERROR" (error code: 4101) will occur.

(2) File register size check
When writing to or reading from the file register, check the file register size so that data can be written or read
within the size (points) set for the CPU module.

(a) Checking the file register size
The file register size can be checked in the File register capacity area (SD647). *1
The file register size data in units of 1K points is stored in this SD647.
*1: If a file register file is switched to another, the size of the currently selected file register file is stored in SD647.

The remainder after dividing the file register size by 1K points is discarded.
To ensure an accurate "range of use" check, specify the file register setting in units of 1K points (1024 points).

(b) Checking timing
• In a program using any file register, check the file register size at step 0.
• After execution of the file register file switching instruction (QDRSET), check the file register size.
• Before executing the file register block switching instruction (RSET), confirm that space of 1K points or
more can be ensured after the switching.
(File register size) > [32K points

9 - 62

(Switching block No) + {1K points]

CHAPTER9 DEVICES

• Check the file register size used for each sequence program.
• Check the total file register size set in SD647 on the sequence program to see if there are sufficient

number of points to be used or not.
[Program example 1]

The file register range of use is checked at the beginning of each program.
4K points specified

SM400
<

SD647

Final file register
range check

Alarm processing

Transfer command
MOVP K4X20 R0

Writing to file
register

[Program example 2]
The file register range of use is checked after execution of the QDRSET instruction.

QDRSET "1:ABCD"

Changing file register to
ABCD of Drive 1

SM400
SD647 K4

Final file register
range check

Alarm processing

M0
9.7 File Register (R)
9.7.6 Precautions for using the file register

M0 Transfer command

MOVP K4X20 R0

Writing to file
register

[Program example 3]
When a block is switched to another:
SM400
<

SD647 K33

Final file register
range check

Alarm processing

M0
Block switching
M0
command
RSET K1

Switching to block 1

Figure 9.78 Program examples of file register checking

(3) Deleting a file register file
To delete an unnecessary file register file, select [Online]

[Delete PLC data] in GX Developer.

9 - 63

9.8 Extended Data Register (D) and Extended Link Register
(W) Note9.5
(1) Definition
The extended data register (D) and extended link register (W) are devices for using the large-capacity file register
(ZR) area as an extended area of the data register (D) and link register (W). These devices can be programmed
as the data register (D) and link register (W) together with the file register (ZR) area.Note1

Device numbers can be assigned to the
data register and extended data register
consecutively.

Internal user device
D0

K123

D10

K567

D1300

Device

Points for data
register
D1228

Data register

File register file

D12287
D12288

ZR
Points for
file
register

Extended data
register

ZR210943
D12288
Points for
extended
data register

D63487

D63487
M2000

The file size is the total
points for the file
register, extended data
register, and extended
link register.

Points for
extended
link register

Figure 9.79 Operation of the extended data register (D) and extended link register (W)

Note1

Note9.5

Universal

For the Q00UJCPU, the extended data register (D) and extended link register (W) cannot be used.
For using them for the Q02UCPU, Q03UDCPU, Q04UDHCPU, Q06UDHCPU, Q13UDHCPU, Q26UDHCPU, and
Built-in Ethernet port QCPU, check the version of GX Developer. (

9 - 64

Appendix 2)

CHAPTER9 DEVICES

(2) Device numbers
Device numbers for the extended data register (D) and extended link register (W) can be assigned consecutively
after those for the internal user devices, data register (D) and link register (W).

●

Even though device numbers are consecutively assigned, there is no physical area contiguity between the data register
(D) (internal user device) and the extended data register (D), and between the link register (W) (internal user device)
and the extended link register (W).
To use them as one contiguous area, set the points for the data register (D) and link register (W) (internal user device)
to "0" in the Device tab of the PLC parameter dialog box, and use only the extended data register (D) and extended link
register (W).
When using the file register (ZR), extended data register (D) and extended link register (W) with the auto refresh setting
enabled in GX Configurator, the points set in the File register extended setting in the Device tab of the PLC parameter
dialog box must not be exceeded.

3
4
5
6
7
8

9.8 Extended Data Register (D) and Extended Link Register (W)

9 - 65

(3) Setting method
Since the extended data register (D) and extended link register (W) use the file register area, data must be set for
both the file register setting and the device setting.

(a) File register setting
Select "Use the following file." in the PLC file tab of the PLC parameter dialog box, and enter data in the boxes
indicated in Figure 9.80.
The "Use the same file name as the program." option is not selectable.

Specify the target memory,
file name, and file size.

Figure 9.80 Dialog box for file register point setting

Table9.8 File register setting item list
Item

Corresponding memory
*4

Any name

1 to 4086K points

Memory card (ROM) *4

Any name

1 to 2039K points *3

Memory card (RAM)

Q00UCPU, Q01UCPU, Q02UCPU
"Use the following
file"

Capacity *1

File name

1 to 96K points

Q04UDHCPU, Q04UDEHCPU

1 to 128K points

Q06UDHCPU, Q06UDEHCPU

RAM

Q10UDHCPU, Q10UDEHCPU,
Q13UDHCPU, Q13UDEHCPU
Q20UDHCPU, Q20UDEHCPU,
Q26UDHCPU, Q26UDEHCPU

Any name

1 to 384K points
1 to 512K points
1 to 640K points

*1: The total points of the file register (ZR), extended data register (D), and extended link register (W).
*2: This is the maximum number of points when an SRAM card (8M bytes) is used.
*3: This is the maximum number of points when a Flash card (4M bytes) is used.
*4: For the Q00UCPU and Q01UCPU, no memory card can be used.

9 - 66

Remarks
Read only

1 to 64K points

Q03UDCPU, Q03UDECPU
Standard

CHAPTER9 DEVICES

(b) Device setting
Set each number of points for the file register (ZR), extended data register (D), and extended link register (W)

in the File register extended setting in the Device tab of the PLC parameter dialog box.
Assign a part of the points set for the file register (ZR) in the PLC file tab to the extended data register (D) and
extended link register (W).

2
3

If data are to be latched, specify the latch range.
• Latch (2) of the file register (ZR)
• Latch (1) and (2) of the extended data register (D)

• Latch (1) and (2) of the extended link register (W)
The number of file register points set in the
PLC file tab is displayed.

5
6
Set these points so that the total is equal to the file
register size set in the PLC file tab.

Specify the latch range if data are to be latched.

Figure 9.81 File register extended setting

Once the points for the extended data register (D) and extended link register (W) is set, areas for these devices

are reserved in the file register file.
Actual area

9.8 Extended Data Register (D) and Extended Link Register (W)

Internal user device
D0

Device

Points for data
register

D0
D1228
Data register

File register file

D12287
D12288

ZR
Points for
file
register

Extended data
register

ZR1112063
D12288
D63487

D1036287
W2000

Areas for the
extended data register
and extended link
register are reserved
Points for
in this order, after the
extended
data register area for the file
register points.
Points for
extended
link register

Figure 9.82 Areas for the extended data register (D) and extended link register (W)

9 - 67

(4) Checking the points by the special register
The points for each of the file register (ZR), extended data register (D), and extended link register (W) can be
checked in the following special register areas.
• SD306, SD307: File register (ZR)
• SD308, SD309: Extended data register (D)
• SD310, SD311: Extended link register (W)

(5) Precautions
For use of the extended data register (D) and extended link register (W), pay attention to the following.
1) When the extended data register (D) and extended link register (W) are specified, the values of the
following items will be the same as those for the file register (ZR).
• Number of program steps
• Instruction processing time
• Processing time of auto refresh with network modules
• Processing time of auto refresh with intelligent function modules
• Processing time of auto refresh between CPU shared memories
2) The file register size cannot be changed in the RUN status.
3) The file register cannot be switched to another using the QDRSET instruction. ("OPERATION ERROR"
(error code: 4100))
4) Set the refresh ranges for the following auto refresh properly so that each refresh range does not cross over
the boundary between the internal user device and the extended data register (D) or extended link register
(W).
• Auto refresh with network modules
• Auto refresh with intelligent function modules
• Auto refresh between CPU shared memories
5) Set the following properly so that each specification does not cross over the boundary between the internal
user device and the extended data register (D) or extended link register (W).
• Index modification
• Indirect specification
• Specification for instructions that use block data *1
*1: Block data means the following:
•Data used in instructions, such as FMOV, BMOV, and BK+, which treat more than one word for operation.

•Control data, composed of two or more words, which are specified in instructions, such as SP.FWRITE and SP.FREAD.
•Data in a 32-bit or greater format (binary 32 bits, real number, indirect address of a device)

Remark
For details on the index modification and indirect specification with the extended data register (D) and extended link
register (W), refer to the following.
QCPU Programming Manual (Common Instructions)

9 - 68

CHAPTER9 DEVICES

6) To access the extended data register (D) or extended link register (W) from a module that does not support
the use of these devices, device numbers need to be specified with those of the file register (ZR).

Calculation formulas for obtaining device numbers of the file register (ZR) to be specified to access the
extended data register (D) and extended link register (W) and calculation examples are described below.
Table9.9 Calculation formulas for obtaining device numbers of the file register (ZR) to be specified to access the extended data

Calculation formula

Device number of the file register (ZR) used to access the extended data register (D)

EDZN = ZRC + (EDN - DC )

Device number of the file register (ZR) used to access the extended link register (W)

EWZN = ZRC + EDC +(EWN - WC )

*1: Variables in the table indicate the following:
•ZRC: Points of the file register (ZR)

•EDZN: Device number of the file register (ZR) used to access the extended data register (D)
•EDN: Access target device number of the extended data register (D)
•DC: Points of the data register (D)
•EDC: Points of the extended data register (D)
•EWZN: Device number of the file register (ZR) used to access the extended link register (W)
•EWN: Access target device number of the extended link register (W) (hexadecimal)
•WC: Points of the link register (W)

4
5
6
7

[Calculation example]
• DC: Points of the data register (D) ••• 12288 points
• WC: Points of the link register (W) ••• 8192 points

• ZRC: Points of the file register (ZR) ••• 2048 points
• EDC: Points of the extended data register (D) ••• 2048 points

9.8 Extended Data Register (D) and Extended Link Register (W)

1) Device number of the file register (ZR) used to access D13000
EDZN = 2048 + (13000-12288) = 2760
2) Device number of the file register (ZR) used to access W2100
EWZN = 2048 + 2048 + (2100H - 8192) = 2048 + 2048 + (8448 - 8192) = 4352
D0
Data register (D)
ZR0

D12287
D12288

ZR2047
ZR2048

1) D13000

ZR2760

D14335

File register (ZR)

Extended data register (D)

W0
Link register (W)
ZR4095

W1999

ZR4096

W2000

ZR4352

2) W2100

ZR6143

W27FF

Extended link register (W)

Figure 9.83 Access to the extended data register (D) and extended link register (W)

9 - 69

9.9 Nesting (N)
(1) Definition
Nesting (N) is a device used in the master control instructions (MC and MCR instructions) to program operation
conditions in a nesting structure.

(2) Specification method using master control instructions
The master control instruction opens or closes a common ladder gate to switch the ladder of a sequence program
efficiently.
Specify the nesting (N) in ascending order (in order of N0 to N14), starting from the outside of the nesting
structure.

Designated in
ascending No. order

A
MC
N0

M15

M15
B
MC

M16

M16
Executed when conditions
A and B are met.

C
MC
Control
range of
nesting N0

Control
range of
nesting N1

Control
range of
nesting N2

Executed when condition
A is met.

M17

Designated in
descending No. order
Executed when conditions
A, B, and C are met.

MCR

N2
Executed when conditions
A and B are met.

MCR

N1
Executed when condition
A is met.

MCR

Executed regardless of
conditions A, B, and C.
Figure 9.84 Programming example using the nesting

Remark
For use of the nesting, refer to the following.
QCPU Programming Manual (Common Instructions)

9 - 70

CHAPTER9 DEVICES

9.10 Pointer (P)

(1) Definition
The pointer (P) is a device used in jump instructions (CJ, SCJ, or JMP) or subroutine call instructions (such as

CALL).

(2) Applications
Pointers can be used in the following applications.
• Specification of the jump destination in a jump instruction (CJ, SCJ, or JMP) and a label (start address of the
jump destination)

• Specification of the call destination of a subroutine call instruction (CALL or CALLP) and a label (start
address of the subroutine program)

5
CALL P0

FEND

P0
RET

END

9.10 Pointer (P)

Figure 9.85 Program using a pointer

(3) Pointer types
There are the following two different pointer types.
• Local pointer (

Section 9.10.1):

The pointer used independently in each program
• Common pointer (

Section 9.10.2):

The pointer that can be called in all running programs by the subroutine call instruction.

(4) Number of available pointer points
The number of points available for the pointer is 4096.

Remark
For the jump instructions and subroutine call instructions, refer to the following.
QCPU Programming Manual (Common Instructions)

9 - 71

9.10.1 Local pointer
(1) Definition
The local pointer is a pointer that can be used independently in jump instructions and subroutine call instructions
in each program.
The same pointer number can be used in respective programs.
Program A

Program B
The same pointer
No. can be used.
CALL P0

CALL P0

FEND

P0
RET

RET

END

Figure 9.86 Using the same pointer in respective programs (local pointer)

(2) Number of local pointer points
The local pointer can be divided for use of all the programs stored in the program memory.
The local pointer number ranges from P0 to the highest number of the local pointer in use. (The CPU module's
system computes the number of points used.)
Even if only P99 is used in a program, for example, the number of points used will be 100, which is from P0 to
P99.
For using the local pointer for several programs, use the pointers in ascending order starting from P0 in each
program.

Example The total is 600 points when the pointer is used as shown below.
Program A

Program B

Program C

Using P0 to P99

Using P100 to
P199

Using P299 only

200 points of
P0 to P199 occupied

300 points of
P0 to P299 occupied

Use of P0 to P99
occupies 100
points.

Use of P0
occupies 1 points.

100 points of
P0 to P99 occupied

Figure 9.87 Concept of the local pointer points

9 - 72

Total of 600 points are used.

CHAPTER9 DEVICES

(3) Precautions for using the local pointer
(a) Program where the local pointer is described

A jump from another program is not allowed.
jump instructions and sub-routine CALL instructions.
Use the ECALL instruction from another program when calling a subroutine program in a program file that
contains any local pointer.

(b) Total number of local pointer points
If the total number of pointers (in all programs) exceeds 4096 points, a "Pointer configuration error" (error code:
4020) occurs.

4
5
6
7
8

9.10 Pointer (P)
9.10.1 Local pointer

9 - 73

9.10.2 Common pointer
(1) Definition
The common pointer is used to call subroutine programs from all programs that are being executed.
Program A

Program C

CALL P204

P204

CALL P0
RET

FEND

P205
Program B
RET
CALL P205
END
FEND
Label
Figure 9.88 Calling pointers in another program (common pointer)

(2) Common pointer range
In the PLC system tab of the PLC parameter dialog box, set the start number for the common pointer.
The common pointer range is from the specified pointer number to P4095.
However, the pointer number that can be entered here is a number higher than the total points used for the local
pointer.
Set the start
number of the
common
pointer.

Figure 9.89 Dialog box for setting the common pointer

If a total of 400 points are used in three programs (100 points in each of Program A and Program B, and 200
points in Program C), for example, P400 and higher numbers can be set for the common pointer.

9 - 74

CHAPTER9 DEVICES

(3) Precautions
1) The same pointer number cannot be used as a label.

Doing so will result in a "Pointer configuration error" (error code: 4021).
2) If the total number of the local pointer points used in several programs exceeds the start number of the

common pointer, a "Pointer configuration error (error code: 4020) will occur.
Program A

Program B

Using P0 to P99

100 points of
P0 to P99 occupied

100 points of
P0 to P99 occupied
Total of 400 points
are used.

Program C
Using
P0 to P199

200 points of
P0 to P199 occupied

P400 and higher numbers
can be used for the common pointer.

Figure 9.90 Concept of the common pointer range

7
The jump instructions are not capable of executing a jump to the common pointer in other programs.
Use the common pointer with subroutine call instructions only.

9.10 Pointer (P)
9.10.2 Common pointer

9 - 75

9.11 Interrupt Pointer(I)
(1) Definition
The interrupt pointer (I) is used as a label at the start of an interrupt program, and can be used in any programs.
Interrupt pointer (interrupt program label)
I
Interrupt program
IRET
Figure 9.91 Interrupt pointer

(2) Number of available points
The number of points available for the interrupt pointer is 256 (I0 to I255).

(3) Interrupt factors
Interrupt factors are listed in Table9.10.
Table9.10 Classification of interrupt factors
Interrupt factor
Interrupt by an interrupt

module *1

Interrupt by the internal timer
Multiple CPU synchronous interrupt *2
Intelligent function module interrupt

Interrupt pointer No.

Description

I0 to I15

Interrupt input from an interrupt module

I28 to I31

Fixed scan interrupt by the internal timer of the CPU module

I45
I50 to I255

Fixed scan interrupt to execute synchronized control with the
operation cycle of a motion controller
Interrupt from an intelligent function module *3

*1: For available interrupt modules, refer to the following.
QCPU User's Manual (Hardware Design, Maintenance and Inspection)
*2: Applicable when using the Universal model QCPU and motion controller that support the multiple CPU high speed transmission.
*3: This module can be a serial communication module, MELSECNET/H module, Ethernet module, or high-speed counter module.
For details, refer to the manual for each module.

To use the intelligent function module interrupt (
Section 6.22), the intelligent function module setting (interrupt pointer
setting) is required in the "PLC system" tab of the PLC parameter dialog box.

9 - 76

CHAPTER9 DEVICES

9.11.1 List of interrupt pointer numbers and interrupt factors

The list of interrupt pointer numbers and interrupt factors are shown below.

Table9.11 List of interrupt pointer numbers and interrupt factors
I No.

Interrupt factor

Priority

I No.

1st point

2nd point

3rd point

4th point

5th point

6th point

7th point

I32 to

8th point

I44

9th point

I6
Interrupt by

interrupt module

(QI60)

10th point

I10

11th point

I11

12th point

I12

13th point

I13

14th point

I14

15th point

I15

16th point

N/A

7
I45
*2 *5

Multiple CPU
synchronous

0.88ms

N/A

interrupt
-

Intelligent
function module
I50 to

interrupt *3 *5/

I255

Interrupt by
interrupt module

I29 *5
I30

I31 *5

Specify the intelligent function
module or interrupt module (QI60)

22 to 227

with a parameter.

(QI60)

I28 *5
Interrupt by
internal timer

100ms

40ms

20ms

10ms

*1: The time-limit value of the internal timer is set by default.
In the PLC system tab of the PLC parameter dialog box, the value can be changed within the range of 0.5ms to 1000ms in increments
of 0.5ms.
*2: This is available for multiple CPU system configuration.
*3: To use the intelligent function module interrupt, the intelligent function module setting (interrupt pointer setting) is required in the PLC
system tab of the PLC parameter dialog box. (For interrupt from an intelligent function module, refer to Section 6.22.
*4: I50 has the highest priority (priority 22), and I255 has the lowest priority (priority 227).
*5: When an interrupt occurs, even if no interrupt pointer exists on the program, CANíT EXECUTE(I) (error code: 4220) does not occur.

9 - 77

9.11 Interrupt Pointer(I)
9.11.1 List of interrupt pointer numbers and interrupt factors

I49

I27

Priority

I46 to

I16 to

Interrupt factor

9.12 Other Devices
9.12.1 SFC block device (BL)
The SFC block is used to check that the specified block in the SFC program is activated.

Remark
For use of the SFC block device, refer to the following.
QCPU (Q Mode)/QnACPU Programming Manual (SFC)

9.12.2 Network No. specification device (J)
(1) Definition
The network No. specification device is used to specify the network number in the link dedicated instructions.

(2) Specification method
In the link dedicated instruction, this device is specified as shown in Figure 9.92.

JP.READ Jn S1 S2 S3 D
Network No. specification device
(n: network No.)
Instruction name
Network No. specification instruction
Figure 9.92 How to use the network No. specification device

Remark
For details of the link dedicated instructions, refer to the following.
Reference manual for each network module

9 - 78

CHAPTER9 DEVICES

9.12.3 I/O No. specification device (U)

(1) Definition
The I/O No. specification device is used to specify I/O numbers in the intelligent function module dedicated
instructions.

(2) Specification method

2
3

In the intelligent function module dedicated instruction, this device is specified as shown in Figure 9.93.

GP.READ Un S1 S2 S3 D
I/O No. specification device
(n: I/O No.)
Instruction name
I/O No. specification instruction

Figure 9.93 How to use the I/O No. specification device

Remark

For details of the intelligent function module dedicated instructions, refer to the following.
Manual for the intelligent function module used

9.12 Other Devices
9.12.3 I/O No. specification device (U)

9 - 79

9.12.4 Macro instruction argument device (VD)
(1) Definition
The macro instruction argument device (VD) is used with ladders registered as macros.
When a VD

setting is specified, the value is converted to the specified device when the macro instruction is

executed.

(2) Specification method
Among the devices used in the ladders registered as macros in GX Developer, specify a device used for VD.
When using macro instructions in the sequence program, specify devices that correspond to the macro instruction
argument devices used in the macro registration ladders in ascending order.
Sequence program

Ladder registered as a macro (registration name: MAX)
M.MAX D0 D1 R0

VD0 VD1

MOV VD0 VD2

VD0 VD1

MOV VD1 VD2

Passing to VD2
Passing to VD1
Passing to VD0

Command with the name of the ladder registered as a macro

Sequence program that actually runs in the CPU module
>

D0 D1

MOV D0 R0

D0 D1

MOV D1 R0

Figure 9.94 Macro instruction argument device specification

●

With the macro instruction argument device, VD0 to VD9 can be used in one macro registration ladder.

●

The GX Developer read mode provides an option to view a program in macro instruction format.
To change the display, select [View]
[Display macro instruction format].

Macro instruction display switching

Figure 9.95 Setting for macro instruction display

9 - 80

CHAPTER9 DEVICES

9.13 Constants

9.13.1 Decimal constant (K)

(1) Definition
The decimal constant (K) is used to specify decimal data in sequence programs.
Specify it as K

(example: K1234) in sequence programs.

In the CPU module, data are stored in binary (BIN). (

Section 2.4.1)

(2) Specification range
The specification ranges for decimal constants are as follows:

• When using word data (16-bit data) •••••••••••••••••••••••••••••••• K-32768 to K32767
• When using 2-word data (32-bit data)•••••••••••••••••••••••••••••• K-2147483648 to K2147483647

6
The most significant bit represents a sign bit.

7
8

9.13.2 Hexadecimal constant (H)
(1) Definition
(For BCD data, each digit of a hexadeciml number is specified with 0 to 9.)
In sequence programs, specify it as H

(example: H1234). (

Section 2.4.2)

(2) Specification range
The specification ranges for hexadecimal constants are as follows:
• When using word data (16-bit data) ••• H0 to HFFFF (For BCD data, H0 to H9999)
• When using 2-word data (32-bit data) ••• H0 to HFFFFFFFF (For BCD data, H0 to H99999999)

9 - 81

9.13 Constants
9.13.1 Decimal constant (K)

The hexadecimal constant (H) is a device for specifying hexadecimal or BCD data in sequence programs.

9.13.3 Real number (E)
(1) Definition
The real number (E) is a device used to specify real numbers in sequence programs.
In sequence programs, specify it as E

(example: E1.234). (

Section 2.4.4)

X1
EMOVP E1.234

Figure 9.96 Real number specification

(2) Specification range
(a) Real number setting range
• For single-precision floating-point data
-2128 < Device

-2-126, 0, 2-126

Device < 2128

• For double-precision floating-point data
-21024 < Device

-2-1022, 0, 2-1022

Device < 21024

(b) When an overflow or underflow has occurred
Table9.12 shows the operation of the CPU module when an overflow or underflow has occurred during
arithmetic operation.
Table9.12 When an overflow or underflow has occurred
Overflow

Underflow

OPERATION ERROR (error code: 4141)

Turned to 0 without any error

(c) When a special value*1 is input
If operation is performed with input data that contains a special value, "OPERATION ERROR" (error code:
4140) occurs.
*1: The special values are -0, unnormalized numbers, nonnumeric characters, and

(3) Specification method
Real numbers can be specified in sequence programs by the following expressions.
• Normal expression ••• A numeric value can be specified as it is.

Example 10.2345 can be specified as E10.2345.
• Exponential expression ••• A numeric value is specified by (Value)

Example 1234 is specified as E1.234 + 3.*1
*1: + 3 represents 103 in E1.234 + 3.

9 - 82

10n.

CHAPTER9 DEVICES

9.13.4 Character string (" ")

(1) Definition
The character string is a device used to specify a character string in sequence program.

Characters enclosed in quotation marks (example: "ABCD1234") are specified.

(2) Available characters

All ASCII code characters can be used in character strings.
The CPU module distinguishes between upper and lower case characters.

4
(3) Number of specified characters
A string from the specified character to the NUL code (00H) is one unit.
Note that, however, up to 32 characters can be specified for an instruction using a character string, such as

$MOV.

6
7
8

9.13 Constants
9.13.4 Character string (" ")

9 - 83

9.14 Convenient Usage of Devices
When multiple programs are executed in the CPU module, each program can be executed independently by specifying
an internal user device as a local device.
Devices of the CPU module are classified into the following two types:
• Global device that can be shared by multiple programs that are being executed.
• Local device that is used independently for each program.

9.14.1 Global device
Programs being executed in the CPU module can share the global device.
Global device data are stored in the device memory of the CPU module, and can be shared by all programs.
CPU module
Global device can be shared by the programs that are being executed.
Program A

Device memory

M0
M0

Y12
M0 ON/OFF data

Program B
M0
Y11
M0 ON/OFF data

Figure 9.97 Using a global device

9 - 84

Internal relay
ON/OFF

CHAPTER9 DEVICES

9
●

All of the devices that have not been set as local devices (

●

For execution of multiple programs, the range to be shared by all programs and the range to be used independently by
each program (

Section 9.14.2) are global devices.

Section 9.14.2) must be specified in advance.

Example: Internal relay
M0 Shared by all programs
Used in program A

The range must be specified
for each program.

Used in program B
Used in program C

Figure 9.98 Range specification for a device

6
9.14.2 Local device

Note9.6

The local device is a device that can be used independently for each program.Note1
Using local devices allows programming of multiple independently-executed programs without considering other
programs.

Note that local device data can be stored in the standard RAM and a memory card (SRAM) only.
CPU module
9.14 Convenient Usage of Devices
9.14.2 Local device

If M7000 and higher portion is set as a local device, it can be separately used for each
program that is executing M7000 and higher portion.
Standard RAM/memory card
Program A
For program A

M7000
Y12

M7000

Internal relay
ON/OFF

ON/OFF data of M7000

Program B

For program B

M7000
M7000

Y11

Internal relay
ON/OFF

ON/OFF data of M7000

Figure 9.99 Using local devices

Note1

Note9.6

Universal

For the Q00UJCPU, local devices cannot be used.

9 - 85

(1) Devices that can be used as local devices
The following devices can be used as local devices.
• Internal relay (M)
• Edge relay (V)
• Timer (T, ST)
• Counter (C)
• Data register (D)
Note9.7Note1

• Index register (Z)

(2) Saving and restoring a local device file
When some programs use a local device, respective local device file data in the standard RAM or a memory card
(SRAM) are exchanged with the device memory data of the CPU module after execution of each program.
For this reason, the scan time increases by the time spent for data exchange.

Sequence program

Program A
Restored

Program B
Saved

Restored

Program C
Saved

Local device

For
program A

For
program B

For
program C

Restored

Figure 9.100 Saving and restoring local device files

Remark
1.

There are some instructions for which a local device cannot be specified.
For details, refer to the pages describing devices available for each instruction in the following manual.
QCPU Programming Manual (Common Instructions)

For the concept of the number of words used for the local devices, refer to Section 9.2.

Note1

Note9.7

Universal

When using the index register as a local device for the Q02UCPU, Q03UDCPU, Q04UDHCPU, Q06UDHCPU,
Q13UDHCPU, Q26UDHCPU, and Built-in Ethernet port QCPU, check the versions of the CPU module and GX
Developer. (

9 - 86

Appendix 2)

CHAPTER9 DEVICES

(3) Local device setting
(a) Setting the local device range

In the Device tab of the PLC parameter dialog box, set the range that is used as a local device.

3
4
5
6
7
Figure 9.101 Device

Note that the local device range is common to all programs, and cannot be changed for each program.
For example, if a local device range is specified as M0 to M100, this range setting applies to all programs that

Program A

Program B

Program C

Local
device

9.14 Convenient Usage of Devices
9.14.2 Local device

use the local device.

Locla device
range is
common to all
programs.

M100
Figure 9.102 Local device range

●

The 32-bit index modification range must not overlap with the local device setting range of the index register.
If overlapped, 32-bit index modification values will be written over the local device values.

●

When CPU module parameters which contains local device setting of the index register are read out from the GX
Developer that does not support the setting, all of the index register data will be read out as global device data.

9 - 87

(b) Setting the drive and file name
After setting the local device range, set a memory for storing the local device file and a file name in the PLC file
tab of the PLC parameter dialog box.

Figure 9.103 PLC file

[Write to PLC] in GX Developer.

Figure 9.104 Device memory writing

9 - 88

CHAPTER9 DEVICES

9
●

If the size setting of the local device in the standard RAM is changed with a sampling trace file stored in the standard
RAM, the sampling trace file is cleared.
To save the trace results in your personal computer, perform the following operations.
1) Click the

Trace result PLC read

personal computer. (

●

Section 6.14(5)(e))

2) Click the

Trace result

3) Click the

Create CSV file

button on the Sampling trace dialog box to read the trace result into the

button to display the trace result.
button to store the trace results in CSV format.

All of the devices that have not been set as local devices are global devices.

5
(4) Setting of whether to use a local device (for each program)

Note9.8Note1

Use of the local device can be set for each program, and this function can reduce the scan time.
Also, since the area for saving and restoring data is not required for the programs not using a local device, the

local device file size can be reduced.
Program execution
Program A

Local device file (.QDL)

Save/Restore

For program A

Program B

tore
ve/Res

For program C
ore

est

e/R

Sav

Scan time decreases because saving
/restoring process is not performed.

9.14 Convenient Usage of Devices
9.14.2 Local device

Program C

File size can be reduced since the saving or
restoring area for program B is not created.

Figure 9.105 Save area configuration of a local device file

Note1

Note9.8

Universal

For setting a local device for each program in the Q02UCPU, Q03UDCPU, Q04UDHCPU, Q06UDHCPU,
Q13UDHCPU, and Q26UDHCPU, check the versions of the CPU module and GX Developer. (

Appendix 2)

9 - 89

(a) Setting method
In addition to the setting in (3) in this section, set the following.
Select the File usability setting button in the Program tab of the PLC parameter dialog box, and specify the
programs that use the local device.

Click the
File usability setting button.

Figure 9.106 File usability setting dialog box

(b) Precautions
1) Change of the local device
Do not change or refer to the local device in a program for which the local device is set to "Not used".
Even if the local device is changed in such a program, the changed data will not be held.

2) Conditions for creating a local device file
Creation of a local device file depends on the PLC parameter settings.
Table9.13 shows the conditions for creating a local device file.
Table9.13 Conditions for creating a local device file
PLC parameter setting
PLC file setting

Device setting*1
Set

Set
Not set

Set
Not set
Not set

File usability setting

File creation

Error detection

Use PLC file setting

Not used

Use PLC file setting

Not used

Use PLC file setting

PARAMETER ERROR (error code: 3000)

Not used

Use PLC file setting

Not used

: Created,

*1: Indicates the local device range setting in the Device tab.

9 - 90

: Not created

CHAPTER9 DEVICES

(5) Using the local device corresponding to the file where a subroutine program is
stored
When executing a subroutine program, you can utilize the local device corresponding to the file where the
subroutine program is stored.

9
2

Use of the relevant local device is set by ON/OFF of SM776.

Table9.14 Local device switching by ON/OFF of the special relay (SM776)
SM776

Operation

OFF

Perform operations with the local device that corresponds to the source file of the subroutine program.

Perform operations with the local device that corresponds to the file where the subroutine program is stored.

4
5

(a) When SM776 is off
File name: DEF
(Stand-by type program)

File name: ABC
X0
CALL P100

Execution of subroutine
program

P100

X2
Subroutine
program

INCP D0

RET

END

Local device
writing/reading

Local device area for
file name, DEF

9.14 Convenient Usage of Devices
9.14.2 Local device

Local device area for
file name, ABC

Figure 9.107 When SM776 is off

(b) When SM776 is on
File name: DEF
(Stand-by type program)

File name: ABC
X0
CALL P100

Execution of subroutine
program

P100

X2
INCP D0
Local device
writing/reading

Subroutine
program
RET

END

Local device area for
file name, ABC

Local device area for
file name, DEF
Figure 9.108 When SM776 is on

9 - 91

(c) Precautions
• When SM776 is on, local device data are read out when a subroutine program is called, and the data are
saved after execution of the RET instruction.
Because of this, the scan time is increased if one subroutine program is executed with SM776 set to on.
• The on/off status of SM776 is set for each CPU module.
It cannot be set for each file.
• If the on/off status of SM776 is changed during sequence program execution, control is implemented
according to the information after the change.

Remark
For details of SM776, refer to CHAPTER 12.

9 - 92

CHAPTER9 DEVICES

(6) When executing an interrupt/fixed scan execution type program
When executing an interrupt/fixed scan execution type program, you can utilize the local device corresponding to
the file where the program is stored.

Use of the relevant local device is set by ON/OFF of SM777. *1
*1: The index register set as the local device uses the local device area for the program executed before the interrupt/fixed
scan execution type program, regardless of the on/off status of SM777.

Table9.15 Local device switching by ON/OFF of the special relay (SM777)
SM777
OFF
ON

Operation
Perform operations with the local device that corresponds to the program executed before the interrupt/fixed scan
execution type program.
Perform operations with the local device that corresponds to the program file where the interrupt/fixed scan execution

type program is stored.

6
(a) When SM777 is off

X0
Interrupt occurred

DECP D1
X2
INCP

File name: DEF
(Stand-by type program)

File name: ABC

Execution of
interrupt program

Interrupt program

IRET
9.14 Convenient Usage of Devices
9.14.2 Local device

END

Local device area for
file name, ABC

Local device
writing/reading

Local device area for
file name, DEF

Figure 9.109 When SM777 is off

(b) When SM777 is on
File name: DEF
(Stand-by type program)

File name: ABC
X0
Interrupt occurred

DECP D1
X2
INCP

Execution of
interrupt program

Interrupt
program
IRET

END

Local device area for
file name, ABC

Local device
writing/reading

Local device area for
file name, DEF

Figure 9.110 When SM777 is on

9 - 93

(c) Precautions
• When SM777 is on, local device data are read out before execution of an interrupt/fixed scan execution
type program, and the data are saved after execution of the IRET instruction.
Because of this, the scan time is increased if one interrupt/fixed scan execution type program is executed
with SM777 set to on.
• The on/off status of SM777 is set for each CPU module.
It cannot be set for each file.
• If the on/off status of SM777 is changed during sequence program execution, control is implemented
according to the information after the change.

Remark
For details of SM777, refer to CHAPTER 12.

(7) Clearing local device data
Local device data is cleared by either of the following:
• When the CPU module is powered off and then on or is reset
• When the CPU module status is changed from STOP to RUN
Local device data cannot be cleared from GX Developer.

9 - 94

CHAPTER10 CPU MODULE PROCESSING TIME

This chapter describes the CPU module processing time.

10.1 Scan Time

This section describes the scan time structures and CPU module processing time.

10.1.1 Scan time structure

A CPU module sequentially performs the following processing in the RUN status.
Scan time is the time required for all processing and executions to be performed.

Processing
in the RUN status

Program check

I/O refresh time
Section 10.1.2(1))
(

I/O refresh

Execution of the DUTY instruction in END processing
(no execution when the DUTY instruction is not used)

Instruction execution time in END processing

Section 10.1.2(2))

(

Program execution

Instruction execution time
End the program?*1

Section 10.1.2(3))

(

YES

10.1 Scan Time
10.1.1 Scan time structure

Refresh via CC-Link IE controller network
Module refresh time
Refresh via CC-Link

(

Section 10.1.2(4))

Refresh by the intelligent function module
parameters set in GX Configurator

Common END processing time

Refresh via MELSECNET/H

Scan time

Calendar update, error clear
Function execution time
in END processing
Device data latch processing

Service processing

(

Section 10.1.2(5))

Service processing time
(
Section 10.1.2(6) )

Processing during the constant scan waiting time
(no processing when the constant scan time is not set)

WDT reset, scan time calculation
Common processing time
(
STOP/PAUSE status
STOP/PAUSE
processing

Section 10.1.2(7))

Operating status check
RUN status

Figure 10.1 Scan time structure
*1: End of a program indicates the timing when the END, GOEND, FEND, or STOP instruction is executed.

10 - 1

(1) How to check scan time
The CPU module measures current, minimum, and maximum values of the scan time.
The scan time can be checked by monitoring the special register (SD520, SD521, and SD524 to SD527).
Accuracy of each stored scan time is

0.1ms.

Current value

SD520

SD521

Minimum value

SD524

SD525

Maximum value

SD526

SD527
Stores the scan time of 1ms or less (unit: s).
Stores the scan time. (unit: ms).
Figure 10.2 Scan time storage location

Example If the stored values in SD520 and SD521 are 3 and 400 respectively, the scan time is 3.4ms.

10.1.2 Time required for each processing included in scan time
This section describes how to calculate the processing and execution time described in Section 10.1.1.

(1) I/O refresh time
The I/O refresh time is time required for refreshing I/O data to/from the following modules mounted on
the main base unit and extension base units.
• Input module
• Output module
• Intelligent function module
Calculation method
Use the following expression to calculate the I/O refresh time.
(I/O refresh time) = (number of input points/16)

N1 + (number of output points/16)

For N1 and N2, refer to Table10.1.
Table10.1 I/O refresh time
CPU module

B, Q3
N1

SB, Q3

RB, Q3

B, Q6

RB
N2

Q00UJCPU, Q00UCPU, Q01UCPU

1.8

1.0

2.6

1.9

Q02UCPU

1.5

1.1

2.4

1.9

1.5

1.0

2.3

1.8

Q03UDCPU, Q04UDHCPU,
Q06UDHCPU, Q10UDHCPU,
Q13UDHCPU, Q20UDHCPU,
Q26UDHCPU, Q03UDECPU,
Q04UDEHCPU, Q06UDEHCPU,
Q10UDEHCPU, Q13UDEHCPU,
Q20UDEHCPU, Q26UDEHCPU

10 - 2

CHAPTER10 CPU MODULE PROCESSING TIME

(2) Instruction execution time in END processing
This is the processing time of the DUTY instruction in END processing.
The user timing clock (SM420 to 424 and SM430 to SM434) specified with the DUTY instruction is turned on/off
during the END processing.

Table10.2 Instruction execution time in END processing
CPU module

Processing time in END processing
When set to 1

When set to 5

Q00UJCPU, Q00UCPU, Q01UCPU

0.0120ms

0.0140ms

Q02UCPU

0.0050ms

0.0550ms

Q03UDCPU, Q03UDECPU

0.0043ms

0.0046ms

0.0041ms

0.0045ms

Q04UDHCPU, Q06UDHCPU, Q10UDHCPU, Q13UDHCPU,
Q20UDHCPU, Q26UDHCPU, Q04UDEHCPU, Q06UDEHCPU,

Q10UDEHCPU, Q13UDEHCPU, Q20UDEHCPU, Q26UDEHCPU

6
(3) Instruction execution time
The instruction execution time is the time required for all instructions used in the program to be executed.

7
8

Remark
For the processing time required for each instruction, refer to the following.
QCPU Programming Manual (Common Instructions)

10.1 Scan Time
10.1.2 Time required for each processing included in scan time

10 - 3

(a) Overhead time at execution of interrupt and fixed scan execution type programs
When calculating instruction execution time, add the overhead time given in the following table to the instruction execution time, which is described in (3).
Two kinds of overhead time (pre-start and program-end) need to be added to interrupt programs.
Table10.3 Pre-start overhead time for interrupt programs

CPU module

Fixed scan interrupt

Multiple CPU synchronous

(I28 to I31)

interrupt (I45)

Without
high-speed
start

With highspeed start

Without
high-speed
start

Interrupt*1 (I0 to I15) from QI60 or
interrupt (I50 to I127) from the
intelligent function module

With high-

Without high-

With high-speed

speed start

start

Q00UJCPU, Q00UCPU, Q01UCPU

---

Q02UCPU

---

Q03UDCPU, Q03UDECPU

Q04UDHCPU, Q06UDHCPU,
Q10UDHCPU, Q13UDHCPU,
Q20UDHCPU, Q26UDHCPU,
Q04UDEHCPU, Q06UDEHCPU,
Q10UDEHCPU, Q13UDEHCPU,
Q20UDEHCPU, Q26UDEHCPU
*1: Indicates the value when the QI60 is mounted on the slot 0 of the main base unit.

Table10.4 Program-end overhead time for interrupt programs
CPU module

Without highspeed start

With high-speed
start

Q00UJCPU, Q00UCPU, Q01UCPU

Q02UCPU

Q03UDCPU, Q03UDECPU

Q04UDHCPU, Q06UDHCPU, Q10UDHCPU, Q13UDHCPU, Q20UDHCPU,
Q26UDHCPU, Q04UDEHCPU, Q06UDEHCPU, Q10UDEHCPU, Q13UDEHCPU,
Q20UDEHCPU, Q26UDEHCPU

Table10.5 Overhead time for fixed scan execution type programs
CPU module

Without highspeed start

With high-speed
start

Q00UJCPU, Q00UCPU, Q01UCPU

Q02UCPU

Q03UDCPU, Q03UDECPU

Q04UDHCPU, Q06UDHCPU, Q10UDHCPU, Q13UDHCPU, Q20UDHCPU,
Q26UDHCPU, Q04UDEHCPU, Q06UDEHCPU, Q10UDEHCPU, Q13UDEHCPU,
Q20UDEHCPU, Q26UDEHCPU

10 - 4

CHAPTER10 CPU MODULE PROCESSING TIME

1) Overhead time when local devices in the interrupt program are enabled
When SM777 (Enable/disable local device in interrupt program) is turned on, the time given in Table10.6 and

Table10.7 will be added to the overhead time given in Table10.3 and Table10.4.

Each n, N1, N2, and N3 in the table indicates the following:
• n: Number of local device points (unit: K words)
• N1: Number of devices that specified a local device

• N2: Number of word device points that specified a local device
• N3: Number of bit device points that specified a local device

Table10.6 When a local device file in the standard RAM is used
CPU module

Additional time to the pre-start overhead time
for interrupt programs (Table10.3)

Additional time to the program-end overhead
time for interrupt programs (Table10.4)

Q00UCPU, Q01UCPU

(13.2

N1) + (0.22

(N2 + (N3

16))) + 210

N1) + (0.23

(N2 + (N3

16))) + 30

Q02UCPU

(13.2

N1) + (0.22

(N2 + (N3

16))) + 210

N1) + (0.22

(N2 + (N3

16))) + 30

Q03UDCPU, Q03UDECPU

N1) + (0.22

(N2 + (N3

16))) + 80

N1) + (0.22

(N2 + (N3

16))) + 20

N1) + (0.10

(N2 + (N3

16))) + 80

N1) + (0.10

(N2 + (N3

16))) + 20

Q04UDHCPU, Q06UDHCPU,
Q10UDHCPU, Q13UDHCPU,
Q20UDHCPU, Q26UDHCPU,
Q04UDEHCPU, Q06UDEHCPU,
Q10UDEHCPU, Q13UDEHCPU,
Q20UDEHCPU, Q26UDEHCPU

8
Table10.7 When a local device file in a SRAM card is used
CPU module

Additional time to the program-end overhead
time for interrupt programs (Table 10.4)

Q02UCPU

(16

N1) + (0.43

(N2 + (N3

16))) + 260

(16

N1) + (0.43

(N2 + (N3

16))) + 60

Q03UDCPU, Q03UDECPU

(12

N1) + (0.43

(N2 + (N3

16))) + 100

(12

N1) + (0.43

(N2 + (N3

16))) + 20

(12

N1) + (0.40

(N2 + (N3

16))) + 100

(12

N1) + (0.40

(N2 + (N3

16))) + 20

Q04UDHCPU, Q06UDHCPU,
Q10UDHCPU, Q13UDHCPU,
Q20UDHCPU, Q26UDHCPU,
Q04UDEHCPU, Q06UDEHCPU,
Q10UDEHCPU, Q13UDEHCPU,
Q20UDEHCPU, Q26UDEHCPU

10 - 5

10.1 Scan Time
10.1.2 Time required for each processing included in scan time

Additional time to the pre-start overhead time
for interrupt programs (Table 10.3)

(4) Module refresh time
Module refresh time is the total time required for the CPU module to refresh data with CC-Link IE controller network, MELSECNET/H, and CC-Link modules.
(a) Refresh via CC-Link IE controller network
This is the time required for refreshing data between link devices in a CC-Link IE controller network
module and devices in the CPU module.
(b) Refresh via MELSECNET/H
This is the time required for refreshing data between link devices in a MELSECNET/H network
module and devices in the CPU module.
(c) Auto refresh via CC-Link
This is the time required for refreshing data between a CC-Link system master/local module and
CPU module.

Remark
For each refresh time, refer to the following.
Reference manual of each network module

10 - 6

CHAPTER10 CPU MODULE PROCESSING TIME

(d) Auto refresh with an intelligent function module
This is the time required for refreshing data between the buffer memory of an intelligent function module and

devices in the CPU module.
Use intelligent function module utility package (GX Configurator) for auto refresh settings.

Calculation method

Use the following expression to calculate the auto refresh time with an intelligent function module.

(Refresh time) = KN1 + KN2

(number of refresh points)

For KN1 and KN2, use the values given in Table10.8 and Table10.9.
Table10.8 When an intelligent function module is mounted on the main base unit
CPU module

KN1

Q00UJCPU, Q00UCPU, Q01UCPU

96.3

KN2
s

6.7

Q02UCPU

Q03UDCPU, Q03UDECPU

Q04UDHCPU, Q06UDHCPU, Q10UDHCPU, Q13UDHCPU, Q20UDHCPU,
Q26UDHCPU, Q04UDEHCPU, Q06UDEHCPU, Q10UDEHCPU, Q13UDEHCPU,
Q20UDEHCPU, Q26UDEHCPU

Table10.9 When an intelligent function module is mounted on the extension base unit
CPU module

KN1
79.7

Q00UCPU, Q01UCPU

79.7

KN2
s

8.9

8.1

Q02UCPU

7.0

Q03UDCPU, Q03UDECPU

6.0

Q04UDHCPU, Q06UDHCPU, Q10UDHCPU, Q13UDHCPU, Q20UDHCPU,
Q26UDHCPU, Q04UDEHCPU, Q06UDEHCPU, Q10UDEHCPU, Q13UDEHCPU,

Q20UDEHCPU, Q26UDEHCPU

Example When the number of auto refresh points for the analog-digital converter module (Q64AD)
is 4 points (when the module is mounted on the Q26UDHCPU main base unit)
0.029 (ms) = 0.005 + 0.006

10 - 7

10.1 Scan Time
10.1.2 Time required for each processing included in scan time

Q00UJCPU

(5) Function execution time in END processing
This is the time required for updating calender or clearing error in END processing.

(a) Calendar update processing time
When the clock data set request (SM210 changes from off to on) or the clock data read request
(SM213 turns on) is issued, the processing time for changing or reading the clock data is required in
END processing.
Table10.10 Calendar update processing time
Processing time in END processing
CPU module

When the clock data set

When the clock data read

request is issued

Q00UJCPU, Q00UCPU, Q01UCPU

0.040ms

0.019ms

Q02UCPU

0.040ms

0.019ms

0.011ms

0.004ms

Q03UDCPU, Q04UDHCPU, Q06UDHCPU, Q10UDHCPU, Q13UDHCPU,
Q20UDHCPU, Q26UDHCPU, Q03UDECPU, Q04UDEHCPU,
Q06UDEHCPU, Q10UDEHCPU, Q13UDEHCPU, Q20UDEHCPU,
Q26UDEHCPU

(b) Error clear processing time
Upon the rising edge (changes from off to on) of SM50 (Error reset), the processing time for clearing the continuation error stored in SD50 is required.
Table10.11 Error clear processing time
Processing time in END processing
CPU module

When the error is cleared
(the one detected by the

When the error is cleared

annunciator)
Q00UJCPU, Q00UCPU, Q01UCPU

0.185ms

Q02UCPU

0.180ms

0.175ms

Q03UDCPU, Q03UDECPU

0.068ms

0.062ms

0.065ms

0.062ms

Q04UDHCPU, Q06UDHCPU, Q10UDHCPU, Q13UDHCPU,
Q20UDHCPU, Q26UDHCPU, Q04UDEHCPU, Q06UDEHCPU,
Q10UDEHCPU, Q13UDEHCPU, Q20UDEHCPU, Q26UDEHCPU

10 - 8

CHAPTER10 CPU MODULE PROCESSING TIME

(6) Device data latch processing time
When the latch range is set in the Device tab of the PLC parameter dialog box*1 *2 *3, the processing

time shown in Table10.12 is required.
Each N1, N2, and N3 in the table indicates the following:

• N1: Number of devices specified to be latched (Count the latch range (1) and the latch
range (2) as different devices.)
• N2: Number of bit device points specified to be latched

• N3: Number of word device points specified to be latched
Table10.12 Processing time when the latch range is set

CPU module

Processing time

Q00UJCPU, Q00UCPU, Q01UCPU

(4.4

N1) + (0.12

(N2

16 + N3))

Q02UCPU

(4.0

N1) + (0.12

(N2

16 + N3))

Q03UDCPU, Q03UDECPU

(3.0

N1) + (0.12

(N2

16 + N3))

(3.0

N1) + (0.05

(N2

16 + N3))

Q04UDHCPU, Q06UDHCPU, Q10UDHCPU, Q13UDHCPU, Q20UDHCPU,
Q26UDHCPU, Q04UDEHCPU, Q06UDEHCPU, Q10UDEHCPU, Q13UDEHCPU,
Q20UDEHCPU, Q26UDEHCPU
*1: When setting the latch range of the timer (T), retentive timer (ST), and counter (C), one point for word device and two points for bit device
are occupied per point.
*2: The case where the points are set for the latch relay (L) is included.
*3: The scan time will not increase if the latch range is set for the file register (R, ZR), extended data register (D), or extended link register
(W).

• Move data to be latched to the file register.
• Store device data that is updated less frequently to the standard ROM with the SP.DEVST instruction. (The device
data stored in the standard ROM can be read with the S(P).DEVLD instruction.)
QCPU Programming Manual (Common Instructions)

10 - 9

10.1 Scan Time
10.1.2 Time required for each processing included in scan time

To shorten the scan time, minimize the number of latch points.
The number of latch points can be reduced by performing the following.

(7) Service processing time
Service processing is the communication processing with GX Developer and external devices.
When monitoring device data, reading programs, and setting monitor conditions in GX Developer, the
processing time shown in Table10.13 or Table10.14 is required.
Table10.13 Processing time to monitor device data and read programs

Processing time*1
Monitoring device
data (Data register: 32
points)

CPU module

Reading programs
(10K step)

Q00UJCPU, Q00UCPU, Q01UCPU

1.60ms

3.70ms

Q02UCPU

1.00ms

1.55ms

0.35ms

0.95ms

Q03UDCPU, Q04UDHCPU, Q06UDHCPU, Q10UDHCPU, Q13UDHCPU,
Q20UDHCPU, Q26UDHCPU, Q03UDECPU, Q04UDEHCPU, Q06UDEHCPU,
Q10UDEHCPU, Q13UDEHCPU, Q20UDEHCPU, Q26UDEHCPU
*1: The time in the table is for the case where the service processing count is set to one.

Table10.14 Processing time to set monitor conditions

Processing time
CPU module

Specified step match

Q02UCPU

Specified device
match

0.03ms

0.04ms

0.01ms

0.03ms

Q03UDCPU, Q04UDHCPU, Q06UDHCPU, Q10UDHCPU, Q13UDHCPU,
Q20UDHCPU, Q26UDHCPU, Q03UDECPU, Q04UDEHCPU, Q06UDEHCPU,
Q10UDEHCPU, Q13UDEHCPU, Q20UDEHCPU, Q26UDEHCPU

(8) Common processing time
The CPU module performs common processing by the system. The common processing time shown in
Table10.15 is required.
Table10.15 Common processing time

CPU module

Processing time

Q00UJCPU, Q00UCPU, Q01UCPU

0.25ms

Q02UCPU

0.17ms

Q03UDCPU

0.12ms

Q04UDHCPU, Q06UDHCPU, Q10UDHCPU, Q13UDHCPU, Q20UDHCPU,
Q26UDHCPU
Q03UDECPU

0.09ms
0.21ms

Q04UDEHCPU, Q06UDEHCPU, Q10UDEHCPU, Q13UDEHCPU,
Q20UDEHCPU, Q26UDEHCPU

0.17ms

(9) Multiple CPU high speed transmission processing time
This is the processing time required for data transmission between the CPU modules when the multiple CPU high
speed transmission function is used.
For the multiple CPU high speed transmission processing time, refer to the following.

QCPU User's Manual (Multiple CPU System)

10 - 10

CHAPTER10 CPU MODULE PROCESSING TIME

10.1.3 Factors that increase the scan time

When executing any of the functions or operations described in this section, add the given processing time
to the time value calculated in Section 10.1.2.

(1) Sampling trace
When the sampling trace function (

Section 6.14) is executed, the processing time shown in

Table10.16 is required.
Table10.16 Processing time (when 50 points of the internal relay (for bit device) and 50 points of the data register (for word device)
are set as sampling trace data)

CPU module

Standard RAM

0.12ms

Q02UCPU

0.09ms

Q03UDCPU, Q03UDECPU

0.07ms

Q04UDHCPU, Q06UDHCPU, Q10UDHCPU,
Q04UDEHCPU, Q06UDEHCPU, Q10UDEHCPU,

Processing time

Q00UCPU, Q01UCPU

Q13UDHCPU, Q20UDHCPU, Q26UDHCPU,

0.06ms

Q13UDEHCPU, Q20UDEHCPU, Q26UDEHCPU

SRAM card

Q02UCPU

0.16ms

Q03UDCPU, Q03UDECPU

0.08ms

Q04UDHCPU, Q06UDHCPU, Q10UDHCPU,
Q13UDHCPU, Q20UDHCPU, Q26UDHCPU,
Q04UDEHCPU, Q06UDEHCPU, Q10UDEHCPU,

0.06ms

Q13UDEHCPU, Q20UDEHCPU, Q26UDEHCPU

10.1 Scan Time
10.1.3 Factors that increase the scan time

10 - 11

(2) Use of local devices
When local devices are used, the processing time shown in Table10.17 is required.
Each n, N1, N2, and N3 in the table indicates the following:
• n: Number of programs using a local device*1
• N1: Number of devices that specified a local device
• N2: Number of word device points that specified a local device
• N3: Number of bit device points that specified a local device
Table10.17 Processing time (when local devices are used)

CPU module
Q00UCPU, Q01UCPU
Q02UCPU

Standard RAM

Processing time
((12.5

N1) + (0.24

(N2 + (N3

16))) + 170)

((12

N1) + (0.22

(N2 + (N3

16))) + 140)

((8

N1) + (0.22

(N2 + (N3

16))) + 50)

((8

N1) + (0.10

(N2 + (N3

16))) + 50)

Q02UCPU

((16

N1) + (0.43

(N2 + (N3

16))) + 160)

Q03UDCPU, Q03UDECPU

((12

N1) + (0.43

(N2 + (N3

16))) + 60)

((12

N1) + (0.40

(N2 + (N3

16))) + 60)

Q03UDCPU, Q03UDECPU

Q04UDHCPU, Q06UDHCPU, Q10UDHCPU,
Q13UDHCPU, Q20UDHCPU, Q26UDHCPU,
Q04UDEHCPU, Q06UDEHCPU, Q10UDEHCPU,
Q13UDEHCPU, Q20UDEHCPU, Q26UDEHCPU

SRAM card

Q04UDHCPU, Q06UDHCPU, Q10UDHCPU,
Q13UDHCPU, Q20UDHCPU, Q26UDHCPU,
Q04UDEHCPU, Q06UDEHCPU, Q10UDEHCPU,
Q13UDEHCPU, Q20UDEHCPU, Q26UDEHCPU

*1: If the serial number (first five digits) of the Universal model QCPU is "10011" or earlier, "n" indicates the number of executed programs.

10 - 12

CHAPTER10 CPU MODULE PROCESSING TIME

(a) When local devices in a subroutine program are enabled
When SM776 (Enable/disable local device at CALL) is turned on, the processing time shown in Table10.18 or

Table10.19 is required for each subroutine call.

Each n, N1, N2, and N3 in the table indicates the following:
• n: Number of local device points (unit: K words)

• N1: Number of devices that specified a local device
• N2: Number of word device points that specified a local device
• N3: Number of bit device points that specified a local device

Table10.18 Processing time (when a local device file in the standard RAM is used)

CPU module

Processing time when a
subroutine program in the same
file is called

Processing time when a subroutine program
in a different file is called

Q00UCPU, Q01UCPU

0.00

(24

N1) + (0.73

(N2 + (N3

16))) + 280

Q02UCPU

0.00

(24

N1) + (0.44

(N2 + (N3

16))) + 280

Q03UDCPU, Q03UDECPU

0.00

(16

N1) + (0.44

(N2 + (N3

6))) + 100

0.00

(16

N1) + (0.20

(N2 + (N3

16))) + 100

5
6

Q04UDHCPU, Q06UDHCPU,
Q10UDHCPU, Q13UDHCPU,
Q20UDHCPU, Q26UDHCPU,
Q04UDEHCPU, Q06UDEHCPU,

Q10UDEHCPU, Q13UDEHCPU,

Q20UDEHCPU, Q26UDEHCPU

Table10.19 Processing time (when a local device file in a SRAM card is used)

Processing time when a
subroutine program in the same
file is called

Processing time when a subroutine program
in a different file is called

Q02UCPU

0.00

(32

N1) + (0.86

(N2 + (N3

16))) + 320

Q03UDCPU, Q03UDECPU

0.00

(24

N1) + (0.86

(N2 + (N3

16))) + 120

0.00

(24

N1) + (0.80

(N2 + (N3

16))) + 120

Q04UDHCPU, Q06UDHCPU,
Q10UDHCPU, Q13UDHCPU,
Q20UDHCPU, Q26UDHCPU,
Q04UDEHCPU, Q06UDEHCPU,
Q10UDEHCPU, Q13UDEHCPU,
Q20UDEHCPU, Q26UDEHCPU

10 - 13

10.1 Scan Time
10.1.3 Factors that increase the scan time

CPU module

(3) Execution of multiple programs
When multiple programs are executed, the processing time shown in Table10.20 is required for each program.
Table10.20 Processing time for each program (when multiple programs are executed)

CPU module

Processing time

Q00UJCPU, Q00UCPU, Q01UCPU

0.053

n*1 ms

Q02UCPU

0.04

n*1 ms

Q03UDCPU, Q03UDECPU

0.02

n*1 ms

0.02

n*1 ms

Q04UDHCPU, Q06UDHCPU, Q10UDHCPU, Q13UDHCPU, Q20UDHCPU,
Q26UDHCPU, Q04UDEHCPU, Q06UDEHCPU, Q10UDEHCPU, Q13UDEHCPU,
Q20UDEHCPU, Q26UDEHCPU
*1: "n" indicates the number of program files.

(4) Removal and insertion of a memory card
When a memory card is removed or inserted, the processing time shown inTable10.21 is required only for one
scan where a memory card is removed or inserted.
Table10.21 Processing time (when a memory card is removed or inserted)

Processing time
CPU module

When a memory
card is inserted

When a memory
card is removed

0.7ms

0.2ms

0.6ms

0.1ms

Q02UCPU
Q03UDCPU, Q04UDHCPU, Q06UDHCPU, Q10UDHCPU, Q13UDHCPU,
Q20UDHCPU, Q26UDHCPU, Q03UDECPU, Q04UDEHCPU, Q06UDEHCPU,
Q10UDEHCPU, Q13UDEHCPU, Q20UDEHCPU, Q26UDEHCPU

(5) Use of the file register
When “Use the same file name as the program.” is selected in the PLC file tab of the PLC parameter

dialog box, the processing time shown in Table10.22 is required.
When “Use the following file.” is selected, the scan time will not be increased.
Table10.22 Processing time (when the file register is used)

CPU module

Standard RAM

Processing time

Q00UCPU, Q01UCPU

0.135ms

Q02UCPU

0.082ms

Q03UDCPU, Q03UDECPU

0.043ms

Q04UDHCPU, Q06UDHCPU, Q10UDHCPU, Q13UDHCPU, Q20UDHCPU,
Q26UDHCPU, Q04UDEHCPU, Q06UDEHCPU, Q10UDEHCPU,

0.041ms

Q13UDEHCPU, Q20UDEHCPU, Q26UDEHCPU

SRAM card

Q02UCPU

0.11

n*1 ms

Q03UDCPU, Q03UDECPU

0.06

n*1 ms

0.06

n*1 ms

Q04UDHCPU, Q06UDHCPU, Q10UDHCPU, Q13UDHCPU, Q20UDHCPU,
Q26UDHCPU, Q04UDEHCPU, Q06UDEHCPU, Q10UDEHCPU,
Q13UDEHCPU, Q20UDEHCPU, Q26UDEHCPU

*1: "n" indicates the number of program files.

10 - 14

CHAPTER10 CPU MODULE PROCESSING TIME

(6) Online change
When data is written to the running CPU module, the processing time described below is required.
(a) Online change (ladder mode)
When a program in the running CPU module is changed in ladder mode, the processing time shown
in Table10.23 is required.*1

10
3

*1: The time in the table is for the case where the service processing count is set to one.

Table10.23 Proceccing time (online change (ladder mode))
Processing time
CPU module

The reserved area for online change

is not changed.

is re-set.

Q00UJCPU, Q00UCPU, Q01UCPU

Up to 2.1ms

Q02UCPU

Up to 1.3ms

Q03UDCPU, Q03UDECPU

Up to 1.0ms

Up to 0.7ms

5
6

Q04UDHCPU, Q06UDHCPU, Q10UDHCPU,
Q13UDHCPU, Q20UDHCPU, Q26UDHCPU,
Q04UDEHCPU, Q06UDEHCPU, Q10UDEHCPU,

Q13UDEHCPU, Q20UDEHCPU, Q26UDEHCPU

(b) Online change (files)
When a file is written to the running CPU module, the processing time shown in Table10.24 is
required. *1

Table10.24 Processing time (online change (files))
CPU module

Processing time
Scan time = 2ms

Scan time = 20ms

Q00UJCPU

Up to 4.00ms

Up to 6.20ms

Q00UCPU

Up to 3.50ms

Up to 5.80ms

Q01UCPU

Up to 3.50ms

Up to 5.60ms

Q02UCPU

Up to 4.80ms

Q03UDCPU, Q03UDECPU

Up to 3.75ms

Up to 3.70ms

Q04UDHCPU, Q06UDHCPU, Q10UDHCPU,
Q13UDHCPU, Q20UDHCPU, Q26UDHCPU,
Q04UDEHCPU, Q06UDEHCPU, Q10UDEHCPU,
Q13UDEHCPU, Q20UDEHCPU, Q26UDEHCPU

10 - 15

10.1 Scan Time
10.1.3 Factors that increase the scan time

*1: The time in the table is for the case where the service processing count is set to one.

(7) Non-group output status read
In multiple CPU systems, the scan time increases when “All CPUs can read all outputs” is selected in
the Multiple CPU settings screen of the PLC parameter dialog box.

The scan time increases
when this parameter is set.

Figure 10.3 Multiple CPU settings screen

(8) Scan time measurement
When the scan time is measured by GX Developer, the processing time shown in Table10.25 is required (
Section 6.13.3)
Table10.25 Processing time (when the scan time is measured)

CPU module

Processing time

Q00UJCPU, Q00UCPU, Q01UCPU

179.5 + 5.8

number of branch instructions

s*1

Q02UCPU

40.0 + 3.0

number of branch instructions

s*1

40.0 + 1.5

number of branch instructions

s*1

Q03UDCPU, Q04UDHCPU, Q06UDHCPU, Q10UDHCPU, Q13UDHCPU,
Q20UDHCPU, Q26UDHCPU, Q03UDECPU, Q04UDEHCPU, Q06UDEHCPU,
Q10UDEHCPU, Q13UDEHCPU, Q20UDEHCPU, Q26UDEHCPU
*1: The number of the branch instructions is a total of the following instructions, which are executed during the scan time measurement.
Pointer branch instruction

: CJ, SCJ, JMP

Subroutine program call instruction: CALL(P), FCALL(P), ECALL(P), EFCALL(P), XCALL(P), RET

10 - 16

CHAPTER10 CPU MODULE PROCESSING TIME

(9) Time taken to collect module errors
When using the module error collection, the scan time increases by the time found by the following calculation
formula.

Calculation formula
Collection time = N1 + N2

(Number of module errors collected in one scan)

The following table shows N1 and N2 values.

Table10.26 N1 values
Mounted base unit

CPU module

Main base unit

Extension base unit

Q00UJCPU

175 s

190 s

Q00UCPU, Q01UCPU

145 s

190 s

Q02UCPU

145 s

185 s

15 s

Q03UDCPU, Q04UDHCPU, Q06UDHCPU, Q10UDHCPU, Q13UDHCPU,
Q20UDHCPU, Q26UDHCPU, Q03UDECPU, Q04UDEHCPU, Q06UDEHCPU,
Q10UDEHCPU, Q13UDEHCPU, Q20UDEHCPU, Q26UDEHCPU

Mounted base unit
Extension base unit

Q00UJCPU, Q00UCPU, Q01UCPU

120 s

140 s

Q02UCPU

90 s

105 s

70 s

100 s

Q03UDCPU, Q04UDHCPU, Q06UDHCPU, Q10UDHCPU, Q13UDHCPU,
Q10UDEHCPU, Q13UDEHCPU, Q20UDEHCPU, Q26UDEHCPU

10 - 17

10.1 Scan Time
10.1.3 Factors that increase the scan time

Main base unit

Q20UDHCPU, Q26UDHCPU, Q03UDECPU, Q04UDEHCPU, Q06UDEHCPU,

6
7

Table10.27 N2 values
CPU module

(10)Batch transfer of data to the program memory
When data in the program cache memory is batch-transferred to the program memory by GX Developer, the processing time shown in Table10.28 is required.*1
*1: The time in the table is for the case where the service processing count is set to one.
Table10.28 Processing time (when data is batch-transferred to the program memory)
CPU module

Processing time
Scan time = 2ms

Scan time = 20ms

1.90ms

4.90ms

Q02UCPU

1.55ms

4.50ms

Q03UDCPU, Q03UDECPU

1.10ms

3.65ms

1.05ms

3.65ms

Q00UJCPU, Q00UCPU, Q01UCPU

Q04UDHCPU, Q06UDHCPU, Q10UDHCPU, Q13UDHCPU,
Q20UDHCPU, Q26UDHCPU, Q04UDEHCPU, Q06UDEHCPU,
Q10UDEHCPU, Q13UDEHCPU, Q20UDEHCPU, Q26UDEHCPU

(11) Diagnostics of the redundant power supply system
When the "Diagnose redundant power supply system." is selected on the PLC RAS tab of the PLC
parameter dialog box, the processing time shown in Table10.29 is required.
Table10.29 Processing time (when the diagnostics for the redundant power supply system is enabled)
Processing time
CPU module

With a power supply module

Without a power supply module

failure*1

Q00UCPU

125

165

Q01UCPU

125

135

Q02UCPU

Q03UDCPU, Q04UDHCPU, Q06UDHCPU, Q10UDHCPU,
Q13UDHCPU, Q20UDHCPU, Q26UDHCPU, Q03UDECPU,
Q04UDEHCPU, Q06UDEHCPU, Q10UDEHCPU, Q13UDEHCPU,
Q20UDEHCPU, Q26UDEHCPU
*1: A power supply module failure indicates any of the following.
The redundant power supply module has failed.
Power for the redundant power supply module is turned off.
The redundant power supply module is not mounted.

10 - 18

CHAPTER11 PROCEDURES FOR WRITING PROGRAM TO CPU MODULE

CHAPTER11 PROCEDURES FOR WRITING PROGRAM TO
CPU MODULE

1
2

This chapter describes procedures for writing a program created by GX Developer to the CPU module.

Remark
For procedures for starting the CPU module, refer to the following.
QCPU User's Manual (Hardware Design, Maintenance and Inspection)

4
5

11.1 Items to be Considered for Creating Programs

To create a program, the number of device points, size, and file name of the program must be
predetermined.

(1) Program size
Check whether the total size of programs and parameters are within the program size executable in
the CPU module used. (

Section 5.3.3)

Table11.1 provides the program size executable in each CPU module.
Table11.1 Program size
Program size
10K steps (40K bytes)

Q01UCPU

15K steps (60K bytes)

Q02UCPU

20K steps (80K bytes)

Q03UDCPU, Q03UDECPU

30K steps (120K bytes)

Q04UDHCPU, Q04UDEHCPU

40K steps (160K bytes)

Q06UDHCPU, Q06UDEHCPU

60K steps (240K bytes)

Q10UDHCPU, Q10UDEHCPU

100K steps (400K bytes)

Q13UDHCPU, Q13UDEHCPU

130K steps (520K bytes)

Q20UDHCPU, Q20UDEHCPU

200K steps (800K bytes)

Q26UDHCPU, Q26UDEHCPU

260K steps (1040K bytes)

Whether parameters are stored to the program memory, standard ROM, or memory card can be set.
If the program size above is required for only programs, store the parameters in the standard ROM or memory
card.

(2) Determining a unit for structuring the programs
When creating multiple programs, determine a unit (process/function) for structuring the programs.

(3) Setting the execution conditions for programs to be created
When executing multiple programs, set their execution conditions to each program. (

Section 2.3)

Without the setting, the programs cannot be executed.

11 - 1

11.1 Items to be Considered for Creating Programs

CPU module
Q00UJCPU, Q00UCPU

(4) Setting the applications of devices and the number of device points
Consider the applications of devices and the number of device points used in the program.
(

CHAPTER 9)

(5) Setting the initial device value
Set data necessary as an initial value to the device memory and the buffer memory of the intelligent
function module. (

Section 6.25)

(6) Setting boot operation
When storing a program to the memory card, execute the program after boot operation.
For boot operation, make the setting in the Boot file tab of the PLC parameter dialog box.
(

11 - 2

Section 5.1.8, Section 5.1.10)

CHAPTER11 PROCEDURES FOR WRITING PROGRAM TO CPU MODULE

11.2 Hardware Check

This section describes a procedure for checking hardware before writing a created program.
In the following procedure,

indicates an operation on the CPU module side.

Start

Start GX Developer and create a project.

GX Developer Version 8 Operating Manual

Connect the personal computer to which
GX Developer is installed to the CPU module.

Set the RUN/STOP/RESET switch to
STOP and power on the programmable
controller (the ERR. LED turns on).

Is the BAT. LED on?

6
7

YES

Check the special relays (SM51 and SM52)
and special registers (SD51 and SD52) and
replace the battery if required.

GX Developer Version 8 Operating Manual

Select [Online]
[Write to PLC]
"Program memory/Device memory" for
"Target memory" in GX Developer and
write the parameters and program
(Write the PLC parameters and program
with the same settings immediately after
the project was created by GX Developer).

GX Developer Version 8 Operating Manual

11.2 Hardware Check

Select [Online]
[Format PLC memory]
in GX Developer and format the program
memory.

11 - 3

Power off the programmable controller
and then on or reset the CPU module.

Set the RUN/STOP/RESET switch to RUN to
change the CPU module in the RUN status.

YES
Is the RUN LED on?
To Section 11.3
NO
YES
Is the ERR. LED off?

NO
Check the error cause in the System Monitor screen
displayed by selecting [Diagnostics]
[System
Monitor] in GX Developer or in the "PLC diagnostics"
screen and remove the error.

Please consult your local Mitsubishi
service center or representative,
explaining a detailed description of
the problem.
QCPU User's Manual
(Hardware Design, Maintenance and Inspection)

Figure 11.1 Hardware check flowchart

Remark
For installation and mounting procedures of the CPU module, refer to the following.
QCPU User's Manual (Hardware Design, Maintenance and Inspection)

11 - 4

CHAPTER11 PROCEDURES FOR WRITING PROGRAM TO CPU MODULE

11.3 Procedure for Writing One Program
This section describes a procedure for writing a program to the program memory. (

1
Section 5.1.2)

Follow the procedure below and then the procedure provided in Section 11.5 before storing the program in

the memory card for boot operation.
In the following procedure,

indicates an operation on the CPU module side.

Start

4
Start GX Developer.

GX Developer Version 8 Operating Manual

Set the project.

Change the number
of device points?

YES
Change the number of device points in the
Device tab of the PLC parameter dialog box.

8
Ladder (writing) screen
11.3 Procedure for Writing One Program

Create a program to be executed in the
CPU module.

GX Developer Version 8 Operating Manual

Use the initial device value?

YES
Set the device memory.

Section 6.25

Set the initial device value range.

Section 6.25

Set a file name for initial device value in the
PLC file tab of the PLC parameter dialog box.

Section 6.25

Set the RUN/STOP/RESET switch to STOP
and power on the CPU module
(the ERR. LED turns on).

11 - 5

Select [Online] [Format PLC memory]
in GX Developer and format the program
memory.

To write the parameters, created program, and
initial device value, make settings in the Write
to PLC screen displayed by selecting
[Online] [Write to PLC] in GX Developer.

Power off the programmable controller
and then on or reset the CPU module.

Write to PLC screen

QCPU User's Manual
(Hardware Design, Maintenance and Inspection)

Set the RUN/STOP/RESET switch to RUN to
change the CPU module in the RUN status.

Is the ERR. LED on
the CPU module on
(flashing)?
YES

Check the error cause in the System Monitor
screen displayed by selecting [Diagnostics]
[System Monitor] in GX Developer or in the
"PLC diagnostics" screen and remove the error.

QCPU User's Manual
(Hardware Design, Maintenance and Inspection)

NO
Start boot operation?

YES
End

To Section 11.5
Figure 11.2 Flowchart for writing one program

*1: When storing the file register and initial device value to the standard RAM or memory card (except the Flash card), format
the memory used.
*2: Write each data in the memory as shown below:
•Program:Program memory
•Parameter:Memory set in the parameter-valid drive
•Initial device value:Memory set in the PLC file tab of the PLC parameter dialog box

When the Universal model QCPU No.1 is the control CPU in the MELSECNET/H system, the Universal model QCPU can
communicate with the Universal model QCPU where MISSING PARA. has been detected via the MELSECNET/H (for the
network number 1 only).

11 - 6

CHAPTER11 PROCEDURES FOR WRITING PROGRAM TO CPU MODULE

11.4 Procedure for Writing Multiple Programs

This section describes a procedure for writing multiple programs to the program memory. (

Section

5.1.2)
Follow the procedure below and then the procedure provided in Section 11.5 before storing the programs
in the memory card for boot operation.
In the following procedure,

indicates an operation on the CPU module side.

Start

Start GX Developer.

GX Developer Version 8 Operating Manual

Set the project.

6
NO

Change the number of
device points?

YES
Change the number of device points in the
Device tab of the PLC parameter dialog box.

11.4 Procedure for Writing Multiple Programs

Create programs to be executed in the
CPU module.

Section 9.2

Ladder (writing) screen

Use the initial device value?

YES
Set the device memory.

Section 6.25

Set the initial device value range.

Section 6.25

Set a file name for initial device value in the
PLC file tab of the PLC parameter dialog box.

Section 6.25

11 - 7

Set local devices?

YES
Set the local device range in the Device
tab of the PLC parameter dialog box.

Section 9.14.1

Set a file name for the local devices in the
PLC file tab of the PLC parameter dialog box.

Section 9.14.1

Use the common
pointers?
YES

Set the start pointer number in the PLC
system tab of the PLC parameter dialog box.

Section 9.10

Set the names and execution conditions of
programs to be executed in the Program
tab of the PLC parameter dialog box.

Section 2.3

Connect the personal computer to which GX
Developer is installed to the CPU module.

Set the RUN/STOP/RESET switch to
STOP and power on the CPU module
(the ERR. LED turns on).

Select [Online] [Format PLC memory]
in GX Developer and format the program
memory.

Write to PLC screen
Select [Online] [Write to PLC] "Program
memory/Device memory" for "Target memory"
in GX Developer and write the parameters
and created programs.

Power off the programmable controller
and then on or reset the CPU module.

Set the RUN/STOP/RESET switch to RUN to
change the CPU module in the RUN status.

11 - 8

CHAPTER11 PROCEDURES FOR WRITING PROGRAM TO CPU MODULE

Is the ERR. LED
on the CPU module
on (flashing)?
YES

Check the error cause in the System Monitor
screen displayed by selecting [Diagnostics]
[System Monitor] in GX Developer or in the
"PLC diagnostics" screen and remove the error.

11
QCPU User's Manual
(Hardware Design, Maintenance and Inspection)

5
Start boot operation?

YES
End

To Section 11.5
Figure 11.3 Flowchart for writing multiple programs

11 - 9

11.4 Procedure for Writing Multiple Programs

11.5 Procedure for Boot Operation
This section describes a procedure for boot operation.
In the following procedure,

indicates an operation on the CPU module side.

Start (continued from
Section 11.3 or Section 11.4 )

If the RUN/STOP/RESET switch is in
RUN, set the switch to STOP.

Set the file name of parameters, a
program, devices, initial values and
device comments in the Boot file tab
of the PLC parameter dialog box.

Set the names and execution conditions of
programs to be executed in the Program tab
of the PLC parameter dialog box (This setting
is necessary when one program is written).

Use the memory
card (except the
Flash card)?

Section 5.1.8

Section 2.3

YES
Select [Online] [Format PLC memory]
in GX Developer and format the
program memory.

Select [Online] [Write to PLC (Flash ROM)]
[Write to PLC (Flash ROM)] "Program
memory/Device memory" for "Target
memory" in GX Developer and write the
parameters and created programs.

GX Developer Version 8 Operating Manual

Section 5.1.7

Power off the programmable controller
and then on or reset the CPU module.

NO
Is the BOOT LED on?

YES
End
Figure 11.4 Flowchart for boot operation

11 - 10

CHAPTER12 SPECIAL RELAY LIST AND SPECIAL REGISTER LIST

1
2

12.1 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.

3
12

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.
Table12.1 Explanation of special relay list
Item
Number
Name
Meaning
Explanation

Function of Item
• Indicates special relay number
• Indicates name of special relay
• Indicates contents of special relay
• Discusses contents of special relay in more detail
• Indicates whether the relay is set by the system or user, and, if it is set by the system, when setting is performed.

6
7

: Set by system

: Set by user (sequence programs or test operations from GX Developer)

S/U

: Set by both system and user

Set by

Each END

: Set during each END processing

Initial

: Set only during initial processing (when power supply is turned ON, or when going from STOP

Status change

: Set only when there is a change in status

Error

: Set when error occurs

to RUN)

Instruction execution : Set when instruction is executed
Request

: Set only when there is a user request (through SM, etc.)

System switching
: Set when system switching is executed.
• Indicates the corresponding special relay (M9
) of the ACPU.
Corresponding

(When the contents are changed, the special relay is represented M9

ACPU M9

Q00J/Q00/Q01 and QnPRH.)

format change. Incompatible with the

• New indicates the special relay newly added to the Q series CPU module.
Indicates the corresponding CPU module type name.
QCPU

: Indicates all the Q series CPU modules.

Q00J/Q00/Q01

: Indicates the Basic model QCPU.

Corresponding

Qn(H)

: Indicates the High Performance model QCPU.

CPU

QnPH

: Indicates the Process CPU.

QnPRH

: Indicates the Redundant CPU.

QnU

: Indicates the Universal model QCPU

Each CPU module model name: Indicates the relevant specific CPU module. (Example: Q02U)

For details on the following items, refer to the following manuals:
• Networks
Manual of the corresponding network module
• SFC
QCPU(Q mode)/QnACPU Programming Manual (SFC)

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 - 1

12.1 SPECIAL RELAY LIST

(When set)

Indicated only for registers set by system

(1) Diagnostic Information
Table12.2 Special relay

Number

Name

Meaning

Explanation

Set by
(When Set)

Corresponding
ACPU

Corresponding
CPU

SM0

SM1

Diagnostic errors

Self-diagnostic error

OFF : No error
ON : Error

OFF : No self-diagnosis
errors
ON : Self-diagnosis

• Turns ON if an error occurs as a result of diagnosis.
(Includes when an annunciator is ON, and when an
error is detected with CHK instruction)
• Remains ON even if the condition is restored to
normal thereafter.

S (Error)

New

Qn(H)
QnPH
QnPRH

• Turns ON if an error occurs as a result of diagnosis.
(Includes when an annunciator is ON)
• Remains ON even if the condition is restored to
normal thereafter.

S (Error)

New

Q00J/Q00/Q01
QnU

• Turns ON if an error occurs as a result of diagnosis.
(Does not include when an annunciator is ON or
when an error is detected by the CHK instruction)
• Remains ON even if the condition is restored to
normal thereafter.

S (Error)

M9008

Qn(H)
QnPH
QnPRH

• Turns ON if an error occurs as a result of diagnosis.
(Does not include when an annunciator is ON)
• Remains ON even if the condition is restored to
normal thereafter.

S (Error)

New

Q00J/Q00/Q01
QnU

SM5

Error common
information

OFF : No error common
information
ON : Error common
information

• When SM0 is ON, turns ON if there is error common
information

S (Error)

New

SM16

Error individual
information

OFF : No error individual
information
ON : Error individual
information

• When SM0 is ON, turns ON if there is error individual
information

S (Error)

New

SM50

Error reset

OFF

SM51

SM52

SM53

Battery low latch

Battery low

AC/DC DOWN
detection

12 - 2

ON: Error reset

OFF : Normal
ON : Battery low

OFF : AC/DC DOWN not
detected
ON : AC/DC DOWN
detected

QCPU

New

• Turns ON if battery voltage at CPU module or
memory card drops below rated value.
• Remains ON even if the battery voltage returns to
normal thereafter.
• Synchronizes with the BAT. LED.

• Conducts error reset operation

S (Error)

M9007

Qn(H)
QnPH
QnPRH
QnU

• Turns ON if battery voltage at CPU module drops
below rated value.
• Remains ON even if the battery voltage returns to
normal thereafter.
• Synchronous with ERR. LED

S (Error)

New

Q00J/Q00/Q01

• Same as SM51, but turns OFF subsequently when
battery voltage returns to normal.

S (Error)

M9006

S (Error)

M9005

• Turns ON if an instantaneous power failure of within
20ms occurs during use of the AC power supply
module.
Reset when the power supply is switched OFF, then
ON.
• Turns ON if an instantaneous power failure of within
10ms occurs during use of the DC power supply
module.
Reset when the power supply is switched OFF, then
ON.

QCPU

CHAPTER12 SPECIAL RELAY LIST AND SPECIAL REGISTER LIST

Table12.2 Special relay

Number

Name

Meaning

Explanation

Set by
(When Set)

Corresponding
ACPU

1
Corresponding
CPU

M9
SM56

SM60

Operation error

OFF : Normal
ON : Operation error

• ON when operation error is generated
• Remains ON if the condition is restored to normal
thereafter.

S (Error)

M9011

Blown fuse detection

OFF : Normal
ON : Module with blown
fuse

• Turns ON if there is at least one output module
whose fuse has blown.
• Remains ON if the condition is restored to normal
thereafter.
• Blown fuse status is checked even for remote I/O
station output modules.

S (Error)

M9000

S (Error)

M9002

QCPU

SM61

I/O module verify error

OFF : Normal
ON : Error

• Turns ON if the I/O module differs from the status
registered at power on.
• Remains ON if the condition is restored to normal
thereafter.
• I/O module verification is also conducted for remote
I/O station modules.

SM62

Annunciator detection

OFF : Not detected
ON : Detected

• Goes ON if even one annunciator (F) goes ON.

S (Instruction
execution)

M9009

SM80

CHK detection

OFF : Not detected
ON : Detected

• Goes ON if error is detected by CHK instruction.
• Remains ON if the condition is restored to normal
thereafter.

S (Instruction
execution)

New

SM90

Corresponds
to SD90

M9108

SM91

Corresponds
to SD91

M9109

SM92

Corresponds
to SD92

M9110

SM93

Corresponds
to SD93

M9111

SM94
SM95

Startup of monitoring
OFF : Not started(monitoring
timer for step transition
timer reset)
(Enabled only when
ON : Started(monitoring
SFC program exists)
timer started)

Corresponds
to SD94
Corresponds
to SD95

• Goes ON when measurement of
step transition monitoring timer is
commenced.
• Resets step transition monitoring
timer when it goes OFF.

M9112
U
M9113

SM96

Corresponds
to SD96

SM97

Corresponds
to SD97

New

SM98

Corresponds
to SD98

New

SM99

Corresponds
to SD99

New

Serial communication
function using flag

SM101

Communication
protocol status flag

OFF : GX Developer
ON : MC protocol
communication device

• Stores whether the device that is communicating via
the RS-232 interface is GX Developer or MC protocol
communication device

Protocol error

OFF : Normal
ON : Abnormal

• Turns ON when an abnormal protocol was used to
make communication in the serial communication
function.
• Remains ON if the condition is restored to normal
thereafter

S (Error)

• Stores the setting of whether the serial
communication function is used or not in the serial
communication setting parameter

S (Power-ON or
reset)
S (RS232
communication)

SM111

Communication status

OFF : Normal
ON : Abnormal

• Turns ON when the mode used to make
communication was different from the setting in the
serial communication function.
• Remains ON if the condition is restored to normal
thereafter.

SM112

Error information clear

ON : Cleared

• Turns ON when the error codes stored in SM110,
SM111, SD110 and SD111 are cleared. (Activated
when turned from OFF to ON)

SM113

Overrun error

OFF : Normal
ON : Abnormal

• Turns ON when an overrun error occurred in the
serial communication error.

S (Error)

Parity error

OFF : Normal
ON : Abnormal

• Turns ON when a parity error occurred in the serial
communication error.

S (Error)

Framing error

OFF : Normal
ON : Abnormal

• Turns ON when a framing error occurred in the serial
communication error.

S (Error)

OFF : Completed
ON : Not being executed or
Not completed

• Turns ON when the data is written to the program
cache memory.
• Turns OFF when the program memory batch transfer
is completed.
• Remains ON if the program memory batch transfer is
not executed after the data is written to the program
cache memory.

S (When status
changed)

SM115

SM165

Program memory
batch transfer
execution status

Qn(H)
QnPH
QnPRH

6
7

Qn(H)
QnPH
QnPRH

New

12.1 SPECIAL RELAY LIST

SM100

SM114

M9114

OFF : Serial communication
function is not used.
ON : Serial communication
function is used.

SM110

Q00/Q01
Q00UJ
Q00U
Q01U
Q02U*7

New

QnU*6

*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 - 3

(2) System information
Table12.3 Special relay

Number

Name

Meaning

Explanation

Set by
(When Set)

Corresponding
ACPU

Corresponding
CPU

M9
• When this relay goes from OFF to ON, the LEDs
corresponding to the individual bits at SD202 go off

SM202

LED OFF command

SM203

STOP contact

STOP status

• Goes ON at STOP status

S (Status change)

M9042

SM204

PAUSE contact

PAUSE status

• Goes ON at PAUSE status

S (Status change)

M9041

SM206

PAUSE enable coil

OFF : PAUSE disabled
ON : PAUSE enabled

• PAUSE status is entered if this relay is ON when the
PAUSE contact goes ON

M9040

M9025

OFF

ON : LED OFF

New

SM210

Clock data set request

OFF : Ignored
ON : Set request

• When this relay goes from OFF to ON and after END
instruction execution of subsequent scan, clock data
stored in SD210 to SD213 are written to the CPU
module.

SM211

Clock data error

OFF : No error
ON : Error

• ON when error is generated in clock data (SD210 to
SD213) value, and OFF if no error is detected.

S (Request)

M9026

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.

M9028

SM220

CPU No.1 preparation
completed

OFF : CPU No.1 preparation
uncompleted
ON : CPU No.1 preparation
completed

Turned ON when access can be made to the CPU
module No.1 from the other CPU module at power-on
or reset operation. SM220 is used as interlock for
accessing the CPU module No.1 when the multiple
CPU synchronous setting is asynchronous.

SM221

CPU No.2 preparation
completed

OFF : CPU No.2 preparation
uncompleted
ON : CPU No.2 preparation
completed

Turned ON when access can be made to the CPU
module No.2 from the other CPU module at power-on
or reset operation. SM221 is used as interlock for
accessing the CPU module No.2 when the multiple
CPU synchronous setting is asynchronous.

SM222

CPU No.3 preparation
completed

OFF : CPU No.3 preparation
uncompleted
ON : CPU No.3 preparation
completed

Turned ON when access can be made to the CPU
module No.3 from the other CPU module at power-on
or reset operation. SM222 is used as interlock for
accessing the CPU module No.3 when the multiple
CPU synchronous setting is asynchronous.

SM223

CPU No.4 preparation
completed

OFF : CPU No.4 preparation
uncompleted
ON : CPU No.4 preparation
completed

Turned ON when access can be made to the CPU
module No.4 from the other CPU module at power-on
or reset operation. SM223 is used as interlock for
accessing the CPU module No.4 when the multiple
CPU synchronous setting is asynchronous.

SM235

Online module change
flag

OFF : Online module change
is not in progress
ON : Online module change
in progress

• Turns on during online module change. (for host
CPU)

SM236

Online module change
complete flag

OFF : Online module change
incomplete
ON : Online module change
complete

• Turns ON for one scan after online module change is
complete.
• This contact point can only be used by the scan
program. (for host CPU)

SM237

Device range check
inhibit flag

OFF : Device range checked
ON : Device range not
checked

• Selects whether to check a device range during
execution of the BMOV, FMOV or DFMOV
instruction (only when the conditions for subset
processing are established).

*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 - 4

Qn(H)
QnPH
QnPRH
QnU

QCPU

QnU

S (When status
changed)

New

QnU*8

QnU*5

S (During online
module change)

New
QnPH

S (When online
module change is
complete)

New

QnU*6

CHAPTER12 SPECIAL RELAY LIST AND SPECIAL REGISTER LIST

Table12.3 Special relay

Number

Name

Meaning

Explanation

Set by
(When Set)

Corresponding
ACPU

1
Corresponding
CPU

SM240

SM241

SM242

SM243

SM244

SM245

No. 1 CPU reset flag

OFF : No. 1 CPU reset
cancel
ON : No. 1 CPU resetting

• Goes OFF when reset of the No. 1 CPU is canceled.
• Comes ON when the No. 1 CPU is resetting
(including the case where the CPU module is
removed from the base).
The other CPUs are also put in reset status.

No. 2 CPU reset flag

OFF : No. 2 CPU reset
cancel
ON : No. 2 CPU resetting

• Goes OFF when reset of the No. 2 CPU is canceled.
• Comes ON when the No. 2 CPU is resetting
(including the case where the CPU module is
removed from the base).
The other CPUs result in "MULTI CPU DOWN" (error
code: 7000).

No. 3 CPU reset flag

OFF : No. 3 CPU reset
cancel
ON : No. 3 CPU resetting

• Goes OFF when reset of the No. 3 CPU is canceled.
• Comes ON when the No. 3 CPU is resetting
(including the case where the CPU module is
removed from the base).
The other CPUs result in "MULTI CPU DOWN" (error
code: 7000).

No. 4 CPU reset flag

OFF : No. 4 CPU reset
cancel
ON : No. 4 CPU resetting

• Goes OFF when reset of the No. 4 CPU is canceled.
• Comes ON when the No. 4 CPU is resetting
(including the case where the CPU module is
removed from the base).
The other CPUs result in "MULTI CPU DOWN" (error
code: 7000).

No. 1 CPU error flag

OFF : No. 1 CPU normal
ON : No. 1 CPU during stop
error

• Goes OFF when the No. 1 CPU is normal (including
a continuation error).
• Comes ON when the No. 1 CPU is during a stop
error.

No. 2 CPU error flag

OFF : No. 2 CPU normal
ON : No. 2 CPU during stop
error

• Goes OFF when the No. 2 CPU is normal (including
a continuation error).
• Comes ON when the No. 2 CPU is during a stop
error.

No. 3 CPU error flag

OFF : No. 3 CPU normal
ON : No. 3 CPU during stop
error

SM247

No. 4 CPU error flag

OFF : No. 4 CPU normal
ON : No. 4 CPU during stop
error

• Goes OFF when the No. 4 CPU is normal (including
a continuation error).
• Comes ON when the No. 4 CPU is during a stop
error

OFF : Ignored
ON : Read

• When this relay goes from OFF to ON, maximum
loaded I/O number is read to SD250.

SM250

Max. loaded I/O read

Qn(H)*1
QnPH
QnU*8

S (Status change)

New
Qn(H)*1
QnPH
QnU*5

SM254

OFF : Refresh arrival station
ON : Refresh all stations

• Designate whether to receive arrival stations only or
to receive all slave stations in the CC-Link IE
controller network .
• Effective for the batch refresh (also effective for the
low speed cyclic)
• Specify whether to receive only arrival station or all
stations in the MELSECNET/H or CC-Link IE
controller network.

6
7

Q00/Q01*1
Qn(H)*1
QnPH
QnU*8

S (Status change)

New

Qn(H)*1
QnPH
QnU*5

New
Qn(H)
QnPH
QnPRH

• Effective for the batch refresh (also effective for the
low speed cyclic)
• Designate whether to receive arrival stations only or
to receive all slave stations in the MELSECNET/H.
All stations refresh
command

Qn(H)*2
U

New

QnPH*6
QnPRH*6

QnU

*1: This applies to the CPU of function version B or later.
*2: The module whose first 5 digits of serial No. is "09012" or later.
*5: The Universal model QCPU except the Q00UJCPU, Q00UCPU, Q01UCPU, and Q02UCPU.
*6: The module whose first 5 digits of serial No. is "10042" or later.
*8: The Universal model QCPU except the Q00UJCPU.

12 - 5

12.1 SPECIAL RELAY LIST

SM246

• Goes OFF when the No. 3 CPU is normal (including
a continuation error).
• Comes ON when the No. 3 CPU is during a stop
error.

3
Q00/Q01*1

Table12.3 Special relay
Number

Name

Meaning

Explanation

Set by
(When Set)

Corresponding
ACPU

Corresponding
CPU

M9
SM255

OFF : Operative network
ON : Standby network

• Goes ON for standby network(If no designation has
been made concerning active or standby, active is
assumed.)

OFF : Reads
ON : Does not read

S (Initial)

New

• For refresh from link to CPU module (B, W, etc.)
indicate whether to read from the link module.

New

SM257

OFF : Writes
ON : Does not write

• For refresh from CPU module to link (B, W, etc.),
designate whether to write to the link module.

New

SM260

OFF : Operative network
ON : Standby network

• Goes ON for standby network
(If no designation has been made concerning active
or standby, active is assumed.)

S (Initial)

New

OFF : Reads
ON : Does not read

• For refresh from link to CPU module (B, W, etc.)
indicate whether to read from the link module.

New

OFF : Writes
ON : Does not write

• For refresh from CPU module to link (B, W, etc.),
designate whether to write to the link module.

New

OFF : Operative network
ON : Standby network

• Goes ON for standby network
(If no designation has been made concerning active
or standby, active is assumed.)

S (Initial)

New

OFF : Reads
ON : Does not read

• For refresh from link to CPU module (B, W, etc.)
indicate whether to read from the link module.

New

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.

New

SM270

OFF : Operative network
ON : Standby network

• Goes ON for standby network
(If no designation has been made concerning active
or standby, active is assumed.)

S (Initial)

New

OFF : Reads
ON : Does not read

• For refresh from link to CPU module (B, W, etc.)
indicate whether to read from the link module.

New

OFF : Writes
ON : Does not write

• For refresh from CPU module to link (B, W, etc.),
designate whether to write to the link module.

New

OFF : Normal
ON : Error

• Goes ON when a CC-Link error is detected in any of
the installed CC-Link module. Goes OFF when
normal operation is restored.

S (Status change)

New

S (Initial)

M9100

SM256

SM261

MELSECNET/10,
MELSECNET/H
module 1 information

MELSECNET/10,
MELSECNET/H
module 2 information

SM262

SM265

SM266

SM271

MELSECNET/10,
MELSECNET/H
module 3 information

MELSECNET/10,
MELSECNET/H
module 4 information

SM272

SM280

CC-Link error

SM315

Communication
reserved time delay
enable/disable flag

OFF : Without delay
ON : With delay

• This flag is enabled when the time reserved for
communication processing is set in SD315.
• Turns ON to delay the END processing by the time
set in SD315 in order to perform communication
processing.
(The scan time increases by the period set in
SD315.)
• Turns OFF to perform the END processing without a
delay of the time set in SD315 when there is no
communication processing. (Defaults to OFF)

SM320

Presence/absence of
SFC program

OFF : SFC program absent
ON : SFC program present

• Turns ON when an SFC program is registered.
• OFF when an SFC program is not registered.

OFF : SFC program not
executed (stop)
ON : SFC program executed
(start)

• Initial value is set at the same value as SM320.
(Goes ON automatically if SFC program is present.)
• Turn this relay from ON to OFF to stop program
execution.
• Turn this relay from OFF to ON to resume program
execution.

SM321

Start/stop SFC
program

*1: This applies to the CPU of function version B or later.

12 - 6

S (Initial)/U

M9101form
at change

Qn(H)
QnPH
QnPRH

Q00J/Q00/Q01

Q00J/Q00/Q01*1
Qn(H)
QnPH
QnPRH
QnU

CHAPTER12 SPECIAL RELAY LIST AND SPECIAL REGISTER LIST

Table12.3 Special relay
Number

Name

Meaning

Explanation

Set by
(When Set)

Corresponding
ACPU

1
Corresponding
CPU

SM322

SFC program start
status

OFF : Initial start
ON : Resume start

SM323

Presence/absence of
continuous transition
for entire block

OFF : Continuous transition
not effective
ON : Continuous transition
effective

SM324

Continuous transition
prevention flag

OFF : When transition is
executed
ON : When no transition

• The SFC program starting mode in the SFC setting
of the PLC parameter dialog box is set as the initial
value.
AT initial start: OFF
At continued start: ON

S (Initial)/U

M9102form
at change

Set the presence/absence of continuous transition for
the block where "Continuous transition bit" of the SFC
data device has not been set.

M9103

S (Instruction
execution)

M9104

S (Status change)

New

S (Initial)/U

M9196

• OFF during operation in the continuous transition
mode or during continuous transition, and ON when
continuous transition is not executed.
• Always ON during operation in the no continuous
transition mode.

2
3
Q00J/Q00/Q01*1
Qn(H)
QnPH
QnPRH
QnU

SM325

Output mode at block
stop

OFF : OFF
ON : Preserves

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
the parameter is OFF when the coil outputs are OFF,
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.

SM326

SFC device clear
mode

OFF : Clear device
ON : Preserves device

Selects the device status when the stopped CPU is run
after the sequence program or SFC program has been
modified when the SFC program exists.

SM327

Output during end step
execution

OFF : Hold step output
turned OFF (cleared)
ON : Hold step output held

Select the device status at the time of switching from
STOP to program write to RUN.(All devices except the
step relay)

OFF : Clear processing is
performed.
ON : Clear processing is not
performed.

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.?
• When this relay turns OFF, all active steps are
forcibly terminated to terminate the block.
• When this relay is ON, the execution of the block is
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.

New

Q00J/Q00/Q01*1
QnU

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
execution type program is performed continuously
within the excess time.
• 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.

New

Qn(H)
QnPH

S (Status change)

New

6
S (Initial)/U

New

Clear processing
mode when end step
is reached

Operation mode for
low speed execution
type program

OFF : Asynchronous mode
ON : Synchronous mode

SM331

Normal SFC program
execution status

OFF : Not executed
ON : Being executed

• Indicates whether the normal SFC program is being
executed or not.
• Used as an SFC control instruction execution
interlock.

Qn(H)*3
QnPH*4
QnPRH

Program execution
management SFC
program execution
status

OFF : Not executed
ON : Being executed

• Indicates whether the program execution
management SFC program is being executed or not.
• Used as an SFC control instruction execution
interlock.

SM390

Access execution flag

ON indicates completion of
intelligent function module
access

• The status of the intelligent function module access
instruction executed immediately before is stored.
(This data is overwritten when the intelligent function
module access instruction is executed again.)
• Used by the user in a program as a completion bit.

S (Status change)

New

Qn(H)
QnPH
QnPRH

SM391

GINT instruction
execution completion
flag

OFF : Not executed
ON : Execution completed

Indicates execution status of the S(P).GINT instruction.
• Turned OFF before the instruction is executed.
• Turned ON after the instruction is completed.

S (Instruction
execution)

New

QnU

SM332

*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 - 7

12.1 SPECIAL RELAY LIST

SM330

Qn(H)
QnPH
QnPRH
QnU
Q00J/Q00/Q01*1

SM328

(3) System clocks/counters
Table12.4 Special relay

Number

Name

Meaning

Explanation

Set by
(When Set)

Corresponding
ACPU

Corresponding
CPU

M9
SM400

Always ON

ON
OFF

Always OFF

ON
OFF

• Normally is ON

S (Every END
processing)

• Normally is OFF

S (Every END
processing)

M9037

S (Every END
processing)

M9038

Qn(H)
QnPH
QnPRH
QnU

S (Every END
processing)

New

Q00J/Q00/Q01

S (Every END
processing)

M9039

Qn(H)
QnPH
QnPRH
QnU

• After RUN, OFF for 1 scan only.

S (Every END
processing)

New

Q00J/Q00/Q01

1 scan

• After RUN, ON for 1 scan only.
• This connection can be used for low speed execution type
programs only.

S (Every END
processing)

New

1 scan

• After RUN, OFF for 1 scan only.
• This connection can be used for low speed execution type
programs only.

S (Every END
processing)

New

• Repeatedly changes between ON and OFF at 5-ms
interval.
• When Programmable Controller power supply is
turned ON or a CPU module reset is performed,
goes from OFF to start.
(Note that the ON-OFF status changes when the
designated time has elapsed during the execution of
the program.)

S (Status change)

New

M9036
QCPU

SM401

SM402

After RUN, ON for 1
scan only

• After RUN, ON for 1 scan only.
• This connection can be used for scan execution type
programs only.
• When an initial execution type program is used, this
relay turns OFF at the END processing of the scan
execution type program in the first scan after RUN.

ON
OFF

1 scan

ON
OFF

Initial
execution
type program

1 scan of scan
execution type
program

• After RUN, ON for 1 scan only.
• After RUN, OFF for 1 scan only.
• This connection can be used for scan execution type
programs only.
• When an initial execution type program is used, this
relay turns OFF at the END processing of the scan
execution type program in the first scan after RUN.
SM403

After RUN, OFF for 1
scan only

ON
OFF

1 scan

ON
OFF
Initial
execution
type program

SM404

Low speed execution
type programON for 1
scan only after RUN

SM405

Low speed execution
type programAfter
RUN, OFF for 1 scan
only

ON
OFF
ON
OFF

SM409

0.01 second clock

0.005s

SM410

0.1 second clock

0.05s

SM411

0.2 second clock

0.005s

0.05s
0.1s
0.1s

SM412

1 second clock

0.5s

SM413

2 second clock

SM414

2n second clock

12 - 8

0.5s

1 scan of scan
execution type
program

Qn(H)
QnPH
QnPRH
QnU

M9030
• Repeatedly changes between ON and OFF at each
designated time interval.
• When Programmable Controller power supply is
turned ON or a CPU module reset is performed,
goes from OFF to start.
(Note that the ON-OFF status changes when the
designated time has elapsed during the execution of
the program.)

M9031
S (Status change)
M9032

M9033

Qn(H)
QnPH

• This relay alternates between ON and OFF at
intervals of the time (unit: s) specified in SD414.
• When Programmable Controller power supply is
turned ON or a CPU module reset is performed,
goes from OFF to start.
(Note that the ON-OFF status changes when the
designated time has elapsed during the execution of
the program.)

S (Status change)

M9034form
at change

QCPU

CHAPTER12 SPECIAL RELAY LIST AND SPECIAL REGISTER LIST

Table12.4 Special relay

Number

Name

Meaning

Set by
(When Set)

Explanation

Corresponding
ACPU

1
Corresponding
CPU

SM415

2n (ms) clock

SM420

User timing clock No.0

SM421

User timing clock No.1

SM422

User timing clock No.2

SM423

User timing clock No.3

SM424

User timing clock No.4

• This relay alternates between ON and OFF at
intervals of the time (unit: ms) specified in SD415.
• When Programmable Controller power supply is
turned ON or a CPU module reset is performed,
goes from OFF to start.
(Note that the ON-OFF status changes when the
designated time has elapsed during the execution of
the program.)

n(ms)
n(ms)

n2 scan

• Relay repeats ON/OFF switching at fixed scan
intervals.
• When Programmable Controller power supply is
turned ON or a CPU module reset is performed,
goes from OFF to start.
(For the redundant CPU, however, this relay is
always OFF after system switching.)
• The ON/OFF intervals are set with the DUTY
instruction

DUTY
n1 scan

SM430

User timing clock No.5

SM431

User timing clock No.6

SM432

User timing clock No.7

SM433

User timing clock No.8

SM434

User timing clock No.9

S (Status change)

New

Qn(H)
QnPH
QnPRH
QnU

M9020

3
12

M9021
M9022
M9023
S (Every END
processing)

QCPU
M9024

SM420

n1: ON scan interval
n2: OFF scan interval

• For use with SM420 to SM424 low speed programs

6
S (Every END
processing)

New

Qn(H)
QnPH

7
8

(4) Scan information
Table12.5 Special relay

Name

Meaning

Explanation

Corresponding
CPU

S (Every END
processing)

New

Qn(H)
QnPH

New

Qn(H)
QnPH
QnPRH

Set by
(When Set)

Corresponding
ACPU

M9
SM510

Low speed program
execution flag

OFF : Completed or not
executed
ON : Execution under way.

• Goes ON when low speed execution type program is
executed.

SM551

Reads module service
interval

OFF : Ignored
ON : Read

• When this relay goes from OFF to ON, the module
service interval designated by SD550 is read to
SD551 to SD552.

(5) I/O refresh
Table12.6 Special relay

Number

Name

Meaning

Explanation

Corresponding
CPU

SM580

Program to program I/
O refresh

OFF : Not refreshed
ON : Refreshed

• 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.
When a sequence program and an SFC program are
to be executed, the sequence program is executed,
I/O refresh is performed, and the SFC program is
then executed.

New

Q00J/Q00/Q01*1

*1: This applies to the CPU of function version B or later.

12 - 9

12.1 SPECIAL RELAY LIST

Number

Corresponding
ACPU

Set by
(When Set)

(6) Memory cards
Table12.7 Special relay

Number

Name

Meaning

Explanation

Set by
(When Set)

Corresponding
ACPU

Corresponding
CPU

M9
SM600

Memory card usable
flags

OFF : Unusable
ON : Use enabled

• ON when memory card is ready for use by user

S (Status change)

New

SM601

Memory card protect
flag

OFF : No protect
ON : Protect

• Goes ON when memory card protect switch is ON

S (Status change)

New

SM602

Drive 1 flag

OFF : No drive 1
ON : Drive 1 present

• Turns ON when the mounted memory card is RAM

S (Status change)

New

SM603

Drive 2 flag

OFF : No drive 2
ON : Drive 2 present

• Turns ON when the mounted memory card is ROM

S (Status change)

New

SM604

Memory card in-use
flag

OFF : Not used
ON : In use

• Goes ON when memory card is in use

S (Status change)

New

SM605

Memory card remove/
insert prohibit flag

OFF : Remove/insert enabled
ON : Remove/insert
prohibited

• Goes ON when memory card cannot be inserted or
removed

New

SM609

Memory card remove/
insert enable flag

OFF : Remove/insert
prohibited
ON : Remove/insert enabled

• Turned ON by user to enable the removal/insertion
of memory card.
• Turned OFF by the system after the memory card is
removed.
• This contact can be used only when SM604 and
SM605 are OFF.

S/U

New

SM620

Drive 3/4 usable flags

OFF : Unusable
ON : Use enabled

• Always ON

S (Initial)

New

SM622

Drive 3 flag

OFF : No drive 3
ON : Drive 3 present

• Always ON

Qn(H)
QnPH
QnPRH
QnU*1

S (Initial)

New

QCPU
Q00J/Q00/Q01
Qn(H)
QnPH
QnPRH
QnU*2

SM623

Drive 4 flag

OFF : No drive 4
ON : Drive 4 present

• Always ON

SM624

Drive 3/4 in-use flag

OFF : Not used
ON : In use

• Goes ON when the file within Drive 3 (standard
RAM) or Drive 4 (standard ROM) is used.

File register use

OFF : File register not used
ON : File register in use

SM640

• Goes ON when file register is in use

S (Initial)

New

QCPU

S (Status change)

New

Qn(H)
QnPH
QnPRH
QnU

S (Status change)

New

Q00J/Q00/Q01
Qn(H)
QnPH
QnPRH
QnU*2

*1: The Universal model QCPU except the Q00UJCPU, Q00UCPU, and Q01UCPU.
*2: The Universal model QCPU except the Q00UJCPU.

12 - 10

CHAPTER12 SPECIAL RELAY LIST AND SPECIAL REGISTER LIST

Table12.7 Special relay

Number

Name

Meaning

Explanation

Set by
(When Set)

Corresponding
ACPU

1
Corresponding
CPU

M9
SM650

SM660

Comment use

Boot operation

OFF : File register not used
ON : File register in use

• Goes ON when comment file is in use

S (Status change)

New

Qn(H)
QnPH
QnPRH
QnU

OFF : Internal memory
execution
ON : Boot operation in
progress

• Goes ON while boot operation is in process
• Goes OFF if boot designation switch is OFF

S (Status change)

New

Qn(H)
QnPH
QnPRH

OFF : Program memory
execution
ON : Boot operation in
progress

• Goes ON while boot operation is in process

S (Status change)

New

Q00J/Q00/Q01
QnU*1

SM671

Latch data backup to
standard ROM
completion flag

OFF : Not completed
ON : Completed

• Turned ON when latch data backup to the standard
ROM is completed.
• Time when the latch data backup to the standard
ROM was performed is stored in SD672 or later.

S (Status change)

New

QnU

SM672

Memory card file
register access range
flag

OFF : Within access range
ON : Outside access range

• Goes ON when access is made to area outside the
range of file register of memory card(Set within END
processing.)
• Reset at user program

S/U

New

Qn(H)
QnPH
QnPRH

SM675

Error completion of
latch data backup to
standard ROM

OFF : No Error
ON : Error

• Turned ON when data cannot be backuped to the
standard ROM by the latch data backup normally.
• Turned OFF when data is backuped to the standard
ROM by the latch data backup normally.

Specification of
restration repeated
execution

OFF : Not specified
ON : Specified

• If latch data backup is performed when SM676 is
ON, restore the data every time turning ON from
OFF the power supply from the next power-on.
• Delete the backuped latch data, or restore the data
every time turning ON from OFF the power supply
until the latch data backup operation will be executed
again.

SM680

Program memory write
error

OFF : Write error
ON : Write not executed/
normal

• Turns ON if a write error is detected at writing to
program memory (flash ROM).
Turns OFF by the write direction.

S (At write)

New

SM681

Program memory
writing flag

OFF : During writing
ON : Write not executed

• Turns ON when writing to the program memory (flash
ROM) is in progress, and turns OFF when writing is
completed.

S (At write)

New

SM682

Program memory
overwrite count error
flag

OFF : Overwrite count is
100,000 or more
ON : Overwrite count is less
than 100,000

• Turns ON when the overwrite count of program
memory (flash ROM) reaches 100,000.

S (At write)

New

SM685

Standard ROM write
error

OFF : Write error
ON : Write not executed/
normal

• Turns ON when write error is detected at writing to
standard ROM (flash ROM).
• Turns OFF by the write direction.

S (At write)

New

SM686

Standard ROM writing
flag

OFF : During overwriting
ON : Overwrite not executed

• Turns ON when writing to the standard ROM (flash
ROM) is in progress, and turns OFF when writing is
completed.

S (At write)

New

SM687

Standard ROM
overwrite count error
flag

OFF : Overwrite count is
100,000 or more
ON : Overwrite count is less
than 100,000

• Turns ON when the overwrite count of standard
ROM (flash ROM) reaches 100,000.
(It is necessary to change CPU module.)

S (At write)

New

SM691

Backup start
preparation status flag

OFF : Backup start
preparation not
completed
ON : Backup start
preparation completed

Turns on when the backup start preparation is
completed.

S (Status change)

New

OFF : Restoration not
completed
ON : Restoration completed

Turns on when restoration of the backup data in the
memory card is completed.

SM676

Restoration complete
flag

3
12

New

7
New

8
QnU

QnU*3
S (Status change)

New

*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 - 11

12.1 SPECIAL RELAY LIST

SM692

(7) Instruction-Related Special Relays
Table12.8 Special relay

Number

Name

Meaning

Explanation

Set by
(When Set)

Corresponding
ACPU

Corresponding
CPU

M9
SM700

Carry flag

OFF : Carry OFF
ON : Carry ON

• Carry flag used in application instruction

S (Instruction
execution)

M9012

QCPU

SM701

Number of output
characters selection

Switching the number of
output characters and the
output pattern

• Used for the PR, PRC, BINDA, DBINDA, BINHA,
DBINHA, BCDDA, DBCDDA, or COMRD instruction

M9049

Qn(H)
QnPH
QnPRH
QnU

SM702

Search method

OFF : Search next
ON : 2-part search

• Designates method to be used by search instruction.
• Data must be arranged for 2-part search.

New

Sort order

OFF : Ascending order
ON : Descending order

• The sort instruction is used to designate whether
data should be sorted in ascending order or in
descending order.

New

• Goes ON when all data conditions have been met for
the BKCMP instruction.

S (Instruction
execution)

New

Block comparison

OFF : Non-match found
ON : All match

• Goes ON when all data conditions have been met for
the DBKCMP instruction.

S (Instruction
execution)

New

SM709

DT/TM instruction
improper data
detection flag

Turns on when the data to be compared by the DT or
OFF : Improper data not
TM instruction is not recognized as date data or time
detected
data, or the device (3 words) to be compared exceeds
ON : Improper data detected
the specified device range.

S (Instruction
execution) or U

New

SM710

CHK instruction
priority ranking flag

OFF : Conditions priority
ON : Pattern priority

• Remains as originally set when OFF.
• CHK priorities updated when ON.

S (Instruction
execution)

New

Qn(H)
QnPH
QnPRH

SM715

EI flag

OFF : During DI
ON : During EI

• ON when EI instruction is being executed.

S (Instruction
execution)

New

QCPU

SM703

SM704

SM716

Block comparison
(Except an interrupt
program)

OFF : Mismatch found
ON : No mismatch

Turns on when all data conditions are confirmed that
they are met by the DBKCMP instruction.
(Initial execution type program, scan execution type
program, stand-by type program executed from initial
execution type program or scan execution type
program)

SM717

Block comparison
(Interrupt program)

OFF : Mismatch found
ON : No mismatch

Turns on when all data conditions are confirmed that
they are met by the DBKCMP instruction.
(Interrupt program, fixed scan execution type program,
stand-by type program executed from interrupt program
or fixed scan execution type program)

SM718

Block comparison
(Interrupt program
(I45))

OFF : Mismatch found
ON : No mismatch

Turns on when all data conditions are confirmed that
they are met by the DBKCMP instruction.
(Interrupt program (I45) or Stand-by type program
executed from interrupt program (I45))

SM720

Comment read
completion flag

OFF : Comment read not
completed
ON : Comment read
completed

• Turns on only during one scan when the processing
of the COMRD or PRC instruction is completed.
• Turns on only during one scan when the processing
of the COMRD instruction is completed.

QnU*2

QnU*2
S (Instruction
execution)

New

QnU*3

S (Status change)

New

• Switches ON while a file is being accessed by the
SP. FWRITE, SP. FREAD, COMRD, PRC, or LEDC
instruction.

SM721

SM722

File being accessed

BIN/DBIN instruction
error disabling flag

OFF : File not accessed
ON : File being accessed

OFF : Error detection
performed
ON : Error detection not
performed

• Switches ON while a file is being accessed by the
SP. FWRITE, SP. FREAD, COMRD or LEDC
instruction.

Qn(H)
QnPH
QnPRH
QnU
Qn(H)
QnPH

S (Status change)

New

Qn(H)
QnPH
QnPRH

• Switches ON while a file is being accessed by the
SP. FWRITE, SP. FREAD, COMRD or SP.DEVST
instruction.

QnU

• Turns ON while the ATA card or standard ROM is
being accessed.

QnU*1

• Turned ON when "OPERATION ERROR" is
suppressed for BIN or DBIN instruction.

*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 - 12

QCPU

New

QCPU

CHAPTER12 SPECIAL RELAY LIST AND SPECIAL REGISTER LIST

Table12.8 Special relay

Number

Name

Meaning

Explanation

• During OFF, XCALL instructions will not be executed
even if execution condition is risen.
• During ON, XCALL instructions will be executed
when execution condition is risen.

Set by
(When Set)

Corresponding
ACPU

1
Corresponding
CPU

SM734

XCALL instruction
execution condition
designation

OFF : Not executed by
execution condition
risen
ON : Executed by execution
condition risen

SM735

SFC comment readout
instruction in
execution flag

OFF : SFC comment readout
instruction is
inactivated.
ON : SFC comment readout
instruction is
activating.

• Turns on the instructions, (S(P).SFCSCOMR) to
read the SFC step comments and (S(P).
SFCTCOMR) to read the SFC transition condition
comments.

SM738

MSG instruction
reception flag

OFF : Instruction not
executed
ON : Instruction execution

• Goes ON when MSG instruction is executed

S (Instruction
execution)

New

Qn(H)
QnPRH

SM750

Scaling instruction
search method setting

OFF : Search next
ON : 2-part search

Determines a search method when the scaling
instruction is executed.

New

QnU*8

SM774

PID bumpless
processing
(for complete
derivative)

OFF : Matched
ON : Not matched

• Specifies whether to match the set value (SV) with
the process value (PV) or not in the manual mode.

New

Q00J/Q00/Q01*4
Qn(H)
QnPRH
QnU

OFF : Performs link refresh
ON : Performs no link
refresh

• Select whether link refresh processing will be
performed or not when only communication with the
CPU module is made at the execution of the COM
instruction.

New

Q00J/Q00/Q01
Qn(H)
QnPH

OFF : Performs refresh
processes other than
an I/O refresh
ON : Performs refresh set
by SD778

• Select whether to perform refresh processes other
than an I/O refresh set by SD778 when the COM or
CCOM instruction is executed.

New

SM775

Selection of refresh
processing during
COM/CCOM
instruction execution

New

Qn(H)*1

S (status change)

New

QnPH*3

Qn(H)*2
QnPRH*3

Q00J/Q00/Q01*4

SM776

Enable/disable local
device at CALL

OFF : Local device disabled
ON : Local device enabled

• Set whether the local device of the subroutine
program called at execution of the CALL instruction
is valid or invalid.

SM777

Enable/disable local
device in interrupt
program

OFF : Local device disabled
ON : Local device enabled

• Set whether the local device at execution of the
interrupt program is valid or invalid.

SM794

PID bumpless
processing(for
incomplete derivative)

OFF : Matched
ON : Not matched

• Specifies whether to match the set value (SV) with
the process value (PV) or not in the manual mode.

New

Qn(H)*5
QnPH*3
QnPRH
QnU

Qn(H)
QnPH
QnPRH

QnU

Q00J/Q00/Q01*4
New

Qn(H)*6
QnPRH
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 - 13

12.1 SPECIAL RELAY LIST

Table12.8 Special relay

Number

Name

Meaning

Explanation

Set by
(When Set)

Corresponding
ACPU

Corresponding
CPU

M9
OFF : Block is secured
ON : Block set by SD796
cannot be secured

• Turns ON when the number of the remaining blocks
of the dedicated instruction transmission area used
for the multiple CPU high-speed transmission
dedicated instruction(target CPU= CPU No.1) is less
than the number of blocks specified by SD796.
Turns ON at instruction execution. Turns OFF when
the empty area exists at END processing.

S (When
instruction/END
processing
executed)

New

OFF : Block is secured
ON : Block set by SD797
cannot be secured

• Turns ON when the number of the remaining blocks
of the dedicated instruction transmission area used
for the multiple CPU high-speed transmission
dedicated instruction (target CPU= CPU No.2) is less
than the number of blocks specified by SD797.
Turns ON at instruction execution. Turns OFF when
the empty area exists at END processing.

S (When
instruction/END
processing
executed)

New

SM798

Block information
using multiple CPU
high-speed
transmission
dedicated instruction
(for CPU No.3)

OFF : Block is secured
ON : Block set by SD798
cannot be secured

• Turns ON when the number of the remaining blocks
of the dedicated instruction transmission area used
for the multiple CPU high-speed transmission
dedicated instruction (target CPU= CPU No.3) is less
than the number of blocks specified by SD798.
Turns ON at instruction execution. Turns OFF when
the empty area exists at END processing.

S (When
instruction/END
processing
executed)

New

SM799

Block information
using multiple CPU
high-speed
transmission
dedicated instruction
(for CPU No.4)

OFF : Block is secured
ON : Block set by SD799
cannot be secured

• Turns ON when the number of the remaining blocks
of the dedicated instruction transmission area used
for the multiple CPU high-speed transmission
dedicated instruction(target CPU= CPU No.4) is less
than the number of blocks specified by SD799.
Turns ON at instruction execution. Turns OFF when
the empty area exists at END processing.

S (When
instruction/END
processing
executed)

New

SM796

Block information
using multiple CPU
high-speed
transmission
dedicated instruction
(for CPU No.1)

SM797

Block information
using multiple CPU
high-speed
transmission
dedicated instruction
(for CPU No.2)

QnU*7

*7: The Universal model QCPU except the Q00UJCPU, Q00UCPU, Q01UCPU, and Q02UCPU.

(8) Debug
Table12.9 Special relay

Number

Name

Meaning

Explanation

Set by
(When Set)

Corresponding
ACPU

Corresponding
CPU

M9
SM800

Trace preparation

OFF : Not ready
ON : Ready

• Switches ON when the trace preparation is
completed

SM801

Trace start

OFF : Suspend
ON : Start

• Trace is started when this relay switches ON.
• Trace is suspended when this relay switches OFF.
(All related special Ms switches OFF.)

SM802

Trace execution in
progress

OFF : Suspend
ON : Start

• Switches ON during execution of trace.

Trace trigger

OFF

• Trace is triggered when this relay switches from OFF
to ON. (Identical to TRACE instruction execution
status)

SM804

After trace trigger

OFF : Not after trigger
ON : After trigger

• Switches ON after trace is triggered.

S (Status change)

New

SM805

Trace completed

OFF : Not completed
ON : End

• Switches ON at completion of trace

S (Status change)

M9043

SM826

Trace error

OFF : Normal
ON : Errors

• Switches ON if error occurs during execution of trace

S (Status change)

New

SM829

Forced registration
specification of trace
setting

ON : Forced registration
enabled
OFF : Forced registration
disabled

• Even when the trace condition or the trigger
condition is established, the sampling trace setting
can be set to the CPU module by turning SM829 ON
and registering the sampling trace setting by GX
Developer.

New

SM803

ON: Start

*1: The Universal model QCPU except the Q00UJCPU.

12 - 14

S (Status change)

New

M9047

S (Status change)

M9046

M9044

Qn(H)
QnPH
QnPRH
QnU*1

QnU*1

CHAPTER12 SPECIAL RELAY LIST AND SPECIAL REGISTER LIST

(9) 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.

1
2
3
12

6
7

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.
is provided, the converted special relay can be used for the device number.

When

is provided, the device number does not work with QCPU.

Table12.10 Special relay
ACPU
Special
Relay

M9000

M9002

Special
Special
Relay after
Relay for
Conversion Modification

SM1000

SM1002

–

Name

Fuse blown

I/O module verify
error

Meaning

Details

OFF : Normal
ON : Module with blown
fuse

• Turned on when there is one or more output modules of
which fuse has been blown.
• Remains ON if the condition is restored to normal
thereafter.
• Output modules of remote I/O stations are also checked
fore fuse condition.

OFF : Normal
ON : Error

• Turned on if the status of I/O module is different form
entered status when power is turned on.
• Remains ON if the condition is restored to normal
thereafter.
• I/O module verification is done also to remote I/O station
modules.
• Reset is enabled only when special registers SD1116 to
SD1123 are reset.

Corresponding
CPU

Qn(H)
QnPH
QnU*1

*1: The relevant modules are as follows:
• The Universal model QCPU whose serial number (first five digits) is "10102" or later.
• Q00UJCPU, Q00UCPU, Q01UCPU

12 - 15

12.1 SPECIAL RELAY LIST

When

Table12.11 Special relay
ACPU
Special
Relay

Special
Relay after
Conversion

Special
Relay for
Modification

Name

Meaning

Details
• Turns ON if an instantaneous power failure of within 20ms
occurs during use of the AC power supply module.
• Reset when the power supply is switched OFF, then ON.

M9005

SM1005

–

AC DOWN
detection

OFF : AC DOWN not
detected
ON : AC DOWN detected

M9006

SM1006

–

Battery low

OFF : Normal
ON : Battery low

• Turns ON when the battery voltage drops to or below the
specified.
• Turns OFF when the battery voltage returns to normal
thereafter.

M9007

SM1007

–

Battery low latch

OFF : Normal
ON : Battery low

• Turns ON when the battery voltage drops to or below the
specified.
• Remains ON if the battery voltage returns to normal
thereafter.

M9008

SM1008

SM1

Self-diagnosis
error

OFF : No error
ON : Error

• Turned on when error is found as a result of selfdiagnosis.

M9009

SM1009

SM62

Annunciator
detection

OFF : No F number detected
ON : F number detected

• Turned on when OUT F of SET F instruction is
executed.
• Switched off when SD1124 data is cleared to zero.

M9011

SM1011

SM56

Operation error
flag

OFF : No error
ON : Error

• Turned on when operation error occurs during execution
of application instruction.
• Remains ON if the condition is restored to normal
thereafter.

M9012

SM1012

SM700

Carry flag

OFF : Carry OFF
ON : Carry ON

• Carry flag used in application instruction.

M9016

SM1016

Data memory clear
flag

OFF : lgnored
ON : Output claered

• Clears the data memory including the latch range (other
than special relays and special registers) in remote run
mode from computer, etc. when SM1016 is on.

M9017

SM1017

Data memory clear
flag

OFF : lgnored
ON : Output claered

• Clears the unlatched data memory (other than special
relays and special registers) in remote run mode from
computer, etc. when SM1017 is on.

M9020

SM1020

–

User timing clock
No.0

M9021

SM1021

–

User timing clock
No.1

–

User timing clock
No.2

M9022

SM1022

• Turns ON if an instantaneous power failure of within 10ms
occurs during use of the DC power supply module.
• Reset when the power supply is switched OFF, then ON.

SM1023

–

n2 scan

n1: ON scan interval
n2: OFF scan interval
* : If DUTY instruction, which specified from SM 1020 to
SM 1024 of User timing clock in programs other than
a program for a Universal model QCPU, changes the
programmable controller to the Universal model
QCPU, the special relays SM 420 to 424 will be
replaced.
(Universal model QCPUs cannot specify the special
relays from SM 1020 to SM1024.)

User timing clock
No.3

SM1024

–

User timing clock
No.4

M9025

SM1025

–

Clock data set
request

OFF : Ignored
ON : Set request present
used

• Writes the clock data stored in SD1025 to SD1028 to the
CPU module after the END instruction is executed in the
scan in which SM1025 turned from OFF to ON.

M9026

SM1026

–

Clock data error

OFF : No error
ON : Error

• Switched on by clock data (SD1025 to SD1028) error

–

Clock data read
request

OFF : Ignored
ON : Read request

• Reads clock data to SD1025 to SD1028 in BCD when
SD1028 is on.

Batch processing
of data
communications
requests

OFF : Batch processing not
conducted
ON : Batch processing
conducted

• The SM1029 relay is turned on using a sequence program
to process all data communication requests accepted
during one scan in the END processing of that scan.
• The batch processing of the data communication requests
can be turned on and off during running.
• The default is OFF (processed one at a time for each END
processing in the order in which data communication
requests are accepted).

SM1028

M9029

SM1029

M9030

SM1030

–

0.1 second clock

0.05s

M9031

SM1031

–

0.2 second clock

0.1s

M9032

SM1032

–

1 second clock

0.5s

M9033

SM1033

–

2 second clock

Qn(H)
QnPH

Qn(H)
QnPH
QnU*1

Qn(H)
QnPH

0.05s

0.1s

0.5s

• 0.1 second, 0.2 second, 1 second and 2 second, clocks
are generated.
• Not turned on or off per scan but turned on and off even
during scan if corresponding time has elapsed.
• Starts with off when Programmable Controller power
supply is turned on or CPU module reset is performed.

*1: The relevant modules are as follows:
• The Universal model QCPU whose serial number (first five digits) is "10102" or later.
• Q00UJCPU, Q00UCPU, Q01UCPU

12 - 16

QnU*1

DUTY n1 n2 SM1020
n2 scan

M9024

M9028

Qn(H)
QnPH

• Relay which repeats on/off at intervals of predetermined
scan.
• When power is turned on or reset is per-formed, the clock
starts with off.
Set the intervals of on/off by DUTY instruction.

n1 scan

M9023

Corresponding
CPU

Qn(H)
QnPH
QnU*1

CHAPTER12 SPECIAL RELAY LIST AND SPECIAL REGISTER LIST

Table12.11 Special relay
ACPU
Special
Relay

Special
Special
Relay after
Relay for
Conversion Modification

M9034

SM1034

–

M9036

SM1036

–

Name

2n minute clock(1
minute clock)*2

Always ON

Meaning

1
Details

ns
ns

ON
OFF

• Used as dummy contacts of initialization and application
instruction in sequence program.
• SM1038 and SM1037 are turned on and off without regard
to position of key switch on CPU module front. SM1038
and SM1039 are under the same condition as RUN status
except when the key switch is at STOP position, and
turned off and on. Switched off if the key switch is in STOP
position. SM1038 is on for one scan only and SM1039 is
off for one scan only if the key switch is not in STOP
position.

SM1037

–

Always OFF

ON
OFF

M9038

SM1038

–

ON for 1 scan only
after RUN

ON
OFF

1 scan

M9039

SM1039

–

RUN flag(After
RUN, OFF for 1
scan only)

ON
OFF

1 scan

M9040

SM1040

SM206

PAUSE enable coil

OFF : PAUSE disabled
ON : PAUSE enabled

M9041

SM1041

SM204

PAUSE status
contact

OFF : PAUSE not in effect
ON : PAUSE in effect

M9042

SM1042

SM203

STOP status
contact

OFF : STOP not in effect
ON : STOP in effect

• Switched on when the RUN key switch or RUN/STOP
switch is in STOP position.

SM805

Sampling trace
completed

OFF : Sampling trace in
progress
ON : Sampling trace
completed

• Turned on upon completion of sampling trace performed
the number of times preset by parameter after STRA
instruction is executed.
Reset when STRAR instruction is executed.

SM1043

OFF
M9044

SM1044

SM1045

M9046

SM1046

SM802

Sampling trace

ON Same as STRA
instruction
execution
OFF Same as STRAR
instruction
execution

• When RUN key switch is at PAUSE position or pause
contact has turned on and if SM1040 is on, PAUSE mode
is set and SM1041 is turned on.

• Turning on/off SM1044 can execute STRA/STRAR
instruction.
(SM1044 is forcibly turned on/off by a peripheral device.)
When switched from OFF to ON: STRA instruction
When switched from ON to OFF: STRAR instruction
The value stored in SD1044 is used as the condition for
the sampling trace.
At scanning, at time
Time (10 ms unit)

Watchdog timer
(WDT) reset

OFF : Does not reset WDT
ON : Resets WDT

• The SM1045 relay is turned on to reset the WDT when the
ZCOM instruction and data communication request batch
processing are executed (used when the scan time
exceeds 200 ms).

Sampling trace

OFF : Trace not in progress
ON : Trace in progress

• Switched on during sampling trace.

SM1047

SM801

Sampling trace
preparations

OFF : Sampling trace
suspended
ON : Sampling trace started

• Sampling trace is not executed unless SM1047 is turned
ON.
Sampling trace is suspended when SM1047 goes OFF.

M9049

SM1049

SM701

Switching the
number of output
characters

OFF : Output until NULL
code encountered
ON : 16 characters output

• When SM1049 is OFF, characters up to NULL (00H) code
are output.
• When SM1049 is ON, ASCII codes of 16 characters are
output.

OFF : Enabled
ON : Disable

• Switched ON to disable the CHG instruction.
• Switched ON when program transfer is requested.
Automatically switched OFF when transfer is complete.

OFF : 7SEG segment display
ON : I/O partial refresh

• When SM1052 is ON, the SEG instruction is executed as
an I/O partial refresh instruction.
When SM1052 is OFF, the SEG instruction is executed as
a 7-SEG display instruction.

M9051

SM1051

M9052

SM1052

SEG instruction
switch

Qn(H)
QnPH
QnU*1

Qn(H)
QnPH

Qn(H)
QnPH
QnU*1

6
7
8

Qn(H)
QnPH

Qn(H)
QnPH
QnU*1

M9047

CHG instruction
execution disable

Qn(H)
QnPH

*1: The relevant modules are as follows:
• The Universal model QCPU whose serial number (first five digits) is "10102" or later.
• Q00UJCPU, Q00UCPU, Q01UCPU
*2: minute clock indicates the name of the special relay (M9034) of the ACPU.

12 - 17

12.1 SPECIAL RELAY LIST

M9045

SM803

• Alternates between ON and OFF according to the
seconds specified at SD414. (Default: n = 30)
• Not turned on or off per scan but turned on and off even
during scan if corresponding time has elapsed.
• Starts with off when Programmable Controller power
supply is turned on or CPU module reset is performed.

M9037

M9043

Corresponding
CPU

Table12.11 Special relay
ACPU
Special
Relay

Special
Relay after
Conversion

Special
Relay for
Modification

Name

Meaning

M9056

SM1056

Main side P, I set
request

OFF : Other than when P, I
set being requested
ON : P, I set being
requested

M9057

SM1057

Sub side P, I set
request

OFF : Other than when P, I
set being requested
ON : P, I set being
requested

M9058

SM1058

Main side P, I set
completion

Momentarily ON at P, I set
completion

M9059

SM1059

Sub program P, I
set completion

Momentarily ON at P, I set
completion

M9060

SM1060

Sub program 2 P, I
set request

OFF : Other than when P, I
set being requested
ON : P, I set being
requested

M9061

SM1061

Sub program 3 P, I
set request

OFF : Other than when P, I
set being requested
ON : P, I set being
requested

M9070

SM1070

A8UPU/
A8PUJrequired
search time*3

OFF : Read time not
shortened
ON : Read time shortened

Details

• Provides P, I set request after transfer of the other
program (for example subprogram when main program is
being run) is complete during run. Automatically switched
off when P, I setting is complete.

• Turned ON once when the P, I set has been completed,
and then turned OFF again.

• Turned ON to shorten the search time in the A8UPU/
A8PUJ.
(In this case, the scan time is extended by 10 %.)
It is set whether the error checks below are performed or not
when the END instruction is processed (to set the END
instruction processing time).
• Check for fuse blown.
• Check of battery
• Collation check of I/O module

M9084

SM1084

Error check

OFF : Error check executed
ON : No error check

M9091

SM1091

Operation error
details flag

OFF : No error
ON : Error

• Turns ON when the detail factor of the operation error is
stored into SD1091.
• Remains ON if the condition is restored to normal
thereafter.

M9100

SM1100

Presence/absence
of SFC program

OFF : SFC programs not
used
ON : SFC programs used

• Turned on if the SFC program is registered.
• Turned off if the SFC program is not registered.

SM320

M9101

SM1101

SM321

Start/stop SFC
program

OFF : SFC programs stop
ON : SFC programs start

• The value in SM1100 is set as the initial value.
(The relay automatically turns ON when the SFC program
is present.)
• When this relay turns from ON to OFF, execution of the
SFC program stops.
• When this relay turns from OFF to ON, execution of the
SFC program resumes.

M9102

SM1102

SM322

SFC program start
status

OFF : Initial start
ON : Resume start

• The SFC program start mode in the SFC setting of the
PLC parameter dialog box is set as the initial value.
At initial start: OFF
At continue start: ON

*3: The A8UPU/A8PUJ is not available for the QCPU/QnACPU.

12 - 18

Corresponding
CPU

Qn(H)
QnPH

CHAPTER12 SPECIAL RELAY LIST AND SPECIAL REGISTER LIST

Table12.11 Special relay
ACPU
Special
Relay
M9103

Special
Special
Relay after
Relay for
Conversion Modification
SM1103

Name
Presence/absence
of continuous
transition

OFF : Continuous transition
not effective
ON : Continuous transition
effective

• Set whether continuous transition will be performed for the
block where the "continuous transition bit" of the SFC
information device is not set.

OFF : When transition is
completed
ON : When no transition

• OFF during operation in the continuous transition mode or
during continuous transition, and ON when continuous
transition is not executed.
• Always ON during operation in the no continuous
transition mode.

M9104

SM1104

SM324

M9108

SM1108

SM90

Step transition
monitoring timer
start (equivalent of
SD90)

M9109

SM1109

SM91

Step transition
monitoring timer
start (equivalent of
SD91)

M9110

SM1110

SM92

Step transition
monitoring timer
start (equivalent of
SD92)

M9111

SM1111

SM93

Step transition
monitoring timer
start (equivalent of
SD93)

M9112

SM1112

SM94

Step transition
monitoring timer
start (equivalent of
SD94)

M9113

SM1113

SM95

Step transition
monitoring timer
start (equivalent of
SD95)

M9114

SM1114

SM96

Step transition
monitoring timer
start (equivalent of
SD96)

SM325

Operation output
at block stop

SM1197
Switch between
blown fuse and I/O
verify error display

M9198

M9199

OFF : Monitoring timer reset
ON : Monitoring timer reset
start

Data recovery of
online sampling
trace/status latch

• Turns ON when the measurement of the step transition
monitoring timer is started.
Turning this relay OFF resets the step transition
monitoring timer.

7
Qn(H)
QnPH

OFF : Coil output OFF
ON : Coil output ON

SM
1198

I/O numbers
to be
displayed

OFF

X/Y0 to 7F0

OFF

X/Y800 to
FF0

OFF

X/Y1000 to
17F0

X/Y1800 to
1FF0

SM1198

SM1199

SM
1197
M9197

OFF : Data recovery disabled
ON : Data recovery enabled

• 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
executed at block stop.
OFF : All coil outputs are turned off. (Operation output
by the SET instruction is retained regardless of
the ON/OFF status of SM1196.)

Switches I/O numbers in the fuse blow module storage
registers (SD1100 to SD1107) and I/O module verify error
storage registers (SD1116 to SD1123) according to the
combination of ON/OFF of the SM1197 and SM1198.

• Recovers the setting data stored in the CPU module at
restart when sampling trace/status latch is executed.
• SM1199 should be ON to execute again. (Unnecessary
when writing the data again from peripheral devices.)

(10) QCPU with built-in Ethernet port
Table12.12 Special relay

Number

Name

Meaning

Explanation

Set by
(When Set)

Corresponding
ACPU

Corresponding
CPU

M9
SM1270

Time setting function
(SNTP client)
execution

OFF : No time setting function
(SNTP client) execution
ON : Time setting function
(SNTP client) execution

SM1273

Remote password
mismatch count clear

OFF : Normal
ON : Clear

12.1 SPECIAL RELAY LIST

SM1196

Details

SM323

Continuous
transition
suspension flag

M9196

Meaning

Corresponding
CPU

Set this to ON when executing the time setting function
(SNTP client).
(Only when the time setting function is in "Use" with the
time setting parameter.)

To clear the acumulated numeber (SD979 to 999) of
mismatched remote passwords, the setting SM1273 is
executed.

New
QnU*1
New

* 1: This applies to the Built-in Ethernet port QCPU.

12 - 19

(11) Process control instructions
Table12.13 Special relay

Number

Name

Meaning

Set by
(When Set)

Explanation

Corresponding
ACPU

Corresponding
CPU

M9
SM1500

SM1501

Hold mode

OFF : No-hold
ON : Hold

• Specifies whether or not to hold the output value
when a range over occurs for the S.IN instruction
range check.

Hold mode

OFF : No-hold
ON : Hold

• Specifies whether or not the output value is held
when a range over occurs for the S.OUT instruction
range check.

New

Set by
(When Set)

Corresponding
ACPU

QnPH
QnPRH

(12) For redundant systems (Host system CPU information *1)
SM1510 to SM1599 are only valid for redundant systems.
All off for standalone systems.
Table12.14 Special relay

Number

Name

Meaning

Explanation

Corresponding
CPU

SM1510

Operation mode

SM1511

System A identification
flag

SM1512

System B identification
flag

SM1513

Debug mode status
flag

SM1515

Control system
judgment flag

SM1516

Standby system
judgment flag

OFF : Redundant system
backup mode, standalone system
ON : Redundant system
separate mode

S (Each END)

New

S (Initial)

New

• Distinguishes between system A and system B.
• The flag status does not change even if the tracking cable is disconnected.

System A

System B

When TRK. CABLE ERR.
(error code: 6210) occurs (Unknown)

SM1511

OFF

SM1512

OFF

OFF : Not in debug mode
ON : Debug mode

• Turns on when the redundant system operating
mode is set to debug mode.

QnPRH
S (Initial)

New

S (Status change)

New

• Indicates operation system status.
• The flag status does not change even if the tracking cable is disconnected.

Control
system

Standby
system

When TRK. CABLE ERR.
(error code: 6210) occurs (Unknown)

SM1515

OFF

SM1516

OFF

*1: The information of the host CPU module is stored.

12 - 20

• Turns on when the operating mode is redundant
system separate.

CHAPTER12 SPECIAL RELAY LIST AND SPECIAL REGISTER LIST

Table12.13 Special relay

Number

Name

Meaning

Explanation

Set by
(When Set)

Corresponding
ACPU

1
Corresponding
CPU

M9
OFF : Power supply on
startup
ON : Operation system
switch start up

• Turns on when the CPU module is started up by the
system switching (switching from the standby system
to the control system). Remains OFF when the
standby system is switched to the control system by
a power-ON startup.

S (Status change)

SM1517

CPU module startup
status

SM1518

Standby system to
control system
switching status flag

ON
OFF

1 scan

• Turns ON once switch between standby system to
control system, (ON for 1 scan only) occurs.
• This status flag can only be used for scan execution
type programs.

S (Each END)

New

SM1519

Previous Control
System Identification
Flag

ON
OFF

1 scan

• On the last operation Control System was System
B,if power supply is supplied, or reset is released on
both SYSTEM together,After RUN, ON for 1 scan
only by System A side.

S (Each END)

New

SM1520

Block 1

SM1521

Block 2

SM1522

Block 3

SM1523

Block 4

SM1524

Block 5

SM1525

Block 6

SM1526

Block 7

SM1527

Block 8

SM1528

Block 9

SM1529

Block 10

SM1530

Block 11

SM1531

Block 12

SM1532

Block 13

SM1533

Block 14

SM1534

Block 15

SM1534
SM1535

Data tracking transfer
trigger specification

OFF : No trigger
ON : Trigger

Block 16

SM1536

Block 17

SM1537

Block 18

SM1538

Block 19

SM1539

Block 20

SM1540

Block 21

SM1541

Block 22

SM1542

Block 23

SM1543

Block 24

SM1544

Block 25

SM1545

Block 26

SM1546

Block 27

SM1547

Block 28

SM1548

Block 29

3
12

6
• When data is transferred
based on the tracking
setting of the redundant
parameter dialog box, the
target block is specified
as trigger.
• When "Auto Tracking
block No.1" is enabled in
the tracking setting,
SM1520 is turned ON by
the system at power ON/
STOP to RUN. In other
cases, SM1520 to
SM1583 are turned ON
by the user.

QnPRH

S (initial)/U

7
8

New

12.1 SPECIAL RELAY LIST

SM1535

SM1536

New

12 - 21

Table12.13 Special relay

Number

Name

Meaning

Explanation

Set by
(When Set)

Corresponding
ACPU

Corresponding
CPU

M9
SM1549

SM1549

Block 30

SM1550

Block 31

SM1551

Block 32

SM1552

Block 33

SM1553

Block 34

SM1554

Block 35

SM1555

Block 36

SM1556

Block 37

SM1557

Block 38

SM1558

Block 39

SM1559

Block 40

SM1560

Block 41

SM1561

Block 42

SM1562

Block 43

SM1563

Block 44

SM1564

Block 45

SM1565

Block 46

SM1566

Block 47

SM1567

Block 48

SM1568

Block 49

SM1569

Block 50

SM1570

Block 51

SM1571

Block 52

SM1572

Block 53

SM1573

Block 54

SM1574

Block 55

SM1575

Block 56

SM1576

Block 57

SM1577

Block 58

SM1578

Block 59

SM1579

Block 60

SM1580

Block 61

SM1581

Block 62

SM1582

Block 63

SM1583

Block 64

SM1566
SM1567

Data tracking transfer
trigger specification

OFF : No trigger
ON : Trigger

• When data is transferred
based on the tracking
setting of the redundant
parameter dialog box, the
target block is specified
as trigger.
• When "Auto tracking
block No. 1" is enabled in
the tracking setting,
SM1520 is turned ON by
the system at power ON/
STOP to RUN. In other
cases, SM1520 to
SM1583 are turned ON
by the user.

SM1590

System switching
enable/disable flag
from network module

OFF : System switching
request issuing module
absent
ON : System switching
request issuing module
present

• Turns ON when a system switching request is issued
from the network module. The module No. that
issued system switching can be checked by SD1590.
• Turns OFF when all bits of SD1590 are OFF.

SM1591

Standby system error
detection disable flag
at system switching

ON : Error is not detected by
new standby system at
system switching
OFF : Error is detected by
new standby system at
system switching

SM1592

Enable/disable user
system switching

OFF : Disable user system
switching
ON : Enable user system
switching

12 - 22

S (initial)/U

New

QnPRH

S (Each END)

New

This flag is used to determine if the new standby station
detects 6210:STANDBY during system switching.
This applies to the following switching methods:
• System switching from GX Developer
• System switching using dedicated instruction
• System switching by the intelligent function module

New

• This flag enables system switching by the user from
GX Developer or by dedicated instruction.
(SP.CONTSW).

New

CHAPTER12 SPECIAL RELAY LIST AND SPECIAL REGISTER LIST

Table12.13 Special relay

Number

Name

Meaning

Explanation

Set by
(When Set)

Corresponding
ACPU

1
Corresponding
CPU

SM1593

Setting to access
extension base unit of
standby system CPU

OFF : Error
ON : Ignored

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
returned when accessing buffer memory of the
intelligent function module on the extension base
unit from the standby system CPU.
ON : No processing is performed when accessing
buffer memory of intelligent function module on
the extension base unit from the standby system
CPU.
• When SM1595 is turned from OFF to ON, memory
copy from control system to standby system starts.
Note that when SM1595 is turned from OFF to ON,
memory copy does not start if the I/O No. of the copy
destination (standby system CPU module: 3D1H) is
not stored in SD1595.

SM1595

Memory copy to other
system start flag

OFF : Start memory copy
ON : No memory copy
initiated

SM1596

Memory copy to other
system status flag

OFF : Memory copy not
executed
ON : Memory copy executed

• Turns on while memory is copied to other system.
• Turns off when memory copy execution has
completed.

SM1597

Memory copy to other
system completion
flag

OFF : Memory copy not
completed
ON : Memory copy
completed

• Turns on once the memory copying to the other
system has completed.

SM1598

Copy contents of
standard ROM during
memory copy

OFF : Copy standard ROM
data
ON : Standard ROM data is
not copied

• If set to on by user, the standard ROM data is not
copied to the other system while memory copy is
executing.

QnPRH*2

3
12

New

S (Starting to
copy/finish)

QnPRH

S (finish)/U

New
U

*2: The module whose first 5 digits of serial No. is “09012” or later.

(13) For redundant system (Other system CPU information *1)

Table12.14 Special relay

Number

Name

Meaning

Explanation

Set by
(When Set)

Corresp
onding
Host
SM
*2

SM1600

Other system error
flag

OFF : No error
ON : Error

• Turns on when an error occurs during redundant
system. Error check (Turns on single bit of SD1600.)
• Is off when no errors are present

S (Each END)

–

SM1610

Other system
diagnostics error

OFF : No error
ON : Error

• Turns on when a diagnostics error occurs. (Includes
error detection when annunciator is ON, and by CHK
instruction)
• Corresponds to status of SM0 at other system

S (Each END)

SM0

SM1611

Other systems self
diagnostics error.

OFF : No self diagnostics
error occurred
ON : Self diagnostics error
occurred

• Turns on when a self diagnostics error occurs.
(Does not include error detection when annunciator
is ON, and by CHK instruction)
• Corresponds to status of SM1 at other system

S (Each END)

SM1

SM1615

Other system common
error information

OFF : No common error
information present
ON : Common error
information present

• Turns on when there is common error information at
other system
• Corresponds to status of SM5 at other system

S (Each END)

SM5

SM1626

Error individual
information for other
systems

OFF : No individual error
information present
ON : Individual error
information present

• Turns on when there is individual error information at
other system
• Corresponds to status of SM16 at other system

S (Each END)

SM16

SM1649

Standby system
cancel error flag

OFF to ON:
Cancels error of standby
system

By turning this relay from OFF to ON, the continue error
that occurred in the standby system CPU module can
be canceled.
Use SD1649 to specify the error code of the error to be
canceled.

–

Corresponding
CPU

QnPRH

*1 Stores other system CPU diagnostic information and system information.
*2 This shows the special relay(SM

) for the host system CPU.

12 - 23

12.1 SPECIAL RELAY LIST

SM1600 to SM1650 only valid for the CPU redundant system backup mode, so they cannot
be refreshed during the separate mode.
Either the backup mode or the separate mode is valid for the SM4651 to SM1699.
SM1600 to SM1699 are all turned off for stand-alone system.

(14) For redundant system (tracking)
Either the backup mode or the second mode is valid for SM1700 to SM1799.
All is turned off for stand-alone system.
Table12.15 Special relay

Number

Name

Meaning

Explanation

Set by
(When Set)

Corresponding
ACPU

Corresponding
CPU

M9
SM1700

Transfer trigger
completion flag

OFF : Transfer not completed
ON : Transfer completed

• Turns on for one scan, once transfer of block 1 to
block 64 is completed.
(1)

SM1709

Manual system
switching disable/
enable setting during
online program
change redundant
tracking

ON : Manual system
switching enabled
(Disable canceled)
OFF : Manual system
switching disabled

(2)

(3)

(1)

SM1710

Transfer tracking data
during online program
change enable flag

OFF : No device tracking
ON : Transfer device
memory

(2)

(3)

12 - 24

S (status change)

Turning this relay from OFF to ON enables
manual system switching during online program
change redundant tracking.
After the manual system switching disable status
is canceled, the system automatically turns off
SM1709.
System switching due to any of the following
conditions is executed even during online
program change redundant tracking, regardless of
the status of this relay.
•Power off, reset, hardware failure, CPU stop error
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
•File batch online program change redundant
tracking execution status

S (When
executed)/U

Set whether the tracking of the following data will
be executed or not during online program change
redundant tracking.
•Device memory
(Including SM/SD that will automatically execute
tracking)
•PIDINIT information, S.PIDINIT information, SFC
information
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
performed to ensure consistency of both systems.
This SM is also transferred form control system
CPU module to standby system CPU module by
tracking data.

New

QnPRH

CHAPTER12 SPECIAL RELAY LIST AND SPECIAL REGISTER LIST

Table12.15 Special relay

Number

Name

Meaning

Explanation

Set by
(When Set)

Corresponding
ACPU

1
Corresponding
CPU

M9
SM1712

Block 1

SM1713

Block 2

SM1714

Block 3

SM1715

Block 4

SM1716

Block 5

SM1717

Block 6

SM1718

Block 7

SM1719

Block 8

SM1720

Block 9

SM1721

Block 10

SM1722

Block 11

SM1723

Block 12

SM1724

Block 13

SM1725

Block 14

SM1726

Block 15

SM1727

Block 16

SM1728

Block 17

SM1729

Block 18

SM1730

Block 19

SM1731

Block 20

SM1732

Block 21

SM1733

Block 22

SM1734

Block 23

SM1735

Block 24

SM1736

Block 25

SM1737

Block 26

SM1738

Block 27

SM1739

Block 28

SM1740

Block 29

SM1741

Block 30

SM1742

Block 31

SM1743

Block 32

SM1744

Block 33

SM1745

Block 34

SM1746

Block 35

SM1747

Block 36

SM1748

Block 37

SM1749

Block 38

SM1750

Block 39

SM1751

Block 40

SM1752

Block 41

SM1753

Block 42

SM1754

Block 43

SM1755

Block 44

SM1756

Block 45

SM1757

Block 46

SM1758

Block 47

SM1759

Block 48

SM1735
SM1736

Transfer trigger
completion flag

OFF : Transfer uncompleted
ON : Transfer completed

2
3
12

6
7
Turns ON only during one
scan when the transmission
of the corresponding block is
completed.

S (status change)

New

QnPRH

12.1 SPECIAL RELAY LIST

SM1712

12 - 25

Table12.15 Special relay
Number

Name

Meaning

Explanation

Set by
(When Set)

Corresponding
ACPU

Corresponding
CPU

M9
SM1760

SM1760

Block 49

SM1761

Block 50

SM1762

Block 51

SM1763

Block 52

SM1764

Block 53

SM1765

Block 54

SM1766

Block 55

SM1767

Block 56

SM1768

Block 57

SM1769

Block 58

SM1770

Block 59

SM1771

Block 60

SM1772

Block 61

SM1773

Block 62

SM1774

Block 63

SM1775

Block 64

SM1767
SM1768

Transfer trigger
completion flag

SM1769

OFF : Transmission
uncompleted
ON : Transmission end

Turns ON only during one
scan when the transmission
of the corresponding block is
completed.

S (status change)

New

QnPRH

Set by
(When Set)

Corresponding
ACPU

Corresponding
CPU

(15) Redundant power supply module information
Table12.16 Special relay

Number

Name

Meaning

Explanation

SM1780

SM1781

SM1782

SM1783

Power supply off
detection flag

OFF : No redundant power
supply module with
input power OFF
detected
ON : Redundant power
supply module with
input power OFF
detected

• Turns ON when one or more redundant power
supply modules with input power OFF are detected.
• Turns on if any of SD1780 bits is on.
• Turns off if all bits of SD1780 are off.
• Turns OFF when the main base unit is not the
redundant main base unit (Q38RB).
• When the multiple CPU system is configured, the
flags are stored only to the CPU No.1.

S (Each END)

Power supply failure
detection flag

OFF : No faulty redundant
power supply module
detected
ON : Faulty redundant
power supply module
detected

• Turns ON when one or more faulty redundant power
supply modules are detected.
• Turns on if any of SD1781 bits is on.
• Turns off if all bits of SD1781 are off.
• Turns OFF when the main base unit is not the
redundant main base unit (Q38RB).
• When the multiple CPU system is configured, the
flags are stored only to the CPU No.1.

S (Each END)

OFF : No momentary power
failure detected
ON : Momentary power
failure detected

• Turns ON when a momentary power failure of the
input power supply to the power supply 1 or 2 is
detected one or more times. After turning ON,
remains ON even if the power supply recovers from
the momentary power failure.
• Turns OFF the flag (SM1782, SM1783) of the power
supply 1/2 when the CPU module starts.
• When the input power to one of the redundant power
supply modules turns OFF the corresponding flag
turns OFF.
• Turns OFF when the main base unit is not the
redundant main base unit (Q38RB).
• When the multiple CPU system is configured, the
flags are stored only to the CPU No.1.

S (Each END)

Momentary power
failure detection flag
for power supply 1 *1

Momentary power
failure detection flag
for power supply 2 *1

New

*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 - 26

Qn(H)*2
QnPH*2
QnPRH
QnU*3

CHAPTER12 PECIAL RELAY LIST AND SPECIAL REGISTER LIST

12.2 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.

2
3
12

The heading descriptions in the following special register lists are shown in 4.1.
Table12.17 Descriptions of the special register lists headings
Item

Function of Item

Number

• Indicates special register number

Name

• Indicates name of special register

Meaning

• Indicates contents of special register

Explanation

• Discusses contents of special register in more detail

Set by
(When set)

• Indicates corresponding special register in ACPU
Corresponding ACPU
M9

Corresponding CPU

(When the contents are changed, the special register is represented D9
and QnPRH.)
• New indicates the special register newly added to the Q series CPU module.

format change. Incompatible with the Q00J/Q00/Q01

Indicates the relevant CPU module.
QCPU
: Indicates all the Q series CPU modules.
Q00J/Q00/Q01
: Indicates the Basic model QCPU.
Qn(H)
: Indicates the High Performance model QCPU.
QnPH
: Indicates the Process CPU.
QnPRH
: Indicates the Redundant CPU.
QnU
: Indicates the Universal model QCPU
Each CPU type name
: Can be applied only to the specific CPU. (e.g. Q02U)

For details on the following items, refer to the following manuals:
• Networks

Manual of the corresponding network module

• SFC

QCPU(Q mode)/QnACPU Programming Manual (SFC)

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 - 27

7
8

12.2 SPECIAL REGISTER LIST

• Indicates whether the relay is set by the system or user, and, if it is set by the system, when setting is performed.

S
: Set by system
U
: Set by user (sequence programs or test operations from GX Developer)
S/U
: Set by both system and user

Indicated only for registers set by system
Each END
: Set during each END processing
Initial
: Set only during initial processing (when power supply is turned ON, or when going from STOP to RUN)
Status change
: Set only when there is a change in status
Error
: Set when error occurs
Instruction execution
: Set when instruction is executed
Request
: Set only when there is a user request (through SM, etc.)
System switching
: Set when system switching is executed.

(1) Diagnostic Information
Table12.18 Special register

Number

Name

Meaning

Set by
(When Set)

Explanation

Corresponding
ACPU

Corresponding
CPU

D9
SD0

Diagnostic
errors

Diagnosis error
code

• Error codes for errors found by diagnosis are stored as BIN data.
• Contents identical to latest fault history information.

S (Error)

D9008
format
change

S (Error)

New

• Year (last two digits) and month that SD0 data was updated is stored as
BCD 2-digit code.
SD1

SD2

b15 to
b8 b7 to
b0
Year (0 to 99) Month (1 to 12)
Clock time for
diagnosis error
occurrence

Clock time for
diagnosis error
occurrence

(Example) October, 1995
9510H

• The day and hour that SD0 was updated is stored as BCD 2-digit code.

b15 to
b8 b7 to
b0
Day (1 to 31) Hour (0 to 23)

(Example) 10 a.m. on 25th
2510H

• The minute and second that SD0 data was updated is stored as BCD 2digit code.
SD3

b15
to
b8 b7
to
b0
Minutes (0 to 59) Seconds (0 to 59)

(Example) 35 min. 48 sec.
3548H

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
b8 b7
b0
to
to
Individual information Common information
category codes
category codes
• The common information category codes store the following codes:
0 : No error

SD4

Error
information
categories

12 - 28

Error information
category code

1: Unit/module No./ CPU No./Base No.*
2: File name/Drive name
3: Time (value set)
4: Program error location
5: System switching cause (for Redundant CPU only)
6: Reason(s) for tracking capacity excess error (specific to Redundant
CPU)
7: Base No./Power supply No. (The first 5 digits of serial number 10072
or higer are chosen for Universal model QCPU.)
8: Tracking transmission data classification (specific to Redundant CPU)
*: For a multiple CPU system that consists of the Basic model QCPU,
High Performance model QCPU, Process CPU, Universal model
QCPU the module number or CPU number is stored depending on the
error that occurred.
(Refer to the corresponding error code for which number has been
stored.)
CPU No. 1: 1, CPU No. 2: 2, CPU No. 3: 3, CPU No. 4: 4
• The individual information category codes store the following codes:
0: No error
1: (Empty)
2: File name/Drive name
3: Time (value actually measured)
4: Program error location
5: Parameter number
6: Annunciator number
7: CHK instruction failure No. (except for the Basic model QCPU and the
Universal model QCPU)
8: Reason(s) for system switching failure (specific to Redundant CPU)
12: File diagnostic information (specific to the Universal model QCPU)
13: Parameter No./CPU No. (specific to the Universal model QCPU)

QCPU

S (Error)

New

CHAPTER12 PECIAL RELAY LIST AND SPECIAL REGISTER LIST

Table12.18 Special register
Number

Name

Meaning

Explanation

Set by
(When Set)

Corresponding
ACPU

Corresponding
CPU

D9
SD5

SD6

Number
SD5
SD6
SD7
SD8
SD9
SD10
SD11
SD12
SD13
SD14
SD15

SD7

SD8

SD9

SD10

SD11

SD12

SD13

Error common
information

Meaning
Slot No./CPU No./Base No. 1, 2, 3, 4
I/O No. 5

12
(Empty)

*1: For a multiple CPU system that consists of the Basic model QCPU, High
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
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
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.
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.

Value used to identify the base unit on which the CPU module has
been mounted. The following shows the definition of the base No.

6
7
8
S (Error)

New

QCPU

12.2 SPECIAL REGISTER LIST

Base No.
Definition
Indicates the main base unit mounted with the CPU
0
module.
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

SD14

SD15

• Common information corresponding to the error codes (SD0) is stored
here.
• The following ten types of information are stored here:
• The error common information type can be judged by the "common information category code" in SD4. (The values of the "common information
category code" stored in SD4 correspond to following 1) to 8).)
1)
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
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.

File name/Drive name
(Example) File name =
Number
Meaning
ABCDEFGH. IJK
SD5
Drive
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 - 29

Table12.18 Special register

Number

Name

Meaning

Explanation

Set by
(When Set)

Corresponding
ACPU

Corresponding
CPU

SD5

SD6

Time (value set)

Number
SD5
SD6
SD7
SD8
SD9
SD10
SD11
SD12
SD13
SD14
SD15

SD7

SD8

SD9

Error common
information
SD10

SD11

Error common
information

Meaning
Time : 1 s units (0 to 999 s)
Time : 1ms units (0 to 65535ms)

(Empty)

Program error location

Meaning
Number
SD5
File name
SD6
(ASCII code: 8 characters)
SD7
SD8
2EH(.)
SD9 Extension 6
(ASCII code: 3 characters)
SD10
SD11
Pattern 7
SD12
Block No.
SD13
Step No./transition condition
Sequence step No. (L)
SD14
Sequence step No. (H)
SD15
*7 : Contents of pattern data

15 14
0 0
SD12

to
to

4 3 2 1 0
0 0

(Not used)

(Bit number)

SFC block designation present
(1)/absent (0)
SFC step designation present
(1)/absent (0)

SD13

SD14

SD15

12 - 30

SFC transition designation present
(1)/absent (0)

S (Error)

New

QCPU

CHAPTER12 PECIAL RELAY LIST AND SPECIAL REGISTER LIST

Table12.18 Special register

Number

Name

Meaning

Set by
(When Set)

Explanation

Corresponding
ACPU

1
Corresponding
CPU

D9
5)

Number
SD5

SD5

Meaning
System switching condition 13
Control system switching
instruction argument

SD6
SD7
SD8
SD9
SD10
SD11
SD12
SD13
SD14
SD15

SD6

SD7

0 : No system switching condition
(default)
1 : Power-OFF, reset, hardware failure,
watchdog timer error
2 : Stop error
(except watchdog timer error)
3 : System switching request by
network module
16 : Control system switching instruction
17 : Control system switching request
from GX Developer
6)

SD10
Error common
information

SD14

SD15

S (Error)

New

QnPRH

b14 b13 b12 b11 b10 b9

b7 b6 b5 b4 b3 b2 b1

SD5

1
(SM1535)
(Block16)

SD6

SD7

SD8

1
(SM1583)
(Block64)

SD9

SD15

1
(SM1528)
(Block9)

1
(SM1520)
(Block1)

1
(SM1568)
(Block49)

Power supply No.

Number
SD5
SD6
SD7
SD8
SD9
SD10
SD11
SD12
SD13
SD14
SD15

7
8

Reason(s) for tracking capacity excess error
The block No. when the data amount that can be tracked (100k) is
exceeded is indicated by the bit pattern of the corresponding special
relay.
b15

12.2 SPECIAL REGISTER LIST

Error common
information

SD13

*13: Details of reason(s) for system switching

SD9

SD12

(Empty)

SD8

SD11

Reason(s) for system switching

Meaning
Base No.
Power supply No.

(Empty)
Qn(H)*1
S (Error)

New

QnPH*1
QnPRH
QnU*2

1: Power supply 1 fault
2: Power supply 2 fault
"Power
Redundant power supply module
supply
mounted on POWER 1 slot of redundant
module 1": base unit (Q38RB, Q68RB, Q65WRB)
"Power
Redundant power supply module
supply
mounted on POWER 2 slot of redundant
module 2": base unit (Q38RB, Q68RB, Q65WRB)

*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 - 31

Table12.18 Special register

Number

Name

Meaning

Set by
(When Set)

Explanation

Corresponding
ACPU

Corresponding
CPU

SD5

SD6

SD7

Number
SD5
SD6
SD7
SD8
SD9
SD10
SD11
SD12
SD13
SD14
SD15

SD8

SD9

SD10

Tracking transmission data classification
Stores the data classification during tracking.

Error common
information

Meaning
Data type 15

(Empty)

*15: Details of data classification

b15 b14 to b6 b5
0

S (Error)

Each bit
0: Not sent
1: Being sent
Device data

SD11

Signal flow
PIDINIT/S. PIDINIT
instruction data
SFC execution data

SD12

System switching
request
Operation mode
change request
System data

SD13

SD14

SD15

12 - 32

New

QnPRH

CHAPTER12 PECIAL RELAY LIST AND SPECIAL REGISTER LIST

Table12.18 Special register

Number

Name

Meaning

Set by
(When Set)

Explanation

Corresponding
ACPU

1
Corresponding
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
information category code" in SD4. (The values of the "individual information category code" stored in SD4 correspond to following 1) to 8),
12), and 13).)

SD16

(Empty)

File name/Drive name

SD17

Number
Meaning
SD16
Drive
SD17
File
name
SD18
SD19 (ASCII code: 8 characters)
SD20
2EH(.)
SD21 Extension 6
SD22 (ASCII code: 3 characters)
SD23
SD24
(Empty)
SD25
SD26

SD18

3)
SD19

SD21

7
8

(Empty)

Program error location

SD23

*7 : Contents of pattern data

15 14
0 0

to
to

4 3 2 1 0
0 0

S (Error)

New

QCPU

(Bit number)

SFC block designation
present (1)/absent (0)

(Not used)

SFC step designation
present (1)/absent (0)

SD24

SFC transition designation
present (1)/absent (0)

SD25

SD26

5) Parameter No. 6) Annunciator number /
7) CHK instruction
malfunction number
Number
Meaning
SD16 Parameter No. 16
SD17
SD18
SD19
SD20
SD21
(Empty)
SD22
SD23
SD24
SD25
SD26

Number
SD16
SD17
SD18
SD19
SD20
SD21
SD22
SD23
SD24
SD25
SD26

Meaning
No.

(Empty)

*16: For details of the parameter No., refer to the User's Manual
(Function Explanation, Program Fundamentals) of the CPU
module used.

12 - 33

12.2 SPECIAL REGISTER LIST

SD22

Error individual
information

Meaning
Time : 1 s units (0 to 999 s)
Time : 1ms units (0 to 65535ms)

Number
Meaning
SD16
SD17
File name
SD18
(ASCII code: 8 characters)
SD19
2EH(.)
SD20 Extension 6
(ASCII code: 3 characters)
SD21
SD22
Pattern 7
SD23
Block No.
SD24
Step No./transition No.
Sequence step No. (L)
SD25
Sequence step No. (H)
SD26

Error individual
information

(Example) File name =
ABCDEFGH. IJK
b15 to b8 b7 to b0
42H(B) 41H(A)
44H(D) 43H(C)
46H(F) 45H(E)
48H(H) 47H(G)
49H(I)
2EH(.)
4BH(K) 4AH(J)

Time (value actually measured)

Number
SD16
SD17
SD18
SD19
SD20
SD21
SD22
SD23
SD24
SD25
SD26

SD20

*6 : Extensions are shown below.
Table12.19 Extension name
SDn

SDn+1

Extension

File Type

Higher 8 bits

Lower 8 bits

Higher 8 bits

Name

51H

50H

41H

QPA

51H

50H

47H

QPG

51H

43H

44H

QCD

51H

44H

49H

QDI

Initial device value

51H

44H

52H

QDR

File register

51H

44H

4CH

QDL

51H

54H

44H

QTD

51H

46H

44H

QFD

Parameters
• Sequence program
• SFC program
Device comment

Local device
(Other than the Basic model QCPU)
Sampling trace data
(Other than the Basic model QCPU)
Breakdown history data
(Other than the Basic model QCPU and
the Universal model QCPU)

51H

12 - 34

53H

54H

QST

SP.DEVST/S.DEVLD instruction file
(For Universal model QCPU only)

CHAPTER12 PECIAL RELAY LIST AND SPECIAL REGISTER LIST

Table12.18 Special register

Number

Name

Meaning

Explanation

Set by
(When Set)

Corresponding
ACPU

1
Corresponding
CPU

D9
8)

Reason(s) for system switching failure

Number
SD16
SD17
SD18
SD19
SD20
SD21
SD22
SD23
SD24
SD25
SD26

Meaning
System switching prohibition
condition 14

2
3

(Empty)

*14: Details of reason(s) for system switching failure

SD26

Error individual
information

12)

Failuer information (H)

8
S (Error)

New

drive No.(L)

File name
(ASCll: 8 characters)
EXtension *6
2EH(.)
(ASCll; 3 characters)
Failure information 2
(CRC value that is read)
Failure information 3
(CRC value that is calculated)

QnU

Parameter No./CPU No.

Number
SD16
SD17
SD18
SD19
SD20
SD21
SD22
SD23
SD24
SD25
SD26

6
7

File diagnostic information

SD16
SD17
SD18
SD19
SD20
SD21
SD22
SD23
SD24
SD25
SD26

13)

QnPRH

12.2 SPECIAL REGISTER LIST

0 : Normal switching completion
(default)
1 : Tracking cable fault (cable
removal, cable fault, internal
circuit fault, hardware fault)
2 : Hardware failure, power OFF,
reset or watchdog timer error
occurring in standby system
3 : Hardware failure, power OFF,
reset or watchdog timer error
occurring in control system
4 : Preparing for tracking
5 : Time limit exceeded
6 : Standby system is in stop error
(except watchdog timer error)
7 : Operation differs between two
systems (in backup mode only)
8 : During memory copy from control
system to standby system
9 : Online program change
10 : Error detected by network
module of standby system
11 : System switching being executed
12 : Online module change in
progress

Meaning
Parameter No.*16
CPU No. (1 to 4)

(Empty)

12 - 35

Table12.18 Special register

Number

Name

Meaning

Set by
(When Set)

Explanation

Corresponding
ACPU

Corresponding
CPU

D9
SD50

Error reset

Error number that
performs error
reset

• Stores error number that performs error reset

New

S (Error)

New

• All corresponding bits go 1(ON) when battery voltage drops.
• Subsequently, these remain 1(ON) even after battery voltage has been
returned to normal.
b15

SD51

Battery low
latch

Bit pattern
indicating where
battery voltage
drop occurred

to
0

b3 b2 b1 b0

CPU error
alarm
error

1: This does not apply to Basic model QCPU.
• In the alarm, data can be held within the time specified for battery low.
• The error indicates the complete discharge of the battery.

QCPU

SD52

Battery low

Bit pattern
indicating where
battery voltage
drop occurred

SD53

AC/DC DOWN
detection

Number of times
for AC/DC DOWN
detection

• Every time the input voltage falls to or below 85% (AC power)/65% (DC
power) of the rating during operation of the CPU module, the value is
incremented by 1 and stored in BIN code.
• The counter repeats increment and decrement of the value ;
0
32767
-32768
0

S (Error)

D9005

SD60

Number of
module with
blown fuse

Number of module
with blown fuse

• Value stored here is the lowest station I/O number of the module with
the blown fuse.

S (Error)

D9000

SD61

I/O module
verify error
number

I/O module verify
error module
number

• The lowest I/O number of the module where the I/O module verification
number took place.

S (Error)

D9002

12 - 36

• Same configuration as SD51 above
• After the alarm is detected (ON), the alarm turns OFF by error detection
(ON). (For the Universal model QCPU only)
• Turns to 0 (OFF) when the battery voltage returns to normal thereafter.

S (Error)

New

CHAPTER12 PECIAL RELAY LIST AND SPECIAL REGISTER LIST

Table12.18 Special register

Number

Name

Meaning

Explanation

Set by
(When Set)

Corresponding
ACPU

1
Corresponding
CPU

D9
SD62

Annunciator
number

• The first annunciator number (F number) to be detected is stored here.

S (Instruction
execution)

D9009

SD63

Number of
annunciators

• Stores the number of annunciators searched.

S (Instruction
execution)

D9124

When F goes ON due to OUT F or SET F instruction, the F numbers which
go progressively ON from SD64 through SD79 are registered.
The F numbers turned OFF by RST F instruction are deleted from SD64 SD79, and the F numbers stored after the deleted F numbers are shifted to
the preceding registers.
Execution of the LEDR instruction shifts the contents of SD64 to SD79 up
by one.
After 16 annunciators have been detected, detection of the 17th will not be
stored from SD64 through SD79.

SD64
SD65
SD66
SD67
SD68

SD71
SD72

Table of
detected
annunciator
numbers

SD63 0
Annunciator
detection number

SD73
SD74
SD75
SD76
SD77
SD78

CHK number

SD90
SD91
SD92
SD93
SD94
SD95
SD96
SD97
SD98
SD99

Step transition
monitoring timer
setting value
(Enabled only
when SFC
program exists)

F number for timer
set value and time
over error

SD64
SD65
SD66
SD67
SD68
SD69
SD70
SD71
SD72
SD73
SD74
SD75
SD76
SD77
SD78
SD79

D9128
D9129
D9130

8 (Number of
annunciators
detected)

0 50 50 50 50 50 50 50 50 50 50 50 99
0 0 25 25 99 99 99 99 99 99 99 99 15
0 0 0 99 0 15 15 15 15 15 15 15 70
0 0 0 0 0 0 70 70 70 70 70 70 65
0 0 0 0 0 0 0 65 65 65 65 65 38
0 0 0 0 0 0 0 0 38 38 38 38 110
0 0 0 0 0 0 0 0 0 110 110 110 151
0 0 0 0 0 0 0 0 0 0 151 151 210
0 0 0 0 0 0 0 0 0 0 0 210 0
0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0

D9131
QCPU
S (Instruction
execution)

b8 b7

New

(Number
detected)

New
New
New
New
S (Instruction
execution)

New
D9108
D9109
D9110

D9111
D9112

F number setting
(0 to 255)

New

• Set the annunciator number (F number) that will
be turned ON when the step transition
monitoring timer setting or monitoring timeout
occurs.

b15

D9132

New

• Error codes detected by the CHK instruction are stored as BCD code.
Corresponds to
SM90
Corresponds to
SM91
Corresponds to
SM92
Corresponds to
SM93
Corresponds to
SM94
Corresponds to
SM95
Corresponds to
SM96
Corresponds to
SM97
Corresponds to
SM98
Corresponds to
SM99

D9127

Timer time limit
setting
(1 to 255s:
(1s units))

• Turning ON any of SM90 to SM99 during an
active step starts the timer, and if the transition
condition next to the corresponding step is not
met within the timer time limit, the set
annunciator (F) turns ON.

Qn(H)
QnPH
QnPRH

D9113
D9114
New
New
New

12 - 37

12.2 SPECIAL REGISTER LIST

SD79
SD80

D9126

SD62 0 50 50 50 50 50 50 50 50 50 50 50 99 (Number
detected)

SD70

D9125

SET SET SET RST SET SET SET SET SET SET SET
F50 F25 F99 F25 F15 F70 F65 F38 F110 F151 F210 LEDR

SD69

Table12.18 Special register

Number

Name

Meaning

Set by
(When Set)

Explanation

Corresponding
ACPU

Corresponding
CPU

SD100

Transmission
speed storage
area

Stores the
transmission
speed specified in
the serial
communication
setting.

96
576

: 9.6kbps,
: 57.6kbps,

b15

SD101

Communication
setting storage
area

Stores the
communication
setting specified in
the serial
communication
setting.

192
1152

: 19.2kbps,
: 115.2kbps

384 : 38.4kbps,

b6 b5 b4 b3

Write during RUN setting
0: Disabled
1: Enabled

S (Power-ON or
reset)

New

Sumcheck presence
0: Absent
1: Present

Q00/Q01
Q00UJ
Q00U
Q01U
Q02U*4

S (Power-ON or
reset)

New

S (Power-ON or
reset)

New

Qn(H)
QnPH
QnPRH
QnU*3

New

Q00/Q01
Q00UJ
Q00U
Q01U
Q02U*4

* : Since the data is used by the system, it is undefined.
Transmission
wait time
storage area

Stores the
transmission wait
time specifed in
the serial
communication
setting.

SD105

CH1
transmission
speed setting
(RS-232)

Stores the preset
transmission
speed when GX
Developer is
used.

96
: 9600bps,
192 : 19.2kbps, 384
: 38.4kbps,
576 : 57.6kbps,
1152 : 115.2kbps
*: Other than RS-232 connection holds the data at RS-232 connection.
(When disconnected, the default value is 1152.)

SD110

Data sending
result storage
area

Stores the data
sending result
when the serial
communication
function is used.

Stores the error code at the timeout sending data.

Stores the data
receiving result
when the serial
communication
function is used.

Stores the error code at the time of receiving data.

S (Error)

Amount of battery
consumption

Displays the current amount of battery consumption.
The value range:1 to 2(Q00UJCPU, Q00UCPU, Q01UCPU,
Q02UCPU, Q03UD(E)CPU, Q04UD(E)HCPU)
1 to 3(Q06UD(E)HCPU)
1 to 4(Q10UD(E)HCPU, Q20UD(E)HCPU,
Q13UD(E)HCPU, Q26UD(E)HCPU)

S (Status
change)

New

QnU*4

S (Status
change)

New

QnU

SD102

SD111

Data receiving
result storage
area

SD118

Amount of
battery
consumption

0
: No waiting time
10 to 150: Waiting time (unit: ms)
Defaults to 0.

S (Error)

Stores the factor which makes the battery life-prolonging function valid.
When SD119 is other than 0, the battery life-prolonging function is valid.

SD119

Battery lifeprolonging
factor

Battery lifeprolonging factor

b15

0:No factor
1:Foctor

b2 b1 b0

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 - 38

CHAPTER12 PECIAL RELAY LIST AND SPECIAL REGISTER LIST

Table12.18 Special register

Number

Name

Meaning

Set by
(When Set)

Explanation

Corresponding
ACPU

1
Corresponding
CPU

D9
• The numbers of output modules whose fuses have blown are input as a
bit pattern (in units of 16 points).
(If the module numbers are set by parameter, the parameter-set
numbers are stored.)

SD130
SD131
SD132
SD133
SD134

Fuse blown
module

SD135

Bit pattern in units
of 16 points,
indicating the
modules whose
fuses have blown
0: No blown fuse
1: Blown fuse
present

SD130

SD137

(Y7B0)

1
(Y1A0)

(Y730)

SD136

SD152

SD156
SD157

• When I/O modules, of which data are different from those entered 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 numbers set in
parmeters when parameter setting has been performed.)

SD151

SD155

• Not cleared even if the blown fuse is replaced with a new one.
This flag is cleared by error resetting operation

SD150

SD154

Indicates fuse blow.

SD137

SD153

b15 b14 b13 b12 b11b10 b9 b8 b7 b6 b5 b4 b3 b2 b1 b0
1
1
0 0 0 (YC0) 0 0 0 (Y80) 0 0 0 0 0 0 0 0

1
SD131 (Y1F0)
0

I/O module
verify error

Bit pattern, in units
of 16 points,
indicating the
modules with
verify errors.
0: No I/O verify
errors
1: I/O verify error
present

S (Error)

New

Q00J/Q00/Q01

b15 b14 b13 b12 b11 b10 b9 b8 b7 b6 b5 b4 b3 b2 b1 b0
1
0 0 0 0 0 0 0 0 0 0 0 0 0 0 (X Y)
0
1
SD151 0
0 0 0 0 0 ( X Y) 0 0 0 0 0 0 0 0 0
190
SD150 0

SD157 0 ( X Y) 0
7E0

Indicates an I/O module verify error.
• Not cleared even if the blown fuse is replaced with a new one.
This flag is cleared by error resetting operation.

12.2 SPECIAL REGISTER LIST

12 - 39

(2) System information
Table12.20 Special register

Number

Name

Meaning

Set by
(When Set)

Explanation

Corresponding
ACPU

Corresponding
CPU

D9
• The CPU switch status is stored in the following format:

b15

b12 b11 to

b8 b7

Status of switch

Status of CPU
switch

b4 b3

Empty

0: RUN
1: STOP
2: L.CLR

1): CPU switch status

SD200

2): Memory card
switch

Always OFF

3): DIP switch

b8 through b12 correspond to
SW1 through SW5 of system
setting switch 1.
0: OFF, 1: ON.
b13 through b15 are empty.

S (Every END
processing)

New

Qn(H)
QnPH
QnPRH

S (Every END
processing)

New

Q00J/Q00/Q01

S (when RUN/
STOP/RESET
switch changed)

New

QnU

S (Status
change)

New

Q00J/Q00/Q01
Qn(H)
QnPH
QnPRH

S (Status
change)

New

QnU

• The CPU switch status is stored in the following format:

b15

b8 b7

b4 b3
2)

Empty

1):

CPU switch status

0: RUN
1: STOP

2):

Memory card switch

Always OFF

• The CPU switch status is stored in the following format:

b15

b8 b7

b4 b3
2)

Empty

1):

CPU switch status

0: RUN
1: STOP

2):

Memory card switch

Always OFF

• 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

SD201

LED status

Status of
CPU-LED

b12b11
7)

b8 b7
5)

b4 b3
3)

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
(The Basic model QCPU does not include 3) to 8).)
• 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
8)

b12b11
7)

b8 b7
5)

b4 b3
3)

1): RUN
5): BOOT
2): ERROR
6): Empty
3): USER
7): Empty
4): BAT.
8): MODE
(The Q00UJCPU, Q00UCPU, and Q01UCPU do not include 5).)

12 - 40

b0
1)

CHAPTER12 PECIAL RELAY LIST AND SPECIAL REGISTER LIST

Table12.20 Special register

Number

Name

Meaning

Set by
(When Set)

Explanation

Corresponding
ACPU

1
Corresponding
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
SD202

LED off
command

b8
Fixed
to 0

Bit pattern of LED
that is turned off

b4
Fixed
to 0

b0
Fixed
to 0

2
3

New

USER
LED

Qn(H)
QnPH
QnPRH
QnU

BOOT
LED
(The Q00UJCPU, Q00UCPU, and Q01UCPU cannot specify the BOOT
LED.)
• The CPU operating status is stored as indicated in the following figure:

b15

b12 b11

b8 b7

b4 b3

1): Operating status
of CPU
SD203

Operating
status of CPU

Operating status
of CPU

2): STOP/PAUSE
cause

RUN
STEP-RUN (For the QnACPU only)
STOP
PAUSE

S (Every END
processing)

0: Instruction in remote operation program
from RUN/STOP switch ("RUN/STOP/
RESET switch" for Basic model QCPU)
1: Remote contact
2: Remote operation from GX Developer/
serial communication, etc.
3: Internal program instruction

D9015
format
change

7
QCPU

4: Error

• The LED display color of the LED status shown in SD201 1) to 8).
b15

b12

b11

b8 b7

b4 b3

1)RUN LED
0: OFF
1: Green
2)ERROR LED
0: OFF
1: Red

SD204

LED display
color

CPU-LED display
color

3)USER LED
0: OFF
1: Red
4)BAT. LED
0: OFF
1: Yellow
2: Green

S (status
change)

New

QnU

5)BOOT LED
0: OFF
1: Green
6)Empty
7)Empty
8)MODE LED
0: OFF
1: Green

(The Q00UJCPU, Q00UCPU, and Q01UCPU do not include 5).)

12 - 41

12.2 SPECIAL REGISTER LIST

Note: Priority is
earliest first

0:
1:
2:
3:

Table12.20 Special register

Number

Name

Meaning

Set by
(When Set)

Explanation

Corresponding
ACPU

Corresponding
CPU

SD207

Priorities 1 to 4

SD208

Priorities 5 to 8

• When error is generated, the LED display (flicker) is made according to
the error number setting priorities.
(The Basic model QCPU supports only the annunciator (error item No.
7).
• 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
SD207 Priority 4
Priority 3
SD208 Priority 8
Priority 7
SD209
Priority 11

D9038

b7 to b4 b3 to b0
Priority 1
Priority 2
Priority 5
Priority 6
Priority 10 Priority 9

D9039
format
change

(Priority 11 is valid when Redundant CPU is used.)
LED display
priority ranking

SD209

Priorities 9 to 11

Default Value
SD207 = 4321H(0000H for Basic model QCPU)
SD208 = 8765H(0700H for Basic model QCPU)
(0765H for Redundant CPU)
SD209 = 00A9H(0000H for Basic model QCPU)
(0B09H for Redundant CPU)
• No display is made if "0" is set.
• In case of the Basic model QCPU, the ERR. LED turns ON when the
annunciator turns ON, if "7" has been set to either of priorities 1 to 11.
• In case of the Basic model QCPU, the ERR. LED does not turn ON
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.

Q00J/ Q00/Q01*9
Qn(H)
QnPH
QnPRH
QnU

New

• The year (last two digits) and month are stored as BCD code as shown
below:
SD210

Clock data

Clock data (year,
month)

b15 to b12 b11 to

b8 b7 to

b4 b3 to

b0 Example:
D9025

July, 1993
9307H
Year

Month

• The day and hour are stored as BCD code as shown below:

b15 to b12 b11 to
SD211

Clock data

b8 b7 to

b4 b3 to

Clock data (day,
hour)

b0 Example:

31st, 10 a.m.
3110H
Day

S (Request)/U

D9026

Hour

• The minutes and seconds (after the hour) are stored as BCD code as
shown below:
SD212

Clock data

Clock data
(minute, second)

b15 to b12 b11 to

12 - 42

b4 b3

b0 Example:

35 min, 48 s
3548H
Minute

*9: Function version is B or later.

b8 b7

Second

D9027

QCPU

CHAPTER12 PECIAL RELAY LIST AND SPECIAL REGISTER LIST

Table12.20 Special register

Number

Name

Meaning

Set by
(When Set)

Explanation

Corresponding
ACPU

1
Corresponding
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

b4 b3

b0 Example:

1993, Friday
1905H
SD213

Clock data

Clock data
(higher digits of
year, day of week)

Day of the week
0
Sunday
1
Monday
2
Tuesday
3 Wednesday
4 Thursday
5
Friday
6 Saturday

Higher digits of year (19 or 20)

S (Request)/U

D9028

• LED display ASCII data (16 characters) stored here.
(On the Basic model QCPU, the registers store the message (16
characters of ASCII data) at error occurrence (including annunciator
ON).

SD220

SD221

b15

SD220

SD222

SD221
SD223

SD222
LED display
data

LED display data

SD224

SD223
SD224

SD225

SD225
SD226

SD226

SD227

b8 b7

15th character from
the right
13th character from
the right
11th character from
the right
9th character from
the right
7th character from
the right
5th character from
the right
3rd character from
the right
1st character from
the right

QCPU

16th character from
the right
14th character from
the right
12th character from
the right
10th character from
the right
8th character from
the right
6th character from
the right
4th character from
the right
2nd character from
the right

7
S (When
changed)

New

• The LED display device data at the time of CHK is not stored in the
Basic model QCPU and the Universal model QCPU.

SD235

Module to which
online module
change is being
performed

The header I/O
number of the
module to which
online module
change is being
performed /10H

• 10H is added to the value of the header I/O number of which the online
module change is being performed.

SD240

Base mode

0: Automatic
mode
1: Detail mode

SD241

Extension stage
number

0: Main base only
1 to 7: Extension
stage number

S (During online
module change)

New

• Stores the base mode.

S (Initial)

New

• Stores the maximum number of the extension bases being installed.

S (Initial)

New

QnPH
QnPRH

QCPU

12 - 43

12.2 SPECIAL REGISTER LIST

SD227

Table12.20 Special register

Number

Name

Meaning

Set by
(When Set)

Explanation

Corresponding
ACPU

Corresponding
CPU

A/Q base
differentiation

Base type
differentiation
0: QA**B is
installed
(A mode)
1: Q**B is installed
(Q mode)

Fixed to 0

b2 b1 b0

to
Main base unit
1st extension
base
2nd extension
base
to
7th extension
base

b4
Installed Q base
presence/
absence
SD242

Base type
differentiation
0: Base not
installed
1: Q**B is installed

S (Initial)

New

Qn(H)
QnPH
QnPRH

S (Initial)

New

Q00J/Q00/Q01

S (Initial)

New

QnU

S (Initial)

New

Qn(H)
QnPH
QnPRH
QnU

Fixed to 0
when the
base is not
installed.

b2 b1 b0

Fixed to 0

to
Main base unit
1st extension base
2nd extension base
to
4th extension base

b7
Fixed to 0

Installed Q base
presence/
absence

b2 b1 b0

to
Main base unit
1st extension
base
2nd extension
base
to
7th extension
base

Base type
differentiation
0: Base not
installed
1: Q**B is installed

Fixed to 0
when the
base is not
installed.

• 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.
b15 to b12 b11 to b8 b7 to b4 b3 to b0

SD243

Extension Extension
SD243 Extension
3
2
1

No. of base
slots

No. of base slots

SD244

SD243

SD244

No. of base
slots (Operation
status)

SD250

• As shown above, each area stores the number of slots being installed.
• 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.
b15 to b12 b11 to b8 b7 to b4 b3 to b0
Extension Extension Extension Main
3
2
1
to Fixed to Fixed to Extension
SD244 Fixed
0
0
0
4

SD243
No. of base slots

S (Initial)

• As shown above, each area stores the number of slots being installed.
(Number of set slots when parameter setting has been made)

SD245

SD246

Main

Extension Extension Extension
SD244 Extension
7
6
5
4

No. of base
slots (Mounting
status)

No. of base slots

b15 to b12 b11 to b8 b7 to b4 b3 to b0
Extension Extension Main
SD245 Extension
3
2
1
to Fixed to Fixed to Extension
SD246 Fixed
0
0
0
4

Q00J/Q00/Q01

New

Q00J/Q00/Q01*9

S (Initial)

• As shown above, each area stores the number of module-mounted slots
of the base unit (actual number of slots of the installed base unit).

Loaded
maximum I/O

Loaded maximum
I/O No.

*9: Function version is B or later.

12 - 44

• When SM250 goes from OFF to ON, the upper 2 digits of the final I/O
number plus 1 of the modules loaded are stored as BIN values.

S (Request
END)

New

Qn(H)
QnPH
QnPRH

• The upper 2 digits of the final I/O number plus 1 of the modules loaded
are stored as BIN values.

S (Initial)

New

Q00J/Q00/Q01
QnU

CHAPTER12 PECIAL RELAY LIST AND SPECIAL REGISTER LIST

Table12.20 Special register

Number

Name

Meaning

Set by
(When Set)

Explanation

Corresponding
ACPU

1
Corresponding
CPU

D9
Number of
modules installed

SD254

SD256
SD257
SD258

SD259

MELSECNET/
10.
MELSECNET/H
information

Information from 1st module

SD255

• Indicates the number of mounted MELSECNET/10 modules or
MELSECNET/H modules.

I/O No.

• Indicates I/O number of mounted MELSECNET/10 module or
MELSECNET/H module

Network
No.

• Indicates network No. of mounted MELSECNET/10 module or
MELSECNET/H module

Group
number

• Indicates group No. of mounted MELSECNET/10 module or
MELSECNET/H module

Station
No.

• Indicates station No. of mounted MELSECNET/10 module or
MELSECNET/H module

Standby
information

• In the case of standby stations, the module number of the standby
station is stored. (1 to 4)

QCPU

S (Initial)

New
Qn(H)
QnPH
QnPRH

Information from
2nd module

• Configuration is identical to that for the first module.

QnU*10

SD265
to
SD269

Information from
3rd module

• Configuration is identical to that for the first module.

SD270
to
SD274

Information from
4th module

Qn(H)
QnPH
QnPRH

• Configuration is identical to that for the first module.

QnU*11

SD280

CC-Link error

Error detection
status

b15 to b12 b11 to
Empty

b8 b7

Information
of 1)

b4 b3

6
7

1) When Xn0 of the mounted CC-Link module turns ON, the bit of the
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.

Information
of 2)

3
12

SD260
to
SD264

Information
of 3)

b0
S (Error)

New

Qn(H)
QnPH
QnPRH

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
counted.)

*10: The Universal model QCPU except the Q00UJCPU, Q00UCPU, and Q01UCPU.
*11: The Universal model QCPU except the Q00UJCPU, Q00UCPU, Q01UCPU, and Q02UCPU.

12 - 45

12.2 SPECIAL REGISTER LIST

1st
module
2nd
module
3rd
module
4th
module

Table12.20 Special register

Number

Name

Meaning

Set by
(When Set)

Explanation

Corresponding
ACPU

Corresponding
CPU

D9
1) When Xn0 of the mounted CC-Link module turns ON, the bit of the
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.

Information
of 3)

SD281

CC-Link error

Error detection
status

b15 to b12 b11 to
Empty

Information
of 2)

b8 b7

Information
of 1)

b4 b3

Qn(H)*14

5st
module
6nd
module
7rd
module
8th
module

S (Error)

New

QnPH*14
QnPRH*15

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
counted.)
SD286

Points assigned to
M (for extension)

• The number of points assigned to M is stored with 32 bits.
• Even if the points assigned to M are 32k points or less, the points are
stored.

Points assigned to
B (for extension)

• The number of points assigned to B is stored with 32 bits.
• Even if the points assigned to B are 32k points or less, the points are
stored.

SD290

Number of points
assigned for X

• Stores the number of points currently set for X devices

SD291

Number of points
assigned for Y

• Stores the number of points currently set for Y devices

Number of points
assigned for M

• Stores the number of points currently set for M devices

Number of points
assigned for L

• Stores the number of points currently set for L devices

Number of points
assigned for B

• Stores the number of points currently set for B devices

SD295

Number of points
assigned for F

• Stores the number of points currently set for F devices

SD296

Number of points
assigned for SB

• Stores the number of points currently set for SB devices

SD297

Number of points
assigned for V

• Stores the number of points currently set for V devices

SD298

Number of points
assigned for S

• Stores the number of points currently set for S devices

SD299

Number of points
assigned for T

• Stores the number of points currently set for T device

Number of points
assigned for ST

• Stores the number of points currently set for ST devices

Number of points
assigned for C

• Stores the number of points currently set for C devices

SD302

Number of points
assigned for D

• Stores the number of points currently set for D devices

SD303

Number of points
assigned for W

• Stores the number of points currently set for W devices

SD304

Number of points
assigned for SW

• Stores the number of points currently set for SW devices

SD287
SD288

Device
assignment

SD289

SD292
SD293
SD294

SD300
SD301

Device
assignment
(Same as
parameter
contents)

New

S (Initial)

New

QnU*16

QCPU

S (Initial)

*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 - 46

S (Initial)

New

CHAPTER12 PECIAL RELAY LIST AND SPECIAL REGISTER LIST

Table12.20 Special register

Number

Meaning

Explanation

Device
assignment
(Index register)

16 bit modification
Number of points
assigned for Z

• Stores the number of points of index register (Z) to be modified in the
range of 16 bits.
(The assignment is set by the ZR device index modification setting
parameter.)

Device
assignment
(Same as
parameter
contents)

Number of points
assigned for ZR
(for extension)

• Stores the number of ZR device points (except the number of points of
extended data register (D) and extended link register (W)). The number
of assignment points of ZR device is stored into this SD only when 1k
point or more is set to the extended data register (D) and extended link
register (W).

Number of points
assigned for D (for
inside + for
extension)

• Stores the total number of points of the extended data register (D) and
data register in internal device memory area (stores the value in 32-bit
binary).

Number of points
assigned for W
(for inside + for
extension)

• Stores the total number of points of the extended link register (W) and
link register in internal device memory area (stores the value in 32-bit
binary).

Time reserved for
communication
processing

• 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
communication with other devices (GX Developer, serial communication
units) becomes.
• If the designated value is out of the range above, it is processed that no
setting is made.
• Setting range: 1 to 100 ms
• Note that the scan time becomes longer by the designated time.

SD340

No. of modules
installed

• Indicates the number of mounted Ethernet module.

SD341

I/O No.

• Indicates I/O No. of mounted Ethernet module

SD342

Network
No.

• Indicates network No. of mounted Ethernet module

Group No.

• Indicates group No. of mounted Ethernet module

Station
No.

• Indicates station No. of mounted Ethernet module

Empty

• Empty
(With QCPU, the Ethernet module IP address of the 1st module is stored
in buffer memory.)

Empty

• Empty
(With QCPU, the Ethernet module error code of the 1st module is read
with the ERRRD instruction.)

Set by
(When Set)

1
Corresponding
CPU

SD305

SD306
SD307
SD308
SD309
SD310
SD311

SD315

Device
assignment
(assignment
including the
number of
points set to the
extended data
register (D) and
extended link
register (W))

Time reserved
for
communication
processing

SD343
SD344

Ethernet
information

SD345 to
SD346

SD347
SD348 to
SD354
SD355 to
SD361
SD362 to
SD368

Ethernet
information

Information of 1st module

Information from
2nd module

• Configuration is identical to that for the first module.

Information from
3rd module

• Configuration is identical to that for the first module.

Information from
4th module

• Configuration is identical to that for the first module.

S (Initial)

New

QnU

3
12
S (Initial)

New

QnU

*17

6
U

New

Q00J/Q00/Q01
Qn(H)
QnPH
QnPRH

7
8

QCPU

S (Initial)

New

Qn(H)
QnPH
QnPRH
QnU*10

S (Initial)

New

Qn(H)
QnPH
QnPRH
QnU*11

*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 - 47

12.2 SPECIAL REGISTER LIST

Name

Corresponding
ACPU

Table12.20 Special register

Number

Name

Meaning

Explanation

Set by
(When Set)

Corresponding
ACPU

Corresponding
CPU

SD380

Ethernet
instruction
reception status

Instruction
reception status of
1st module

b15 to b8 b7 b6 b5 b4 b3 b2 b1 b0
0
Not used
Instruction reception
status of channel 1
Instruction reception
status of channel 2
Instruction reception
status of channel 3
Instruction reception
status of channel 4
Instruction reception
status of channel 5
Instruction reception
status of channel 6
Instruction reception
status of channel 7
Instruction reception
status of channel 8

ON: Received (Channel is being used.)
OFF: Not received (Channel is not used.)
SD381

SD382

Ethernet
instruction
reception
status

SD383

12 - 48

Instruction
reception status of
2nd module

• Configuration is identical to that for the first module.

Instruction
reception status of
3rd module

• Configuration is identical to that for the first module.

Instruction
reception status of
4th module

• Configuration is identical to that for the first module.

S (Instruction
execution)

New

QnPRH

CHAPTER12 PECIAL RELAY LIST AND SPECIAL REGISTER LIST

Table12.20 Special register

Number

Name

Meaning

Set by
(When Set)

Explanation

Corresponding
ACPU

Corresponding
CPU

D9
Number of
multiple CPUs

SD393

Q00/Q01*9
QnU

• The number of CPU modules that comprise the multiple CPU system is
stored. (1 to 3, Empty also included)
• The CPU module types of No. 1 CPU to 3 and whether the CPU
modules are mounted or not are stored.

SD394

S (Initial)

SD395

Multiple CPU
system
information

SD396

No. 1 CPU
operation status

SD397

No. 2 CPU
operation status

• In a multiple CPU system configuration, the CPU number of the host
CPU is stored.
CPU No. 1: 1, CPU No. 2: 2, CPU No. 3: 3, CPU No. 4: 4

SD399

No. 4 CPU
operation statu

S (Initial)

New

Qn(H)*9
QnPH
QnU

to
Vacancy

to
b8 b7 to
b4 b3
b0
Classification Operation status

Q00/Q01*9
QnU*17
S (END
processing
error)

0: Normal
1: Minor fault
2: Medium fault
3: Major fault
FH: Reset

0: RUN
2: STOP
3: PAUSE
4: Initial
FH: Reset
QnU*11

(3) System clocks/counters
Table12.21 Special register

Name

Meaning

Explanation

Set by
(When Set)

Corresponding
ACPU

Corresponding
CPU

D9
SD412
SD414
SD415

SD420

SD430

1 second
counter

Number of counts
in 1-second units

2n second clock
setting
2nms clock
setting

2n second clock
units

Scan counter

Low speed scan
counter

2nms clock units

Number of counts
in each scan

• Following programmable controller CPU module RUN, 1 is added each
second
• Count repeats from 0 to 32767 to -32768 to 0
• Stores value n of 2n second clock (Default is 30)
• Setting can be made between 1 and 32767
• Stores value n of 2nms clock (Default is 30)
• Setting can be made between 1 and 32767
• Incremented by 1 for each scan execution after the CPU module is set to
RUN.
(Not counted by the scan in an initial execution type program.)
• Count repeats from 0 to 32767 to -32768 to 0
• Incremented by 1 for each scan execution after the CPU module is set to
RUN.
• Count repeats from 0 to 32767 to -32768 to 0
• Incremented by 1 for each scan execution after the CPU module is set to
RUN.
• Count repeats from 0 to 32767 to -32768 to 0
• Used only for low speed execution type programs

New

*9: Function version is B or later.
*11: The Universal model QCPU except the Q00UJCPU, Q00UCPU, Q01UCPU, and Q02UCPU.
*17: The Universal model QCPU except the Q00UJCPU.

Number

S (Status
change)

D9022

New

S (Every END
processing)

New

S (Every END
processing)

New

Q00J/Q00/Q01

S (Every END
processing)

New

Qn(H)
QnPH

QCPU

Qn(H)
QnPH
QnPRH
QnU

12 - 49

12.2 SPECIAL REGISTER LIST

No. 3 CPU
operation status

Q00/Q01*9

The operation information of each CPU No. is stored.
(The information on the number of multiple CPUs indicated in SD393 is
stored.)

b15 b14

CPU module type
0: PLC CPU
1: Motion CPU
2: PC CPU

mounted
0: Not mounted
1: Mounted
SD398

New
Q00/Q01*9

CPU module mounted or
not mounted
0: Not mounted
1: Mounted

Multiple CPU
number

b15 to b12 b11 to
b8 b7
b0
to b4 b3 to
Empty (0) CPU No.3
CPU No.2
CPU No.1

CPU mounting
information

SD394

(4) Scan information
Table12.22 Special register

Number

Name

Meaning

Explanation

Set by
(When Set)

Corresponding
ACPU

Corresponding
CPU

D9
SD500

Execution
program No.

Program No. in
execution

• Program number of program currently being executed is stored as BIN
value.

SD510

Low speed
excution type
program No.

Low speed
execution type
program No. in
execution

• Program number of low speed excution type program No. currently
being executed is stored as BIN value.
• Enabled only when SM510 is ON.

Current scan time
(in 1 ms units)

SD520

Current scan
time
SD521

Current scan time
(in 100 s units)

SD522

Initial scan time
(in 1 ms units)
Initial scan time

SD523

Initial scan time
(in 100 s units)

SD524

Minimum scan
time (in 1 ms
units)

Minimum scan
time
SD525

Minimum scan
time (in 100 s
units)

SD526

Maximum scan
time (in 1 ms
units)

Maximum scan
time
SD527

SD528

SD529

SD532

SD533

SD534

SD535

Current scan
time for low
speed execution
type programs

Minimum scan
time for low
speed execution
type programs

Maximum scan
time for low
speed execution
type programs

SD540
END processing
time
SD541

12 - 50

Maximum scan
time (in 100 s
units)
Current scan time
(in 1 ms units)
Current scan time
(in 100 s units)
Minimum scan
time (in 1 ms
units)
Minimum scan
time (in 100 s
units)
Maximum scan
time (in 1 ms
units)
Maximum scan
time (in 100 s
units)
END processing
time (in 1 ms
units)
END processing
time (in 100 s
units)

• The current scan time is stored into SD520 and SD521.
(Measurement is made in 100 s units. (For the Universal model QCPU,
in 1 s units.))
SD520: Stores the ms place. (Storage range: 0 to 65535)
SD521: Stores the s place. (Storage range: 0 to 900 (For the
Universal model QCPU, storage range is 0 to 999))
(Example) When the current scan time is 23.6ms, the following values are
stored.
SD520 = 23
SD521 = 600
• Stores the scan time of an initial execution type program into SD522 and
SD523.
(Measurement is made in 100 s units. (For the Universal model QCPU,
in 1 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
model QCPU, storage range is 0 to 999))
• Stores the minimum value of the scan time except that of an initial
execution type program into SD524 and SD525. (Measurement is made
in 100 s units. (For the Universal model QCPU, in 1 s units.))
SD524: Stores the ms place. (Storage range: 0 to 65535)
SD525: Stores the s place. (Storage range: 0 to 900 (For the Universal
model QCPU, storage range is 0 to 999))

S (Status
change)

New

Qn(H)
QnPH
QnPRH
QnU

S (Every END
processing)

New

Qn(H)
QnPH

S (Every END
processing)

D9018
format
change

S (Every END
processing)

New

S (First END
processing)

New

S (Every END
processing)

D9017
format
change

S (Every END
processing)

New

QCPU

Qn(H)
QnPH
QnPRH
QnU

D9019
format
change

• Stores the maximum value of the scan time except that of an initial
execution type program into SD526 and SD527. (Measurement is made
in 100 s units. (For the Universal model QCPU, in 1 s units.))
SD526: Stores the ms place. (Storage range: 0 to 65535)
SD527: Stores the s place. (Storage range: 0 to 900 (For the Universal
model QCPU, storage range is 0 to 999))

S (Every END
processing)

• Stores the current scan time of a low speed execution type program into
SD528 and SD529.
(Measurement is made in 100 s units.)
SD528: Stores the ms place. (Storage range: 0 to 65535)
SD529: Stores the s place. (Storage range: 0 to 900)

S (Every END
processing)

New

• Stores the minimum value of the scan time of a low speed execution
type program into SD532 and SD533.
(Measurement is made in 100 s units.)
SD532: Stores the ms place. (Storage range: 0 to 65535)
SD533: Stores the s place. (Storage range: 0 to 900)

S (Every END
processing)

New

• Stores the maximum value of the scan time except that of the first scan
of a low speed execution type program into SD534 and SD535.
(Measurement is made in 100 s units.)
SD534: Stores the ms place. (Storage range: 0 to 65535)
SD535: Stores the s place. (Storage range: 0 to 900)

S (Every END
processing)

New

• Stores the time from the end of a scan execution type program to the
start of the next scan into SD540 and SD541.
(Measurement is made in 100 s units.(For the Universal model QCPU,
in 1 s units.))
SD540: Stores the ms place. (Storage range: 0 to 65535)
SD541: Stores the s place. (Storage range: 0 to 900) (Storage range: 0
to 900 (For the Universal model QCPU, storage range is 0 to 999))

S (Every END
processing)

New

Qn(H)
QnPH

Qn(H)
QnPH
QnPRH
QnU

CHAPTER12 PECIAL RELAY LIST AND SPECIAL REGISTER LIST

Table12.22 Special register

Number

Name

Meaning

Explanation

Set by
(When Set)

Corresponding
ACPU

1
Corresponding
CPU

D9
SD524
Minimum scan
time
SD525

SD526
Maximum scan
time

Minimum scan
time (in 1 ms
units)
Minimum scan
time (in 100 s
units)
Maximum scan
time (in 1 ms
units)

SD527

Maximum scan
time (in 100 s
units)

SD540

END processing
time (in 1 ms
units)

END processing
time
SD541

END processing
time (in 100 s
units)

SD542

Constant scan
wait time (in 1 ms
units)

Constant scan
wait time
SD543

Constant scan
wait time (in 100
s units)

SD544

Cumulative
execution time for
low speed
execution type
programs
(in 1 ms units)

Cumulative
execution time
for low speed
execution type
programs
SD545

Execution time
for low speed
execution type
programs

Execution time for
low speed
execution type
programs
(in 1 ms units)

SD547

Execution time for
low speed
execution type
programs
(in 100 s units)

SD548

Scan execution
type program
execution time (in
1 ms units)

Scan execution
type program
execution time
SD549

Scan execution
type program
execution time (in
100 s units)

SD548

Scan program
execution time
(in 1 ms units)
Scan program
execution time

SD549

SD550

Service interval
measurement
module

SD551
Service interval
time
SD552

Scan program
execution time
(in 100 s units)

Unit/module No.
Module service
interval
(in 1 ms units)
Module service
interval
(in 100 s units)

S (Every END
processing)

3
New

• Stores the maximum value of the scan time into SD526 and SD527.
(Measurement is made in 100 s units.)
SD526: Stores the ms place. (Storage range: 0 to 65535)
SD527: Stores the s place. (Storage range: 0 to 900)

S (Every END
processing)

• Stores the time from when the scan program ends until the next scan
starts into SD540 and SD541.
(Measurement is made in 100 s units.)
SD540: Stores the ms place. (Storage range: 0 to 65535)
SD541: Stores the s place. (Storage range: 0 to 900)

S (Every END
processing)

• Stores the wait time for constant scan setting into SD542 and SD543.
(Measurement is made in 100 s units. (For the Universal model QCPU,
in 1 s units.))
SD542: Stores the ms place. (Storage range: 0 to 65535)
SD543: Stores the s place. (Storage range: 0 to 900 (For the Universal
model QCPU, storage range is 0 to 999))

S (Every END
processing)

• Stores the cumulative execution time of a low speed execution type
program into SD544 and SD545.
(Measurement is made in 100 s units.)
SD544: Stores the ms place. (Storage range: 0 to 65535)
SD545: Stores the s place. (Storage range: 0 to 900)
• Cleared to 0 after the end of one low speed scan.

S (Every END
processing)

Q00J/Q00/Q01

New

6
New

QCPU

7
8

New

Qn(H)
QnPH

• Stores the execution time of a low speed execution type program during
one scan into SD546 and SD547.
(Measurement is made in 100 s units.)
SD546: Stores the ms place. (Storage range: 0 to 65535)
SD547: Stores the s place. (Storage range: 0 to 900)
• Stored every scan.

S (Every END
processing)

New

• Stores the execution time of a scan execution type program during one
scan into SD548 and SD549.
(Measurement is made in 100 s units.)
SD548: Stores the ms place. (Storage range: 0 to 65535)
SD549: Stores the s place. (Storage range: 0 to 900)
• Stored every scan.

S (Every END
processing)

New

Qn(H)
QnPH
QnPRH

• Stores the execution time of a scan program during one scan into
SD548 and SD549.
(Measurement is made in 100 s units. (For the Universal model QCPU,
in 1 s units.))
SD548: Stores the ms place. (Storage range: 0 to 65535)
SD549: Stores the s place. (Storage range: 0 to 900 (For the Universal
model QCPU, storage range is 0 to 999))
• Stored every scan.

S (Every END
processing)

New

Q00J/Q00/Q01
QnU

New

• Sets I/O number for module that measures service interval.

• Stores the service interval for the module specified in SD550 into SD551
and SD552 when SM551 is turned ON.
(Measurement is made in 100 s units.)
SD551: Stores the ms place. (Storage range: 0 to 65535)
SD552: Stores the s place. (Storage range: 0 to 900)

S (Request)

New

Qn(H)
QnPH
QnPRH

12 - 51

12.2 SPECIAL REGISTER LIST

SD546

Cumulative
execution time for
low speed
execution type
programs
(in 100 s units)

• Stores the minimum value of the scan time into SD524 and SD525.
(Measurement is made in 100 s units.)
SD524: Stores the ms place. (Storage range: 0 to 65535)
SD525: Stores the s place. (Storage range: 0 to 900)

(5) Memory card
Table12.23 Special register

Number

Name

Meaning

Set by
(When Set)

Explanation

Corresponding
ACPU

Corresponding
CPU

D9
• Indicates the type of the memory card installed.
b15

b8 b7

b4 b3

SD600

Memory card
typs

Drive 1
(RAM) type

Memory card typs
Drive 2 type

0: Does not exist
1: SRAM card
0: Does not exist
(1: SRAM)
2: ATA card
3: Flash card

S (Initial and
card removal)

New

Qn(H)
QnPH
QnPRH
QnU

(The bits for the drive 1 (RAM) type and drive 2 (ROM) type are fixed to "0"
in the Q00UJCPU, Q00UCPU, and Q01UCPU.)
SD602

Drive 1
(Memory card
RAM) capacity

Drive 1 capacity

• Drive 1 capacity is stored in 1 k byte units.
• (Empty capacity after format is stored.)

S (Initial and
card removal)

New

SD603

Drive 2
(Memory card
ROM) capacity

Drive 2 capacity

• Drive 2 capacity is stored in 1 k byte units.*1

S (Initial and
card removal)

Qn(H)
QnPH
QnPRH

New

QnU*2

S (Status
change)

New

Qn(H)
QnPH
QnPRH

S (Status
change)

New

QnU*2

• The use conditions for memory card are stored as bit patterns .
(In use when ON)
• The significance of these bit patterns is indicated below:

Memory card
use conditions

Memory card use
conditions

b0 : Boot operation (QBT)

b8 : Not used

b1 : Parameters (QPA)

b9 : CPU fault history (QFD)

b2 : Device comments (QCD)

b10 : Not used

b3 : Device initial value (QDI)

b11 : Local device (QDL)

b4 : File register R (QDR)

b12 : Not used

b5 : Sampling trace (QTD)

b13 : Not used

b6 : Not used

b14 : Not used

b7 : Not used

b15 : Not used

• The use conditions for memory card are stored as bit patterns .
(In use when ON)
• The significance of these bit patterns is indicated below:

SD604

Memory card
use conditions

Memory card use
conditions

b0 : Boot operation (QBT)*1

b8 : Not used

b1 : Parameters (QPA)

b9 : Not used

b2 : Device comments (QCD)

b10 : Not used

b3 : Device initial value (QDI)*2

b11 : Local device (QDL)

b4 : File register R (QDR)

b12 : Not used

b5 : Sampling trace (QTD)

b13 : Not used

b6 : Not used

b14 : Not used

b7 : Backup data (QBP) *3

b15 : Not used

*1: Turned ON at boot start and OFF at boot completion.
*2: Turned ON when reflection of device initial value is started and OFF
when reflection of device initial value is completed.
*3: The module whose first 5 digits of serial No. is "10102" or later.

*1:

*2:

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 QCPU User's Manual (Hardware Design, Maintenance and Inspection).
The Universal model QCPU except the Q00UJCPU, Q00UCPU, and Q01UCPU.

12 - 52

CHAPTER12 PECIAL RELAY LIST AND SPECIAL REGISTER LIST

Table12.23 Special register
Number

Name

Meaning

Set by
(When Set)

Explanation

Corresponding
ACPU
D9

Corresponding
CPU

New

Qn(H)
QnPH
QnPRH
QnU

• Indicates the drive 3/4 type.
b15

SD620

Drive 3/4 typs

to
0

b8 b7

b4 b3

Drive 3
(Standrd
RAM)

Fixed to 1

Drive 4
(Standrd
ROM)

Fixed to 3

S (Initial)

(The bits for the drive 3 (standard RAM) type is fixed to "0" in the
Q00UJCPU.)
• Indicates the drive 3/4 type.
b15

b8 b7 to

to
0

b4 b3 to

0: Absent
Drive 3
(Standard RAM) 1: Present

S (Initial)

New

Q00J/Q00/Q01

Fixed to
Drive 4
(Standrd ROM) "3 (FLASH ROM)"

SD622

SD623

Drive 3
(Standard RAM)
capacity

Drive 4
(Standard
ROM) capacity

Drive 3 capacity

Drive 4 capacity

S (Initial)

New

Qn(H)
QnPH
QnPRH
QnU

• Drive 3 capacity is stored in 1k byte units.

S (Initial)

New

Q00J/Q00/Q01

• Drive 4 capacity is stored in 1 k byte units.
(Empty capacity after format is stored.)

S (Initial)

New

Qn(H)
QnPH
QnPRH
QnU

S (Initial)

New

Q00J/Q00/Q01

Drive 3/4 use
conditions

S (Status
change)

New

Qn(H)
QnPH
QnPRH

S (Status
change)

New

QnU

S (Status
change)

New

Q00J/Q00/Q01

b0 : Boot operation (QBT)

b8 : Not used

b1 : Parameters (QPA)

b9 : CPU fault history (QFD)

b2 : Device comments (QCD)

b10 : SFC trace (QTS)

b3 : Device initial value (QDI)

b11 : Local device (QDL)

b4 : File register (QDR)

b12 : Not used

b5 : Sampling trace (QTD)

b13 : Not used

b6 : Not used

b14 : Not used

b7 : Not used

b15 : Not used

• 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:

SD624

b8 : Module error log *2

b0 : Not used

Drive 3/4 use
conditions

b1 : Parameters (QPA)

b9 : Not used

b2 : Device comments (QCD)

b10 : Not used

b3 : Device initial value (QDI)*1

b11 : Local device (QDL)

b4 : File register (QDR)

b12 : Not used

b5 : Sampling trace (QTD)

b13 : Not used

b6 : Not used

b14 : Not used

b7 : Not used

b15 : Not used

*1: Turned ON at boot start and OFF at boot completion.
*2: Supported by the modules having a serial number (first five digits)
"11043" or later.
• The conditions for usage for drive 3/4 are stored as bit patterns.
b15

SD624

Drive 3/4 use
conditions

to
0

to
b5 b4
0 0 0

b0
0

Boot operation (QBT)
0: Not used 1: In use
File register (QDR)
0: Not used 1: In use

SD640

File register
drive

Drive number:

• Stores drive number being used by file register

S (Status
change) *10

New

Q00J/Q00/Q01
Qn(H)
QnPH
QnPRH
QnU*3

*3: The Universal model QCPU except the Q00UJCPU.
*10: On the Basic model QCPU, data is set at STOP to RUN or RSET instruction execution after parameter execution.

12 - 53

7
8

12.2 SPECIAL REGISTER LIST

• Drive 3 capacity is stored in 1 k byte units.
(Empty capacity after format is stored.)

• Drive 4 capacity is stored in 1k byte units.
• 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:

Drive 3/4 use
conditions

Table12.23 Special register

Number

Name

Meaning

Set by
(When Set)

Explanation

Corresponding
ACPU

Corresponding
CPU

D9
• Stores file register file name (with extension) selected at parameters or
by use of QDRSET instruction as ASCII code.

SD641
SD642

b15
b8
to
2nd character
4th character
6th character
8th character
1st character of
SD645
extension

SD641
SD642
SD643
SD644

SD643
SD644
SD645

SD646
File register file
name

File register file
name

SD645
SD646

SD647

File register
capacity

b0
to
1st character
3rd character
5th character
7th character

S (Status
change)

New

QnU*3

2EH(.)
2nd character of
the extension

b15
b8
to
2nd character (A)
4th character (N)
6th character ( )
8th character ( )
1st character of
the extension (Q)
3rd character of
the extension (R)

b7
b0
to
1st character (M)
3rd character (I)
5th character ( )
7th character ( )

S (Initial)

New

SD648

File register block
number

Q00J/Q00/Q01

2EH(.)
2nd character of
the extension (D)

• Stores the data capacity of the currently selected file register in 1 k word
units.

S (Status
change)

New

S (Initial)

File register
block number

Qn(H)
QnPH
QnPRH

• Stores file register file name (MAIN.QDR) selected at parameters as
ASCII code.

SD641
SD642
SD643
SD644

SD646

3rd character of
the extension

• Stores the currently selected file register block number.

S (Status
change) *10

Qn(H)
QnPH
QnPRH
QnU*3
Q00J/Q00/Q01

D9035

Q00J/Q00/Q01
Qn(H)
QnPH
QnPRH
QnU*3

SD650

Comment drive

Comment drive
number

SD651

SD653

SD655

Comment file
name

SD656

Boot designation
file drive number

SD660

SD662

SD664

New

b15
b8
to
2nd character
4th character
6th character
8th character
1st character of
SD655
the extension
3rd character of
SD656
the extension

SD651
SD652
SD653
SD654

b0
to
1st character
3rd character
5th character
7th character

S (Status
change)

New

S (Initial)

New

Qn(H)
QnPH
QnPRH
QnU

2EH(.)
2nd character of
the extension

• Stores the drive number where the boot designation file (*.QBT) is being
stored.
• Stores the file name of the boot designation file (*.QBT).

SD661

SD663

S (Status
change)

• Stores the comment file name (with extension) selected at the
parameters or by the QCDSET instruction in ASCII code.

SD652

SD654

• Stores the comment drive number selected at the parameters or by the
QCDSET instruction.

Boot operation
designation file

SD665

SD666

File name of boot
designation file

b15
b8
to
2nd character
4th character
6th character
8th character
1st character of
SD665
the extension
3rd character of
SD666
the extension

SD661
SD662
SD663
SD664

b0
to
1st character
3rd character
5th character
7th character

S (Initial)

2EH(.)
2nd character of
the extension

*3: The Universal model QCPU except the Q00UJCPU.
*4: The Universal model QCPU except the Q00UJCPU, Q00UCPU, and Q01UCPU.
*10: On the Basic model QCPU, data is set at STOP to RUN or RSET instruction execution after parameter execution.

12 - 54

New

Qn(H)
QnPH
QnPRH
QnU*4

CHAPTER12 PECIAL RELAY LIST AND SPECIAL REGISTER LIST

Table12.23 Special register

Number

Name

Meaning

Set by
(When Set)

Explanation

Corresponding
ACPU

1
Corresponding
CPU

SD670

Parameter
enable drive
information

Parameter enable
drive No.

• Stores information of parameter storage destination drive which is
enabled.
0: Drive 0 (Program memory)
1: Drive 1 (SRAM card)
2: Drive 2 (Flash card/ATA card)
4: Drive 4 (Standard ROM)
(Only drive 0 and drive 4 are valid in the Q00UJCPU, Q00UCPU, and
Q01UCPU.)

S (Initial)

New

Indicates the status of the latch data backup function.
Presence/
absence of
backup data

Status
0

SD671

Status of latch
data backup
function

Status display

No backup data

Absent

Restore operation at
turning power supply
ON from OFF
Restoring not executed
Restoring executed when
turning power supply
ON from OFF the
following time

Restore ready
completion

Restore execution
completion

Backup execution wait

Restoring not executed

Restore repeated
execution ready
completion

Restoring executed
when turning power
supply ON from OFF

Restoring not executed

Present

S (Status
change)

New

6
7

• "2 Restore ready completion" is a status immediately after restoring
data.
"3 Backup execution wait" is a status after turning power supply ON from
OFF at "2 Restore ready completion".
• Stores the last 2 digits of year and month when backup is performed in
2-digit BCD code.
Backup time (Year
and month)

SD672

b15 to b12 b11 to

b8 b7 to

b4 b3 to

b0 Example:

July, 1993
9307H
Year

QnU

Month

b15 to b12 b11 to

b8 b7 to

b4 b3 to

Backup time (Day
and hour)

SD673

12.2 SPECIAL REGISTER LIST

• Stores the day and hour when backup is performed in 2-digit BCD code.

b0 Example:

31st, 10 a.m.
3110H
Day

Hour

• Stores the minute and second when backup is performed in 2-digit BCD
code.
SD674

Backup
information

Backup time
(Minute and
second)

b15 to b12 b11 to

b8 b7

b4 b3

b0 Example:

35 min., 48 sec.
3548H
Minute

S (At write)

New

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

b4 b3

b0 Example:

1993, Friday
1905H
SD675

Backup time (Year
and day of week)

Higher digits of year (0 to 99)

Day of the week
0
Sunday
1
Monday
2
Tuesday
3 Wednesday
4 Thursday
5
Friday
6 Saturday

12 - 55

Number

Name

Meaning

Set by
(When Set)

Explanation

Corresponding
ACPU

Corresponding
CPU

D9
• Stores the last 2 digits of year and month when data is restored in 2-digit
BCD code.
Restore time
(Year and month)

SD676

b15 to b12 b11 to

b8 b7 to

b4 b3 to

b0 Example:

July, 1993
9307H
Year

Month

• Stores the day and time when data is restored in 2-digit BCD code.

b15 to b12 b11 to

b8 b7 to

b4 b3 to

Restore time (Day
and time)

SD677

b0 Example:

31st, 10 a.m.
3110H
Day

Hour

• Stores the minute and second when data is restored in 2-digit BCD
code.
SD678

Backup data
restration
information

Restore time
(Minute and
second)

b15 to b12 b11 to

b8 b7

b4 b3

b0 Example:

35 min., 48 sec.
3548H
Minute

S (Initial)

New

Second

• Stores the first 2 digits of year and day of week when data is restored in
BCD code.
b15 to b12 b11 to

b8 b7

b4 b3

b0 Example:

1993, Friday
1905H
Restore time
(Year and day of
week)

SD679

SD681

Program
memory write
(transfer) status

SD686

Displays the status of writing (transferring) the program memory (flash
ROM) in percentage. (0 to 100%) "0" is set when the write direction is set.

S (At write)

New

Program
memory write
count index

Write count index
up to present

• Stores the index value for the number of write operations to the program
memory (flash ROM) up to the present in BIN 32-bit value.
When the index value exceeds 100 thousand times, "FLASH ROM
ERROR" (error code: 1610) occurs. (The index value is calculated even
when exceeding 100 thousand times.)
Note) The write count does not equal to the index value.(Since a flash
ROM write life is prolonged by the system, 1 is added to the write count
index when writing is performed twice or so.).

S (At write)

New

Standard ROM
write (transfer)
status

Write (transfer)
status display (percentage)

Displays the status of writing (transferring) the standard ROM (flash ROM)
in percentage. (0 to 100%) "0" is set when the write direction is set.

S (At write)

New

Write count index
up to present

• Stores the index value for the number of write operations to the standard
ROM (flash ROM) up to the present in BIN 32-bit value.
When the index value exceeds 100 thousand times, "FLASH ROM
ERROR" (error code: 1610) occurs. (The index value is calculated even
when exceeding 100 thousand times.)
Note) The write count does not equal to the index value. (Since a flash
ROM write life is prolonged by the system, 1 is added to the write count
index when the total write capacity after the previous count up reaches
about 1M byte.)

S (At write)

New

Backup error
factor

Stores the factor of the error that occurred in the backup.
0H : No error
100H: Memory card not inserted
200H: Size of backup target data exceeded
300H: Memory card write inhibit setting
400H: Memory card write error
500H: Backup target data read error (from program memory)
503H: Backup target data read error (from standard RAM)
504H: Backup target data read error (from standard ROM)
510H: Backup target data read error (from system data)

S (Backup error
occurrence)

New

SD687

SD688

SD689

SD690

QnU

Write (transfer)
status display
(percentage)

SD682

SD683

Higher digits of year (0 to 99)

Day of the week
0
Sunday
1
Monday
2
Tuesday
3 Wednesday
4 Thursday
5
Friday
6 Saturday

Standard ROM
write count index

Backup error
factor

Backup status

Stores the current backup status.
0 : Before backup start
1 : Backup start prepared
2 : Backup start preparation completed
3 : Backup in execution
4 : Backup completed
FF: Backup error

QnU*1

S (Status
change)

*1: The module whose first 5 digits of serial No. is "10102" or later. (Except the Q00UJCPU, Q00UCPU, and Q01UCPU)

12 - 56

New

CHAPTER12 PECIAL RELAY LIST AND SPECIAL REGISTER LIST

Number

Name

Meaning

Explanation

Set by
(When Set)

Corresponding
ACPU

Corresponding
CPU

D9
SD691

SD692

Backup
execution status

Restoration error
factor

Backup execution
status display
(Percentage)

• Displays the execution status of data backup to the memory card in
percentage (0 to 100%).
• "0" is set when the backup starts.

New

S (Status
change)

New

Current restoration
status

SD694

Restoration
execution status

Restoration
execution status
display
(Percentage)

• Displays the execution status of restoration to the CPU module in
percentage (0 to 100%).
• "0" is set before the restoration.
Sets "0" (Before restoring), however, when the restoration is completed
only during the automatic restoration.

SD698
SD699

New

S (Status
change)

Restoration
status

SD697

S (Error
occurrence)

Factor of error
occurred in the
restoration

SD693

SD696

New

Stores the factor of an error that occurred in the restoration.
Each error factor is as follows:
800H: The CPU module model name is not matched.
801H: The file password is set only for the restoration destination data or is
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:
0 : Before restoration start
1 : Restoration in execution
2 : Restoration completed
FF: Restoration error
Sets "0" (Before restoring), however, when the restoration is completed
only during the automatic restoration.

SD695

S (Status
change)

Specification of
writing to standard ROM
instruction count

Specification of
writing to standard
ROM instruction
count

Available
memory in
memory card

Available memory
in memory card

Backup data
capacity

• Specifies the maximum number of executions of the writing to standard
ROM instruction (SP.DEVST) to write to the standard ROM per day.
• When the number of executions of the writing to standard ROM
instruction exceeds the number of times set by SD695, “OPERATION
ERROR” (error code: 4113) occurs.
• 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.
Stores the available memory in memory card. (Stores the value in 32-bit
binary.)

2
3
QnU*1

6
U

New

QnU

7
S (Backup in
operation)

New

QnU*1

Stores the backup data capacity. (Stores the value in 32-bit binary.)

*1: The module whose first 5 digits of serial No. is "10102" or later. (Except the Q00UJCPU, Q00UCPU, and Q01UCPU)

12.2 SPECIAL REGISTER LIST

12 - 57

(6) Instruction-Related Registers
Table12.24 Special register

Number

Name

Meaning

Set by
(When Set)

Explanation

Corresponding
ACPU

Corresponding
CPU

D9
SD705
Mask pattern

Mask pattern

SD706

New

S (During
execution)

New

Q00J/Q00/Q01
Qn(H)
QnPH
QnPRH

• Patterns masked by use of the IMASK instruction are stored in the
following manner:

SD715
SD716

• During block operations, turning SM705 ON makes it possible to use the
mask pattern being stored at SD705 (or at SD705 and SD706 if double
words are being used) to operate on all data in the block with the
masked values.

IMASK
instruction mask
pattern

SD715 l15

SD716 l31

l17

l16

SD717 l47

l33

l32

b15
Mask pattern

SD717

QCPU

SD718
Accumulator

Accumulator

Program No.
designation for
PLOADP
instruction

• For use as replacement for accumulators used in A series programs.

S/U

New

Stores the program number of the program to be loaded by the PLOADP
instruction when designated.
Designation range: 1 to 124

New

Qn(H)
QnPH

S (During
execution)

New

QCPU

SD719

SD720

SD738

• Stores the message designated by the MSG instruction.

SD739
SD740
SD741
SD742
SD743
SD744
SD745
SD746
SD747
SD748
SD749
SD750
SD751
SD752
SD753
SD754

Message
storage

SD755
SD756
SD757
SD758
SD759
SD760
SD761
SD762
SD763
SD764
SD765
SD766
SD767
SD768
SD769

12 - 58

Message storage

SD738
SD739
SD740
SD741
SD742
SD743
SD744
SD745
SD746
SD747
SD748
SD749
SD750
SD751
SD752
SD753
SD754
SD755
SD756
SD757
SD758
SD759
SD760
SD761
SD762
SD763
SD764
SD765
SD766
SD767
SD768
SD769

b15
b8
to
2nd character
4th character
6th character
8th character
10th character
12th character
14th character
16th character
18th character
20th character
22nd character
24th character
26th character
28th character
30th character
32nd character
34th character
36th character
38th character
40th character
42nd character
44th character
46th character
48th character
50th character
52nd character
54th character
56th character
58th character
60th character
62nd character
64th character

b0
to
1st character

3rd character
5th character
7th character
9th character
11th character
13th character
15th character
17th character
19th character
21st character
23rd character
25th character
27th character
29th character
31st character
33rd character
35th character
37th character
39th character
41st character
43rd character
45th character
47th character
49th character
51st character
53rd character
55th character
57th character
59th character
61st character
63rd character

CHAPTER12 PECIAL RELAY LIST AND SPECIAL REGISTER LIST

Table12.24 Special register

Number

Name

Meaning

Set by
(When Set)

Explanation

Corresponding
ACPU

1
Corresponding
CPU

D9
• Specify the limit of each PID loop as shown below.
SD774
to
SD775

SD774

PID limit setting
(for complete
derivative)

0: With limit
1: Without limit

SD774 Loop16

b15
to

Loop2

Loop1

SD775 Loop32

Loop18

Loop17

New

Qn(H)
QnPRH
QnU

0: With limit
1: Without limit

b15

SD774

Loop8

Loop2

Loop1

New

Q00J/Q00/Q01*9

• 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
SD778 0/1

to
0

0/1 0/1 0/1 0/1 0/1

Automatic refresh of
intelligent function
modules
Automatic refresh of
CPU shared memory
(Fixed to "0" for
Redundant CPU)
Execution/nonexecution of
communication with
CPU module

Q00J/Q00/Q01*9
U

New

Qn(H)*11

• 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
0
SD778 0/1

b6 b5 b4 b3 b2 b1 b0
0/1 0/1 0/1 0/1 0/1 0/1
I/O refresh
CC-Link refresh
CC-Link IE controller
network or
MELSECNET/H refresh
Automatic refresh of
intelligent function
modules
Reading input/output
from group outside
multiple CPU system
Auto refresh using the
multiple CPU high speed
transmission area of
multiple CPU system

Qn(H)*13
U

New

QnPH*12
QnPRH

Execution/nonexecution of
communication with
CPU module

• Refresh between multiple CPUs by COM instruction is performed under
the following occasion.
Receiving operation from other device: b4 of SD778(refresh in the CPU
shared memory) is turned to 1.
Sending operation from host CPU : b15 of SD778(communication with
peripheral device is executed/nonexecuted) is turned to 0.
• When b2 (refresh of the CC-Link IE controller network and
MELSECNET/H) of SD778 is 1, the CC-Link IE controller network and
MELSECNET/H perform refresh.
Therefore, if there are many refresh points, processing time for the COM
instruction will be extended.

*9: Function version is B or later.
*11: The module whose first 5 digits of serial No. is "04012" or later.
*12: The module whose first 5 digits of serial No. is "07032" or later.
*13: The module whose first 5 digits of serial No. is "09012" or later.

12 - 59

12.2 SPECIAL REGISTER LIST

SD778

b0 to b14:
0: Do not
refresh
1: Refresh
b15 bit
0: Communication
with CPU
module is
executed
1: Communication
withCPU
module is
nonexecuted

b5 b4 b3 b2 b1 b0
I/O refresh
CC-Link refresh
MELSECNET/H
refresh

Refresh
processing
selection when
the COM/
CCOM
instruction is
executed

• Specify the limit of each PID loop as shown below.

Table12.24 Special register

Number

Name

Meaning

Set by
(When Set)

Explanation

Corresponding
ACPU

Corresponding
CPU

D9
• Selects whether or not the data is refreshed when the COM, CCOM
instruction is executed.
• Designation of SD778 is made valid when SM775 turns ON.

b15 b14 to
SD778 0/1
0

SD778

Refresh
processing
selection when
the COM/
CCOM
instruction is
executed

b6 b5 b4 b3 b2 b1 b0
0/1 0/1 0/1 0/1 0/1 0/1
I/O refresh
CC-Link refresh
Refresh of
MELSECNET/H and
CC-Link IE controller
network
Automatic refresh of
intelligent function
modules

b0 to b14:
0: Do not
refresh
1: Refresh
b15 bit
0: communication
with peripheral
device is
executed
1: communication
with peripheral
device is
nonexecuted

New

QnU

S (During
execution)

New

Qn(H)
QnPH
QnPRH
QnU

S (During
execution)

New

Q00J/Q00/Q01

New

Qn(H)*13
QnPRH
QnU

New

Q00J/Q00/Q01*9

Auto refresh using
QCPU standard area of
multiple CPU system and
reading input/output from
group outside.
Auto refresh using the
multiple CPU high speed
transmission area of
multiple CPU system
Execution/nonexecution of
communication with
CPU module

• Stores the mask patterns masked by the IMASK instruction as follows:

b15

SD781
to
SD793

Mask pattern of
IMASK
instruction

SD781 l63

l49

l48

SD782 l79

l65

l64

Mask pattern

to
SD793 l255

l241 l240

(The Q00UJCPU, Q00UCPU, and Q01UCPU cannot use the special
registers SD786 to SD793.)
• Stores the mask patterns masked by the IMASK instruction as follows:

b15
SD781
to
SD785

Mask pattern of
IMASK
instruction

Mask pattern

SD781 l63

l49

l48

SD782 l79

l65

l64

SD785 l127

l113 l112

• Specify the limit of each PID loop as shown below.
SD794
to
SD795

SD794

PID limit setting
(for incomplete
derivative)

0: With limit
1: Without limit

SD794 Loop16

b15
to

Loop2

Loop1

SD795 Loop32

Loop18

Loop17

• Specify the limit of each PID loop as shown below.
0: With limit
1: Without limit

b15

SD794

*9: Function version is B or later.
*13: The module whose first 5 digits of serial No. is "09012" or later.

12 - 60

b7
Loop8

Loop2

Loop1

CHAPTER12 PECIAL RELAY LIST AND SPECIAL REGISTER LIST

Table12.24 Special register

Number

Name

Meaning

Explanation

Set by
(When Set)

Corresponding
ACPU

Corresponding
CPU

SD796

SD797

SD798

Maximum
number of
blocks used for
the multiple
CPU highspeed
transmission
dedicated
instruction
setting (for CPU
No.2)
Maximum
number of
blocks used for
the multiple
CPU highspeed
transmission
dedicated
instruction
setting (for CPU
No.3)
Maximum
number of
blocks used for
the multiple
CPU highspeed
transmission
dedicated
instruction
setting (for CPU
No.4)

Maximum number
of blocks range for
dedicated
instructions
Range: 1 to 7
(Default: 2 Or
when setting other
than 1 to 7, the
register operates
as 7).

• Specifies the maximum number of blocks used for the multiple CPU
high-speed transmission dedicated instruction (target CPU=CPU No.1).
When the dedicated instruction of Multiple CPU transmission is
executed to the CPU No.1, and the number of empty blocks of the
dedicated instruction transmission area is less than the setting value of
this register, SM796 is turned ON, which is used as the interlock signal
for consecutive execution of the dedicated instruction of Multiple CPU
transmission.

U (At 1 scan
after RUN)

• Specifies the maximum number of blocks used for the multiple CPU
high-speed transmission dedicated instruction (target CPU=CPU No.2).
When the dedicated instruction of Multiple CPU transmission is
executed to the CPU No.2, and the number of empty blocks of the
dedicated instruction transmission area is less than the setting value of
this register, SM797 is turned ON, which is used as the interlock signal
for consecutive execution of the dedicated instruction of Multiple CPU
transmission.

U (At 1 scan
after RUN)

2
3

New

QnU*14*15
• Specifies the maximum number of blocks used for the multiple CPU
high-speed transmission dedicated instruction (target CPU=CPU No.3).
When the dedicated instruction of Multiple CPU transmission is
executed to the CPU No.3, and the number of empty blocks of the
dedicated instruction transmission area is less than the setting value of
this register, SM798 is turned ON, which is used as the interlock signal
for consecutive execution of the dedicated instruction of Multiple CPU
transmission.

U (At 1 scan
after RUN)

• Specifies the maximum number of blocks used for the multiple CPU
high-speed transmission dedicated instruction (target CPU=CPU No.4).
When the dedicated instruction of Multiple CPU transmission is
executed to the CPU No.4, and the number of empty blocks of the
dedicated instruction transmission area is less than the setting value of
this register, SM799 is turned ON, which is used as the interlock signal
for consecutive execution of the dedicated instruction of Multiple CPU
transmission.

U (At 1 scan
after RUN)

6
7

New

12.2 SPECIAL REGISTER LIST

SD799

Maximum
number of
blocks used for
the multiple
CPU highspeed
transmission
dedicated
instruction
setting (for CPU
No.1)

New

*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 - 61

(7) Debug
Table12.25 Special register

Number

Name

Meaning

Explanation

Set by
(When Set)

Corresponding
ACPU

Corresponding
CPU

SD840

Debug function
usage

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

S (Status
change)

New

QnU*1

Corresponding
ACPU

Corresponding
CPU

Forced ON/OFF for
external I/O
Executional conditioned
device test
(0: Not used, 1: Used)

*1: The module whose first 5 digits of serial No. is "10042" or later.

(8) Redundant CPU information (host system CPU information*1)
Table12.26 Special register

Number

Name

Meaning

Explanation

Latest status of
memory copy
from control
system to standby
system

Stores the completion status of the memory copy from control system to
standby system executed last.
1)
Stores the same value as stored into SD1596 at normal completion/
abnormal completion of the memory copy from control system to
standby system.
2)
Backed up for a power failure, this special register holds the status of
memory copy from control system to standby system executed last.
3)
Cleared to 0 by latch clear operation.

Set by
(When Set)

SD952

History of
memory copy
from control
system to
standby system

S (Status
change)

New

QnPRH

Corresponding
ACPU

Corresponding
CPU

*1: The host system CPU information is stored.

(9) Remote password count
Table12.27 Special register

Number

Name

Meaning

Explanation

Set by
(When Set)

D9
SD979

Direct
MELSOFT
connection

SD980 to
SD995

Connection
1 to 16

SD998

MELSOFT
connection
using TCP port

SD999

FTP
communi
cation port

Count of unlock
processing
failures

Stores the count of unlock processing failures.
Range: 0 to FFFEH (FFFFH when the limit is exceeded)

*1: This applies to the Built-in Ethernet port QCPU.

12 - 62

S(Status
change)

New

QnU*1

CHAPTER12 PECIAL RELAY LIST AND SPECIAL REGISTER LIST

(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.

1
2
3
12

6
7

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
Device numbers for which

is specified, special register after conversion can be used.

is specified do not function for QCPU.
12.2 SPECIAL REGISTER LIST

12 - 63

Table12.28 Special register
ACPU
Special
Register

D9000

Special
Register
after
Conversion

Special
Register for
Modification

–

SD1000

Name

Fuse blown

Meaning

Number of module
with blown fuse

Corresponding
CPU

Details

• When fuse blown modules are detected, the first I/O number of the
lowest number of the detected modules is stored in hexadecimal.
(Example: When fuses of Y50 to 6F output modules have blown,
"50" is stored in hexadecimal)
To monitor the number by peripheral devices, perform monitor
operation given in hexadecimal.
(Cleared when all contents of SD1100 to SD1107 are reset to 0.)
• Fuse blow check is executed also to the output modules of remote
I/O stations.

Qn(H)
QnPH
QnU*1

• Stores the module numbers corresponding to setting switch
numbers or base slot numbers when fuse blow occurred.

AJ02 I/O module

D9001

–

SD1001

Fuse blown

Number of module
with blown fuse

Setting
switch

Stored
data

0
1
2
3
4
5
6
7

Extension base unit
Base unit
slot No.
0
1
2
3

Stored
data
4
5
6
7

Qn(H)
QnPH

• For the remote I/O station, the value of (module I/O No./10H) + 1 is
stored.

D9002

D9005

D9008

–

SD1002

–

SD1005

SD1008

SD0

I/O module
verify error

AC DOWN
counter

Self-diagnostic
error

I/O module verify
error module number

Number of times for
AC DOWN

Self-diagnostic error
number

• 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
lowest number unit among the detected units is stored in
hexadecimal. (Storing method is the same as that of SD1000.)
To monitor the number by peripheral devices, perform monitor
operation given in hexadecimal.
(Cleared when all contents of SD1116 to SD1123 are reset to 0.)
• I/O module verify check is executed also to the modules of remote
I/O terminals.
• When the AC power supply module is used, 1 is added at
occurrence of an instantaneous power failure of within 20ms.
(The value is stored in BIN code.) It is reset when the power supply
is switched from OFF to ON.
• When the DC power supply module is used, 1 is added at
occurrence of an instantaneous power failure of within 10ms.
(The value is stored in BIN code.) It is reset when the power supply
is switched from OFF to ON.
• When error is found as a result of self-diagnosis, error number is
stored in BIN code.

*1: The relevant modules are as follows:
• The Universal model QCPU whose serial number (first five digits) is "10102" or later.
• Q00UJCPU, Q00UCPU, Q01UCPU

12 - 64

Qn(H)
QnPH
QnU*1

Qn(H)
QnPH
QnU*1
Qn(H)
QnPH
QnU*1
Qn(H)
QnPH
QnU*1

CHAPTER12 PECIAL RELAY LIST AND SPECIAL REGISTER LIST

Table12.28 Special register
ACPU
Special
Register

D9009

D9010

D9011

D9014

Special
Special
Register
Register for
after
Modification
Conversion

SD1009

SD62

SD1010

Name

Annunciator
detection

Error step

Meaning

1
Corresponding
CPU

Details

F number at which
external failure has
occurred

• When one of F0 to 2047 is turned on by OUT F or
SET F instruction, the F number, which has been detected earliest
among the F numbers which have turned on, is stored in BIN code.
• SD1009 can be cleared by RST F or LEDR instruction.
If another F number has been detected, the clearing of SD1009
causes the next number to be stored in SD1009.

Step number at which
operation error has
occurred.

• When operation error has occurred during execution of application
instruction, the step number, at which the error has occurred, is
stored in BIN code.
Thereafter, each time operation error occurs, the contents of
SD1010 are renewed.

SD1011

Error step

Step number at which
operation error has
occurred.

• When operation error has occurred during execution of application
instruction, the step number, at which the error has occurred, is
stored in BIN code. Since the step number is stored into SD1011
when SM1011 turns from OFF to ON, the data of SD1011 is not
updated unless SM1011 is cleared by a user program.

SD1014

I/O control
mode

I/O control mode
number

• The I/O control mode set is returned in any of the following
numbers:
0: Both input and output in direct mode
1: Input in refresh mode, output in direct mode
3: Both input and output in refresh mode

2
Qn(H)
QnPH
QnU*1

3
12

Qn(H)
QnPH

• The operation status of CPU as shown below are stored in
SD1015.
b15 to b12 b11 to

Remote RUN/STOP
by computer

D9015

SD1015

SD203

Operating
status of CPU

Operating status of
CPU

RUN

STOP

PAUSE 1

Except below

STOP
Instruction
execution

b4 b3

CPU key switch
0

RUN

STOP

PAUSE 1

STEP RUN

Qn(H)
QnPH
QnU*1

Remains the same in
remote RUN/STOP
mode.
Remote RUN/STOP
by parameter setting
0

RUN

STOP

PAUSE 1

12.2 SPECIAL REGISTER LIST

Status in program

b8 b7

*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.

*1: The relevant modules are as follows:
• The Universal model QCPU whose serial number (first five digits) is "10102" or later.
• Q00UJCPU, Q00UCPU, Q01UCPU

12 - 65

Table12.28 Special register
ACPU
Special
Register

D9016

Special
Register
after
Conversion

Special
Register for
Modification

Name

Program
number

SD1016

Details

Corresponding
CPU

• Indicates which sequence program is run presently. One value of 0
to B is stored in BIN code.

Qn(H)
QnPH

Meaning

0: Main program
(ROM)
1: Main program
(RAM)
2: Subprogram 1
(RAM)
3: Subprogram 2
(RAM)
4: Subprogram 3
(RAM)
5: Subprogram 1
(ROM)
6: Subprogram 2
(ROM)
7: Subprogram 3
(ROM)
8: Main program
(E2PROM)
9: Subprogram 1
(E2PROM)
A: Subprogram 2
(E2PROM)
B: Subprogram 3
(E2PROM)

D9017

SD1017

SD524

Scan time

Minimum scan time
(10 ms units)

• If scan time is smaller than the content of SD1017, the value is
newly stored at each END. Namely, the minimum value of scan
time is stored into SD1017 in BIN code.

D9018

SD1018

SD520

Scan time

Scan time
(10 ms units)

• At every END, the scan time is stored in BIN code and always
rewritten.

Scan time

Maximum scan time
(10 ms units)

• If scan time is larger than the content of SD1019, the value is newly
stored at each END. Namely, the maximum value of scan time is
stored into SD1019 in BIN code.

Constant scan

Constant scan time
(User sets in 10 ms
units)

D9019

D9020

SD1019

SD526

SD1020

D9021

SD1021

D9022

SD1022

–

SD412

• Sets the interval between consecutive program starts in multiples
of 10 ms.
0
: No setting
1 to 200

: Set. Program is executed at intervals of (set
value) 10 ms.

Scan time

Scan time
(1 ms units)

• At every END, the scan time is stored in BIN code and always
rewritten.

1 second
counter

Count in units of 1s.

• When the PC CPU starts running, it starts counting 1 every
second.
• It starts counting up from 0 to 32767, then down to -32768 and
then again up to 0. Counting repeats this routine.

Qn(H)
QnPH
QnU*1

Qn(H)
QnPH

• The year (last two digits) and month are stored as BCD code as
shown below.
D9025

SD1025

–

Clock data

Clock data
(year, month)

b15 to b12 b11 to

b8 b7 to

b4 b3 to

b0 Example:

1987, July
H8707

Year

Qn(H)
QnPH

Month

• The day and hour are stored as BCD code as shown below.

b15 to b12 b11 to
D9026

SD1026

–

Clock data

b8 b7 to

b4 b3 to b0

Clock data
(day, hour)

Day

Example:
31st, 10 a.m.
H3110

Hour

• The minute and second are stored as BCD code as shown below.

b15 to b12 b11 to
D9027

SD1027

–

Clock data

b4 b3 to b0 Example:

35 min, 48 sec.
H3548
Minute

*1: The relevant modules are as follows:
• The Universal model QCPU whose serial number (first five digits) is "10102" or later.
• Q00UJCPU, Q00UCPU, Q01UCPU

12 - 66

b8 b7 to

Clock data
(minute, second)

Second

QnU*1

CHAPTER12 PECIAL RELAY LIST AND SPECIAL REGISTER LIST

Table12.28 Special register
ACPU
Special
Register

Special
Special
Register
Register for
after
Modification
Conversion

Name

Meaning

Corresponding
CPU

Details

• The day of the week is stored as BCD code as shown below.
b15

D9028

D9035

D9036

–

SD1028

SD1035

SD648

Clock data

Extension file
register

b8 b7

b4 b3

Example:
Friday
H0005

Day of the week

Clock data
(day of week)

Use block No.

b12 b11

Monday

Qn(H)
QnPH

Tuesday

QnU*1

Wednesday

Thursday

Friday

Saturday

Always set "0"

Sunday

SD1036
Device number when
individual devices
from extension file
register are directly
accessed

SD1037

Extension file register

SD1037,SD1036
Device No. (BIN data)

0
to
16383

Block No.1
area

16384
to

Block No.2
area

D9038

SD1038

Priorities 1 to 4

SD207

• Sets priority of ERROR LEDs which illuminate (or flicker) to
indicate errors with error code numbers.
• Configuration of the priority setting areas is as shown below.

SD207
SD208

D9039

D9044

D9049

SD1039

SD208

Priorities 5 to 7

b15 to b12 b11 to b8 b7 to
b4 b3 to
b0
Priority 4
Priority 3
Priority 2
Priority 1

Priority 7

Priority 6

Priority 5

• For details, refer to the applicable CPUs User's Manual and the
ACPU Programming manual (Fundamentals).

SD1044

For sampling
trace

Step or time during
sampling trace

• Turned on/off with a peripheral device.
When STRA or STRAR instruction is executed, the value stored in
SD1044 is used as the sampling trace condition.
At scanning--------0
At time--------------Time (10 msec unit)
The value is stored into SD1044 in BIN code.

SD1049

Work area for
SFC

Block number of
extension file register

• 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
binary value.
• 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.

D9050

SD1050

SFC program
error number

Error code generated
by SFC program

• Stores error code of errors occurred in the SFC program in BIN
code.
0 : No error
80: SFC program parameter error
81: SFC code error
82: Number of steps of simultaneous execution exceeded
83: Block start error
84: SFC program operation error

D9051

SD1051

Error block

Block number where
error occurred

• Stores the block number in which an error occurred in the SFC
program in BIN code.
In the case of error 83 the starting block number is stored.

D9052

SD1052

Error step

Step number where
error occurred

• Stores the step number, where error code 84 occurred in an SFC
program, in BIN value.
• Stores "0" when error code 80, 81 or 82 occurred.
• Stores the block stating step number when error code 83 occurs.

Qn(H)
QnPH

*1: The relevant modules are as follows:
• The Universal model QCPU whose serial number (first five digits) is "10102" or later.
• Q00UJCPU, Q00UCPU, Q01UCPU

12 - 67

12.2 SPECIAL REGISTER LIST

LED display
priority ranking

• Stores the block No. of the extension file register being used in
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.
Use consecutive numbers beginning with R0 of block No. 1 to
designate device numbers.

Extension file
registerfor
designation of
device number
D9037

Table12.28 Special register
ACPU
Special
Register

Special
Register
after
Conversion

Special
Register for
Modification

Name

Meaning

Corresponding
CPU

Details

D9053

SD1053

Error transition

Transition condition
number where error
occurred

• Stores the transition condition number, where error code 84 occurred
in an SFC program, in BIN value.
Stores "0" when error code 80, 81, 82 or 83 occurred.

D9054

SD1054

Error sequence
step

Sequence step
number where error
occurred

• Stores the sequence step number of transfer condition and
operation output in which error 84 occurred in the SFC program in
BIN code.

D9055

SD1055

SD812

Status latch
execution step
number

Status latch step

• Stores the step number when status latch is executed.
• Stores the step number in a binary value if status latch is executed
in a main sequence program.
• Stores the block number and the step number if status latch is
executed in a SFC program.

Block No.
(BIN)
Upper 8 bits

SD1085

1 s to 65535 s

• Sets the time check time of the data link instructions (ZNRD,
ZNWR) for the MELSECNET/10.
• Setting range : 1 s to 65535 s (1 to 65535)
• Setting unit
:1s
• Default value : 10 s (If 0 has been set, default 10 s is applied)

D9090

SD1090

Number of
special
functions
modules over

Number of special
functions modules
over

• For details, refer to the manual of each microcomputer program
package.

D9091

SD1091

Detailed error
code

Self-diagnosis
detailed error code

• Stores the detail code of cause of an instruction error.

SD1094

Head I/O
number of I/O
module to be
replaced

Head I/O number of I/
O module to be
replaced

• Stores the first two digits of the head I/O number of the I/O module,
which will be dismounted/mounted online (with power on), in BIN
value.
Example) Input module X2F0 H2F

D9094

PLC
communication
check

Lower 8 bits

• In the self-loopback test of the serial communication module, the
serial communication module writes/reads data automatically to
make communication checks.

D9085

SD1072

Step No.
(BIN)

Data check of serial
communication
module

D9072

SD251

Qn(H)
QnPH

Qn(H)
QnPH
QnU*1
Qn(H)
QnPH

• The DIP switch information of the CPU module is stored in the
following format.
0: OFF
1: ON

b15 to b5 b4 b3 b2 b1 b0
D9095

SD1095

SD200

DIP switch
information

*1: The relevant modules are as follows:
• The Universal model QCPU whose serial number (first five digits) is "10102" or later.
• Q00UJCPU, Q00UCPU, Q01UCPU

12 - 68

D9095

SW1
SW2
SW3
SW4
SW5

Qn(H)
QnPH

CHAPTER12 PECIAL RELAY LIST AND SPECIAL REGISTER LIST

Table12.28 Special register
ACPU
Special
Register

Special
Register
after
Conversion

D9100

SD1100

D9101

SD1101

D9102

SD1102

Special
Register for
Modification

Name

Meaning

Corresponding
CPU

Details

• Output module numbers (in units of 16 points), of which fuses have
blown, are entered in bit pattern. (Preset output module numbers
when parameter setting has been performed.)

b15 b14b13b12b11b10 b9 b8 b7 b6 b5 b4 b3 b2 b1 b0

D9103

SD1103

–
D9104

SD1104

D9105

SD1105

D9106

SD1106

D9107

SD1107

D9108

SD1108

D9109

SD1109

D9110

SD1110

D9111

SD1111
SD1112

D9113

SD1113

D9114

SD1114

D9116

SD1116

D9117

SD1117

D9118

SD1118

D9119

D9121

SD1101 0

SD1107 0

1
(YC0)

Y7
B0

1
(Y80)

0
0

Qn(H)
QnPH

QnU*1

Y7
30

• 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
required to perform clear by user program.)

• Set the value of the step transition monitoring timer and the
annunciator number (F number) that will be turned ON when the
monitoring timer times out.

b15

–

Step transfer
monitoring timer
setting

Timer setting valve
and the F number at
time out

b8 b7

F number setting
(02 to 255)

b0
Qn(H)
QnPH

Timer time limit setting
(1 to 255 s:(1 s units))

• When I/O modules, of which data are different from those entered
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
numbers set in parmeters when parameter setting has been
performed.)

SD1120

I/O module
verification error

Bit pattern, in units of
16 points, indicating
the modules with
verification errors.

b15 b14b13b12b11b10 b9 b8 b7 b6 b5 b4 b3 b2 b1 b0
1
0 0 0 0 0 0 0 0 0 0 0 0 0 0 XY

SD1116 0

SD1117 0

SD1123 0

XY
7B0

XY
190

SD1121

Indicates an I/O module verify error.
SD1122

D9123

SD1123

D9124

SD1124

Qn(H)
QnPH
QnU*1

• I/O module verify check is executed also to remote I/O station
modules.
(If normal status is restored, clear is not performed. Therefore, it is
required to perform clear by user program.)

SD63

Number of
annuciator
detections

Number of annuciator
detections

7
8

• By turning ON any of SM1108 to SM1114, the monitoring timer
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.)

SD1119

D9122

Indicates fuse blow.

–
D9120

Bit pattern in units of
16 points, indicating
the modules whose
fuses have blown

• 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
RST F or LEDR instruction is executed, 1 is subtracted from the
contents of SD63.
• Quantity, which has been turned on by SET F instruction is stored
into SD63 in BIN code. The value of SD63 is maximum 16.

*1: The relevant modules are as follows:
• The Universal model QCPU whose serial number (first five digits) is "10102" or later.
• Q00UJCPU, Q00UCPU, Q01UCPU

12 - 69

12.2 SPECIAL REGISTER LIST

D9112

Fuse blown
module

SD1100 0

Table12.28 Special register
Special
Register
after
Conversion

Special
Register for
Modification

D9125

SD1125

SD64

D9126

SD1126

SD65

D9127

SD1127

SD66

ACPU
Special
Register

Name

Meaning

Corresponding
CPU

Details

• When any of F0 to 2047 is turned on by SET F instruction, the
annunciator numbers (F numbers) that are turned on in order are
registered into SD1125 to SD1132.
• The F number turned off by RST F instruction is erased from any of
SD1125 to SD1132, and the F numbers stored after the erased F
number are shifted to the preceding registerers.
By executing LEDR instruction, the contents of SD1125 to SD1132
are shifted upward by one.
When there are 8 annunciator detections, the 9th one is not stored
into SD1125 to SD1132 even if detected.
SET SET SET RST SET SET SET SET SET SET SET
F50 F25 F99 F25 F15 F70 F65 F38 F110 F151 F210 LEDR

D9128

SD1128

SD67
Annunciator
detection
number

D9129

D9130

D9131

D9132

SD1129

SD1130

SD1131

SD1132

SD68

SD69

SD70

SD71

Annunciator
detection number

SD1009

50 50 50 50 50 50 50 50 50 50 50 99

SD1124

SD1125

50 50 50 50 50 50 50 50 50 50 50 99

SD1126

25 25 99 99 99 99 99 99 99 99 15

SD1127

15 15 15 15 15 15 15 70

SD1128

70 70 70 70 70 70 65

SD1129

65 65 65 65 65 38

SD1130

38 38 38 38 110

SD1131

0 110 110 110 151

SD1132

*1: The relevant modules are as follows:
• The Universal model QCPU whose serial number (first five digits) is "10102" or later.
• Q00UJCPU, Q00UCPU, Q01UCPU

12 - 70

0 151 151 210

Qn(H)
QnPH
QnU*1

CHAPTER12 PECIAL RELAY LIST AND SPECIAL REGISTER LIST

(11) QCPU with built-in Ethernet port

Table12.29 Special register

Number

Name

Meaning

Set by
(When Set)

Explanation

Corresponding
ACPU

Corresponding
CPU

D9
Operation
result

SD1270

Stores
operationresult.

Stores the operation result of the time setting function.
0: Not executed
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.

b15 to b12 b11 to

b8 b7 to

b4 b3 to

b0 Example:

SD1272

31st, 10 a.m.
3110H

SD1273

Time setting function

Day

Hour

Stores minutes and seconds acquired with time setting function by two digits
of BCD code.
Execution
time

Stores time
acquired with time
setting function.

b15 to b12 b11 to

b8 b7

b4 b3

b0 Example:

35 min., 48 sec.
3548H
Minute

S (status
change)

Second

Stores years (first two digits of the Christian Era) and days acquierd with time
setting function.
b15 to b12 b11 to

b8 b7

b4 b3

b0 Example:

1993, Friday
1905H

Higher digits of year (0 to 99)

SD1275

Required
response
time

Stores time
required for clock
time aquisition.

SD1276

New

Day of the week
0
Sunday
1
Monday
2
Tuesday
3 Wednesday
4 Thursday
5
Friday
6 Saturday

QnU*1

Stores time taken from transmission to SNTP server to clook time setup at
CPU.
Range: 0 to FFFEH (Unit: ms)
FFFFH when the above limit is exceeded.
Specify this when a connection is to be invalidated forcibly on the user
program. If invalidation is specified for a connection, it stops communication
and does not respond. (When a remote password is used and frequent unlock
processing errors have occurred on a connection, this is useful for temporarily
inhibiting access to the connection.)
b15b14

b1 b0

SD1276
Connection 1
Connection 2
Connection 15

SD1277

Forced
connection
invalidation

Specifies forced
connection
invalidation.

Connection 16
b15b14 b13 b12
SD1277 0

to
0

b4 b3 b2 b1 b0
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.

*1: This applies to the Built-in Ethernet port QCPU.

12 - 71

12.2 SPECIAL REGISTER LIST

SD1274

Table12.30 Special register

Number

Name

Meaning

Set by
(When Set)

Explanation

Corresponding
ACPU

Corresponding
CPU

D9
Open completion status of connections (whose open system is socket
communication) using socket communication functions is stored.
All bits corresponding to connections using any communications other than
the socket communication are fixed to "0".
b15b14

SD1282

Open completion
signal

Stores open
completion status

b1 b0

SD1282
Connection 1
Connection 2
to
Connection 15

S (Status
change)

New

QnU*2

S (Status
change)

New

QnU*2

S (Status
change)

New

QnU*2

S (Status
change)

New

QnU*2

Connection 16

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

SD1284

Open request
signal

Stores open
request status

b1 b0

SD1284
Connection 1
Connection 2
to
Connection 15
Connection 16

0 : No open requests
1 : In open request
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

b1 b0

SD1286

Reception status
signal

Stores reception
status

Connection 1
Connection 2
to
Connection 15
Connection 16

For TCP (Normal reception mode)
0 : Data have not been received.
1 : Data have been received.
For TCP (Fixed length reception mode)
0 : Data have not been received
,or received data size has not been reached to valid buffer size.
1 : Received data size has been reached to valid buffer size.
For UDP
0 : Data have not been received.
1 : Data have been received.
Connection status of built-in Ethernet port is stored.
b15
SD1288

SD1288

Built-in Ethernet
port connection
status

Stores connection
status of built-in
Ethernet port

b11 b10 b9

1/0

Connection status
0 : Not connected with or disconnected from hubs or devices.
1 : Connected to hubs or devices

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 - 72

CHAPTER12 PECIAL RELAY LIST AND SPECIAL REGISTER LIST

(12) Fuse blown module
Table12.31 Special register
Number
SD1300
SD1301
SD1302
SD1303
SD1304
SD1305
SD1306
SD1307
SD1308
SD1309
to
SD1330

Name

Meaning

Set by
(When Set)

Explanation
• The numbers of output modules whose fuses have blown are input as a
bit pattern (in units of 16 points).
(If the module numbers are set by parameter, the parameter-set
numbers are stored.)
• Also detects blown fuse condition at remote station output modules

Bit pattern in units
of 16 points,
indicating the
modules whose
fuses have blown
0 : No blown fuse
1 : Blown fuse
present

Fuse blown
module

SD1300
SD1301

b15 b14 b13 b12 b11b10 b9 b8 b7 b6 b5 b4 b3 b2 b1 b0
1
1
0 0 0 (YC0) 0 0 0 (Y80) 0 0 0 0 0 0 0 0
1
(Y1F0)

1
(Y1A0)

1
SD1331

Y1F
B0

S (Error)

Corresponding
ACPU
D9
D9100
D9101
D9102
D9103
D9104
D9105
D9106
D9107
New

Corresponding
CPU

3
Qn(H)
QnPH
QnPRH
QnU

1
0

Y1F
30

New

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.

(13) I/O module verification
Table12.32 Special register
Number

Meaning

Bit pattern, in units
of 16 points,
indicating the
modules with
verification errors.
0 : No I/O
verification
errors
1 : I/O verification
error present

I/O module
verify error

Set by
(When Set)

Explanation
• When the I/O modules whose I/O module information differs from that
registered at power-ON are detected, the numbers of those I/O modules
are entered in bit pattern.
(If the I/O numbers are set by parameter, the parameter-set numbers
are stored.)
• Also detects I/O module information.

SD1400

b15 b14 b13 b12 b11 b10 b9 b8 b7 b6 b5 b4 b3 b2 b1 b0
1
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 X0Y

SD1401

SD1431

0
1

1FE0

XY
190

S (Error)

D9116
D9117
D9118
D9119
D9120
D9121
D9122
D9123
New

Corresponding
CPU

Qn(H)
QnPH
QnPRH
QnU

New

• Not cleared even if the blown fuse is replaced with a new one.
This flag is cleared by error resetting operation.

(14) Process control instructions
Table12.33 Special register
Number

SD1500
SD1501

SD1502

SD1503
SD1506
SD1507

SD1508

Name

Basic period

Meaning

Basic period tome

Set by
(When Set)

Corresponding
ACPU
D9

New

• Shows the detailed error contents for the error that occurred in the
process control instruction.

S (Error)

New

• Shows the error process block that occurred in the process control
instruction.

S (Error)

New

QnPH
QnPRH

New

QnPH
QnPRH

Explanation
• Set the basic period (1 second units) use for the process control
instruction using floating point data.

Floating point
pointsdata
data==

SD1501

Corresponding
CPU

SD1500

Process control
instruction detail
error code
Process control
instruction
generated error
location

Dummy device

Function
availability
selection for
process control
instruction

• Selects the availability (enabled/disabled) of the function for process
b0
control instructions.
Bumpless function
b15 b14
to
b2 b1 b0
availability setting
SD1508 0
0 1/0
0
for the S.PIDP
instrunction
Bumpless function
0: Enabled
availability for the
1: Disabled
S.PIDP instruction
(Default: 0)

• Used to specify dummy devices by a process control instruction.

7
8

New

Indicates an I/O module verify error.

SD1431

Corresponding
ACPU
D9

QnPH

12 - 73

12.2 SPECIAL REGISTER LIST

SD1400
SD1401
SD1402
SD1403
SD1404
SD1405
SD1406
SD1407
SD1408
SD1409
to
SD1430

Name

(15) For redundant systems (Host system CPU information *1)
SD1510 to SD1599 are only valid for redundant systems.
They are all set to 0 for stand-alone systems.
Table12.34 Special register

Number

Name

Meaning

Explanation

Set by
(When Set)

Corresponding
ACPU

Corresponding
CPU

D9
The LED status for BACKUP, CONTROL, SYSTEM A, SYSTEM B is
stored in the following format:

b15 to b10b9 b8 b7 b6 b5 b4 b3 b2 to b0

SD1585

Redundant
system LED
status

4 LED states
• BACKUP
• CONTROL
• SYSTEM A
• SYSTEM B

0
BACKUP
0: Off
1: On (red)
5: On (orange-yellow)
2: Flicker(red) 6: Flicker
(orange-yellow)
3: On(green)
4: Flicker(green)

SYSTEM B
0: Off
1: On
2: Flicker
SYSTEM A
0: Off
1: On
2: Flicker

SD1588

Reason(s) for
system switching

Reason(s) for
system switching
that occurred in
host station

SD1589

Reason(s) for
system
switching failure
conditions

Reason(s) for
system switching
failure No.

SD1590

Network module
head address,
which requested
system
switching

Network module
head address,
which requested
system switching

b15 to b11
0
0/1

New

CONTROL
0: Off
1: On

Stores the reason(s) for system switching on the host system.
The following values are stored corresponding to the methods for system
switching:
Initialized to 0 when the power supply is switched off and then on or the
RESET switch is set to the RESET position and then to the neutral
position.
0: Initial value (control system has not been switched)
1: Power off, Reset, H/W failure, WDT error,
2: CPU stop error (except WDT)
3: System switching request from network module
16: System switching dedicated instruction
17: System switching request from GX Developer
• Stores the reason(s) for system switching failure.
0: System switching normal (default)
1: Tracking cable is not connected , tracking cable error, FPGA circuit
failure.
2: H/W failure, power-OFF, Reset, WDT error on the standby system
3: H/W failure, power-OFF, Reset, WDT error on the Control system
4: Tracking data transfer initialization
5: Communication timeout
6: Serious error(except WDT error) on the Standby system
7: There is difference between both systems
(detected as Backup mode only)
8: During memory copy from control system to standby system
9: During online program change
10: During detection of intelligent function module failure on the standby
system
11: System switching being executed
• Resets to "0" when host system is powered on.
• Resets to "0" once system has been switched successfully.
• Stores head address of network module which a system switch request
was initiated.
• Turns off automatically by system, after network error is reset by user.

SD1590

S (status
change)

b1 b0
0/1 0

QnPRH

S (when
condition occurs)

S(when system
is switched)

QnPRH

Each bit
0:OFF
1:ON

Module 0: CPU module is invalid
as it is 2-slot model.
Module 1: Module on the right
side of the CPU module
to

S (Error/Status
change)

New

Module11: Module at the
rightmost end of the
12-slot base (Q312B)

QnPRH

• Please refer to SD1690 which stores the corresponding head address of
network module on other system.
SD1595

SD1596

Memory copy
target I/O
number

Memory copy
status

Memory copy
target I/O number

• Stores the memory copy target I/O No.(Standby system CPU module:
3D1H) of before SM1595 is turned from OFF to ON.

Memory copy
status

• Stores the execution result of Memory copy function.
0
: Memory copy successfully completed
4241H : Standby system power supply off
4242H : Tracking cable is disconnected or is damaged
4247H : Memory copy function is being executed
4248H : Unsupported memory copy destination I/O Number

*1: The information of the host CPU module is stored.

12 - 74

New

S (Status
change)

New

CHAPTER12 PECIAL RELAY LIST AND SPECIAL REGISTER LIST

(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.

Name

Meaning

Set by
(When Set)

Explanation

2
3

Table12.35 Special register

Number

Corresponding
ACPU
SD

Corresponding
CPU

• 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.

b15
SD1600

SD1600

System error
information

System switching
results

SD1602

System
switching
dedicated
instruction
parameter

System switching
dedicated
instruction
parameter

SD1611
SD1612
SD1613

Diagnostic error
code
Diagnostic error
occurrence time

• 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.
0: Initial value (System switching has not occurred)
1: Power-OFF, Reset, H/W failure, WDT error,(*)
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
SP.CONTSW.
(The parameters (SD1602) for SP.CONTSW are stored in both systems
A&B)
• SD1602 is only valid when "16" is stored in SD1601.
• This SD1602 is updated once system switch instruction SP.CONTSW is
activated.
• The error value sorted in BIN code.
• Stores SD0 of the other system CPU module
• Stores the date and time when diagnostics error occurred corresponding
to error code stored in SD1610.
• Data format is the same as SD1 to SD3.
• Also, stores the value to SD1 to SD3.

6
S(Every END)

7
8
–

S(when system
is switched)

QnPRH

S(when system
is switched)

S(Every END)

SD0

S(Every END)

SD1 to
SD3

SD1614

Other system
error
information
category

Error information
category code

• Stores the category code corresponding to the error comment
information/individual information code.
• Data format is the same as SD4.
• Also, stores the value to SD4.

S(Every END)

SD4

SD1615
to
SD1625

Other system
error common
information

Error common
information

• Stores the common information corresponding to the error code stored
in this system CPU.
• Data composition is the same as SD5 to SD15.
• Also, stores the value to SD5 to SD15.

S(Every END)

SD5 to
SD15

SD1626
to
SD1636

Other system
error individual
information

Error individual
information

• Stores the individual information corresponding to the error code stored
in this system CPU.
• Data composition is the same as SD16 to SD26.
• Also, stores the value to SD16 to SD26.

S(Every END)

SD16 to
SD26

*2: Shows the special register (SD

) for the host system CPU module.

12 - 75

12.2 SPECIAL REGISTER LIST

System
switching
results

Other system
diagnostic error
Other system
diagnostic error
occurrence
time

Fixed to 0

Each bit
0: OFF
1: ON
Tracking cable is not
connected or damaged
Power-OFF, reset,
watchdog timer error or
hardware failure occurred
in other system
Other system stop error
(except watchdog timer
error)
Bit turns on when failing to
connect with other system.
The following causes are
shown below:
Tracking H/W failure
Host system WDT
error
Cannot recognize
other system therefore
causing error

SD1601

SD1610

b2 b1 b0

Table12.35 Special register

Number

Name

Set by
(When Set)

Meaning

Explanation

Error code of error
to be cleared

• Stores the error code of the error to be cleared by clearing a standby
system error.
• Stores the error code of the error to be cleared into this register and turn
SM1649 from OFF to ON to clear the standby system error.
• The value in the lowest digit (1 place) of the error code is ignored when
stored into this register.
(By storing 4100 in this register and resetting the error, errors 4100 to
4109 can be cleared.)

Corresponding
ACPU
SD

SD1649

Standby system
error cancel
command

Corresponding
CPU

S(Every END)

Stores the operation information of the other system CPU module in the
following format.
"00FFH" I stored when a communication error occurs, or when in debug
mode.

b15
SD1650

SD1650

Other system
operating
information

to
0

b8 b7tob4 b3to b0

0:No error
1:Continue error
2:Stop error
F:Communication with
other system
disabled ( )

Other system
operating
information

0:RUN
2:STOP
3:PAUSE
F:Communication with
other system
disabled ( )

: Communication
with other system
disabled, debug
mode

S(Every END)

–

Note : A communication error is caused by the following:.
• When the power supply is switched off, or when the other system is
reset.
• H/W error occurs on either of system A or B.
• WDT error occurs.
• Tracking cable is not connected.
• Tracking cable is disconnected or damaged.
• Stores head address of network module which a system switch request
was initiated, using the following format.
• Turns off automatically by system, after network error is reset by user.

SD1690

Network module
head address,
which requested
system
switching on
host (control)
system

SD1690

b15 to b11
0
0/1

Network module
head address,
which requested
system switching
on host (control)
system

b1 b0
0/1 0

Each bit
0:OFF
1:ON

Module 0:
Module 1:
to
Module11:

CPU module is
invalid as it is 2slot model
Module on the
right side of the
CPU module
Module at the
rightmost end of
the 12-slot base
(Q312B)

• Please refer to SD1590 which stores the corresponding head address of
network module on host system.

*2 : Shows the special register (SD

12 - 76

) for the host system CPU.

S(Every END)

QnPRH

CHAPTER12 PECIAL RELAY LIST AND SPECIAL REGISTER LIST

(17) For redundant systems (Trucking)

SD1700 to SD1779 is valid only for redundant systems.
These are all 0 for stand-alone systems.

Table12.36 Special register

Number

Name

Meaning

Explanation

Set by
(When Set)

Corresponding
ACPU

Corresponding
CPU

D9
SD1700

SD1710

Tracking error
detection count

Waiting time for
online program
change
(standby
system)

Tracking error
detection count

• When the tracking error is detected, count is added by one.
• The counter repeats an increment and decrement of the value; 0
32767
- 32768
0

Waiting time for
online program
change (standby
system)

• 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
consistency check between system A & B suspended during the online
program change. Also, the control system CPU module is set to accept a
new request of online program change for redundancy.
• When both systems are powered on, 90 seconds are set to SD1710 as
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.

S(Error)

QnPRH

New
U/ S (Initial)

QnPRH

6
7
8

12.2 SPECIAL REGISTER LIST

12 - 77

(18) Redundant power supply module information
SD1780 to SD1789 are valid only for a redundant power supply system.
The bits are all 0 for a singular power supply system.
Table12.37 Special register

Number

Name

Meaning

Set by
(When Set)

Explanation

Corresponding
ACPU

Corresponding
CPU

D9
• Stores the status of the redundant power supply module with input
power OFF in the following bit pattern.
• Stores 0 when the main base unit is not the redundant power main base
unit (Q38RB).
Input power OFF
detection status of
1
power supply 2

SD1780

Power supply
off detection
status

Power supply off
detection status

b15

Input power OFF
detection status of
power supply 1 1

b9 b8 b7

SD1780

b1 b0

Each bit
0: Input power ON status/ No
redundant power supply
module
1: Input power OFF status

S(Every END)

New

S(Every END)

New

Main base unit
Extension base unit 1st stage
:
Extension base unit 7th stage
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
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
supply 2 1

SD1781

Power supply
failure detection
status

b15
SD1781

to
to

b9 b8 b7

Failure detection
status of power
supply 1 1
to
to

b1 b0

Each bit
0: Redundant power supply
module failure not
detected/No redundant power
supply module
1: Redundant power supply
module failure detected
(Detectable for redundant
power supply module only)
Main base unit
Extension base unit 1st stage
:
Extension base unit 7th stage

Qn(H)*2
QnPH*2
QnPRH
QnU*3

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.

SD1782

Momentary
power failure
detection
counter for
power supply

Momentary power
failure detection
count for power
supply 1

1*1

SD1783

Momentary
power failure
detection
counter for
power supply
2*1

Momentary power
failure detection
count for power
supply 2

• Counts the number of times of momentary power failure of the power
supply 1/2.
• Monitors the status of the power supply 1/ 2 mounted on the redundant
power main base unit (Q38RB) and counts the number of times of
momentary power failure.
Status of power supply 1/power supply 2 mounted on the redundant
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
the power supply 1/ 2 is detected.(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.
• Stores 0 when the main base unit is not the redundant power main base
unit (Q38RB).
• 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.

S(Every END)

New

S(Every END)

New

*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 - 78

APPENDICES

Appendix 1 List of Parameter Numbers

Each parameter number will be stored in the special register (SD16 to SD26) when an error occurs in the
parameter settings.

TableApp.1 lists the parameter items and corresponding parameter numbers.
For explanation of M and N shown in the "Parameter No." column, refer to Section 8.2.
TableApp.1 List of parameter numbers

Item

Parameter No.

Label

0000H

Comment

0001H

Reference
APPENDIX

Section 8.1(1)

Type
I/O assignment

Model name
Points

0400H

Section 4.2.2, 8.1 (9)

Start XY (Start I/O number)

Base model name
Base setting

Power model name

Section 4.2.1, Section 8.1(10)

Error time output mode

0403H

Section 6.8, Section 8.1(10)

I/O response time

0405H

Section 6.8, Section 8.1(10)

Control PLC

0406H

Section 8.1 (9),
QCPU User’s Manual (Muitiple
CPU System)

Slots

Detailed setting

No. of PLC

0E00H

Operating mode

0E01H

I/O sharing when using

All CPUs can read all inputs

Multiple CPUs

All CPUs can read all outputs

Timer limit setting
RUN-PAUSE contacts

Low speed
High speed
RUN
PAUSE

0E04H

Section 8.1 (12),
QCPU User’s Manual (Muitiple
CPU System)

1000H

Section 8.1(2)

1001H

Section 6.6.1, Section 8.1(2)
Section 6.6.2, Section 8.1(2)

1002H

Section 6.6.3, Section 8.1(2)

Output mode at STOP to RUN

1003H

Section 6.4, Section 8.1(2)

Common pointer No.

1005H

Section 9.10.2, Section 8.1(2)

Points occupied by empty slot

1007H

Section 4.4.2, Section 8.1(2)

Remote reset

Interrupt program/Fixed scan program setting
System interrupt settings

Fixed scan interval (n : 28 to 31)

1008H

Section 2.2.3, 2.3.4, 8.1 (2)
Section 8.1(2)

Intelligent function module setting (Interrupt pointer setting)

100AH

Section 9.11, Section 8.1(2)

Module synchronization

100CH

Section 8.1(2)
(To the next page)

App - 1

Appendix 1 List of Parameter Numbers

0401H

Extension cable

TableApp.1 List of parameter numbers (continued)

Item

Parameter No.

Reference

Use serial communication
Transmission speed
Sum check

100EH

Transmission wait time
RUN write setting

Section 6.23, Section
8.1(11)

Service processing setting

1013H

Latch data backup operation valid contact

1014H

Section 6.24.1, Section
8.1(2)
Section 6.28, Section 8.1(2)

File register
Comment file used in a command

1100H
1101H

Section 9.7, Section 8.1(3)
Section 8.1(3)

Initial Device value

1102H

File for local device

1103H

Transfer to Standard ROM at Latch data backup operation

1104H

Section 6.25, Section 8.1(3)
Section 9.14.2, Section
8.1(3)
Section 6.28, Section 8.1(3)

File used for SP.DEVST/S.DEVLD instruction
Device points

1105H
2000H

Section 6.29, Section 8.1(6)
Section 9.1, Section 8.1(6)

Latch (1) start/end
Latch (2) start/end

2001H
2002H

Section 3.4, 6.3, Section
8.1(3)

Local device start/end

2003H

Section 9.14.2, Section
8.1(6)

Device points

2000H

File register extended

Latch (1) start/end

2004H

setting

Latch (2) start/end
32 bit Indexing

2000H

Section 8.1(6)

3000H

Section 6.16, Section 8.1(4)
Section 2.3.1, Section
8.1(4)

WDT (watchdog timer)
setting

2005H

WDT setting
Initial execution monitoring time

Section 9.8, Section 8.1(6)

Carry out battery check
Carry out fuse blown check
Error check

Verify module
Check device range at indexing

3001H

Diagnose redundant power supply system
Computation error
Expanded command error
Fuse blown
Operating mode when
there is an error

Module verify error
Intelligent module program execution error

Section 6.17, Section 8.1(4)

3002H

File access error
Memory card operation error
External power supply OFF
Constant scanning

3003H

Section 6.2, Section 8.1(4)

Module error collection setting
Detailed setting
H/W error time PLC operation mode

300AH
4004H

Section 6.32, Section 8.1(5)
Section 6.9, Section 8.1(10)
(To the next page)

App - 2

APPENDICES

TableApp.1 List of parameter numbers (continued)

Item

Parameter No.

Number of modules on MELSECNET/H

5000H

Valid module during other station access

5001H

Interlink transmission parameters

5002H

Routing parameters

5003H

Reference

2
3

Starting I/O No.
Network No.

5NM0H

Total stations
Mode

5NM0H

Refresh parameters

5NM1H

Common parameters

5NM2H

Station inherent parameters

5NM3H

Sub-master parameters

5NM5H

Common parameters 2

5NMAH

Station inherent parameters 2
Interrupt settings
Program

Section 8.2(2)
APPENDIX

6
7

5NMBH
7000H

Section 2.3, Section 8.1(7)

7000H

Section 5.1.2, 5.1.8, Section
8.1(8)

Clear program memory
Boot option

Auto Download all Data from Memory card to
Standard ROM

Boot file setting
8002H

Start conditions

8003H

Output mode when the block is stopped

8006H

Number of modules on Ethernet

9000H

Appendix 1 List of Parameter Numbers

SFC program start mode

Section 8.1(9)

Starting I/O No.
Network No.
Group No.

9N00H

Station No.
Operational settings
Initial settings

9N01H

Open settings

9N02H

Router relay parameter

9N03H

Station No.<->IP information

9N05H

FTP Parameters

9N06H

E-mail settings

9N07H
News setting

Section 8.2(3)

9N08H

Interrupt settings

9N09H

Routing parameters

9N04H
(To the next page)

App - 3

TableApp.1 List of parameter numbers (continued)

Item

Parameter No.

Number of modules on CC-Link IE controller network

A000H

Interlink transmission parameters

A002H

Routing parameters

A003H

Reference

Starting I/O No.
Network No.
Total stations

ANM0H

Section 8.2(1)

Station No.
Mode

ANM0H

Refresh parameters

ANM1H

Common parameters

ANM2H

Station inherent parameters

ANM3H

Number of modules

C000H

Remote input (RX)
Remote output (RY)
Remote register (RWr)
Remote register (RWw)
Ver.2 Remote input (RX)
Ver.2 Remote output (RY)

CNM1H

Ver.2 Remote register (RWr)
Ver.2 Remote register (RWw)
Special relay (SB)
Special register (SW)

Section 8.2(4)

Operational setting
All connect count
Retry count
Automatic reconnection station count
Standby master station No.
PLC down select

CNM2H

Scan mode setting
Delay information setting
Station information setting
Remote device station initial setting
Interrupt setting
(To the next page)

App - 4

APPENDICES

TableApp.1 List of parameter numbers (continued)

Item
Communication area setting (refresh setting)

Parameter No.

Reference

E002H,

Online module change

E006H

Refresh parameter detailed device specification

E007H

Section 8.1 (12),

Multiple CPU high

E008H

QCPU User’s Manual

CPU specific send range

(Muitiple CPU System)

speed transmission
area setting

E003H

Auto refresh setting

E009H

Multiple CPU synchronous startup setting

E00BH

Host CPU number

E00CH

APPENDIX

6
7
8

Appendix 1 List of Parameter Numbers

App - 5

Appendix 2 Functions Added or Changed by Version Upgrade
The Universal model QCPU is upgraded when some functions are added or specifications are changed.
Therefore, the functions and specifications differdepending on the function version and serial number.

(1) Function added and supported CPU module and GX Developer versions
TableApp.2 Functions added and supported CPU module and GX Developer versions
Function
*1

Use of the PC CPU module

(

Function

First 5 digits of

Supported GX

version

serial No.

Developer

QCPU User’s Manual (Multiple CPU

"09072" or later

System))
Setting of whether to use local device for each program (
Program batch transfer execution status (SM165) (

Section 9.14.2)

Version 8.62Q or
later

Section 5.1.3)

Multiple CPU high speed transmission dedicated instruction*1 (

QCPU

"10012" or later

Programming Manual (Common Instructions))
Amount of battery consumption display (

QCPU User's Manual (Hardware

Design, Maintenance and Inspection))
Bit device extension (

Section 9.2)

Executional conditioned device test (

Section 6.11.4)

Auto start sampling trace function*1 (

Section 6.14)

CC-Link IE group cyclic transmission function (

CC-Link IE Controller

Network Reference Manual)
Scan time measurement (

External input/output forced on/off (
Monitor condition

setting*1

"10042" or later

Section 6.13.3)

(

Version 8.68W or
later

Section 6.11.3)
B

Section 6.11.3)

Redundant power supply system-compatible *1 (
32-bit index modification using "ZZ" (

Section 6.20)

QCPU Programming Manual

(Common Instructions))
Extended data register (D) and extended link register (W)*1 *2 (

Section

9.8)
Serial Communication Function*1 (

"09042"or later *1

Version 8.70Y or
later

Section 6.23)

CPU module change function with memory card*1 (
Local device setting of the index register

*1 (

Section 6.30)
Section 9.14.2)

"10102" or later
Version 8.78G or

Communication using the A-compatible 1C/1E frame (MC protocol)*3 *4 (

later

Q Corresponding MELSEC Communication Protocol Reference Manual)
Socket communication function (

QnUCPU User's Manual

(Communication via Built-in Ethernet Port))*1
Module model name read (
Module error collection function (

Section 6.31)
Section 6.32)

"11012" or later
Version 8.82L or
"11043" or later

later
- *5

: Not related to GX Developer

App - 6

APPENDICES

*1: Some models do not support the function. For details, refer to the corresponding reference.
*2: Data of the extended data register (D) and extended link register (W) can be retained in the standard ROM by using the latch data backup
to standard ROM function (
Section 6.28) if the serial number (first five digits) of the Universal model QCPU is "10042" or later.
*3: Communication using the A-compatible 1E frame is available only via any Ethernet module.
If the module is connected to the built-in Ethernet port of the CPU module, this function is not available.
*4: Communication using the A-compatible 1C frame is available only via any serial communication module.
If the module is connected to the built-in RS-232 interface of the CPU module, this function is not available.
*5: Use GX Works2 of version 1.12N or later.

1
2
3

APPENDIX

6
7
8

Appendix 2 Functions Added or Changed by Version Upgrade

App - 7

Appendix 3 Method of Replacing Basic Model QCPU or High
Performance Model QCPU with Universal Model QCPU
Appendix 3.1 Replacement Precautions
This section describes precautions for replacing the Basic model QCPU or High Performance model QCPU with the
Universal model QCPU and the replacement methods.

Appendix 3.1.1 Replacing Basic model QCPU with Universal model QCPU
(1) System configuration
TableApp.3 Precautions for replacement and replacement methods (System configuration)
Item
GOT

Precautions

Replacement method

GOT900 series cannot be connected.

Reference

Use GOT1000 series.

---

Products need to be replaced for the
compatibility with the Universal model
Applicable products

Products and software compatible with

QCPU and software need to be upgraded

and software

the Universal model QCPU must be used.

for the communication with the Universal

Appendix 3.2

model QCPU are described in Appendix
3.2.
Multiple CPU system

To configure a multiple CPU system, CPU

CPU modules compatible with the

modules compatible with the Universal

Universal model QCPU are described in

model QCPU must be used.

Appendix 3.2.

Appendix 3.2

(2) Program
TableApp.4 Precautions for replacement and replacement methods (Program)
Item
Language and
instruction

Precautions

Replacement method

Reference

Replace the instructions not supported in
Some instructions are not supported.

the Universal model QCPU are described

Appendix 3.3

in Appendix 3.3.
When using the floating-point data
comparison instructions, LDE
ANDE

Floating-point
operation

, ORE

and ORED

, LDED

, ANDED

, if the comparison source

data are -0, nonnumeric, unnormalized
number, or

, “OPERATION

When the floating-point data comparison
instructions are used, modify the program
as described in Appendix 3.4.2.

Section 2.4.4, Appendix
3.4.2

ERROR” (error code: 4101) is detected.
(

indicates one of the followings;

=,<>,<=,>=,<,>.)
When a device number exceeds a setting

Deselect the "Check device range at

Device range check at

range due to index modification,

indexing" checkbox in the PLC RAS tab of

Section 6.17, Appendix

index modification

“OPERATION ERROR” (error code:

the PLC parameter dialog box so that

3.4.3

4101) is detected.

checking is not performed.

(To the next page)

App - 8

APPENDICES

TableApp.4 Precautions for replacement and replacement methods (Program) (Continued)
Item

Precautions

Replacement method

Reference

The latch function of the Universal model
QCPU is enhanced.
(1) Large-capacity file register (R, ZR)
If latch ranges of internal user devices are
Latch setting

(2) Writing/reading device data to the
standard ROM (SP.DEVST and

specified, the processing time is added in
proportion to the device points set to be
latched.

S(P).DEVLD instructions)
(3) Latch range specification of internal

Section 6.3, Appendix

3.4.4

devices
Change the latch method to the method
described in (1) to (3) above according to
the application.

APPENDIX

Check the numbers of executions for
Interrupt counter

Interrupt counter is not supported.

interrupt programs on the Interrupt
program monitor list screen of GX

Section 6.13.2, 9.2.11

Developer.

SCJ instruction

When the SCJ instruction is used in the

Insert the AND SM400 (or NOP

Section 6.5.1 in the

Universal model QCPU, the AND SM400

instruction) immediately before the SCJ

QCPU Programming

(or NOP instruction) needs to be inserted

instruction when the SCJ instruction is

Manual (Common

immediately before the SCJ instruction.

used.

Instructions)

of the target station specified in D3 when

To get the same operation as the Basic

Section 8.3.2 in the

the SREAD and SWRITE instructions are

model QCPU, omit D3 or use the READ

QCPU Programming

used is available. (The Basic model

instruction instead of the SREAD instruc-

Manual (Common

QCPU ignores the device specified in

tion.

Instructions)

6
7

Use of the completion notification device
JP/GP.SREAD and JP/
GP.SWRITE
instructions

D3.)
increased to 20 for the Universal model
ZPUSH instruction

QCPU. The area for saving the data in the
index register with the ZPUSH instruction

Section 7.18.8 in the
Increase the save area used for the

QCPU Programming

ZPUSH instruction as needed.

Manual (Common
Instructions)

is increased as well.
Use of the annunciator
(SET F
F

and OUT

instructions)

When the annunciator is turned on by the
SET F

or OUT F

instruction, the

---

USER LED turns on.

---

(The ERR.LED does not turn on.)
Execute I/O refresh at the start or end of
each program with the RFS or COM

I/O refresh between

I/O refresh between programs cannot be

instruction.

programs

executed.

(When the COM instruction is used, I/O

---

refresh to be executed can be specified in
SD778 by turning on SM774.)
SM/SD

Usage of a part of the special relay and
special register is different.

Replace the corresponding special relay
and special register as described in

Appendix 3.5

Appendix 3.5.
If the user setting area in the CPU shared
memory is specified in the program,

Multiple CPU system

The start address for the user setting area

change the address for the user setting

(auto refresh) in the CPU shared memory

area by performing an operation for

is changed.

replacing a device in GX Developer.

---

(Example: "MOV D0 U3E0\G192"
"MOV D0U3E0\G2048")

(To the next page)

App - 9

Appendix 3 Method of Replacing Basic Model QCPU or High Performance Model QCPU with Universal
Model QCPU
Appendix 3.1 Replacement Precautions

The number of index registers is

TableApp.4 Precautions for replacement and replacement methods (Program) (Continued)
Item
File register

Precautions

Replacement method

To use the file register, capacity setting is

Set the capacity of the file register used in

required.

the PLC file tab of the PLC parameter.

Reference

The following settings are required for
using SFC programs.
• Program setting (when both sequence
SFC program

• Set program details in the Program tab
of the PLC parameter dialog box.

programs and SFC programs exist.)

• Enter a common pointer number in the

• Common pointer No. setting (to exe-

PLC system of the PLC parameter dia-

cute the CALL instruction from SFC

Section 8.1

log box.

programs)

(3) Drive and file
TableApp.5 Precautions for replacement and replacement methods (Drive and file)
Item

Precautions

Replacement method

Reference

Since the Universal model QCPU holds
the data in the program memory even
when the battery voltage drops, the boot
Boot file setting

The boot file setting is not supported.

file setting is not necessary.

Section 5.1.8

Move files with the boot setting (from the
standard ROM to the program memory) to
the program memory.

(4) External communication (Service processing)
TableApp.6 Precautions for replacement and replacement methods (External communication (Service processing))
Item
Time reserved for
communication processing

Precautions
The time reserved for communication processing (SM315/SD315) is not supported.

Replacement method

Reference

Set service processing time in the PLC
system tab of the PLC parameter dialog

Section 6.24.1

box.

The following commands cannot specify
monitoring conditions.
• Randomly reading data in units of word
(Command: 0403)

Q Corresponding

• Device memory monitoring (Command:
MC protocol

0801)

MELSEC
---

Communication
Protocol Reference

The applicable frame types are as follows:
• QnA-compatible 3C/4C frame
• QnA-compatible 3E frame
• 4E frame

App - 10

Manual

APPENDICES

(5) Battery installation position
TableApp.7 Precautions for replacement and replacement methods (Battery installation position)
Item

Precautions

Replacement method

Reference

The battery replacement method is different.
The battery installation position varies
Battery installation
position

depending on the model.
• Q00JCPU, Q00CPU, Q01CPU
...On the front of the module.

Section 7.2 in the
For the battery replacement method,
refer to the in the Reference column.

• Q00UJCPU, Q00UCPU, Q01UCPU

QCPU User's Manual
(Hardware Design,

Maintenance and
Inspection)

...At the bottom of the module.

(6) Program size

APPENDIX

TableApp.8 Precautions for replacement and replacement methods (Program size)
Item

Precautions

Replacement method

Reference

Data in the program memory of the Basic
Program size

model QCPU may exceed the size of the

Store parameter and device comment

program memory of the Universal model

files in the standard ROM.

---

QCPU.

Appendix 3 Method of Replacing Basic Model QCPU or High Performance Model QCPU with Universal
Model QCPU
Appendix 3.1 Replacement Precautions

App - 11

Appendix 3.1.2 Replacing High Performance model QCPU with Universal
model QCPU
(1) System configuration
TableApp.9 Precautions for replacement and replacement methods (System configuration)
Item
Use of AnS/A series
module
GOT

Precautions

Replacement method

Reference

AnS/A series modules are not supported.

Use Q series modules.

---

GOT900 series cannot be connected.

Use GOT1000 series.

---

Applicable USB cables are different.
Programming tool
connection

• High Performance model QCPU
... A-B type
• Universal model QCPU

Use USB cables of A-miniB type. Or, use
USB conversion adapters of B-miniB

---

type.

... A-miniB type
Products need to be replaced for the
compatibility with the Universal model
Applicable products

Products and softwares compatible with

QCPU and software need to be upgraded

and software

the Universal model QCPU must be used.

for the communication with the Universal

Appendix 3.2

model QCPU are described in Appendix
3.2.

Multiple CPU system

To configure a multiple CPU system, CPU

CPU modules compatible with the

modules compatible with the Universal

Universal model QCPU are described in

model QCPU must be used.

Appendix 3.2.

In a multiple CPU system using the

For data communication with the Motion

Motion CPU, an existing auto refresh area

CPU, use an auto refresh area and user

and user setting area cannot be used for

setting area in the multiple CPU high-

data communication with the Motion CPU.

speed transmission area.

Appendix 3.2

Chapter 4 in the QCPU
User's Manual (Multiple
CPU System)

In a redundant power supply system
using the Q38RB redundant power supply
Section 5.3 in the

main base unit and the Q68RB redundant
Redundant power
supply system*1

power supply extension base unit, the

Check the status of the power supply

QCPU User's Manual

status of the power supply module cannot

module by the LED on the front of the

(Hardware Design,

be stored in the special relay and special

module.

Maintenance and
Inspection)

Section 7.7 in the Q
Corresponding
MELSECNET/H

The simple dual-structured network
function is not supported.

---

MELSECNET/H
Network System
Reference Manual (PLC
to PLC network)

*1: The serial number (first five digits) of the applicable module (Q02UCPU, Q03UDCPU, Q04UDHCPU, Q06UDHCPU, Q13UDHCPU, and
Q26UDHCPU) must be "10041" or earlier.

App - 12

APPENDICES

(2) Program
TableApp.10 Precautions for replacement and replacement methods (Program)
Item
Language and
instruction

Precautions

Replacement method

Reference

Replace the instructions not supported in
Some instructions are not supported.

the Universal model QCPU are described

Appendix 3.3

in Appendix 3.3.

Instructions for floating-point doubleprecision operations are added for the

The Universal model QCPU performs
program operations of floating-point data
in single precision.

Universal model QCPU. Replace the
instructions if floating-point doubleprecision operations ares required, as
described in Appendix 3.4.

APPENDIX

When using the floating-point data
Floating-point
operation

comparison instructions, LDE
ANDE

, ORE

and ORED

, LDED

Section 2.4.4, Appendix

, ANDED

, if the comparison source

data are -0, nonnumeric, unnormalized
number, or

3.4, Appendix 3.4.2

“OPERATION

When the floating-point data comparison
instructions are used, modify the program
as described in Appendix 3.4.2.

ERROR “ (error code: 4101) is detected.
(

indicates one of the followings;

=,<>,<=,>=,<,>.)

Deselect the "Check device range at

range due to index modification,

indexing" checkbox in the PLC RAS tab of

Section 6.17, Appendix

index modification

“OPERATION ERROR” (error code:

the PLC parameter dialog box so that

3.4.3

4101) is detected.

checking is not performed.

Low-speed execution type programs are

Use scan execution type programs or

not supported.

fixed scan execution type programs.

Program execution
type

A program execution type cannot be
changed by remote operation.

Section 2.3

Use instructions for switching program
execution types, such as PSTOP, POFF,

Section 2.3

and PSCAN.
The latch function of the Universal model
QCPU is enhanced.

If latch ranges of internal user devices are
specified, the processing time is added in
Latch setting

proportion to the device points set to be
latched. (For example, if 8K points are
latched for the latch relay (L), the
processing time of 28.6

s is required.)

(1) Large-capacity file register (R, ZR)
(2) Writing/reading device data to the
standard ROM (SP.DEVST and
S(P).DEVLD instructions)
(3) Latch range specification of internal

Section 6.3, Appendix
3.4.4

devices
Change the latch method to the method
described in (1) to (3) above according to
the application.

(To the next page)

App - 13

Appendix 3 Method of Replacing Basic Model QCPU or High Performance Model QCPU with Universal
Model QCPU
Appendix 3.1 Replacement Precautions

When a device number exceeds a setting
Device range check at

TableApp.9 Precautions for replacement and replacement methods (Program) (Continued)
Item

Precautions

Replacement method

The interrupt pointer (I49) for the high-

Consider the use of interrupt pointers for

speed interrupt function is not supported.

fixed scan interrupt (I28 to I31).
Check the numbers of executions for

Interrupt program

Interrupt counter is not supported.

interrupt programs on the Interrupt

Reference

Section 6.13.2, 9.2.11

program monitor list screen of GX
Developer.

The interrupt pointers (I32 to I40) due to

---

an error are not supported.

SCJ instruction

When the SCJ instruction is used in the

Insert the AND SM400 (or NOP

Section 6.5.1 in the

Universal model QCPU, the AND SM400

instruction) immediately before the SCJ

QCPU Programming

(or NOP instruction) needs to be inserted

instruction when the SCJ instruction is

Manual (Common

immediately before the SCJ instruction.

used.

Instructions)

The number of index registers is
increased to 20 for the Universal model
ZPUSH instruction

Section 9.11

QCPU. The area for saving the data in the
index register with the ZPUSH instruction

Section 7.18.8 in the
Increase the save areas used for the

QCPU Programming

ZPUSH instruction as needed.

Manual (Common
Instructions)

is increased as well.
The following file usability setting for each
File usability setting for
each program

program is not available.*1
• File register
• Initial device value

When file usability is set, modify the

Section 2.3, Appendix

program as described in Appendix 3.4.

3.4.5

• Comment
• Section 2.3
I/O refresh setting for

I/O refresh setting for each program is not

Use the RFS instruction if I/O refresh

• QCPU Programming

each program

available.

setting for each program is required.

Manual (Common
Instructions)

Usage of a part of the special relay and
special register is different.

Replace the corresponding special relay
and special register as described in

Appendix 3.5

Appendix 3.5.
Using GX Developer, A series-compatible
special relay and special register can be

SM/SD

replaced with the Universal model QCPUA sereis-compatible special relay and

compatible special relay and special

special register are not supported.

(SM1000 to SM1255/SD1000 to SD1255)

which are not compatible with the

Chapter 12

Universal model QCPU are replaced with
SM1255 and SD1255. Modify programs
as needed.
Processing time

Scan time and each processing time are

Modify programs as needed, checking the

different.

processing timing.

---

* 1: Even the local device file usability setting is not available for the Q02UCPU, Q03UDCPU, Q04UDHCPU, and Q06UDHCPU if the serial
number (first five digits) is "10011" or earlier.

App - 14

APPENDICES

(3) Drive and file
TableApp.11 Precautions for replacement and replacement methods (Drive and file)
Item

Precautions

Replacement method

Reference

Since the Universal model QCPU holds
the data in the program memory even
Files in the standard ROM cannot be
booted to the program memory.
Boot file setting

when the battery voltage drops, the boot
file setting is not necessary.
Move files with the boot setting (from the
standard ROM to the program memory) to

Section 5.1.8, 5.1.10,

the program memory.

Appendix 3.4.6

Replacement method when the
parameter-valid drive and the boot file
Booting operation is different.

APPENDIX

setting are set in the High Performance
model QCPU is described in Appendix
3.4.6.

In the Boot file tab of the PLC parameter
Automatic all data write
from memory card to
standard ROM

dialog box, select "standard ROM" for the
The setting method of this function is

transfer destination. Note, however, that

different.

the transfer destination of "program" is

Section 5.1.8

fixed to "program memory". (Setting by
DIP switches is not necessary.)

(4) External communication
TableApp.12 Precautions for replacement and replacement methods (External communication)
Item

Precautions
The module service interval time cannot

time read

be read.
The following frame types cannot be used
when accessing the Universal model
QCPU.*1
• A-compatible 1C frame
• A-compatible 1E frame

---

• QnA-compatible 2C/3C/4C frame
• QnA-compatible 3E frame
• 4E frame
Q Corresponding

monitoring conditions.

MELSEC

• Randomly reading data in units of word

Communication

(Command: 0403)

Protocol Reference

• Device memory monitoring (Command:
0801)

Section 6.24.1

Use the frame types below.

The following commands cannot specify
MC protocol

Reference

---

Manual

The applicable frame types are as follows:
• QnA-compatible 3C/4C frame
• QnA-compatible 3E frame
• 4E frame
*1: The serial number (first five digits) of the applicable module (Q02UCPU, Q03UDCPU, Q04UDHCPU, Q06UDHCPU, Q13UDHCPU, and
Q26UDHCPU) must be "10101" or earlier.

App - 15

Appendix 3 Method of Replacing Basic Model QCPU or High Performance Model QCPU with Universal
Model QCPU
Appendix 3.1 Replacement Precautions

Module service interval

Replacement method

(5) Diagnostic function
TableApp.13 Precautions for replacement and replacement methods (Diagnostic function)
Item

Precautions

Replacement method

Reference

The Universal model QCPU can store
Error history

Error history data cannot be stored in the

history data by the number of storable

memory card.

history data in a memory card (100) to the

Section 6.18

system memory.
LED indication priority
setting

LED indication priority cannot be set. Only
LED indication setting at error occurrence

---

Section 6.21.2

is supported.

(6) Debugging
TableApp.14 Precautions for replacement and replacement methods (Debugging)
Item

Precautions

Replacement method

Reference

Use the sampling trace function for
checking device data under the specified
monitoring condition. With this function,
changes of the specified device data can
be recorded at the following timings:
Monitor*3

The monitoring condition cannot be set.

• at execution of the specified step

Section 6.11.1, 6.14

• on the rising/falling edge of bit devices
• when the value of word devices
coincide with the setting value
• at every specified time (settable range:
1 to 5000ms)
• Section 6.13.3
Scan time

Time required for executing a part of the

measurement by GX

program cannot be measured using the

Developer*3

scan time measurement function.*1

Calculate the time using instruction
processing time described in the manual.

• Appendix 1.4 in the
QCPU Programming
Manual (Common
Instructions)

The function can be replaced with the
programs described in Appendix 3.4.7.
Note, however, that replacement method
described does not apply in the following
cases:
External input/output
forced on/off

The external input/output forced on/off
*2

function is not supported.

• Input and output targeted for forced on/

Section 6.11.3,

off are referred to or changed using the

Appendix 3.4.7

direct input device (DX) and direct
output device (DY).
• Input and output targeted for forced on/
off are referred to or changed within an
interrupt program.
* 1: Scan time of each program can be checked on the Program monitor list screen.
* 2: Device test by GX Developer can be performed.
* 3: The serial number (first five digits) of the applicable module (Q02UCPU, Q03UDCPU, Q04UDHCPU, Q06UDHCPU, Q13UDHCPU, and
Q26UDHCPU) must be "10041" or earlier.

App - 16

APPENDICES

(7) Switch on the front of the CPU module
TableApp.15 Precautions for replacement and replacement methods (Switch on the front of the CPU module)
Item

Precautions

The operation method with the RESET/
RUN/STOP switch is modified.

Replacement method

Reference

The RESET/STOP/RUN switch of the

Section 4.4 in the

Universal model QCPU can be used for

QCPU User's Manual

the reset operation of the CPU module

(Hardware Design,

and switching between the STOP and

Maintenance and

RUN status.

Inspection)

2
3

Section 4.4 in the
Latch data cannot be cleared by the switch.

clear operation of GX Developer.

QCPU User's Manual
(Hardware Design,
Maintenance and
Inspection)

Switch on the front of
the CPU module

To clear latch data, use the remote latch

APPENDIX

Data in the files can be protected by
The system protect cannot be set by the

setting a password for each file.

switch.

Password for each file can be registered

Section 6.19

with GX Developer.
The Universal model QCPU
automatically determines the parameterThe parameter-valid drive setting is not
necessary.

valid drive. Change the setting as
described in Appendix 3.4.5 when the
parameter-valid drive is set to other than
the program memory in the High
Performance model QCPU.

• Appendix 3.4.6
• Section 4.4 in the
QCPU User's Manual

(Hardware Design,
Maintenance and
Inspection)

Appendix 3 Method of Replacing Basic Model QCPU or High Performance Model QCPU with Universal
Model QCPU
Appendix 3.1 Replacement Precautions

App - 17

(8) SFC
TableApp.16 Precautions for replacement and replacement methods (SFC)
Item

Precautions

Replacement method

Reference
Section 4.6 and

Step transition

The step transition monitoring timer is not

monitoring timer

supported.

Change the program as described in

Appendix 3.1 in the

Appendix 3.1 in the manual in the

QCPU (Q Mode)/

Reference column.

QnACPU Programming
Manual (SFC)
Section 4.7.4 and

The periodic execution block setting is not
supported.

Change the program as described in

Appendix 3.2 in the

Appendix 3.2 in the manual in the

QCPU (Q Mode)/

Reference column.

QnACPU Programming
Manual (SFC)

SFC operation mode
setting

Section 4.7.5 in the
An operation mode at double block START

---

cannot be selected. (Fixed to “WAIT”.)

QCPU (Q Mode)/
QnACPU Programming
Manual (SFC)
Section 4.7.6 in the

An operation mode at transition to active
step cannot be selected. (Fixed to

---

“TRANSFER”.)
SFC program for
program execution
management

QCPU (Q Mode)/
QnACPU Programming
Manual (SFC)
Section 5.2.3 in the

SFC programs for program execution

---

management are not supported.

QCPU (Q Mode)/
QnACPU Programming
Manual (SFC)
• Appendix 3.3

SFC control instructions not supported in

• Section 4.4 in the

SFC control

Some SFC control instructions are not

the Universal model QCPU and

QCPU (Q Mode)/

instruction

supported.

replacing methods are described in

QnACPU

Appendix 3.3.

Programming Manual
(SFC)

The following SFC comment readout
instructions are not supported.
SFC comment
readout instruction

• S(P).SFCSCOMR (SFC step comment
readout instruction)

Section 4.8 in the
---

• S(P).SFCTCOMR (SFC transition

QCPU (Q Mode)/
QnACPU Programming
Manual (SFC)

condition comment readout instruction)
Method of SFC
program change

App - 18

SFC program files cannot be written to the

Write program data to the CPU module

running CPU module. (Programs in SFC

after changing the Universal model

Figure can be changed online.)

QCPU status to STOP.

Section 6.6 in the
QCPU (Q Mode)/
QnACPU Programming
Manual (SFC)

APPENDICES

Appendix 3.2 Applicable devices and software

(1) Products need to be replaced for the compatibility with the Universal model QCPU
The following tables show products need to be replaced for the compatibility with the Universal model
QCPU. (As for products not listed in the tables below, replacement is not required.)

2
3

TableApp.17 Product need to be replaced (Communication module)
Serial number (first five digits) of the product compatible with the Universal
model QCPU*2
Product

Model

Used with Q02U/Q03UD/Q04UDH/
Q06UDHCPU

Used with Q00UJ/Q00U/Q01UCPU/
Q10UDH/Q13UDH/Q20UDH/
Q26UDHCPU,
or Built-in Ethernet port QCPU

Web server module*1

• QJ71WS96

"09042" or later.

"10012" or later.

MES interface module

• QJ71MES96

"09042" or later.

"10012" or later.

*1: The Universal model QCPU does not operate normally when the Web server module on which GX RemoteService-I is installed is used.
*2: The Universal model QCPU does not operate normally when a product not compatible with the Universal model QCPU is used.

APPENDIX

6
7

TableApp.18 Product need to be replaced (Personal computer board)
Dedicated software package version compatible with the Universal model
QCPU*1
Product

Used with Q13UDH/
Q26UDHCPU

Used with Q00UJ/Q00U/
Q01U/Q10UDH/
Q20UDHCPU, or Built-in
Ethernet port QCPU

• Q80BD-J71GP21-SX
• Q80BD-J71GP21S-SX

No restrictions

Version 1.03D or later

Version 1.06G or later

SI/QSI/H-PCF
optical cable

• Q80BD-J71LP21-25
• Q80BD-J71LP21S-25

Version 15R or later

Version 18U or later

• Q81BD-J71LP21-25

Version 19V or later

Version 15R or later

Version 18U or later

• Q80BD-J61BT11N

Version 1.02C or later

Version 1.05F or later

• Q81BD-J61BT11

Version 1.06G or later

GI optical cable

• Q80BD-J71LP21G

Coaxial cable

• Q80BD-J71BR11

CC-Link system master/local interface board

Version 20W or later

Version 1.07H or later

*1: No restrictions on the board itself.

TableApp.19 Product need to be replaced (GOT)
OS version provided with GT Designer2 compatible with the Universal model QCPU*1
Product

GOT1000

Model

GT15

GT11

GT10

Used with Q00UJ/
Q00U/Q01U/
Q10UDH/
Q20UDHCPU

Used with Q02U/
Q03UD/Q04UDH/
Q06UDHCPU

Used with
Q13UDH/
Q26UDHCPU

Used with Q03UDE/
Q04UDEH/Q06UDEH/
Q13UDEH/
Q26UDEHCPU

Used with
Q10UDEH/
Q20UDEHCPU

Version 2.91V or
later

Version 2.60N or
later

Version 2.76E or
later

Version 2.81K or later

Version 2.91V or
later

Version 2.76E or
later

---

*1: No restrictions on GOT itself.

App - 19

Appendix 3 Method of Replacing Basic Model QCPU or High Performance Model QCPU with Universal
Model QCPU
Appendix 3.2 Applicable devices and software

CC-Link IE controller network
interface board

MELSECNET/H
interface board

Used with Q02U/Q03UD/
Q04UDH/Q06UDHCPU

Model

TableApp.20 Product need to be replaced (Network module and serial communication module)
Module version compatible with the Universal model QCPU
Product

Model

MELSECNET/H model

•
•
•
•

Serial communication module

• QJ71C24N
• QJ71C24N-R2
• QJ71C24N-R4

Modem interface module

• QJ71CMON

Used with Q00UJ/Q00U/Q01U/Q02U/
Q03UD/Q04UDH/Q06UDH/Q10UDH/
Q13UDH/Q20UDH/Q26UDHCPU

QJ71LP21-25
QJ71LP21S-25
QJ71LP21G
QJ71BR11

Used with Built-in Ethernet port QCPU

Some restrictions depending on use
conditions*1
No restrictions
Serial number (first five digits) "10042" or
later

*1: The serial number (first five digits) of the MELSECNET/H module must be "10042" or later if all conditions 1) to 4) described below are satisfied.
1) A multiple CPU system including Built-in Ethernet port QCPU is configured.
2) GX Developer or GOT is connected to an Ethernet port of the Built-in Ethernet port QCPU.
3) GX Developer or GOT accesses the CPU module on another station via the MELSECNET/H module controlled by another CPU.
4) The access target on another station is A/QnA series CPU module.

App - 20

APPENDICES

(2) CPU modules that can configure a multiple CPU system with the Universal model
QCPU
CPU modules that can configure a multiple CPU system with the Universal model QCPU are shown
below.

(a) For the QnUD(H)CPU or Built-in Ethernet port QCPU
TableApp.21 CPU module that can configure a multiple CPU system with the QnUD(H)CPU or Built-in Ethernet port QCPU

1
2
3

Applicable version
CPU module

Motion CPU

Model

Configured with
Q03UD/Q04UDH/
Q06UDHCPU

Configured with
Q13UDH/Q26UDH,
Q03UDE/Q04UDEH,
Q06UDEH/Q13UDEH/
Q26UDEHCPU

• Q172DCPU
• Q173DCPU

Configured with
Q10UDH/Q20UDH/
Q10UDEH/
Q20UDEHCPU

Restrictions

Use only the multiple CPU
high-speed main base unit

No restrictions

(Q3

DB) as a main base

unit.

PC CPU module

C Controller module

• PPC-CPU852(MS)

• Q06CCPU-V
• Q06CCPU-V-B

Driver S/W (PPC-

DRV-02) version

1.01 or later

1.02 or later

1.03 or later

No restrictions

Serial number (first five
digits) "10012" or later

Serial number (first five
digits) "10102" or later.

High Performance
model QCPU

Q02CPU
Q02HCPU
Q06HCPU
Q12HCPU
Q25HCPU

•
•
•
•

Q02PHCPU
Q06PHCPU
Q12PHCPU
Q25PHCPU

7
-----

Function version B or later

---

No restrictions

---

(b) For the Q00UCPU, Q01UCPU, or Q02UCPU
TableApp.22 CPU module that can configure a multiple CPU system with Q00UCPU, Q01UCPU, or Q02UCPU
Applicable version
CPU module

Motion CPU

Model
•
•
•
•

Q172CPUN(-T)
Q173CPUN(-T)
Q172HCPU(-T)
Q173HCPU(-T)

PC CPU module

• PPC-CPU852(MS)

C Controller module

• Q06CCPU-V
• Q06CCPU-V-B
• Q12DCCPU-V

Configured with Q00U/
Q01UCPU

Restrictions

Configured with Q02UCPU

The multiple CPU high-speed main base

No restrictions

unit (Q3

DB) cannot be used as a

main base unit.

Driver S/W (PPC-DRV-

02) version 1.03 or later

02) version 1.01 or later

Serial number (first five
digits) "10102" or later

No restrictions

-------

App - 21

Appendix 3 Method of Replacing Basic Model QCPU or High Performance Model QCPU with Universal
Model QCPU
Appendix 3.2 Applicable devices and software

Process CPU

•
•
•
•
•

---

No restrictions

• Q12DCCPU-V

APPENDIX

(3) Software need to be upgraded for the compatibility with the Universal model QCPU
The following table shows software need to be upgraded for the communication with the Universal model QCPU.
(As for software not listed in the table below, version upgrade is not required.)
The latest version can be downloaded from the MELFANSweb.
TableApp.23 Software need to be upgraded for the compatibility with the Universal model QCPU
Version compatible with the Universal model QCPU
Product

GX Developer

Model

SW8D5C-GPPW-E

Used with Q02U/
Q03UD/Q04UDH/
Q06UDHCPU

Used with Q13UDH/
Q26UDHCPU

Used with Q03UDE/
Q04UDEH/Q06UDEH/
Q13UDEH/
Q26UDEHCPU

Used with Q00UJ/Q00U/
Q01U/Q10UDH/
Q20UDH/Q10UDEH/
Q20UDEHCPU

Version 8.48A or later

Version 8.62Q or later

Version 8.68W or later

Version 8.78G or later

later*2

later*3

Version 2.05F or later*4

later*1

GX Configurator-AD

SW2D5C-QADU-E

Version 2.05F or

GX Configurator-DA

SW2D5C-QDAU-E

Version 2.06G or later*1

Version 2.06G or later*2

Version 2.06G or later*3

Version 2.06G or later*4

GX Configurator-SC

SW2D5C-QSCU-E

Version 2.12N or later*1

Version 2.12N or later*2

Version 2.17T or later*3

Version 2.17T or later*4

GX Configurator-CT

SW0D5C-QCTU-E

Version 1.25AB or later*1

Version 1.25AB or later*2

Version 1.25AB or later*3

Version 1.25AB or later*4

GX Configurator-TI

SW1D5C-QTIU-E

Version 1.24AA or later*1

Version 1.24AA or later*2

Version 1.24AA or later*3

Version 1.24AA or later*4

later*1

Version 2.05F or

later*2

Version 2.05F or

later*3

Version 1.23Z or later*4

GX Configurator-TC

SW0D5C-QTCU-E

Version 1.23Z or

GX Configurator-FL

SW0D5C-QFLU-E

Version 1.23Z or later*1

Version 1.23Z or later*2

Version 1.23Z or later*3

Version 1.23Z or later*4

GX Configurator-QP

SW2D5C-QD75P-E

Version 2.25B or later

Version 2.29F or later

Version 2.30G or later*5

Version 2.32J or later

GX Configurator-PT

SW1D5C-QPTU-E

Version 1.23Z or later

Version 1.23Z or

GX Configurator-AS

SW1D5C-QASU-E

Version 1.21X or later*1

GX Configurator-MB

SW1D5C-QMBU-E

GX Configurator-DN

SW1D5C-QDNU-E

MX Component

SW3D5C-ACT-E

Version 3.09K or later

Version 3.10L or later

Version 3.11M or later

Version 3.12N or later

GX Simulator

SW7D5C-LLT-J

Version 7.23Z or later*4

Version 1.23Z or

later*3

Version 1.23Z or later*4

Version 1.21X or later*2

Version 1.21X or later*3

Version 1.21X or later*4

Version 1.08J or later*1

Version 1.08J or later*2

Version 1.08J or later*3

Version 1.08J or later*4

Version 1.23Z or later

later*2

Version 1.23Z or

Version 1.23Z or later

Version 1.23Z or

Version 1.24AA or later

Version 1.24AA or later*4

*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: GX Configurator-QP Version 2.29F can be used when connected via USB.

(4) Software not supported in the Universal model QCPU
The following table shows software not supported in the Universal model QCPU.
TableApp.24 Software not supported in the Universal model QCPU
Product
GX Explorer
GX Converter

App - 22

Model
SW
SW

D5C-EXP-E
D5C-CNVW-E

APPENDICES

Appendix 3.3 Instructions

Appendix 3.3.1 Instructions not supported in the Universal model QCPU
and replacing methods

The Universal model QCPU does not support instructions listed in the TableApp.24. and TableApp.25.
Instructions need to be replaced using replacing methods described in the tables. (If no instruction in the
list is used, replacement is not required.)

TableApp.25 Instructions not supported in the Universal model QCPU and replacing methods
Symbol

Instruction

Replacing method

Index modification of entire

IXEND

ladder

IXDEV

Modification value specification

Change the program so that the device offset values

in index modification of entire

specified by the IXSET instruction are directly set to the

ladder

index modification table using the MOV instruction.

IXSET

Instructions can be replaced using a replacement program.

Reference
Appendix 3.3.3 (1)

Appendix 3.3.3 (2)

APPENDIX

• It is recommended to use GOT as an ASCII code display
device. ASCII codes stored in devices are directly
PR

Print ASCII code instruction

displayed as characters on GOT.
• Instructions can be replaced using a replacement
program.
• It is recommended to use GOT as an ASCII code display

Appendix 3.3.3 (3)

device.Device comments can be displayed on GOT.
PRC

Print comment instruction

• Comment data can be output to a display device in the
replacement program of the PR instruction after reading
(COMRD(P)).

CHKST

Specific format failure check

CHK

instruction

CHKCIR

Format change instruction for

Failure detection ladder patterns can be changed in a

CHKEND

CHK instruction

replacement program.

Instructions can be replaced using a replacement program.
Appendix 3.3.3 (4)

• Use the PSCAN instruction instead of this instruction
when low-speed execution type programs are replaced
PLOW

registration instruction

with scan execution type programs.
• No instruction can be used if low-speed execution type

---

programs are replaced with fixed scan execution type
programs.
PCHK

Program execution status
check instruction

Check a program execution status on the Program monitor
list screen of GX Developer. For details, refer to Section

---

6.13.1 in this manual.
• It is recommended to use GOT as a numeral input device.

KEY

Numerical key input instruction

• Instructions can be replaced using a replacement

Appendix 3.3.3 (5)

program.
PLOADP
PUNLOADP

Load program from memory

Store all programs to be executed in the program memory.

card

The Universal model QCPU can neither add programs to

Unload program from memory

the program memory nor change them with other programs

card

during RUN. If the capacity of the program memory is not

---

enough, store parameters, device comments, and initial
PSWAPP

Load + Unload

device values in the program memory into the standard
ROM or a memory card instead.

App - 23

Appendix 3 Method of Replacing Basic Model QCPU or High Performance Model QCPU with Universal
Model QCPU
Appendix 3.3 Instructions

data using the reading device comment data instruction

Program low-speed execution

TableApp.26 SFC control instructions not supported in the Universal model QCPU and replacing methods
Symbol

Instruction

Replacing method

LD TRn
AND TRn
OR TRn
LDI TRn
ANDI TRn
ORI TRn

Forced transition check

When the programmable controller type is changed, these instructions are

LD BLm\TRn

instruction

converted into SM1255. Modify programs as needed.

AND BLm\TRn
OR BLm\TRn
LDI BLm\TRn
ANDI BLm\TRn
ORI BLm\TRn
SCHG(D)

Active step change
instruction

Refer to Appendix 3 "Restrictions and replacing method of the Basic model QCPU
and Universal model QCPU" in the QCPU (Q Mode)/QnACPU Programming
Manual (SFC).

SET TRn
SET BLm\TRn
RST TRn

Refer to Appendix 3 "Restrictions and replacing method of the Basic model QCPU
Transition control instruction

and Universal model QCPU" in the QCPU (Q Mode)/QnACPU Programming
Manual (SFC).

RST BLm\TRn
BRSET(S)

App - 24

Block switching instruction

When the programmable controller type is changed, these instructions are
converted into SM1255. Modify programs as needed.

APPENDICES

Appendix 3.3.2 Replacing programs using multiple CPU transmission
dedicated instructions

(1) Replacing the module with the QnUD(H)CPU or Built-in Ethernet port QCPU

TableApp.26 shows instructions need to be replaced and corresponding alternative instructions. For
the specifications of each instruction, refer to the manuals for the Motion CPU.

3
TableApp.27 SFC instructions not supported in the QnUD(H)CPU and Built-in Ethernet port QCPU and thier alternatives
Symbol

Instruction description

Symbol of alternative
instruction

S(P).DDWR

Write other CPU device data into host CPU

D(P).DDWR

S(P).DDRD

Read other CPU device data into host CPU

D(P).DDRD

S(P).SFCS

Request of motion SFC program startup

D(P).SFCS

S(P).SVST

Request of servo program startup

D(P).SVST

S(P).CHGA

Current value change of halted axis/synchronized encoder/cam axis

D(P).CHGA

S(P).CHGV

Axis speed change during positioning and JOG operation

D(P).CHGV

S(P).CHGT

Torque control value change during operation and suspension in real mode

D(P).CHGT

S(P).GINT

Request of other CPU interrupt program startup

D(P).GINT

APPENDIX

6
7
8

(2) Replacing the module with the Q00UCPU, Q01UCPU, or Q02UCPU
The Q00UCPU, Q01UCPU, and Q02UCPU support the same multiple CPU transmission dedicated instructions
Appendix 3 Method of Replacing Basic Model QCPU or High Performance Model QCPU with Universal
Model QCPU
Appendix 3.3 Instructions

used in the Basic model QCPU.
The alternative instructions in TableApp.27 are not available for these CPU modules.

App - 25

Appendix 3.3.3 Program replacement examples
This section shows program replacement examples for the instructions of which replacement programs
are available in Appendix 3.3. (Skip this section if instructions listed in Appendix 3.3.1 are not used.)

(1) Replacement example of the IX and IXEND instructions
Since index registers are saved using the ZPUSH instruction, a 23-word index register save area is required.

(a) Example of device assignment
TableApp.28 Example of device assignment
Before replacement
Application
Index modification table

After replacement
Device

D100 to D115

Application

Device

Index modification table

D100 to D115

Index register save area

D200 to D222

If the device numbers in the example above are used for other applications, assign unused device numbers
instead.

(b) Program before replacement
The modification value set in the
index modification table is added.

Modification target
(No change required)

Figure App.1 Sample program

App - 26

APPENDICES

(c) Program after replacement
• Replace the IX instruction with the ZPUSH instruction and the processing for setting the contents of index

modification table to index registers.
• Replace the IXEND instruction with the ZPOP instruction.

2
Current index register is
saved.

APPENDIX

6
Contents of the index
modification table are
set to the index
registers Z0 to Z15.

Transition
from the IX
instruction

7
8

The saved index register is restored.
(Transition from the IXEND instruction)

Figure App.2 Sample program

App - 27

Appendix 3 Method of Replacing Basic Model QCPU or High Performance Model QCPU with Universal
Model QCPU
Appendix 3.3 Instructions

Modification target
(No change required)

(2) Replacement example of the IXDEV and IXSET instructions
Change the program so that the device offset value specified by the contacts between the IXDEV and the IXSET
instructions are directly set to the index modification table using the MOV instruction.
For the devices whose device offset value is not specified by the IXDEV and IXSET instructions, set the device
offset value to 0 in the program after replacement.
Figure App.3 shows how the device offset value is set in the program before and after replacement.
Device offset specification
Timer
Counter
Input *1
Output *1
Internal relay
Latch relay

Index modification table

(D)+0

(D)+1

(D)+2

(D)+3

(D)+4

(D)+5

(D)+6

Edge relay
Link relay *1
Data register
Link register *1
File register
Intelligent function
module device *2

Link direct device *3
File register
(through number)
Pointer

(D)+7

D .XX

(D)+8

W .XX

(D)+9

R .XX

(D)+10
Start I/O number

(D)+11

Buffer memory address

(D)+12

U \G .XX

J \B

(D)+13

ZR .XX

IXSET

(D)+14
P

(D)+15

Figure App.3 Device offset value specification and index modification table

*1: Device numbers are represented in hexadecimal. Use hexadecimal constants (H
fication table.

) when setting values in the index modi-

*2: Start I/O numbers (U ) are represented in hexadecimal. Use hexadecimal constants (H
index modification table.

) when setting values in the

*3: Devices B, W, X, or Y can be specified following J\. . Set device numbers for B, W, X, and Y as device offset values of
each device in the index modification table.
For example, if "J10\Y220" is specified by the IXDEV and IXSET instructions, set "K10" in (D)+13 and "H220" in (D)+3 in
the replacement program. ((D) indicates the start device in the index modification table.)

App - 28

APPENDICES

(a) Program before replacement
The device offset values for input
(X), output (Y), internal relay (M),
data register (D), link register (W),
and pointer (P) are set to the index
modification table starting from D0.

Figure App.4 Sample program

2
3

(b) Program after replacement

APPENDIX

6
7
8

Figure App.5 Sample program

App - 29

Appendix 3 Method of Replacing Basic Model QCPU or High Performance Model QCPU with Universal
Model QCPU
Appendix 3.3 Instructions

The device offset values specified
by the IXDEV and IXSET
instructions are set to the index
modification table starting from D0.

(3) Replacement example of the PR instruction
The number of output characters can be switched by the on/off status of SM701.

(a) Example of device assignment
TableApp.29 Example of device assignment
Before replacemen
Application

After replacement
Device

Application

Device

Output string

D0 to D3

Output string

D0 to D3

ASCII code output signal

Y100 to Y107

ASCII code output signal

Y100 to Y107

Strobe signal

Y108

Strobe signal

Y108

In-execution flag

Y109

In-execution flag

Y109

Output string storage address (BIN32)

D20 to D21

Output string storage address (BIN32)
(Used for sub-routine programs and

D200 to D201

interrupt programs)
Number of output characters

D202

Output module start Y number

D203

Character extraction position

D204

Number of extracted characters

D205

String output status value

D206

Result of string extraction by the MIDR
instruction

D207

String output in-execution flag

M200

For index modification

If the device numbers in the example above are used for other applications, assign unused device numbers
instead.

(b) Program before replacement
The number of output strings is set
to variable. (Output until ASCII code
00H appears.)

The strings stored in D0 and later are
output from Y100 to Y108.

Figure App.6 Sample program

App - 30

APPENDICES

In the sequence program after replacement, three programs are required as shown below.

Main routine
program

END

Output strings and output string storage address are set.

FEND
P1

Subroutine
program

Initial processing

RET
I31

IInterrupt
program

APPENDIX

The strings stored in D0 are output.

IRET
END

Figure App.7 Program execution

1) Main routine program
• Replace the PR instruction with the CALL instruction so that a subroutine program is called.
• Output string storage device ("D0" in the program below) cannot be specified directly with the CALL
instruction.

• Use the ADRSET instruction to acquire the indirect address for the CALL instruction.
• Y device ("Y100" in the program before replacement shown in (b)) cannot be specified directly as output
Y number with the CALL instruction. Specify the output Y number in integer.
interrupt programs using the EI instruction.

The strings stored in D0 and
later are output from Y100 to
Y108.
An execution of interrupt program is
enabled.

Figure App.8 Sample program

App - 31

Appendix 3 Method of Replacing Basic Model QCPU or High Performance Model QCPU with Universal
Model QCPU
Appendix 3.3 Instructions

• An interrupt program is used to output character codes via the output module. Enable the execution of

2) Subroutine program
• In the subroutine program, the data for outputting ASCII codes using a fixed scan interrupt program
(10ms) are set to work devices. Also, the flag for activating the processing in the fixed scan interrupt program is turned on.
• Specify the following arguments for the subroutine program.
First argument

Output string storage address

(Input)

Second argument

Output module start Y number

(Input)

Data specified by the CALL(P)
arguments are saved.
Output string storage address
Number of output strings
Output module start number

Devices used for the string
output processing of the
interrupt program I31 are
initialized.

Yn0 to Yn7 (ASCII code),
Yn8 (strobe signal), and Yn9
(in-execution flag) are all
turned OFF.

The flag for activating the string
output processing in the interrupt
program is turned on.

Figure App.9 Sample program

App - 32

APPENDICES

3) Interrupt program

The following processing is added to a fixed scan interrupt program (10ms).
The fixed scan interrupt program outputs ASCII codes from the output module and controls the strobe signal.

2
The following signals are
all turned off when all
strings are output.
Yn0 to Yn7 (ASCII code)
Yn8 (strobe signal)
Yn9 (in-execution flag)

APPENDIX

Status 0:
One character is extracted
from the output string using
the MIDR instruction and
output to the Y module.
The strobe signal is turned
off for 10ms.
Status 1:
The strobe signal is turned on for
10ms.
Status 2:
The strobe signal is turned off
for 10ms.

6
7
8

The status value is incremented
by one.

Figure App.10 Sample program

App - 33

Appendix 3 Method of Replacing Basic Model QCPU or High Performance Model QCPU with Universal
Model QCPU
Appendix 3.3 Instructions

Status 3:
The status value is returned
to 0 since the output
processing of one character
is completed. The next
character is extracted.

(4) Replacement example of the CHKST and CHK instructions
In the example below, if the replacement program for the CHKST and CHK instructions detects a failure, a failure
number (contact number + coil number) is stored in D200 and the annunciator F200 is turned on.

(a) Example of device assignment
TableApp.30 Example of device assignment
Before replacement

After replacement

Application

Device

Application

Device

Advance end detection sensor input 1

X100

Advance end detection sensor input 1

X100

Retract end detection sensor input 1

X101

Retract end detection sensor input 1

X101

Advance end detection sensor input 2

X102

Advance end detection sensor input 2

X102

Retract end detection sensor input 2

X103

Retract end detection sensor input 2

X103

Advance end detection sensor input 3

X104

Advance end detection sensor input 3

X104

Retract end detection sensor input 3

X105

Retract end detection sensor input 3

X105

Advance end detection sensor input 4

X106

Advance end detection sensor input 4

X106

Retract end detection sensor input 4

X107

Retract end detection sensor input 4

X107

Failure detection output 1

Y100

Failure detection output 1

Y100

Failure detection output 2

Y102

Failure detection output 2

Y102

Failure detection output 3

Y104

Failure detection output 3

Y104

Failure detection output 4

Y106

Failure detection output 4

Y106

Coil number (failure type detected)

D100

Contact number

D101

Failure number

D200

Failure detection display

F200

For index modification

If the device numbers in the example above are used for other applications, assign unused device numbers
instead.
When the advance end detection sensor input performs a failure detection of Xn, assign device numbers for
the retract end detection sensor input and the failure detection output as described below.
Advance end detection sensor input

Retract end detection sensor input

Xn+1

Failure detection output

(b) Program before replacement

Figure App.11 Sample program

App - 34

APPENDICES

Main routine
program

END

Initial processing

FEND
P0

Subroutine
program

An failure status is checked, and if a failure is detected,
a failure number is stored in D200.

RET
END
APPENDIX

Figure App.12 Program execution

1) Main routine program
• Replace the CHKST and CHK instructions with the CALL instructions so that a subroutine program is
called.
• One CALL instruction is required for each device specified as check condition in front of the CHK

instruction. (In the program before replacement shown in (b), four CALL instructions need to be added
since there are four check conditions in front of the CHK instruction.)
• Device number and contact number of X devices (check condition) are specified in each CALL instruc-

tion.
• Contact number is used to display failure number when a failure is detected.
Appendix 3 Method of Replacing Basic Model QCPU or High Performance Model QCPU with Universal
Model QCPU
Appendix 3.3 Instructions

Figure App.13 Sample program

App - 35

2) Subroutine program
• In the subroutine program, an failure status is checked using a failure detection ladder pattern.
• If a failure is detected, a failure number is stored in D200 and the annunciator F200 is turned on.
• Specify the following arguments for the subroutine program.
First argument

Device number of X device targeted for failure check

(Input)

Second argument

Contact number of X device targeted for failure check

(Input)

If a failure is detected, the
coil number corresponding
to the failure type is set to
D100.

If a failure is detected, a
failure number is created
by combining the coil
number corresponding to
the failure type and the
contact number.
The annunciator is turned
on.

Figure App.14 Sample program

(d) Replacement method when failure detection ladder patterns are changed by the CHKCIR and
CHKEND instructions
Failure detection ladder patterns can be changed in the subroutine program described in (c).

App - 36

APPENDICES

(5) Replacement example of the KEY instruction
(a) Example of device assignment

TableApp.31 Example of device assignment
Before replacemen
Application
Numeric input execution

After replacement
Device

Application

Device

Numeric input execution instruction

Input complete flag

Input data area

D200 to D203

Input data area

D200 to D203

ASCII code input signal

X100 to X107

ASCII code input signal

X100 to X107

Strobe signal

X108

Strobe signal

X108

Input data area address (BIN32)

D210 to D211

(Input data area + 0) address (BIN32)

D212 to D213

(Input data area + 1) address (BIN32)

D214 to D215

(Input data area + 2) address (BIN32)

D216 to D217

For shifting input data

D218

For converting input data

D219 to D220

instruction

If the device numbers in the example above are used for other applications, assign unused device
numbers instead.

APPENDIX

6
7
8

(b) Program before replacement
Appendix 3 Method of Replacing Basic Model QCPU or High Performance Model QCPU with Universal
Model QCPU
Appendix 3.3 Instructions

Figure App.15 Sample program

App - 37

Main routine
program

END

Initial processing

FEND
P2

Subroutine
program

ASCII code is added to the input data area.

RET
END
Figure App.16 Program execution

1) Main routing program
• Set "0" in the input data area on the rising edge of the execution instruction ("M0" in the program below)
and initialize the program.
• Execute the CALL instruction on every rising edge of the strobe signal ("X108" in the program below) so
that a subroutine program is called.
• In the subroutine program, input codes are added to the input data area and the completion status is
checked.
• Pass the following data to the subroutine program at execution of the CALL instruction.
1) ASCII code input values from the input module (Xn0 to Xn7)
2) Number of digits to be input
3) Indirect address of the input data area (Use the ADRSET instruction to acquire the indirect
address for the input data area.)
4) Bit devices to be turned on when input is completed

The input data area is initialized.

A subroutine program is called at
the rising edge of the strobe signal.

Figure App.17 Sample program

App - 38

APPENDICES

2) Subroutine program
• In the subroutine program, ASCII codes specified by an argument are added to the input data area and

the completion status is checked.
• Specify the following arguments for the subroutine program.
First argument

ASCII code input from the input module (K2Xn)

(Input)

Second argument

Number of digits to be input

(Input)

Third argument

Indirect address of the input data area

(Input)

Fourth argument

Bit device to be turned on when input is completed

(Output)

2
3

Numeric entry is ended when
the at-completion on signal is
on or 0DH is input.

APPENDIX
Addresses of the input data
area are saved in the work
devices.

6
7

The 1st to 4th digit numerals
in (input data area +2) are
shifted for one digit to the left.

The 5th to 8th digit numerals
in (input data area +1) are
shifted for one digit to the left
and the converted numeral is
set to the 8th digit.
The number of digits to be input
in (input data area +0) is
incremented by one.
The at-completion on signal
is turned on when the input
processing for specified digits
is completed.

Figure App.18 Sample program

App - 39

Appendix 3 Method of Replacing Basic Model QCPU or High Performance Model QCPU with Universal
Model QCPU
Appendix 3.3 Instructions

Numeral entered in ASCII code
is converted into one numeral
in BIN data using the HABIN
instruction.

Appendix 3.4 Functions
Appendix 3.4.1 Floating-point operation instructions
(1) Differences between High Performance model QCPU and Universal model QCPU
(a) High Performance model QCPU
The High Performance model QCPU can perform only the single-precision floating-point operation
instructions. Note, however, that internal operation processing can be performed in double precision
by selecting the item shown below (default: selected).

Selected by default.

Figure App.19 PLC system tab

(b) Universal model QCPU
The Universal model QCPU supports the double-precision floating-point operation instructions.
The operation can be performed either in single precision or double precision depending on the data. Therefore, the "Perform internal arithmetic operations in double precision" item in the PLC system tab of the PLC
parameter dialog box cannot be selected.
Because of this new function, operation results (both in single precision and double precision) slightly differ
between the High Performance model QCPU and the Universal model QCPU if "Perform internal arithmetic
operations in double precision" is selected in the High Performance model QCPU.
If higher accuracy is required in floating-point operations, replace the floating-point operation instructions as
described in (4).
However, if six or less digits are used as significant digits for the floating-point operation instructions, replacement is not necessary. The single-precision floating-point operation results in the Universal model QCPU can
be used as they are in the system. When not replacing instructions, make sure that it does not cause any problems in the system.

App - 40

APPENDICES

(2) Floating-point operation instructions for the Universal model QCPU
TableApp.30 lists floating-point operation instructions for the Universal model QCPU.

Specifications of the single-precision floating-point operation instructions are compatible with those for
the High Performance model QCPU.

TableApp.32 List of floating-point operation instructions supported in the Universal model QCPU

Instruction symbol
Instruction name

Single-precision

Double-precision

floating-point data

LDE

LDED

ANDE

ANDED

ORE

ORED

Floating-point data transfer

EMOV(P)

EDMOV(P)

Floating-point data addition

E+(P)

ED+(P)

Four arithmetic

Floating-point data subtraction

E-(P)

ED-(P)

operation

Floating-point data multiplication

E*(P)

ED*(P)

Floating-point data division

E/(P)

ED/(P)

FLT(P)

FLTD(P)

DFLT(P)

DFLTD(P)

Comparison

Floating-point data comparison

Data transfer

Conversion from BIN 16-bit data
to floating-point data
Conversion from BIN 32-bit data
to floating-point data
Data conversion

Conversion from floating-point

<>,=,<,>,<=,>=

APPENDIX

6
7

---

DINTD(P)

Floating-point sign inversion

ENEG(P)

EDNEG(P)

SIN operation

SIN(P)

SIND(P)

COS operation

COS(P)

COSD(P)

TAN operation

TAN(P)

TAND(P)

SIN-1 operation

ASIN(P)

ASIND(P)

COS-1 operation

ACOS(P)

ACOSD(P)

TAN-1operation

ATAN(P)

ATAND(P)

Conversion from angle to radian

RAD(P)

RADD(P)

Conversion from radian to angle

DEG(P)

DEGD(P)

Square root

SQR(P)

SQRD(P)

Exponential operation

EXP(P)

EXPD(P)

Natural logarithm operation

LOG(P)

LOGD(P)

---

Floating-point data can be converted mutually between single precision and double precision using
instructions in TableApp.33.
TableApp.33 Floating-point data conversion instructions (single precision

double precision)

Instruction name

Instruction symbol

Single precision to double precision conversion

ECON(P)

Double precision to single precision conversion

EDCON(P)

App - 41

Appendix 3 Method of Replacing Basic Model QCPU or High Performance Model QCPU with Universal
Model QCPU
Appendix 3.4 Functions

DINT(P)

data to BIN 32-bit data

---

INTD(P)

Conversion from floating-point

Special function

indicates one of
the followings;

INT(P)

data to BIN 16-bit data

Remarks

(3) Advantages and disadvantages when using the double-precision floating-point data of
the Universal model QCPU
TableApp.32 shows the advantages and disadvantages when executing the double-precision floating-point operation instructions in the Universal model QCPU.

If higher accuracy is required in floating-point operations, it is recommended to replace the instructions with the double-precision floating-point operation instructions.
TableApp.34 Advantages and disadvantages when using the double-precision floating-point operation instructions
Advantage
The results are more accurate than those of the
single-precision floating-point operation
instructions.

Disadvantage
The instruction processing speed is slower than that of the singleprecision floating-point operation instructions.*1
Double-precision floating-operation data use twice as many word device
points as single-precision floating-operation data.

*1: The processing speed of the double-precision floating-point operation instructions in the Universal model QCPU is higher
than that of floating-point operation instructions using internal double-precision operations in the High Performance
model QCPU.

TableApp.33 shows the comparison between single-precision and double precision floating-point data.
TableApp.35 Comparison between single-precision and double precision floating-point data
Item
Word point required for data retention

Single-precision floating-point

data

2 words

4 words

-2128= / LDED>=)
Instruction processing

Data transfer

speed (Q04UDHCPU/

(EMOV/EDMOV)

Q06UDHCPU) (Maximum)

Addition (3 devices)
(E+ / ED+)
SIN operation (SIN/SIND)

App - 42

Double-precision floating-point

data

APPENDICES

(4) Replacing the High Performance model QCPU with the Universal model QCPU
(a) Replacing all single-precision floating-point operation instructions with double-precision
floating-point operation instructions

1
2

Single-precision floating-point data occupy two points of word device per data.
On the other hand, four points are required per double-precision floating-point data.

Therefore, all device numbers for storing floating-point data need to be reassigned.
Example

Replacing the floating-point operation [A
data into double precision.)

B+C] (Changing all floating-point

1) Device assignment

APPENDIX

TableApp.36 Device assignment
Before replacement
Application

Device

Data A

D0 to D1

Data B

D2 to D3

Data C

D4 to D5

Result

D6 to D7

After replacement
Data type

Application

Device

Data type

Data A

D0 to D3

Floating-point data

Data B

D4 to D7

Floating-point data

(single precision)

Data C

D8 to D11

(double precision)

Result

D12 to D15

6
7
8

2) Program before replacement

3) Program after replacement
Operation is performed using
double-precision floating-point
data.

Figure App.21 Sample program

App - 43

Appendix 3 Method of Replacing Basic Model QCPU or High Performance Model QCPU with Universal
Model QCPU
Appendix 3.4 Functions

Figure App.20 Sample program

(b) Replacing a part of floating-point operation instructions with double-precision floating-point
operation instructions
Only operations that require high accuracy are replaced with double-precision floating-point operation instructions.
Using the ECON and EDCON instructions, convert floating-point data mutually between single precision and double-precision. The flow of a replacement program is as follows:
• Data required for operations are converted from single precision to double precision using the ECON
instruction.
• Operations are performed in double precision using the double-precision floating-point operation instructions.
• Operation results are converted from double precision to single precision using the EDCON instruction.

A program example that floating-point data are converted mutually between single precision and
double precision before and after operations is shown below.
Example

Replacing the floating-point operation [A
instructions)

B+C] (Using the ECON and EDCON

1) Device assignment
TableApp.37 Device assignment
Before replacement
Application

Device

After replacement
Data type

Application

Device

Data type

Data A

D0 to D1

Data A

D0 to D1

Data B

D2 to D3

Floating-point data

Data B

D2 to D3

Floating-point data

Data C

D4 to D5

(single precision)

Data C

D4 to D5

(single precision)

Result

D6 to D7

Result

D6 to D7

Data A

D10 to D13

Data B

D14 to D17

Floating-point data

Data C

D18 to D21

(double precision)

Result

D22 to D25

2) Program before replacement

Figure App.22 Sample program

App - 44

APPENDICES

3) Program after replacement

1
Floating-point data are
converted from single precision
to double precision.

Operation is performed using
double-precision floating-point
data.

2
3

The floating-point operation result
data are converted from double
precision to singe precision.

Figure App.23 Sample program

APPENDIX

6
7
8

Appendix 3 Method of Replacing Basic Model QCPU or High Performance Model QCPU with Universal
Model QCPU
Appendix 3.4 Functions

App - 45

(c) Replacing a part of floating-point operation instructions with double-precision floating-point
operation instructions using subroutine programs
The flow of a replacement program described in (b) can be regarded as one subroutine program.
Create a subroutine program for each floating-point operation instruction and then replace the original floatingpoint operation instructions with the CALL(P) instruction so that the corresponding subroutine program is
called.
With this method, changes in the program are minimized, but the processing for calling subroutine programs
increases the scan time.
In addition, since conversions from double precision to single precision are performed for each instruction,
rounding-off errors generated during operations are larger than those in the replacement program described in
(b).

Example

Replacing the floating-point operation[A

B+C] (Using a subroutine program)

1) Device assignment
TableApp.38 Device assignment
Before replacement
Application

Device

After replacement

Data type

Application

Device

Data type

Data A

D0 to D1

Data A

D0 to D1

Data B

D2 to D3

Floating-point data

Data B

D2 to D3

Floating-point data

Data C

D4 to D5

(single precision)

Data C

D4 to D5

(single precision)

Result

D6 to D7

Result

D6 to D7

Subroutine input
data 1
Subroutine input
data 2
Subroutine
operation result

2) Program before replacemennt

Figure App.24 Sample program

App - 46

D900 to D903
D904 to D907
D908 to D911

Floating-point data
(double precision)

APPENDICES

3) Program after replacement

1
2
3
A subroutine program for
multiplication using the
double-precision
floating-point operation
instruction

APPENDIX

6
A subroutine program for
addition using the
double-precision
floating-point operation
instruction

7
8

Figure App.25 Sample program

Appendix 3 Method of Replacing Basic Model QCPU or High Performance Model QCPU with Universal
Model QCPU
Appendix 3.4 Functions

App - 47

Appendix 3.4.2 Error check processing for floating-point data comparison
instructions
(1) Input data check
Error check processing for floating-point data comparison instructions performed in the Universal model QCPU
are enhanced. Input of a "special value" (-0, nonnumeric, unnormalized number, or

) is checked, and if those

special values are input, the CPU module detects “OPERATION ERROR” (error code: 4140).
When the LDE , ANDE , ORE , LDED , ANDED , and/or ORED

instructions (

indicates one of the fol-

lowings; =,<>,<,>,<=,>=) are used in the program, “OPERATION ERROR” (error code: 4140) may be detected if
invalid floating-point data exist. This occurs even when interlocks are provided using the valid data flags (the signal which shows the floating-point validity).
Invalid floating-point data are not stored in the result of operations performed in the Universal model QCPU.
Those invalid data are considered to be stored in the following cases:
• The same device is used for storing floating-point data and other data, such as binary values, BCD values,
and strings.
Use different devices for storing floating-point data and data other than floating-point data.
• Floating-point data externally written are invalid.
Take measures on the external-source side so that valid data are written.

If an error occurs in the floating-point data comparison instructions, take appropriate measures to
remove error causes described above.
Example 1) Detecting “OPERATION ERROR” (error code: 4140) in the LDE

[Ladder mode]

instruction

[List mode]

In the ladder block starting from the step 104, the floating-point data comparison instructions of the step 105 and
109 are not executed when the M101 (valid data flag) is off.
However, the LDE<= instruction of the step 105 and the ORE>= instruction of the step 109 are executed regardless of the execution result of the LD instruction of the step 104 in the program above.
Therefore, even when the M101 is off, “OPERATION ERROR” (error code: 4140) will be detected in the LDE<=
instruction of the step 105 if a "special value" is stored in D100.
For the method of avoiding “OPERATION ERROR”, refer to(2) in this section.

App - 48

APPENDICES

Example 2) Not detecting “OPERATION ERROR” (error code: 4140) in the ANDE
instruction
[Ladder mode]

1
2

[List mode]

In the ladder block starting from the step 104, the ANDE<= instruction of the step 105 is not executed when the
M101 (valid data flag) is off.

APPENDIX

The ANDE<= instruction of the step 105 is not executed when the M101 is off in the LD instruction of the step 104
in the program above. Therefore, when the M101 is off, “OPERATION ERROR” (error code: 4140) will not be
detected even if a "special value" is stored in D100.

Example 3) Detecting "OPERATION
instruction

ERROR"

(error

code:

[Ladder mode]

4140)

the

ANDE

[List mode]

the step 110 are not executed when the M101 (valid data flag) is off.
However, if the M90 is on in the LD instruction of the step 105, the ANDE<= instruction of the step 106 is executed. Therefore, even when the M101 is off, "OPERATION ERROR" (error code: 4140) will be detected in the
ANDE<= instruction of the step 106 if the M90 is on and a "special value" is stored in D100.
For the method of avoiding “OPERATION ERROR”, refer to (2) in this section.

App - 49

7
8

Appendix 3 Method of Replacing Basic Model QCPU or High Performance Model QCPU with Universal
Model QCPU
Appendix 3.4 Functions

In the ladder block starting from the step 104, the ANDE<= instruction of the step 106 and the OR>= instruction of

(2) Method of avoiding “OPERATION ERROR” (error code: 4140) in the floating-point data
comparison instructions
As shown in the modification examples below, connect the contacts of valid data flag in series for each floatingpoint data comparison instruction. (Use AND connection for connecting the contact of the valid data flag and the
floating-point data comparison instruction.)
Make sure that there is no line (OR connection) between the valid data flag and the floating-point data comparison instruction.

(Before modification)
E<=

(After modification)
D100

E10

Valid
data
flag

E<=

D100

E10

E>=

D100

E200

Valid
data
flag
E>=

D100

E200
Valid
data
flag

Make sure that there is no line (OR connection)
between the signal which shows the
floating-point data validity (valid data flag) and
the floating-point data comparison instruction.

(Before modification)
E<=

(After modification)
D100

E10

M200

M201
Valid
data
flag

App - 50

E<=

D100

M200

M201

Valid
data
flag

E10

APPENDICES

Program examples after modification for Example 1) and 3) in (1) are shown below.

Example 4) Program after modification for Example 1) ("OPERATION ERROR" (error code:
4140) is no longer detected.)
[Ladder mode]

[List mode]

APPENDIX

Example 5) Program after modification for Example 3) ("OPERATION ERROR" (error code:
4140) is no longer detected.)
[Ladder mode]

6
7

[List mode]

Appendix 3 Method of Replacing Basic Model QCPU or High Performance Model QCPU with Universal
Model QCPU
Appendix 3.4 Functions

App - 51

Appendix 3.4.3 Range check processing for index-modified devices
(1) Device range check
Error check processing at index modification of devices has been enhanced for the Universal model QCPU.
Each index-modified device range is checked, and if the check target device is outside the device range before
index modification, the CPU module detects "OPERATION ERROR" (error code: 4101).

Example 1) Detecting "OPERATION ERROR" (error code: 4101) by error check processing at
index modification of devices

In Example 1), when the contact (M0) is on and the value, -1 or less, is specified in Z1, the device D0Z1 is
included in the C device range, exceeding the D device range, as shown in Figure App.26.
As a result, "OPERATION ERROR" (error code: 4101) will be detected.

When the value of Z1 is -1,
the device is included in the
C device range, resulting in an error.

C device area

D0
D device area

W0
W device area

Figure App.26 Device D0Z1 when the value of Z1 is -1

When an error is detected, check the index modification value (value of Z1 in the above example) and remove the
error cause.
Examples of the cases where an error is detected and not detected are shown below.

App - 52

APPENDICES

Example 2) Detecting "OPERATION ERROR" (error code: 4101)
[Ladder mode]

[List mode]

2
3

In Example 2, in the ladder block starting from the step 15, the AND<> instruction of the step 17 or 21 is supposed
to be not executed when M0 (valid data flag) is off.
However, since the LD instruction which is always executed is used in the step 16 and 20, the AND<> instruction
of the step 17 or 21 is executed regardless of the execution status of the LD instruction in the step 15 when M1 or

APPENDIX

M2 is on.
For this reason, even when M0 is off, if the D10Z1 value is outside the D device range, "OPERATION ERROR"
(error code: 4101) will be detected in the AND<> instruction of the step 17.

Note that the step 26 (MOV D0 D1) and the step 28 (INC D2) are not executed.
For the method of avoiding "OPERATION ERROR" (error code: 4101), refer to (2) in this section.

Example 3) Not detecting "OPERATION ERROR" (error code: 4101)

[Ladder mode]

[List mode]

For this reason, "OPERATION ERROR" (error code: 4101) will not be detected no matter what the D10Z1 value
is.

App - 53

Appendix 3 Method of Replacing Basic Model QCPU or High Performance Model QCPU with Universal
Model QCPU
Appendix 3.4 Functions

In Example 3, the AND<> instruction of the step 16 is not executed when M0 (valid data flag) of the step 15 is off.

(2) Method of avoiding "OPERATION ERROR" (error code: 4101)
When the index-modified device range does not need to be checked, use the method 1).
When the index-modified device range needs to be checked, use the method 2).
1) Deselect the "Check device range at indexing" item in the PLC RAS tab of the PLC parameter dialog box so
that the index-modified device range will not be checked.
2) As shown in the modification examples below, connect the contacts of valid data flag in series for each
instruction that checks the index-modified device range.

(Before modification)

(After modification)

[Ladder mode]

M1
<> D10Z1 K5

<> D10Z1 K5

Valid
data
flag

Valid data
flag
M0

M2
<> D10Z1 K10

<> D10Z1 K10

Valid data
flag
[List mode]
LD
LD
AND <>
LD
AND <>
ORB
ANB

[List mode]
M0
M1
D10Z1
M2
D10Z1

K5
K10

LD
AND
AND <>
LD
AND
AND <>
ORB

M0
M1
D10Z1
M0
M2
D10Z1

K10

In the program before modification (on the left), the instruction immediately before the AND<> instruction is
regarded as the LD instruction. However, in the program after modification (on the right), the same instruction will
be regarded as the AND instruction.
In the program after modification, only when both contacts of M0 and M1 (or M2) turn on, the AND<> instruction
is executed. As a result, no error will be detected during index-modified device range check processing.

App - 54

APPENDICES

Appendix 3.4.4 Device latch function

(1) Overview
The device latch function*1 for the Universal model QCPU is more enhanced compared to that for the Basic
model QCPU and High performance model QCPU.

This section describes the enhanced device latch function in the Universal model QCPU.

*1: The latch function is used to hold device data even when the CPU module is powered off or reset.

(2) Device data latch methods
Device data of the Universal model QCPU can be latched by:
• using the large-capacity file register (R, ZR),
• writing/reading device data to the standard ROM (with the SP.DEVST and S(P).DEVLD instructions), or
• specifying a latch range of internal user devices.

APPENDIX

(3) Details of each latch method
(a) Large-capacity file register (R, ZR)
Data in the file register can be latched by batteries.
File register size is larger and processing speed is higher in the Universal model QCPU, compared to the Basic

model QCPU and High Performance model QCPU.
To latch a lot of data (many device points), use of the file register is effective.

TableApp.39 shows the file register size available for each CPU module.
TableApp.39 File register size available for each CPU module
File register (R, ZR) size in the standard RAM

Q00UCPU,Q01UCPU,Q02UCPU

64K points

Q03UDCPU,Q03UDECPU

96K points

Q04UDHCPU,Q04UDEHCPU

128K points

Q06UDHCPU,Q06UDEHCPU

384K points

Q10UDHCPU,Q13UDHCPU,Q10UDEHCPU,Q13UDEHCPU

512K points

Q20UDHCPU,Q20UDHCPU,Q26UDEHCPU,Q26UDEHCPU

640K points

(b) Writing/reading device data to the standard ROM (SP.DEVST and S(P).DEVLD instructions)
Device data of the Universal model QCPU can be latched using the SP.DEVST and S (P).DEVLD instructions
(instructions for writing/reading data to/from the standard ROM).
Utilizing the standard ROM allows data backup without batteries.
This method is effective for latching data that will be updated less frequently.

App - 55

Appendix 3 Method of Replacing Basic Model QCPU or High Performance Model QCPU with Universal
Model QCPU
Appendix 3.4 Functions

Model

(c) Specifying the latch range of internal user devices
Device data of the Universal model QCPU can be latched by specifying a latch range of internal user devices in
the same way as for the Basic model QCPU and High Performance model QCPU.
The ranges can be set in the Device tab of the PLC parameter dialog box.
Internal user devices that can be latched are as follows:
• Latch relay (L)
• Link relay (B)
• Annunciator (F)
• Edge relay (V)
• Timer (T)
• Retentive timer (ST)
• Counter (C)
• Data register (D)
• Link register (W)

●

If latch ranges of internal user devices are specified in the Universal model QCPU, the processing time will be added to
the scan time in proportion to the device points set to be latched. (For example, if 8K points are latched for the latch
relay (L), the scan time will be 28.6 s.) To shorten the scan time, remove unnecessary latch device points to minimize
the latch range.

●

The scan time will not increase when a latch range of the file register (R, ZR) is specified.

(4) How to shorten the scan time
When data to be latched are stored in the file register (R, ZR), the processing time is shorter than that
for latching internal user device.
Example

Reducing the latch points of the data register (D) from 8K points to 2K points,
and using the file register (ZR) instead (when the Q06UDHCPU is used)

TableApp.40 Differences between before and after moving latch points of the data register (D) to the file register (ZR)
Item

Before

After

8192 (8K) points

(6K points are moved to the file

2048 (2K) points
Latch points of the data register (D)

Data register (D) (Latch range)
File register (ZR) (Standard RAM)

400

100

300

0.41ms

0.13ms*1

---

300 steps

*1: Time indicates the time required additionally when the file register is stored in the standard RAM.

App - 56

APPENDICES

Appendix 3.4.5 File usability setting

(1) Differences between High Performance model QCPU and Universal model QCPU

(a) High Performance model QCPU
In the High Performance model QCPU, file usability ("Use PLC file setting" or "Not used") of the following files
can be set for each program on the screen opened by clicking the "File usability setting" button on the Program
tab of the PLC parameter dialog box.

• File register
• Initial device value
• Comment
• Local device
APPENDIX

6
7
8

Appendix 3 Method of Replacing Basic Model QCPU or High Performance Model QCPU with Universal
Model QCPU
Appendix 3.4 Functions

Figure App.27 Program tab

App - 57

(b) Universal model QCPU
In the Universal model QCPU, file usability of the following files*1 cannot be set for each program on the screen
opened by clicking the "File usability setting" button on the Program tab of the PLC parameter dialog box.
• File register
• Initial device value
• Comment

Figure App.28 File usability setting screen
*1: Even file usability of local device file cannot be set if the serial number (first five digits) of the Q02UCPU, Q03UDCPU,
Q04UDHCPU, or Q06UDHCPU is "10011" or earlier.
If the local device is set to be used in the PLC file tab of the PLC parameter dialog box in the High Performance
model QCPU, all the programs use the local device in the Universal model QCPU after replacement.

When the file usability setting is set in the High Performance model QCPU, change the setting as described
below.

App - 58

APPENDICES

(2) Method of replacing High Performance model QCPU with Universal model QCPU

Replacement method varies depending on the settings in the PLC file tab of the PLC parameter dialog box.

TableApp.41 Replacement method
Setting in the PLC file tab
"Not used." is selected.

Setting in Universal model QCPU
No change in parameter settings is required. Operation of the Universal model QCPU is the same
regardless of the file usability setting in the High Performance model QCPU.
When file usability is set to "Not used." in the High Performance model QCPU, delete the

corresponding program file (file register, initial device value, or comment), which uses the same name
as the program, from the target memory. The Universal model QCPU executes a program without
using a program file if no program file that uses the same name as the program exists in the target
memory.

High Performance model QCPU
PLC parameter setting

"Use the same file name as the

Universal model QCPU
PLC parameter setting

PLC file setting

Use the same file name as the
File register
program. (Target memory: Memory
setting
card (RAM))

Program setting

program." is selected.

Program name
File
usability
setting

MAIN

APPENDIX

6
7

File register
Use PLC file setting

SUB1

Not used

SUB2

Not used

SRAM card

8
SRAM card

SUB1

SUB2

MAIN

File
register

Programs do not use file registers 'SUB1' and 'SUB2'
according to the "File usability setting".

SUB1
File
register

SUB2
File
register

File registers 'SUB1' and 'SUB2' shall be deleted so that the
programs 'SUB1' and 'SUB2' do not used them.

"Use the following file." is

No change in parameter settings is required. Operation of the Universal model QCPU is the same

selected.

regardless of the file usability setting in the High Performance model QCPU.

App - 59

Appendix 3 Method of Replacing Basic Model QCPU or High Performance Model QCPU with Universal
Model QCPU
Appendix 3.4 Functions

MAIN
File
register

Appendix 3.4.6 Parameter-valid drive and boot file setting
(1) Differences between High Performance model QCPU and Universal model QCPU
(a) High Performance model QCPU
The parameter-valid drive is specified by the switches on the front panel of the High Performance
model QCPU.
(b) Universal model QCPU
The Universal model QCPU automatically determines the parameter-valid drive, depending on the existence of
parameters in the drive (program memory, memory card, or standard ROM).
Therefore, when replacing the High Performance model QCPU with the Universal model QCPU, changing the
boot file setting for parameter and/or moving files to another drive may be required.
When replacing the module, change the setting as described below.

(2) Method of replacing High Performance model QCPU with Universal model QCPU
(a) When the parameter-valid drive is set to the standard ROM in the High Performance model
QCPU
TableApp.42 When the parameter-valid drive is set to the standard ROM
Setting in High Performance model QCPU
Setting in Universal model QCPU

Setting in the Boot file tab of the PLC parameter
dialog box

Change the setting so that the Universal model QCPU can refer to the
parameters in the standard ROM.

No boot file setting

• Changes in parameter settings are not required.
• Delete parameters that exist in the program memory and memory card.*2
Change the setting so that programs are stored in the program memory in the
first place, instead of booting from the standard ROM.

Settings in the Boot file tab
Type

Transfer from

Transfer to

Program

Standard ROM

Program memory

• Delete all settings for parameter in the Boot file tab of the PLC parameter
dialog box.
• Delete parameters that exist in the program memory and memory card.*2
• Move the programs with boot setting into the program memory from the

(No boot file setting for parameters)

standard ROM.*1
Change the setting so that programs and parameters are stored in the

Settings in the Boot file tab

program memory in the first place, instead of booting from the standard ROM.

Type

Transfer from

Transfer to

Program

Standard ROM

Program memory

Parameter

Standard ROM

Program memory

• Move the programs and parameters with boot setting into the program
memory from the standard ROM.*1
• Delete all settings for parameter in the Boot file tab of the PLC parameter
dialog box.
Change the setting so that the Universal model QCPU can refer to the

Settings in the Boot file tab

parameters in the memory card, and programs are booted from the memory

Type

Transfer from

Transfer to

Program

Memory card

Program memory

(No boot file setting for parameters)

card to the program memory.
• Move the parameters in the standard ROM into the memory card.
• Make setting so that programs are booted from the memory card to the
program memory in the Boot file tab of the PLC parameter dialog box.*3

(To the next page)

App - 60

APPENDICES

TableApp.42 When the parameter-valid drive is set to the standard ROM (Continued)
Setting in High Performance model QCPU

Setting in Universal model QCPU

Setting in the Boot file tab of the PLC parameter
dialog box

Change the setting so that the Universal model QCPU can refer to the
parameters in the memory card, and programs and parameters are booted

Settings in the Boot file tab
Type

Transfer from

Transfer to

Program

Memory card

Program memory

Parameter

Memory card

Program memory

from the memory card to the program memory.

• Move the parameters in the standard ROM into the memory card.
• Make setting so that programs and parameters are booted from the memory
card to the program memory in the Boot file tab of the PLC parameter dialog
box.*3

Settings in the Boot file tab
Type

Transfer from

Transfer to

Memory card

Program memory

(Data other
than program

Delete all settings for data other than programs and parameters in the boot file

and parameter)

setting.
Since these data can be used even not stored in the program memory, it is not
necessary to transfer them to the program memory. Or, change the setting so

Settings in the Boot file tab
Type

APPENDIX

Transfer from

that they are stored in the program memory in the first place.
Transfer to

• Delete all settings for data other than programs and parameters in the Boot
file tab of the PLC parameter dialog box.

(Data other
than program Standard ROM

Program memory

and parameter)

• Move the data other than programs and parameters into the program
memory as needed.

(Data other than program and parameter indicate initial
device value, device comment, and label program.)

App - 61

Appendix 3 Method of Replacing Basic Model QCPU or High Performance Model QCPU with Universal
Model QCPU
Appendix 3.4 Functions

*1: Since the Universal model QCPU holds the data in the program memory even when the battery voltage drops, the boot file setting is not
necessary.
*2: The Universal model QCPU searches for parameters in order of in the program memory, in the memory card, and in the standard ROM.
Then, the module uses the parameters found first.
If parameters exist in the program memory or the memory card, the Universal model QCPU cannot use the parameters in the standard
ROM.
*3: The Universal model QCPU ignores the boot file setting for parameters in the standard ROM.

(b) When the parameter-valid drive is set to the memory card (RAM) or memory card (ROM) in
the High Performance model QCPU
TableApp.43 When the parameter-valid drive is set to the memory card (RAM) or memory card (ROM)
Setting in High Performance model QCPU
Setting in Universal model QCPU

Setting in the Boot file tab of the PLC parameter
dialog box

Change the setting so that the Universal model QCPU can refer to the
parameters in the memory card.

No boot file setting

• Changes in parameter settings are not required.
• Delete parameters that exist in the program memory.*2

Settings in the Boot file tab

Change the setting so that the Universal model QCPU can refer to the

Type

Transfer from

Transfer to

Program

Memory card

Program memory

parameters in the memory card.
• Changes in parameter settings are not required.
• Delete parameters that exist in the program memory.*2

(No boot file setting for parameters)
Settings in the Boot file tab
Type

Transfer from

Transfer to

Program

Memory card

Program memory

Parameter

Memory card

Program memory

No changes are required.

Change the setting so that programs are stored in the program memory in the
first place, instead of booting from the standard ROM.

Settings in the Boot file tab
Type

Transfer from

Transfer to

Program

Standard ROM

Program memory

• Move the programs targeted for booting from the standard ROM into the
program memory.*1
• Delete all settings for program in the Boot file tab of the PLC parameter
dialog box.

(No boot file setting for parameters)

• Delete parameters that exist in the program memory.*2
Change the setting so that programs are stored in the program memory in the

Settings in the Boot file tab

first place, instead of booting from the standard ROM.

Type

Transfer from

Transfer to

Program

Standard ROM

Program memory

Parameter

Memory card

Program memory

• Move the programs targeted for booting from the standard ROM into the
program memory.*1
• Delete all settings for program in the Boot file tab of the PLC parameter
dialog box.

Settings in the Boot file tab
Type

Transfer from

Transfer to

Memory card

Program memory

(Data other
than program

Delete all settings for data other than programs and parameters in the boot file

and parameter)

Since these data can be used even not stored in the program memory, it is not
necessary to transfer them to the program memory. Or, change the setting so

Settings in the Boot file tab
Type

setting.

Transfer from

that they are stored in the program memory in the first place.
Transfer to

than program Standard ROM

• Delete all settings for data other than programs and parameters in the Boot
file tab of the PLC parameter dialog box.

(Data other
Program memory

and parameter)

• Move the data other than programs and parameters into the program
memory as needed.

(Data other than program and parameter indicate initial
device value, device comment, and label program.)
*1: Since the Universal model QCPU holds the data in the program memory even when the battery voltage drops, the boot file setting is not
necessary.
*2: The Universal model QCPU searches for parameters in order of in the program memory, in the memory card, and in the standard ROM.
Then, the module uses the parameters found first.
If parameters exist in the program memory or the memory card, the Universal model QCPU cannot use the parameters in the standard
ROM.

App - 62

APPENDICES

Appendix 3.4.7 External input/output forced on/off function

(1) Differences between High Performance model QCPU and Universal model QCPU

(a) High Performance model QCPU
External input/output can be forcibly turned on/off on the screen opened by selecting [Online]
[Debug]

[Forced input output registration/cancellation] in GX Developer.

(b) Universal model QCPUNote1
The external input/output forced on/off function is not supported in the Universal model QCPU.

NoteApp.1

External input/output can be forcibly turned on/off by using the replacement program described below.

(2) Method of replacing High Performance model QCPU with Universal model QCPU
As shown in Figure App.29, add programs, "SETX" and "SETY", in the Program tab of the PLC parameter dialog

APPENDIX

box.

6
7
8

Figure App.29 Modification in the Program tab of the PLC parameter setting

The following table shows the program setting of the "SETX" and "SETY".

Program name

Execution type

Position where program is added

SETX

Scan

Start of Program setting (No.1)

SETY

Scan

End of Program setting

Note1

NoteApp.1

Universal

When performing an external input/output forced on/off operation for the Q02UCPU, Q03UDCPU, Q04UDHCPU,
Q06UDHCPU, Q13UDHCPU, or Q26UDHCPU, check the versions of the CPU module and GX Develover.
(

Appendix 2 )

App - 63

Appendix 3 Method of Replacing Basic Model QCPU or High Performance Model QCPU with Universal
Model QCPU
Appendix 3.4 Functions

TableApp.44 ÅgProgram setting of "SETX" and "SETY"

Example)

Forcibly turning X40, X77, and X7A on, and X41 and Y7B off

The programs, "SETX" and "SETY", turns on or off the X and Y devices, which have been registered
for forced on/off using the external input/output forced on/off function, at each scan using the SET and
RST instructions.
High Performance model QCPU

(1)
(2)
(3)
(4)
(5)

Universal model QCPU
• Program example of “SETX”

(1)
(2)

• Program example of “SETY”

(3)
(4)
(5)

App - 64

APPENDICES

(3) Replacing the COM instruction
If the COM instruction is used, add subroutine calls for P10 and P11 before and after the COM instruction. (P10 and P11 are pointers shown in the program examples in (2).) When SM775 is on (Executes
refresh set by SD778) and also the 0 bit of SD778 is off (Do not execute I/O refresh), replacement of

the instruction is not necessary.

(a) Program before replacement

Selection of refresh processing
during COM instruction execution

APPENDIX

(b) Program after replacement
Selection of refresh processing
during COM instruction execution

7
8

Appendix 3 Method of Replacing Basic Model QCPU or High Performance Model QCPU with Universal
Model QCPU
Appendix 3.4 Functions

App - 65

(4) Replacing the RFS instruction
If any I/O numbers targeted for forced on/off are included in the partial refresh range specified by the RFS instruction, add subroutine calls for P10 and P11 before and after the RFS instruction. (P10 and P11 are pointers shown
in the program examples in (2).)
If no I/O number targeted for forced on/off is included, addition of subroutine calls for P10 and P11 is not necessary.

(a) When partial refresh for input (X) is executed by the RFS instruction
Add a subroutine call that executes forced input after the RFS instruction.

A subroutine call that executes
forced input is added.

(b) When partial refresh for output (Y) is executed by the RFS instruction
Add a subroutine call that executes forced output before the RFS instruction.

A subroutine call that executes
forced output is added.

(5) Restrictions
Replacements described in (2) to (4) do not apply in the following cases.
• Input and output targeted for forced on/off are referred to or changed using the direct input device (DX) and
direct output device (DY).
• Input and output targeted for forced on/off are referred to or changed within an interrupt program.

App - 66

APPENDICES

Appendix 3.5 Special Relay and Special Register

The Universal model QCPU does not support the use of the special relay and special register described in Appendix
3.5.1 and Appendix 3.5.2.

Replace them using the method described in the table or delete the corresponding sections.

Appendix 3.5.1 Special relay list

TableApp.41 lists the special relay not supported in the Universal model QCPU and measures to be taken.
TableApp.45 Special relay not supported by the Universal model QCPU and measures
Number

Name/Description

Measures
The Universal model QCPU does not support the CHK

SM80

CHK detection

instruction. For the replacing method of the CHK

APPENDIX

instruction, refer to Appendix 3.3.3.
SM91

SM92
SM93

The Universal model QCPU does not support the step

SM94

transition monitoring timer function. For the replacing

SM95

Step transition monitoring timer start

SM96

method of this function, refer to “Appendix 3.
Restrictions and replacing method of the Basic model

QCPU and Universal model QCPU" in the QCPU (Q

SM97

Mode)/QnACPU Programming Manual (SFC).

SM98

SM99
Operation of SD250 is not necessary. The Universal
SM250

Largest mounted I/O number read

model QCPU always stores the largest mounted I/O

SM256
SM257

Indicates operative network or standby network
MELSECNET/H

At refresh from link module to CPU, selects

module 1

whether to read data from the link module.

information

At refresh from CPU to link module, selects
whether to write data to the link module.

SM260
SM261
SM262

Indicates operative network or standby network
MELSECNET/H

At refresh from link module to CPU, selects

module 2

whether to read data from the link module.

information

At refresh from CPU to link module, selects

These are special relays for the simple dual-structured

whether to write data to the link module.

network function. Since the Universal model QCPU

Indicates operative network or standby network

does not support this function, there is no application for

MELSECNET/H

At refresh from link module to CPU, selects

these special relays. Delete the corresponding sections.

module 3

whether to read data from the link module.

information

At refresh from CPU to link module, selects

SM265
SM266
SM267

whether to write data to the link module.
Indicates operative network or standby network

SM270
SM271
SM272

MELSECNET/H

At refresh from link module to CPU, selects

module 4

whether to read data from the link module.

information

At refresh from CPU to link module, selects
whether to write data to the link module.
(To the next page)

App - 67

Appendix 3 Method of Replacing Basic Model QCPU or High Performance Model QCPU with Universal
Model QCPU
Appendix 3.5 Special Relay and Special Register

number in SD250. Delete the corresponding sections.
SM255

TableApp.45 Special relay not supported in the Universal model QCPU and measures (Continued)
Number
SM280
SM315
SM330
SM331
SM332
SM390
SM404
SM405
SM430
SM431
SM432
SM433
SM434
SM510

Name/Description
CC-Link error

Measures
Replace the relay with the I/O signals (Xn0, Xn1, and XnF) of the mounted CC-Link
module.

Communication reserved time delay

Set a service processing time value in the PLC system tab of the PLC parameter dia-

enable/disable flag

log box.

Operation mode for low-speed

The Universal model QCPU does not support low-speed execution type programs.

execution type program

Delete the corresponding sections.

Normal SFC program execution
status

The Universal model QCPU supports only normal SFC programs. Delete SM331 and

Program execution management

SM332, which are used as interlocks, or replace them with SM321.

SFC program execution status
Access execution flag
ON for only 1 scan after RUN of lowspeed execution type programs
Off for only 1 scan after RUN of lowspeed execution type programs

Modify the program that Module ready signal (Xn) is used as an interlock, according
to sample programs described in the manual for each module.
The Universal model QCPU does not support low-speed execution type programs.
Delete the corresponding sections or replace them with the special relays for scan
execution type programs (SM402 and SM403).

User timing clock No.5 (for lowspeed execution type programs)
User timing clock No.6 (for lowspeed execution type programs)
User timing clock No.7 (for lowspeed execution type programs)
User timing clock No.8 (for low-

The Universal model QCPU does not support low-speed execution type programs.
Delete the corresponding sections or replace them with the special relays for scan
execution type programs (SM420 and SM424).

speed execution type programs)
User timing clock No.9 (for lowspeed execution type programs)
Low-speed execution type program

The Universal model QCPU does not support low-speed execution type programs.

executing flag

Delete the corresponding sections.

SM551

Module service interval time read

SM580

Program to program I/O refresh

SM660

Boot operation

The Universal model QCPU does not support the service interval measurement
function. Delete the corresponding sections.
Perform I/O refresh at the start or end of each program with the RFS or COM instruction.
Move files with a boot setting (from the standard ROM or a memory card to the program memory) to the program memory.
When outside the range of the file register in the memory card is accessed, the

SM672

Memory card file register access

Universal model QCPU detects "OPERATION ERROR" (error code: 4101).

range flag

Programming for detecting errors using this special realy is not necessary. Delete
the corresponding sections.

SM710

SM734

CHK instruction priority flag
XCALL instruction execution
condition specification

The Universal model QCPU does not support the CHK instruction. For the replacing
method of the CHK instruction, refer to Appendix 3.3.
The Universal model QCPU executes the XCALL instruction on the rising edge of
execution condition as well. There is no application for this special relay. Delete the
corresponding sections.
The Universal model QCPU does not support the following instructions:

SM735

SFC comment readout instruction inexecution flag

• SFC step comment readout instruction (S(P).SFCSCOMR)
• SFC transition condition comment readout instruction (S(P).SFCTCOMR)
Delete the corresponding sections.
(To the next page)

App - 68

APPENDICES

TableApp.45 Special relay not supported in the Universal model QCPU and measures (Continued)
Number
SM1780*1
SM1781

SM1782*1
SM1783*1

Name/Description

Measures

Power supply off detection flag
Power supply failure detection flag

The Universal model QCPU does not store redundant power supply system

Momentary power failure detection

information in SM1780 to SM1783. Delete the corresponding sections. (SM1780 to

flag for power supply 1

SM1783 are always off.)

Momentary power failure detection
flag for power supply 2

*1: The special relay can be used if the serial number (first five digits) of the Universal model QCPU is "10042" or later.

APPENDIX

6
7
8

Appendix 3 Method of Replacing Basic Model QCPU or High Performance Model QCPU with Universal
Model QCPU
Appendix 3.5 Special Relay and Special Register

App - 69

Appendix 3.5.2 Special register list
TableApp.42 lists the special register not supported in the Universal model QCPU and measures to be
taken
TableApp.46 Special register not supported in the Universal model QCPU and measures
Number
SD80

Name/Description
CHK number

Measures
The Universal model QCPU does not support the CHK instruction. For the replacing
method of the CHK instruction, refer to Appendix 3.3.

SD90
SD91
SD92
SD93

The Universal model QCPU does not support the step transition monitoring timer

SD94

Step transition monitoring timer

function. For the replacing method of this function, refer to ”Appendix 3. Restrictions

SD95

setting value

and replacing method of the Basic model QCPU and Universal model QCPU" in the
QCPU (Q Mode)/QnACPU Programming Manual (SFC).

SD96
SD97
SD98
SD99
SD130 to
SD137
SD150 to
SD157
SD245
SD246
SD280
SD281

Fuse blown module

Replace SD130 to SD137 with SD1300 to SD1307.

I/O module verify error

Replace SD150 to SD157 with SD1400 to SD1407.

No. of base slots (Mounting status)

Replace SD245 and SD246 with SD243 and SD244, respectively.

CC-Link error

Replace these registers with the I/O signals (Xn0, Xn1, and XnF) of the mounted CCLink module.
Service processing setting is available for the Universal model QCPU on the PLC

SD315

Time reserved for communication

system setting tab of the PLC parameter dialog box.

processing

Select "Specify service process time." for the service processing setting parameter
and set the service processing time. Other setting methods can be selected as well.
• Check the type and model of other CPU modules mounted on the System monitor

SD394

CPU mounting information

screen of GX Developer.
• Check the mounting status of other CPU modules in SD396 to SD398.
The Universal model QCPU does not support low-speed execution type programs.

SD430

Low-speed scan counter

Delete the corresponding sections or replace them with the special register for scan
execution type programs (SD420).

SD510
SD528

Low-speed execution type program
number
Current scan time for low-speed

The Universal model QCPU does not support low-speed execution type programs.
Delete the corresponding sections or replace them with the special register for scan
execution type programs (SD500).
The Universal model QCPU does not support low-speed execution type programs.
Delete the corresponding sections or replace them with the special register for scan

SD529

execution type programs

SD532

Minimum scan time for low-speed

SD533

execution type programs

SD534

Maximum scan time for low-speed

SD535

execution type programs

SD544

Cumulative execution time for low-

The Universal model QCPU does not support low-speed execution type programs.

SD545

speed execution type programs

Delete the corresponding sections.

SD546

Execution time for low-speed

The Universal model QCPU does not support low-speed execution type programs.

SD547

execution type programs

Delete the corresponding sections.

execution type programs (SD520 and SD521).
The Universal model QCPU does not support low-speed execution type programs.
Delete the corresponding sections or replace them with the special registers for scan
execution type programs (SD524 to SD527).

(To the next page)

App - 70

APPENDICES

TableApp.46 Special register not supported in the Universal model QCPU and measures (Continued)
Number

Name/Description

Measures

Service interval measurement

SD550

module

SD551

Service interval time

SD552
SD720

The Universal model QCPU does not support the PLAODP instruction. Delete the

PLAODP instruction

corresponding sections.

SD1780

Power supply off detection status

SD1781

Power supply failure detection status

SD1783 *1

function. Delete the corresponding sections.

Program No. specification for
*1

SD1782 *1

The Universal model QCPU does not support the service interval measurement

The Universal model QCPU does not store redundant power supply system

Momentary power failure detection

information in SD1780 to SD1783. Delete the corresponding sections. (SD1780 to

counter for power supply 1

SD1783 are always off.)

Momentary power failure detection

APPENDIX

counter for power supply 1

*1: The special register can be used if the serial number (first five digits)of the Universal model QCPU is "10042" or later.

7
8

Appendix 3 Method of Replacing Basic Model QCPU or High Performance Model QCPU with Universal
Model QCPU
Appendix 3.5 Special Relay and Special Register

App - 71

Appendix 4 Device Point Assignment Sheet

TableApp.47 Device point assignment sheet
Device name

Symbol

Numeric
notation

Number of device point *2
Points

Restriction check
Size (words)*3

Range

Points (bits)*2

Input relay*1

Hexadecimal

8K (8192)

X0000 to X1FFF

/16

512

8192

Output relay*1

Hexadecimal

8K (8192)

Y0000 to Y1FFF

/16

512

8192

Internal relay

Decimal

)

M0 to

/16

Latch relay

Decimal

)

L0 to

/16

Link relay

Hexadecimal

)

B0000 to

/16

Annunciator

Decimal

)

F0 to

/16

Link special relay

Hexadecimal

)

SB0000 to

/16

Edge relay

Decimal

)

V0 to

/16

Step relay*1

Decimal

S0 to S8191

/16

Timer

Decimal

)

T0 to

18
16

Retentive timer

Decimal

)

ST0 to

18
16

Counter

Decimal

)

C0 to

18
16

Data register

Decimal

)

D0 to

Link register

Hexadecimal

)

W0000 to

Link special
register

Hexadecimal

)

SW0000 to

Total

8K (8192)

512

(29696 or less)

8192

(65536 or less)

App - 72

INDEX
[A]
Acknowledge XY assignment . . . . . . . . . . . . . . . 8-16
Annunciator (F)
Processing after annunciator off . . . . . . . . . . . 9-14
Processing after annunciator on . . . . . . . . . . . 9-12
ASCII code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43
Auto mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Auto refresh setting . . . . . . . . . . . . . . . . . . . . . . . . 7-2
[B]
B (Link relay) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16
Backup data restoration function . . . . . . . . . . . . 6-157
Backup function to memory card . . . . . . . . . . . . 6-149
Base unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-21
Battery life-prolonging function . . . . . . . . . . . . . 6-139
BCD (Binary-coded decimal) . . . . . . . . . . . . . . . . 2-38
BIN (Binary code) . . . . . . . . . . . . . . . . . . . . . . . . 2-35
BL (SFC block device). . . . . . . . . . . . . . . . . . . . . 9-78
Boot operation . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23
Built-in Ethernet port of the CPU module . . . . . . 1-12
Built-in Ethernet port setting . . . . . . . . . . . . . . . . 8-19
[C]
C (Counter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-27
CC-Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-22
Changing clock data . . . . . . . . . . . . . . . . . . . . . . 6-14
Changing the program execution type. . . . . . . . . 2-30
Character string . . . . . . . . . . . . . . . . . . . . . . . . . . 9-83
Checking the function version . . . . . . . . . . . . . . . 1-13
Checking the serial number. . . . . . . . . . . . . . . . . 1-13
Clearing
Clearing data in the latch relay . . . . . . . . . . . . 9-10
Clearing local device data . . . . . . . . . . . . . . . . 9-94
Clearing the counter value . . . . . . . . . . . . . . . . 9-28
Clearing the error history data . . . . . . . . . . . . 6-105
Clearing the file register data . . . . . . . . . . . . . . 9-54
Clearing the retentive timer value . . . . . . . . . . 9-22
Remote latch clear . . . . . . . . . . . . . . . . . . . . . . 6-25
Clock function . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13
Common pointer . . . . . . . . . . . . . . . . . . . . . . . . . 9-74
Communications with the FROM and TO
instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Constant scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Counter (C)
Counting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-27
Resetting the counter . . . . . . . . . . . . . . . . . . . . 9-28
CPU module change function with memory card
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-147
Cyclic transmission area device (U3En\G) . . . . 9-45
[D]
D (Data register) . . . . . . . . . . . . . . . . . . . . . . . . . 9-31

1
Data clear processing . . . . . . . . . . . . . . . . . . . . . . 3-6
Data register (D) . . . . . . . . . . . . . . . . . . . . . . . . . 9-31
Debug execution
Operation procedure . . . . . . . . . . . . . . . . . . . . 6-92
Debug function from multiple GX Developers . . . 6-91
Decimal constant (K) . . . . . . . . . . . . . . . . . . . . . . 9-81
Detail mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Device list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Device point assignment sheet . . . . . . . . . . . .App-72
Device setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
Direct access input . . . . . . . . . . . . . . . . . . . . . . . 3-12
Direct access input (DX) . . . . . . . . . . . . . . . . . . . 3-12
Direct access output . . . . . . . . . . . . . . . . . . . . . . 3-12
Direct access output (DY) . . . . . . . . . . . . . . . . . . 3-12
Direct mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Double-precision floating-point data . . . . . . . . . . 2-41
Duty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-30
DX (Direct access input) . . . . . . . . . . . . . . . . . . . 3-12
DY (Direct access output) . . . . . . . . . . . . . . . . . . 3-12
[E]
E (Real number) . . . . . . . . . . . . . . . . . . . . . . . . . 9-82
Edge relay (V) . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15
END processing. . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Error
Clearing errors . . . . . . . . . . . . . . . . . . . . . . . . 6-104
Error time output mode setting. . . . . . . . . . . . . 6-29
Operating mode when there is an error . . . . . . . 8-6
Error history . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-105
Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-22
Execution time measurement . . . . . . . . . . . . . . . 6-69
Executional conditioned device test. . . . . . . . . . . 6-48
Extended data register (D). . . . . . . . . . . . . . . . . . 9-64
Extended link register (W) . . . . . . . . . . . . . . . . . . 9-64
Extension base unit . . . . . . . . . . . . . . . . . . . . . . .A-21
External input/output forced on/off. . . . . . . . . . . . 6-43
[F]
F (Annunciator) . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11
FD (Function register) . . . . . . . . . . . . . . . . . . . . . 9-36
File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30
File register
Accesses available for the file register . . . . . . . 9-55
Block switching method . . . . . . . . . . . . . . . . . . 9-61
Clearing the file register data . . . . . . . . . . . . . . 9-54
Serial number access method . . . . . . . . . . . . . 9-61
File size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
File usability setting . . . . . . . . . . . . . . . . . . . . . . . 2-15
Fixed scan execution type program. . . . . . . . . . . 2-26
Floating-point data . . . . . . . . . . . . . . . . . . . . . . . . 2-39
Forced on/off . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-43
Formatting
Formatting the ATA card . . . . . . . . . . . . . . . . . 5-15
Formatting the SRAM card. . . . . . . . . . . . . . . . 5-15

Index - 1

2
3
4
INDEX

INDEX

7
8

Memory card clear . . . . . . . . . . . . . . . . . . . . . 5-15
Function devices (FX, FY, FD) . . . . . . . . . . . . . . 9-35
Function list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
FX (Function input) . . . . . . . . . . . . . . . . . . . . . . . 9-35
FY (Function output) . . . . . . . . . . . . . . . . . . . . . . 9-36
[G]
Global device . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-84
GOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-22
GX Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
GX Developer . . . . . . . . . . . . . . . . . . . . . . . . . . . A-22

List of interrupt factors. . . . . . . . . . . . . . . . . . . 9-77
Interrupt program/Fixed scan program setting . . . 8-4
[J]
J (Network No. specification device). . . . . . . . . . 9-78
J\ (Link direct device) . . . . . . . . . . . . . . . . . . 9-40
[K]
K (Decimal constant) . . . . . . . . . . . . . . . . . . . . . 9-81
[L]

[H]
H (Hexadecimal constant) . . . . . . . . . . . . . . . . .
H/W error time PLC operation mode . . . . . . . . .
H/W error time PLC operation mode setting. . . .
Hardware check . . . . . . . . . . . . . . . . . . . . . . . . .
HEX (Hexadecimal) . . . . . . . . . . . . . . . . . . . . . .
Hexadecimal constant (H) . . . . . . . . . . . . . . . . .
High-speed timer (T). . . . . . . . . . . . . . . . . . . . . .

9-81
6-30
6-30
11-3
2-37
9-81
9-21

[I]
I (Interrupt pointer) . . . . . . . . . . . . . . . . . . . . . . . 9-76
I/O assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
I/O assignment on remote I/O stations . . . . . . . . . 4-6
I/O No. specification device (U) . . . . . . . . . . . . . 9-79
I/O number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
I/O number assignment . . . . . . . . . . . . . . . . . . . . 4-1
I/O processing and response delay . . . . . . . . . . . 3-8
I/O response time . . . . . . . . . . . . . . . . . . . . . . . . 6-27
Index register (Z)
Restoring the index register data . . . . . . . . . . 9-49
Saving the index register data . . . . . . . . . . . . 9-49
Initial device value . . . . . . . . . . . . . . . . . . . . . . 6-135
Initial execution monitoring time . . . . . . . . . . . . . 2-19
Initial execution type program. . . . . . . . . . . . . . . 2-17
Initial processing. . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Initial setting . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2,7-5
Input (X) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6
Intelligent function module
Intelligent function module dedicated
instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
Intelligent function module device (U\G). . 9-43
Intelligent function module switch setting . . . . 6-31
Interrupt form intelligent function module . . . 6-119
Intelligent function module setting . . . . . . . . . . . . 8-3
Internal relay (M) . . . . . . . . . . . . . . . . . . . . . . . . . 9-9
Internal system device . . . . . . . . . . . . . . . . . . . . 9-35
Internal user device . . . . . . . . . . . . . . . . . . . . . . . 9-3
Interrupt
Interrupt form intelligent function module . . . 6-119
Interrupt module . . . . . . . . . . . . . . . . . . . . . . . 6-27
Interrupt pointer (I) . . . . . . . . . . . . . . . . . . . . . 9-76
Interrupt pointer setting . . . . . . . . . . . . . . . . . . . 8-3
Interrupt program . . . . . . . . . . . . . . . . . . . . . . . 2-6
Interrupt program monitor list . . . . . . . . . . . . . 6-72

Index - 2

L (Latch relay). . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10
Ladder mode. . . . . . . . . . . . . . . . . . . . . . . . . 2-2,6-58
Latch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Latch clear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Latch clear operation disable range
(Latch (2) start/end) . . . . . . . . . . . . . . . . . . . . . . . 3-7
Latch clear operation enable range
(Latch (1) start/end) . . . . . . . . . . . . . . . . . . . . . . . 3-7
Latch data backup to standard ROM function
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-141
Latch function . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Latch relay (L). . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10
LED
Methods for turning off the LEDs . . . . . . . . . 6-116
Link direct device (J\) . . . . . . . . . . . . . . . . . . 9-40
Link register (W) . . . . . . . . . . . . . . . . . . . . . . . . . 9-32
Link relay (B). . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16
Link special register (SW). . . . . . . . . . . . . . . . . . 9-34
Link special relay (SB) . . . . . . . . . . . . . . . . . . . . 9-18
List mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Local device . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-85
Clearing local device data . . . . . . . . . . . . . . . . 9-94
Local device monitor . . . . . . . . . . . . . . . . . . . . 6-40
Local pointer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-72
Low-speed timer (T) . . . . . . . . . . . . . . . . . . . . . . 9-21
[M]
M (Internal relay). . . . . . . . . . . . . . . . . . . . . . . . . . 9-9
Macro instruction argument device (VD) . . . . . . 9-80
Main base unit . . . . . . . . . . . . . . . . . . . . . . . . . . A-21
Main routine program . . . . . . . . . . . . . . . . . . . . . . 2-4
Maximum counting speed. . . . . . . . . . . . . . . . . . 9-30
MELSECNET/H . . . . . . . . . . . . . . . . . . . . . . . . . A-22
Memory capacities of files . . . . . . . . . . . . . . . . . 5-34
Memory capacity. . . . . . . . . . . . . . . . . . . . . . . . . 5-34
Memory card. . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
Memory check function. . . . . . . . . . . . . . . . . . . 6-140
Memory composition. . . . . . . . . . . . . . . . . . . . . . . 5-1
Module service interval . . . . . . . . . . . . . . . . . . . 6-128
Momentary power failure . . . . . . . . . . . . . . . . . . . 3-5
Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-33
Monitor condition setting. . . . . . . . . . . . . . . . . . . 6-34
Motion CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-21

Multiple CPU high speed transmission area
setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18
Multiple CPU settings . . . . . . . . . . . . . . . . . . . . . 8-17
Multiple CPU synchronous interrupt . . . . . . . . . . 9-76
[N]
N (Nesting) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-70
Nesting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-70
Network No. specification device (J) . . . . . . . . . . 9-78
Network parameters . . . . . . . . . . . . . . . . . . . . . . 8-21
[O]
Online change . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-58
Online change (files) . . . . . . . . . . . . . . . . . . . . 6-61
Online change (ladder mode) . . . . . . . . . . . . . 6-58
Online change from multiple GX Developers . . . 6-93
Output mode at STOP to RUN . . . . . . . . . . . . . . 6-11
[P]
P (Pointer) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-71
Parameters
Network parameters. . . . . . . . . . . . . . . . . . . . . 8-21
PLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-106
PAUSE status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
PC CPU module . . . . . . . . . . . . . . . . . . . . . . . . . A-21
PC RAS (1) setting . . . . . . . . . . . . . . . . . . . . . . . . 8-6
PLC file setting . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
PLC name setting . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
PLC parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Pointer
Common pointer . . . . . . . . . . . . . . . . . . . . . . . 9-74
Interrupt pointer . . . . . . . . . . . . . . . . . . . . . . . . 9-76
Local pointer . . . . . . . . . . . . . . . . . . . . . . . . . . 9-72
Points occupied by empty slot . . . . . . . . . . . . . . . . 8-4
Procedure
Procedure for boot run . . . . . . . . . . . . . . . . . . . 5-24
Procedure for writing a program . . . . . . . . . . . 5-19
Program cache memory . . . . . . . . . . . . . . . . . . . . 5-8
Program monitor list . . . . . . . . . . . . . . . . . . . . . . 6-69
Program setting . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10
Protection
Password registration . . . . . . . . . . . . . . . . . . 6-106
Remote password . . . . . . . . . . . . . . . . . . . . . 6-108
[Q]
Q series power supply module . . . . . . . . . . . . . . A-22
Q3B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-21
Q3DB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-21
Q3RB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-21
Q3SB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-21
Q5B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-21
Q6B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-21
Q6RB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-21
QI60. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-27

QnUD(H)CPU . . . . . . . . . . . . . . . . . . . . . . . . . . .A-21

[R]
R (File register) . . . . . . . . . . . . . . . . . . . . . . . . . . 9-53
Reading clock data . . . . . . . . . . . . . . . . . . . . . . . 6-15
Redundant power extension base unit . . . . . . . .A-21
Redundant power main base unit . . . . . . . . . . . .A-21
Refresh mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Remote latch clear. . . . . . . . . . . . . . . . . . . . . . . . 6-25
Remote operation . . . . . . . . . . . . . . . . . . . . . . . . 6-18
Remote password . . . . . . . . . . . . . . . . . . . . . . . 6-108
Remote PAUSE . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21
Remote RESET . . . . . . . . . . . . . . . . . . . . . . . . . . 6-23
Remote RUN/STOP. . . . . . . . . . . . . . . . . . . . . . . 6-18
RUN status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

2
3
4
INDEX

[S]
S (Step relay). . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19
Sampling trace. . . . . . . . . . . . . . . . . . . . . . . . . . . 6-77
SB (Link special relay) . . . . . . . . . . . . . . . . . . . . . 9-18
Scan execution type program . . . . . . . . . . . . . . . 2-20
Scan time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
Scan time accuracy . . . . . . . . . . . . . . . . . . . . . . . 2-18
Scan time measurement . . . . . . . . . . . . . . . . . . . 6-73
SD (Special register) . . . . . . . . . . . . . . . . . . . . . . 9-38
Self-diagnostic function . . . . . . . . . . . . . . . . . . . . 6-97
Serial communication function. . . . . . . . . . . . . . 6-120
Serial setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-15
Service processing . . . . . . . . . . . . . . . . . . . . . . 6-128
Service processing setting. . . . . . . . . . . . . . . . . 6-128
Setting in GX Configurator. . . . . . . . . . . . . . . . . . . 7-2
SFC block device (BL) . . . . . . . . . . . . . . . . . . . . . 9-78
SFC setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12
Single-precision floating-point data . . . . . . . . . . . 2-39
Size (file capacity) . . . . . . . . . . . . . . . . . . . . . . . . 5-34
Slim type main base unit . . . . . . . . . . . . . . . . . . .A-21
Slim type power supply module . . . . . . . . . . . . . .A-22
SM (Special relay) . . . . . . . . . . . . . . . . . . . . . . . . 9-38
Special register (SD) . . . . . . . . . . . . . . . . . . . . . . 9-38
Special relay (SM) . . . . . . . . . . . . . . . . . . . . . . . . 9-38
ST (Retentive timer). . . . . . . . . . . . . . . . . . . . . . . 9-22
Standard device register (Z) . . . . . . . . . . . . . . . . 9-48
Standard RAM . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Standard ROM. . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
Stand-by type program . . . . . . . . . . . . . . . . . . . . 2-21
Step relay (S). . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19
STOP status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Subroutine program . . . . . . . . . . . . . . . . . . . . . . . . 2-5
SW (Link special register) . . . . . . . . . . . . . . . . . . 9-34
Switch setting
Intelligent function module switch setting. . . . . 6-31
System protection . . . . . . . . . . . . . . . . . . . . . . . 6-106
[T]
T (Timer) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-20
Timer (T)

Index - 3

INDEX

7
8

Accuracy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-24
Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-23
Timer limit setting . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Transferring data to the program memory . . . . . . 5-9
[U]
U (I/O No. specification device) . . . . . . . . . . . . . 9-79
U3En\G (Cyclic transmission area device) . . . 9-45
Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36
Units of file sizes. . . . . . . . . . . . . . . . . . . . . . . . . 5-36
U\G (Intelligent function module device) . . . 9-43
User setting system area . . . . . . . . . . . . . . . . . . . 5-5
[V]
V (Edge relay). . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15
VD (Macro instruction argument device) . . . . . . 9-80
[W]
W (Link register) . . . . . . . . . . . . . . . . . . . . . . . . . 9-32
Watchdog timer (WDT). . . . . . . . . . . . . . . . . . . . 6-95
WDT (Watchdog timer). . . . . . . . . . . . . . . . . . . . 6-95
WDT setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-95
Write the program memory to ROM . . . . . . . . . . 5-18
Write to PLC (Flash ROM) . . . . . . . . . . . . . . . . . 5-20
Writing
Writing data to the memory card . . . . . . . . . . . 5-16
Writing data to the program memory . . . . . . . . 5-7
Writing data to the standard RAM . . . . . . . . . . 5-13
Writing data to the standard ROM . . . . . . . . . 5-11
Writing/reading device data to/from standard
ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-146
[X]
X (Input) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6
[Y]
Y (Output) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8
[Z]
Z (Index register) . . . . . . . . . . . . . . . . . . . . . . . . 9-46
Z (Standard device register) . . . . . . . . . . . . . . . . 9-48
ZR (Serial number access method of file
register) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-61

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.

Microsoft, Windows, Windows NT, Windows Vista are registered trademarks of Microsoft Corporation in the United States
and other countries.
Pentium and Celeron are trademarks of Intel Corporation in the United States and other countries.
Ethernet is a trademark of Xerox Co., Ltd. in the United States.
CompactFlash is a trademark of SanDisk Corporation.
VxWorks, Tornado, WindPower, WindSh and WindView are registered trademarks of Wind River Systems, Inc.
Other company names and product names used in this document are trademarks or registered trademarks of respective
owners.

SH(NA)-080807ENG-D

Source Exif Data:

File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.3
Linearized                      : Yes
Encryption                      : Standard V1.2 (40-bit)
User Access                     : Print, Copy, Annotate, Fill forms, Extract, Assemble, Print high-res
Create Date                     : 2009:11:19 08:32:41Z
Subject                         : SH-080807ENG-D
Author                          : 
Keywords                        : eMANUAL
Modify Date                     : 2009:11:19 10:26:08+09:00
Page Mode                       : UseOutlines
XMP Toolkit                     : 3.1-702
Producer                        : Acrobat Distiller 7.0.5 (Windows)
Creator Tool                    : FrameMaker 7.1
Metadata Date                   : 2009:11:19 10:24:59+09:00
Format                          : application/pdf
Title                           : QnUCPU User's Manual (Function Explanation, Program Fundamentals)
Creator                         : 
Description                     : SH-080807ENG-D
Document ID                     : uuid:0169e870-4c93-4ab7-9b53-b2f0b7a19c56
Instance ID                     : uuid:6c528842-9111-4cc3-b6f1-f11edae8ba7e
Page Count                      : 630
Page Layout                     : SinglePage

EXIF Metadata provided by EXIF.tools

Mitsubishi Electronics Digital Home Theater Server Qnucpu Users Manual User's (Function Explanation, Program Fundamentals)

QnUCPU to the manual 5f0c62ae-3154-4750-b924-eaffe9077da0

Navigation menu

Versions of this User Manual:

Views

Navigation